mirror of
https://git.linuxfromscratch.org/lfs.git
synced 2025-06-19 11:49:20 +01:00
fixed setup to 'set up'
git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1883 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
This commit is contained in:
parent
02ef5b5866
commit
34a2f0ce88
@ -39,7 +39,7 @@ device.</para></sect4>
|
|||||||
or aren't network based.</para></sect4>
|
or aren't network based.</para></sect4>
|
||||||
|
|
||||||
<sect4><title>network</title>
|
<sect4><title>network</title>
|
||||||
<para>The network script setup network interfaces (such as network cards)
|
<para>The network script sets up network interfaces (such as network cards)
|
||||||
and sets up the default gateway where applicable.</para></sect4>
|
and sets up the default gateway where applicable.</para></sect4>
|
||||||
|
|
||||||
<sect4><title>rc</title>
|
<sect4><title>rc</title>
|
||||||
|
@ -497,7 +497,7 @@ files (dependencies, download location, descriptions)</para></listitem>
|
|||||||
installation.</para></listitem>
|
installation.</para></listitem>
|
||||||
|
|
||||||
<listitem><para>January 15th, 2002 [gerard]: Chapter 7: Removed most of the
|
<listitem><para>January 15th, 2002 [gerard]: Chapter 7: Removed most of the
|
||||||
scripts, only left the part of a few where we setup up config files in
|
scripts, only left the part of a few where we set up config files in
|
||||||
/etc/sysconfig.</para></listitem>
|
/etc/sysconfig.</para></listitem>
|
||||||
|
|
||||||
<listitem><para>January 15th, 2002 [gerard]: Chapter 6 - Configuring
|
<listitem><para>January 15th, 2002 [gerard]: Chapter 6 - Configuring
|
||||||
|
@ -11,7 +11,7 @@ makes sense because you would still have access to those files when you boot
|
|||||||
into the LFS system. $LFS/usr/src is just a logical place to store source
|
into the LFS system. $LFS/usr/src is just a logical place to store source
|
||||||
code, but by no means a requirement. You may even want to create a
|
code, but by no means a requirement. You may even want to create a
|
||||||
subdirectory under $LFS/usr/src for tarball storage. That way you can
|
subdirectory under $LFS/usr/src for tarball storage. That way you can
|
||||||
seperate tarballs from temporary build directories, but again that's up
|
separate tarballs from temporary build directories, but again that's up
|
||||||
to you.</para>
|
to you.</para>
|
||||||
|
|
||||||
<para>The next chapter contains a list of all the packages that need to be
|
<para>The next chapter contains a list of all the packages that need to be
|
||||||
|
@ -15,7 +15,7 @@ example, if you have a Dutch keyboard, you would run:</para>
|
|||||||
|
|
||||||
<para><screen><userinput>ln -s i386/qwerty/nl.map.gz /usr/share/kbd/keymaps/defkeymap.map.gz</userinput></screen></para>
|
<para><screen><userinput>ln -s i386/qwerty/nl.map.gz /usr/share/kbd/keymaps/defkeymap.map.gz</userinput></screen></para>
|
||||||
|
|
||||||
<para>An second option to configure your keyboard's layout is to compile
|
<para>A second option to configure your keyboard's layout is to compile
|
||||||
the keymap directly into the kernel. This will make sure that your
|
the keymap directly into the kernel. This will make sure that your
|
||||||
keyboard always works as expected, even when you have booted into
|
keyboard always works as expected, even when you have booted into
|
||||||
maintenance mode (by passing `init=/bin/sh' to the kernel) in which case
|
maintenance mode (by passing `init=/bin/sh' to the kernel) in which case
|
||||||
|
Loading…
Reference in New Issue
Block a user