Page 1 of 2
Re: How clean are your boots
Posted: 2018-04-15 12:48
by Wheelerof4te
@dcihon Yeah, you have many partitions. Plus, snaps must be mounted, too. Don't know why they take so long, but then again I don't use them.
Flatpaks FTW.
Seriously, that looks like a mess. Really dirty
Re: How clean are your boots
Posted: 2018-04-15 12:57
by None1975
My boots. Clean and fast. About 8 sec. (system on traditional spinning hard drive (hdd)
Code: Select all
systemd-analyze blame
3.821s keyboard-setup.service
3.677s dev-sda1.device
3.273s ufw.service
747ms systemd-tmpfiles-setup-dev.service
546ms systemd-udevd.service
451ms rsyslog.service
451ms atopacct.service
451ms systemd-user-sessions.service
339ms systemd-logind.service
285ms dev-mqueue.mount
272ms sys-kernel-debug.mount
271ms dev-hugepages.mount
243ms systemd-udev-trigger.service
241ms systemd-timesyncd.service
239ms user@1000.service
238ms systemd-remount-fs.service
231ms systemd-fsck@dev-disk-by\x2duuid-f8b6e55b\x2d99dc\x2d4585\x2d8df8\x2d52c55677b22b.service
190ms systemd-modules-load.service
185ms dev-disk-by\x2duuid-5540013f\x2d2eed\x2d412e\x2dba2d\x2df4d8bc3af386.swap
177ms systemd-journal-flush.service
176ms networking.service
174ms systemd-journald.service
171ms systemd-sysctl.service
150ms systemd-random-seed.service
136ms systemd-tmpfiles-setup.service
134ms systemd-update-utmp.service
121ms console-setup.service
104ms home.mount
61ms kmod-static-nodes.service
53ms systemd-tmpfiles-clean.service
7ms alsa-restore.service
5ms systemd-update-utmp-runlevel.service
Startup time
Code: Select all
systemd-analyze
Startup finished in 2.637s (kernel) + 5.907s (userspace) = 8.545s
Re: How clean are your boots
Posted: 2018-04-15 18:00
by Lysander
Same here, None1975. I'm using an SSD but I suspect your overall hardware is superior to mine.
Code: Select all
lysander@psychopig-xxxiii:~$ systemd-analyze blame
5.431s NetworkManager-wait-online.service
1.586s keyboard-setup.service
1.496s systemd-journal-flush.service
1.402s dev-sdc1.device
705ms ufw.service
457ms mnt-01C962C5B094A220.mount
294ms ModemManager.service
217ms systemd-logind.service
209ms sddm.service
180ms lm-sensors.service
171ms systemd-timesyncd.service
165ms virtualbox.service
151ms pppd-dns.service
149ms rsyslog.service
130ms systemd-udevd.service
121ms accounts-daemon.service
120ms systemd-journald.service
116ms NetworkManager.service
114ms upower.service
97ms dev-disk-by\x2duuid-48548a61\x2de316\x2d42e3\x2db7c1\x2de074029fa679.swap
95ms networking.service
91ms udisks2.service
90ms systemd-udev-trigger.service
79ms avahi-daemon.service
79ms rtkit-daemon.service
75ms packagekit.service
63ms alsa-restore.service
62ms user@116.service
59ms binfmt-support.service
59ms gdomap.service
55ms user@1000.service
47ms speech-dispatcher.service
47ms systemd-tmpfiles-setup-dev.service
44ms colord.service
42ms systemd-fsck@dev-disk-by\x2duuid-c6406cea\x2db96c\x2d48c1\x2da33f\x2d804c9f611ae6.service
40ms polkit.service
35ms systemd-tmpfiles-setup.service
34ms systemd-modules-load.service
32ms gdm.service
29ms geoclue.service
24ms sys-kernel-debug.mount
23ms dev-mqueue.mount
22ms wpa_supplicant.service
21ms proc-sys-fs-binfmt_misc.mount
21ms dev-hugepages.mount
20ms systemd-random-seed.service
18ms systemd-user-sessions.service
16ms systemd-remount-fs.service
16ms kmod-static-nodes.service
15ms home.mount
14ms systemd-update-utmp.service
13ms sys-fs-fuse-connections.mount
13ms hddtemp.service
10ms systemd-sysctl.service
8ms systemd-update-utmp-runlevel.service
7ms console-setup.service
7ms minissdpd.service
Code: Select all
lysander@psychopig-xxxiii:~$ systemd-analyze
Startup finished in 2.268s (kernel) + 7.915s (userspace) = 10.184s
By comparison Slackware with SvsV takes between 50-60 seconds to boot [both VM and bare metal] but I have never had a boot issue with it, unlike in systemd.
Re: How clean are your boots
Posted: 2018-04-15 19:53
by anticapitalista
Using antiX with sysvinit and eudev, slim login and herbstluftwm.
i5 lenovo thinkpad L412 laptop, ssd, 6GB RAM.
Boot time is less than 10 secs.
Code: Select all
inxi -Fxz
System: Host: antix1 Kernel: 4.16.2-antix.2-amd64-smp x86_64 bits: 64 compiler: gcc v: 6.3.0
Desktop: herbstluftwm Distro: antiX-17.a2_x64-full keerfa 16 February 2017
Machine: Type: Laptop System: LENOVO product: 0585W28 v: ThinkPad L412 serial: N/A
Mobo: LENOVO model: 0585W28 serial: N/A BIOS: LENOVO v: 81ET63WW (1.39 ) date: 04/11/2013
Battery: ID-1: BAT1 charge: 21.3 Wh condition: 21.5/47.5 Wh (45%) model: SANYO 42T4751 status: Unknown
CPU: Topology: Dual Core model: Intel Core i5 M 520 type: MT MCP arch: Nehalem rev: 2 L2 cache: 3072 KiB
flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 19151
Speed: 1312 MHz min/max: 1199/2400 MHz Core speeds (MHz): 1: 1264 2: 1363 3: 1354 4: 1432
Graphics: Card-1: Intel Core Processor Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0
Display: server: X.Org 1.19.2 driver: intel resolution: 1366x768~60Hz
OpenGL: renderer: Mesa DRI Intel Ironlake Mobile v: 2.1 Mesa 13.0.6 direct render: Yes
Audio: Card-1: Intel 5 Series/3400 Series High Definition Audio driver: snd_hda_intel v: kernel
bus ID: 00:1b.0
Sound Server: ALSA v: k4.16.2-antix.2-amd64-smp
Network: Card-1: Intel Centrino Advanced-N 6200 driver: iwlwifi v: kernel bus ID: 03:00.0
IF: wlan0 state: up mac: <filter>
Card-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet driver: r8169 v: 2.3LK-NAPI
port: 2000 bus ID: 04:00.0
IF: eth0 state: down mac: <filter>
Drives: HDD Total Size: 111.79 GiB used: 65.99 GiB (59.0%)
ID-1: /dev/sda model: SanDisk_SDSSDA12 size: 111.79 GiB
Partition: ID-1: / size: 109.53 GiB used: 65.99 GiB (60.2%) fs: ext4 dev: /dev/sda1
Sensors: System Temperatures: cpu: 40.0 C mobo: 0.0 C
Fan Speeds (RPM): cpu: 0
Info: Processes: 156 Uptime: 5m Memory: 7.60 GiB used: 558.6 MiB (7.2%) Init: SysVinit runlevel: 5
Compilers: gcc: 6.3.0 Shell: bash v: 4.4.12 inxi: 3.0.03
Re: How clean are your boots
Posted: 2018-04-16 01:14
by llivv
stevepusser wrote:
with backported Debian 4.15 kernels, but they don't appear at all with backported 4.15 Liquorix kernels. Either way, both kernels run just fine for me regardless of whatever pstore is, and others don't report the messages on their machines at all.
mine are cleaning right up after replacing the old 686-pae kernels with amd64 kernels.
and debootstraping new userspace since it's way easier than relinking new libs.
stevepusser wrote:
hehe glad you got the double meaning in the title
Re: How clean are your boots
Posted: 2018-04-29 19:12
by llivv
I had to go back to a 2.6 kernel in squeeze to get a clean ( no kworker ) boot.
I got close right after a minimal install of jessie, but as soon as userland was added boots got dirty real fast.