path: root/po/pl/preparing.po

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR Free Software Foundation, Inc.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: http://bugs.kde.org\n"
"POT-Creation-Date: 2006-01-31 23:11+0000\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\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 "
"<emphasis>not</emphasis> 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 <firstterm>base system</"
"firstterm>."
msgstr ""

#. Tag: para
#: preparing.xml:128
#, no-c-format
msgid ""
"Install a <firstterm>boot loader</firstterm> 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, <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."
msgstr ""

#. Tag: para
#: preparing.xml:157
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:163
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:172
#, no-c-format
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."
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 "
"<quote>BVMBug</quote> or <quote>16xBug</quote> 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 "
"<ulink url=\"&url-release-area;/installmanual\">various formats and "
"translations</ulink>."
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 <ulink url="
"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>."
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 <keycap>Delete</keycap> 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:446 preparing.xml:498
#, no-c-format
msgid "Available free space."
msgstr ""

#. Tag: entry
#: preparing.xml:447
#, no-c-format
msgid "Partitions."
msgstr ""

#. Tag: entry
#: preparing.xml:449
#, no-c-format
msgid "Partitions where other operating systems are installed."
msgstr ""

#. Tag: entry
#: preparing.xml:453
#, no-c-format
msgid "Monitor"
msgstr ""

#. Tag: entry
#: preparing.xml:454 preparing.xml:474 preparing.xml:480 preparing.xml:486
#, no-c-format
msgid "Model and manufacturer."
msgstr ""

#. Tag: entry
#: preparing.xml:456
#, no-c-format
msgid "Resolutions supported."
msgstr ""

#. Tag: entry
#: preparing.xml:457
#, no-c-format
msgid "Horizontal refresh rate."
msgstr ""

#. Tag: entry
#: preparing.xml:458
#, no-c-format
msgid "Vertical refresh rate."
msgstr ""

#. Tag: entry
#: preparing.xml:460
#, no-c-format
msgid "Color depth (number of colors) supported."
msgstr ""

#. Tag: entry
#: preparing.xml:462
#, no-c-format
msgid "Screen size."
msgstr ""

#. Tag: entry
#: preparing.xml:465
#, no-c-format
msgid "Mouse"
msgstr ""

#. Tag: entry
#: preparing.xml:466
#, no-c-format
msgid "Type: serial, PS/2, or USB."
msgstr ""

#. Tag: entry
#: preparing.xml:468
#, no-c-format
msgid "Port."
msgstr ""

#. Tag: entry
#: preparing.xml:469
#, no-c-format
msgid "Manufacturer."
msgstr ""

#. Tag: entry
#: preparing.xml:470
#, no-c-format
msgid "Number of buttons."
msgstr ""

#. Tag: entry
#: preparing.xml:473 preparing.xml:501
#, no-c-format
msgid "Network"
msgstr ""

#. Tag: entry
#: preparing.xml:476 preparing.xml:502
#, no-c-format
msgid "Type of adapter."
msgstr ""

#. Tag: entry
#: preparing.xml:479
#, no-c-format
msgid "Printer"
msgstr ""

#. Tag: entry
#: preparing.xml:482
#, no-c-format
msgid "Printing resolutions supported."
msgstr ""

#. Tag: entry
#: preparing.xml:485
#, no-c-format
msgid "Video Card"
msgstr ""

#. Tag: entry
#: preparing.xml:488
#, no-c-format
msgid "Video RAM available."
msgstr ""

#. Tag: entry
#: preparing.xml:490
#, no-c-format
msgid ""
"Resolutions and color depths supported (these should be checked against your "
"monitor's capabilities)."
msgstr ""

#. Tag: entry
#: preparing.xml:495
#, no-c-format
msgid "DASD"
msgstr ""

#. Tag: entry
#: preparing.xml:496
#, no-c-format
msgid "Device number(s)."
msgstr ""

#. Tag: entry
#: preparing.xml:504
#, no-c-format
msgid "Device numbers."
msgstr ""

