Many other UNIX operating systems—but not all of them—use the system of bootup scripts used by Linux. Even those that do use it have some slight differences in their implementation, and almost all use different directories for storing the actual scripts and links.
Sun Solaris, HP/UX, SCO UnixWare, SCO OpenServer, CompaqTru64/OSF1, and SGI Irix
All these operating systems use action scripts that are very similar to Linux, but are stored in different directories. Because those that come with the system do not have descriptions, the main page of the module will just display action names by default.
Table 9.1. Module Configuration Options| Allow selection of individual runlevels | If set to Yes when editing or creating an action, you will be able to enter the exact order number for the action in each runlevel. Because this is rather complex, this option is set to No by default so that Webmin only displays a single Start at boot? option when creating or editing an action. |
| Display actions with descriptions | If this option is set to Yes, and show all runlevels, the main page will show exactly which runlevels each action is started in, along with the description.
If set to Yes, each action will only show whether it is started at boot or not, and its description. This is the default on most systems.
If set to No, the main page will display only a table of action names with no descriptions or boot information. This can be useful if you have a lot of actions or your operating system does not include descriptions in the action scripts. |
| Show boot order of actions? | If Yes is selected, the main page will include the boot order of each action in the current runlevel, or in some other runlevel. The default No option hides this information. |
| Show current status of actions | On some Linux distributions, the standard action scripts can report the status of the servers that they start. This option allows Webmin to display this status information in various places.
If set to No, the status of actions is never displayed unless you click the Show Status button when editing an action.
If set to On action page only, Webmin will display the current status of an action when you edit it by selecting it from the main page of the module.
If set to On index and action pages, the main page of the module will display the current status of every single action. This provides a lot of information, but can be very slow. |
| Sort actions by | When Boot order is chosen, actions on the main page are listed in the order that they will be started by your system in the current runlevel. The default of Name causes them to be sorted by name instead. |
FreeBSD, NetBSD and OpenBSD
The BSD family of operating systems does not use action scripts at all, relying instead on a fixed set of scripts that are run at boot time. One of these scripts (/etc/rc.local) allows system administrators to add their own commands to be run at boot time.
On any of these operating systems, the main page of the module will just display a form for editing the rc.local file, above the Reboot System and Shutdown System buttons. To add any commands that you want run at boot time, just enter them into the text box and click the Save button.
IBM AIX
AIX is very similar to the BSD operating systems in that it does not have action scripts. Instead, the file /etc/rc can be edited to add additional commands to be run at boot time, using the form on the main page of the module.
Apple MacOS X
Apple's version of UNIX uses a totally different set of files for storing actions to be run at boot time than any other supported operating system. Separate action scripts still exist, but the user interface in this module for viewing and editing them is quite different.
If your operating system is not in this list, then the Bootup and Shutdown module does not support it at all, therefore the module icon will not appear in Webmin.
