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