#. Tag: entry
#: preparing.xml:505
#, no-c-format
msgid "Relative adapter number for OSA cards."
msgstr ""

#. Tag: title
#: preparing.xml:513
#, no-c-format
msgid "Hardware Compatibility"
msgstr ""

#. Tag: para
#: preparing.xml:515
#, 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:521
#, 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:526
#, 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:533
#, 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:538
#, no-c-format
msgid "You can check hardware compatibility by:"
msgstr ""

#. Tag: para
#: preparing.xml:543
#, no-c-format
msgid "Checking manufacturers' web sites for new drivers."
msgstr ""

#. Tag: para
#: preparing.xml:548
#, 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:555
#, no-c-format
msgid ""
"Checking hardware compatibility lists for Linux on web sites dedicated to "
"your architecture."
msgstr ""

#. Tag: para
#: preparing.xml:561
#, no-c-format
msgid "Searching the Internet for other users' experiences."
msgstr ""

#. Tag: title
#: preparing.xml:572
#, no-c-format
msgid "Network Settings"
msgstr ""

#. Tag: para
#: preparing.xml:574
#, no-c-format
msgid ""
"If your computer is connected to a network 24 hours a day (i.e., an Ethernet "
"or equivalent connection &mdash; not a PPP connection), you should ask your "
"network's system administrator for this information."
msgstr ""

#. Tag: para
#: preparing.xml:581
#, no-c-format
msgid "Your host name (you may be able to decide this on your own)."
msgstr ""

#. Tag: para
#: preparing.xml:586
#, no-c-format
msgid "Your domain name."
msgstr ""

#. Tag: para
#: preparing.xml:591
#, no-c-format
msgid "Your computer's IP address."
msgstr ""

#. Tag: para
#: preparing.xml:596
#, no-c-format
msgid "The netmask to use with your network."
msgstr ""

#. Tag: para
#: preparing.xml:601
#, no-c-format
msgid ""
"The IP address of the default gateway system you should route to, if your "
"network <emphasis>has</emphasis> a gateway."
msgstr ""

#. Tag: para
#: preparing.xml:607
#, 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:615
#, 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:622
#, no-c-format
msgid "If you use a wireless network, you should also find out:"
msgstr ""

#. Tag: para
#: preparing.xml:627
#, no-c-format
msgid "ESSID of your wireless network."
msgstr ""

#. Tag: para
#: preparing.xml:632
#, no-c-format
msgid "WEP security key (if applicable)."
msgstr ""

#. Tag: title
#: preparing.xml:649
#, no-c-format
msgid "Meeting Minimum Hardware Requirements"
msgstr ""

#. Tag: para
#: preparing.xml:650
#, 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:656
#, 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:662
#, 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:667
#, 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:672
#, 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:681
#, no-c-format
msgid "Recommended Minimum System Requirements"
msgstr ""

#. Tag: entry
#: preparing.xml:685
#, no-c-format
msgid "Install Type"
msgstr ""

#. Tag: entry
#: preparing.xml:685
#, no-c-format
msgid "<entry>RAM</entry>"
msgstr ""

#. Tag: entry
#: preparing.xml:685
#, no-c-format
msgid "Hard Drive"
msgstr ""

#. Tag: entry
#: preparing.xml:691
#, no-c-format
msgid "No desktop"
msgstr ""

#. Tag: entry
#: preparing.xml:692
#, no-c-format
msgid "24 megabytes"
msgstr ""

#. Tag: entry
#: preparing.xml:693
#, no-c-format
msgid "450 megabytes"
msgstr ""

#. Tag: entry
#: preparing.xml:695
#, no-c-format
msgid "With Desktop"
msgstr ""

#. Tag: entry
#: preparing.xml:696
#, no-c-format
msgid "64 megabytes"
msgstr ""

#. Tag: entry
#: preparing.xml:697
#, no-c-format
msgid "1 gigabyte"
msgstr ""

#. Tag: entry
#: preparing.xml:699
#, no-c-format
msgid "Server"
msgstr ""

