Hacker News new | ask | show | jobs
by bayindirh 1696 days ago
> I wonder why Linux has not yet taken that approach? That is move GUI far up in the init-queue and let it initialize networks, avahi, resolved, firewalld, etc as GUI is showing login screen...

Because it boots faster than a Windows system in that scenario. I personally like to be able to use my system as soon as the desktop is visible.

Also this is the way. When your system boots, it boots.

1 comments

I just timed my Windows 11 vs my Ubuntu. Windows 11 booted faster to a usable GUI by a factor of about 2:1
> Windows 11 booted faster to a usable GUI by a factor of about 2:1

Probably used fast boot and returned from an image. :)

From a fully fresh start on an NVMe, Windows 10 does start up approximately just as fast as a brand new Debian install.

With the added benefit of not having X11 setting modes 5 times in the mean time.

This is quite surprising. My experience has been quite different. Have you run systemd-analyze to try to locate what's causing the slower boot?
Surprising indeed. Windows 10 boots quite quickly (don't know about Windows 11) but the boot of a fresh install of the latest version of Debian feels instantaneous. In a systemd container, it boots under 2 seconds even with a few extra services.
> but the boot of a fresh install of the latest version of Debian feels instantaneous.

Starting with latest iterations CentOS 7 and Debian 10, booting Linux is almost instantaneous. We have quite a few VMs, and after restarting one (i.e.: reboot <enter>), I just need to sip a little coffee to be able to SSH into a fully booted system.

On the other hand some of the higher end servers we have can fit a meaningful chat to the booting process (in fast boot mode, no less).

This means that most of the overhead is hardware initialization waits, IO and GRUB.

BTW, X11 is not modesetting 5 times on me. Maybe the first modeset you see is kernel's terminal modeset?