# SOME DESCRIPTIVE TITLE. # Copyright (C) YEAR Free Software Foundation, Inc. # FIRST AUTHOR , YEAR. # #, fuzzy msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: http://bugs.kde.org\n" "POT-Creation-Date: 2006-03-02 09:59+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: ENCODING\n" #. Tag: title #: preparing.xml:5 #, no-c-format msgid "Before Installing &debian;" msgstr "" #. Tag: para #: preparing.xml:6 #, no-c-format msgid "" "This chapter deals with the preparation for installing Debian before you " "even boot the installer. This includes backing up your data, gathering " "information about your hardware, and locating any necessary information." msgstr "" #. Tag: title #: preparing.xml:19 #, no-c-format msgid "Overview of the Installation Process" msgstr "" #. Tag: para #: preparing.xml:20 #, no-c-format msgid "" "First, just a note about re-installations. With Debian, a circumstance that " "will require a complete re-installation of your system is very rare; perhaps " "mechanical failure of the hard disk would be the most common case." msgstr "" #. Tag: para #: preparing.xml:27 #, no-c-format msgid "" "Many common operating systems may require a complete installation to be " "performed when critical failures take place or for upgrades to new OS " "versions. Even if a completely new installation isn't required, often the " "programs you use must be re-installed to operate properly in the new OS." msgstr "" #. Tag: para #: preparing.xml:35 #, no-c-format msgid "" "Under &debian;, it is much more likely that your OS can be repaired rather " "than replaced if things go wrong. Upgrades never require a wholesale " "installation; you can always upgrade in-place. And the programs are almost " "always compatible with successive OS releases. If a new program version " "requires newer supporting software, the Debian packaging system ensures that " "all the necessary software is automatically identified and installed. The " "point is, much effort has been put into avoiding the need for re-" "installation, so think of it as your very last option. The installer is " "not designed to re-install over an existing system." msgstr "" #. Tag: para #: preparing.xml:48 #, no-c-format msgid "" "Here's a road map for the steps you will take during the installation " "process." msgstr "" #. Tag: para #: preparing.xml:56 #, no-c-format msgid "" "Back up any existing data or documents on the hard disk where you plan to " "install." msgstr "" #. Tag: para #: preparing.xml:62 #, no-c-format msgid "" "Gather information about your computer and any needed documentation, before " "starting the installation." msgstr "" #. Tag: para #: preparing.xml:68 #, no-c-format msgid "Create partition-able space for Debian on your hard disk." msgstr "" #. Tag: para #: preparing.xml:73 #, no-c-format msgid "" "Locate and/or download the installer software and any specialized driver " "files your machine requires (except Debian CD users)." msgstr "" #. Tag: para #: preparing.xml:79 #, no-c-format msgid "" "Set up boot tapes/floppies/USB sticks, or place boot files (most Debian CD " "users can boot from one of the CDs)." msgstr "" #. Tag: para #: preparing.xml:85 #, no-c-format msgid "Boot the installation system." msgstr "" #. Tag: para #: preparing.xml:90 #, no-c-format msgid "Select installation language." msgstr "" #. Tag: para #: preparing.xml:95 #, no-c-format msgid "Activate the ethernet network connection, if available." msgstr "" #. Tag: para #: preparing.xml:101 #, no-c-format msgid "Configure one network interface." msgstr "" #. Tag: para #: preparing.xml:106 #, no-c-format msgid "Open a ssh connection to the new system." msgstr "" #. Tag: para #: preparing.xml:111 #, no-c-format msgid "Attach one or more DASDs (Direct Access Storage Device)." msgstr "" #. Tag: para #: preparing.xml:117 #, no-c-format msgid "Create and mount the partitions on which Debian will be installed." msgstr "" #. Tag: para #: preparing.xml:122 #, no-c-format msgid "" "Watch the automatic download/install/setup of the base system." msgstr "" #. Tag: para #: preparing.xml:128 #, no-c-format msgid "" "Install a boot loader which can start up &debian; and/" "or your existing system." msgstr "" #. Tag: para #: preparing.xml:134 #, no-c-format msgid "Load the newly installed system for the first time." msgstr "" #. Tag: para #: preparing.xml:141 #, no-c-format 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:" msgstr "" #. Tag: para #: preparing.xml:147 #, no-c-format msgid "" "The installer software, debian-installer, is the " "primary concern of this manual. It detects hardware and loads appropriate " "drivers, uses dhcp-client to set up the network " "connection, and runs debootstrap to install the base " "system packages. Many more actors play smaller parts in this process, but " "debian-installer has completed its task when you load " "the new system for the first time." msgstr "" #. Tag: para #: preparing.xml:157 #, no-c-format msgid "" "To tune the system to your needs, tasksel allows you " "to choose to install various predefined bundles of software like a Web " "server or a Desktop environment." msgstr "" #. Tag: para #: preparing.xml:163 #, no-c-format msgid "" "When debian-installer 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 tasksel. 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." msgstr "" #. Tag: para #: preparing.xml:172 #, no-c-format msgid "" "Just be aware that the X system is completely separate from " "debian-installer, and in fact is much more " "complicated. Installation and trouble shooting of the X window installation " "is not within the scope of this manual." msgstr "" #. Tag: title #: preparing.xml:188 #, no-c-format msgid "Back Up Your Existing Data!" msgstr "" #. Tag: para #: preparing.xml:189 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:202 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:213 #, no-c-format 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 " "BVMBug or 16xBug boot ROMs." msgstr "" #. Tag: title #: preparing.xml:231 #, no-c-format msgid "Information You Will Need" msgstr "" #. Tag: title #: preparing.xml:234 #, no-c-format msgid "Documentation" msgstr "" #. Tag: title #: preparing.xml:237 #, no-c-format msgid "Installation Manual" msgstr "" #. Tag: para #: preparing.xml:239 #, no-c-format msgid "This document you are now reading, in plain ASCII, HTML or PDF format." msgstr "" #. Tag: itemizedlist #: preparing.xml:245 #, no-c-format msgid "&list-install-manual-files;" msgstr "" #. Tag: para #: preparing.xml:251 #, no-c-format msgid "" "The document you are now reading, which is the official version of the " "Installation Guide for the &releasename; release of Debian; available in " "various formats and " "translations." msgstr "" #. Tag: para #: preparing.xml:260 #, no-c-format msgid "" "The document you are now reading, which is a development version of the " "Installation Guide for the next release of Debian; available in various formats and translations." msgstr "" #. Tag: title #: preparing.xml:272 #, no-c-format msgid "Hardware documentation" msgstr "" #. Tag: para #: preparing.xml:273 #, no-c-format msgid "" "Often contains useful information on configuring or using your hardware." msgstr "" #. Tag: ulink #: preparing.xml:284 #, no-c-format msgid "Linux Hardware Compatibility HOWTO" msgstr "" #. Tag: ulink #: preparing.xml:290 #, no-c-format msgid "Linux/m68k FAQ" msgstr "" #. Tag: ulink #: preparing.xml:296 #, no-c-format msgid "Linux/Alpha FAQ" msgstr "" #. Tag: ulink #: preparing.xml:302 #, no-c-format msgid "Linux for SPARC Processors FAQ" msgstr "" #. Tag: ulink #: preparing.xml:308 #, no-c-format msgid "Linux/Mips website" msgstr "" #. Tag: title #: preparing.xml:317 #, no-c-format msgid "&arch-title; Hardware References" msgstr "" #. Tag: para #: preparing.xml:318 #, no-c-format msgid "" "Installation instructions and device drivers (DASD, XPRAM, Console, tape, " "z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4" msgstr "" #. Tag: ulink #: preparing.xml:330 #, no-c-format msgid "Device Drivers and Installation Commands" msgstr "" #. Tag: para #: preparing.xml:335 #, no-c-format msgid "" "IBM Redbook describing how Linux can be combined with z/VM on zSeries and " "&arch-title; hardware." msgstr "" #. Tag: ulink #: preparing.xml:345 #, no-c-format msgid "Linux for &arch-title;" msgstr "" #. Tag: para #: preparing.xml:351 #, no-c-format 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." msgstr "" #. Tag: ulink #: preparing.xml:362 #, no-c-format msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" msgstr "" #. Tag: title #: preparing.xml:372 #, no-c-format msgid "Finding Sources of Hardware Information" msgstr "" #. Tag: para #: preparing.xml:373 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:379 #, no-c-format msgid "Hardware information can be gathered from:" msgstr "" #. Tag: para #: preparing.xml:386 #, no-c-format msgid "The manuals that come with each piece of hardware." msgstr "" #. Tag: para #: preparing.xml:391 #, no-c-format 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 Delete key." msgstr "" #. Tag: para #: preparing.xml:398 #, no-c-format msgid "The cases and boxes for each piece of hardware." msgstr "" #. Tag: para #: preparing.xml:404 #, no-c-format msgid "The System window in the Windows Control Panel." msgstr "" #. Tag: para #: preparing.xml:410 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:417 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:429 #, no-c-format msgid "Hardware Information Needed for an Install" msgstr "" #. Tag: entry #: preparing.xml:433 #, no-c-format msgid "Hardware" msgstr "" #. Tag: entry #: preparing.xml:433 #, no-c-format msgid "Information You Might Need" msgstr "" #. Tag: entry #: preparing.xml:439 #, no-c-format msgid "Hard Drives" msgstr "" #. Tag: entry #: preparing.xml:440 #, no-c-format msgid "How many you have." msgstr "" #. Tag: entry #: preparing.xml:442 #, no-c-format msgid "Their order on the system." msgstr "" #. Tag: entry #: preparing.xml:444 #, no-c-format msgid "Whether IDE or SCSI (most computers are IDE)." msgstr "" #. Tag: entry #: preparing.xml:447 #, no-c-format msgid "Whether IDE or SCSI (most m68k computers are SCSI)." msgstr "" #. Tag: entry #: preparing.xml:449 preparing.xml:501 #, no-c-format msgid "Available free space." msgstr "" #. Tag: entry #: preparing.xml:450 #, no-c-format msgid "Partitions." msgstr "" #. Tag: entry #: preparing.xml:452 #, no-c-format msgid "Partitions where other operating systems are installed." msgstr "" #. Tag: entry #: preparing.xml:456 #, no-c-format msgid "Monitor" msgstr "" #. Tag: entry #: preparing.xml:457 preparing.xml:477 preparing.xml:483 preparing.xml:489 #, no-c-format msgid "Model and manufacturer." msgstr "" #. Tag: entry #: preparing.xml:459 #, no-c-format msgid "Resolutions supported." msgstr "" #. Tag: entry #: preparing.xml:460 #, no-c-format msgid "Horizontal refresh rate." msgstr "" #. Tag: entry #: preparing.xml:461 #, no-c-format msgid "Vertical refresh rate." msgstr "" #. Tag: entry #: preparing.xml:463 #, no-c-format msgid "Color depth (number of colors) supported." msgstr "" #. Tag: entry #: preparing.xml:465 #, no-c-format msgid "Screen size." msgstr "" #. Tag: entry #: preparing.xml:468 #, no-c-format msgid "Mouse" msgstr "" #. Tag: entry #: preparing.xml:469 #, no-c-format msgid "Type: serial, PS/2, or USB." msgstr "" #. Tag: entry #: preparing.xml:471 #, no-c-format msgid "Port." msgstr "" #. Tag: entry #: preparing.xml:472 #, no-c-format msgid "Manufacturer." msgstr "" #. Tag: entry #: preparing.xml:473 #, no-c-format msgid "Number of buttons." msgstr "" #. Tag: entry #: preparing.xml:476 preparing.xml:504 #, no-c-format msgid "Network" msgstr "" #. Tag: entry #: preparing.xml:479 preparing.xml:505 #, no-c-format msgid "Type of adapter." msgstr "" #. Tag: entry #: preparing.xml:482 #, no-c-format msgid "Printer" msgstr "" #. Tag: entry #: preparing.xml:485 #, no-c-format msgid "Printing resolutions supported." msgstr "" #. Tag: entry #: preparing.xml:488 #, no-c-format msgid "Video Card" msgstr "" #. Tag: entry #: preparing.xml:491 #, no-c-format msgid "Video RAM available." msgstr "" #. Tag: entry #: preparing.xml:493 #, no-c-format msgid "" "Resolutions and color depths supported (these should be checked against your " "monitor's capabilities)." msgstr "" #. Tag: entry #: preparing.xml:498 #, no-c-format msgid "DASD" msgstr "" #. Tag: entry #: preparing.xml:499 #, no-c-format msgid "Device number(s)." msgstr "" #. Tag: entry #: preparing.xml:507 #, no-c-format msgid "Device numbers." msgstr "" #. Tag: entry #: preparing.xml:508 #, no-c-format msgid "Relative adapter number for OSA cards." msgstr "" #. Tag: title #: preparing.xml:516 #, no-c-format msgid "Hardware Compatibility" msgstr "" #. Tag: para #: preparing.xml:518 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:524 #, no-c-format msgid "" "In particular, Linux usually cannot run hardware that requires a running " "version of Windows to work." msgstr "" #. Tag: para #: preparing.xml:529 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:536 #, no-c-format msgid "" "So called win-modems are the most common type of this hardware. However, " "printers and other equipment may also be Windows-specific." msgstr "" #. Tag: para #: preparing.xml:541 #, no-c-format msgid "You can check hardware compatibility by:" msgstr "" #. Tag: para #: preparing.xml:546 #, no-c-format msgid "Checking manufacturers' web sites for new drivers." msgstr "" #. Tag: para #: preparing.xml:551 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:558 #, no-c-format msgid "" "Checking hardware compatibility lists for Linux on web sites dedicated to " "your architecture." msgstr "" #. Tag: para #: preparing.xml:564 #, no-c-format msgid "Searching the Internet for other users' experiences." msgstr "" #. Tag: title #: preparing.xml:575 #, no-c-format msgid "Network Settings" msgstr "" #. Tag: para #: preparing.xml:577 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:584 #, no-c-format msgid "Your host name (you may be able to decide this on your own)." msgstr "" #. Tag: para #: preparing.xml:589 #, no-c-format msgid "Your domain name." msgstr "" #. Tag: para #: preparing.xml:594 #, no-c-format msgid "Your computer's IP address." msgstr "" #. Tag: para #: preparing.xml:599 #, no-c-format msgid "The netmask to use with your network." msgstr "" #. Tag: para #: preparing.xml:604 #, no-c-format msgid "" "The IP address of the default gateway system you should route to, if your " "network has a gateway." msgstr "" #. Tag: para #: preparing.xml:610 #, no-c-format msgid "" "The system on your network that you should use as a DNS (Domain Name " "Service) server." msgstr "" #. Tag: para #: preparing.xml:618 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:625 #, no-c-format msgid "If you use a wireless network, you should also find out:" msgstr "" #. Tag: para #: preparing.xml:630 #, no-c-format msgid "ESSID of your wireless network." msgstr "" #. Tag: para #: preparing.xml:635 #, no-c-format msgid "WEP security key (if applicable)." msgstr "" #. Tag: title #: preparing.xml:652 #, no-c-format msgid "Meeting Minimum Hardware Requirements" msgstr "" #. Tag: para #: preparing.xml:653 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:659 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:665 #, no-c-format msgid "" "A Pentium 100 is the minimum recommended for desktop systems, and a Pentium " "II-300 for a Server." msgstr "" #. Tag: para #: preparing.xml:670 #, no-c-format msgid "" "A 68030 or better processor is recommended for m68k installs. You may get by " "with a little less drive space than shown." msgstr "" #. Tag: para #: preparing.xml:675 #, no-c-format msgid "" "Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For " "servers, a minimum 132-Mhz machine is recommended." msgstr "" #. Tag: title #: preparing.xml:684 #, no-c-format msgid "Recommended Minimum System Requirements" msgstr "" #. Tag: entry #: preparing.xml:688 #, no-c-format msgid "Install Type" msgstr "" #. Tag: entry #: preparing.xml:688 #, no-c-format msgid "RAM" msgstr "" #. Tag: entry #: preparing.xml:688 #, no-c-format msgid "Hard Drive" msgstr "" #. Tag: entry #: preparing.xml:694 #, no-c-format msgid "No desktop" msgstr "" #. Tag: entry #: preparing.xml:695 #, no-c-format msgid "24 megabytes" msgstr "" #. Tag: entry #: preparing.xml:696 #, no-c-format msgid "450 megabytes" msgstr "" #. Tag: entry #: preparing.xml:698 #, no-c-format msgid "With Desktop" msgstr "" #. Tag: entry #: preparing.xml:699 #, no-c-format msgid "64 megabytes" msgstr "" #. Tag: entry #: preparing.xml:700 #, no-c-format msgid "1 gigabyte" msgstr "" #. Tag: entry #: preparing.xml:702 #, no-c-format msgid "Server" msgstr "" #. Tag: entry #: preparing.xml:703 #, no-c-format msgid "128 megabytes" msgstr "" #. Tag: entry #: preparing.xml:704 #, no-c-format msgid "4 gigabytes" msgstr "" #. Tag: para #: preparing.xml:709 #, no-c-format 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 ." msgstr "" #. Tag: term #: preparing.xml:719 #, no-c-format msgid "Standard Server" msgstr "" #. Tag: para #: preparing.xml:720 #, no-c-format 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." msgstr "" #. Tag: term #: preparing.xml:732 #, no-c-format msgid "Desktop" msgstr "" #. Tag: para #: preparing.xml:733 #, no-c-format 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." msgstr "" #. Tag: term #: preparing.xml:743 #, no-c-format msgid "Work Console" msgstr "" #. Tag: para #: preparing.xml:744 #, no-c-format 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." msgstr "" #. Tag: term #: preparing.xml:754 #, no-c-format msgid "Developer" msgstr "" #. Tag: para #: preparing.xml:755 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:765 #, no-c-format 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 /var partition contains a lot of state " "information specific to Debian in addition to its regular contents like " "logfiles. The dpkg files (with information on all " "installed packages) can easily consume 20MB. Also, apt-get puts downloaded packages here before they are installed. You should " "usually allocate at least 100MB for /var." msgstr "" #. Tag: title #: preparing.xml:789 #, no-c-format msgid "Pre-Partitioning for Multi-Boot Systems" msgstr "" #. Tag: para #: preparing.xml:790 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:797 #, no-c-format msgid "" "Whenever this section talks about disks 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." msgstr "" #. Tag: para #: preparing.xml:803 #, no-c-format msgid "" "If you already have an operating system on your system (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, " "…) (Tru64 (Digital UNIX), OpenVMS, " "Windows NT, FreeBSD, …) (VM, z/OS, " "OS/390, …) (Amiga OS, Atari TOS, Mac " "OS, …) 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." msgstr "" #. Tag: para #: preparing.xml:830 #, no-c-format msgid "" "You can find information about your current partition setup by using a " "partitioning tool for your current operating system, " "such as fdisk or PartitionMagic, such as " "Drive Setup, HD Toolkit, or MacTools, such as " "HD SC Setup, HDToolBox, or SCSITool, such as " "the VM diskmap. Partitioning tools always provide a way to show " "existing partitions without making changes." msgstr "" #. Tag: para #: preparing.xml:840 #, no-c-format 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." msgstr "" #. Tag: emphasis #: preparing.xml:850 #, no-c-format msgid "FIXME: write about HP-UX disks?" msgstr "" #. Tag: para #: preparing.xml:852 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:859 #, no-c-format 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 (), " "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." msgstr "" #. Tag: para #: preparing.xml:874 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:884 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:890 #, no-c-format 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 not 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." msgstr "" #. Tag: para #: preparing.xml:902 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:910 #, no-c-format msgid "" "You can recover from these actions or avoid them, but installing the native " "system first saves you trouble." msgstr "" #. Tag: para #: preparing.xml:915 #, no-c-format 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 before 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." msgstr "" #. Tag: para #: preparing.xml:927 #, no-c-format 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:" msgstr "" #. Tag: para #: preparing.xml:934 #, no-c-format msgid "Back up everything on the computer." msgstr "" #. Tag: para #: preparing.xml:939 #, no-c-format msgid "" "Boot from the native operating system installer media such as CD-ROM or " "tapes. When booting from a MacOS CD, hold the " "c key while booting to force the CD to become the active " "MacOS system." msgstr "" #. Tag: para #: preparing.xml:949 #, no-c-format msgid "" "Use the native partitioning tools to create native system partition(s). " "Leave either a place holder partition or free space for &debian;." msgstr "" #. Tag: para #: preparing.xml:956 #, no-c-format msgid "Install the native operating system on its new partition." msgstr "" #. Tag: para #: preparing.xml:961 #, no-c-format msgid "" "Boot back into the native system to verify everything's OK, and to download " "the Debian installer boot files." msgstr "" #. Tag: para #: preparing.xml:967 #, no-c-format msgid "Boot the Debian installer to continue installing Debian." msgstr "" #. Tag: title #: preparing.xml:981 #, no-c-format msgid "Partitioning in Tru64 UNIX" msgstr "" #. Tag: para #: preparing.xml:982 #, no-c-format 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 disk label, which allows for up to eight partitions per disk drive. The " "partitions are numbered 1 through to 8 in " "Linux and lettered a through to h in UNIX. Linux kernels 2.2 and higher always correspond 1 to a, 2 to b and so on. " "For example, rz0e in Tru64 UNIX would most likely be " "called sda5 in Linux." msgstr "" #. Tag: para #: preparing.xml:994 #, no-c-format msgid "" "Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be " "used from Tru64, the c partition is required to span the " "entire disk (thus overlapping all other non-empty partitions). Under Linux " "this makes sda3 identical to sda " "(sdb3 to sdb, 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." msgstr "" #. Tag: para #: preparing.xml:1007 #, no-c-format msgid "" "Another conventional requirement is for the a 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." msgstr "" #. Tag: para #: preparing.xml:1016 #, no-c-format 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 " "mkswap 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 mkswap from the Linux start-up scripts " "before adding swap space with swapon -a." msgstr "" #. Tag: para #: preparing.xml:1025 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1034 #, no-c-format msgid "Partitioning in Windows NT" msgstr "" #. Tag: para #: preparing.xml:1036 #, no-c-format 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 harmless signature on non-Windows disks if you " "have any. Never let it do that, as this signature will " "destroy the partition information." msgstr "" #. Tag: para #: preparing.xml:1049 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1066 #, no-c-format msgid "Partitioning From DOS or Windows" msgstr "" #. Tag: para #: preparing.xml:1067 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1075 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1089 #, no-c-format msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" msgstr "" #. Tag: para #: preparing.xml:1092 #, no-c-format 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 Manually edit " "partition table , select the partition to resize, " "and specify its new size. So in most cases you should not need to use the " "method described below." msgstr "" #. Tag: para #: preparing.xml:1104 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1113 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1122 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: preparing.xml:1135 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: preparing.xml:1145 #, no-c-format msgid "" "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." msgstr "" #. Tag: para #: preparing.xml:1151 #, no-c-format msgid "" "Note that there are many other partition managers out there, in case " "fips doesn't do the trick for you." msgstr "" #. Tag: title #: preparing.xml:1159 #, no-c-format msgid "Partitioning for DOS" msgstr "" #. Tag: para #: preparing.xml:1161 #, no-c-format 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 scandisk, or other " "weird errors in DOS or Windows." msgstr "" #. Tag: para #: preparing.xml:1169 #, no-c-format 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. Do this prior to running " "DOS's format command, from Linux:" msgstr "" #. Tag: screen #: preparing.xml:1175 #, no-c-format msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" msgstr "" #. Tag: title #: preparing.xml:1186 #, no-c-format msgid "Partitioning in AmigaOS" msgstr "" #. Tag: para #: preparing.xml:1187 #, no-c-format msgid "" "If you are running AmigaOS, you can use the HDToolBox " "program to adjust your native partitions prior to installation." msgstr "" #. Tag: title #: preparing.xml:1195 #, no-c-format msgid "Partitioning in Atari TOS" msgstr "" #. Tag: para #: preparing.xml:1196 #, no-c-format msgid "" "Atari partition IDs are three ASCII characters, use LNX for " "data and SWP 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 MNX. 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." msgstr "" #. Tag: para #: preparing.xml:1207 #, no-c-format msgid "" "There are a multitude of third party partitioning tools available (the Atari " "harddisk utility doesn't permit changing the partition " "ID); this manual cannot give detailed descriptions for all of them. The " "following description covers SCSITool (from Hard+Soft " "GmBH)." msgstr "" #. Tag: para #: preparing.xml:1216 #, no-c-format msgid "" "Start SCSITool and select the disk you want to partition " "(Disk menu, item select)." msgstr "" #. Tag: para #: preparing.xml:1222 #, no-c-format msgid "" "From the Partition menu, select either New to add new partitions or change the existing partition sizes, " "or Change to change one specific partition. " "Unless you have already created partitions with the right sizes and only " "want to change the partition ID, New is probably " "the best choice." msgstr "" #. Tag: para #: preparing.xml:1232 #, no-c-format msgid "" "For the New choice, select existing 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 OK button." msgstr "" #. Tag: para #: preparing.xml:1244 #, no-c-format msgid "" "For the Change option, select the partition to " "change in the selection list, and select other systems " "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 OK button." msgstr "" #. Tag: para #: preparing.xml:1254 #, no-c-format msgid "" "Write down the Linux names for each of the partitions you created or changed " "for use with Linux — see ." msgstr "" #. Tag: para #: preparing.xml:1260 #, no-c-format msgid "" "Quit SCSITool using the Quit " "item from the File 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?)." msgstr "" #. Tag: para #: preparing.xml:1272 #, no-c-format msgid "" "There is a partitioning tool for Linux/m68k called atari-fdisk 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). " "SCSITool 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." msgstr "" #. Tag: title #: preparing.xml:1287 #, no-c-format msgid "Partitioning in MacOS" msgstr "" #. Tag: para #: preparing.xml:1288 #, no-c-format msgid "" "Partitioning tools for Macintosh tested include pdisk, " "HD SC Setup 7.3.5 (Apple), HDT 1.8 " "(FWB), SilverLining (LaCie), and DiskTool (Tim Endres, GPL). Full versions are required for HDT and SilverLining. The Apple tool requires a " "patch in order to recognize third-party disks (a description on how to patch " "HD SC Setup using ResEdit can be found " "at )." msgstr "" #. Tag: para #: preparing.xml:1299 #, no-c-format msgid "" "For IDE based Macs, you need to use Apple Drive Setup 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." msgstr "" #. Tag: title #: preparing.xml:1315 #, no-c-format msgid "Partitioning from SunOS" msgstr "" #. Tag: para #: preparing.xml:1317 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1332 #, no-c-format msgid "Partitioning from Linux or another OS" msgstr "" #. Tag: para #: preparing.xml:1334 #, no-c-format msgid "" "Whatever system you are using to partition, make sure you create a " "Sun disk label 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 fdisk, the s 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." msgstr "" #. Tag: para #: preparing.xml:1346 #, no-c-format msgid "" "You will probably be using SILO as your boot loader (the " "small program which runs the operating system kernel). SILO has certain requirements for partition sizes and location; see " "." msgstr "" #. Tag: title #: preparing.xml:1361 #, no-c-format msgid "MacOS/OSX Partitioning" msgstr "" #. Tag: para #: preparing.xml:1363 #, no-c-format msgid "" "The Apple Drive Setup application can be found in " "the Utilities 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 Drive Setup." msgstr "" #. Tag: para #: preparing.xml:1370 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1376 #, no-c-format 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, Startup Disk (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 option key at boot time, and " "separate options can be installed in the yaboot " "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." msgstr "" #. Tag: para #: preparing.xml:1389 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1409 #, no-c-format msgid "Pre-Installation Hardware and Operating System Setup" msgstr "" #. Tag: para #: preparing.xml:1410 #, no-c-format 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 firmware 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." msgstr "" #. Tag: title #: preparing.xml:1427 #, no-c-format msgid "Invoking the BIOS Set-Up Menu" msgstr "" #. Tag: para #: preparing.xml:1429 #, no-c-format 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 must ensure that your BIOS is setup correctly; not " "doing so can lead to intermittent crashes or an inability to install Debian." msgstr "" #. Tag: para #: preparing.xml:1438 #, no-c-format msgid "" "The rest of this section is lifted from the , answering the question, How do I enter the CMOS configuration " "menu?. How you access the BIOS (or CMOS) " "configuration menu depends on who wrote your BIOS software:" msgstr "" #. Tag: term #: preparing.xml:1452 #, no-c-format msgid "AMI BIOS" msgstr "" #. Tag: para #: preparing.xml:1453 #, no-c-format msgid "Delete key during the POST (power on self test)" msgstr "" #. Tag: term #: preparing.xml:1461 #, no-c-format msgid "Award BIOS" msgstr "" #. Tag: para #: preparing.xml:1462 #, no-c-format msgid "" " CtrlAltEsc , or Delete key during the POST" msgstr "" #. Tag: term #: preparing.xml:1471 #, no-c-format msgid "DTK BIOS" msgstr "" #. Tag: para #: preparing.xml:1472 #, no-c-format msgid "Esc key during the POST" msgstr "" #. Tag: term #: preparing.xml:1479 #, no-c-format msgid "IBM PS/2 BIOS" msgstr "" #. Tag: para #: preparing.xml:1480 #, no-c-format msgid "" " CtrlAltInsert " " after CtrlAltDelete " msgstr "" #. Tag: term #: preparing.xml:1494 #, no-c-format msgid "Phoenix BIOS" msgstr "" #. Tag: para #: preparing.xml:1495 #, no-c-format msgid "" " CtrlAltEsc or CtrlAltS or F1" msgstr "" #. Tag: para #: preparing.xml:1511 #, no-c-format msgid "" "Information on invoking other BIOS routines can be found in ." msgstr "" #. Tag: para #: preparing.xml:1516 #, no-c-format 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 ." msgstr "" #. Tag: title #: preparing.xml:1527 preparing.xml:1870 #, no-c-format msgid "Boot Device Selection" msgstr "" #. Tag: para #: preparing.xml:1529 #, no-c-format 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 " "A: (the first floppy disk), then optionally the first " "CD-ROM device (possibly appearing as D: or E:" "), and then from C: (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." msgstr "" #. Tag: para #: preparing.xml:1540 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1547 #, no-c-format msgid "" "Other popular option is to boot from a USB storage (also called USB memory " "stick or USB key). Some BIOSes can boot USB storage directly, and some " "cannot. You may need to configure your BIOS to boot from a Removable " "drive or even a USB-ZIP to get it to boot from the " "USB device." msgstr "" #. Tag: para #: preparing.xml:1555 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1564 #, no-c-format msgid "Changing the Boot Order on IDE Computers" msgstr "" #. Tag: para #: preparing.xml:1567 #, no-c-format msgid "" "As your computer starts, press the keys to enter the BIOS utility. Often, it " "is the Delete key. However, consult the hardware " "documentation for the exact keystrokes." msgstr "" #. Tag: para #: preparing.xml:1574 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1579 #, no-c-format msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" #. Tag: para #: preparing.xml:1584 #, no-c-format msgid "C is the hard drive, and A is the floppy drive." msgstr "" #. Tag: para #: preparing.xml:1590 #, no-c-format msgid "" "Change the boot sequence setting so that the CD-ROM or the floppy is first. " "Usually, the Page Up or Page Down keys " "cycle through the possible choices." msgstr "" #. Tag: para #: preparing.xml:1598 #, no-c-format msgid "" "Save your changes. Instructions on the screen tell you how to save the " "changes on your computer." msgstr "" #. Tag: title #: preparing.xml:1608 #, no-c-format msgid "Changing the Boot Order on SCSI Computers" msgstr "" #. Tag: para #: preparing.xml:1612 #, no-c-format msgid "" "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" #. Tag: para #: preparing.xml:1617 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1623 #, no-c-format msgid "" "The keystrokes you need depend on the utility. Often, it is " "CtrlF2. However, " "consult your hardware documentation for the exact keystrokes." msgstr "" #. Tag: para #: preparing.xml:1631 #, no-c-format msgid "Find the utility for changing the boot order." msgstr "" #. Tag: para #: preparing.xml:1636 #, no-c-format msgid "" "Set the utility so that the SCSI ID of the CD drive is first on the list." msgstr "" #. Tag: para #: preparing.xml:1642 #, no-c-format msgid "" "Save your changes. Instructions on the screen tell you how to save the " "changes on your computer. Often, you must press F10." msgstr "" #. Tag: title #: preparing.xml:1656 #, no-c-format msgid "Miscellaneous BIOS Settings" msgstr "" #. Tag: title #: preparing.xml:1658 #, no-c-format msgid "CD-ROM Settings" msgstr "" #. Tag: para #: preparing.xml:1659 #, no-c-format 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 seek failed error messages, this may be " "your problem." msgstr "" #. Tag: title #: preparing.xml:1669 #, no-c-format msgid "Extended vs. Expanded Memory" msgstr "" #. Tag: para #: preparing.xml:1670 #, no-c-format msgid "" "If your system provides both extended and " "expanded 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." msgstr "" #. Tag: title #: preparing.xml:1680 #, no-c-format msgid "Virus Protection" msgstr "" #. Tag: para #: preparing.xml:1681 #, no-c-format 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 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. ." msgstr "" #. Tag: title #: preparing.xml:1702 #, no-c-format msgid "Shadow RAM" msgstr "" #. Tag: para #: preparing.xml:1703 #, no-c-format msgid "" "Your motherboard may provide shadow RAM or BIOS " "caching. You may see settings for Video BIOS Shadow, " "C800-CBFF Shadow, etc. Disable 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." msgstr "" #. Tag: title #: preparing.xml:1720 #, no-c-format msgid "Memory Hole" msgstr "" #. Tag: para #: preparing.xml:1721 #, no-c-format msgid "" "If your BIOS offers something like 15–16 MB Memory Hole, please disable that. Linux expects to find memory there if you have " "that much RAM." msgstr "" #. Tag: para #: preparing.xml:1727 #, no-c-format msgid "" "We have a report of an Intel Endeavor motherboard on which there is an " "option called LFB or Linear Frame Buffer. This " "had two settings: Disabled and 1 Megabyte. Set " "it to 1 Megabyte. 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." msgstr "" #. Tag: title #: preparing.xml:1743 #, no-c-format msgid "Advanced Power Management" msgstr "" #. Tag: para #: preparing.xml:1744 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1762 #, no-c-format msgid "Firmware Revisions and Existing OS Setup" msgstr "" #. Tag: para #: preparing.xml:1764 #, no-c-format 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." msgstr "" #. Tag: title #: preparing.xml:1787 #, no-c-format msgid "Invoking OpenFirmware" msgstr "" #. Tag: para #: preparing.xml:1788 #, no-c-format 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." msgstr "" #. Tag: para #: preparing.xml:1796 #, no-c-format msgid "" "On &arch-title; Macintoshes, you invoke OpenFirmware with " "Command option O F while booting. Generally it will check " "for these keystrokes after the chime, but the exact timing varies from model " "to model. See for more " "hints." msgstr "" #. Tag: para #: preparing.xml:1805 #, no-c-format msgid "" "The OpenFirmware prompt looks like this: \n" "ok\n" "0 >\n" " Note that on older model &arch-title; Macs, the " "default and sometimes hardwired I/O for OpenFirmware user interaction is " "through the serial (modem) port. If you invoke OpenFirmware on one of these " "machines, you will just see a black screen. In that case, a terminal program " "running on another computer, connected to the modem port, is needed to " "interact with OpenFirmware." msgstr "" #. Tag: para #: preparing.xml:1818 #, no-c-format msgid "" "The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, " "is broken. These machines will most likely not be able to boot from the hard " "drive unless the firmware is patched. A firmware patch is included in the " "System Disk 2.3.1 utility, available from Apple " "at . After unpacking the utility in MacOS, " "and launching it, select the Save button to have the firmware patches " "installed to nvram." msgstr "" #. Tag: title #: preparing.xml:1837 #, no-c-format msgid "Invoking OpenBoot" msgstr "" #. Tag: para #: preparing.xml:1839 #, no-c-format msgid "" "OpenBoot provides the basic functions needed to boot the &arch-title; " "architecture. This is rather similar in function to the BIOS in the x86 " "architecture, although much nicer. The Sun boot PROMs have a built-in forth " "interpreter which lets you do quite a number of things with your machine, " "such as diagnostics, simple scripts, etc." msgstr "" #. Tag: para #: preparing.xml:1847 #, no-c-format msgid "" "To get to the boot prompt you need to hold down the Stop " "key (on older type 4 keyboards, use the L1 key, if you have " "a PC keyboard adapter, use the Break key) and press the " "A key. The boot PROM will give you a prompt, either " "ok or >. It is preferred to " "have the ok prompt. So if you get the old style " "prompt, hit the n key to get the new style prompt." msgstr "" #. Tag: para #: preparing.xml:1859 #, no-c-format msgid "" "If you are using a serial console, send a break to the machine. With " "Minicom, use Ctrl-A F, with cu, hit Enter, " "then type %~break. Consult the documentation of your " "terminal emulator if you are using a different program." msgstr "" #. Tag: para #: preparing.xml:1872 #, no-c-format msgid "" "You can use OpenBoot to boot from specific devices, and also to change your " "default boot device. However, you need to know some details about how " "OpenBoot names devices; it's much different from Linux device naming, " "described in . Also, the command will vary a " "bit, depending on what version of OpenBoot you have. More information about " "OpenBoot can be found in the Sun OpenBoot " "Reference." msgstr "" #. Tag: para #: preparing.xml:1882 #, no-c-format msgid "" "Typically, with newer revisions, you can use OpenBoot device such as " "floppy, cdrom, net, " "disk, or disk2. These have the obvious " "meanings; the net device is for booting from the network. " "Additionally, the device name can specify a particular partition of a disk, " "such as disk2:a to boot disk2, first partition. Full OpenBoot " "device names have the form \n" "driver-name@\n" "unit-address:\n" "device-arguments\n" ". In older revisions of OpenBoot, device naming " "is a bit different: the floppy device is called /fd, and SCSI " "disk devices are of the form sd(controller, disk-target-id, disk-" "lun). The command show-devs in " "newer OpenBoot revisions is useful for viewing the currently configured " "devices. For full information, whatever your revision, see the Sun OpenBoot Reference." msgstr "" #. Tag: para #: preparing.xml:1905 #, no-c-format msgid "" "To boot from a specific device, use the command boot " "device. You can set this behavior as " "the default using the setenv command. However, the " "name of the variable to set changed between OpenBoot revisions. In OpenBoot " "1.x, use the command setenv boot-from device. In later revisions of OpenBoot, use the command " "setenv boot-device device. " "Note, this is also configurable using the eeprom command " "on Solaris, or modifying the appropriate files in /proc/openprom/" "options/, for example under Linux: \n" "# echo disk1:1 > /proc/openprom/options/boot-device\n" " and under Solaris:" msgstr "" #. Tag: screen #: preparing.xml:1924 #, no-c-format msgid "eeprom boot-device=disk1:1" msgstr "" #. Tag: title #: preparing.xml:1934 #, no-c-format msgid "BIOS Setup" msgstr "" #. Tag: para #: preparing.xml:1935 #, no-c-format msgid "" "In order to install &debian; on a &arch-title; or zSeries machine you have " "first boot a kernel into the system. The boot mechanism of this platform is " "inherently different to other ones, especially from PC-like systems: there " "are no floppy devices available at all. You will notice another big " "difference while you work with this platform: most (if not all) of the time " "you will work remote, with the help of some client session software like " "telnet, or a browser. This is due to that special system architecture where " "the 3215/3270 console is line-based instead of character-based." msgstr "" #. Tag: para #: preparing.xml:1947 #, no-c-format msgid "" "Linux on this platform runs either natively on the bare machine, in a so-" "called LPAR (Logical Partition) or in a virtual machine supplied by the VM " "system. You can use a boot tape on all of those systems; you may use some " "other boot media, too, but those may not be generally available. For " "example, you can use the virtual card reader of a virtual machine, or boot " "from the HMC (Hardware Management Console) of an LPAR if the HMC and this " "option is available for you." msgstr "" #. Tag: para #: preparing.xml:1957 #, no-c-format msgid "" "Before you actually perform an installation, you have to go over some design " "and preparation steps. IBM has made documentation available about the whole " "process, e.g. how to prepare an installation medium and how actually boot " "from that medium. Duplicating that information here is neither possible nor " "necessary. However, we will describe here which kind of Debian-specific data " "is needed and where do you find them. Based on both sources of information " "you have to prepare your machine and the installation medium and to perform " "a boot from it. When you see the welcome message in your client session join " "this document again for the Debian-specific installation steps." msgstr "" #. Tag: title #: preparing.xml:1974 #, no-c-format msgid "Native and LPAR installations" msgstr "" #. Tag: para #: preparing.xml:1975 #, no-c-format msgid "" "Please refer to chapter 5 of the Linux for &arch-title; Redbook " "and chapter 3.2 of the Linux for IBM eServer zSeries and &arch-title;: " "Distributions Redbook on how to set up an LPAR for Linux." msgstr "" #. Tag: title #: preparing.xml:1989 #, no-c-format msgid "Installation as a VM guest" msgstr "" #. Tag: para #: preparing.xml:1991 #, no-c-format msgid "" "Please refer to chapter 6 of the Linux for &arch-title; Redbook " "and chapter 3.1 of the Linux for IBM eServer zSeries and &arch-title;: " "Distributions Redbook on how to set up a VM guest for running Linux." msgstr "" #. Tag: para #: preparing.xml:2001 #, no-c-format msgid "" "You need to copy all the files from the generic sub-" "directory to your CMS disk. Be sure to transfer kernel.debian and initrd.debian in binary mode with a fixed " "record length of 80 characters." msgstr "" #. Tag: title #: preparing.xml:2013 #, no-c-format msgid "Setting up an installation server" msgstr "" #. Tag: para #: preparing.xml:2015 #, no-c-format msgid "" "If you don't have a connection to the Internet (either directly or via a web " "proxy) you need to create a local installation server that can be accessed " "from your S/390. This server keeps all the packages you want to install and " "must make them available using NFS, HTTP or FTP." msgstr "" #. Tag: para #: preparing.xml:2023 #, no-c-format msgid "" "The installation server needs to copy the exact directory structure from any " "&debian; mirror but of only the s390 and architecture-independent files are " "required. You can also copy the contents of all installation CDs into such a " "directory tree." msgstr "" #. Tag: emphasis #: preparing.xml:2032 #, no-c-format msgid "FIXME: more information needed — from a Redbook?" msgstr "" #. Tag: title #: preparing.xml:2038 #, no-c-format msgid "Hardware Issues to Watch Out For" msgstr "" #. Tag: para #: preparing.xml:2039 #, no-c-format msgid "" "Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It " "sometimes works, but is sensitive to temperature and other factors and can " "actually damage your system. One of the authors of this document over-" "clocked his own system for a year, and then the system started aborting the " "gcc program with an unexpected signal while it was " "compiling the operating system kernel. Turning the CPU speed back down to " "its rated value solved the problem." msgstr "" #. Tag: para #: preparing.xml:2049 #, no-c-format msgid "" "The gcc compiler is often the first thing to die from bad " "memory modules (or other hardware problems that change data unpredictably) " "because it builds huge data structures that it traverses repeatedly. An " "error in these data structures will cause it to execute an illegal " "instruction or access a non-existent address. The symptom of this will be " "gcc dying from an unexpected signal." msgstr "" #. Tag: para #: preparing.xml:2059 #, no-c-format msgid "" "Atari TT RAM boards are notorious for RAM problems under Linux; if you " "encounter any strange problems, try running at least the kernel in ST-RAM. " "Amiga users may need to exclude RAM using a booter memfile. FIXME: more description of this needed. " msgstr "" #. Tag: para #: preparing.xml:2071 #, no-c-format msgid "" "The very best motherboards support parity RAM and will actually tell you if " "your system has a single-bit error in RAM. Unfortunately, they don't have a " "way to fix the error, thus they generally crash immediately after they tell " "you about the bad RAM. Still, it's better to be told you have bad memory " "than to have it silently insert errors in your data. Thus, the best systems " "have motherboards that support parity and true-parity memory modules; see " "." msgstr "" #. Tag: para #: preparing.xml:2082 #, no-c-format msgid "" "If you do have true-parity RAM and your motherboard can handle it, be sure " "to enable any BIOS settings that cause the motherboard to interrupt on " "memory parity errors." msgstr "" #. Tag: title #: preparing.xml:2090 #, no-c-format msgid "The Turbo Switch" msgstr "" #. Tag: para #: preparing.xml:2091 #, no-c-format msgid "" "Many systems have a turbo switch that controls the " "speed of the CPU. Select the high-speed setting. If your BIOS allows you to " "disable software control of the turbo switch (or software control of CPU " "speed), do so and lock the system in high-speed mode. We have one report " "that on a particular system, while Linux is auto-probing (looking for " "hardware devices) it can accidentally touch the software control for the " "turbo switch." msgstr "" #. Tag: title #: preparing.xml:2104 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "" #. Tag: para #: preparing.xml:2105 #, no-c-format msgid "" "Many users of Cyrix CPUs have had to disable the cache in their systems " "during installation, because the floppy disk has errors if they do not. If " "you have to do this, be sure to re-enable your cache when you are finished " "with installation, as the system runs much slower with " "the cache disabled." msgstr "" #. Tag: para #: preparing.xml:2113 #, no-c-format msgid "" "We don't think this is necessarily the fault of the Cyrix CPU. It may be " "something that Linux can work around. We'll continue to look into the " "problem. For the technically curious, we suspect a problem with the cache " "being invalid after a switch from 16-bit to 32-bit code." msgstr "" #. Tag: title #: preparing.xml:2123 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "" #. Tag: para #: preparing.xml:2124 #, no-c-format msgid "" "You may have to change some settings or jumpers on your computer's " "peripheral cards. Some cards have setup menus, while others rely on jumpers. " "This document cannot hope to provide complete information on every hardware " "device; what it hopes to provide is useful tips." msgstr "" #. Tag: para #: preparing.xml:2131 #, no-c-format msgid "" "If any cards provide mapped memory, the memory should be " "mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 " "megabyte) or at an address at least 1 megabyte greater than the total amount " "of RAM in your system." msgstr "" #. Tag: title #: preparing.xml:2142 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para #: preparing.xml:2143 #, no-c-format msgid "" "If you have no AT-style keyboard and only a USB model, you may need to " "enable legacy AT keyboard emulation in your BIOS setup. Only do this if the " "installation system fails to use your keyboard in USB mode. Conversely, for " "some systems (especially laptops) you may need to disable legacy USB support " "if your keyboard does not respond. Consult your main board manual and look " "in the BIOS for Legacy keyboard emulation or USB " "keyboard support options." msgstr "" #. Tag: title #: preparing.xml:2156 #, no-c-format msgid "More than 64 MB RAM" msgstr "" #. Tag: para #: preparing.xml:2157 #, no-c-format msgid "" "The Linux Kernel cannot always detect what amount of RAM you have. If this " "is the case please look at ." msgstr ""