#. Tag: entry
#: preparing.xml:700
#, no-c-format
msgid "128 megabytes"
msgstr ""

#. Tag: entry
#: preparing.xml:701
#, no-c-format
msgid "4 gigabytes"
msgstr ""

#. Tag: para
#: preparing.xml:706
#, 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 <xref linkend=\"tasksel-size-list\"/>."
msgstr ""

#. Tag: term
#: preparing.xml:716
#, no-c-format
msgid "Standard Server"
msgstr ""

#. Tag: para
#: preparing.xml:717
#, 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:729
#, no-c-format
msgid "Desktop"
msgstr ""

#. Tag: para
#: preparing.xml:730
#, 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:740
#, no-c-format
msgid "Work Console"
msgstr ""

#. Tag: para
#: preparing.xml:741
#, 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:751
#, no-c-format
msgid "Developer"
msgstr ""

#. Tag: para
#: preparing.xml:752
#, 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:762
#, 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 <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>."
msgstr ""

#. Tag: title
#: preparing.xml:786
#, no-c-format
msgid "Pre-Partitioning for Multi-Boot Systems"
msgstr ""

#. Tag: para
#: preparing.xml:787
#, 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:794
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:800
#, no-c-format
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, "
"&hellip;) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, "
"Windows NT, FreeBSD, &hellip;) </phrase> <phrase arch=\"s390\"> (VM, z/OS, "
"OS/390, &hellip;) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac "
"OS, &hellip;) </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."
msgstr ""

#. Tag: para
#: preparing.xml:827
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:837
#, 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:847
#, no-c-format
msgid "FIXME: write about HP-UX disks?"
msgstr ""

#. Tag: para
#: preparing.xml:849
#, 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:856
#, 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 (<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."
msgstr ""

#. Tag: para
#: preparing.xml:871
#, 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:881
#, 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:887
#, 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 <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."
msgstr ""

#. Tag: para
#: preparing.xml:899
#, 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:907
#, 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:912
#, 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 <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."
msgstr ""

#. Tag: para
#: preparing.xml:924
#, 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:931
#, no-c-format
msgid "Back up everything on the computer."
msgstr ""

#. Tag: para
#: preparing.xml:936
#, no-c-format
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>"
msgstr ""

#. Tag: para
#: preparing.xml:946
#, 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:953
#, no-c-format
msgid "Install the native operating system on its new partition."
msgstr ""

#. Tag: para
#: preparing.xml:958
#, 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:964
#, no-c-format
msgid "Boot the Debian installer to continue installing Debian."
msgstr ""

#. Tag: title
#: preparing.xml:978
#, no-c-format
msgid "Partitioning in Tru64 UNIX"
msgstr ""

#. Tag: para
#: preparing.xml:979
#, 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 <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."
msgstr ""

#. Tag: para
#: preparing.xml:991
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1004
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1013
#, 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 "
"<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>."
msgstr ""

#. Tag: para
#: preparing.xml:1022
#, 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:1031
#, no-c-format
msgid "Partitioning in Windows NT"
msgstr ""

#. Tag: para
#: preparing.xml:1033
#, 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 <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."
msgstr ""

#. Tag: para
#: preparing.xml:1046
#, 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:1063
#, no-c-format
msgid "Partitioning From DOS or Windows"
msgstr ""

#. Tag: para
#: preparing.xml:1064
#, 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:1072
#, 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:1086
#, no-c-format
msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2"
msgstr ""

#. Tag: para
#: preparing.xml:1089
#, 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 <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."
msgstr ""

#. Tag: para
#: preparing.xml:1101
#, 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:1110
#, 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:1119
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1132
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1142
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1148
#, no-c-format
msgid ""
"Note that there are many other partition managers out there, in case "
"<command>fips</command> doesn't do the trick for you."
msgstr ""

#. Tag: title
#: preparing.xml:1156
#, no-c-format
msgid "Partitioning for DOS"
msgstr ""

#. Tag: para
#: preparing.xml:1158
#, 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 <command>scandisk</command>, or other "
"weird errors in DOS or Windows."
msgstr ""

