| 1 |
kmuto |
11647 |
<!-- retain these comments for translator revision tracking -->
|
| 2 |
|
|
<!-- $Id: reactivating-win.xml 11568 2004-03-21 12:12:18Z waldi $ -->
|
| 3 |
|
|
|
| 4 |
|
|
|
| 5 |
|
|
<sect1 arch="i386" id="reactivating-win">
|
| 6 |
|
|
<title>Reactivating DOS and Windows</title>
|
| 7 |
|
|
<para>
|
| 8 |
|
|
|
| 9 |
|
|
After installing the base system and writing to the <emphasis>Master Boot
|
| 10 |
|
|
Record</emphasis>, you will be able boot Linux, but probably nothing else.
|
| 11 |
|
|
This depends what you have chosen during the installation. This chapter
|
| 12 |
|
|
will describe how you can reactivate your old systems so that you can also
|
| 13 |
|
|
boot your DOS or Windows again.
|
| 14 |
|
|
|
| 15 |
|
|
</para><para>
|
| 16 |
|
|
|
| 17 |
|
|
<command>LILO</command> is a boot manager with which you can also boot
|
| 18 |
|
|
other operating systems than Linux, which complies to PC
|
| 19 |
|
|
conventions. The boot manager is configured via
|
| 20 |
|
|
<filename>/etc/lilo.conf</filename> file. Whenever you edited this
|
| 21 |
|
|
file you have to run <command>lilo</command> afterwards. The reason
|
| 22 |
|
|
for this is that the changes will take place only when you call the
|
| 23 |
|
|
program.
|
| 24 |
|
|
|
| 25 |
|
|
</para><para>
|
| 26 |
|
|
|
| 27 |
|
|
Important parts of the <filename>lilo.conf</filename> file are the
|
| 28 |
|
|
lines containing the <userinput>image</userinput> and
|
| 29 |
|
|
<userinput>other</userinput> keywords, as well as the lines following
|
| 30 |
|
|
those. They can be used to describe a system which can be booted by
|
| 31 |
|
|
<command>LILO</command>. Such a system can include a kernel
|
| 32 |
|
|
(<userinput>image</userinput>), a root partition, additional kernel
|
| 33 |
|
|
parameters, etc. as well as a configuration to boot another, non-Linux
|
| 34 |
|
|
(<userinput>other</userinput>) operating system. These keywords can
|
| 35 |
|
|
also be used more than once. The ordering of these systems within the
|
| 36 |
|
|
configuration file is important because it determines which system
|
| 37 |
|
|
will be booted automatically after, for instance, a timeout
|
| 38 |
|
|
(<userinput>delay</userinput>) presuming <command>LILO</command>
|
| 39 |
|
|
wasn't stopped by pressing the <keycap>shift</keycap> key.
|
| 40 |
|
|
|
| 41 |
|
|
</para><para>
|
| 42 |
|
|
|
| 43 |
|
|
After a fresh install of Debian, just the current system is configured
|
| 44 |
|
|
for booting with <command>LILO</command>. If you want to boot another
|
| 45 |
|
|
Linux kernel, you have to edit the configuration file
|
| 46 |
|
|
<filename>/etc/lilo.conf</filename> to add the following lines:
|
| 47 |
|
|
|
| 48 |
|
|
<informalexample><screen>
|
| 49 |
|
|
|
| 50 |
|
|
&additional-lilo-image;
|
| 51 |
|
|
|
| 52 |
|
|
</screen></informalexample>
|
| 53 |
|
|
|
| 54 |
|
|
For a basic setup just the first two lines are necessary. If you want
|
| 55 |
|
|
to know more about the other two options please have a look at the
|
| 56 |
|
|
<command>LILO</command> documentation. This can be found in
|
| 57 |
|
|
<filename>/usr/share/doc/lilo/</filename>. The file which should be
|
| 58 |
|
|
read is <filename>Manual.txt</filename>. To have a quicker start into
|
| 59 |
|
|
the world of booting a system you can also look at the
|
| 60 |
|
|
<command>LILO</command> man pages <filename>lilo.conf</filename> for
|
| 61 |
|
|
an overview of configuration keywords and <filename>lilo</filename>
|
| 62 |
|
|
for description of the installation of the new configuration into the
|
| 63 |
|
|
boot sector.
|
| 64 |
|
|
|
| 65 |
|
|
</para><para>
|
| 66 |
|
|
|
| 67 |
|
|
Notice that there are other boot loaders available in &debian;, such as
|
| 68 |
|
|
GRUB (in <classname>grub</classname> package),
|
| 69 |
|
|
CHOS (in <classname>chos</classname> package),
|
| 70 |
|
|
Extended-IPL (in <classname>extipl</classname> package),
|
| 71 |
|
|
loadlin (in <classname>loadlin</classname> package) etc.
|
| 72 |
|
|
|
| 73 |
|
|
</para>
|
| 74 |
|
|
</sect1>
|
Parent Directory
| 
Revision Log