Why does it take forever for linux distros to start up? fedora

>>61108636
Install gentoo

Thats a problem with Fedora more than anything else. Shit show

>>61108636
Works on my machine. Gentoo on an SSD with OpenRC boots up in just under 6 seconds. Would probably boot faster with systemD, but fuck systemD.

>>61108636
it think is systemd shit, like those big ass logs and all that stuff. i was running fedora but now installed devuan, everything is just fine

>>61108636
I use Debian on all of my machines and I only notice the slowness on old hardware. Even my Core2 machines with SSDs boot in like 3 seconds.

Just use SSDs as your boot drives.

Fedora is bloated as hell

Decided to boot windows 10 this morning and update.
Two and a half hours downloading updates and 50 minutes rebooting so far.

File: maxresdefault (6).jpg (103KB, 1920x1080px) Image search: [Google]

103KB, 1920x1080px

i have pic-related

are there any linux distros that don't have systemd that will work on it? for some reason ubuntu/debian/arch linux distros wont boot on it. I don't know why. it must be the firmware. I have only got fedora to boot on it

>>61108674
I don't think it's systemd, my Arch machine boots up in less than 10 seconds.

>>61108658
>Would probably boot faster with systemD
Systemd reduces boot times.

>>61108761
>in less than 10 seconds
>doesn't encrypt

>>61108731
Turn off secure boot and turn on legacy mode in the BIOS. Otherwise, just use Fedora.

>>61108761
yeah, it must have been a bunch of services i remember some dnf cache stuff that took like 2 minutes on every startup, i didn't feel like fixing that shit
>>61108731
must be a bootloader problem, does that thing use uefi ? i'd install any of those first distros and then fix the bootloader from an ubuntu live cd with boot-repair, it just works.

>>61108636
use sleep instead of shutdown

File: b703cb6.png (324KB, 500x500px) Image search: [Google]

324KB, 500x500px

>>61108658

I don't have SSD and both Fedora and Ubuntu boots in 75s. Can't compare to Windows because my last Windows installation was terribly bloated with Lenovo factory bloatware and it took 3 minutes.
Systemd shoud be blazing when virtualized and in containers. It's aggressive parallelization for starting services sounds like a good idea and gets rig of dependencies between them. So it's probably distros' fault, because on Gentoo or Void I get 30s boottime without tinkering.

Startup finished in 19.475s (kernel) + 26.021s (userspace) = 45.497s

Is this bad?

>>61108717
I decided to drive my car today. 30 minutes of driving to a gas station and filling up gas.

>>61109053
Also had to take it to a mechanic to tune it up. Took 5 hours.

>>61109044
>Startup finished in 1.548s (firmware) + 5.923s (loader) + 1.149s (kernel) + 3.051s (initrd) + 23.840s (userspace) = 35.514s
I'm on SSD.

>>61109086
Mine is a ST1000DM003-9YN162 external drive, cpu is a6-3410mx

>>61108770
Isn't that exactly what that means?

I'm not my PC, but I think "systemd-analyse blame" will show you whats delaying boot.

>>61109153

bash: systemd-analyze: command not found

>>61109012
checked systemd-analyze on fresh Fedora (after updates and shit)

Startup finished in 1.862s (kernel) + 5.114s (initrd) + 40.718s (userspace) = 47.695s

Userspace and Gnome (not included) takes the most time.

>>61109175
Are you sure you're even running systemd?

I'm experiencing this on Ubuntu too. I have an SSD. Windows boots in probably 1/5 of the time. It feels like it's 1998 again.

>>61109079
Sure showed me.
My windows update only took 4 hours.

>>61109196
Give us the details of userspace?

>>61109217
$ systemd-analyze blame

File: Screenshot from 2017-06-28 05-05-31.png (27KB, 722x516px) Image search: [Google]

27KB, 722x516px

18s on cold boot
Not that bad, if you are impatient you can always sleep instead of shutting down like windows

File: seems about right.jpg (5KB, 670x21px) Image search: [Google]

5KB, 670x21px

>>61109244

"systemd-analyze blame" got a "command not found" error, but systemd-analyze gave pic related.

>>61109345
No idea why blame isn't working for you guys.

There's heaps of ways to visualize boot performance tho, have a look here https://wiki.archlinux.org/index.php/Improving_performance/Boot_process#Using_systemd-analyze

>>61108636
Click Esc while booting to see if anything is going wrong, mine too half a minute to start up because I deleted my swap partition and forgot to update fstab. Now it takes a few seconds

>>61109315
>Not that bad, if you are impatient you can always sleep instead of shutting down like windows

I never understand these sentences. Does this mean sleep like windows, or shut down like windows?

>>61108770
>>61109140
did you mean it snarky? like an
>implying Systemd reduces boot times...
kind of way?

>>61108717
Did you last boot your 486 up 3 years ago?

>>61109481
No I didn't. I never used systemD but I've seen plenty of anons using it and getting far better boot times than other init systems.

>>61109244

$ systemd-analyze blame
         13.077s plymouth-quit-wait.service
         12.680s NetworkManager-wait-online.service
          9.150s lvm2-monitor.service
          8.676s dnf-makecache.service
          8.586s akmods.service
          7.969s systemd-udev-settle.service
          7.478s firewalld.service
          7.014s dev-mapper-fedora\x2droot.device
          6.946s libvirtd.service
          5.901s systemd-journald.service
          5.161s lvm2-pvscan@8:2.service
          ... and bunch of sub 5s

>>61109079
what kind of shit do you drive bro?

>>61109538
BMW.

>>61109519
>plymouth-quit-wait.service
>NetworkManager-wait-online.service
Disable these, you don't need them, and they're literally just sitting there holding up boot.

>>61109559
me too - e46 and i only change oil, filters and brake pads once a year. nothing else breaks.

FFS, you fucking spergs! Just install Solus already. Boots in 3s!

>>61109740
> they're literally just sitting there holding up boot
Not sure about that, they should run in parallel since time sum is ~1m30s and analize reports 41s.

>>61108636
Encrypted drive, SELinux

>>61109905
Oh and if you have SSD then you probably have the fstrim service running also. That shit takes like 20sec to start on boot also.

Startup finished in 1.592s (kernel) + 11.287s (initrd) + 9.145s (userspace) = 22.025s

5-year-old Thinkpad/SSD, encrypted Fedora (dib:DD)

File: systemd1.png (147KB, 690x951px) Image search: [Google]

147KB, 690x951px

>>61109405
I rebooted and now it works. These are the results of systemd-analyze, systemd-analyze blame and systemd-analyze critical-chain

Image 1/2

File: systemd2.png (186KB, 740x1377px) Image search: [Google]

186KB, 740x1377px

>>61109985
Image 2/2

I don't really know what to tell from this, though.

>>61108654
and yet fedora is the has been the best distro for several years now, funny how that works.

let me know when wayland supports everything.

>>61108779
does that make you feel important?
are you some sort of drug kingpin?

>>61109419
sleep like windows, windoez doesn't shut down

>>61108636
(((They)))

Startup finished in 2.419s (kernel) + 10.544s (initrd) + 11.058s (userspace) = 24.022s

SSD on a T430, encrypted papa dora

File: arch peek.webm (219KB, 946x645px) Image search: [Google]

219KB, 946x645px

Get on my level, nigs

File: hmm.png (46KB, 463x605px) Image search: [Google]

46KB, 463x605px

is this good

File: Screenshot_2017-06-27_13-13-16.png (103KB, 1183x444px) Image search: [Google]

103KB, 1183x444px

>>61109898
Maybe you're right about the plymouth service, but not NetworkManager-wait-online.service. It runs afters some services, and some services also run after, but it doesn't do anything but wait uselessly. You can check with

systemd-analyze plot > output.svg

if it runs running parallel or not. Pic related, 8 seconds of nothing before I masked it.

>>61109985
>>61110006

This should help you anon https://askubuntu.com/questions/800479/ubuntu-16-04-slow-boot-apt-daily-service

File: 1485513020698.png (15KB, 674x365px) Image search: [Google]

15KB, 674x365px

Get on my level fags.

UBUNTU
B
U
N
T
U

>>61108636
Why would you use red-hat beta? Anyways, it's probably some systemd service hanging it.

File: 1497242301528.webm (2MB, 800x600px) Image search: [Google]

2MB, 800x600px

>>61108636
CloverOS starts instantly desu

>>61108636
Arch literally takes less than ten seconds every time the computer is powered down properly (maybe 30 seconds with a disk check) while Windows takes about 2 to 5 minutes depending on the day.

File: DeepinScreenshot_Select area_20170627235536.png (16KB, 534x73px) Image search: [Google]

16KB, 534x73px

>>61111282

Arch.