#. Tag: para
#: preparing.xml:1166
#, 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 <command>format</command> command, from Linux:"
msgstr ""

#. Tag: screen
#: preparing.xml:1172
#, no-c-format
msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4"
msgstr ""

#. Tag: title
#: preparing.xml:1183
#, no-c-format
msgid "Partitioning in AmigaOS"
msgstr ""

#. Tag: para
#: preparing.xml:1184
#, no-c-format
msgid ""
"If you are running AmigaOS, you can use the <command>HDToolBox</command> "
"program to adjust your native partitions prior to installation."
msgstr ""

#. Tag: title
#: preparing.xml:1192
#, no-c-format
msgid "Partitioning in Atari TOS"
msgstr ""

#. Tag: para
#: preparing.xml:1193
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1204
#, no-c-format
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)."
msgstr ""

#. Tag: para
#: preparing.xml:1213
#, no-c-format
msgid ""
"Start <command>SCSITool</command> and select the disk you want to partition "
"(<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)."
msgstr ""

#. Tag: para
#: preparing.xml:1219
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1229
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1241
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1251
#, no-c-format
msgid ""
"Write down the Linux names for each of the partitions you created or changed "
"for use with Linux &mdash; see <xref linkend=\"device-names\"/>."
msgstr ""

#. Tag: para
#: preparing.xml:1257
#, no-c-format
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?)."
msgstr ""

#. Tag: para
#: preparing.xml:1269
#, no-c-format
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."
msgstr ""

#. Tag: title
#: preparing.xml:1284
#, no-c-format
msgid "Partitioning in MacOS"
msgstr ""

#. Tag: para
#: preparing.xml:1285
#, no-c-format
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>)."
msgstr ""

#. Tag: para
#: preparing.xml:1296
#, no-c-format
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."
msgstr ""

#. Tag: title
#: preparing.xml:1312
#, no-c-format
msgid "Partitioning from SunOS"
msgstr ""

#. Tag: para
#: preparing.xml:1314
#, 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:1329
#, no-c-format
msgid "Partitioning from Linux or another OS"
msgstr ""

#. Tag: para
#: preparing.xml:1331
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1343
#, no-c-format
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\"/>."
msgstr ""

#. Tag: title
#: preparing.xml:1358
#, no-c-format
msgid "MacOS/OSX Partitioning"
msgstr ""

#. Tag: para
#: preparing.xml:1360
#, no-c-format
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>."
msgstr ""

#. Tag: para
#: preparing.xml:1367
#, 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:1373
#, 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, <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."
msgstr ""

#. Tag: para
#: preparing.xml:1386
#, 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:1406
#, no-c-format
msgid "Pre-Installation Hardware and Operating System Setup"
msgstr ""

#. Tag: para
#: preparing.xml:1407
#, 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 <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."
msgstr ""

#. Tag: title
#: preparing.xml:1424
#, no-c-format
msgid "Invoking the BIOS Set-Up Menu"
msgstr ""

#. Tag: para
#: preparing.xml:1426
#, 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 <emphasis>must</emphasis> 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:1435
#, no-c-format
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:"
msgstr ""

#. Tag: term
#: preparing.xml:1449
#, no-c-format
msgid "AMI BIOS"
msgstr ""

#. Tag: para
#: preparing.xml:1450
#, no-c-format
msgid "<keycap>Delete</keycap> key during the POST (power on self test)"
msgstr ""

#. Tag: term
#: preparing.xml:1458
#, no-c-format
msgid "Award BIOS"
msgstr ""

#. Tag: para
#: preparing.xml:1459
#, no-c-format
msgid ""
"<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </"
"keycombo>, or <keycap>Delete</keycap> key during the POST"
msgstr ""

#. Tag: term
#: preparing.xml:1468
#, no-c-format
msgid "DTK BIOS"
msgstr ""

#. Tag: para
#: preparing.xml:1469
#, no-c-format
msgid "<keycap>Esc</keycap> key during the POST"
msgstr ""

