On 2013-03-27, Michael Mol <mike...@gmail.com> wrote: > The case for systemd is twofold: > > 1) Boot-to-desktop session management by one tool.
Ah, the old "universal generic tool" approach. I've seen a lot of money and time poured into black-hole projects with names containing words like universal and generic, so I don't really like the sound of that. [Is that the right response for somebody who started using V7 Unix on a PDP11?] > (The same thing that launches your cron daemon is what launches > your favorite apps when you log in.) The only app that runs when I log in is bash. Then I usually start XFCE from the command line -- but not always. > 2) Reduce the amount of CPU and RAM consumed when you're talking > about booting tens of thousands of instances simultaneously across > your entire infrastructure, or when your server instance might be > spun up and down six times over the course of a single day. It sounds like systemd really isn't intended for the likes of me. >> Are there people who reboot their machines every few minutes and >> therefore need to shave a few seconds off their boot time? > > On-demand server contexts, yes. Thanks for the explanation -- I never would have guessed that's how the whole cloud thing worked. -- Grant
