Linked by diegocg on Mon 23rd Aug 2010 14:10 UTC
Linux Lennart Poettering has posted a status update about systemd, an init/upstart alternative. systemd is able now to replace /etc/fstab and cron, and it seems it will be the default init system for Fedora 14. He has also written a post about systemd for administrators.
Thread beginning with comment 437962
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: I am not okay with this
by sorpigal on Tue 24th Aug 2010 14:40 UTC in reply to "RE[5]: I am not okay with this"
sorpigal
Member since:
2005-11-02

I wrote a reply to this same example on lwn, I won't repeat it here.

If you want to know why, think beyond just desktop systems.

I am thinking specifically of my servers. As for embedded, I understand that there every once of performance matters. Let them over-optimize if they must.

Package maintainers already have written init scripts. They don't have to convert.

Are the systemd developers recommending that sysvinit scripts remain in use and that people do not convert to "native" systemd? If the answer is "No" then sooner or later there will be no more init scripts written at all.

Reply Parent Score: 2

RE[7]: I am not okay with this
by Rahul on Tue 24th Aug 2010 14:45 in reply to "RE[6]: I am not okay with this"
Rahul Member since:
2005-07-06

Servers need 99% boiler plate code to be executed? Don't think so. Simple configuration wins. How would you love to have full control over the processes spawned via control groups? How about automatic service recovery? fully detailed reported of why the service failed if it did? And yes, systemd developers are not recommending everyone convert. Even in Fedora 14, only a few default packages ship with native systemd service files and the rest of the system continues to use sysv init scripts. If anyone wants to try it out, they are free to include both. Exclusivity is not needed.

Reply Parent Score: 1