From Wikipedia, the free encyclopedia
Jump to: navigation, search
WikiProject Software / Computing  (Rated Start-class)
WikiProject icon This article is within the scope of WikiProject Software, a collaborative effort to improve the coverage of software on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.
Start-Class article Start  This article has been rated as Start-Class on the project's quality scale.
 ???  This article has not yet received a rating on the project's importance scale.
Taskforce icon
This article is supported by WikiProject Computing.

Removed sentence from intro[edit]

I removed this:

Opinions on the relative merits of different schemes can be strongly held, leading both to occasional "flame wars", and also to the development of several alternatives.

seemed like fluff. Hotdogger 01:23, 22 February 2007 (UTC)

I agree that it didn't belong in the introduction like that, and was unreferenced to boot. A "History" section would be a better place to discuss the actual flame wars, if any, that have occurred. John Vandenberg 01:47, 22 February 2007 (UTC)


That 'about' section reads like it is talking about linux, but doesn't it also apply to the BSDs as well? Mentioning Slackware in its own right seems a bit misleading. --Maru Dubshinki

Well, I was referring to the init systems used on Linux distributions, and I felt it worth mentioning that some, such as slackware and gentoo, use their own init systems. -- Lakerdonald
Fair enough. I've taken the liberty of moving the man init in see also, to external links, and linking to a copy of the man page. --maru 15:51, 18 May 2005 (UTC)
Sounds good. Looks nice :D --lakerdonald


Hey, this'll be my very first Wiki edit. Go me. :) Anyway, this page seems very Linux-centric, even though the init program is present (but behaves differently) on every Unix system. For example, while runlevel 5 may be the default on many Linux distributions, if you switched a Sun/Solaris machine to runlevel 5, it would physically turn itself off. That might come as a bit of a nasty surprise if you're not expecting it. I've added a note to that effect. 18:44, 15 February 2006 (UTC)

Hey, nice job. I further explained that with AIX, and Solaris, the default run levels are different. Now I wonder, should the default runlevels be put into a table for easier readability. This table would also help make the whole article seem less Linux-centric. --Unixguy 19:15, 13 July 2006 (UTC)

BIOS password[edit]

"If the system administrator feels this is insecure, they can always setup a BIOS password." Surely this should be "bootloader password"? --Anon

I think both. BIOSs can be set to require a password before loading the bootloader, and the bootloader can be passworded (I forget whether it blocks loading one of the kernels and partitions, or whether just changing the settings). --maru (talk) contribs 00:57, 26 February 2006 (UTC)
Well in the context of the Article, the BIOS password is not going to prevent someone from typing custom options into grub, lilo or yaboot. To stop the runlevel 1 loophole you need a bootloader password.

Examples needed[edit]

This article is taking shape nicely, but I think it could use a couple of examples.

Example inittab files
   Typical SUSE inittab:
(paste here)

   Typical Solaris inittab:
sS:s:wait:/sbin/rcS                     >/dev/msglog 2<>/dev/msglog </dev/console
s0:0:wait:/sbin/rc0                     >/dev/msglog 2<>/dev/msglog </dev/console
s1:1:respawn:/sbin/rc1                  >/dev/msglog 2<>/dev/msglog </dev/console
s2:23:wait:/sbin/rc2                    >/dev/msglog 2<>/dev/msglog </dev/console
s3:3:wait:/sbin/rc3                     >/dev/msglog 2<>/dev/msglog </dev/console
s5:5:wait:/sbin/rc5                     >/dev/msglog 2<>/dev/msglog </dev/console
s6:6:wait:/sbin/rc6                     >/dev/msglog 2<>/dev/msglog </dev/console

   Typical AIX inittab:
l2:2:wait:/etc/rc.d/rc 2
l3:3:wait:/etc/rc.d/rc 3
l4:4:wait:/etc/rc.d/rc 4
l5:5:wait:/etc/rc.d/rc 5
l6:6:wait:/etc/rc.d/rc 6
l7:7:wait:/etc/rc.d/rc 7
l8:8:wait:/etc/rc.d/rc 8
l9:9:wait:/etc/rc.d/rc 9

--Unixguy 00:48, 27 November 2006 (UTC)

On second thought, adding examples would probably be too technical, and not of much value to an online encyclopedia. --Unixguy 16:03, 3 July 2007 (UTC)

discussion about merging init and runlevel[edit]

I don't think they should be merged; They are so related, but they are not the same. Callmejosh (talk) 07:46, 6 September 2008 (UTC)


sysvinit redirects to this article. What does it mean? --Abdull (talk) 16:34, 7 March 2010 (UTC)

Sysvinit = an Init implementation as originally used in UNIX System V and now followed by most Linux distributions. There's an entire section devoted to it in this article. :) (talk) 04:53, 2 May 2010 (UTC)

Article would benefit from a list of operating systems that support SysVinit. Believe it or not, for every face-in-his-hand hipster staring at a mobile app, there is a server somewhere that doesn't need to reboot 3 times a day. For servers, stability is more important than bling. (talk) 21:30, 21 August 2015 (UTC)

All processes?[edit]

"init is the program on Unix and Unix-like systems that spawns all other processes."
Does init really spawn all processes, so for example a webbrowser that a user requested to start from a GUI is also spawned through init's services? --Abdull (talk) 17:59, 7 March 2010 (UTC)

You're right. Init doesn't spawn all processes. It spawns its child processes which in return spawn their child processes etc. According to pstree on my system though a webbrowser is really a child of init. It would be correct to say that init is a common ancestor of all processes. (talk) 05:09, 2 May 2010 (UTC)
It is a child of init because it was re-parented, not because init created your web browser as a child. Justinc (talk) 20:34, 18 August 2012 (UTC)