summaryrefslogtreecommitdiff
path: root/sag-0.6.1-www/Invisible/sag-0.6/node72.html
blob: b01cecdff55934e4aeab84fe38c71027d45433c6 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<!--Converted with LaTeX2HTML 96.1-h (September 30, 1996) by Nikos Drakos (nikos@cbl.leeds.ac.uk), CBLU, University of Leeds -->
<HTML>
<HEAD>
<TITLE>Emergency boot floppies</TITLE>
<META NAME="description" CONTENT="Emergency boot floppies">
<META NAME="keywords" CONTENT="sag">
<META NAME="resource-type" CONTENT="document">
<META NAME="distribution" CONTENT="global">
<LINK REL=STYLESHEET HREF="sag.css">
</HEAD>
<BODY LANG="EN" >
 <A NAME="tex2html1216" HREF="node73.html"><IMG WIDTH=37 HEIGHT=24 ALIGN=BOTTOM ALT="next" SRC="./next_motif.gif"></A> <A NAME="tex2html1214" HREF="node66.html"><IMG WIDTH=26 HEIGHT=24 ALIGN=BOTTOM ALT="up" SRC="./up_motif.gif"></A> <A NAME="tex2html1210" HREF="node71.html"><IMG WIDTH=63 HEIGHT=24 ALIGN=BOTTOM ALT="previous" SRC="./previous_motif.gif"></A> <A NAME="tex2html1218" HREF="node1.html"><IMG WIDTH=65 HEIGHT=24 ALIGN=BOTTOM ALT="contents" SRC="./contents_motif.gif"></A> <A NAME="tex2html1219" HREF="node114.html"><IMG WIDTH=43 HEIGHT=24 ALIGN=BOTTOM ALT="index" SRC="./index_motif.gif"></A> <BR>
<B> Next:</B> <A NAME="tex2html1217" HREF="node73.html">init</A>
<B>Up:</B> <A NAME="tex2html1215" HREF="node66.html">Boots And Shutdowns</A>
<B> Previous:</B> <A NAME="tex2html1211" HREF="node71.html">Single user mode</A>
<BR> <P>
<H1><A NAME="SECTION00760000000000000000">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.
<A NAME="2091">&#160;</A>
<A NAME="2092">&#160;</A>
<P>
	Most Linux distributions allow one to create an <b>emergency
	boot floppy</b> 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.
<A NAME="2094">&#160;</A>
<A NAME="2095">&#160;</A>
<A NAME="2096">&#160;</A>
<P>
	Thus, it might be necessary to create a custom root floppy as well.
	The <em>Bootdisk HOWTO</em> by Graham Chapman ([<A HREF="node113.html#bootdisk-howto">Cha</A>])
	contains instructions for doing this.
	You must, of course, remember to keep your emergency boot
	and root floppies up to date.
<A NAME="2099">&#160;</A>
<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.
<A NAME="2100">&#160;</A>
<P>
<BR> <HR>
<P><ADDRESS>
<I>Lars Wirzenius <BR>
Sat Nov 15 02:32:11 EET 1997</I>
</ADDRESS>
</BODY>
</HTML>