summaryrefslogtreecommitdiff
path: root/fi/post-install/reactivating-win.xml
blob: e34f01d127e74db9d5e24470afad4498adc6ee67 (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
64
65
66
67
68
69
70
71
72
<!-- retain these comments for translator revision tracking -->
<!-- original version: 28672 untranslated -->


 <sect1 arch="i386" id="reactivating-win">
 <title>Reactivating DOS and Windows</title>
<para>

After installing the base system and writing to the <emphasis>Master Boot
Record</emphasis>, you will be able to boot Linux, but probably nothing else.
This depends what you have chosen during the installation. This chapter
will describe how you can reactivate your old systems so that you can also
boot your DOS or Windows again.

</para><para>

<command>LILO</command> is a boot manager with which you can also boot
other operating systems than Linux, which complies to PC
conventions. The boot manager is configured via
<filename>/etc/lilo.conf</filename> file. Whenever you edited this
file you have to run <command>lilo</command> afterwards. The reason
for this is that the changes will take place only when you call the
program.

</para><para>

Important parts of the <filename>lilo.conf</filename> file are the
lines containing the <userinput>image</userinput> and
<userinput>other</userinput> keywords, as well as the lines following
those. They can be used to describe a system which can be booted by
<command>LILO</command>. Such a system can include a kernel
(<userinput>image</userinput>), a root partition, additional kernel
parameters, etc. as well as a configuration to boot another, non-Linux
(<userinput>other</userinput>) operating system.  These keywords can
also be used more than once.  The ordering of these systems within the
configuration file is important because it determines which system
will be booted automatically after, for instance, a timeout
(<userinput>delay</userinput>) presuming <command>LILO</command>
wasn't stopped by pressing the <keycap>shift</keycap> key.

</para><para>

After a fresh install of Debian, just the current system is configured
for booting with <command>LILO</command>. If you want to boot another
Linux kernel, you have to edit the configuration file
<filename>/etc/lilo.conf</filename> to add the following lines:

<informalexample><screen>
&additional-lilo-image;
</screen></informalexample>

For a basic setup just the first two lines are necessary. If you want
to know more about the other two options please have a look at the
<command>LILO</command> documentation. This can be found in
<filename>/usr/share/doc/lilo/</filename>. The file which should be
read is <filename>Manual.txt</filename>. To have a quicker start into
the world of booting a system you can also look at the
<command>LILO</command> man pages <filename>lilo.conf</filename> for
an overview of configuration keywords and <filename>lilo</filename>
for description of the installation of the new configuration into the
boot sector.

</para><para>

Notice that there are other boot loaders available in &debian;, such as
GRUB (in <classname>grub</classname> package),
CHOS (in <classname>chos</classname> package),
Extended-IPL (in <classname>extipl</classname> package),
loadlin (in <classname>loadlin</classname> package) etc.

</para>
 </sect1>