diff options
| author | Frans Pop <elendil@planet.nl> | 2006-06-24 19:24:43 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-06-24 19:24:43 +0000 |
| commit | d3ccba713ba8448b3b77d579a062674a37a77024 (patch) | |
| tree | dd2e6e75c5c86a4e43f1b468418ad1244424eae0 /po/pot | |
| parent | 7d152bdee537779582f12d27952de980de310eb6 (diff) | |
| download | installation-guide-d3ccba713ba8448b3b77d579a062674a37a77024.zip | |
Update of POT and PO files for the manual
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/preparing.pot | 498 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 474 |
2 files changed, 492 insertions, 480 deletions
diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index e6d1fd61f..2637d7a07 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-06-21 13:30+0000\n" +"POT-Creation-Date: 2006-06-24 19:23+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" @@ -416,1237 +416,1237 @@ msgstr "" msgid "Their order on the system." msgstr "" -#: preparing.xml:444 +#: preparing.xml:445 #, no-c-format #. Tag: entry msgid "Whether IDE or SCSI (most computers are IDE)." msgstr "" -#: preparing.xml:447 +#: preparing.xml:448 #, no-c-format #. Tag: entry msgid "Whether IDE or SCSI (most m68k computers are SCSI)." msgstr "" -#: preparing.xml:449 preparing.xml:501 +#: preparing.xml:450 preparing.xml:502 #, no-c-format #. Tag: entry msgid "Available free space." msgstr "" -#: preparing.xml:450 +#: preparing.xml:451 #, no-c-format #. Tag: entry msgid "Partitions." msgstr "" -#: preparing.xml:452 +#: preparing.xml:453 #, no-c-format #. Tag: entry msgid "Partitions where other operating systems are installed." msgstr "" -#: preparing.xml:456 +#: preparing.xml:457 #, no-c-format #. Tag: entry msgid "Monitor" msgstr "" -#: preparing.xml:457 preparing.xml:477 preparing.xml:483 preparing.xml:489 +#: preparing.xml:458 preparing.xml:478 preparing.xml:484 preparing.xml:490 #, no-c-format #. Tag: entry msgid "Model and manufacturer." msgstr "" -#: preparing.xml:459 +#: preparing.xml:460 #, no-c-format #. Tag: entry msgid "Resolutions supported." msgstr "" -#: preparing.xml:460 +#: preparing.xml:461 #, no-c-format #. Tag: entry msgid "Horizontal refresh rate." msgstr "" -#: preparing.xml:461 +#: preparing.xml:462 #, no-c-format #. Tag: entry msgid "Vertical refresh rate." msgstr "" -#: preparing.xml:463 +#: preparing.xml:464 #, no-c-format #. Tag: entry msgid "Color depth (number of colors) supported." msgstr "" -#: preparing.xml:465 +#: preparing.xml:466 #, no-c-format #. Tag: entry msgid "Screen size." msgstr "" -#: preparing.xml:468 +#: preparing.xml:469 #, no-c-format #. Tag: entry msgid "Mouse" msgstr "" -#: preparing.xml:469 +#: preparing.xml:470 #, no-c-format #. Tag: entry msgid "Type: serial, PS/2, or USB." msgstr "" -#: preparing.xml:471 +#: preparing.xml:472 #, no-c-format #. Tag: entry msgid "Port." msgstr "" -#: preparing.xml:472 +#: preparing.xml:473 #, no-c-format #. Tag: entry msgid "Manufacturer." msgstr "" -#: preparing.xml:473 +#: preparing.xml:474 #, no-c-format #. Tag: entry msgid "Number of buttons." msgstr "" -#: preparing.xml:476 preparing.xml:504 +#: preparing.xml:477 preparing.xml:505 #, no-c-format #. Tag: entry msgid "Network" msgstr "" -#: preparing.xml:479 preparing.xml:505 +#: preparing.xml:480 preparing.xml:506 #, no-c-format #. Tag: entry msgid "Type of adapter." msgstr "" -#: preparing.xml:482 +#: preparing.xml:483 #, no-c-format #. Tag: entry msgid "Printer" msgstr "" -#: preparing.xml:485 +#: preparing.xml:486 #, no-c-format #. Tag: entry msgid "Printing resolutions supported." msgstr "" -#: preparing.xml:488 +#: preparing.xml:489 #, no-c-format #. Tag: entry msgid "Video Card" msgstr "" -#: preparing.xml:491 +#: preparing.xml:492 #, no-c-format #. Tag: entry msgid "Video RAM available." msgstr "" -#: preparing.xml:493 +#: preparing.xml:494 #, no-c-format #. Tag: entry msgid "Resolutions and color depths supported (these should be checked against your monitor's capabilities)." msgstr "" -#: preparing.xml:498 +#: preparing.xml:499 #, no-c-format #. Tag: entry msgid "DASD" msgstr "" -#: preparing.xml:499 +#: preparing.xml:500 #, no-c-format #. Tag: entry msgid "Device number(s)." msgstr "" -#: preparing.xml:507 +#: preparing.xml:508 #, no-c-format #. Tag: entry msgid "Device numbers." msgstr "" -#: preparing.xml:508 +#: preparing.xml:509 #, no-c-format #. Tag: entry msgid "Relative adapter number for OSA cards." msgstr "" -#: preparing.xml:516 +#: preparing.xml:517 #, no-c-format #. Tag: title msgid "Hardware Compatibility" msgstr "" -#: preparing.xml:518 +#: preparing.xml:519 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:524 +#: preparing.xml:525 #, no-c-format #. Tag: para msgid "In particular, Linux usually cannot run hardware that requires a running version of Windows to work." msgstr "" -#: preparing.xml:529 +#: preparing.xml:530 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:536 +#: preparing.xml:537 #, no-c-format #. Tag: para msgid "So called win-modems are the most common type of this hardware. However, printers and other equipment may also be Windows-specific." msgstr "" -#: preparing.xml:541 +#: preparing.xml:542 #, no-c-format #. Tag: para msgid "You can check hardware compatibility by:" msgstr "" -#: preparing.xml:546 +#: preparing.xml:547 #, no-c-format #. Tag: para msgid "Checking manufacturers' web sites for new drivers." msgstr "" -#: preparing.xml:551 +#: preparing.xml:552 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:558 +#: preparing.xml:559 #, no-c-format #. Tag: para msgid "Checking hardware compatibility lists for Linux on web sites dedicated to your architecture." msgstr "" -#: preparing.xml:564 +#: preparing.xml:565 #, no-c-format #. Tag: para msgid "Searching the Internet for other users' experiences." msgstr "" -#: preparing.xml:575 +#: preparing.xml:576 #, no-c-format #. Tag: title msgid "Network Settings" msgstr "" -#: preparing.xml:577 +#: preparing.xml:578 #, no-c-format #. Tag: para msgid "If your computer is connected to a network 24 hours a day (i.e., an Ethernet or equivalent connection — not a PPP connection), you should ask your network's system administrator for this information." msgstr "" -#: preparing.xml:584 +#: preparing.xml:585 #, no-c-format #. Tag: para msgid "Your host name (you may be able to decide this on your own)." msgstr "" -#: preparing.xml:589 +#: preparing.xml:590 #, no-c-format #. Tag: para msgid "Your domain name." msgstr "" -#: preparing.xml:594 +#: preparing.xml:595 #, no-c-format #. Tag: para msgid "Your computer's IP address." msgstr "" -#: preparing.xml:599 +#: preparing.xml:600 #, no-c-format #. Tag: para msgid "The netmask to use with your network." msgstr "" -#: preparing.xml:604 +#: preparing.xml:605 #, no-c-format #. Tag: para msgid "The IP address of the default gateway system you should route to, if your network <emphasis>has</emphasis> a gateway." msgstr "" -#: preparing.xml:610 +#: preparing.xml:611 #, no-c-format #. Tag: para msgid "The system on your network that you should use as a DNS (Domain Name Service) server." msgstr "" -#: preparing.xml:618 +#: preparing.xml:619 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:625 +#: preparing.xml:626 #, no-c-format #. Tag: para msgid "If you use a wireless network, you should also find out:" msgstr "" -#: preparing.xml:630 +#: preparing.xml:631 #, no-c-format #. Tag: para msgid "ESSID of your wireless network." msgstr "" -#: preparing.xml:635 +#: preparing.xml:636 #, no-c-format #. Tag: para msgid "WEP security key (if applicable)." msgstr "" -#: preparing.xml:652 +#: preparing.xml:653 #, no-c-format #. Tag: title msgid "Meeting Minimum Hardware Requirements" msgstr "" -#: preparing.xml:653 +#: preparing.xml:654 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:659 +#: preparing.xml:660 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:665 +#: preparing.xml:666 #, no-c-format #. Tag: para msgid "A Pentium 100 is the minimum recommended for desktop systems, and a Pentium II-300 for a Server." msgstr "" -#: preparing.xml:670 +#: preparing.xml:671 #, no-c-format #. Tag: para msgid "A 68030 or better processor is recommended for m68k installs. You may get by with a little less drive space than shown." msgstr "" -#: preparing.xml:675 +#: preparing.xml:676 #, no-c-format #. Tag: para msgid "Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For servers, a minimum 132-Mhz machine is recommended." msgstr "" -#: preparing.xml:684 +#: preparing.xml:685 #, no-c-format #. Tag: title msgid "Recommended Minimum System Requirements" msgstr "" -#: preparing.xml:688 +#: preparing.xml:689 #, no-c-format #. Tag: entry msgid "Install Type" msgstr "" -#: preparing.xml:688 +#: preparing.xml:689 #, no-c-format #. Tag: entry msgid "<entry>RAM</entry>" msgstr "" -#: preparing.xml:688 +#: preparing.xml:689 #, no-c-format #. Tag: entry msgid "Hard Drive" msgstr "" -#: preparing.xml:694 +#: preparing.xml:695 #, no-c-format #. Tag: entry msgid "No desktop" msgstr "" -#: preparing.xml:695 +#: preparing.xml:696 #, no-c-format #. Tag: entry msgid "24 megabytes" msgstr "" -#: preparing.xml:696 +#: preparing.xml:697 #, no-c-format #. Tag: entry msgid "450 megabytes" msgstr "" -#: preparing.xml:698 +#: preparing.xml:699 #, no-c-format #. Tag: entry msgid "With Desktop" msgstr "" -#: preparing.xml:699 +#: preparing.xml:700 #, no-c-format #. Tag: entry msgid "64 megabytes" msgstr "" -#: preparing.xml:700 +#: preparing.xml:701 #, no-c-format #. Tag: entry msgid "1 gigabyte" msgstr "" -#: preparing.xml:702 +#: preparing.xml:703 #, no-c-format #. Tag: entry msgid "Server" msgstr "" -#: preparing.xml:703 +#: preparing.xml:704 #, no-c-format #. Tag: entry msgid "128 megabytes" msgstr "" -#: preparing.xml:704 +#: preparing.xml:705 #, no-c-format #. Tag: entry msgid "4 gigabytes" msgstr "" -#: preparing.xml:709 +#: preparing.xml:710 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:719 +#: preparing.xml:720 #, no-c-format #. Tag: term msgid "Standard Server" msgstr "" -#: preparing.xml:720 +#: preparing.xml:721 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:732 +#: preparing.xml:733 #, no-c-format #. Tag: term msgid "Desktop" msgstr "" -#: preparing.xml:733 +#: preparing.xml:734 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:743 +#: preparing.xml:744 #, no-c-format #. Tag: term msgid "Work Console" msgstr "" -#: preparing.xml:744 +#: preparing.xml:745 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:754 +#: preparing.xml:755 #, no-c-format #. Tag: term msgid "Developer" msgstr "" -#: preparing.xml:755 +#: preparing.xml:756 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:765 +#: preparing.xml:766 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:789 +#: preparing.xml:790 #, no-c-format #. Tag: title msgid "Pre-Partitioning for Multi-Boot Systems" msgstr "" -#: preparing.xml:790 +#: preparing.xml:791 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:797 +#: preparing.xml:798 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:803 +#: preparing.xml:804 #, no-c-format #. Tag: para msgid "If you already have an operating system on your system <phrase arch=\"i386\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, …) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, OS/390, …) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac OS, …) </phrase> and want to stick Linux on the same disk, you will need to repartition the disk. Debian requires its own hard disk partitions. It cannot be installed on Windows or MacOS partitions. It may be able to share some partitions with other Linux systems, but that's not covered here. At the very least you will need a dedicated partition for the Debian root." msgstr "" -#: preparing.xml:830 +#: preparing.xml:831 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:840 +#: preparing.xml:841 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:850 +#: preparing.xml:851 #, no-c-format #. Tag: emphasis msgid "FIXME: write about HP-UX disks?" msgstr "" -#: preparing.xml:852 +#: preparing.xml:853 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:859 +#: preparing.xml:860 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:874 +#: preparing.xml:875 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:884 +#: preparing.xml:885 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:890 +#: preparing.xml:891 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:902 +#: preparing.xml:903 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:910 +#: preparing.xml:911 #, no-c-format #. Tag: para msgid "You can recover from these actions or avoid them, but installing the native system first saves you trouble." msgstr "" -#: preparing.xml:915 +#: preparing.xml:916 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:927 +#: preparing.xml:928 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:934 +#: preparing.xml:935 #, no-c-format #. Tag: para msgid "Back up everything on the computer." msgstr "" -#: preparing.xml:939 +#: preparing.xml:940 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:949 +#: preparing.xml:950 #, no-c-format #. Tag: para msgid "Use the native partitioning tools to create native system partition(s). Leave either a place holder partition or free space for &debian;." msgstr "" -#: preparing.xml:956 +#: preparing.xml:957 #, no-c-format #. Tag: para msgid "Install the native operating system on its new partition." msgstr "" -#: preparing.xml:961 +#: preparing.xml:962 #, no-c-format #. Tag: para msgid "Boot back into the native system to verify everything's OK, and to download the Debian installer boot files." msgstr "" -#: preparing.xml:967 +#: preparing.xml:968 #, no-c-format #. Tag: para msgid "Boot the Debian installer to continue installing Debian." msgstr "" -#: preparing.xml:981 +#: preparing.xml:982 #, no-c-format #. Tag: title msgid "Partitioning in Tru64 UNIX" msgstr "" -#: preparing.xml:982 +#: preparing.xml:983 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:994 +#: preparing.xml:995 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1007 +#: preparing.xml:1008 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1016 +#: preparing.xml:1017 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1025 +#: preparing.xml:1026 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1034 +#: preparing.xml:1035 #, no-c-format #. Tag: title msgid "Partitioning in Windows NT" msgstr "" -#: preparing.xml:1036 +#: preparing.xml:1037 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1049 +#: preparing.xml:1050 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1066 +#: preparing.xml:1067 #, no-c-format #. Tag: title msgid "Partitioning From DOS or Windows" msgstr "" -#: preparing.xml:1067 +#: preparing.xml:1068 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1075 +#: preparing.xml:1076 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1089 +#: preparing.xml:1090 #, no-c-format #. Tag: title msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" msgstr "" -#: preparing.xml:1092 +#: preparing.xml:1093 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1104 +#: preparing.xml:1105 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1113 +#: preparing.xml:1114 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1122 +#: preparing.xml:1123 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1135 +#: preparing.xml:1136 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1145 +#: preparing.xml:1146 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1151 +#: preparing.xml:1152 #, no-c-format #. Tag: para msgid "Note that there are many other partition managers out there, in case <command>fips</command> doesn't do the trick for you." msgstr "" -#: preparing.xml:1159 +#: preparing.xml:1160 #, no-c-format #. Tag: title msgid "Partitioning for DOS" msgstr "" -#: preparing.xml:1161 +#: preparing.xml:1162 #, no-c-format #. Tag: para 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 "" -#: preparing.xml:1169 +#: preparing.xml:1170 #, 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. You should do this prior to running DOS's <command>format</command> command by executing the following command from Linux:" msgstr "" -#: preparing.xml:1176 +#: preparing.xml:1177 #, no-c-format #. Tag: screen msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" msgstr "" -#: preparing.xml:1187 +#: preparing.xml:1188 #, no-c-format #. Tag: title msgid "Partitioning in AmigaOS" msgstr "" -#: preparing.xml:1188 +#: preparing.xml:1189 #, 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:1196 +#: preparing.xml:1197 #, no-c-format #. Tag: title msgid "Partitioning in Atari TOS" msgstr "" -#: preparing.xml:1197 +#: preparing.xml:1198 #, 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:1208 +#: preparing.xml:1209 #, 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:1217 +#: preparing.xml:1218 #, 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:1223 +#: preparing.xml:1224 #, 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:1233 +#: preparing.xml:1234 #, 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:1245 +#: preparing.xml:1246 #, 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:1255 +#: preparing.xml:1256 #, 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:1261 +#: preparing.xml:1262 #, 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:1273 +#: preparing.xml:1274 #, 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:1288 +#: preparing.xml:1289 #, no-c-format #. Tag: title msgid "Partitioning in MacOS" msgstr "" -#: preparing.xml:1289 +#: preparing.xml:1290 #, 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:1300 +#: preparing.xml:1301 #, 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:1316 +#: preparing.xml:1317 #, no-c-format #. Tag: title msgid "Partitioning from SunOS" msgstr "" -#: preparing.xml:1318 +#: preparing.xml:1319 #, 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:1333 +#: preparing.xml:1334 #, no-c-format #. Tag: title msgid "Partitioning from Linux or another OS" msgstr "" -#: preparing.xml:1335 +#: preparing.xml:1336 #, 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:1347 +#: preparing.xml:1348 #, 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:1362 +#: preparing.xml:1363 #, no-c-format #. Tag: title msgid "MacOS/OSX Partitioning" msgstr "" -#: preparing.xml:1364 +#: preparing.xml:1365 #, 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:1371 +#: preparing.xml:1372 #, 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:1377 +#: preparing.xml:1378 #, 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:1390 +#: preparing.xml:1391 #, 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:1410 +#: preparing.xml:1411 #, no-c-format #. Tag: title msgid "Pre-Installation Hardware and Operating System Setup" msgstr "" -#: preparing.xml:1411 +#: preparing.xml:1412 #, 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:1428 +#: preparing.xml:1429 #, no-c-format #. Tag: title msgid "Invoking the BIOS Set-Up Menu" msgstr "" -#: preparing.xml:1430 +#: preparing.xml:1431 #, 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:1439 +#: preparing.xml:1440 #, 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:1453 +#: preparing.xml:1454 #, no-c-format #. Tag: term msgid "AMI BIOS" msgstr "" -#: preparing.xml:1454 +#: preparing.xml:1455 #, no-c-format #. Tag: para msgid "<keycap>Delete</keycap> key during the POST (power on self test)" msgstr "" -#: preparing.xml:1462 +#: preparing.xml:1463 #, no-c-format #. Tag: term msgid "Award BIOS" msgstr "" -#: preparing.xml:1463 +#: preparing.xml:1464 #, 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:1472 +#: preparing.xml:1473 #, no-c-format #. Tag: term msgid "DTK BIOS" msgstr "" -#: preparing.xml:1473 +#: preparing.xml:1474 #, no-c-format #. Tag: para msgid "<keycap>Esc</keycap> key during the POST" msgstr "" -#: preparing.xml:1480 +#: preparing.xml:1481 #, no-c-format #. Tag: term msgid "IBM PS/2 BIOS" msgstr "" -#: preparing.xml:1481 +#: preparing.xml:1482 #, 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:1495 +#: preparing.xml:1496 #, no-c-format #. Tag: term msgid "Phoenix BIOS" msgstr "" -#: preparing.xml:1496 +#: preparing.xml:1497 #, 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:1512 +#: preparing.xml:1513 #, 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:1517 +#: preparing.xml:1518 #, 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:1528 preparing.xml:1872 +#: preparing.xml:1529 preparing.xml:1873 #, no-c-format #. Tag: title msgid "Boot Device Selection" msgstr "" -#: preparing.xml:1530 +#: preparing.xml:1531 #, 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:1541 +#: preparing.xml:1542 #, 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:1548 +#: preparing.xml:1549 #, no-c-format #. Tag: para 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:1556 +#: preparing.xml:1557 #, 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:1565 +#: preparing.xml:1566 #, no-c-format #. Tag: title msgid "Changing the Boot Order on IDE Computers" msgstr "" -#: preparing.xml:1568 +#: preparing.xml:1569 #, 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:1575 +#: preparing.xml:1576 #, 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:1580 +#: preparing.xml:1581 #, no-c-format #. Tag: para msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." msgstr "" -#: preparing.xml:1585 +#: preparing.xml:1586 #, no-c-format #. Tag: para msgid "C is the hard drive, and A is the floppy drive." msgstr "" -#: preparing.xml:1591 +#: preparing.xml:1592 #, 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:1599 +#: preparing.xml:1600 #, 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:1609 +#: preparing.xml:1610 #, no-c-format #. Tag: title msgid "Changing the Boot Order on SCSI Computers" msgstr "" -#: preparing.xml:1613 +#: preparing.xml:1614 #, no-c-format #. Tag: para msgid "As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" -#: preparing.xml:1618 +#: preparing.xml:1619 #, 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:1624 +#: preparing.xml:1625 #, 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:1632 +#: preparing.xml:1633 #, no-c-format #. Tag: para msgid "Find the utility for changing the boot order." msgstr "" -#: preparing.xml:1637 +#: preparing.xml:1638 #, 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:1643 +#: preparing.xml:1644 #, 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:1657 +#: preparing.xml:1658 #, no-c-format #. Tag: title msgid "Miscellaneous BIOS Settings" msgstr "" -#: preparing.xml:1659 +#: preparing.xml:1660 #, no-c-format #. Tag: title msgid "CD-ROM Settings" msgstr "" -#: preparing.xml:1660 +#: preparing.xml:1661 #, 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:1670 +#: preparing.xml:1671 #, no-c-format #. Tag: title msgid "Extended vs. Expanded Memory" msgstr "" -#: preparing.xml:1671 +#: preparing.xml:1672 #, 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:1681 +#: preparing.xml:1682 #, no-c-format #. Tag: title msgid "Virus Protection" msgstr "" -#: preparing.xml:1682 +#: preparing.xml:1683 #, 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:1703 +#: preparing.xml:1704 #, no-c-format #. Tag: title msgid "Shadow RAM" msgstr "" -#: preparing.xml:1704 +#: preparing.xml:1705 #, 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:1721 +#: preparing.xml:1722 #, no-c-format #. Tag: title msgid "Memory Hole" msgstr "" -#: preparing.xml:1722 +#: preparing.xml:1723 #, 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:1728 +#: preparing.xml:1729 #, 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:1744 +#: preparing.xml:1745 #, no-c-format #. Tag: title msgid "Advanced Power Management" msgstr "" -#: preparing.xml:1745 +#: preparing.xml:1746 #, 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:1763 +#: preparing.xml:1764 #, no-c-format #. Tag: title msgid "Firmware Revisions and Existing OS Setup" msgstr "" -#: preparing.xml:1765 +#: preparing.xml:1766 #, 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:1788 +#: preparing.xml:1789 #, no-c-format #. Tag: title msgid "Invoking OpenFirmware" msgstr "" -#: preparing.xml:1789 +#: preparing.xml:1790 #, 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:1797 +#: preparing.xml:1798 #, 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:1806 +#: preparing.xml:1807 #, no-c-format #. Tag: para msgid "" @@ -1656,43 +1656,43 @@ 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:1819 +#: preparing.xml:1820 #, 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 <guibutton>Save button</guibutton> to have the firmware patches installed to nvram." msgstr "" -#: preparing.xml:1839 +#: preparing.xml:1840 #, no-c-format #. Tag: title msgid "Invoking OpenBoot" msgstr "" -#: preparing.xml:1841 +#: preparing.xml:1842 #, 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 and simple scripts." msgstr "" -#: preparing.xml:1849 +#: preparing.xml:1850 #, 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:1861 +#: preparing.xml:1862 #, 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:1874 +#: preparing.xml:1875 #, 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 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:1884 +#: preparing.xml:1885 #, no-c-format #. Tag: para msgid "" @@ -1703,7 +1703,7 @@ msgid "" "</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:1907 +#: preparing.xml:1908 #, no-c-format #. Tag: para msgid "" @@ -1712,205 +1712,205 @@ msgid "" "</screen></informalexample> and under Solaris:" msgstr "" -#: preparing.xml:1926 +#: preparing.xml:1927 #, no-c-format #. Tag: screen msgid "eeprom boot-device=disk1:1" msgstr "" -#: preparing.xml:1936 +#: preparing.xml:1937 #, no-c-format #. Tag: title msgid "BIOS Setup" msgstr "" -#: preparing.xml:1937 +#: preparing.xml:1938 #, 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:1949 +#: preparing.xml:1950 #, 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:1959 +#: preparing.xml:1960 #, 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:1976 +#: preparing.xml:1977 #, no-c-format #. Tag: title msgid "Native and LPAR installations" msgstr "" -#: preparing.xml:1977 +#: preparing.xml:1978 #, 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:1991 +#: preparing.xml:1992 #, no-c-format #. Tag: title msgid "Installation as a VM guest" msgstr "" -#: preparing.xml:1993 +#: preparing.xml:1994 #, 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:2003 +#: preparing.xml:2004 #, 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:2015 +#: preparing.xml:2016 #, no-c-format #. Tag: title msgid "Setting up an installation server" msgstr "" -#: preparing.xml:2017 +#: preparing.xml:2018 #, 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:2025 +#: preparing.xml:2026 #, no-c-format #. Tag: para 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:2034 +#: preparing.xml:2035 #, no-c-format #. Tag: emphasis msgid "FIXME: more information needed — from a Redbook?" msgstr "" -#: preparing.xml:2040 +#: preparing.xml:2041 #, no-c-format #. Tag: title msgid "Hardware Issues to Watch Out For" msgstr "" -#: preparing.xml:2041 +#: preparing.xml:2042 #, 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:2051 +#: preparing.xml:2052 #, 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:2061 +#: preparing.xml:2062 #, 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:2073 +#: preparing.xml:2074 #, 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:2084 +#: preparing.xml:2085 #, 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:2092 +#: preparing.xml:2093 #, no-c-format #. Tag: title msgid "The Turbo Switch" msgstr "" -#: preparing.xml:2093 +#: preparing.xml:2094 #, 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:2106 +#: preparing.xml:2107 #, no-c-format #. Tag: title msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "" -#: preparing.xml:2107 +#: preparing.xml:2108 #, 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:2115 +#: preparing.xml:2116 #, 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:2125 +#: preparing.xml:2126 #, no-c-format #. Tag: title msgid "Peripheral Hardware Settings" msgstr "" -#: preparing.xml:2126 +#: preparing.xml:2127 #, 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:2133 +#: preparing.xml:2134 #, 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:2144 +#: preparing.xml:2145 #, no-c-format #. Tag: title msgid "USB BIOS support and keyboards" msgstr "" -#: preparing.xml:2145 +#: preparing.xml:2146 #, 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:2158 +#: preparing.xml:2159 #, no-c-format #. Tag: title msgid "More than 64 MB RAM" msgstr "" -#: preparing.xml:2159 +#: preparing.xml:2160 #, 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\"/>." msgstr "" -#: preparing.xml:2168 +#: preparing.xml:2169 #, no-c-format #. Tag: title msgid "Display visibility on OldWorld Powermacs" msgstr "" -#: preparing.xml:2169 +#: preparing.xml:2170 #, no-c-format #. Tag: para msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver but possibly others as well, may not produce a colormap with reliably results in visible output under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of <quote>thousands</quote> or <quote>millions</quote>." diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index 040668193..65a911ff1 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" -"POT-Creation-Date: 2006-06-21 12:48+0000\n" +"POT-Creation-Date: 2006-06-24 19:23+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" @@ -653,945 +653,957 @@ msgstr "" #: using-d-i.xml:781 #, no-c-format #. Tag: para -msgid "If you choose guided partitioning, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind, that guided partitioning needs certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." +msgid "If you choose guided partitioning, you may have two options: to create partitions directly on the hard disk (classic method) or to use Logical Volume Management (LVM). In the second case, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. Note: the option to use LVM may not be available on all architectures." msgstr "" -#: using-d-i.xml:797 +#: using-d-i.xml:790 +#, no-c-format +#. Tag: para +msgid "After you choose guided partitioning (either classic or using LVM), you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in <xref linkend=\"partitioning\"/>. If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." +msgstr "" + +#: using-d-i.xml:807 #, no-c-format #. Tag: entry msgid "Partitioning scheme" msgstr "" -#: using-d-i.xml:798 +#: using-d-i.xml:808 #, no-c-format #. Tag: entry msgid "Minimum space" msgstr "" -#: using-d-i.xml:799 +#: using-d-i.xml:809 #, no-c-format #. Tag: entry msgid "Created partitions" msgstr "" -#: using-d-i.xml:805 +#: using-d-i.xml:815 #, no-c-format #. Tag: entry msgid "All files in one partition" msgstr "" -#: using-d-i.xml:806 +#: using-d-i.xml:816 #, no-c-format #. Tag: entry msgid "600MB" msgstr "" -#: using-d-i.xml:807 +#: using-d-i.xml:817 #, no-c-format #. Tag: entry msgid "<filename>/</filename>, swap" msgstr "" -#: using-d-i.xml:809 +#: using-d-i.xml:819 #, no-c-format #. Tag: entry -msgid "Desktop machine" +msgid "Separate /home partition" msgstr "" -#: using-d-i.xml:810 +#: using-d-i.xml:820 #, no-c-format #. Tag: entry msgid "500MB" msgstr "" -#: using-d-i.xml:811 +#: using-d-i.xml:821 #, no-c-format #. Tag: entry msgid "<filename>/</filename>, <filename>/home</filename>, swap" msgstr "" -#: using-d-i.xml:815 +#: using-d-i.xml:825 #, no-c-format #. Tag: entry -msgid "Multi-user workstation" +msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "" -#: using-d-i.xml:816 +#: using-d-i.xml:826 #, no-c-format #. Tag: entry msgid "<entry>1GB</entry>" msgstr "" -#: using-d-i.xml:817 +#: using-d-i.xml:827 #, no-c-format #. Tag: entry msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" msgstr "" -#: using-d-i.xml:826 +#: using-d-i.xml:836 #, no-c-format #. Tag: para -msgid "If you chose an automatic partitioning for your IA64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." +msgid "If you choose guided partitioning using LVM, the installer will also create a separate /boot partition. The other partitions, except for the swap partition, will be created inside the LVM partition." msgstr "" -#: using-d-i.xml:834 +#: using-d-i.xml:842 #, no-c-format #. Tag: para -msgid "If you chose an automatic partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader." +msgid "If you choose guided partitioning for your IA64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." msgstr "" -#: using-d-i.xml:840 +#: using-d-i.xml:850 +#, no-c-format +#. Tag: para +msgid "If you choose guided partitioning for your Alpha system, an additional, unformatted partition will be allocated at the beginning of your disk to reserve this space for the aboot boot loader." +msgstr "" + +#: using-d-i.xml:856 #, no-c-format #. Tag: para msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted." msgstr "" -#: using-d-i.xml:846 +#: using-d-i.xml:862 #, no-c-format #. Tag: para msgid "" "The list of partitions might look like this: <informalexample><screen>\n" " IDE1 master (hda) - 6.4 GB WDC AC36400L\n" - " #1 primary 16.4 MB ext2 /boot\n" - " #2 primary 551.0 MB swap swap\n" - " #3 primary 5.8 GB ntfs\n" - " pri/log 8.2 MB FREE SPACE\n" + " #1 primary 16.4 MB B f ext2 /boot\n" + " #2 primary 551.0 MB swap swap\n" + " #3 primary 5.8 GB ntfs\n" + " pri/log 8.2 MB FREE SPACE\n" "\n" " IDE1 slave (hdb) - 80.0 GB ST380021A\n" - " #1 primary 15.9 MB ext3\n" - " #2 primary 996.0 MB fat16\n" - " #3 primary 3.9 GB xfs /home\n" - " #5 logical 6.0 GB ext3 /\n" - " #6 logical 1.0 GB ext3 /var\n" - " #7 logical 498.8 MB ext3\n" - " #8 logical 551.5 MB swap swap\n" - " #9 logical 65.8 GB ext2\n" - "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any)." + " #1 primary 15.9 MB ext3\n" + " #2 primary 996.0 MB fat16\n" + " #3 primary 3.9 GB xfs /home\n" + " #5 logical 6.0 GB f ext3 /\n" + " #6 logical 1.0 GB f ext3 /var\n" + " #7 logical 498.8 MB ext3\n" + " #8 logical 551.5 MB swap swap\n" + " #9 logical 65.8 GB ext2\n" + "</screen></informalexample> This example shows two IDE harddrives divided into several partitions; the first disk has some free space. Each partition line consists of the partition number, its type, size, optional flags, file system, and mountpoint (if any). Note: this particular setup cannot be created using guided partitioning but it does show possible variation that can be achieved using manual partitioning)." msgstr "" -#: using-d-i.xml:858 +#: using-d-i.xml:875 #, no-c-format #. Tag: para -msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem>, to run guided partitioning again or modify the proposed changes as described below for manual partitioning." +msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to <guimenuitem>Undo changes to partitions</guimenuitem><footnote> <para> If you selected guided partitioning using LVM, you will not be able to undo all changes made as some changes will already have been committed to the hard disk. The installer will warn you before that happens though. </para> </footnote> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" -#: using-d-i.xml:868 +#: using-d-i.xml:895 #, no-c-format #. Tag: para msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually setup your partition table and the usage of partitions by your new Debian system will be covered in the remainder of this section." msgstr "" -#: using-d-i.xml:876 +#: using-d-i.xml:903 #, no-c-format #. Tag: para msgid "If you select a pristine disk which doesn't have neither partitions nor free space on it, you will be offered to create a new partition table (this is needed so you can create new partitions). After this a new line entitled <quote>FREE SPACE</quote> should appear under the selected disk." msgstr "" -#: using-d-i.xml:884 +#: using-d-i.xml:911 #, no-c-format #. Tag: para -msgid "If you select some free space, you will be offered to create new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with detailed overview of your new partition. There are options like mountpoint, mount options, bootable flag, or way of usage. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose different filesystem for this partition including the possibility to use the partition for swap, software RAID, LVM, or not use it at all. Other nice feature is the possibility to copy data from existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will be thrown back to the <command>partman</command>'s main screen." +msgid "If you select some free space, you will be offered to create new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with detailed overview of your new partition. There are options like mountpoint, mount options, bootable flag, or way of usage. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option <guimenuitem>Use as:</guimenuitem>, you can choose different filesystem for this partition including the possibility to use the partition for swap, software RAID, LVM, or not use it at all. Other nice feature is the possibility to copy data from existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will be thrown back to <command>partman</command>'s main screen." msgstr "" -#: using-d-i.xml:902 +#: using-d-i.xml:929 #, no-c-format #. Tag: para msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. Because this is the same screen like when creating a new partition, you can change the same set of options. One thing which might not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." msgstr "" -#: using-d-i.xml:913 +#: using-d-i.xml:940 #, no-c-format #. Tag: para msgid "Be sure to create at least two partitions: one for the <emphasis>root</emphasis> filesystem (which must be mounted as <filename>/</filename>) and one for <emphasis>swap</emphasis>. If you forget to mount the root filesystem, <command>partman</command> won't let you continue until you correct this issue." msgstr "" -#: using-d-i.xml:921 +#: using-d-i.xml:948 #, no-c-format #. Tag: para -msgid "If you forget to select and format an EFI boot partition <command>partman</command> will detect this and will not let you continue until you allocate one." +msgid "If you forget to select and format an EFI boot partition, <command>partman</command> will detect this and will not let you continue until you allocate one." msgstr "" -#: using-d-i.xml:927 +#: using-d-i.xml:954 #, no-c-format #. Tag: para msgid "Capabilities of <command>partman</command> can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. <filename>partman-ext3</filename>, <filename>partman-xfs</filename>, or <filename>partman-lvm</filename>)." msgstr "" -#: using-d-i.xml:935 +#: using-d-i.xml:962 #, no-c-format #. Tag: para msgid "After you are satisfied with partitioning, select <guimenuitem>Finish partitioning and write changes to disk</guimenuitem> from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested." msgstr "" -#: using-d-i.xml:963 +#: using-d-i.xml:990 #, no-c-format #. Tag: title msgid "Configuring Logical Volume Manager (LVM)" msgstr "" -#: using-d-i.xml:964 +#: using-d-i.xml:991 #, no-c-format #. Tag: para msgid "If you are working with computers at the level of system administrator or <quote>advanced</quote> user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation with moving stuff around, symlinking, etc." msgstr "" -#: using-d-i.xml:972 +#: using-d-i.xml:999 #, no-c-format #. Tag: para msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (<firstterm>physical volumes</firstterm> in LVM lingo) to form a virtual disc (so called <firstterm>volume group</firstterm>), which can then be divided into virtual partitions (<firstterm>logical volumes</firstterm>). The point is that logical volumes (and of course underlying volume groups) can span across several physical discs." msgstr "" -#: using-d-i.xml:982 +#: using-d-i.xml:1009 #, no-c-format #. Tag: para msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disc to the computer, join it with your existing volume group and then resize the logical volume which holds your <filename>/home</filename> filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." msgstr "" -#: using-d-i.xml:993 +#: using-d-i.xml:1020 #, no-c-format #. Tag: para msgid "LVM setup in &d-i; is quite simple. At first, you have to mark your partitions to be used as physical volumes for LVM. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>.) Then start the <command>lvmcfg</command> module (either directly from <command>partman</command> or from the &d-i;'s main menu) and combine physical volumes to volume group(s) under the <guimenuitem>Modify volume groups (VG)</guimenuitem> menu. After that, you should create logical volumes on the top of volume groups from the menu <guimenuitem>Modify logical volumes (LV)</guimenuitem>." msgstr "" -#: using-d-i.xml:1008 +#: using-d-i.xml:1035 #, no-c-format #. Tag: para msgid "After returning from <command>lvmcfg</command> back to <command>partman</command>, you will see any created logical volumes in the same way as ordinary partitions (and you should treat them like that)." msgstr "" -#: using-d-i.xml:1023 +#: using-d-i.xml:1050 #, no-c-format #. Tag: title msgid "Configuring Multidisk Device (Software RAID)" msgstr "" -#: using-d-i.xml:1024 +#: using-d-i.xml:1051 #, no-c-format #. Tag: para msgid "If you have more than one harddrive<footnote><para> To be honest, you can construct MD device even from partitions residing on single physical drive, but that won't bring you anything useful. </para></footnote> in your computer, you can use <command>mdcfg</command> to setup your drives for increased performance and/or better reliability of your data. The result is called <firstterm>Multidisk Device</firstterm> (or after its most famous variant <firstterm>software RAID</firstterm>)." msgstr "" -#: using-d-i.xml:1038 +#: using-d-i.xml:1065 #, no-c-format #. Tag: para msgid "MD is basically a bunch of partitions located on different disks and combined together to form a <emphasis>logical</emphasis> device. This device can then be used like an ordinary partition (i.e. in <command>partman</command> you can format it, assign a mountpoint, etc.)." msgstr "" -#: using-d-i.xml:1046 +#: using-d-i.xml:1073 #, no-c-format #. Tag: para msgid "The benefit you gain depends on a type of a MD device you are creating. Currently supported are: <variablelist> <varlistentry> <term>RAID0</term><listitem><para> Is mainly aimed at performance. RAID0 splits all incoming data into <firstterm>stripes</firstterm> and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will loose <emphasis>everything</emphasis> (part of the information is still on the healthy disk(s), the other part <emphasis>was</emphasis> on the failed disk). </para><para> The typical use for RAID0 is a partition for video editing. </para></listitem> </varlistentry> <varlistentry> <term>RAID1</term><listitem><para> Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file reads are load balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. </para><para> Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para></listitem> </varlistentry> <varlistentry> <term>RAID5</term><listitem><para> Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incomming data into stripes and distributes them equally on all but one disks (similar to RAID0). Unlike RAID0, RAID5 also computes <firstterm>parity</firstterm> information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. </para><para> As you can see, RAID5 has similar degree of reliability like RAID1 while achieving less redundancy. On the other hand it might be a bit slower on write operation than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:" msgstr "" -#: using-d-i.xml:1124 +#: using-d-i.xml:1151 #, no-c-format #. Tag: entry msgid "Type" msgstr "" -#: using-d-i.xml:1125 +#: using-d-i.xml:1152 #, no-c-format #. Tag: entry msgid "Minimum Devices" msgstr "" -#: using-d-i.xml:1126 +#: using-d-i.xml:1153 #, no-c-format #. Tag: entry msgid "Spare Device" msgstr "" -#: using-d-i.xml:1127 +#: using-d-i.xml:1154 #, no-c-format #. Tag: entry msgid "Survives disk failure?" msgstr "" -#: using-d-i.xml:1128 +#: using-d-i.xml:1155 #, no-c-format #. Tag: entry msgid "Available Space" msgstr "" -#: using-d-i.xml:1134 +#: using-d-i.xml:1161 #, no-c-format #. Tag: entry msgid "RAID0" msgstr "" -#: using-d-i.xml:1135 using-d-i.xml:1143 +#: using-d-i.xml:1162 using-d-i.xml:1170 #, no-c-format #. Tag: entry msgid "<entry>2</entry>" msgstr "" -#: using-d-i.xml:1136 using-d-i.xml:1137 +#: using-d-i.xml:1163 using-d-i.xml:1164 #, no-c-format #. Tag: entry msgid "<entry>no</entry>" msgstr "" -#: using-d-i.xml:1138 +#: using-d-i.xml:1165 #, no-c-format #. Tag: entry msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" -#: using-d-i.xml:1142 +#: using-d-i.xml:1169 #, no-c-format #. Tag: entry msgid "RAID1" msgstr "" -#: using-d-i.xml:1144 using-d-i.xml:1152 +#: using-d-i.xml:1171 using-d-i.xml:1179 #, no-c-format #. Tag: entry msgid "optional" msgstr "" -#: using-d-i.xml:1145 using-d-i.xml:1153 +#: using-d-i.xml:1172 using-d-i.xml:1180 #, no-c-format #. Tag: entry msgid "<entry>yes</entry>" msgstr "" -#: using-d-i.xml:1146 +#: using-d-i.xml:1173 #, no-c-format #. Tag: entry msgid "Size of the smallest partition in RAID" msgstr "" -#: using-d-i.xml:1150 +#: using-d-i.xml:1177 #, no-c-format #. Tag: entry msgid "RAID5" msgstr "" -#: using-d-i.xml:1151 +#: using-d-i.xml:1178 #, no-c-format #. Tag: entry msgid "<entry>3</entry>" msgstr "" -#: using-d-i.xml:1154 +#: using-d-i.xml:1181 #, no-c-format #. Tag: entry msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" -#: using-d-i.xml:1162 +#: using-d-i.xml:1189 #, no-c-format #. Tag: para msgid "If you want to know the whole truth about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." msgstr "" -#: using-d-i.xml:1167 +#: using-d-i.xml:1194 #, no-c-format #. Tag: para msgid "To create a MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in <command>partman</command> in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for RAID</guimenuitem> </menuchoice>.)" msgstr "" -#: using-d-i.xml:1176 +#: using-d-i.xml:1203 #, no-c-format #. Tag: para msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (<filename>/</filename>) filesystem. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." msgstr "" -#: using-d-i.xml:1185 +#: using-d-i.xml:1212 #, no-c-format #. Tag: para msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. On the first screen of <command>mdcfg</command> simply select <guimenuitem>Create MD device</guimenuitem>. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" -#: using-d-i.xml:1196 +#: using-d-i.xml:1223 #, no-c-format #. Tag: para msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" -#: using-d-i.xml:1203 +#: using-d-i.xml:1230 #, no-c-format #. Tag: para msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided few seconds ago. Don't worry. If you make a mistake and select different number of partitions, the &d-i; won't let you continue until you correct the issue." msgstr "" -#: using-d-i.xml:1215 +#: using-d-i.xml:1242 #, no-c-format #. Tag: para msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" -#: using-d-i.xml:1223 +#: using-d-i.xml:1250 #, no-c-format #. Tag: para msgid "It is perfectly possible to have several types of MD at once. For example if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine first partitions on all three disk into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for <filename>/home</filename>)." msgstr "" -#: using-d-i.xml:1232 +#: using-d-i.xml:1259 #, no-c-format #. Tag: para msgid "After you setup MD devices to your liking, you can <guimenuitem>Finish</guimenuitem> <command>mdcfg</command> to return back to the <command>partman</command> to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" -#: using-d-i.xml:1245 +#: using-d-i.xml:1272 #, no-c-format #. Tag: title msgid "Setting up the System" msgstr "" -#: using-d-i.xml:1246 +#: using-d-i.xml:1273 #, no-c-format #. Tag: para msgid "After partitioning the installer asks a few more questions that will be used to set up the system it is about to install." msgstr "" -#: using-d-i.xml:1258 +#: using-d-i.xml:1285 #, no-c-format #. Tag: title msgid "Configuring Your Time Zone" msgstr "" -#: using-d-i.xml:1260 +#: using-d-i.xml:1287 #, no-c-format #. Tag: para msgid "Depending on the location selected at the beginning of the installation process, you might be shown a list of timezones relevant for that location. If your location has only one time zone, you will not be asked anything and the system will assume that time zone." msgstr "" -#: using-d-i.xml:1276 +#: using-d-i.xml:1303 #, no-c-format #. Tag: title msgid "Configuring the Clock" msgstr "" -#: using-d-i.xml:1278 +#: using-d-i.xml:1305 #, no-c-format #. Tag: para msgid "The installer might ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" -#: using-d-i.xml:1285 +#: using-d-i.xml:1312 #, no-c-format #. Tag: para msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. <phrase arch=\"m68k;powerpc\">Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase> <phrase arch=\"i386\">Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of GMT.</phrase>" msgstr "" -#: using-d-i.xml:1296 +#: using-d-i.xml:1323 #, no-c-format #. Tag: para msgid "Note that the installer does not currently allow you to actually set the time in the computer's clock. You can set the clock to the current time after you have installed, if it is incorrect or if it was previously not set to UTC." msgstr "" -#: using-d-i.xml:1312 +#: using-d-i.xml:1339 #, no-c-format #. Tag: title msgid "Setting Up Users And Passwords" msgstr "" -#: using-d-i.xml:1315 +#: using-d-i.xml:1342 #, no-c-format #. Tag: title msgid "Set the Root Password" msgstr "" -#: using-d-i.xml:1317 +#: using-d-i.xml:1344 #, no-c-format #. Tag: para msgid "The <emphasis>root</emphasis> account is also called the <emphasis>super-user</emphasis>; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." msgstr "" -#: using-d-i.xml:1325 +#: using-d-i.xml:1352 #, no-c-format #. Tag: para msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." msgstr "" -#: using-d-i.xml:1333 +#: using-d-i.xml:1360 #, no-c-format #. Tag: para msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." msgstr "" -#: using-d-i.xml:1343 +#: using-d-i.xml:1370 #, no-c-format #. Tag: title msgid "Create an Ordinary User" msgstr "" -#: using-d-i.xml:1345 +#: using-d-i.xml:1372 #, no-c-format #. Tag: para msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should <emphasis>not</emphasis> use the root account for daily use or as your personal login." msgstr "" -#: using-d-i.xml:1352 +#: using-d-i.xml:1379 #, no-c-format #. Tag: para msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a <emphasis>Trojan-horse</emphasis> program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." msgstr "" -#: using-d-i.xml:1362 +#: using-d-i.xml:1389 #, no-c-format #. Tag: para msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." msgstr "" -#: using-d-i.xml:1369 +#: using-d-i.xml:1396 #, no-c-format #. Tag: para msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." msgstr "" -#: using-d-i.xml:1381 +#: using-d-i.xml:1408 #, no-c-format #. Tag: title msgid "Installing the Base System" msgstr "" -#: using-d-i.xml:1382 +#: using-d-i.xml:1409 #, no-c-format #. Tag: para msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" -#: using-d-i.xml:1396 +#: using-d-i.xml:1423 #, no-c-format #. Tag: title msgid "Base System Installation" msgstr "" -#: using-d-i.xml:1398 +#: using-d-i.xml:1425 #, no-c-format #. Tag: para msgid "During the Base installation, package unpacking and setup messages are redirected to <userinput>tty4</userinput>. You can access this terminal by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</keycap></keycombo>; get back to the main installer process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></keycombo>." msgstr "" -#: using-d-i.xml:1408 +#: using-d-i.xml:1435 #, no-c-format #. Tag: para msgid "The unpack/setup messages generated by the base installation are saved in <filename>/var/log/syslog</filename> when the installation is performed over a serial console." msgstr "" -#: using-d-i.xml:1414 +#: using-d-i.xml:1441 #, no-c-format #. Tag: para msgid "As part of the installation, a Linux kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" -#: using-d-i.xml:1427 +#: using-d-i.xml:1454 #, no-c-format #. Tag: title msgid "Installing Additional Software" msgstr "" -#: using-d-i.xml:1428 +#: using-d-i.xml:1455 #, no-c-format #. Tag: para msgid "After the base system is installed, you have a usable but limited system. Most users will want to add additional software to the system to tune it to their needs, and the installer lets you do so. This step can take even longer than installing the base system if you have a slow computer or network." msgstr "" -#: using-d-i.xml:1442 +#: using-d-i.xml:1469 #, no-c-format #. Tag: title msgid "Configuring apt" msgstr "" -#: using-d-i.xml:1444 +#: using-d-i.xml:1471 #, no-c-format #. Tag: para msgid "The main means that people use to install packages on their system is via a program called <command>apt-get</command>, from the <classname>apt</classname> package.<footnote> <para> Note that the actual program that installs packages is called <command>dpkg</command>. However, this program is more of a low-level tool. <command>apt-get</command> is a higher-level tool as it will invoke <command>dpkg</command> as appropriate and also because it knows to install other packages which are required for the package you're trying to install, as well as how to retrieve the package from your CD, the network, or wherever. </para> </footnote> Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command> are also in use and depend on <command>apt-get</command>. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface." msgstr "" -#: using-d-i.xml:1468 +#: using-d-i.xml:1495 #, no-c-format #. Tag: para msgid "<command>apt</command> must be configured so that it knows where to retrieve packages from. The installer largely takes care of this automatically based on what it knows about your installation medium. The results of this configuration are written to the file <filename>/etc/apt/sources.list</filename>, and you can examine and edit it to your liking after the install is complete." msgstr "" -#: using-d-i.xml:1484 +#: using-d-i.xml:1511 #, no-c-format #. Tag: title msgid "Selecting and Installing Software" msgstr "" -#: using-d-i.xml:1486 +#: using-d-i.xml:1513 #, no-c-format #. Tag: para msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" -#: using-d-i.xml:1495 +#: using-d-i.xml:1522 #, no-c-format #. Tag: para msgid "So, you have the ability to choose <emphasis>tasks</emphasis> first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as <quote>Desktop environment</quote>, <quote>Web server</quote>, or <quote>Print server</quote><footnote> <para> You should know that to present this list, the installer is merely invoking the <command>tasksel</command> program. It can be run at any time after installation to install (or remove) more packages, or you can use a more fine-grained tool such as <command>aptitude</command>. If you are looking for a specific single package, after installation is complete, simply run <userinput>aptitude install <replaceable>package</replaceable></userinput>, where <replaceable>package</replaceable> is the name of the package you are looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> lists the space requirements for the available tasks." msgstr "" -#: using-d-i.xml:1520 +#: using-d-i.xml:1547 #, no-c-format #. Tag: para msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages you've selected." msgstr "" -#: using-d-i.xml:1527 +#: using-d-i.xml:1554 #, no-c-format #. Tag: para msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" -#: using-d-i.xml:1534 +#: using-d-i.xml:1561 #, no-c-format #. Tag: para msgid "Note that some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can un-select the tasks. You can even opt to install no tasks at all at this point." msgstr "" -#: using-d-i.xml:1542 +#: using-d-i.xml:1569 #, no-c-format #. Tag: para msgid "Each package you selected with <command>tasksel</command> is downloaded, unpacked and then installed in turn by the <command>apt-get</command> and <command>dpkg</command> programs. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" -#: using-d-i.xml:1551 +#: using-d-i.xml:1578 #, no-c-format #. Tag: title msgid "Configuring Your Mail Transport Agent" msgstr "" -#: using-d-i.xml:1553 +#: using-d-i.xml:1580 #, no-c-format #. Tag: para msgid "Today, email is a very important part of many people's life, so it's no surprise Debian lets you configure your mail system right as a part of the installation process. The standard mail transport agent in Debian is <command>exim4</command>, which is relatively small, flexible, and easy to learn." msgstr "" -#: using-d-i.xml:1561 +#: using-d-i.xml:1588 #, no-c-format #. Tag: para msgid "You may ask if this is needed even if your computer is not connected to any network. The short answer is: Yes. The longer explanation: Some system utilities (like <command>cron</command>, <command>quota</command>, <command>aide</command>, …) may send you important notices via email." msgstr "" -#: using-d-i.xml:1569 +#: using-d-i.xml:1596 #, no-c-format #. Tag: para msgid "So on the first screen you will be presented with several common mail scenarios. Choose the one that most closely resembles your needs:" msgstr "" -#: using-d-i.xml:1578 +#: using-d-i.xml:1605 #, no-c-format #. Tag: term msgid "internet site" msgstr "" -#: using-d-i.xml:1579 +#: using-d-i.xml:1606 #, no-c-format #. Tag: para msgid "Your system is connected to a network and your mail is sent and received directly using SMTP. On the following screens you will be asked a few basic questions, like your machine's mail name, or a list of domains for which you accept or relay mail." msgstr "" -#: using-d-i.xml:1590 +#: using-d-i.xml:1617 #, no-c-format #. Tag: term msgid "mail sent by smarthost" msgstr "" -#: using-d-i.xml:1591 +#: using-d-i.xml:1618 #, no-c-format #. Tag: para msgid "In this scenario is your outgoing mail forwarded to another machine, called a <quote>smarthost</quote>, which does the actual job for you. Smarthost also usually stores incoming mail addressed to your computer, so you don't need to be permanently online. That also means you have to download your mail from the smarthost via programs like fetchmail. This option is suitable for dial-up users." msgstr "" -#: using-d-i.xml:1604 +#: using-d-i.xml:1631 #, no-c-format #. Tag: term msgid "local delivery only" msgstr "" -#: using-d-i.xml:1605 +#: using-d-i.xml:1632 #, no-c-format #. Tag: para msgid "Your system is not on a network and mail is sent or received only between local users. Even if you don't plan to send any messages, this option is highly recommended, because some system utilities may send you various alerts from time to time (e.g. beloved <quote>Disk quota exceeded</quote>). This option is also convenient for new users, because it doesn't ask any further questions." msgstr "" -#: using-d-i.xml:1618 +#: using-d-i.xml:1645 #, no-c-format #. Tag: term msgid "no configuration at this time" msgstr "" -#: using-d-i.xml:1619 +#: using-d-i.xml:1646 #, no-c-format #. Tag: para msgid "Choose this if you are absolutely convinced you know what you are doing. This will leave you with an unconfigured mail system — until you configure it, you won't be able to send or receive any mail and you may miss some important messages from your system utilities." msgstr "" -#: using-d-i.xml:1630 +#: using-d-i.xml:1657 #, no-c-format #. Tag: para msgid "If none of these scenarios suits your needs, or if you need a finer setup, you will need to edit configuration files under the <filename>/etc/exim4</filename> directory after the installation is complete. More information about <command>exim4</command> may be found under <filename>/usr/share/doc/exim4</filename>." msgstr "" -#: using-d-i.xml:1645 +#: using-d-i.xml:1672 #, no-c-format #. Tag: title msgid "Making Your System Bootable" msgstr "" -#: using-d-i.xml:1647 +#: using-d-i.xml:1674 #, no-c-format #. Tag: para msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. <phrase arch=\"sparc\">You may wish to set the OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" -#: using-d-i.xml:1655 +#: using-d-i.xml:1682 #, no-c-format #. Tag: para msgid "Note that multiple operating systems booting on a single machine is still something of a black art. This document does not even attempt to document the various boot managers, which vary by architecture and even by subarchitecture. You should see your boot manager's documentation for more information." msgstr "" -#: using-d-i.xml:1670 +#: using-d-i.xml:1697 #, no-c-format #. Tag: title msgid "Detecting other operating systems" msgstr "" -#: using-d-i.xml:1672 +#: using-d-i.xml:1699 #, no-c-format #. Tag: para msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to Debian." msgstr "" -#: using-d-i.xml:1680 +#: using-d-i.xml:1707 #, no-c-format #. Tag: para msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" -#: using-d-i.xml:1698 +#: using-d-i.xml:1725 #, no-c-format #. Tag: title msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" -#: using-d-i.xml:1699 +#: using-d-i.xml:1726 #, no-c-format #. Tag: para msgid "If you have booted from SRM, if you select this option, the installer will write <command>aboot</command> to the first sector of the disk on which you installed Debian. Be <emphasis>very</emphasis> careful — it is <emphasis>not</emphasis> possible to boot multiple operating systems (e.g. GNU/Linux, Free/Open/NetBSD, OSF/1 a.k.a. Digital Unix a.k.a. Tru64 Unix, or OpenVMS) from the same disk. If you also have a different operating system installed on the disk where you have installed Debian, you will have to boot GNU/Linux from a floppy instead." msgstr "" -#: using-d-i.xml:1719 +#: using-d-i.xml:1746 #, no-c-format #. Tag: title msgid "<command>palo</command>-installer" msgstr "" -#: using-d-i.xml:1720 +#: using-d-i.xml:1747 #, no-c-format #. Tag: para msgid "The bootloader on PA-RISC is <quote>palo</quote>. <command>PALO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>PALO</command> allows you to boot any kernel image on your boot partition. This is because <command>PALO</command> can actually read Linux partitions." msgstr "" -#: using-d-i.xml:1729 +#: using-d-i.xml:1756 #, no-c-format #. Tag: para msgid "hppa FIXME ( need more info )" msgstr "" -#: using-d-i.xml:1741 +#: using-d-i.xml:1768 #, no-c-format #. Tag: title msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:1743 +#: using-d-i.xml:1770 #, no-c-format #. Tag: para msgid "The main &architecture; boot loader is called <quote>grub</quote>. Grub is a flexible and robust boot loader and a good default choice for newbies and old hands alike." msgstr "" -#: using-d-i.xml:1749 +#: using-d-i.xml:1776 #, no-c-format #. Tag: para msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" -#: using-d-i.xml:1755 +#: using-d-i.xml:1782 #, no-c-format #. Tag: para msgid "If you do not want to install grub at all, use the Back button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" -#: using-d-i.xml:1769 +#: using-d-i.xml:1796 #, no-c-format #. Tag: title msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:1771 +#: using-d-i.xml:1798 #, no-c-format #. Tag: para msgid "The second &architecture; boot loader is called <quote>LILO</quote>. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory <filename>/usr/share/doc/lilo/</filename> if you have special needs; also see the <ulink url=\"&url-lilo-howto;\">LILO mini-HOWTO</ulink>." msgstr "" -#: using-d-i.xml:1781 +#: using-d-i.xml:1808 #, no-c-format #. Tag: para msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be <firstterm>chainloaded</firstterm>. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" -#: using-d-i.xml:1789 +#: using-d-i.xml:1816 #, no-c-format #. Tag: para msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:" msgstr "" -#: using-d-i.xml:1796 +#: using-d-i.xml:1823 #, no-c-format #. Tag: term msgid "Master Boot Record (MBR)" msgstr "" -#: using-d-i.xml:1796 +#: using-d-i.xml:1823 #, no-c-format #. Tag: para msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" -#: using-d-i.xml:1803 +#: using-d-i.xml:1830 #, no-c-format #. Tag: term msgid "new Debian partition" msgstr "" -#: using-d-i.xml:1803 +#: using-d-i.xml:1830 #, no-c-format #. Tag: para msgid "Choose this if you want to use another boot manager. <command>LILO</command> will install itself at the beginning of the new Debian partition and it will serve as a secondary boot loader." msgstr "" -#: using-d-i.xml:1812 +#: using-d-i.xml:1839 #, no-c-format #. Tag: term msgid "Other choice" msgstr "" -#: using-d-i.xml:1812 +#: using-d-i.xml:1839 #, no-c-format #. Tag: para msgid "Useful for advanced users who want to install <command>LILO</command> somewhere else. In this case you will be asked for desired location. You can use devfs style names, such as those that start with <filename>/dev/ide</filename>, <filename>/dev/scsi</filename>, and <filename>/dev/discs</filename>, as well as traditional names, such as <filename>/dev/hda</filename> or <filename>/dev/sda</filename>." msgstr "" -#: using-d-i.xml:1824 +#: using-d-i.xml:1851 #, no-c-format #. Tag: para msgid "If you can no longer boot into Windows 9x (or DOS) after this step, you'll need to use a Windows 9x (MS-DOS) boot disk and use the <userinput>fdisk /mbr</userinput> command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian! For more information on this please read <xref linkend=\"reactivating-win\"/>." msgstr "" -#: using-d-i.xml:1841 +#: using-d-i.xml:1868 #, no-c-format #. Tag: title msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:1843 +#: using-d-i.xml:1870 #, no-c-format #. Tag: para msgid "The &architecture; boot loader is called <quote>elilo</quote>. It is modeled on the <quote>lilo</quote> boot loader for the x86 architecture and uses a similar configuration file. However, instead of writing an MBR or partition boot record to the disk, it copies the necessary files to a separate FAT formatted disk partition and modifies the <guimenuitem>EFI Boot Manager</guimenuitem> menu in the firmware to point to the files in the EFI partition. The <command>elilo</command> boot loader is really in two parts. The <filename>/usr/sbin/elilo</filename> command manages the partition and copies file into it. The <filename>elilo.efi</filename> program is copied into the EFI partition and then run by the <quote>EFI Boot Manager</quote> to actually do the work of loading and starting the Linux kernel." msgstr "" -#: using-d-i.xml:1859 +#: using-d-i.xml:1886 #, no-c-format #. Tag: para msgid "The <quote>elilo</quote> configuration and installation is done as the last step of installing the packages of the base installation. &d-i; will present you with a list of potential disk partitions that it has found suitable for an EFI partition. Select the partition you set up earlier in the installation, typically a partition on the same disk that contains your <emphasis>root</emphasis> filesystem." msgstr "" -#: using-d-i.xml:1871 +#: using-d-i.xml:1898 #, no-c-format #. Tag: title msgid "Choose the correct partition!" msgstr "" -#: using-d-i.xml:1873 +#: using-d-i.xml:1900 #, no-c-format #. Tag: para msgid "The criteria for selecting a partition is that it is FAT format filesystem with its <emphasis>boot</emphasis> flag set. &d-i; may show multiple choices depending on what it finds from scanning all of the disks of the system including EFI partitions of other system disks and EFI diagnostic partitions. Remember, the <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" -#: using-d-i.xml:1888 +#: using-d-i.xml:1915 #, no-c-format #. Tag: title msgid "EFI Partition Contents" msgstr "" -#: using-d-i.xml:1890 +#: using-d-i.xml:1917 #, no-c-format #. Tag: para msgid "The EFI partition is a FAT filesystem format partition on one of the hard disks of the system, usually the same disk that contains the <emphasis>root</emphasis> filesystem. It is normally not mounted on a running system as it is only needed by the <quote>EFI Boot Manager</quote> to load the system and the installer part of the <command>elilo</command> writes to the filesystem directly. The <command>/usr/sbin/elilo</command> utility writes the following files into the <filename>efi/debian</filename> directory of the EFI partition during the installation. Note that the <quote>EFI Boot Manager</quote> would find these files using the path <filename>fs<replaceable>n</replaceable>:\\efi\\debian</filename>. There may be other files in this filesystem as well over time as the system is updated or re-configured." msgstr "" -#: using-d-i.xml:1912 +#: using-d-i.xml:1939 #, no-c-format #. Tag: filename msgid "elilo.conf" msgstr "" -#: using-d-i.xml:1913 +#: using-d-i.xml:1940 #, no-c-format #. Tag: para msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the <filename>/etc/elilo.conf</filename> with the filenames re-written to refer to files in the EFI partition." msgstr "" -#: using-d-i.xml:1922 +#: using-d-i.xml:1949 #, no-c-format #. Tag: filename msgid "elilo.efi" msgstr "" -#: using-d-i.xml:1923 +#: using-d-i.xml:1950 #, no-c-format #. Tag: para msgid "This is the boot loader program that the <quote>EFI Boot Manager</quote> runs to boot the system. It is the program behind the <guimenuitem>Debian GNU/Linux</guimenuitem> menu item of the <quote>EFI Boot Manager</quote> command menu." msgstr "" -#: using-d-i.xml:1933 +#: using-d-i.xml:1960 #, no-c-format #. Tag: filename msgid "initrd.img" msgstr "" -#: using-d-i.xml:1934 +#: using-d-i.xml:1961 #, no-c-format #. Tag: para msgid "This is the initial root filesystem used to boot the kernel. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/initrd.img</filename>." msgstr "" -#: using-d-i.xml:1946 +#: using-d-i.xml:1973 #, no-c-format #. Tag: filename msgid "readme.txt" msgstr "" -#: using-d-i.xml:1947 +#: using-d-i.xml:1974 #, no-c-format #. Tag: para msgid "This is a small text file warning you that the contents of the directory are managed by the <command>elilo</command> and that any local changes would be lost at the next time <filename>/usr/sbin/elilo</filename> is run." msgstr "" -#: using-d-i.xml:1957 +#: using-d-i.xml:1984 #, no-c-format #. Tag: filename msgid "vmlinuz" msgstr "" -#: using-d-i.xml:1958 +#: using-d-i.xml:1985 #, no-c-format #. Tag: para msgid "This is the compressed kernel itself. It is a copy of the file referenced in the <filename>/etc/elilo.conf</filename>. In a standard Debian installation it would be the file in <filename>/boot</filename> pointed to by the symbolic link <filename>/vmlinuz</filename>." msgstr "" -#: using-d-i.xml:1978 +#: using-d-i.xml:2005 #, no-c-format #. Tag: title msgid "<command>arcboot</command>-installer" msgstr "" -#: using-d-i.xml:1979 +#: using-d-i.xml:2006 #, no-c-format #. Tag: para msgid "" @@ -1604,61 +1616,61 @@ msgid "" "</screen></informalexample> on the firmware prompt, and then typing <command>boot</command>." msgstr "" -#: using-d-i.xml:1998 +#: using-d-i.xml:2025 #, no-c-format #. Tag: replaceable msgid "scsi" msgstr "" -#: using-d-i.xml:1999 +#: using-d-i.xml:2026 #, no-c-format #. Tag: para msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" -#: using-d-i.xml:2007 +#: using-d-i.xml:2034 #, no-c-format #. Tag: replaceable msgid "disk" msgstr "" -#: using-d-i.xml:2008 +#: using-d-i.xml:2035 #, no-c-format #. Tag: para msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" -#: using-d-i.xml:2016 using-d-i.xml:2085 +#: using-d-i.xml:2043 using-d-i.xml:2112 #, no-c-format #. Tag: replaceable msgid "partnr" msgstr "" -#: using-d-i.xml:2017 +#: using-d-i.xml:2044 #, no-c-format #. Tag: para msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" -#: using-d-i.xml:2025 +#: using-d-i.xml:2052 #, no-c-format #. Tag: replaceable msgid "config" msgstr "" -#: using-d-i.xml:2026 +#: using-d-i.xml:2053 #, no-c-format #. Tag: para msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" -#: using-d-i.xml:2047 +#: using-d-i.xml:2074 #, no-c-format #. Tag: title msgid "<command>delo</command>-installer" msgstr "" -#: using-d-i.xml:2048 +#: using-d-i.xml:2075 #, no-c-format #. Tag: para msgid "" @@ -1667,247 +1679,247 @@ msgid "" "</screen></informalexample> on the firmware prompt." msgstr "" -#: using-d-i.xml:2067 +#: using-d-i.xml:2094 #, no-c-format #. Tag: replaceable msgid "<replaceable>#</replaceable>" msgstr "" -#: using-d-i.xml:2068 +#: using-d-i.xml:2095 #, no-c-format #. Tag: para msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" -#: using-d-i.xml:2076 +#: using-d-i.xml:2103 #, no-c-format #. Tag: replaceable msgid "<replaceable>id</replaceable>" msgstr "" -#: using-d-i.xml:2077 +#: using-d-i.xml:2104 #, no-c-format #. Tag: para msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" -#: using-d-i.xml:2086 +#: using-d-i.xml:2113 #, no-c-format #. Tag: para msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" -#: using-d-i.xml:2094 +#: using-d-i.xml:2121 #, no-c-format #. Tag: replaceable msgid "name" msgstr "" -#: using-d-i.xml:2095 +#: using-d-i.xml:2122 #, no-c-format #. Tag: para msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" -#: using-d-i.xml:2105 +#: using-d-i.xml:2132 #, no-c-format #. Tag: para msgid "In case <filename>/etc/delo.conf</filename> is on the first partition on the disk and the default configuration shall be booted, it is sufficient to use" msgstr "" -#: using-d-i.xml:2111 +#: using-d-i.xml:2138 #, no-c-format #. Tag: screen msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" -#: using-d-i.xml:2121 +#: using-d-i.xml:2148 #, no-c-format #. Tag: title msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" -#: using-d-i.xml:2122 +#: using-d-i.xml:2149 #, no-c-format #. Tag: para msgid "Newer (mid 1998 and on) PowerMacs use <command>yaboot</command> as their boot loader. The installer will set up <command>yaboot</command> automatically, so all you need is a small 820k partition named <quote>bootstrap</quote> with type <emphasis>Apple_Bootstrap</emphasis> created back in the partitioning component. If this step completes successfully then your disk should now be bootable and OpenFirmware will be set to boot &debian;." msgstr "" -#: using-d-i.xml:2140 +#: using-d-i.xml:2167 #, no-c-format #. Tag: title msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" -#: using-d-i.xml:2141 +#: using-d-i.xml:2168 #, no-c-format #. Tag: para msgid "The boot loader for OldWorld Power Macintosh machines is <command>quik</command>. You can also use it on CHRP. The installer will attempt to set up <command>quik</command> automatically. The setup has been known to work on 7200, 7300, and 7600 Powermacs, and on some Power Computing clones." msgstr "" -#: using-d-i.xml:2157 +#: using-d-i.xml:2184 #, no-c-format #. Tag: title msgid "<command>zipl</command>-installer" msgstr "" -#: using-d-i.xml:2158 +#: using-d-i.xml:2185 #, no-c-format #. Tag: para msgid "The boot loader on &arch-title; is <quote>zipl</quote>. <command>ZIPL</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. Please take a look at <quote>LINUX for &arch-title; Device Drivers and Installation Commands</quote> from IBM's developerWorks web site if you want to know more about <command>ZIPL</command>." msgstr "" -#: using-d-i.xml:2175 +#: using-d-i.xml:2202 #, no-c-format #. Tag: title msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" -#: using-d-i.xml:2177 +#: using-d-i.xml:2204 #, no-c-format #. Tag: para msgid "The standard &architecture; boot loader is called <quote>silo</quote>. It is documented in <filename>/usr/share/doc/silo/</filename>. <command>SILO</command> is similar in configuration and usage to <command>LILO</command>, with a few exceptions. First of all, <command>SILO</command> allows you to boot any kernel image on your drive, even if it is not listed in <filename>/etc/silo.conf</filename>. This is because <command>SILO</command> can actually read Linux partitions. Also, <filename>/etc/silo.conf</filename> is read at boot time, so there is no need to rerun <command>silo</command> after installing a new kernel like you would with <command>LILO</command>. <command>SILO</command> can also read UFS partitions, which means it can boot SunOS/Solaris partitions as well. This is useful if you want to install GNU/Linux alongside an existing SunOS/Solaris install." msgstr "" -#: using-d-i.xml:2202 +#: using-d-i.xml:2229 #, no-c-format #. Tag: title msgid "Continue Without Boot Loader" msgstr "" -#: using-d-i.xml:2204 +#: using-d-i.xml:2231 #, no-c-format #. Tag: para msgid "This option can be used to complete the installation even when no boot loader is to be installed, either because the arch/subarch doesn't provide one, or because none is desired (e.g. you will use existing boot loader). <phrase arch=\"m68k\">This option is especially useful for Macintosh, Atari, and Amiga systems, where the original operating system must be maintained on the box and used to boot GNU/Linux.</phrase>" msgstr "" -#: using-d-i.xml:2213 +#: using-d-i.xml:2240 #, no-c-format #. Tag: para msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in <filename>/target/boot</filename>. You should also check that directory for the presence of an <firstterm>initrd</firstterm>; if one is present, you will probably have to instruct your bootloader to use it. Other information you will need are the disk and partition you selected for your <filename>/</filename> filesystem and, if you chose to install <filename>/boot</filename> on a separate partition, also your <filename>/boot</filename> filesystem." msgstr "" -#: using-d-i.xml:2230 +#: using-d-i.xml:2257 #, no-c-format #. Tag: title msgid "Finishing the Installation" msgstr "" -#: using-d-i.xml:2231 +#: using-d-i.xml:2258 #, no-c-format #. Tag: para msgid "These are the last bits to do before rebooting to your new system. It mostly consists of tidying up after the &d-i;." msgstr "" -#: using-d-i.xml:2243 +#: using-d-i.xml:2270 #, no-c-format #. Tag: title msgid "Finish the Installation and Reboot" msgstr "" -#: using-d-i.xml:2245 +#: using-d-i.xml:2272 #, no-c-format #. Tag: para msgid "This is the last step in the initial Debian installation process. You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. The installer will do any last minute tasks, and then reboot into your new Debian system." msgstr "" -#: using-d-i.xml:2252 +#: using-d-i.xml:2279 #, no-c-format #. Tag: para msgid "Select the <guimenuitem>Finish the installation</guimenuitem> menu item which will halt the system because rebooting is not supported on &arch-title; in this case. You then need to IPL GNU/Linux from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" -#: using-d-i.xml:2266 +#: using-d-i.xml:2293 #, no-c-format #. Tag: title msgid "Miscellaneous" msgstr "" -#: using-d-i.xml:2267 +#: using-d-i.xml:2294 #, no-c-format #. Tag: para msgid "The components listed in this section are usually not involved in the installation process, but are waiting in the background to help the user in case something goes wrong." msgstr "" -#: using-d-i.xml:2280 +#: using-d-i.xml:2307 #, no-c-format #. Tag: title msgid "Saving the installation logs" msgstr "" -#: using-d-i.xml:2282 +#: using-d-i.xml:2309 #, no-c-format #. Tag: para msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to <filename>/var/log/installer/</filename> on your new Debian system." msgstr "" -#: using-d-i.xml:2289 +#: using-d-i.xml:2316 #, no-c-format #. Tag: para msgid "Choosing <guimenuitem>Save debug logs</guimenuitem> from the main menu allows you to save the log files to a floppy disk, network, hard disk, or other media. This can be useful if you encounter fatal problems during the installation and wish to study the logs on another system or attach them to an installation report." msgstr "" -#: using-d-i.xml:2309 +#: using-d-i.xml:2336 #, no-c-format #. Tag: title msgid "Using the Shell and Viewing the Logs" msgstr "" -#: using-d-i.xml:2312 +#: using-d-i.xml:2339 #, no-c-format #. Tag: para msgid "There is an <guimenuitem>Execute a Shell</guimenuitem> item on the menu. If the menu is not available when you need to use the shell, press <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap> </keycombo>) to switch to the second <emphasis>virtual console</emphasis>. That's the <keycap>Alt</keycap> key on the left-hand side of the <keycap>space bar</keycap>, and the <keycap>F2</keycap> function key, at the same time. This is a separate window running a Bourne shell clone called <command>ash</command>." msgstr "" -#: using-d-i.xml:2324 +#: using-d-i.xml:2351 #, no-c-format #. Tag: para msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command <command>ls /bin /sbin /usr/bin /usr/sbin</command> and by typing <command>help</command>. The text editor is <command>nano</command>. The shell has some nice features like autocompletion and history." msgstr "" -#: using-d-i.xml:2333 +#: using-d-i.xml:2360 #, no-c-format #. Tag: para msgid "Use the menus to perform any task that they are able to do — the shell and commands are only there in case something goes wrong. In particular, you should always use the menus, not the shell, to activate your swap partition, because the menu software can't detect that you've done this from the shell. Press <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to get back to menus, or type <command>exit</command> if you used a menu item to open the shell." msgstr "" -#: using-d-i.xml:2352 +#: using-d-i.xml:2379 #, no-c-format #. Tag: title msgid "Installation Over the Network" msgstr "" -#: using-d-i.xml:2354 +#: using-d-i.xml:2381 #, no-c-format #. Tag: para msgid "One of the more interesting components is <firstterm>network-console</firstterm>. It allows you to do a large part of the installation over the network via SSH. The use of the network implies you will have to perform the first steps of the installation from the console, at least to the point of setting up the networking. (Although you can automate that part with <xref linkend=\"automatic-install\"/>.)" msgstr "" -#: using-d-i.xml:2364 +#: using-d-i.xml:2391 #, no-c-format #. Tag: para msgid "This component is not loaded into the main installation menu by default, so you have to explicitly ask for it. If you are installing from CD, you need to boot with medium priority or otherwise invoke the main installation menu and choose <guimenuitem>Load installer components from CD</guimenuitem> and from the list of additional components select <guimenuitem>network-console: Continue installation remotely using SSH</guimenuitem>. Successful load is indicated by a new menu entry called <guimenuitem>Continue installation remotely using SSH</guimenuitem>." msgstr "" -#: using-d-i.xml:2377 +#: using-d-i.xml:2404 #, no-c-format #. Tag: para msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" -#: using-d-i.xml:2382 +#: using-d-i.xml:2409 #, no-c-format #. Tag: para msgid "<phrase arch=\"not-s390\">After selecting this new entry, you</phrase> <phrase arch=\"s390\">You</phrase> will be asked for a new password to be used for connecting to the installation system and for its confirmation. That's all. Now you should see a screen which instructs you to login remotely as the user <emphasis>installer</emphasis> with the password you just provided. Another important detail to notice on this screen is the fingerprint of this system. You need to transfer the fingerprint securely to the <quote>person who will continue the installation remotely</quote>." msgstr "" -#: using-d-i.xml:2394 +#: using-d-i.xml:2421 #, no-c-format #. Tag: para msgid "Should you decide to continue with the installation locally, you can always press &enterkey;, which will bring you back to the main menu, where you can select another component." msgstr "" -#: using-d-i.xml:2400 +#: using-d-i.xml:2427 #, no-c-format #. Tag: para msgid "" @@ -1916,25 +1928,25 @@ msgid "" "</screen></informalexample> Where <replaceable>install_host</replaceable> is either the name or IP address of the computer being installed. Before the actual login the fingerprint of the remote system will be displayed and you will have to confirm that it is correct." msgstr "" -#: using-d-i.xml:2417 +#: using-d-i.xml:2444 #, no-c-format #. Tag: para msgid "If you install several computers in turn and they happen to have the same IP address or hostname, <command>ssh</command> will refuse to connect to such host. The reason is that it will have different fingerprint, which is usually a sign of a spoofing attack. If you are sure this is not the case, you will need to delete the relevant line from <filename>~/.ssh/known_hosts</filename> and try again." msgstr "" -#: using-d-i.xml:2426 +#: using-d-i.xml:2453 #, no-c-format #. Tag: para msgid "After the login you will be presented with an initial screen where you have two possibilities called <guimenuitem>Start menu</guimenuitem> and <guimenuitem>Start shell</guimenuitem>. The former brings you to the main installer menu, where you can continue with the installation as usual. The latter starts a shell from which you can examine and possibly fix the remote system. You should only start one SSH session for the installation menu, but may start multiple sessions for shells." msgstr "" -#: using-d-i.xml:2436 +#: using-d-i.xml:2463 #, no-c-format #. Tag: para msgid "After you have started the installation remotely over SSH, you should not go back to the installation session running on the local console. Doing so may corrupt the database that holds the configuration of the new system. This in turn may result in a failed installation or problems with the installed system." msgstr "" -#: using-d-i.xml:2444 +#: using-d-i.xml:2471 #, no-c-format #. Tag: para msgid "Also, if you are running the SSH session from an X terminal, you should not resize the window as that will result in the connection being terminated." |