Context Navigation

-              r2df36e4
+              r8604d92f
 <para><parameter>bs=1k count=4096</parameter>: These parameters tell
 <filename>dd</filename> to read and write in "chunks" of 1024 bytes and
+<command>dd</command> to read and write in "chunks" of 1024 bytes and
 process 4096 "chunks".</para>
 …
 the version of <command>mount</command> (older ones don't have the
 <userinput>-o loop</userinput> option) or if <filename>/etc/mtab</filename>
 is symlinked to <filename>/proc</filename> (which causes mount to be
+is symlinked to <filename class="directory">/proc</filename> (which causes mount to be
 unable to properly "unbind" a loop device, due to "lost" information).
 An alternate set of commands is provided, after these three commands,
 …
 <option>-o loop</option> option <emphasis>and</emphasis> your
 <filename>/etc/mtab</filename> is a real file, rather than a symlink to
 <filename>/proc</filename>, the three above commands can be replaced
+<filename class="directory">/proc</filename>, the three above commands can be replaced
 by these next two commands.</para>
 …
 command tells <command>mount</command> to bind the named file to a
 loopback device it automatically selects (the first available) and mount
 the device on <filename>/mnt/loop1</filename>.</para>
+the device on <filename class="directory">/mnt/loop1</filename>.</para>
 <para><emphasis>Add components to the file system</emphasis></para>
 …
 <para><emphasis>A cautionary note:</emphasis> if you are not running in a
 <command>chroot</command> environment, be sure that you do not accidently
 omit the <filename>/mnt/loop1</filename> reference in the commands. If
+omit the <filename class="directory">/mnt/loop1</filename> reference in the commands. If
 you do so, you might replace the equivalent components on your host with
 the components that are installed by these procedures.  Even if you are
 …
 &nbsp;&nbsp;/mnt/loop1/dev</command></userinput></screen>
 <para><emphasis>What is needed in the <filename>/etc</filename>
+<para><emphasis>What is needed in the <filename class="directory">/etc</filename>
 directory</emphasis></para>
 …
 diskette to carry these files.</para>
 <para>Some might like to copy their <filename>/etc/rc*</filename>
+<para>Some might like to copy their <filename class="directory">/etc/rc*</filename>
 directory into the ramdisk image, but this may have no value, other
 than archival use, in a worst-case recovery scenario.  If you want
 …
 <command>noauto</command> in the options field so they don't cause an
 attempt to mount a potentially corrupt partition.  Copy it to
 <filename>/tmp</filename>, edit it as desired and then:</para>
+<filename class="directory">/tmp</filename>, edit it as desired and then:</para>
 <screen><userinput><command>cp -a /tmp/fstab /mnt/loop1/etc</command></userinput></screen>
 …
 control to <command>linuxrc</command> (<application><ulink
 url="http://www.busybox.net/downloads/busybox-0.60.4.tar.bz2">busybox
 </ulink></application>).  It wants to run an <filename>/etc/init.d/rcS</filename>
+</ulink></application>).  It wants to run an <filename class="directory">/etc/init.d/rcS</filename>
 script to do any initial setup.</para>
 <para>If you use devfsd, you will need to set up the
 <filename>rcS</filename> script to handle the devfsd startup.  Put the
 following commands in <filename>/mnt/loop1/etc/init.d/rcS</filename>.
+following commands in <filename class="directory">/mnt/loop1/etc/init.d/rcS</filename>.
 You may also want to add some of the processes shown in the non-devfs
 version that follows.</para>
 …
 /sbin/devfsd /dev</userinput></screen>
+<para>If you don't use devfsd, but created a static <filename>/dev</filename>
+<para>If you don't use devfsd, but created a static <filename
+class="directory">/dev</filename>
 directory using <command>MAKEDEV</command>, or any similar process, the
 <filename>rcS</filename> script will do slightly different things.
 …
 files, thus saving space on the diskette.</para>
 <para>The script made next will mount <filename>/proc</filename>, turn
+<para>The script made next will mount <filename class="directory">/proc</filename>, turn
 on swap (no harm is done if it fails), make the
 <filename>/etc/passwd</filename> and <filename>/etc/group</filename>
 …
 <para>To make a single-floppy rescue, using devfs, use the following
 commands. If you use the static <filename>/dev</filename> setup, use
+commands. If you use the static <filename class="directory">/dev</filename> setup, use
 <filename>/dev/fd0</filename> instead of the /dev/floppy/0.</para>
 …
 the kernel will use when it boots. Because it loads an initrd, it will
 automatically set that as the root device, initially. So, the
 <userinput>0,0</userinput> gives it "no value", telling the kernel to not
+<option>0,0</option> gives it "no value", telling the kernel to not
 mount any other device. Some folks give <filename>/dev/fd0</filename> or
 something similar. But this has effect <emphasis>only</emphasis> when
 …
 following commands, with the proper numbers inserted. Notice that the
 <command>seek</command> parameter's number must be the size, in blocks,
 of your kernel image. If you use the static <filename>/dev</filename>
+of your kernel image. If you use the static <filename class="directory">/dev</filename>
 setup, use <filename>/dev/fd0</filename> in the commands below, instead
 of <filename>/dev/floppy/0</filename>.</para>

postlfs/config/profile.xml

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

postlfs/config/skel.xml

-              r2df36e4
+              r8604d92f
 <para>Together, the <command>/usr/sbin/useradd</command> command and
 <filename>/etc/skel</filename> directory (both are easy to setup and use)
+<filename class="directory">/etc/skel</filename> directory (both are easy to setup and use)
 provide a way to assure new users are added on your <acronym>LFS</acronym>
 system with the same beginning settings for things like <envar>PATH</envar>,
 …
 makes it easier to assure this initial state for each new user.</para>
 <para>The <filename>/etc/skel</filename> directory holds copies of various
+<para>The <filename class="directory">/etc/skel</filename> directory holds copies of various
 initialization and other files that may be copied to the new user's home
 directory when the <command>/usr/sbin/useradd</command> program adds the new
 …
 <para>For more information see <command>man useradd</command>.</para>
 <para><emphasis><filename>/etc/skel</filename></emphasis></para>
+<para><emphasis><filename class="directory">/etc/skel</filename></emphasis></para>
 <para>To get started create an <filename>/etc/skel</filename> directory
+<para>To get started create an <filename class="directory">/etc/skel</filename> directory
 and make sure it is writable only by the system administrator, usually
 root. Creating the directory as root is the best way to go.</para>
 <para>The mode of any files from this part of the book that you put in
 <filename>/etc/skel</filename> should be writable only by the owner.
+<filename class="directory">/etc/skel</filename> should be writable only by the owner.
 Also, since there is no telling what kind of sensitive information a
 user may eventually place in their copy of these files, you should
 make them unreadable by "group" and "other".</para>
 <para>You can also put other files in <filename>/etc/skel</filename> and
+<para>You can also put other files in <filename class="directory">/etc/skel</filename> and
 different permissions may be needed for them.</para>
 …
 <para>The files from those sections that you might want to place in
 <filename>/etc/skel</filename> include
+<filename class="directory">/etc/skel</filename> include
 <filename>.inputrc</filename>, <filename>.bash_profile</filename>,
 <filename>.bashrc</filename>, <filename>.bash_logout</filename>,
 …
 <para>You will run a slightly modified set of commands for files which
 are placed in <filename>/etc/skel</filename>. Each section will remind
+are placed in <filename class="directory">/etc/skel</filename>. Each section will remind
 you of this. In brief, the book's commands have been written for files
 <emphasis>not</emphasis> added to <filename>/etc/skel</filename> and
+<emphasis>not</emphasis> added to <filename class="directory">/etc/skel</filename> and
 just send the results to the user's home directory. If the file is going
 to be in <filename>/etc/skel</filename>, change the book's command(s) to
+to be in <filename class="directory">/etc/skel</filename>, change the book's command(s) to
 send output there instead and then just copy the file from
 <filename>/etc/skel</filename> to the appropriate directories, like
 <filename>/etc</filename>, <filename>~</filename> or the home directoriy
+<filename class="directory">/etc/skel</filename> to the appropriate directories, like
+<filename class="directory">/etc</filename>, <filename class="directory">~</filename> or the home directoriy
 of any other user already in the system.</para>
 …
 the <option>-m</option> parameter, which tells
 <command>useradd</command> to create the user's home directory and
 copy files from <filename>/etc/skel</filename> (can be overridden) to
+copy files from <filename class="directory">/etc/skel</filename> (can be overridden) to
 the new user's home directory.  For example:</para>

postlfs/editors/vim/vim-exp.xml

r2df36e4	r8604d92f
2	2	<title>Command explanations</title>
3	3
4		<para><parameter>--with-features=huge</parameter>: Enables all the additional
	4	<para><parameter>--with-features=huge</parameter>: This switch enables all the additional
5	5	features available in <application>Vim</application>.</para>
6	6

postlfs/filesystems/reiser/reiser-exp.xml

-              r2df36e4
+              r8604d92f
 <para><parameter>--prefix=/usr</parameter>: This ensures that
 the manual pages are installed in the correct location while still
 installing the programs in <filename>/sbin</filename> as they should
+installing the programs in <filename class="directory">/sbin</filename> as they should
 be.</para>
 <para><parameter>--sbindir=/sbin</parameter>: This ensures that the
 <application>ReiserFS</application>
 utilities are installed in <filename>/sbin</filename> as they should be.</para>
+utilities are installed in <filename class="directory">/sbin</filename> as they should be.</para>
 </sect2>

postlfs/security/gnupg/gnupg-exp.xml

-              r2df36e4
+              r8604d92f
 <title>Command explanations</title>
