mirror of https://github.com/tLDP/LDP
- a bit more
This commit is contained in:
klakier
parent
4ef54b3311
commit
5db8a40701
|
|
@ -1,19 +1,27 @@
|
|||
<chapter id="oper">
|
||||
<title>Basic operation</title>
|
||||
<abstract>
|
||||
<para>Some basics</para>
|
||||
</abstract>
|
||||
<section>
|
||||
<title>Restarting and shutting down</title>
|
||||
<para>
|
||||
Traditional way of shutting down the machine is via <command>shutdown</command>
|
||||
command, e.g.:
|
||||
<programlisting>shutdown -h now</programlisting>.</para>
|
||||
<para>
|
||||
Using <command>halt</command> also works fine; simply type:
|
||||
<programlisting>halt</programlisting> and wait until system is down.
|
||||
</para>
|
||||
</section>
|
||||
<chapter id="oper">
|
||||
<title>Basic operation</title>
|
||||
<abstract>
|
||||
<para>Some basics</para>
|
||||
</abstract>
|
||||
<section>
|
||||
<title>Restarting and shutting down</title>
|
||||
<para>
|
||||
Traditional way of shutting down the machine is via <command>shutdown</command>
|
||||
command, e.g.:
|
||||
<programlisting>shutdown -h now</programlisting></para>
|
||||
<para>
|
||||
But two simple commands can be used instead:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><command>halt</command> immediatelly runs shutdown procedure</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><command>reboot</command> immediatelly runs reboot procedure</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
On PC computers reboot can be also invoked by pressing Ctrl-Alt-Del sequence.
|
||||
</para>
|
||||
</section>
|
||||
<section id="subsystems">
|
||||
<title>Starting/stopping particular subsystems</title>
|
||||
<para>
|
||||
|
|
@ -22,7 +30,7 @@
|
|||
driver script
|
||||
available in <filename>/etc/rc.d/init.d/</filename> directory.
|
||||
If you run script without parameters, it displays short info, e.g.
|
||||
<emphasis>network</emphasis> subsystem script diplays:
|
||||
<emphasis>network</emphasis> subsystem script displays:
|
||||
<programlisting>
|
||||
# /etc/rc.d/init.d/network
|
||||
Usage: /etc/rc.d/init.d/network {start|stop|restart|status}
|
||||
|
|
@ -66,6 +74,23 @@ Usage: /etc/rc.d/init.d/network {start|stop|restart|status}
|
|||
|
||||
</variablelist>
|
||||
</para>
|
||||
<example>
|
||||
<title>Starting/stopping services</title>
|
||||
<para>
|
||||
This example sequence stops and starts network again
|
||||
(turning on/off existing interfaces, setting default routing, etc. See
|
||||
<xref linkend="network"/>)
|
||||
</para>
|
||||
<programlisting>
|
||||
[root@pldmachine root]# /etc/rc.d/init.d/network stop
|
||||
Shutting down interface eth0.......................................[ DONE ]
|
||||
Shutting down interface eth1.......................................[ DONE ]
|
||||
[root@pldmachine root]# /etc/rc.d/init.d/network start
|
||||
Setting network parameters.........................................[ DONE ]
|
||||
Bringing up interface eth0.........................................[ DONE ]
|
||||
Bringing up interface eth1.........................................[ DONE ]
|
||||
</programlisting>
|
||||
</example>
|
||||
</section>
|
||||
<section id="runlevels">
|
||||
<title>Changing runlevels</title>
|
||||
|
|
|
|||
|
|
@ -1,10 +1,10 @@
|
|||
<chapter>
|
||||
<chapter id="network">
|
||||
<title>Network configuration</title>
|
||||
<section id="interfaces">
|
||||
<title>Interfaces</title>
|
||||
<para>ethernet, dial-ups, how to up/down interface</para>
|
||||
</section>
|
||||
<section>
|
||||
<section id="sysconfig-network">
|
||||
<title>Basic configuration</title>
|
||||
<para>resolver, local network, hostname, default router</para>
|
||||
</section>
|
||||
|
|
|
|||
|
|
@ -233,51 +233,58 @@ source=Primary PLD ftp server,ftp,ftp.pld.org.pl,/PLD-1.0/i586/PLD/,RPMS,inst</p
|
|||
</variablelist>
|
||||
|
||||
</section>
|
||||
<section>
|
||||
<title>Managing bootloaders with rc-boot</title>
|
||||
<para>
|
||||
PLD comes with simple utility called <emphasis>rc-boot</emphasis>.
|
||||
This package
|
||||
provides an uniform interface to install and update bootloader.
|
||||
With rc-boot this task can be done with simple running
|
||||
<command>rc-boot</command> command;
|
||||
what bootloader should rc-boot use, and what are bootloader options,
|
||||
this is specified in uniform way
|
||||
in rc-boot config files instead of particular bootloader's config files.
|
||||
Basic rc-boot behaviour is controlled by file
|
||||
<filename>/etc/sysconfig/rc-boot/config</filename>.
|
||||
To know what linux kernels or other systems should be available
|
||||
at boot time, rc-boot needs also <quote>image description</quote>
|
||||
files residing in
|
||||
directory <filename>/etc/sysconfig/rc-boot/config/</filename>.
|
||||
Newly installed system should contain at least one these file,
|
||||
that is, the file describing default system kernel,
|
||||
but in general it is possible to have more of them.
|
||||
Image description files can be written by the user, but the main idea of
|
||||
rc-boot was that they come with particular packages that need to be
|
||||
handled by bootloader. These packages are primarily kernel packages,
|
||||
but can be also other packages like memtest86 etc.
|
||||
</para>
|
||||
<para>
|
||||
It is used for easy kernel upgrades:
|
||||
as was just mentioned, each kernel rpm package comes with
|
||||
<quote>boot image description</quote> file.
|
||||
During kernel package installation, rc-boot is automatically invoked to ensure that
|
||||
newly installed kernel will be seen by bootloader at next boot-up.
|
||||
</para>
|
||||
<note>
|
||||
<section id="bootloaders">
|
||||
<title>Bootloaders</title>
|
||||
<section>
|
||||
<title>General issues</title>
|
||||
<para>initrd etc, geninitrd etc</para>
|
||||
</section>
|
||||
<section>
|
||||
<title>Easy way: rc-boot</title>
|
||||
<para>
|
||||
rc-boot support works only if rc-boot is installed (thats obvious),
|
||||
but it must also be enabled. This is done in it's main config file.
|
||||
For details refer to
|
||||
<citerefentry>
|
||||
<refentrytitle>rc-boot</refentrytitle>
|
||||
<manvolnum>8</manvolnum>
|
||||
</citerefentry>.
|
||||
PLD comes with simple utility called <emphasis>rc-boot</emphasis>.
|
||||
This package
|
||||
provides an uniform interface to install and update bootloader.
|
||||
With rc-boot this task can be done with simple running
|
||||
<command>rc-boot</command> command;
|
||||
what bootloader should rc-boot use, and what are bootloader options,
|
||||
this is specified in uniform way
|
||||
in rc-boot config files instead of particular bootloader's config files.
|
||||
Basic rc-boot behaviour is controlled by file
|
||||
<filename>/etc/sysconfig/rc-boot/config</filename>.
|
||||
To know what linux kernels or other systems should be available
|
||||
at boot time, rc-boot needs also <quote>image description</quote>
|
||||
files residing in
|
||||
directory <filename>/etc/sysconfig/rc-boot/config/</filename>.
|
||||
Newly installed system should contain at least one these file,
|
||||
that is, the file describing default system kernel,
|
||||
but in general it is possible to have more of them.
|
||||
Image description files can be written by the user, but the main idea of
|
||||
rc-boot was that they come with particular packages that need to be
|
||||
handled by bootloader. These packages are primarily kernel packages,
|
||||
but can be also other packages like memtest86 etc.
|
||||
</para>
|
||||
</note>
|
||||
<para>
|
||||
It is used for easy kernel upgrades:
|
||||
as was just mentioned, each kernel rpm package comes with
|
||||
<quote>boot image description</quote> file.
|
||||
During kernel package installation, rc-boot is automatically invoked to ensure that
|
||||
newly installed kernel will be seen by bootloader at next boot-up.
|
||||
</para>
|
||||
<note>
|
||||
<para>
|
||||
rc-boot support works only if rc-boot is installed (thats obvious),
|
||||
but it must also be enabled. This is done in it's main config file.
|
||||
For details refer to
|
||||
<citerefentry>
|
||||
<refentrytitle>rc-boot</refentrytitle>
|
||||
<manvolnum>8</manvolnum>
|
||||
</citerefentry>.
|
||||
</para>
|
||||
</note>
|
||||
</section>
|
||||
</section>
|
||||
</chapter>
|
||||
</chapter>
|
||||
|
||||
|
||||
<!-- Keep this comment at the end of the file
|
||||
|
|
|
|||
|
|
@ -1,20 +1,66 @@
|
|||
<chapter>
|
||||
<title>System configuration</title>
|
||||
<section>
|
||||
<title>Kernel modules</title>
|
||||
<section id="modules">
|
||||
<title>Device support (kernel modules config)</title>
|
||||
<para>
|
||||
Kernel modules configuration is stored in <filename>/etc/modules.conf</filename>.
|
||||
Some common examples:</para>
|
||||
PLD contains highly modularized kernel.
|
||||
All kernel-supported device drivers that can be compiled as a module
|
||||
are compiled in this way.
|
||||
</para>
|
||||
<para>
|
||||
Use kernel module <literal>3c509</literal> (3Com 509/509b adapter) to handle first ethernet
|
||||
device (eth0):
|
||||
To support devices available in the system, proper modules must be
|
||||
loaded into the kernel. That can be done primarily in four ways:
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
They can be loaded by hand with <command>modprobe</command> or
|
||||
<command>insmod</command> command (the least convenient method)
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
They can be loaded at boot-up by some extra script
|
||||
(e.g. /etc/rc.d/init/rc.local).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Some devices (mainly disk interfaces)
|
||||
need support at very very early stage of system boot-up.
|
||||
Modules for these devices must be loade from
|
||||
so-called <emphasis>initrd</emphasis>
|
||||
(see more in <xref linkend="bootloaders"/>)
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Finally, they can be loaded automatically, when they are
|
||||
needed, by <command>kmod</command> daemon.
|
||||
</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
The latter method is most convenient, although not every device can be
|
||||
supported like that.
|
||||
</para>
|
||||
<para>
|
||||
Some typical entries in <filename>/etc/modules.conf</filename>:
|
||||
</para>
|
||||
<para>
|
||||
Use kernel module <literal>3c509</literal> (3Com 509/509b adapter) to support
|
||||
first ethernet device (eth0):
|
||||
<programlisting>alias eth0 3c509</programlisting>
|
||||
|
||||
Use kernel module <literal>aic7xxx</literal> to handle SCSI hostadapter:
|
||||
<programlisting>alias scsi_hostadapter aic7xxx</programlisting>
|
||||
</para>
|
||||
<para>
|
||||
See <citerefentry><refentrytitle>modules.conf</refentrytitle></citerefentry>for details.
|
||||
See
|
||||
<citerefentry>
|
||||
<refentrytitle>modules.conf</refentrytitle>
|
||||
<manvolnum>5</manvolnum>
|
||||
</citerefentry>
|
||||
for details.
|
||||
</para>
|
||||
</section>
|
||||
<section>
|
||||
|
|
@ -27,35 +73,63 @@
|
|||
removable media: CD, diskettes etc
|
||||
user access
|
||||
automounter
|
||||
LVM?
|
||||
journaling?
|
||||
raid?
|
||||
</literallayout>
|
||||
</section>
|
||||
<section id="inittab">
|
||||
<title>Init control: /etc/inittab</title>
|
||||
<para>
|
||||
This file is read by <command>init</command> to control
|
||||
behaviour in particular runlevel.
|
||||
What it usually contains is:
|
||||
system behaviour in particular runlevel. Full description
|
||||
of this file can be found in
|
||||
<citerefentry>
|
||||
<refentrytitle>inittab</refentrytitle>
|
||||
<manvolnum>5</manvolnum>
|
||||
</citerefentry>
|
||||
</para>
|
||||
<para>
|
||||
What this file usually contains:
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>
|
||||
<emphasis>Default runlevel</emphasis> - the runlevel used
|
||||
when init is invoked without parameters (e.g. during system startup).
|
||||
(runlevels are described in <xref linkend="runlevels"/>),
|
||||
(runlevels are described in <xref linkend="runlevels"/>).
|
||||
Default runlevel is given in the form:
|
||||
<programlisting>id:3:initdefault:</programlisting>
|
||||
Here the digit 3 indicates use of runlevel 3. This can be changed
|
||||
to any other valid runlevel.
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Instructions to start consoles.
|
||||
Instructions to run getty on consoles. They look like that:
|
||||
<programlisting>1:12345:respawn:/sbin/mingetty --noclear tty1</programlisting>.
|
||||
One of possible situations when this needs to be changed is
|
||||
when we want console on serial port (see e.g. <xref linkend="installer-serial"/>).
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Invocation of proper init scripts.
|
||||
Invocation of proper init scripts. These are lines like this
|
||||
<programlisting>
|
||||
si::sysinit:/etc/rc.d/rc.sysinit
|
||||
l0:0:wait:/etc/rc.d/rc 0
|
||||
</programlisting>
|
||||
</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>
|
||||
Handling special events like Ctrl-Alt-Del keystroke.
|
||||
The line looks like this:
|
||||
<programlisting>
|
||||
ca::ctrlaltdel:/sbin/shutdown -t3 -r now
|
||||
</programlisting>
|
||||
The command run at Ctrl-Alt-Del event can be replaced here,
|
||||
e.g. one can change <command>shutdown -r</command>
|
||||
to <command>shutdown -h</command> to get the halt instead reboot.
|
||||
</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
|
|
|||
|
|
@ -69,7 +69,7 @@
|
|||
serial console, and kernel will use /dev/ttyS0 as /dev/console.
|
||||
</para>
|
||||
<para>
|
||||
Try it - it really works, and once you'll start using serial
|
||||
Try it - it really works, and once you start using serial
|
||||
console, you will find it really usefull - for example think
|
||||
of remote console access.
|
||||
</para>
|
||||
|
|
|
|||
Loading…
Reference in New Issue