Linked by Eugenia Loli on Wed 1st Oct 2003 23:09 UTC
General Development OSNews was the first news magazine to break the story on Gnome's Seth Nickell effort to replace the Init system. Soon, it became confusing to many readers as to if Seth is planning to completely replace the Init system or simply "bridge" it. We had a chat with Seth and discussed about his plans on the project (which is a personal project so far) and for Storage, an exciting project which aims to replace the traditional filesystem with a new database-based document store.
Permalink for comment
To read all comments associated with this story, please click here.

There's nothing preventing a "daemon" from also being an init script - people don't usually write it that way because doing so would LIMIT an admin's ability to modify start-up stuff in a familiar language. If you want to release a binary that can be suitably run as an init script, just code it that way.

The only reason all the distro's still use init scripts slightly differently is because no one has yet published a compelling standard for enhancing their functionality. Publish a document and convince the guys at either Redhat or LSB to add features uniformly to all the init scripts they support and you'll have a good base that others will probably start to copy.

The only thing you're really offering to programmers is a standardized implementation of profiles - and you're really not sure you want to offer that. It's the only useful suggestion this project includes. Redhat has started to put some concept of profiles into its network startup scripts, but abstracting the concept out far enough that it can apply instead of runlevels would be a useful improvement.

For example, runlevels 3 and 5 are the only ones people typically change - but why can't I create runlevels, 8, 9, and "home"? If init were cognizant of user defined "profiles", which is really just another word for "runlevels", as opposed to just being aware of modifications to predefined runlevels, then distros wouldn't have to re-invent that implementation in their init scripts.