diff options
Diffstat (limited to 'po/pot/preparing.pot')
| -rw-r--r-- | po/pot/preparing.pot | 260 |
1 files changed, 130 insertions, 130 deletions
diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 4ae8e67f3..8c42f3b45 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-03-02 09:59+0000\n" +"POT-Creation-Date: 2006-04-28 19:34+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" @@ -1157,496 +1157,496 @@ msgstr "" #: preparing.xml:1169 #, no-c-format #. Tag: para -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:" +msgid "Apparently, whenever you create or resize a partition for DOS use, it's a good idea to fill the first few sectors with zeros. You should do this prior to running DOS's <command>format</command> command by executing the following command from Linux:" msgstr "" -#: preparing.xml:1175 +#: preparing.xml:1176 #, no-c-format #. Tag: screen msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" msgstr "" -#: preparing.xml:1186 +#: preparing.xml:1187 #, no-c-format #. Tag: title msgid "Partitioning in AmigaOS" msgstr "" -#: preparing.xml:1187 +#: preparing.xml:1188 #, no-c-format #. Tag: para msgid "If you are running AmigaOS, you can use the <command>HDToolBox</command> program to adjust your native partitions prior to installation." msgstr "" -#: preparing.xml:1195 +#: preparing.xml:1196 #, no-c-format #. Tag: title msgid "Partitioning in Atari TOS" msgstr "" -#: preparing.xml:1196 +#: preparing.xml:1197 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1207 +#: preparing.xml:1208 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1216 +#: preparing.xml:1217 #, no-c-format #. Tag: para msgid "Start <command>SCSITool</command> and select the disk you want to partition (<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)." msgstr "" -#: preparing.xml:1222 +#: preparing.xml:1223 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1232 +#: preparing.xml:1233 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1244 +#: preparing.xml:1245 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1254 +#: preparing.xml:1255 #, no-c-format #. Tag: para msgid "Write down the Linux names for each of the partitions you created or changed for use with Linux — see <xref linkend=\"device-names\"/>." msgstr "" -#: preparing.xml:1260 +#: preparing.xml:1261 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1272 +#: preparing.xml:1273 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1287 +#: preparing.xml:1288 #, no-c-format #. Tag: title msgid "Partitioning in MacOS" msgstr "" -#: preparing.xml:1288 +#: preparing.xml:1289 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1299 +#: preparing.xml:1300 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1315 +#: preparing.xml:1316 #, no-c-format #. Tag: title msgid "Partitioning from SunOS" msgstr "" -#: preparing.xml:1317 +#: preparing.xml:1318 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1332 +#: preparing.xml:1333 #, no-c-format #. Tag: title msgid "Partitioning from Linux or another OS" msgstr "" -#: preparing.xml:1334 +#: preparing.xml:1335 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1346 +#: preparing.xml:1347 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1361 +#: preparing.xml:1362 #, no-c-format #. Tag: title msgid "MacOS/OSX Partitioning" msgstr "" -#: preparing.xml:1363 +#: preparing.xml:1364 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1370 +#: preparing.xml:1371 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1376 +#: preparing.xml:1377 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1389 +#: preparing.xml:1390 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1409 +#: preparing.xml:1410 #, no-c-format #. Tag: title msgid "Pre-Installation Hardware and Operating System Setup" msgstr "" -#: preparing.xml:1410 +#: preparing.xml:1411 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1427 +#: preparing.xml:1428 #, no-c-format #. Tag: title msgid "Invoking the BIOS Set-Up Menu" msgstr "" -#: preparing.xml:1429 +#: preparing.xml:1430 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1438 +#: preparing.xml:1439 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1452 +#: preparing.xml:1453 #, no-c-format #. Tag: term msgid "AMI BIOS" msgstr "" -#: preparing.xml:1453 +#: preparing.xml:1454 #, no-c-format #. Tag: para msgid "<keycap>Delete</keycap> key during the POST (power on self test)" msgstr "" -#: preparing.xml:1461 +#: preparing.xml:1462 #, no-c-format #. Tag: term msgid "Award BIOS" msgstr "" -#: preparing.xml:1462 +#: preparing.xml:1463 #, no-c-format #. Tag: para msgid "<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </keycombo>, or <keycap>Delete</keycap> key during the POST" msgstr "" -#: preparing.xml:1471 +#: preparing.xml:1472 #, no-c-format #. Tag: term msgid "DTK BIOS" msgstr "" -#: preparing.xml:1472 +#: preparing.xml:1473 #, no-c-format #. Tag: para msgid "<keycap>Esc</keycap> key during the POST" msgstr "" -#: preparing.xml:1479 +#: preparing.xml:1480 #, no-c-format #. Tag: term msgid "IBM PS/2 BIOS" msgstr "" -#: preparing.xml:1480 +#: preparing.xml:1481 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1494 +#: preparing.xml:1495 #, no-c-format #. Tag: term msgid "Phoenix BIOS" msgstr "" -#: preparing.xml:1495 +#: preparing.xml:1496 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1511 +#: preparing.xml:1512 #, no-c-format #. Tag: para msgid "Information on invoking other BIOS routines can be found in <ulink url=\"&url-invoking-bios-info;\"></ulink>." msgstr "" -#: preparing.xml:1516 +#: preparing.xml:1517 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1527 preparing.xml:1870 +#: preparing.xml:1528 preparing.xml:1872 #, no-c-format #. Tag: title msgid "Boot Device Selection" msgstr "" -#: preparing.xml:1529 +#: preparing.xml:1530 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1540 +#: preparing.xml:1541 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1547 +#: preparing.xml:1548 #, no-c-format #. Tag: para -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." +msgid "Another popular option is to boot from a USB storage device (also called a USB memory stick or USB key). Some BIOSes can boot directly from a USB storage device, but some cannot. You may need to configure your BIOS to boot from a <quote>Removable drive</quote> or even from <quote>USB-ZIP</quote> to get it to boot from the USB device." msgstr "" -#: preparing.xml:1555 +#: preparing.xml:1556 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1564 +#: preparing.xml:1565 #, no-c-format #. Tag: title msgid "Changing the Boot Order on IDE Computers" msgstr "" -#: preparing.xml:1567 +#: preparing.xml:1568 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1574 +#: preparing.xml:1575 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1579 +#: preparing.xml:1580 #, no-c-format #. Tag: para msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" -#: preparing.xml:1584 +#: preparing.xml:1585 #, no-c-format #. Tag: para msgid "C is the hard drive, and A is the floppy drive." msgstr "" -#: preparing.xml:1590 +#: preparing.xml:1591 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1598 +#: preparing.xml:1599 #, no-c-format #. Tag: para msgid "Save your changes. Instructions on the screen tell you how to save the changes on your computer." msgstr "" -#: preparing.xml:1608 +#: preparing.xml:1609 #, no-c-format #. Tag: title msgid "Changing the Boot Order on SCSI Computers" msgstr "" -#: preparing.xml:1612 +#: preparing.xml:1613 #, no-c-format #. Tag: para msgid "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" -#: preparing.xml:1617 +#: preparing.xml:1618 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1623 +#: preparing.xml:1624 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1631 +#: preparing.xml:1632 #, no-c-format #. Tag: para msgid "Find the utility for changing the boot order." msgstr "" -#: preparing.xml:1636 +#: preparing.xml:1637 #, no-c-format #. Tag: para msgid "Set the utility so that the SCSI ID of the CD drive is first on the list." msgstr "" -#: preparing.xml:1642 +#: preparing.xml:1643 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1656 +#: preparing.xml:1657 #, no-c-format #. Tag: title msgid "Miscellaneous BIOS Settings" msgstr "" -#: preparing.xml:1658 +#: preparing.xml:1659 #, no-c-format #. Tag: title msgid "CD-ROM Settings" msgstr "" -#: preparing.xml:1659 +#: preparing.xml:1660 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1669 +#: preparing.xml:1670 #, no-c-format #. Tag: title msgid "Extended vs. Expanded Memory" msgstr "" -#: preparing.xml:1670 +#: preparing.xml:1671 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1680 +#: preparing.xml:1681 #, no-c-format #. Tag: title msgid "Virus Protection" msgstr "" -#: preparing.xml:1681 +#: preparing.xml:1682 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1702 +#: preparing.xml:1703 #, no-c-format #. Tag: title msgid "Shadow RAM" msgstr "" -#: preparing.xml:1703 +#: preparing.xml:1704 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1720 +#: preparing.xml:1721 #, no-c-format #. Tag: title msgid "Memory Hole" msgstr "" -#: preparing.xml:1721 +#: preparing.xml:1722 #, no-c-format #. Tag: para msgid "If your BIOS offers something like <quote>15–16 MB Memory Hole</quote>, please disable that. Linux expects to find memory there if you have that much RAM." msgstr "" -#: preparing.xml:1727 +#: preparing.xml:1728 #, no-c-format #. Tag: para msgid "We have a report of an Intel Endeavor motherboard on which there is an option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was not read correctly, and the system eventually crashed. At this writing we don't understand what's going on with this particular device — it just worked with that setting and not without it." msgstr "" -#: preparing.xml:1743 +#: preparing.xml:1744 #, no-c-format #. Tag: title msgid "Advanced Power Management" msgstr "" -#: preparing.xml:1744 +#: preparing.xml:1745 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1762 +#: preparing.xml:1763 #, no-c-format #. Tag: title msgid "Firmware Revisions and Existing OS Setup" msgstr "" -#: preparing.xml:1764 +#: preparing.xml:1765 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1787 +#: preparing.xml:1788 #, no-c-format #. Tag: title msgid "Invoking OpenFirmware" msgstr "" -#: preparing.xml:1788 +#: preparing.xml:1789 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1796 +#: preparing.xml:1797 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1805 +#: preparing.xml:1806 #, no-c-format #. Tag: para msgid "" @@ -1656,54 +1656,54 @@ msgid "" "</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 "" -#: preparing.xml:1818 +#: preparing.xml:1819 #, no-c-format #. Tag: para -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." +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 <guibutton>Save button</guibutton> to have the firmware patches installed to nvram." msgstr "" -#: preparing.xml:1837 +#: preparing.xml:1839 #, no-c-format #. Tag: title msgid "Invoking OpenBoot" msgstr "" -#: preparing.xml:1839 +#: preparing.xml:1841 #, no-c-format #. Tag: para -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." +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 and simple scripts." msgstr "" -#: preparing.xml:1847 +#: preparing.xml:1849 #, no-c-format #. Tag: para 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>></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 "" -#: preparing.xml:1859 +#: preparing.xml:1861 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1872 +#: preparing.xml:1874 #, no-c-format #. Tag: para -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>." +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 considerably 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 "" -#: preparing.xml:1882 +#: preparing.xml:1884 #, no-c-format #. Tag: para 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" + "Typically, with newer revisions, you can use OpenBoot devices 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 "" -#: preparing.xml:1905 +#: preparing.xml:1907 #, no-c-format #. Tag: para msgid "" @@ -1712,193 +1712,193 @@ msgid "" "</screen></informalexample> and under Solaris:" msgstr "" -#: preparing.xml:1924 +#: preparing.xml:1926 #, no-c-format #. Tag: screen msgid "eeprom boot-device=disk1:1" msgstr "" -#: preparing.xml:1934 +#: preparing.xml:1936 #, no-c-format #. Tag: title msgid "BIOS Setup" msgstr "" -#: preparing.xml:1935 +#: preparing.xml:1937 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1947 +#: preparing.xml:1949 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1957 +#: preparing.xml:1959 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1974 +#: preparing.xml:1976 #, no-c-format #. Tag: title msgid "Native and LPAR installations" msgstr "" -#: preparing.xml:1975 +#: preparing.xml:1977 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1989 +#: preparing.xml:1991 #, no-c-format #. Tag: title msgid "Installation as a VM guest" msgstr "" -#: preparing.xml:1991 +#: preparing.xml:1993 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2001 +#: preparing.xml:2003 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2013 +#: preparing.xml:2015 #, no-c-format #. Tag: title msgid "Setting up an installation server" msgstr "" -#: preparing.xml:2015 +#: preparing.xml:2017 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2023 +#: preparing.xml:2025 #, no-c-format #. Tag: para -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." +msgid "The installation server needs to copy the exact directory structure from any &debian; mirror, but 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 "" -#: preparing.xml:2032 +#: preparing.xml:2034 #, no-c-format #. Tag: emphasis msgid "FIXME: more information needed — from a Redbook?" msgstr "" -#: preparing.xml:2038 +#: preparing.xml:2040 #, no-c-format #. Tag: title msgid "Hardware Issues to Watch Out For" msgstr "" -#: preparing.xml:2039 +#: preparing.xml:2041 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2049 +#: preparing.xml:2051 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2059 +#: preparing.xml:2061 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2071 +#: preparing.xml:2073 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2082 +#: preparing.xml:2084 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2090 +#: preparing.xml:2092 #, no-c-format #. Tag: title msgid "The Turbo Switch" msgstr "" -#: preparing.xml:2091 +#: preparing.xml:2093 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2104 +#: preparing.xml:2106 #, no-c-format #. Tag: title msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "" -#: preparing.xml:2105 +#: preparing.xml:2107 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2113 +#: preparing.xml:2115 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2123 +#: preparing.xml:2125 #, no-c-format #. Tag: title msgid "Peripheral Hardware Settings" msgstr "" -#: preparing.xml:2124 +#: preparing.xml:2126 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2131 +#: preparing.xml:2133 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2142 +#: preparing.xml:2144 #, no-c-format #. Tag: title msgid "USB BIOS support and keyboards" msgstr "" -#: preparing.xml:2143 +#: preparing.xml:2145 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:2156 +#: preparing.xml:2158 #, no-c-format #. Tag: title msgid "More than 64 MB RAM" msgstr "" -#: preparing.xml:2157 +#: preparing.xml:2159 #, no-c-format #. Tag: para 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\"/>." |