| |||||||||||||
The road forward for systemdThe road forward for systemdPosted May 26, 2010 18:33 UTC (Wed) by Cyberax (✭ supporter ✭, #52523)In reply to: The road forward for systemd by drago01 Parent article: The road forward for systemd
Care to provide even more trivial links without addressing a single line in my post?
Lennart also is misguided - target based systems are NOT good. Most of users _need_ NetworkManager to be started as soon as possible.
In essence, the goal is usually 'run everything ASAP' and not just 'run GNOME'. There are generally very little subsystems that don't need to be started on each boot.
However, sometimes we DO need to delay some service (a good example is CUPS). And that's where his ideas might be useful.
'Involuntary confinement' with cgroups might also be useful as an optional feature in Upstart or other init systems (even in standard Sys-V-ish daemon startup scripts).
(Log in to post comments)
The road forward for systemd Posted May 26, 2010 18:44 UTC (Wed) by mezcalero (subscriber, #45103) [Link]
you have not read the blog story. please do that. then you'll see that your comments are mislead.
The road forward for systemd Posted May 26, 2010 22:51 UTC (Wed) by Cyberax (✭ supporter ✭, #52523) [Link]
Sorry, your mind-reading ability has failed you.
So go and read MY post - it contains valid objections.
The road forward for systemd Posted May 31, 2010 16:16 UTC (Mon) by mezcalero (subscriber, #45103) [Link]
Because if you had read it you should have understood that in fact we start all services at the same time, in one big transaction. So if you try to argue against systemd by saying things like "Most of users _need_ NetworkManager to be started as soon as possible" then it is clear that you have not understood who systemd works: because in fact we start nm much earlier than Upstart or SysV: we start it right at the same time as we also start Syslog and D-Bus.
The road forward for systemd Posted May 27, 2010 14:21 UTC (Thu) by buchanmilne (guest, #42315) [Link] 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 CUPSDid you read the blog post?
|
|||||||||||||