Translation Source string Target string
Linux From Scratch 12.2/chapter09_usage — Spanish
System V Bootscript Usage and Configuration
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Bootscripts
 
Linux From Scratch 12.2/chapter09_usage — Spanish
usage
 
Linux From Scratch 12.2/chapter09_usage — Spanish
How Do the System V Bootscripts Work?
 
Linux From Scratch 12.2/chapter09_usage — Spanish
This version of LFS uses a special booting facility named SysVinit, based on a series of <emphasis>run levels</emphasis>. The boot procedure can be quite different from one system to another; the fact that things worked one way in a particular Linux distribution does not guarantee they will work the same way in LFS. LFS has its own way of doing things, but it does respect generally accepted standards.
 
Linux From Scratch 12.2/chapter09_usage — Chinese (Simplified Han script)
There is an alternative boot procedure called <command>systemd</command>. We will not discuss that boot process any further here. For a detailed description visit <ulink url="https://www.linux.com/training-tutorials/understanding-and-using-systemd/"/>.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
There is an alternative boot procedure called <command>systemd</command>. We will not discuss that boot process any further here. For a detailed description visit <ulink url="https://www.linux.com/training-tutorials/understanding-and-using-systemd/"/>.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
SysVinit (which will be referred to as <quote>init</quote> from now on) uses a run levels scheme. There are seven run levels, numbered 0 to 6. (Actually, there are more run levels, but the others are for special cases and are generally not used. See <ulink role='man' url='&man;init.8'>init(8)</ulink> for more details.) Each one of the seven corresponds to actions the computer is supposed to perform when it starts up or shuts down. The default run level is 3. Here are the descriptions of the different run levels as they are implemented in LFS:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
0: halt the computer
1: single-user mode
2: reserved for customization, otherwise the same as 3
3: multi-user mode with networking
4: reserved for customization, otherwise the same as 3
5: same as 4, it is usually used for GUI login (like GNOME's <command>gdm</command> or LXDE's <command>lxdm</command>)
6: reboot the computer
 
Linux From Scratch 12.2/chapter09_usage — Chinese (Simplified Han script)
Classically, run level 2 above was defined as <quote>multi-user mode without networking,</quote> but this was only the case many years ago when multiple users could connect to a system via serial ports. In today's environment it makes no sense, and we now say it is <quote>reserved.</quote>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Classically, run level 2 above was defined as <quote>multi-user mode without networking,</quote> but this was only the case many years ago when multiple users could connect to a system via serial ports. In today's environment it makes no sense, and we now say it is <quote>reserved.</quote>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Configuring SysVinit
 
Linux From Scratch 12.2/chapter09_usage — Spanish
SysVinit
 
Linux From Scratch 12.2/chapter09_usage — Spanish
configuring
 
Linux From Scratch 12.2/chapter09_usage — Spanish
/etc/inittab
 
Linux From Scratch 12.2/chapter09_usage — Spanish
During kernel initialization, the first program that is run (if not overridden on the command line) is <command>init</command>. This program reads the initialization file <filename>/etc/inittab</filename>. Create this file with:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/inittab &lt;&lt; "EOF"
<literal># Begin /etc/inittab

id:3:initdefault:

si::sysinit:/etc/rc.d/init.d/rc S

l0:0:wait:/etc/rc.d/init.d/rc 0
l1:S1:wait:/etc/rc.d/init.d/rc 1
l2:2:wait:/etc/rc.d/init.d/rc 2
l3:3:wait:/etc/rc.d/init.d/rc 3
l4:4:wait:/etc/rc.d/init.d/rc 4
l5:5:wait:/etc/rc.d/init.d/rc 5
l6:6:wait:/etc/rc.d/init.d/rc 6

ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now

su:S06:once:/sbin/sulogin
s1:1:respawn:/sbin/sulogin

1:2345:respawn:/sbin/agetty --noclear tty1 9600
2:2345:respawn:/sbin/agetty tty2 9600
3:2345:respawn:/sbin/agetty tty3 9600
4:2345:respawn:/sbin/agetty tty4 9600
5:2345:respawn:/sbin/agetty tty5 9600
6:2345:respawn:/sbin/agetty tty6 9600

