Cucumber Linux uses System V Init style init scripts. The actual init scripts (for starting and stopping services) are placed in /etc/rc.d/init.d. These scripts are then symlinked into /etc/rc.d/rc?.d, where ? is the runlevel (one of the following: S0123456). Each script is prefixed with an S or K, and a 2 digit number. For example, ssh may become S55sshd, and httpd may become K20httpd.

When init(8) or telinit(8) commands goes into the runlevel to “<n>”, the system basically executes the initialization scripts as follows:

• The script names starting with a “K” in “/etc/rc<n>.d/” are executed in alphabetical order with the single argument “stop”. (killing services)
• The script names starting with an “S” in “/etc/rc<n>.d/” are executed in alphabetical order with the single argument “start”. (starting services)

A notable exception to this rule occurs when entering runlevel 0 or 6. Since these runlevels are entered when the system is about to halt, init scripts in the /etc/rc.d/rc{0,6}.d directory will be executed with the “stop” argument, regardless of whether they are prefixed with an S or K.

Cucumber Linux make the following use of each runlevel:

• 0 - Shutdown
• 1 - Single User Mode (for Maintenance)
• 2 - Multi User Mode without Networking
• 3 - Multi User Mode with Networking (Default)
• 4 - Same as runlevel 3
• 5 - Graphical (X11) Login
• 6 - Reboot

This file should contain any additional commands that need to be run during system startup to correctly configure the system clock. Most users do not need to edit this file.

This file should contain any commands that need to be run during system startup to correctly configure the console. Native English speakers probably don't need /etc/console at all. For documentation on setting up alternative language support, see http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html.

This file is the createfiles script config file. It is used to control the recreation of certain files after the filesystem is cleaned by cleanfs.

This file controls the module auto-loading configuration. The syntax of this file is as follows:

<module> [<arg1> <arg2> ...]

Each module should be on its own line, and any options that you want passed to the module should follow it. The argument deliminator is either a space or a tab. The line deliminator is a newline.

More information about configuring module support can be found at Module Configuration Page.

This file allows you to override certain parameters for init scripts. Editing this file is completely optional. If any value is not set here, the default value will be used. Most people will never have any need to touch this file, but it's there just in case you ever need to change something.

This file is the udev_retry script configuration. Each subsystem that may need to be re-triggered after mountfs runs should be listed in this file. Probable subsystems to be listed here are rtc (due to /var/lib/hwclock/adjtime) and sound (due to both /var/lib/alsa/asound.state and /usr/sbin/alsactl). Entries are whitespace-separated.