150
150
#: preparing.xml:141
152
msgid "For &arch-title; you have the option of using <phrase arch=\"x86\">a</phrase> <phrase arch=\"powerpc\">an experimental</phrase> graphical version of the installation system. For more information about this graphical installer, see <xref linkend=\"graphical\"/>."
152
158
msgid "If you have problems during the installation, it helps to know which packages are involved in which steps. Introducing the leading software actors in this installation drama:"
158
msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, and runs <classname>debootstrap</classname> to install the base system packages. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
164
msgid "The installer software, <classname>debian-installer</classname>, is the primary concern of this manual. It detects hardware and loads appropriate drivers, uses <classname>dhcp-client</classname> to set up the network connection, runs <classname>debootstrap</classname> to install the base system packages, and runs <classname>tasksel</classname> to allow you to install certain additional software. Many more actors play smaller parts in this process, but <classname>debian-installer</classname> has completed its task when you load the new system for the first time."
164
170
msgid "To tune the system to your needs, <classname>tasksel</classname> allows you to choose to install various predefined bundles of software like a Web server or a Desktop environment."
170
msgid "When <classname>debian-installer</classname> finishes, before the first system load, you have only a very basic command line driven system. The graphical interface which displays windows on your monitor will not be installed unless you select it with <classname>tasksel</classname>. It's optional because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job."
176
msgid "One important option during the installation is whether or not to install a graphical desktop environment, consisting of the X Window System and one of the available graphical desktop environments. If you choose not to select the <quote>Desktop environment</quote> task, you will only have a relatively basic, command line driven system. Installing the Desktop environment task is optional because it requires a fairly large amount of disk space, and because many &debian; systems are servers which don't really have any need for a graphical user interface to do their job."
176
msgid "Just be aware that the X system is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and trouble shooting of the X window installation is not within the scope of this manual."
182
msgid "Just be aware that the X Window System is completely separate from <classname>debian-installer</classname>, and in fact is much more complicated. Installation and troubleshooting of the X Window System is not within the scope of this manual."
182
188
msgid "Back Up Your Existing Data!"
188
msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you should count on losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
194
msgid "Before you start, make sure to back up every file that is now on your system. If this is the first time a non-native operating system has been installed on your computer, it's quite likely you will need to re-partition your disk to make room for &debian;. Anytime you partition your disk, you run a risk of losing everything on the disk, no matter what program you use to do it. The programs used in installation are quite reliable and most have seen years of use; but they are also quite powerful and a false move can cost you. Even after backing up, be careful and think about your answers and actions. Two minutes of thinking can save hours of unnecessary work."
194
200
msgid "If you are creating a multi-boot system, make sure that you have the distribution media of any other present operating systems on hand. Especially if you repartition your boot drive, you might find that you have to reinstall your operating system's boot loader, or in many cases the whole operating system itself and all files on the affected partitions."
200
206
msgid "With the exception of the BVM and Motorola VMEbus computers, the only supported installation method for m68k systems is booting from a local disk or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these machines you will need the original operating system in order to boot Linux. In order to boot Linux on the BVM and Motorola VMEbus machines you will need the <quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs."
206
212
msgid "Information You Will Need"
212
218
msgid "Documentation"
218
224
msgid "Installation Manual"
224
230
msgid "This document you are now reading, in plain ASCII, HTML or PDF format."
227
233
#. Tag: itemizedlist
230
236
msgid "&list-install-manual-files;"
236
242
msgid "The document you are now reading, which is the official version of the Installation Guide for the &releasename; release of Debian; available in <ulink url=\"&url-release-area;/installmanual\">various formats and translations</ulink>."
242
248
msgid "The document you are now reading, which is a development version of the Installation Guide for the next release of Debian; available in <ulink url=\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
248
254
msgid "Hardware documentation"
254
260
msgid "Often contains useful information on configuring or using your hardware."
260
266
msgid "Linux Hardware Compatibility HOWTO"
266
272
msgid "Linux/m68k FAQ"
272
278
msgid "Linux/Alpha FAQ"
278
284
msgid "Linux for SPARC Processors FAQ"
284
290
msgid "Linux/Mips website"
290
296
msgid "&arch-title; Hardware References"
296
302
msgid "Installation instructions and device drivers (DASD, XPRAM, Console, tape, z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4"
302
308
msgid "Device Drivers and Installation Commands"
308
314
msgid "IBM Redbook describing how Linux can be combined with z/VM on zSeries and &arch-title; hardware."
314
320
msgid "Linux for &arch-title;"
320
326
msgid "IBM Redbook describing the Linux distributions available for the mainframe. It has no chapter about Debian but the basic installation concepts are the same across all &arch-title; distributions."
326
332
msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions"
332
338
msgid "Finding Sources of Hardware Information"
338
344
msgid "In many cases, the installer will be able to automatically detect your hardware. But to be prepared, we do recommend familiarizing yourself with your hardware before the install."
344
350
msgid "Hardware information can be gathered from:"
350
356
msgid "The manuals that come with each piece of hardware."
356
362
msgid "The BIOS setup screens of your computer. You can view these screens when you start your computer by pressing a combination of keys. Check your manual for the combination. Often, it is the <keycap>Delete</keycap> key."
362
368
msgid "The cases and boxes for each piece of hardware."
368
374
msgid "The System window in the Windows Control Panel."
374
380
msgid "System commands or tools in another operating system, including file manager displays. This source is especially useful for information about RAM and hard drive memory."
380
386
msgid "Your system administrator or Internet Service Provider. These sources can tell you the settings you need to set up your networking and e-mail."
386
392
msgid "Hardware Information Needed for an Install"
398
404
msgid "Information You Might Need"
404
410
msgid "Hard Drives"
410
416
msgid "How many you have."
416
422
msgid "Their order on the system."
422
428
msgid "Whether IDE or SCSI (most computers are IDE)."
428
434
msgid "Whether IDE or SCSI (most m68k computers are SCSI)."
432
#: preparing.xml:450 preparing.xml:502
438
#: preparing.xml:462 preparing.xml:514
434
440
msgid "Available free space."
440
446
msgid "Partitions."
446
452
msgid "Partitions where other operating systems are installed."
456
#: preparing.xml:458 preparing.xml:478 preparing.xml:484 preparing.xml:490
462
#: preparing.xml:470 preparing.xml:490 preparing.xml:496 preparing.xml:502
458
464
msgid "Model and manufacturer."
464
470
msgid "Resolutions supported."
470
476
msgid "Horizontal refresh rate."
476
482
msgid "Vertical refresh rate."
482
488
msgid "Color depth (number of colors) supported."
488
494
msgid "Screen size."
500
506
msgid "Type: serial, PS/2, or USB."
512
518
msgid "Manufacturer."
518
524
msgid "Number of buttons."
522
#: preparing.xml:477 preparing.xml:505
528
#: preparing.xml:489 preparing.xml:517
528
#: preparing.xml:480 preparing.xml:506
534
#: preparing.xml:492 preparing.xml:518
530
536
msgid "Type of adapter."
542
548
msgid "Printing resolutions supported."
548
554
msgid "Video Card"
554
560
msgid "Video RAM available."
560
566
msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)."
572
578
msgid "Device number(s)."
578
584
msgid "Device numbers."
584
590
msgid "Relative adapter number for OSA cards."
590
596
msgid "Hardware Compatibility"
596
msgid "Many brand name products work without trouble on Linux. Moreover, hardware for Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems."
602
msgid "Many brand name products work without trouble on Linux. Moreover, hardware support in Linux is improving daily. However, Linux still does not run as many different types of hardware as some operating systems."
602
608
msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work."
608
614
msgid "Although some Windows-specific hardware can be made to run on Linux, doing so usually requires extra effort. In addition, Linux drivers for Windows-specific hardware are usually specific to one Linux kernel. Therefore, they can quickly become obsolete."
614
620
msgid "So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific."
620
626
msgid "You can check hardware compatibility by:"
626
632
msgid "Checking manufacturers' web sites for new drivers."
632
638
msgid "Looking at web sites or manuals for information about emulation. Lesser known brands can sometimes use the drivers or settings for better-known ones."
638
644
msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture."
644
650
msgid "Searching the Internet for other users' experiences."
650
656
msgid "Network Settings"
656
662
msgid "If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection — not a PPP connection), you should ask your network's system administrator for this information."
662
668
msgid "Your host name (you may be able to decide this on your own)."
668
674
msgid "Your domain name."
674
680
msgid "Your computer's IP address."
680
686
msgid "The netmask to use with your network."
686
692
msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway."
692
698
msgid "The system on your network that you should use as a DNS (Domain Name Service) server."
698
704
msgid "On the other hand, if your administrator tells you that a DHCP server is available and is recommended, then you don't need this information because the DHCP server will provide it directly to your computer during the installation process."
704
710
msgid "If you use a wireless network, you should also find out:"
710
716
msgid "ESSID of your wireless network."
716
722
msgid "WEP security key (if applicable)."
722
728
msgid "Meeting Minimum Hardware Requirements"
728
734
msgid "Once you have gathered information about your computer's hardware, check that your hardware will let you do the type of installation that you want to do."
734
740
msgid "Depending on your needs, you might manage with less than some of the recommended hardware listed in the table below. However, most users risk being frustrated if they ignore these suggestions."
740
msgid "A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server."
746
msgid "A Pentium 4, 1GHz system is the minimum recommended for a desktop systems."
746
752
msgid "A 68030 or better processor is recommended for m68k installs. You may get by with a little less drive space than shown."
752
msgid "Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For servers, a minimum 132-Mhz machine is recommended."
758
msgid "Any OldWorld or NewWorld PowerPC can serve well as a desktop system."
758
764
msgid "Recommended Minimum System Requirements"
764
770
msgid "Install Type"
770
msgid "<entry>RAM</entry>"
776
msgid "RAM (minimal)"
782
msgid "RAM (recommended)"
776
788
msgid "Hard Drive"
782
794
msgid "No desktop"
794
msgid "450 megabytes"
798
#: preparing.xml:709 preparing.xml:714
806
800
msgid "64 megabytes"
806
msgid "256 megabytes"
812
812
msgid "1 gigabyte"
824
msgid "128 megabytes"
836
msgid "Here is a sampling of some common Debian system configurations. You can also get an idea of the disk space used by related groups of programs by referring to <xref linkend=\"tasksel-size-list\"/>."
842
msgid "Standard Server"
824
msgid "512 megabytes"
846
834
#: preparing.xml:721
848
msgid "This is a small server profile, useful for a stripped down server which does not have a lot of niceties for shell users. It includes an FTP server, a web server, DNS, NIS, and POP. For these 100MB of disk space would suffice, and then you would need to add space for any data you serve up."
860
msgid "A standard desktop box, including the X window system, full desktop environments, sound, editors, etc. You'll need about 2GB using the standard desktop task, though it can be done in far less."
872
msgid "A more stripped-down user machine, without the X window system or X applications. Possibly suitable for a laptop or mobile computer. The size is around 140MB."
884
msgid "A desktop setup with all the development packages, such as Perl, C, C++, etc. Size is around 475MB. Assuming you are adding X11 and some additional packages for other uses, you should plan around 800MB for this type of machine."
890
msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 20MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 100MB for <filename>/var</filename>."
836
msgid "The actual minimum memory requirements are a lot less then the numbers listed in this table. Depending on the architecture, it is possible to install Debian with as little as 20MB (for s390) to 48MB (for i386 and amd64). The same goes for the disk space requirements, especially if you pick and choose which applications to install; see <xref linkend=\"tasksel-size-list\"/> for additional information on disk space requirements."
842
msgid "It is possible to run a graphical desktop environment on older or low-end systems, but in that case it is recommended to install a window manager that is less resource-hungry than those of the GNOME or KDE desktop environments; alternatives include <classname>xfce4</classname>, <classname>icewm</classname> and <classname>wmaker</classname>, but there are others to choose from."
848
msgid "It is practically impossible to give general memory or disk space requirements for server installations as those very much depend on what the server is to be used for."
854
msgid "Remember that these sizes don't include all the other materials which are usually to be found, such as user files, mail, and data. It is always best to be generous when considering the space for your own files and data."
860
msgid "Disk space required for the smooth operation of the &debian; system itself is taken into account in these recommended system requirements. Notably, the <filename>/var</filename> partition contains a lot of state information specific to Debian in addition to its regular contents, like logfiles. The <command>dpkg</command> files (with information on all installed packages) can easily consume 40MB. Also, <command>apt-get</command> puts downloaded packages here before they are installed. You should usually allocate at least 200MB for <filename>/var</filename>, and a lot more if you install a graphical desktop environment."
896
866
msgid "Pre-Partitioning for Multi-Boot Systems"
902
872
msgid "Partitioning your disk simply refers to the act of breaking up your disk into sections. Each section is then independent of the others. It's roughly equivalent to putting up walls inside a house; if you add furniture to one room it doesn't affect any other room."
908
878
msgid "Whenever this section talks about <quote>disks</quote> you should translate this into a DASD or VM minidisk in the &arch-title; world. Also a machine means an LPAR or VM guest in this case."
914
msgid "If you already have an operating system on your system <phrase arch=\"i386\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root."
920
msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"i386\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"m68k\">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes."
884
msgid "If you already have an operating system on your system <phrase arch=\"x86\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root."
890
msgid "You can find information about your current partition setup by using a partitioning tool for your current operating system<phrase arch=\"x86\">, such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"m68k\">, such as HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch=\"s390\">, such as the VM diskmap</phrase>. Partitioning tools always provide a way to show existing partitions without making changes."
926
896
msgid "In general, changing a partition with a file system already on it will destroy any information there. Thus you should always make backups before doing any repartitioning. Using the analogy of the house, you would probably want to move all the furniture out of the way before moving a wall or you risk destroying it."
932
902
msgid "FIXME: write about HP-UX disks?"
938
908
msgid "If your computer has more than one hard disk, you may want to dedicate one of the hard disks completely to Debian. If so, you don't need to partition that disk before booting the installation system; the installer's included partitioning program can handle the job nicely."
944
914
msgid "If your machine has only one hard disk, and you would like to completely replace the current operating system with &debian;, you also can wait to partition as part of the installation process (<xref linkend=\"partman\"/>), after you have booted the installation system. However this only works if you plan to boot the installer system from tapes, CD-ROM or files on a connected machine. Consider: if you boot from files placed on the hard disk, and then partition that same hard disk within the installation system, thus erasing the boot files, you'd better hope the installation is successful the first time around. At the least in this case, you should have some alternate means of reviving your machine like the original system's installation tapes or CDs."
950
920
msgid "If your machine already has multiple partitions, and enough space can be provided by deleting and replacing one or more of them, then you too can wait and use the Debian installer's partitioning program. You should still read through the material below, because there may be special circumstances like the order of the existing partitions within the partition map, that force you to partition before installing anyway."
956
926
msgid "If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, you can wait and use Debian installer's partitioning program to resize the filesystem."
962
932
msgid "If none of the above apply, you'll need to partition your hard disk before starting the installation to create partition-able space for Debian. If some of the partitions will be owned by other operating systems, you should create those partitions using native operating system partitioning programs. We recommend that you do <emphasis>not</emphasis> attempt to create partitions for &debian; using another operating system's tools. Instead, you should just create the native operating system's partitions you will want to retain."
968
938
msgid "If you are going to install more than one operating system on the same machine, you should install all other system(s) before proceeding with Linux installation. Windows and other OS installations may destroy your ability to start Linux, or encourage you to reformat non-native partitions."
974
944
msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble."
980
950
msgid "In order for OpenFirmware to automatically boot &debian; the Linux partitions should appear before all other partitions on the disk, especially MacOS boot partitions. This should be kept in mind when pre-partitioning; you should create a Linux placeholder partition to come <emphasis>before</emphasis> the other bootable partitions on the disk. (The small partitions dedicated to Apple disk drivers are not bootable.) You can delete the placeholder with the Linux partition tools later during the actual install, and replace it with Linux partitions."
986
956
msgid "If you currently have one hard disk with one partition (a common setup for desktop computers), and you want to multi-boot the native operating system and Debian, you will need to:"
992
962
msgid "Back up everything on the computer."
998
968
msgid "Boot from the native operating system installer media such as CD-ROM or tapes. <phrase arch=\"powerpc\">When booting from a MacOS CD, hold the <keycap>c</keycap> key while booting to force the CD to become the active MacOS system.</phrase>"
1002
#: preparing.xml:950
1004
974
msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;."
1008
#: preparing.xml:957
1010
980
msgid "Install the native operating system on its new partition."
1014
#: preparing.xml:962
1016
986
msgid "Boot back into the native system to verify everything's OK, and to download the Debian installer boot files."
1020
#: preparing.xml:968
1022
992
msgid "Boot the Debian installer to continue installing Debian."
1026
#: preparing.xml:982
1028
998
msgid "Partitioning in Tru64 UNIX"
1032
#: preparing.xml:983
1002
#: preparing.xml:970
1034
1004
msgid "Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</quote>, which allows for up to eight partitions per disk drive. The partitions are numbered <quote>1</quote> through to <quote>8</quote> in Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be called <filename>sda5</filename> in Linux."
1008
#: preparing.xml:982
1010
msgid "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be used from Tru64, the <quote>c</quote> partition is required to span the entire disk (thus overlapping all other non-empty partitions). Under Linux this makes <filename>sda3</filename> identical to <filename>sda</filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so on). However, the partman partitioning tool used by &d-i; cannot handle overlapping partitions at present. As a result, it is currently not recommended to share disks between Tru64 and Debian. Partitions on Tru64 disks can be mounted under Debian after installation has been completed."
1038
1014
#: preparing.xml:995
1040
msgid "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be used from Tru64, the <quote>c</quote> partition is required to span the entire disk (thus overlapping all other non-empty partitions). Under Linux this makes <filename>sda3</filename> identical to <filename>sda</filename> (<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so on). However, the partman partitioning tool used by &d-i; cannot handle overlapping partitions at present. As a result, it is currently not recommended to share disks between Tru64 and Debian. Partitions on Tru64 disks can be mounted under Debian after installation has been completed."
1044
#: preparing.xml:1008
1046
1016
msgid "Another conventional requirement is for the <quote>a</quote> partition to start from the beginning of the disk, so that it always includes the boot block with the disk label. If you intend to boot Debian from that disk, you need to size it at least 2MB to fit aboot and perhaps a kernel. Note that this partition is only required for compatibility; you must not put a file system onto it, or you'll destroy data."
1050
#: preparing.xml:1017
1020
#: preparing.xml:1004
1052
1022
msgid "It is possible, and indeed quite reasonable, to share a swap partition between UNIX and Linux. In this case it will be needed to do a <command>mkswap</command> on that partition every time the system is rebooted from UNIX into Linux, as UNIX will damage the swap signature. You may want to run <command>mkswap</command> from the Linux start-up scripts before adding swap space with <command>swapon -a</command>."
1056
#: preparing.xml:1026
1026
#: preparing.xml:1013
1058
1028
msgid "If you want to mount UNIX partitions under Linux, note that Digital UNIX can use two different file system types, UFS and AdvFS, of which Linux only understands the former."
1062
#: preparing.xml:1035
1032
#: preparing.xml:1022
1064
1034
msgid "Partitioning in Windows NT"
1038
#: preparing.xml:1024
1040
msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information."
1068
1044
#: preparing.xml:1037
1070
msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer you to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information."
1074
#: preparing.xml:1050
1076
1046
msgid "If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you will need a (small) FAT partition for MILO. 5 MB is quite sufficient. If Windows NT is installed, its 6 MB bootstrap partition can be employed for this purpose. Debian &releasename; does not support installing MILO. If you already have MILO installed on your system, or install MILO from other media, Debian can still be booted from ARC."
1080
#: preparing.xml:1067
1050
#: preparing.xml:1054
1082
1052
msgid "Partitioning From DOS or Windows"
1086
#: preparing.xml:1068
1056
#: preparing.xml:1055
1088
1058
msgid "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."
1092
#: preparing.xml:1076
1062
#: preparing.xml:1063
1094
msgid "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."
1064
msgid "But if you have a large IDE disk, and are not using LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), or 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 disk (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition."
1098
#: preparing.xml:1090
1068
#: preparing.xml:1077
1100
1070
msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2"
1104
#: preparing.xml:1093
1074
#: preparing.xml:1080
1106
msgid "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 <menuchoice> <guimenuitem>Manually edit partition table</guimenuitem> </menuchoice>, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below."
1076
msgid "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 and when you get to the partitioning step, select the option for <menuchoice> <guimenuitem>Manual</guimenuitem> </menuchoice> partitioning, select the partition to resize, and specify its new size. So in most cases you should not need to use the method described below."
1110
#: preparing.xml:1105
1080
#: preparing.xml:1092
1112
1082
msgid "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."
1116
#: preparing.xml:1114
1086
#: preparing.xml:1101
1118
1088
msgid "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."
1092
#: preparing.xml:1110
1094
msgid "The first thing needed is a copy of <command>fips</command> which is available in the <filename>tools/</filename> directory on your nearest Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can be created using the command <filename>sys a:</filename> under DOS. <command>fips</command> 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 <emphasis>before</emphasis> you defragment the disk."
1122
1098
#: preparing.xml:1123
1124
msgid "The first thing needed is a copy of <command>fips</command> which is available in the <filename>tools/</filename> directory on your nearest Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> to a bootable floppy. A bootable floppy can be created using the command <filename>sys a:</filename> under DOS. <command>fips</command> 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 <emphasis>before</emphasis> you defragment the disk."
1128
#: preparing.xml:1136
1130
1100
msgid "The next thing needed is to move all the data to the beginning of the partition. <command>defrag</command>, which comes standard with DOS 6.0 and later, can easily do the job. See the <command>fips</command> documentation for a list of other software that may do the trick. Note that if you have Windows 9x, you must run <command>defrag</command> from there, since DOS doesn't understand VFAT, which is used to support for long filenames, used in Windows 95 and higher."
1134
#: preparing.xml:1146
1104
#: preparing.xml:1133
1136
1106
msgid "After running the defragmenter (which can take a while on a large disk), reboot with the <command>fips</command> disk you created in the floppy drive. Simply type <filename>a:\\fips</filename> and follow the directions."
1140
#: preparing.xml:1152
1110
#: preparing.xml:1139
1142
1112
msgid "Note that there are many other partition managers out there, in case <command>fips</command> doesn't do the trick for you."
1146
#: preparing.xml:1160
1116
#: preparing.xml:1147
1148
1118
msgid "Partitioning for DOS"
1152
#: preparing.xml:1162
1122
#: preparing.xml:1149
1154
1124
msgid "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 <command>scandisk</command>, or other weird errors in DOS or Windows."
1158
#: preparing.xml:1170
1128
#: preparing.xml:1157
1160
1130
msgid "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 <command>format</command> command by executing the following command from Linux:"
1164
#: preparing.xml:1177
1134
#: preparing.xml:1164
1166
1136
msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4"
1170
#: preparing.xml:1188
1140
#: preparing.xml:1175
1172
1142
msgid "Partitioning in AmigaOS"
1176
#: preparing.xml:1189
1146
#: preparing.xml:1176
1178
1148
msgid "If you are running AmigaOS, you can use the <command>HDToolBox</command> program to adjust your native partitions prior to installation."
1182
#: preparing.xml:1197
1152
#: preparing.xml:1184
1184
1154
msgid "Partitioning in Atari TOS"
1188
#: preparing.xml:1198
1158
#: preparing.xml:1185
1190
1160
msgid "Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for data and <quote>SWP</quote> for swap partitions. If using the low memory installation method, a small Minix partition is also needed (about 2 MB), for which the partition ID is <quote>MNX</quote>. Failure to set the appropriate partition IDs not only prevents the Debian installation process from recognizing the partitions, but also results in TOS attempting to use the Linux partitions, which confuses the hard disk driver and renders the whole disk inaccessible."
1194
#: preparing.xml:1209
1164
#: preparing.xml:1196
1196
1166
msgid "There are a multitude of third party partitioning tools available (the Atari <command>harddisk</command> utility doesn't permit changing the partition ID); this manual cannot give detailed descriptions for all of them. The following description covers <command>SCSITool</command> (from Hard+Soft GmBH)."
1200
#: preparing.xml:1218
1170
#: preparing.xml:1205
1202
1172
msgid "Start <command>SCSITool</command> and select the disk you want to partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)."
1206
#: preparing.xml:1224
1176
#: preparing.xml:1211
1208
1178
msgid "From the <guimenu>Partition</guimenu> menu, select either <guimenuitem>New</guimenuitem> to add new partitions or change the existing partition sizes, or <guimenuitem>Change</guimenuitem> to change one specific partition. Unless you have already created partitions with the right sizes and only want to change the partition ID, <guimenuitem>New</guimenuitem> is probably the best choice."
1212
#: preparing.xml:1234
1182
#: preparing.xml:1221
1214
1184
msgid "For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</guilabel> in the dialog box prompting the initial settings. The next window shows a list of existing partitions which you can adjust using the scroll buttons, or by clicking in the bar graphs. The first column in the partition list is the partition type; just click on the text field to edit it. When you are finished changing partition settings, save the changes by leaving the window with the <guibutton>OK</guibutton> button."
1218
#: preparing.xml:1246
1188
#: preparing.xml:1233
1220
1190
msgid "For the <guimenuitem>Change</guimenuitem> option, select the partition to change in the selection list, and select <guilabel>other systems</guilabel> in the dialog box. The next window lists detailed information about the location of this partition, and lets you change the partition ID. Save changes by leaving the window with the <guibutton>OK</guibutton> button."
1224
#: preparing.xml:1256
1194
#: preparing.xml:1243
1226
1196
msgid "Write down the Linux names for each of the partitions you created or changed for use with Linux — see <xref linkend=\"device-names\"/>."
1230
#: preparing.xml:1262
1200
#: preparing.xml:1249
1232
1202
msgid "Quit <command>SCSITool</command> using the <guimenuitem>Quit</guimenuitem> item from the <guimenu>File</guimenu> menu. The computer will reboot to make sure the changed partition table is used by TOS. If you changed any TOS/GEM partitions, they will be invalidated and have to be reinitialized (we told you to back up everything on the disk, didn't we?)."
1236
#: preparing.xml:1274
1206
#: preparing.xml:1261
1238
1208
msgid "There is a partitioning tool for Linux/m68k called <command>atari-fdisk</command> in the installation system, but for now we recommend you partition your disk using a TOS partition editor or some disk tool. If your partition editor doesn't have an option to edit the partition type, you can do this crucial step at a later stage (from the booted temporary install RAMdisk). <command>SCSITool</command> is only one of the partition editors we know of which supports selection of arbitrary partition types. There may be others; select the tool that suits your needs."
1242
#: preparing.xml:1289
1212
#: preparing.xml:1276
1244
1214
msgid "Partitioning in MacOS"
1248
#: preparing.xml:1290
1218
#: preparing.xml:1277
1250
1220
msgid "Partitioning tools for Macintosh tested include <command>pdisk</command>, <command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 (FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</command> (Tim Endres, GPL). Full versions are required for <command>HDT</command> and <command>SilverLining</command>. The Apple tool requires a patch in order to recognize third-party disks (a description on how to patch <command>HD SC Setup</command> using <command>ResEdit</command> can be found at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></ulink>)."
1254
#: preparing.xml:1301
1224
#: preparing.xml:1288
1256
msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available from the MkLinux FTP server."
1226
msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available for download from <ulink url=\"http://homepage.mac.com/alk/downloads/pdisk.sit.hqx\">Alsoft</ulink>."
1260
#: preparing.xml:1317
1230
#: preparing.xml:1304
1262
1232
msgid "Partitioning from SunOS"
1266
#: preparing.xml:1319
1236
#: preparing.xml:1306
1268
msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. Just make sure you leave room for the Debian root partition within the first 1GB area of the boot disk. You can also place the kernel image on a UFS partition if that is easier than putting the root partition there. SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS (SunOS), romfs and iso9660 (CDROM) partitions."
1238
msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. SILO supports booting Linux and SunOS from any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions."
1272
#: preparing.xml:1334
1242
#: preparing.xml:1318
1274
1244
msgid "Partitioning from Linux or another OS"
1278
#: preparing.xml:1336
1248
#: preparing.xml:1320
1280
1250
msgid "Whatever system you are using to partition, make sure you create a <quote>Sun disk label</quote> on your boot disk. This is the only kind of partition scheme that the OpenBoot PROM understands, and so it's the only scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</keycap> key is used to create Sun disk labels. You only need to do this on drives that do not already have a Sun disk label. If you are using a drive that was previously formatted using a PC (or other architecture) you must create a new disk label, or problems with the disk geometry will most likely occur."
1284
#: preparing.xml:1348
1254
#: preparing.xml:1332
1286
1256
msgid "You will probably be using <command>SILO</command> as your boot loader (the small program which runs the operating system kernel). <command>SILO</command> has certain requirements for partition sizes and location; see <xref linkend=\"partitioning\"/>."
1290
#: preparing.xml:1363
1260
#: preparing.xml:1347
1292
1262
msgid "MacOS/OSX Partitioning"
1296
#: preparing.xml:1365
1266
#: preparing.xml:1349
1298
1268
msgid "The <application>Apple Drive Setup</application> application can be found in the <filename>Utilities</filename> folder on the MacOS CD. It will not adjust existing partitions; it is limited to partitioning the entire disk at once. The disk driver partitions don't show up in <application>Drive Setup</application>."
1302
#: preparing.xml:1372
1272
#: preparing.xml:1356
1304
1274
msgid "Remember to create a placeholder partition for GNU/Linux, preferably positioned first in the disk layout. it doesn't matter what type it is, it will be deleted and replaced later inside the &debian; installer."
1308
#: preparing.xml:1378
1278
#: preparing.xml:1362
1310
1280
msgid "If you are planning to install both MacOS 9 and OS X, it is best to create separate partitions for OS 9 and OS X. If they are installed on the same partition, <application>Startup Disk</application> (and reboot) must be used to select between the two; the choice between the two systems can't be made at boot time. With separate partitions, separate options for OS 9 and OS X will appear when holding the <keycap>option</keycap> key at boot time, and separate options can be installed in the <application>yaboot</application> boot menu as well. Also, Startup Disk will de-bless all other mountable partitions, which can affect GNU/Linux booting. Both OS 9 and OS X partitions will be accessible from either OS 9 or OS X."
1314
#: preparing.xml:1391
1284
#: preparing.xml:1375
1316
1286
msgid "GNU/Linux is unable to access information on UFS partitions, but does support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two types for its boot partition. MacOS 9 can be installed on either HFS (aka MacOS Standard) or HFS+. To share information between the MacOS and GNU/Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT partitions are supported by both MacOS and Linux."
1320
#: preparing.xml:1411
1290
#: preparing.xml:1395
1322
1292
msgid "Pre-Installation Hardware and Operating System Setup"
1326
#: preparing.xml:1412
1296
#: preparing.xml:1396
1328
1298
msgid "This section will walk you through pre-installation hardware setup, if any, that you will need to do prior to installing Debian. Generally, this involves checking and possibly changing firmware settings for your system. The <quote>firmware</quote> is the core software used by the hardware; it is most critically invoked during the bootstrap process (after power-up). Known hardware issues affecting the reliability of &debian; on your system are also highlighted."
1332
#: preparing.xml:1429
1302
#: preparing.xml:1418
1334
1304
msgid "Invoking the BIOS Set-Up Menu"
1338
#: preparing.xml:1431
1308
#: preparing.xml:1420
1340
1310
msgid "BIOS provides the basic functions needed to boot your machine to allow your operating system to access your hardware. Your system probably provides a BIOS set-up menu, which is used to configure the BIOS. Before installing, you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not doing so can lead to intermittent crashes or an inability to install Debian."
1344
#: preparing.xml:1440
1314
#: preparing.xml:1429
1346
1316
msgid "The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></ulink>, answering the question, <quote>How do I enter the CMOS configuration menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) configuration menu depends on who wrote your BIOS software:"
1350
#: preparing.xml:1454
1320
#: preparing.xml:1443
1352
1322
msgid "AMI BIOS"
1356
#: preparing.xml:1455
1326
#: preparing.xml:1444
1358
1328
msgid "<keycap>Delete</keycap> key during the POST (power on self test)"
1362
#: preparing.xml:1463
1332
#: preparing.xml:1452
1364
1334
msgid "Award BIOS"
1368
#: preparing.xml:1464
1338
#: preparing.xml:1453
1370
1340
msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST"
1374
#: preparing.xml:1473
1344
#: preparing.xml:1462
1376
1346
msgid "DTK BIOS"
1380
#: preparing.xml:1474
1350
#: preparing.xml:1463
1382
1352
msgid "<keycap>Esc</keycap> key during the POST"
1386
#: preparing.xml:1481
1356
#: preparing.xml:1470
1388
1358
msgid "IBM PS/2 BIOS"
1392
#: preparing.xml:1482
1362
#: preparing.xml:1471
1394
1364
msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> </keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Delete</keycap> </keycombo>"
1398
#: preparing.xml:1496
1368
#: preparing.xml:1485
1400
1370
msgid "Phoenix BIOS"
1404
#: preparing.xml:1497
1374
#: preparing.xml:1486
1406
1376
msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</keycap> </keycombo> or <keycap>F1</keycap>"
1410
#: preparing.xml:1513
1380
#: preparing.xml:1502
1412
1382
msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>."
1416
#: preparing.xml:1518
1386
#: preparing.xml:1507
1418
1388
msgid "Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. They require a software CMOS setup program. If you don't have the Installation and/or Diagnostics diskette for your machine, you can try using a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></ulink>."
1422
#: preparing.xml:1529 preparing.xml:1873
1392
#: preparing.xml:1518 preparing.xml:1862
1424
1394
msgid "Boot Device Selection"
1398
#: preparing.xml:1520
1400
msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian."
1428
1404
#: preparing.xml:1531
1430
msgid "Many BIOS set-up menus allow you to select the devices that will be used to bootstrap the system. Set this to look for a bootable operating system on <filename>A:</filename> (the first floppy disk), then optionally the first CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:</filename>), and then from <filename>C:</filename> (the first hard disk). This setting enables you to boot from either a floppy disk or a CD-ROM, which are the two most common boot devices used to install Debian."
1434
#: preparing.xml:1542
1436
1406
msgid "If you have a newer SCSI controller and you have a CD-ROM device attached to it, you are usually able to boot from the CD-ROM. All you have to do is enable booting from a CD-ROM in the SCSI-BIOS of your controller."
1440
#: preparing.xml:1549
1410
#: preparing.xml:1538
1442
1412
msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device."
1446
#: preparing.xml:1557
1416
#: preparing.xml:1546
1448
1418
msgid "Here are some details about how to set the boot order. Remember to reset the boot order after Linux is installed, so that you restart your machine from the hard drive."
1452
#: preparing.xml:1566
1422
#: preparing.xml:1555
1454
1424
msgid "Changing the Boot Order on IDE Computers"
1458
#: preparing.xml:1569
1428
#: preparing.xml:1558
1460
1430
msgid "As your computer starts, press the keys to enter the BIOS utility. Often, it is the <keycap>Delete</keycap> key. However, consult the hardware documentation for the exact keystrokes."
1464
#: preparing.xml:1576
1434
#: preparing.xml:1565
1466
1436
msgid "Find the boot sequence in the setup utility. Its location depends on your BIOS, but you are looking for a field that lists drives."
1470
#: preparing.xml:1581
1440
#: preparing.xml:1570
1472
1442
msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom."
1476
#: preparing.xml:1586
1446
#: preparing.xml:1575
1478
1448
msgid "C is the hard drive, and A is the floppy drive."
1482
#: preparing.xml:1592
1452
#: preparing.xml:1581
1484
1454
msgid "Change the boot sequence setting so that the CD-ROM or the floppy is first. Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys cycle through the possible choices."
1488
#: preparing.xml:1600
1458
#: preparing.xml:1589
1490
1460
msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer."
1494
#: preparing.xml:1610
1464
#: preparing.xml:1599
1496
1466
msgid "Changing the Boot Order on SCSI Computers"
1500
#: preparing.xml:1614
1470
#: preparing.xml:1603
1502
1472
msgid "As your computer starts, press the keys to enter the SCSI setup utility."
1506
#: preparing.xml:1619
1476
#: preparing.xml:1608
1508
1478
msgid "You can start the SCSI setup utility after the memory check and the message about how to start the BIOS utility displays when you start your computer."
1512
#: preparing.xml:1625
1482
#: preparing.xml:1614
1514
1484
msgid "The keystrokes you need depend on the utility. Often, it is <keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, consult your hardware documentation for the exact keystrokes."
1518
#: preparing.xml:1633
1488
#: preparing.xml:1622
1520
1490
msgid "Find the utility for changing the boot order."
1524
#: preparing.xml:1638
1494
#: preparing.xml:1627
1526
1496
msgid "Set the utility so that the SCSI ID of the CD drive is first on the list."
1530
#: preparing.xml:1644
1500
#: preparing.xml:1633
1532
1502
msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer. Often, you must press <keycap>F10</keycap>."
1536
#: preparing.xml:1658
1506
#: preparing.xml:1647
1538
1508
msgid "Miscellaneous BIOS Settings"
1542
#: preparing.xml:1660
1512
#: preparing.xml:1649
1544
1514
msgid "CD-ROM Settings"
1548
#: preparing.xml:1661
1518
#: preparing.xml:1650
1550
1520
msgid "Some BIOS systems (such as Award BIOS) allow you to automatically set the CD speed. You should avoid that, and instead set it to, say, the lowest speed. If you get <userinput>seek failed</userinput> error messages, this may be your problem."
1554
#: preparing.xml:1671
1524
#: preparing.xml:1660
1556
1526
msgid "Extended vs. Expanded Memory"
1560
#: preparing.xml:1672
1530
#: preparing.xml:1661
1562
1532
msgid "If your system provides both ex<emphasis>ten</emphasis>ded and ex<emphasis>pan</emphasis>ded memory, set it so that there is as much extended and as little expanded memory as possible. Linux requires extended memory and cannot use expanded memory."
1566
#: preparing.xml:1682
1536
#: preparing.xml:1671
1568
1538
msgid "Virus Protection"
1572
#: preparing.xml:1683
1542
#: preparing.xml:1672
1574
1544
msgid "Disable any virus-warning features your BIOS may provide. If you have a virus-protection board or other special hardware, make sure it is disabled or physically removed while running GNU/Linux. These aren't compatible with GNU/Linux; moreover, due to the file system permissions and protected memory of the Linux kernel, viruses are almost unheard of<footnote> <para> After installation you can enable Boot Sector protection if you want. This offers no additional security in Linux but if you also run Windows it may prevent a catastrophe. There is no need to tamper with the Master Boot Record (MBR) after the boot manager has been set up. </para> </footnote>."
1578
#: preparing.xml:1704
1548
#: preparing.xml:1693
1580
1550
msgid "Shadow RAM"
1584
#: preparing.xml:1705
1554
#: preparing.xml:1694
1586
1556
msgid "Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS caching. You may see settings for <quote>Video BIOS Shadow</quote>, <quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your motherboard and on some of the controller cards. Linux does not use these ROMs once it has booted because it provides its own faster 32-bit software in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may make some of it available for programs to use as normal memory. Leaving the shadow RAM enabled may interfere with Linux access to hardware devices."
1590
#: preparing.xml:1722
1560
#: preparing.xml:1711
1592
1562
msgid "Memory Hole"
1596
#: preparing.xml:1723
1566
#: preparing.xml:1712
1598
1568
msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM."
1602
#: preparing.xml:1729
1572
#: preparing.xml:1718
1604
1574
msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it."
1608
#: preparing.xml:1745
1578
#: preparing.xml:1734
1610
1580
msgid "Advanced Power Management"
1614
#: preparing.xml:1746
1584
#: preparing.xml:1735
1616
1586
msgid "If your motherboard provides Advanced Power Management (APM), configure it so that power management is controlled by APM. Disable the doze, standby, suspend, nap, and sleep modes, and disable the hard disk's power-down timer. Linux can take over control of these modes, and can do a better job of power-management than the BIOS."
1620
#: preparing.xml:1764
1590
#: preparing.xml:1753
1622
1592
msgid "Firmware Revisions and Existing OS Setup"
1626
#: preparing.xml:1766
1596
#: preparing.xml:1755
1628
1598
msgid "&arch-title; machines are generally self-configuring and do not require firmware configuration. However, you should make sure that you have the appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 is recommended because version 7.0.1 contains a bug in the video drivers preventing the boot loader from deactivating the video interrupts, resulting in a boot hang. On the BVM VMEbus systems you should make sure you are using BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as standard on the BVM systems but are available from BVM on request free of charge."
1632
#: preparing.xml:1789
1602
#: preparing.xml:1778
1634
1604
msgid "Invoking OpenFirmware"
1638
#: preparing.xml:1790
1608
#: preparing.xml:1779
1640
1610
msgid "There is normally no need to set up the BIOS (called OpenFirmware) on &arch-title; systems. PReP and CHRP are equipped with OpenFirmware, but unfortunately, the means you use to invoke it vary from manufacturer to manufacturer. You'll have to consult the hardware documentation which came with your machine."
1644
#: preparing.xml:1798
1614
#: preparing.xml:1787
1646
1616
msgid "On &arch-title; Macintoshes, you invoke OpenFirmware with <keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check for these keystrokes after the chime, but the exact timing varies from model to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more hints."
1650
#: preparing.xml:1807
1620
#: preparing.xml:1796
1653
1623
"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
added
removed
po/pot/preparing.pot
