Your message dated Mon, 04 May 2015 01:27:35 +0100
with message-id <1430699255.4113.124.ca...@decadent.org.uk>
and subject line Re: update information about i386 bootloader configuration
has caused the Debian Bug report #283972,
regarding update information about i386 bootloader configuration
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
283972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=283972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: debian-installer-manual
Severity: normal
Tags: patch
I would propose to move the reference to section 8.3 from lilo-installer
to os-prober, because this seems more appropriate. You might consider
ignoring the other more cosmetic parts of the patch, although I think we
really should stop talking about Windows 9x as probably most of the people
reading this will have 2000 or XP installed by now.
Index: en/using-d-i/modules/os-prober.xml
===================================================================
--- en/using-d-i/modules/os-prober.xml (revision 24138)
+++ en/using-d-i/modules/os-prober.xml (working copy)
@@ -34,4 +34,15 @@
</para></note>
+<para arch="i386">
+
+If you can no longer boot into Windows (or DOS) after this step,
+you'll need to use a Windows (MS-DOS) boot disk and use the
+<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS
+master boot record —; 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>
Index: en/using-d-i/modules/i386/lilo-installer.xml
===================================================================
--- en/using-d-i/modules/i386/lilo-installer.xml (revision 24138)
+++ en/using-d-i/modules/i386/lilo-installer.xml (working copy)
@@ -19,7 +19,8 @@
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.
+systems like GNU/Linux (beside the one you just installed of course)
+and GNU/Hurd after the installation.
</para></note>
<para>
@@ -59,8 +60,8 @@
</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
+If you can no longer boot into Windows (or DOS) after this step,
+you'll need to use a Windows (MS-DOS) boot disk and use the
<userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS
master boot record — however, this means that you'll need to use
some other way to get back into Debian! For more information on this
This change of course will require a rewrite of the linked reactivating-win
document which is overdue anyway. I'm on it and will add it to this bug report
once I'm finished.
Gruesse,
Frank Lichtenheld
-- System Information:
Debian Release: 3.1
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.8-1-k7-smp
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8
--- End Message ---
--- Begin Message ---
The proposed text is present in the Debian 8 installation manual.
Ben.
--
Ben Hutchings
If you seem to know what you are doing, you'll be given more to do.
signature.asc
Description: This is a digitally signed message part
--- End Message ---