#. Tag: term
#: preparing.xml:1476
#, no-c-format
msgid "IBM PS/2 BIOS"
msgstr ""

#. Tag: para
#: preparing.xml:1477
#, no-c-format
msgid ""
"<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> "
"</keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</"
"keycap><keycap>Delete</keycap> </keycombo>"
msgstr ""

#. Tag: term
#: preparing.xml:1491
#, no-c-format
msgid "Phoenix BIOS"
msgstr ""

#. Tag: para
#: preparing.xml:1492
#, no-c-format
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>"
msgstr ""

#. Tag: para
#: preparing.xml:1508
#, no-c-format
msgid ""
"Information on invoking other BIOS routines can be found in <ulink url="
"\"&url-invoking-bios-info;\"></ulink>."
msgstr ""

#. Tag: para
#: preparing.xml:1513
#, 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 <ulink url=\"&url-simtel;\"></"
"ulink>."
msgstr ""

#. Tag: title
#: preparing.xml:1524 preparing.xml:1867
#, no-c-format
msgid "Boot Device Selection"
msgstr ""

#. Tag: para
#: preparing.xml:1526
#, 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 "
"<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."
msgstr ""

#. Tag: para
#: preparing.xml:1537
#, 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:1544
#, 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 <quote>Removable "
"drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the "
"USB device."
msgstr ""

#. Tag: para
#: preparing.xml:1552
#, 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:1561
#, no-c-format
msgid "Changing the Boot Order on IDE Computers"
msgstr ""

#. Tag: para
#: preparing.xml:1564
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1571
#, 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:1576
#, no-c-format
msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom."
msgstr ""

#. Tag: para
#: preparing.xml:1581
#, no-c-format
msgid "C is the hard drive, and A is the floppy drive."
msgstr ""

#. Tag: para
#: preparing.xml:1587
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1595
#, 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:1605
#, no-c-format
msgid "Changing the Boot Order on SCSI Computers"
msgstr ""

#. Tag: para
#: preparing.xml:1609
#, no-c-format
msgid ""
"As your computer starts, press the keys to enter the SCSI setup utility."
msgstr ""

#. Tag: para
#: preparing.xml:1614
#, 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:1620
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1628
#, no-c-format
msgid "Find the utility for changing the boot order."
msgstr ""

#. Tag: para
#: preparing.xml:1633
#, 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:1639
#, 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 <keycap>F10</keycap>."
msgstr ""

#. Tag: title
#: preparing.xml:1653
#, no-c-format
msgid "Miscellaneous BIOS Settings"
msgstr ""

#. Tag: title
#: preparing.xml:1655
#, no-c-format
msgid "CD-ROM Settings"
msgstr ""

#. Tag: para
#: preparing.xml:1656
#, 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 <userinput>seek failed</userinput> error messages, this may be "
"your problem."
msgstr ""

#. Tag: title
#: preparing.xml:1666
#, no-c-format
msgid "Extended vs. Expanded Memory"
msgstr ""

#. Tag: para
#: preparing.xml:1667
#, no-c-format
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."
msgstr ""

#. Tag: title
#: preparing.xml:1677
#, no-c-format
msgid "Virus Protection"
msgstr ""

#. Tag: para
#: preparing.xml:1678
#, 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<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>."
msgstr ""

#. Tag: title
#: preparing.xml:1699
#, no-c-format
msgid "Shadow RAM"
msgstr ""

#. Tag: para
#: preparing.xml:1700
#, no-c-format
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."
msgstr ""

#. Tag: title
#: preparing.xml:1717
#, no-c-format
msgid "Memory Hole"
msgstr ""

#. Tag: para
#: preparing.xml:1718
#, no-c-format
msgid ""
"If your BIOS offers something like <quote>15&ndash;16 MB Memory Hole</"
"quote>, please disable that. Linux expects to find memory there if you have "
"that much RAM."
msgstr ""

#. Tag: para
#: preparing.xml:1724
#, no-c-format
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 &mdash; it just "
"worked with that setting and not without it."
msgstr ""

