Context Navigation

r0a9287a	r64d97b7c
25	25
26	26	<para>
27		Now that we have a file mounted and useable, let's prepare it to be
	27	Now that we have a file mounted and usable, let's prepare it to be
28	28	filled with useful material. Since this is only a rescue floppy we'll
29	29	only need to set up the minimum directories.</para>

postlfs/config/config.xml

r0a9287a	r64d97b7c
15	15	subsystems but these are mostly simply pretty frontends to the process
16	16	of editing the file. The advantage of text-only configuration is that
17		you can edit parameters using your favourite text editor, whether that
	17	you can edit parameters using your favorite text editor, whether that
18	18	be vim, emacs or anything else.</para>
19	19

-              r0a9287a
+              r64d97b7c
 <sect1 id="postlfs-config-logon">
 <?dbhtml filename="logon.html" dir="postlfs"?>
 <title>/etc/issue (Customising your logon)</title>
+<title>/etc/issue (Customizing your logon)</title>
 <para>When you first boot up your new LFS system, the logon screen will
 …
 alone.</para>
 <para>The following escapes are recognised by agetty (the program which
+<para>The following escapes are recognized by agetty (the program which
 usually parses <filename>/etc/issue</filename>).  This information is from
 <userinput>man agetty</userinput> where you can find extra information

-              r0a9287a
+              r64d97b7c
 <para>The shell program <filename>/bin/bash</filename> (hereafter
 refered to as just "the shell") uses a collection of startup files to
+referred to as just "the shell") uses a collection of startup files to
 help create an environment to run in.  Each file has a specific use and
 may affect login and interactive environments differently.</para>
 …
 <filename>~/.bash_profile</filename>, and
 <filename>~/.bashrc</filename>.  The file
 <filename>~/.bash_logout</filename> is not used for an invokation of the
+<filename>~/.bash_logout</filename> is not used for an invocation of the
 shell.  It is read by the shell when a user logouts of the system.  The
 files <filename>/etc/profile</filename> and
 …
 # by James Robertson &lt;jameswrobertson@earthlink.net&gt;
 # Personal envrionment variables and startup programs.
+# Personal environment variables and startup programs.
 # Personal aliases and functions should go in ~/.bashrc.  System wide
 …
 # Personal environment variables and startup programs should go in
 # ~/.bash_profile.  System wide environment variables and starup
+# ~/.bash_profile.  System wide environment variables and startup
 # programs are in /etc/profile.  System wide aliases and functions are
 # in /etc/bashrc.

-              r0a9287a
+              r64d97b7c
 <listitem><para><userinput>set bs=2 :</userinput>
 This influences the behaviour of the backspace option.  It is fairly
+This influences the behavior of the backspace option.  It is fairly
 complex so see <userinput>:help 'bs'</userinput> for more
 details.</para></listitem>
 …
 <listitem><para><userinput>set background=dark :</userinput>
 This tells vim to use colours which look good on a dark
+This tells vim to use colors which look good on a dark
 background.</para></listitem>

r0a9287a	r64d97b7c
13	13	setup more complex and your box less secure: You induce the risks of
14	14	misconfigured services or running a service with an exploitable bug, both risks
15		that a firewall principially should be immune of. See the introduction to
	15	that a firewall principally should be immune of. See the introduction to
16	16	<xref linkend="postlfs-security-fw-masqRouter"/> for some more details.</para>
17	17

-              r0a9287a
+              r64d97b7c
 to aim no harm, you wouldn't need to do firewalling!
 In the real world however, daemons may be misconfigured,
 exploits against essential services are freely availiable, you
+exploits against essential services are freely available, you
 may wish to choose which services are accessible by certain machines,
 you may wish to limit which machines or applications are allowed
 …
 <sect3><title><xref linkend="postlfs-security-fw-masqRouter"/></title>
 <para>This is a box placed between the internet and an intranet.
 To minimize the risk of compromizing the firewall itself it
+To minimize the risk of compromising the firewall itself it
 should generally have only one role, that of protecting the intranet.
 Although not completely riskless, the tasks of doing the routing
 …
 of the packets it routes from clients with private IP-addresses onto
 the internet so that they seem to come from the firewall
 itself</para></footnote> are commonly considerd harmless.</para></sect3>
+itself</para></footnote> are commonly considered harmless.</para></sect3>
 <sect3><title><xref linkend="postlfs-security-fw-busybox"/></title>

r0a9287a	r64d97b7c
15	15
16	16	<sect3><title>iptables-save, ~-restore</title>
17		<para>to save and to restore your elabourated set of chains and rules.
	17	<para>to save and to restore your elaborated set of chains and rules.
18	18	Until iptables-1.2.5 they were declared experimental.</para>
19	19	</sect3>

r0a9287a	r64d97b7c
24	24	is checked (if it is available at <filename>/usr/src/linux</filename> to
25	25	see which features are available. Support will only be compiled into
26		iptables for the features recognised at compile-time. Applying a kernel
	26	iptables for the features recognized at compile-time. Applying a kernel
27	27	patch may result in errors, often because the hooks for the patches
28	28	have changed or because the runme script doesn't recognize that a patch

r0a9287a	r64d97b7c
1	1	<sect2>
2		<title>Reinstallation of shadow to utilize PAM</title>
	2	<title>Re-installation of shadow to utilize PAM</title>
3	3
4	4	<para>Download the patch for shadow from <ulink url="&hfile-root;"/></para>

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