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 --- eu/boot-installer/boot-installer.xml | 2 +- eu/boot-installer/i386.xml | 542 --------------------------- eu/boot-installer/x86.xml | 542 +++++++++++++++++++++++++++ eu/partitioning/partition-programs.xml | 2 +- eu/partitioning/partition/i386.xml | 86 ----- eu/partitioning/partition/x86.xml | 86 +++++ eu/preparing/non-debian-partitioning.xml | 2 +- eu/preparing/nondeb-part/i386.xml | 122 ------ eu/preparing/nondeb-part/x86.xml | 122 ++++++ eu/using-d-i/components.xml | 4 +- eu/using-d-i/modules/i386/grub-installer.xml | 27 -- eu/using-d-i/modules/i386/lilo-installer.xml | 65 ---- eu/using-d-i/modules/x86/grub-installer.xml | 27 ++ eu/using-d-i/modules/x86/lilo-installer.xml | 65 ++++ 14 files changed, 847 insertions(+), 847 deletions(-) delete mode 100644 eu/boot-installer/i386.xml create mode 100644 eu/boot-installer/x86.xml delete mode 100644 eu/partitioning/partition/i386.xml create mode 100644 eu/partitioning/partition/x86.xml delete mode 100644 eu/preparing/nondeb-part/i386.xml create mode 100644 eu/preparing/nondeb-part/x86.xml delete mode 100644 eu/using-d-i/modules/i386/grub-installer.xml delete mode 100644 eu/using-d-i/modules/i386/lilo-installer.xml create mode 100644 eu/using-d-i/modules/x86/grub-installer.xml create mode 100644 eu/using-d-i/modules/x86/lilo-installer.xml (limited to 'eu') diff --git a/eu/boot-installer/boot-installer.xml b/eu/boot-installer/boot-installer.xml index 9bf77d2b2..b98b4c6dd 100644 --- a/eu/boot-installer/boot-installer.xml +++ b/eu/boot-installer/boot-installer.xml @@ -10,7 +10,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/eu/boot-installer/i386.xml b/eu/boot-installer/i386.xml deleted file mode 100644 index 6a2727f83..000000000 --- a/eu/boot-installer/i386.xml +++ /dev/null @@ -1,542 +0,0 @@ - - - - Booting from a CD-ROM - -&boot-installer-intro-cd.xml; - - - -You may need to configure your hardware as indicated in -. Then put the CD-ROM into the drive, -and reboot. The system should boot up, and you should be presented -with the boot: prompt. Here you can enter your -boot arguments, or just hit &enterkey;. - - - - - - -If your system can't boot directly from CD-ROM, or you simply can't -seem to get it to work, don't despair; you can simply run -E:\install\boot.bat under DOS (replace -E: with whatever drive letter DOS assigns to -your CD-ROM drive) to start the installation process. Then, skip down -to . - - - -Also, if you're going to be installing from a FAT (DOS) partition, you -have the option of booting the installer from the hard disk. See - for more information on -installing via this method. - - - - - - - - Booting from a DOS partition - -&boot-installer-intro-hd.xml; - - - -Boot into DOS (not Windows) without any drivers being loaded. To do -this, you have to press F8 at exactly the right -moment (and optionally select the `safe mode command prompt only' -option). Enter the subdirectory for the flavor you chose, e.g., - - - -cd c:\current\compact - -. - -Next, execute install.bat. -The kernel will load and launch the installer system. - - - -Please note, there is currently a loadlin problem (#142421) which -precludes install.bat from being used with the -bf2.4 flavor. The symptom of the problem is an -invalid compressed format error. - - - - - - - Booting from linux using <command>LILO</command> or - <command>GRUB</command> - - -For LILO, you will need to configure two -essentials 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/ram - append="devfs=mount,dall" - - - -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/ram devfs=mount,dall -initrd (hd0,0)/boot/newinstall/initrd.gz - - - -and reboot. Please note, that you may need an additional parameter -ramdisk_size=size in KB, -depending on the image you are booting. From now on, there should be -no difference between GRUB or LILO. - - - -You can trace the initrd magic at work several -times during the boot. - - - - -before the kernel has even been loaded, LILO -displays a much longer Loading -imagelabel...... line with -more dots than usual, showing the progression of the RAM disk image -loading. - - - - -You should see the RAM disk driver -initialized -notice, near the real time clock initialization, proving that your -kernel supports the RAM disk feature. - - - - -Finally, if you don't see RAMDISK: ext2 filesystem -found at block 0 immediately after the partition -checks, it's probably because -your kernel miss the initrd feature. - - - - - - -You should now see the debian installer running. If you do not use any -removable medium, you want to check very early that your network -connection is working and before irreversibly -partitioning your hard disk. So you maybe need to -insmod some additional kernel modules for this, -for instance for your network interface. It's time -not to follow the order of steps suggested by -debian-installer. Leap directly to Mount a -Previously-Initialized Partition, and mount the partition -where you stored the modules that you extracted from -drivers.tgz (). - - - - - - - -Then switch to an other virtual terminal and use a shell (see -) to find drivers -in the just mounted /target -directory. insmod the ones you need. - - - -Go to in the -debian-installer installer menus, and -ping your favorite debian mirror at last. -Congratulations! - - - -Use Unmount a Partition if you have mounted one -in the previous -paragraph, safely go back to the partitioning steps at the start of -debian-installer and follow the regular procedure, -with the network as a bonus. At this stage, it is even possible -(only a bit risky) to completely wipe out all the previous partitions -on your hard drive for a very clean installation. The only risk is that -your hard drive will be un-bootable for a short period of time. - - - - - - Booting from USB memory stick - - -Lets 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;. - - - -In case your computer doesn't support booting from USB memory devices, -you can still use a single floppy to do the initial boot and then -switch to USB. Advance according to ; the -kernel on boot floppy should detect your USB stick automatically. When -it asks for the root floppy, simply press &enterkey;. You should see -&d-i; starting. - - - - - - Booting from Floppies - - -You will have already downloaded the floppy images you needed and -created floppies from the images in . -If you need to, you can also modify the boot floppy; see -. - - - -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 a 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. - - - -You can do two things at the boot: prompt. You can -press the function keys F1 through -F10 to view a few pages of helpful information, or -you can boot the system. - - - -Information on boot parameters which might be useful can be found by -pressing F4 through F7. 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 floppy=thinkpad). If you simply press &enterkey;, -that's the same as typing linux without any special -parameters. - - - -Once you press &enterkey;, you should see the message -Loading..., followed by -Uncompressing Linux..., and -then a screenful 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. - - - - Etherboot - - -The etherboot project -provides bootdiskettes and even bootroms that do a TFTPboot. - - - - - 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. - - - - - NIC or Motherboard that support PXE - - -It could be that your Network Interface Card or Motherboard provides -PXE boot functionality. -Which is a Intel re-implemention -of TFTP boot. - - - -Let us (&email-debian-boot-list;) know how did you manage it. -Please refer to this document. - - - - - - - i386 Boot Parameters - - -If you are booting from the boot floppy or from CD-ROM you will be -presented with the boot prompt, boot:. Details -about how to use boot parameters with the boot floppy can be found -in . If you are booting from an -existing operating system, you'll have to use other means to set boot -parameters. For instance, if you are installing from DOS, you can -edit the install.bat file with any text editor. - - - -Some systems have floppies with ``inverted DCLs''. If you receive -errors reading from the floppy, even when you know the floppy is good, -try the parameter floppy=thinkpad. - - - -On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 -disk drivers), the IDE drive may not be properly recognized. Again, -try it first without the parameters and see if the IDE drive is -recognized properly. If not, determine your drive geometry -(cylinders, heads, and sectors), and use the parameter -hd=cylinders,heads,sectors. - - - -If you have a very old machine, and the kernel hangs after saying -Checking 'hlt' instruction..., then -you should try the no-hlt boot argument, which -disables this test. - - - -If your screen begins to show a weird picture while the kernel boots, -eg. pure white, pure black or colored pixel garbage, your system may -contain a problematic video card which does not switch to the -framebuffer mode properly. Then you can use the boot parameter -debian-installer/framebuffer=false or -video=vga16:off to disable the framebuffer -console. The language chooser will not appear; only the english -language will be available during the installation due to limited -console features. See for details. - - - - - - - System freeze during the PCMCIA configuration phase - - - -Some laptop models produced by Dell are known to crash when PCMCIA device -detection tries to access some hardware addresses. Other laptops may display -similar problems. If you experience such a problem and you don't need PCMCIA -support during the installation, you can disable PCMCIA using the -hw-detect/start_pcmcia=false boot parameter. You can -then configure PCMCIA after the installation is completed and exclude the -resource range causing the problems. - - - -Alternatively, you can boot the installer in expert mode. You will -then be asked to enter the resource range options your hardware -needs. For example, if you have one of the Dell laptops mentioned -above, you should enter exclude port -0x800-0x8ff here. There is also a list of some common -resource range options in the System -resource settings section of the PCMCIA HOWTO. Note that you -have to omit the commas, if any, when you enter this value in the -installer. - - - - - - System freeze while loading the USB modules - - -The kernel normally tries to install USB modules and the USB keyboard driver -in order to support some non-standard USB keyboards. However, there are some -broken USB systems where the driver hangs on loading. A possible workaround -may be disabling the USB controller in your mainboard BIOS setup. Another option -is passing the debian-installer/probe/usb=false parameter -at the boot prompt, which will prevent the modules from being loaded. - - - diff --git a/eu/boot-installer/x86.xml b/eu/boot-installer/x86.xml new file mode 100644 index 000000000..6a2727f83 --- /dev/null +++ b/eu/boot-installer/x86.xml @@ -0,0 +1,542 @@ + + + + Booting from a CD-ROM + +&boot-installer-intro-cd.xml; + + + +You may need to configure your hardware as indicated in +. Then put the CD-ROM into the drive, +and reboot. The system should boot up, and you should be presented +with the boot: prompt. Here you can enter your +boot arguments, or just hit &enterkey;. + + + + + + +If your system can't boot directly from CD-ROM, or you simply can't +seem to get it to work, don't despair; you can simply run +E:\install\boot.bat under DOS (replace +E: with whatever drive letter DOS assigns to +your CD-ROM drive) to start the installation process. Then, skip down +to . + + + +Also, if you're going to be installing from a FAT (DOS) partition, you +have the option of booting the installer from the hard disk. See + for more information on +installing via this method. + + + + + + + + Booting from a DOS partition + +&boot-installer-intro-hd.xml; + + + +Boot into DOS (not Windows) without any drivers being loaded. To do +this, you have to press F8 at exactly the right +moment (and optionally select the `safe mode command prompt only' +option). Enter the subdirectory for the flavor you chose, e.g., + + + +cd c:\current\compact + +. + +Next, execute install.bat. +The kernel will load and launch the installer system. + + + +Please note, there is currently a loadlin problem (#142421) which +precludes install.bat from being used with the +bf2.4 flavor. The symptom of the problem is an +invalid compressed format error. + + + + + + + Booting from linux using <command>LILO</command> or + <command>GRUB</command> + + +For LILO, you will need to configure two +essentials 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/ram + append="devfs=mount,dall" + + + +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/ram devfs=mount,dall +initrd (hd0,0)/boot/newinstall/initrd.gz + + + +and reboot. Please note, that you may need an additional parameter +ramdisk_size=size in KB, +depending on the image you are booting. From now on, there should be +no difference between GRUB or LILO. + + + +You can trace the initrd magic at work several +times during the boot. + + + + +before the kernel has even been loaded, LILO +displays a much longer Loading +imagelabel...... line with +more dots than usual, showing the progression of the RAM disk image +loading. + + + + +You should see the RAM disk driver +initialized +notice, near the real time clock initialization, proving that your +kernel supports the RAM disk feature. + + + + +Finally, if you don't see RAMDISK: ext2 filesystem +found at block 0 immediately after the partition +checks, it's probably because +your kernel miss the initrd feature. + + + + + + +You should now see the debian installer running. If you do not use any +removable medium, you want to check very early that your network +connection is working and before irreversibly +partitioning your hard disk. So you maybe need to +insmod some additional kernel modules for this, +for instance for your network interface. It's time +not to follow the order of steps suggested by +debian-installer. Leap directly to Mount a +Previously-Initialized Partition, and mount the partition +where you stored the modules that you extracted from +drivers.tgz (). + + + + + + + +Then switch to an other virtual terminal and use a shell (see +) to find drivers +in the just mounted /target +directory. insmod the ones you need. + + + +Go to in the +debian-installer installer menus, and +ping your favorite debian mirror at last. +Congratulations! + + + +Use Unmount a Partition if you have mounted one +in the previous +paragraph, safely go back to the partitioning steps at the start of +debian-installer and follow the regular procedure, +with the network as a bonus. At this stage, it is even possible +(only a bit risky) to completely wipe out all the previous partitions +on your hard drive for a very clean installation. The only risk is that +your hard drive will be un-bootable for a short period of time. + + + + + + Booting from USB memory stick + + +Lets 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;. + + + +In case your computer doesn't support booting from USB memory devices, +you can still use a single floppy to do the initial boot and then +switch to USB. Advance according to ; the +kernel on boot floppy should detect your USB stick automatically. When +it asks for the root floppy, simply press &enterkey;. You should see +&d-i; starting. + + + + + + Booting from Floppies + + +You will have already downloaded the floppy images you needed and +created floppies from the images in . +If you need to, you can also modify the boot floppy; see +. + + + +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 a 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. + + + +You can do two things at the boot: prompt. You can +press the function keys F1 through +F10 to view a few pages of helpful information, or +you can boot the system. + + + +Information on boot parameters which might be useful can be found by +pressing F4 through F7. 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 floppy=thinkpad). If you simply press &enterkey;, +that's the same as typing linux without any special +parameters. + + + +Once you press &enterkey;, you should see the message +Loading..., followed by +Uncompressing Linux..., and +then a screenful 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. + + + + Etherboot + + +The etherboot project +provides bootdiskettes and even bootroms that do a TFTPboot. + + + + + 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. + + + + + NIC or Motherboard that support PXE + + +It could be that your Network Interface Card or Motherboard provides +PXE boot functionality. +Which is a Intel re-implemention +of TFTP boot. + + + +Let us (&email-debian-boot-list;) know how did you manage it. +Please refer to this document. + + + + + + + i386 Boot Parameters + + +If you are booting from the boot floppy or from CD-ROM you will be +presented with the boot prompt, boot:. Details +about how to use boot parameters with the boot floppy can be found +in . If you are booting from an +existing operating system, you'll have to use other means to set boot +parameters. For instance, if you are installing from DOS, you can +edit the install.bat file with any text editor. + + + +Some systems have floppies with ``inverted DCLs''. If you receive +errors reading from the floppy, even when you know the floppy is good, +try the parameter floppy=thinkpad. + + + +On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 +disk drivers), the IDE drive may not be properly recognized. Again, +try it first without the parameters and see if the IDE drive is +recognized properly. If not, determine your drive geometry +(cylinders, heads, and sectors), and use the parameter +hd=cylinders,heads,sectors. + + + +If you have a very old machine, and the kernel hangs after saying +Checking 'hlt' instruction..., then +you should try the no-hlt boot argument, which +disables this test. + + + +If your screen begins to show a weird picture while the kernel boots, +eg. pure white, pure black or colored pixel garbage, your system may +contain a problematic video card which does not switch to the +framebuffer mode properly. Then you can use the boot parameter +debian-installer/framebuffer=false or +video=vga16:off to disable the framebuffer +console. The language chooser will not appear; only the english +language will be available during the installation due to limited +console features. See for details. + + + + + + + System freeze during the PCMCIA configuration phase + + + +Some laptop models produced by Dell are known to crash when PCMCIA device +detection tries to access some hardware addresses. Other laptops may display +similar problems. If you experience such a problem and you don't need PCMCIA +support during the installation, you can disable PCMCIA using the +hw-detect/start_pcmcia=false boot parameter. You can +then configure PCMCIA after the installation is completed and exclude the +resource range causing the problems. + + + +Alternatively, you can boot the installer in expert mode. You will +then be asked to enter the resource range options your hardware +needs. For example, if you have one of the Dell laptops mentioned +above, you should enter exclude port +0x800-0x8ff here. There is also a list of some common +resource range options in the System +resource settings section of the PCMCIA HOWTO. Note that you +have to omit the commas, if any, when you enter this value in the +installer. + + + + + + System freeze while loading the USB modules + + +The kernel normally tries to install USB modules and the USB keyboard driver +in order to support some non-standard USB keyboards. However, there are some +broken USB systems where the driver hangs on loading. A possible workaround +may be disabling the USB controller in your mainboard BIOS setup. Another option +is passing the debian-installer/probe/usb=false parameter +at the boot prompt, which will prevent the modules from being loaded. + + + diff --git a/eu/partitioning/partition-programs.xml b/eu/partitioning/partition-programs.xml index fa6f11267..0c4dfcc9a 100644 --- a/eu/partitioning/partition-programs.xml +++ b/eu/partitioning/partition-programs.xml @@ -127,7 +127,7 @@ beharreko pausuak baitakartza. &partition-alpha.xml; &partition-hppa.xml; -&partition-i386.xml; +&partition-x86.xml; &partition-ia64.xml; &partition-mips.xml; &partition-powerpc.xml; diff --git a/eu/partitioning/partition/i386.xml b/eu/partitioning/partition/i386.xml deleted file mode 100644 index 26c3e4296..000000000 --- a/eu/partitioning/partition/i386.xml +++ /dev/null @@ -1,86 +0,0 @@ - - - - - Partitioning for &arch-title; - - -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 BIOS, 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 (5-10MB -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/eu/partitioning/partition/x86.xml b/eu/partitioning/partition/x86.xml new file mode 100644 index 000000000..26c3e4296 --- /dev/null +++ b/eu/partitioning/partition/x86.xml @@ -0,0 +1,86 @@ + + + + + Partitioning for &arch-title; + + +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 BIOS, 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 (5-10MB +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/eu/preparing/non-debian-partitioning.xml b/eu/preparing/non-debian-partitioning.xml index 11bc81616..de301cf5d 100644 --- a/eu/preparing/non-debian-partitioning.xml +++ b/eu/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/eu/preparing/nondeb-part/i386.xml b/eu/preparing/nondeb-part/i386.xml deleted file mode 100644 index 5ab8df92b..000000000 --- a/eu/preparing/nondeb-part/i386.xml +++ /dev/null @@ -1,122 +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. As explained in the -, decreasing the size -of an existing partition -will almost certainly damage the data on that partition unless certain -precautions are taken. The method described here, while not -guaranteed to protect your data, works extremely well in practice. As -a precaution, you should make a backup. - - - -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 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. Do this -prior to running DOS's format command, from Linux: - - -dd if=/dev/zero of=/dev/hdXX bs=512 count=4 - - - - - - diff --git a/eu/preparing/nondeb-part/x86.xml b/eu/preparing/nondeb-part/x86.xml new file mode 100644 index 000000000..5ab8df92b --- /dev/null +++ b/eu/preparing/nondeb-part/x86.xml @@ -0,0 +1,122 @@ + + + + + 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. As explained in the +, decreasing the size +of an existing partition +will almost certainly damage the data on that partition unless certain +precautions are taken. The method described here, while not +guaranteed to protect your data, works extremely well in practice. As +a precaution, you should make a backup. + + + +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 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. Do this +prior to running DOS's format command, from Linux: + + +dd if=/dev/zero of=/dev/hdXX bs=512 count=4 + + + + + + diff --git a/eu/using-d-i/components.xml b/eu/using-d-i/components.xml index 6dff28b56..743ee2b76 100644 --- a/eu/using-d-i/components.xml +++ b/eu/using-d-i/components.xml @@ -93,8 +93,8 @@ gehiago jakiteko. &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/eu/using-d-i/modules/i386/grub-installer.xml b/eu/using-d-i/modules/i386/grub-installer.xml deleted file mode 100644 index cb42e642a..000000000 --- a/eu/using-d-i/modules/i386/grub-installer.xml +++ /dev/null @@ -1,27 +0,0 @@ - - - - - <command>Grub</command> Abiarazlea Disko - gogorrean instalatzen - - -&architecture; lehenetsitako abiarazlea grub deitzen da. -Grub abiarazle fidagarri eta oso malgu bat da eta normalean aukera -ona izaten zein erabiltzaile berri zein aurreratuagoentzat. - - - -Lehenespen bezala grub Abiarazte Grabaketa Nagusian (MBR) grabtuko da, -horik abiarazte prozesuaren kudeaketa guztia eginez. Zuk nahiago baduzu, -beste nombait instalatu dezakezu. Begiratu grub manual orrialdea -xehetasun gehiagorako. - - - -Hala ere zuk ez baduzu grub instalatu nahi, erabili atzera botoia -menu nagusira itzultzekoe eta han aukeratu instalatu nahi duzun -abiarazlea. - - - diff --git a/eu/using-d-i/modules/i386/lilo-installer.xml b/eu/using-d-i/modules/i386/lilo-installer.xml deleted file mode 100644 index 01dcce470..000000000 --- a/eu/using-d-i/modules/i386/lilo-installer.xml +++ /dev/null @@ -1,65 +0,0 @@ - - - - - <command>LILO</command> Abiarazlea diska - gogorrean instalatu - - -&architecture; bigarrengo abiarazlea LILO deitzen da. -Hau programa komplexu zahar bat eta funtzionalitate asko ditu, DOS, -Windows, eta OS/2 kudeaketa barne. Mesedez irakurri -/usr/share/doc/lilo/ karpetako argibideak -zuk behar bereizirik baduzu. -LILO mini-HOWTO ere interesgarri -izan daiteke.. - - - -&d-i;-k hiru aukera ematen dizkizu LILO -abiarazlea instalatzerakoan: - - - -Abiarazte Erregistro Nagusian (MBR) - -Modu honetan LILO-k abiarazten kontrol guztia -hartuko du. - - - -Debian partizio berrian - -Hau aukeratu beste abiarazle bat erabili nahi -baduzu. LILO Debian partizio hasieran -grabtuko da eta bigarren abiarazle bezala erabil daiteke. - - - - -Beste aukera bat - -Erabiltzaile aurreratuek LILO beste nombait -instalatu nahi dezakete. Kasu honetan zuri galdetu egin da -non instalatu behar den. devfs erako izenak erabili ditzatezi nolan -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, eta -/dev/discs, baita izen tradizionalak ere, nolan -/dev/hda edo /dev/sda. - - - - - - -Pausu honen ondoren ezin baduzu Windows 9x (edo DOS) abiaraz, -Windows 9x (MS-DOS) abiarazte disko bat artu eta -fdisk /mbr komandoa erabili MS-DOS abiarazte -erregistro nagusia — grabatzeko, honek zuk Debian abiarazteko -beste nolabait egin beharko duzula esan nahi du!. Argibide gehiagorako -irakurri . - - - diff --git a/eu/using-d-i/modules/x86/grub-installer.xml b/eu/using-d-i/modules/x86/grub-installer.xml new file mode 100644 index 000000000..cb42e642a --- /dev/null +++ b/eu/using-d-i/modules/x86/grub-installer.xml @@ -0,0 +1,27 @@ + + + + + <command>Grub</command> Abiarazlea Disko + gogorrean instalatzen + + +&architecture; lehenetsitako abiarazlea grub deitzen da. +Grub abiarazle fidagarri eta oso malgu bat da eta normalean aukera +ona izaten zein erabiltzaile berri zein aurreratuagoentzat. + + + +Lehenespen bezala grub Abiarazte Grabaketa Nagusian (MBR) grabtuko da, +horik abiarazte prozesuaren kudeaketa guztia eginez. Zuk nahiago baduzu, +beste nombait instalatu dezakezu. Begiratu grub manual orrialdea +xehetasun gehiagorako. + + + +Hala ere zuk ez baduzu grub instalatu nahi, erabili atzera botoia +menu nagusira itzultzekoe eta han aukeratu instalatu nahi duzun +abiarazlea. + + + diff --git a/eu/using-d-i/modules/x86/lilo-installer.xml b/eu/using-d-i/modules/x86/lilo-installer.xml new file mode 100644 index 000000000..01dcce470 --- /dev/null +++ b/eu/using-d-i/modules/x86/lilo-installer.xml @@ -0,0 +1,65 @@ + + + + + <command>LILO</command> Abiarazlea diska + gogorrean instalatu + + +&architecture; bigarrengo abiarazlea LILO deitzen da. +Hau programa komplexu zahar bat eta funtzionalitate asko ditu, DOS, +Windows, eta OS/2 kudeaketa barne. Mesedez irakurri +/usr/share/doc/lilo/ karpetako argibideak +zuk behar bereizirik baduzu. +LILO mini-HOWTO ere interesgarri +izan daiteke.. + + + +&d-i;-k hiru aukera ematen dizkizu LILO +abiarazlea instalatzerakoan: + + + +Abiarazte Erregistro Nagusian (MBR) + +Modu honetan LILO-k abiarazten kontrol guztia +hartuko du. + + + +Debian partizio berrian + +Hau aukeratu beste abiarazle bat erabili nahi +baduzu. LILO Debian partizio hasieran +grabtuko da eta bigarren abiarazle bezala erabil daiteke. + + + + +Beste aukera bat + +Erabiltzaile aurreratuek LILO beste nombait +instalatu nahi dezakete. Kasu honetan zuri galdetu egin da +non instalatu behar den. devfs erako izenak erabili ditzatezi nolan +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, eta +/dev/discs, baita izen tradizionalak ere, nolan +/dev/hda edo /dev/sda. + + + + + + +Pausu honen ondoren ezin baduzu Windows 9x (edo DOS) abiaraz, +Windows 9x (MS-DOS) abiarazte disko bat artu eta +fdisk /mbr komandoa erabili MS-DOS abiarazte +erregistro nagusia — grabatzeko, honek zuk Debian abiarazteko +beste nolabait egin beharko duzula esan nahi du!. Argibide gehiagorako +irakurri . + + + -- cgit v1.2.3