...
Boot time thread
Henry Price
Grayson Smith
> systemd-analyze
Startup finished in 2.776s (kernel) + 9.605s (userspace) = 12.382s
Aiden Gonzalez
...
Luis Jackson
Startup finished in 4.792s (kernel) + 2.853s (userspace) = 7.646s
Landon Campbell
Startup finished in 2.672s (kernel) + 8.656s (userspace) = 11.328s
Kayden Rodriguez
>11.593s (kernel) + 18.249s (userspace = 29.843s
that sounds low actually, considering how long the BIOS takes to lovingly fondle all its devices and disks at boot time
Henry Powell
>Startup finished in 1.508s (kernel) + 1.309s (initrd) + 1.614s (userspace) = 4.433s
wew
William Gonzalez
>Startup finished in 2.302s (kernel) + 1.956s (userspace) = 4.258s
I'm using Arch btw.
Noah Rodriguez
systemd? Hahaha
Grayson Collins
does anyone happen to know how to prevent eth0 from trying to connect to the network when it's not plugged in? It takes a few seconds during boot that are wasted. I'm on the latest slackware
Anthony Brooks
...
Hudson Flores
...
Connor Peterson
looks like nobody using apparmor
Parker Gray
Startup finished in 1.355s (kernel) + 2.180s (userspace) = 3.535s
Austin Martin
systemd-analyze
Startup finished in 4.532s (kernel) + 39.697s (userspace) = 44.229s
Austin Lopez
>bloatd
Samuel Ortiz
>17.868s (firmware)
X99 user detected
Thomas Cruz
Startup finished in 29.614s (firmware) + 5.388s (loader) + 2.091s (kernel) + 13.633s (userspace) = 50.728s
Fucking this, send help
Colton Sanders
Startup finished in
Kernel 2.913s
Userspace 7.135s
Total 10.049s
(laptop, 4700qm + samsung 840pro 256gb + debian testing)
Parker Morales
...
James Gonzalez
>systemd-analyze
systemd-analyze isn't accurate as it doesn't account for how long the hardware takes to start. You gotta time it from when you press the button.
Jose Hall
...
Logan Sanchez
>Startup finished in 1.614s (kernel) + 4.651s (userspace) = 6.266s
Daniel Myers
...
Nicholas Davis
...