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.
*BSD init, OS X init, etc.
by lord summerisle on Thu 2nd Oct 2003 17:23 UTC

If you want a simpler, quicker replacement for SysV init, use the rc.* system used by BSD. Someone mentioned the NetBSD rc.*, that's even better. As for linux, doesn't Slackware use rc.*? What's wrong with that?
On my machine (old dual celery abit), FreeBSD takes perhaps 7 seconds to go from boot to login screen. RHL takes about 20 seconds. I'd bet that Slackware boots closer to FreeBSD's speed rather than RHL's... That's with a lot of services (anaconda, etc) disabled on RHL, btw.
I don't buy that most unix admins have difficulty understanding how the SysV init system works. I hate it, but I understand how it works just fine. It's not rocket science, after all.
OS X uses rc.* in single-user mode, and then uses NetInfo to initialize startup services once it's gone multiuser.
The real core of these kinds of changes seems to be that UNIX, as UNIX, isn't valid for the desktop. If the people who work on these projects, or use them, don't like multiuser UNIX as their desktop, why not get rid of it? Make your own setup that boots with network services running, etc., but make it single-user only. No need for a login screen, or any of that other 'unnecessary' stuff. I'd think that'd be a more constructive use of skills and time, rather than building a kludgy 'framework' to replace simple no-overhead shell scripts designed to provide service startup and shutdown with an integrated framework that can start up and shut down services. Oh yeah, and query their status. I just don't get it. The work the guy's done on his natural language parser project is impressive. This is less so.