Changeset 8604d92f for postlfs/config


Ignore:
Timestamp:
10/01/2003 12:45:19 AM (21 years ago)
Author:
Larry Lawrence <larry@…>
Branches:
10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
Children:
bb363985
Parents:
2df36e4
Message:

Chapter 13, again

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1251 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:
postlfs/config
Files:
3 edited

Legend:

Unmodified
Added
Removed

  • postlfs/config/bootdisk.xml

    r2df36e4 r8604d92f  
    149149
    150150<para><parameter>bs=1k count=4096</parameter>: These parameters tell
    151 <filename>dd</filename> to read and write in "chunks" of 1024 bytes and
     151<command>dd</command> to read and write in "chunks" of 1024 bytes and
    152152process 4096 "chunks".</para>
    153153
    … …  
    157157the version of <command>mount</command> (older ones don't have the
    158158<userinput>-o loop</userinput> option) or if <filename>/etc/mtab</filename>
    159 is symlinked to <filename>/proc</filename> (which causes mount to be
     159is symlinked to <filename class="directory">/proc</filename> (which causes mount to be
    160160unable to properly "unbind" a loop device, due to "lost" information).
    161161An alternate set of commands is provided, after these three commands,
    … …  
    186186<option>-o loop</option> option <emphasis>and</emphasis> your
    187187<filename>/etc/mtab</filename> is a real file, rather than a symlink to
    188 <filename>/proc</filename>, the three above commands can be replaced
     188<filename class="directory">/proc</filename>, the three above commands can be replaced
    189189by these next two commands.</para>
    190190
    … …  
    204204command tells <command>mount</command> to bind the named file to a
    205205loopback device it automatically selects (the first available) and mount
    206 the device on <filename>/mnt/loop1</filename>.</para>
     206the device on <filename class="directory">/mnt/loop1</filename>.</para>
    207207
    208208<para><emphasis>Add components to the file system</emphasis></para>
    … …  
    210210<para><emphasis>A cautionary note:</emphasis> if you are not running in a
    211211<command>chroot</command> environment, be sure that you do not accidently
    212 omit the <filename>/mnt/loop1</filename> reference in the commands. If
     212omit the <filename class="directory">/mnt/loop1</filename> reference in the commands. If
    213213you do so, you might replace the equivalent components on your host with
    214214the components that are installed by these procedures.  Even if you are
    … …  
    258258&nbsp;&nbsp;/mnt/loop1/dev</command></userinput></screen>
    259259
    260 <para><emphasis>What is needed in the <filename>/etc</filename>
     260<para><emphasis>What is needed in the <filename class="directory">/etc</filename>
    261261directory</emphasis></para>
    262262
    … …  
    276276diskette to carry these files.</para>
    277277
    278 <para>Some might like to copy their <filename>/etc/rc*</filename>
     278<para>Some might like to copy their <filename class="directory">/etc/rc*</filename>
    279279directory into the ramdisk image, but this may have no value, other
    280280than archival use, in a worst-case recovery scenario.  If you want
    … …  
    298298<command>noauto</command> in the options field so they don't cause an
    299299attempt to mount a potentially corrupt partition.  Copy it to
    300 <filename>/tmp</filename>, edit it as desired and then:</para>
     300<filename class="directory">/tmp</filename>, edit it as desired and then:</para>
    301301
    302302<screen><userinput><command>cp -a /tmp/fstab /mnt/loop1/etc</command></userinput></screen>
    … …  
    309309control to <command>linuxrc</command> (<application><ulink
    310310url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox
    311 </ulink></application>).  It wants to run an <filename>/etc/init.d/rcS</filename>
     311</ulink></application>).  It wants to run an <filename class="directory">/etc/init.d/rcS</filename>
    312312script to do any initial setup.</para>
    313313
    314314<para>If you use devfsd, you will need to set up the
    315315<filename>rcS</filename> script to handle the devfsd startup.  Put the
    316 following commands in <filename>/mnt/loop1/etc/init.d/rcS</filename>.
     316following commands in <filename class="directory">/mnt/loop1/etc/init.d/rcS</filename>.
    317317You may also want to add some of the processes shown in the non-devfs
    318318version that follows.</para>
    … …  
    322322/sbin/devfsd /dev</userinput></screen>
    323323
    324 <para>If you don't use devfsd, but created a static <filename>/dev</filename>
     324<para>If you don't use devfsd, but created a static <filename
     325class="directory">/dev</filename>
    325326directory using <command>MAKEDEV</command>, or any similar process, the
    326327<filename>rcS</filename> script will do slightly different things.
    … …  
    329330files, thus saving space on the diskette.</para>
    330331
    331 <para>The script made next will mount <filename>/proc</filename>, turn
     332<para>The script made next will mount <filename class="directory">/proc</filename>, turn
    332333on swap (no harm is done if it fails), make the
    333334<filename>/etc/passwd</filename> and <filename>/etc/group</filename>
    … …  
    533534
    534535<para>To make a single-floppy rescue, using devfs, use the following
    535 commands. If you use the static <filename>/dev</filename> setup, use
     536commands. If you use the static <filename class="directory">/dev</filename> setup, use
    536537<filename>/dev/fd0</filename> instead of the /dev/floppy/0.</para>
    537538
    … …  
    545546the kernel will use when it boots. Because it loads an initrd, it will
    546547automatically set that as the root device, initially. So, the
    547 <userinput>0,0</userinput> gives it "no value", telling the kernel to not
     548<option>0,0</option> gives it "no value", telling the kernel to not
    548549mount any other device. Some folks give <filename>/dev/fd0</filename> or
    549550something similar. But this has effect <emphasis>only</emphasis> when
    … …  
    588589following commands, with the proper numbers inserted. Notice that the
    589590<command>seek</command> parameter's number must be the size, in blocks,
    590 of your kernel image. If you use the static <filename>/dev</filename>
     591of your kernel image. If you use the static <filename class="directory">/dev</filename>
    591592setup, use <filename>/dev/fd0</filename> in the commands below, instead
    592593of <filename>/dev/floppy/0</filename>.</para>

  • postlfs/config/profile.xml

    r2df36e4 r8604d92f  
    77help create an environment to run in.  Each file has a specific use and
    88may affect login and interactive environments differently.  The files in
    9 the <filename>/etc</filename> directory generally provide global
     9the <filename class="directory">/etc</filename> directory generally provide global
    1010settings. If an equivalent file exists in your home directory it may
    1111override the global settings.
    … …  
    193193<para>Here is a base <filename>~/.bashrc</filename>.  Comments in the
    194194file should explain everything you need.  The comments and
    195 instructions for using <filename>/etc/skel</filename> for
     195instructions for using <filename class="directory">/etc/skel</filename> for
    196196<filename>.bash_profile</filename> above also apply here. Only the
    197197target file names are different.</para>
    … …  
    234234<para>
    235235If you want to use the <filename>dircolors</filename> capability
    236 then run the following command. The <filename>/etc/skel</filename> setup
     236then run the following command. The <filename class="directory">/etc/skel</filename> setup
    237237steps seen above also can be used here to provide a
    238238<filename>.dircolors</filename> file when a new user is set up. As

  • postlfs/config/skel.xml

    r2df36e4 r8604d92f  
    44
    55<para>Together, the <command>/usr/sbin/useradd</command> command and
    6 <filename>/etc/skel</filename> directory (both are easy to setup and use)
     6<filename class="directory">/etc/skel</filename> directory (both are easy to setup and use)
    77provide a way to assure new users are added on your <acronym>LFS</acronym>
    88system with the same beginning settings for things like <envar>PATH</envar>,
    … …  
    1010makes it easier to assure this initial state for each new user.</para>
    1111
    12 <para>The <filename>/etc/skel</filename> directory holds copies of various
     12<para>The <filename class="directory">/etc/skel</filename> directory holds copies of various
    1313initialization and other files that may be copied to the new user's home
    1414directory when the <command>/usr/sbin/useradd</command> program adds the new
    … …  
    5151<para>For more information see <command>man useradd</command>.</para>
    5252
    53 <para><emphasis><filename>/etc/skel</filename></emphasis></para>
     53<para><emphasis><filename class="directory">/etc/skel</filename></emphasis></para>
    5454
    55 <para>To get started create an <filename>/etc/skel</filename> directory
     55<para>To get started create an <filename class="directory">/etc/skel</filename> directory
    5656and make sure it is writable only by the system administrator, usually
    5757root. Creating the directory as root is the best way to go.</para>
    5858
    5959<para>The mode of any files from this part of the book that you put in
    60 <filename>/etc/skel</filename> should be writable only by the owner.
     60<filename class="directory">/etc/skel</filename> should be writable only by the owner.
    6161Also, since there is no telling what kind of sensitive information a
    6262user may eventually place in their copy of these files, you should
    6363make them unreadable by "group" and "other".</para>
    6464
    65 <para>You can also put other files in <filename>/etc/skel</filename> and
     65<para>You can also put other files in <filename class="directory">/etc/skel</filename> and
    6666different permissions may be needed for them.</para>
    6767
    … …  
    7474
    7575<para>The files from those sections that you might want to place in
    76 <filename>/etc/skel</filename> include
     76<filename class="directory">/etc/skel</filename> include
    7777<filename>.inputrc</filename>, <filename>.bash_profile</filename>,
    7878<filename>.bashrc</filename>, <filename>.bash_logout</filename>,
    … …  
    8383
    8484<para>You will run a slightly modified set of commands for files which
    85 are placed in <filename>/etc/skel</filename>. Each section will remind
     85are placed in <filename class="directory">/etc/skel</filename>. Each section will remind
    8686you of this. In brief, the book's commands have been written for files
    87 <emphasis>not</emphasis> added to <filename>/etc/skel</filename> and
     87<emphasis>not</emphasis> added to <filename class="directory">/etc/skel</filename> and
    8888just send the results to the user's home directory. If the file is going
    89 to be in <filename>/etc/skel</filename>, change the book's command(s) to
     89to be in <filename class="directory">/etc/skel</filename>, change the book's command(s) to
    9090send output there instead and then just copy the file from
    91 <filename>/etc/skel</filename> to the appropriate directories, like
    92 <filename>/etc</filename>, <filename>~</filename> or the home directoriy
     91<filename class="directory">/etc/skel</filename> to the appropriate directories, like
     92<filename class="directory">/etc</filename>, <filename class="directory">~</filename> or the home directoriy
    9393of any other user already in the system.</para>
    9494
    … …  
    9898the <option>-m</option> parameter, which tells
    9999<command>useradd</command> to create the user's home directory and
    100 copy files from <filename>/etc/skel</filename> (can be overridden) to
     100copy files from <filename class="directory">/etc/skel</filename> (can be overridden) to
    101101the new user's home directory.  For example:</para>
    102102
Note: See TracChangeset for help on using the changeset viewer.