Linked by Dennis Heuer on Wed 25th Aug 2010 22:23 UTC
Linux I came across a news entry at Phoronix about a new init replacement, systemd, and curiously started a read into the surprisingly heavy matter. Systemd is by no means as simple as upstart. It does far more things far more straight and in more detail. The differences are so significant that they enforce quite different configuration strategies. One can argue for both, depending on the goal to reach. However, that's not what I want to write about. After having read what systemd is capable of, and how it does it, I began to put the existence of all system daemons - in their today's forms - in question.
Thread beginning with comment 438262
To read all comments associated with this story, please click here.
Isn't that just...
by TheGZeus on Thu 26th Aug 2010 03:45 UTC
Member since:

...a microkernel/set of servers?
Except with a larger-than-normal kernel.

Reply Score: 2

RE: Isn't that just...
by Lennie on Thu 26th Aug 2010 06:39 in reply to "Isn't that just..."
Lennie Member since:

Probably is, but shhh don't tell anyone. :-)

But really a microkernel also would seperate filesystems and drivers, which is (or was at the time Linux was created) slower then doing it all in the same memory space.

so no, not in the strict sense.

Reply Parent Score: 2

RE[2]: Isn't that just...
by snadrus on Mon 30th Aug 2010 14:48 in reply to "RE: Isn't that just..."
snadrus Member since:

For FileSystems it's an option (FUSE), and yes it is slower for hard I/O, but the convenience is nice.

Reply Parent Score: 1