Changeset 53b5ccf


Ignore:
Timestamp:
03/19/2001 02:30:14 PM (23 years ago)
Author:
Thomas Balu Walter <tw@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v3_0, v3_1, v3_2, v3_3, v4_0, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
81a47c0
Parents:
137bd50
Message:

You

git-svn-id: ​http://svn.linuxfromscratch.org/LFS/trunk/BOOK@336 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Files:
17 edited

Legend:

Unmodified
Added
Removed

  • chapter07/checkfs.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/checkfs</filename> containing
     5A new file <filename>/etc/init.d/checkfs</filename> is created containing
    66the following:
    77</para>

  • chapter07/createdirs.xml

    r137bd50 r53b5ccf  
    44<para>
    55We need to start by creating a few extra directories that are used by
    6 the boot scripts. Create these directories by running:
     6the boot scripts. These directories are created by running:
    77</para>
    88

  • chapter07/fstab.xml

    r137bd50 r53b5ccf  
    55In order for certain programs to be able to determine where certain
    66partitions are supposed to be mounted by default, the /etc/fstab file is
    7 used. Create a new file <filename>/etc/fstab</filename> containing the
     7used. A new file <filename>/etc/fstab</filename> is created containing the
    88following:
    99</para>
    … …  
    2424
    2525<para>
    26 Replace &lt;LFS-partition designation&gt;, &lt;swap-partition
    27 designation&gt; and &lt;fs-type&gt; with the appropriate values
     26&lt;LFS-partition designation&gt;, &lt;swap-partition
     27designation&gt; and &lt;fs-type&gt; have to be replaced with the appropriate
     28 values
    2829(/dev/hda2, /dev/hda5 and reiserfs for example).
    2930</para>

  • chapter07/functions.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/functions</filename> containing
     5A new file <filename>/etc/init.d/functions</filename> is created containing
    66the following:
    77</para>

  • chapter07/halt.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/halt</filename> containing the
     5A new file <filename>/etc/init.d/halt</filename> is created containing the
    66following:
    77</para>

  • chapter07/loadkeys.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 You only need to create this script if you don't have a default 101 keys
    6 US keyboard layout. Create a new file
    7 <filename>/etc/init.d/loadkeys</filename> containing  the following:
     5A user only needs to create this script if he don't have a default 101 keys
     6US keyboard layout. A new file
     7<filename>/etc/init.d/loadkeys</filename> containing  the following has to be
     8created:
    89</para>
    910

  • chapter07/mountfs.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/mountfs</filename> containing
     5A new file <filename>/etc/init.d/mountfs</filename> is created containing
    66the following:
    77</para>

  • chapter07/rc.xml

    r137bd50 r53b5ccf  
    44<para>
    55The first main bootscript is the <filename>/etc/init.d/rc</filename> script.
    6 Create a new file <filename>/etc/init.d/rc</filename> containing the
     6A new file <filename>/etc/init.d/rc</filename> is created containing the
    77following: </para>
    88

  • chapter07/setclock.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 The following script is only for real use when your hardware clock (also
     5The following script is only for real use when the hardware clock (also
    66known as BIOS or CMOS clock) isn't set to GMT time. The recommended
    7 setup is setting your hardware clock to GMT and have the time converted
    8 to localtime using the /etc/localtime symbolic link. But if you run an
    9 OS that doesn't understand a clock set to GMT (most notable are
    10 Microsoft OS'es) you might want to set your clock to localtime so that
     7setup is setting the hardware clock to GMT and having the time converted
     8to localtime using the /etc/localtime symbolic link. But if an
     9OS is run that doesn't understand a clock set to GMT (most notable are
     10Microsoft OS'es) a user might want to set the clock to localtime so that
    1111the time is properly displayed on those OS'es. This script will reset
    1212the kernel time to the hardware clock without converting the time using
    … …  
    1515
    1616<para>
    17 If you want to use this script on your system even if you have your
    18 hardware clock set to GMT, then change the UTC variable below to the
     17If a user wants to use this script on the system even if the
     18hardware clock is set to GMT, then the UTC variable below has to be changed
     19 to the
    1920value of <emphasis>1</emphasis>.
    2021</para>
    … …  
    8384
    8485<para>
    85 If your hardware clock (also known as BIOS or CMOS clock) is not set to
    86 GMT time, than set the UTC variable in the /etc/sysconfig/clock file to
     86If the hardware clock (also known as BIOS or CMOS clock) is not set to
     87GMT time, then the UTC variable in the /etc/sysconfig/clock file needs to be
     88set to
    8789the value <emphasis>0</emphasis> (zero).
    8890</para>

  • chapter07/symperm.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Give these files the proper permissions and create the necessary symlinks
    6 by running the following commands. If you did not create the loadkeys
    7 and setclock scripts, make sure you don't type them in the commands
     5These files get the proper permissions and the necessary symlinks are created
     6by running the following commands. If a user did not create the loadkeys
     7and setclock scripts, he has to make sure not to type them in the commands
    88below.
    99</para>

  • chapter07/sysklogd.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/sysklogd</filename> containing
     5A new file <filename>/etc/init.d/sysklogd</filename> is created containing
    66the following:
    77</para>

  • chapter07/template.xml

    r137bd50 r53b5ccf  
    33
    44<para>
    5 Create a new file <filename>/etc/init.d/template</filename> containing
     5A new file <filename>/etc/init.d/template</filename> is created containing
    66the following:
    77</para>

  • chapter07/usage.xml

    r137bd50 r53b5ccf  
    55Linux uses a special booting facility named SysVinit. It's based on a
    66concept of <emphasis>runlevels</emphasis>. It can be widely different
    7 from one system to another, so  don't assume that because things
     7from one system to another, so it can not be assumed that because things
    88worked in &lt;insert distro name&gt; they should work like that in LFS
    99too. LFS has it's own way of doing things, but it respects generally
    … …  
    1515using a runlevels scheme. There are 7 (from 0 to 6) runlevels
    1616(actually, there are more runlevels but they are for special cases and
    17 generally not used. Read the init man page for those details), and each
    18 one of those corresponds to the things you want your computer to do when
     17generally not used. The init man page describes those details), and each
     18one of those corresponds to the things the computer is supposed to do when
    1919it starts up. The default runlevel is 3. Here are the descriptions of the
    2020different runlevels as they are often implemented:
    … …  
    3434The command used to change runlevels is <userinput>init
    3535&lt;runlevel&gt;</userinput> where &lt;runlevel&gt; is
    36 the target runlevel. For example, to reboot the computer, you'd issue
     36the target runlevel. For example, to reboot the computer, a user would issue
    3737the init 6 command. The reboot command is just an alias, as is the halt
    3838command an alias to init 0.
    … …  
    4747<para>
    4848There are a number of directories under /etc that look like like rc?.d
    49 where ? is the number of the runlevel and rcS.d. Take a look at one of
    50 them (after you finish this chapter that is, right now there's nothing
     49where ? is the number of the runlevel and rcS.d. A user might take a look
     50at one of
     51them (after this chapter is finished, right now there's nothing
    5152there yet). There are a number of symbolic links. Some begin with an K,
    5253the others begin with an S, and all of them have three numbers following
    … …  
    8889<listitem><para>
    8990<emphasis>reload</emphasis>: The configuration of the service is updated.
    90 Use this after you have modified the configuration file of a service, when
    91 you don't need/want to restart the service.
     91This is used after the configuration file of a service was modified, when
     92the service doesn't need to be restarted.
    9293</para></listitem>
    9394
    9495<listitem><para>
    95 <emphasis>status</emphasis>: Tells you if the service is running and with
     96<emphasis>status</emphasis>: Tells if the service is running and with
    9697which PID's.
    9798</para></listitem>
    … …  
    100101
    101102<para>
    102 Feel free to modify the way the boot process works (after all it's your
    103 LFS system, not ours). The files here are just an example of how you
    104 can do it in a nice way (well what we consider nice anyway. You may
    105 hate it).
     103Feel free to modify the way the boot process works (after all it's the users
     104LFS system, not ours). The files here are just an example of how it can be
     105done
     106in a nice way (well what we consider nice anyway. A user may hate it).
    106107</para>
    107108

  • chapter08/introduction.xml

    r137bd50 r53b5ccf  
    44<para>
    55This chapter will make LFS bootable. This chapter deals with building a
    6 new kernel for our new LFS system and adding the proper entries to LILO
    7 so that you can select to boot the LFS system at the LILO: prompt.
     6new kernel for the new LFS system and adding the proper entries to LILO
     7so that the LFS system can be selected for booting at the LILO: prompt.
    88</para>
    99

  • chapter08/kernel.xml

    r137bd50 r53b5ccf  
    1010<para>
    1111Building the kernel involves a few steps: configuring it and compiling
    12 it. There are a few ways to configure the kernel. If you don't like the
    13 way this book does it, read the <filename>README</filename> file and find out
    14 what your other options are. Run the following commands to build the
     12it. There are a few ways to configure the kernel. If a user doesn't like the
     13way this book does it, he should read the <filename>README</filename>
     14file and find out
     15what the other options are. The following commands are run to build the
    1516kernel:
    1617</para>

  • chapter08/lilo.xml

    r137bd50 r53b5ccf  
    44<para>
    55In order to being able to boot from this partition, we need to update our
    6 /etc/lilo.conf file. Add the following lines to lilo.conf by running:
     6/etc/lilo.conf file. The following lines get added to lilo.conf by running:
    77</para>
    88
    … …  
    1919
    2020<para>
    21 &lt;partition&gt; must be replaced by your partition's designation (which
     21&lt;partition&gt; must be replaced by the partition's designation (which
    2222would be /dev/hda5 in my case).
    2323</para>
    2424
    2525<para>
    26 Now update the boot loader by running:
     26Now the boot loader gets updated by running:
    2727</para>
    2828

  • chapter08/reboot.xml

    r137bd50 r53b5ccf  
    44<para>
    55Now that all software has been installed, bootscripts have been created,
    6 it's time for you to reboot your computer. Shutdown your system with
    7 shutdown -r now and reboot into LFS. After the reboot you will have a normal
    8 login prompt like you have on your normal Linux system (unless you use XDM or
    9 some sort of other Display Manger (like KDM - KDE's version of XDM).
     6it's time to reboot the computer. The system is shutdown with
     7shutdown -r now and rebooted into LFS. After the reboot a normal
     8login prompt like on the normal Linux system comes up (unless XDM or
     9some sort of other Display Manger is used (like KDM - KDE's version of XDM)).
    1010</para>
    1111
    1212<para>
    13 One thing remains to be done and that's setting up networking. After you
    14 rebooted and finished the next chapter of this book your LFS system is
    15 ready for use and you can do with it whatever you want.
     13One thing remains to be done and that's setting up networking. After having
     14rebooted and finished the next chapter of this book the LFS system is
     15ready for use and can be used to do with it whatever is wanted.
    1616</para>
    1717
Note: See TracChangeset for help on using the changeset viewer.