#. Tag: title
#: preparing.xml:1740
#, no-c-format
msgid "Advanced Power Management"
msgstr ""

#. Tag: para
#: preparing.xml:1741
#, 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:1759
#, no-c-format
msgid "Firmware Revisions and Existing OS Setup"
msgstr ""

#. Tag: para
#: preparing.xml:1761
#, 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:1784
#, no-c-format
msgid "Invoking OpenFirmware"
msgstr ""

#. Tag: para
#: preparing.xml:1785
#, 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:1793
#, no-c-format
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."
msgstr ""

#. Tag: para
#: preparing.xml:1802
#, no-c-format
msgid ""
"The OpenFirmware prompt looks like this: <informalexample><screen>\n"
"ok\n"
"0 &gt;\n"
"</screen></informalexample> 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:1815
#, 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 "
"<application>System Disk 2.3.1</application> utility, available from Apple "
"at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/"
"SystemDisk2.3.1.smi.bin\"></ulink>. 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:1834
#, no-c-format
msgid "Invoking OpenBoot"
msgstr ""

#. Tag: para
#: preparing.xml:1836
#, 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:1844
#, no-c-format
msgid ""
"To get to the boot prompt you need to hold down the <keycap>Stop</keycap> "
"key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have "
"a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the "
"<keycap>A</keycap> key. The boot PROM will give you a prompt, either "
"<userinput>ok</userinput> or <userinput>&gt;</userinput>. It is preferred to "
"have the <userinput>ok</userinput> prompt. So if you get the old style "
"prompt, hit the <keycap>n</keycap> key to get the new style prompt."
msgstr ""

#. Tag: para
#: preparing.xml:1856
#, no-c-format
msgid ""
"If you are using a serial console, send a break to the machine. With "
"Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, "
"then type <userinput>%~break</userinput>. Consult the documentation of your "
"terminal emulator if you are using a different program."
msgstr ""

#. Tag: para
#: preparing.xml:1869
#, 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 <xref linkend=\"device-names\"/>. Also, the command will vary a "
"bit, depending on what version of OpenBoot you have. More information about "
"OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot "
"Reference</ulink>."
msgstr ""

#. Tag: para
#: preparing.xml:1879
#, no-c-format
msgid ""
"Typically, with newer revisions, you can use OpenBoot device such as "
"<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, "
"<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious "
"meanings; the <quote>net</quote> device is for booting from the network. "
"Additionally, the device name can specify a particular partition of a disk, "
"such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot "
"device names have the form <informalexample> <screen>\n"
"<replaceable>driver-name</replaceable>@\n"
"<replaceable>unit-address</replaceable>:\n"
"<replaceable>device-arguments</replaceable>\n"
"</screen></informalexample>. In older revisions of OpenBoot, device naming "
"is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI "
"disk devices are of the form <quote>sd(<replaceable>controller</"
"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-"
"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in "
"newer OpenBoot revisions is useful for viewing the currently configured "
"devices. For full information, whatever your revision, see the <ulink url="
"\"&url-openboot;\">Sun OpenBoot Reference</ulink>."
msgstr ""

#. Tag: para
#: preparing.xml:1902
#, no-c-format
msgid ""
"To boot from a specific device, use the command <userinput>boot "
"<replaceable>device</replaceable></userinput>. You can set this behavior as "
"the default using the <userinput>setenv</userinput> command. However, the "
"name of the variable to set changed between OpenBoot revisions. In OpenBoot "
"1.x, use the command <userinput>setenv boot-from <replaceable>device</"
"replaceable></userinput>. In later revisions of OpenBoot, use the command "
"<userinput>setenv boot-device <replaceable>device</replaceable></userinput>. "
"Note, this is also configurable using the <command>eeprom</command> command "
"on Solaris, or modifying the appropriate files in <filename>/proc/openprom/"
"options/</filename>, for example under Linux: <informalexample><screen>\n"
"# echo disk1:1 &gt; /proc/openprom/options/boot-device\n"
"</screen></informalexample> and under Solaris:"
msgstr ""

