1 files changed, 171 insertions, 0 deletions
diff --git a/sag-0.6.1-www/sag-0.6.1.html/x1697.html b/sag-0.6.1-www/sag-0.6.1.html/x1697.html
new file mode 100644
index 0000000..59049a7
--- /dev/null
+++ b/sag-0.6.1-www/sag-0.6.1.html/x1697.html
@@ -0,0 +1,171 @@
+<!DOCTYPE HTML PUBLIC "-//Norman Walsh//DTD DocBook HTML 1.0//EN">
+<HTML
+><HEAD
+><TITLE
+>Emergency boot floppies</TITLE
+><META
+NAME="GENERATOR"
+CONTENT="Modular DocBook HTML Stylesheet"><LINK
+REL="HOME"
+TITLE="The Linux System Administrators' Guide"
+HREF="book1.html"><LINK
+REL="UP"
+TITLE="Boots And Shutdowns"
+HREF="c1582.html"><LINK
+REL="PREVIOUS"
+TITLE="Single user mode"
+HREF="x1693.html"><LINK
+REL="NEXT"
+TITLE="init"
+HREF="c1705.html"></HEAD
+><BODY
+BGCOLOR="#FFFFFF"
+TEXT="#000000"
+><DIV
+CLASS="NAVHEADER"
+><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TH
+COLSPAN="3"
+ALIGN="center"
+>The Linux System Administrators' Guide</TH
+></TR
+><TR
+><TD
+WIDTH="10%"
+ALIGN="left"
+VALIGN="bottom"
+><A
+HREF="x1693.html"
+>Prev</A
+></TD
+><TD
+WIDTH="80%"
+ALIGN="center"
+VALIGN="bottom"
+>Chapter 6. Boots And Shutdowns</TD
+><TD
+WIDTH="10%"
+ALIGN="right"
+VALIGN="bottom"
+><A
+HREF="c1705.html"
+>Next</A
+></TD
+></TR
+></TABLE
+><HR
+ALIGN="LEFT"
+WIDTH="100%"></DIV
+><DIV
+CLASS="SECT1"
+><H1
+CLASS="SECT1"
+><A
+NAME="AEN1697"
+>Emergency boot floppies</A
+></H1
+><P
+>It is not always possible to boot a computer from the hard disk.
+	For example, if you make a mistake in configuring LILO, you might
+	make your system unbootable.  For these situations, you need an
+	alternative way of booting that will always work (as long as the
+	hardware works).  For typical PC's, this means booting from the
+	floppy drive.</P
+><P
+>Most Linux distributions allow one to create an
+	<I
+CLASS="GLOSSTERM"
+>emergency boot floppy</I
+> during installation.
+	It is a good idea to do this.  However, some such boot disks
+	contain only the kernel, and assume you will be using the programs
+	on the distribution's installation disks to fix whatever problem
+	you have.  Sometimes those programs aren't enough; for example,
+	you might have to restore some files from backups made with
+	software not on the installation disks.</P
+><P
+>Thus, it might be necessary to create a custom root floppy
+	as well.  The <I
+CLASS="CITETITLE"
+>Bootdisk HOWTO</I
+> by Graham
+	Chapman (XXX citation) contains instructions for doing this.
+	You must, of course, remember to keep your emergency boot and
+	root floppies up to date.</P
+><P
+>You can't use the floppy drive you use to mount the root
+	floppy for anything else.  This can be inconvenient if you only
+	have one floppy drive.	However, if you have enough memory, you
+	can configure your boot floppy to load the root disk to a ramdisk
+	(the boot floppy's kernel needs to be specially configured for
+	this).	Once the root floppy has been loaded into the ramdisk,
+	the floppy drive is free to mount other disks.	</P
+></DIV
+><DIV
+CLASS="NAVFOOTER"
+><HR
+ALIGN="LEFT"
+WIDTH="100%"><TABLE
+WIDTH="100%"
+BORDER="0"
+CELLPADDING="0"
+CELLSPACING="0"
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+><A
+HREF="x1693.html"
+>Prev</A
+></TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="book1.html"
+>Home</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><A
+HREF="c1705.html"
+>Next</A
+></TD
+></TR
+><TR
+><TD
+WIDTH="33%"
+ALIGN="left"
+VALIGN="top"
+>Single user mode</TD
+><TD
+WIDTH="34%"
+ALIGN="center"
+VALIGN="top"
+><A
+HREF="c1582.html"
+>Up</A
+></TD
+><TD
+WIDTH="33%"
+ALIGN="right"
+VALIGN="top"
+><B
+CLASS="COMMAND"
+>init</B
+></TD
+></TR
+></TABLE
+></DIV
+></BODY
+></HTML
+>
+\ No newline at end of file