# End /etc/inittab</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
An explanation of this initialization file is in the man page for <emphasis>inittab</emphasis>. In LFS, the key command is <command>rc</command>. The initialization file above instructs <command>rc</command> to run all the scripts starting with an S in the <filename class="directory">/etc/rc.d/rcS.d</filename> directory followed by all the scripts starting with an S in the <filename class="directory">/etc/rc.d/rc?.d</filename> directory where the question mark is specified by the initdefault value.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
As a convenience, the <command>rc</command> script reads a library of functions in <filename class="directory">/lib/lsb/init-functions</filename>. This library also reads an optional configuration file, <filename>/etc/sysconfig/rc.site</filename>. Any of the system configuration parameters described in subsequent sections can be placed in this file, allowing consolidation of all system parameters in this one file.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
As a debugging convenience, the functions script also logs all output to <filename>/run/var/bootlog</filename>. Since the <filename class="directory">/run</filename> directory is a tmpfs, this file is not persistent across boots; however, it is appended to the more permanent file <filename>/var/log/boot.log</filename> at the end of the boot process.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Changing Run Levels
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Changing run levels is done with <command>init <replaceable>&lt;runlevel&gt;</replaceable></command>, where <replaceable>&lt;runlevel&gt;</replaceable> is the target run level. For example, to reboot the computer, a user could issue the <command>init 6</command> command, which is an alias for the <command>reboot</command> command. Likewise, <command>init 0</command> is an alias for the <command>halt</command> command.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
There are a number of directories under <filename class="directory">/etc/rc.d</filename> that look like <filename class="directory">rc?.d</filename> (where ? is the number of the run level) and <filename class="directory">rcS.d</filename>, all containing a number of symbolic links. Some links begin with a <emphasis>K</emphasis>; the others begin with an <emphasis>S</emphasis>, and all of them have two numbers following the initial letter. The K means to stop (kill) a service and the S means to start a service. The numbers determine the order in which the scripts are run, from 00 to 99&mdash;the smaller the number, the sooner the script runs. When <command>init</command> switches to another run level, the appropriate services are either started or stopped, depending on the run level chosen.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The real scripts are in <filename class="directory">/etc/rc.d/init.d</filename>. They do the actual work, and the symlinks all point to them. K links and S links point to the same script in <filename class="directory">/etc/rc.d/init.d</filename>. This is because the scripts can be called with different parameters like <parameter>start</parameter>, <parameter>stop</parameter>, <parameter>restart</parameter>, <parameter>reload</parameter>, and <parameter>status</parameter>. When a K link is encountered, the appropriate script is run with the <parameter>stop</parameter> argument. When an S link is encountered, the appropriate script is run with the <parameter>start</parameter> argument.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
These are descriptions of what the arguments make the scripts do:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<parameter>start</parameter>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The service is started.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<parameter>stop</parameter>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The service is stopped.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<parameter>restart</parameter>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The service is stopped and then started again.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<parameter>reload</parameter>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The configuration of the service is updated. This is used after the configuration file of a service was modified, when the service does not need to be restarted.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<parameter>status</parameter>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Tells if the service is running and with which PIDs.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Feel free to modify the way the boot process works (after all, it is your own LFS system). The files given here are an example of how it can be done.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Udev Bootscripts
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <filename>/etc/rc.d/init.d/udev</filename> initscript starts <command>udevd</command>, triggers any "coldplug" devices that have already been created by the kernel, and waits for any rules to complete. The script also unsets the uevent handler from the default of <filename>/sbin/hotplug </filename>. This is done because the kernel no longer needs to call an external binary. Instead, <command>udevd</command> will listen on a netlink socket for uevents that the kernel raises.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <command>/etc/rc.d/init.d/udev_retry</command> script takes care of re-triggering events for subsystems whose rules may rely on file systems that are not mounted until the <command>mountfs</command> script is run (in particular, <filename class="directory">/usr</filename> and <filename class="directory">/var</filename> may cause this). This script runs after the <command>mountfs</command> script, so those rules (if re-triggered) should succeed the second time around. It is configured by the <filename>/etc/sysconfig/udev_retry</filename> file; any words in this file other than comments are considered subsystem names to trigger at retry time. To find the subsystem of a device, use <command>udevadm info --attribute-walk &lt;device&gt;</command> where &lt;device&gt; is an absolute path in /dev or /sys, such as /dev/sr0, or /sys/class/rtc.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
For information on kernel module loading and udev, see <xref linkend="module-loading" role='.'/>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Configuring the System Clock
 
Linux From Scratch 12.2/chapter09_usage — Spanish
setclock
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <command>setclock</command> script reads the time from the hardware clock, also known as the BIOS or Complementary Metal Oxide Semiconductor (CMOS) clock. If the hardware clock is set to UTC, this script will convert the hardware clock's time to the local time using the <filename>/etc/localtime</filename> file (which tells the <command>hwclock</command> program which time zone to use). There is no way to detect whether or not the hardware clock is set to UTC, so this must be configured manually.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <command>setclock</command> program is run via <application>udev</application> when the kernel detects the hardware capability upon boot. It can also be run manually with the stop parameter to store the system time to the CMOS clock.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
If you cannot remember whether or not the hardware clock is set to UTC, find out by running the <userinput>hwclock --localtime --show</userinput> command. This will display what the current time is according to the hardware clock. If this time matches whatever your watch says, then the hardware clock is set to local time. If the output from <command>hwclock</command> is not local time, chances are it is set to UTC time. Verify this by adding or subtracting the proper number of hours for your time zone to the time shown by <command>hwclock</command>. For example, if you are currently in the MST time zone, which is also known as GMT -0700, add seven hours to the local time.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Change the value of the <envar>UTC</envar> variable below to a value of <parameter>0</parameter> (zero) if the hardware clock is <emphasis>NOT</emphasis> set to UTC time.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Create a new file <filename>/etc/sysconfig/clock</filename> by running the following:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/clock &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/clock

UTC=1

# Set this to any options you might need to give to hwclock,
# such as machine hardware clock type for Alphas.
CLOCKPARAMS=

# End /etc/sysconfig/clock</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
A good hint explaining how to deal with time on LFS is available at <ulink url="&hints-root;time.txt"/>. It explains issues such as time zones, UTC, and the <envar>TZ</envar> environment variable.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The CLOCKPARAMS and UTC parameters may also be set in the <filename>/etc/sysconfig/rc.site</filename> file.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Configuring the Linux Console
 
Linux From Scratch 12.2/chapter09_usage — Spanish
console
 
Linux From Scratch 12.2/chapter09_usage — Spanish
This section discusses how to configure the <command>console</command> bootscript that sets up the keyboard map, console font, and console kernel log level. If non-ASCII characters (e.g., the copyright sign, the British pound sign, and the Euro symbol) will not be used and the keyboard is a U.S. one, much of this section can be skipped. Without the configuration file, (or equivalent settings in <filename>rc.site</filename>), the <command>console</command> bootscript will do nothing.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <command>console</command> script reads the <filename>/etc/sysconfig/console</filename> file for configuration information. Decide which keymap and screen font will be used. Various language-specific HOWTOs can also help with this; see <ulink url="https://tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in doubt, look in the <filename class="directory">/usr/share/keymaps</filename> and <filename class="directory">/usr/share/consolefonts</filename> directories for valid keymaps and screen fonts. Read the <ulink role='man' url='&man;loadkeys.1'>loadkeys(1)</ulink> and <ulink role='man' url='&man;setfont.8'>setfont(8)</ulink> manual pages to determine the correct arguments for these programs.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <filename>/etc/sysconfig/console</filename> file should contain lines of the form: <envar>VARIABLE=value</envar>. The following variables are recognized:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
LOGLEVEL
 
Linux From Scratch 12.2/chapter09_usage — Spanish
This variable specifies the log level for kernel messages sent to the console as set by <command>dmesg -n</command>. Valid levels are from <literal>1</literal> (no messages) to <literal>8</literal>. The default level is <literal>7</literal>, which is quite verbose.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
KEYMAP
 
Linux From Scratch 12.2/chapter09_usage — Spanish
This variable specifies the arguments for the <command>loadkeys</command> program, typically, the name of the keymap to load, e.g., <literal>it</literal>. If this variable is not set, the bootscript will not run the <command>loadkeys</command> program, and the default kernel keymap will be used. Note that a few keymaps have multiple versions with the same name (cz and its variants in qwerty/ and qwertz/, es in olpc/ and qwerty/, and trf in fgGIod/ and qwerty/). In these cases the parent directory should also be specified (e.g. qwerty/es) to ensure the proper keymap is loaded.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
KEYMAP_CORRECTIONS
 
Linux From Scratch 12.2/chapter09_usage — Spanish
This (rarely used) variable specifies the arguments for the second call to the <command>loadkeys</command> program. This is useful if the stock keymap is not completely satisfactory and a small adjustment has to be made. E.g., to include the Euro sign into a keymap that normally doesn't have it, set this variable to <literal>euro2</literal>.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
FONT
 
Linux From Scratch 12.2/chapter09_usage — Spanish
This variable specifies the arguments for the <command>setfont</command> program. Typically, this includes the font name, <literal>-m</literal>, and the name of the application character map to load. E.g., in order to load the <quote>lat1-16</quote> font together with the <quote>8859-1</quote> application character map (appropriate in the USA), set this variable to <literal>lat1-16 -m 8859-1</literal>. In UTF-8 mode, the kernel uses the application character map to convert 8-bit key codes to UTF-8. Therefore the argument of the "-m" parameter should be set to the encoding of the composed key codes in the keymap.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
UNICODE
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Set this variable to <literal>1</literal>, <literal>yes</literal>, or <literal>true</literal> in order to put the console into UTF-8 mode. This is useful in UTF-8 based locales and harmful otherwise.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
LEGACY_CHARSET
 
Linux From Scratch 12.2/chapter09_usage — Spanish
For many keyboard layouts, there is no stock Unicode keymap in the Kbd package. The <command>console</command> bootscript will convert an available keymap to UTF-8 on the fly if this variable is set to the encoding of the available non-UTF-8 keymap.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Some examples:
 
Linux From Scratch 12.2/chapter09_usage — Chinese (Simplified Han script)
We'll use <literal>C.UTF-8</literal> as the locale for interactive sessions in the Linux console in <xref role=',' linkend='ch-config-locale'/> so we should set <literal>UNICODE</literal> to <literal>1</literal>. And the console fonts shipped by the <application>Kbd</application> package containing the glyphs for all characters from the program messages in the <literal>C.UTF-8</literal> locale are <filename>LatArCyrHeb*.psfu.gz</filename>, <filename>LatGrkCyr*.psfu.gz</filename>, <filename>Lat2-Terminus16.psfu.gz</filename>, and <filename>pancyrillic.f16.psfu.gz</filename> in <filename class='directory'>/usr/share/consolefonts</filename> (the other shipped console fonts lack glyphs of some characters like the Unicode left/right quotation marks and the Unicode English dash). So set one of them, for example <filename>Lat2-Terminus16.psfu.gz</filename> as the default console font:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
We'll use <literal>C.UTF-8</literal> as the locale for interactive sessions in the Linux console in <xref role=',' linkend='ch-config-locale'/> so we should set <literal>UNICODE</literal> to <literal>1</literal>. And the console fonts shipped by the <application>Kbd</application> package containing the glyphs for all characters from the program messages in the <literal>C.UTF-8</literal> locale are <filename>LatArCyrHeb*.psfu.gz</filename>, <filename>LatGrkCyr*.psfu.gz</filename>, <filename>Lat2-Terminus16.psfu.gz</filename>, and <filename>pancyrillic.f16.psfu.gz</filename> in <filename class='directory'>/usr/share/consolefonts</filename> (the other shipped console fonts lack glyphs of some characters like the Unicode left/right quotation marks and the Unicode English dash). So set one of them, for example <filename>Lat2-Terminus16.psfu.gz</filename> as the default console font:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/console

UNICODE="1"
FONT="Lat2-Terminus16"

# End /etc/sysconfig/console</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
For a non-Unicode setup, only the KEYMAP and FONT variables are generally needed. E.g., for a Polish setup, one would use:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/console

KEYMAP="pl2"
FONT="lat2a-16 -m 8859-2"

# End /etc/sysconfig/console</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
As mentioned above, it is sometimes necessary to adjust a stock keymap slightly. The following example adds the Euro symbol to the German keymap:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/console

KEYMAP="de-latin1"
KEYMAP_CORRECTIONS="euro2"
FONT="lat0-16 -m 8859-15"
UNICODE="1"

# End /etc/sysconfig/console</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The following is a Unicode-enabled example for Bulgarian, where a stock UTF-8 keymap exists:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/console

UNICODE="1"
KEYMAP="bg_bds-utf8"
FONT="LatArCyrHeb-16"

# End /etc/sysconfig/console</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Due to the use of a 512-glyph LatArCyrHeb-16 font in the previous example, bright colors are no longer available on the Linux console unless a framebuffer is used. If one wants to have bright colors without a framebuffer and can live without characters not belonging to his language, it is still possible to use a language-specific 256-glyph font, as illustrated below:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/console

UNICODE="1"
KEYMAP="bg_bds-utf8"
FONT="cyr-sun16"

# End /etc/sysconfig/console</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The following example illustrates keymap autoconversion from ISO-8859-15 to UTF-8 and enabling dead keys in Unicode mode:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<userinput>cat &gt; /etc/sysconfig/console &lt;&lt; "EOF"
<literal># Begin /etc/sysconfig/console

UNICODE="1"
KEYMAP="de-latin1"
KEYMAP_CORRECTIONS="euro2"
LEGACY_CHARSET="iso-8859-15"
FONT="LatArCyrHeb-16 -m 8859-15"

# End /etc/sysconfig/console</literal>
EOF</userinput>
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Some keymaps have dead keys (i.e., keys that don't produce a character by themselves, but put an accent on the character produced by the next key) or define composition rules (such as: <quote>press Ctrl+. A E to get &AElig;</quote> in the default keymap). Linux-&linux-version; interprets dead keys and composition rules in the keymap correctly only when the source characters to be composed together are not multibyte. This deficiency doesn't affect keymaps for European languages, because there accents are added to unaccented ASCII characters, or two ASCII characters are composed together. However, in UTF-8 mode it is a problem; e.g., for the Greek language, where one sometimes needs to put an accent on the letter α. The solution is either to avoid the use of UTF-8, or to install the X window system, which doesn't have this limitation, in its input handling.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
For Chinese, Japanese, Korean, and some other languages, the Linux console cannot be configured to display the needed characters. Users who need such languages should install the X Window System, fonts that cover the necessary character ranges, and the proper input method (e.g., SCIM supports a wide variety of languages).
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <filename>/etc/sysconfig/console</filename> file only controls the Linux text console localization. It has nothing to do with setting the proper keyboard layout and terminal fonts in the X Window System, with ssh sessions, or with a serial console. In such situations, limitations mentioned in the last two list items above do not apply.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Creating Files at Boot
 
Linux From Scratch 12.2/chapter09_usage — Spanish
File creation at boot
 
Linux From Scratch 12.2/chapter09_usage — Spanish
At times, it is desirable to create files at boot time. For instance, the <filename class="directory">/tmp/.ICE-unix</filename> directory is often needed. This can be done by creating an entry in the <filename>/etc/sysconfig/createfiles</filename> configuration script. The format of this file is embedded in the comments of the default configuration file.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Configuring the Sysklogd Script
 
Linux From Scratch 12.2/chapter09_usage — Spanish
sysklogd
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The <filename>sysklogd</filename> script invokes the <command>syslogd</command> program as a part of System V initialization. The <parameter>-m 0</parameter> option turns off the periodic timestamp mark that <command>syslogd</command> writes to the log files every 20 minutes by default. If you want to turn on this periodic timestamp mark, edit <filename>/etc/sysconfig/rc.site</filename> and define the variable SYSKLOGD_PARMS to the desired value. For instance, to remove all parameters, set the variable to a null value:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
SYSKLOGD_PARMS=
 
Linux From Scratch 12.2/chapter09_usage — Spanish
See <userinput>man syslogd</userinput> for more options.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The rc.site File
 
Linux From Scratch 12.2/chapter09_usage — Spanish
rc.site
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The optional <filename>/etc/sysconfig/rc.site</filename> file contains settings that are automatically set for each SystemV boot script. It can alternatively set the values specified in the <filename>hostname</filename>, <filename>console</filename>, and <filename>clock</filename> files in the <filename class='directory'>/etc/sysconfig/</filename> directory. If the associated variables are present in both these separate files and <filename>rc.site</filename>, the values in the script-specific files take effect.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
<filename>rc.site</filename> also contains parameters that can customize other aspects of the boot process. Setting the IPROMPT variable will enable selective running of bootscripts. Other options are described in the file comments. The default version of the file is as follows:
 
Linux From Scratch 12.2/chapter09_usage — Spanish
&site;
 
Linux From Scratch 12.2/chapter09_usage — Spanish
Customizing the Boot and Shutdown Scripts
 
Linux From Scratch 12.2/chapter09_usage — Spanish
The LFS boot scripts boot and shut down a system in a fairly efficient manner, but there are a few tweaks you can make in the rc.site file to improve speed even more, and to adjust messages according to your preferences. To do this, adjust the settings in the <filename>/etc/sysconfig/rc.site</filename> file above.
 
Linux From Scratch 12.2/chapter09_usage — Spanish
During the boot script <filename>udev</filename>, there is a call to <command>udev settle</command> that requires some time to complete. This time may or may not be required depending on the devices in the system. If you only have simple partitions and a single ethernet card, the boot process will probably not need to wait for this command. To skip it, set the variable OMIT_UDEV_SETTLE=y.