On Thu, 27 Aug 2009, Russell Coker <[email protected]> wrote: > On Wed, 26 Aug 2009, Russell Coker <[email protected]> wrote: > > On Wed, 26 Aug 2009, Michael Biebl <[email protected]> wrote: > > > Well, ttbomk there are currently 4: minit, runit-run, upstart and > > > sysvinit. > > > > From the minit description in unstable: > > # This package is experimental and not easy to install and use. > > I've just looked at the source. minit used dietlibc, it is apparently not > designed for full-featured systems, and it doesn't even provide /sbin/init > (you have to use init=/sbin/minit to use it). > > So we are down to three init packages now.
Starting portmap daemon.... Starting NFS common utilities: statd. Cleaning up temporary files.... Setting console screen modes and fonts. - runit: leave stage: /etc/runit/1 - runit: enter stage: /etc/runit/2 I have just tested runit-run. When I boot with it the boot process ends with the above on the console (and with sshd and getty not running). It also has a serious bug against it which is a duplicate of bug #408280 from 2007 - which has not even had a comment from the maintainer. One of the main features of minit seems to be the use of dietlibc. It seems likely that there will be few people who find that they can't afford the 1.4M of disk space for glibc (on AMD64 architecture) but who can afford the disk space for SE Linux. I think it's reasonable to use the word "both" when referring to init systems that are viable for fully configured systems running SE Linux. PS Does SUSE use the same initrd as Red Hat? If not then there are more initrd's in common use than there are init's... -- [email protected] http://etbe.coker.com.au/ My Main Blog http://doc.coker.com.au/ My Documents Blog -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
