diff options
Diffstat (limited to 'po/pot')
| -rw-r--r-- | po/pot/install-methods.pot | 142 | ||||
| -rw-r--r-- | po/pot/post-install.pot | 4 | ||||
| -rw-r--r-- | po/pot/preparing.pot | 16 | ||||
| -rw-r--r-- | po/pot/preseed.pot | 12 | ||||
| -rw-r--r-- | po/pot/random-bits.pot | 277 | ||||
| -rw-r--r-- | po/pot/using-d-i.pot | 664 |
6 files changed, 608 insertions, 507 deletions
diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 4bd915dbd..558c502a4 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-08-18 17:32+0000\n" +"POT-Creation-Date: 2006-12-27 04:04+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" @@ -814,77 +814,77 @@ msgstr "" #. Tag: para #: install-methods.xml:1079 #, no-c-format -msgid "You need to setup a TFTP server, and for many machines, a BOOTP server <phrase condition=\"supports-rarp\">, or RARP server</phrase> <phrase condition=\"supports-dhcp\">, or DHCP server</phrase>." +msgid "You need to setup a TFTP server, and for many machines a DHCP server<phrase condition=\"supports-rarp\">, or RARP server</phrase><phrase condition=\"supports-bootp\">, or BOOTP server</phrase>." msgstr "" #. Tag: para -#: install-methods.xml:1085 +#: install-methods.xml:1086 #, no-c-format -msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol. </phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image. </phrase> <phrase arch=\"m68k\"> Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM. </phrase> <phrase condition=\"supports-dhcp\">The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP. </phrase>" +msgid "<phrase condition=\"supports-rarp\">The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol.</phrase> <phrase condition=\"supports-bootp\">BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image.</phrase> <phrase arch=\"m68k\">Yet another alternative exists on VMEbus systems: the IP address can be manually configured in boot ROM.</phrase> The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1102 +#: install-methods.xml:1103 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1108 +#: install-methods.xml:1109 #, no-c-format msgid "Unlike the Open Firmware found on Sparc and PowerPC machines, the SRM console will <emphasis>not</emphasis> use RARP to obtain its IP address, and therefore you must use BOOTP for net booting your Alpha<footnote> <para> Alpha systems can also be net-booted using the DECNet MOP (Maintenance Operations Protocol), but this is not covered here. Presumably, your local OpenVMS operator will be happy to assist you should you have some burning need to use MOP to boot Linux on your Alpha. </para> </footnote>. You can also enter the IP configuration for network interfaces directly in the SRM console." msgstr "" #. Tag: para -#: install-methods.xml:1125 +#: install-methods.xml:1126 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an <classname>rbootd</classname> package available in Debian." msgstr "" #. Tag: para -#: install-methods.xml:1130 +#: install-methods.xml:1131 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1138 +#: install-methods.xml:1139 #, no-c-format msgid "To use the Pre-boot Execution Environment (PXE) method of TFTP booting, you will need a TFTP server with <userinput>tsize</userinput> support. On a &debian; server, the <classname>atftpd</classname> and <classname>tftpd-hpa</classname> packages qualify; we recommend <classname>tftpd-hpa</classname>." msgstr "" #. Tag: title -#: install-methods.xml:1156 +#: install-methods.xml:1157 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1157 +#: install-methods.xml:1158 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can <phrase arch=\"sparc\"> pick it off the initial OpenPROM boot messages, use the OpenBoot <userinput>.enet-addr</userinput> command, or </phrase> boot into <quote>Rescue</quote> mode (e.g., from the rescue floppy) and use the command <userinput>/sbin/ifconfig eth0</userinput>." msgstr "" #. Tag: para -#: install-methods.xml:1169 +#: install-methods.xml:1170 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the <command>rarpd</command> program. You need to ensure that the Ethernet hardware address for the client is listed in the <quote>ethers</quote> database (either in the <filename>/etc/ethers</filename> file, or via NIS/NIS+) and in the <quote>hosts</quote> database. Then you need to start the RARP daemon. Issue the command (as root): <userinput>/usr/sbin/rarpd -a</userinput> on most Linux systems and SunOS 5 (Solaris 2), <userinput>/usr/sbin/in.rarpd -a</userinput> on some other Linux systems, or <userinput>/usr/etc/rarpd -a</userinput> in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1191 +#: install-methods.xml:1192 #, no-c-format -msgid "Setting up BOOTP server" +msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1192 +#: install-methods.xml:1193 #, no-c-format -msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp</classname> packages respectively." +msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU <command>bootpd</command>. The other is actually a DHCP server: ISC <command>dhcpd</command>. In &debian; these are contained in the <classname>bootp</classname> and <classname>dhcp3-server</classname> packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1200 +#: install-methods.xml:1201 #, no-c-format msgid "" "To use CMU <command>bootpd</command>, you must first uncomment (or add) the relevant line in <filename>/etc/inetd.conf</filename>. On &debian;, you can run <userinput>update-inetd --enable bootps</userinput>, then <userinput>/etc/init.d/inetd reload</userinput> to do so. Just in case your BOOTP server does not run Debian, the line in question should look like: <informalexample><screen>\n" @@ -901,22 +901,27 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1233 +#: install-methods.xml:1234 #, no-c-format -msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. Otherwise, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd restart</userinput>." +msgid "By contrast, setting up BOOTP with ISC <command>dhcpd</command> is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section <xref linkend=\"dhcpd\"/>. In that case, you will probably be able to get away with simply adding the <userinput>allow bootp</userinput> directive to the configuration block for the subnet containing the client, and restart <command>dhcpd</command> with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1254 +#: install-methods.xml:1255 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1255 +#: install-methods.xml:1256 +#, no-c-format +msgid "One free software DHCP server is ISC <command>dhcpd</command>. For &debian;, the <classname>dhcp3-server</classname> package is recommended. Here is a sample configuration file for it (see <filename>/etc/dhcp3/dhcpd.conf</filename>):" +msgstr "" + +#. Tag: screen +#: install-methods.xml:1263 #, no-c-format msgid "" - "One free software DHCP server is ISC <command>dhcpd</command>. In &debian;, this is available in the <classname>dhcp</classname> package. Here is a sample configuration file for it (usually <filename>/etc/dhcpd.conf</filename>): <informalexample><screen>\n" "option domain-name \"example.com\";\n" "option domain-name-servers ns1.example.com;\n" "option subnet-mask 255.255.255.0;\n" @@ -935,30 +940,29 @@ msgid "" " next-server servername;\n" " hardware ethernet 01:23:45:67:89:AB;\n" " fixed-address 192.168.1.90;\n" - "}\n" - "</screen></informalexample> Note: the new (and preferred) <classname>dhcp3</classname> package uses <filename>/etc/dhcp3/dhcpd.conf</filename>." + "}" msgstr "" #. Tag: para -#: install-methods.xml:1267 +#: install-methods.xml:1265 #, no-c-format msgid "In this example, there is one server <replaceable>servername</replaceable> which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The <replaceable>filename</replaceable> option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1277 +#: install-methods.xml:1275 #, no-c-format -msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd restart</userinput>." +msgid "After you have edited the <command>dhcpd</command> configuration file, restart it with <userinput>/etc/init.d/dhcpd3-server restart</userinput>." msgstr "" #. Tag: title -#: install-methods.xml:1285 +#: install-methods.xml:1283 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1286 +#: install-methods.xml:1284 #, no-c-format msgid "" "Here is another example for a <filename>dhcp.conf</filename> using the Pre-boot Execution Environment (PXE) method of TFTP. <informalexample><screen>\n" @@ -982,24 +986,24 @@ msgid "" "}\n" "\n" "group {\n" - " next-server 192.168.1.3;\n" - " host tftpclient {\n" + " next-server 192.168.1.3;\n" + " host tftpclient {\n" "# tftp client hardware address\n" " hardware ethernet 00:10:DC:27:6C:15;\n" - " filename \"/tftpboot/pxelinux.0\";\n" + " filename \"pxelinux.0\";\n" " }\n" "}\n" "</screen></informalexample> Note that for PXE booting, the client filename <filename>pxelinux.0</filename> is a boot loader, not a kernel image (see <xref linkend=\"tftp-images\"/> below)." msgstr "" #. Tag: title -#: install-methods.xml:1302 +#: install-methods.xml:1300 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1303 +#: install-methods.xml:1301 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that <command>tftpd</command> is enabled. This is usually enabled by having something like the following line in <filename>/etc/inetd.conf</filename>: <informalexample><screen>\n" @@ -1008,13 +1012,19 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1314 +#: install-methods.xml:1313 #, no-c-format -msgid "Look in that file and remember the directory which is used as the argument of <command>in.tftpd</command>; you'll need that below. The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." +msgid "Historically TFTP servers used <filename>/tftpboot</filename> as directory to serve images from. However, &debian; packages may use other directories to comply with the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink>. For example, <classname>tftpd-hpa</classname> by default uses <filename>/var/lib/tftpboot</filename>. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1328 +#: install-methods.xml:1323 +#, no-c-format +msgid "Look in <filename>/etc/inetd.conf</filename> and remember the directory which is used as the argument of <command>in.tftpd</command><footnote> <para> The <userinput>-l</userinput> argument enables some versions of <command>in.tftpd</command> to log all requests to the system logs; this is useful for diagnosing boot errors. </para> </footnote>; you'll need that below. If you've had to change <filename>/etc/inetd.conf</filename>, you'll have to notify the running <command>inetd</command> process that the file has changed. On a Debian machine, run <userinput>/etc/init.d/inetd reload</userinput>; on other machines, find out the process ID for <command>inetd</command>, and run <userinput>kill -HUP <replaceable>inetd-pid</replaceable></userinput>." +msgstr "" + +#. Tag: para +#: install-methods.xml:1341 #, no-c-format msgid "" "If you intend to install Debian on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: <informalexample><screen>\n" @@ -1025,85 +1035,85 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1350 +#: install-methods.xml:1363 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1351 +#: install-methods.xml:1364 #, no-c-format -msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. Generally, this directory will be <filename>/tftpboot</filename>. You'll have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." +msgid "Next, place the TFTP boot image you need, as found in <xref linkend=\"where-files\"/>, in the <command>tftpd</command> boot image directory. You may have to make a link from that file to the file which <command>tftpd</command> will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1361 +#: install-methods.xml:1373 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the <command>yaboot</command> boot loader as the TFTP boot image. <command>Yaboot</command> will then retrieve the kernel and RAMdisk images via TFTP itself. For net booting, use the <filename>yaboot-netboot.conf</filename>. Just rename this to <filename>yaboot.conf</filename> in the TFTP directory." msgstr "" #. Tag: para -#: install-methods.xml:1370 +#: install-methods.xml:1382 #, no-c-format -msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." +msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>pxelinux.0</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1378 +#: install-methods.xml:1390 #, no-c-format msgid "For PXE booting, everything you should need is set up in the <filename>netboot/netboot.tar.gz</filename> tarball. Simply extract this tarball into the <command>tftpd</command> boot image directory. Make sure your dhcp server is configured to pass <filename>/debian-installer/ia64/elilo.efi</filename> to <command>tftpd</command> as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1390 +#: install-methods.xml:1402 #, no-c-format msgid "DECstation TFTP Images" msgstr "" #. Tag: para -#: install-methods.xml:1391 +#: install-methods.xml:1403 #, no-c-format msgid "For DECstations, there are tftpimage files for each subarchitecture, which contain both kernel and installer in one file. The naming convention is <filename><replaceable>subarchitecture</replaceable>/netboot-boot.img</filename>. Copy the tftpimage file you would like to use to <userinput>/tftpboot/tftpboot.img</userinput> if you work with the example BOOTP/DHCP setups described above." msgstr "" #. Tag: para -#: install-methods.xml:1401 +#: install-methods.xml:1413 #, no-c-format msgid "The DECstation firmware boots by TFTP with the command <userinput>boot <replaceable>#</replaceable>/tftp</userinput>, where <replaceable>#</replaceable> is the number of the TurboChannel device from which to boot. On most DECstations this is <quote>3</quote>. If the BOOTP/DHCP server does not supply the filename or you need to pass additional parameters, they can optionally be appended with the following syntax:" msgstr "" #. Tag: userinput -#: install-methods.xml:1413 +#: install-methods.xml:1425 #, no-c-format msgid "boot #/tftp/filename param1=value1 param2=value2 ..." msgstr "" #. Tag: para -#: install-methods.xml:1415 +#: install-methods.xml:1427 #, no-c-format msgid "Several DECstation firmware revisions show a problem with regard to net booting: the transfer starts, but after some time it stops with an <computeroutput>a.out err</computeroutput>. This can have several reasons: <orderedlist> <listitem><para> The firmware does not respond to ARP requests during a TFTP transfer. This leads to an ARP timeout and the transfer stops. The solution is to add the MAC address of the Ethernet card in the DECstation statically to the ARP table of the TFTP server. This is done by running <userinput>arp -s <replaceable>IP-address</replaceable> <replaceable>MAC-address</replaceable></userinput> as root on the machine acting as TFTP server. The MAC-address of the DECstation can be read out by entering <command>cnfg</command> at the DECstation firmware prompt. </para></listitem> <listitem><para> The firmware has a size limit on the files that can be booted by TFTP. </para></listitem> </orderedlist> There are also firmware revisions that cannot boot via TFTP at all. An overview about the different firmware revisions can be found at the NetBSD web pages: <ulink url=\"http://www.netbsd.org/Ports/pmax/board-list.html#proms\"></ulink>." msgstr "" #. Tag: title -#: install-methods.xml:1453 +#: install-methods.xml:1465 #, no-c-format msgid "Alpha TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1454 +#: install-methods.xml:1466 #, no-c-format msgid "On Alpha, you must specify the filename (as a relative path to the boot image directory) using the <userinput>-file</userinput> argument to the SRM <userinput>boot</userinput> command, or by setting the <userinput>BOOT_FILE</userinput> environment variable. Alternatively, the filename can be given via BOOTP (in ISC <command>dhcpd</command>, use the <userinput>filename</userinput> directive). Unlike Open Firmware, there is <emphasis>no default filename</emphasis> on SRM, so you <emphasis>must</emphasis> specify a filename by either one of these methods." msgstr "" #. Tag: title -#: install-methods.xml:1469 +#: install-methods.xml:1481 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1470 +#: install-methods.xml:1482 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as <quote>SUN4M</quote> or <quote>SUN4C</quote>, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be <filename>C0A80103.SUN4C</filename>. However, there are also subarchitectures where the file the client looks for is just <filename>client-ip-in-hex</filename>. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). <informalexample><screen>\n" @@ -1112,79 +1122,79 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1486 +#: install-methods.xml:1498 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as <userinput>boot net my-sparc.image</userinput>. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1497 +#: install-methods.xml:1509 #, no-c-format msgid "BVM/Motorola TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1498 +#: install-methods.xml:1510 #, no-c-format msgid "For BVM and Motorola VMEbus systems copy the files &bvme6000-tftp-files; to <filename>/tftpboot/</filename>." msgstr "" #. Tag: para -#: install-methods.xml:1503 +#: install-methods.xml:1515 #, no-c-format msgid "Next, configure your boot ROMs or BOOTP server to initially load the <filename>tftplilo.bvme</filename> or <filename>tftplilo.mvme</filename> files from the TFTP server. Refer to the <filename>tftplilo.txt</filename> file for your subarchitecture for additional system-specific configuration information." msgstr "" #. Tag: title -#: install-methods.xml:1515 +#: install-methods.xml:1527 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1516 +#: install-methods.xml:1528 #, no-c-format msgid "On SGI machines you can rely on the <command>bootpd</command> to supply the name of the TFTP file. It is given either as the <userinput>bf=</userinput> in <filename>/etc/bootptab</filename> or as the <userinput>filename=</userinput> option in <filename>/etc/dhcpd.conf</filename>." msgstr "" #. Tag: title -#: install-methods.xml:1528 +#: install-methods.xml:1540 #, no-c-format msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1529 +#: install-methods.xml:1541 #, no-c-format msgid "You don't have to configure DHCP in a special way because you'll pass the full path of the file to be loaded to CFE." msgstr "" #. Tag: title -#: install-methods.xml:1634 +#: install-methods.xml:1646 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1635 +#: install-methods.xml:1647 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. Debian packages intended for this include <classname>fai</classname> (which uses an install server), <classname>replicator</classname>, <classname>systemimager</classname>, <classname>autoinstall</classname>, and the Debian Installer itself." msgstr "" #. Tag: title -#: install-methods.xml:1648 +#: install-methods.xml:1660 #, no-c-format msgid "Automatic Installation Using the Debian Installer" msgstr "" #. Tag: para -#: install-methods.xml:1649 +#: install-methods.xml:1661 #, no-c-format msgid "The Debian Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1656 +#: install-methods.xml:1668 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in <xref linkend=\"appendix-preseed\"/>." msgstr "" diff --git a/po/pot/post-install.pot b/po/pot/post-install.pot index 2a7c98ebc..22576b136 100644 --- a/po/pot/post-install.pot +++ b/po/pot/post-install.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-27 04:04+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" @@ -113,7 +113,7 @@ msgstr "" #. Tag: para #: post-install.xml:162 #, no-c-format -msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user under which the cron job runs." +msgid "On the other hand, if you have a cron job that (a) needs to run as a special user, or (b) needs to run at a special time or frequency, you can use either <filename>/etc/crontab</filename>, or, better yet, <filename>/etc/cron.d/whatever</filename>. These particular files also have an extra field that allows you to stipulate the user account under which the cron job runs." msgstr "" #. Tag: para diff --git a/po/pot/preparing.pot b/po/pot/preparing.pot index 7232e9aa4..9f0b9f47f 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 20:11+0000\n" +"POT-Creation-Date: 2006-12-27 04:04+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" @@ -1067,7 +1067,7 @@ msgstr "" #. Tag: para #: preparing.xml:1037 #, no-c-format -msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer you to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information." +msgid "Windows NT uses the PC-style partition table. If you are manipulating existing FAT or NTFS partitions, it is recommended that you use the native Windows NT tools (or, more conveniently, you can also repartition your disk from the AlphaBIOS setup menu). Otherwise, it is not really necessary to partition from Windows; the Linux partitioning tools will generally do a better job. Note that when you run NT, the Disk Administrator may offer to write a <quote>harmless signature</quote> on non-Windows disks if you have any. <emphasis>Never</emphasis> let it do that, as this signature will destroy the partition information." msgstr "" #. Tag: para @@ -1091,7 +1091,7 @@ msgstr "" #. Tag: para #: preparing.xml:1076 #, no-c-format -msgid "But if you have a large IDE disk, and are using neither LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), nor a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard drive (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition." +msgid "But if you have a large IDE disk, and are not using LBA addressing, overlay drivers (sometimes provided by hard disk manufacturers), or a new (post 1998) BIOS that supports large disk access extensions, then you must locate your Debian boot partition carefully. In this case, you will have to put the boot partition into the first 1024 cylinders of your hard disk (usually around 524 megabytes, without BIOS translation). This may require that you move an existing FAT or NTFS partition." msgstr "" #. Tag: title @@ -1253,7 +1253,7 @@ msgstr "" #. Tag: para #: preparing.xml:1301 #, no-c-format -msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available from the MkLinux FTP server." +msgid "For IDE based Macs, you need to use <command>Apple Drive Setup</command> to create empty space for the Linux partitions, and complete the partitioning under Linux, or use the MacOS version of pdisk available for download from <ulink url=\"http://homepage.mac.com/alk/downloads/pdisk.sit.hqx\">Alsoft</ulink>." msgstr "" #. Tag: title @@ -1265,7 +1265,7 @@ msgstr "" #. Tag: para #: preparing.xml:1319 #, no-c-format -msgid "It's perfectly fine to partition from SunOS; in fact, if you intend to run both SunOS and Debian on the same machine, it is recommended that you partition using SunOS prior to installing Debian. The Linux kernel understands Sun disk labels, so there are no problems there. Just make sure you leave room for the Debian root partition within the first 1GB area of the boot disk. You can also place the kernel image on a UFS partition if that is easier than putting the root partition there. SILO supports booting Linux and SunOS from either EXT2 (Linux), UFS (SunOS), romfs and iso9660 (CDROM) partitions." +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 any of EXT2 (Linux), UFS (SunOS), romfs or iso9660 (CDROM) partitions." msgstr "" #. Tag: title @@ -1739,7 +1739,7 @@ msgstr "" #. Tag: para #: preparing.xml:1965 #, no-c-format -msgid "Before you actually perform an installation, you have to go over some design and preparation steps. IBM has made documentation available about the whole process, e.g. how to prepare an installation medium and how actually boot from that medium. Duplicating that information here is neither possible nor necessary. However, we will describe here which kind of Debian-specific data is needed and where do you find them. Based on both sources of information you have to prepare your machine and the installation medium and to perform a boot from it. When you see the welcome message in your client session join this document again for the Debian-specific installation steps." +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 to 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 to find it. Using both sources of information you have to prepare your machine and the installation medium do you can perform a boot from it. When you see the welcome message in your client session, return to this document to go through the Debian-specific installation steps." msgstr "" #. Tag: title @@ -1901,12 +1901,12 @@ msgstr "" #. Tag: title #: preparing.xml:2163 #, no-c-format -msgid "Display visibility on OldWorld Powermacs" +msgid "Display-visibility on OldWorld Powermacs" msgstr "" #. Tag: para #: preparing.xml:2164 #, no-c-format -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>." +msgid "Some OldWorld Powermacs, most notably those with the <quote>control</quote> display driver, may not reliable produce a colormap 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>." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index e8ddbfe52..bb92af6df 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-26 01:54+0000\n" +"POT-Creation-Date: 2006-12-27 04:04+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" @@ -793,7 +793,7 @@ msgstr "" #. Tag: para #: preseed.xml:726 #, no-c-format -msgid "Depending on the installation method you use, a mirror may be used both to download additional components of the installer, the base system and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." +msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the <filename>/etc/apt/sources.list</filename> for the installed system." msgstr "" #. Tag: para @@ -832,7 +832,7 @@ msgstr "" #. Tag: para #: preseed.xml:756 #, no-c-format -msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to either partition existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding." +msgid "Using preseeding to partition the harddisk is very much limited to what is supported by <classname>partman-auto</classname>. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file. It is currently not possible to partition multiple disks using preseeding." msgstr "" #. Tag: para @@ -1135,8 +1135,8 @@ msgid "" "# if no other operating system is detected on the machine.\n" "d-i grub-installer/only_debian boolean true\n" "\n" - "# This one makes grub-installer install to the MBR if if finds some other OS\n" - "# too, which is less safe as it might not be able to boot that other OS.\n" + "# This one makes grub-installer install to the MBR if it also finds some other\n" + "# OS, which is less safe as it might not be able to boot that other OS.\n" "d-i grub-installer/with_other_os boolean true\n" "\n" "# Alternatively, if you want to install to a location other than the mbr,\n" @@ -1235,7 +1235,7 @@ msgstr "" #. Tag: para #: preseed.xml:943 #, no-c-format -msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be either comma-separated or space-separated, so you can also use it easily on the kernel command line." +msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter <classname>pkgsel/include</classname>. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well." msgstr "" #. Tag: screen diff --git a/po/pot/random-bits.pot b/po/pot/random-bits.pot index dfd41571d..0fc78e716 100644 --- a/po/pot/random-bits.pot +++ b/po/pot/random-bits.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-29 14:49+0000\n" +"POT-Creation-Date: 2006-12-27 04:04+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" @@ -639,57 +639,57 @@ msgstr "" #. Tag: para #: random-bits.xml:332 #, no-c-format -msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need at least 150MB of space available for a console only install, or at least 300MB if you plan to install X." +msgid "With your current *nix partitioning tools, repartition the hard drive as needed, creating at least one filesystem plus swap. You need around 350MB of space available for a console only install, or about 1GB if you plan to install X (more if you intend to install destop environments like GNOME or KDE)." msgstr "" #. Tag: para -#: random-bits.xml:339 +#: random-bits.xml:340 #, no-c-format msgid "" - "Create file systems on your partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n" - "# mke2fs -j /dev/hda6\n" + "Next, create file systems on the partitions. For example, to create an ext3 file system on partition <filename>/dev/hda6</filename> (that's our example root partition): <informalexample><screen>\n" + "# mke2fs -j /dev/<replaceable>hda6</replaceable>\n" "</screen></informalexample> To create an ext2 file system instead, omit <userinput>-j</userinput>." msgstr "" #. Tag: para -#: random-bits.xml:349 +#: random-bits.xml:350 #, no-c-format msgid "" "Initialize and activate swap (substitute the partition number for your intended Debian swap partition): <informalexample><screen>\n" - "# mkswap /dev/hda5\n" + "# mkswap /dev/<replaceable>hda5</replaceable>\n" "# sync; sync; sync\n" - "# swapon /dev/hda5\n" + "# swapon /dev/<replaceable>hda5</replaceable>\n" "</screen></informalexample> Mount one partition as <filename>/mnt/debinst</filename> (the installation point, to be the root (<filename>/</filename>) filesystem on your new system). The mount point name is strictly arbitrary, it is referenced later below." msgstr "" #. Tag: screen -#: random-bits.xml:361 +#: random-bits.xml:362 #, no-c-format msgid "" "# mkdir /mnt/debinst\n" - "# mount /dev/hda6 /mnt/debinst" + "# mount /dev/<replaceable>hda6</replaceable> /mnt/debinst" msgstr "" #. Tag: para -#: random-bits.xml:364 +#: random-bits.xml:365 #, no-c-format msgid "If you want to have parts of the filesystem (e.g. /usr) mounted on separate partitions, you will need to create and mount these directories manually before proceding with the next stage." msgstr "" #. Tag: title -#: random-bits.xml:374 +#: random-bits.xml:375 #, no-c-format msgid "Install <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:375 +#: random-bits.xml:376 #, no-c-format msgid "The utility used by the Debian installer, and recognized as the official way to install a Debian base system, is <command>debootstrap</command>. It uses <command>wget</command> and <command>ar</command>, but otherwise depends only on <classname>/bin/sh</classname> and basic Unix/Linux tools<footnote> <para> These include the GNU core utilities and commands like <command>sed</command>, <command>grep</command>, <command>tar</command> and <command>gzip</command>. </para> </footnote>. Install <command>wget</command> and <command>ar</command> if they aren't already on your current system, then download and install <command>debootstrap</command>." msgstr "" #. Tag: para -#: random-bits.xml:405 +#: random-bits.xml:406 #, no-c-format msgid "" "Or, you can use the following procedure to install it manually. Make a work folder for extracting the .deb into: <informalexample><screen>\n" @@ -699,7 +699,7 @@ msgid "" msgstr "" #. Tag: screen -#: random-bits.xml:420 +#: random-bits.xml:421 #, no-c-format msgid "" "# ar -x debootstrap_0.X.X_all.deb\n" @@ -708,63 +708,66 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:426 +#: random-bits.xml:427 #, no-c-format msgid "Run <command>debootstrap</command>" msgstr "" #. Tag: para -#: random-bits.xml:427 +#: random-bits.xml:428 #, no-c-format msgid "<command>debootstrap</command> can download the needed files directly from the archive when you run it. You can substitute any Debian archive mirror for <userinput>http.us.debian.org/debian</userinput> in the command example below, preferably a mirror close to you network-wise. Mirrors are listed at <ulink url=\"http://www.debian.org/misc/README.mirrors\"></ulink>." msgstr "" #. Tag: para -#: random-bits.xml:436 +#: random-bits.xml:437 #, no-c-format msgid "If you have a &releasename; &debian; CD mounted at <filename>/cdrom</filename>, you could substitute a file URL instead of the http URL: <userinput>file:/cdrom/debian/</userinput>" msgstr "" #. Tag: para -#: random-bits.xml:442 +#: random-bits.xml:443 #, no-c-format -msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>." +msgid "Substitute one of the following for <replaceable>ARCH</replaceable> in the <command>debootstrap</command> command: <userinput>alpha</userinput>, <userinput>amd64</userinput>, <userinput>arm</userinput>, <userinput>hppa</userinput>, <userinput>i386</userinput>, <userinput>ia64</userinput>, <userinput>m68k</userinput>, <userinput>mips</userinput>, <userinput>mipsel</userinput>, <userinput>powerpc</userinput>, <userinput>s390</userinput>, or <userinput>sparc</userinput>." msgstr "" #. Tag: screen -#: random-bits.xml:459 +#: random-bits.xml:461 #, no-c-format msgid "" "# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" - " /mnt/debinst http://http.us.debian.org/debian" + " /mnt/debinst http://ftp.us.debian.org/debian" msgstr "" #. Tag: title -#: random-bits.xml:465 +#: random-bits.xml:467 #, no-c-format msgid "Configure The Base System" msgstr "" #. Tag: para -#: random-bits.xml:466 +#: random-bits.xml:468 #, no-c-format -msgid "Now you've got a real Debian system, though rather lean, on disk. <command>Chroot</command> into it:" +msgid "" + "Now you've got a real Debian system, though rather lean, on disk. <command>chroot</command> into it: <informalexample><screen>\n" + "# LANG=C chroot /mnt/debinst /bin/bash\n" + "</screen></informalexample> After chrooting you may need to set the terminal definition to be compatible with the Debian base system, for example:" msgstr "" #. Tag: screen -#: random-bits.xml:471 +#: random-bits.xml:478 #, no-c-format -msgid "# LANG= chroot /mnt/debinst /bin/bash" +msgid "# export TERM=<replaceable>xterm-color</replaceable>" msgstr "" #. Tag: title -#: random-bits.xml:476 +#: random-bits.xml:483 #, no-c-format msgid "Mount Partitions" msgstr "" #. Tag: para -#: random-bits.xml:477 +#: random-bits.xml:484 #, no-c-format msgid "" "You need to create <filename>/etc/fstab</filename>. <informalexample><screen>\n" @@ -779,68 +782,70 @@ msgid "" "/dev/XXX none swap sw 0 0\n" "proc /proc proc defaults 0 0\n" "\n" - "/dev/fd0 /mnt/floppy auto noauto,rw,sync,user,exec 0 0\n" - "/dev/cdrom /mnt/cdrom iso9660 noauto,ro,user,exec 0 0\n" + "/dev/fd0 /media/floppy auto noauto,rw,sync,user,exec 0 0\n" + "/dev/cdrom /media/cdrom iso9660 noauto,ro,user,exec 0 0\n" "\n" "/dev/XXX /tmp ext3 rw,nosuid,nodev 0 2\n" "/dev/XXX /var ext3 rw,nosuid,nodev 0 2\n" "/dev/XXX /usr ext3 rw,nodev 0 2\n" "/dev/XXX /home ext3 rw,nosuid,nodev 0 2\n" - "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or to mount file systems individually use: <informalexample><screen>\n" + "</screen></informalexample> Use <userinput>mount -a</userinput> to mount all the file systems you have specified in your <filename>/etc/fstab</filename>, or, to mount file systems individually, use: <informalexample><screen>\n" "# mount /path # e.g.: mount /usr\n" + "</screen></informalexample> Current Debian systems have mountpoints for removable media under <filename>/media</filename>, but keep compatibility symlinks in <filename>/</filename>. Create these as as needed, for example: <informalexample><screen>\n" + "# cd /media\n" + "# mkdir cdrom0\n" + "# ln -s cdrom0 cdrom\n" + "# cd /\n" + "# ln -s media/cdrom\n" "</screen></informalexample> You can mount the proc file system multiple times and to arbitrary locations, though <filename>/proc</filename> is customary. If you didn't use <userinput>mount -a</userinput>, be sure to mount proc before continuing:" msgstr "" #. Tag: screen -#: random-bits.xml:497 +#: random-bits.xml:510 #, no-c-format msgid "# mount -t proc proc /proc" msgstr "" #. Tag: para -#: random-bits.xml:499 +#: random-bits.xml:512 #, no-c-format msgid "The command <userinput>ls /proc</userinput> should now show a non-empty directory. Should this fail, you may be able to mount proc from outside the chroot:" msgstr "" #. Tag: screen -#: random-bits.xml:505 +#: random-bits.xml:518 #, no-c-format msgid "# mount -t proc proc /mnt/debinst/proc" msgstr "" #. Tag: title -#: random-bits.xml:511 +#: random-bits.xml:524 #, no-c-format -msgid "Configure Keyboard" +msgid "Setting Timezone" msgstr "" #. Tag: para -#: random-bits.xml:512 +#: random-bits.xml:525 #, no-c-format -msgid "To configure your keyboard:" +msgid "An option in the file <filename>/etc/default/rcS</filename> determines whether the system will interpret the hardware clock as being set to UTC or local time. The following command allow you to set that and choose your timezone." msgstr "" #. Tag: screen -#: random-bits.xml:516 +#: random-bits.xml:532 #, no-c-format -msgid "# dpkg-reconfigure console-data" -msgstr "" - -#. Tag: para -#: random-bits.xml:518 -#, no-c-format -msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot." +msgid "" + "# editor /etc/default/rcS\n" + "# tzconfig" msgstr "" #. Tag: title -#: random-bits.xml:527 +#: random-bits.xml:538 #, no-c-format msgid "Configure Networking" msgstr "" #. Tag: para -#: random-bits.xml:528 +#: random-bits.xml:539 #, no-c-format msgid "" "To configure networking, edit <filename>/etc/network/interfaces</filename>, <filename>/etc/resolv.conf</filename>, <filename>/etc/hostname</filename> and <filename>/etc/hosts</filename>. <informalexample><screen>\n" @@ -879,76 +884,135 @@ msgid "" "nameserver 192.168.9.100\n" "</screen></informalexample> Enter your system's host name (2 to 63 characters): <informalexample><screen>\n" "# echo DebianHostName > /etc/hostname\n" + "</screen></informalexample> And a basic <filename>/etc/hosts</filename> with IPv6 support: <informalexample><screen>\n" + "127.0.0.1 localhost DebianHostName\n" + "\n" + "# The following lines are desirable for IPv6 capable hosts\n" + "::1 ip6-localhost ip6-loopback\n" + "fe00::0 ip6-localnet\n" + "ff00::0 ip6-mcastprefix\n" + "ff02::1 ip6-allnodes\n" + "ff02::2 ip6-allrouters\n" + "ff02::3 ip6-allhosts\n" "</screen></informalexample> If you have multiple network cards, you should arrange the names of driver modules in the <filename>/etc/modules</filename> file into the desired order. Then during boot, each card will be associated with the interface name (eth0, eth1, etc.) that you expect." msgstr "" #. Tag: title -#: random-bits.xml:565 +#: random-bits.xml:580 +#, no-c-format +msgid "Configure Apt" +msgstr "" + +#. Tag: para +#: random-bits.xml:581 +#, no-c-format +msgid "" + "Debootstrap will have created a very basic <filename>/etc/apt/sources.list</filename> that will allow installing additional packages. However, you may want to add some additional sources, for example for source packages and security updates: <informalexample><screen>\n" + "deb-src http://ftp.us.debian.org/debian etch main\n" + "\n" + "deb http://security.debian.org/ etch/updates main\n" + "deb-src http://security.debian.org/ etch/updates main\n" + "</screen></informalexample> Make sure to run <userinput>aptitude update</userinput> after you have made changes to the sources list." +msgstr "" + +#. Tag: title +#: random-bits.xml:597 #, no-c-format -msgid "Configure Locales" +msgid "Configure Locales and Keyboard" msgstr "" #. Tag: para -#: random-bits.xml:566 +#: random-bits.xml:598 #, no-c-format msgid "" - "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it: <informalexample><screen>\n" + "To configure your locale settings to use a language other than English, install the <classname>locales</classname> support package and configure it. Currently the use of UTF-8 locales is recommended. <informalexample><screen>\n" "# aptitude install locales\n" "# dpkg-reconfigure locales\n" - "</screen></informalexample> NOTE: <classname>apt</classname> must be configured beforehand by creating a sources.list and running <command>aptitude update</command>. Before using locales with character sets other than ASCII or latin1, please consult the appropriate localization HOWTO." + "</screen></informalexample> To configure your keyboard (if needed):" +msgstr "" + +#. Tag: screen +#: random-bits.xml:608 +#, no-c-format +msgid "" + "# aptitude install console-data\n" + "# dpkg-reconfigure console-data" +msgstr "" + +#. Tag: para +#: random-bits.xml:610 +#, no-c-format +msgid "Note that the keyboard cannot be set while in the chroot, but will be configured for the next reboot." msgstr "" #. Tag: title -#: random-bits.xml:584 +#: random-bits.xml:620 #, no-c-format msgid "Install a Kernel" msgstr "" #. Tag: para -#: random-bits.xml:585 +#: random-bits.xml:621 #, no-c-format msgid "" - "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with <informalexample><screen>\n" + "If you intend to boot this system, you probably want a Linux kernel and a boot loader. Identify available pre-packaged kernels with: <informalexample><screen>\n" "# apt-cache search linux-image\n" "</screen></informalexample> Then install your choice using its package name." msgstr "" #. Tag: screen -#: random-bits.xml:594 +#: random-bits.xml:630 #, no-c-format msgid "# aptitude install linux-image-<replaceable>&kernelversion;-arch-etc</replaceable>" msgstr "" +#. Tag: para +#: random-bits.xml:633 +#, no-c-format +msgid "The configuration file <filename>/etc/kernel-img.conf</filename> influences the installation and upgrade of pre-packaged Debian kernels. A default file will be created when you first install a Debian kernel image. For additional information about this file, consult its man page which will be available after installing the <classname>kernel-package</classname> package." +msgstr "" + #. Tag: title -#: random-bits.xml:600 +#: random-bits.xml:645 #, no-c-format msgid "Set up the Boot Loader" msgstr "" #. Tag: para -#: random-bits.xml:601 +#: random-bits.xml:646 #, no-c-format msgid "To make your &debian; system bootable, set up your boot loader to load the installed kernel with your new root partition. Note that <command>debootstrap</command> does not install a boot loader, though you can use <command>aptitude</command> inside your Debian chroot to do so." msgstr "" #. Tag: para -#: random-bits.xml:608 +#: random-bits.xml:653 +#, no-c-format +msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call <command>lilo</command> (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)." +msgstr "" + +#. Tag: para +#: random-bits.xml:665 #, no-c-format -msgid "Check <userinput>info grub</userinput> or <userinput>man lilo.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing grub <filename>menu.lst</filename> or <filename>lilo.conf</filename>. For <filename>lilo.conf</filename>, you could also copy it to the new system and edit it there. After you are done editing, call lilo (remember it will use <filename>lilo.conf</filename> relative to the system you call it from)." +msgid "" + "Installing and setting up <classname>grub</classname> is as easy as: <informalexample><screen>\n" + "# aptitude install grub\n" + "# grub-install /dev/<replaceable>hda</replaceable>\n" + "# update-grub\n" + "</screen></informalexample> The second command will install <command>grub</command> (in this case in the MBR of <literal>hda</literal>). The last command will create a sane and working <filename>/boot/grub/menu.lst</filename>." msgstr "" #. Tag: para -#: random-bits.xml:619 +#: random-bits.xml:675 #, no-c-format msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" msgstr "" #. Tag: screen -#: random-bits.xml:623 +#: random-bits.xml:679 #, no-c-format msgid "" - "boot=/dev/hda6\n" - "root=/dev/hda6\n" + "boot=/dev/<replaceable>hda6</replaceable>\n" + "root=/dev/<replaceable>hda6</replaceable>\n" "install=menu\n" "delay=20\n" "lba32\n" @@ -957,13 +1021,13 @@ msgid "" msgstr "" #. Tag: para -#: random-bits.xml:625 +#: random-bits.xml:681 #, no-c-format msgid "Check <userinput>man yaboot.conf</userinput> for instructions on setting up the bootloader. If you are keeping the system you used to install Debian, just add an entry for the Debian install to your existing <filename>yaboot.conf</filename>. You could also copy it to the new system and edit it there. After you are done editing, call ybin (remember it will use <filename>yaboot.conf</filename> relative to the system you call it from)." msgstr "" #. Tag: para -#: random-bits.xml:635 +#: random-bits.xml:691 #, no-c-format msgid "" "Here is a basic <filename>/etc/yaboot.conf</filename> as an example: <informalexample><screen>\n" @@ -979,79 +1043,106 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:653 +#: random-bits.xml:704 +#, no-c-format +msgid "Finishing touches" +msgstr "" + +#. Tag: para +#: random-bits.xml:705 +#, no-c-format +msgid "" + "As mentioned earlier, the installed system will be very basic. If you would like to make the system a bit more mature, there is an easy method to packages of <quote>standard</quote> priority: <informalexample><screen>\n" + "# tasksel install standard\n" + "</screen></informalexample> Of course, you can also just use <command>aptitude</command> to install packages individually." +msgstr "" + +#. Tag: para +#: random-bits.xml:716 +#, no-c-format +msgid "After the installation there will be a lot of downloaded packages in <filename>/var/cache/apt/archives/</filename>. You can free up some diskspace by running:" +msgstr "" + +#. Tag: screen +#: random-bits.xml:722 +#, no-c-format +msgid "# aptitude clean" +msgstr "" + +#. Tag: title +#: random-bits.xml:733 #, no-c-format msgid "Installing &debian; over Parallel Line IP (PLIP)" msgstr "" #. Tag: para -#: random-bits.xml:655 +#: random-bits.xml:735 #, no-c-format msgid "This section explains how to install &debian; on a computer without an Ethernet card, but with just a remote gateway computer attached via a Null-Modem cable (also called Null-Printer cable). The gateway computer should be connected to a network that has a Debian mirror on it (e.g. to the Internet)." msgstr "" #. Tag: para -#: random-bits.xml:663 +#: random-bits.xml:743 #, no-c-format msgid "In the example in this appendix we will set up a PLIP connection using a gateway connected to the Internet over a dial-up connection (ppp0). We will use IP addresses 192.168.0.1 and 192.168.0.2 for the PLIP interfaces on the target system and the source system respectively (these addresses should be unused within your network address space)." msgstr "" #. Tag: para -#: random-bits.xml:671 +#: random-bits.xml:751 #, no-c-format msgid "The PLIP connection set up during the installation will also be available after the reboot into the installed system (see <xref linkend=\"boot-new\"/>)." msgstr "" #. Tag: para -#: random-bits.xml:676 +#: random-bits.xml:756 #, no-c-format msgid "Before you start, you will need to check the BIOS configuration (IO base address and IRQ) for the parallel ports of both the source and target systems. The most common values are <literal>io=0x378</literal>, <literal>irq=7</literal>." msgstr "" #. Tag: title -#: random-bits.xml:686 +#: random-bits.xml:766 #, no-c-format msgid "Requirements" msgstr "" #. Tag: para -#: random-bits.xml:689 +#: random-bits.xml:769 #, no-c-format msgid "A target computer, called <emphasis>target</emphasis>, where Debian will be installed." msgstr "" #. Tag: para -#: random-bits.xml:695 +#: random-bits.xml:775 #, no-c-format msgid "System installation media; see <xref linkend=\"installation-media\"/>." msgstr "" #. Tag: para -#: random-bits.xml:700 +#: random-bits.xml:780 #, no-c-format msgid "Another computer connected to the Internet, called <emphasis>source</emphasis>, that will function as the gateway." msgstr "" #. Tag: para -#: random-bits.xml:706 +#: random-bits.xml:786 #, no-c-format msgid "A DB-25 Null-Modem cable. See the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-HOWTO</ulink> for more information on this cable and instructions how to make your own." msgstr "" #. Tag: title -#: random-bits.xml:718 +#: random-bits.xml:798 #, no-c-format msgid "Setting up source" msgstr "" #. Tag: para -#: random-bits.xml:719 +#: random-bits.xml:799 #, no-c-format msgid "The following shell script is a simple example of how to configure the source computer as a gateway to the Internet using ppp0." msgstr "" #. Tag: screen -#: random-bits.xml:724 +#: random-bits.xml:804 #, no-c-format msgid "" "#!/bin/sh\n" @@ -1072,13 +1163,13 @@ msgid "" msgstr "" #. Tag: title -#: random-bits.xml:730 +#: random-bits.xml:810 #, no-c-format msgid "Installing target" msgstr "" #. Tag: para -#: random-bits.xml:731 +#: random-bits.xml:811 #, no-c-format msgid "" "Boot the installation media. The installation needs to be run in expert mode; enter <userinput>expert</userinput> at the boot prompt. If you need to set parameters for kernel modules, you also need to do this at the boot prompt. For example, to boot the installer and set values for the <quote>io</quote> and <quote>irq</quote> options for the parport_pc module, enter the following at the boot prompt: <informalexample><screen>\n" @@ -1087,61 +1178,61 @@ msgid "" msgstr "" #. Tag: guimenuitem -#: random-bits.xml:750 +#: random-bits.xml:830 #, no-c-format msgid "Load installer components from CD" msgstr "" #. Tag: para -#: random-bits.xml:752 +#: random-bits.xml:832 #, no-c-format msgid "Select the <userinput>plip-modules</userinput> option from the list; this will make the PLIP drivers available to the installation system." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:760 +#: random-bits.xml:840 #, no-c-format msgid "Detect network hardware" msgstr "" #. Tag: para -#: random-bits.xml:765 +#: random-bits.xml:845 #, no-c-format msgid "If target <emphasis>does</emphasis> have a network card, a list of driver modules for detected cards will be shown. If you want to force &d-i; to use plip instead, you have to deselect all listed driver modules. Obviously, if target doesn't have a network card, the installer will not show this list." msgstr "" #. Tag: para -#: random-bits.xml:774 +#: random-bits.xml:854 #, no-c-format msgid "Because no network card was detected/selected earlier, the installer will ask you to select a network driver module from a list. Select the <userinput>plip</userinput> module." msgstr "" #. Tag: guimenuitem -#: random-bits.xml:786 +#: random-bits.xml:866 #, no-c-format msgid "Configure the network" msgstr "" #. Tag: para -#: random-bits.xml:789 +#: random-bits.xml:869 #, no-c-format msgid "Auto-configure network with DHCP: No" msgstr "" #. Tag: para -#: random-bits.xml:794 +#: random-bits.xml:874 #, no-c-format msgid "IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:799 +#: random-bits.xml:879 #, no-c-format msgid "Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></userinput>" msgstr "" #. Tag: para -#: random-bits.xml:805 +#: random-bits.xml:885 #, no-c-format msgid "Name server addresses: you can enter the same addresses used on source (see <filename>/etc/resolv.conf</filename>)" msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index af8eca9b4..c28c064c1 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" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 20:11+0000\n" +"POT-Creation-Date: 2006-12-27 04:04+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" @@ -473,317 +473,317 @@ msgstr "" #. Tag: para #: using-d-i.xml:441 #, no-c-format -msgid "During a low memory install, not all components will be available. One of the limitations is that you won't be able to choose a language for the installation." +msgid "The first measure taken to reduce memory consumption by the installer is to disable translations. If that is not sufficient, the installer will only load components essential to complete a basic installation by default. This reduces the functionality of the installation system. You will be given the opportunity to load additional components manually, but you should be aware that each component you select will use additional memory and thus may cause the installation to fail." msgstr "" #. Tag: title -#: using-d-i.xml:456 +#: using-d-i.xml:460 #, no-c-format msgid "Selecting Localization Options" msgstr "" #. Tag: para -#: using-d-i.xml:458 +#: using-d-i.xml:462 #, no-c-format msgid "In most cases the first questions you will be asked concern the selection of localization options to be used both for the installation and for the installed system. The localization options consist of language, country and locales." msgstr "" #. Tag: para -#: using-d-i.xml:465 +#: using-d-i.xml:469 #, no-c-format msgid "The language you choose will be used for the rest of the installation process, provided a translation of the different dialogs is available. If no valid translation is available for the selected language, the installer will default to English." msgstr "" #. Tag: para -#: using-d-i.xml:472 +#: using-d-i.xml:476 #, no-c-format msgid "The selected country will be used later in the installation process to pick the default timezone and a Debian mirror appropriate for your geographic location. Language and country together will be used to set the default locale for your system and to help select your keyboard." msgstr "" #. Tag: para -#: using-d-i.xml:479 +#: using-d-i.xml:483 #, no-c-format msgid "You will first be asked to select your preferred language. The language names are listed in both English (left side) and in the language itself (right side); the names on the right side are also shown in the proper script for the language. The list is sorted on the English names. At the top of the list is an extra option that allows you to select the <quote>C</quote> locale instead of a language. Choosing the <quote>C</quote> locale will result in the installation proceding in English; the installed system will have no localization support as the <classname>locales</classname> package will not be installed." msgstr "" #. Tag: para -#: using-d-i.xml:491 +#: using-d-i.xml:495 #, no-c-format msgid "If you selected a language that is recognized as an official language for more than one country<footnote> <para> In technical terms: where multiple locales exist for that language with differing country codes. </para> </footnote>, you will next be asked to select a country. If you choose <guimenuitem>Other</guimenuitem> at the bottom of the list, you will be presented with a list of all countries, grouped by continent. If the language has only one country associated with it, that country will be selected automatically." msgstr "" #. Tag: para -#: using-d-i.xml:509 +#: using-d-i.xml:513 #, no-c-format msgid "A default locale will be selected based on the selected language and country. If you are installing at medium or low priority, you will have the option of selecting a different default locale and of selecting additional locales to be generated for the installed system." msgstr "" #. Tag: title -#: using-d-i.xml:524 +#: using-d-i.xml:528 #, no-c-format msgid "Choosing a Keyboard" msgstr "" #. Tag: para -#: using-d-i.xml:526 +#: using-d-i.xml:530 #, no-c-format msgid "Keyboards are often tailored to the characters used in a language. Select a layout that conforms to the keyboard you are using, or select something close if the keyboard layout you want isn't represented. Once the system installation is complete, you'll be able to select a keyboard layout from a wider range of choices (run <command>kbdconfig</command> as root after you have completed the installation)." msgstr "" #. Tag: para -#: using-d-i.xml:536 +#: using-d-i.xml:540 #, no-c-format msgid "Move the highlight to the keyboard selection you desire and press &enterkey;. Use the arrow keys to move the highlight — they are in the same place in all national language keyboard layouts, so they are independent of the keyboard configuration. An 'extended' keyboard is one with <keycap>F1</keycap> through <keycap>F10</keycap> keys along the top row." msgstr "" #. Tag: para -#: using-d-i.xml:545 +#: using-d-i.xml:549 #, no-c-format msgid "On DECstations there is currently no loadable keymap available, so you have to skip the keyboard selection and keep the default kernel keymap (LK201 US). This may change in the future as it depends on further Linux/MIPS kernel development." msgstr "" #. Tag: para -#: using-d-i.xml:552 +#: using-d-i.xml:556 #, no-c-format msgid "There are two keyboard layouts for US keyboards; the qwerty/mac-usb-us (Apple USB) layout will place the Alt function on the <keycap>Command/Apple</keycap> key (in the keyboard position next to the <keycap>space</keycap> key similar to <keycap>Alt</keycap> on PC keyboards), while the qwerty/us (Standard) layout will place the Alt function on the <keycap>Option</keycap> key (engraved with 'alt' on most Mac keyboards). In other respects the two layouts are similar." msgstr "" #. Tag: title -#: using-d-i.xml:582 +#: using-d-i.xml:586 #, no-c-format msgid "Looking for the Debian Installer ISO Image" msgstr "" #. Tag: para -#: using-d-i.xml:583 +#: using-d-i.xml:587 #, no-c-format msgid "When installing via the <emphasis>hd-media</emphasis> method, there will be a moment where you need to find and mount the Debian Installer iso image in order to get the rest of the installation files. The component <command>iso-scan</command> does exactly this." msgstr "" #. Tag: para -#: using-d-i.xml:590 +#: using-d-i.xml:594 #, no-c-format msgid "At first, <command>iso-scan</command> automatically mounts all block devices (e.g. partitions) which have some known filesystem on them and sequentially searches for filenames ending with <filename>.iso</filename> (or <filename>.ISO</filename> for that matter). Beware that the first attempt scans only files in the root directory and in the first level of subdirectories (i.e. it finds <filename>/<replaceable>whatever</replaceable>.iso</filename>, <filename>/data/<replaceable>whatever</replaceable>.iso</filename>, but not <filename>/data/tmp/<replaceable>whatever</replaceable>.iso</filename>). After an iso image has been found, <command>iso-scan</command> checks its content to determine if the image is a valid Debian iso image or not. In the former case we are done, in the latter <command>iso-scan</command> seeks for another image." msgstr "" #. Tag: para -#: using-d-i.xml:607 +#: using-d-i.xml:611 #, no-c-format msgid "In case the previous attempt to find an installer iso image fails, <command>iso-scan</command> will ask you whether you would like to perform a more thorough search. This pass doesn't just look into the topmost directories, but really traverses whole filesystem." msgstr "" #. Tag: para -#: using-d-i.xml:614 +#: using-d-i.xml:618 #, no-c-format msgid "If <command>iso-scan</command> does not discover your installer iso image, reboot back to your original operating system and check if the image is named correctly (ending in <filename>.iso</filename>), if it is placed on a filesystem recognizable by &d-i;, and if it is not corrupted (verify the checksum). Experienced Unix users could do this without rebooting on the second console." msgstr "" #. Tag: title -#: using-d-i.xml:635 +#: using-d-i.xml:639 #, no-c-format msgid "Configuring Network" msgstr "" #. Tag: para -#: using-d-i.xml:637 +#: using-d-i.xml:641 #, no-c-format msgid "As you enter this step, if the system detects that you have more than one network device, you'll be asked to choose which device will be your <emphasis>primary</emphasis> network interface, i.e. the one which you want to use for installation. The other interfaces won't be configured at this time. You may configure additional interfaces after installation is complete; see the <citerefentry> <refentrytitle>interfaces</refentrytitle> <manvolnum>5</manvolnum> </citerefentry> man page." msgstr "" #. Tag: para -#: using-d-i.xml:648 +#: using-d-i.xml:652 #, no-c-format msgid "By default, &d-i; tries to configure your computer's network automatically via DHCP. If the DHCP probe succeeds, you are done. If the probe fails, it may be caused by many factors ranging from unplugged network cable, to a misconfigured DHCP setup. Or maybe you don't have a DHCP server in your local network at all. For further explanation check the error messages on the third console. In any case, you will be asked if you want to retry, or if you want to perform manual setup. DHCP servers are sometimes really slow in their responses, so if you are sure everything is in place, try again." msgstr "" #. Tag: para -#: using-d-i.xml:660 +#: using-d-i.xml:664 #, no-c-format msgid "The manual network setup in turn asks you a number of questions about your network, notably <computeroutput>IP address</computeroutput>, <computeroutput>Netmask</computeroutput>, <computeroutput>Gateway</computeroutput>, <computeroutput>Name server addresses</computeroutput>, and a <computeroutput>Hostname</computeroutput>. Moreover, if you have a wireless network interface, you will be asked to provide your <computeroutput>Wireless ESSID</computeroutput> and a <computeroutput>WEP key</computeroutput>. Fill in the answers from <xref linkend=\"needed-info\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:674 +#: using-d-i.xml:678 #, no-c-format msgid "Some technical details you might, or might not, find handy: the program assumes the network IP address is the bitwise-AND of your system's IP address and your netmask. It will guess the broadcast address is the bitwise OR of your system's IP address with the bitwise negation of the netmask. It will also guess your gateway. If you can't find any of these answers, use the system's guesses — you can change them once the system has been installed, if necessary, by editing <filename>/etc/network/interfaces</filename>." msgstr "" #. Tag: title -#: using-d-i.xml:711 +#: using-d-i.xml:715 #, no-c-format msgid "Partitioning and Mount Point Selection" msgstr "" #. Tag: para -#: using-d-i.xml:712 +#: using-d-i.xml:716 #, no-c-format msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related issues like LVM or RAID devices." msgstr "" #. Tag: title -#: using-d-i.xml:734 +#: using-d-i.xml:738 #, no-c-format msgid "Partitioning Your Disks" msgstr "" #. Tag: para -#: using-d-i.xml:736 +#: using-d-i.xml:740 #, no-c-format msgid "Now it is time to partition your disks. If you are uncomfortable with partitioning, or just want to know more details, see <xref linkend=\"partitioning\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:742 +#: using-d-i.xml:746 #, no-c-format msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called <quote>guided</quote> partitioning. If you do not want to autopartition, choose <guimenuitem>Manual</guimenuitem> from the menu." msgstr "" #. Tag: para -#: using-d-i.xml:749 +#: using-d-i.xml:753 #, no-c-format msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM<footnote> <para> The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's <quote>dm-crypt</quote> support. </para> </footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:764 +#: using-d-i.xml:768 #, no-c-format msgid "The option to use (encrypted) LVM may not be available on all architectures." msgstr "" #. Tag: para -#: using-d-i.xml:769 +#: using-d-i.xml:773 #, no-c-format msgid "When using LVM or encrypted LVM, 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. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data." msgstr "" #. Tag: para -#: using-d-i.xml:778 +#: using-d-i.xml:782 #, no-c-format msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk." msgstr "" #. Tag: para -#: using-d-i.xml:787 +#: using-d-i.xml:791 #, no-c-format msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk." msgstr "" #. Tag: para -#: using-d-i.xml:797 +#: using-d-i.xml:801 #, no-c-format msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them." msgstr "" #. Tag: para -#: using-d-i.xml:806 +#: using-d-i.xml:810 #, no-c-format msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible." msgstr "" #. Tag: para -#: using-d-i.xml:814 +#: using-d-i.xml:818 #, no-c-format msgid "Next, 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 "" #. Tag: entry -#: using-d-i.xml:830 +#: using-d-i.xml:834 #, no-c-format msgid "Partitioning scheme" msgstr "" #. Tag: entry -#: using-d-i.xml:831 +#: using-d-i.xml:835 #, no-c-format msgid "Minimum space" msgstr "" #. Tag: entry -#: using-d-i.xml:832 +#: using-d-i.xml:836 #, no-c-format msgid "Created partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:838 +#: using-d-i.xml:842 #, no-c-format msgid "All files in one partition" msgstr "" #. Tag: entry -#: using-d-i.xml:839 +#: using-d-i.xml:843 #, no-c-format msgid "600MB" msgstr "" #. Tag: entry -#: using-d-i.xml:840 +#: using-d-i.xml:844 #, no-c-format msgid "<filename>/</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:842 +#: using-d-i.xml:846 #, no-c-format msgid "Separate /home partition" msgstr "" #. Tag: entry -#: using-d-i.xml:843 +#: using-d-i.xml:847 #, no-c-format msgid "500MB" msgstr "" #. Tag: entry -#: using-d-i.xml:844 +#: using-d-i.xml:848 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:848 +#: using-d-i.xml:852 #, no-c-format msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:849 +#: using-d-i.xml:853 #, no-c-format msgid "<entry>1GB</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:850 +#: using-d-i.xml:854 #, no-c-format msgid "<filename>/</filename>, <filename>/home</filename>, <filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</filename>, swap" msgstr "" #. Tag: para -#: using-d-i.xml:859 +#: using-d-i.xml:863 #, no-c-format msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate <filename>/boot</filename> partition. The other partitions, except for the swap partition, will be created inside the LVM partition." msgstr "" #. Tag: para -#: using-d-i.xml:865 +#: using-d-i.xml:869 #, no-c-format msgid "If you choose guided partitioning for your IA-64 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 "" #. Tag: para -#: using-d-i.xml:873 +#: using-d-i.xml:877 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:879 +#: using-d-i.xml:883 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:885 +#: using-d-i.xml:889 #, no-c-format msgid "" "The list of partitions might look like this: <informalexample><screen>\n" @@ -806,559 +806,553 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:898 +#: using-d-i.xml:902 #, no-c-format 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> and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" #. Tag: para -#: using-d-i.xml:908 +#: using-d-i.xml:912 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:916 +#: using-d-i.xml:920 #, no-c-format -msgid "If you select a pristine disk which has 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." +msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled <quote>FREE SPACE</quote> should appear in the table under the selected disk." msgstr "" #. Tag: para -#: using-d-i.xml:924 +#: using-d-i.xml:928 #, no-c-format -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." +msgid "If you select some free space, you will have the opportunity to create a 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 a detailed overview of your new partition. The main setting is <guimenuitem>Use as:</guimenuitem>, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. 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 options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select <guimenuitem>Done setting up the partition</guimenuitem> and you will return to <command>partman</command>'s main screen." msgstr "" #. Tag: para -#: using-d-i.xml:942 +#: using-d-i.xml:950 #, no-c-format -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." +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. This is the same screen like when creating a new partition, so you can change the same settings. 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 "" #. Tag: para -#: using-d-i.xml:953 +#: using-d-i.xml:961 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:961 +#: using-d-i.xml:969 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:967 +#: using-d-i.xml:975 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:975 +#: using-d-i.xml:983 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1003 +#: using-d-i.xml:1011 #, no-c-format msgid "Configuring Multidisk Device (Software RAID)" msgstr "" #. Tag: para -#: using-d-i.xml:1004 +#: using-d-i.xml:1012 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1018 +#: using-d-i.xml:1026 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1026 +#: using-d-i.xml:1034 #, no-c-format -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:" +msgid "What benefits this brings depends on the type of 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 lose <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 incoming data into stripes and distributes them equally on all but one disk (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 a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. </para></listitem> </varlistentry> </variablelist> To sum it up:" msgstr "" #. Tag: entry -#: using-d-i.xml:1104 +#: using-d-i.xml:1112 #, no-c-format msgid "Type" msgstr "" #. Tag: entry -#: using-d-i.xml:1105 +#: using-d-i.xml:1113 #, no-c-format msgid "Minimum Devices" msgstr "" #. Tag: entry -#: using-d-i.xml:1106 +#: using-d-i.xml:1114 #, no-c-format msgid "Spare Device" msgstr "" #. Tag: entry -#: using-d-i.xml:1107 +#: using-d-i.xml:1115 #, no-c-format msgid "Survives disk failure?" msgstr "" #. Tag: entry -#: using-d-i.xml:1108 +#: using-d-i.xml:1116 #, no-c-format msgid "Available Space" msgstr "" #. Tag: entry -#: using-d-i.xml:1114 +#: using-d-i.xml:1122 #, no-c-format msgid "RAID0" msgstr "" #. Tag: entry -#: using-d-i.xml:1115 using-d-i.xml:1123 +#: using-d-i.xml:1123 using-d-i.xml:1131 #, no-c-format msgid "<entry>2</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1116 using-d-i.xml:1117 +#: using-d-i.xml:1124 using-d-i.xml:1125 #, no-c-format msgid "<entry>no</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1118 +#: using-d-i.xml:1126 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1122 +#: using-d-i.xml:1130 #, no-c-format msgid "RAID1" msgstr "" #. Tag: entry -#: using-d-i.xml:1124 using-d-i.xml:1132 +#: using-d-i.xml:1132 using-d-i.xml:1140 #, no-c-format msgid "optional" msgstr "" #. Tag: entry -#: using-d-i.xml:1125 using-d-i.xml:1133 +#: using-d-i.xml:1133 using-d-i.xml:1141 #, no-c-format msgid "<entry>yes</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1126 +#: using-d-i.xml:1134 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1130 +#: using-d-i.xml:1138 #, no-c-format msgid "RAID5" msgstr "" #. Tag: entry -#: using-d-i.xml:1131 +#: using-d-i.xml:1139 #, no-c-format msgid "<entry>3</entry>" msgstr "" #. Tag: entry -#: using-d-i.xml:1134 +#: using-d-i.xml:1142 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" #. Tag: para -#: using-d-i.xml:1142 +#: using-d-i.xml:1150 #, no-c-format -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>." +msgid "If you want to know more about Software RAID, have a look at <ulink url=\"&url-software-raid-howto;\">Software RAID HOWTO</ulink>." msgstr "" #. Tag: para -#: using-d-i.xml:1147 +#: using-d-i.xml:1155 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1156 +#: using-d-i.xml:1164 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1165 +#: using-d-i.xml:1173 #, no-c-format msgid "Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> from the main <command>partman</command> menu. (The menu will only appear after you mark at least one partition for use as <guimenuitem>physical volume for RAID</guimenuitem>.) 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 "" #. Tag: para -#: using-d-i.xml:1178 +#: using-d-i.xml:1186 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1185 +#: using-d-i.xml:1193 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1197 +#: using-d-i.xml:1205 #, no-c-format msgid "RAID5 has similar setup procedure as RAID1 with the exception that you need to use at least <emphasis>three</emphasis> active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1205 +#: using-d-i.xml:1213 #, no-c-format 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 disks 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 "" #. Tag: para -#: using-d-i.xml:1214 +#: using-d-i.xml:1222 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1229 +#: using-d-i.xml:1237 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1230 +#: using-d-i.xml:1238 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1238 +#: using-d-i.xml:1246 #, no-c-format 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 disk (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 disks." msgstr "" #. Tag: para -#: using-d-i.xml:1248 +#: using-d-i.xml:1256 #, no-c-format msgid "Now when you realize you need more space for your old 160GB <filename>/home</filename> partition, you can simply add a new 300GB disk 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 "" #. Tag: para -#: using-d-i.xml:1259 +#: using-d-i.xml:1267 #, no-c-format msgid "LVM setup in &d-i; is quite simple and completely supported inside <command>partman</command>. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the <guimenu>Partition settings</guimenu> menu where you should select <menuchoice> <guimenu>Use as:</guimenu> <guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>." msgstr "" #. Tag: para -#: using-d-i.xml:1268 +#: using-d-i.xml:1276 #, no-c-format msgid "When you return to the main <command>partman</command> screen, you will see a new option <guimenuitem>Configure the Logical Volume Manager</guimenuitem>. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" msgstr "" #. Tag: para -#: using-d-i.xml:1279 +#: using-d-i.xml:1287 #, no-c-format msgid "<guimenuitem>Display configuration details</guimenuitem>: shows LVM device structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1284 +#: using-d-i.xml:1292 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1287 +#: using-d-i.xml:1295 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1290 +#: using-d-i.xml:1298 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1293 +#: using-d-i.xml:1301 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1296 +#: using-d-i.xml:1304 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1299 +#: using-d-i.xml:1307 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1301 +#: using-d-i.xml:1309 #, no-c-format msgid "<guimenuitem>Finish</guimenuitem>: return to the main <command>partman</command> screen" msgstr "" #. Tag: para -#: using-d-i.xml:1307 +#: using-d-i.xml:1315 #, no-c-format msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." msgstr "" #. Tag: para -#: using-d-i.xml:1313 -#, no-c-format -msgid "You can also use this menu to delete an existing LVM configuration from your hard disk before choosing <quote>Guided partitioning using LVM</quote>. Guided partitioning using LVM is not possible if there already are volume groups defined, but by removing them you can get a clean start." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1321 +#: using-d-i.xml:1320 #, no-c-format msgid "After you return to the main <command>partman</command> screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." msgstr "" #. Tag: title -#: using-d-i.xml:1335 +#: using-d-i.xml:1334 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1336 +#: using-d-i.xml:1335 #, no-c-format msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the <firstterm>passphrase</firstterm> used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." msgstr "" #. Tag: para -#: using-d-i.xml:1348 +#: using-d-i.xml:1347 #, no-c-format msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example <filename>/var</filename> where database servers, mail servers or print servers store their data, or <filename>/tmp</filename> which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the <filename>/boot</filename> partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." msgstr "" #. Tag: para -#: using-d-i.xml:1363 +#: using-d-i.xml:1362 #, no-c-format msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." msgstr "" #. Tag: para -#: using-d-i.xml:1370 +#: using-d-i.xml:1369 #, no-c-format -msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition setting</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." +msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the <guimenu>Partition settings</guimenu> menu, you need to select <guimenuitem>physical volume for encryption</guimenuitem> at the <menuchoice> <guimenu>Use as:</guimenu> </menuchoice> option. The menu will then change to include several cryptographic options for the partition." msgstr "" #. Tag: para -#: using-d-i.xml:1381 +#: using-d-i.xml:1380 #, no-c-format msgid "&d-i; supports several encryption methods. The default method is <firstterm>dm-crypt</firstterm> (included in newer Linux kernels, able to host LVM physical volumes), the other is <firstterm>loop-AES</firstterm> (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." msgstr "" #. Tag: para -#: using-d-i.xml:1393 +#: using-d-i.xml:1392 #, no-c-format msgid "First, let's have a look at the options available when you select <userinput>Device-mapper (dm-crypt)</userinput> as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." msgstr "" #. Tag: term -#: using-d-i.xml:1403 +#: using-d-i.xml:1402 #, no-c-format msgid "Encryption: <userinput>aes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1405 +#: using-d-i.xml:1404 #, no-c-format msgid "This option lets you select the encryption algorithm (<firstterm>cipher</firstterm>) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: <firstterm>aes</firstterm>, <firstterm>blowfish</firstterm>, <firstterm>serpent</firstterm>, and <firstterm>twofish</firstterm>. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, <emphasis>AES</emphasis> was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." msgstr "" #. Tag: term -#: using-d-i.xml:1423 +#: using-d-i.xml:1422 #, no-c-format msgid "Key size: <userinput>256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1425 +#: using-d-i.xml:1424 #, no-c-format msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term -#: using-d-i.xml:1437 +#: using-d-i.xml:1436 #, no-c-format msgid "IV algorithm: <userinput>cbc-essiv:sha256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1439 +#: using-d-i.xml:1438 #, no-c-format msgid "The <firstterm>Initialization Vector</firstterm> or <firstterm>IV</firstterm> algorithm is used in cryptography to ensure that applying the cipher on the same <firstterm>clear text</firstterm> data with the same key always produces a unique <firstterm>cipher text</firstterm>. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." msgstr "" #. Tag: para -#: using-d-i.xml:1449 +#: using-d-i.xml:1448 #, no-c-format msgid "From the provided alternatives, the default <userinput>cbc-essiv:sha256</userinput> is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." msgstr "" #. Tag: term -#: using-d-i.xml:1461 +#: using-d-i.xml:1460 #, no-c-format msgid "Encryption key: <userinput>Passphrase</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1463 +#: using-d-i.xml:1462 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1469 +#: using-d-i.xml:1468 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1470 +#: using-d-i.xml:1469 #, no-c-format msgid "The encryption key will be computed<footnote> <para> Using a passphrase as the key currently means that the partition will be set up using <ulink url=\"&url-luks;\">LUKS</ulink>. </para></footnote> on the basis of a passphrase which you will be able to enter later in the process." msgstr "" #. Tag: term -#: using-d-i.xml:1485 using-d-i.xml:1578 +#: using-d-i.xml:1484 using-d-i.xml:1577 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:1486 +#: using-d-i.xml:1485 #, no-c-format msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" msgstr "" #. Tag: para -#: using-d-i.xml:1495 +#: using-d-i.xml:1494 #, no-c-format msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will <emphasis>not</emphasis> be able to use the <quote>suspend-to-disk</quote> functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." msgstr "" #. Tag: term -#: using-d-i.xml:1514 using-d-i.xml:1591 +#: using-d-i.xml:1513 using-d-i.xml:1590 #, no-c-format msgid "Erase data: <userinput>yes</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1516 +#: using-d-i.xml:1515 #, no-c-format msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations<footnote><para> It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. </para></footnote>." msgstr "" #. Tag: para -#: using-d-i.xml:1536 +#: using-d-i.xml:1535 #, no-c-format msgid "If you select <menuchoice> <guimenu>Encryption method:</guimenu> <guimenuitem>Loopback (loop-AES)</guimenuitem> </menuchoice>, the menu changes to provide the following options:" msgstr "" #. Tag: term -#: using-d-i.xml:1545 +#: using-d-i.xml:1544 #, no-c-format msgid "Encryption: <userinput>AES256</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1547 +#: using-d-i.xml:1546 #, no-c-format msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." msgstr "" #. Tag: term -#: using-d-i.xml:1557 +#: using-d-i.xml:1556 #, no-c-format msgid "Encryption key: <userinput>Keyfile (GnuPG)</userinput>" msgstr "" #. Tag: para -#: using-d-i.xml:1559 +#: using-d-i.xml:1558 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1565 +#: using-d-i.xml:1564 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:1566 +#: using-d-i.xml:1565 #, no-c-format msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with <application>GnuPG</application>, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." msgstr "" #. Tag: para -#: using-d-i.xml:1579 +#: using-d-i.xml:1578 #, no-c-format msgid "Please see the the section on random keys above." msgstr "" #. Tag: para -#: using-d-i.xml:1593 +#: using-d-i.xml:1592 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:1602 +#: using-d-i.xml:1601 #, no-c-format msgid "Please note that the <emphasis>graphical</emphasis> version of the installer still has some limitations when compared to the textual one. For cryptography it means you can set up only volumes using <emphasis>passphrases</emphasis> as the encryption keys." msgstr "" #. Tag: para -#: using-d-i.xml:1609 +#: using-d-i.xml:1608 #, no-c-format msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called <guimenu>Configure encrypted volumes</guimenu>. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:1620 +#: using-d-i.xml:1619 #, no-c-format msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1629 +#: using-d-i.xml:1628 #, no-c-format msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:1642 +#: using-d-i.xml:1641 #, no-c-format msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into <filename>/dev/null</filename>, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:1658 +#: using-d-i.xml:1657 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. <informalexample><screen>\n" @@ -1371,595 +1365,583 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1671 +#: using-d-i.xml:1670 #, no-c-format msgid "One thing to note here are the identifiers in parentheses (<replaceable>sda2_crypt</replaceable> and <replaceable>loop0</replaceable> in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between ordinary boot process and boot process with encryption involved will be covered later in <xref linkend=\"mount-encrypted-volumes\"/>." msgstr "" #. Tag: para -#: using-d-i.xml:1681 +#: using-d-i.xml:1680 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:1692 +#: using-d-i.xml:1691 #, no-c-format msgid "Setting up the System" msgstr "" #. Tag: para -#: using-d-i.xml:1693 +#: using-d-i.xml:1692 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1705 +#: using-d-i.xml:1704 #, no-c-format msgid "Configuring Your Time Zone" msgstr "" #. Tag: para -#: using-d-i.xml:1707 +#: using-d-i.xml:1706 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1723 +#: using-d-i.xml:1722 #, no-c-format msgid "Configuring the Clock" msgstr "" #. Tag: para -#: using-d-i.xml:1725 +#: using-d-i.xml:1724 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1732 +#: using-d-i.xml:1731 #, no-c-format 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=\"x86\">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 "" #. Tag: para -#: using-d-i.xml:1743 +#: using-d-i.xml:1742 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1759 +#: using-d-i.xml:1758 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: title -#: using-d-i.xml:1762 +#: using-d-i.xml:1761 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:1764 +#: using-d-i.xml:1763 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1772 +#: using-d-i.xml:1771 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1780 +#: using-d-i.xml:1779 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1790 +#: using-d-i.xml:1789 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:1792 +#: using-d-i.xml:1791 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1799 +#: using-d-i.xml:1798 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1809 +#: using-d-i.xml:1808 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1816 +#: using-d-i.xml:1815 #, no-c-format msgid "If at any point after installation you would like to create another account, use the <command>adduser</command> command." msgstr "" #. Tag: title -#: using-d-i.xml:1828 +#: using-d-i.xml:1827 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:1829 +#: using-d-i.xml:1828 #, no-c-format 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 "" -#. Tag: title -#: using-d-i.xml:1843 -#, no-c-format -msgid "Base System Installation" -msgstr "" - #. Tag: para -#: using-d-i.xml:1845 +#: using-d-i.xml:1841 #, no-c-format -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>." +msgid "During installation of the base system, 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 "" #. Tag: para -#: using-d-i.xml:1855 +#: using-d-i.xml:1850 #, no-c-format -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." +msgid "The unpack/setup messages generated during this phase are also saved in <filename>/var/log/syslog</filename>. You can check them there if the installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:1861 +#: using-d-i.xml:1856 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1874 +#: using-d-i.xml:1868 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:1875 +#: using-d-i.xml:1869 #, no-c-format -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." +msgid "After the base system is installed, you have a usable but limited system. Most users will want to install additional software to the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network." msgstr "" #. Tag: title -#: using-d-i.xml:1889 +#: using-d-i.xml:1883 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:1891 +#: using-d-i.xml:1885 #, no-c-format -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." +msgid "One of the tools used to install packages on a &debian; system is a program called <command>apt-get</command>, from the <classname>apt</classname> package<footnote> <para> Note that the program which actually installs the 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, which will invoke <command>dpkg</command> as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. </para> </footnote>. Other front-ends for package management, like <command>aptitude</command> and <command>synaptic</command>, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, <command>aptitude</command> is now the recommended utility for package management." msgstr "" #. Tag: para -#: using-d-i.xml:1915 +#: using-d-i.xml:1911 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:1931 +#: using-d-i.xml:1927 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:1933 +#: using-d-i.xml:1929 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:1942 +#: using-d-i.xml:1938 #, no-c-format 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 more packages (or remove them), 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 "" #. Tag: para -#: using-d-i.xml:1967 +#: using-d-i.xml:1963 #, no-c-format msgid "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 "" #. Tag: para -#: using-d-i.xml:1974 +#: using-d-i.xml:1970 #, no-c-format msgid "The <quote>Desktop environment</quote> task will install the GNOME desktop environment. The options offered by the installer currently do not allow to select a different desktop environment such as for example KDE." msgstr "" #. Tag: para -#: using-d-i.xml:1980 +#: using-d-i.xml:1976 #, no-c-format msgid "It is possible to get the installer to install KDE by using preseeding (see <xref linkend=\"preseed-pkgsel\"/>) or by adding <literal>tasks=\"standard, kde-desktop\"</literal> at the boot prompt when starting the installer. However, this will only work if the packages needed for KDE are actually available. If you are installing using a full CD image, they will need to be downloaded from a mirror as KDE packages are not included on the first full CD; installing KDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:1991 +#: using-d-i.xml:1987 #, no-c-format msgid "The various server tasks will install software roughly as follows. DNS server: <classname>bind9</classname>; File server: <classname>samba</classname>, <classname>nfs</classname>; Mail server: <classname>exim4</classname>, <classname>spamassassin</classname>, <classname>uw-imap</classname>; Print server: <classname>cups</classname>; SQL server: <classname>postgresql</classname>; Web server: <classname>apache</classname>." msgstr "" #. Tag: para -#: using-d-i.xml:2003 +#: using-d-i.xml:1999 #, no-c-format msgid "Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this point, <command>aptitude</command> will install the packages that are part of the tasks you've selected." msgstr "" #. Tag: para -#: using-d-i.xml:2010 +#: using-d-i.xml:2006 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2019 +#: using-d-i.xml:2015 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2030 +#: using-d-i.xml:2026 #, no-c-format msgid "Configuring Your Mail Transport Agent" msgstr "" #. Tag: para -#: using-d-i.xml:2032 +#: using-d-i.xml:2028 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2040 +#: using-d-i.xml:2036 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2048 +#: using-d-i.xml:2044 #, no-c-format 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 "" #. Tag: term -#: using-d-i.xml:2057 +#: using-d-i.xml:2053 #, no-c-format msgid "internet site" msgstr "" #. Tag: para -#: using-d-i.xml:2058 +#: using-d-i.xml:2054 #, no-c-format 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 "" #. Tag: term -#: using-d-i.xml:2069 +#: using-d-i.xml:2065 #, no-c-format msgid "mail sent by smarthost" msgstr "" #. Tag: para -#: using-d-i.xml:2070 +#: using-d-i.xml:2066 #, no-c-format 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 "" #. Tag: term -#: using-d-i.xml:2083 +#: using-d-i.xml:2079 #, no-c-format msgid "local delivery only" msgstr "" #. Tag: para -#: using-d-i.xml:2084 +#: using-d-i.xml:2080 #, no-c-format 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 "" #. Tag: term -#: using-d-i.xml:2097 +#: using-d-i.xml:2093 #, no-c-format msgid "no configuration at this time" msgstr "" #. Tag: para -#: using-d-i.xml:2098 +#: using-d-i.xml:2094 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2109 +#: using-d-i.xml:2105 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2123 +#: using-d-i.xml:2119 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2125 -#, no-c-format -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 "" - -#. Tag: para -#: using-d-i.xml:2133 +#: using-d-i.xml:2121 #, no-c-format -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." +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 OpenBoot to boot from the network by default; see <xref linkend=\"boot-dev-select-sun\"/>.</phrase>" msgstr "" #. Tag: title -#: using-d-i.xml:2148 +#: using-d-i.xml:2136 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2150 +#: using-d-i.xml:2138 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2158 +#: using-d-i.xml:2146 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2176 +#: using-d-i.xml:2164 #, no-c-format msgid "Install <command>aboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2177 +#: using-d-i.xml:2165 #, no-c-format -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." +msgid "If you have booted from SRM and 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 "" #. Tag: title -#: using-d-i.xml:2197 +#: using-d-i.xml:2185 #, no-c-format msgid "<command>palo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2198 +#: using-d-i.xml:2186 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2207 +#: using-d-i.xml:2195 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2219 +#: using-d-i.xml:2207 #, no-c-format msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2221 +#: using-d-i.xml:2209 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2227 +#: using-d-i.xml:2215 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2233 +#: using-d-i.xml:2221 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2247 +#: using-d-i.xml:2235 #, no-c-format msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2249 +#: using-d-i.xml:2237 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2259 +#: using-d-i.xml:2247 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2267 +#: using-d-i.xml:2255 #, no-c-format -msgid "&d-i; presents you three choices where to install the <command>LILO</command> boot loader:" +msgid "&d-i; offers you three choices on where to install the <command>LILO</command> boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2274 +#: using-d-i.xml:2262 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2274 +#: using-d-i.xml:2262 #, no-c-format msgid "This way the <command>LILO</command> will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2281 +#: using-d-i.xml:2269 #, no-c-format msgid "new Debian partition" msgstr "" #. Tag: para -#: using-d-i.xml:2281 +#: using-d-i.xml:2269 #, no-c-format 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 "" #. Tag: term -#: using-d-i.xml:2290 +#: using-d-i.xml:2278 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2290 +#: using-d-i.xml:2278 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2302 +#: using-d-i.xml:2290 #, no-c-format 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!" msgstr "" #. Tag: title -#: using-d-i.xml:2318 +#: using-d-i.xml:2306 #, no-c-format msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2320 +#: using-d-i.xml:2308 #, no-c-format -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." +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 files 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 do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2336 +#: using-d-i.xml:2324 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2348 +#: using-d-i.xml:2336 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2350 +#: using-d-i.xml:2338 #, no-c-format -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!" +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, <command>elilo</command> may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2365 +#: using-d-i.xml:2353 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2367 +#: using-d-i.xml:2355 #, no-c-format 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 "" #. Tag: filename -#: using-d-i.xml:2389 +#: using-d-i.xml:2377 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2390 +#: using-d-i.xml:2378 #, no-c-format 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 "" #. Tag: filename -#: using-d-i.xml:2399 +#: using-d-i.xml:2387 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2400 +#: using-d-i.xml:2388 #, no-c-format 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 "" #. Tag: filename -#: using-d-i.xml:2410 +#: using-d-i.xml:2398 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2411 +#: using-d-i.xml:2399 #, no-c-format 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 "" #. Tag: filename -#: using-d-i.xml:2423 +#: using-d-i.xml:2411 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2424 +#: using-d-i.xml:2412 #, no-c-format 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 "" #. Tag: filename -#: using-d-i.xml:2434 +#: using-d-i.xml:2422 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2435 +#: using-d-i.xml:2423 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2455 +#: using-d-i.xml:2443 #, no-c-format msgid "<command>arcboot</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2456 +#: using-d-i.xml:2444 #, no-c-format msgid "" "The boot loader on SGI machines is <command>arcboot</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). Arcboot supports different configurations which are set up in <filename>/etc/arcboot.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering <informalexample><screen>\n" @@ -1972,61 +1954,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2475 +#: using-d-i.xml:2463 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2476 +#: using-d-i.xml:2464 #, no-c-format msgid "is the SCSI bus to be booted from, this is <userinput>0</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2484 +#: using-d-i.xml:2472 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2485 +#: using-d-i.xml:2473 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>arcboot</command> is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2493 using-d-i.xml:2562 +#: using-d-i.xml:2481 using-d-i.xml:2550 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2494 +#: using-d-i.xml:2482 #, no-c-format msgid "is the number of the partition on which <filename>/etc/arcboot.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2502 +#: using-d-i.xml:2490 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2503 +#: using-d-i.xml:2491 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/arcboot.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: title -#: using-d-i.xml:2524 +#: using-d-i.xml:2512 #, no-c-format msgid "<command>delo</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2525 +#: using-d-i.xml:2513 #, no-c-format msgid "" "The boot loader on DECstations is <command>DELO</command>. It has to be installed on the same hard disk as the kernel (this is done automatically by the installer). DELO supports different configurations which are set up in <filename>/etc/delo.conf</filename>. Each configuration has a unique name, the default setup as created by the installer is <quote>linux</quote>. After DELO has been installed, the system can be booted from hard disk by entering <informalexample><screen>\n" @@ -2035,247 +2017,265 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2544 +#: using-d-i.xml:2532 #, no-c-format msgid "<replaceable>#</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2545 +#: using-d-i.xml:2533 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is <userinput>3</userinput> for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2553 +#: using-d-i.xml:2541 #, no-c-format msgid "<replaceable>id</replaceable>" msgstr "" #. Tag: para -#: using-d-i.xml:2554 +#: using-d-i.xml:2542 #, no-c-format msgid "is the SCSI ID of the hard disk on which <command>DELO</command> is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2563 +#: using-d-i.xml:2551 #, no-c-format msgid "is the number of the partition on which <filename>/etc/delo.conf</filename> resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2571 +#: using-d-i.xml:2559 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2572 +#: using-d-i.xml:2560 #, no-c-format msgid "is the name of the configuration entry in <filename>/etc/delo.conf</filename>, which is <quote>linux</quote> by default." msgstr "" #. Tag: para -#: using-d-i.xml:2582 +#: using-d-i.xml:2570 #, no-c-format 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 "" #. Tag: screen -#: using-d-i.xml:2588 +#: using-d-i.xml:2576 #, no-c-format msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" msgstr "" #. Tag: title -#: using-d-i.xml:2598 +#: using-d-i.xml:2586 #, no-c-format msgid "Install <command>Yaboot</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2599 +#: using-d-i.xml:2587 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2617 +#: using-d-i.xml:2605 #, no-c-format msgid "Install <command>Quik</command> on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2618 +#: using-d-i.xml:2606 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2634 +#: using-d-i.xml:2622 #, no-c-format msgid "<command>zipl</command>-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2635 +#: using-d-i.xml:2623 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2652 +#: using-d-i.xml:2640 #, no-c-format msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2654 +#: using-d-i.xml:2642 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2679 +#: using-d-i.xml:2667 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2681 +#: using-d-i.xml:2669 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2690 +#: using-d-i.xml:2678 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2707 +#: using-d-i.xml:2695 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2708 +#: using-d-i.xml:2696 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2720 +#: using-d-i.xml:2708 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2722 +#: using-d-i.xml:2710 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2729 +#: using-d-i.xml:2717 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2743 +#: using-d-i.xml:2731 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2744 +#: using-d-i.xml:2732 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2757 +#: using-d-i.xml:2745 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2759 +#: using-d-i.xml:2747 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2766 +#: using-d-i.xml:2754 #, no-c-format 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 "" #. Tag: title -#: using-d-i.xml:2786 +#: using-d-i.xml:2774 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2789 +#: using-d-i.xml:2776 +#, no-c-format +msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second <emphasis>virtual console</emphasis> by pressing <keycombo><keycap>Left Alt</keycap> <keycap>F2</keycap></keycombo><footnote> <para> That is: press 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. </para> </footnote> (on a Mac keyboard, <keycombo><keycap>Option</keycap> <keycap>F2</keycap></keycombo>). Use <keycombo><keycap>Left Alt</keycap> <keycap>F1</keycap></keycombo> to switch back to installer itself." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2794 #, no-c-format -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>." +msgid "If you cannot switch consoles, there is also an <guimenuitem>Execute a Shell</guimenuitem> item on the main menu that can be used to start a shell. To get back to the installer itself, type <userinput>exit</userinput> to close the shell." msgstr "" #. Tag: para #: using-d-i.xml:2801 #, no-c-format -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." +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 shell is a Bourne shell clone called <command>ash</command> and has some nice features like autocompletion and history." msgstr "" #. Tag: para #: using-d-i.xml:2810 #, no-c-format -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." +msgid "To edit and view files, use the text editor <command>nano</command>. Log files for the installation system can be found in the <filename>/var/log</filename> directory." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2817 +#, no-c-format +msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." +msgstr "" + +#. Tag: para +#: using-d-i.xml:2823 +#, no-c-format +msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:2829 +#: using-d-i.xml:2838 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2831 +#: using-d-i.xml:2840 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2841 +#: using-d-i.xml:2850 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2854 +#: using-d-i.xml:2863 #, no-c-format msgid "For installations on &arch-title;, this is the default method after setting up the network." msgstr "" #. Tag: para -#: using-d-i.xml:2859 +#: using-d-i.xml:2868 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2871 +#: using-d-i.xml:2880 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2877 +#: using-d-i.xml:2886 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need to configure your terminal for UTF-8 encoding, because that is what the installation system uses. If you do not, remote installation will be still possible, but you may encounter strange display artefacts like destroyed dialog borders or unreadable non-ascii characters. Establishing a connection with the installation system is as simple as typing: <informalexample><screen>\n" @@ -2284,25 +2284,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2894 +#: using-d-i.xml:2903 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2903 +#: using-d-i.xml:2912 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2913 +#: using-d-i.xml:2922 #, no-c-format 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 "" #. Tag: para -#: using-d-i.xml:2921 +#: using-d-i.xml:2930 #, no-c-format 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." msgstr "" |