#. Tag: screen
#: preparing.xml:1921
#, no-c-format
msgid "eeprom boot-device=disk1:1"
msgstr ""

#. Tag: title
#: preparing.xml:1931
#, no-c-format
msgid "BIOS Setup"
msgstr ""

#. Tag: para
#: preparing.xml:1932
#, 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:1944
#, 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:1954
#, 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:1971
#, no-c-format
msgid "Native and LPAR installations"
msgstr ""

#. Tag: para
#: preparing.xml:1972
#, no-c-format
msgid ""
"Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/"
"pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook "
"and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/"
"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: "
"Distributions</ulink> Redbook on how to set up an LPAR for Linux."
msgstr ""

#. Tag: title
#: preparing.xml:1986
#, no-c-format
msgid "Installation as a VM guest"
msgstr ""

#. Tag: para
#: preparing.xml:1988
#, no-c-format
msgid ""
"Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/"
"pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook "
"and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/"
"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: "
"Distributions</ulink> Redbook on how to set up a VM guest for running Linux."
msgstr ""

#. Tag: para
#: preparing.xml:1998
#, no-c-format
msgid ""
"You need to copy all the files from the <filename>generic</filename> sub-"
"directory to your CMS disk. Be sure to transfer <filename>kernel.debian</"
"filename> and <filename>initrd.debian</filename> in binary mode with a fixed "
"record length of 80 characters."
msgstr ""

#. Tag: title
#: preparing.xml:2010
#, no-c-format
msgid "Setting up an installation server"
msgstr ""

#. Tag: para
#: preparing.xml:2012
#, 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:2020
#, 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:2029
#, no-c-format
msgid "FIXME: more information needed &mdash; from a Redbook?"
msgstr ""

#. Tag: title
#: preparing.xml:2035
#, no-c-format
msgid "Hardware Issues to Watch Out For"
msgstr ""

#. Tag: para
#: preparing.xml:2036
#, 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 "
"<command>gcc</command> 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:2046
#, no-c-format
msgid ""
"The <command>gcc</command> 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 "
"<command>gcc</command> dying from an unexpected signal."
msgstr ""

#. Tag: para
#: preparing.xml:2056
#, 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. <phrase "
"condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </"
"emphasis></phrase>"
msgstr ""

#. Tag: para
#: preparing.xml:2068
#, 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 "
"<xref linkend=\"Parity-RAM\"/>."
msgstr ""

#. Tag: para
#: preparing.xml:2079
#, 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:2087
#, no-c-format
msgid "The Turbo Switch"
msgstr ""

#. Tag: para
#: preparing.xml:2088
#, no-c-format
msgid ""
"Many systems have a <emphasis>turbo</emphasis> 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:2101
#, no-c-format
msgid "Cyrix CPUs and Floppy Disk Errors"
msgstr ""

#. Tag: para
#: preparing.xml:2102
#, 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 <emphasis>much</emphasis> slower with "
"the cache disabled."
msgstr ""

#. Tag: para
#: preparing.xml:2110
#, 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:2120
#, no-c-format
msgid "Peripheral Hardware Settings"
msgstr ""

#. Tag: para
#: preparing.xml:2121
#, 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:2128
#, no-c-format
msgid ""
"If any cards provide <quote>mapped memory</quote>, 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:2139
#, no-c-format
msgid "USB BIOS support and keyboards"
msgstr ""

#. Tag: para
#: preparing.xml:2140
#, 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 <quote>Legacy keyboard emulation</quote> or <quote>USB "
"keyboard support</quote> options."
msgstr ""

#. Tag: title
#: preparing.xml:2153
#, no-c-format
msgid "More than 64 MB RAM"
msgstr ""

#. Tag: para
#: preparing.xml:2154
#, no-c-format
msgid ""
"The Linux Kernel cannot always detect what amount of RAM you have. If this "
"is the case please look at <xref linkend=\"boot-parms\"/>."
msgstr ""