Bug#518808: [PATCH] d-i manual: document booting from DOS
Hello,
This is a fixed patch with FJP's comments addressed, I believe.
Frans Pop, le Fri 06 Nov 2009 04:16:39 +0100, a écrit :
> I've looked at the patch from Holger (as that's the most extensive of the
> two), but have some problems with it. My comments below.
>
> Cheers,
> FJP
>
> On Saturday 19 September 2009, Holger Wansing wrote:
> > I have tested booting testing/squeeze from MS-DOS and here are some
> > improvements/updates to the d-i manual documentation on this.
> >
> > Please consider to use the patch attached here.
>
> --- en/boot-installer/x86.xml 2009-09-18 22:29:22.000000000 +0200
> +++ en/boot-installer/x86_workingcopy.xml 2009-09-18 22:19:39.000000000 +0200
> [...]
> Boot into DOS (not Windows) without any drivers being loaded. To do
> this, you have to press <keycap>F8</keycap> at exactly the right
> moment (and optionally select the <quote>safe mode command prompt only</quote>
>
> FJP:
> AFAIK current versions of Windows (including XP!) don't have a "safe
> mode command prompt only" option. This is ancient history. If you want
> to revive this, we need to provide updated info in how to run DOS in the
> first place.
I have replaced that with booting from a recovery or diagnostic disk.
> -option). Enter the subdirectory for the flavor you chose, e.g.,
> +option). Enter the subdirectory install.386:
>
> FJP:
> "install.386" is only valid for i386, but for amd64 it should be
> "install.amd". As the section is for arch="x86", we should cover both
> correctly. The best way to do this is probably to define an entity in
> build/entities/common.ent, something like:
> <!ENTITY x86-install-dir
> "install.<phrase arch="i386">386</phrase><phrase arch="amd64">amd</phrase>">
> And then use that whereever the patch now has 'install.386'.
I did it.
> --- en/install-methods/boot-drive-files.xml 2009-09-18 22:29:22.000000000 +0200
> +++ en/install-methods/boot-drive-files_workingcopy.xml 2009-09-18 22:23:24.000000000 +0200
> [...]
> +Copy the following directories from a &d-i; installation CD or DVD to your
> +hard drive, let's say to <filename>c:\</filename>:
>
> FJP:
> This is too vague. The directories *must* be copied to c:\, or at
> least to the root dir of a hard drive because otherwise the batchfile
> will not work.
> But wouldn't it be much simpler to completely forget about copying files
> and just say:
> - mount the CD drive
> - change to the CD drive
> - cd to \install.{386,amd}
> - run install.bat
> ?
It might be quite difficult to find CD drivers actually. On my laptop,
for instance, the recovery partition doesn't have any. Copying the
files ahead still permits to boot in that case. I have reworked it to
say to copy to c:\. I have added the possibility of booting directly
from the CD, however.
Samuel
Index: en/install-methods/boot-drive-files.xml
===================================================================
--- en/install-methods/boot-drive-files.xml (révision 64518)
+++ en/install-methods/boot-drive-files.xml (copie de travail)
@@ -16,10 +16,6 @@
and burning CD images or struggling with too numerous and
unreliable floppy disks.
-</para><para arch="x86">
-
-The installer cannot boot from files on an NTFS file system.
-
</para><para arch="powerpc">
The installer cannot boot from files on an HFS+ file system. MacOS
@@ -57,7 +53,8 @@
</para><para>
Copy the following files from the Debian archives to a
-convenient location on your hard drive, for instance to
+convenient location on your hard drive (note that LILO
+can not boot from files on an NTFS file system), for instance to
<filename>/boot/newinstall/</filename>.
<itemizedlist>
@@ -82,6 +79,35 @@
</sect2>
+ <sect2 arch="x86" id="files-loadlin">
+ <title>Hard disk installer booting using <command>loadlin</command></title>
+<para>
+
+This section explains how to prepare your hard drive for booting the installer
+from DOS using <command>loadlin</command>.
+
+</para><para>
+
+Copy the following files from a Debian CD image to <filename>c:\</filename>.
+
+<itemizedlist>
+<listitem><para>
+
+<filename>/&x86-install-dir;</filename> (kernel binary and ramdisk image)
+
+</para></listitem>
+<listitem><para>
+
+<filename>/tools</filename> (loadlin tool)
+
+</para></listitem>
+
+</itemizedlist>
+
+</para>
+ </sect2>
+
+
<sect2 arch="powerpc" id="files-oldworld">
<title>Hard Disk Installer Booting for OldWorld Macs</title>
<para>
Index: en/boot-installer/x86.xml
===================================================================
--- en/boot-installer/x86.xml (révision 64518)
+++ en/boot-installer/x86.xml (copie de travail)
@@ -95,40 +95,46 @@
</para>
</sect2>
-<!-- FIXME the documented procedure does not exactly work, commented out
- until fixes
-
<sect2 arch="x86" id="install-from-dos">
- <title>Booting from a DOS partition</title>
+ <title>Booting from DOS</title>
+<para>
-&boot-installer-intro-hd.xml;
+Boot into DOS (not Windows). To do this, you can for instance boot from a
+recovery or diagnostic disk.
-<para>
+</para><para>
-Boot into DOS (not Windows) without any drivers being loaded. To do
-this, you have to press <keycap>F8</keycap> at exactly the right
-moment (and optionally select the <quote>safe mode command prompt only</quote>
-option). Enter the subdirectory for the flavor you chose, e.g.,
+If you can access the installation CD, change the current drive to the CD-ROM
+drive, e.g.
<informalexample><screen>
-cd c:\install
-</screen></informalexample>.
+d:
+</screen></informalexample>
-Next, execute <command>install.bat</command>.
-The kernel will load and launch the installer system.
+else make sure you have first prepared your hard disk as explained in
+<xref linkend="files-loadlin"/>, and change the current drive to it if needed.
</para><para>
-Please note, there is currently a loadlin problem (#142421) which
-precludes <filename>install.bat</filename> from being used with the
-bf2.4 flavor. The symptom of the problem is an
-<computeroutput>invalid compressed format</computeroutput> error.
+Enter the subdirectory for the flavor you chose, e.g.,
+<informalexample><screen>
+cd \&x86-install-dir;
+</screen></informalexample>
+
+If you prefer using the graphical installer, enter the <filename>gtk</filename>
+sub-directory.
+
+<informalexample><screen>
+cd gtk
+</screen></informalexample>
+
+Next, execute <command>install.bat</command>.
+The kernel will load and launch the installer system.
+
</para>
</sect2>
-END FIXME -->
-
<sect2 arch="x86" id="boot-initrd">
<title>Booting from Linux Using <command>LILO</command> or
<command>GRUB</command></title>
Index: build/entities/common.ent
===================================================================
--- build/entities/common.ent (révision 64519)
+++ build/entities/common.ent (copie de travail)
@@ -159,6 +159,11 @@
append="mcd=0x320,11"
read-only'>
+<!-- CD directory containing the kernel binary and ramdisk image,
+ according to the architecture. -->
+<!ENTITY x86-install-dir
+ "install.<filename arch='i386'>386</filename><filename arch='amd64'>amd</filename>">
+
<!-- prefix for files that can be downloaded -->
<!-- <![ %official-web-build; [ <!ENTITY downloadable-file "&url-boot-floppies;"> ]]> -->
<!ENTITY downloadable-file "&url-debian-installer;">
Reply to: