The road forward for systemd
Posted May 27, 2010 14:21 UTC (Thu) by buchanmilne
In reply to: The road forward for systemd
Parent article: The road forward for systemd
Most of users _need_ NetworkManager to be started as soon as possible.
AFAICT, systemd should start NetworkManager sooner, because systemd won't wait for (e.g.) messagebus to finish starting before starting NetworkManager. If there are any other D-Bus-based services that NetworkManager requires (maybe wpa_supplicant?, sorry, my distro doesn't use NetworkManager, and all network interfaces come up very early, including WiFi ...), they will also be started in parallel.
This is covered in the blog post.
In essence, the goal is usually 'run everything ASAP' and not just 'run GNOME'.
Where do you see this goal of 'run GNOME'? It's certainly not in the systemd blog post ...
However, sometimes we DO need to delay some service (a good example is CUPS)
Quote from the blog post:
Same for a printing system: unless the machine physically is connected to a printer, or an application wants to print something, there is no need to run a printing daemon such as CUPS
Did you read the blog post?
to post comments)