From 29ba2e2cf1e8043f68702e111f12b097446058b9 Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Mon, 7 Aug 2006 21:03:18 +0000 Subject: Rename some i386 files/directories to x86 because of AMD64 inclusion --- en/boot-installer/boot-installer.xml | 2 +- en/boot-installer/i386.xml | 367 --------------------------- en/boot-installer/x86.xml | 367 +++++++++++++++++++++++++++ en/install-methods/boot-usb-files.xml | 2 +- en/install-methods/usb-setup/i386.xml | 97 ------- en/install-methods/usb-setup/x86.xml | 97 +++++++ en/partitioning/partition-programs.xml | 2 +- en/partitioning/partition/i386.xml | 95 ------- en/partitioning/partition/x86.xml | 95 +++++++ en/preparing/non-debian-partitioning.xml | 2 +- en/preparing/nondeb-part/i386.xml | 121 --------- en/preparing/nondeb-part/x86.xml | 121 +++++++++ en/using-d-i/components.xml | 4 +- en/using-d-i/modules/i386/grub-installer.xml | 26 -- en/using-d-i/modules/i386/lilo-installer.xml | 70 ----- en/using-d-i/modules/x86/grub-installer.xml | 26 ++ en/using-d-i/modules/x86/lilo-installer.xml | 70 +++++ 17 files changed, 782 insertions(+), 782 deletions(-) delete mode 100644 en/boot-installer/i386.xml create mode 100644 en/boot-installer/x86.xml delete mode 100644 en/install-methods/usb-setup/i386.xml create mode 100644 en/install-methods/usb-setup/x86.xml delete mode 100644 en/partitioning/partition/i386.xml create mode 100644 en/partitioning/partition/x86.xml delete mode 100644 en/preparing/nondeb-part/i386.xml create mode 100644 en/preparing/nondeb-part/x86.xml delete mode 100644 en/using-d-i/modules/i386/grub-installer.xml delete mode 100644 en/using-d-i/modules/i386/lilo-installer.xml create mode 100644 en/using-d-i/modules/x86/grub-installer.xml create mode 100644 en/using-d-i/modules/x86/lilo-installer.xml (limited to 'en') diff --git a/en/boot-installer/boot-installer.xml b/en/boot-installer/boot-installer.xml index 61c60df6f..cf6f83f3d 100644 --- a/en/boot-installer/boot-installer.xml +++ b/en/boot-installer/boot-installer.xml @@ -15,7 +15,7 @@ &boot-installer-alpha.xml; &boot-installer-arm.xml; -&boot-installer-i386.xml; +&boot-installer-x86.xml; &boot-installer-ia64.xml; &boot-installer-m68k.xml; &boot-installer-mips.xml; diff --git a/en/boot-installer/i386.xml b/en/boot-installer/i386.xml deleted file mode 100644 index fbdb87ba5..000000000 --- a/en/boot-installer/i386.xml +++ /dev/null @@ -1,367 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - - - - - - - - Booting from Linux Using <command>LILO</command> or - <command>GRUB</command> - - -To boot the installer from hard disk, you must first download -and place the needed files as described in . - - - -If you intend to use the hard drive only for booting and then -download everything over the network, you should download the -netboot/debian-installer/i386/initrd.gz file and its -corresponding kernel. This will allow you to repartition the hard disk -from which you boot the installer, although you should do so with care. - - - -Alternatively, if you intend to keep an existing partition on the hard -drive unchanged during the install, you can download the -hd-media/initrd.gz file and its kernel, as well as -copy a CD iso to the drive (make sure the file is named ending in -.iso). The installer can then boot from the drive -and install from the CD image, without needing the network. - - - -For LILO, you will need to configure two -essential things in /etc/lilo.conf: - - - -to load the initrd.gz installer at boot time; - - - - -have the vmlinuz kernel use a RAM disk as -its root partition. - - - - -Here is a /etc/lilo.conf example: - - - - -image=/boot/newinstall/vmlinuz - label=newinstall - initrd=/boot/newinstall/initrd.gz - root=/dev/ram0 - append="ramdisk_size=12000" - - -For more details, refer to the -initrd -4 and -lilo.conf -5 man pages. Now run -lilo and reboot. - - - -The procedure for GRUB is quite similar. Locate your -menu.lst in the /boot/grub/ -directory (sometimes in the /boot/boot/grub/), -add the following lines: - - -title New Install -kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000 -initrd (hd0,0)/boot/newinstall/initrd.gz - - -and reboot. - - - -Note that the value of the ramdisk_size may need to be -adjusted for the size of the initrd image. -From here on, there should be no difference between GRUB -or LILO. - - - - - - Booting from USB Memory Stick - - -Let's assume you have prepared everything from and . Now -just plug your USB stick into some free USB connector and reboot the -computer. The system should boot up, and you should be presented with -the boot: prompt. Here you can enter optional boot -arguments, or just hit &enterkey;. - - - - - - Booting from Floppies - - -You will have already downloaded the floppy images you needed and -created floppies from the images in . - - - - -To boot from the installer boot floppy, place it in the primary floppy -drive, shut down the system as you normally would, then turn it back -on. - - - -For installing from an LS-120 drive (ATAPI version) with a set of -floppies, you need to specify the virtual location for the floppy -device. This is done with the root= boot -argument, giving the device that the ide-floppy driver maps the device -to. For example, if your LS-120 drive is connected as the first IDE -device (master) on the second cable, you enter -linux root=/dev/hdc at the boot prompt. -Installation from LS-120 is only supported by 2.4 and later kernels. - - - -Note that on some machines, Control -Alt Delete does not -properly reset the machine, so a hard reboot is recommended. If -you are installing from an existing operating system (e.g., from a DOS -box) you don't have a choice. Otherwise, please do a hard reboot when -booting. - - - -The floppy disk will be accessed, and you should then see a screen -that introduces the boot floppy and ends with the boot: -prompt. - - - -Once you press &enterkey;, you should see the message -Loading..., followed by -Uncompressing Linux..., and -then a screenfull or so of information about the hardware in your -system. More information on this phase of the boot process can be -found below in . - - - -After booting from the boot floppy, the root floppy is -requested. Insert the root floppy and press &enterkey;, and the -contents are loaded into memory. The installer program -debian-installer is automatically launched. - - - - - Booting with TFTP - -&boot-installer-intro-net.xml; - - - -There are various ways to do a TFTP boot on i386. - - - - NIC or Motherboard that support PXE - - -It could be that your Network Interface Card or Motherboard provides -PXE boot functionality. -This is a Intel re-implementation -of TFTP boot. If so you may be able to configure your BIOS to boot from the -network. - - - - - NIC with Network BootROM - - -It could be that your Network Interface Card provides -TFTP boot functionality. - - - -Let us (&email-debian-boot-list;) know how did you manage it. -Please refer to this document. - - - - - Etherboot - - -The etherboot project -provides bootdiskettes and even bootroms that do a TFTPboot. - - - - - - The Boot Prompt - - -When the installer boots, you should be presented with a friendly graphical -screen showing the Debian logo and the boot prompt: - - -Press F1 for help, or ENTER to boot: - - -At the boot prompt -you can either just press &enterkey; to boot the installer with -default options or enter a specific boot method and, optionally, boot -parameters. - - - -Information on available boot methods and on boot parameters which might -be useful can be found by pressing F2 through -F8. If you add any parameters to -the boot command line, be sure to type the boot method (the default is -linux) and a space before the first parameter (e.g., -linux fb=false). - - - -If you are installing the system via a remote management device that -provides a text interface to the VGA console, you may not be able to -see the initial graphical splash screen upon booting the installer; -you may even not see the boot prompt. Examples of these devices include -the text console of Compaq's integrated Lights Out (iLO) -and HP's Integrated Remote Assistant (IRA). -You can blindly press F1 - - - -In some cases these devices will require special escape sequences to -enact this keypress, for example the IRA uses Ctrl -F , 1. - - - - to bypass this screen and view the help text. Once you are -past the splash screen and at the help text your keystrokes will be echoed -at the prompt as expected. To prevent the installer from using the -framebuffer for the rest of the installation, you will also want to add -fb=false to the boot prompt, -as described in the help text. - - - - - diff --git a/en/boot-installer/x86.xml b/en/boot-installer/x86.xml new file mode 100644 index 000000000..fbdb87ba5 --- /dev/null +++ b/en/boot-installer/x86.xml @@ -0,0 +1,367 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + + + + + + + + Booting from Linux Using <command>LILO</command> or + <command>GRUB</command> + + +To boot the installer from hard disk, you must first download +and place the needed files as described in . + + + +If you intend to use the hard drive only for booting and then +download everything over the network, you should download the +netboot/debian-installer/i386/initrd.gz file and its +corresponding kernel. This will allow you to repartition the hard disk +from which you boot the installer, although you should do so with care. + + + +Alternatively, if you intend to keep an existing partition on the hard +drive unchanged during the install, you can download the +hd-media/initrd.gz file and its kernel, as well as +copy a CD iso to the drive (make sure the file is named ending in +.iso). The installer can then boot from the drive +and install from the CD image, without needing the network. + + + +For LILO, you will need to configure two +essential things in /etc/lilo.conf: + + + +to load the initrd.gz installer at boot time; + + + + +have the vmlinuz kernel use a RAM disk as +its root partition. + + + + +Here is a /etc/lilo.conf example: + + + + +image=/boot/newinstall/vmlinuz + label=newinstall + initrd=/boot/newinstall/initrd.gz + root=/dev/ram0 + append="ramdisk_size=12000" + + +For more details, refer to the +initrd +4 and +lilo.conf +5 man pages. Now run +lilo and reboot. + + + +The procedure for GRUB is quite similar. Locate your +menu.lst in the /boot/grub/ +directory (sometimes in the /boot/boot/grub/), +add the following lines: + + +title New Install +kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000 +initrd (hd0,0)/boot/newinstall/initrd.gz + + +and reboot. + + + +Note that the value of the ramdisk_size may need to be +adjusted for the size of the initrd image. +From here on, there should be no difference between GRUB +or LILO. + + + + + + Booting from USB Memory Stick + + +Let's assume you have prepared everything from and . Now +just plug your USB stick into some free USB connector and reboot the +computer. The system should boot up, and you should be presented with +the boot: prompt. Here you can enter optional boot +arguments, or just hit &enterkey;. + + + + + + Booting from Floppies + + +You will have already downloaded the floppy images you needed and +created floppies from the images in . + + + + +To boot from the installer boot floppy, place it in the primary floppy +drive, shut down the system as you normally would, then turn it back +on. + + + +For installing from an LS-120 drive (ATAPI version) with a set of +floppies, you need to specify the virtual location for the floppy +device. This is done with the root= boot +argument, giving the device that the ide-floppy driver maps the device +to. For example, if your LS-120 drive is connected as the first IDE +device (master) on the second cable, you enter +linux root=/dev/hdc at the boot prompt. +Installation from LS-120 is only supported by 2.4 and later kernels. + + + +Note that on some machines, Control +Alt Delete does not +properly reset the machine, so a hard reboot is recommended. If +you are installing from an existing operating system (e.g., from a DOS +box) you don't have a choice. Otherwise, please do a hard reboot when +booting. + + + +The floppy disk will be accessed, and you should then see a screen +that introduces the boot floppy and ends with the boot: +prompt. + + + +Once you press &enterkey;, you should see the message +Loading..., followed by +Uncompressing Linux..., and +then a screenfull or so of information about the hardware in your +system. More information on this phase of the boot process can be +found below in . + + + +After booting from the boot floppy, the root floppy is +requested. Insert the root floppy and press &enterkey;, and the +contents are loaded into memory. The installer program +debian-installer is automatically launched. + + + + + Booting with TFTP + +&boot-installer-intro-net.xml; + + + +There are various ways to do a TFTP boot on i386. + + + + NIC or Motherboard that support PXE + + +It could be that your Network Interface Card or Motherboard provides +PXE boot functionality. +This is a Intel re-implementation +of TFTP boot. If so you may be able to configure your BIOS to boot from the +network. + + + + + NIC with Network BootROM + + +It could be that your Network Interface Card provides +TFTP boot functionality. + + + +Let us (&email-debian-boot-list;) know how did you manage it. +Please refer to this document. + + + + + Etherboot + + +The etherboot project +provides bootdiskettes and even bootroms that do a TFTPboot. + + + + + + The Boot Prompt + + +When the installer boots, you should be presented with a friendly graphical +screen showing the Debian logo and the boot prompt: + + +Press F1 for help, or ENTER to boot: + + +At the boot prompt +you can either just press &enterkey; to boot the installer with +default options or enter a specific boot method and, optionally, boot +parameters. + + + +Information on available boot methods and on boot parameters which might +be useful can be found by pressing F2 through +F8. If you add any parameters to +the boot command line, be sure to type the boot method (the default is +linux) and a space before the first parameter (e.g., +linux fb=false). + + + +If you are installing the system via a remote management device that +provides a text interface to the VGA console, you may not be able to +see the initial graphical splash screen upon booting the installer; +you may even not see the boot prompt. Examples of these devices include +the text console of Compaq's integrated Lights Out (iLO) +and HP's Integrated Remote Assistant (IRA). +You can blindly press F1 + + + +In some cases these devices will require special escape sequences to +enact this keypress, for example the IRA uses Ctrl +F , 1. + + + + to bypass this screen and view the help text. Once you are +past the splash screen and at the help text your keystrokes will be echoed +at the prompt as expected. To prevent the installer from using the +framebuffer for the rest of the installation, you will also want to add +fb=false to the boot prompt, +as described in the help text. + + + + + diff --git a/en/install-methods/boot-usb-files.xml b/en/install-methods/boot-usb-files.xml index df1d34704..ec879fd5b 100644 --- a/en/install-methods/boot-usb-files.xml +++ b/en/install-methods/boot-usb-files.xml @@ -78,7 +78,7 @@ should use the following method to put the files on your stick. -&usb-setup-i386.xml; +&usb-setup-x86.xml; &usb-setup-powerpc.xml; diff --git a/en/install-methods/usb-setup/i386.xml b/en/install-methods/usb-setup/i386.xml deleted file mode 100644 index c35ef1e24..000000000 --- a/en/install-methods/usb-setup/i386.xml +++ /dev/null @@ -1,97 +0,0 @@ - - - - - USB stick partitioning on &arch-title; - - -We will show how to setup the memory stick to use the first partition, -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 to create a FAT16 partition, and then -create the filesystem using: - - -# mkdosfs /dev/sda1 - - -Take care that you use the correct device name for your USB stick. The -mkdosfs command is contained in the -dosfstools Debian package. - - - -In order to start the kernel after booting from the USB stick, we will -put a boot loader on the stick. Although any boot loader -(e.g. LILO) should work, it's convenient to use -SYSLINUX, since it uses a FAT16 partition and can -be reconfigured by just editing a text file. Any operating system -which supports the FAT file system can be used to make changes to the -configuration of the boot loader. - - - -To put SYSLINUX on the FAT16 partition on your USB -stick, install the syslinux and -mtools packages on your system, and do: - - -# syslinux /dev/sda1 - - -Again, take care that you use the correct device name. The partition -must not be mounted when starting SYSLINUX. This -procedure writes a boot sector to the partition and creates the file -ldlinux.sys which contains the boot loader code. - - - -Mount the partition (mount /dev/sda1 /mnt) and -copy the following files from the Debian archives to the stick: - - - - -vmlinuz (kernel binary) - - - - -initrd.gz (initial ramdisk image) - - - - -syslinux.cfg (SYSLINUX configuration file) - - - - -Optional kernel modules - - - - -If you want to rename the files, please note that -SYSLINUX can only process DOS (8.3) file names. - - - -The syslinux.cfg configuration file should -contain the following two lines: - - -default vmlinuz -append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw - - -Please note that the ramdisk_size parameter -may need to be increased, depending on the image you are booting. - - - diff --git a/en/install-methods/usb-setup/x86.xml b/en/install-methods/usb-setup/x86.xml new file mode 100644 index 000000000..c35ef1e24 --- /dev/null +++ b/en/install-methods/usb-setup/x86.xml @@ -0,0 +1,97 @@ + + + + + USB stick partitioning on &arch-title; + + +We will show how to setup the memory stick to use the first partition, +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 to create a FAT16 partition, and then +create the filesystem using: + + +# mkdosfs /dev/sda1 + + +Take care that you use the correct device name for your USB stick. The +mkdosfs command is contained in the +dosfstools Debian package. + + + +In order to start the kernel after booting from the USB stick, we will +put a boot loader on the stick. Although any boot loader +(e.g. LILO) should work, it's convenient to use +SYSLINUX, since it uses a FAT16 partition and can +be reconfigured by just editing a text file. Any operating system +which supports the FAT file system can be used to make changes to the +configuration of the boot loader. + + + +To put SYSLINUX on the FAT16 partition on your USB +stick, install the syslinux and +mtools packages on your system, and do: + + +# syslinux /dev/sda1 + + +Again, take care that you use the correct device name. The partition +must not be mounted when starting SYSLINUX. This +procedure writes a boot sector to the partition and creates the file +ldlinux.sys which contains the boot loader code. + + + +Mount the partition (mount /dev/sda1 /mnt) and +copy the following files from the Debian archives to the stick: + + + + +vmlinuz (kernel binary) + + + + +initrd.gz (initial ramdisk image) + + + + +syslinux.cfg (SYSLINUX configuration file) + + + + +Optional kernel modules + + + + +If you want to rename the files, please note that +SYSLINUX can only process DOS (8.3) file names. + + + +The syslinux.cfg configuration file should +contain the following two lines: + + +default vmlinuz +append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw + + +Please note that the ramdisk_size parameter +may need to be increased, depending on the image you are booting. + + + diff --git a/en/partitioning/partition-programs.xml b/en/partitioning/partition-programs.xml index 9783c19c2..c44fe79d0 100644 --- a/en/partitioning/partition-programs.xml +++ b/en/partitioning/partition-programs.xml @@ -156,7 +156,7 @@ includes steps you should take if you are sharing your disk with MacOS. &partition-alpha.xml; &partition-hppa.xml; -&partition-i386.xml; +&partition-x86.xml; &partition-ia64.xml; &partition-mips.xml; &partition-powerpc.xml; diff --git a/en/partitioning/partition/i386.xml b/en/partitioning/partition/i386.xml deleted file mode 100644 index 55681bd39..000000000 --- a/en/partitioning/partition/i386.xml +++ /dev/null @@ -1,95 +0,0 @@ - - - - - Partitioning for &arch-title; - - -If you have an existing other operating system such as DOS or Windows and -you want to preserve that operating system while installing Debian, you may -need to resize its partition to free up space for the Debian installation. -The installer supports resizing of both FAT and NTFS filesystems; when you -get to the installer's partitioning step, select the option -Manually edit partition table and then simply -select an existing partition and change its size. - - - -The PC BIOS generally adds additional constraints for disk -partitioning. There is a limit to how many primary and -logical partitions a drive can contain. Additionally, with pre -1994–98 BIOSes, there are limits to where on the drive the BIOS can boot -from. More information can be found in the -Linux Partition HOWTO and the -Phoenix BIOS FAQ, but -this section will include a brief overview to help you plan most situations. - - - -Primary partitions are the original partitioning scheme for PC -disks. However, there can only be four of them. To get past this -limitation, extended and logical partitions were invented. By -setting one of your primary partitions as an extended partition, you -can subdivide all the space allocated to that partition into logical -partitions. You can create up to 60 logical partitions per extended -partition; however, you can only have one extended partition per -drive. - - - -Linux limits the partitions per drive to 15 partitions for SCSI disks -(3 usable primary partitions, 12 logical partitions), and 63 -partitions on an IDE drive (3 usable primary partitions, 60 logical -partitions). However the normal &debian; system provides -only 20 devices for partitions, so you may not install on partitions -higher than 20 unless you first manually create devices for those -partitions. - - - -If you have a large IDE disk, and are using neither LBA addressing, -nor overlay drivers (sometimes provided by hard disk manufacturers), -then the boot partition (the partition containing your kernel image) -must be placed within the first 1024 cylinders of your hard drive -(usually around 524 megabytes, without BIOS translation). - - - -This restriction doesn't apply if you have a BIOS newer than around -1995–98 (depending on the manufacturer) that supports the Enhanced -Disk Drive Support Specification. Both Lilo, the Linux loader, and -Debian's alternative mbr must use the BIOS to read the -kernel from the disk into RAM. If the BIOS int 0x13 large disk access -extensions are found to be present, they will be utilized. Otherwise, -the legacy disk access interface is used as a fall-back, and it cannot -be used to address any location on the disk higher than the 1023rd -cylinder. Once Linux is booted, no matter what BIOS your computer -has, these restrictions no longer apply, since Linux does not use the -BIOS for disk access. - - - -If you have a large disk, you might have to use cylinder translation -techniques, which you can set from your BIOS setup program, such as -LBA (Logical Block Addressing) or CHS translation mode (Large). -More information about issues with large disks can be found in the -Large Disk HOWTO. If you -are using a cylinder translation scheme, and the BIOS does not support -the large disk access extensions, then your boot partition has to fit -within the translated representation of the -1024th cylinder. - - - -The recommended way of accomplishing this is to create a small (25–50MB -should suffice) partition at the beginning of the disk to be used as -the boot partition, and then create whatever other partitions you wish -to have, in the remaining area. This boot partition -must be mounted on /boot, -since that is the directory where the Linux kernel(s) will be stored. -This configuration will work on any system, regardless of whether LBA -or large disk CHS translation is used, and regardless of whether your -BIOS supports the large disk access extensions. - - - diff --git a/en/partitioning/partition/x86.xml b/en/partitioning/partition/x86.xml new file mode 100644 index 000000000..55681bd39 --- /dev/null +++ b/en/partitioning/partition/x86.xml @@ -0,0 +1,95 @@ + + + + + Partitioning for &arch-title; + + +If you have an existing other operating system such as DOS or Windows and +you want to preserve that operating system while installing Debian, you may +need to resize its partition to free up space for the Debian installation. +The installer supports resizing of both FAT and NTFS filesystems; when you +get to the installer's partitioning step, select the option +Manually edit partition table and then simply +select an existing partition and change its size. + + + +The PC BIOS generally adds additional constraints for disk +partitioning. There is a limit to how many primary and +logical partitions a drive can contain. Additionally, with pre +1994–98 BIOSes, there are limits to where on the drive the BIOS can boot +from. More information can be found in the +Linux Partition HOWTO and the +Phoenix BIOS FAQ, but +this section will include a brief overview to help you plan most situations. + + + +Primary partitions are the original partitioning scheme for PC +disks. However, there can only be four of them. To get past this +limitation, extended and logical partitions were invented. By +setting one of your primary partitions as an extended partition, you +can subdivide all the space allocated to that partition into logical +partitions. You can create up to 60 logical partitions per extended +partition; however, you can only have one extended partition per +drive. + + + +Linux limits the partitions per drive to 15 partitions for SCSI disks +(3 usable primary partitions, 12 logical partitions), and 63 +partitions on an IDE drive (3 usable primary partitions, 60 logical +partitions). However the normal &debian; system provides +only 20 devices for partitions, so you may not install on partitions +higher than 20 unless you first manually create devices for those +partitions. + + + +If you have a large IDE disk, and are using neither LBA addressing, +nor overlay drivers (sometimes provided by hard disk manufacturers), +then the boot partition (the partition containing your kernel image) +must be placed within the first 1024 cylinders of your hard drive +(usually around 524 megabytes, without BIOS translation). + + + +This restriction doesn't apply if you have a BIOS newer than around +1995–98 (depending on the manufacturer) that supports the Enhanced +Disk Drive Support Specification. Both Lilo, the Linux loader, and +Debian's alternative mbr must use the BIOS to read the +kernel from the disk into RAM. If the BIOS int 0x13 large disk access +extensions are found to be present, they will be utilized. Otherwise, +the legacy disk access interface is used as a fall-back, and it cannot +be used to address any location on the disk higher than the 1023rd +cylinder. Once Linux is booted, no matter what BIOS your computer +has, these restrictions no longer apply, since Linux does not use the +BIOS for disk access. + + + +If you have a large disk, you might have to use cylinder translation +techniques, which you can set from your BIOS setup program, such as +LBA (Logical Block Addressing) or CHS translation mode (Large). +More information about issues with large disks can be found in the +Large Disk HOWTO. If you +are using a cylinder translation scheme, and the BIOS does not support +the large disk access extensions, then your boot partition has to fit +within the translated representation of the +1024th cylinder. + + + +The recommended way of accomplishing this is to create a small (25–50MB +should suffice) partition at the beginning of the disk to be used as +the boot partition, and then create whatever other partitions you wish +to have, in the remaining area. This boot partition +must be mounted on /boot, +since that is the directory where the Linux kernel(s) will be stored. +This configuration will work on any system, regardless of whether LBA +or large disk CHS translation is used, and regardless of whether your +BIOS supports the large disk access extensions. + + + diff --git a/en/preparing/non-debian-partitioning.xml b/en/preparing/non-debian-partitioning.xml index 0f95aefe4..005d9fb84 100644 --- a/en/preparing/non-debian-partitioning.xml +++ b/en/preparing/non-debian-partitioning.xml @@ -190,7 +190,7 @@ Boot the Debian installer to continue installing Debian. &nondeb-part-alpha.xml; -&nondeb-part-i386.xml; +&nondeb-part-x86.xml; &nondeb-part-m68k.xml; &nondeb-part-sparc.xml; &nondeb-part-powerpc.xml; diff --git a/en/preparing/nondeb-part/i386.xml b/en/preparing/nondeb-part/i386.xml deleted file mode 100644 index 4346fe83f..000000000 --- a/en/preparing/nondeb-part/i386.xml +++ /dev/null @@ -1,121 +0,0 @@ - - - - - Partitioning From DOS or Windows - - -If you are manipulating existing FAT or NTFS partitions, it is -recommended that you either use the scheme below or native Windows or -DOS tools. Otherwise, it is not really necessary to partition from DOS -or Windows; the Linux partitioning tools will generally do a better -job. - - - -But if you have a large IDE disk, and are using neither LBA addressing, -overlay drivers (sometimes provided by hard disk manufacturers), nor a -new (post 1998) BIOS that supports large disk access extensions, then -you must locate your Debian boot partition carefully. In this case, -you will have to put the boot partition into the first 1024 cylinders -of your hard drive (usually around 524 megabytes, without BIOS -translation). This may require that you move an existing FAT or NTFS -partition. - - - - - Lossless Repartitioning When Starting From DOS, Win-32 or OS/2 - - - - -One of the most common installations is onto a system that already -contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, -NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk -without destroying the previous system. Note that the installer supports -resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply -start the installer, select the option to Manually -edit partition table , select the partition to -resize, and specify its new size. -So in most cases you should not need to use the method described below. - - - -Before going any further, you should have decided how you will be -dividing up the disk. The method in this section will only split a -partition into two pieces. One will contain the original OS and the -other will be used for Debian. During the installation of Debian, you -will be given the opportunity to use the Debian portion of the disk as you -see fit, i.e., as swap or as a file system. - - - -The idea is to move all the data on the partition to the beginning, -before changing the partition information, so that nothing will be -lost. It is important that you do as little as possible between the -data movement and repartitioning to minimize the chance of a file -being written near the end of the partition as this will decrease the -amount of space you can take from the partition. - - - -The first thing needed is a copy of fips which is -available in the tools/ directory on your nearest Debian -mirror. Unzip the archive and copy the files -RESTORRB.EXE, FIPS.EXE and -ERRORS.TXT to a bootable floppy. A bootable floppy can -be created using the command sys a: under DOS. -fips comes with very good documentation which you may -want to read. You will definitely need to read the documentation if -you use a disk compression driver or a disk manager. Create the disk -and read the documentation before you defragment the disk. - - - -The next thing needed is to move all the data to the beginning of the -partition. defrag, which comes standard with DOS 6.0 and -later, can easily do the job. See the fips documentation -for a list of other software that may do the trick. Note that if you -have Windows 9x, you must run defrag from there, since -DOS doesn't understand VFAT, which is used to support for long -filenames, used in Windows 95 and higher. - - - -After running the defragmenter (which can take a while on a large -disk), reboot with the fips disk you created in the -floppy drive. Simply type a:\fips and follow the directions. - - - -Note that there are many other partition managers out there, in -case fips doesn't do the trick for you. - - - - - Partitioning for DOS - - - -If you are partitioning for DOS drives, or changing the size of DOS -partitions, using Linux tools, many people experience problems working -with the resulting FAT partitions. For instance, some have reported -slow performance, consistent problems with scandisk, or -other weird errors in DOS or Windows. - - - -Apparently, whenever you create or resize a partition for DOS use, -it's a good idea to fill the first few sectors with zeros. You should do -this prior to running DOS's format command by executing -the following command from Linux: - - -# dd if=/dev/zero of=/dev/hdXX bs=512 count=4 - - - - - diff --git a/en/preparing/nondeb-part/x86.xml b/en/preparing/nondeb-part/x86.xml new file mode 100644 index 000000000..4346fe83f --- /dev/null +++ b/en/preparing/nondeb-part/x86.xml @@ -0,0 +1,121 @@ + + + + + Partitioning From DOS or Windows + + +If you are manipulating existing FAT or NTFS partitions, it is +recommended that you either use the scheme below or native Windows or +DOS tools. Otherwise, it is not really necessary to partition from DOS +or Windows; the Linux partitioning tools will generally do a better +job. + + + +But if you have a large IDE disk, and are using neither LBA addressing, +overlay drivers (sometimes provided by hard disk manufacturers), nor a +new (post 1998) BIOS that supports large disk access extensions, then +you must locate your Debian boot partition carefully. In this case, +you will have to put the boot partition into the first 1024 cylinders +of your hard drive (usually around 524 megabytes, without BIOS +translation). This may require that you move an existing FAT or NTFS +partition. + + + + + Lossless Repartitioning When Starting From DOS, Win-32 or OS/2 + + + + +One of the most common installations is onto a system that already +contains DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, +NT, 2000, XP), or OS/2, and it is desired to put Debian onto the same disk +without destroying the previous system. Note that the installer supports +resizing of FAT and NTFS filesystems as used by DOS and Windows. Simply +start the installer, select the option to Manually +edit partition table , select the partition to +resize, and specify its new size. +So in most cases you should not need to use the method described below. + + + +Before going any further, you should have decided how you will be +dividing up the disk. The method in this section will only split a +partition into two pieces. One will contain the original OS and the +other will be used for Debian. During the installation of Debian, you +will be given the opportunity to use the Debian portion of the disk as you +see fit, i.e., as swap or as a file system. + + + +The idea is to move all the data on the partition to the beginning, +before changing the partition information, so that nothing will be +lost. It is important that you do as little as possible between the +data movement and repartitioning to minimize the chance of a file +being written near the end of the partition as this will decrease the +amount of space you can take from the partition. + + + +The first thing needed is a copy of fips which is +available in the tools/ directory on your nearest Debian +mirror. Unzip the archive and copy the files +RESTORRB.EXE, FIPS.EXE and +ERRORS.TXT to a bootable floppy. A bootable floppy can +be created using the command sys a: under DOS. +fips comes with very good documentation which you may +want to read. You will definitely need to read the documentation if +you use a disk compression driver or a disk manager. Create the disk +and read the documentation before you defragment the disk. + + + +The next thing needed is to move all the data to the beginning of the +partition. defrag, which comes standard with DOS 6.0 and +later, can easily do the job. See the fips documentation +for a list of other software that may do the trick. Note that if you +have Windows 9x, you must run defrag from there, since +DOS doesn't understand VFAT, which is used to support for long +filenames, used in Windows 95 and higher. + + + +After running the defragmenter (which can take a while on a large +disk), reboot with the fips disk you created in the +floppy drive. Simply type a:\fips and follow the directions. + + + +Note that there are many other partition managers out there, in +case fips doesn't do the trick for you. + + + + + Partitioning for DOS + + + +If you are partitioning for DOS drives, or changing the size of DOS +partitions, using Linux tools, many people experience problems working +with the resulting FAT partitions. For instance, some have reported +slow performance, consistent problems with scandisk, or +other weird errors in DOS or Windows. + + + +Apparently, whenever you create or resize a partition for DOS use, +it's a good idea to fill the first few sectors with zeros. You should do +this prior to running DOS's format command by executing +the following command from Linux: + + +# dd if=/dev/zero of=/dev/hdXX bs=512 count=4 + + + + + diff --git a/en/using-d-i/components.xml b/en/using-d-i/components.xml index 0d0570fd2..5f7dfaa07 100644 --- a/en/using-d-i/components.xml +++ b/en/using-d-i/components.xml @@ -144,8 +144,8 @@ documentation for more information. &module-os-prober.xml; &module-alpha-aboot-installer.xml; &module-hppa-palo-installer.xml; -&module-i386-grub-installer.xml; -&module-i386-lilo-installer.xml; +&module-x86-grub-installer.xml; +&module-x86-lilo-installer.xml; &module-ia64-elilo-installer.xml; &module-mips-arcboot-installer.xml; &module-mipsel-colo-installer.xml; diff --git a/en/using-d-i/modules/i386/grub-installer.xml b/en/using-d-i/modules/i386/grub-installer.xml deleted file mode 100644 index 814ad824b..000000000 --- a/en/using-d-i/modules/i386/grub-installer.xml +++ /dev/null @@ -1,26 +0,0 @@ - - - - - Install the <command>Grub</command> Boot Loader - on a Hard Disk - - -The main &architecture; boot loader is called grub. -Grub is a flexible and robust boot loader and a good default choice for -newbies and old hands alike. - - - -By default, grub will be installed into the Master Boot Record (MBR), where -it will take over complete control of the boot process. If you prefer, you -can install it elsewhere. See the grub manual for complete information. - - - -If you do not want to install grub at all, use the Back button to get to -the main menu, and from there select whatever bootloader you would like to -use. - - - diff --git a/en/using-d-i/modules/i386/lilo-installer.xml b/en/using-d-i/modules/i386/lilo-installer.xml deleted file mode 100644 index 9b2ead402..000000000 --- a/en/using-d-i/modules/i386/lilo-installer.xml +++ /dev/null @@ -1,70 +0,0 @@ - - - - - Install the <command>LILO</command> Boot Loader - on a Hard Disk - - -The second &architecture; boot loader is called LILO. -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 -/usr/share/doc/lilo/ if you have special needs; -also see the LILO mini-HOWTO. - - - - -Currently the LILO installation will only create menu entries for other -operating systems if these can be chainloaded. -This means you may have to manually add a menu entry for operating -systems like GNU/Linux and GNU/Hurd after the installation. - - - - -&d-i; presents you three choices where to install the -LILO boot loader: - - - -Master Boot Record (MBR) - -This way the LILO will take complete control of the -boot process. - - - -new Debian partition - -Choose this if you want to use another boot -manager. LILO will install itself at the beginning -of the new Debian partition and it will serve as a secondary boot -loader. - - - -Other choice - -Useful for advanced users who want to install LILO -somewhere else. In this case you will be asked for desired -location. You can use devfs style names, such as those that start with -/dev/ide, /dev/scsi, and -/dev/discs, as well as traditional names, such as -/dev/hda or /dev/sda. - - - - - - -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 -fdisk /mbr 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 . - - - diff --git a/en/using-d-i/modules/x86/grub-installer.xml b/en/using-d-i/modules/x86/grub-installer.xml new file mode 100644 index 000000000..814ad824b --- /dev/null +++ b/en/using-d-i/modules/x86/grub-installer.xml @@ -0,0 +1,26 @@ + + + + + Install the <command>Grub</command> Boot Loader + on a Hard Disk + + +The main &architecture; boot loader is called grub. +Grub is a flexible and robust boot loader and a good default choice for +newbies and old hands alike. + + + +By default, grub will be installed into the Master Boot Record (MBR), where +it will take over complete control of the boot process. If you prefer, you +can install it elsewhere. See the grub manual for complete information. + + + +If you do not want to install grub at all, use the Back button to get to +the main menu, and from there select whatever bootloader you would like to +use. + + + diff --git a/en/using-d-i/modules/x86/lilo-installer.xml b/en/using-d-i/modules/x86/lilo-installer.xml new file mode 100644 index 000000000..9b2ead402 --- /dev/null +++ b/en/using-d-i/modules/x86/lilo-installer.xml @@ -0,0 +1,70 @@ + + + + + Install the <command>LILO</command> Boot Loader + on a Hard Disk + + +The second &architecture; boot loader is called LILO. +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 +/usr/share/doc/lilo/ if you have special needs; +also see the LILO mini-HOWTO. + + + + +Currently the LILO installation will only create menu entries for other +operating systems if these can be chainloaded. +This means you may have to manually add a menu entry for operating +systems like GNU/Linux and GNU/Hurd after the installation. + + + + +&d-i; presents you three choices where to install the +LILO boot loader: + + + +Master Boot Record (MBR) + +This way the LILO will take complete control of the +boot process. + + + +new Debian partition + +Choose this if you want to use another boot +manager. LILO will install itself at the beginning +of the new Debian partition and it will serve as a secondary boot +loader. + + + +Other choice + +Useful for advanced users who want to install LILO +somewhere else. In this case you will be asked for desired +location. You can use devfs style names, such as those that start with +/dev/ide, /dev/scsi, and +/dev/discs, as well as traditional names, such as +/dev/hda or /dev/sda. + + + + + + +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 +fdisk /mbr 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 . + + + -- cgit v1.2.3