From 896130878d9d413d302aad68f6a87a981a23b3bb Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Sun, 30 Apr 2006 23:34:32 +0000 Subject: More corrections inspired by Clytie --- en/install-methods/boot-drive-files.xml | 6 +++--- en/install-methods/boot-usb-files.xml | 24 +++++++++++++----------- en/install-methods/create-floppy.xml | 11 ++++++----- en/install-methods/install-tftp.xml | 26 +++++++++++++------------- en/install-methods/ipl-tape.xml | 2 +- en/install-methods/tftp/bootp.xml | 12 ++++++------ en/install-methods/usb-setup/i386.xml | 2 +- 7 files changed, 43 insertions(+), 40 deletions(-) (limited to 'en/install-methods') diff --git a/en/install-methods/boot-drive-files.xml b/en/install-methods/boot-drive-files.xml index acde0cb56..39c36d50e 100644 --- a/en/install-methods/boot-drive-files.xml +++ b/en/install-methods/boot-drive-files.xml @@ -163,9 +163,9 @@ of your hard drive (this can be accomplished by Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS pdisk -program, you can use the L command to check for the partition -number. You will need this partition number for the command you type -at the Open Firmware prompt when you boot the installer. +program, you can use the L command to check for the +partition number. You will need this partition number for the command +you type at the Open Firmware prompt when you boot the installer. diff --git a/en/install-methods/boot-usb-files.xml b/en/install-methods/boot-usb-files.xml index 78615be96..22399fedc 100644 --- a/en/install-methods/boot-usb-files.xml +++ b/en/install-methods/boot-usb-files.xml @@ -6,17 +6,17 @@ -For preparing the USB stick you will need a system where GNU/Linux is +To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. You should ensure that the usb-storage kernel module is loaded (modprobe usb-storage) and try to find out which SCSI device the USB stick has been mapped to (in this example /dev/sda is used). To write to your stick, you -will probably have to turn off its write protection switch. +may have to turn off its write protection switch. -Note, that the USB stick should be at least 128 MB in size (smaller +Note that the USB stick should be at least 128 MB in size (smaller setups are possible if you follow ). @@ -81,12 +81,15 @@ should use the following method to put the files on your stick. &usb-setup-i386.xml; &usb-setup-powerpc.xml; - + + Adding an ISO image -Now you should put any Debian ISO image (businesscard, netinst or even -a full one) onto your stick (if it fits). The file name of such an +The installer will look for a Debian ISO image on the stick as its source +for additional data needed for the installation. So your next step is to +copy a Debian ISO image (businesscard, netinst or even a full CD image) +onto your stick (be sure to select one that fits). The file name of the image must end in .iso. @@ -104,11 +107,11 @@ When you are done, unmount the USB memory stick (umount /mnt) and activate its write protection switch. - + - - - Booting the USB stick + + + Booting the USB stick If your system refuses to boot from the memory stick, the stick may @@ -121,6 +124,5 @@ contain an invalid master boot record (MBR). To fix this, use the - diff --git a/en/install-methods/create-floppy.xml b/en/install-methods/create-floppy.xml index 433c91697..2b31174e1 100644 --- a/en/install-methods/create-floppy.xml +++ b/en/install-methods/create-floppy.xml @@ -10,11 +10,12 @@ installer on hardware that cannot boot from CD or by other means. -Floppy disk booting reportedly fails on Mac USB floppy drives. +Booting the installer from floppy disk reportedly fails on Mac USB +floppy drives. -Floppy disk booting is not supported on Amigas or +Booting the installer from floppy disk is not supported on Amigas or 68k Macs. @@ -30,9 +31,9 @@ floppy. -There are different techniques for creating floppies from disk images, -which depend on your platform. This section describes how to create -floppies from disk images on different platforms. +There are different techniques for creating floppies from disk images. +This section describes how to create floppies from disk images on +different platforms. diff --git a/en/install-methods/install-tftp.xml b/en/install-methods/install-tftp.xml index 0926ed5dc..45ad26d1b 100644 --- a/en/install-methods/install-tftp.xml +++ b/en/install-methods/install-tftp.xml @@ -186,7 +186,8 @@ to tftpd as the filename to boot. For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming -convention is subarchitecture/netboot-boot.img. +convention is +subarchitecture/netboot-boot.img. Copy the tftpimage file you would like to use to /tftpboot/tftpboot.img if you work with the example BOOTP/DHCP setups described above. @@ -262,22 +263,21 @@ these methods. SPARC TFTP Booting -SPARC architectures for instance use the subarchitecture names, such -as SUN4M or SUN4C; in some cases, the -architecture is left blank, so the file the client looks for is just -client-ip-in-hex. Thus, if your system -subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename -would be C0A80103.SUN4C. An easy way to determine -this is to enter the following command in a shell (assuming the -machine's intended IP is 10.0.0.4). +Some SPARC architectures add the subarchitecture names, such as +SUN4M or SUN4C, to the filename. Thus, +if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, +the filename would be C0A80103.SUN4C. However, +there are also subarchitectures where the file the client looks for is +just client-ip-in-hex. An easy way to determine the +hexadecimal code for the IP address is to enter the following command +in a shell (assuming the machine's intended IP is 10.0.0.4). $ printf '%.2x%.2x%.2x%.2x\n' 10 0 0 4 -This will spit out the IP in hexadecimal; to get to the correct -filename, you will need to change all letters to uppercase and -if necessary append the subarchitecture name. +To get to the correct filename, you will need to change all letters to +uppercase and if necessary append the subarchitecture name. @@ -325,7 +325,7 @@ the filename= option in You don't have to configure DHCP in a special way because you'll pass the -full path of the file to the loaded to CFE. +full path of the file to be loaded to CFE. diff --git a/en/install-methods/ipl-tape.xml b/en/install-methods/ipl-tape.xml index 383a302fc..fe8080e79 100644 --- a/en/install-methods/ipl-tape.xml +++ b/en/install-methods/ipl-tape.xml @@ -17,7 +17,7 @@ need to write to the tape are (in this order): parmfile.debian and initrd.debian. The files can be downloaded from the tape sub-directory, see -, +. diff --git a/en/install-methods/tftp/bootp.xml b/en/install-methods/tftp/bootp.xml index 0f1fb963d..cda0f9c66 100644 --- a/en/install-methods/tftp/bootp.xml +++ b/en/install-methods/tftp/bootp.xml @@ -6,11 +6,11 @@ Setting up BOOTP server -There are two BOOTP servers available for GNU/Linux, the CMU -bootpd and the other is actually a DHCP server, ISC -dhcpd, which are contained in the +There are two BOOTP servers available for GNU/Linux. The first is CMU +bootpd. The other is actually a DHCP server: ISC +dhcpd. In &debian; these are contained in the bootp and dhcp packages -in &debian;. +respectively. @@ -18,8 +18,8 @@ To use CMU bootpd, you must first uncomment (or add) the relevant line in /etc/inetd.conf. On &debian;, you can run update-inetd --enable bootps, then /etc/init.d/inetd -reload to do so. Elsewhere, the line in question should -look like: +reload to do so. Just in case your BOOTP server does not +run Debian, the line in question should look like: bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120 diff --git a/en/install-methods/usb-setup/i386.xml b/en/install-methods/usb-setup/i386.xml index 47c81e4ec..567a5e837 100644 --- a/en/install-methods/usb-setup/i386.xml +++ b/en/install-methods/usb-setup/i386.xml @@ -13,7 +13,7 @@ instead of the entire device. Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use cfdisk -or any other partitioning tool for creating a FAT16 partition and then +or any other partitioning tool to create a FAT16 partition, and then create the filesystem using: -- cgit v1.2.3