lfs/LFS_Book
1
0
Fork 0
mirror of https://github.com/avmaisak/LFS_Book.git synced 2026-01-14 02:00:45 +00:00
Code Issues Packages Projects Releases Wiki Activity

batch contents translation

Browse Source
This commit is contained in:
Anton Maisak
2018-06-08 12:15:49 +03:00
parent 7c678f2519
commit d4510ee034
27 changed files with 98 additions and 98 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
chapter07/bootscripts.xml
View File

@ -17,14 +17,14 @@
<title>LFS-Bootscripts-&lfs-bootscripts-version;</title>
<indexterm zone="ch-scripts-bootscripts">
<primary sortas="a-Bootscripts">Bootscripts</primary>
<primary sortas="a-Bootscripts">Загрузочные файлы сценариев</primary>
</indexterm>
<sect2 role="package">
<title/>
<para>The LFS-Bootscripts пакет содержит a set of scripts to start/stop
the LFS system at bootup/shutdown.
the LFS system at bootup/shutdown.
The configuration files and procedures needed to
customize the boot process are described in the following sections.</para>

2
chapter07/chapter07.xml
View File

@ -9,7 +9,7 @@
<?dbhtml dir="chapter07"?>
<?dbhtml filename="chapter07.html"?>
<title>System Configuration</title>
<title>Конфигурация системы</title>
<!-- sysv -->
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.xml"/>

2
chapter07/clock.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-clock" revision="systemd">
<?dbhtml filename="clock.html"?>
<title>Configuring the system clock</title>
<title>Настройка системных часов</title>
<indexterm zone="ch-scripts-clock">
<primary sortas="d-clock">clock</primary>

4
chapter07/console.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-console">
<?dbhtml filename="console.html"?>
<title>Configuring the Linux Console</title>
<title>Настройка консоли Linux</title>
<indexterm zone="ch-scripts-console">
<primary sortas="d-console">console</primary>
@ -31,7 +31,7 @@
information. Decide which keymap and screen font will be used. Various
language-specific HOWTOs can also help with this, see <ulink
url="http://www.tldp.org/HOWTO/HOWTO-INDEX/other-lang.html"/>. If still in
doubt, look in the <filename class="directory">/usr/share/keymaps</filename>
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 <filename>loadkeys(1)</filename> and
<filename>setfont(8)</filename> manual pages to determine the correct

2
chapter07/consoled.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-console" revision="systemd">
<?dbhtml filename="console.html"?>
<title>Configuring the Linux Console</title>
<title>Настройка консоли Linux</title>
<indexterm zone="ch-scripts-console">
<primary sortas="d-console">console</primary>

2
chapter07/etcshells.xml
View File

@ -14,7 +14,7 @@
<date>$Date$</date>
</sect1info>
-->
<title>Creating the /etc/shells File</title>
<title>Создание файла /etc/shells</title>
<indexterm zone="ch-config-shells">
<primary sortas="e-etc-shells">/etc/shells</primary>

2
chapter07/hostname.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-hostname">
<?dbhtml filename="hostname.html"?>
<title>Configuring the system hostname</title>
<title>Настройка имени хоста системы</title>
<indexterm zone="ch-scripts-hostname">
<primary sortas="d-hostname">hostname</primary>

2
chapter07/hosts.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-hosts">
<?dbhtml filename="hosts.html"?>
<title>Customizing the /etc/hosts File</title>
<title>Настройка файла /etc/hosts</title>
<indexterm zone="ch-scripts-hosts">
<primary sortas="e-/etc/hosts">/etc/hosts</primary>

2
chapter07/inputrc.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-inputrc">
<?dbhtml filename="inputrc.html"?>
<title>Creating the /etc/inputrc File</title>
<title>Создание файла /etc/inputrc File</title>
<indexterm zone="ch-scripts-inputrc">
<primary sortas="e-/etc/inputrc">/etc/inputrc</primary>

2
chapter07/locale.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-locale" revision="systemd">
<?dbhtml filename="locale.html"?>
<title>Configuring the System Locale</title>
<title>Настройка языкового стандарта системы</title>
<indexterm zone="ch-scripts-locale">
<primary sortas="e-etc-locale-conf">/etc/locale.conf</primary>

22
chapter07/network.xml
View File

@ -41,7 +41,7 @@
will assign network card interface names based on system physical
characteristics such as enp2s1. If you are not sure what your interface
name is, you can always run <command>ip link</command> or <command>ls
/sys/class/net</command> after you have booted your system.
/sys/class/net</command> after you have booted your system.
</para></note>
<para>The following command creates a sample file for the
@ -97,7 +97,7 @@ EOF</userinput></screen>
</sect2>
<sect2 id="resolv.conf">
<title>Creating the /etc/resolv.conf File</title>
<title>Создание файла /etc/resolv.conf</title>
<indexterm zone="resolv.conf">
<primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
@ -161,26 +161,26 @@ EOF</userinput></screen>
</sect2>
<sect2 id="ch-scripts-hosts">
<title>Customizing the /etc/hosts File</title>
<title>Настройка файла /etc/hosts</title>
<indexterm zone="ch-scripts-hosts">
<primary sortas="e-/etc/hosts">/etc/hosts</primary>
</indexterm>
<indexterm zone="ch-scripts-hosts">
<primary sortas="d-localnet">localnet</primary>
<secondary>/etc/hosts</secondary>
</indexterm>
<indexterm zone="ch-scripts-hosts">
<primary sortas="d-network">network</primary>
<secondary>/etc/hosts</secondary>
</indexterm>
<para>Decide on the IP address, fully-qualified domain name (FQDN), and
possible aliases for use in the <filename>/etc/hosts</filename> file. The
syntax is:</para>
<screen><literal>IP_address myhost.example.org aliases</literal></screen>
<para>Unless the computer is to be visible to the Internet (i.e., there is
@ -195,13 +195,13 @@ EOF</userinput></screen>
<para>x can be any number in the range 16-31. y can be any number in the
range 0-255.</para>
<para>A valid private IP address could be 192.168.1.1. A valid FQDN for
this IP could be lfs.example.org.</para>
<para>Even if not using a network card, a valid FQDN is still required.
This is necessary for certain programs to operate correctly.</para>
<para>Create the <filename>/etc/hosts</filename> file выполнив команду:</para>
<screen><userinput>cat &gt; /etc/hosts &lt;&lt; "EOF"
@ -218,7 +218,7 @@ ff02::2 ip6-allrouters
EOF</userinput></screen>
<para>The <replaceable>&lt;192.168.1.1&gt;</replaceable>,
<replaceable>&lt;FQDN&gt;</replaceable>, and
<replaceable>&lt;FQDN&gt;</replaceable>, and
<replaceable>&lt;HOSTNAME&gt;</replaceable> values need to be
changed for specific uses or requirements (if assigned an IP address by a
network/system administrator and the machine will be connected to an

22
chapter07/networkd.xml
View File

@ -38,7 +38,7 @@
<filename class="extension">.link</filename>,
<filename class="extension">.netdev</filename> and
<filename class="extension">.network</filename> files. For detailed
descriptions and example contents of these configuration files, consult
descriptions and example contents of these configuration files, consult
the <filename>systemd-link(5)</filename>,
<filename>systemd-netdev(5)</filename> and
<filename>systemd-network(5)</filename> manual pages.</para>
@ -57,7 +57,7 @@
For most systems, there is only one network interface for
each type of connection. For example, the classic interface
name for a wired connection is eth0. A wireless connection
will usually have the name wifi0 or wlan0.
will usually have the name wifi0 or wlan0.
</para>
<para>
@ -75,10 +75,10 @@
<listitem>
<para>
Create a manual naming scheme, for example by naming the
interfaces something like "internet0", "dmz0", or "lan0".
interfaces something like "internet0", "dmz0", or "lan0".
For that, create .link
files in /etc/systemd/network/, that choose an explicit name or a
better naming scheme for one, some, or all of your interfaces.
better naming scheme for one, some, or all of your interfaces.
For example:
</para>
@ -92,13 +92,13 @@ Name=ether0</literal>
EOF</userinput></screen>
<para>
See the man page systemd.link(5) for more information.
See the man page systemd.link(5) for more information.
</para>
</listitem>
<listitem>
<para>
In /boot/grub/grub.cfg, pass the option net.ifnames=0 on the
In /boot/grub/grub.cfg, pass the option net.ifnames=0 on the
kernel command line.
</para>
</listitem>
@ -151,7 +151,7 @@ EOF</userinput></screen>
</sect2>
<sect2 id="resolv.conf">
<title>Creating the /etc/resolv.conf File</title>
<title>Создание файла /etc/resolv.conf</title>
<indexterm zone="resolv.conf">
<primary sortas="e-/etc/resolv.conf">/etc/resolv.conf</primary>
@ -244,17 +244,17 @@ EOF</userinput></screen>
</sect2>
<sect2 id="ch-scripts-hosts">
<title>Customizing the /etc/hosts File</title>
<title>Настройка файла /etc/hosts</title>
<indexterm zone="ch-scripts-hosts">
<primary sortas="e-/etc/hosts">/etc/hosts</primary>
</indexterm>
<indexterm zone="ch-scripts-hosts">
<primary sortas="d-localnet">localnet</primary>
<secondary>/etc/hosts</secondary>
</indexterm>
<indexterm zone="ch-scripts-hosts">
<primary sortas="d-network">network</primary>
<secondary>/etc/hosts</secondary>
@ -328,7 +328,7 @@ EOF</userinput></screen>
changed for specific uses or requirements (if assigned an IP address by a
network/system administrator and the machine will be connected to an
existing network). The optional alias name(s) can be omitted.</para>
</sect2>
</sect1>

2
chapter07/profile.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-profile" revision="sysv">
<?dbhtml filename="profile.html"?>
<title>The Bash Shell Startup Files</title>
<title>Файлы запуска оболочки Bash</title>
<indexterm zone="ch-scripts-profile">
<primary sortas="e-/etc/profile">/etc/profile</primary>

2
chapter07/setclock.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-clock">
<?dbhtml filename="clock.html"?>
<title>Configuring the System Clock</title>
<title>Настройка системных часов</title>
<para>Procedures for setting the system clock differ between systemd and
System V, however the separate procedures do not conflict so both

2
chapter07/site.xml
View File

@ -9,7 +9,7 @@
<sect1 id="ch-scripts-site">
<?dbhtml filename="site.html"?>
<title>The rc.site File</title>
<title>Файл rc.site</title>
<indexterm zone="ch-scripts-site">
<primary sortas="a-rc.site">rc.site</primary>

24
chapter07/symlinks.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-symlinks">
<?dbhtml filename="symlinks.html"?>
<title>Managing Devices</title>
<title>Управление устройствами</title>
<sect2 revision="sysv">
@ -22,7 +22,7 @@
Intel and Realtek, the network card manufactured by Intel may become eth0
and the Realtek card becomes eth1. In some cases, after a reboot the cards
get renumbered the other way around.</para>
<para>In the new naming scheme, typical network device names would then
be something like enp5s0 or wlp3s0. If this naming convention is not
desired, the traditional naming scheme or a custom scheme can be
@ -30,20 +30,20 @@
<sect3>
<title>Disabling Persistent Naming on the Kernel Command Line</title>
<para>The traditional naming scheme using eth0, eth1, etc can be
restored by adding <userinput>net.ifnames=0</userinput> on the
restored by adding <userinput>net.ifnames=0</userinput> on the
kernel command line. This is most appropriate for those systems
that have only one ethernet device of the same type. Laptops
often have multiple ethernet connections that are named eth0 and
wlan0 and are also candidates for this method. The command line
is passed in the GRUB configuration file.
often have multiple ethernet connections that are named eth0 and
wlan0 and are also candidates for this method. The command line
is passed in the GRUB configuration file.
See <xref linkend="grub-cfg"/>.</para>
</sect3>
<sect3>
<title>Creating Custom Udev Rules</title>
<para>The naming scheme can be customized by creating custom Udev
rules. A script has been included that generates the initial rules.
Generate these rules выполнив команду:</para>
@ -61,7 +61,7 @@
the network rules file may not have been generated because addresses
are not consistently assigned. In these cases, this method cannot
be used.</para></note>
<para>The file begins with a comment block followed by two lines for each
NIC. The first line for each NIC is a commented description showing its
hardware IDs (e.g. its PCI vendor and device IDs, if it's a PCI card),
@ -69,11 +69,11 @@
the hardware ID nor the driver is used to determine which name to give an
interface; this information is only for reference. The second line is the
Udev rule that matches this NIC and actually assigns it a name.</para>
<para>All Udev rules are made up of several keys, separated by commas and
optional whitespace. This rule's keys and an explanation of each of them
are as follows:</para>
<itemizedlist>
<listitem>
<para><literal>SUBSYSTEM=="net"</literal> - This tells Udev to ignore
@ -106,7 +106,7 @@
Udev will assign to this interface.</para>
</listitem>
</itemizedlist>
<para>The value of <literal>NAME</literal> is the important part. Make sure
you know which name has been assigned to each of your network cards before
proceeding, and be sure to use that <literal>NAME</literal> value when

2
chapter07/sysklogd.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-sysklogd">
<?dbhtml filename="sysklogd.html"?>
<title>Configuring the sysklogd Script</title>
<title>Настройка сценариев sysklogd</title>
<indexterm zone="ch-scripts-sysklogd">
<primary sortas="d-sysklogd">sysklogd</primary>

14
chapter07/systemd-custom.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-systemd-custom" revision="systemd">
<?dbhtml filename="systemd-custom.html"?>
<title>Systemd Usage and Configuration</title>
<title>Использование и конфигурация Systemd</title>
<indexterm zone="ch-scripts-systemd-custom">
<primary sortas="e-Systemd">Systemd Customization</primary>
@ -54,7 +54,7 @@ EOF</userinput></screen>
<screen role="nodump"><userinput>ln -sfv /dev/null /etc/systemd/system/tmp.mount</userinput></screen>
<para>Alternatively, if a a separate partition for
<filename class="directory">/tmp</filename> is desired, specify that
<filename class="directory">/tmp</filename> is desired, specify that
partition in an <filename>/etc/fstab</filename> entry.</para>
<warning>
@ -79,9 +79,9 @@ EOF</userinput></screen>
<listitem><para>systemd-tmpfiles-setup-dev.service</para></listitem>
<listitem><para>systemd-tmpfiles-setup.service</para></listitem>
</itemizedlist>
<para>The system location for the configuration files is
<filename>/usr/lib/tmpfiles.d/*.conf</filename>. The local
<filename>/usr/lib/tmpfiles.d/*.conf</filename>. The local
configuration files are in
<filename class="directory">/etc/tmpfiles.d</filename>. Files in
<filename class="directory">/etc/tmpfiles.d</filename> override
@ -92,9 +92,9 @@ EOF</userinput></screen>
<para>
Note that the syntax for the
<filename>/usr/lib/tmpfiles.d/*.conf</filename> files can be
<filename>/usr/lib/tmpfiles.d/*.conf</filename> files can be
confusing. For example, the default deletion of files in the /tmp directory
is located in <filename>/usr/lib/tmpfiles.d/tmp.conf</filename> with
is located in <filename>/usr/lib/tmpfiles.d/tmp.conf</filename> with
the line:
<screen role="nodump">q /tmp 1777 root root 10d</screen>
@ -146,7 +146,7 @@ EOF</userinput></screen>
<para>Rather than plain shell scripts used in SysVinit or BSD style init
systems, systemd uses a unified format for different types of startup
files (or units). The command <command>systemctl</command> is used to
enable, disable, control state, and obtain status of unit files. Here
enable, disable, control state, and obtain status of unit files. Here
are some examples of frequently used commands:</para>
<itemizedlist>

4
chapter07/udev.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-scripts-udev">
<?dbhtml filename="udev.html"?>
<title>Overview of Device and Module Handling</title>
<title>Обзор обработки устройств и модулей</title>
<indexterm zone="ch-scripts-udev">
<primary sortas="a-Udev">Udev</primary>
@ -119,7 +119,7 @@
rule for the device it is creating, it will leave the permissions and
ownership at whatever <systemitem
class="filesystem">devtmpfs</systemitem> used initially.</para> </sect3>
<sect3>
<title>Module Loading</title>

46
chapter07/usage.xml
View File

@ -24,7 +24,7 @@
system to another, so it cannot be assumed that because things worked in one
particular Linux distribution, they should work the same in LFS too. LFS has its
own way of doing things, but it respects generally accepted standards.</para>
<para>SysVinit (which will be referred to as <quote>init</quote> from now on)
works using a run-levels scheme. There are seven (numbered 0 to 6) run-levels
(actually, there are more run-levels, but they are for special cases and are
@ -573,28 +573,28 @@ EOF</userinput></screen>
<sect2 id="ch-scripts-createfiles">
<title>Creating Files at Boot</title>
<indexterm zone="ch-scripts-createfiles">
<primary sortas="d-createfiles">File creation at boot</primary>
<secondary>configuring</secondary>
</indexterm>
<para>At times, it is desired to create files at boot time. For instance,
the <filename class="directory">/tmp/.ICE-unix</filename> directory
may be desired. 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
The format of this file is embedded in the comments of the default
configuration file.</para>
</sect2>
<sect2 id="ch-scripts-sysklogd">
<title>Configuring the sysklogd Script</title>
<indexterm zone="ch-scripts-sysklogd">
<primary sortas="d-sysklogd">sysklogd</primary>
<secondary>configuring</secondary>
</indexterm>
<para>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
@ -611,12 +611,12 @@ EOF</userinput></screen>
</sect2>
<sect2 id="ch-scripts-site">
<title>The rc.site File</title>
<title>Файл rc.site</title>
<indexterm zone="ch-scripts-site">
<primary sortas="a-rc.site">rc.site</primary>
</indexterm>
<para>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>,
@ -625,33 +625,33 @@ EOF</userinput></screen>
associated variables are present in both these separate files and
<filename>rc.site</filename>, the values in the script specific files have
precedence. </para>
<para><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:</para>
<!-- Use role to fix a pdf generation problem -->
<screen role="auto">&site;</screen>
<sect3>
<title>Customizing the Boot and Shutdown Scripts</title>
<para>The LFS boot scripts boot and shut down a system in a fairly
efficient manner, but there are a few tweaks that 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.</para>
<itemizedlist>
<listitem><para>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 devices present
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.</para></listitem>
<listitem><para>The boot script <filename>udev_retry</filename> also runs
<command>udev settle</command> by default. This command is only needed by
default if the <filename class='directory'>/var</filename> directory is
@ -660,12 +660,12 @@ EOF</userinput></screen>
also need to wait for udev to complete, but in many installations it is not
needed. Skip the command by setting the variable OMIT_UDEV_RETRY_SETTLE=y.
</para></listitem>
<listitem><para>By default, the file system checks are silent. This can
appear to be a delay during the bootup process. To turn on the
<command>fsck</command> output, set the variable VERBOSE_FSCK=y.
</para></listitem>
<listitem><para>When rebooting, you may want to skip the filesystem check,
<command>fsck</command>, completely. To do this, either create the file
<filename>/fastboot</filename> or reboot the system with the command
@ -674,17 +674,17 @@ EOF</userinput></screen>
<filename>/forcefsck</filename> or running <command>shutdown</command> with
the <parameter>-F</parameter> parameter instead of <parameter>-f</parameter>.
</para>
<para>Setting the variable FASTBOOT=y will disable <command>fsck</command>
during the boot process until it is removed. This is not recommended
on a permanent basis.</para></listitem>
<listitem><para>Normally, all files in the <filename
class='directory'>/tmp</filename> directory are deleted at boot time.
Depending on the number of files or directories present, this can cause a
noticeable delay in the boot process. To skip removing these files set the
variable SKIPTMPCLEAN=y.</para></listitem>
<listitem><para>During shutdown, the <command>init</command> program sends
a TERM signal to each program it has started (e.g. agetty), waits for a set
time (default 3 seconds), and sends each process a KILL signal and waits
@ -696,9 +696,9 @@ EOF</userinput></screen>
-t0 -r now</command>). The delay for the <command>sendsignals</command>
script can be skipped by setting the parameter
KILLDELAY=0.</para></listitem>
</itemizedlist>
</sect3>
</sect2>
</sect1>

2
chapter08/chapter08.xml
View File

@ -9,7 +9,7 @@
<?dbhtml dir="chapter08"?>
<?dbhtml filename="chapter08.html"?>
<title>Making the LFS System Bootable</title>
<title>Делаем систему LFS загрузочной</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="introduction.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="fstab.xml"/>

2
chapter08/fstab.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-bootable-fstab">
<?dbhtml filename="fstab.html"?>
<title>Creating the /etc/fstab File</title>
<title>Создание файла /etc/fstab</title>
<indexterm zone="ch-bootable-fstab">
<primary sortas="e-/etc/fstab">/etc/fstab</primary>

8
chapter08/grub.xml
View File

@ -14,7 +14,7 @@
<address>&grub-url;</address>
</sect1info>
<title>Using GRUB to Set Up the Boot Process</title>
<title>Использование GRUB для настройки процесса загрузки</title>
<sect2>
<title>Введение</title>
@ -34,8 +34,8 @@
url="&blfs-book;multimedia/libisoburn.html">
libisoburn</ulink> package.</para>
<screen role="nodump"><userinput>cd /tmp
grub-mkrescue --output=grub-img.iso
<screen role="nodump"><userinput>cd /tmp
grub-mkrescue --output=grub-img.iso
xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></screen>
<note>
@ -127,7 +127,7 @@ xorriso -as cdrecord -v dev=/dev/cdrw blank=as_needed grub-img.iso</userinput></
</sect2>
<sect2 id="grub-cfg">
<title>Creating the GRUB Configuration File</title>
<title>Создание файла конфигурации GRUB </title>
<para>Generate <filename>/boot/grub/grub.cfg</filename>:</para>

12
chapter08/kernel.xml
View File

@ -23,7 +23,7 @@
<sect2 role="package">
<title/>
<para>The Linux пакет содержит the Linux kernel.</para>
<para>Ядро операционной системы.</para>
<segmentedlist>
<segtitle>&buildtime;</segtitle>
@ -66,7 +66,7 @@
<ulink url="http://www.kroah.com/lkn/"/> </para>
<note>
<para>A good starting place for setting up the kernel configuration is to
run <command>make defconfig</command>. This will set the base
configuration to a good state that takes your current system architecture
@ -138,7 +138,7 @@ Kernel hacking ---&gt;
<para>A fuller description of managing UEFI environments from within LFS
is covered by the lfs-uefi.txt hint at
<ulink
<ulink
url="http://www.linuxfromscratch.org/hints/downloads/files/lfs-uefi.txt"/>.
</para>
</note>
@ -273,11 +273,11 @@ cp -r Documentation/* /usr/share/doc/linux-&linux-version;</userinput></screen>
source.</para>
<note>
<para>In many cases, the configuration of the kernel will need to be
<para>In many cases, the configuration of the kernel will need to be
updated for packages that will be installed later in BLFS. Unlike
other packages, it is not necessary to remove the kernel source tree
after the newly built kernel is installed.</para>
after the newly built kernel is installed.</para>
<para>If the kernel source tree is going to be retained, run
<command>chown -R 0:0</command> on the <filename
class="directory">linux-&linux-version;</filename> directory to ensure

2
chapter09/chapter09.xml
View File

@ -9,7 +9,7 @@
<?dbhtml dir="chapter09"?>
<?dbhtml filename="chapter09.html"?>
<title>The End</title>
<title>Заключение</title>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="theend.xml"/>
<xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="getcounted.xml"/>

2
chapter09/reboot.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-finish-reboot">
<?dbhtml filename="reboot.html"?>
<title>Rebooting the System</title>
<title>Перезагрузка системы</title>
<para>Now that all of the software has been installed, it is time to reboot
your computer. However, you should be aware of a few things. The system you

4
chapter09/theend.xml
View File

@ -8,7 +8,7 @@
<sect1 id="ch-finish-theend">
<?dbhtml filename="theend.html"?>
<title>The End</title>
<title>Заключение</title>
<indexterm zone="ch-finish-theend">
<primary sortas="e-/etc/lfs-release">/etc/lfs-release</primary>
@ -25,7 +25,7 @@
<para>Well done! The new LFS system is installed! We wish you much
success with your shiny new custom-built Linux system.</para>
<para revision="systemd">Create an <filename>/etc/os-release</filename>
<para revision="systemd">Create an <filename>/etc/os-release</filename>
file required by systemd:</para>
<screen revision="systemd"><userinput>cat &gt; /etc/os-release &lt;&lt; "EOF"