summaryrefslogtreecommitdiff
path: root/nl/using-d-i/modules/x86/lilo-installer.xml
blob: 89cc7f37e008a78564efa624ea43145ca42753fb (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
<!-- retain these comments for translator revision tracking -->
<!-- original version: 49849 untranslated -->

  <sect3 arch="x86">
  <title>Install the <command>LILO</command> Boot Loader
         on a Hard Disk</title>
<para>

The second &architecture; boot loader is called <quote>LILO</quote>.
It is an old complex program which offers lots of functionality,
including DOS, Windows, and OS/2 boot management.  Please carefully
read the instructions in the directory
<filename>/usr/share/doc/lilo/</filename> if you have special needs;
also see the <ulink url="&url-lilo-howto;">LILO mini-HOWTO</ulink>.

</para>
<note><para>

Currently the LILO installation will only create menu entries for other
operating systems if these can be <firstterm>chainloaded</firstterm>.
This means you may have to manually add a menu entry for operating
systems like GNU/Linux and GNU/Hurd after the installation.

</para></note>
<para>

&d-i; offers you three choices on where to install the
<command>LILO</command> boot loader:

<variablelist>
<varlistentry>
<term>Master Boot Record (MBR)</term><listitem><para>

This way the <command>LILO</command> will take complete control of the
boot process.

</para></listitem></varlistentry>
<varlistentry>
<term>new &debian; partition</term><listitem><para>

Choose this if you want to use another boot
manager. <command>LILO</command> will install itself at the beginning
of the new &debian; partition and it will serve as a secondary boot
loader.

</para></listitem></varlistentry>
<varlistentry>
<term>Other choice</term><listitem><para>

Useful for advanced users who want to install <command>LILO</command>
somewhere else. In this case you will be asked for desired
location. You can use traditional device names such as
<filename>/dev/hda</filename> or <filename>/dev/sda</filename>.

</para></listitem></varlistentry>
</variablelist>

</para><para>

If you can no longer boot into Windows 9x (or DOS) after this step,
you'll need to use a Windows 9x (MS-DOS) boot disk and use the
<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS
master boot record &mdash; however, this means that you'll need to use
some other way to get back into &debian;!

</para>
  </sect3>