switchconf(8) [debian man page]
switchconf(8) System Manager's Manual switchconf(8) NAME
switchconf - Change system configuration to one of many predefined SYNOPSIS
switchconf [ -list | config_scheme ] DESCRIPTION
switchconf is a command line tool that helps nomad laptop users to easily change their configuration. OPTIONS
switchconf takes only one argument. If this argument is -list, a list of all known configuration schemes is returned (found in $conf_top_dirs). If the argument is a configuration scheme, this configuration will be installed on the laptop. CONFIGURATION FILE
The configuration file (/etc/switchconf/conf) is simple. The following entries are defined: conf_top_dirs This specify where are located the configurations schemes. dest_dir This specify in which top directory you want to install the new configuration. This option is pretty useful if you want to debug your configuration without overwritting the actual one. exec_dir_before, exec_dir_after This specify the name of the exec directory : all files included will be executed before or after configuration changes run_parts This specify the path to the run-parts command, that is used to execute the scripts. Leave it empty to use the internal implementa- tion of run-parts. config_method This specify the method to use to copy the configuration files, to their places: softlink, hardlink, copy /etc/switchconf/conf should be written so it is parsable as a shell script - There should be no spaces between the variable name and its value. SCHEMES
You should create a directory for each configuration scheme you define, including all the files it should set in the system. Inside /etc/switchconf the directories you should create the files including the full path (i.e., /etc/switchconf/home/etc/network/interfaces for /etc/network/interfaces). No scheme should be named as either the exec_dir_before or the exec_dir_after, unless the conf_top_dirs is moved out of its default direc- tory, /etc/switchconf. Although it is not really necessary, you should probably ensure that all the files existing in one of the schemes exist on every other scheme, in order to ensure you do not end up in a hybrid state. FILES
/etc/switchconf/conf Configuration file. /var/lib/misc/switchconf.lastcfg Memory file, has the name of the current active scheme BUGS
Actually no bugs are reported. AUTHOR
switchconf was written by Sebastien J. Gross <seb@sjgross.org> switchconf was contributed by Julien Ducros <jul@chezwam.org> switchconf was maintained by Jose Calhariz <jose.calhariz@tagus.ist.utl.pt> 3rd Berkeley Distribution April 2002 switchconf(8)
Check Out this Related Man Page
rc.config(4) Kernel Interfaces Manual rc.config(4) NAME
rc.config, rc.config.d - files containing system configuration information SYNOPSIS
DESCRIPTION
The system configuration used at startup is contained in files within the directory The file sources all of the files within and and exports their contents to the environment. /etc/rc.config The file is a script that sources all of the scripts, and also sources To read the configuration definitions, only this file need be sourced. This file is sourced by whenever it is run, such as when the command is run to transition between run states. Each file that exists in is sourced, without regard to which startup scripts are to be executed. /etc/rc.config.d The configuration information is structured as a directory of files, rather than as a single file containing the same information. This allows developers to create and manage their own configuration files here, without the complications of shared ownership and access of a common file. /etc/rc.config.d/* Files This is where files containing configuration variable assignments are located. Configuration scripts must be written to be read by the POSIX shell, and not the Bourne shell, or In some cases, these files must also be read and possibly modified by control scripts or the sam program. See sd(4) and sam(1M). For this reason, each variable definition must appear on a separate line, with the syntax: No trailing comments may appear on a variable definition line. Comment statements must be on separate lines, with the comment character in column one. This example shows the required syntax for configuration files: Configuration variables may be declared as array parameters when describing multiple instances of the variable configuration. For example, a system may contain two network interfaces, each having a unique IP address and subnet mask (see ifconfig(1M)). An example of such a dec- laration is as follows: Note that there must be no requirements on the order of the files sourced. This means configuration files must not refer to variables defined in other configuration files, since there is no guarantee that the variable being referenced is currently defined. There is no protection against environment variable namespace collision in these configuration files. Programmers must take care to avoid such prob- lems. /etc/TIMEZONE The file contains the definition of the environment variable. This file is required by POSIX. It is sourced by at the same time the files are sourced. SEE ALSO
rc(1M). rc.config(4)