+<para><parameter>--libexecdir=/usr/sbin</parameter>: This command
+creates a <filename>gnupg</filename> directory in <filename>/usr/sbin</filename> instead of
+<filename>/usr/libexec</filename>.</para>
+<para><parameter>--libexecdir=/usr/lib</parameter>: This command
+creates a <filename class="directory">gnupg</filename> directory in
+<filename class="directory">/usr/sbin</filename> instead of
+<filename class="directory">/usr/libexec</filename>.</para>
 </sect2>

postlfs/security/gnupg/gnupg-inst.xml

r2df36e4	r8604d92f
4	4	<para>Install <application>GnuPG</application> by running the following commands:</para>
5	5
6		<screen><userinput><command>./configure --prefix=/usr --libexecdir=/usr/~~sbin~~ &&
	6	<screen><userinput><command>./configure --prefix=/usr --libexecdir=/usr/lib &&
7	7	make &&
8	8	make install &&

postlfs/security/pam/linux_pam-desc.xml

-              r2df36e4
+              r8604d92f
 <para>The <application>Linux-<acronym>PAM</acronym></application> package
+contains <command>unix-chkpwd</command> and <filename>libpam</filename>
+contains <command>unix-chkpwd</command> and <filename
+class="libraryfile">libpam</filename>
 libraries.</para>
 …
 <sect3><title>libpam libraries</title>
 <para><filename>libpam</filename> libraries provide the interfaces between
+<para><filename class="libraryfile">libpam</filename> libraries provide the interfaces between
 applications and the modules included with <acronym>PAM</acronym>.</para></sect3>

postlfs/security/shadow/shadow-config.xml

r2df36e4	r8604d92f
14	14
15	15	<para>Add the following <application><acronym>PAM</acronym></application>
16		configuration files to <filename>/etc/pam.d</filename> (or add them to
	16	configuration files to <filename class="directory">/etc/pam.d</filename> (or add them to
17	17	<filename>/etc/pam.conf</filename> with the additional field for the program).
18	18	</para>

postlfs/security/tripwire/tripwire-config.xml

-              r2df36e4
+              r8604d92f
 <sect3><title>Config files</title>
 <para><filename>/etc/tripwire</filename></para>
+<para><filename class="directory">/etc/tripwire</filename></para>
 </sect3>
 …
 <para><application>Tripwire</application> uses a policy file to determine which
 files integrity are checked. The default policy file (<filename>twpol.txt
 </filename> found in <filename>/etc/tripwire/</filename>) is for a default
+</filename> found in <filename class="directory">/etc/tripwire/</filename>) is for a default
 installation of Redhat 7.0 and is woefully outdated.</para>
 …
 Custom policy file for SuSE 7.2 system</screen>
 <para>Download the custom policy file you'd like to try, copy it into <filename>
+/etc/tripwire/</filename>, and use it instead of <filename>twpol.txt
 </filename>. It is, however, recommended that you make your own policy file.
+<para>Download the custom policy file you'd like to try, copy it into
+<filename class="directory">/etc/tripwire/</filename>, and use it instead of
+<filename>twpol.txt</filename>. It is, however, recommended that you make your own policy file.
 Get ideas from the examples above and read <filename>
 /usr/share/doc/tripwire/policyguide.txt</filename>. <filename>twpol.txt
 …
 changes for uninstallation of software.</para>
 <para>After your policy file has been transferred to <filename>/etc/tripwire/
 </filename> you may begin the configuration steps:</para>
+<para>After your policy file has been transferred to <filename
+class="directory">/etc/tripwire/</filename> you may begin the configuration steps:</para>
 <screen><userinput><command>twadmin -m P /etc/tripwire/twpol.txt &amp;&amp;
 tripwire -m i</command></userinput></screen>
 <para>During configuration tripwire will create two (2) keys: a site key and
+<para>During configuration <application>Tripwire</application> will create two (2) keys: a site key and
  a local key which will be stored in <filename class="directory">/etc/tripwire/
 </filename>.</para>
 …
 <para>Please note that after you run an integrity check, you must check
+the report or email and then modify the tripwire database of the files
+on your system so that tripwire will not continually notify you that
+the report or email and then modify the
+<application>Tripwire</application> database of the files
+on your system so that <application>Tripwire</application> will not continually notify you that
 files you intentionally changed are a security violation. To do this you
 must first <command>ls /var/lib/tripwire/report/</command> and note
 the name of the newest file which starts with <filename>linux-</filename> and
 ends in <filename>.twr</filename>. This encrypted file was created during the
+last report creation and is needed to update the tripwire database of your
+last report creation and is needed to update the
+<application>Tripwire</application> database of your
 system. Then, type in the following command making the appropriate
 substitutions for '?':</para>

Note: See TracChangeset for help on using the changeset viewer.

Context Navigation

Changeset 8604d92f for postlfs

Legend:

Download in other formats: