From 1ea73eea5ecc6a8ed901316049259aee737ee554 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@debian.org>
Date: Fri, 7 Oct 2005 19:51:38 +0000
Subject: move manual to top-level directory, split out of debian-installer
 package

---
 it/using-d-i/modules/i386/lilo-installer.xml | 70 ++++++++++++++++++++++++++++
 1 file changed, 70 insertions(+)
 create mode 100644 it/using-d-i/modules/i386/lilo-installer.xml

(limited to 'it/using-d-i/modules/i386/lilo-installer.xml')

diff --git a/it/using-d-i/modules/i386/lilo-installer.xml b/it/using-d-i/modules/i386/lilo-installer.xml
new file mode 100644
index 000000000..30726d83a
--- /dev/null
+++ b/it/using-d-i/modules/i386/lilo-installer.xml
@@ -0,0 +1,70 @@
+<!-- retain these comments for translator revision tracking -->
+<!-- original version: 22935 untranslated -->
+
+  <sect3 arch="i386">
+  <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; presents you three choices 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 devfs style names, such as those that start with
+<filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and
+<filename>/dev/discs</filename>, as well as traditional 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! For more information on this
+please read <xref linkend="reactivating-win"/>.
+
+</para>
+  </sect3>
-- 
cgit v1.2.3