diff options
| author | Frans Pop <elendil@planet.nl> | 2006-04-16 14:13:47 +0000 |
|---|---|---|
| committer | Frans Pop <elendil@planet.nl> | 2006-04-16 14:13:47 +0000 |
| commit | ce6b74522dadaf2ddfe553b09b66b6bde220ff61 (patch) | |
| tree | 14c54703f0930dd669d5e3dc324233633debd650 /po | |
| parent | 48888cea18d2202a8a954543c5af0180c353230d (diff) | |
| download | installation-guide-ce6b74522dadaf2ddfe553b09b66b6bde220ff61.zip | |
Remove Polish translation as there has been zero work done on it since po files were created in 2005/12
Diffstat (limited to 'po')
| -rw-r--r-- | po/pl/administrivia.po | 174 | ||||
| -rw-r--r-- | po/pl/bookinfo.po | 74 | ||||
| -rw-r--r-- | po/pl/boot-installer.po | 3416 | ||||
| -rw-r--r-- | po/pl/boot-new.po | 329 | ||||
| -rw-r--r-- | po/pl/gpl.po | 661 | ||||
| -rw-r--r-- | po/pl/hardware.po | 3810 | ||||
| -rw-r--r-- | po/pl/install-methods.po | 1797 | ||||
| -rw-r--r-- | po/pl/installation-howto.po | 445 | ||||
| -rw-r--r-- | po/pl/partitioning.po | 1306 | ||||
| -rw-r--r-- | po/pl/post-install.po | 602 | ||||
| -rw-r--r-- | po/pl/preface.po | 55 | ||||
| -rw-r--r-- | po/pl/preparing.po | 2672 | ||||
| -rw-r--r-- | po/pl/preseed.po | 1360 | ||||
| -rw-r--r-- | po/pl/random-bits.po | 1350 | ||||
| -rw-r--r-- | po/pl/using-d-i.po | 2892 | ||||
| -rw-r--r-- | po/pl/welcome.po | 676 |
16 files changed, 0 insertions, 21619 deletions
diff --git a/po/pl/administrivia.po b/po/pl/administrivia.po deleted file mode 100644 index 4c6e4f0af..000000000 --- a/po/pl/administrivia.po +++ /dev/null @@ -1,174 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: administrivia.xml:5 -#, no-c-format -msgid "Administrivia" -msgstr "" - -#. Tag: title -#: administrivia.xml:9 -#, no-c-format -msgid "About This Document" -msgstr "" - -#. Tag: para -#: administrivia.xml:11 -#, no-c-format -msgid "" -"This manual was created for Sarge's debian-installer, based on the Woody " -"installation manual for boot-floppies, which was based on earlier Debian " -"installation manuals, and on the Progeny distribution manual which was " -"released under GPL in 2003." -msgstr "" - -#. Tag: para -#: administrivia.xml:18 -#, no-c-format -msgid "" -"This document is written in DocBook XML. Output formats are generated by " -"various programs using information from the <classname>docbook-xml</" -"classname> and <classname>docbook-xsl</classname> packages." -msgstr "" - -#. Tag: para -#: administrivia.xml:25 -#, no-c-format -msgid "" -"In order to increase the maintainability of this document, we use a number " -"of XML features, such as entities and profiling attributes. These play a " -"role akin to variables and conditionals in programming languages. The XML " -"source to this document contains information for each different architecture " -"— profiling attributes are used to isolate certain bits of text as " -"architecture-specific." -msgstr "" - -#. Tag: title -#: administrivia.xml:52 -#, no-c-format -msgid "Contributing to This Document" -msgstr "" - -#. Tag: para -#: administrivia.xml:54 -#, no-c-format -msgid "" -"If you have problems or suggestions regarding this document, you should " -"probably submit them as a bug report against the package <classname>debian-" -"installer-manual</classname>. See the <classname>reportbug</classname> " -"package or read the online documentation of the <ulink url=\"&url-bts;" -"\">Debian Bug Tracking System</ulink>. It would be nice if you could check " -"the <ulink url=\"&url-bts;debian-installer-manual\">open bugs against debian-" -"installer-manual</ulink> to see whether your problem has already been " -"reported. If so, you can supply additional corroboration or helpful " -"information to <email><replaceable>XXXX</replaceable>@bugs.debian.org</" -"email>, where <replaceable>XXXX</replaceable> is the number for the already-" -"reported bug." -msgstr "" - -#. Tag: para -#: administrivia.xml:70 -#, no-c-format -msgid "" -"Better yet, get a copy of the DocBook source for this document, and produce " -"patches against it. The DocBook source can be found at the <ulink url=\"&url-" -"d-i-websvn;\">debian-installer WebSVN</ulink>. If you're not familiar with " -"DocBook, don't worry: there is a simple cheatsheet in the manuals directory " -"that will get you started. It's like html, but oriented towards the meaning " -"of the text rather than the presentation. Patches submitted to the debian-" -"boot mailing list (see below) are welcomed. For instructions on how to check " -"out the sources via SVN, see <ulink url=\"&url-d-i-readme;\">README</ulink> " -"from the source root directory." -msgstr "" - -#. Tag: para -#: administrivia.xml:84 -#, no-c-format -msgid "" -"Please do <emphasis>not</emphasis> contact the authors of this document " -"directly. There is also a discussion list for &d-i;, which includes " -"discussions of this manual. The mailing list is <email>debian-boot@lists." -"debian.org</email>. Instructions for subscribing to this list can be found " -"at the <ulink url=\"&url-debian-lists-subscribe;\">Debian Mailing List " -"Subscription</ulink> page; or you can browse the <ulink url=\"&url-debian-" -"list-archives;\">Debian Mailing List Archives</ulink> online." -msgstr "" - -#. Tag: title -#: administrivia.xml:101 -#, no-c-format -msgid "Major Contributions" -msgstr "" - -#. Tag: para -#: administrivia.xml:103 -#, no-c-format -msgid "" -"This document was originally written by Bruce Perens, Sven Rudolph, Igor " -"Grobman, James Treacy, and Adam Di Carlo. Sebastian Ley wrote the " -"Installation Howto. Many, many Debian users and developers contributed to " -"this document. Particular note must be made of Michael Schmitz (m68k " -"support), Frank Neumann (original author of the <ulink url=\"&url-m68k-old-" -"amiga-install;\">Amiga install manual</ulink>), Arto Astala, Eric Delaunay/" -"Ben Collins (SPARC information), Tapio Lehtonen, and Stéphane Bortzmeyer for " -"numerous edits and text. We have to thank Pascal Le Bail for useful " -"information about booting from USB memory sticks. Miroslav Kuře has " -"documented a lot of the new functionality in Sarge's debian-installer." -msgstr "" - -#. Tag: para -#: administrivia.xml:118 -#, no-c-format -msgid "" -"Extremely helpful text and information was found in Jim Mintha's HOWTO for " -"network booting (no URL available), the <ulink url=\"&url-debian-faq;" -"\">Debian FAQ</ulink>, the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</" -"ulink>, the <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC Processors " -"FAQ</ulink>, the <ulink url=\"&url-alpha-faq;\">Linux/Alpha FAQ</ulink>, " -"amongst others. The maintainers of these freely available and rich sources " -"of information must be recognized." -msgstr "" - -#. Tag: para -#: administrivia.xml:130 -#, no-c-format -msgid "" -"The section on chrooted installations in this manual (<xref linkend=\"linux-" -"upgrade\"/>) was derived in part from documents copyright Karsten M. Self." -msgstr "" - -#. Tag: para -#: administrivia.xml:136 -#, no-c-format -msgid "" -"The section on installations over plip in this manual (<xref linkend=\"plip" -"\"/>) was based on the <ulink url=\"&url-plip-install-howto;\">PLIP-Install-" -"HOWTO</ulink> by Gilles Lamiral." -msgstr "" - -#. Tag: title -#: administrivia.xml:147 -#, no-c-format -msgid "Trademark Acknowledgement" -msgstr "" - -#. Tag: para -#: administrivia.xml:148 -#, no-c-format -msgid "All trademarks are property of their respective trademark owners." -msgstr "" diff --git a/po/pl/bookinfo.po b/po/pl/bookinfo.po deleted file mode 100644 index 751ccb0e8..000000000 --- a/po/pl/bookinfo.po +++ /dev/null @@ -1,74 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: bookinfo.xml:5 -#, no-c-format -msgid "&debian; Installation Guide" -msgstr "" - -#. Tag: para -#: bookinfo.xml:8 -#, no-c-format -msgid "" -"This document contains installation instructions for the &debian; &release; " -"system (codename <quote>&releasename;</quote>), for the &arch-title; " -"(<quote>&architecture;</quote>) architecture. It also contains pointers to " -"more information and information on how to make the most of your new Debian " -"system." -msgstr "" - -#. Tag: para -#: bookinfo.xml:17 -#, no-c-format -msgid "" -"This installation guide is based on an earlier manual written for the old " -"Debian installation system (the <quote>boot-floppies</quote>), and has been " -"updated to document the new Debian installer. However, for &architecture;, " -"the manual has not been fully updated and fact checked for the new " -"installer. There may remain parts of the manual that are incomplete or " -"outdated or that still document the boot-floppies installer. A newer version " -"of this manual, possibly better documenting this architecture, may be found " -"on the Internet at the <ulink url=\"&url-d-i;\">&d-i; home page</ulink>. You " -"may also be able to find additional translations there." -msgstr "" - -#. Tag: para -#: bookinfo.xml:30 -#, no-c-format -msgid "" -"Although this installation guide for &architecture; is mostly up-to-date, we " -"plan to make some changes and reorganize parts of the manual after the " -"official release of &releasename;. A newer version of this manual may be " -"found on the Internet at the <ulink url=\"&url-d-i;\">&d-i; home page</" -"ulink>. You may also be able to find additional translations there." -msgstr "" - -#. Tag: holder -#: bookinfo.xml:44 -#, no-c-format -msgid "the Debian Installer team" -msgstr "" - -#. Tag: para -#: bookinfo.xml:48 -#, no-c-format -msgid "" -"This manual is free software; you may redistribute it and/or modify it under " -"the terms of the GNU General Public License. Please refer to the license in " -"<xref linkend=\"appendix-gpl\"/>." -msgstr "" diff --git a/po/pl/boot-installer.po b/po/pl/boot-installer.po deleted file mode 100644 index 28df91cbb..000000000 --- a/po/pl/boot-installer.po +++ /dev/null @@ -1,3416 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-03-19 13:45+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: boot-installer.xml:4 -#, no-c-format -msgid "Booting the Installation System" -msgstr "" - -#. Tag: title -#: boot-installer.xml:9 -#, no-c-format -msgid "Booting the Installer on &arch-title;" -msgstr "" - -#. Tag: title -#: boot-installer.xml:20 -#, no-c-format -msgid "Alpha Console Firmware" -msgstr "" - -#. Tag: para -#: boot-installer.xml:21 -#, no-c-format -msgid "" -"Console firmware is stored in a flash ROM and started when an Alpha system " -"is powered up or reset. There are two different console specifications used " -"on Alpha systems, and hence two classes of console firmware available:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:31 -#, no-c-format -msgid "" -"<emphasis>SRM console</emphasis>, based on the Alpha Console Subsystem " -"specification, which provides an operating environment for OpenVMS, Tru64 " -"UNIX, and Linux operating systems." -msgstr "" - -#. Tag: para -#: boot-installer.xml:38 -#, no-c-format -msgid "" -"<emphasis>ARC, AlphaBIOS, or ARCSBIOS console</emphasis>, based on the " -"Advanced RISC Computing (ARC) specification, which provides an operating " -"environment for Windows NT." -msgstr "" - -#. Tag: para -#: boot-installer.xml:47 -#, no-c-format -msgid "" -"From the user's perspective, the most important difference between SRM and " -"ARC is that the choice of console constrains the possible disk-partitioning " -"scheme for the hard disk which you wish to boot off of." -msgstr "" - -#. Tag: para -#: boot-installer.xml:54 -#, no-c-format -msgid "" -"ARC requires that you use an MS-DOS partition table (as created by " -"<command>cfdisk</command>) for the boot disk. Therefore MS-DOS partition " -"tables are the <quote>native</quote> partition format when booting from ARC. " -"In fact, since AlphaBIOS contains a disk partitioning utility, you may " -"prefer to partition your disks from the firmware menus before installing " -"Linux." -msgstr "" - -#. Tag: para -#: boot-installer.xml:63 -#, no-c-format -msgid "" -"Conversely, SRM is <emphasis>incompatible</emphasis><footnote> <para> " -"Specifically, the bootsector format required by the Console Subsystem " -"Specification conflicts with the placement of the DOS partition table. </" -"para> </footnote> with MS-DOS partition tables. Since Tru64 Unix uses the " -"BSD disklabel format, this is the <quote>native</quote> partition format for " -"SRM installations." -msgstr "" - -#. Tag: para -#: boot-installer.xml:76 -#, no-c-format -msgid "" -"GNU/Linux is the only operating system on Alpha that can be booted from both " -"console types, but &debian; &release; only supports booting on SRM-based " -"systems. If you have an Alpha for which no version of SRM is available, if " -"you will be dual-booting the system with Windows NT, or if your boot device " -"requires ARC console support for BIOS initialization, you will not be able " -"to use the &debian; &release; installer. You can still run &debian; " -"&release; on such systems by using other install media; for instance, you " -"can install Debian woody with MILO and upgrade." -msgstr "" - -#. Tag: para -#: boot-installer.xml:87 -#, no-c-format -msgid "" -"Because <command>MILO</command> is not available for any of the Alpha " -"systems currently in production (as of February 2000), and because it is no " -"longer necessary to buy an OpenVMS or Tru64 Unix license to have SRM " -"firmware on your older Alpha, it is recommended that you use SRM when " -"possible." -msgstr "" - -#. Tag: para -#: boot-installer.xml:95 -#, no-c-format -msgid "" -"The following table summarizes available and supported system type/console " -"combinations (see <xref linkend=\"alpha-cpus\"/> for the system type names). " -"The word <quote>ARC</quote> below denotes any of the ARC-compliant consoles." -msgstr "" - -#. Tag: entry -#: boot-installer.xml:107 -#, no-c-format -msgid "System Type" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:108 -#, no-c-format -msgid "Console Type Supported" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:114 -#, no-c-format -msgid "alcor" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:115 boot-installer.xml:118 boot-installer.xml:124 -#: boot-installer.xml:130 boot-installer.xml:133 boot-installer.xml:136 -#: boot-installer.xml:139 boot-installer.xml:145 boot-installer.xml:148 -#: boot-installer.xml:151 boot-installer.xml:160 boot-installer.xml:169 -#: boot-installer.xml:184 boot-installer.xml:187 -#, no-c-format -msgid "ARC or SRM" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:117 -#, no-c-format -msgid "avanti" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:120 -#, no-c-format -msgid "book1" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:121 boot-installer.xml:127 boot-installer.xml:142 -#: boot-installer.xml:154 boot-installer.xml:163 boot-installer.xml:166 -#: boot-installer.xml:172 boot-installer.xml:178 boot-installer.xml:181 -#, no-c-format -msgid "SRM only" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:123 -#, no-c-format -msgid "cabriolet" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:126 -#, no-c-format -msgid "dp264" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:129 -#, no-c-format -msgid "eb164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:132 -#, no-c-format -msgid "eb64p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:135 -#, no-c-format -msgid "eb66" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:138 -#, no-c-format -msgid "eb66p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:141 -#, no-c-format -msgid "jensen" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:144 -#, no-c-format -msgid "lx164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:147 -#, no-c-format -msgid "miata" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:150 -#, no-c-format -msgid "mikasa" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:153 -#, no-c-format -msgid "mikasa-p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:156 -#, no-c-format -msgid "nautilus" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:157 -#, no-c-format -msgid "ARC (see motherboard manual) or SRM" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:159 -#, no-c-format -msgid "noname" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:162 -#, no-c-format -msgid "noritake" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:165 -#, no-c-format -msgid "noritake-p" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:168 -#, no-c-format -msgid "pc164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:171 -#, no-c-format -msgid "rawhide" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:174 -#, no-c-format -msgid "ruffian" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 -#, no-c-format -msgid "ARC only" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:177 -#, no-c-format -msgid "sable" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:180 -#, no-c-format -msgid "sable-g" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:183 -#, no-c-format -msgid "sx164" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:186 -#, no-c-format -msgid "takara" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:189 -#, no-c-format -msgid "<entry>xl</entry>" -msgstr "" - -#. Tag: entry -#: boot-installer.xml:192 -#, no-c-format -msgid "<entry>xlt</entry>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:200 -#, no-c-format -msgid "" -"Generally, none of these consoles can boot Linux directly, so the assistance " -"of an intermediary bootloader is required. For the SRM console, " -"<command>aboot</command>, a small, platform-independent bootloader, is used. " -"See the (unfortunately outdated) <ulink url=\"&url-srm-howto;\">SRM HOWTO</" -"ulink> for more information on <command>aboot</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:209 -#, no-c-format -msgid "" -"The following paragraphs are from the woody install manual, and are included " -"here for reference; they may be useful to someone at a later date when " -"Debian supports MILO-based installs again." -msgstr "" - -#. Tag: para -#: boot-installer.xml:215 -#, no-c-format -msgid "" -"Generally, none of these consoles can boot Linux directly, so the assistance " -"of an intermediary bootloader is required. There are two mainstream Linux " -"loaders: <command>MILO</command> and <command>aboot</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:221 -#, no-c-format -msgid "" -"<command>MILO</command> is itself a console, which replaces ARC or SRM in " -"memory. <command>MILO</command> can be booted from both ARC and SRM and is " -"the only way to bootstrap Linux from the ARC console. <command>MILO</" -"command> is platform-specific (a different <command>MILO</command> is needed " -"for each system type) and exist only for those systems, for which ARC " -"support is shown in the table above. See also the (unfortunately outdated) " -"<ulink url=\"&url-milo-howto;\">MILO HOWTO</ulink>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:231 -#, no-c-format -msgid "" -"<command>aboot</command> is a small, platform-independent bootloader, which " -"runs from SRM only. See the (also unfortunately outdated) <ulink url=\"&url-" -"srm-howto;\">SRM HOWTO</ulink> for more information on <command>aboot</" -"command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:238 -#, no-c-format -msgid "" -"Thus, three scenarios are generally possible, depending on the system's " -"console firmware and whether or not <command>MILO</command> is available: " -"<informalexample><screen>\n" -"SRM -> aboot\n" -"SRM -> MILO\n" -"ARC -> MILO\n" -"</screen></informalexample> Because <command>MILO</command> is not available " -"for any of the Alpha systems currently in production (as of February 2000), " -"and because it is no longer necessary to buy an OpenVMS or Tru64 Unix " -"license to have SRM firmware on your older Alpha, it is recommended that you " -"use SRM and <command>aboot</command> on new installations of GNU/Linux, " -"unless you wish to dual-boot with Windows NT." -msgstr "" - -#. Tag: para -#: boot-installer.xml:253 -#, no-c-format -msgid "" -"The majority of AlphaServers and all current server and workstation products " -"contain both SRM and AlphaBIOS in their firmware. For <quote>half-flash</" -"quote> machines such as the various evaluation boards, it is possible to " -"switch from one version to another by reflashing the firmware. Also, once " -"SRM is installed, it is possible to run ARC/AlphaBIOS from a floppy disk " -"(using the <command>arc</command> command). For the reasons mentioned above, " -"we recommend switching to SRM before installing &debian;." -msgstr "" - -#. Tag: para -#: boot-installer.xml:264 -#, no-c-format -msgid "" -"As on other architectures, you should install the newest available revision " -"of the firmware<footnote> <para> Except on Jensen, where Linux is not " -"supported on firmware versions newer than 1.7 — see <ulink url=\"&url-" -"jensen-howto;\"></ulink> for more information. </para> </footnote> before " -"installing &debian;. For Alpha, firmware updates can be obtained from <ulink " -"url=\"&url-alpha-firmware;\">Alpha Firmware Updates</ulink>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:283 boot-installer.xml:1007 boot-installer.xml:1498 -#: boot-installer.xml:1993 boot-installer.xml:2075 boot-installer.xml:2164 -#: boot-installer.xml:2508 boot-installer.xml:2604 -#, no-c-format -msgid "Booting with TFTP" -msgstr "" - -#. Tag: para -#: boot-installer.xml:284 -#, no-c-format -msgid "" -"In SRM, Ethernet interfaces are named with the <userinput>ewa</userinput> " -"prefix, and will be listed in the output of the <userinput>show dev</" -"userinput> command, like this (edited slightly): <informalexample><screen>\n" -">>> show dev\n" -"ewa0.0.0.9.0 EWA0 08-00-2B-86-98-65\n" -"ewb0.0.0.11.0 EWB0 08-00-2B-86-98-54\n" -"ewc0.0.0.2002.0 EWC0 00-06-2B-01-32-B0\n" -"</screen></informalexample> You first need to set the boot protocol: " -"<informalexample><screen>\n" -">>> set ewa0_protocol bootp\n" -"</screen></informalexample> Then check the medium type is correct: " -"<informalexample><screen>\n" -">>> set ewa0_mode <replaceable>mode</replaceable>\n" -"</screen></informalexample> You can get a listing of valid modes with " -"<userinput>>>>set ewa0_mode</userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:302 -#, no-c-format -msgid "" -"Then, to boot from the first Ethernet interface, you would type: " -"<informalexample><screen>\n" -">>> boot ewa0 -flags \"\"\n" -"</screen></informalexample> This will boot using the default kernel " -"parameters as included in the netboot image." -msgstr "" - -#. Tag: para -#: boot-installer.xml:311 -#, no-c-format -msgid "" -"If you wish to use a serial console, you <emphasis>must</emphasis> pass the " -"<userinput>console=</userinput> parameter to the kernel. This can be done " -"using the <userinput>-flags</userinput> argument to the SRM <userinput>boot</" -"userinput> command. The serial ports are named the same as their " -"corresponding files in <userinput>/dev</userinput>. Also, when specifying " -"additional kernel parameters, you must repeat certain default options that " -"are needed by the &d-i; images. For example, to boot from <userinput>ewa0</" -"userinput> and use a console on the first serial port, you would type:" -msgstr "" - -#. Tag: screen -#: boot-installer.xml:323 -#, no-c-format -msgid "" -">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -"console=ttyS0"" -msgstr "" - -#. Tag: title -#: boot-installer.xml:328 -#, no-c-format -msgid "Booting from CD-ROM with the SRM Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:329 -#, no-c-format -msgid "" -"Type <informalexample><screen>\n" -">>> boot xxxx -flags 0\n" -"</screen></informalexample> where <replaceable>xxxx</replaceable> is your CD-" -"ROM drive in SRM notation." -msgstr "" - -#. Tag: title -#: boot-installer.xml:341 -#, no-c-format -msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:342 -#, no-c-format -msgid "" -"To boot a CD-ROM from the ARC console, find your sub-architecture code name " -"(see <xref linkend=\"alpha-cpus\"/>), then enter <filename>\\milo\\linload." -"exe</filename> as the boot loader and <filename>\\milo" -"\\<replaceable>subarch</replaceable></filename> (where <replaceable>subarch</" -"replaceable> is the proper subarchitecture name) as the OS Path in the `OS " -"Selection Setup' menu. Ruffians make an exception: You need to use <filename>" -"\\milo\\ldmilo.exe</filename> as boot loader." -msgstr "" - -#. Tag: title -#: boot-installer.xml:358 -#, no-c-format -msgid "Booting from Floppies with the SRM Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:359 -#, no-c-format -msgid "" -"At the SRM prompt (<prompt>>>></prompt>), issue the following " -"command: <informalexample><screen>\n" -">>> boot dva0 -flags 0\n" -"</screen></informalexample> possibly replacing <filename>dva0</filename> " -"with the actual device name. Usually, <filename>dva0</filename> is the " -"floppy; type <informalexample><screen>\n" -">>> show dev\n" -"</screen></informalexample> to see the list of devices (e.g., if you want to " -"boot from a CD). Note that if you are booting via MILO, <command>-flags</" -"command> argument is ignored, so you can just type <command>boot dva0</" -"command>. If everything works OK, you will eventually see the Linux kernel " -"boot." -msgstr "" - -#. Tag: para -#: boot-installer.xml:376 -#, no-c-format -msgid "" -"If you want to specify kernel parameters when booting via <command>aboot</" -"command>, use the following command: <informalexample><screen>\n" -">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -"load_ramdisk=1 arguments\"\n" -"</screen></informalexample> (typed on one line), substituting, if necessary, " -"the actual SRM boot device name for <filename>dva0</filename>, the Linux " -"boot device name for <filename>fd0</filename>, and the desired kernel " -"parameters for <filename>arguments</filename>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:388 -#, no-c-format -msgid "" -"If you want to specify kernel parameters when booting via <command>MILO</" -"command>, you will have to interrupt bootstrap once you get into MILO. See " -"<xref linkend=\"booting-from-milo\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:398 -#, no-c-format -msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:400 -#, no-c-format -msgid "" -"In the OS Selection menu, set <command>linload.exe</command> as the boot " -"loader, and <command>milo</command> as the OS Path. Bootstrap using the " -"newly created entry." -msgstr "" - -#. Tag: title -#: boot-installer.xml:409 -#, no-c-format -msgid "Booting with MILO" -msgstr "" - -#. Tag: para -#: boot-installer.xml:410 -#, no-c-format -msgid "" -"MILO contained on the bootstrap media is configured to proceed straight to " -"Linux automatically. Should you wish to intervene, all you need is to press " -"space during MILO countdown." -msgstr "" - -#. Tag: para -#: boot-installer.xml:416 -#, no-c-format -msgid "" -"If you want to specify all the bits explicitly (for example, to supply " -"additional parameters), you can use a command like this: " -"<informalexample><screen>\n" -"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 <!-- arguments -->\n" -"</screen></informalexample> If you are booting from something other than a " -"floppy, substitute <filename>fd0</filename> in the above example with the " -"appropriate device name in Linux notation. The <command>help</command> " -"command would give you a brief MILO command reference." -msgstr "" - -#. Tag: title -#: boot-installer.xml:435 -#, no-c-format -msgid "Booting from TFTP" -msgstr "" - -#. Tag: para -#: boot-installer.xml:441 boot-installer.xml:1013 boot-installer.xml:1516 -#: boot-installer.xml:1999 boot-installer.xml:2514 boot-installer.xml:2610 -#, no-c-format -msgid "" -"Booting from the network requires that you have a network connection and a " -"TFTP network boot server (DHCP, RARP, or BOOTP)." -msgstr "" - -#. Tag: para -#: boot-installer.xml:446 boot-installer.xml:1018 boot-installer.xml:1521 -#: boot-installer.xml:2004 boot-installer.xml:2519 boot-installer.xml:2615 -#, no-c-format -msgid "" -"Older systems such as the 715 might require the use of an RBOOT server " -"instead of a BOOTP server." -msgstr "" - -#. Tag: para -#: boot-installer.xml:451 boot-installer.xml:1023 boot-installer.xml:1526 -#: boot-installer.xml:2009 boot-installer.xml:2524 boot-installer.xml:2620 -#, no-c-format -msgid "" -"The installation method to support network booting is described in <xref " -"linkend=\"install-tftp\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:459 -#, no-c-format -msgid "Booting from TFTP on Netwinder" -msgstr "" - -#. Tag: para -#: boot-installer.xml:460 -#, no-c-format -msgid "" -"Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " -"(which is generally referred to as <literal>eth0</literal>) and a 100Mbps " -"Tulip card. There may be problems loading the image via TFTP using the " -"100Mbps card so it is recommended that you use the 10Mbps interfaced (the " -"one labeled with <literal>10 Base-T</literal>)." -msgstr "" - -#. Tag: para -#: boot-installer.xml:469 -#, no-c-format -msgid "" -"You need NeTTrom 2.2.1 or later to boot the installation system, and version " -"2.3.3 is recommended. Unfortunately, firmware files are currently not " -"available for download because of license issues. If this situation changes, " -"you may find new images at <ulink url=\"http//www.netwinder.org/\"></ulink>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:477 -#, no-c-format -msgid "" -"When you boot your Netwinder you have to interrupt the boot process during " -"the countdown. This allows you to set a number of firmware settings needed " -"in order to boot the installer. First of all, start by loading the default " -"settings: <informalexample><screen>\n" -" NeTTrom command-> load-defaults\n" -"</screen></informalexample> Furthermore, you must configure the network, " -"either with a static address: <informalexample><screen>\n" -" NeTTrom command-> setenv netconfig_eth0 flash\n" -" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -"</screen></informalexample> where 24 is the number of set bits in the " -"netmask, or a dynamic address: <informalexample><screen>\n" -" NeTTrom command-> setenv netconfig_eth0 dhcp\n" -"</screen></informalexample> You may also need to configure the " -"<userinput>route1</userinput> settings if the TFTP server is not on the " -"local subnet. Following these settings, you have to specify the TFTP server " -"and the location of the image. You can then store your settings to flash. " -"<informalexample><screen>\n" -" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -" NeTTrom command-> setenv kerntftpfile boot.img\n" -" NeTTrom command-> save-all\n" -"</screen></informalexample> Now you have to tell the firmware that the TFTP " -"image should be booted: <informalexample><screen>\n" -" NeTTrom command-> setenv kernconfig tftp\n" -" NeTTrom command-> setenv rootdev /dev/ram\n" -"</screen></informalexample> If you use a serial console to install your " -"Netwinder, you need to add the following setting: <informalexample><screen>\n" -" NeTTrom command-> setenv cmdappend root=/dev/ram " -"console=ttyS0,115200\n" -"</screen></informalexample> Alternatively, for installations using a " -"keyboard and monitor you have to set: <informalexample><screen>\n" -" NeTTrom command-> setenv cmdappend root=/dev/ram\n" -"</screen></informalexample> You can use the <command>printenv</command> " -"command to review your environment settings. After you have verified that " -"the settings are correct, you can load the image: <informalexample><screen>\n" -" NeTTrom command-> boot\n" -"</screen></informalexample> In case you run into any problems, a <ulink url=" -"\"http://www.netwinder.org/howto/Firmware-HOWTO.html\">detailed HOWTO</" -"ulink> is available." -msgstr "" - -#. Tag: title -#: boot-installer.xml:529 -#, no-c-format -msgid "Booting from TFTP on CATS" -msgstr "" - -#. Tag: para -#: boot-installer.xml:530 -#, no-c-format -msgid "" -"On CATS machines, use <command>boot de0:</command> or similar at the Cyclone " -"prompt." -msgstr "" - -#. Tag: title -#: boot-installer.xml:540 -#, no-c-format -msgid "Booting from CD-ROM" -msgstr "" - -#. Tag: para -#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1135 -#: boot-installer.xml:1956 boot-installer.xml:2296 boot-installer.xml:2650 -#, no-c-format -msgid "" -"The easiest route for most people will be to use a set of Debian CDs. If you " -"have a CD set, and if your machine supports booting directly off the CD, " -"great! Simply <phrase arch=\"i386\"> configure your system for booting off a " -"CD as described in <xref linkend=\"boot-dev-select\"/>, </phrase> insert " -"your CD, reboot, and proceed to the next chapter." -msgstr "" - -#. Tag: para -#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1146 -#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 -#, no-c-format -msgid "" -"Note that certain CD drives may require special drivers, and thus be " -"inaccessible in the early installation stages. If it turns out the standard " -"way of booting off a CD doesn't work for your hardware, revisit this chapter " -"and read about alternate kernels and installation methods which may work for " -"you." -msgstr "" - -#. Tag: para -#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1154 -#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 -#, no-c-format -msgid "" -"Even if you cannot boot from CD-ROM, you can probably install the Debian " -"system components and any packages you want from CD-ROM. Simply boot using a " -"different media, such as floppies. When it's time to install the operating " -"system, base system, and any additional packages, point the installation " -"system at the CD-ROM drive." -msgstr "" - -#. Tag: para -#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1162 -#: boot-installer.xml:1983 boot-installer.xml:2323 boot-installer.xml:2677 -#, no-c-format -msgid "" -"If you have problems booting, see <xref linkend=\"boot-troubleshooting\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:580 -#, no-c-format -msgid "" -"To boot a CD-ROM from the Cyclone console prompt, use the command " -"<command>boot cd0:cats.bin</command>" -msgstr "" - -#. Tag: title -#: boot-installer.xml:589 -#, no-c-format -msgid "Booting from Firmware" -msgstr "" - -#. Tag: para -#: boot-installer.xml:595 -#, no-c-format -msgid "" -"There is an increasing number of consumer devices that directly boot from a " -"flash chip on the device. The installer can be written to flash so it will " -"automatically start when you reboot your machines." -msgstr "" - -#. Tag: para -#: boot-installer.xml:601 -#, no-c-format -msgid "" -"In many cases, changing the firmware of an embedded device voids your " -"warranty. Sometimes you are also not able to recover your device if there " -"are problems during the flashing process. Therefore, please take care and " -"follow the steps precisely." -msgstr "" - -#. Tag: title -#: boot-installer.xml:612 -#, no-c-format -msgid "Booting the NSLU2" -msgstr "" - -#. Tag: para -#: boot-installer.xml:613 -#, no-c-format -msgid "There are three ways how to put the installer firmware into flash:" -msgstr "" - -#. Tag: title -#: boot-installer.xml:619 -#, no-c-format -msgid "Using the NSLU2 web interface" -msgstr "" - -#. Tag: para -#: boot-installer.xml:620 -#, no-c-format -msgid "" -"Go to the administration section and choose the menu item <literal>Upgrade</" -"literal>. You can then browse your disk for the installer image you have " -"previously downloaded. Then press the <literal>Start Upgrade</literal> " -"button, confirm, wait for a few minutes and confirm again. The system will " -"then boot straight into the installer." -msgstr "" - -#. Tag: title -#: boot-installer.xml:631 -#, no-c-format -msgid "Via the network using Linux/Unix" -msgstr "" - -#. Tag: para -#: boot-installer.xml:632 -#, no-c-format -msgid "" -"You can use <command>upslug2</command> from any Linux or Unix machine to " -"upgrade the machine via the network. This software is packaged for Debian. " -"First, you have to put your NSLU2 in upgrade mode: <orderedlist> " -"<listitem><para> Disconnect any disks and/or devices from the USB ports. </" -"para></listitem> <listitem><para> Power off the NSLU2 </para></listitem> " -"<listitem><para> Press and hold the reset button (accessible through the " -"small hole on the back just above the power input). </para></listitem> " -"<listitem><para> Press and release the power button to power on the NSLU2. </" -"para></listitem> <listitem><para> Wait for 10 seconds watching the ready/" -"status LED. After 10 seconds it will change from amber to red. Immediately " -"release the reset button. </para></listitem> <listitem><para> The NSLU2 " -"ready/status LED will flash alternately red/green (there is a 1 second delay " -"before the first green). The NSLU2 is now in upgrade mode. </para></" -"listitem> </orderedlist> See the <ulink url=\"http://www.nslu2-linux.org/" -"wiki/OpenSlug/UsingTheBinary\">NSLU2-Linux pages</ulink> if you have " -"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " -"new image: <informalexample><screen>\n" -"sudo upslug2 -i di-nslu2.bin\n" -"</screen></informalexample> Note that the tool also shows the MAC address of " -"your NSLU2, which may come in handy to configure your DHCP server. After the " -"whole image has been written and verified, the system will automatically " -"reboot. Make sure you connect your USB disk again now, otherwise the " -"installer won't be able to find it." -msgstr "" - -#. Tag: title -#: boot-installer.xml:693 -#, no-c-format -msgid "Via the network using Windows" -msgstr "" - -#. Tag: para -#: boot-installer.xml:694 -#, no-c-format -msgid "" -"There is <ulink url=\"http://www.everbesthk.com/8-download/sercomm/firmware/" -"all_router_utility.zip\">a tool</ulink> for Windows to upgrade the firmware " -"via the network." -msgstr "" - -#. Tag: title -#: boot-installer.xml:710 boot-installer.xml:1129 boot-installer.xml:1944 -#: boot-installer.xml:2290 boot-installer.xml:2644 -#, no-c-format -msgid "Booting from a CD-ROM" -msgstr "" - -#. Tag: title -#: boot-installer.xml:848 -#, no-c-format -msgid "" -"Booting from Linux Using <command>LILO</command> or <command>GRUB</command>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:851 -#, no-c-format -msgid "" -"To boot the installer from hard disk, you must first download and place the " -"needed files as described in <xref linkend=\"boot-drive-files\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:856 -#, no-c-format -msgid "" -"If you intend to use the hard drive only for booting and then download " -"everything over the network, you should download the <filename>netboot/" -"debian-installer/i386/initrd.gz</filename> file and its corresponding " -"kernel. This will allow you to repartition the hard disk from which you boot " -"the installer, although you should do so with care." -msgstr "" - -#. Tag: para -#: boot-installer.xml:864 -#, no-c-format -msgid "" -"Alternatively, if you intend to keep an existing partition on the hard drive " -"unchanged during the install, you can download the <filename>hd-media/initrd." -"gz</filename> file and its kernel, as well as copy a CD iso to the drive " -"(make sure the file is named ending in <literal>.iso</literal>). The " -"installer can then boot from the drive and install from the CD image, " -"without needing the network." -msgstr "" - -#. Tag: para -#: boot-installer.xml:873 -#, no-c-format -msgid "" -"For <command>LILO</command>, you will need to configure two essential things " -"in <filename>/etc/lilo.conf</filename>: <itemizedlist> <listitem><para> to " -"load the <filename>initrd.gz</filename> installer at boot time; </para></" -"listitem> <listitem><para> have the <filename>vmlinuz</filename> kernel use " -"a RAM disk as its root partition. </para></listitem> </itemizedlist> Here is " -"a <filename>/etc/lilo.conf</filename> example:" -msgstr "" - -#. Tag: screen -#: boot-installer.xml:894 -#, no-c-format -msgid "" -"image=/boot/newinstall/vmlinuz\n" -" label=newinstall\n" -" initrd=/boot/newinstall/initrd.gz\n" -" root=/dev/ram0\n" -" append=\"ramdisk_size=12000\"" -msgstr "" - -#. Tag: para -#: boot-installer.xml:894 -#, no-c-format -msgid "" -"For more details, refer to the <citerefentry><refentrytitle>initrd</" -"refentrytitle> <manvolnum>4</manvolnum></citerefentry> and " -"<citerefentry><refentrytitle>lilo.conf</refentrytitle> <manvolnum>5</" -"manvolnum></citerefentry> man pages. Now run <userinput>lilo</userinput> and " -"reboot." -msgstr "" - -#. Tag: para -#: boot-installer.xml:903 -#, no-c-format -msgid "" -"The procedure for <command>GRUB</command> is quite similar. Locate your " -"<filename>menu.lst</filename> in the <filename>/boot/grub/</filename> " -"directory (sometimes in the <filename>/boot/boot/grub/</filename>), add the " -"following lines: <informalexample><screen>\n" -"title New Install\n" -"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" -"initrd (hd0,0)/boot/newinstall/initrd.gz\n" -"</screen></informalexample> and reboot." -msgstr "" - -#. Tag: para -#: boot-installer.xml:914 -#, no-c-format -msgid "" -"Note that the value of the <userinput>ramdisk_size</userinput> may need to " -"be adjusted for the size of the initrd image. From here on, there should be " -"no difference between <command>GRUB</command> or <command>LILO</command>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:925 -#, no-c-format -msgid "Booting from USB Memory Stick" -msgstr "" - -#. Tag: para -#: boot-installer.xml:926 -#, no-c-format -msgid "" -"Let's assume you have prepared everything from <xref linkend=\"boot-dev-" -"select\"/> and <xref linkend=\"boot-usb-files\"/>. Now just plug your USB " -"stick into some free USB connector and reboot the computer. The system " -"should boot up, and you should be presented with the <prompt>boot:</prompt> " -"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." -msgstr "" - -#. Tag: para -#: boot-installer.xml:935 -#, no-c-format -msgid "" -"In case your computer doesn't support booting from USB memory devices, you " -"can still use a single floppy to do the initial boot and then switch to USB. " -"Boot your system as described in <xref linkend=\"floppy-boot\"/>; the kernel " -"on the boot floppy should detect your USB stick automatically. When it asks " -"for the root floppy, simply press &enterkey;. You should see &d-i; starting." -msgstr "" - -#. Tag: title -#: boot-installer.xml:948 boot-installer.xml:2056 boot-installer.xml:2550 -#: boot-installer.xml:2698 -#, no-c-format -msgid "Booting from Floppies" -msgstr "" - -#. Tag: para -#: boot-installer.xml:949 boot-installer.xml:2558 -#, no-c-format -msgid "" -"You will have already downloaded the floppy images you needed and created " -"floppies from the images in <xref linkend=\"create-floppy\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:956 -#, no-c-format -msgid "" -"To boot from the installer boot floppy, place it in the primary floppy " -"drive, shut down the system as you normally would, then turn it back on." -msgstr "" - -#. Tag: para -#: boot-installer.xml:962 -#, no-c-format -msgid "" -"For installing from an LS-120 drive (ATAPI version) with a set of floppies, " -"you need to specify the virtual location for the floppy device. This is done " -"with the <emphasis>root=</emphasis> boot argument, giving the device that " -"the ide-floppy driver maps the device to. For example, if your LS-120 drive " -"is connected as the first IDE device (master) on the second cable, you enter " -"<userinput>linux root=/dev/hdc</userinput> at the boot prompt. Installation " -"from LS-120 is only supported by 2.4 and later kernels." -msgstr "" - -#. Tag: para -#: boot-installer.xml:973 -#, no-c-format -msgid "" -"Note that on some machines, <keycombo><keycap>Control</keycap> <keycap>Alt</" -"keycap> <keycap>Delete</keycap></keycombo> does not properly reset the " -"machine, so a <quote>hard</quote> reboot is recommended. If you are " -"installing from an existing operating system (e.g., from a DOS box) you " -"don't have a choice. Otherwise, please do a hard reboot when booting." -msgstr "" - -#. Tag: para -#: boot-installer.xml:982 -#, no-c-format -msgid "" -"The floppy disk will be accessed, and you should then see a screen that " -"introduces the boot floppy and ends with the <prompt>boot:</prompt> prompt." -msgstr "" - -#. Tag: para -#: boot-installer.xml:988 -#, no-c-format -msgid "" -"Once you press &enterkey;, you should see the message " -"<computeroutput>Loading...</computeroutput>, followed by " -"<computeroutput>Uncompressing Linux...</computeroutput>, and then a " -"screenfull or so of information about the hardware in your system. More " -"information on this phase of the boot process can be found below in <xref " -"linkend=\"kernel-msgs\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:997 -#, no-c-format -msgid "" -"After booting from the boot floppy, the root floppy is requested. Insert the " -"root floppy and press &enterkey;, and the contents are loaded into memory. " -"The installer program <command>debian-installer</command> is automatically " -"launched." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1031 -#, no-c-format -msgid "There are various ways to do a TFTP boot on i386." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1037 -#, no-c-format -msgid "NIC or Motherboard that support PXE" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1038 -#, no-c-format -msgid "" -"It could be that your Network Interface Card or Motherboard provides PXE " -"boot functionality. This is a <trademark class=\"trade\">Intel</trademark> " -"re-implementation of TFTP boot. If so you may be able to configure your BIOS " -"to boot from the network." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1049 -#, no-c-format -msgid "NIC with Network BootROM" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1050 -#, no-c-format -msgid "" -"It could be that your Network Interface Card provides TFTP boot " -"functionality." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1055 -#, no-c-format -msgid "" -"Let us (<email>&email-debian-boot-list;</email>) know how did you manage it. " -"Please refer to this document." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1063 -#, no-c-format -msgid "Etherboot" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1064 -#, no-c-format -msgid "" -"The <ulink url=\"http://www.etherboot.org\">etherboot project</ulink> " -"provides bootdiskettes and even bootroms that do a TFTPboot." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1073 -#, no-c-format -msgid "The Boot Prompt" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1074 -#, no-c-format -msgid "" -"When the installer boots, you should be presented with a friendly graphical " -"screen showing the Debian logo and the boot prompt: " -"<informalexample><screen>\n" -"Press F1 for help, or ENTER to boot:\n" -"</screen></informalexample> At the boot prompt you can either just press " -"&enterkey; to boot the installer with default options or enter a specific " -"boot method and, optionally, boot parameters." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1086 -#, no-c-format -msgid "" -"Information on available boot methods and on boot parameters which might be " -"useful can be found by pressing <keycap>F2</keycap> through <keycap>F8</" -"keycap>. If you add any parameters to the boot command line, be sure to type " -"the boot method (the default is <userinput>linux</userinput>) and a space " -"before the first parameter (e.g., <userinput>linux debconf/priority=medium</" -"userinput>)." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1095 -#, no-c-format -msgid "" -"If you are installing the system via a remote management device that " -"provides a text interface to the VGA console, you may not be able to see the " -"initial graphical splash screen upon booting the installer; you may even not " -"see the boot prompt. Examples of these devices include the text console of " -"Compaq's <quote>integrated Lights Out</quote> (iLO) and HP's " -"<quote>Integrated Remote Assistant</quote> (IRA). You can blindly press " -"F1<footnote> <para> In some cases these devices will require special escape " -"sequences to enact this keypress, for example the IRA uses <keycombo> " -"<keycap>Ctrl</keycap> <keycap>F</keycap> </keycombo>, <keycap>1</" -"keycap>. </para> </footnote> to bypass this screen and view the help text. " -"Once you are past the splash screen and at the help text your keystrokes " -"will be echoed at the prompt as expected. To prevent the installer from " -"using the framebuffer for the rest of the installation, you will also want " -"to add <userinput>debian-installer/framebuffer=false</userinput> to the boot " -"prompt, as described in the help text." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1170 -#, no-c-format -msgid "CD Contents" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1172 -#, no-c-format -msgid "" -"There are three basic variations of Debian Install CDs. The " -"<emphasis>Business Card</emphasis> CD has a minimal installation that will " -"fit on the small form factor CD media. It requires a network connection in " -"order to install the rest of the base installation and make a usable system. " -"The <emphasis>Network Install</emphasis> CD has all of the packages for a " -"base install but requires a network connection to a Debian mirror site in " -"order to install the extra packages one would want for a complete system . " -"The set of Debian CDs can install a complete system from the wide range of " -"packages without needing access to the network." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1188 -#, no-c-format -msgid "" -"The IA-64 architecture uses the next generation Extensible Firmware " -"Interface (EFI) from Intel. Unlike the traditional x86 BIOS which knows " -"little about the boot device other than the partition table and Master Boot " -"Record (MBR), EFI can read and write files from FAT16 or FAT32 formatted " -"disk partitions. This simplifies the often arcane process of starting a " -"system. The system boot loader and the EFI firmware that supports it have a " -"full filesystem to store the files necessary for booting the machine. This " -"means that the system disk on an IA-64 system has an additional disk " -"partition dedicated to EFI instead of the simple MBR or boot block on more " -"conventional systems." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1204 -#, no-c-format -msgid "" -"The Debian Installer CD contains a small EFI partition where the " -"<command>ELILO</command> bootloader, its configuration file, the installer's " -"kernel, and initial filesystem (initrd) are located. The running system also " -"contains an EFI partition where the necessary files for booting the system " -"reside. These files are readable from the EFI Shell as described below." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1213 -#, no-c-format -msgid "" -"Most of the details of how <command>ELILO</command> actually loads and " -"starts a system are transparent to the system installer. However, the " -"installer must set up an EFI partition prior to installing the base system. " -"Otherwise, the installation of <command>ELILO</command> will fail, rendering " -"the system un-bootable. The EFI partition is allocated and formatted in the " -"partitioning step of the installation prior to loading any packages on the " -"system disk. The partitioning task also verifies that a suitable EFI " -"partition is present before allowing the installation to proceed." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1225 -#, no-c-format -msgid "" -"The EFI Boot Manager is presented as the last step of the firmware " -"initialization. It displays a menu list from which the user can select an " -"option. Depending on the model of system and what other software has been " -"loaded on the system, this menu may be different from one system to another. " -"There should be at least two menu items displayed, <command>Boot Option " -"Maintenance Menu</command> and <command>EFI Shell (Built-in)</command>. " -"Using the first option is preferred, however, if that option is not " -"available or the CD for some reason does not boot with it, use the second " -"option." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1244 -#, no-c-format -msgid "IMPORTANT" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1245 -#, no-c-format -msgid "" -"The EFI Boot Manager will select a default boot action, typically the first " -"menu choice, within a pre-set number of seconds. This is indicated by a " -"countdown at the bottom of the screen. Once the timer expires and the " -"systems starts the default action, you may have to reboot the machine in " -"order to continue the installation. If the default action is the EFI Shell, " -"you can return to the Boot Manager by running <command>exit</command> at the " -"shell prompt." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1257 -#, no-c-format -msgid "Option 1: Booting from the Boot Option Maintenance Menu" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1264 -#, no-c-format -msgid "" -"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " -"display the EFI Boot Manager page and menu after it completes its system " -"initialization." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1270 -#, no-c-format -msgid "" -"Select <command>Boot Maintenance Menu</command> from the menu with the arrow " -"keys and press <command>ENTER</command>. This will display a new menu." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1276 -#, no-c-format -msgid "" -"Select <command>Boot From a File</command> from the menu with the arrow keys " -"and press <command>ENTER</command>. This will display a list of devices " -"probed by the firmware. You should see two menu lines containing either the " -"label <command>Debian Inst [Acpi ...</command> or <command>Removable Media " -"Boot</command>. If you examine the rest of the menu line, you will notice " -"that the device and controller information should be the same." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1287 -#, no-c-format -msgid "" -"You can choose either of the entries that refer to the CD/DVD drive. Select " -"your choice with the arrow keys and press <command>ENTER</command>. If you " -"choose <command>Removable Media Boot</command> the machine will immediately " -"start the boot load sequence. If you choose <command>Debian Inst [Acpi ...</" -"command> instead, it will display a directory listing of the bootable " -"portion of the CD, requiring you to proceed to the next (additional) step." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1298 -#, no-c-format -msgid "" -"You will only need this step if you chose <command>Debian Inst [Acpi ...</" -"command>. The directory listing will also show <command>[Treat like " -"Removable Media Boot]</command> on the next to the last line. Select this " -"line with the arrow keys and press <command>ENTER</command>. This will start " -"the boot load sequence." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1310 -#, no-c-format -msgid "" -"These steps start the Debian boot loader which will display a menu page for " -"you to select a boot kernel and options. Proceed to selecting the boot " -"kernel and options." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1320 -#, no-c-format -msgid "Option 2: Booting from the EFI Shell" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1321 -#, no-c-format -msgid "" -"If, for some reason, option 1 is not successful, reboot the machine and when " -"the EFI Boot Manager screen appears there should be one option called " -"<command>EFI Shell [Built-in]</command>. Boot the Debian Installer CD with " -"the following steps:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1332 -#, no-c-format -msgid "" -"Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " -"display the EFI Boot Manager page and menu after it completes system " -"initialization." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1338 -#, no-c-format -msgid "" -"Select <command>EFI Shell</command> from the menu with the arrow keys and " -"press <command>ENTER</command>. The EFI Shell will scan all of the bootable " -"devices and display them to the console before displaying its command " -"prompt. The recognized bootable partitions on devices will show a device " -"name of <filename>fs<replaceable>n</replaceable>:</filename>. All other " -"recognized partitions will be named <filename>blk<replaceable>n</" -"replaceable>:</filename>. If you inserted the CD just before entering the " -"shell, this may take a few extra seconds as it initializes the CD drive." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1352 -#, no-c-format -msgid "" -"Examine the output from the shell looking for the CDROM drive. It is most " -"likely the <filename>fs0:</filename> device although other devices with " -"bootable partitions will also show up as <filename>fs<replaceable>n</" -"replaceable></filename>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1359 -#, no-c-format -msgid "" -"Enter <command>fs<replaceable>n</replaceable>:</command> and press " -"<command>ENTER</command> to select that device where <replaceable>n</" -"replaceable> is the partition number for the CDROM. The shell will now " -"display the partition number as its prompt." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1366 -#, no-c-format -msgid "" -"Enter <command>elilo</command> and press <command>ENTER</command>. This will " -"start the boot load sequence." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1373 -#, no-c-format -msgid "" -"As with option 1, these steps start the Debian boot loader which will " -"display a menu page for you to select a boot kernel and options. You can " -"also enter the shorter <command>fs<replaceable>n</replaceable>:elilo</" -"command> command at the shell prompt. Proceed to selecting the boot kernel " -"and options." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1387 -#, no-c-format -msgid "Installing using a Serial Console" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1389 -#, no-c-format -msgid "" -"You may choose to perform an install using a monitor and keyboard or using a " -"serial connection. To use a monitor/keyboard setup, select an option " -"containing the string [VGA console]. To install over a serial connection, " -"choose an option containing the string [<replaceable>BAUD</replaceable> baud " -"serial console], where <replaceable>BAUD</replaceable> is the speed of your " -"serial console. Menu items for the most typical baud rate settings on the " -"ttyS0 device are preconfigured." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1400 -#, no-c-format -msgid "" -"In most circumstances, you will want the installer to use the same baud rate " -"as your connection to the EFI console. If you aren't sure what this setting " -"is, you can obtain it using the command <command>baud</command> at the EFI " -"shell." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1407 -#, no-c-format -msgid "" -"If there is not an option available that is configured for the serial device " -"or baud rate you would like to use, you may override the console setting for " -"one of the existing menu options. For example, to use a 57600 baud console " -"over the ttyS1 device, enter <command>console=ttyS1,57600n8</command> into " -"the <classname>Boot:</classname> text window." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1418 -#, no-c-format -msgid "" -"Most IA-64 boxes ship with a default console setting of 9600 baud. This " -"setting is rather slow, and the normal installation process will take a " -"significant time to draw each screen. You should consider either increasing " -"the baud rate used for performing the installation, or performing a Text " -"Mode installation. See the <classname>Params</classname> help menu for " -"instructions on starting the installer in Text Mode." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1427 -#, no-c-format -msgid "" -"If you select the wrong console type, you will be able to select the kernel " -"and enter parameters but both the display and your input will go dead as " -"soon as the kernel starts, requiring you to reboot before you can begin the " -"installation." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1436 -#, no-c-format -msgid "Selecting the Boot Kernel and Options" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1438 -#, no-c-format -msgid "" -"The boot loader will display a form with a menu list and a text window with " -"a <classname>Boot:</classname> prompt. The arrow keys select an item from " -"the menu and any text typed at the keyboard will appear in the text window. " -"There are also help screens which can be displayed by pressing the " -"appropriate function key. The <classname>General</classname> help screen " -"explains the menu choices and the <classname>Params</classname> screen " -"explains the common command line options." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1450 -#, no-c-format -msgid "" -"Consult the <classname>General</classname> help screen for the description " -"of the kernels and install modes most appropriate for your installation. You " -"should also consult <xref linkend=\"boot-parms\"/> below for any additional " -"parameters that you may want to set in the <classname>Boot:</classname> text " -"window. The kernel version you choose selects the kernel version that will " -"be used for both the installation process and the installed system. If you " -"encounter kernel problems with the installation, you may also have those " -"same problems with the system you install. The following two steps will " -"select and start the install:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1468 -#, no-c-format -msgid "" -"Select the kernel version and installation mode most appropriate to your " -"needs with the arrow keys." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1473 -#, no-c-format -msgid "" -"Enter any boot parameters by typing at the keyboard. The text will be " -"displayed directly in the text window. This is where kernel parameters (such " -"as serial console settings) are specified." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1480 -#, no-c-format -msgid "" -"Press <command>ENTER</command>. This will load and start the kernel. The " -"kernel will display its usual initialization messages followed by the first " -"screen of the Debian Installer." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1489 -#, no-c-format -msgid "" -"Proceed to the next chapter to continue the installation where you will set " -"up the language locale, network, and disk partitions." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1500 -#, no-c-format -msgid "" -"Booting an IA64 system from the network is similar to a CD boot. The only " -"difference is how the installation kernel is loaded. The EFI Boot Manager " -"can load and start programs from a server on the network. Once the " -"installation kernel is loaded and starts, the system install will proceed " -"thru the same steps as the CD install with the exception that the packages " -"of the base install will be loaded from the network rather than the CD drive." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1534 -#, no-c-format -msgid "" -"Network booting an ia64 system requires two architecture-specific actions. " -"On the boot server, DHCP and TFTP must be configured to deliver " -"<command>elilo</command>. On the client a new boot option must be defined in " -"the EFI boot manager to enable loading over a network." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1545 -#, no-c-format -msgid "Configuring the Server" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1546 -#, no-c-format -msgid "" -"A suitable TFTP entry for network booting an ia64 system looks something " -"like this: <informalexample><screen>\n" -"host mcmuffin {\n" -" hardware ethernet 00:30:6e:1e:0e:83;\n" -" fixed-address 10.0.0.21;\n" -" filename \"debian-installer/ia64/elilo.efi\";\n" -"}\n" -"</screen></informalexample> Note that the goal is to get <command>elilo.efi</" -"command> running on the client." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1556 -#, no-c-format -msgid "" -"Extract the <filename>netboot.tar.gz</filename> file into the directory used " -"as the root for your tftp server. Typical tftp root directories include " -"<filename>/var/lib/tftp</filename> and <filename>/tftpboot</filename>. This " -"will create a <filename>debian-installer</filename> directory tree " -"containing the boot files for an IA-64 system." -msgstr "" - -#. Tag: screen -#: boot-installer.xml:1566 -#, no-c-format -msgid "" -"# cd /var/lib/tftp\n" -"# tar xvfz /home/user/netboot.tar.gz\n" -"./\n" -"./debian-installer/\n" -"./debian-installer/ia64/\n" -"[...]" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1566 -#, no-c-format -msgid "" -"The <filename>netboot.tar.gz</filename> contains an <filename>elilo.conf</" -"filename> file that should work for most configurations. However, should you " -"need to make changes to this file, you can find it in the <filename>debian-" -"installer/ia64/</filename> directory. It is possible to have different " -"config files for different clients by naming them using the client's IP " -"address in hex with the suffix <filename>.conf</filename> instead of " -"<filename>elilo.conf</filename>. See documentation provided in the " -"<classname>elilo</classname> package for details." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1583 -#, no-c-format -msgid "Configuring the Client" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1584 -#, no-c-format -msgid "" -"To configure the client to support TFTP booting, start by booting to EFI and " -"entering the <guimenu>Boot Option Maintenance Menu</guimenu>. <itemizedlist> " -"<listitem><para> Add a boot option. </para></listitem> <listitem><para> You " -"should see one or more lines with the text <guimenuitem>Load File [Acpi" -"()/.../Mac()]</guimenuitem>. If more than one of these entries exist, choose " -"the one containing the MAC address of the interface from which you'll be " -"booting. Use the arrow keys to highlight your choice, then press enter. </" -"para></listitem> <listitem><para> Name the entry <userinput>Netboot</" -"userinput> or something similar, save, and exit back to the boot options " -"menu. </para></listitem> </itemizedlist> You should see the new boot option " -"you just created, and selecting it should initiate a DHCP query, leading to " -"a TFTP load of <filename>elilo.efi</filename> from the server." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1616 -#, no-c-format -msgid "" -"The boot loader will display its prompt after it has downloaded and " -"processed its configuration file. At this point, the installation proceeds " -"with the same steps as a CD install. Select a boot option as in above and " -"when the kernel has completed installing itself from the network, it will " -"start the Debian Installer." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1625 -#, no-c-format -msgid "" -"Proceed to the next chapter to continue the installation where you will set " -"up the language locale, network, and the disk partitions." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1638 -#, no-c-format -msgid "Choosing an Installation Method" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1640 -#, no-c-format -msgid "" -"Some &arch-title; subarchs have the option of booting using either a 2.4.x " -"or 2.2.x linux kernel. When such a choice exists, try the 2.4.x linux " -"kernel. The installer should also require less memory when using a 2.4.x " -"linux kernel as 2.2.x support requires a fixed-sized ramdisk and 2.4.x uses " -"tmpfs." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1648 -#, no-c-format -msgid "" -"If you are using a 2.2.x linux kernel, then you need to use the " -"&ramdisksize; kernel parameter." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1653 -#, no-c-format -msgid "" -"Make sure <userinput>root=/dev/ram</userinput> is one of your kernel " -"parameters." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1658 -#, no-c-format -msgid "" -"If you're having trouble, check <ulink url=\"&url-m68k-cts-faq;\">cts's " -"&arch-title; debian-installer FAQ</ulink>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1675 -#, no-c-format -msgid "Amiga" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1676 -#, no-c-format -msgid "" -"The only method of installation available to amiga is the hard drive (see " -"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not " -"bootable.</emphasis>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1682 -#, no-c-format -msgid "" -"Amiga does not currently work with bogl, so if you are seeing bogl errors, " -"you need to include the kernel parameter <userinput>debian-installer/" -"framebuffer=false</userinput>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1691 -#, no-c-format -msgid "Atari" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1692 -#, no-c-format -msgid "" -"The installer for atari may be started from either the hard drive (see <xref " -"linkend=\"m68k-boot-hd\"/>) or from floppies (see <xref linkend=\"boot-from-" -"floppies\"/>). <emphasis>In other words the cdrom is not bootable.</emphasis>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1699 -#, no-c-format -msgid "" -"Atari does not currently work with bogl, so if you are seeing bogl errors, " -"you need to include the kernel parameter <userinput>debian-installer/" -"framebuffer=false</userinput>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1708 -#, no-c-format -msgid "BVME6000" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1709 -#, no-c-format -msgid "" -"The installer for BVME6000 may be started from a cdrom (see <xref linkend=" -"\"m68k-boot-cdrom\"/>), floppies (see <xref linkend=\"boot-from-floppies\"/" -">), or the net (see <xref linkend=\"boot-tftp\"/>)." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1719 -#, no-c-format -msgid "Macintosh" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1720 -#, no-c-format -msgid "" -"The only method of installation available to mac is from the hard drive (see " -"<xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom is not " -"bootable.</emphasis> Macs do not have a working 2.4.x kernel." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1727 -#, no-c-format -msgid "" -"If your hardware uses a 53c9x-based scsi bus, then you may need to include " -"the kernel parameter <userinput>mac53c9x=1,0</userinput>. Hardware with two " -"such scsi buses, such as the Quadra 950, will need <userinput>mac53c9x=2,0</" -"userinput> instead. Alternatively, the parameter can be specified as " -"<userinput>mac53c9x=-1,0</userinput> which will leave autodetection on, but " -"which will disable SCSI disconnects. Note that specifying this parameter is " -"only necessary if you have more than one hard disk; otherwise, the system " -"will run faster if you do not specify it." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1742 -#, no-c-format -msgid "MVME147 and MVME16x" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1743 -#, no-c-format -msgid "" -"The installer for MVME147 and MVME16x may be started from either floppies " -"(see <xref linkend=\"boot-from-floppies\"/>) or the net (see <xref linkend=" -"\"boot-tftp\"/>). <emphasis>In other words the cdrom is not bootable.</" -"emphasis>" -msgstr "" - -#. Tag: title -#: boot-installer.xml:1753 -#, no-c-format -msgid "Q40/Q60" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1754 -#, no-c-format -msgid "" -"The only method of installation available to Q40/Q60 is from the hard drive " -"(see <xref linkend=\"m68k-boot-hd\"/>). <emphasis>In other words the cdrom " -"is not bootable.</emphasis>" -msgstr "" - -#. Tag: title -#: boot-installer.xml:1765 -#, no-c-format -msgid "Booting from a Hard Disk" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1771 boot-installer.xml:2369 -#, no-c-format -msgid "" -"Booting from an existing operating system is often a convenient option; for " -"some systems it is the only supported method of installation." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1777 boot-installer.xml:2375 -#, no-c-format -msgid "" -"To boot the installer from hard disk, you will have already completed " -"downloading and placing the needed files in <xref linkend=\"boot-drive-files" -"\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1786 -#, no-c-format -msgid "" -"At least six different ramdisks may be used to boot from the hard drive, " -"three different types each with and without support for a 2.2.x linux kernel " -"(see <ulink url=\"&disturl;/main/installer-&architecture;/current/images/" -"MANIFEST\">MANIFEST</ulink> for details)." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1794 -#, no-c-format -msgid "" -"The three different types of ramdisks are <filename>cdrom</filename>, " -"<filename>hd-media</filename>, and <filename>nativehd</filename>. These " -"ramdisks differ only in their source for installation packages. The " -"<filename>cdrom</filename> ramdisk uses a cdrom to get debian-installer " -"packages. The <filename>hd-media</filename> ramdisk uses an iso image file " -"of a cdrom currently residing on a hard disk. Finally, the " -"<filename>nativehd</filename> ramdisk uses the net to install packages." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1815 -#, no-c-format -msgid "Booting from AmigaOS" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1816 -#, no-c-format -msgid "" -"In the <command>Workbench</command>, start the Linux installation process by " -"double-clicking on the <guiicon>StartInstall</guiicon> icon in the " -"<filename>debian</filename> directory." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1822 -#, no-c-format -msgid "" -"You may have to press the &enterkey; key twice after the Amiga installer " -"program has output some debugging information into a window. After this, the " -"screen will go grey, there will be a few seconds' delay. Next, a black " -"screen with white text should come up, displaying all kinds of kernel " -"debugging information. These messages may scroll by too fast for you to " -"read, but that's OK. After a couple of seconds, the installation program " -"should start automatically, so you can continue down at <xref linkend=\"d-i-" -"intro\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1837 -#, no-c-format -msgid "Booting from Atari TOS" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1838 -#, no-c-format -msgid "" -"At the GEM desktop, start the Linux installation process by double-clicking " -"on the <guiicon>bootstra.prg</guiicon> icon in the <filename>debian</" -"filename> directory and clicking <guibutton>Ok</guibutton> at the program " -"options dialog box." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1845 -#, no-c-format -msgid "" -"You may have to press the &enterkey; key after the Atari bootstrap program " -"has output some debugging information into a window. After this, the screen " -"will go grey, there will be a few seconds' delay. Next, a black screen with " -"white text should come up, displaying all kinds of kernel debugging " -"information. These messages may scroll by too fast for you to read, but " -"that's OK. After a couple of seconds, the installation program should start " -"automatically, so you can continue below at <xref linkend=\"d-i-intro\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1860 -#, no-c-format -msgid "Booting from MacOS" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1861 -#, no-c-format -msgid "" -"You must retain the original Mac system and boot from it. It is " -"<emphasis>essential</emphasis> that, when booting MacOS in preparation for " -"booting the Penguin linux loader, you hold the <keycap>shift</keycap> key " -"down to prevent extensions from loading. If you don't use MacOS except for " -"loading linux, you can accomplish the same thing by removing all extensions " -"and control panels from the Mac's System Folder. Otherwise extensions may be " -"left running and cause random problems with the running linux kernel." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1872 -#, no-c-format -msgid "" -"Macs require the <command>Penguin</command> bootloader. If you do not have " -"the tools to handle a <command>Stuffit</command> archive, &penguin19.hfs; is " -"an hfs disk image with <command>Penguin</command> unpacked. <xref linkend=" -"\"create-floppy\"/> describes how to copy this image to a floppy." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1881 -#, no-c-format -msgid "" -"At the MacOS desktop, start the Linux installation process by double-" -"clicking on the <guiicon>Penguin Prefs</guiicon> icon in the " -"<filename>Penguin</filename> directory. The <command>Penguin</command> " -"booter will start up. Go to the <guimenuitem>Settings</guimenuitem> item in " -"the <guimenu>File</guimenu> menu, click the <guilabel>Kernel</guilabel> tab. " -"Select the kernel (<filename>vmlinuz</filename>) and ramdisk " -"(<filename>initrd.gz</filename>) images in the <filename>install</filename> " -"directory by clicking on the corresponding buttons in the upper right " -"corner, and navigating the file select dialogs to locate the files." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1896 -#, no-c-format -msgid "" -"To set the boot parameters in Penguin, choose <guimenu>File</guimenu> -> " -"<guimenuitem>Settings...</guimenuitem>, then switch to the " -"<guilabel>Options</guilabel> tab. Boot parameters may be typed in to the " -"text entry area. If you will always want to use these settings, select " -"<guimenu>File</guimenu> -> <guimenuitem>Save Settings as Default</" -"guimenuitem>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1905 -#, no-c-format -msgid "" -"Close the <guilabel>Settings</guilabel> dialog, save the settings and start " -"the bootstrap using the <guimenuitem>Boot Now</guimenuitem> item in the " -"<guimenu>File</guimenu> menu." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1912 -#, no-c-format -msgid "" -"The <command>Penguin</command> booter will output some debugging information " -"into a window. After this, the screen will go grey, there will be a few " -"seconds' delay. Next, a black screen with white text should come up, " -"displaying all kinds of kernel debugging information. These messages may " -"scroll by too fast for you to read, but that's OK. After a couple of " -"seconds, the installation program should start automatically, so you can " -"continue below at <xref linkend=\"d-i-intro\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:1927 -#, no-c-format -msgid "Booting from Q40/Q60" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1929 -#, no-c-format -msgid "FIXME" -msgstr "" - -#. Tag: para -#: boot-installer.xml:1933 -#, no-c-format -msgid "" -"The installation program should start automatically, so you can continue " -"below at <xref linkend=\"d-i-intro\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:1945 -#, no-c-format -msgid "" -"Currently, the only &arch-title; subarchitecture that supports CD-ROM " -"booting is the BVME6000." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2017 -#, no-c-format -msgid "" -"After booting the VMEbus systems you will be presented with the LILO " -"<prompt>Boot:</prompt> prompt. At that prompt enter one of the following to " -"boot Linux and begin installation proper of the Debian software using vt102 " -"terminal emulation:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2028 -#, no-c-format -msgid "type <screen>i6000 &enterkey;</screen> to install a BVME4000/6000" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2033 -#, no-c-format -msgid "type <screen>i162 &enterkey;</screen> to install an MVME162" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2038 -#, no-c-format -msgid "type <screen>i167 &enterkey;</screen> to install an MVME166/167" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2045 -#, no-c-format -msgid "" -"You may additionally append the string <screen>TERM=vt100</screen> to use " -"vt100 terminal emulation, e.g., <screen>i6000 TERM=vt100 &enterkey;</screen>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2057 -#, no-c-format -msgid "" -"For most &arch-title; architectures, booting from a local filesystem is the " -"recommended method." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2062 -#, no-c-format -msgid "" -"Booting from the boot floppy is supported only for Atari and VME (with a " -"SCSI floppy drive on VME) at this time." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2078 boot-installer.xml:2125 -#, no-c-format -msgid "SGI TFTP Booting" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2079 -#, no-c-format -msgid "" -"After entering the command monitor use <informalexample><screen>\n" -"bootp():\n" -"</screen></informalexample> on SGI machines to boot linux and to begin " -"installation of the Debian Software. In order to make this work you may have " -"to unset the <envar>netaddr</envar> environment variable. Type " -"<informalexample><screen>\n" -"unsetenv netaddr\n" -"</screen></informalexample> in the command monitor to do this." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2098 boot-installer.xml:2147 boot-installer.xml:2202 -#: boot-installer.xml:2241 -#, no-c-format -msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2099 boot-installer.xml:2203 -#, no-c-format -msgid "" -"On the Broadcom BCM91250A and BCM91480B evaluation boards, you have to load " -"the SiByl boot loader via TFTP which will then load and start the Debian " -"installer. In most cases, you will first obtain an IP address via DHCP but " -"it is also possible to configure a static address. In order to use DHCP, you " -"can enter the following command on the CFE prompt: " -"<informalexample><screen>\n" -"ifconfig eth0 -auto\n" -"</screen></informalexample> Once you have obtained an IP address, you can " -"load SiByl with the following command: <informalexample><screen>\n" -"boot 192.168.1.1:/boot/sibyl\n" -"</screen></informalexample> You need to substitute the IP address listed in " -"this example with either the name or the IP address of your TFTP server. " -"Once you issue this command, the installer will be loaded automatically." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2122 boot-installer.xml:2226 boot-installer.xml:2749 -#, no-c-format -msgid "Boot Parameters" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2126 -#, no-c-format -msgid "" -"On SGI machines you can append boot parameters to the <command>bootp():</" -"command> command in the command monitor." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2131 -#, no-c-format -msgid "" -"Following the <command>bootp():</command> command you can give the path and " -"name of the file to boot if you did not give an explicit name via your bootp/" -"dhcp server. Example: <informalexample><screen>\n" -"bootp():/boot/tftpboot.img\n" -"</screen></informalexample> Further kernel parameters can be passed via " -"<command>append</command>:" -msgstr "" - -#. Tag: screen -#: boot-installer.xml:2141 -#, no-c-format -msgid "bootp(): append=\"root=/dev/sda1\"" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2148 boot-installer.xml:2242 -#, no-c-format -msgid "" -"You cannot pass any boot parameters directly from the CFE prompt. Instead, " -"you have to edit the <filename>/boot/sibyl.conf</filename> file on the TFTP " -"server and add your parameters to the <replaceable>extra_args</replaceable> " -"variable." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2167 boot-installer.xml:2229 -#, no-c-format -msgid "Cobalt TFTP Booting" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2168 -#, no-c-format -msgid "" -"Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to " -"install an NFS server and put the installer files in <filename>/nfsroot</" -"filename>. When you boot your Cobalt, you have to press the left and the " -"right cursor buttons at the same time and the machine will boot via the " -"network from NFS. It will then display several options on the display. There " -"are the following two installation methods:" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2178 -#, no-c-format -msgid "" -"Via SSH (default): In this case, the installer will configure the network " -"via DHCP and start an SSH server. It will then display a random password and " -"other login information (such as the IP address) on the Cobalt LCD. When you " -"connect to the machine with an SSH client you can start with the " -"installation." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2187 -#, no-c-format -msgid "" -"Via serial console: Using a null modem cable, you can connect to the serial " -"port of your Cobalt machine (using 115200 bps) and perform the installation " -"this way. This option is not available on Qube 2700 (Qube1) machines since " -"they have no serial port." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2230 -#, no-c-format -msgid "" -"You cannot pass any boot parameters directly. Instead, you have to edit the " -"<filename>/nfsroot/default.colo</filename> file on the NFS server and add " -"your parameters to the <replaceable>args</replaceable> variable." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2258 -#, no-c-format -msgid "s390 Limitations" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2259 -#, no-c-format -msgid "" -"In order to run the installation system a working network setup and ssh " -"session is needed on S/390." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2264 -#, no-c-format -msgid "" -"The booting process starts with a network setup that prompts you for several " -"network parameters. If the setup is successful, you will login to the system " -"by starting a ssh session which will launch the standard installation system." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2275 -#, no-c-format -msgid "s390 Boot Parameters" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2276 -#, no-c-format -msgid "" -"On S/390 you can append boot parameters in the parm file. This file can " -"either be in ASCII or EBCDIC format. Please read <ulink url=\"&url-s390-" -"devices;\">Device Drivers and Installation Commands</ulink> for more " -"information about S/390-specific boot parameters." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2330 -#, no-c-format -msgid "" -"Currently, the only &arch-title; subarchitectures that support CD-ROM " -"booting are PReP and New World PowerMacs. On PowerMacs, hold the <keycap>c</" -"keycap> key, or else the combination of <keycap>Command</keycap>, " -"<keycap>Option</keycap>, <keycap>Shift</keycap>, and <keycap>Delete</keycap> " -"keys together while booting to boot from the CD-ROM." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2339 -#, no-c-format -msgid "" -"OldWorld PowerMacs will not boot a Debian CD, because OldWorld computers " -"relied on a Mac OS ROM CD boot driver to be present on the CD, and a free-" -"software version of this driver is not available. All OldWorld systems have " -"floppy drives, so use the floppy drive to launch the installer, and then " -"point the installer to the CD for the needed files." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2348 -#, no-c-format -msgid "" -"If your system doesn't boot directly from CD-ROM, you can still use the CD-" -"ROM to install the system. On NewWorlds, you can also use an OpenFirmware " -"command to boot from the CD-ROM manually. Follow the instructions in <xref " -"linkend=\"boot-newworld\"/> for booting from the hard disk, except use the " -"path to <command>yaboot</command> on the CD at the OF prompt, such as" -msgstr "" - -#. Tag: screen -#: boot-installer.xml:2357 -#, no-c-format -msgid "0 > boot cd:,\\install\\yaboot" -msgstr "" - -#. Tag: title -#: boot-installer.xml:2363 -#, no-c-format -msgid "Booting from Hard Disk" -msgstr "" - -#. Tag: title -#: boot-installer.xml:2384 -#, no-c-format -msgid "Booting CHRP from OpenFirmware" -msgstr "" - -#. Tag: emphasis -#: boot-installer.xml:2388 -#, no-c-format -msgid "Not yet written." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2393 -#, no-c-format -msgid "Booting OldWorld PowerMacs from MacOS" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2394 -#, no-c-format -msgid "" -"If you set up BootX in <xref linkend=\"files-oldworld\"/>, you can use it to " -"boot into the installation system. Double click the <guiicon>BootX</guiicon> " -"application icon. Click on the <guibutton>Options</guibutton> button and " -"select <guilabel>Use Specified RAM Disk</guilabel>. This will give you the " -"chance to select the <filename>ramdisk.image.gz</filename> file. You may " -"need to select the <guilabel>No Video Driver</guilabel> checkbox, depending " -"on your hardware. Then click the <guibutton>Linux</guibutton> button to shut " -"down MacOS and launch the installer." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2412 -#, no-c-format -msgid "Booting NewWorld Macs from OpenFirmware" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2413 -#, no-c-format -msgid "" -"You will have already placed the <filename>vmlinux</filename>, " -"<filename>initrd.gz</filename>, <filename>yaboot</filename>, and " -"<filename>yaboot.conf</filename> files at the root level of your HFS " -"partition in <xref linkend=\"files-newworld\"/>. Restart the computer, and " -"immediately (during the chime) hold down the <keycap>Option</keycap>, " -"<keycap>Command (cloverleaf/Apple)</keycap>, <keycap>o</keycap>, and " -"<keycap>f</keycap> keys all together. After a few seconds you will be " -"presented with the Open Firmware prompt. At the prompt, type " -"<informalexample><screen>\n" -"0 > boot hd:<replaceable>x</replaceable>,yaboot\n" -"</screen></informalexample> replacing <replaceable>x</replaceable> with the " -"partition number of the HFS partition where the kernel and yaboot files were " -"placed, followed by a &enterkey;. On some machines, you may need to use " -"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>. In a few " -"more seconds you will see a yaboot prompt <informalexample><screen>\n" -"boot:\n" -"</screen></informalexample> At yaboot's <prompt>boot:</prompt> prompt, type " -"either <userinput>install</userinput> or <userinput>install video=ofonly</" -"userinput> followed by a &enterkey;. The <userinput>video=ofonly</userinput> " -"argument is for maximum compatibility; you can try it if <userinput>install</" -"userinput> doesn't work. The Debian installation program should start." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2448 -#, no-c-format -msgid "Booting from USB memory stick" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2449 -#, no-c-format -msgid "Currently, NewWorld PowerMac systems are known to support USB booting." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2455 -#, no-c-format -msgid "" -"Make sure you have prepared everything from <xref linkend=\"boot-usb-files\"/" -">. To boot a Macintosh system from a USB stick, you will need to use the " -"Open Firmware prompt, since Open Firmware does not search USB storage " -"devices by default. To get to the prompt, hold down " -"<keycombo><keycap>Command</keycap> <keycap>Option</keycap> <keycap>o</" -"keycap> <keycap>f</keycap></keycombo> all together while booting (see <xref " -"linkend=\"invoking-openfirmware\"/>)." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2467 -#, no-c-format -msgid "" -"You will need to work out where the USB storage device appears in the device " -"tree, since at the moment <command>ofpath</command> cannot work that out " -"automatically. Type <userinput>dev / ls</userinput> and <userinput>devalias</" -"userinput> at the Open Firmware prompt to get a list of all known devices " -"and device aliases. On the author's system with various types of USB stick, " -"paths such as <filename>usb0/disk</filename>, <filename>usb0/hub/disk</" -"filename>, <filename>/pci@f2000000/usb@1b,1/disk@1</filename>, and " -"<filename>/pci@f2000000/usb@1b,1/hub@1/disk@1</filename> work." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2479 -#, no-c-format -msgid "" -"Having worked out the device path, use a command like this to boot the " -"installer: <informalexample><screen>\n" -"boot <replaceable>usb0/disk</replaceable>:<replaceable>2</replaceable>,\\\\:" -"tbxi\n" -"</screen></informalexample> The <replaceable>2</replaceable> matches the " -"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " -"earlier, and the <userinput>,\\\\:tbxi</userinput> part instructs Open " -"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " -"<command>yaboot</command>) in the directory previously blessed with " -"<command>hattrib -b</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2493 -#, no-c-format -msgid "" -"The system should now boot up, and you should be presented with the " -"<prompt>boot:</prompt> prompt. Here you can enter optional boot arguments, " -"or just hit &enterkey;." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2499 -#, no-c-format -msgid "" -"This boot method is new, and may be difficult to get to work on some " -"NewWorld systems. If you have problems, please file an installation report, " -"as explained in <xref linkend=\"submit-bug\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2532 -#, no-c-format -msgid "Currently, PReP and New World PowerMac systems support netbooting." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2536 -#, no-c-format -msgid "" -"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " -"monitor (see <xref linkend=\"invoking-openfirmware\"/>) and use the command " -"<command>boot enet:0</command>. PReP and CHRP boxes may have different ways " -"of addressing the network. On a PReP machine, you should try <userinput>boot " -"<replaceable>server_ipaddr</replaceable>,<replaceable>file</replaceable>," -"<replaceable>client_ipaddr</replaceable></userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2551 -#, no-c-format -msgid "" -"Booting from floppies is supported for &arch-title;, although it is " -"generally only applicable for OldWorld systems. NewWorld systems are not " -"equipped with floppy drives, and attached USB floppy drives are not " -"supported for booting." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2563 -#, no-c-format -msgid "" -"To boot from the <filename>boot-floppy-hfs.img</filename> floppy, place it " -"in floppy drive after shutting the system down, and before pressing the " -"power-on button." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2569 -#, no-c-format -msgid "" -"For those not familiar with Macintosh floppy operations: a floppy placed in " -"the machine prior to boot will be the first priority for the system to boot " -"from. A floppy without a valid boot system will be ejected, and the machine " -"will then check for bootable hard disk partitions." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2576 -#, no-c-format -msgid "" -"After booting, the <filename>root.bin</filename> floppy is requested. Insert " -"the root floppy and press &enterkey;. The installer program is automatically " -"launched after the root system has been loaded into memory." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2587 -#, no-c-format -msgid "PowerPC Boot Parameters" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2588 -#, no-c-format -msgid "" -"Many older Apple monitors used a 640x480 67Hz mode. If your video appears " -"skewed on an older Apple monitor, try appending the boot argument " -"<userinput>video=atyfb:vmode:6</userinput> , which will select that mode for " -"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " -"<userinput>video=aty128fb:vmode:6</userinput> ." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2628 -#, no-c-format -msgid "" -"On machines with OpenBoot, simply enter the boot monitor on the machine " -"which is being installed (see <xref linkend=\"invoking-openboot\"/>). Use " -"the command <userinput>boot net</userinput> to boot from a TFTP and RARP " -"server, or try <userinput>boot net:bootp</userinput> or <userinput>boot net:" -"dhcp</userinput> to boot from a TFTP and BOOTP or DHCP server. Some older " -"OpenBoot revisions require using the device name, such as <userinput>boot le" -"()</userinput>; these probably don't support BOOTP nor DHCP." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2684 -#, no-c-format -msgid "" -"Most OpenBoot versions support the <userinput>boot cdrom</userinput> command " -"which is simply an alias to boot from the SCSI device on ID 6 (or the " -"secondary master for IDE based systems). You may have to use the actual " -"device name for older OpenBoot versions that don't support this special " -"command. Note that some problems have been reported on Sun4m (e.g., Sparc " -"10s and Sparc 20s) systems booting from CD-ROM." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2699 -#, no-c-format -msgid "" -"To boot from floppy on a Sparc, use <informalexample><screen>\n" -"Stop-A -> OpenBoot: \"boot floppy\"\n" -"</screen></informalexample> Be warned that the newer Sun4u (ultra) " -"architecture does not support floppy booting. A typical error message is " -"<computeroutput>Bad magic number in disk label - Can't open disk label " -"package</computeroutput>. Furthermore, a number of Sun4c models (such as the " -"IPX) do not support the compressed images found on the disks, so also are " -"not supported." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2711 -#, no-c-format -msgid "" -"Several Sparcs (e.g. Ultra 10) have an OBP bug that prevents them from " -"booting (instead of not supporting booting at all). The appropriate OBP " -"update can be downloaded as product ID 106121 from <ulink url=\"http://" -"sunsolve.sun.com\"></ulink>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2718 -#, no-c-format -msgid "" -"If you are booting from the floppy, and you see messages such as " -"<informalexample><screen>\n" -"Fatal error: Cannot read partition\n" -"Illegal or malformed device name\n" -"</screen></informalexample> then it is possible that floppy booting is " -"simply not supported on your machine." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2730 -#, no-c-format -msgid "IDPROM Messages" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2731 -#, no-c-format -msgid "" -"If you cannot boot because you get messages about a problem with " -"<quote>IDPROM</quote>, then it's possible that your NVRAM battery, which " -"holds configuration information for you firmware, has run out. See the " -"<ulink url=\"&url-sun-nvram-faq;\">Sun NVRAM FAQ</ulink> for more " -"information." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2750 -#, no-c-format -msgid "" -"Boot parameters are Linux kernel parameters which are generally used to make " -"sure that peripherals are dealt with properly. For the most part, the kernel " -"can auto-detect information about your peripherals. However, in some cases " -"you'll have to help the kernel a bit." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2757 -#, no-c-format -msgid "" -"If this is the first time you're booting the system, try the default boot " -"parameters (i.e., don't try setting parameters) and see if it works " -"correctly. It probably will. If not, you can reboot later and look for any " -"special parameters that inform the system about your hardware." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2764 -#, no-c-format -msgid "" -"Information on many boot parameters can be found in the <ulink url=\"http://" -"www.tldp.org/HOWTO/BootPrompt-HOWTO.html\"> Linux BootPrompt HOWTO</ulink>, " -"including tips for obscure hardware. This section contains only a sketch of " -"the most salient parameters. Some common gotchas are included below in <xref " -"linkend=\"boot-troubleshooting\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2773 -#, no-c-format -msgid "" -"When the kernel boots, a message <informalexample><screen>\n" -"Memory:<replaceable>avail</replaceable>k/<replaceable>total</replaceable>k " -"available\n" -"</screen></informalexample> should be emitted early in the process. " -"<replaceable>total</replaceable> should match the total amount of RAM, in " -"kilobytes. If this doesn't match the actual amount of RAM you have " -"installed, you need to use the <userinput>mem=<replaceable>ram</" -"replaceable></userinput> parameter, where <replaceable>ram</replaceable> is " -"set to the amount of memory, suffixed with <quote>k</quote> for kilobytes, " -"or <quote>m</quote> for megabytes. For example, both <userinput>mem=65536k</" -"userinput> and <userinput>mem=64m</userinput> mean 64MB of RAM." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2789 -#, no-c-format -msgid "" -"If you are booting with a serial console, generally the kernel will " -"autodetect this<phrase arch=\"mipsel\"> (although not on DECstations)</" -"phrase>. If you have a videocard (framebuffer) and a keyboard also attached " -"to the computer which you wish to boot via serial console, you may have to " -"pass the <userinput>console=<replaceable>device</replaceable></userinput> " -"argument to the kernel, where <replaceable>device</replaceable> is your " -"serial device, which is usually something like <filename>ttyS0</filename>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2802 -#, no-c-format -msgid "" -"For &arch-title; the serial devices are <filename>ttya</filename> or " -"<filename>ttyb</filename>. Alternatively, set the <envar>input-device</" -"envar> and <envar>output-device</envar> OpenPROM variables to " -"<filename>ttya</filename>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:2813 -#, no-c-format -msgid "Debian Installer Parameters" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2814 -#, no-c-format -msgid "" -"The installation system recognizes a few additional boot " -"parameters<footnote> <para> Note that the kernel accepts a maximum of 8 " -"command line options and 8 environment options (including any options added " -"by default for the installer). If these numbers are exceeded, 2.4 kernels " -"will drop any excess options and 2.6 kernels will panic. With kernel 2.6.9 " -"or newer, you can use 32 command line options and 32 environment options. </" -"para> </footnote> which may be useful." -msgstr "" - -#. Tag: term -#: boot-installer.xml:2834 -#, no-c-format -msgid "debconf/priority" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2835 -#, no-c-format -msgid "This parameter sets the lowest priority of messages to be displayed." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2839 -#, no-c-format -msgid "" -"The default installation uses <userinput>debconf/priority=high</userinput>. " -"This means that both high and critical priority messages are shown, but " -"medium and low priority messages are skipped. If problems are encountered, " -"the installer adjusts the priority as needed." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2846 -#, no-c-format -msgid "" -"If you add <userinput>debconf/priority=medium</userinput> as boot parameter, " -"you will be shown the installation menu and gain more control over the " -"installation. When <userinput>debconf/priority=low</userinput> is used, all " -"messages are shown (this is equivalent to the <emphasis>expert</emphasis> " -"boot method). With <userinput>debconf/priority=critical</userinput>, the " -"installation system will display only critical messages and try to do the " -"right thing without fuss." -msgstr "" - -#. Tag: term -#: boot-installer.xml:2860 -#, no-c-format -msgid "DEBIAN_FRONTEND" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2861 -#, no-c-format -msgid "" -"This boot parameter controls the type of user interface used for the " -"installer. The current possible parameter settings are: <itemizedlist> " -"<listitem> <para><userinput>DEBIAN_FRONTEND=noninteractive</userinput></" -"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=text</" -"userinput></para> </listitem><listitem> " -"<para><userinput>DEBIAN_FRONTEND=newt</userinput></para> </" -"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=slang</userinput></" -"para> </listitem><listitem> <para><userinput>DEBIAN_FRONTEND=ncurses</" -"userinput></para> </listitem><listitem> " -"<para><userinput>DEBIAN_FRONTEND=bogl</userinput></para> </" -"listitem><listitem> <para><userinput>DEBIAN_FRONTEND=gtk</userinput></para> " -"</listitem><listitem> <para><userinput>DEBIAN_FRONTEND=corba</userinput></" -"para> </listitem> </itemizedlist> The default front end is " -"<userinput>DEBIAN_FRONTEND=newt</userinput>. " -"<userinput>DEBIAN_FRONTEND=text</userinput> may be preferable for serial " -"console installs. Generally only the <userinput>newt</userinput> frontend is " -"available on default install media, so this is not very useful right now." -msgstr "" - -#. Tag: term -#: boot-installer.xml:2897 -#, no-c-format -msgid "BOOT_DEBUG" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2898 -#, no-c-format -msgid "" -"Setting this boot parameter to 2 will cause the installer's boot process to " -"be verbosely logged. Setting it to 3 makes debug shells available at " -"strategic points in the boot process. (Exit the shells to continue the boot " -"process.)" -msgstr "" - -#. Tag: userinput -#: boot-installer.xml:2907 -#, no-c-format -msgid "BOOT_DEBUG=0" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2908 -#, no-c-format -msgid "This is the default." -msgstr "" - -#. Tag: userinput -#: boot-installer.xml:2912 -#, no-c-format -msgid "BOOT_DEBUG=1" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2913 -#, no-c-format -msgid "More verbose than usual." -msgstr "" - -#. Tag: userinput -#: boot-installer.xml:2917 -#, no-c-format -msgid "BOOT_DEBUG=2" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2918 -#, no-c-format -msgid "Lots of debugging information." -msgstr "" - -#. Tag: userinput -#: boot-installer.xml:2922 -#, no-c-format -msgid "BOOT_DEBUG=3" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2923 -#, no-c-format -msgid "" -"Shells are run at various points in the boot process to allow detailed " -"debugging. Exit the shell to continue the boot." -msgstr "" - -#. Tag: term -#: boot-installer.xml:2937 -#, no-c-format -msgid "INSTALL_MEDIA_DEV" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2938 -#, no-c-format -msgid "" -"The value of the parameter is the path to the device to load the Debian " -"installer from. For example, <userinput>INSTALL_MEDIA_DEV=/dev/floppy/0</" -"userinput>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2944 -#, no-c-format -msgid "" -"The boot floppy, which normally scans all floppies and USB storage devices " -"it can to find the root floppy, can be overridden by this parameter to only " -"look at the one device." -msgstr "" - -#. Tag: term -#: boot-installer.xml:2954 -#, no-c-format -msgid "debian-installer/framebuffer" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2955 -#, no-c-format -msgid "" -"Some architectures use the kernel framebuffer to offer installation in a " -"number of languages. If framebuffer causes a problem on your system you can " -"disable the feature by the parameter <userinput>debian-installer/" -"framebuffer=false</userinput>. Problem symptoms are error messages about " -"bterm or bogl, a blank screen, or a freeze within a few minutes after " -"starting the install." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2964 -#, no-c-format -msgid "" -"The <userinput>video=vga16:off</userinput> argument may also be used to " -"disable the framebuffer. Such problems have been reported on a Dell Inspiron " -"with Mobile Radeon card." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2970 -#, no-c-format -msgid "Such problems have been reported on the Amiga 1200 and SE/30." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2974 -#, no-c-format -msgid "Such problems have been reported on hppa." -msgstr "" - -#. Tag: para -#: boot-installer.xml:2978 -#, no-c-format -msgid "" -"Because of display problems on some systems, framebuffer support is " -"<emphasis>disabled by default</emphasis> for &arch-title;. This can result " -"in ugly display on systems that do properly support the framebuffer, like " -"those with ATI graphical cards. If you see display problems in the " -"installer, you can try booting with parameter <userinput>debian-installer/" -"framebuffer=true</userinput>." -msgstr "" - -#. Tag: term -#: boot-installer.xml:2991 -#, no-c-format -msgid "debian-installer/probe/usb" -msgstr "" - -#. Tag: para -#: boot-installer.xml:2992 -#, no-c-format -msgid "" -"Set to <userinput>false</userinput> to prevent probing for USB on boot, if " -"that causes problems." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3001 -#, no-c-format -msgid "netcfg/disable_dhcp" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3002 -#, no-c-format -msgid "" -"By default, the &d-i; automatically probes for network configuration via " -"DHCP. If the probe succeeds, you won't have a chance to review and change " -"the obtained settings. You can get to the manual network setup only in case " -"the DHCP probe fails." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3009 -#, no-c-format -msgid "" -"If you have a DHCP server on your local network, but want to avoid it " -"because e.g. it gives wrong answers, you can use the parameter " -"<userinput>netcfg/disable_dhcp=true</userinput> to prevent configuring the " -"network with DHCP and to enter the information manually." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3020 -#, no-c-format -msgid "hw-detect/start_pcmcia" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3021 -#, no-c-format -msgid "" -"Set to <userinput>false</userinput> to prevent starting PCMCIA services, if " -"that causes problems. Some laptops are well known for this misbehavior." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3031 -#, no-c-format -msgid "preseed/url" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3032 -#, no-c-format -msgid "" -"Specify the url to a preconfiguration file to download and use in automating " -"the install. See <xref linkend=\"automatic-install\"/>." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3041 -#, no-c-format -msgid "preseed/file" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3042 -#, no-c-format -msgid "" -"Specify the path to a preconfiguration file to load to automating the " -"install. See <xref linkend=\"automatic-install\"/>." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3051 -#, no-c-format -msgid "cdrom-detect/eject" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3052 -#, no-c-format -msgid "" -"By default, before rebooting, &d-i; automatically ejects the optical media " -"used during the installation. This can be unnecessary if the system does not " -"automatically boot off the CD. In some cases it may even be undesirable, for " -"example if the optical drive cannot reinsert the media itself and the user " -"is not there to do it manually. Many slot loading, slim-line, and caddy " -"style drives cannot reload media automatically." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3061 -#, no-c-format -msgid "" -"Set to <userinput>false</userinput> to disable automatic ejection, and be " -"aware that you may need to ensure that the system does not automatically " -"boot from the optical drive after the initial installation." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3072 -#, no-c-format -msgid "ramdisk_size" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3073 -#, no-c-format -msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -msgstr "" - -#. Tag: term -#: boot-installer.xml:3081 -#, no-c-format -msgid "rescue/enable" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3082 -#, no-c-format -msgid "" -"Set to <userinput>true</userinput> to enter rescue mode rather than " -"performing a normal installation. See <xref linkend=\"rescue\"/>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3100 -#, no-c-format -msgid "Troubleshooting the Installation Process" -msgstr "" - -#. Tag: title -#: boot-installer.xml:3105 -#, no-c-format -msgid "Floppy Disk Reliability" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3107 -#, no-c-format -msgid "" -"The biggest problem for people using floppy disks to install Debian seems to " -"be floppy disk reliability." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3112 -#, no-c-format -msgid "" -"The boot floppy is the floppy with the worst problems, because it is read by " -"the hardware directly, before Linux boots. Often, the hardware doesn't read " -"as reliably as the Linux floppy disk driver, and may just stop without " -"printing an error message if it reads incorrect data. There can also be " -"failures in the Driver Floppies most of which indicate themselves with a " -"flood of messages about disk I/O errors." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3121 -#, no-c-format -msgid "" -"If you are having the installation stall at a particular floppy, the first " -"thing you should do is re-download the floppy disk image and write it to a " -"<emphasis>different</emphasis> floppy. Simply reformatting the old floppy " -"may not be sufficient, even if it appears that the floppy was reformatted " -"and written with no errors. It is sometimes useful to try writing the floppy " -"on a different system." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3131 -#, no-c-format -msgid "" -"One user reports he had to write the images to floppy <emphasis>three</" -"emphasis> times before one worked, and then everything was fine with the " -"third floppy." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3137 -#, no-c-format -msgid "" -"Other users have reported that simply rebooting a few times with the same " -"floppy in the floppy drive can lead to a successful boot. This is all due to " -"buggy hardware or firmware floppy drivers." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3146 -#, no-c-format -msgid "Boot Configuration" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3148 -#, no-c-format -msgid "" -"If you have problems and the kernel hangs during the boot process, doesn't " -"recognize peripherals you actually have, or drives are not recognized " -"properly, the first thing to check is the boot parameters, as discussed in " -"<xref linkend=\"boot-parms\"/>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3155 -#, no-c-format -msgid "" -"If you are booting with your own kernel instead of the one supplied with the " -"installer, be sure that <userinput>CONFIG_DEVFS</userinput> is set in your " -"kernel. The installer requires <userinput>CONFIG_DEVFS</userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3162 -#, no-c-format -msgid "" -"Often, problems can be solved by removing add-ons and peripherals, and then " -"trying booting again. <phrase arch=\"i386\">Internal modems, sound cards, " -"and Plug-n-Play devices can be especially problematic.</phrase>" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3168 -#, no-c-format -msgid "" -"If you have a large amount of memory installed in your machine, more than " -"512M, and the installer hangs when booting the kernel, you may need to " -"include a boot argument to limit the amount of memory the kernel sees, such " -"as <userinput>mem=512m</userinput>." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3179 -#, no-c-format -msgid "Common &arch-title; Installation Problems" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3180 -#, no-c-format -msgid "" -"There are some common installation problems that can be solved or avoided by " -"passing certain boot parameters to the installer." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3185 -#, no-c-format -msgid "" -"Some systems have floppies with <quote>inverted DCLs</quote>. If you receive " -"errors reading from the floppy, even when you know the floppy is good, try " -"the parameter <userinput>floppy=thinkpad</userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3191 -#, no-c-format -msgid "" -"On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " -"drivers), the IDE drive may not be properly recognized. Again, try it first " -"without the parameters and see if the IDE drive is recognized properly. If " -"not, determine your drive geometry (cylinders, heads, and sectors), and use " -"the parameter <userinput>hd=<replaceable>cylinders</replaceable>," -"<replaceable>heads</replaceable>,<replaceable>sectors</replaceable></" -"userinput>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3200 -#, no-c-format -msgid "" -"If you have a very old machine, and the kernel hangs after saying " -"<computeroutput>Checking 'hlt' instruction...</computeroutput>, then you " -"should try the <userinput>no-hlt</userinput> boot argument, which disables " -"this test." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3207 -#, no-c-format -msgid "" -"If your screen begins to show a weird picture while the kernel boots, eg. " -"pure white, pure black or colored pixel garbage, your system may contain a " -"problematic video card which does not switch to the framebuffer mode " -"properly. Then you can use the boot parameter <userinput>debian-installer/" -"framebuffer=false</userinput> or <userinput>video=vga16:off</userinput> to " -"disable the framebuffer console. Only the English language will be available " -"during the installation due to limited console features. See <xref linkend=" -"\"boot-parms\"/> for details." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3222 -#, no-c-format -msgid "System Freeze During the PCMCIA Configuration Phase" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3223 -#, no-c-format -msgid "" -"Some laptop models produced by Dell are known to crash when PCMCIA device " -"detection tries to access some hardware addresses. Other laptops may display " -"similar problems. If you experience such a problem and you don't need PCMCIA " -"support during the installation, you can disable PCMCIA using the " -"<userinput>hw-detect/start_pcmcia=false</userinput> boot parameter. You can " -"then configure PCMCIA after the installation is completed and exclude the " -"resource range causing the problems." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3233 -#, no-c-format -msgid "" -"Alternatively, you can boot the installer in expert mode. You will then be " -"asked to enter the resource range options your hardware needs. For example, " -"if you have one of the Dell laptops mentioned above, you should enter " -"<userinput>exclude port 0x800-0x8ff</userinput> here. There is also a list " -"of some common resource range options in the <ulink url=\"http://pcmcia-cs." -"sourceforge.net/ftp/doc/PCMCIA-HOWTO-1.html#ss1.12\">System resource " -"settings section of the PCMCIA HOWTO</ulink>. Note that you have to omit the " -"commas, if any, when you enter this value in the installer." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3250 -#, no-c-format -msgid "System Freeze while Loading the USB Modules" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3251 -#, no-c-format -msgid "" -"The kernel normally tries to install USB modules and the USB keyboard driver " -"in order to support some non-standard USB keyboards. However, there are some " -"broken USB systems where the driver hangs on loading. A possible workaround " -"may be disabling the USB controller in your mainboard BIOS setup. Another " -"option is passing the <userinput>debian-installer/probe/usb=false</" -"userinput> parameter at the boot prompt, which will prevent the modules from " -"being loaded." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3265 -#, no-c-format -msgid "Interpreting the Kernel Startup Messages" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3267 -#, no-c-format -msgid "" -"During the boot sequence, you may see many messages in the form " -"<computeroutput>can't find <replaceable>something</replaceable> </" -"computeroutput>, or <computeroutput> <replaceable>something</replaceable> " -"not present</computeroutput>, <computeroutput>can't initialize " -"<replaceable>something</replaceable> </computeroutput>, or even " -"<computeroutput>this driver release depends on <replaceable>something</" -"replaceable> </computeroutput>. Most of these messages are harmless. You see " -"them because the kernel for the installation system is built to run on " -"computers with many different peripheral devices. Obviously, no one computer " -"will have every possible peripheral device, so the operating system may emit " -"a few complaints while it looks for peripherals you don't own. You may also " -"see the system pause for a while. This happens when it is waiting for a " -"device to respond, and that device is not present on your system. If you " -"find the time it takes to boot the system unacceptably long, you can create " -"a custom kernel later (see <xref linkend=\"kernel-baking\"/>)." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3292 -#, no-c-format -msgid "Bug Reporter" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3293 -#, no-c-format -msgid "" -"If you get through the initial boot phase but cannot complete the install, " -"the bug reporter menu choice may be helpful. It lets you store system error " -"logs and configuration information from the installer to a floppy, or " -"download them in a web browser. This information may provide clues as to " -"what went wrong and how to fix it. If you are submitting a bug report you " -"may want to attach this information to the bug report." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3304 -#, no-c-format -msgid "" -"Other pertinent installation messages may be found in <filename>/var/log/</" -"filename> during the installation, and <filename>/var/log/installer/</" -"filename> after the computer has been booted into the installed system." -msgstr "" - -#. Tag: title -#: boot-installer.xml:3315 -#, no-c-format -msgid "Submitting Installation Reports" -msgstr "" - -#. Tag: para -#: boot-installer.xml:3316 -#, no-c-format -msgid "" -"If you still have problems, please submit an installation report. We also " -"encourage installation reports to be sent even if the installation is " -"successful, so that we can get as much information as possible on the " -"largest number of hardware configurations." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3323 -#, no-c-format -msgid "" -"If you have a working Debian system, the easiest way to send an installation " -"report is to install the installation-report and reportbug packages " -"(<command>apt-get install installation-report reportbug</command>) and run " -"the command <command>reportbug installation-report</command>." -msgstr "" - -#. Tag: para -#: boot-installer.xml:3330 -#, no-c-format -msgid "" -"Please use this template when filling out installation reports, and file the " -"report as a bug report against the <classname>installation-reports</" -"classname> pseudo package, by sending it to <email>submit@bugs.debian.org</" -"email>. <informalexample><screen>\n" -"Package: installation-reports\n" -"\n" -"Boot method: <How did you boot the installer? CD? floppy? network?>\n" -"Image version: <Fill in date and from where you got the image>\n" -"Date: <Date and time of the install>\n" -"\n" -"Machine: <Description of machine (eg, IBM Thinkpad R32)>\n" -"Processor:\n" -"Memory:\n" -"Partitions: <df -Tl will do; the raw partition table is preferred>\n" -"\n" -"Output of lspci and lspci -n:\n" -"\n" -"Base System Installation Checklist:\n" -"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" -"\n" -"Initial boot worked: [ ]\n" -"Configure network HW: [ ]\n" -"Config network: [ ]\n" -"Detect CD: [ ]\n" -"Load installer modules: [ ]\n" -"Detect hard drives: [ ]\n" -"Partition hard drives: [ ]\n" -"Create file systems: [ ]\n" -"Mount partitions: [ ]\n" -"Install base system: [ ]\n" -"Install boot loader: [ ]\n" -"Reboot: [ ]\n" -"\n" -"Comments/Problems:\n" -"\n" -"<Description of the install, in prose, and any thoughts, comments\n" -" and ideas you had during the initial install.>\n" -"</screen></informalexample> In the bug report, describe what the problem is, " -"including the last visible kernel messages in the event of a kernel hang. " -"Describe the steps that you did which brought the system into the problem " -"state." -msgstr "" diff --git a/po/pl/boot-new.po b/po/pl/boot-new.po deleted file mode 100644 index 99f459d32..000000000 --- a/po/pl/boot-new.po +++ /dev/null @@ -1,329 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: boot-new.xml:5 -#, no-c-format -msgid "Booting Into Your New Debian System" -msgstr "" - -#. Tag: title -#: boot-new.xml:7 -#, no-c-format -msgid "The Moment of Truth" -msgstr "" - -#. Tag: para -#: boot-new.xml:8 -#, no-c-format -msgid "" -"Your system's first boot on its own power is what electrical engineers call " -"the <quote>smoke test</quote>." -msgstr "" - -#. Tag: para -#: boot-new.xml:13 -#, no-c-format -msgid "" -"If you are booting directly into Debian, and the system doesn't start up, " -"either use your original installation boot media, or insert the custom boot " -"floppy if you have one, and reset your system. This way, you will probably " -"need to add some boot arguments like <userinput>root=<replaceable>root</" -"replaceable></userinput>, where <replaceable>root</replaceable> is your root " -"partition, such as <filename>/dev/sda1</filename>. Alternatively, see <xref " -"linkend=\"rescue\"/> for instructions on using the installer's built-in " -"rescue mode." -msgstr "" - -#. Tag: title -#: boot-new.xml:27 -#, no-c-format -msgid "BVME 6000 Booting" -msgstr "" - -#. Tag: para -#: boot-new.xml:28 -#, no-c-format -msgid "" -"If you have just performed a diskless install on a BVM or Motorola VMEbus " -"machine: once the system has loaded the <command>tftplilo</command> program " -"from the TFTP server, from the <prompt>LILO Boot:</prompt> prompt enter one " -"of:" -msgstr "" - -#. Tag: para -#: boot-new.xml:36 -#, no-c-format -msgid "" -"<userinput>b6000</userinput> followed by &enterkey; to boot a BVME 4000/6000" -msgstr "" - -#. Tag: para -#: boot-new.xml:41 -#, no-c-format -msgid "<userinput>b162</userinput> followed by &enterkey; to boot an MVME162" -msgstr "" - -#. Tag: para -#: boot-new.xml:46 -#, no-c-format -msgid "" -"<userinput>b167</userinput> followed by &enterkey; to boot an MVME166/167" -msgstr "" - -#. Tag: title -#: boot-new.xml:58 -#, no-c-format -msgid "Macintosh Booting" -msgstr "" - -#. Tag: para -#: boot-new.xml:60 -#, no-c-format -msgid "" -"Go to the directory containing the installation files and start up the " -"<command>Penguin</command> booter, holding down the <keycap>command</keycap> " -"key. Go to the <userinput>Settings</userinput> dialogue (<keycombo> " -"<keycap>command</keycap> <keycap>T</keycap> </keycombo>), and locate the " -"kernel options line which should look like <userinput>root=/dev/ram " -"video=font:VGA8x16</userinput> or similar." -msgstr "" - -#. Tag: para -#: boot-new.xml:70 -#, no-c-format -msgid "" -"You need to change the entry to <userinput>root=/dev/<replaceable>yyyy</" -"replaceable></userinput>. Replace the <replaceable>yyyy</replaceable> with " -"the Linux name of the partition onto which you installed the system (e.g. " -"<filename>/dev/sda1</filename>); you wrote this down earlier. The " -"<userinput>video=font:VGA8x8</userinput> is recommended especially for users " -"with tiny screens. The kernel would pick a prettier (6x11) font but the " -"console driver for this font can hang the machine, so using 8x16 or 8x8 is " -"safer at this stage. You can change this at any time." -msgstr "" - -#. Tag: para -#: boot-new.xml:83 -#, no-c-format -msgid "" -"If you don't want to start GNU/Linux immediately each time you start, " -"uncheck the <userinput>Auto Boot</userinput> option. Save your settings in " -"the <filename>Prefs</filename> file using the <userinput>Save Settings As " -"Default</userinput> option." -msgstr "" - -#. Tag: para -#: boot-new.xml:90 -#, no-c-format -msgid "" -"Now select <userinput>Boot Now</userinput> (<keycombo> <keycap>command</" -"keycap> <keycap>B</keycap> </keycombo>) to start your freshly installed GNU/" -"Linux instead of the RAMdisk installer system." -msgstr "" - -#. Tag: para -#: boot-new.xml:96 -#, no-c-format -msgid "" -"Debian should boot, and you should see the same messages as when you first " -"booted the installation system, followed by some new messages." -msgstr "" - -#. Tag: title -#: boot-new.xml:106 -#, no-c-format -msgid "OldWorld PowerMacs" -msgstr "" - -#. Tag: para -#: boot-new.xml:107 -#, no-c-format -msgid "" -"If the machine fails to boot after completing the installation, and stops " -"with a <prompt>boot:</prompt> prompt, try typing <userinput>Linux</" -"userinput> followed by &enterkey;. (The default boot configuration in " -"<filename>quik.conf</filename> is labeled Linux). The labels defined in " -"<filename>quik.conf</filename> will be displayed if you press the " -"<keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt. You can also " -"try booting back into the installer, and editing the <filename>/target/etc/" -"quik.conf</filename> placed there by the <guimenuitem>Install Quik on a Hard " -"Disk</guimenuitem> step. Clues for dealing with <command>quik</command> are " -"available at <ulink url=\"&url-powerpc-quik-faq;\"></ulink>." -msgstr "" - -#. Tag: para -#: boot-new.xml:121 -#, no-c-format -msgid "" -"To boot back into MacOS without resetting the nvram, type <userinput>bye</" -"userinput> at the OpenFirmware prompt (assuming MacOS has not been removed " -"from the machine). To obtain an OpenFirmware prompt, hold down the " -"<keycombo> <keycap>command</keycap> <keycap>option</keycap> <keycap>o</" -"keycap> <keycap>f</keycap> </keycombo> keys while cold booting the machine. " -"If you need to reset the OpenFirmware nvram changes to the MacOS default in " -"order to boot back to MacOS, hold down the <keycombo> <keycap>command</" -"keycap> <keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </" -"keycombo> keys while cold booting the machine." -msgstr "" - -#. Tag: para -#: boot-new.xml:134 -#, no-c-format -msgid "" -"If you use <command>BootX</command> to boot into the installed system, just " -"select your desired kernel in the <filename>Linux Kernels</filename> folder, " -"un-choose the ramdisk option, and add a root device corresponding to your " -"installation; e.g. <userinput>/dev/hda8</userinput>." -msgstr "" - -#. Tag: title -#: boot-new.xml:146 -#, no-c-format -msgid "NewWorld PowerMacs" -msgstr "" - -#. Tag: para -#: boot-new.xml:147 -#, no-c-format -msgid "" -"On G4 machines and iBooks, you can hold down the <keycap>option</keycap> key " -"and get a graphical screen with a button for each bootable OS, &debian; will " -"be a button with a small penguin icon." -msgstr "" - -#. Tag: para -#: boot-new.xml:154 -#, no-c-format -msgid "" -"If you kept MacOS and at some point it changes the OpenFirmware <envar>boot-" -"device</envar> variable you should reset OpenFirmware to its default " -"configuration. To do this hold down the <keycombo> <keycap>command</keycap> " -"<keycap>option</keycap> <keycap>p</keycap> <keycap>r</keycap> </keycombo> " -"keys while cold booting the machine." -msgstr "" - -#. Tag: para -#: boot-new.xml:162 -#, no-c-format -msgid "" -"The labels defined in <filename>yaboot.conf</filename> will be displayed if " -"you press the <keycap>Tab</keycap> key at the <prompt>boot:</prompt> prompt." -msgstr "" - -#. Tag: para -#: boot-new.xml:168 -#, no-c-format -msgid "" -"Resetting OpenFirmware on G3 or G4 hardware will cause it to boot &debian; " -"by default (if you correctly partitioned and placed the Apple_Bootstrap " -"partition first). If you have &debian; on a SCSI disk and MacOS on an IDE " -"disk this may not work and you will have to enter OpenFirmware and set the " -"<envar>boot-device</envar> variable, <command>ybin</command> normally does " -"this automatically." -msgstr "" - -#. Tag: para -#: boot-new.xml:177 -#, no-c-format -msgid "" -"After you boot &debian; for the first time you can add any additional " -"options you desire (such as dual boot options) to <filename>/etc/yaboot." -"conf</filename> and run <command>ybin</command> to update your boot " -"partition with the changed configuration. Please read the <ulink url=\"&url-" -"powerpc-yaboot-faq;\">yaboot HOWTO</ulink> for more information." -msgstr "" - -#. Tag: title -#: boot-new.xml:191 -#, no-c-format -msgid "Log In" -msgstr "" - -#. Tag: para -#: boot-new.xml:193 -#, no-c-format -msgid "" -"Once your system boots, you'll be presented with the login prompt. Log in " -"using the personal login and password you selected during the installation " -"process. Your system is now ready to use." -msgstr "" - -#. Tag: para -#: boot-new.xml:199 -#, no-c-format -msgid "" -"If you are a new user, you may want to explore the documentation which is " -"already installed on your system as you start to use it. There are currently " -"several documentation systems, work is proceeding on integrating the " -"different types of documentation. Here are a few starting points." -msgstr "" - -#. Tag: para -#: boot-new.xml:207 -#, no-c-format -msgid "" -"Documentation accompanying programs you have installed is in <filename>/usr/" -"share/doc/</filename>, under a subdirectory named after the program. For " -"example, the APT User's Guide for using <command>apt</command> to install " -"other programs on your system, is located in <filename>/usr/share/doc/apt/" -"guide.html/index.html</filename>." -msgstr "" - -#. Tag: para -#: boot-new.xml:216 -#, no-c-format -msgid "" -"In addition, there are some special folders within the <filename>/usr/share/" -"doc/</filename> hierarchy. Linux HOWTOs are installed in <emphasis>.gz</" -"emphasis> format, in <filename>/usr/share/doc/HOWTO/en-txt/</filename>. " -"After installing <command>dhelp</command> you will find a browse-able index " -"of documentation in <filename>/usr/share/doc/HTML/index.html</filename>." -msgstr "" - -#. Tag: para -#: boot-new.xml:226 -#, no-c-format -msgid "" -"One easy way to view these documents is to <userinput>cd /usr/share/doc/</" -"userinput>, and type <userinput>lynx</userinput> followed by a space and a " -"dot (the dot stands for the current directory)." -msgstr "" - -#. Tag: para -#: boot-new.xml:233 -#, no-c-format -msgid "" -"You can also type <userinput>info <replaceable>command</replaceable></" -"userinput> or <userinput>man <replaceable>command</replaceable></userinput> " -"to see documentation on most commands available at the command prompt. " -"Typing <userinput>help</userinput> will display help on shell commands. And " -"typing a command followed by <userinput>--help</userinput> will usually " -"display a short summary of the command's usage. If a command's results " -"scroll past the top of the screen, type <userinput>| more</userinput> after " -"the command to cause the results to pause before scrolling past the top of " -"the screen. To see a list of all commands available which begin with a " -"certain letter, type the letter and then two tabs." -msgstr "" - -#. Tag: para -#: boot-new.xml:248 -#, no-c-format -msgid "" -"For a more complete introduction to Debian and GNU/Linux, see <filename>/usr/" -"share/doc/debian-guide/html/noframes/index.html</filename>." -msgstr "" diff --git a/po/pl/gpl.po b/po/pl/gpl.po deleted file mode 100644 index 83ab984e5..000000000 --- a/po/pl/gpl.po +++ /dev/null @@ -1,661 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: gpl.xml:4 -#, no-c-format -msgid "GNU General Public License" -msgstr "" - -#. Tag: para -#: gpl.xml:6 -#, no-c-format -msgid "Version 2, June 1991" -msgstr "" - -#. Tag: para -#: gpl.xml:10 -#, no-c-format -msgid "" -"Copyright (C) 1989, 1991 Free Software Foundation, Inc. — 51 Franklin " -"St, Fifth Floor, Boston, MA 02110-1301, USA." -msgstr "" - -#. Tag: para -#: gpl.xml:15 -#, no-c-format -msgid "" -"Everyone is permitted to copy and distribute verbatim copies of this license " -"document, but changing it is not allowed." -msgstr "" - -#. Tag: title -#: gpl.xml:22 -#, no-c-format -msgid "Preamble" -msgstr "" - -#. Tag: para -#: gpl.xml:23 -#, no-c-format -msgid "" -"The licenses for most software are designed to take away your freedom to " -"share and change it. By contrast, the gnu General Public License is intended " -"to guarantee your freedom to share and change free software — to make " -"sure the software is free for all its users. This General Public License " -"applies to most of the Free Software Foundation's software and to any other " -"program whose authors commit to using it. (Some other Free Software " -"Foundation software is covered by the gnu Library General Public License " -"instead.) You can apply it to your programs, too." -msgstr "" - -#. Tag: para -#: gpl.xml:35 -#, no-c-format -msgid "" -"When we speak of free software, we are referring to freedom, not price. Our " -"General Public Licenses are designed to make sure that you have the freedom " -"to distribute copies of free software (and charge for this service if you " -"wish), that you receive source code or can get it if you want it, that you " -"can change the software or use pieces of it in new free programs; and that " -"you know you can do these things." -msgstr "" - -#. Tag: para -#: gpl.xml:45 -#, no-c-format -msgid "" -"To protect your rights, we need to make restrictions that forbid anyone to " -"deny you these rights or to ask you to surrender the rights. These " -"restrictions translate to certain responsibilities for you if you distribute " -"copies of the software, or if you modify it." -msgstr "" - -#. Tag: para -#: gpl.xml:52 -#, no-c-format -msgid "" -"For example, if you distribute copies of such a program, whether gratis or " -"for a fee, you must give the recipients all the rights that you have. You " -"must make sure that they, too, receive or can get the source code. And you " -"must show them these terms so they know their rights." -msgstr "" - -#. Tag: para -#: gpl.xml:60 -#, no-c-format -msgid "" -"We protect your rights with two steps: (1) copyright the software, and (2) " -"offer you this license which gives you legal permission to copy, distribute " -"and/or modify the software." -msgstr "" - -#. Tag: para -#: gpl.xml:66 -#, no-c-format -msgid "" -"Also, for each author's protection and ours, we want to make certain that " -"everyone understands that there is no warranty for this free software. If " -"the software is modified by someone else and passed on, we want its " -"recipients to know that what they have is not the original, so that any " -"problems introduced by others will not reflect on the original authors' " -"reputations." -msgstr "" - -#. Tag: para -#: gpl.xml:75 -#, no-c-format -msgid "" -"Finally, any free program is threatened constantly by software patents. We " -"wish to avoid the danger that redistributors of a free program will " -"individually obtain patent licenses, in effect making the program " -"proprietary. To prevent this, we have made it clear that any patent must be " -"licensed for everyone's free use or not licensed at all." -msgstr "" - -#. Tag: para -#: gpl.xml:84 -#, no-c-format -msgid "" -"The precise terms and conditions for copying, distribution and modification " -"follow." -msgstr "" - -#. Tag: title -#: gpl.xml:92 -#, no-c-format -msgid "GNU GENERAL PUBLIC LICENSE" -msgstr "" - -#. Tag: para -#: gpl.xml:93 -#, no-c-format -msgid "TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION" -msgstr "" - -#. Tag: para -#: gpl.xml:99 -#, no-c-format -msgid "" -"This License applies to any program or other work which contains a notice " -"placed by the copyright holder saying it may be distributed under the terms " -"of this General Public License. The \"Program\", below, refers to any such " -"program or work, and a \"work based on the Program\" means either the " -"Program or any derivative work under copyright law: that is to say, a work " -"containing the Program or a portion of it, either verbatim or with " -"modifications and/or translated into another language. (Hereinafter, " -"translation is included without limitation in the term \"modification\".) " -"Each licensee is addressed as \"you\"." -msgstr "" - -#. Tag: para -#: gpl.xml:111 -#, no-c-format -msgid "" -"Activities other than copying, distribution and modification are not covered " -"by this License; they are outside its scope. The act of running the Program " -"is not restricted, and the output from the Program is covered only if its " -"contents constitute a work based on the Program (independent of having been " -"made by running the Program). Whether that is true depends on what the " -"Program does." -msgstr "" - -#. Tag: para -#: gpl.xml:121 -#, no-c-format -msgid "" -"You may copy and distribute verbatim copies of the Program's source code as " -"you receive it, in any medium, provided that you conspicuously and " -"appropriately publish on each copy an appropriate copyright notice and " -"disclaimer of warranty; keep intact all the notices that refer to this " -"License and to the absence of any warranty; and give any other recipients of " -"the Program a copy of this License along with the Program." -msgstr "" - -#. Tag: para -#: gpl.xml:131 -#, no-c-format -msgid "" -"You may charge a fee for the physical act of transferring a copy, and you " -"may at your option offer warranty protection in exchange for a fee." -msgstr "" - -#. Tag: para -#: gpl.xml:138 -#, no-c-format -msgid "" -"You may modify your copy or copies of the Program or any portion of it, thus " -"forming a work based on the Program, and copy and distribute such " -"modifications or work under the terms of Section 1 above, provided that you " -"also meet all of these conditions:" -msgstr "" - -#. Tag: para -#: gpl.xml:145 -#, no-c-format -msgid "" -"a) You must cause the modified files to carry prominent notices stating that " -"you changed the files and the date of any change." -msgstr "" - -#. Tag: para -#: gpl.xml:150 -#, no-c-format -msgid "" -"b) You must cause any work that you distribute or publish, that in whole or " -"in part contains or is derived from the Program or any part thereof, to be " -"licensed as a whole at no charge to all third parties under the terms of " -"this License." -msgstr "" - -#. Tag: para -#: gpl.xml:157 -#, no-c-format -msgid "" -"c) If the modified program normally reads commands interactively when run, " -"you must cause it, when started running for such interactive use in the most " -"ordinary way, to print or display an announcement including an appropriate " -"copyright notice and a notice that there is no warranty (or else, saying " -"that you provide a warranty) and that users may redistribute the program " -"under these conditions, and telling the user how to view a copy of this " -"License. (Exception: if the Program itself is interactive but does not " -"normally print such an announcement, your work based on the Program is not " -"required to print an announcement.)" -msgstr "" - -#. Tag: para -#: gpl.xml:170 -#, no-c-format -msgid "" -"These requirements apply to the modified work as a whole. If identifiable " -"sections of that work are not derived from the Program, and can be " -"reasonably considered independent and separate works in themselves, then " -"this License, and its terms, do not apply to those sections when you " -"distribute them as separate works. But when you distribute the same sections " -"as part of a whole which is a work based on the Program, the distribution of " -"the whole must be on the terms of this License, whose permissions for other " -"licensees extend to the entire whole, and thus to each and every part " -"regardless of who wrote it." -msgstr "" - -#. Tag: para -#: gpl.xml:183 -#, no-c-format -msgid "" -"Thus, it is not the intent of this section to claim rights or contest your " -"rights to work written entirely by you; rather, the intent is to exercise " -"the right to control the distribution of derivative or collective works " -"based on the Program." -msgstr "" - -#. Tag: para -#: gpl.xml:190 -#, no-c-format -msgid "" -"In addition, mere aggregation of another work not based on the Program with " -"the Program (or with a work based on the Program) on a volume of a storage " -"or distribution medium does not bring the other work under the scope of this " -"License." -msgstr "" - -#. Tag: para -#: gpl.xml:198 -#, no-c-format -msgid "" -"You may copy and distribute the Program (or a work based on it, under " -"Section 2) in object code or executable form under the terms of Sections 1 " -"and 2 above provided that you also do one of the following:" -msgstr "" - -#. Tag: para -#: gpl.xml:205 -#, no-c-format -msgid "" -"a) Accompany it with the complete corresponding machine-readable source " -"code, which must be distributed under the terms of Sections 1 and 2 above on " -"a medium customarily used for software interchange; or," -msgstr "" - -#. Tag: para -#: gpl.xml:212 -#, no-c-format -msgid "" -"b) Accompany it with a written offer, valid for at least three years, to " -"give any third party, for a charge no more than your cost of physically " -"performing source distribution, a complete machine-readable copy of the " -"corresponding source code, to be distributed under the terms of Sections 1 " -"and 2 above on a medium customarily used for software interchange; or," -msgstr "" - -#. Tag: para -#: gpl.xml:221 -#, no-c-format -msgid "" -"c) Accompany it with the information you received as to the offer to " -"distribute corresponding source code. (This alternative is allowed only for " -"noncommercial distribution and only if you received the program in object " -"code or executable form with such an offer, in accord with Subsection b " -"above.)" -msgstr "" - -#. Tag: para -#: gpl.xml:229 -#, no-c-format -msgid "" -"The source code for a work means the preferred form of the work for making " -"modifications to it. For an executable work, complete source code means all " -"the source code for all modules it contains, plus any associated interface " -"definition files, plus the scripts used to control compilation and " -"installation of the executable. However, as a special exception, the source " -"code distributed need not include anything that is normally distributed (in " -"either source or binary form) with the major components (compiler, kernel, " -"and so on) of the operating system on which the executable runs, unless that " -"component itself accompanies the executable." -msgstr "" - -#. Tag: para -#: gpl.xml:242 -#, no-c-format -msgid "" -"If distribution of executable or object code is made by offering access to " -"copy from a designated place, then offering equivalent access to copy the " -"source code from the same place counts as distribution of the source code, " -"even though third parties are not compelled to copy the source along with " -"the object code." -msgstr "" - -#. Tag: para -#: gpl.xml:251 -#, no-c-format -msgid "" -"You may not copy, modify, sublicense, or distribute the Program except as " -"expressly provided under this License. Any attempt otherwise to copy, " -"modify, sublicense or distribute the Program is void, and will automatically " -"terminate your rights under this License. However, parties who have received " -"copies, or rights, from you under this License will not have their licenses " -"terminated so long as such parties remain in full compliance." -msgstr "" - -#. Tag: para -#: gpl.xml:262 -#, no-c-format -msgid "" -"You are not required to accept this License, since you have not signed it. " -"However, nothing else grants you permission to modify or distribute the " -"Program or its derivative works. These actions are prohibited by law if you " -"do not accept this License. Therefore, by modifying or distributing the " -"Program (or any work based on the Program), you indicate your acceptance of " -"this License to do so, and all its terms and conditions for copying, " -"distributing or modifying the Program or works based on it." -msgstr "" - -#. Tag: para -#: gpl.xml:274 -#, no-c-format -msgid "" -"Each time you redistribute the Program (or any work based on the Program), " -"the recipient automatically receives a license from the original licensor to " -"copy, distribute or modify the Program subject to these terms and " -"conditions. You may not impose any further restrictions on the recipients' " -"exercise of the rights granted herein. You are not responsible for enforcing " -"compliance by third parties to this License." -msgstr "" - -#. Tag: para -#: gpl.xml:285 -#, no-c-format -msgid "" -"If, as a consequence of a court judgment or allegation of patent " -"infringement or for any other reason (not limited to patent issues), " -"conditions are imposed on you (whether by court order, agreement or " -"otherwise) that contradict the conditions of this License, they do not " -"excuse you from the conditions of this License. If you cannot distribute so " -"as to satisfy simultaneously your obligations under this License and any " -"other pertinent obligations, then as a consequence you may not distribute " -"the Program at all. For example, if a patent license would not permit " -"royalty-free redistribution of the Program by all those who receive copies " -"directly or indirectly through you, then the only way you could satisfy both " -"it and this License would be to refrain entirely from distribution of the " -"Program." -msgstr "" - -#. Tag: para -#: gpl.xml:301 -#, no-c-format -msgid "" -"If any portion of this section is held invalid or unenforceable under any " -"particular circumstance, the balance of the section is intended to apply and " -"the section as a whole is intended to apply in other circumstances." -msgstr "" - -#. Tag: para -#: gpl.xml:308 -#, no-c-format -msgid "" -"It is not the purpose of this section to induce you to infringe any patents " -"or other property right claims or to contest validity of any such claims; " -"this section has the sole purpose of protecting the integrity of the free " -"software distribution system, which is implemented by public license " -"practices. Many people have made generous contributions to the wide range of " -"software distributed through that system in reliance on consistent " -"application of that system; it is up to the author/donor to decide if he or " -"she is willing to distribute software through any other system and a " -"licensee cannot impose that choice." -msgstr "" - -#. Tag: para -#: gpl.xml:321 -#, no-c-format -msgid "" -"This section is intended to make thoroughly clear what is believed to be a " -"consequence of the rest of this License." -msgstr "" - -#. Tag: para -#: gpl.xml:327 -#, no-c-format -msgid "" -"If the distribution and/or use of the Program is restricted in certain " -"countries either by patents or by copyrighted interfaces, the original " -"copyright holder who places the Program under this License may add an " -"explicit geographical distribution limitation excluding those countries, so " -"that distribution is permitted only in or among countries not thus excluded. " -"In such case, this License incorporates the limitation as if written in the " -"body of this License." -msgstr "" - -#. Tag: para -#: gpl.xml:338 -#, no-c-format -msgid "" -"The Free Software Foundation may publish revised and/or new versions of the " -"General Public License from time to time. Such new versions will be similar " -"in spirit to the present version, but may differ in detail to address new " -"problems or concerns. Each version is given a distinguishing version number. " -"If the Program specifies a version number of this License which applies to " -"it and \"any later version\", you have the option of following the terms and " -"conditions either of that version or of any later version published by the " -"Free Software Foundation. If the Program does not specify a version number " -"of this License, you may choose any version ever published by the Free " -"Software Foundation." -msgstr "" - -#. Tag: para -#: gpl.xml:353 -#, no-c-format -msgid "" -"If you wish to incorporate parts of the Program into other free programs " -"whose distribution conditions are different, write to the author to ask for " -"permission. For software which is copyrighted by the Free Software " -"Foundation, write to the Free Software Foundation; we sometimes make " -"exceptions for this. Our decision will be guided by the two goals of " -"preserving the free status of all derivatives of our free software and of " -"promoting the sharing and reuse of software generally." -msgstr "" - -#. Tag: para -#: gpl.xml:364 -#, no-c-format -msgid "NO WARRANTY" -msgstr "" - -#. Tag: para -#: gpl.xml:369 -#, no-c-format -msgid "" -"because the program is licensed free of charge, there is no warranty for the " -"program, to the extent permitted by applicable law. except when otherwise " -"stated in writing the copyright holders and/or other parties provide the " -"program \"as is\" without warranty of any kind, either expressed or implied, " -"including, but not limited to, the implied warranties of merchantability and " -"fitness for a particular purpose. the entire risk as to the quality and " -"performance of the program is with you. should the program prove defective, " -"you assume the cost of all necessary servicing, repair or correction." -msgstr "" - -#. Tag: para -#: gpl.xml:382 -#, no-c-format -msgid "" -"in no event unless required by applicable law or agreed to in writing will " -"any copyright holder, or any other party who may modify and/or redistribute " -"the program as permitted above, be liable to you for damages, including any " -"general, special, incidental or consequential damages arising out of the use " -"or inability to use the program (including but not limited to loss of data " -"or data being rendered inaccurate or losses sustained by you or third " -"parties or a failure of the program to operate with any other programs), " -"even if such holder or other party has been advised of the possibility of " -"such damages." -msgstr "" - -#. Tag: para -#: gpl.xml:397 -#, no-c-format -msgid "END OF TERMS AND CONDITIONS" -msgstr "" - -#. Tag: title -#: gpl.xml:404 -#, no-c-format -msgid "How to Apply These Terms to Your New Programs" -msgstr "" - -#. Tag: para -#: gpl.xml:405 -#, no-c-format -msgid "" -"If you develop a new program, and you want it to be of the greatest possible " -"use to the public, the best way to achieve this is to make it free software " -"which everyone can redistribute and change under these terms." -msgstr "" - -#. Tag: para -#: gpl.xml:412 -#, no-c-format -msgid "" -"To do so, attach the following notices to the program. It is safest to " -"attach them to the start of each source file to most effectively convey the " -"exclusion of warranty; and each file should have at least the \"copyright\" " -"line and a pointer to where the full notice is found." -msgstr "" - -#. Tag: para -#: gpl.xml:419 -#, no-c-format -msgid "one line to give the program's name and a brief idea of what it does." -msgstr "" - -#. Tag: para -#: gpl.xml:424 -#, no-c-format -msgid "Copyright (C) year name of author" -msgstr "" - -#. Tag: para -#: gpl.xml:428 -#, no-c-format -msgid "" -"This program is free software; you can redistribute it and/or modify it " -"under the terms of the gnu General Public License as published by the Free " -"Software Foundation; either version 2 of the License, or (at your option) " -"any later version." -msgstr "" - -#. Tag: para -#: gpl.xml:435 -#, no-c-format -msgid "" -"This program is distributed in the hope that it will be useful, but without " -"any warranty; without even the implied warranty of merchantability or " -"fitness for a particular purpose. See the gnu General Public License for " -"more details." -msgstr "" - -#. Tag: para -#: gpl.xml:442 -#, no-c-format -msgid "" -"You should have received a copy of the gnu General Public License along with " -"this program; if not, write to the Free Software Foundation, Inc., 51 " -"Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA." -msgstr "" - -#. Tag: para -#: gpl.xml:449 -#, no-c-format -msgid "" -"Also add information on how to contact you by electronic and paper mail." -msgstr "" - -#. Tag: para -#: gpl.xml:454 -#, no-c-format -msgid "" -"If the program is interactive, make it output a short notice like this when " -"it starts in an interactive mode:" -msgstr "" - -#. Tag: para -#: gpl.xml:459 -#, no-c-format -msgid "Gnomovision version 69, Copyright (C) year name of author" -msgstr "" - -#. Tag: para -#: gpl.xml:463 -#, no-c-format -msgid "" -"Gnomovision comes with absolutely no warranty; for details type `show w'." -msgstr "" - -#. Tag: para -#: gpl.xml:468 -#, no-c-format -msgid "" -"This is free software, and you are welcome to redistribute it under certain " -"conditions; type `show c' for details." -msgstr "" - -#. Tag: para -#: gpl.xml:473 -#, no-c-format -msgid "" -"The hypothetical commands `show w' and `show c' should show the appropriate " -"parts of the General Public License. Of course, the commands you use may be " -"called something other than `show w' and `show c'; they could even be mouse-" -"clicks or menu items — whatever suits your program." -msgstr "" - -#. Tag: para -#: gpl.xml:481 -#, no-c-format -msgid "" -"You should also get your employer (if you work as a programmer) or your " -"school, if any, to sign a \"copyright disclaimer\" for the program, if " -"necessary. Here is a sample; alter the names:" -msgstr "" - -#. Tag: para -#: gpl.xml:487 -#, no-c-format -msgid "" -"Yoyodyne, Inc., hereby disclaims all copyright interest in the program " -"`Gnomovision' (which makes passes at compilers) written by James Hacker." -msgstr "" - -#. Tag: para -#: gpl.xml:493 -#, no-c-format -msgid "signature of Ty Coon, 1 April 1989" -msgstr "" - -#. Tag: para -#: gpl.xml:497 -#, no-c-format -msgid "Ty Coon, President of Vice" -msgstr "" - -#. Tag: para -#: gpl.xml:501 -#, no-c-format -msgid "" -"This General Public License does not permit incorporating your program into " -"proprietary programs. If your program is a subroutine library, you may " -"consider it more useful to permit linking proprietary applications with the " -"library. If this is what you want to do, use the gnu Library General Public " -"License instead of this License." -msgstr "" diff --git a/po/pl/hardware.po b/po/pl/hardware.po deleted file mode 100644 index 78da1e1bb..000000000 --- a/po/pl/hardware.po +++ /dev/null @@ -1,3810 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-03-26 19:43+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: hardware.xml:5 -#, no-c-format -msgid "System Requirements" -msgstr "" - -#. Tag: para -#: hardware.xml:7 -#, no-c-format -msgid "" -"This section contains information about what hardware you need to get " -"started with Debian. You will also find links to further information about " -"hardware supported by GNU and Linux." -msgstr "" - -#. Tag: title -#: hardware.xml:20 -#, no-c-format -msgid "Supported Hardware" -msgstr "" - -#. Tag: para -#: hardware.xml:22 -#, no-c-format -msgid "" -"Debian does not impose hardware requirements beyond the requirements of the " -"Linux kernel and the GNU tool-sets. Therefore, any architecture or platform " -"to which the Linux kernel, libc, <command>gcc</command>, etc. have been " -"ported, and for which a Debian port exists, can run Debian. Please refer to " -"the Ports pages at <ulink url=\"&url-ports;\"></ulink> for more details on " -"&arch-title; architecture systems which have been tested with Debian." -msgstr "" - -#. Tag: para -#: hardware.xml:33 -#, no-c-format -msgid "" -"Rather than attempting to describe all the different hardware configurations " -"which are supported for &arch-title;, this section contains general " -"information and pointers to where additional information can be found." -msgstr "" - -#. Tag: title -#: hardware.xml:42 -#, no-c-format -msgid "Supported Architectures" -msgstr "" - -#. Tag: para -#: hardware.xml:44 -#, no-c-format -msgid "" -"Debian &release; supports eleven major architectures and several variations " -"of each architecture known as <quote>flavors</quote>." -msgstr "" - -#. Tag: entry -#: hardware.xml:55 -#, no-c-format -msgid "Architecture" -msgstr "" - -#. Tag: entry -#: hardware.xml:55 -#, no-c-format -msgid "Debian Designation" -msgstr "" - -#. Tag: entry -#: hardware.xml:56 -#, no-c-format -msgid "Subarchitecture" -msgstr "" - -#. Tag: entry -#: hardware.xml:56 -#, no-c-format -msgid "Flavor" -msgstr "" - -#. Tag: entry -#: hardware.xml:62 -#, no-c-format -msgid "Intel x86-based" -msgstr "" - -#. Tag: entry -#: hardware.xml:63 -#, no-c-format -msgid "i386" -msgstr "" - -#. Tag: entry -#: hardware.xml:65 -#, no-c-format -msgid "vanilla" -msgstr "" - -#. Tag: entry -#: hardware.xml:67 -#, no-c-format -msgid "speakup" -msgstr "" - -#. Tag: entry -#: hardware.xml:69 -#, no-c-format -msgid "linux26" -msgstr "" - -#. Tag: entry -#: hardware.xml:73 -#, no-c-format -msgid "Motorola 680x0" -msgstr "" - -#. Tag: entry -#: hardware.xml:74 -#, no-c-format -msgid "m68k" -msgstr "" - -#. Tag: entry -#: hardware.xml:75 -#, no-c-format -msgid "Atari" -msgstr "" - -#. Tag: entry -#: hardware.xml:76 -#, no-c-format -msgid "atari" -msgstr "" - -#. Tag: entry -#: hardware.xml:78 -#, no-c-format -msgid "Amiga" -msgstr "" - -#. Tag: entry -#: hardware.xml:79 -#, no-c-format -msgid "amiga" -msgstr "" - -#. Tag: entry -#: hardware.xml:81 -#, no-c-format -msgid "68k Macintosh" -msgstr "" - -#. Tag: entry -#: hardware.xml:82 -#, no-c-format -msgid "<entry>mac</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:84 -#, no-c-format -msgid "<entry>VME</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:85 -#, no-c-format -msgid "bvme6000" -msgstr "" - -#. Tag: entry -#: hardware.xml:87 -#, no-c-format -msgid "mvme147" -msgstr "" - -#. Tag: entry -#: hardware.xml:89 -#, no-c-format -msgid "mvme16x" -msgstr "" - -#. Tag: entry -#: hardware.xml:93 -#, no-c-format -msgid "DEC Alpha" -msgstr "" - -#. Tag: entry -#: hardware.xml:94 -#, no-c-format -msgid "alpha" -msgstr "" - -#. Tag: entry -#: hardware.xml:100 -#, no-c-format -msgid "Sun SPARC" -msgstr "" - -#. Tag: entry -#: hardware.xml:101 -#, no-c-format -msgid "sparc" -msgstr "" - -#. Tag: entry -#: hardware.xml:103 -#, no-c-format -msgid "sun4cdm" -msgstr "" - -#. Tag: entry -#: hardware.xml:105 -#, no-c-format -msgid "sun4u" -msgstr "" - -#. Tag: entry -#: hardware.xml:109 -#, no-c-format -msgid "ARM and StrongARM" -msgstr "" - -#. Tag: entry -#: hardware.xml:110 -#, no-c-format -msgid "<entry>arm</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:111 -#, no-c-format -msgid "Netwinder and CATS" -msgstr "" - -#. Tag: entry -#: hardware.xml:112 -#, no-c-format -msgid "netwinder" -msgstr "" - -#. Tag: entry -#: hardware.xml:114 -#, no-c-format -msgid "Linksys NSLU2" -msgstr "" - -#. Tag: entry -#: hardware.xml:115 -#, no-c-format -msgid "nslu2" -msgstr "" - -#. Tag: entry -#: hardware.xml:117 -#, no-c-format -msgid "RiscPC and Riscstation" -msgstr "" - -#. Tag: entry -#: hardware.xml:118 -#, no-c-format -msgid "riscpc" -msgstr "" - -#. Tag: entry -#: hardware.xml:122 -#, no-c-format -msgid "IBM/Motorola PowerPC" -msgstr "" - -#. Tag: entry -#: hardware.xml:123 -#, no-c-format -msgid "<entry>powerpc</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:124 -#, no-c-format -msgid "CHRP" -msgstr "" - -#. Tag: entry -#: hardware.xml:125 -#, no-c-format -msgid "chrp" -msgstr "" - -#. Tag: entry -#: hardware.xml:127 -#, no-c-format -msgid "PowerMac" -msgstr "" - -#. Tag: entry -#: hardware.xml:128 -#, no-c-format -msgid "pmac" -msgstr "" - -#. Tag: entry -#: hardware.xml:130 -#, no-c-format -msgid "PReP" -msgstr "" - -#. Tag: entry -#: hardware.xml:131 -#, no-c-format -msgid "prep" -msgstr "" - -#. Tag: entry -#: hardware.xml:133 -#, no-c-format -msgid "APUS" -msgstr "" - -#. Tag: entry -#: hardware.xml:134 -#, no-c-format -msgid "<entry>apus</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:138 -#, no-c-format -msgid "HP PA-RISC" -msgstr "" - -#. Tag: entry -#: hardware.xml:139 -#, no-c-format -msgid "hppa" -msgstr "" - -#. Tag: entry -#: hardware.xml:140 -#, no-c-format -msgid "PA-RISC 1.1" -msgstr "" - -#. Tag: entry -#: hardware.xml:141 -#, no-c-format -msgid "<entry>32</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:143 -#, no-c-format -msgid "PA-RISC 2.0" -msgstr "" - -#. Tag: entry -#: hardware.xml:144 -#, no-c-format -msgid "<entry>64</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:148 -#, no-c-format -msgid "Intel ia64-based" -msgstr "" - -#. Tag: entry -#: hardware.xml:149 -#, no-c-format -msgid "ia64" -msgstr "" - -#. Tag: entry -#: hardware.xml:155 -#, no-c-format -msgid "MIPS (big endian)" -msgstr "" - -#. Tag: entry -#: hardware.xml:156 -#, no-c-format -msgid "mips" -msgstr "" - -#. Tag: entry -#: hardware.xml:157 -#, no-c-format -msgid "SGI IP22 (Indy/Indigo 2)" -msgstr "" - -#. Tag: entry -#: hardware.xml:158 -#, no-c-format -msgid "r4k-ip22" -msgstr "" - -#. Tag: entry -#: hardware.xml:160 -#, no-c-format -msgid "r5k-ip22" -msgstr "" - -#. Tag: entry -#: hardware.xml:162 -#, no-c-format -msgid "SGI IP32 (O2)" -msgstr "" - -#. Tag: entry -#: hardware.xml:163 -#, no-c-format -msgid "r5k-ip32" -msgstr "" - -#. Tag: entry -#: hardware.xml:165 hardware.xml:183 -#, no-c-format -msgid "Broadcom BCM91250A (SWARM)" -msgstr "" - -#. Tag: entry -#: hardware.xml:166 hardware.xml:184 -#, no-c-format -msgid "sb1-bcm91250a" -msgstr "" - -#. Tag: entry -#: hardware.xml:168 hardware.xml:186 -#, no-c-format -msgid "Broadcom BCM91480B (BigSur)" -msgstr "" - -#. Tag: entry -#: hardware.xml:169 hardware.xml:187 -#, no-c-format -msgid "sb1a-bcm91480b" -msgstr "" - -#. Tag: entry -#: hardware.xml:173 -#, no-c-format -msgid "MIPS (little endian)" -msgstr "" - -#. Tag: entry -#: hardware.xml:174 -#, no-c-format -msgid "mipsel" -msgstr "" - -#. Tag: entry -#: hardware.xml:175 -#, no-c-format -msgid "Cobalt" -msgstr "" - -#. Tag: entry -#: hardware.xml:176 -#, no-c-format -msgid "cobalt" -msgstr "" - -#. Tag: entry -#: hardware.xml:178 -#, no-c-format -msgid "DECstation" -msgstr "" - -#. Tag: entry -#: hardware.xml:179 hardware.xml:1023 hardware.xml:1038 hardware.xml:1048 -#, no-c-format -msgid "r4k-kn04" -msgstr "" - -#. Tag: entry -#: hardware.xml:181 hardware.xml:1018 hardware.xml:1028 hardware.xml:1033 -#: hardware.xml:1043 -#, no-c-format -msgid "r3k-kn02" -msgstr "" - -#. Tag: entry -#: hardware.xml:191 -#, no-c-format -msgid "IBM S/390" -msgstr "" - -#. Tag: entry -#: hardware.xml:192 -#, no-c-format -msgid "s390" -msgstr "" - -#. Tag: entry -#: hardware.xml:193 -#, no-c-format -msgid "IPL from VM-reader and DASD" -msgstr "" - -#. Tag: entry -#: hardware.xml:194 -#, no-c-format -msgid "generic" -msgstr "" - -#. Tag: entry -#: hardware.xml:196 -#, no-c-format -msgid "IPL from tape" -msgstr "" - -#. Tag: entry -#: hardware.xml:197 -#, no-c-format -msgid "tape" -msgstr "" - -#. Tag: para -#: hardware.xml:202 -#, no-c-format -msgid "" -"This document covers installation for the <emphasis>&arch-title;</emphasis> " -"architecture. If you are looking for information on any of the other Debian-" -"supported architectures take a look at the <ulink url=\"http://www.debian." -"org/ports/\">Debian-Ports</ulink> pages." -msgstr "" - -#. Tag: para -#: hardware.xml:210 -#, no-c-format -msgid "" -"This is the first official release of &debian; for the &arch-title; " -"architecture. We feel that it has proven itself sufficiently to be released. " -"However, because it has not had the exposure (and hence testing by users) " -"that some other architectures have had, you may encounter a few bugs. Use " -"our <ulink url=\"&url-bts;\">Bug Tracking System</ulink> to report any " -"problems; make sure to mention the fact that the bug is on the &arch-title; " -"platform. It can be necessary to use the <ulink url=\"&url-list-subscribe;" -"\">debian-&arch-listname; mailing list</ulink> as well." -msgstr "" - -#. Tag: title -#: hardware.xml:233 hardware.xml:692 hardware.xml:781 hardware.xml:800 -#: hardware.xml:843 hardware.xml:885 hardware.xml:953 hardware.xml:1112 -#: hardware.xml:1518 -#, no-c-format -msgid "CPU, Main Boards, and Video Support" -msgstr "" - -#. Tag: para -#: hardware.xml:234 -#, no-c-format -msgid "" -"Complete information regarding supported DEC Alphas can be found at <ulink " -"url=\"&url-alpha-howto;\">Linux Alpha HOWTO</ulink>. The purpose of this " -"section is to describe the systems supported by the boot disks." -msgstr "" - -#. Tag: para -#: hardware.xml:241 -#, no-c-format -msgid "" -"Alpha machines are subdivided into different system types because there are " -"a number of generations of motherboard and supporting chipsets. Different " -"systems (<quote>sub-architectures</quote>) often have radically different " -"engineering and capabilities. Therefore, the process of installing and, more " -"to the point, booting, can vary from system to system." -msgstr "" - -#. Tag: para -#: hardware.xml:249 -#, no-c-format -msgid "" -"The following table lists the system types supported by the Debian " -"installation system. The table also indicates the <emphasis>code name</" -"emphasis> for these system types. You'll need to know this code name when " -"you actually begin the installation process:" -msgstr "" - -#. Tag: entry -#: hardware.xml:266 -#, no-c-format -msgid "Hardware Type" -msgstr "" - -#. Tag: entry -#: hardware.xml:267 -#, no-c-format -msgid "Aliases" -msgstr "" - -#. Tag: entry -#: hardware.xml:267 -#, no-c-format -msgid "MILO image" -msgstr "" - -#. Tag: entry -#: hardware.xml:273 -#, no-c-format -msgid "ALCOR" -msgstr "" - -#. Tag: entry -#: hardware.xml:274 -#, no-c-format -msgid "AlphaStation 500 5/266.300" -msgstr "" - -#. Tag: entry -#: hardware.xml:275 -#, no-c-format -msgid "Maverick" -msgstr "" - -#. Tag: entry -#: hardware.xml:276 hardware.xml:280 hardware.xml:284 -#, no-c-format -msgid "alcor" -msgstr "" - -#. Tag: entry -#: hardware.xml:278 -#, no-c-format -msgid "AlphaStation 500 5/333...500" -msgstr "" - -#. Tag: entry -#: hardware.xml:279 -#, no-c-format -msgid "Bret" -msgstr "" - -#. Tag: entry -#: hardware.xml:282 -#, no-c-format -msgid "AlphaStation 600/266...300" -msgstr "" - -#. Tag: entry -#: hardware.xml:283 -#, no-c-format -msgid "Alcor" -msgstr "" - -#. Tag: entry -#: hardware.xml:286 -#, no-c-format -msgid "AlphaStation 600/300...433" -msgstr "" - -#. Tag: entry -#: hardware.xml:287 -#, no-c-format -msgid "<entry>XLT</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:288 -#, no-c-format -msgid "<entry>xlt</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:292 -#, no-c-format -msgid "BOOK1" -msgstr "" - -#. Tag: entry -#: hardware.xml:293 -#, no-c-format -msgid "AlphaBook1 (laptop)" -msgstr "" - -#. Tag: entry -#: hardware.xml:294 -#, no-c-format -msgid "Alphabook1/Burns" -msgstr "" - -#. Tag: entry -#: hardware.xml:295 -#, no-c-format -msgid "book1" -msgstr "" - -#. Tag: entry -#: hardware.xml:299 -#, no-c-format -msgid "AVANTI" -msgstr "" - -#. Tag: entry -#: hardware.xml:300 -#, no-c-format -msgid "AlphaStation 200 4/100...166" -msgstr "" - -#. Tag: entry -#: hardware.xml:301 -#, no-c-format -msgid "Mustang" -msgstr "" - -#. Tag: entry -#: hardware.xml:302 hardware.xml:306 hardware.xml:310 hardware.xml:314 -#: hardware.xml:318 hardware.xml:322 hardware.xml:326 hardware.xml:330 -#, no-c-format -msgid "avanti" -msgstr "" - -#. Tag: entry -#: hardware.xml:304 -#, no-c-format -msgid "AlphaStation 200 4/233" -msgstr "" - -#. Tag: entry -#: hardware.xml:305 -#, no-c-format -msgid "Mustang+" -msgstr "" - -#. Tag: entry -#: hardware.xml:308 -#, no-c-format -msgid "AlphaStation 205 4/133...333" -msgstr "" - -#. Tag: entry -#: hardware.xml:309 -#, no-c-format -msgid "<entry>LX3</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:312 -#, no-c-format -msgid "AlphaStation 250 4/300" -msgstr "" - -#. Tag: entry -#: hardware.xml:313 -#, no-c-format -msgid "<entry>M3+</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:316 -#, no-c-format -msgid "AlphaStation 255 4/133...333" -msgstr "" - -#. Tag: entry -#: hardware.xml:317 -#, no-c-format -msgid "LX3+" -msgstr "" - -#. Tag: entry -#: hardware.xml:320 -#, no-c-format -msgid "AlphaStation 300 4/266" -msgstr "" - -#. Tag: entry -#: hardware.xml:321 -#, no-c-format -msgid "Melmac" -msgstr "" - -#. Tag: entry -#: hardware.xml:324 -#, no-c-format -msgid "AlphaStation 400 4/166" -msgstr "" - -#. Tag: entry -#: hardware.xml:325 -#, no-c-format -msgid "Chinet" -msgstr "" - -#. Tag: entry -#: hardware.xml:328 -#, no-c-format -msgid "AlphaStation 400 4/233...300" -msgstr "" - -#. Tag: entry -#: hardware.xml:329 -#, no-c-format -msgid "Avanti" -msgstr "" - -#. Tag: entry -#: hardware.xml:334 hardware.xml:347 hardware.xml:348 -#, no-c-format -msgid "EB164" -msgstr "" - -#. Tag: entry -#: hardware.xml:335 -#, no-c-format -msgid "AlphaPC164" -msgstr "" - -#. Tag: entry -#: hardware.xml:336 -#, no-c-format -msgid "PC164" -msgstr "" - -#. Tag: entry -#: hardware.xml:337 -#, no-c-format -msgid "pc164" -msgstr "" - -#. Tag: entry -#: hardware.xml:339 -#, no-c-format -msgid "AlphaPC164-LX" -msgstr "" - -#. Tag: entry -#: hardware.xml:340 -#, no-c-format -msgid "LX164" -msgstr "" - -#. Tag: entry -#: hardware.xml:341 -#, no-c-format -msgid "lx164" -msgstr "" - -#. Tag: entry -#: hardware.xml:343 -#, no-c-format -msgid "AlphaPC164-SX" -msgstr "" - -#. Tag: entry -#: hardware.xml:344 -#, no-c-format -msgid "SX164" -msgstr "" - -#. Tag: entry -#: hardware.xml:345 -#, no-c-format -msgid "sx164" -msgstr "" - -#. Tag: entry -#: hardware.xml:349 -#, no-c-format -msgid "eb164" -msgstr "" - -#. Tag: entry -#: hardware.xml:353 hardware.xml:362 hardware.xml:363 -#, no-c-format -msgid "EB64+" -msgstr "" - -#. Tag: entry -#: hardware.xml:354 -#, no-c-format -msgid "AlphaPC64" -msgstr "" - -#. Tag: entry -#: hardware.xml:355 hardware.xml:359 -#, no-c-format -msgid "Cabriolet" -msgstr "" - -#. Tag: entry -#: hardware.xml:356 hardware.xml:360 -#, no-c-format -msgid "cabriolet" -msgstr "" - -#. Tag: entry -#: hardware.xml:358 -#, no-c-format -msgid "AlphaPCI64" -msgstr "" - -#. Tag: entry -#: hardware.xml:364 -#, no-c-format -msgid "eb64p" -msgstr "" - -#. Tag: entry -#: hardware.xml:368 hardware.xml:369 hardware.xml:370 -#, no-c-format -msgid "EB66" -msgstr "" - -#. Tag: entry -#: hardware.xml:371 -#, no-c-format -msgid "eb66" -msgstr "" - -#. Tag: entry -#: hardware.xml:373 hardware.xml:374 -#, no-c-format -msgid "EB66+" -msgstr "" - -#. Tag: entry -#: hardware.xml:375 -#, no-c-format -msgid "eb66p" -msgstr "" - -#. Tag: entry -#: hardware.xml:379 -#, no-c-format -msgid "JENSEN" -msgstr "" - -#. Tag: entry -#: hardware.xml:380 -#, no-c-format -msgid "DEC 2000 Model 300(S)" -msgstr "" - -#. Tag: entry -#: hardware.xml:381 hardware.xml:389 -#, no-c-format -msgid "Jensen" -msgstr "" - -#. Tag: entry -#: hardware.xml:382 hardware.xml:386 hardware.xml:390 hardware.xml:451 -#: hardware.xml:455 hardware.xml:473 hardware.xml:477 hardware.xml:481 -#: hardware.xml:485 hardware.xml:489 hardware.xml:493 hardware.xml:497 -#: hardware.xml:511 hardware.xml:515 hardware.xml:519 hardware.xml:523 -#: hardware.xml:527 hardware.xml:561 hardware.xml:565 hardware.xml:569 -#: hardware.xml:573 hardware.xml:587 hardware.xml:591 hardware.xml:595 -#: hardware.xml:599 hardware.xml:606 hardware.xml:610 hardware.xml:614 -#: hardware.xml:618 hardware.xml:622 hardware.xml:626 hardware.xml:630 -#: hardware.xml:634 hardware.xml:638 hardware.xml:642 hardware.xml:646 -#: hardware.xml:650 hardware.xml:654 hardware.xml:661 hardware.xml:665 -#, no-c-format -msgid "<entry>N/A</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:384 -#, no-c-format -msgid "DEC 2000 Model 500" -msgstr "" - -#. Tag: entry -#: hardware.xml:385 -#, no-c-format -msgid "Culzen" -msgstr "" - -#. Tag: entry -#: hardware.xml:388 -#, no-c-format -msgid "DECpc 150" -msgstr "" - -#. Tag: entry -#: hardware.xml:394 -#, no-c-format -msgid "MIATA" -msgstr "" - -#. Tag: entry -#: hardware.xml:395 -#, no-c-format -msgid "Personal WorkStation 433a" -msgstr "" - -#. Tag: entry -#: hardware.xml:396 hardware.xml:400 hardware.xml:404 hardware.xml:408 -#: hardware.xml:412 hardware.xml:416 hardware.xml:420 hardware.xml:424 -#, no-c-format -msgid "Miata" -msgstr "" - -#. Tag: entry -#: hardware.xml:397 hardware.xml:401 hardware.xml:405 hardware.xml:409 -#: hardware.xml:413 hardware.xml:417 hardware.xml:421 hardware.xml:425 -#, no-c-format -msgid "miata" -msgstr "" - -#. Tag: entry -#: hardware.xml:399 -#, no-c-format -msgid "Personal WorkStation 433au" -msgstr "" - -#. Tag: entry -#: hardware.xml:403 -#, no-c-format -msgid "Personal WorkStation 466au" -msgstr "" - -#. Tag: entry -#: hardware.xml:407 -#, no-c-format -msgid "Personal WorkStation 500a" -msgstr "" - -#. Tag: entry -#: hardware.xml:411 -#, no-c-format -msgid "Personal WorkStation 500au" -msgstr "" - -#. Tag: entry -#: hardware.xml:415 -#, no-c-format -msgid "Personal WorkStation 550au" -msgstr "" - -#. Tag: entry -#: hardware.xml:419 -#, no-c-format -msgid "Personal WorkStation 600a" -msgstr "" - -#. Tag: entry -#: hardware.xml:423 -#, no-c-format -msgid "Personal WorkStation 600au" -msgstr "" - -#. Tag: entry -#: hardware.xml:429 -#, no-c-format -msgid "MIKASA" -msgstr "" - -#. Tag: entry -#: hardware.xml:430 -#, no-c-format -msgid "AlphaServer 1000 4/200" -msgstr "" - -#. Tag: entry -#: hardware.xml:431 -#, no-c-format -msgid "Mikasa" -msgstr "" - -#. Tag: entry -#: hardware.xml:432 hardware.xml:436 hardware.xml:440 hardware.xml:444 -#, no-c-format -msgid "mikasa" -msgstr "" - -#. Tag: entry -#: hardware.xml:434 -#, no-c-format -msgid "AlphaServer 1000 4/233..266" -msgstr "" - -#. Tag: entry -#: hardware.xml:435 -#, no-c-format -msgid "Mikasa+" -msgstr "" - -#. Tag: entry -#: hardware.xml:438 hardware.xml:442 -#, no-c-format -msgid "AlphaServer 1000 5/300" -msgstr "" - -#. Tag: entry -#: hardware.xml:439 -#, no-c-format -msgid "Mikasa-Pinnacle" -msgstr "" - -#. Tag: entry -#: hardware.xml:443 -#, no-c-format -msgid "Mikasa-Primo" -msgstr "" - -#. Tag: entry -#: hardware.xml:448 -#, no-c-format -msgid "NAUTILUS" -msgstr "" - -#. Tag: entry -#: hardware.xml:449 -#, no-c-format -msgid "UP1000" -msgstr "" - -#. Tag: entry -#: hardware.xml:450 -#, no-c-format -msgid "Nautilus" -msgstr "" - -#. Tag: entry -#: hardware.xml:453 -#, no-c-format -msgid "UP1100" -msgstr "" - -#. Tag: entry -#: hardware.xml:454 -#, no-c-format -msgid "Galaxy-Train/Nautilus Jr." -msgstr "" - -#. Tag: entry -#: hardware.xml:459 -#, no-c-format -msgid "NONAME" -msgstr "" - -#. Tag: entry -#: hardware.xml:460 -#, no-c-format -msgid "AXPpci33" -msgstr "" - -#. Tag: entry -#: hardware.xml:461 -#, no-c-format -msgid "Noname" -msgstr "" - -#. Tag: entry -#: hardware.xml:462 hardware.xml:466 -#, no-c-format -msgid "noname" -msgstr "" - -#. Tag: entry -#: hardware.xml:464 -#, no-c-format -msgid "<entry>UDB</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:465 -#, no-c-format -msgid "Multia" -msgstr "" - -#. Tag: entry -#: hardware.xml:470 -#, no-c-format -msgid "NORITAKE" -msgstr "" - -#. Tag: entry -#: hardware.xml:471 -#, no-c-format -msgid "AlphaServer 1000A 4/233...266" -msgstr "" - -#. Tag: entry -#: hardware.xml:472 -#, no-c-format -msgid "Noritake" -msgstr "" - -#. Tag: entry -#: hardware.xml:475 -#, no-c-format -msgid "AlphaServer 1000A 5/300" -msgstr "" - -#. Tag: entry -#: hardware.xml:476 -#, no-c-format -msgid "Noritake-Pinnacle" -msgstr "" - -#. Tag: entry -#: hardware.xml:479 -#, no-c-format -msgid "AlphaServer 1000A 5/333...500" -msgstr "" - -#. Tag: entry -#: hardware.xml:480 -#, no-c-format -msgid "Noritake-Primo" -msgstr "" - -#. Tag: entry -#: hardware.xml:483 -#, no-c-format -msgid "AlphaServer 800 5/333...500" -msgstr "" - -#. Tag: entry -#: hardware.xml:484 hardware.xml:492 hardware.xml:496 -#, no-c-format -msgid "Corelle" -msgstr "" - -#. Tag: entry -#: hardware.xml:487 -#, no-c-format -msgid "AlphaStation 600 A" -msgstr "" - -#. Tag: entry -#: hardware.xml:488 -#, no-c-format -msgid "Alcor-Primo" -msgstr "" - -#. Tag: entry -#: hardware.xml:491 -#, no-c-format -msgid "Digital Server 3300" -msgstr "" - -#. Tag: entry -#: hardware.xml:495 -#, no-c-format -msgid "Digital Server 3300R" -msgstr "" - -#. Tag: entry -#: hardware.xml:501 -#, no-c-format -msgid "PLATFORM 2000" -msgstr "" - -#. Tag: entry -#: hardware.xml:502 hardware.xml:503 -#, no-c-format -msgid "<entry>P2K</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:504 -#, no-c-format -msgid "<entry>p2k</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:508 -#, no-c-format -msgid "RAWHIDE" -msgstr "" - -#. Tag: entry -#: hardware.xml:509 -#, no-c-format -msgid "AlphaServer 1200 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:510 hardware.xml:522 -#, no-c-format -msgid "Tincup/DaVinci" -msgstr "" - -#. Tag: entry -#: hardware.xml:513 -#, no-c-format -msgid "AlphaServer 4000 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:514 -#, no-c-format -msgid "Wrangler/Durango" -msgstr "" - -#. Tag: entry -#: hardware.xml:517 -#, no-c-format -msgid "AlphaServer 4100 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:518 hardware.xml:526 -#, no-c-format -msgid "Dodge" -msgstr "" - -#. Tag: entry -#: hardware.xml:521 -#, no-c-format -msgid "Digital Server 5300" -msgstr "" - -#. Tag: entry -#: hardware.xml:525 -#, no-c-format -msgid "Digital Server 7300" -msgstr "" - -#. Tag: entry -#: hardware.xml:531 -#, no-c-format -msgid "RUFFIAN" -msgstr "" - -#. Tag: entry -#: hardware.xml:532 -#, no-c-format -msgid "DeskStation AlphaPC164-UX" -msgstr "" - -#. Tag: entry -#: hardware.xml:533 hardware.xml:537 hardware.xml:541 hardware.xml:545 -#: hardware.xml:549 hardware.xml:553 -#, no-c-format -msgid "Ruffian" -msgstr "" - -#. Tag: entry -#: hardware.xml:534 hardware.xml:538 hardware.xml:542 hardware.xml:546 -#: hardware.xml:550 hardware.xml:554 -#, no-c-format -msgid "ruffian" -msgstr "" - -#. Tag: entry -#: hardware.xml:536 -#, no-c-format -msgid "DeskStation RPL164-2" -msgstr "" - -#. Tag: entry -#: hardware.xml:540 -#, no-c-format -msgid "DeskStation RPL164-4" -msgstr "" - -#. Tag: entry -#: hardware.xml:544 -#, no-c-format -msgid "DeskStation RPX164-2" -msgstr "" - -#. Tag: entry -#: hardware.xml:548 -#, no-c-format -msgid "DeskStation RPX164-4" -msgstr "" - -#. Tag: entry -#: hardware.xml:552 -#, no-c-format -msgid "Samsung AlphaPC164-BX" -msgstr "" - -#. Tag: entry -#: hardware.xml:558 -#, no-c-format -msgid "SABLE" -msgstr "" - -#. Tag: entry -#: hardware.xml:559 -#, no-c-format -msgid "AlphaServer 2000 4/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:560 -#, no-c-format -msgid "Demi-Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:563 -#, no-c-format -msgid "AlphaServer 2000 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:564 -#, no-c-format -msgid "Demi-Gamma-Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:567 -#, no-c-format -msgid "AlphaServer 2100 4/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:568 -#, no-c-format -msgid "Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:571 -#, no-c-format -msgid "AlphaServer 2100 5/xxx" -msgstr "" - -#. Tag: entry -#: hardware.xml:572 -#, no-c-format -msgid "Gamma-Sable" -msgstr "" - -#. Tag: entry -#: hardware.xml:577 -#, no-c-format -msgid "TAKARA" -msgstr "" - -#. Tag: entry -#: hardware.xml:578 -#, no-c-format -msgid "21164 PICMG SBC" -msgstr "" - -#. Tag: entry -#: hardware.xml:579 -#, no-c-format -msgid "Takara" -msgstr "" - -#. Tag: entry -#: hardware.xml:580 -#, no-c-format -msgid "takara" -msgstr "" - -#. Tag: entry -#: hardware.xml:584 -#, no-c-format -msgid "TITAN" -msgstr "" - -#. Tag: entry -#: hardware.xml:585 -#, no-c-format -msgid "AlphaServer DS15" -msgstr "" - -#. Tag: entry -#: hardware.xml:586 -#, no-c-format -msgid "HyperBrick2" -msgstr "" - -#. Tag: entry -#: hardware.xml:589 -#, no-c-format -msgid "AlphaServer DS25" -msgstr "" - -#. Tag: entry -#: hardware.xml:590 -#, no-c-format -msgid "Granite" -msgstr "" - -#. Tag: entry -#: hardware.xml:593 -#, no-c-format -msgid "AlphaServer ES45" -msgstr "" - -#. Tag: entry -#: hardware.xml:594 -#, no-c-format -msgid "Privateer" -msgstr "" - -#. Tag: entry -#: hardware.xml:597 hardware.xml:636 hardware.xml:640 -#, no-c-format -msgid "UNKNOWN" -msgstr "" - -#. Tag: entry -#: hardware.xml:598 -#, no-c-format -msgid "Yukon" -msgstr "" - -#. Tag: entry -#: hardware.xml:603 -#, no-c-format -msgid "TSUNAMI" -msgstr "" - -#. Tag: entry -#: hardware.xml:604 -#, no-c-format -msgid "AlphaServer DS10" -msgstr "" - -#. Tag: entry -#: hardware.xml:605 hardware.xml:653 -#, no-c-format -msgid "Webbrick" -msgstr "" - -#. Tag: entry -#: hardware.xml:608 -#, no-c-format -msgid "AlphaServer DS10L" -msgstr "" - -#. Tag: entry -#: hardware.xml:609 -#, no-c-format -msgid "Slate" -msgstr "" - -#. Tag: entry -#: hardware.xml:612 -#, no-c-format -msgid "AlphaServer DS20" -msgstr "" - -#. Tag: entry -#: hardware.xml:613 -#, no-c-format -msgid "Catamaran/Goldrush" -msgstr "" - -#. Tag: entry -#: hardware.xml:616 -#, no-c-format -msgid "AlphaServer DS20E" -msgstr "" - -#. Tag: entry -#: hardware.xml:617 -#, no-c-format -msgid "Goldrack" -msgstr "" - -#. Tag: entry -#: hardware.xml:620 -#, no-c-format -msgid "AlphaServer DS20L" -msgstr "" - -#. Tag: entry -#: hardware.xml:621 -#, no-c-format -msgid "Shark" -msgstr "" - -#. Tag: entry -#: hardware.xml:624 -#, no-c-format -msgid "AlphaServer ES40" -msgstr "" - -#. Tag: entry -#: hardware.xml:625 -#, no-c-format -msgid "Clipper" -msgstr "" - -#. Tag: entry -#: hardware.xml:628 hardware.xml:629 -#, no-c-format -msgid "DP264" -msgstr "" - -#. Tag: entry -#: hardware.xml:632 -#, no-c-format -msgid "SMARTengine 21264 PCI/ISA SBC" -msgstr "" - -#. Tag: entry -#: hardware.xml:633 -#, no-c-format -msgid "Eiger" -msgstr "" - -#. Tag: entry -#: hardware.xml:637 -#, no-c-format -msgid "Warhol" -msgstr "" - -#. Tag: entry -#: hardware.xml:641 -#, no-c-format -msgid "Windjammer" -msgstr "" - -#. Tag: entry -#: hardware.xml:644 -#, no-c-format -msgid "UP2000" -msgstr "" - -#. Tag: entry -#: hardware.xml:645 -#, no-c-format -msgid "Swordfish" -msgstr "" - -#. Tag: entry -#: hardware.xml:648 -#, no-c-format -msgid "XP1000" -msgstr "" - -#. Tag: entry -#: hardware.xml:649 -#, no-c-format -msgid "Monet/Brisbane" -msgstr "" - -#. Tag: entry -#: hardware.xml:652 -#, no-c-format -msgid "XP900" -msgstr "" - -#. Tag: entry -#: hardware.xml:658 -#, no-c-format -msgid "WILDFIRE" -msgstr "" - -#. Tag: entry -#: hardware.xml:659 -#, no-c-format -msgid "AlphaServer GS160" -msgstr "" - -#. Tag: entry -#: hardware.xml:660 hardware.xml:664 -#, no-c-format -msgid "Wildfire" -msgstr "" - -#. Tag: entry -#: hardware.xml:663 -#, no-c-format -msgid "AlphaServer GS320" -msgstr "" - -#. Tag: entry -#: hardware.xml:669 hardware.xml:671 -#, no-c-format -msgid "<entry>XL</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:670 -#, no-c-format -msgid "XL-233...266" -msgstr "" - -#. Tag: entry -#: hardware.xml:672 -#, no-c-format -msgid "<entry>xl</entry>" -msgstr "" - -#. Tag: para -#: hardware.xml:677 -#, no-c-format -msgid "" -"It is believed that Debian &releasename; supports installing on all alpha " -"sub-architectures with the exception of the ARC-only Ruffian and XL sub-" -"architectures and the Titan subarchitecture, which requires a change to the " -"kernel compile options." -msgstr "" - -#. Tag: para -#: hardware.xml:694 -#, no-c-format -msgid "" -"Each distinct ARM architecture requires its own kernel. Because of this the " -"standard Debian distribution only supports installation on a number of the " -"most common systems. The Debian userland however may be used by " -"<emphasis>any</emphasis> ARM CPU including xscale." -msgstr "" - -#. Tag: para -#: hardware.xml:702 -#, no-c-format -msgid "" -"Most ARM CPUs may be run in either endian mode (big or little). However, the " -"majority of current system implementation uses little-endian mode. Debian " -"currently only supports little-endian ARM systems." -msgstr "" - -#. Tag: para -#: hardware.xml:710 -#, no-c-format -msgid "The supported systems are:" -msgstr "" - -#. Tag: term -#: hardware.xml:717 -#, no-c-format -msgid "Netwinder" -msgstr "" - -#. Tag: para -#: hardware.xml:718 -#, no-c-format -msgid "" -"This is actually the name for the group of machines based upon the StrongARM " -"110 CPU and Intel 21285 Northbridge (also known as Footbridge). It comprises " -"of machines like: Netwinder (possibly one of the most common ARM boxes), " -"CATS (also known as the EB110ATX), EBSA 285 and Compaq personal server (cps, " -"aka skiff)." -msgstr "" - -#. Tag: term -#: hardware.xml:731 -#, no-c-format -msgid "NSLU2" -msgstr "" - -#. Tag: para -#: hardware.xml:732 -#, no-c-format -msgid "" -"The Linksys NSLU2 (Network Storage Link for USB 2.0 Disk Drives) is a small " -"device which allows you to easily provide storage via the network. It comes " -"with an Ethernet connection and two USB ports to which hard drives can be " -"connected." -msgstr "" - -#. Tag: term -#: hardware.xml:743 -#, no-c-format -msgid "RiscPC" -msgstr "" - -#. Tag: para -#: hardware.xml:744 -#, no-c-format -msgid "" -"This machine is the oldest supported hardware: it was released in 1994. It " -"has RISC OS in ROM, Linux can be booted from that OS using linloader. The " -"RiscPC has a modular CPU card and typically has a 30MHz 610, 40MHz 710 or " -"233MHz Strongarm 110 CPU fitted. The mainboard has integrated IDE, SVGA " -"video, parallel port, single serial port, PS/2 keyboard and proprietary " -"mouse port. The proprietary module expansion bus allows for up to eight " -"expansion cards to be fitted depending on configuration, several of these " -"modules have Linux drivers." -msgstr "" - -#. Tag: term -#: hardware.xml:759 -#, no-c-format -msgid "Riscstation" -msgstr "" - -#. Tag: para -#: hardware.xml:760 -#, no-c-format -msgid "" -"This is an inexpensive 56MHz 7500FE based machine with integrated video, " -"IDE, PS/2 keyboard and mouse and two serial ports. Its lack of processing " -"power was made up for by its price. It may be found in two configurations " -"one with RISC OS and one with a simple bootloader." -msgstr "" - -#. Tag: para -#: hardware.xml:782 -#, no-c-format -msgid "" -"The are two major support <emphasis>&architecture;</emphasis> flavors: PA-" -"RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit " -"processors whereas the 2.0 architecture is targeted to the 64-bit " -"processors. Some systems are able to run either kernel. In both cases, the " -"userland is 32-bit. There is the possibility of a 64-bit userland in the " -"future." -msgstr "" - -#. Tag: para -#: hardware.xml:801 -#, no-c-format -msgid "" -"Complete information concerning supported peripherals can be found at <ulink " -"url=\"&url-hardware-howto;\">Linux Hardware Compatibility HOWTO</ulink>. " -"This section merely outlines the basics." -msgstr "" - -#. Tag: title -#: hardware.xml:809 hardware.xml:926 -#, no-c-format -msgid "<title>CPU</title>" -msgstr "" - -#. Tag: para -#: hardware.xml:810 -#, no-c-format -msgid "" -"Nearly all x86-based processors are supported; this includes AMD and VIA " -"(former Cyrix) processors as well. Also the new processors like Athlon XP " -"and Intel P4 Xeon are supported. However, Linux will <emphasis>not</" -"emphasis> run on 286 or earlier processors." -msgstr "" - -#. Tag: title -#: hardware.xml:820 -#, no-c-format -msgid "I/O Bus" -msgstr "" - -#. Tag: para -#: hardware.xml:821 -#, no-c-format -msgid "" -"The system bus is the part of the motherboard which allows the CPU to " -"communicate with peripherals such as storage devices. Your computer must use " -"the ISA, EISA, PCI, the Microchannel Architecture (MCA, used in IBM's PS/2 " -"line), or VESA Local Bus (VLB, sometimes called the VL bus)." -msgstr "" - -#. Tag: para -#: hardware.xml:844 -#, no-c-format -msgid "" -"Complete information concerning supported M68000 based " -"(<emphasis>&architecture;</emphasis>) systems can be found at the <ulink url=" -"\"&url-m68k-faq;\">Linux/m68k FAQ</ulink>. This section merely outlines the " -"basics." -msgstr "" - -#. Tag: para -#: hardware.xml:851 -#, no-c-format -msgid "" -"The &architecture; port of Linux runs on any 680x0 with a PMMU (Paged Memory " -"Management Unit) and a FPU (floating-point unit). This includes the 68020 " -"with an external 68851 PMMU, the 68030, and better, and excludes the " -"<quote>EC</quote> line of 680x0 processors. See the <ulink url=\"&url-m68k-" -"faq;\">Linux/m68k FAQ</ulink> for complete details." -msgstr "" - -#. Tag: para -#: hardware.xml:859 -#, no-c-format -msgid "" -"There are four major flavors of supported <emphasis>&architecture;</" -"emphasis> flavors: Amiga, Atari, Macintosh and VME machines. Amiga and Atari " -"were the first two systems to which Linux was ported; in keeping, they are " -"also the two most well-supported Debian ports. The Macintosh line is " -"supported incompletely, both by Debian and by the Linux kernel; see <ulink " -"url=\"&url-m68k-mac;\">Linux m68k for Macintosh</ulink> for project status " -"and supported hardware. The BVM and Motorola single board VMEbus computers " -"are the most recent addition to the list of machines supported by Debian. " -"Ports to other &architecture; architectures, such as the Sun3 architecture " -"and NeXT black box, are underway but not yet supported by Debian." -msgstr "" - -#. Tag: para -#: hardware.xml:886 -#, no-c-format -msgid "" -"Debian on &arch-title; supports the following platforms: <itemizedlist> " -"<listitem><para> SGI IP22: this platform includes the SGI machines Indy, " -"Indigo 2 and Challenge S. Since these machines are very similar, whenever " -"this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant " -"as well. </para></listitem> <listitem><para> SGI IP32: this platform is " -"generally known as SGI O2. </para></listitem> <listitem><para> Broadcom " -"BCM91250A (SWARM): this is an ATX form factor evaluation board from Broadcom " -"based on the dual-core SB1 1250 CPU. </para></listitem> <listitem><para> " -"Broadcom BCM91480B (BigSur): this is an ATX form factor evaluation board " -"from Broadcom based on the quad-core SB1A 1480 CPU. </para></listitem> </" -"itemizedlist> Complete information regarding supported mips/mipsel machines " -"can be found at the <ulink url=\"&url-linux-mips;\">Linux-MIPS homepage</" -"ulink>. In the following, only the systems supported by the Debian installer " -"will be covered. If you are looking for support for other subarchitectures, " -"please contact the <ulink url=\"&url-list-subscribe;\"> debian-&arch-" -"listname; mailing list</ulink>." -msgstr "" - -#. Tag: para -#: hardware.xml:927 -#, no-c-format -msgid "" -"On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and " -"R5000 processors are supported by the Debian installation system on big " -"endian MIPS. On SGI IP32, currently only systems based on the R5000 are " -"supported. The Broadcom BCM91250A evaluation board comes with an SB1 1250 " -"chip with two cores which are supported in SMP mode by this installer. " -"Similarly, the BCM91480B evaluation board contains an SB1A 1480 chip with " -"four cores which are supported in SMP mode." -msgstr "" - -#. Tag: para -#: hardware.xml:937 -#, no-c-format -msgid "" -"Some MIPS machines can be operated in both big and little endian mode. For " -"little endian MIPS, please read the documentation for the mipsel " -"architecture." -msgstr "" - -#. Tag: para -#: hardware.xml:954 -#, no-c-format -msgid "" -"Debian on &arch-title; supports the following platforms: <itemizedlist> " -"<listitem><para> DECstation: various models of the DECstation are supported. " -"</para></listitem> <listitem><para> Cobalt Microserver: only MIPS based " -"Cobalt machines are covered here. This includes the Cobalt Qube 2700 " -"(Qube1), RaQ, Qube2 and RaQ2, and the Gateway Microserver. </para></" -"listitem> <listitem><para> Broadcom BCM91250A (SWARM): this is an ATX form " -"factor evaluation board from Broadcom based on the dual-core SB1 1250 CPU. </" -"para></listitem> <listitem><para> Broadcom BCM91480B (BigSur): this is an " -"ATX form factor evaluation board from Broadcom based on the quad-core SB1A " -"1480 CPU. </para></listitem> </itemizedlist> Complete information regarding " -"supported mips/mipsel machines can be found at the <ulink url=\"&url-linux-" -"mips;\">Linux-MIPS homepage</ulink>. In the following, only the systems " -"supported by the Debian installer will be covered. If you are looking for " -"support for other subarchitectures, please contact the <ulink url=\"&url-" -"list-subscribe;\"> debian-&arch-listname; mailing list</ulink>." -msgstr "" - -#. Tag: title -#: hardware.xml:994 -#, no-c-format -msgid "CPU/Machine types" -msgstr "" - -#. Tag: para -#: hardware.xml:996 -#, no-c-format -msgid "" -"Currently only DECstations with R3000 and R4000/R4400 CPUs are supported by " -"the Debian installation system on little endian MIPS. The Debian " -"installation system works on the following machines:" -msgstr "" - -#. Tag: entry -#: hardware.xml:1008 -#, no-c-format -msgid "System Type" -msgstr "" - -#. Tag: entry -#: hardware.xml:1008 -#, no-c-format -msgid "<entry>CPU</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:1008 -#, no-c-format -msgid "Code-name" -msgstr "" - -#. Tag: entry -#: hardware.xml:1009 -#, no-c-format -msgid "Debian subarchitecture" -msgstr "" - -#. Tag: entry -#: hardware.xml:1015 -#, no-c-format -msgid "DECstation 5000/1xx" -msgstr "" - -#. Tag: entry -#: hardware.xml:1016 hardware.xml:1026 hardware.xml:1031 hardware.xml:1041 -#, no-c-format -msgid "R3000" -msgstr "" - -#. Tag: entry -#: hardware.xml:1017 hardware.xml:1022 -#, no-c-format -msgid "3MIN" -msgstr "" - -#. Tag: entry -#: hardware.xml:1020 -#, no-c-format -msgid "DECstation 5000/150" -msgstr "" - -#. Tag: entry -#: hardware.xml:1021 hardware.xml:1046 -#, no-c-format -msgid "R4000" -msgstr "" - -#. Tag: entry -#: hardware.xml:1025 -#, no-c-format -msgid "DECstation 5000/200" -msgstr "" - -#. Tag: entry -#: hardware.xml:1027 -#, no-c-format -msgid "3MAX" -msgstr "" - -#. Tag: entry -#: hardware.xml:1030 -#, no-c-format -msgid "DECstation 5000/240" -msgstr "" - -#. Tag: entry -#: hardware.xml:1032 hardware.xml:1037 -#, no-c-format -msgid "3MAX+" -msgstr "" - -#. Tag: entry -#: hardware.xml:1035 -#, no-c-format -msgid "DECstation 5000/260" -msgstr "" - -#. Tag: entry -#: hardware.xml:1036 -#, no-c-format -msgid "R4400" -msgstr "" - -#. Tag: entry -#: hardware.xml:1040 -#, no-c-format -msgid "Personal DECstation 5000/xx" -msgstr "" - -#. Tag: entry -#: hardware.xml:1042 hardware.xml:1047 -#, no-c-format -msgid "Maxine" -msgstr "" - -#. Tag: entry -#: hardware.xml:1045 -#, no-c-format -msgid "Personal DECstation 5000/50" -msgstr "" - -#. Tag: para -#: hardware.xml:1052 -#, no-c-format -msgid "" -"All Cobalt machines are supported. In the past, only machines with a serial " -"console were supported (that is, all machines except for the Qube 2700, aka " -"Qube1). However, installations are now also possible through SSH." -msgstr "" - -#. Tag: para -#: hardware.xml:1059 -#, no-c-format -msgid "" -"The Broadcom BCM91250A evaluation board comes with an SB1 1250 chip with two " -"cores which are supported in SMP mode by this installer. Similarly, the " -"BCM91480B evaluation board contains an SB1A 1480 chip with four cores which " -"are supported in SMP mode." -msgstr "" - -#. Tag: title -#: hardware.xml:1069 -#, no-c-format -msgid "Supported console options" -msgstr "" - -#. Tag: para -#: hardware.xml:1070 -#, no-c-format -msgid "" -"Serial console is available on all supported DECstations (9600 bps, 8N1). " -"For using serial console, you have to boot the installer image with the " -"<literal>console=ttyS</literal><replaceable>x</replaceable> kernel parameter " -"(with <replaceable>x</replaceable> being the number of the serial port you " -"have your terminal connected to — usually <literal>2</literal>, but " -"<literal>0</literal> for the Personal DECstations). On 3MIN and 3MAX+ " -"(DECstation 5000/1xx, 5000/240 and 5000/260) local console is available with " -"the PMAG-BA and the PMAGB-B graphics options." -msgstr "" - -#. Tag: para -#: hardware.xml:1081 -#, no-c-format -msgid "" -"If you have a Linux system to use as serial terminal, an easy way is to run " -"<command>cu</command><footnote> <para> In Woody this command was part of the " -"<classname>uucp</classname> package, but in later releases it is available " -"as a separate package. </para> </footnote> on it. Example: " -"<informalexample><screen>\n" -"$ cu -l /dev/ttyS1 -s 9600\n" -"</screen></informalexample> where the option <literal>-l</literal> (line) " -"sets the serial port to use and <literal>-s</literal> (speed) sets the speed " -"for the connection (9600 bits per second)." -msgstr "" - -#. Tag: para -#: hardware.xml:1099 -#, no-c-format -msgid "Both Cobalt and Broadcom BCM91250A/BCM91480B use 115200 bps." -msgstr "" - -#. Tag: para -#: hardware.xml:1113 -#, no-c-format -msgid "" -"There are four major supported <emphasis>&architecture;</emphasis> " -"subarchitectures: PMac (Power-Macintosh), PReP, APUS (Amiga Power-UP " -"System), and CHRP machines. Each subarchitecture has its own boot methods. " -"In addition, there are four different kernel flavours, supporting different " -"CPU variants." -msgstr "" - -#. Tag: para -#: hardware.xml:1121 -#, no-c-format -msgid "" -"Ports to other <emphasis>&architecture;</emphasis> architectures, such as " -"the Be-Box and MBX architecture, are underway but not yet supported by " -"Debian. We may have a 64-bit port in the future." -msgstr "" - -#. Tag: title -#: hardware.xml:1129 -#, no-c-format -msgid "Kernel Flavours" -msgstr "" - -#. Tag: para -#: hardware.xml:1131 -#, no-c-format -msgid "" -"There are four flavours of the powerpc kernel in Debian, based on the CPU " -"type:" -msgstr "" - -#. Tag: term -#: hardware.xml:1138 -#, no-c-format -msgid "<term>powerpc</term>" -msgstr "" - -#. Tag: para -#: hardware.xml:1139 -#, no-c-format -msgid "" -"Most systems use this kernel flavour, which supports the PowerPC 601, 603, " -"604, 740, 750, and 7400 processors. All Apple Power Macintosh systems up to " -"and including the G4 use one of these processors." -msgstr "" - -#. Tag: term -#: hardware.xml:1149 -#, no-c-format -msgid "power3" -msgstr "" - -#. Tag: para -#: hardware.xml:1150 -#, no-c-format -msgid "" -"The POWER3 processor is used in older IBM 64-bit server systems: known " -"models include the IntelliStation POWER Model 265, the pSeries 610 and 640, " -"and the RS/6000 7044-170, 7043-260, and 7044-270." -msgstr "" - -#. Tag: term -#: hardware.xml:1160 -#, no-c-format -msgid "power4" -msgstr "" - -#. Tag: para -#: hardware.xml:1161 -#, no-c-format -msgid "" -"The POWER4 processor is used in more recent IBM 64-bit server systems: known " -"models include the pSeries 615, 630, 650, 655, 670, and 690." -msgstr "" - -#. Tag: para -#: hardware.xml:1166 -#, no-c-format -msgid "" -"The Apple G5 is also based on the POWER4 architecture, and uses this kernel " -"flavour." -msgstr "" - -#. Tag: term -#: hardware.xml:1175 -#, no-c-format -msgid "<term>apus</term>" -msgstr "" - -#. Tag: para -#: hardware.xml:1176 -#, no-c-format -msgid "This kernel flavour supports the Amiga Power-UP System." -msgstr "" - -#. Tag: title -#: hardware.xml:1188 -#, no-c-format -msgid "Power Macintosh (pmac) subarchitecture" -msgstr "" - -#. Tag: para -#: hardware.xml:1190 -#, no-c-format -msgid "" -"Apple (and briefly a few other manufacturers — Power Computing, for " -"example) makes a series of Macintosh computers based on the PowerPC " -"processor. For purposes of architecture support, they are categorized as " -"NuBus, OldWorld PCI, and NewWorld." -msgstr "" - -#. Tag: para -#: hardware.xml:1197 -#, no-c-format -msgid "" -"Macintosh computers using the 680x0 series of processors are not in the " -"PowerPC family but are instead m68k machines. Those models start with " -"<quote>Mac II</quote> or have a 3-digit model number such as Centris 650 or " -"Quadra 950. Apple's pre-iMac PowerPC model numbers have four digits." -msgstr "" - -#. Tag: para -#: hardware.xml:1204 -#, no-c-format -msgid "" -"NuBus systems are not currently supported by debian/powerpc. The monolithic " -"Linux/PPC kernel architecture does not have support for these machines; " -"instead, one must use the MkLinux Mach microkernel, which Debian does not " -"yet support. These include the following: <itemizedlist> <listitem><para> " -"Power Macintosh 6100, 7100, 8100 </para></listitem> <listitem><para> " -"Performa 5200, 6200, 6300 </para></listitem> <listitem><para> Powerbook " -"1400, 2300, and 5300 </para></listitem> <listitem><para> Workgroup Server " -"6150, 8150, 9150 </para></listitem> </itemizedlist> A linux kernel for these " -"machines and limited support is available at <ulink url=\"http://nubus-pmac." -"sourceforge.net/\"></ulink>" -msgstr "" - -#. Tag: para -#: hardware.xml:1237 -#, no-c-format -msgid "" -"OldWorld systems are most Power Macintoshes with a floppy drive and a PCI " -"bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld " -"machines. The beige colored G3 systems are also OldWorld." -msgstr "" - -#. Tag: para -#: hardware.xml:1243 -#, no-c-format -msgid "" -"The so called NewWorld PowerMacs are any PowerMacs in translucent colored " -"plastic cases. That includes all iMacs, iBooks, G4 systems, blue colored G3 " -"systems, and most PowerBooks manufactured in and after 1999. The NewWorld " -"PowerMacs are also known for using the <quote>ROM in RAM</quote> system for " -"MacOS, and were manufactured from mid-1998 onwards." -msgstr "" - -#. Tag: para -#: hardware.xml:1251 -#, no-c-format -msgid "" -"Specifications for Apple hardware are available at <ulink url=\"http://www." -"info.apple.com/support/applespec.html\">AppleSpec</ulink>, and, for older " -"hardware, <ulink url=\"http://www.info.apple.com/support/applespec.legacy/" -"index.html\">AppleSpec Legacy</ulink>." -msgstr "" - -#. Tag: entry -#: hardware.xml:1267 hardware.xml:1402 hardware.xml:1446 hardware.xml:1475 -#, no-c-format -msgid "Model Name/Number" -msgstr "" - -#. Tag: entry -#: hardware.xml:1268 -#, no-c-format -msgid "Generation" -msgstr "" - -#. Tag: entry -#: hardware.xml:1274 -#, no-c-format -msgid "Apple" -msgstr "" - -#. Tag: entry -#: hardware.xml:1275 -#, no-c-format -msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" -msgstr "" - -#. Tag: entry -#: hardware.xml:1276 hardware.xml:1279 hardware.xml:1282 hardware.xml:1285 -#: hardware.xml:1288 hardware.xml:1291 hardware.xml:1294 hardware.xml:1297 -#: hardware.xml:1300 hardware.xml:1303 hardware.xml:1306 hardware.xml:1309 -#: hardware.xml:1312 hardware.xml:1315 hardware.xml:1318 hardware.xml:1321 -#, no-c-format -msgid "NewWorld" -msgstr "" - -#. Tag: entry -#: hardware.xml:1278 -#, no-c-format -msgid "iMac Summer 2000, Early 2001" -msgstr "" - -#. Tag: entry -#: hardware.xml:1281 -#, no-c-format -msgid "iMac G5" -msgstr "" - -#. Tag: entry -#: hardware.xml:1284 -#, no-c-format -msgid "iBook, iBook SE, iBook Dual USB" -msgstr "" - -#. Tag: entry -#: hardware.xml:1287 -#, no-c-format -msgid "iBook2" -msgstr "" - -#. Tag: entry -#: hardware.xml:1290 -#, no-c-format -msgid "iBook G4" -msgstr "" - -#. Tag: entry -#: hardware.xml:1293 -#, no-c-format -msgid "Power Macintosh Blue and White (B&W) G3" -msgstr "" - -#. Tag: entry -#: hardware.xml:1296 -#, no-c-format -msgid "Power Macintosh G4 PCI, AGP, Cube" -msgstr "" - -#. Tag: entry -#: hardware.xml:1299 -#, no-c-format -msgid "Power Macintosh G4 Gigabit Ethernet" -msgstr "" - -#. Tag: entry -#: hardware.xml:1302 -#, no-c-format -msgid "Power Macintosh G4 Digital Audio, Quicksilver" -msgstr "" - -#. Tag: entry -#: hardware.xml:1305 -#, no-c-format -msgid "Power Macintosh G5" -msgstr "" - -#. Tag: entry -#: hardware.xml:1308 -#, no-c-format -msgid "PowerBook G3 FireWire Pismo (2000)" -msgstr "" - -#. Tag: entry -#: hardware.xml:1311 -#, no-c-format -msgid "PowerBook G3 Lombard (1999)" -msgstr "" - -#. Tag: entry -#: hardware.xml:1314 -#, no-c-format -msgid "PowerBook G4 Titanium" -msgstr "" - -#. Tag: entry -#: hardware.xml:1317 -#, no-c-format -msgid "PowerBook G4 Aluminum" -msgstr "" - -#. Tag: entry -#: hardware.xml:1320 -#, no-c-format -msgid "Xserve G5" -msgstr "" - -#. Tag: entry -#: hardware.xml:1323 -#, no-c-format -msgid "Performa 4400, 54xx, 5500" -msgstr "" - -#. Tag: entry -#: hardware.xml:1324 hardware.xml:1327 hardware.xml:1330 hardware.xml:1333 -#: hardware.xml:1336 hardware.xml:1339 hardware.xml:1342 hardware.xml:1345 -#: hardware.xml:1348 hardware.xml:1351 hardware.xml:1354 hardware.xml:1357 -#: hardware.xml:1363 hardware.xml:1366 hardware.xml:1372 hardware.xml:1378 -#: hardware.xml:1384 -#, no-c-format -msgid "OldWorld" -msgstr "" - -#. Tag: entry -#: hardware.xml:1326 -#, no-c-format -msgid "Performa 6360, 6400, 6500" -msgstr "" - -#. Tag: entry -#: hardware.xml:1329 -#, no-c-format -msgid "Power Macintosh 4400, 5400" -msgstr "" - -#. Tag: entry -#: hardware.xml:1332 -#, no-c-format -msgid "Power Macintosh 7200, 7300, 7500, 7600" -msgstr "" - -#. Tag: entry -#: hardware.xml:1335 -#, no-c-format -msgid "Power Macintosh 8200, 8500, 8600" -msgstr "" - -#. Tag: entry -#: hardware.xml:1338 -#, no-c-format -msgid "Power Macintosh 9500, 9600" -msgstr "" - -#. Tag: entry -#: hardware.xml:1341 -#, no-c-format -msgid "Power Macintosh (Beige) G3 Minitower" -msgstr "" - -#. Tag: entry -#: hardware.xml:1344 -#, no-c-format -msgid "Power Macintosh (Beige) Desktop, All-in-One" -msgstr "" - -#. Tag: entry -#: hardware.xml:1347 -#, no-c-format -msgid "PowerBook 2400, 3400, 3500" -msgstr "" - -#. Tag: entry -#: hardware.xml:1350 -#, no-c-format -msgid "PowerBook G3 Wallstreet (1998)" -msgstr "" - -#. Tag: entry -#: hardware.xml:1353 -#, no-c-format -msgid "Twentieth Anniversary Macintosh" -msgstr "" - -#. Tag: entry -#: hardware.xml:1356 -#, no-c-format -msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" -msgstr "" - -#. Tag: entry -#: hardware.xml:1361 -#, no-c-format -msgid "Power Computing" -msgstr "" - -#. Tag: entry -#: hardware.xml:1362 -#, no-c-format -msgid "PowerBase, PowerTower / Pro, PowerWave" -msgstr "" - -#. Tag: entry -#: hardware.xml:1365 -#, no-c-format -msgid "PowerCenter / Pro, PowerCurve" -msgstr "" - -#. Tag: entry -#: hardware.xml:1370 -#, no-c-format -msgid "UMAX" -msgstr "" - -#. Tag: entry -#: hardware.xml:1371 -#, no-c-format -msgid "C500, C600, J700, S900" -msgstr "" - -#. Tag: entry -#: hardware.xml:1376 -#, no-c-format -msgid "<entry>APS</entry>" -msgstr "" - -#. Tag: entry -#: hardware.xml:1377 -#, no-c-format -msgid "APS Tech M*Power 604e/2000" -msgstr "" - -#. Tag: entry -#: hardware.xml:1382 hardware.xml:1408 -#, no-c-format -msgid "Motorola" -msgstr "" - -#. Tag: entry -#: hardware.xml:1383 -#, no-c-format -msgid "Starmax 3000, 4000, 5000, 5500" -msgstr "" - -#. Tag: title -#: hardware.xml:1392 -#, no-c-format -msgid "PReP subarchitecture" -msgstr "" - -#. Tag: entry -#: hardware.xml:1409 -#, no-c-format -msgid "Firepower, PowerStack Series E, PowerStack II" -msgstr "" - -#. Tag: entry -#: hardware.xml:1411 -#, no-c-format -msgid "MPC 7xx, 8xx" -msgstr "" - -#. Tag: entry -#: hardware.xml:1413 -#, no-c-format -msgid "MTX, MTX+" -msgstr "" - -#. Tag: entry -#: hardware.xml:1415 -#, no-c-format -msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" -msgstr "" - -#. Tag: entry -#: hardware.xml:1417 -#, no-c-format -msgid "MCP(N)750" -msgstr "" - -#. Tag: entry -#: hardware.xml:1421 hardware.xml:1452 -#, no-c-format -msgid "IBM RS/6000" -msgstr "" - -#. Tag: entry -#: hardware.xml:1422 -#, no-c-format -msgid "40P, 43P" -msgstr "" - -#. Tag: entry -#: hardware.xml:1424 -#, no-c-format -msgid "Power 830/850/860 (6070, 6050)" -msgstr "" - -#. Tag: entry -#: hardware.xml:1426 -#, no-c-format -msgid "6030, 7025, 7043" -msgstr "" - -#. Tag: entry -#: hardware.xml:1428 -#, no-c-format -msgid "p640" -msgstr "" - -#. Tag: title -#: hardware.xml:1436 -#, no-c-format -msgid "CHRP subarchitecture" -msgstr "" - -#. Tag: entry -#: hardware.xml:1453 -#, no-c-format -msgid "B50, 43P-150, 44P" -msgstr "" - -#. Tag: entry -#: hardware.xml:1456 -#, no-c-format -msgid "Genesi" -msgstr "" - -#. Tag: entry -#: hardware.xml:1457 -#, no-c-format -msgid "Pegasos I, Pegasos II" -msgstr "" - -#. Tag: title -#: hardware.xml:1465 -#, no-c-format -msgid "APUS subarchitecture" -msgstr "" - -#. Tag: entry -#: hardware.xml:1481 -#, no-c-format -msgid "Amiga Power-UP Systems (APUS)" -msgstr "" - -#. Tag: entry -#: hardware.xml:1482 -#, no-c-format -msgid "A1200, A3000, A4000" -msgstr "" - -#. Tag: title -#: hardware.xml:1495 -#, no-c-format -msgid "S/390 and zSeries machine types" -msgstr "" - -#. Tag: para -#: hardware.xml:1496 -#, no-c-format -msgid "" -"Complete information regarding supported S/390 and zSeries machines can be " -"found in IBM's Redbook <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/" -"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and S/390: " -"Distributions</ulink> in chapter 2.1 or at the <ulink url=\"http://oss." -"software.ibm.com/developerworks/opensource/linux390/documentation-2.4.shtml" -"\">technical details web page</ulink> at <ulink url=\"http://oss.software." -"ibm.com/developerworks/opensource/linux390/index.shtml\">developerWorks</" -"ulink>. In short, G5, Multiprise 3000, G6 and all zSeries are fully " -"supported; Multiprise 2000, G3 and G4 machines are supported with IEEE " -"floating point emulation and thus degraded performance." -msgstr "" - -#. Tag: para -#: hardware.xml:1519 -#, no-c-format -msgid "" -"Currently the <emphasis>&architecture;</emphasis> port supports several " -"types of Sparc systems. The most common identifiers for Sparc systems are " -"sun4, sun4c, sun4m, sun4d and sun4u. Currently we do not support very old " -"sun4 hardware. However, the other systems are supported. Sun4d has been " -"tested the least of these, so expect possible problems with regard to the " -"kernel stability. Sun4c and Sun4m, the most common of the older Sparc " -"hardware, includes such systems as SparcStation 1, 1+, IPC, IPX and the " -"SparcStation LX, 5, 10, and 20, respectively. The UltraSPARC class systems " -"fall under the sun4u identifier, and are supported using the sun4u set of " -"install images. Some systems that fall under these supported identifiers are " -"known to not be supported. Known unsupported systems are the AP1000 " -"multicomputer and the Tadpole Sparcbook 1. See the <ulink url=\"&url-sparc-" -"linux-faq;\">Linux for SPARCProcessors FAQ</ulink> for complete information." -msgstr "" - -#. Tag: title -#: hardware.xml:1539 -#, no-c-format -msgid "Memory Configuration" -msgstr "" - -#. Tag: para -#: hardware.xml:1540 -#, no-c-format -msgid "" -"Some older Sun workstations, notably the Sun IPX and Sun IPC have memory " -"banks located at fixed locations in physical memory. Thus if the banks are " -"not filled gaps will exist in the physical memory space. The Linux " -"installation requires a contiguous memory block into which to load the " -"kernel and the initial RAMdisk. If this is not available a <quote>Data " -"Access Exception</quote> will result." -msgstr "" - -#. Tag: para -#: hardware.xml:1549 -#, no-c-format -msgid "" -"Thus you must configure the memory so that the lowest memory block is " -"contiguous for at least 8Mb. In the IPX and IPC cited above, memory banks " -"are mapped in at 16Mb boundaries. In effect this means that you must have a " -"sufficiently large SIMM in bank zero to hold the kernel and RAMdisk. In this " -"case 4Mb is <emphasis>not</emphasis> sufficient." -msgstr "" - -#. Tag: para -#: hardware.xml:1557 -#, no-c-format -msgid "" -"Example: In a Sun IPX you have a 16Mb SIMM and a 4Mb SIMM. There are four " -"SIMM banks (0,1,2,3). [Bank zero is that furthest away from the SBUS " -"connectors]. You must therefore install the 16Mb SIMM in bank 0; it is then " -"recommended to install the 4Mb SIMM in bank 2." -msgstr "" - -#. Tag: title -#: hardware.xml:1568 -#, no-c-format -msgid "Graphics Configuration" -msgstr "" - -#. Tag: para -#: hardware.xml:1569 -#, no-c-format -msgid "" -"Especially in the case of older Sun workstations, it is very common for " -"there to be an onboard framebuffer which has been superseded (for example " -"the bwtwo on a sun IPC), and an SBUS card containing a later probably " -"accelerated buffer is then plugged in to an SBUS slot. Under Solaris/SunOS " -"this causes no problems because both cards are initialized." -msgstr "" - -#. Tag: para -#: hardware.xml:1578 -#, no-c-format -msgid "" -"However with Linux this can cause a problem, in that the boot PROM monitor " -"may display its output on this additional card; however the linux kernel " -"boot messages may then be directed to the original on board framebuffer, " -"leaving <emphasis>no</emphasis> error messages on the screen, with the " -"machine apparently stuck loading the RAMdisk." -msgstr "" - -#. Tag: para -#: hardware.xml:1586 -#, no-c-format -msgid "" -"To avoid this problem, connect the monitor (if required) to the video card " -"in the lowest numbered SBUS slot (on motherboard card counts as below " -"external slots). Alternatively it is possible to use a serial console." -msgstr "" - -#. Tag: title -#: hardware.xml:1598 -#, no-c-format -msgid "Graphics Card" -msgstr "" - -#. Tag: para -#: hardware.xml:1600 -#, no-c-format -msgid "" -"You should be using a VGA-compatible display interface for the console " -"terminal. Nearly every modern display card is compatible with VGA. Ancient " -"standards such CGA, MDA, or HGA should also work, assuming you do not " -"require X11 support. Note that X11 is not used during the installation " -"process described in this document." -msgstr "" - -#. Tag: para -#: hardware.xml:1608 -#, no-c-format -msgid "" -"Debian's support for graphical interfaces is determined by the underlying " -"support found in X.Org's X11 system. Most AGP, PCI and PCIe video cards work " -"under X.Org. Details on supported graphics buses, cards, monitors, and " -"pointing devices can be found at <ulink url=\"&url-xorg;\"></ulink>. Debian " -"&release; ships with X.Org version &x11ver;." -msgstr "" - -#. Tag: para -#: hardware.xml:1617 -#, no-c-format -msgid "" -"The X.Org X11 window system is only supported on the SGI Indy and the O2. " -"The Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v " -"PCI slots and support VGA emulation or Linux framebuffer on a selected range " -"of graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " -"listing</ulink> for Broadcom evaluation boards is available." -msgstr "" - -#. Tag: para -#: hardware.xml:1626 -#, no-c-format -msgid "" -"The X.Org X11 window system is supported on some DECstation models. The " -"Broadcom BCM91250A and BCM91480B evaluation boards have standard 3.3v PCI " -"slots and support VGA emulation or Linux framebuffer on a selected range of " -"graphics cards. A <ulink url=\"&url-bcm91250a-hardware;\">compatibility " -"listing</ulink> for Broadcom evaluation boards is available." -msgstr "" - -#. Tag: title -#: hardware.xml:1638 -#, no-c-format -msgid "Laptops" -msgstr "" - -#. Tag: para -#: hardware.xml:1639 -#, no-c-format -msgid "" -"Laptops are also supported. Laptops are often specialized or contain " -"proprietary hardware. To see if your particular laptop works well with GNU/" -"Linux, see the <ulink url=\"&url-x86-laptop;\">Linux Laptop pages</ulink>" -msgstr "" - -#. Tag: title -#: hardware.xml:1651 hardware.xml:1676 hardware.xml:1699 -#, no-c-format -msgid "Multiple Processors" -msgstr "" - -#. Tag: para -#: hardware.xml:1653 -#, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is supported for this architecture. The " -"standard Debian &release; kernel image was compiled with SMP support. This " -"should not prevent installation, since the SMP kernel should boot on non-SMP " -"systems; the kernel will simply cause a bit more overhead." -msgstr "" - -#. Tag: para -#: hardware.xml:1661 -#, no-c-format -msgid "" -"In order to optimize the kernel for single CPU systems, you'll have to " -"replace the standard Debian kernel. You can find a discussion of how to do " -"this in <xref linkend=\"kernel-baking\"/>. At this time (kernel version " -"&kernelversion;) the way you disable SMP is to deselect <quote>&smp-config-" -"option;</quote> in the <quote>&smp-config-section;</quote> section of the " -"kernel config." -msgstr "" - -#. Tag: para -#: hardware.xml:1677 -#, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is supported for this architecture. " -"However, the standard Debian &release; kernel image does not support SMP. " -"This should not prevent installation, since the standard, non-SMP kernel " -"should boot on SMP systems; the kernel will simply use the first CPU." -msgstr "" - -#. Tag: para -#: hardware.xml:1686 -#, no-c-format -msgid "" -"In order to take advantage of multiple processors, you'll have to replace " -"the standard Debian kernel. You can find a discussion of how to do this in " -"<xref linkend=\"kernel-baking\"/>. At this time (kernel version " -"&kernelversion;) the way you enable SMP is to select <quote>&smp-config-" -"option;</quote> in the <quote>&smp-config-section;</quote> section of the " -"kernel config." -msgstr "" - -#. Tag: para -#: hardware.xml:1700 -#, no-c-format -msgid "" -"Multi-processor support — also called <quote>symmetric multi-" -"processing</quote> or SMP — is supported for this architecture, and is " -"supported by a precompiled Debian kernel image. Depending on your install " -"media, this SMP-capable kernel may or may not be installed by default. This " -"should not prevent installation, since the standard, non-SMP kernel should " -"boot on SMP systems; the kernel will simply use the first CPU." -msgstr "" - -#. Tag: para -#: hardware.xml:1710 -#, no-c-format -msgid "" -"In order to take advantage of multiple processors, you should check to see " -"if a kernel package that supports SMP is installed, and if not, choose an " -"appropriate kernel package. You can also build your own customized kernel to " -"support SMP. You can find a discussion of how to do this in <xref linkend=" -"\"kernel-baking\"/>. At this time (kernel version &kernelversion;) the way " -"you enable SMP is to select <quote>&smp-config-option;</quote> in the " -"<quote>&smp-config-section;</quote> section of the kernel config." -msgstr "" - -#. Tag: title -#: hardware.xml:1731 -#, no-c-format -msgid "Installation Media" -msgstr "" - -#. Tag: para -#: hardware.xml:1733 -#, no-c-format -msgid "" -"This section will help you determine which different media types you can use " -"to install Debian. For example, if you have a floppy disk drive on your " -"machine, it can be used to install Debian. There is a whole chapter devoted " -"media, <xref linkend=\"install-methods\"/>, which lists the advantages and " -"disadvantages of each media type. You may want to refer back to this page " -"once you reach that section." -msgstr "" - -#. Tag: title -#: hardware.xml:1744 -#, no-c-format -msgid "Floppies" -msgstr "" - -#. Tag: para -#: hardware.xml:1745 -#, no-c-format -msgid "" -"In some cases, you'll have to do your first boot from floppy disks. " -"Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch " -"floppy drive." -msgstr "" - -#. Tag: para -#: hardware.xml:1751 -#, no-c-format -msgid "For CHRP, floppy support is currently broken." -msgstr "" - -#. Tag: title -#: hardware.xml:1758 -#, no-c-format -msgid "CD-ROM/DVD-ROM" -msgstr "" - -#. Tag: para -#: hardware.xml:1760 -#, no-c-format -msgid "" -"Whenever you see <quote>CD-ROM</quote> in this manual, it applies to both CD-" -"ROMs and DVD-ROMs, because both technologies are really the same from the " -"operating system's point of view, except for some very old nonstandard CD-" -"ROM drives which are neither SCSI nor IDE/ATAPI." -msgstr "" - -#. Tag: para -#: hardware.xml:1767 -#, no-c-format -msgid "" -"CD-ROM based installation is supported for some architectures. On machines " -"which support bootable CD-ROMs, you should be able to do a completely " -"<phrase arch=\"not-s390\">floppy-less</phrase> <phrase arch=\"s390\">tape-" -"less</phrase> installation. Even if your system doesn't support booting from " -"a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to " -"install your system, once you've booted up by other means; see <xref linkend=" -"\"boot-installer\"/>." -msgstr "" - -#. Tag: para -#: hardware.xml:1779 -#, no-c-format -msgid "" -"Both SCSI and IDE/ATAPI CD-ROMs are supported. In addition, all non-standard " -"CD interfaces supported by Linux are supported by the boot disks (such as " -"Mitsumi and Matsushita drives). However, these models might require special " -"boot parameters or other massaging to get them to work, and booting off " -"these non-standard interfaces is unlikely. The <ulink url=\"&url-cd-howto;" -"\">Linux CD-ROM HOWTO</ulink> contains in-depth information on using CD-ROMs " -"with Linux." -msgstr "" - -#. Tag: para -#: hardware.xml:1789 -#, no-c-format -msgid "" -"USB CD-ROM drives are also supported, as are FireWire devices that are " -"supported by the ohci1394 and sbp2 drivers." -msgstr "" - -#. Tag: para -#: hardware.xml:1794 -#, no-c-format -msgid "" -"Both SCSI and IDE/ATAPI CD-ROMs are supported on &arch-title;, as long as " -"the controller is supported by the SRM console. This rules out many add-on " -"controller cards, but most integrated IDE and SCSI chips and controller " -"cards that were provided by the manufacturer can be expected to work. To " -"find out whether your device is supported from the SRM console, see the " -"<ulink url=\"&url-srm-howto;\">SRM HOWTO</ulink>." -msgstr "" - -#. Tag: para -#: hardware.xml:1803 -#, no-c-format -msgid "" -"IDE/ATAPI CD-ROMs are supported on all ARM machines. On RiscPCs, SCSI CD-" -"ROMs are also supported." -msgstr "" - -#. Tag: para -#: hardware.xml:1808 -#, no-c-format -msgid "" -"On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of " -"working with a logical blocksize of 512 bytes. Many of the SCSI CD-DROM " -"drives sold for the PC market do not have this capability. If your CD-ROM " -"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</" -"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position. " -"To start the install, simply choose the <quote>System installation</quote> " -"entry in the firmware. The Broadcom BCM91250A supports standard IDE devices, " -"including CD-ROM drives, but CD images for this platform are currently not " -"provided because the firmware doesn't recognize CD drives. In order to " -"install Debian on an Broadcom BCM91480B evaluation board, you need an PCI " -"IDE, SATA or SCSI card." -msgstr "" - -#. Tag: para -#: hardware.xml:1823 -#, no-c-format -msgid "" -"On DECstations, booting from CD-ROM requires a SCSI CD-ROM drive capable of " -"working with a logical blocksize of 512 bytes. Many of the SCSI CD-DROM " -"drives sold for the PC market do not have this capability. If your CD-ROM " -"drive has a jumper labeled <quote>Unix/PC</quote> or <quote>512/2048</" -"quote>, place it in the <quote>Unix</quote> or <quote>512</quote> position." -msgstr "" - -#. Tag: para -#: hardware.xml:1832 -#, no-c-format -msgid "" -"CD 1 contains the installer for the r3k-kn02 subarchitecture (the R3000-" -"based DECstations 5000/1xx and 5000/240 as well as the R3000-based Personal " -"DECstation models), CD 2 the installer for the r4k-kn04 subarchitecture (the " -"R4x00-based DECstations 5000/150 and 5000/260 as well as the Personal " -"DECstation 5000/50)." -msgstr "" - -#. Tag: para -#: hardware.xml:1841 -#, no-c-format -msgid "" -"To boot from CD, issue the command <userinput>boot <replaceable>#</" -"replaceable>/rz<replaceable>id</replaceable></userinput> on the firmware " -"prompt, where <replaceable>#</replaceable> is the number of the TurboChannel " -"device from which to boot (3 on most DECstations) and <replaceable>id</" -"replaceable> is the SCSI ID of the CD-ROM drive. If you need to pass " -"additional parameters, they can optionally be appended with the following " -"syntax:" -msgstr "" - -#. Tag: userinput -#: hardware.xml:1853 -#, no-c-format -msgid "" -"boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> " -"param1=value1 param2=value2 ..." -msgstr "" - -#. Tag: title -#: hardware.xml:1860 -#, no-c-format -msgid "Hard Disk" -msgstr "" - -#. Tag: para -#: hardware.xml:1862 -#, no-c-format -msgid "" -"Booting the installation system directly from a hard disk is another option " -"for many architectures. This will require some other operating system to " -"load the installer onto the hard disk." -msgstr "" - -#. Tag: para -#: hardware.xml:1868 -#, no-c-format -msgid "" -"In fact, installation from your local disk is the preferred installation " -"technique for most &architecture; machines." -msgstr "" - -#. Tag: para -#: hardware.xml:1873 -#, no-c-format -msgid "" -"Although the &arch-title; does not allow booting from SunOS (Solaris), you " -"can install from a SunOS partition (UFS slices)." -msgstr "" - -#. Tag: title -#: hardware.xml:1881 -#, no-c-format -msgid "USB Memory Stick" -msgstr "" - -#. Tag: para -#: hardware.xml:1883 -#, no-c-format -msgid "" -"Many Debian boxes need their floppy and/or CD-ROM drives only for setting up " -"the system and for rescue purposes. If you operate some servers, you will " -"probably already have thought about omitting those drives and using an USB " -"memory stick for installing and (when necessary) for recovering the system. " -"This is also useful for small systems which have no room for unnecessary " -"drives." -msgstr "" - -#. Tag: title -#: hardware.xml:1895 -#, no-c-format -msgid "Network" -msgstr "" - -#. Tag: para -#: hardware.xml:1897 -#, no-c-format -msgid "" -"You can also <emphasis>boot</emphasis> your system over the network. <phrase " -"arch=\"mips\">This is the preferred installation technique for Mips.</phrase>" -msgstr "" - -#. Tag: para -#: hardware.xml:1903 -#, no-c-format -msgid "" -"Diskless installation, using network booting from a local area network and " -"NFS-mounting of all local filesystems, is another option." -msgstr "" - -#. Tag: para -#: hardware.xml:1908 -#, no-c-format -msgid "" -"After the operating system kernel is installed, you can install the rest of " -"your system via any sort of network connection (including PPP after " -"installation of the base system), via FTP or HTTP." -msgstr "" - -#. Tag: title -#: hardware.xml:1917 -#, no-c-format -msgid "Un*x or GNU system" -msgstr "" - -#. Tag: para -#: hardware.xml:1919 -#, no-c-format -msgid "" -"If you are running another Unix-like system, you could use it to install " -"&debian; without using the &d-i; described in the rest of the manual. This " -"kind of install may be useful for users with otherwise unsupported hardware " -"or on hosts which can't afford downtime. If you are interested in this " -"technique, skip to the <xref linkend=\"linux-upgrade\"/>." -msgstr "" - -#. Tag: title -#: hardware.xml:1931 -#, no-c-format -msgid "Supported Storage Systems" -msgstr "" - -#. Tag: para -#: hardware.xml:1933 -#, no-c-format -msgid "" -"The Debian boot disks contain a kernel which is built to maximize the number " -"of systems it runs on. Unfortunately, this makes for a larger kernel, which " -"includes many drivers that won't be used for your machine (see <xref linkend=" -"\"kernel-baking\"/> to learn how to build your own kernel). Support for the " -"widest possible range of devices is desirable in general, to ensure that " -"Debian can be installed on the widest array of hardware." -msgstr "" - -#. Tag: para -#: hardware.xml:1943 -#, no-c-format -msgid "" -"Generally, the Debian installation system includes support for floppies, IDE " -"drives, IDE floppies, parallel port IDE devices, SCSI controllers and " -"drives, USB, and FireWire. The file systems supported include FAT, Win-32 " -"FAT extensions (VFAT), and NTFS, among others." -msgstr "" - -#. Tag: para -#: hardware.xml:1950 -#, no-c-format -msgid "" -"The disk interfaces that emulate the <quote>AT</quote> hard disk interface " -"which are often called MFM, RLL, IDE, or ATA are supported. Very old 8 bit " -"hard disk controllers used in the IBM XT computer are supported only as a " -"module. SCSI disk controllers from many different manufacturers are " -"supported. See the <ulink url=\"&url-hardware-howto;\">Linux Hardware " -"Compatibility HOWTO</ulink> for more details." -msgstr "" - -#. Tag: para -#: hardware.xml:1960 -#, no-c-format -msgid "" -"Pretty much all storage systems supported by the Linux kernel are supported " -"by the Debian installation system. Note that the current Linux kernel does " -"not support floppies on the Macintosh at all, and the Debian installation " -"system doesn't support floppies for Amigas. Also supported on the Atari is " -"the Macintosh HFS system, and AFFS as a module. Macs support the Atari (FAT) " -"file system. Amigas support the FAT file system, and HFS as a module." -msgstr "" - -#. Tag: para -#: hardware.xml:1970 -#, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. The following SCSI drivers are supported in the default kernel: " -"<itemizedlist> <listitem><para> Sparc ESP </para></listitem> " -"<listitem><para> PTI Qlogic,ISP </para></listitem> <listitem><para> Adaptec " -"AIC7xxx </para></listitem> <listitem><para> NCR and Symbios 53C8XX </para></" -"listitem> </itemizedlist> IDE systems (such as the UltraSPARC 5) are also " -"supported. See <ulink url=\"&url-sparc-linux-faq;\">Linux for SPARC " -"Processors FAQ</ulink> for more information on SPARC hardware supported by " -"the Linux kernel." -msgstr "" - -#. Tag: para -#: hardware.xml:2003 -#, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. This includes both SCSI and IDE disks. Note, however, that on " -"many systems, the SRM console is unable to boot from IDE drives, and the " -"Jensen is unable to boot from floppies. (see <ulink url=\"&url-jensen-howto;" -"\"></ulink> for more information on booting the Jensen)" -msgstr "" - -#. Tag: para -#: hardware.xml:2012 -#, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. Note that the current Linux kernel does not support floppies on " -"CHRP systems at all." -msgstr "" - -#. Tag: para -#: hardware.xml:2018 -#, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. Note that the current Linux kernel does not support the floppy " -"drive." -msgstr "" - -#. Tag: para -#: hardware.xml:2024 -#, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system." -msgstr "" - -#. Tag: para -#: hardware.xml:2029 -#, no-c-format -msgid "" -"Any storage system supported by the Linux kernel is also supported by the " -"boot system. This means that FBA and ECKD DASDs are supported with the old " -"Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." -msgstr "" - -#. Tag: title -#: hardware.xml:2046 -#, no-c-format -msgid "Peripherals and Other Hardware" -msgstr "" - -#. Tag: para -#: hardware.xml:2047 -#, no-c-format -msgid "" -"Linux supports a large variety of hardware devices such as mice, printers, " -"scanners, PCMCIA and USB devices. However, most of these devices are not " -"required while installing the system." -msgstr "" - -#. Tag: para -#: hardware.xml:2053 -#, no-c-format -msgid "" -"USB hardware generally works fine, only some USB keyboards may require " -"additional configuration (see <xref linkend=\"usb-keyboard-config\"/>)." -msgstr "" - -#. Tag: para -#: hardware.xml:2059 -#, no-c-format -msgid "" -"Again, see the <ulink url=\"&url-hardware-howto;\">Linux Hardware " -"Compatibility HOWTO</ulink> to determine whether your specific hardware is " -"supported by Linux." -msgstr "" - -#. Tag: para -#: hardware.xml:2065 -#, no-c-format -msgid "" -"Package installations from XPRAM and tape are not supported by this system. " -"All packages that you want to install need to be available on a DASD or over " -"the network using NFS, HTTP or FTP." -msgstr "" - -#. Tag: para -#: hardware.xml:2071 -#, no-c-format -msgid "" -"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 " -"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation " -"board features four 64 bit PCI slots." -msgstr "" - -#. Tag: para -#: hardware.xml:2077 -#, no-c-format -msgid "" -"The Broadcom BCM91250A evaluation board offers standard 3.3v 32 bit and 64 " -"bit PCI slots as well as USB connectors. The Broadcom BCM91480B evaluation " -"board features four 64 bit PCI slots. The Cobalt RaQ has no support for " -"additional devices but the Qube has one PCI slot." -msgstr "" - -#. Tag: title -#: hardware.xml:2087 -#, no-c-format -msgid "Purchasing Hardware Specifically for GNU/Linux" -msgstr "" - -#. Tag: para -#: hardware.xml:2089 -#, no-c-format -msgid "" -"There are several vendors, who ship systems with Debian or other " -"distributions of GNU/Linux <ulink url=\"&url-pre-installed;\">pre-installed</" -"ulink>. You might pay more for the privilege, but it does buy a level of " -"peace of mind, since you can be sure that the hardware is well-supported by " -"GNU/Linux." -msgstr "" - -#. Tag: para -#: hardware.xml:2097 -#, no-c-format -msgid "" -"Unfortunately, it's quite rare to find any vendor shipping new &arch-title; " -"machines at all." -msgstr "" - -#. Tag: para -#: hardware.xml:2102 -#, no-c-format -msgid "" -"If you do have to buy a machine with Windows bundled, carefully read the " -"software license that comes with Windows; you may be able to reject the " -"license and obtain a rebate from your vendor. Searching the Internet for " -"<quote>windows refund</quote> may get you some useful information to help " -"with that." -msgstr "" - -#. Tag: para -#: hardware.xml:2110 -#, no-c-format -msgid "" -"Whether or not you are purchasing a system with Linux bundled, or even a " -"used system, it is still important to check that your hardware is supported " -"by the Linux kernel. Check if your hardware is listed in the references " -"found above. Let your salesperson (if any) know that you're shopping for a " -"Linux system. Support Linux-friendly hardware vendors." -msgstr "" - -#. Tag: title -#: hardware.xml:2121 -#, no-c-format -msgid "Avoid Proprietary or Closed Hardware" -msgstr "" - -#. Tag: para -#: hardware.xml:2122 -#, no-c-format -msgid "" -"Some hardware manufacturers simply won't tell us how to write drivers for " -"their hardware. Others won't allow us access to the documentation without a " -"non-disclosure agreement that would prevent us from releasing the Linux " -"source code." -msgstr "" - -#. Tag: para -#: hardware.xml:2129 -#, no-c-format -msgid "" -"Another example is the proprietary hardware in the older Macintosh line. In " -"fact, no specifications or documentation have ever been released for any " -"Macintosh hardware, most notably the ADB controller (used by the mouse and " -"keyboard), the floppy controller, and all acceleration and CLUT manipulation " -"of the video hardware (though we do now support CLUT manipulation on nearly " -"all internal video chips). In a nutshell, this explains why the Macintosh " -"Linux port lags behind other Linux ports." -msgstr "" - -#. Tag: para -#: hardware.xml:2140 -#, no-c-format -msgid "" -"Since we haven't been granted access to the documentation on these devices, " -"they simply won't work under Linux. You can help by asking the manufacturers " -"of such hardware to release the documentation. If enough people ask, they " -"will realize that the free software community is an important market." -msgstr "" - -#. Tag: title -#: hardware.xml:2152 -#, no-c-format -msgid "Windows-specific Hardware" -msgstr "" - -#. Tag: para -#: hardware.xml:2153 -#, no-c-format -msgid "" -"A disturbing trend is the proliferation of Windows-specific modems and " -"printers. In some cases these are specially designed to be operated by the " -"Microsoft Windows operating system and bear the legend <quote>WinModem</" -"quote> or <quote>Made especially for Windows-based computers</quote>. This " -"is generally done by removing the embedded processors of the hardware and " -"shifting the work they do over to a Windows driver that is run by your " -"computer's main CPU. This strategy makes the hardware less expensive, but " -"the savings are often <emphasis>not</emphasis> passed on to the user and " -"this hardware may even be more expensive than equivalent devices that retain " -"their embedded intelligence." -msgstr "" - -#. Tag: para -#: hardware.xml:2166 -#, no-c-format -msgid "" -"You should avoid Windows-specific hardware for two reasons. The first is " -"that the manufacturers do not generally make the resources available to " -"write a Linux driver. Generally, the hardware and software interface to the " -"device is proprietary, and documentation is not available without a non-" -"disclosure agreement, if it is available at all. This precludes its being " -"used for free software, since free software writers disclose the source code " -"of their programs. The second reason is that when devices like these have " -"had their embedded processors removed, the operating system must perform the " -"work of the embedded processors, often at <emphasis>real-time</emphasis> " -"priority, and thus the CPU is not available to run your programs while it is " -"driving these devices. Since the typical Windows user does not multi-process " -"as intensively as a Linux user, the manufacturers hope that the Windows user " -"simply won't notice the burden this hardware places on their CPU. However, " -"any multi-processing operating system, even Windows 2000 or XP, suffers from " -"degraded performance when peripheral manufacturers skimp on the embedded " -"processing power of their hardware." -msgstr "" - -#. Tag: para -#: hardware.xml:2187 -#, no-c-format -msgid "" -"You can help this situation by encouraging these manufacturers to release " -"the documentation and other resources necessary for us to program their " -"hardware, but the best strategy is simply to avoid this sort of hardware " -"until it is listed as working in the <ulink url=\"&url-hardware-howto;" -"\">Linux Hardware Compatibility HOWTO</ulink>." -msgstr "" - -#. Tag: title -#: hardware.xml:2200 -#, no-c-format -msgid "Fake or <quote>Virtual</quote> Parity RAM" -msgstr "" - -#. Tag: para -#: hardware.xml:2201 -#, no-c-format -msgid "" -"If you ask for Parity RAM in a computer store, you'll probably get " -"<emphasis>virtual parity</emphasis> memory modules instead of <emphasis>true " -"parity</emphasis> ones. Virtual parity SIMMs can often (but not always) be " -"distinguished because they only have one more chip than an equivalent non-" -"parity SIMM, and that one extra chip is smaller than all the others. Virtual-" -"parity SIMMs work exactly like non-parity memory. They can't tell you when " -"you have a single-bit RAM error the way true-parity SIMMs do in a " -"motherboard that implements parity. Don't ever pay more for a virtual-parity " -"SIMM than a non-parity one. Do expect to pay a little more for true-parity " -"SIMMs, because you are actually buying one extra bit of memory for every 8 " -"bits." -msgstr "" - -#. Tag: para -#: hardware.xml:2216 -#, no-c-format -msgid "" -"If you want complete information on &arch-title; RAM issues, and what is the " -"best RAM to buy, see the <ulink url=\"&url-pc-hw-faq;\">PC Hardware FAQ</" -"ulink>." -msgstr "" - -#. Tag: para -#: hardware.xml:2222 -#, no-c-format -msgid "Most, if not all, Alpha systems require true-parity RAM." -msgstr "" - -#. Tag: title -#: hardware.xml:2237 -#, no-c-format -msgid "Memory and Disk Space Requirements" -msgstr "" - -#. Tag: para -#: hardware.xml:2239 -#, no-c-format -msgid "" -"You must have at least &minimum-memory; of memory and &minimum-fs-size; of " -"hard disk space. For a minimal console-based system (all standard packages), " -"250MB is required. If you want to install a reasonable amount of software, " -"including the X Window System, and some development programs and libraries, " -"you'll need at least 400MB. For a more or less complete desktop system, " -"you'll need a few gigabytes." -msgstr "" - -#. Tag: para -#: hardware.xml:2248 -#, no-c-format -msgid "" -"On the Amiga the size of FastRAM is relevant towards the total memory " -"requirements. Also, using Zorro cards with 16-bit RAM is not supported; " -"you'll need 32-bit RAM. The <command>amiboot</command> program can be used " -"to disable 16-bit RAM; see the <ulink url=\"&url-m68k-faq;\">Linux/m68k FAQ</" -"ulink>. Recent kernels should disable 16-bit RAM automatically." -msgstr "" - -#. Tag: para -#: hardware.xml:2257 -#, no-c-format -msgid "" -"On the Atari, both ST-RAM and Fast RAM (TT-RAM) are used by Linux. Many " -"users have reported problems running the kernel itself in Fast RAM, so the " -"Atari bootstrap will place the kernel in ST-RAM. The minimum requirement for " -"ST-RAM is 2 MB. You will need an additional 12 MB or more of TT-RAM." -msgstr "" - -#. Tag: para -#: hardware.xml:2265 -#, no-c-format -msgid "" -"On the Macintosh, care should be taken on machines with RAM-based video " -"(RBV). The RAM segment at physical address 0 is used as screen memory, " -"making the default load position for the kernel unavailable. The alternate " -"RAM segment used for kernel and RAMdisk must be at least 4 MB." -msgstr "" - -#. Tag: emphasis -#: hardware.xml:2275 -#, no-c-format -msgid "FIXME: is this still true?" -msgstr "" - -#. Tag: title -#: hardware.xml:2286 -#, no-c-format -msgid "Network Connectivity Hardware" -msgstr "" - -#. Tag: para -#: hardware.xml:2288 -#, no-c-format -msgid "" -"Most PCI and many older ISA network cards are supported. Some network " -"interface cards are not supported by most Debian installation disks, such as " -"AX.25 cards and protocols; NI16510 EtherBlaster cards; Schneider & Koch " -"G16 cards; and the Zenith Z-Note built-in network card. Microchannel (MCA) " -"network cards are not supported by the standard installation system, but see " -"<ulink url=\"&url-linux-mca;\">Linux on MCA</ulink> for some (old) " -"instructions. FDDI networks are also not supported by the installation " -"disks, both cards and protocols." -msgstr "" - -#. Tag: para -#: hardware.xml:2307 -#, no-c-format -msgid "" -"As for ISDN, the D-channel protocol for the (old) German 1TR6 is not " -"supported; Spellcaster BRI ISDN boards are also not supported by the &d-i;." -msgstr "" - -#. Tag: para -#: hardware.xml:2315 -#, no-c-format -msgid "" -"Any network interface card (NIC) supported by the Linux kernel should also " -"be supported by the boot disks. You may need to load your network driver as " -"a module. Again, see <ulink url=\"&url-m68k-faq;\"></ulink> for complete " -"details." -msgstr "" - -#. Tag: para -#: hardware.xml:2324 -#, no-c-format -msgid "" -"The following network interface cards (NICs) are supported from the bootable " -"kernel directly:" -msgstr "" - -#. Tag: para -#: hardware.xml:2330 -#, no-c-format -msgid "Sun LANCE" -msgstr "" - -#. Tag: para -#: hardware.xml:2336 -#, no-c-format -msgid "Sun Happy Meal" -msgstr "" - -#. Tag: para -#: hardware.xml:2344 -#, no-c-format -msgid "" -"The following network interface cards are supported as modules. They can be " -"enabled once the drivers are installed during the setup. However, due to the " -"magic of OpenPROM, you still should be able to boot from these devices:" -msgstr "" - -#. Tag: para -#: hardware.xml:2352 -#, no-c-format -msgid "Sun BigMAC" -msgstr "" - -#. Tag: para -#: hardware.xml:2358 -#, no-c-format -msgid "Sun QuadEthernet" -msgstr "" - -#. Tag: para -#: hardware.xml:2363 -#, no-c-format -msgid "MyriCOM Gigabit Ethernet" -msgstr "" - -#. Tag: para -#: hardware.xml:2370 hardware.xml:2376 hardware.xml:2382 hardware.xml:2388 -#: hardware.xml:2394 -#, no-c-format -msgid "" -"Any network interface card (NIC) supported by the Linux kernel should also " -"be supported by the boot disks. You may need to load your network driver as " -"a module." -msgstr "" - -#. Tag: para -#: hardware.xml:2400 -#, no-c-format -msgid "" -"Due to kernel limitations only the onboard network interfaces on DECstations " -"are supported, TurboChannel option network cards currently do not work." -msgstr "" - -#. Tag: para -#: hardware.xml:2406 -#, no-c-format -msgid "" -"Any network interface card (NIC) supported by the Linux kernel are also be " -"supported by the boot disks. All network drivers are compiled as modules so " -"you need to load one first during the initial network setup. The list of " -"supported network devices is:" -msgstr "" - -#. Tag: para -#: hardware.xml:2414 -#, no-c-format -msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" -msgstr "" - -#. Tag: para -#: hardware.xml:2419 -#, no-c-format -msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" -msgstr "" - -#. Tag: para -#: hardware.xml:2424 -#, no-c-format -msgid "" -"Inter-User Communication Vehicle (IUCV) — available for VM guests only" -msgstr "" - -#. Tag: para -#: hardware.xml:2429 -#, no-c-format -msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" -msgstr "" - -#. Tag: para -#: hardware.xml:2438 -#, no-c-format -msgid "" -"The following network interface cards are supported directly by the boot " -"disks on Netwinder and CATS machines:" -msgstr "" - -#. Tag: para -#: hardware.xml:2444 -#, no-c-format -msgid "PCI-based NE2000" -msgstr "" - -#. Tag: para -#: hardware.xml:2450 -#, no-c-format -msgid "DECchip Tulip" -msgstr "" - -#. Tag: para -#: hardware.xml:2457 -#, no-c-format -msgid "" -"The following network interface cards are supported directly by the boot " -"disks on RiscPCs:" -msgstr "" - -#. Tag: para -#: hardware.xml:2463 -#, no-c-format -msgid "Ether1" -msgstr "" - -#. Tag: para -#: hardware.xml:2468 -#, no-c-format -msgid "Ether3" -msgstr "" - -#. Tag: para -#: hardware.xml:2473 -#, no-c-format -msgid "EtherH" -msgstr "" - -#. Tag: para -#: hardware.xml:2480 -#, no-c-format -msgid "" -"If your card is mentioned in the lists above, the complete installation can " -"be carried out from the network with no need for CD-ROMs or floppy disks." -msgstr "" - -#. Tag: para -#: hardware.xml:2486 -#, no-c-format -msgid "" -"Any other network interface card (NIC) supported by the Linux kernel should " -"also be supported by the boot disks. You may need to load your network " -"driver as a module; this means that you will have to install the operating " -"system kernel and modules using some other media." -msgstr "" diff --git a/po/pl/install-methods.po b/po/pl/install-methods.po deleted file mode 100644 index 3704ae5d8..000000000 --- a/po/pl/install-methods.po +++ /dev/null @@ -1,1797 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-03-19 13:45+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: install-methods.xml:5 -#, no-c-format -msgid "Obtaining System Installation Media" -msgstr "" - -#. Tag: title -#: install-methods.xml:12 -#, no-c-format -msgid "Official &debian; CD-ROM Sets" -msgstr "" - -#. Tag: para -#: install-methods.xml:13 -#, no-c-format -msgid "" -"By far the easiest way to install &debian; is from an Official Debian CD-ROM " -"Set. You can buy a set from a vendor (see the <ulink url=\"&url-debian-cd-" -"vendors;\">CD vendors page</ulink>). You may also download the CD-ROM images " -"from a Debian mirror and make your own set, if you have a fast network " -"connection and a CD burner (see the <ulink url=\"&url-debian-cd;\">Debian CD " -"page</ulink> for detailed instructions). If you have a Debian CD set and CDs " -"are bootable on your machine, you can skip right to <xref linkend=\"boot-" -"installer\"/>; much effort has been expended to ensure the files most people " -"need are there on the CD. Although a full set of binary packages requires " -"several CDs, it is unlikely you will need packages on the third CD and " -"above. You may also consider using the DVD version, which saves a lot of " -"space on your shelf and you avoid the CD shuffling marathon." -msgstr "" - -#. Tag: para -#: install-methods.xml:30 -#, no-c-format -msgid "" -"If your machine doesn't support CD booting, but you do have a CD set, you " -"can use an alternative strategy such as <phrase condition=\"supports-floppy-" -"boot\">floppy disk,</phrase> <phrase arch=\"s390\">tape, emulated tape,</" -"phrase> <phrase condition=\"bootable-disk\">hard disk,</phrase> <phrase " -"condition=\"bootable-usb\">usb stick,</phrase> <phrase condition=\"supports-" -"tftp\">net boot,</phrase> or manually loading the kernel from the CD to " -"initially boot the system installer. The files you need for booting by " -"another means are also on the CD; the Debian network archive and CD folder " -"organization are identical. So when archive file paths are given below for " -"particular files you need for booting, look for those files in the same " -"directories and subdirectories on your CD." -msgstr "" - -#. Tag: para -#: install-methods.xml:52 -#, no-c-format -msgid "" -"Once the installer is booted, it will be able to obtain all the other files " -"it needs from the CD." -msgstr "" - -#. Tag: para -#: install-methods.xml:57 -#, no-c-format -msgid "" -"If you don't have a CD set, then you will need to download the installer " -"system files and place them on the <phrase arch=\"s390\">installation tape</" -"phrase> <phrase condition=\"supports-floppy-boot\">floppy disk or</phrase> " -"<phrase condition=\"bootable-disk\">hard disk or</phrase> <phrase condition=" -"\"bootable-usb\">usb stick or</phrase> <phrase condition=\"supports-tftp\">a " -"connected computer</phrase> so they can be used to boot the installer." -msgstr "" - -#. Tag: title -#: install-methods.xml:83 -#, no-c-format -msgid "Downloading Files from Debian Mirrors" -msgstr "" - -#. Tag: para -#: install-methods.xml:85 -#, no-c-format -msgid "" -"To find the nearest (and thus probably the fastest) mirror, see the <ulink " -"url=\"&url-debian-mirrors;\">list of Debian mirrors</ulink>." -msgstr "" - -#. Tag: para -#: install-methods.xml:90 -#, no-c-format -msgid "" -"When downloading files from a Debian mirror, be sure to download the files " -"in <emphasis>binary</emphasis> mode, not text or automatic mode." -msgstr "" - -#. Tag: title -#: install-methods.xml:99 -#, no-c-format -msgid "Where to Find Installation Images" -msgstr "" - -#. Tag: para -#: install-methods.xml:101 -#, no-c-format -msgid "" -"The installation images are located on each Debian mirror in the directory " -"<ulink url=\"&url-debian-installer;/images\">debian/dists/&releasename;/main/" -"installer-&architecture;/current/images/</ulink> — the <ulink url=" -"\"&url-debian-installer;/images/MANIFEST\">MANIFEST</ulink> lists each image " -"and its purpose." -msgstr "" - -#. Tag: title -#: install-methods.xml:113 -#, no-c-format -msgid "Alpha Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:114 -#, no-c-format -msgid "" -"If you choose to boot from ARC console firmware using <command>MILO</" -"command>, you will also need to prepare a disk containing <command>MILO</" -"command> and <command>LINLOAD.EXE</command> from the provided disk images. " -"See <xref linkend=\"alpha-firmware\"/> for more information on Alpha " -"firmware and boot loaders. The floppy images can be found in the " -"<filename>MILO</filename> directory as " -"<filename>milo_<replaceable>subarchitecture</replaceable>.bin</filename>." -msgstr "" - -#. Tag: para -#: install-methods.xml:125 -#, no-c-format -msgid "" -"Unfortunately, these <command>MILO</command> images could not be tested and " -"might not work for all subarchitectures. If you find it doesn't work for " -"you, try copying the appropriate <command>MILO</command> binary onto the " -"floppy (<ulink url=\"&disturlftp;main/disks-alpha/current/MILO/\"></ulink>). " -"Note that those <command>MILO</command>s don't support ext2 <quote>sparse " -"superblocks</quote>, so you can't use them to load kernels from newly " -"generated ext2 file systems. As a workaround, you can put your kernel onto " -"the FAT partition next to the <command>MILO</command>." -msgstr "" - -#. Tag: para -#: install-methods.xml:137 -#, no-c-format -msgid "" -"<command>MILO</command> binaries are platform-specific. See <xref linkend=" -"\"alpha-cpus\"/> to determine the appropriate <command>MILO</command> image " -"for your Alpha platform." -msgstr "" - -#. Tag: title -#: install-methods.xml:152 -#, no-c-format -msgid "RiscPC Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:153 -#, no-c-format -msgid "" -"The RiscPC installer is booted initially from RISC OS. All the necessary " -"files are provided in one Zip archive, &rpc-install-kit;. Download this file " -"onto the RISC OS machine, copy the <filename>linloader.!Boot</filename> " -"components into place, and run <filename>!dInstall</filename>." -msgstr "" - -#. Tag: title -#: install-methods.xml:165 -#, no-c-format -msgid "Netwinder Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:166 -#, no-c-format -msgid "" -"The easiest way to boot a Netwinder is over the network, using the supplied " -"TFTP image &netwinder-boot-img;." -msgstr "" - -#. Tag: title -#: install-methods.xml:175 -#, no-c-format -msgid "CATS Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:176 -#, no-c-format -msgid "" -"CATS can be booted either via the network or from CD-ROM. The kernel and " -"initrd can be obtained from &cats-boot-img;." -msgstr "" - -#. Tag: title -#: install-methods.xml:185 -#, no-c-format -msgid "NSLU2 Installation Files" -msgstr "" - -#. Tag: para -#: install-methods.xml:186 -#, no-c-format -msgid "" -"A firmware image is provided for the Linksys NSLU2 which will automatically " -"boot <classname>debian-installer</classname>. This firmware image can be " -"obtained from &nslu2-firmware-img;." -msgstr "" - -#. Tag: title -#: install-methods.xml:232 -#, no-c-format -msgid "Choosing a Kernel" -msgstr "" - -#. Tag: para -#: install-methods.xml:234 -#, no-c-format -msgid "" -"Some m68k subarchs have a choice of kernels to install. In general we " -"recommend trying the most recent version first. If your subarch or machine " -"needs to use a 2.2.x kernel, make sure you choose one of the images that " -"supports 2.2.x kernels (see the <ulink url=\"&disturl;/main/installer-" -"&architecture;/current/images/MANIFEST\">MANIFEST</ulink>)." -msgstr "" - -#. Tag: para -#: install-methods.xml:243 -#, no-c-format -msgid "" -"All of the m68k images for use with 2.2.x kernels, require the kernel " -"parameter &ramdisksize;." -msgstr "" - -#. Tag: title -#: install-methods.xml:261 -#, no-c-format -msgid "Creating an IPL tape" -msgstr "" - -#. Tag: para -#: install-methods.xml:263 -#, no-c-format -msgid "" -"If you can't boot (IPL) from the CD-ROM and you are not using VM you need to " -"create an IPL tape first. This is described in section 3.4.3 in the <ulink " -"url=\"http://www.redbooks.ibm.com/pubs/pdfs/redbooks/sg246264.pdf\"> Linux " -"for IBM eServer zSeries and S/390: Distributions</ulink> Redbook. The files " -"you need to write to the tape are (in this order): <filename>kernel.debian</" -"filename>, <filename>parmfile.debian</filename> and <filename>initrd.debian</" -"filename>. The files can be downloaded from the <filename>tape</filename> " -"sub-directory, see <xref linkend=\"where-files\"/>," -msgstr "" - -#. Tag: title -#: install-methods.xml:287 -#, no-c-format -msgid "Creating Floppies from Disk Images" -msgstr "" - -#. Tag: para -#: install-methods.xml:288 -#, no-c-format -msgid "" -"Bootable floppy disks are generally used as a last resort to boot the " -"installer on hardware that cannot boot from CD or by other means." -msgstr "" - -#. Tag: para -#: install-methods.xml:293 -#, no-c-format -msgid "Floppy disk booting reportedly fails on Mac USB floppy drives." -msgstr "" - -#. Tag: para -#: install-methods.xml:297 -#, no-c-format -msgid "Floppy disk booting is not supported on Amigas or 68k Macs." -msgstr "" - -#. Tag: para -#: install-methods.xml:302 -#, no-c-format -msgid "" -"Disk images are files containing the complete contents of a floppy disk in " -"<emphasis>raw</emphasis> form. Disk images, such as <filename>boot.img</" -"filename>, cannot simply be copied to floppy drives. A special program is " -"used to write the image files to floppy disk in <emphasis>raw</emphasis> " -"mode. This is required because these images are raw representations of the " -"disk; it is required to do a <emphasis>sector copy</emphasis> of the data " -"from the file onto the floppy." -msgstr "" - -#. Tag: para -#: install-methods.xml:313 -#, no-c-format -msgid "" -"There are different techniques for creating floppies from disk images, which " -"depend on your platform. This section describes how to create floppies from " -"disk images on different platforms." -msgstr "" - -#. Tag: para -#: install-methods.xml:319 -#, no-c-format -msgid "" -"No matter which method you use to create your floppies, you should remember " -"to flip the write-protect tab on the floppies once you have written them, to " -"ensure they are not damaged unintentionally." -msgstr "" - -#. Tag: title -#: install-methods.xml:327 -#, no-c-format -msgid "Writing Disk Images From a Linux or Unix System" -msgstr "" - -#. Tag: para -#: install-methods.xml:328 -#, no-c-format -msgid "" -"To write the floppy disk image files to the floppy disks, you will probably " -"need root access to the system. Place a good, blank floppy in the floppy " -"drive. Next, use the command <informalexample><screen>\n" -"$ dd if=<replaceable>filename</replaceable> of=/dev/fd0 bs=1024 conv=sync ; " -"sync\n" -"</screen></informalexample> where <replaceable>filename</replaceable> is one " -"of the floppy disk image files (see <xref linkend=\"downloading-files\"/> " -"for what <replaceable>filename</replaceable> should be). <filename>/dev/fd0</" -"filename> is a commonly used name of the floppy disk device, it may be " -"different on your workstation <phrase arch=\"sparc\">(on Solaris, it is " -"<filename>/dev/fd/0</filename>)</phrase>. The command may return to the " -"prompt before Unix has finished writing the floppy disk, so look for the " -"disk-in-use light on the floppy drive and be sure that the light is out and " -"the disk has stopped revolving before you remove it from the drive. On some " -"systems, you'll have to run a command to eject the floppy from the drive " -"<phrase arch=\"sparc\">(on Solaris, use <command>eject</command>, see the " -"manual page)</phrase>." -msgstr "" - -#. Tag: para -#: install-methods.xml:352 -#, no-c-format -msgid "" -"Some systems attempt to automatically mount a floppy disk when you place it " -"in the drive. You might have to disable this feature before the workstation " -"will allow you to write a floppy in <emphasis>raw mode</emphasis>. " -"Unfortunately, how to accomplish this will vary based on your operating " -"system. <phrase arch=\"sparc\"> On Solaris, you can work around volume " -"management to get raw access to the floppy. First, make sure that the floppy " -"is auto-mounted (using <command>volcheck</command> or the equivalent command " -"in the file manager). Then use a <command>dd</command> command of the form " -"given above, just replace <filename>/dev/fd0</filename> with <filename>/vol/" -"rdsk/<replaceable>floppy_name</replaceable></filename>, where " -"<replaceable>floppy_name</replaceable> is the name the floppy disk was given " -"when it was formatted (unnamed floppies default to the name " -"<filename>unnamed_floppy</filename>). On other systems, ask your system " -"administrator. </phrase>" -msgstr "" - -#. Tag: para -#: install-methods.xml:373 -#, no-c-format -msgid "" -"If writing a floppy on powerpc Linux, you will need to eject it. The " -"<command>eject</command> program handles this nicely; you might need to " -"install it." -msgstr "" - -#. Tag: title -#: install-methods.xml:391 -#, no-c-format -msgid "Writing Disk Images From DOS, Windows, or OS/2" -msgstr "" - -#. Tag: para -#: install-methods.xml:393 -#, no-c-format -msgid "" -"If you have access to an i386 machine, you can use one of the following " -"programs to copy images to floppies." -msgstr "" - -#. Tag: para -#: install-methods.xml:398 -#, no-c-format -msgid "" -"The <command>rawrite1</command> and <command>rawrite2</command> programs can " -"be used under MS-DOS. To use these programs, first make sure that you are " -"booted into DOS. Trying to use these programs from within a DOS box in " -"Windows, or double-clicking on these programs from the Windows Explorer is " -"<emphasis>not</emphasis> expected to work." -msgstr "" - -#. Tag: para -#: install-methods.xml:406 -#, no-c-format -msgid "" -"The <command>rwwrtwin</command> program runs on Windows 95, NT, 98, 2000, " -"ME, XP and probably later versions. To use it you will need to unpack diskio." -"dll in the same directory." -msgstr "" - -#. Tag: para -#: install-methods.xml:412 -#, no-c-format -msgid "" -"These tools can be found on the Official Debian CD-ROMs under the <filename>/" -"tools</filename> directory." -msgstr "" - -#. Tag: title -#: install-methods.xml:425 -#, no-c-format -msgid "Writing Disk Images on Atari Systems" -msgstr "" - -#. Tag: para -#: install-methods.xml:426 -#, no-c-format -msgid "" -"You'll find the &rawwrite.ttp; program in the same directory as the floppy " -"disk images. Start the program by double clicking on the program icon, and " -"type in the name of the floppy image file you want written to the floppy at " -"the TOS program command line dialog box." -msgstr "" - -#. Tag: title -#: install-methods.xml:437 -#, no-c-format -msgid "Writing Disk Images on Macintosh Systems" -msgstr "" - -#. Tag: para -#: install-methods.xml:438 -#, no-c-format -msgid "" -"There is no MacOS application to write images to floppy disks (and there " -"would be no point in doing this as you can't use these floppies to boot the " -"installation system or install kernel and modules from on Macintosh). " -"However, these files are needed for the installation of the operating system " -"and modules, later in the process." -msgstr "" - -#. Tag: title -#: install-methods.xml:456 -#, no-c-format -msgid "Writing Disk Images From MacOS" -msgstr "" - -#. Tag: para -#: install-methods.xml:457 -#, no-c-format -msgid "" -"An AppleScript, <application>Make Debian Floppy</application>, is available " -"for burning floppies from the provided disk image files. It can be " -"downloaded from <ulink url=\"ftp://ftp2.sourceforge.net/pub/sourceforge/d/de/" -"debian-imac/MakeDebianFloppy.sit\"></ulink>. To use it, just unstuff it on " -"your desktop, and then drag any floppy image file to it. You must have " -"Applescript installed and enabled in your extensions manager. Disk Copy will " -"ask you to confirm that you wish to erase the floppy and proceed to write " -"the file image to it." -msgstr "" - -#. Tag: para -#: install-methods.xml:468 -#, no-c-format -msgid "" -"You can also use the MacOS utility <command>Disk Copy</command> directly, or " -"the freeware utility <command>suntar</command>. The <filename>root.bin</" -"filename> file is an example of a floppy image. Use one of the following " -"methods to create a floppy from the floppy image with these utilities." -msgstr "" - -#. Tag: title -#: install-methods.xml:479 -#, no-c-format -msgid "Writing Disk Images with <command>Disk Copy</command>" -msgstr "" - -#. Tag: para -#: install-methods.xml:480 -#, no-c-format -msgid "" -"If you are creating the floppy image from files which were originally on the " -"official &debian; CD, then the Type and Creator are already set correctly. " -"The following <command>Creator-Changer</command> steps are only necessary if " -"you downloaded the image files from a Debian mirror." -msgstr "" - -#. Tag: para -#: install-methods.xml:489 -#, no-c-format -msgid "" -"Obtain <ulink url=\"&url-powerpc-creator-changer;\">Creator-Changer</ulink> " -"and use it to open the <filename>root.bin</filename> file." -msgstr "" - -#. Tag: para -#: install-methods.xml:496 -#, no-c-format -msgid "" -"Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the Type " -"to <userinput>DDim</userinput> (binary floppy image). The case is sensitive " -"for these fields." -msgstr "" - -#. Tag: para -#: install-methods.xml:503 -#, no-c-format -msgid "" -"<emphasis>Important:</emphasis> In the Finder, use <userinput>Get Info</" -"userinput> to display the Finder information about the floppy image, and " -"<quote>X</quote> the <userinput>File Locked</userinput> check box so that " -"MacOS will be unable to remove the boot blocks if the image is accidentally " -"mounted." -msgstr "" - -#. Tag: para -#: install-methods.xml:512 -#, no-c-format -msgid "" -"Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it " -"will very likely be there already, otherwise try <ulink url=\"&url-powerpc-" -"diskcopy;\"></ulink>." -msgstr "" - -#. Tag: para -#: install-methods.xml:519 -#, no-c-format -msgid "" -"Run <command>Disk Copy</command>, and select <menuchoice> " -"<guimenu>Utilities</guimenu> <guimenuitem>Make a Floppy</guimenuitem> </" -"menuchoice>, then select the <emphasis>locked</emphasis> image file from the " -"resulting dialog. It will ask you to insert a floppy, then ask if you really " -"want to erase it. When done it should eject the floppy." -msgstr "" - -#. Tag: title -#: install-methods.xml:534 -#, no-c-format -msgid "Writing Disk Images with <command>suntar</command>" -msgstr "" - -#. Tag: para -#: install-methods.xml:538 -#, no-c-format -msgid "" -"Obtain <command>suntar</command> from <ulink url=\"&url-powerpc-suntar;\"> </" -"ulink>. Start the <command>suntar</command> program and select " -"<quote>Overwrite Sectors...</quote> from the <userinput>Special</userinput> " -"menu." -msgstr "" - -#. Tag: para -#: install-methods.xml:546 -#, no-c-format -msgid "" -"Insert the floppy disk as requested, then hit &enterkey; (start at sector 0)." -msgstr "" - -#. Tag: para -#: install-methods.xml:552 -#, no-c-format -msgid "" -"Select the <filename>root.bin</filename> file in the file-opening dialog." -msgstr "" - -#. Tag: para -#: install-methods.xml:557 -#, no-c-format -msgid "" -"After the floppy has been created successfully, select <menuchoice> " -"<guimenu>File</guimenu> <guimenuitem>Eject</guimenuitem> </menuchoice>. If " -"there are any errors writing the floppy, simply toss that floppy and try " -"another." -msgstr "" - -#. Tag: para -#: install-methods.xml:565 -#, no-c-format -msgid "" -"Before using the floppy you created, <emphasis>set the write protect tab</" -"emphasis>! Otherwise if you accidentally mount it in MacOS, MacOS will " -"helpfully ruin it." -msgstr "" - -#. Tag: title -#: install-methods.xml:584 -#, no-c-format -msgid "Preparing Files for USB Memory Stick Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:586 -#, no-c-format -msgid "" -"For preparing the USB stick you will need a system where GNU/Linux is " -"already running and where USB is supported. You should ensure that the usb-" -"storage kernel module is loaded (<userinput>modprobe usb-storage</" -"userinput>) and try to find out which SCSI device the USB stick has been " -"mapped to (in this example <filename>/dev/sda</filename> is used). To write " -"to your stick, you will probably have to turn off its write protection " -"switch." -msgstr "" - -#. Tag: para -#: install-methods.xml:596 -#, no-c-format -msgid "" -"Note, that the USB stick should be at least 128 MB in size (smaller setups " -"are possible if you follow <xref linkend=\"usb-copy-flexible\"/>)." -msgstr "" - -#. Tag: title -#: install-methods.xml:604 -#, no-c-format -msgid "Copying the files — the easy way" -msgstr "" - -#. Tag: para -#: install-methods.xml:605 -#, no-c-format -msgid "" -"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which " -"contains all the installer files (including the kernel) as well as " -"<command>SYSLINUX</command> and its configuration file. You only have to " -"extract it directly to your USB stick:" -msgstr "" - -#. Tag: screen -#: install-methods.xml:612 -#, no-c-format -msgid "# zcat boot.img.gz > /dev/<replaceable>sda</replaceable>" -msgstr "" - -#. Tag: para -#: install-methods.xml:614 -#, no-c-format -msgid "" -"There is an all-in-one file <filename>hd-media/boot.img.gz</filename> which " -"contains all the installer files (including the kernel) as well as " -"<command>yaboot</command> and its configuration file. Create a partition of " -"type \"Apple_Bootstrap\" on your USB stick using <command>mac-fdisk</" -"command>'s <userinput>C</userinput> command and extract the image directly " -"to that:" -msgstr "" - -#. Tag: screen -#: install-methods.xml:623 -#, no-c-format -msgid "# zcat boot.img.gz > /dev/<replaceable>sda2</replaceable>" -msgstr "" - -#. Tag: para -#: install-methods.xml:626 -#, no-c-format -msgid "" -"Using this method will destroy anything already on the device. Make sure " -"that you use the correct device name for your USB stick." -msgstr "" - -#. Tag: para -#: install-methods.xml:632 -#, no-c-format -msgid "" -"After that, mount the USB memory stick (<userinput>mount <replaceable arch=" -"\"i386\">/dev/sda</replaceable> <replaceable arch=\"powerpc\">/dev/sda2</" -"replaceable> /mnt</userinput>), which will now have <phrase arch=\"i386\">a " -"FAT filesystem</phrase> <phrase arch=\"powerpc\">an HFS filesystem</phrase> " -"on it, and copy a Debian netinst or businesscard ISO image to it. Please " -"note that the file name must end in <filename>.iso</filename>. Unmount the " -"stick (<userinput>umount /mnt</userinput>) and you are done." -msgstr "" - -#. Tag: title -#: install-methods.xml:648 -#, no-c-format -msgid "Copying the files — the flexible way" -msgstr "" - -#. Tag: para -#: install-methods.xml:649 -#, no-c-format -msgid "" -"If you like more flexibility or just want to know what's going on, you " -"should use the following method to put the files on your stick." -msgstr "" - -#. Tag: title -#: install-methods.xml:661 install-methods.xml:753 -#, no-c-format -msgid "USB stick partitioning on &arch-title;" -msgstr "" - -#. Tag: para -#: install-methods.xml:662 -#, no-c-format -msgid "" -"We will show how to setup the memory stick to use the first partition, " -"instead of the entire device." -msgstr "" - -#. Tag: para -#: install-methods.xml:667 -#, no-c-format -msgid "" -"Since most USB sticks come pre-configured with a single FAT16 partition, you " -"probably won't have to repartition or reformat the stick. If you have to do " -"that anyway, use <command>cfdisk</command> or any other partitioning tool " -"for creating a FAT16 partition and then create the filesystem using: " -"<informalexample><screen>\n" -"# mkdosfs /dev/<replaceable>sda1</replaceable>\n" -"</screen></informalexample> Take care that you use the correct device name " -"for your USB stick. The <command>mkdosfs</command> command is contained in " -"the <classname>dosfstools</classname> Debian package." -msgstr "" - -#. Tag: para -#: install-methods.xml:681 -#, no-c-format -msgid "" -"In order to start the kernel after booting from the USB stick, we will put a " -"boot loader on the stick. Although any boot loader (e.g. <command>LILO</" -"command>) should work, it's convenient to use <command>SYSLINUX</command>, " -"since it uses a FAT16 partition and can be reconfigured by just editing a " -"text file. Any operating system which supports the FAT file system can be " -"used to make changes to the configuration of the boot loader." -msgstr "" - -#. Tag: para -#: install-methods.xml:691 -#, no-c-format -msgid "" -"To put <command>SYSLINUX</command> on the FAT16 partition on your USB stick, " -"install the <classname>syslinux</classname> and <classname>mtools</" -"classname> packages on your system, and do: <informalexample><screen>\n" -"# syslinux /dev/<replaceable>sda1</replaceable>\n" -"</screen></informalexample> Again, take care that you use the correct device " -"name. The partition must not be mounted when starting <command>SYSLINUX</" -"command>. This procedure writes a boot sector to the partition and creates " -"the file <filename>ldlinux.sys</filename> which contains the boot loader " -"code." -msgstr "" - -#. Tag: para -#: install-methods.xml:704 -#, no-c-format -msgid "" -"Mount the partition (<userinput>mount /dev/sda1 /mnt</userinput>) and copy " -"the following files from the Debian archives to the stick: <itemizedlist> " -"<listitem><para> <filename>vmlinuz</filename> (kernel binary) </para></" -"listitem> <listitem><para> <filename>initrd.gz</filename> (initial ramdisk " -"image) </para></listitem> <listitem><para> <filename>syslinux.cfg</filename> " -"(SYSLINUX configuration file) </para></listitem> <listitem><para> Optional " -"kernel modules </para></listitem> </itemizedlist> If you want to rename the " -"files, please note that <command>SYSLINUX</command> can only process DOS " -"(8.3) file names." -msgstr "" - -#. Tag: para -#: install-methods.xml:735 -#, no-c-format -msgid "" -"The <filename>syslinux.cfg</filename> configuration file should contain the " -"following two lines: <informalexample><screen>\n" -"default vmlinuz\n" -"append initrd=initrd.gz ramdisk_size=12000 root=/dev/ram rw\n" -"</screen></informalexample> Please note that the <userinput>ramdisk_size</" -"userinput> parameter may need to be increased, depending on the image you " -"are booting." -msgstr "" - -#. Tag: para -#: install-methods.xml:754 -#, no-c-format -msgid "" -"Most USB sticks do not come pre-configured in such a way that Open Firmware " -"can boot from them, so you will need to repartition the stick. On Mac " -"systems, run <userinput>mac-fdisk /dev/sda</userinput>, initialise a new " -"partition map using the <userinput>i</userinput> command, and create a new " -"partition of type Apple_Bootstrap using the <userinput>C</userinput> " -"command. (Note that the first \"partition\" will always be the partition map " -"itself.) Then type <informalexample><screen>\n" -"$ hformat /dev/<replaceable>sda2</replaceable>\n" -"</screen></informalexample> Take care that you use the correct device name " -"for your USB stick. The <command>hformat</command> command is contained in " -"the <classname>hfsutils</classname> Debian package." -msgstr "" - -#. Tag: para -#: install-methods.xml:770 -#, no-c-format -msgid "" -"In order to start the kernel after booting from the USB stick, we will put a " -"boot loader on the stick. The <command>yaboot</command> boot loader can be " -"installed on an HFS filesystem and can be reconfigured by just editing a " -"text file. Any operating system which supports the HFS file system can be " -"used to make changes to the configuration of the boot loader." -msgstr "" - -#. Tag: para -#: install-methods.xml:779 -#, no-c-format -msgid "" -"The normal <command>ybin</command> tool that comes with <command>yaboot</" -"command> does not yet understand USB storage devices, so you will have to " -"install <command>yaboot</command> by hand using the <classname>hfsutils</" -"classname> tools. Type <informalexample><screen>\n" -"$ hmount /dev/sda2\n" -"$ hcopy -r /usr/lib/yaboot/yaboot :\n" -"$ hattrib -c UNIX -t tbxi :yaboot\n" -"$ hattrib -b :\n" -"$ humount\n" -"</screen></informalexample> Again, take care that you use the correct device " -"name. The partition must not be otherwise mounted during this procedure. " -"This procedure writes the boot loader to the partition, and uses the HFS " -"utilities to mark it in such a way that Open Firmware will boot it. Having " -"done this, the rest of the USB stick may be prepared using the normal Unix " -"utilities." -msgstr "" - -#. Tag: para -#: install-methods.xml:795 -#, no-c-format -msgid "" -"Mount the partition (<userinput>mount /dev/sda2 /mnt</userinput>) and copy " -"the following files from the Debian archives to the stick:" -msgstr "" - -#. Tag: para -#: install-methods.xml:801 -#, no-c-format -msgid "<filename>vmlinux</filename> (kernel binary)" -msgstr "" - -#. Tag: para -#: install-methods.xml:806 -#, no-c-format -msgid "<filename>initrd.gz</filename> (initial ramdisk image)" -msgstr "" - -#. Tag: para -#: install-methods.xml:811 -#, no-c-format -msgid "<filename>yaboot.conf</filename> (yaboot configuration file)" -msgstr "" - -#. Tag: para -#: install-methods.xml:816 -#, no-c-format -msgid "<filename>boot.msg</filename> (optional boot message)" -msgstr "" - -#. Tag: para -#: install-methods.xml:821 -#, no-c-format -msgid "Optional kernel modules" -msgstr "" - -#. Tag: para -#: install-methods.xml:828 -#, no-c-format -msgid "" -"The <filename>yaboot.conf</filename> configuration file should contain the " -"following lines: <informalexample><screen>\n" -"default=install\n" -"root=/dev/ram\n" -"\n" -"message=/boot.msg\n" -"\n" -"image=/vmlinux\n" -" label=install\n" -" initrd=/initrd.gz\n" -" initrd-size=10000\n" -" read-only\n" -"</screen></informalexample> Please note that the <userinput>initrd-size</" -"userinput> parameter may need to be increased, depending on the image you " -"are booting." -msgstr "" - -#. Tag: title -#: install-methods.xml:843 -#, no-c-format -msgid "Adding an ISO image" -msgstr "" - -#. Tag: para -#: install-methods.xml:844 -#, no-c-format -msgid "" -"Now you should put any Debian ISO image (businesscard, netinst or even a " -"full one) onto your stick (if it fits). The file name of such an image must " -"end in <filename>.iso</filename>." -msgstr "" - -#. Tag: para -#: install-methods.xml:850 -#, no-c-format -msgid "" -"If you want to install over the network, without using an ISO image, you " -"will of course skip the previous step. Moreover you will have to use the " -"initial ramdisk from the <filename>netboot</filename> directory instead of " -"the one from <filename>hd-media</filename>, because <filename>hd-media/" -"initrd.gz</filename> does not have network support." -msgstr "" - -#. Tag: para -#: install-methods.xml:859 -#, no-c-format -msgid "" -"When you are done, unmount the USB memory stick (<userinput>umount /mnt</" -"userinput>) and activate its write protection switch." -msgstr "" - -#. Tag: title -#: install-methods.xml:869 -#, no-c-format -msgid "Booting the USB stick" -msgstr "" - -#. Tag: para -#: install-methods.xml:870 -#, no-c-format -msgid "" -"If your system refuses to boot from the memory stick, the stick may contain " -"an invalid master boot record (MBR). To fix this, use the <command>install-" -"mbr</command> command from the package <classname>mbr</classname>:" -msgstr "" - -#. Tag: screen -#: install-methods.xml:877 -#, no-c-format -msgid "# install-mbr /dev/<replaceable>sda</replaceable>" -msgstr "" - -#. Tag: title -#: install-methods.xml:889 -#, no-c-format -msgid "Preparing Files for Hard Disk Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:890 -#, no-c-format -msgid "" -"The installer may be booted using boot files placed on an existing hard " -"drive partition, either launched from another operating system or by " -"invoking a boot loader directly from the BIOS." -msgstr "" - -#. Tag: para -#: install-methods.xml:896 -#, no-c-format -msgid "" -"A full, <quote>pure network</quote> installation can be achieved using this " -"technique. This avoids all hassles of removable media, like finding and " -"burning CD images or struggling with too numerous and unreliable floppy " -"disks." -msgstr "" - -#. Tag: para -#: install-methods.xml:903 -#, no-c-format -msgid "The installer cannot boot from files on an NTFS file system." -msgstr "" - -#. Tag: para -#: install-methods.xml:907 -#, no-c-format -msgid "" -"The installer cannot boot from files on an HFS+ file system. MacOS System " -"8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To " -"determine whether your existing file system is HFS+, select <userinput>Get " -"Info</userinput> for the volume in question. HFS file systems appear as " -"<userinput>Mac OS Standard</userinput>, while HFS+ file systems say " -"<userinput>Mac OS Extended</userinput>. You must have an HFS partition in " -"order to exchange files between MacOS and Linux, in particular the " -"installation files you download." -msgstr "" - -#. Tag: para -#: install-methods.xml:918 -#, no-c-format -msgid "" -"Different programs are used for hard disk installation system booting, " -"depending on whether the system is a <quote>NewWorld</quote> or an " -"<quote>OldWorld</quote> model." -msgstr "" - -#. Tag: title -#: install-methods.xml:927 -#, no-c-format -msgid "" -"Hard disk installer booting using <command>LILO</command> or <command>GRUB</" -"command>" -msgstr "" - -#. Tag: para -#: install-methods.xml:929 -#, no-c-format -msgid "" -"This section explains how to add to or even replace an existing linux " -"installation using either <command>LILO</command> or <command>GRUB</command>." -msgstr "" - -#. Tag: para -#: install-methods.xml:935 -#, no-c-format -msgid "" -"At boot time, both bootloaders support loading in memory not only the " -"kernel, but also a disk image. This RAM disk can be used as the root file-" -"system by the kernel." -msgstr "" - -#. Tag: para -#: install-methods.xml:941 -#, no-c-format -msgid "" -"Copy the following files from the Debian archives to a convenient location " -"on your hard drive, for instance to <filename>/boot/newinstall/</filename>." -msgstr "" - -#. Tag: para -#: install-methods.xml:948 -#, no-c-format -msgid "<filename>vmlinuz</filename> (kernel binary)" -msgstr "" - -#. Tag: para -#: install-methods.xml:953 -#, no-c-format -msgid "<filename>initrd.gz</filename> (ramdisk image)" -msgstr "" - -#. Tag: para -#: install-methods.xml:960 -#, no-c-format -msgid "" -"Finally, to configure the bootloader proceed to <xref linkend=\"boot-initrd" -"\"/>." -msgstr "" - -#. Tag: title -#: install-methods.xml:970 -#, no-c-format -msgid "Hard Disk Installer Booting for OldWorld Macs" -msgstr "" - -#. Tag: para -#: install-methods.xml:971 -#, no-c-format -msgid "" -"The <filename>boot-floppy-hfs</filename> floppy uses <application>miBoot</" -"application> to launch Linux installation, but <application>miBoot</" -"application> cannot easily be used for hard disk booting. " -"<application>BootX</application>, launched from MacOS, supports booting from " -"files placed on the hard disk. <application>BootX</application> can also be " -"used to dual-boot MacOS and Linux after your Debian installation is " -"complete. For the Performa 6360, it appears that <command>quik</command> " -"cannot make the hard disk bootable. So <application>BootX</application> is " -"required on that model." -msgstr "" - -#. Tag: para -#: install-methods.xml:984 -#, no-c-format -msgid "" -"Download and unstuff the <application>BootX</application> distribution, " -"available from <ulink url=\"&url-powerpc-bootx;\"></ulink>, or in the " -"<filename>dists/woody/main/disks-powerpc/current/powermac</filename> " -"directory on Debian http/ftp mirrors and official Debian CDs. Use " -"<application>Stuffit Expander</application> to extract it from its archive. " -"Within the package, there is an empty folder called <filename>Linux Kernels</" -"filename>. Download <filename>linux.bin</filename> and <filename>ramdisk." -"image.gz</filename> from the <filename>disks-powerpc/current/powermac</" -"filename> folder, and place them in the <filename>Linux Kernels</filename> " -"folder. Then place the <filename>Linux Kernels</filename> folder in the " -"active System Folder." -msgstr "" - -#. Tag: title -#: install-methods.xml:1004 -#, no-c-format -msgid "Hard Disk Installer Booting for NewWorld Macs" -msgstr "" - -#. Tag: para -#: install-methods.xml:1005 -#, no-c-format -msgid "" -"NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as " -"well as loading ELF binaries directly from the hard disk. These machines " -"will boot Linux directly via <command>yaboot</command>, which supports " -"loading a kernel and RAMdisk directly from an ext2 partition, as well as " -"dual-booting with MacOS. Hard disk booting of the installer is particularly " -"appropriate for newer machines without floppy drives. <command>BootX</" -"command> is not supported and must not be used on NewWorld PowerMacs." -msgstr "" - -#. Tag: para -#: install-methods.xml:1016 -#, no-c-format -msgid "" -"<emphasis>Copy</emphasis> (not move) the following four files which you " -"downloaded earlier from the Debian archives, onto the root level of your " -"hard drive (this can be accomplished by <keycap>option</keycap>-dragging " -"each file to the hard drive icon)." -msgstr "" - -#. Tag: filename -#: install-methods.xml:1026 -#, no-c-format -msgid "vmlinux" -msgstr "" - -#. Tag: filename -#: install-methods.xml:1031 -#, no-c-format -msgid "initrd.gz" -msgstr "" - -#. Tag: filename -#: install-methods.xml:1036 -#, no-c-format -msgid "yaboot" -msgstr "" - -#. Tag: filename -#: install-methods.xml:1041 -#, no-c-format -msgid "yaboot.conf" -msgstr "" - -#. Tag: para -#: install-methods.xml:1046 -#, no-c-format -msgid "" -"Make a note of the partition number of the MacOS partition where you place " -"these files. If you have the MacOS <command>pdisk</command> program, you can " -"use the L command to check for the partition number. You will need this " -"partition number for the command you type at the Open Firmware prompt when " -"you boot the installer." -msgstr "" - -#. Tag: para -#: install-methods.xml:1054 -#, no-c-format -msgid "To boot the installer, proceed to <xref linkend=\"boot-newworld\"/>." -msgstr "" - -#. Tag: title -#: install-methods.xml:1067 -#, no-c-format -msgid "Preparing Files for TFTP Net Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1068 -#, no-c-format -msgid "" -"If your machine is connected to a local area network, you may be able to " -"boot it over the network from another machine, using TFTP. If you intend to " -"boot the installation system from another machine, the boot files will need " -"to be placed in specific locations on that machine, and the machine " -"configured to support booting of your specific machine." -msgstr "" - -#. Tag: para -#: install-methods.xml:1076 -#, 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>." -msgstr "" - -#. Tag: para -#: install-methods.xml:1082 -#, 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>" -msgstr "" - -#. Tag: para -#: install-methods.xml:1099 -#, 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:1105 -#, 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:1122 -#, 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:1127 -#, 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:1135 -#, 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:1153 -#, no-c-format -msgid "Setting up RARP server" -msgstr "" - -#. Tag: para -#: install-methods.xml:1154 -#, no-c-format -msgid "" -"To setup 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:1166 -#, no-c-format -msgid "" -"On a RARP server system using a Linux 2.2.x kernel, you need to populate the " -"kernel's RARP table. To do this, run the following commands: " -"<informalexample><screen>\n" -"# <userinput>/sbin/rarp -s\n" -"<replaceable>client-hostname</replaceable>\n" -"<replaceable>client-enet-addr</replaceable></userinput>\n" -"\n" -"# <userinput>/usr/sbin/arp -s\n" -"<replaceable>client-ip</replaceable>\n" -"<replaceable>client-enet-addr</replaceable></userinput>\n" -"</screen></informalexample> If you get <informalexample><screen>\n" -"SIOCSRARP: Invalid argument\n" -"</screen></informalexample> you probably need to load the RARP kernel module " -"or else recompile the kernel to support RARP. Try <userinput>modprobe rarp</" -"userinput> and then try the <command>rarp</command> command again." -msgstr "" - -#. Tag: para -#: install-methods.xml:1182 -#, no-c-format -msgid "" -"On a RARP server system using a Linux 2.4.x kernel, there is no RARP module, " -"and you should instead use the <command>rarpd</command> program. The " -"procedure is similar to that used under SunOS in the following paragraph." -msgstr "" - -#. Tag: para -#: install-methods.xml:1190 -#, no-c-format -msgid "" -"Under SunOS, 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. In " -"SunOS 4, issue the command (as root): <userinput>/usr/etc/rarpd -a</" -"userinput>; in SunOS 5, use <userinput>/usr/sbin/rarpd -a</userinput>." -msgstr "" - -#. Tag: title -#: install-methods.xml:1209 -#, no-c-format -msgid "Setting up BOOTP server" -msgstr "" - -#. Tag: para -#: install-methods.xml:1210 -#, no-c-format -msgid "" -"There are two BOOTP servers available for GNU/Linux, the CMU " -"<command>bootpd</command> and the other is actually a DHCP server, ISC " -"<command>dhcpd</command>, which are contained in the <classname>bootp</" -"classname> and <classname>dhcp</classname> packages in &debian;." -msgstr "" - -#. Tag: para -#: install-methods.xml:1218 -#, 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. Elsewhere, the line in " -"question should look like: <informalexample><screen>\n" -"bootps dgram udp wait root /usr/sbin/bootpd bootpd -i -t 120\n" -"</screen></informalexample> Now, you must create an <filename>/etc/bootptab</" -"filename> file. This has the same sort of familiar and cryptic format as the " -"good old BSD <filename>printcap</filename>, <filename>termcap</filename>, " -"and <filename>disktab</filename> files. See the <filename>bootptab</" -"filename> manual page for more information. For CMU <command>bootpd</" -"command>, you will need to know the hardware (MAC) address of the client. " -"Here is an example <filename>/etc/bootptab</filename>: " -"<informalexample><screen>\n" -"client:\\\n" -" hd=/tftpboot:\\\n" -" bf=tftpboot.img:\\\n" -" ip=192.168.1.90:\\\n" -" sm=255.255.255.0:\\\n" -" sa=192.168.1.1:\\\n" -" ha=0123456789AB:\n" -"</screen></informalexample> You will need to change at least the <quote>ha</" -"quote> option, which specifies the hardware address of the client. The " -"<quote>bf</quote> option specifies the file a client should retrieve via " -"TFTP; see <xref linkend=\"tftp-images\"/> for more details. <phrase arch=" -"\"mips\"> On SGI machines you can just enter the command monitor and type " -"<userinput>printenv</userinput>. The value of the <userinput>eaddr</" -"userinput> variable is the machine's MAC address. </phrase>" -msgstr "" - -#. Tag: para -#: install-methods.xml:1251 -#, 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>." -msgstr "" - -#. Tag: title -#: install-methods.xml:1272 -#, no-c-format -msgid "Setting up a DHCP server" -msgstr "" - -#. Tag: para -#: install-methods.xml:1273 -#, 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" -"default-lease-time 600;\n" -"max-lease-time 7200;\n" -"server-name \"servername\";\n" -"\n" -"subnet 192.168.1.0 netmask 255.255.255.0 {\n" -" range 192.168.1.200 192.168.1.253;\n" -" option routers 192.168.1.1;\n" -"}\n" -"\n" -"host clientname {\n" -" filename \"/tftpboot/tftpboot.img\";\n" -" server-name \"servername\";\n" -" 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:1285 -#, 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:1295 -#, no-c-format -msgid "" -"After you have edited the <command>dhcpd</command> configuration file, " -"restart it with <userinput>/etc/init.d/dhcpd restart</userinput>." -msgstr "" - -#. Tag: title -#: install-methods.xml:1303 -#, no-c-format -msgid "Enabling PXE Booting in the DHCP configuration" -msgstr "" - -#. Tag: para -#: install-methods.xml:1304 -#, 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" -"option domain-name \"example.com\";\n" -"\n" -"default-lease-time 600;\n" -"max-lease-time 7200;\n" -"\n" -"allow booting;\n" -"allow bootp;\n" -"\n" -"# The next paragraph needs to be modified to fit your case\n" -"subnet 192.168.1.0 netmask 255.255.255.0 {\n" -" range 192.168.1.200 192.168.1.253;\n" -" option broadcast-address 192.168.1.255;\n" -"# the gateway address which can be different\n" -"# (access to the internet for instance)\n" -" option routers 192.168.1.1;\n" -"# indicate the dns you want to use\n" -" option domain-name-servers 192.168.1.3;\n" -"}\n" -"\n" -"group {\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" -" }\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:1320 -#, no-c-format -msgid "Enabling the TFTP Server" -msgstr "" - -#. Tag: para -#: install-methods.xml:1321 -#, 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" -"tftp dgram udp wait nobody /usr/sbin/tcpd in.tftpd /tftpboot\n" -"</screen></informalexample> Debian packages will in general set this up " -"correctly by default when they are installed." -msgstr "" - -#. Tag: para -#: install-methods.xml:1332 -#, 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>." -msgstr "" - -#. Tag: para -#: install-methods.xml:1346 -#, 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" -"# echo 1 > /proc/sys/net/ipv4/ip_no_pmtu_disc\n" -"</screen></informalexample> to turn off Path MTU discovery, otherwise the " -"SGI's PROM can't download the kernel. Furthermore, make sure TFTP packets " -"are sent from a source port no greater than 32767, or the download will " -"stall after the first packet. Again, it's Linux 2.4.X tripping this bug in " -"the PROM, and you can avoid it by setting <informalexample><screen>\n" -"# echo \"2048 32767\" > /proc/sys/net/ipv4/ip_local_port_range\n" -"</screen></informalexample> to adjust the range of source ports the Linux " -"TFTP server uses." -msgstr "" - -#. Tag: title -#: install-methods.xml:1368 -#, no-c-format -msgid "Move TFTP Images Into Place" -msgstr "" - -#. Tag: para -#: install-methods.xml:1369 -#, 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." -msgstr "" - -#. Tag: para -#: install-methods.xml:1379 -#, 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:1388 -#, 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." -msgstr "" - -#. Tag: para -#: install-methods.xml:1396 -#, 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:1408 -#, no-c-format -msgid "DECstation TFTP Images" -msgstr "" - -#. Tag: para -#: install-methods.xml:1409 -#, 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 " -"<replaceable>subarchitecture</replaceable>/netboot-boot.img. 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:1418 -#, 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:1430 -#, no-c-format -msgid "boot #/tftp/filename param1=value1 param2=value2 ..." -msgstr "" - -#. Tag: para -#: install-methods.xml:1432 -#, 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:1470 -#, no-c-format -msgid "Alpha TFTP Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1471 -#, 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:1486 -#, no-c-format -msgid "SPARC TFTP Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1487 -#, no-c-format -msgid "" -"SPARC architectures for instance use the subarchitecture names, such as " -"<quote>SUN4M</quote> or <quote>SUN4C</quote>; in some cases, the " -"architecture is left blank, so the file the client looks for is just " -"<filename>client-ip-in-hex</filename>. Thus, if your system subarchitecture " -"is a SUN4C, and its IP is 192.168.1.3, the filename would be " -"<filename>C0A80103.SUN4C</filename>. An easy way to determine this is to " -"enter the following command in a shell (assuming the machine's intended IP " -"is 10.0.0.4). <informalexample><screen>\n" -"$ printf '%.2x%.2x%.2x%.2x\\n' 10 0 0 4\n" -"</screen></informalexample> This will spit out the IP in hexadecimal; to get " -"to the correct filename, you will need to change all letters to uppercase " -"and if necessary append the subarchitecture name." -msgstr "" - -#. Tag: para -#: install-methods.xml:1504 -#, 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:1515 -#, no-c-format -msgid "BVM/Motorola TFTP Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1516 -#, 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:1521 -#, 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:1533 -#, no-c-format -msgid "SGI TFTP Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1534 -#, 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:1546 -#, no-c-format -msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" -msgstr "" - -#. Tag: para -#: install-methods.xml:1547 -#, 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 the loaded to CFE." -msgstr "" - -#. Tag: title -#: install-methods.xml:1652 -#, no-c-format -msgid "Automatic Installation" -msgstr "" - -#. Tag: para -#: install-methods.xml:1653 -#, 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:1666 -#, no-c-format -msgid "Automatic Installation Using the Debian Installer" -msgstr "" - -#. Tag: para -#: install-methods.xml:1667 -#, 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:1674 -#, 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/pl/installation-howto.po b/po/pl/installation-howto.po deleted file mode 100644 index 68b617cdf..000000000 --- a/po/pl/installation-howto.po +++ /dev/null @@ -1,445 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: installation-howto.xml:5 -#, no-c-format -msgid "Installation Howto" -msgstr "" - -#. Tag: para -#: installation-howto.xml:7 -#, no-c-format -msgid "" -"This document describes how to install &debian; &releasename; for the &arch-" -"title; (<quote>&architecture;</quote>) with the new &d-i;. It is a quick " -"walkthrough of the installation process which should contain all the " -"information you will need for most installs. When more information can be " -"useful, we will link to more detailed explanations in the <link linkend=" -"\"debian_installation_guide\">&debian; Installation Guide</link>." -msgstr "" - -#. Tag: title -#: installation-howto.xml:20 -#, no-c-format -msgid "Preliminaries" -msgstr "" - -#. Tag: para -#: installation-howto.xml:21 -#, no-c-format -msgid "" -"<phrase condition=\"unofficial-build\"> The debian-installer is still in a " -"beta state. </phrase> If you encounter bugs during your install, please " -"refer to <xref linkend=\"submit-bug\"/> for instructions on how to report " -"them. If you have questions which cannot be answered by this document, " -"please direct them to the debian-boot mailing list (&email-debian-boot-" -"list;) or ask on IRC (#debian-boot on the freenode network)." -msgstr "" - -#. Tag: title -#: installation-howto.xml:37 -#, no-c-format -msgid "Booting the installer" -msgstr "" - -#. Tag: para -#: installation-howto.xml:38 -#, no-c-format -msgid "" -"<phrase condition=\"unofficial-build\"> For some quick links to CD images, " -"check out the <ulink url=\"&url-d-i;\"> &d-i; home page</ulink>. </phrase> " -"The debian-cd team provides builds of CD images using &d-i; on the <ulink " -"url=\"&url-debian-cd;\">Debian CD page</ulink>. For more information on " -"where to get CDs, see <xref linkend=\"official-cdrom\"/>." -msgstr "" - -#. Tag: para -#: installation-howto.xml:48 -#, no-c-format -msgid "" -"Some installation methods require other images than CD images. <phrase " -"condition=\"unofficial-build\"> The <ulink url=\"&url-d-i;\">&d-i; home " -"page</ulink> has links to other images. </phrase> <xref linkend=\"where-files" -"\"/> explains how to find images on Debian mirrors." -msgstr "" - -#. Tag: para -#: installation-howto.xml:58 -#, no-c-format -msgid "" -"The subsections below will give the details about which images you should " -"get for each possible means of installation." -msgstr "" - -#. Tag: title -#: installation-howto.xml:66 -#, no-c-format -msgid "CDROM" -msgstr "" - -#. Tag: para -#: installation-howto.xml:68 -#, no-c-format -msgid "" -"There are two different netinst CD images which can be used to install " -"&releasename; with the &d-i;. These images are intended to boot from CD and " -"install additional packages over a network, hence the name 'netinst'. The " -"difference between the two images is that on the full netinst image the base " -"packages are included, whereas you have to download these from the web if " -"you are using the business card image. If you'd rather, you can get a full " -"size CD image which will not need the network to install. You only need the " -"first CD of the set." -msgstr "" - -#. Tag: para -#: installation-howto.xml:79 -#, no-c-format -msgid "" -"Download whichever type you prefer and burn it to a CD. <phrase arch=\"i386" -"\">To boot the CD, you may need to change your BIOS configuration, as " -"explained in <xref linkend=\"bios-setup\"/>.</phrase> <phrase arch=\"powerpc" -"\"> To boot a PowerMac from CD, press the <keycap>c</keycap> key while " -"booting. See <xref linkend=\"boot-cd\"/> for other ways to boot from CD. </" -"phrase>" -msgstr "" - -#. Tag: title -#: installation-howto.xml:93 -#, no-c-format -msgid "Floppy" -msgstr "" - -#. Tag: para -#: installation-howto.xml:94 -#, no-c-format -msgid "" -"If you can't boot from CD, you can download floppy images to install Debian. " -"You need the <filename>floppy/boot.img</filename>, the <filename>floppy/root." -"img</filename> and possibly one of the driver disks." -msgstr "" - -#. Tag: para -#: installation-howto.xml:100 -#, no-c-format -msgid "" -"The boot floppy is the one with <filename>boot.img</filename> on it. This " -"floppy, when booted, will prompt you to insert a second floppy — use " -"the one with <filename>root.img</filename> on it." -msgstr "" - -#. Tag: para -#: installation-howto.xml:106 -#, no-c-format -msgid "" -"If you're planning to install over the network, you will usually need the " -"<filename>floppy/net-drivers.img</filename>, which contains additional " -"drivers for many ethernet cards, and support for PCMCIA." -msgstr "" - -#. Tag: para -#: installation-howto.xml:112 -#, no-c-format -msgid "" -"If you have a CD, but cannot boot from it, then boot from floppies and use " -"<filename>floppy/cd-drivers.img</filename> on a driver disk to complete the " -"install using the CD." -msgstr "" - -#. Tag: para -#: installation-howto.xml:118 -#, no-c-format -msgid "" -"Floppy disks are one of the least reliable media around, so be prepared for " -"lots of bad disks (see <xref linkend=\"unreliable-floppies\"/>). Each " -"<filename>.img</filename> file you downloaded goes on a single floppy; you " -"can use the dd command to write it to /dev/fd0 or some other means (see " -"<xref linkend=\"create-floppy\"/> for details). Since you'll have more than " -"one floppy, it's a good idea to label them." -msgstr "" - -#. Tag: title -#: installation-howto.xml:131 -#, no-c-format -msgid "USB memory stick" -msgstr "" - -#. Tag: para -#: installation-howto.xml:132 -#, no-c-format -msgid "" -"It's also possible to install from removable USB storage devices. For " -"example a USB keychain can make a handy Debian install medium that you can " -"take with you anywhere." -msgstr "" - -#. Tag: para -#: installation-howto.xml:138 -#, no-c-format -msgid "" -"The easiest way to prepare your USB memory stick is to download <filename>hd-" -"media/boot.img.gz</filename>, and use gunzip to extract the 128 MB image " -"from that file. Write this image directly to your memory stick, which must " -"be at least 128 mb in size. Of course this will destroy anything already on " -"the memory stick. Then mount the memory stick, which will now have a FAT " -"filesystem on it. Next, download a Debian netinst CD image, and copy that " -"file to the memory stick; any filename is ok as long as it ends in <literal>." -"iso</literal>." -msgstr "" - -#. Tag: para -#: installation-howto.xml:149 -#, no-c-format -msgid "" -"There are other, more flexible ways to set up a memory stick to use the " -"debian-installer, and it's possible to get it to work with smaller memory " -"sticks. For details, see <xref linkend=\"boot-usb-files\"/>." -msgstr "" - -#. Tag: para -#: installation-howto.xml:155 -#, no-c-format -msgid "" -"Some BIOSes can boot USB storage directly, and some cannot. You may need to " -"configure your BIOS to boot from a <quote>removable drive</quote> or even a " -"<quote>USB-ZIP</quote> to get it to boot from the USB device. If it doesn't, " -"you can boot from one floppy and use the USB stick for the rest of the " -"install. For helpful hints and details, see <xref linkend=\"usb-boot\"/>." -msgstr "" - -#. Tag: para -#: installation-howto.xml:163 -#, no-c-format -msgid "" -"Booting Macintosh systems from USB storage devices involves manual use of " -"Open Firmware. For directions, see <xref linkend=\"usb-boot\"/>." -msgstr "" - -#. Tag: title -#: installation-howto.xml:172 -#, no-c-format -msgid "Booting from network" -msgstr "" - -#. Tag: para -#: installation-howto.xml:173 -#, no-c-format -msgid "" -"It's also possible to boot &d-i; completely from the net. The various " -"methods to netboot depend on your architecture and netboot setup. The files " -"in <filename>netboot/</filename> can be used to netboot &d-i;." -msgstr "" - -#. Tag: para -#: installation-howto.xml:179 -#, no-c-format -msgid "" -"The easiest thing to set up is probably PXE netbooting. Untar the file " -"<filename>netboot/pxeboot.tar.gz</filename> into <filename>/var/lib/" -"tftpboot</filename> or wherever is appropriate for your tftp server. Set up " -"your DHCP server to pass filename <filename>/pxelinux.0</filename> to " -"clients, and with luck everything will just work. For detailed instructions, " -"see <xref linkend=\"install-tftp\"/>." -msgstr "" - -#. Tag: title -#: installation-howto.xml:193 -#, no-c-format -msgid "Booting from hard disk" -msgstr "" - -#. Tag: para -#: installation-howto.xml:194 -#, no-c-format -msgid "" -"It's possible to boot the installer using no removable media, but just an " -"existing hard disk, which can have a different OS on it. Download " -"<filename>hd-media/initrd.gz</filename>, <filename>hd-media/vmlinuz</" -"filename>, and a Debian CD image to the top-level directory of the hard " -"disk. Make sure that the CD image has a filename ending in <literal>.iso</" -"literal>. Now it's just a matter of booting linux with the initrd. <phrase " -"arch=\"i386\"> <xref linkend=\"boot-initrd\"/> explains one way to do it. </" -"phrase>" -msgstr "" - -#. Tag: title -#: installation-howto.xml:211 -#, no-c-format -msgid "Installation" -msgstr "" - -#. Tag: para -#: installation-howto.xml:212 -#, no-c-format -msgid "" -"Once the installer starts, you will be greeted with an initial screen. Press " -"&enterkey; to boot, or read the instructions for other boot methods and " -"parameters (see <xref linkend=\"boot-parms\"/>). <phrase arch=\"i386\"> If " -"you want a 2.4 kernel, type <userinput>install24</userinput> at the " -"<prompt>boot:</prompt> prompt. <footnote><para> The 2.6 kernel is the " -"default for most boot methods, but is not available when booting from a " -"floppy. </para></footnote> </phrase>" -msgstr "" - -#. Tag: para -#: installation-howto.xml:228 -#, no-c-format -msgid "" -"After a while you will be asked to select your language. Use the arrow keys " -"to pick a language and press &enterkey; to continue. Next you'll be asked to " -"select your country, with the choices including countries where your " -"language is spoken. If it's not on the short list, a list of all the " -"countries in the world is available." -msgstr "" - -#. Tag: para -#: installation-howto.xml:236 -#, no-c-format -msgid "" -"You may be asked to confirm your keyboard layout. Choose the default unless " -"you know better." -msgstr "" - -#. Tag: para -#: installation-howto.xml:241 -#, no-c-format -msgid "" -"Now sit back while debian-installer detects some of your hardware, and loads " -"the rest of itself from CD, floppy, USB, etc." -msgstr "" - -#. Tag: para -#: installation-howto.xml:246 -#, no-c-format -msgid "" -"Next the installer will try to detect your network hardware and set up " -"networking by DHCP. If you are not on a network or do not have DHCP, you " -"will be given the opportunity to configure the network manually." -msgstr "" - -#. Tag: para -#: installation-howto.xml:252 -#, no-c-format -msgid "" -"Now it is time to partition your disks. First you will be given the " -"opportunity to automatically partition either an entire drive, or free space " -"on a drive. This is recommended for new users or anyone in a hurry, but if " -"you do not want to autopartition, choose manual from the menu." -msgstr "" - -#. Tag: para -#: installation-howto.xml:259 -#, no-c-format -msgid "" -"If you have an existing DOS or Windows partition that you want to preserve, " -"be very careful with automatic partitioning. If you choose manual " -"partitioning, you can use the installer to resize existing FAT or NTFS " -"partitions to create room for the Debian install: simply select the " -"partition and specify its new size." -msgstr "" - -#. Tag: para -#: installation-howto.xml:266 -#, no-c-format -msgid "" -"On the next screen you will see your partition table, how the partitions " -"will be formatted, and where they will be mounted. Select a partition to " -"modify or delete it. If you did automatic partitioning, you should just be " -"able to choose <guimenuitem>Finished partitioning</guimenuitem> from the " -"menu to use what it set up. Remember to assign at least one partition for " -"swap space and to mount a partition on <filename>/</filename>. <xref linkend=" -"\"partitioning\"/> has more information about partitioning." -msgstr "" - -#. Tag: para -#: installation-howto.xml:276 -#, no-c-format -msgid "" -"Now &d-i; formats your partitions and starts to install the base system, " -"which can take a while. That is followed by installing a kernel." -msgstr "" - -#. Tag: para -#: installation-howto.xml:281 -#, no-c-format -msgid "" -"The last step is to install a boot loader. If the installer detects other " -"operating systems on your computer, it will add them to the boot menu and " -"let you know. <phrase arch=\"i386\">By default GRUB will be installed to the " -"master boot record of the first harddrive, which is generally a good choice. " -"You'll be given the opportunity to override that choice and install it " -"elsewhere. </phrase>" -msgstr "" - -#. Tag: para -#: installation-howto.xml:291 -#, no-c-format -msgid "" -"&d-i; will now tell you that the installation has finished. Remove the cdrom " -"or other boot media and hit &enterkey; to reboot your machine. It should " -"boot up into the next stage of the install process, which is explained in " -"<xref linkend=\"boot-new\"/>." -msgstr "" - -#. Tag: para -#: installation-howto.xml:298 -#, no-c-format -msgid "" -"If you need more information on the install process, see <xref linkend=\"d-i-" -"intro\"/>." -msgstr "" - -#. Tag: title -#: installation-howto.xml:307 -#, no-c-format -msgid "Send us an installation report" -msgstr "" - -#. Tag: para -#: installation-howto.xml:308 -#, no-c-format -msgid "" -"If you successfully managed an installation with &d-i;, please take time to " -"provide us with a report. The simplest way to do so is to install the " -"reportbug package (<command>apt-get install reportbug</command>), and run " -"<command>reportbug installation-report</command>." -msgstr "" - -#. Tag: para -#: installation-howto.xml:316 -#, no-c-format -msgid "" -"If you did not complete the install, you probably found a bug in debian-" -"installer. To improve the installer it is necessary that we know about them, " -"so please take the time to report them. You can use an installation report " -"to report problems; if the install completely fails, see <xref linkend=" -"\"problem-report\"/>." -msgstr "" - -#. Tag: title -#: installation-howto.xml:328 -#, no-c-format -msgid "And finally.." -msgstr "" - -#. Tag: para -#: installation-howto.xml:329 -#, no-c-format -msgid "" -"We hope that your Debian installation is pleasant and that you find Debian " -"useful. You might want to read <xref linkend=\"post-install\"/>." -msgstr "" diff --git a/po/pl/partitioning.po b/po/pl/partitioning.po deleted file mode 100644 index 3eb03eb83..000000000 --- a/po/pl/partitioning.po +++ /dev/null @@ -1,1306 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-03-19 13:45+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: partitioning.xml:5 -#, no-c-format -msgid "Partitioning for Debian" -msgstr "" - -#. Tag: title -#: partitioning.xml:13 -#, no-c-format -msgid "Deciding on Debian Partitions and Sizes" -msgstr "" - -#. Tag: para -#: partitioning.xml:14 -#, no-c-format -msgid "" -"At a bare minimum, GNU/Linux needs one partition for itself. You can have a " -"single partition containing the entire operating system, applications, and " -"your personal files. Most people feel that a separate swap partition is also " -"a necessity, although it's not strictly true. <quote>Swap</quote> is scratch " -"space for an operating system, which allows the system to use disk storage " -"as <quote>virtual memory</quote>. By putting swap on a separate partition, " -"Linux can make much more efficient use of it. It is possible to force Linux " -"to use a regular file as swap, but it is not recommended." -msgstr "" - -#. Tag: para -#: partitioning.xml:26 -#, no-c-format -msgid "" -"Most people choose to give GNU/Linux more than the minimum number of " -"partitions, however. There are two reasons you might want to break up the " -"file system into a number of smaller partitions. The first is for safety. If " -"something happens to corrupt the file system, generally only one partition " -"is affected. Thus, you only have to replace (from the backups you've been " -"carefully keeping) a portion of your system. At a bare minimum, you should " -"consider creating what is commonly called a <quote>root partition</quote>. " -"This contains the most essential components of the system. If any other " -"partitions get corrupted, you can still boot into GNU/Linux to fix the " -"system. This can save you the trouble of having to reinstall the system from " -"scratch." -msgstr "" - -#. Tag: para -#: partitioning.xml:40 -#, no-c-format -msgid "" -"The second reason is generally more important in a business setting, but it " -"really depends on your use of the machine. For example, a mail server " -"getting spammed with e-mail can easily fill a partition. If you made " -"<filename>/var/mail</filename> a separate partition on the mail server, most " -"of the system will remain working even if you get spammed." -msgstr "" - -#. Tag: para -#: partitioning.xml:48 -#, no-c-format -msgid "" -"The only real drawback to using more partitions is that it is often " -"difficult to know in advance what your needs will be. If you make a " -"partition too small then you will either have to reinstall the system or you " -"will be constantly moving things around to make room in the undersized " -"partition. On the other hand, if you make the partition too big, you will be " -"wasting space that could be used elsewhere. Disk space is cheap nowadays, " -"but why throw your money away?" -msgstr "" - -#. Tag: title -#: partitioning.xml:67 -#, no-c-format -msgid "The Directory Tree" -msgstr "" - -#. Tag: para -#: partitioning.xml:68 -#, no-c-format -msgid "" -"&debian; adheres to the <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy " -"Standard</ulink> for directory and file naming. This standard allows users " -"and software programs to predict the location of files and directories. The " -"root level directory is represented simply by the slash <filename>/</" -"filename>. At the root level, all Debian systems include these directories:" -msgstr "" - -#. Tag: entry -#: partitioning.xml:82 -#, no-c-format -msgid "Directory" -msgstr "" - -#. Tag: entry -#: partitioning.xml:82 -#, no-c-format -msgid "Content" -msgstr "" - -#. Tag: filename -#: partitioning.xml:88 -#, no-c-format -msgid "<filename>bin</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:89 -#, no-c-format -msgid "Essential command binaries" -msgstr "" - -#. Tag: filename -#: partitioning.xml:91 -#, no-c-format -msgid "boot" -msgstr "" - -#. Tag: entry -#: partitioning.xml:92 -#, no-c-format -msgid "Static files of the boot loader" -msgstr "" - -#. Tag: filename -#: partitioning.xml:94 -#, no-c-format -msgid "<filename>dev</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:95 -#, no-c-format -msgid "Device files" -msgstr "" - -#. Tag: filename -#: partitioning.xml:97 -#, no-c-format -msgid "<filename>etc</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:98 -#, no-c-format -msgid "Host-specific system configuration" -msgstr "" - -#. Tag: filename -#: partitioning.xml:100 -#, no-c-format -msgid "home" -msgstr "" - -#. Tag: entry -#: partitioning.xml:101 -#, no-c-format -msgid "User home directories" -msgstr "" - -#. Tag: filename -#: partitioning.xml:103 -#, no-c-format -msgid "<filename>lib</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:104 -#, no-c-format -msgid "Essential shared libraries and kernel modules" -msgstr "" - -#. Tag: filename -#: partitioning.xml:106 -#, no-c-format -msgid "media" -msgstr "" - -#. Tag: entry -#: partitioning.xml:107 -#, no-c-format -msgid "Contains mount points for replaceable media" -msgstr "" - -#. Tag: filename -#: partitioning.xml:109 -#, no-c-format -msgid "<filename>mnt</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:110 -#, no-c-format -msgid "Mount point for mounting a file system temporarily" -msgstr "" - -#. Tag: filename -#: partitioning.xml:112 -#, no-c-format -msgid "proc" -msgstr "" - -#. Tag: entry -#: partitioning.xml:113 -#, no-c-format -msgid "Virtual directory for system information (2.4 and 2.6 kernels)" -msgstr "" - -#. Tag: filename -#: partitioning.xml:115 -#, no-c-format -msgid "root" -msgstr "" - -#. Tag: entry -#: partitioning.xml:116 -#, no-c-format -msgid "Home directory for the root user" -msgstr "" - -#. Tag: filename -#: partitioning.xml:118 -#, no-c-format -msgid "sbin" -msgstr "" - -#. Tag: entry -#: partitioning.xml:119 -#, no-c-format -msgid "Essential system binaries" -msgstr "" - -#. Tag: filename -#: partitioning.xml:121 -#, no-c-format -msgid "<filename>sys</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:122 -#, no-c-format -msgid "Virtual directory for system information (2.6 kernels)" -msgstr "" - -#. Tag: filename -#: partitioning.xml:124 -#, no-c-format -msgid "<filename>tmp</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:125 -#, no-c-format -msgid "Temporary files" -msgstr "" - -#. Tag: filename -#: partitioning.xml:127 -#, no-c-format -msgid "<filename>usr</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:128 -#, no-c-format -msgid "Secondary hierarchy" -msgstr "" - -#. Tag: filename -#: partitioning.xml:130 -#, no-c-format -msgid "<filename>var</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:131 -#, no-c-format -msgid "Variable data" -msgstr "" - -#. Tag: filename -#: partitioning.xml:133 -#, no-c-format -msgid "<filename>opt</filename>" -msgstr "" - -#. Tag: entry -#: partitioning.xml:134 -#, no-c-format -msgid "Add-on application software packages" -msgstr "" - -#. Tag: para -#: partitioning.xml:139 -#, no-c-format -msgid "" -"The following is a list of important considerations regarding directories " -"and partitions. Note that disk usage varies widely given system " -"configuration and specific usage patterns. The recommendations here are " -"general guidelines and provide a starting point for partitioning." -msgstr "" - -#. Tag: para -#: partitioning.xml:149 -#, no-c-format -msgid "" -"The root partition <filename>/</filename> must always physically contain " -"<filename>/etc</filename>, <filename>/bin</filename>, <filename>/sbin</" -"filename>, <filename>/lib</filename> and <filename>/dev</filename>, " -"otherwise you won't be able to boot. Typically 150–250 MB is needed " -"for the root partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:158 -#, no-c-format -msgid "" -"<filename>/usr</filename>: contains all user programs (<filename>/usr/bin</" -"filename>), libraries (<filename>/usr/lib</filename>), documentation " -"(<filename>/usr/share/doc</filename>), etc. This is the part of the file " -"system that generally takes up most space. You should provide at least 500 " -"MB of disk space. This amount should be increased depending on the number " -"and type of packages you plan to install. A generous workstation or server " -"installation should allow 4-6 GB." -msgstr "" - -#. Tag: para -#: partitioning.xml:171 -#, no-c-format -msgid "" -"<filename>/var</filename>: variable data like news articles, e-mails, web " -"sites, databases, the packaging system cache, etc. will be placed under this " -"directory. The size of this directory depends greatly on the usage of your " -"system, but for most people will be dictated by the package management " -"tool's overhead. If you are going to do a full installation of just about " -"everything Debian has to offer, all in one session, setting aside 2 or 3 " -"gigabyte of space for <filename>/var</filename> should be sufficient. If you " -"are going to install in pieces (that is to say, install services and " -"utilities, followed by text stuff, then X, ...), you can get away with " -"300–500 MB. If hard drive space is at a premium and you don't plan on " -"doing major system updates, you can get by with as little as 30 or 40 MB." -msgstr "" - -#. Tag: para -#: partitioning.xml:187 -#, no-c-format -msgid "" -"<filename>/tmp</filename>: temporary data created by programs will most " -"likely go in this directory. 40–100 MB should usually be enough. Some " -"applications — including archive manipulators, CD/DVD authoring tools, " -"and multimedia software — may use <filename>/tmp</filename> to " -"temporarily store image files. If you plan to use such applications, you " -"should adjust the space available in <filename>/tmp</filename> accordingly." -msgstr "" - -#. Tag: para -#: partitioning.xml:198 -#, no-c-format -msgid "" -"<filename>/home</filename>: every user will put his personal data into a " -"subdirectory of this directory. Its size depends on how many users will be " -"using the system and what files are to be stored in their directories. " -"Depending on your planned usage you should reserve about 100 MB for each " -"user, but adapt this value to your needs. Reserve a lot more space if you " -"plan to save a lot of multimedia files (pictures, MP3, movies) in your home " -"directory." -msgstr "" - -#. Tag: title -#: partitioning.xml:219 -#, no-c-format -msgid "Recommended Partitioning Scheme" -msgstr "" - -#. Tag: para -#: partitioning.xml:220 -#, no-c-format -msgid "" -"For new users, personal Debian boxes, home systems, and other single-user " -"setups, a single <filename>/</filename> partition (plus swap) is probably " -"the easiest, simplest way to go. However, if your partition is larger than " -"around 6GB, choose ext3 as your partition type. Ext2 partitions need " -"periodic file system integrity checking, and this can cause delays during " -"booting when the partition is large." -msgstr "" - -#. Tag: para -#: partitioning.xml:229 -#, no-c-format -msgid "" -"For multi-user systems or systems with lots of disk space, it's best to put " -"<filename>/usr</filename>, <filename>/var</filename>, <filename>/tmp</" -"filename>, and <filename>/home</filename> each on their own partitions " -"separate from the <filename>/</filename> partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:237 -#, no-c-format -msgid "" -"You might need a separate <filename>/usr/local</filename> partition if you " -"plan to install many programs that are not part of the Debian distribution. " -"If your machine will be a mail server, you might need to make <filename>/var/" -"mail</filename> a separate partition. Often, putting <filename>/tmp</" -"filename> on its own partition, for instance 20 to 50MB, is a good idea. If " -"you are setting up a server with lots of user accounts, it's generally good " -"to have a separate, large <filename>/home</filename> partition. In general, " -"the partitioning situation varies from computer to computer depending on its " -"uses." -msgstr "" - -#. Tag: para -#: partitioning.xml:249 -#, no-c-format -msgid "" -"For very complex systems, you should see the <ulink url=\"&url-multidisk-" -"howto;\"> Multi Disk HOWTO</ulink>. This contains in-depth information, " -"mostly of interest to ISPs and people setting up servers." -msgstr "" - -#. Tag: para -#: partitioning.xml:256 -#, no-c-format -msgid "" -"With respect to the issue of swap partition size, there are many views. One " -"rule of thumb which works well is to use as much swap as you have system " -"memory. It also shouldn't be smaller than 16MB, in most cases. Of course, " -"there are exceptions to these rules. If you are trying to solve 10000 " -"simultaneous equations on a machine with 256MB of memory, you may need a " -"gigabyte (or more) of swap." -msgstr "" - -#. Tag: para -#: partitioning.xml:265 -#, no-c-format -msgid "" -"On the other hand, Atari Falcons and Macs feel pain when swapping, so " -"instead of making a large swap partition, get as much RAM as possible." -msgstr "" - -#. Tag: para -#: partitioning.xml:270 -#, no-c-format -msgid "" -"On 32-bit architectures (i386, m68k, 32-bit SPARC, and PowerPC), the maximum " -"size of a swap partition is 2GB. That should be enough for nearly any " -"installation. However, if your swap requirements are this high, you should " -"probably try to spread the swap across different disks (also called " -"<quote>spindles</quote>) and, if possible, different SCSI or IDE channels. " -"The kernel will balance swap usage between multiple swap partitions, giving " -"better performance." -msgstr "" - -#. Tag: para -#: partitioning.xml:280 -#, no-c-format -msgid "" -"As an example, an older home machine might have 32MB of RAM and a 1.7GB IDE " -"drive on <filename>/dev/hda</filename>. There might be a 500MB partition for " -"another operating system on <filename>/dev/hda1</filename>, a 32MB swap " -"partition on <filename>/dev/hda3</filename> and about 1.2GB on <filename>/" -"dev/hda2</filename> as the Linux partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:289 -#, no-c-format -msgid "" -"For an idea of the space taken by tasks you might be interested in adding " -"after your system installation is complete, check <xref linkend=\"tasksel-" -"size-list\"/>." -msgstr "" - -#. Tag: title -#: partitioning.xml:305 -#, no-c-format -msgid "Device Names in Linux" -msgstr "" - -#. Tag: para -#: partitioning.xml:306 -#, no-c-format -msgid "" -"Linux disks and partition names may be different from other operating " -"systems. You need to know the names that Linux uses when you create and " -"mount partitions. Here's the basic naming scheme:" -msgstr "" - -#. Tag: para -#: partitioning.xml:314 -#, no-c-format -msgid "The first floppy drive is named <filename>/dev/fd0</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:319 -#, no-c-format -msgid "The second floppy drive is named <filename>/dev/fd1</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:324 -#, no-c-format -msgid "" -"The first SCSI disk (SCSI ID address-wise) is named <filename>/dev/sda</" -"filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:330 -#, no-c-format -msgid "" -"The second SCSI disk (address-wise) is named <filename>/dev/sdb</filename>, " -"and so on." -msgstr "" - -#. Tag: para -#: partitioning.xml:336 -#, no-c-format -msgid "" -"The first SCSI CD-ROM is named <filename>/dev/scd0</filename>, also known as " -"<filename>/dev/sr0</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:342 -#, no-c-format -msgid "" -"The master disk on IDE primary controller is named <filename>/dev/hda</" -"filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:348 -#, no-c-format -msgid "" -"The slave disk on IDE primary controller is named <filename>/dev/hdb</" -"filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:354 -#, no-c-format -msgid "" -"The master and slave disks of the secondary controller can be called " -"<filename>/dev/hdc</filename> and <filename>/dev/hdd</filename>, " -"respectively. Newer IDE controllers can actually have two channels, " -"effectively acting like two controllers. <phrase arch=\"m68k\"> The letters " -"may differ from what shows in the mac program pdisk (i.e. what shows up as " -"<filename>/dev/hdc</filename> on pdisk may show up as <filename>/dev/hda</" -"filename> in Debian). </phrase>" -msgstr "" - -#. Tag: para -#: partitioning.xml:369 -#, no-c-format -msgid "The first XT disk is named <filename>/dev/xda</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:374 -#, no-c-format -msgid "The second XT disk is named <filename>/dev/xdb</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:379 -#, no-c-format -msgid "" -"The first ACSI device is named <filename>/dev/ada</filename>, the second is " -"named <filename>/dev/adb</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:388 -#, no-c-format -msgid "The first DASD device is named <filename>/dev/dasda</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:394 -#, no-c-format -msgid "" -"The second DASD device is named <filename>/dev/dasdb</filename>, and so on." -msgstr "" - -#. Tag: para -#: partitioning.xml:402 -#, no-c-format -msgid "" -"The partitions on each disk are represented by appending a decimal number to " -"the disk name: <filename>sda1</filename> and <filename>sda2</filename> " -"represent the first and second partitions of the first SCSI disk drive in " -"your system." -msgstr "" - -#. Tag: para -#: partitioning.xml:409 -#, no-c-format -msgid "" -"Here is a real-life example. Let's assume you have a system with 2 SCSI " -"disks, one at SCSI address 2 and the other at SCSI address 4. The first disk " -"(at address 2) is then named <filename>sda</filename>, and the second " -"<filename>sdb</filename>. If the <filename>sda</filename> drive has 3 " -"partitions on it, these will be named <filename>sda1</filename>, " -"<filename>sda2</filename>, and <filename>sda3</filename>. The same applies " -"to the <filename>sdb</filename> disk and its partitions." -msgstr "" - -#. Tag: para -#: partitioning.xml:420 -#, no-c-format -msgid "" -"Note that if you have two SCSI host bus adapters (i.e., controllers), the " -"order of the drives can get confusing. The best solution in this case is to " -"watch the boot messages, assuming you know the drive models and/or " -"capacities." -msgstr "" - -#. Tag: para -#: partitioning.xml:427 -#, no-c-format -msgid "" -"Linux represents the primary partitions as the drive name, plus the numbers " -"1 through 4. For example, the first primary partition on the first IDE drive " -"is <filename>/dev/hda1</filename>. The logical partitions are numbered " -"starting at 5, so the first logical partition on that same drive is " -"<filename>/dev/hda5</filename>. Remember that the extended partition, that " -"is, the primary partition holding the logical partitions, is not usable by " -"itself. This applies to SCSI disks as well as IDE disks." -msgstr "" - -#. Tag: para -#: partitioning.xml:438 -#, no-c-format -msgid "" -"VMEbus systems using the TEAC FC-1 SCSI floppy drive will see it as normal " -"SCSI disk. To make identification of the drive simpler the installation " -"software will create a symbolic link to the appropriate device and name it " -"<filename>/dev/sfd0</filename>." -msgstr "" - -#. Tag: para -#: partitioning.xml:445 -#, no-c-format -msgid "" -"Sun disk partitions allow for 8 separate partitions (or slices). The third " -"partition is usually (and is preferred to have) the <quote>Whole Disk</" -"quote> partition. This partition references all of the sectors of the disk, " -"and is used by the boot loader (either SILO, or Sun's)." -msgstr "" - -#. Tag: para -#: partitioning.xml:452 -#, no-c-format -msgid "" -"The partitions on each disk are represented by appending a decimal number to " -"the disk name: <filename>dasda1</filename> and <filename>dasda2</filename> " -"represent the first and second partitions of the first DASD device in your " -"system." -msgstr "" - -#. Tag: title -#: partitioning.xml:467 -#, no-c-format -msgid "Debian Partitioning Programs" -msgstr "" - -#. Tag: para -#: partitioning.xml:468 -#, no-c-format -msgid "" -"Several varieties of partitioning programs have been adapted by Debian " -"developers to work on various types of hard disks and computer " -"architectures. Following is a list of the program(s) applicable for your " -"architecture." -msgstr "" - -#. Tag: command -#: partitioning.xml:480 -#, no-c-format -msgid "partman" -msgstr "" - -#. Tag: para -#: partitioning.xml:481 -#, no-c-format -msgid "" -"Recommended partitioning tool in Debian. This Swiss army knife can also " -"resize partitions, create filesystems <phrase arch=\"i386\"> (<quote>format</" -"quote> in Windows speak)</phrase> and assign them to the mountpoints." -msgstr "" - -#. Tag: command -#: partitioning.xml:492 -#, no-c-format -msgid "fdisk" -msgstr "" - -#. Tag: para -#: partitioning.xml:493 -#, no-c-format -msgid "The original Linux disk partitioner, good for gurus." -msgstr "" - -#. Tag: para -#: partitioning.xml:497 -#, no-c-format -msgid "" -"Be careful if you have existing FreeBSD partitions on your machine. The " -"installation kernels include support for these partitions, but the way that " -"<command>fdisk</command> represents them (or not) can make the device names " -"differ. See the <ulink url=\"&url-linux-freebsd;\">Linux+FreeBSD HOWTO</" -"ulink>" -msgstr "" - -#. Tag: command -#: partitioning.xml:509 -#, no-c-format -msgid "cfdisk" -msgstr "" - -#. Tag: para -#: partitioning.xml:510 -#, no-c-format -msgid "A simple-to-use, full-screen disk partitioner for the rest of us." -msgstr "" - -#. Tag: para -#: partitioning.xml:514 -#, no-c-format -msgid "" -"Note that <command>cfdisk</command> doesn't understand FreeBSD partitions at " -"all, and, again, device names may differ as a result." -msgstr "" - -#. Tag: command -#: partitioning.xml:523 -#, no-c-format -msgid "atari-fdisk" -msgstr "" - -#. Tag: para -#: partitioning.xml:524 -#, no-c-format -msgid "Atari-aware version of <command>fdisk</command>." -msgstr "" - -#. Tag: command -#: partitioning.xml:532 -#, no-c-format -msgid "amiga-fdisk" -msgstr "" - -#. Tag: para -#: partitioning.xml:533 -#, no-c-format -msgid "Amiga-aware version of <command>fdisk</command>." -msgstr "" - -#. Tag: command -#: partitioning.xml:541 -#, no-c-format -msgid "mac-fdisk" -msgstr "" - -#. Tag: para -#: partitioning.xml:542 -#, no-c-format -msgid "Mac-aware version of <command>fdisk</command>." -msgstr "" - -#. Tag: command -#: partitioning.xml:550 -#, no-c-format -msgid "pmac-fdisk" -msgstr "" - -#. Tag: para -#: partitioning.xml:551 -#, no-c-format -msgid "" -"PowerMac-aware version of <command>fdisk</command>, also used by BVM and " -"Motorola VMEbus systems." -msgstr "" - -#. Tag: command -#: partitioning.xml:560 -#, no-c-format -msgid "fdasd" -msgstr "" - -#. Tag: para -#: partitioning.xml:561 -#, no-c-format -msgid "" -"&arch-title; version of <command>fdisk</command>; Please read the fdasd " -"manual page or chapter 13 in <ulink url=\"http://oss.software.ibm.com/" -"developerworks/opensource/linux390/docu/l390dd08.pdf\"> Device Drivers and " -"Installation Commands</ulink> for details." -msgstr "" - -#. Tag: para -#: partitioning.xml:572 -#, no-c-format -msgid "" -"One of these programs will be run by default when you select " -"<guimenuitem>Partition a Hard Disk</guimenuitem>. If the one which is run by " -"default isn't the one you want, quit the partitioner, go to the shell " -"(<userinput>tty2</userinput>) by pressing <keycap>Alt</keycap> and " -"<keycap>F2</keycap> keys together, and manually type in the name of the " -"program you want to use (and arguments, if any). Then skip the " -"<guimenuitem>Partition a Hard Disk</guimenuitem> step in <command>debian-" -"installer</command> and continue to the next step." -msgstr "" - -#. Tag: para -#: partitioning.xml:583 -#, no-c-format -msgid "" -"If you will be working with more than 20 partitions on your ide disk, you " -"will need to create devices for partitions 21 and beyond. The next step of " -"initializing the partition will fail unless a proper device is present. As " -"an example, here are commands you can use in <userinput>tty2</userinput> or " -"under Execute A Shell to add a device so the 21st partition can be " -"initialized: <informalexample><screen>\n" -"# cd /dev\n" -"# mknod hda21 b 3 21\n" -"# chgrp disk hda21\n" -"# chmod 660 hda21\n" -"</screen></informalexample> Booting into the new system will fail unless " -"proper devices are present on the target system. After installing the kernel " -"and modules, execute: <informalexample><screen>\n" -"# cd /target/dev\n" -"# mknod hda21 b 3 21\n" -"# chgrp disk hda21\n" -"# chmod 660 hda21\n" -"</screen></informalexample> <phrase arch=\"i386\">Remember to mark your boot " -"partition as <quote>Bootable</quote>.</phrase>" -msgstr "" - -#. Tag: para -#: partitioning.xml:602 -#, no-c-format -msgid "" -"One key point when partitioning for Mac type disks is that the swap " -"partition is identified by its name; it must be named <quote>swap</quote>. " -"All Mac linux partitions are the same partition type, Apple_UNIX_SRV2. " -"Please read the fine manual. We also suggest reading the <ulink url=\"&url-" -"mac-fdisk-tutorial;\">mac-fdisk Tutorial</ulink>, which includes steps you " -"should take if you are sharing your disk with MacOS." -msgstr "" - -#. Tag: title -#: partitioning.xml:618 partitioning.xml:678 partitioning.xml:702 -#: partitioning.xml:798 partitioning.xml:917 partitioning.xml:994 -#, no-c-format -msgid "Partitioning for &arch-title;" -msgstr "" - -#. Tag: para -#: partitioning.xml:619 -#, no-c-format -msgid "" -"Booting Debian from the SRM console (the only disk boot method supported by " -"&releasename;) requires you to have a BSD disk label, not a DOS partition " -"table, on your boot disk. (Remember, the SRM boot block is incompatible with " -"MS-DOS partition tables — see <xref linkend=\"alpha-firmware\"/>.) As " -"a result, <command>partman</command> creates BSD disk labels when running on " -"&architecture;, but if your disk has an existing DOS partition table the " -"existing partitions will need to be deleted before partman can convert it to " -"use a disk label." -msgstr "" - -#. Tag: para -#: partitioning.xml:630 -#, no-c-format -msgid "" -"If you have chosen to use <command>fdisk</command> to partition your disk, " -"and the disk that you have selected for partitioning does not already " -"contain a BSD disk label, you must use the <quote>b</quote> command to enter " -"disk label mode." -msgstr "" - -#. Tag: para -#: partitioning.xml:637 -#, no-c-format -msgid "" -"Unless you wish to use the disk you are partitioning from Tru64 Unix or one " -"of the free 4.4BSD-Lite derived operating systems (FreeBSD, OpenBSD, or " -"NetBSD), it is suggested that you do <emphasis>not</emphasis> make the third " -"partition contain the whole disk. This is not required by <command>aboot</" -"command>, and in fact, it may lead to confusion since the " -"<command>swriteboot</command> utility used to install <command>aboot</" -"command> in the boot sector will complain about a partition overlapping with " -"the boot block." -msgstr "" - -#. Tag: para -#: partitioning.xml:648 -#, no-c-format -msgid "" -"Also, because <command>aboot</command> is written to the first few sectors " -"of the disk (currently it occupies about 70 kilobytes, or 150 sectors), you " -"<emphasis>must</emphasis> leave enough empty space at the beginning of the " -"disk for it. In the past, it was suggested that you make a small partition " -"at the beginning of the disk, to be left unformatted. For the same reason " -"mentioned above, we now suggest that you do not do this on disks that will " -"only be used by GNU/Linux. When using <command>partman</command>, a small " -"partition will still be created for <command>aboot</command> for convenience " -"reasons." -msgstr "" - -#. Tag: para -#: partitioning.xml:660 -#, no-c-format -msgid "" -"For ARC installations, you should make a small FAT partition at the " -"beginning of the disk to contain <command>MILO</command> and " -"<command>linload.exe</command> — 5 megabytes should be sufficient, see " -"<xref linkend=\"non-debian-partitioning\"/>. Unfortunately, making FAT file " -"systems from the menu is not yet supported, so you'll have to do it manually " -"from the shell using <command>mkdosfs</command> before attempting to install " -"the boot loader." -msgstr "" - -#. Tag: para -#: partitioning.xml:679 -#, no-c-format -msgid "" -"PALO, the HPPA boot loader, requires a partition of type <quote>F0</quote> " -"somewhere in the first 2GB. This is where the boot loader and an optional " -"kernel and RAMdisk will be stored, so make it big enough for that — at " -"least 4Mb (I like 8–16MB). An additional requirement of the firmware " -"is that the Linux kernel must reside within the first 2GB of the disk. This " -"is typically achieved by making the root ext2 partition fit entirely within " -"the first 2GB of the disk. Alternatively you can create a small ext2 " -"partition near the start of the disk and mount that on <filename>/boot</" -"filename>, since that is the directory where the Linux kernel(s) will be " -"stored. <filename>/boot</filename> needs to be big enough to hold whatever " -"kernels (and backups) you might wish to load; 25–50MB is generally " -"sufficient." -msgstr "" - -#. Tag: para -#: partitioning.xml:703 -#, no-c-format -msgid "" -"If you have an existing other operating system such as DOS or Windows and " -"you want to preserve that operating system while installing Debian, you may " -"need to resize its partition to free up space for the Debian installation. " -"The installer supports resizing of both FAT and NTFS filesystems; when you " -"get to the installer's partitioning step, select the option to partition " -"manually and then simply select an existing partition and change its size." -msgstr "" - -#. Tag: para -#: partitioning.xml:712 -#, no-c-format -msgid "" -"The PC BIOS generally adds additional constraints for disk partitioning. " -"There is a limit to how many <quote>primary</quote> and <quote>logical</" -"quote> partitions a drive can contain. Additionally, with pre 1994–98 " -"BIOSes, there are limits to where on the drive the BIOS can boot from. More " -"information can be found in the <ulink url=\"&url-partition-howto;\">Linux " -"Partition HOWTO</ulink> and the <ulink url=\"&url-phoenix-bios-faq-large-" -"disk;\">Phoenix BIOS FAQ</ulink>, but this section will include a brief " -"overview to help you plan most situations." -msgstr "" - -#. Tag: para -#: partitioning.xml:723 -#, no-c-format -msgid "" -"<quote>Primary</quote> partitions are the original partitioning scheme for " -"PC disks. However, there can only be four of them. To get past this " -"limitation, <quote>extended</quote> and <quote>logical</quote> partitions " -"were invented. By setting one of your primary partitions as an extended " -"partition, you can subdivide all the space allocated to that partition into " -"logical partitions. You can create up to 60 logical partitions per extended " -"partition; however, you can only have one extended partition per drive." -msgstr "" - -#. Tag: para -#: partitioning.xml:734 -#, no-c-format -msgid "" -"Linux limits the partitions per drive to 15 partitions for SCSI disks (3 " -"usable primary partitions, 12 logical partitions), and 63 partitions on an " -"IDE drive (3 usable primary partitions, 60 logical partitions). However the " -"normal &debian; system provides only 20 devices for partitions, so you may " -"not install on partitions higher than 20 unless you first manually create " -"devices for those partitions." -msgstr "" - -#. Tag: para -#: partitioning.xml:744 -#, no-c-format -msgid "" -"If you have a large IDE disk, and are using neither LBA addressing, nor " -"overlay drivers (sometimes provided by hard disk manufacturers), then the " -"boot partition (the partition containing your kernel image) must be placed " -"within the first 1024 cylinders of your hard drive (usually around 524 " -"megabytes, without BIOS translation)." -msgstr "" - -#. Tag: para -#: partitioning.xml:752 -#, no-c-format -msgid "" -"This restriction doesn't apply if you have a BIOS newer than around " -"1995–98 (depending on the manufacturer) that supports the " -"<quote>Enhanced Disk Drive Support Specification</quote>. Both Lilo, the " -"Linux loader, and Debian's alternative <command>mbr</command> must use the " -"BIOS to read the kernel from the disk into RAM. If the BIOS int 0x13 large " -"disk access extensions are found to be present, they will be utilized. " -"Otherwise, the legacy disk access interface is used as a fall-back, and it " -"cannot be used to address any location on the disk higher than the 1023rd " -"cylinder. Once Linux is booted, no matter what BIOS your computer has, these " -"restrictions no longer apply, since Linux does not use the BIOS for disk " -"access." -msgstr "" - -#. Tag: para -#: partitioning.xml:766 -#, no-c-format -msgid "" -"If you have a large disk, you might have to use cylinder translation " -"techniques, which you can set from your BIOS setup program, such as LBA " -"(Logical Block Addressing) or CHS translation mode (<quote>Large</quote>). " -"More information about issues with large disks can be found in the <ulink " -"url=\"&url-large-disk-howto;\">Large Disk HOWTO</ulink>. If you are using a " -"cylinder translation scheme, and the BIOS does not support the large disk " -"access extensions, then your boot partition has to fit within the " -"<emphasis>translated</emphasis> representation of the 1024th cylinder." -msgstr "" - -#. Tag: para -#: partitioning.xml:778 -#, no-c-format -msgid "" -"The recommended way of accomplishing this is to create a small " -"(25–50MB should suffice) partition at the beginning of the disk to be " -"used as the boot partition, and then create whatever other partitions you " -"wish to have, in the remaining area. This boot partition <emphasis>must</" -"emphasis> be mounted on <filename>/boot</filename>, since that is the " -"directory where the Linux kernel(s) will be stored. This configuration will " -"work on any system, regardless of whether LBA or large disk CHS translation " -"is used, and regardless of whether your BIOS supports the large disk access " -"extensions." -msgstr "" - -#. Tag: para -#: partitioning.xml:800 -#, no-c-format -msgid "" -"The <command>partman</command> disk partitioner is the default partitioning " -"tool for the installer. It manages the set of partitions and their mount " -"points to ensure that the disks and filesystems is properly configured for a " -"successful installation. It actually uses the <command>parted</command> to " -"do the on-disk partitioning." -msgstr "" - -#. Tag: title -#: partitioning.xml:812 -#, no-c-format -msgid "EFI Recognized Formats" -msgstr "" - -#. Tag: para -#: partitioning.xml:813 -#, no-c-format -msgid "" -"The IA64 EFI firmware supports two partition table (or disk label) formats, " -"GPT and MS-DOS. MS-DOS, the format typically used on i386 PCs, is no longer " -"recommended for IA64 systems. Although the installer also provides the " -"<command>cfdisk</command>, you should only use the <ulink url=\"parted.txt" -"\"> <command>parted</command></ulink> because only it can manage both GPT " -"and MS-DOS tables correctly." -msgstr "" - -#. Tag: para -#: partitioning.xml:825 -#, no-c-format -msgid "" -"The automatic partitioning recipes for <command>partman</command> allocate " -"an EFI partition as the first partition on the disk. You can also set up the " -"partition under the <guimenuitem>Guided partitioning</guimenuitem> from the " -"main menu in a manner similar to setting up a <emphasis>swap</emphasis> " -"partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:833 -#, no-c-format -msgid "" -"The <command>partman</command> partitioner will handle most disk layouts. " -"For those rare cases where it is necessary to manually set up a disk, you " -"can use the shell as described above and run the <command>parted</command> " -"utility directly using its command line interface. Assuming that you want to " -"erase your whole disk and create a GPT table and some partitions, then " -"something similar to the following command sequence could be used: " -"<informalexample><screen>\n" -" mklabel gpt\n" -" mkpartfs primary fat 0 50\n" -" mkpartfs primary linux-swap 51 1000\n" -" mkpartfs primary ext2 1001 3000\n" -" set 1 boot on\n" -" print\n" -" quit\n" -"</screen></informalexample> This creates a new partition table, and three " -"partitions to be used as an EFI boot partition, swap space, and a root file " -"system. Finally it sets the boot flag on the EFI partition. Partitions are " -"specified in Megabytes, with start and end offsets from the beginning of the " -"disk. So, for example, above we created a 1999MB ext2 file system starting " -"at offset 1001MB from the start of the disk. Note that formatting swap space " -"with <command>parted</command> can take a few minutes to complete, as it " -"scans the partition for bad blocks." -msgstr "" - -#. Tag: title -#: partitioning.xml:858 -#, no-c-format -msgid "Boot Loader Partition Requirements" -msgstr "" - -#. Tag: para -#: partitioning.xml:860 -#, no-c-format -msgid "" -"ELILO, the ia64 boot loader, requires a partition containing a FAT file " -"system with the <userinput>boot</userinput> flag set. The partition must be " -"big enough to hold the boot loader and any kernels or RAMdisks you may wish " -"to boot. A minimum size would be about 20MB, but if you expect to run with " -"multiple kernels, then 128MB might be a better size." -msgstr "" - -#. Tag: para -#: partitioning.xml:869 -#, no-c-format -msgid "" -"The EFI Boot Manager and the EFI Shell fully support the GPT table so the " -"boot partition does not necessarily have to be the first partition or even " -"on the same disk. This is convenient if you should forget to allocate the " -"partition and only find out after you have formatted the other partitions on " -"your disk(s). The <command>partman</command> partitioner checks for an EFI " -"partition at the same time it checks for a properly set up <emphasis>root</" -"emphasis> partition. This gives you an opportunity to correct the disk " -"layout before the package install begins. The easiest way to correct this " -"omission is to shrink the last partition of the disk to make enough free " -"space for adding an EFI partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:884 -#, no-c-format -msgid "" -"It is strongly recommended that you allocate the EFI boot partition on the " -"same disk as the <emphasis>root</emphasis> filesystem." -msgstr "" - -#. Tag: title -#: partitioning.xml:893 -#, no-c-format -msgid "EFI Diagnostic Partitions" -msgstr "" - -#. Tag: para -#: partitioning.xml:895 -#, no-c-format -msgid "" -"The EFI firmware is significantly more sophisticated than the usual BIOS " -"seen on most x86 PCs. Some system vendors take advantage of the ability of " -"the EFI to access files and run programs from a hard disk filesystem to " -"store diagnostics and EFI based system management utilities on the hard " -"disk. This is a separate FAT format filesystem on the system disk. Consult " -"the system documentation and accessories that come with the system for " -"details. The easiest time to set up a diagnostics partition is at the same " -"time you set up the EFI boot partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:918 -#, no-c-format -msgid "" -"SGI machines require an SGI disk label in order to make the system bootable " -"from hard disk. It can be created in the fdisk expert menu. The thereby " -"created volume header (partition number 9) should be at least 3MB large. If " -"the volume header created is too small, you can simply delete partition " -"number 9 and re-add it with a different size. Note that the volume header " -"must start at sector 0." -msgstr "" - -#. Tag: title -#: partitioning.xml:935 -#, no-c-format -msgid "Partitioning Newer PowerMacs" -msgstr "" - -#. Tag: para -#: partitioning.xml:936 -#, no-c-format -msgid "" -"If you are installing onto a NewWorld PowerMac you must create a special " -"bootstrap partition to hold the boot loader. The size of this partition must " -"be 800KB and its partition type must be <emphasis>Apple_Bootstrap</" -"emphasis>. If the bootstrap partition is not created with the " -"<emphasis>Apple_Bootstrap</emphasis> type your machine cannot be made " -"bootable from the hard disk. This partition can easily be created by " -"creating a new partition in <command>partman</command> and telling it to use " -"it as a <quote>NewWorld boot partition</quote>, or in <command>mac-fdisk</" -"command> using the <userinput>b</userinput> command." -msgstr "" - -#. Tag: para -#: partitioning.xml:949 -#, no-c-format -msgid "" -"The special partition type Apple_Bootstrap is required to prevent MacOS from " -"mounting and damaging the bootstrap partition, as there are special " -"modifications made to it in order for OpenFirmware to boot it automatically." -msgstr "" - -#. Tag: para -#: partitioning.xml:956 -#, no-c-format -msgid "" -"Note that the bootstrap partition is only meant to hold 3 very small files: " -"the <command>yaboot</command> binary, its configuration <filename>yaboot." -"conf</filename>, and a first stage OpenFirmware loader <command>ofboot.b</" -"command>. It need not and must not be mounted on your file system nor have " -"kernels or anything else copied to it. The <command>ybin</command> and " -"<command>mkofboot</command> utilities are used to manipulate this partition." -msgstr "" - -#. Tag: para -#: partitioning.xml:966 -#, no-c-format -msgid "" -"In order for OpenFirmware to automatically boot &debian; the bootstrap " -"partition should appear before other boot partitions on the disk, especially " -"MacOS boot partitions. The bootstrap partition should be the first one you " -"create. However, if you add a bootstrap partition later, you can use " -"<command>mac-fdisk</command>'s <userinput>r</userinput> command to reorder " -"the partition map so the bootstrap partition comes right after the map " -"(which is always partition 1). It's the logical map order, not the physical " -"address order, that counts." -msgstr "" - -#. Tag: para -#: partitioning.xml:978 -#, no-c-format -msgid "" -"Apple disks normally have several small driver partitions. If you intend to " -"dual boot your machine with MacOSX, you should retain these partitions and a " -"small HFS partition (800k is the minimum size). That is because MacOSX, on " -"every boot, offers to initialize any disks which do not have active MacOS " -"partitions and driver partitions." -msgstr "" - -#. Tag: para -#: partitioning.xml:995 -#, no-c-format -msgid "" -"Make sure you create a <quote>Sun disk label</quote> on your boot disk. This " -"is the only kind of partition scheme that the OpenBoot PROM understands, and " -"so it's the only scheme from which you can boot. The <keycap>s</keycap> key " -"is used in <command>fdisk</command> to create Sun disk labels." -msgstr "" - -#. Tag: para -#: partitioning.xml:1003 -#, no-c-format -msgid "" -"Furthermore, on &arch-title; disks, make sure your first partition on your " -"boot disk starts at cylinder 0. While this is required, it also means that " -"the first partition will contain the partition table and the boot block, " -"which are the first two sectors of the disk. You must <emphasis>not</" -"emphasis> put swap on the first partition of the boot drive, since swap " -"partitions do not preserve the first few sectors of the partition. You can " -"put Ext2 or UFS partitions there; these will leave the partition table and " -"the boot block alone." -msgstr "" - -#. Tag: para -#: partitioning.xml:1014 -#, no-c-format -msgid "" -"It is also advised that the third partition should be of type <quote>Whole " -"disk</quote> (type 5), and contain the entire disk (from the first cylinder " -"to the last). This is simply a convention of Sun disk labels, and helps the " -"<command>SILO</command> boot loader keep its bearings." -msgstr "" diff --git a/po/pl/post-install.po b/po/pl/post-install.po deleted file mode 100644 index 4b26c1cd7..000000000 --- a/po/pl/post-install.po +++ /dev/null @@ -1,602 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: post-install.xml:5 -#, no-c-format -msgid "Next Steps and Where to Go From Here" -msgstr "" - -#. Tag: title -#: post-install.xml:13 -#, no-c-format -msgid "If You Are New to Unix" -msgstr "" - -#. Tag: para -#: post-install.xml:14 -#, no-c-format -msgid "" -"If you are new to Unix, you probably should go out and buy some books and do " -"some reading. A lot of valuable information can also be found in the <ulink " -"url=\"&url-debian-reference;\">Debian Reference</ulink>. This <ulink url=" -"\"&url-unix-faq;\">list of Unix FAQs</ulink> contains a number of UseNet " -"documents which provide a nice historical reference." -msgstr "" - -#. Tag: para -#: post-install.xml:22 -#, no-c-format -msgid "" -"Linux is an implementation of Unix. The <ulink url=\"&url-ldp;\">Linux " -"Documentation Project (LDP)</ulink> collects a number of HOWTOs and online " -"books relating to Linux. Most of these documents can be installed locally; " -"just install the <classname>doc-linux-html</classname> package (HTML " -"versions) or the <classname>doc-linux-text</classname> package (ASCII " -"versions), then look in <filename>/usr/share/doc/HOWTO</filename>. " -"International versions of the LDP HOWTOs are also available as Debian " -"packages." -msgstr "" - -#. Tag: title -#: post-install.xml:43 -#, no-c-format -msgid "Orienting Yourself to Debian" -msgstr "" - -#. Tag: para -#: post-install.xml:44 -#, no-c-format -msgid "" -"Debian is a little different from other distributions. Even if you're " -"familiar with Linux in other distributions, there are things you should know " -"about Debian to help you to keep your system in a good, clean state. This " -"chapter contains material to help you get oriented; it is not intended to be " -"a tutorial for how to use Debian, but just a very brief glimpse of the " -"system for the very rushed." -msgstr "" - -#. Tag: title -#: post-install.xml:55 -#, no-c-format -msgid "Debian Packaging System" -msgstr "" - -#. Tag: para -#: post-install.xml:56 -#, no-c-format -msgid "" -"The most important concept to grasp is the Debian packaging system. In " -"essence, large parts of your system should be considered under the control " -"of the packaging system. These include: <itemizedlist> <listitem><para> " -"<filename>/usr</filename> (excluding <filename>/usr/local</filename>) </" -"para></listitem> <listitem><para> <filename>/var</filename> (you could make " -"<filename>/var/local</filename> and be safe in there) </para></listitem> " -"<listitem><para> <filename>/bin</filename> </para></listitem> " -"<listitem><para> <filename>/sbin</filename> </para></listitem> " -"<listitem><para> <filename>/lib</filename> </para></listitem> </" -"itemizedlist> For instance, if you replace <filename>/usr/bin/perl</" -"filename>, that will work, but then if you upgrade your <classname>perl</" -"classname> package, the file you put there will be replaced. Experts can get " -"around this by putting packages on <quote>hold</quote> in <command>aptitude</" -"command>." -msgstr "" - -#. Tag: para -#: post-install.xml:97 -#, no-c-format -msgid "" -"One of the best installation methods is apt. You can use the command line " -"version <command>apt-get</command> or full-screen text version " -"<application>aptitude</application>. Note apt will also let you merge main, " -"contrib, and non-free so you can have export-restricted packages as well as " -"standard versions." -msgstr "" - -#. Tag: title -#: post-install.xml:108 -#, no-c-format -msgid "Application Version Management" -msgstr "" - -#. Tag: para -#: post-install.xml:109 -#, no-c-format -msgid "" -"Alternative versions of applications are managed by update-alternatives. If " -"you are maintaining multiple versions of your applications, read the update-" -"alternatives man page." -msgstr "" - -#. Tag: title -#: post-install.xml:119 -#, no-c-format -msgid "Cron Job Management" -msgstr "" - -#. Tag: para -#: post-install.xml:120 -#, no-c-format -msgid "" -"Any jobs under the purview of the system administrator should be in " -"<filename>/etc</filename>, since they are configuration files. If you have a " -"root cron job for daily, weekly, or monthly runs, put them in <filename>/etc/" -"cron.{daily,weekly,monthly}</filename>. These are invoked from <filename>/" -"etc/crontab</filename>, and will run in alphabetic order, which serializes " -"them." -msgstr "" - -#. Tag: para -#: post-install.xml:129 -#, 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." -msgstr "" - -#. Tag: para -#: post-install.xml:138 -#, no-c-format -msgid "" -"In either case, you just edit the files and cron will notice them " -"automatically. There is no need to run a special command. For more " -"information see cron(8), crontab(5), and <filename>/usr/share/doc/cron/" -"README.Debian</filename>." -msgstr "" - -#. Tag: title -#: post-install.xml:155 -#, no-c-format -msgid "Reactivating DOS and Windows" -msgstr "" - -#. Tag: para -#: post-install.xml:156 -#, no-c-format -msgid "" -"After installing the base system and writing to the <emphasis>Master Boot " -"Record</emphasis>, you will be able to boot Linux, but probably nothing " -"else. This depends what you have chosen during the installation. This " -"chapter will describe how you can reactivate your old systems so that you " -"can also boot your DOS or Windows again." -msgstr "" - -#. Tag: para -#: post-install.xml:164 -#, no-c-format -msgid "" -"<command>LILO</command> is a boot manager with which you can also boot other " -"operating systems than Linux, which complies to PC conventions. The boot " -"manager is configured via <filename>/etc/lilo.conf</filename> file. Whenever " -"you edited this file you have to run <command>lilo</command> afterwards. The " -"reason for this is that the changes will take place only when you call the " -"program." -msgstr "" - -#. Tag: para -#: post-install.xml:174 -#, no-c-format -msgid "" -"Important parts of the <filename>lilo.conf</filename> file are the lines " -"containing the <userinput>image</userinput> and <userinput>other</userinput> " -"keywords, as well as the lines following those. They can be used to describe " -"a system which can be booted by <command>LILO</command>. Such a system can " -"include a kernel (<userinput>image</userinput>), a root partition, " -"additional kernel parameters, etc. as well as a configuration to boot " -"another, non-Linux (<userinput>other</userinput>) operating system. These " -"keywords can also be used more than once. The ordering of these systems " -"within the configuration file is important because it determines which " -"system will be booted automatically after, for instance, a timeout " -"(<userinput>delay</userinput>) presuming <command>LILO</command> wasn't " -"stopped by pressing the <keycap>shift</keycap> key." -msgstr "" - -#. Tag: para -#: post-install.xml:190 -#, no-c-format -msgid "" -"After a fresh install of Debian, just the current system is configured for " -"booting with <command>LILO</command>. If you want to boot another Linux " -"kernel, you have to edit the configuration file <filename>/etc/lilo.conf</" -"filename> to add the following lines: <informalexample><screen>\n" -"&additional-lilo-image;\n" -"</screen></informalexample> For a basic setup just the first two lines are " -"necessary. If you want to know more about the other two options please have " -"a look at the <command>LILO</command> documentation. This can be found in " -"<filename>/usr/share/doc/lilo/</filename>. The file which should be read is " -"<filename>Manual.txt</filename>. To have a quicker start into the world of " -"booting a system you can also look at the <command>LILO</command> man pages " -"<filename>lilo.conf</filename> for an overview of configuration keywords and " -"<filename>lilo</filename> for description of the installation of the new " -"configuration into the boot sector." -msgstr "" - -#. Tag: para -#: post-install.xml:210 -#, no-c-format -msgid "" -"Notice that there are other boot loaders available in &debian;, such as GRUB " -"(in <classname>grub</classname> package), CHOS (in <classname>chos</" -"classname> package), Extended-IPL (in <classname>extipl</classname> " -"package), loadlin (in <classname>loadlin</classname> package) etc." -msgstr "" - -#. Tag: title -#: post-install.xml:225 -#, no-c-format -msgid "Further Reading and Information" -msgstr "" - -#. Tag: para -#: post-install.xml:226 -#, no-c-format -msgid "" -"If you need information about a particular program, you should first try " -"<userinput>man <replaceable>program</replaceable></userinput>, or " -"<userinput>info <replaceable>program</replaceable></userinput>." -msgstr "" - -#. Tag: para -#: post-install.xml:232 -#, no-c-format -msgid "" -"There is lots of useful documentation in <filename>/usr/share/doc</filename> " -"as well. In particular, <filename>/usr/share/doc/HOWTO</filename> and " -"<filename>/usr/share/doc/FAQ</filename> contain lots of interesting " -"information. To submit bugs, look at <filename>/usr/share/doc/debian/bug*</" -"filename>. To read about Debian-specific issues for particular programs, " -"look at <filename>/usr/share/doc/(package name)/README.Debian</filename>." -msgstr "" - -#. Tag: para -#: post-install.xml:243 -#, no-c-format -msgid "" -"The <ulink url=\"http://www.debian.org/\">Debian web site</ulink> contains a " -"large quantity of documentation about Debian. In particular, see the <ulink " -"url=\"http://www.debian.org/doc/FAQ/\">Debian GNU/Linux FAQ</ulink> and the " -"<ulink url=\"http://www.debian.org/doc/user-manuals#quick-reference\">Debian " -"Reference</ulink>. An index of more Debian documentation is available from " -"the <ulink url=\"http://www.debian.org/doc/ddp\">Debian Documentation " -"Project</ulink>. The Debian community is self-supporting; to subscribe to " -"one or more of the Debian mailing lists, see the <ulink url=\"http://www." -"debian.org/MailingLists/subscribe\"> Mail List Subscription</ulink> page. " -"Last, but not least, the <ulink url=\"http://lists.debian.org/\">Debian " -"Mailing List Archives</ulink> contain a wealth of information on Debian." -msgstr "" - -#. Tag: para -#: post-install.xml:261 -#, no-c-format -msgid "" -"A general source of information on GNU/Linux is the <ulink url=\"http://www." -"tldp.org/\">Linux Documentation Project</ulink>. There you will find the " -"HOWTOs and pointers to other very valuable information on parts of a GNU/" -"Linux system." -msgstr "" - -#. Tag: title -#: post-install.xml:276 -#, no-c-format -msgid "Compiling a New Kernel" -msgstr "" - -#. Tag: para -#: post-install.xml:277 -#, no-c-format -msgid "" -"Why would someone want to compile a new kernel? It is often not necessary " -"since the default kernel shipped with Debian handles most configurations. " -"Also, Debian often offers several alternative kernels. So you may want to " -"check first if there is an alternative kernel image package that better " -"corresponds to your hardware. However, it can be useful to compile a new " -"kernel in order to:" -msgstr "" - -#. Tag: para -#: post-install.xml:287 -#, no-c-format -msgid "" -"handle special hardware needs, or hardware conflicts with the pre-supplied " -"kernels" -msgstr "" - -#. Tag: para -#: post-install.xml:293 -#, no-c-format -msgid "" -"use options of the kernel which are not supported in the pre-supplied " -"kernels (such as high memory support)" -msgstr "" - -#. Tag: para -#: post-install.xml:299 -#, no-c-format -msgid "optimize the kernel by removing useless drivers to speed up boot time" -msgstr "" - -#. Tag: para -#: post-install.xml:304 -#, no-c-format -msgid "create a monolithic instead of a modularized kernel" -msgstr "" - -#. Tag: para -#: post-install.xml:309 -#, no-c-format -msgid "run an updated or development kernel" -msgstr "" - -#. Tag: para -#: post-install.xml:314 -#, no-c-format -msgid "learn more about linux kernels" -msgstr "" - -#. Tag: title -#: post-install.xml:323 -#, no-c-format -msgid "Kernel Image Management" -msgstr "" - -#. Tag: para -#: post-install.xml:324 -#, no-c-format -msgid "Don't be afraid to try compiling the kernel. It's fun and profitable." -msgstr "" - -#. Tag: para -#: post-install.xml:328 -#, no-c-format -msgid "" -"To compile a kernel the Debian way, you need some packages: " -"<classname>fakeroot</classname>, <classname>kernel-package</classname>, " -"<phrase condition=\"classic-kpkg\"><classname>kernel-source-&kernelversion;</" -"classname> (the most recent version at the time of this writing)</phrase> " -"<phrase condition=\"common-kpkg\"><classname>linux-source-2.6</classname></" -"phrase> and a few others which are probably already installed (see " -"<filename>/usr/share/doc/kernel-package/README.gz</filename> for the " -"complete list)." -msgstr "" - -#. Tag: para -#: post-install.xml:339 -#, no-c-format -msgid "" -"This method will make a .deb of your kernel source, and, if you have non-" -"standard modules, make a synchronized dependent .deb of those too. It's a " -"better way to manage kernel images; <filename>/boot</filename> will hold the " -"kernel, the System.map, and a log of the active config file for the build." -msgstr "" - -#. Tag: para -#: post-install.xml:347 -#, no-c-format -msgid "" -"Note that you don't <emphasis>have</emphasis> to compile your kernel the " -"<quote>Debian way</quote>; but we find that using the packaging system to " -"manage your kernel is actually safer and easier. In fact, you can get your " -"kernel sources right from Linus instead of <phrase condition=\"classic-kpkg" -"\"><classname>kernel-source-&kernelversion;</classname>,</phrase> <phrase " -"condition=\"common-kpkg\"><classname>linux-source-2.6</classname>,</phrase> " -"yet still use the <classname>kernel-package</classname> compilation method." -msgstr "" - -#. Tag: para -#: post-install.xml:357 -#, no-c-format -msgid "" -"Note that you'll find complete documentation on using <classname>kernel-" -"package</classname> under <filename>/usr/share/doc/kernel-package</" -"filename>. This section just contains a brief tutorial." -msgstr "" - -#. Tag: para -#: post-install.xml:364 -#, no-c-format -msgid "" -"Hereafter, we'll assume you have free rein over your machine and will " -"extract your kernel source to somewhere in your home directory<footnote> " -"<para> There are other locations where you can extract kernel sources and " -"build your custom kernel, but this is easiest as it does not require special " -"permissions. </para> </footnote>. We'll also assume that your kernel version " -"is &kernelversion;. Make sure you are in the directory to where you want to " -"unpack the kernel sources, extract them using <phrase condition=\"classic-" -"kpkg\"><userinput>tar xjf /usr/src/kernel-source-&kernelversion;.tar.bz2</" -"userinput></phrase> <phrase condition=\"common-kpkg\"><userinput>tar xjf /" -"usr/src/linux-source-&kernelversion;.tar.bz2</userinput></phrase> and change " -"to the directory <phrase condition=\"classic-kpkg\"><filename>kernel-source-" -"&kernelversion;</filename></phrase> <phrase condition=\"common-kpkg" -"\"><filename>linux-source-&kernelversion;</filename></phrase> that will have " -"been created." -msgstr "" - -#. Tag: para -#: post-install.xml:389 -#, no-c-format -msgid "" -"Now, you can configure your kernel. Run <userinput>make xconfig</userinput> " -"if X11 is installed, configured and being run; run <userinput>make " -"menuconfig</userinput> otherwise (you'll need <classname>libncurses5-dev</" -"classname> installed). Take the time to read the online help and choose " -"carefully. When in doubt, it is typically better to include the device " -"driver (the software which manages hardware peripherals, such as Ethernet " -"cards, SCSI controllers, and so on) you are unsure about. Be careful: other " -"options, not related to a specific hardware, should be left at the default " -"value if you do not understand them. Do not forget to select <quote>Kernel " -"module loader</quote> in <quote>Loadable module support</quote> (it is not " -"selected by default). If not included, your Debian installation will " -"experience problems." -msgstr "" - -#. Tag: para -#: post-install.xml:404 -#, no-c-format -msgid "" -"Clean the source tree and reset the <classname>kernel-package</classname> " -"parameters. To do that, do <userinput>make-kpkg clean</userinput>." -msgstr "" - -#. Tag: para -#: post-install.xml:409 -#, no-c-format -msgid "" -"Now, compile the kernel: <userinput>fakeroot make-kpkg --revision=custom.1.0 " -"kernel_image</userinput>. The version number of <quote>1.0</quote> can be " -"changed at will; this is just a version number that you will use to track " -"your kernel builds. Likewise, you can put any word you like in place of " -"<quote>custom</quote> (e.g., a host name). Kernel compilation may take quite " -"a while, depending on the power of your machine." -msgstr "" - -#. Tag: para -#: post-install.xml:419 -#, no-c-format -msgid "" -"If you require PCMCIA support, you'll also need to install the " -"<classname>pcmcia-source</classname> package. Unpack the gzipped tar file as " -"root in the directory <filename>/usr/src</filename> (it's important that " -"modules are found where they are expected to be found, namely, <filename>/" -"usr/src/modules</filename>). Then, as root, do <userinput>make-kpkg " -"modules_image</userinput>." -msgstr "" - -#. Tag: para -#: post-install.xml:428 -#, no-c-format -msgid "" -"Once the compilation is complete, you can install your custom kernel like " -"any package. As root, do <userinput>dpkg -i ../kernel-image-&kernelversion;-" -"<replaceable>subarchitecture</replaceable>_custom.1.0_&architecture;.deb</" -"userinput>. The <replaceable>subarchitecture</replaceable> part is an " -"optional sub-architecture, <phrase arch=\"i386\"> such as <quote>i586</" -"quote>, </phrase> depending on what kernel options you set. <userinput>dpkg -" -"i kernel-image...</userinput> will install the kernel, along with some other " -"nice supporting files. For instance, the <filename>System.map</filename> " -"will be properly installed (helpful for debugging kernel problems), and " -"<filename>/boot/config-&kernelversion;</filename> will be installed, " -"containing your current configuration set. Your new <classname>kernel-image-" -"&kernelversion;</classname> package is also clever enough to automatically " -"use your platform's boot-loader to run an update on the booting, allowing " -"you to boot without re-running the boot loader. If you have created a " -"modules package, e.g., if you have PCMCIA, you'll need to install that " -"package as well." -msgstr "" - -#. Tag: para -#: post-install.xml:449 -#, no-c-format -msgid "" -"It is time to reboot the system: read carefully any warning that the above " -"step may have produced, then <userinput>shutdown -r now</userinput>." -msgstr "" - -#. Tag: para -#: post-install.xml:454 -#, no-c-format -msgid "" -"For more information on Debian kernels and kernel compilation, see the " -"<ulink url=\"&url-kernel-handbook;\">Debian Linux Kernel Handbook</ulink>. " -"For more information on <classname>kernel-package</classname>, read the fine " -"documentation in <filename>/usr/share/doc/kernel-package</filename>." -msgstr "" - -#. Tag: title -#: post-install.xml:470 -#, no-c-format -msgid "Recovering a Broken System" -msgstr "" - -#. Tag: para -#: post-install.xml:471 -#, no-c-format -msgid "" -"Sometimes, things go wrong, and the system you've carefully installed is no " -"longer bootable. Perhaps the boot loader configuration broke while trying " -"out a change, or perhaps a new kernel you installed won't boot, or perhaps " -"cosmic rays hit your disk and flipped a bit in <filename>/sbin/init</" -"filename>. Regardless of the cause, you'll need to have a system to work " -"from while you fix it, and rescue mode can be useful for this." -msgstr "" - -#. Tag: para -#: post-install.xml:481 -#, no-c-format -msgid "" -"To access rescue mode, type <userinput>rescue</userinput> at the " -"<prompt>boot:</prompt> prompt, or boot with the <userinput>rescue/" -"enable=true</userinput> boot parameter. You'll be shown the first few " -"screens of the installer, with a note in the corner of the display to " -"indicate that this is rescue mode, not a full installation. Don't worry, " -"your system is not about to be overwritten! Rescue mode simply takes " -"advantage of the hardware detection facilities available in the installer to " -"ensure that your disks, network devices, and so on are available to you " -"while repairing your system." -msgstr "" - -#. Tag: para -#: post-install.xml:496 -#, no-c-format -msgid "" -"Instead of the partitioning tool, you should now be presented with a list of " -"the partitions on your system, and asked to select one of them. Normally, " -"you should select the partition containing the root file system that you " -"need to repair. You may select partitions on RAID and LVM devices as well as " -"those created directly on disks." -msgstr "" - -#. Tag: para -#: post-install.xml:504 -#, no-c-format -msgid "" -"If possible, the installer will now present you with a shell prompt in the " -"file system you selected, which you can use to perform any necessary " -"repairs. <phrase arch=\"i386\"> For example, if you need to reinstall the " -"GRUB boot loader into the master boot record of the first hard disk, you " -"could enter the command <userinput>grub-install '(hd0)'</userinput> to do " -"so. </phrase>" -msgstr "" - -#. Tag: para -#: post-install.xml:516 -#, no-c-format -msgid "" -"If the installer cannot run a usable shell in the root file system you " -"selected, perhaps because the file system is corrupt, then it will issue a " -"warning and offer to give you a shell in the installer environment instead. " -"You may not have as many tools available in this environment, but they will " -"often be enough to repair your system anyway. The root file system you " -"selected will be mounted on the <filename>/target</filename> directory." -msgstr "" - -#. Tag: para -#: post-install.xml:525 -#, no-c-format -msgid "In either case, after you exit the shell, the system will reboot." -msgstr "" - -#. Tag: para -#: post-install.xml:529 -#, no-c-format -msgid "" -"Finally, note that repairing broken systems can be difficult, and this " -"manual does not attempt to go into all the things that might have gone wrong " -"or how to fix them. If you have problems, consult an expert." -msgstr "" diff --git a/po/pl/preface.po b/po/pl/preface.po deleted file mode 100644 index 9cfae2ff1..000000000 --- a/po/pl/preface.po +++ /dev/null @@ -1,55 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: preface.xml:5 -#, no-c-format -msgid "Installing &debian; &release; For &architecture;" -msgstr "" - -#. Tag: para -#: preface.xml:6 -#, no-c-format -msgid "" -"We are delighted that you have decided to try Debian, and are sure that you " -"will find that Debian's GNU/Linux distribution is unique. &debian; brings " -"together high-quality free software from around the world, integrating it " -"into a coherent whole. We believe that you will find that the result is " -"truly more than the sum of the parts." -msgstr "" - -#. Tag: para -#: preface.xml:15 -#, no-c-format -msgid "" -"We understand that many of you want to install Debian without reading this " -"manual, and the Debian installer is designed to make this possible. If you " -"don't have time to read the whole Installation Guide right now, we recommend " -"that you read the Installation Howto, which will walk you through the basic " -"installation process, and links to the manual for more advanced topics or " -"for when things go wrong. The Installation Howto can be found in <xref " -"linkend=\"installation-howto\"/>." -msgstr "" - -#. Tag: para -#: preface.xml:25 -#, no-c-format -msgid "" -"With that said, we hope that you have the time to read most of this manual, " -"and doing so will lead to a more informed and likely more successful " -"installation experience." -msgstr "" diff --git a/po/pl/preparing.po b/po/pl/preparing.po deleted file mode 100644 index 44c979f31..000000000 --- a/po/pl/preparing.po +++ /dev/null @@ -1,2672 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-03-02 09:59+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: preparing.xml:5 -#, no-c-format -msgid "Before Installing &debian;" -msgstr "" - -#. Tag: para -#: preparing.xml:6 -#, no-c-format -msgid "" -"This chapter deals with the preparation for installing Debian before you " -"even boot the installer. This includes backing up your data, gathering " -"information about your hardware, and locating any necessary information." -msgstr "" - -#. Tag: title -#: preparing.xml:19 -#, no-c-format -msgid "Overview of the Installation Process" -msgstr "" - -#. Tag: para -#: preparing.xml:20 -#, no-c-format -msgid "" -"First, just a note about re-installations. With Debian, a circumstance that " -"will require a complete re-installation of your system is very rare; perhaps " -"mechanical failure of the hard disk would be the most common case." -msgstr "" - -#. Tag: para -#: preparing.xml:27 -#, no-c-format -msgid "" -"Many common operating systems may require a complete installation to be " -"performed when critical failures take place or for upgrades to new OS " -"versions. Even if a completely new installation isn't required, often the " -"programs you use must be re-installed to operate properly in the new OS." -msgstr "" - -#. Tag: para -#: preparing.xml:35 -#, no-c-format -msgid "" -"Under &debian;, it is much more likely that your OS can be repaired rather " -"than replaced if things go wrong. Upgrades never require a wholesale " -"installation; you can always upgrade in-place. And the programs are almost " -"always compatible with successive OS releases. If a new program version " -"requires newer supporting software, the Debian packaging system ensures that " -"all the necessary software is automatically identified and installed. The " -"point is, much effort has been put into avoiding the need for re-" -"installation, so think of it as your very last option. The installer is " -"<emphasis>not</emphasis> designed to re-install over an existing system." -msgstr "" - -#. Tag: para -#: preparing.xml:48 -#, no-c-format -msgid "" -"Here's a road map for the steps you will take during the installation " -"process." -msgstr "" - -#. Tag: para -#: preparing.xml:56 -#, no-c-format -msgid "" -"Back up any existing data or documents on the hard disk where you plan to " -"install." -msgstr "" - -#. Tag: para -#: preparing.xml:62 -#, no-c-format -msgid "" -"Gather information about your computer and any needed documentation, before " -"starting the installation." -msgstr "" - -#. Tag: para -#: preparing.xml:68 -#, no-c-format -msgid "Create partition-able space for Debian on your hard disk." -msgstr "" - -#. Tag: para -#: preparing.xml:73 -#, no-c-format -msgid "" -"Locate and/or download the installer software and any specialized driver " -"files your machine requires (except Debian CD users)." -msgstr "" - -#. Tag: para -#: preparing.xml:79 -#, no-c-format -msgid "" -"Set up boot tapes/floppies/USB sticks, or place boot files (most Debian CD " -"users can boot from one of the CDs)." -msgstr "" - -#. Tag: para -#: preparing.xml:85 -#, no-c-format -msgid "Boot the installation system." -msgstr "" - -#. Tag: para -#: preparing.xml:90 -#, no-c-format -msgid "Select installation language." -msgstr "" - -#. Tag: para -#: preparing.xml:95 -#, no-c-format -msgid "Activate the ethernet network connection, if available." -msgstr "" - -#. Tag: para -#: preparing.xml:101 -#, no-c-format -msgid "Configure one network interface." -msgstr "" - -#. Tag: para -#: preparing.xml:106 -#, no-c-format -msgid "Open a ssh connection to the new system." -msgstr "" - -#. Tag: para -#: preparing.xml:111 -#, no-c-format -msgid "Attach one or more DASDs (Direct Access Storage Device)." -msgstr "" - -#. Tag: para -#: preparing.xml:117 -#, no-c-format -msgid "Create and mount the partitions on which Debian will be installed." -msgstr "" - -#. Tag: para -#: preparing.xml:122 -#, no-c-format -msgid "" -"Watch the automatic download/install/setup of the <firstterm>base system</" -"firstterm>." -msgstr "" - -#. Tag: para -#: preparing.xml:128 -#, no-c-format -msgid "" -"Install a <firstterm>boot loader</firstterm> which can start up &debian; and/" -"or your existing system." -msgstr "" - -#. Tag: para -#: preparing.xml:134 -#, no-c-format -msgid "Load the newly installed system for the first time." -msgstr "" - -#. Tag: para -#: preparing.xml:141 -#, no-c-format -msgid "" -"If you have problems during the installation, it helps to know which " -"packages are involved in which steps. Introducing the leading software " -"actors in this installation drama:" -msgstr "" - -#. Tag: para -#: preparing.xml:147 -#, no-c-format -msgid "" -"The installer software, <classname>debian-installer</classname>, is the " -"primary concern of this manual. It detects hardware and loads appropriate " -"drivers, uses <classname>dhcp-client</classname> to set up the network " -"connection, and runs <classname>debootstrap</classname> to install the base " -"system packages. Many more actors play smaller parts in this process, but " -"<classname>debian-installer</classname> has completed its task when you load " -"the new system for the first time." -msgstr "" - -#. Tag: para -#: preparing.xml:157 -#, no-c-format -msgid "" -"To tune the system to your needs, <classname>tasksel</classname> allows you " -"to choose to install various predefined bundles of software like a Web " -"server or a Desktop environment." -msgstr "" - -#. Tag: para -#: preparing.xml:163 -#, no-c-format -msgid "" -"When <classname>debian-installer</classname> finishes, before the first " -"system load, you have only a very basic command line driven system. The " -"graphical interface which displays windows on your monitor will not be " -"installed unless you select it with <classname>tasksel</classname>. It's " -"optional because many &debian; systems are servers which don't really have " -"any need for a graphical user interface to do their job." -msgstr "" - -#. Tag: para -#: preparing.xml:172 -#, no-c-format -msgid "" -"Just be aware that the X system is completely separate from " -"<classname>debian-installer</classname>, and in fact is much more " -"complicated. Installation and trouble shooting of the X window installation " -"is not within the scope of this manual." -msgstr "" - -#. Tag: title -#: preparing.xml:188 -#, no-c-format -msgid "Back Up Your Existing Data!" -msgstr "" - -#. Tag: para -#: preparing.xml:189 -#, no-c-format -msgid "" -"Before you start, make sure to back up every file that is now on your " -"system. If this is the first time a non-native operating system has been " -"installed on your computer, it's quite likely you will need to re-partition " -"your disk to make room for &debian;. Anytime you partition your disk, you " -"should count on losing everything on the disk, no matter what program you " -"use to do it. The programs used in installation are quite reliable and most " -"have seen years of use; but they are also quite powerful and a false move " -"can cost you. Even after backing up be careful and think about your answers " -"and actions. Two minutes of thinking can save hours of unnecessary work." -msgstr "" - -#. Tag: para -#: preparing.xml:202 -#, no-c-format -msgid "" -"If you are creating a multi-boot system, make sure that you have the " -"distribution media of any other present operating systems on hand. " -"Especially if you repartition your boot drive, you might find that you have " -"to reinstall your operating system's boot loader, or in many cases the whole " -"operating system itself and all files on the affected partitions." -msgstr "" - -#. Tag: para -#: preparing.xml:213 -#, no-c-format -msgid "" -"With the exception of the BVM and Motorola VMEbus computers, the only " -"supported installation method for m68k systems is booting from a local disk " -"or floppy using an AmigaOS/TOS/MacOS-based bootstrap, for these machines you " -"will need the original operating system in order to boot Linux. In order to " -"boot Linux on the BVM and Motorola VMEbus machines you will need the " -"<quote>BVMBug</quote> or <quote>16xBug</quote> boot ROMs." -msgstr "" - -#. Tag: title -#: preparing.xml:231 -#, no-c-format -msgid "Information You Will Need" -msgstr "" - -#. Tag: title -#: preparing.xml:234 -#, no-c-format -msgid "Documentation" -msgstr "" - -#. Tag: title -#: preparing.xml:237 -#, no-c-format -msgid "Installation Manual" -msgstr "" - -#. Tag: para -#: preparing.xml:239 -#, no-c-format -msgid "This document you are now reading, in plain ASCII, HTML or PDF format." -msgstr "" - -#. Tag: itemizedlist -#: preparing.xml:245 -#, no-c-format -msgid "&list-install-manual-files;" -msgstr "" - -#. Tag: para -#: preparing.xml:251 -#, no-c-format -msgid "" -"The document you are now reading, which is the official version of the " -"Installation Guide for the &releasename; release of Debian; available in " -"<ulink url=\"&url-release-area;/installmanual\">various formats and " -"translations</ulink>." -msgstr "" - -#. Tag: para -#: preparing.xml:260 -#, no-c-format -msgid "" -"The document you are now reading, which is a development version of the " -"Installation Guide for the next release of Debian; available in <ulink url=" -"\"&url-d-i-alioth-manual;\">various formats and translations</ulink>." -msgstr "" - -#. Tag: title -#: preparing.xml:272 -#, no-c-format -msgid "Hardware documentation" -msgstr "" - -#. Tag: para -#: preparing.xml:273 -#, no-c-format -msgid "" -"Often contains useful information on configuring or using your hardware." -msgstr "" - -#. Tag: ulink -#: preparing.xml:284 -#, no-c-format -msgid "Linux Hardware Compatibility HOWTO" -msgstr "" - -#. Tag: ulink -#: preparing.xml:290 -#, no-c-format -msgid "Linux/m68k FAQ" -msgstr "" - -#. Tag: ulink -#: preparing.xml:296 -#, no-c-format -msgid "Linux/Alpha FAQ" -msgstr "" - -#. Tag: ulink -#: preparing.xml:302 -#, no-c-format -msgid "Linux for SPARC Processors FAQ" -msgstr "" - -#. Tag: ulink -#: preparing.xml:308 -#, no-c-format -msgid "Linux/Mips website" -msgstr "" - -#. Tag: title -#: preparing.xml:317 -#, no-c-format -msgid "&arch-title; Hardware References" -msgstr "" - -#. Tag: para -#: preparing.xml:318 -#, no-c-format -msgid "" -"Installation instructions and device drivers (DASD, XPRAM, Console, tape, " -"z90 crypto, chandev, network) for Linux on &arch-title; using kernel 2.4" -msgstr "" - -#. Tag: ulink -#: preparing.xml:330 -#, no-c-format -msgid "Device Drivers and Installation Commands" -msgstr "" - -#. Tag: para -#: preparing.xml:335 -#, no-c-format -msgid "" -"IBM Redbook describing how Linux can be combined with z/VM on zSeries and " -"&arch-title; hardware." -msgstr "" - -#. Tag: ulink -#: preparing.xml:345 -#, no-c-format -msgid "Linux for &arch-title;" -msgstr "" - -#. Tag: para -#: preparing.xml:351 -#, no-c-format -msgid "" -"IBM Redbook describing the Linux distributions available for the mainframe. " -"It has no chapter about Debian but the basic installation concepts are the " -"same across all &arch-title; distributions." -msgstr "" - -#. Tag: ulink -#: preparing.xml:362 -#, no-c-format -msgid "Linux for IBM eServer zSeries and &arch-title;: Distributions" -msgstr "" - -#. Tag: title -#: preparing.xml:372 -#, no-c-format -msgid "Finding Sources of Hardware Information" -msgstr "" - -#. Tag: para -#: preparing.xml:373 -#, no-c-format -msgid "" -"In many cases, the installer will be able to automatically detect your " -"hardware. But to be prepared, we do recommend familiarizing yourself with " -"your hardware before the install." -msgstr "" - -#. Tag: para -#: preparing.xml:379 -#, no-c-format -msgid "Hardware information can be gathered from:" -msgstr "" - -#. Tag: para -#: preparing.xml:386 -#, no-c-format -msgid "The manuals that come with each piece of hardware." -msgstr "" - -#. Tag: para -#: preparing.xml:391 -#, no-c-format -msgid "" -"The BIOS setup screens of your computer. You can view these screens when you " -"start your computer by pressing a combination of keys. Check your manual for " -"the combination. Often, it is the <keycap>Delete</keycap> key." -msgstr "" - -#. Tag: para -#: preparing.xml:398 -#, no-c-format -msgid "The cases and boxes for each piece of hardware." -msgstr "" - -#. Tag: para -#: preparing.xml:404 -#, no-c-format -msgid "The System window in the Windows Control Panel." -msgstr "" - -#. Tag: para -#: preparing.xml:410 -#, no-c-format -msgid "" -"System commands or tools in another operating system, including file manager " -"displays. This source is especially useful for information about RAM and " -"hard drive memory." -msgstr "" - -#. Tag: para -#: preparing.xml:417 -#, no-c-format -msgid "" -"Your system administrator or Internet Service Provider. These sources can " -"tell you the settings you need to set up your networking and e-mail." -msgstr "" - -#. Tag: title -#: preparing.xml:429 -#, no-c-format -msgid "Hardware Information Needed for an Install" -msgstr "" - -#. Tag: entry -#: preparing.xml:433 -#, no-c-format -msgid "Hardware" -msgstr "" - -#. Tag: entry -#: preparing.xml:433 -#, no-c-format -msgid "Information You Might Need" -msgstr "" - -#. Tag: entry -#: preparing.xml:439 -#, no-c-format -msgid "Hard Drives" -msgstr "" - -#. Tag: entry -#: preparing.xml:440 -#, no-c-format -msgid "How many you have." -msgstr "" - -#. Tag: entry -#: preparing.xml:442 -#, no-c-format -msgid "Their order on the system." -msgstr "" - -#. Tag: entry -#: preparing.xml:444 -#, no-c-format -msgid "Whether IDE or SCSI (most computers are IDE)." -msgstr "" - -#. Tag: entry -#: preparing.xml:447 -#, no-c-format -msgid "Whether IDE or SCSI (most m68k computers are SCSI)." -msgstr "" - -#. Tag: entry -#: preparing.xml:449 preparing.xml:501 -#, no-c-format -msgid "Available free space." -msgstr "" - -#. Tag: entry -#: preparing.xml:450 -#, no-c-format -msgid "Partitions." -msgstr "" - -#. Tag: entry -#: preparing.xml:452 -#, no-c-format -msgid "Partitions where other operating systems are installed." -msgstr "" - -#. Tag: entry -#: preparing.xml:456 -#, no-c-format -msgid "Monitor" -msgstr "" - -#. Tag: entry -#: preparing.xml:457 preparing.xml:477 preparing.xml:483 preparing.xml:489 -#, no-c-format -msgid "Model and manufacturer." -msgstr "" - -#. Tag: entry -#: preparing.xml:459 -#, no-c-format -msgid "Resolutions supported." -msgstr "" - -#. Tag: entry -#: preparing.xml:460 -#, no-c-format -msgid "Horizontal refresh rate." -msgstr "" - -#. Tag: entry -#: preparing.xml:461 -#, no-c-format -msgid "Vertical refresh rate." -msgstr "" - -#. Tag: entry -#: preparing.xml:463 -#, no-c-format -msgid "Color depth (number of colors) supported." -msgstr "" - -#. Tag: entry -#: preparing.xml:465 -#, no-c-format -msgid "Screen size." -msgstr "" - -#. Tag: entry -#: preparing.xml:468 -#, no-c-format -msgid "Mouse" -msgstr "" - -#. Tag: entry -#: preparing.xml:469 -#, no-c-format -msgid "Type: serial, PS/2, or USB." -msgstr "" - -#. Tag: entry -#: preparing.xml:471 -#, no-c-format -msgid "Port." -msgstr "" - -#. Tag: entry -#: preparing.xml:472 -#, no-c-format -msgid "Manufacturer." -msgstr "" - -#. Tag: entry -#: preparing.xml:473 -#, no-c-format -msgid "Number of buttons." -msgstr "" - -#. Tag: entry -#: preparing.xml:476 preparing.xml:504 -#, no-c-format -msgid "Network" -msgstr "" - -#. Tag: entry -#: preparing.xml:479 preparing.xml:505 -#, no-c-format -msgid "Type of adapter." -msgstr "" - -#. Tag: entry -#: preparing.xml:482 -#, no-c-format -msgid "Printer" -msgstr "" - -#. Tag: entry -#: preparing.xml:485 -#, no-c-format -msgid "Printing resolutions supported." -msgstr "" - -#. Tag: entry -#: preparing.xml:488 -#, no-c-format -msgid "Video Card" -msgstr "" - -#. Tag: entry -#: preparing.xml:491 -#, no-c-format -msgid "Video RAM available." -msgstr "" - -#. Tag: entry -#: preparing.xml:493 -#, no-c-format -msgid "" -"Resolutions and color depths supported (these should be checked against your " -"monitor's capabilities)." -msgstr "" - -#. Tag: entry -#: preparing.xml:498 -#, no-c-format -msgid "DASD" -msgstr "" - -#. Tag: entry -#: preparing.xml:499 -#, no-c-format -msgid "Device number(s)." -msgstr "" - -#. Tag: entry -#: preparing.xml:507 -#, no-c-format -msgid "Device numbers." -msgstr "" - -#. Tag: entry -#: preparing.xml:508 -#, no-c-format -msgid "Relative adapter number for OSA cards." -msgstr "" - -#. Tag: title -#: preparing.xml:516 -#, no-c-format -msgid "Hardware Compatibility" -msgstr "" - -#. Tag: para -#: preparing.xml:518 -#, no-c-format -msgid "" -"Many brand name products work without trouble on Linux. Moreover, hardware " -"for Linux is improving daily. However, Linux still does not run as many " -"different types of hardware as some operating systems." -msgstr "" - -#. Tag: para -#: preparing.xml:524 -#, no-c-format -msgid "" -"In particular, Linux usually cannot run hardware that requires a running " -"version of Windows to work." -msgstr "" - -#. Tag: para -#: preparing.xml:529 -#, no-c-format -msgid "" -"Although some Windows-specific hardware can be made to run on Linux, doing " -"so usually requires extra effort. In addition, Linux drivers for Windows-" -"specific hardware are usually specific to one Linux kernel. Therefore, they " -"can quickly become obsolete." -msgstr "" - -#. Tag: para -#: preparing.xml:536 -#, no-c-format -msgid "" -"So called win-modems are the most common type of this hardware. However, " -"printers and other equipment may also be Windows-specific." -msgstr "" - -#. Tag: para -#: preparing.xml:541 -#, no-c-format -msgid "You can check hardware compatibility by:" -msgstr "" - -#. Tag: para -#: preparing.xml:546 -#, no-c-format -msgid "Checking manufacturers' web sites for new drivers." -msgstr "" - -#. Tag: para -#: preparing.xml:551 -#, no-c-format -msgid "" -"Looking at web sites or manuals for information about emulation. Lesser " -"known brands can sometimes use the drivers or settings for better-known ones." -msgstr "" - -#. Tag: para -#: preparing.xml:558 -#, no-c-format -msgid "" -"Checking hardware compatibility lists for Linux on web sites dedicated to " -"your architecture." -msgstr "" - -#. Tag: para -#: preparing.xml:564 -#, no-c-format -msgid "Searching the Internet for other users' experiences." -msgstr "" - -#. Tag: title -#: preparing.xml:575 -#, no-c-format -msgid "Network Settings" -msgstr "" - -#. Tag: para -#: preparing.xml:577 -#, no-c-format -msgid "" -"If your computer is connected to a network 24 hours a day (i.e., an Ethernet " -"or equivalent connection — not a PPP connection), you should ask your " -"network's system administrator for this information." -msgstr "" - -#. Tag: para -#: preparing.xml:584 -#, no-c-format -msgid "Your host name (you may be able to decide this on your own)." -msgstr "" - -#. Tag: para -#: preparing.xml:589 -#, no-c-format -msgid "Your domain name." -msgstr "" - -#. Tag: para -#: preparing.xml:594 -#, no-c-format -msgid "Your computer's IP address." -msgstr "" - -#. Tag: para -#: preparing.xml:599 -#, no-c-format -msgid "The netmask to use with your network." -msgstr "" - -#. Tag: para -#: preparing.xml:604 -#, no-c-format -msgid "" -"The IP address of the default gateway system you should route to, if your " -"network <emphasis>has</emphasis> a gateway." -msgstr "" - -#. Tag: para -#: preparing.xml:610 -#, no-c-format -msgid "" -"The system on your network that you should use as a DNS (Domain Name " -"Service) server." -msgstr "" - -#. Tag: para -#: preparing.xml:618 -#, no-c-format -msgid "" -"On the other hand, if your administrator tells you that a DHCP server is " -"available and is recommended, then you don't need this information because " -"the DHCP server will provide it directly to your computer during the " -"installation process." -msgstr "" - -#. Tag: para -#: preparing.xml:625 -#, no-c-format -msgid "If you use a wireless network, you should also find out:" -msgstr "" - -#. Tag: para -#: preparing.xml:630 -#, no-c-format -msgid "ESSID of your wireless network." -msgstr "" - -#. Tag: para -#: preparing.xml:635 -#, no-c-format -msgid "WEP security key (if applicable)." -msgstr "" - -#. Tag: title -#: preparing.xml:652 -#, no-c-format -msgid "Meeting Minimum Hardware Requirements" -msgstr "" - -#. Tag: para -#: preparing.xml:653 -#, no-c-format -msgid "" -"Once you have gathered information about your computer's hardware, check " -"that your hardware will let you do the type of installation that you want to " -"do." -msgstr "" - -#. Tag: para -#: preparing.xml:659 -#, no-c-format -msgid "" -"Depending on your needs, you might manage with less than some of the " -"recommended hardware listed in the table below. However, most users risk " -"being frustrated if they ignore these suggestions." -msgstr "" - -#. Tag: para -#: preparing.xml:665 -#, no-c-format -msgid "" -"A Pentium 100 is the minimum recommended for desktop systems, and a Pentium " -"II-300 for a Server." -msgstr "" - -#. Tag: para -#: preparing.xml:670 -#, no-c-format -msgid "" -"A 68030 or better processor is recommended for m68k installs. You may get by " -"with a little less drive space than shown." -msgstr "" - -#. Tag: para -#: preparing.xml:675 -#, no-c-format -msgid "" -"Any OldWorld or NewWorld PowerPC can serve well as a Desktop System. For " -"servers, a minimum 132-Mhz machine is recommended." -msgstr "" - -#. Tag: title -#: preparing.xml:684 -#, no-c-format -msgid "Recommended Minimum System Requirements" -msgstr "" - -#. Tag: entry -#: preparing.xml:688 -#, no-c-format -msgid "Install Type" -msgstr "" - -#. Tag: entry -#: preparing.xml:688 -#, no-c-format -msgid "<entry>RAM</entry>" -msgstr "" - -#. Tag: entry -#: preparing.xml:688 -#, no-c-format -msgid "Hard Drive" -msgstr "" - -#. Tag: entry -#: preparing.xml:694 -#, no-c-format -msgid "No desktop" -msgstr "" - -#. Tag: entry -#: preparing.xml:695 -#, no-c-format -msgid "24 megabytes" -msgstr "" - -#. Tag: entry -#: preparing.xml:696 -#, no-c-format -msgid "450 megabytes" -msgstr "" - -#. Tag: entry -#: preparing.xml:698 -#, no-c-format -msgid "With Desktop" -msgstr "" - -#. Tag: entry -#: preparing.xml:699 -#, no-c-format -msgid "64 megabytes" -msgstr "" - -#. Tag: entry -#: preparing.xml:700 -#, no-c-format -msgid "1 gigabyte" -msgstr "" - -#. Tag: entry -#: preparing.xml:702 -#, no-c-format -msgid "Server" -msgstr "" - -#. Tag: entry -#: preparing.xml:703 -#, no-c-format -msgid "128 megabytes" -msgstr "" - -#. Tag: entry -#: preparing.xml:704 -#, no-c-format -msgid "4 gigabytes" -msgstr "" - -#. Tag: para -#: preparing.xml:709 -#, no-c-format -msgid "" -"Here is a sampling of some common Debian system configurations. You can also " -"get an idea of the disk space used by related groups of programs by " -"referring to <xref linkend=\"tasksel-size-list\"/>." -msgstr "" - -#. Tag: term -#: preparing.xml:719 -#, no-c-format -msgid "Standard Server" -msgstr "" - -#. Tag: para -#: preparing.xml:720 -#, no-c-format -msgid "" -"This is a small server profile, useful for a stripped down server which does " -"not have a lot of niceties for shell users. It includes an FTP server, a web " -"server, DNS, NIS, and POP. For these 100MB of disk space would suffice, and " -"then you would need to add space for any data you serve up." -msgstr "" - -#. Tag: term -#: preparing.xml:732 -#, no-c-format -msgid "Desktop" -msgstr "" - -#. Tag: para -#: preparing.xml:733 -#, no-c-format -msgid "" -"A standard desktop box, including the X window system, full desktop " -"environments, sound, editors, etc. You'll need about 2GB using the standard " -"desktop task, though it can be done in far less." -msgstr "" - -#. Tag: term -#: preparing.xml:743 -#, no-c-format -msgid "Work Console" -msgstr "" - -#. Tag: para -#: preparing.xml:744 -#, no-c-format -msgid "" -"A more stripped-down user machine, without the X window system or X " -"applications. Possibly suitable for a laptop or mobile computer. The size is " -"around 140MB." -msgstr "" - -#. Tag: term -#: preparing.xml:754 -#, no-c-format -msgid "Developer" -msgstr "" - -#. Tag: para -#: preparing.xml:755 -#, no-c-format -msgid "" -"A desktop setup with all the development packages, such as Perl, C, C++, " -"etc. Size is around 475MB. Assuming you are adding X11 and some additional " -"packages for other uses, you should plan around 800MB for this type of " -"machine." -msgstr "" - -#. Tag: para -#: preparing.xml:765 -#, no-c-format -msgid "" -"Remember that these sizes don't include all the other materials which are " -"usually to be found, such as user files, mail, and data. It is always best " -"to be generous when considering the space for your own files and data. " -"Notably, the <filename>/var</filename> partition contains a lot of state " -"information specific to Debian in addition to its regular contents like " -"logfiles. The <command>dpkg</command> files (with information on all " -"installed packages) can easily consume 20MB. Also, <command>apt-get</" -"command> puts downloaded packages here before they are installed. You should " -"usually allocate at least 100MB for <filename>/var</filename>." -msgstr "" - -#. Tag: title -#: preparing.xml:789 -#, no-c-format -msgid "Pre-Partitioning for Multi-Boot Systems" -msgstr "" - -#. Tag: para -#: preparing.xml:790 -#, no-c-format -msgid "" -"Partitioning your disk simply refers to the act of breaking up your disk " -"into sections. Each section is then independent of the others. It's roughly " -"equivalent to putting up walls inside a house; if you add furniture to one " -"room it doesn't affect any other room." -msgstr "" - -#. Tag: para -#: preparing.xml:797 -#, no-c-format -msgid "" -"Whenever this section talks about <quote>disks</quote> you should translate " -"this into a DASD or VM minidisk in the &arch-title; world. Also a machine " -"means an LPAR or VM guest in this case." -msgstr "" - -#. Tag: para -#: preparing.xml:803 -#, no-c-format -msgid "" -"If you already have an operating system on your system <phrase arch=\"i386" -"\"> (Windows 9x, Windows NT/2000/XP, OS/2, MacOS, Solaris, FreeBSD, " -"…) </phrase> <phrase arch=\"alpha\"> (Tru64 (Digital UNIX), OpenVMS, " -"Windows NT, FreeBSD, …) </phrase> <phrase arch=\"s390\"> (VM, z/OS, " -"OS/390, …) </phrase> <phrase arch=\"m68k\"> (Amiga OS, Atari TOS, Mac " -"OS, …) </phrase> and want to stick Linux on the same disk, you will " -"need to repartition the disk. Debian requires its own hard disk partitions. " -"It cannot be installed on Windows or MacOS partitions. It may be able to " -"share some partitions with other Linux systems, but that's not covered here. " -"At the very least you will need a dedicated partition for the Debian root." -msgstr "" - -#. Tag: para -#: preparing.xml:830 -#, no-c-format -msgid "" -"You can find information about your current partition setup by using a " -"partitioning tool for your current operating system<phrase arch=\"i386\">, " -"such as fdisk or PartitionMagic</phrase><phrase arch=\"powerpc\">, such as " -"Drive Setup, HD Toolkit, or MacTools</phrase><phrase arch=\"m68k\">, such as " -"HD SC Setup, HDToolBox, or SCSITool</phrase><phrase arch=\"s390\">, such as " -"the VM diskmap</phrase>. Partitioning tools always provide a way to show " -"existing partitions without making changes." -msgstr "" - -#. Tag: para -#: preparing.xml:840 -#, no-c-format -msgid "" -"In general, changing a partition with a file system already on it will " -"destroy any information there. Thus you should always make backups before " -"doing any repartitioning. Using the analogy of the house, you would probably " -"want to move all the furniture out of the way before moving a wall or you " -"risk destroying it." -msgstr "" - -#. Tag: emphasis -#: preparing.xml:850 -#, no-c-format -msgid "FIXME: write about HP-UX disks?" -msgstr "" - -#. Tag: para -#: preparing.xml:852 -#, no-c-format -msgid "" -"If your computer has more than one hard disk, you may want to dedicate one " -"of the hard disks completely to Debian. If so, you don't need to partition " -"that disk before booting the installation system; the installer's included " -"partitioning program can handle the job nicely." -msgstr "" - -#. Tag: para -#: preparing.xml:859 -#, no-c-format -msgid "" -"If your machine has only one hard disk, and you would like to completely " -"replace the current operating system with &debian;, you also can wait to " -"partition as part of the installation process (<xref linkend=\"partman\"/>), " -"after you have booted the installation system. However this only works if " -"you plan to boot the installer system from tapes, CD-ROM or files on a " -"connected machine. Consider: if you boot from files placed on the hard disk, " -"and then partition that same hard disk within the installation system, thus " -"erasing the boot files, you'd better hope the installation is successful the " -"first time around. At the least in this case, you should have some alternate " -"means of reviving your machine like the original system's installation tapes " -"or CDs." -msgstr "" - -#. Tag: para -#: preparing.xml:874 -#, no-c-format -msgid "" -"If your machine already has multiple partitions, and enough space can be " -"provided by deleting and replacing one or more of them, then you too can " -"wait and use the Debian installer's partitioning program. You should still " -"read through the material below, because there may be special circumstances " -"like the order of the existing partitions within the partition map, that " -"force you to partition before installing anyway." -msgstr "" - -#. Tag: para -#: preparing.xml:884 -#, no-c-format -msgid "" -"If your machine has a FAT or NTFS filesystem, as used by DOS and Windows, " -"you can wait and use Debian installer's partitioning program to resize the " -"filesystem." -msgstr "" - -#. Tag: para -#: preparing.xml:890 -#, no-c-format -msgid "" -"If none of the above apply, you'll need to partition your hard disk before " -"starting the installation to create partition-able space for Debian. If some " -"of the partitions will be owned by other operating systems, you should " -"create those partitions using native operating system partitioning programs. " -"We recommend that you do <emphasis>not</emphasis> attempt to create " -"partitions for &debian; using another operating system's tools. Instead, you " -"should just create the native operating system's partitions you will want to " -"retain." -msgstr "" - -#. Tag: para -#: preparing.xml:902 -#, no-c-format -msgid "" -"If you are going to install more than one operating system on the same " -"machine, you should install all other system(s) before proceeding with Linux " -"installation. Windows and other OS installations may destroy your ability to " -"start Linux, or encourage you to reformat non-native partitions." -msgstr "" - -#. Tag: para -#: preparing.xml:910 -#, no-c-format -msgid "" -"You can recover from these actions or avoid them, but installing the native " -"system first saves you trouble." -msgstr "" - -#. Tag: para -#: preparing.xml:915 -#, no-c-format -msgid "" -"In order for OpenFirmware to automatically boot &debian; the Linux " -"partitions should appear before all other partitions on the disk, especially " -"MacOS boot partitions. This should be kept in mind when pre-partitioning; " -"you should create a Linux placeholder partition to come <emphasis>before</" -"emphasis> the other bootable partitions on the disk. (The small partitions " -"dedicated to Apple disk drivers are not bootable.) You can delete the " -"placeholder with the Linux partition tools later during the actual install, " -"and replace it with Linux partitions." -msgstr "" - -#. Tag: para -#: preparing.xml:927 -#, no-c-format -msgid "" -"If you currently have one hard disk with one partition (a common setup for " -"desktop computers), and you want to multi-boot the native operating system " -"and Debian, you will need to:" -msgstr "" - -#. Tag: para -#: preparing.xml:934 -#, no-c-format -msgid "Back up everything on the computer." -msgstr "" - -#. Tag: para -#: preparing.xml:939 -#, no-c-format -msgid "" -"Boot from the native operating system installer media such as CD-ROM or " -"tapes. <phrase arch=\"powerpc\">When booting from a MacOS CD, hold the " -"<keycap>c</keycap> key while booting to force the CD to become the active " -"MacOS system.</phrase>" -msgstr "" - -#. Tag: para -#: preparing.xml:949 -#, no-c-format -msgid "" -"Use the native partitioning tools to create native system partition(s). " -"Leave either a place holder partition or free space for &debian;." -msgstr "" - -#. Tag: para -#: preparing.xml:956 -#, no-c-format -msgid "Install the native operating system on its new partition." -msgstr "" - -#. Tag: para -#: preparing.xml:961 -#, no-c-format -msgid "" -"Boot back into the native system to verify everything's OK, and to download " -"the Debian installer boot files." -msgstr "" - -#. Tag: para -#: preparing.xml:967 -#, no-c-format -msgid "Boot the Debian installer to continue installing Debian." -msgstr "" - -#. Tag: title -#: preparing.xml:981 -#, no-c-format -msgid "Partitioning in Tru64 UNIX" -msgstr "" - -#. Tag: para -#: preparing.xml:982 -#, no-c-format -msgid "" -"Tru64 UNIX, formerly known as Digital UNIX, which is in turn formerly known " -"as OSF/1, uses the partitioning scheme similar to the BSD <quote>disk label</" -"quote>, which allows for up to eight partitions per disk drive. The " -"partitions are numbered <quote>1</quote> through to <quote>8</quote> in " -"Linux and <quote>lettered</quote> <quote>a</quote> through to <quote>h</" -"quote> in UNIX. Linux kernels 2.2 and higher always correspond <quote>1</" -"quote> to <quote>a</quote>, <quote>2</quote> to <quote>b</quote> and so on. " -"For example, <filename>rz0e</filename> in Tru64 UNIX would most likely be " -"called <filename>sda5</filename> in Linux." -msgstr "" - -#. Tag: para -#: preparing.xml:994 -#, no-c-format -msgid "" -"Partitions in a Tru64 disk label may overlap. Moreover, if this disk will be " -"used from Tru64, the <quote>c</quote> partition is required to span the " -"entire disk (thus overlapping all other non-empty partitions). Under Linux " -"this makes <filename>sda3</filename> identical to <filename>sda</filename> " -"(<filename>sdb3</filename> to <filename>sdb</filename>, if present, and so " -"on). However, the partman partitioning tool used by &d-i; cannot handle " -"overlapping partitions at present. As a result, it is currently not " -"recommended to share disks between Tru64 and Debian. Partitions on Tru64 " -"disks can be mounted under Debian after installation has been completed." -msgstr "" - -#. Tag: para -#: preparing.xml:1007 -#, no-c-format -msgid "" -"Another conventional requirement is for the <quote>a</quote> partition to " -"start from the beginning of the disk, so that it always includes the boot " -"block with the disk label. If you intend to boot Debian from that disk, you " -"need to size it at least 2MB to fit aboot and perhaps a kernel. Note that " -"this partition is only required for compatibility; you must not put a file " -"system onto it, or you'll destroy data." -msgstr "" - -#. Tag: para -#: preparing.xml:1016 -#, no-c-format -msgid "" -"It is possible, and indeed quite reasonable, to share a swap partition " -"between UNIX and Linux. In this case it will be needed to do a " -"<command>mkswap</command> on that partition every time the system is " -"rebooted from UNIX into Linux, as UNIX will damage the swap signature. You " -"may want to run <command>mkswap</command> from the Linux start-up scripts " -"before adding swap space with <command>swapon -a</command>." -msgstr "" - -#. Tag: para -#: preparing.xml:1025 -#, no-c-format -msgid "" -"If you want to mount UNIX partitions under Linux, note that Digital UNIX can " -"use two different file system types, UFS and AdvFS, of which Linux only " -"understands the former." -msgstr "" - -#. Tag: title -#: preparing.xml:1034 -#, no-c-format -msgid "Partitioning in Windows NT" -msgstr "" - -#. Tag: para -#: preparing.xml:1036 -#, no-c-format -msgid "" -"Windows NT uses the PC-style partition table. If you are manipulating " -"existing FAT or NTFS partitions, it is recommended that you use the native " -"Windows NT tools (or, more conveniently, you can also repartition your disk " -"from the AlphaBIOS setup menu). Otherwise, it is not really necessary to " -"partition from Windows; the Linux partitioning tools will generally do a " -"better job. Note that when you run NT, the Disk Administrator may offer you " -"to write a <quote>harmless signature</quote> on non-Windows disks if you " -"have any. <emphasis>Never</emphasis> let it do that, as this signature will " -"destroy the partition information." -msgstr "" - -#. Tag: para -#: preparing.xml:1049 -#, no-c-format -msgid "" -"If you plan to boot Linux from an ARC/AlphaBIOS/ARCSBIOS console, you will " -"need a (small) FAT partition for MILO. 5 MB is quite sufficient. If Windows " -"NT is installed, its 6 MB bootstrap partition can be employed for this " -"purpose. Debian &releasename; does not support installing MILO. If you " -"already have MILO installed on your system, or install MILO from other " -"media, Debian can still be booted from ARC." -msgstr "" - -#. Tag: title -#: preparing.xml:1066 -#, no-c-format -msgid "Partitioning From DOS or Windows" -msgstr "" - -#. Tag: para -#: preparing.xml:1067 -#, no-c-format -msgid "" -"If you are manipulating existing FAT or NTFS partitions, it is recommended " -"that you either use the scheme below or native Windows or DOS tools. " -"Otherwise, it is not really necessary to partition from DOS or Windows; the " -"Linux partitioning tools will generally do a better job." -msgstr "" - -#. Tag: para -#: preparing.xml:1075 -#, no-c-format -msgid "" -"But if you have a large IDE disk, and are using neither LBA addressing, " -"overlay drivers (sometimes provided by hard disk manufacturers), nor a new " -"(post 1998) BIOS that supports large disk access extensions, then you must " -"locate your Debian boot partition carefully. In this case, you will have to " -"put the boot partition into the first 1024 cylinders of your hard drive " -"(usually around 524 megabytes, without BIOS translation). This may require " -"that you move an existing FAT or NTFS partition." -msgstr "" - -#. Tag: title -#: preparing.xml:1089 -#, no-c-format -msgid "Lossless Repartitioning When Starting From DOS, Win-32 or OS/2" -msgstr "" - -#. Tag: para -#: preparing.xml:1092 -#, no-c-format -msgid "" -"One of the most common installations is onto a system that already contains " -"DOS (including Windows 3.1), Win32 (such as Windows 95, 98, Me, NT, 2000, " -"XP), or OS/2, and it is desired to put Debian onto the same disk without " -"destroying the previous system. Note that the installer supports resizing of " -"FAT and NTFS filesystems as used by DOS and Windows. Simply start the " -"installer, select the option to <menuchoice> <guimenuitem>Manually edit " -"partition table</guimenuitem> </menuchoice>, select the partition to resize, " -"and specify its new size. So in most cases you should not need to use the " -"method described below." -msgstr "" - -#. Tag: para -#: preparing.xml:1104 -#, no-c-format -msgid "" -"Before going any further, you should have decided how you will be dividing " -"up the disk. The method in this section will only split a partition into two " -"pieces. One will contain the original OS and the other will be used for " -"Debian. During the installation of Debian, you will be given the opportunity " -"to use the Debian portion of the disk as you see fit, i.e., as swap or as a " -"file system." -msgstr "" - -#. Tag: para -#: preparing.xml:1113 -#, no-c-format -msgid "" -"The idea is to move all the data on the partition to the beginning, before " -"changing the partition information, so that nothing will be lost. It is " -"important that you do as little as possible between the data movement and " -"repartitioning to minimize the chance of a file being written near the end " -"of the partition as this will decrease the amount of space you can take from " -"the partition." -msgstr "" - -#. Tag: para -#: preparing.xml:1122 -#, no-c-format -msgid "" -"The first thing needed is a copy of <command>fips</command> which is " -"available in the <filename>tools/</filename> directory on your nearest " -"Debian mirror. Unzip the archive and copy the files <filename>RESTORRB.EXE</" -"filename>, <filename>FIPS.EXE</filename> and <filename>ERRORS.TXT</filename> " -"to a bootable floppy. A bootable floppy can be created using the command " -"<filename>sys a:</filename> under DOS. <command>fips</command> comes with " -"very good documentation which you may want to read. You will definitely need " -"to read the documentation if you use a disk compression driver or a disk " -"manager. Create the disk and read the documentation <emphasis>before</" -"emphasis> you defragment the disk." -msgstr "" - -#. Tag: para -#: preparing.xml:1135 -#, no-c-format -msgid "" -"The next thing needed is to move all the data to the beginning of the " -"partition. <command>defrag</command>, which comes standard with DOS 6.0 and " -"later, can easily do the job. See the <command>fips</command> documentation " -"for a list of other software that may do the trick. Note that if you have " -"Windows 9x, you must run <command>defrag</command> from there, since DOS " -"doesn't understand VFAT, which is used to support for long filenames, used " -"in Windows 95 and higher." -msgstr "" - -#. Tag: para -#: preparing.xml:1145 -#, no-c-format -msgid "" -"After running the defragmenter (which can take a while on a large disk), " -"reboot with the <command>fips</command> disk you created in the floppy " -"drive. Simply type <filename>a:\\fips</filename> and follow the directions." -msgstr "" - -#. Tag: para -#: preparing.xml:1151 -#, no-c-format -msgid "" -"Note that there are many other partition managers out there, in case " -"<command>fips</command> doesn't do the trick for you." -msgstr "" - -#. Tag: title -#: preparing.xml:1159 -#, no-c-format -msgid "Partitioning for DOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1161 -#, no-c-format -msgid "" -"If you are partitioning for DOS drives, or changing the size of DOS " -"partitions, using Linux tools, many people experience problems working with " -"the resulting FAT partitions. For instance, some have reported slow " -"performance, consistent problems with <command>scandisk</command>, or other " -"weird errors in DOS or Windows." -msgstr "" - -#. Tag: para -#: preparing.xml:1169 -#, no-c-format -msgid "" -"Apparently, whenever you create or resize a partition for DOS use, it's a " -"good idea to fill the first few sectors with zeros. Do this prior to running " -"DOS's <command>format</command> command, from Linux:" -msgstr "" - -#. Tag: screen -#: preparing.xml:1175 -#, no-c-format -msgid "# dd if=/dev/zero of=/dev/hdXX bs=512 count=4" -msgstr "" - -#. Tag: title -#: preparing.xml:1186 -#, no-c-format -msgid "Partitioning in AmigaOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1187 -#, no-c-format -msgid "" -"If you are running AmigaOS, you can use the <command>HDToolBox</command> " -"program to adjust your native partitions prior to installation." -msgstr "" - -#. Tag: title -#: preparing.xml:1195 -#, no-c-format -msgid "Partitioning in Atari TOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1196 -#, no-c-format -msgid "" -"Atari partition IDs are three ASCII characters, use <quote>LNX</quote> for " -"data and <quote>SWP</quote> for swap partitions. If using the low memory " -"installation method, a small Minix partition is also needed (about 2 MB), " -"for which the partition ID is <quote>MNX</quote>. Failure to set the " -"appropriate partition IDs not only prevents the Debian installation process " -"from recognizing the partitions, but also results in TOS attempting to use " -"the Linux partitions, which confuses the hard disk driver and renders the " -"whole disk inaccessible." -msgstr "" - -#. Tag: para -#: preparing.xml:1207 -#, no-c-format -msgid "" -"There are a multitude of third party partitioning tools available (the Atari " -"<command>harddisk</command> utility doesn't permit changing the partition " -"ID); this manual cannot give detailed descriptions for all of them. The " -"following description covers <command>SCSITool</command> (from Hard+Soft " -"GmBH)." -msgstr "" - -#. Tag: para -#: preparing.xml:1216 -#, no-c-format -msgid "" -"Start <command>SCSITool</command> and select the disk you want to partition " -"(<guimenu>Disk</guimenu> menu, item <guimenuitem>select</guimenuitem>)." -msgstr "" - -#. Tag: para -#: preparing.xml:1222 -#, no-c-format -msgid "" -"From the <guimenu>Partition</guimenu> menu, select either <guimenuitem>New</" -"guimenuitem> to add new partitions or change the existing partition sizes, " -"or <guimenuitem>Change</guimenuitem> to change one specific partition. " -"Unless you have already created partitions with the right sizes and only " -"want to change the partition ID, <guimenuitem>New</guimenuitem> is probably " -"the best choice." -msgstr "" - -#. Tag: para -#: preparing.xml:1232 -#, no-c-format -msgid "" -"For the <guimenuitem>New</guimenuitem> choice, select <guilabel>existing</" -"guilabel> in the dialog box prompting the initial settings. The next window " -"shows a list of existing partitions which you can adjust using the scroll " -"buttons, or by clicking in the bar graphs. The first column in the partition " -"list is the partition type; just click on the text field to edit it. When " -"you are finished changing partition settings, save the changes by leaving " -"the window with the <guibutton>OK</guibutton> button." -msgstr "" - -#. Tag: para -#: preparing.xml:1244 -#, no-c-format -msgid "" -"For the <guimenuitem>Change</guimenuitem> option, select the partition to " -"change in the selection list, and select <guilabel>other systems</guilabel> " -"in the dialog box. The next window lists detailed information about the " -"location of this partition, and lets you change the partition ID. Save " -"changes by leaving the window with the <guibutton>OK</guibutton> button." -msgstr "" - -#. Tag: para -#: preparing.xml:1254 -#, no-c-format -msgid "" -"Write down the Linux names for each of the partitions you created or changed " -"for use with Linux — see <xref linkend=\"device-names\"/>." -msgstr "" - -#. Tag: para -#: preparing.xml:1260 -#, no-c-format -msgid "" -"Quit <command>SCSITool</command> using the <guimenuitem>Quit</guimenuitem> " -"item from the <guimenu>File</guimenu> menu. The computer will reboot to make " -"sure the changed partition table is used by TOS. If you changed any TOS/GEM " -"partitions, they will be invalidated and have to be reinitialized (we told " -"you to back up everything on the disk, didn't we?)." -msgstr "" - -#. Tag: para -#: preparing.xml:1272 -#, no-c-format -msgid "" -"There is a partitioning tool for Linux/m68k called <command>atari-fdisk</" -"command> in the installation system, but for now we recommend you partition " -"your disk using a TOS partition editor or some disk tool. If your partition " -"editor doesn't have an option to edit the partition type, you can do this " -"crucial step at a later stage (from the booted temporary install RAMdisk). " -"<command>SCSITool</command> is only one of the partition editors we know of " -"which supports selection of arbitrary partition types. There may be others; " -"select the tool that suits your needs." -msgstr "" - -#. Tag: title -#: preparing.xml:1287 -#, no-c-format -msgid "Partitioning in MacOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1288 -#, no-c-format -msgid "" -"Partitioning tools for Macintosh tested include <command>pdisk</command>, " -"<command>HD SC Setup</command> 7.3.5 (Apple), <command>HDT</command> 1.8 " -"(FWB), <command>SilverLining</command> (LaCie), and <command>DiskTool</" -"command> (Tim Endres, GPL). Full versions are required for <command>HDT</" -"command> and <command>SilverLining</command>. The Apple tool requires a " -"patch in order to recognize third-party disks (a description on how to patch " -"<command>HD SC Setup</command> using <command>ResEdit</command> can be found " -"at <ulink url=\"http://www.euronet.nl/users/ernstoud/patch.html\"></ulink>)." -msgstr "" - -#. Tag: para -#: preparing.xml:1299 -#, no-c-format -msgid "" -"For IDE based Macs, you need to use <command>Apple Drive Setup</command> to " -"create empty space for the Linux partitions, and complete the partitioning " -"under Linux, or use the MacOS version of pdisk available from the MkLinux " -"FTP server." -msgstr "" - -#. Tag: title -#: preparing.xml:1315 -#, no-c-format -msgid "Partitioning from SunOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1317 -#, no-c-format -msgid "" -"It's perfectly fine to partition from SunOS; in fact, if you intend to run " -"both SunOS and Debian on the same machine, it is recommended that you " -"partition using SunOS prior to installing Debian. The Linux kernel " -"understands Sun disk labels, so there are no problems there. Just make sure " -"you leave room for the Debian root partition within the first 1GB area of " -"the boot disk. You can also place the kernel image on a UFS partition if " -"that is easier than putting the root partition there. SILO supports booting " -"Linux and SunOS from either EXT2 (Linux), UFS (SunOS), romfs and iso9660 " -"(CDROM) partitions." -msgstr "" - -#. Tag: title -#: preparing.xml:1332 -#, no-c-format -msgid "Partitioning from Linux or another OS" -msgstr "" - -#. Tag: para -#: preparing.xml:1334 -#, no-c-format -msgid "" -"Whatever system you are using to partition, make sure you create a " -"<quote>Sun disk label</quote> on your boot disk. This is the only kind of " -"partition scheme that the OpenBoot PROM understands, and so it's the only " -"scheme from which you can boot. In <command>fdisk</command>, the <keycap>s</" -"keycap> key is used to create Sun disk labels. You only need to do this on " -"drives that do not already have a Sun disk label. If you are using a drive " -"that was previously formatted using a PC (or other architecture) you must " -"create a new disk label, or problems with the disk geometry will most likely " -"occur." -msgstr "" - -#. Tag: para -#: preparing.xml:1346 -#, no-c-format -msgid "" -"You will probably be using <command>SILO</command> as your boot loader (the " -"small program which runs the operating system kernel). <command>SILO</" -"command> has certain requirements for partition sizes and location; see " -"<xref linkend=\"partitioning\"/>." -msgstr "" - -#. Tag: title -#: preparing.xml:1361 -#, no-c-format -msgid "MacOS/OSX Partitioning" -msgstr "" - -#. Tag: para -#: preparing.xml:1363 -#, no-c-format -msgid "" -"The <application>Apple Drive Setup</application> application can be found in " -"the <filename>Utilities</filename> folder on the MacOS CD. It will not " -"adjust existing partitions; it is limited to partitioning the entire disk at " -"once. The disk driver partitions don't show up in <application>Drive Setup</" -"application>." -msgstr "" - -#. Tag: para -#: preparing.xml:1370 -#, no-c-format -msgid "" -"Remember to create a placeholder partition for GNU/Linux, preferably " -"positioned first in the disk layout. it doesn't matter what type it is, it " -"will be deleted and replaced later inside the &debian; installer." -msgstr "" - -#. Tag: para -#: preparing.xml:1376 -#, no-c-format -msgid "" -"If you are planning to install both MacOS 9 and OS X, it is best to create " -"separate partitions for OS 9 and OS X. If they are installed on the same " -"partition, <application>Startup Disk</application> (and reboot) must be used " -"to select between the two; the choice between the two systems can't be made " -"at boot time. With separate partitions, separate options for OS 9 and OS X " -"will appear when holding the <keycap>option</keycap> key at boot time, and " -"separate options can be installed in the <application>yaboot</application> " -"boot menu as well. Also, Startup Disk will de-bless all other mountable " -"partitions, which can affect GNU/Linux booting. Both OS 9 and OS X " -"partitions will be accessible from either OS 9 or OS X." -msgstr "" - -#. Tag: para -#: preparing.xml:1389 -#, no-c-format -msgid "" -"GNU/Linux is unable to access information on UFS partitions, but does " -"support HFS+ (aka MacOS Extended) partitions. OS X requires one of these two " -"types for its boot partition. MacOS 9 can be installed on either HFS (aka " -"MacOS Standard) or HFS+. To share information between the MacOS and GNU/" -"Linux systems, an exchange partition is handy. HFS, HFS+ and MS-DOS FAT " -"partitions are supported by both MacOS and Linux." -msgstr "" - -#. Tag: title -#: preparing.xml:1409 -#, no-c-format -msgid "Pre-Installation Hardware and Operating System Setup" -msgstr "" - -#. Tag: para -#: preparing.xml:1410 -#, no-c-format -msgid "" -"This section will walk you through pre-installation hardware setup, if any, " -"that you will need to do prior to installing Debian. Generally, this " -"involves checking and possibly changing firmware settings for your system. " -"The <quote>firmware</quote> is the core software used by the hardware; it is " -"most critically invoked during the bootstrap process (after power-up). Known " -"hardware issues affecting the reliability of &debian; on your system are " -"also highlighted." -msgstr "" - -#. Tag: title -#: preparing.xml:1427 -#, no-c-format -msgid "Invoking the BIOS Set-Up Menu" -msgstr "" - -#. Tag: para -#: preparing.xml:1429 -#, no-c-format -msgid "" -"BIOS provides the basic functions needed to boot your machine to allow your " -"operating system to access your hardware. Your system probably provides a " -"BIOS set-up menu, which is used to configure the BIOS. Before installing, " -"you <emphasis>must</emphasis> ensure that your BIOS is setup correctly; not " -"doing so can lead to intermittent crashes or an inability to install Debian." -msgstr "" - -#. Tag: para -#: preparing.xml:1438 -#, no-c-format -msgid "" -"The rest of this section is lifted from the <ulink url=\"&url-pc-hw-faq;\"></" -"ulink>, answering the question, <quote>How do I enter the CMOS configuration " -"menu?</quote>. How you access the BIOS (or <quote>CMOS</quote>) " -"configuration menu depends on who wrote your BIOS software:" -msgstr "" - -#. Tag: term -#: preparing.xml:1452 -#, no-c-format -msgid "AMI BIOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1453 -#, no-c-format -msgid "<keycap>Delete</keycap> key during the POST (power on self test)" -msgstr "" - -#. Tag: term -#: preparing.xml:1461 -#, no-c-format -msgid "Award BIOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1462 -#, no-c-format -msgid "" -"<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </" -"keycombo>, or <keycap>Delete</keycap> key during the POST" -msgstr "" - -#. Tag: term -#: preparing.xml:1471 -#, no-c-format -msgid "DTK BIOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1472 -#, no-c-format -msgid "<keycap>Esc</keycap> key during the POST" -msgstr "" - -#. Tag: term -#: preparing.xml:1479 -#, no-c-format -msgid "IBM PS/2 BIOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1480 -#, no-c-format -msgid "" -"<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Insert</keycap> " -"</keycombo> after <keycombo> <keycap>Ctrl</keycap><keycap>Alt</" -"keycap><keycap>Delete</keycap> </keycombo>" -msgstr "" - -#. Tag: term -#: preparing.xml:1494 -#, no-c-format -msgid "Phoenix BIOS" -msgstr "" - -#. Tag: para -#: preparing.xml:1495 -#, no-c-format -msgid "" -"<keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>Esc</keycap> </" -"keycombo> or <keycombo> <keycap>Ctrl</keycap><keycap>Alt</keycap><keycap>S</" -"keycap> </keycombo> or <keycap>F1</keycap>" -msgstr "" - -#. Tag: para -#: preparing.xml:1511 -#, no-c-format -msgid "" -"Information on invoking other BIOS routines can be found in <ulink url=" -"\"&url-invoking-bios-info;\"></ulink>." -msgstr "" - -#. Tag: para -#: preparing.xml:1516 -#, no-c-format -msgid "" -"Some &arch-title; machines don't have a CMOS configuration menu in the BIOS. " -"They require a software CMOS setup program. If you don't have the " -"Installation and/or Diagnostics diskette for your machine, you can try using " -"a shareware/freeware program. Try looking in <ulink url=\"&url-simtel;\"></" -"ulink>." -msgstr "" - -#. Tag: title -#: preparing.xml:1527 preparing.xml:1870 -#, no-c-format -msgid "Boot Device Selection" -msgstr "" - -#. Tag: para -#: preparing.xml:1529 -#, no-c-format -msgid "" -"Many BIOS set-up menus allow you to select the devices that will be used to " -"bootstrap the system. Set this to look for a bootable operating system on " -"<filename>A:</filename> (the first floppy disk), then optionally the first " -"CD-ROM device (possibly appearing as <filename>D:</filename> or <filename>E:" -"</filename>), and then from <filename>C:</filename> (the first hard disk). " -"This setting enables you to boot from either a floppy disk or a CD-ROM, " -"which are the two most common boot devices used to install Debian." -msgstr "" - -#. Tag: para -#: preparing.xml:1540 -#, no-c-format -msgid "" -"If you have a newer SCSI controller and you have a CD-ROM device attached to " -"it, you are usually able to boot from the CD-ROM. All you have to do is " -"enable booting from a CD-ROM in the SCSI-BIOS of your controller." -msgstr "" - -#. Tag: para -#: preparing.xml:1547 -#, no-c-format -msgid "" -"Other popular option is to boot from a USB storage (also called USB memory " -"stick or USB key). Some BIOSes can boot USB storage directly, and some " -"cannot. You may need to configure your BIOS to boot from a <quote>Removable " -"drive</quote> or even a <quote>USB-ZIP</quote> to get it to boot from the " -"USB device." -msgstr "" - -#. Tag: para -#: preparing.xml:1555 -#, no-c-format -msgid "" -"Here are some details about how to set the boot order. Remember to reset the " -"boot order after Linux is installed, so that you restart your machine from " -"the hard drive." -msgstr "" - -#. Tag: title -#: preparing.xml:1564 -#, no-c-format -msgid "Changing the Boot Order on IDE Computers" -msgstr "" - -#. Tag: para -#: preparing.xml:1567 -#, no-c-format -msgid "" -"As your computer starts, press the keys to enter the BIOS utility. Often, it " -"is the <keycap>Delete</keycap> key. However, consult the hardware " -"documentation for the exact keystrokes." -msgstr "" - -#. Tag: para -#: preparing.xml:1574 -#, no-c-format -msgid "" -"Find the boot sequence in the setup utility. Its location depends on your " -"BIOS, but you are looking for a field that lists drives." -msgstr "" - -#. Tag: para -#: preparing.xml:1579 -#, no-c-format -msgid "Common entries on IDE machines are C, A, cdrom or A, C, cdrom." -msgstr "" - -#. Tag: para -#: preparing.xml:1584 -#, no-c-format -msgid "C is the hard drive, and A is the floppy drive." -msgstr "" - -#. Tag: para -#: preparing.xml:1590 -#, no-c-format -msgid "" -"Change the boot sequence setting so that the CD-ROM or the floppy is first. " -"Usually, the <keycap>Page Up</keycap> or <keycap>Page Down</keycap> keys " -"cycle through the possible choices." -msgstr "" - -#. Tag: para -#: preparing.xml:1598 -#, no-c-format -msgid "" -"Save your changes. Instructions on the screen tell you how to save the " -"changes on your computer." -msgstr "" - -#. Tag: title -#: preparing.xml:1608 -#, no-c-format -msgid "Changing the Boot Order on SCSI Computers" -msgstr "" - -#. Tag: para -#: preparing.xml:1612 -#, no-c-format -msgid "" -"As your computer starts, press the keys to enter the SCSI setup utility." -msgstr "" - -#. Tag: para -#: preparing.xml:1617 -#, no-c-format -msgid "" -"You can start the SCSI setup utility after the memory check and the message " -"about how to start the BIOS utility displays when you start your computer." -msgstr "" - -#. Tag: para -#: preparing.xml:1623 -#, no-c-format -msgid "" -"The keystrokes you need depend on the utility. Often, it is " -"<keycombo><keycap>Ctrl</keycap><keycap>F2</keycap></keycombo>. However, " -"consult your hardware documentation for the exact keystrokes." -msgstr "" - -#. Tag: para -#: preparing.xml:1631 -#, no-c-format -msgid "Find the utility for changing the boot order." -msgstr "" - -#. Tag: para -#: preparing.xml:1636 -#, no-c-format -msgid "" -"Set the utility so that the SCSI ID of the CD drive is first on the list." -msgstr "" - -#. Tag: para -#: preparing.xml:1642 -#, no-c-format -msgid "" -"Save your changes. Instructions on the screen tell you how to save the " -"changes on your computer. Often, you must press <keycap>F10</keycap>." -msgstr "" - -#. Tag: title -#: preparing.xml:1656 -#, no-c-format -msgid "Miscellaneous BIOS Settings" -msgstr "" - -#. Tag: title -#: preparing.xml:1658 -#, no-c-format -msgid "CD-ROM Settings" -msgstr "" - -#. Tag: para -#: preparing.xml:1659 -#, no-c-format -msgid "" -"Some BIOS systems (such as Award BIOS) allow you to automatically set the CD " -"speed. You should avoid that, and instead set it to, say, the lowest speed. " -"If you get <userinput>seek failed</userinput> error messages, this may be " -"your problem." -msgstr "" - -#. Tag: title -#: preparing.xml:1669 -#, no-c-format -msgid "Extended vs. Expanded Memory" -msgstr "" - -#. Tag: para -#: preparing.xml:1670 -#, no-c-format -msgid "" -"If your system provides both ex<emphasis>ten</emphasis>ded and " -"ex<emphasis>pan</emphasis>ded memory, set it so that there is as much " -"extended and as little expanded memory as possible. Linux requires extended " -"memory and cannot use expanded memory." -msgstr "" - -#. Tag: title -#: preparing.xml:1680 -#, no-c-format -msgid "Virus Protection" -msgstr "" - -#. Tag: para -#: preparing.xml:1681 -#, no-c-format -msgid "" -"Disable any virus-warning features your BIOS may provide. If you have a " -"virus-protection board or other special hardware, make sure it is disabled " -"or physically removed while running GNU/Linux. These aren't compatible with " -"GNU/Linux; moreover, due to the file system permissions and protected memory " -"of the Linux kernel, viruses are almost unheard of<footnote> <para> After " -"installation you can enable Boot Sector protection if you want. This offers " -"no additional security in Linux but if you also run Windows it may prevent a " -"catastrophe. There is no need to tamper with the Master Boot Record (MBR) " -"after the boot manager has been set up. </para> </footnote>." -msgstr "" - -#. Tag: title -#: preparing.xml:1702 -#, no-c-format -msgid "Shadow RAM" -msgstr "" - -#. Tag: para -#: preparing.xml:1703 -#, no-c-format -msgid "" -"Your motherboard may provide <emphasis>shadow RAM</emphasis> or BIOS " -"caching. You may see settings for <quote>Video BIOS Shadow</quote>, " -"<quote>C800-CBFF Shadow</quote>, etc. <emphasis>Disable</emphasis> all " -"shadow RAM. Shadow RAM is used to accelerate access to the ROMs on your " -"motherboard and on some of the controller cards. Linux does not use these " -"ROMs once it has booted because it provides its own faster 32-bit software " -"in place of the 16-bit programs in the ROMs. Disabling the shadow RAM may " -"make some of it available for programs to use as normal memory. Leaving the " -"shadow RAM enabled may interfere with Linux access to hardware devices." -msgstr "" - -#. Tag: title -#: preparing.xml:1720 -#, no-c-format -msgid "Memory Hole" -msgstr "" - -#. Tag: para -#: preparing.xml:1721 -#, no-c-format -msgid "" -"If your BIOS offers something like <quote>15–16 MB Memory Hole</" -"quote>, please disable that. Linux expects to find memory there if you have " -"that much RAM." -msgstr "" - -#. Tag: para -#: preparing.xml:1727 -#, no-c-format -msgid "" -"We have a report of an Intel Endeavor motherboard on which there is an " -"option called <quote>LFB</quote> or <quote>Linear Frame Buffer</quote>. This " -"had two settings: <quote>Disabled</quote> and <quote>1 Megabyte</quote>. Set " -"it to <quote>1 Megabyte</quote>. When disabled, the installation floppy was " -"not read correctly, and the system eventually crashed. At this writing we " -"don't understand what's going on with this particular device — it just " -"worked with that setting and not without it." -msgstr "" - -#. Tag: title -#: preparing.xml:1743 -#, no-c-format -msgid "Advanced Power Management" -msgstr "" - -#. Tag: para -#: preparing.xml:1744 -#, no-c-format -msgid "" -"If your motherboard provides Advanced Power Management (APM), configure it " -"so that power management is controlled by APM. Disable the doze, standby, " -"suspend, nap, and sleep modes, and disable the hard disk's power-down timer. " -"Linux can take over control of these modes, and can do a better job of power-" -"management than the BIOS." -msgstr "" - -#. Tag: title -#: preparing.xml:1762 -#, no-c-format -msgid "Firmware Revisions and Existing OS Setup" -msgstr "" - -#. Tag: para -#: preparing.xml:1764 -#, no-c-format -msgid "" -"&arch-title; machines are generally self-configuring and do not require " -"firmware configuration. However, you should make sure that you have the " -"appropriate ROM and system patches. On the Macintosh, MacOS version >= 7.1 " -"is recommended because version 7.0.1 contains a bug in the video drivers " -"preventing the boot loader from deactivating the video interrupts, resulting " -"in a boot hang. On the BVM VMEbus systems you should make sure you are using " -"BVMBug revision G or higher boot ROMs. The BVMBug boot ROMs do not come as " -"standard on the BVM systems but are available from BVM on request free of " -"charge." -msgstr "" - -#. Tag: title -#: preparing.xml:1787 -#, no-c-format -msgid "Invoking OpenFirmware" -msgstr "" - -#. Tag: para -#: preparing.xml:1788 -#, no-c-format -msgid "" -"There is normally no need to set up the BIOS (called OpenFirmware) on &arch-" -"title; systems. PReP and CHRP are equipped with OpenFirmware, but " -"unfortunately, the means you use to invoke it vary from manufacturer to " -"manufacturer. You'll have to consult the hardware documentation which came " -"with your machine." -msgstr "" - -#. Tag: para -#: preparing.xml:1796 -#, no-c-format -msgid "" -"On &arch-title; Macintoshes, you invoke OpenFirmware with " -"<keycombo><keycap>Command</keycap> <keycap>option</keycap> <keycap>O</" -"keycap> <keycap>F</keycap></keycombo> while booting. Generally it will check " -"for these keystrokes after the chime, but the exact timing varies from model " -"to model. See <ulink url=\"&url-netbsd-powerpc-faq;\"></ulink> for more " -"hints." -msgstr "" - -#. Tag: para -#: preparing.xml:1805 -#, no-c-format -msgid "" -"The OpenFirmware prompt looks like this: <informalexample><screen>\n" -"ok\n" -"0 >\n" -"</screen></informalexample> Note that on older model &arch-title; Macs, the " -"default and sometimes hardwired I/O for OpenFirmware user interaction is " -"through the serial (modem) port. If you invoke OpenFirmware on one of these " -"machines, you will just see a black screen. In that case, a terminal program " -"running on another computer, connected to the modem port, is needed to " -"interact with OpenFirmware." -msgstr "" - -#. Tag: para -#: preparing.xml:1818 -#, no-c-format -msgid "" -"The OpenFirmware on OldWorld Beige G3 machines, OF versions 2.0f1 and 2.4, " -"is broken. These machines will most likely not be able to boot from the hard " -"drive unless the firmware is patched. A firmware patch is included in the " -"<application>System Disk 2.3.1</application> utility, available from Apple " -"at <ulink url=\"ftp://ftp.apple.com/developer/macosxserver/utilities/" -"SystemDisk2.3.1.smi.bin\"></ulink>. After unpacking the utility in MacOS, " -"and launching it, select the Save button to have the firmware patches " -"installed to nvram." -msgstr "" - -#. Tag: title -#: preparing.xml:1837 -#, no-c-format -msgid "Invoking OpenBoot" -msgstr "" - -#. Tag: para -#: preparing.xml:1839 -#, no-c-format -msgid "" -"OpenBoot provides the basic functions needed to boot the &arch-title; " -"architecture. This is rather similar in function to the BIOS in the x86 " -"architecture, although much nicer. The Sun boot PROMs have a built-in forth " -"interpreter which lets you do quite a number of things with your machine, " -"such as diagnostics, simple scripts, etc." -msgstr "" - -#. Tag: para -#: preparing.xml:1847 -#, no-c-format -msgid "" -"To get to the boot prompt you need to hold down the <keycap>Stop</keycap> " -"key (on older type 4 keyboards, use the <keycap>L1</keycap> key, if you have " -"a PC keyboard adapter, use the <keycap>Break</keycap> key) and press the " -"<keycap>A</keycap> key. The boot PROM will give you a prompt, either " -"<userinput>ok</userinput> or <userinput>></userinput>. It is preferred to " -"have the <userinput>ok</userinput> prompt. So if you get the old style " -"prompt, hit the <keycap>n</keycap> key to get the new style prompt." -msgstr "" - -#. Tag: para -#: preparing.xml:1859 -#, no-c-format -msgid "" -"If you are using a serial console, send a break to the machine. With " -"Minicom, use <keycap>Ctrl-A F</keycap>, with cu, hit <keycap>Enter</keycap>, " -"then type <userinput>%~break</userinput>. Consult the documentation of your " -"terminal emulator if you are using a different program." -msgstr "" - -#. Tag: para -#: preparing.xml:1872 -#, no-c-format -msgid "" -"You can use OpenBoot to boot from specific devices, and also to change your " -"default boot device. However, you need to know some details about how " -"OpenBoot names devices; it's much different from Linux device naming, " -"described in <xref linkend=\"device-names\"/>. Also, the command will vary a " -"bit, depending on what version of OpenBoot you have. More information about " -"OpenBoot can be found in the <ulink url=\"&url-openboot;\">Sun OpenBoot " -"Reference</ulink>." -msgstr "" - -#. Tag: para -#: preparing.xml:1882 -#, no-c-format -msgid "" -"Typically, with newer revisions, you can use OpenBoot device such as " -"<quote>floppy</quote>, <quote>cdrom</quote>, <quote>net</quote>, " -"<quote>disk</quote>, or <quote>disk2</quote>. These have the obvious " -"meanings; the <quote>net</quote> device is for booting from the network. " -"Additionally, the device name can specify a particular partition of a disk, " -"such as <quote>disk2:a</quote> to boot disk2, first partition. Full OpenBoot " -"device names have the form <informalexample> <screen>\n" -"<replaceable>driver-name</replaceable>@\n" -"<replaceable>unit-address</replaceable>:\n" -"<replaceable>device-arguments</replaceable>\n" -"</screen></informalexample>. In older revisions of OpenBoot, device naming " -"is a bit different: the floppy device is called <quote>/fd</quote>, and SCSI " -"disk devices are of the form <quote>sd(<replaceable>controller</" -"replaceable>, <replaceable>disk-target-id</replaceable>, <replaceable>disk-" -"lun</replaceable>)</quote>. The command <userinput>show-devs</userinput> in " -"newer OpenBoot revisions is useful for viewing the currently configured " -"devices. For full information, whatever your revision, see the <ulink url=" -"\"&url-openboot;\">Sun OpenBoot Reference</ulink>." -msgstr "" - -#. Tag: para -#: preparing.xml:1905 -#, no-c-format -msgid "" -"To boot from a specific device, use the command <userinput>boot " -"<replaceable>device</replaceable></userinput>. You can set this behavior as " -"the default using the <userinput>setenv</userinput> command. However, the " -"name of the variable to set changed between OpenBoot revisions. In OpenBoot " -"1.x, use the command <userinput>setenv boot-from <replaceable>device</" -"replaceable></userinput>. In later revisions of OpenBoot, use the command " -"<userinput>setenv boot-device <replaceable>device</replaceable></userinput>. " -"Note, this is also configurable using the <command>eeprom</command> command " -"on Solaris, or modifying the appropriate files in <filename>/proc/openprom/" -"options/</filename>, for example under Linux: <informalexample><screen>\n" -"# echo disk1:1 > /proc/openprom/options/boot-device\n" -"</screen></informalexample> and under Solaris:" -msgstr "" - -#. Tag: screen -#: preparing.xml:1924 -#, no-c-format -msgid "eeprom boot-device=disk1:1" -msgstr "" - -#. Tag: title -#: preparing.xml:1934 -#, no-c-format -msgid "BIOS Setup" -msgstr "" - -#. Tag: para -#: preparing.xml:1935 -#, no-c-format -msgid "" -"In order to install &debian; on a &arch-title; or zSeries machine you have " -"first boot a kernel into the system. The boot mechanism of this platform is " -"inherently different to other ones, especially from PC-like systems: there " -"are no floppy devices available at all. You will notice another big " -"difference while you work with this platform: most (if not all) of the time " -"you will work remote, with the help of some client session software like " -"telnet, or a browser. This is due to that special system architecture where " -"the 3215/3270 console is line-based instead of character-based." -msgstr "" - -#. Tag: para -#: preparing.xml:1947 -#, no-c-format -msgid "" -"Linux on this platform runs either natively on the bare machine, in a so-" -"called LPAR (Logical Partition) or in a virtual machine supplied by the VM " -"system. You can use a boot tape on all of those systems; you may use some " -"other boot media, too, but those may not be generally available. For " -"example, you can use the virtual card reader of a virtual machine, or boot " -"from the HMC (Hardware Management Console) of an LPAR if the HMC and this " -"option is available for you." -msgstr "" - -#. Tag: para -#: preparing.xml:1957 -#, no-c-format -msgid "" -"Before you actually perform an installation, you have to go over some design " -"and preparation steps. IBM has made documentation available about the whole " -"process, e.g. how to prepare an installation medium and how actually boot " -"from that medium. Duplicating that information here is neither possible nor " -"necessary. However, we will describe here which kind of Debian-specific data " -"is needed and where do you find them. Based on both sources of information " -"you have to prepare your machine and the installation medium and to perform " -"a boot from it. When you see the welcome message in your client session join " -"this document again for the Debian-specific installation steps." -msgstr "" - -#. Tag: title -#: preparing.xml:1974 -#, no-c-format -msgid "Native and LPAR installations" -msgstr "" - -#. Tag: para -#: preparing.xml:1975 -#, no-c-format -msgid "" -"Please refer to chapter 5 of the <ulink url=\"http://www.redbooks.ibm.com/" -"pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook " -"and chapter 3.2 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/" -"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: " -"Distributions</ulink> Redbook on how to set up an LPAR for Linux." -msgstr "" - -#. Tag: title -#: preparing.xml:1989 -#, no-c-format -msgid "Installation as a VM guest" -msgstr "" - -#. Tag: para -#: preparing.xml:1991 -#, no-c-format -msgid "" -"Please refer to chapter 6 of the <ulink url=\"http://www.redbooks.ibm.com/" -"pubs/pdfs/redbooks/sg244987.pdf\"> Linux for &arch-title;</ulink> Redbook " -"and chapter 3.1 of the <ulink url=\"http://www.redbooks.ibm.com/pubs/pdfs/" -"redbooks/sg246264.pdf\"> Linux for IBM eServer zSeries and &arch-title;: " -"Distributions</ulink> Redbook on how to set up a VM guest for running Linux." -msgstr "" - -#. Tag: para -#: preparing.xml:2001 -#, no-c-format -msgid "" -"You need to copy all the files from the <filename>generic</filename> sub-" -"directory to your CMS disk. Be sure to transfer <filename>kernel.debian</" -"filename> and <filename>initrd.debian</filename> in binary mode with a fixed " -"record length of 80 characters." -msgstr "" - -#. Tag: title -#: preparing.xml:2013 -#, no-c-format -msgid "Setting up an installation server" -msgstr "" - -#. Tag: para -#: preparing.xml:2015 -#, no-c-format -msgid "" -"If you don't have a connection to the Internet (either directly or via a web " -"proxy) you need to create a local installation server that can be accessed " -"from your S/390. This server keeps all the packages you want to install and " -"must make them available using NFS, HTTP or FTP." -msgstr "" - -#. Tag: para -#: preparing.xml:2023 -#, no-c-format -msgid "" -"The installation server needs to copy the exact directory structure from any " -"&debian; mirror but of only the s390 and architecture-independent files are " -"required. You can also copy the contents of all installation CDs into such a " -"directory tree." -msgstr "" - -#. Tag: emphasis -#: preparing.xml:2032 -#, no-c-format -msgid "FIXME: more information needed — from a Redbook?" -msgstr "" - -#. Tag: title -#: preparing.xml:2038 -#, no-c-format -msgid "Hardware Issues to Watch Out For" -msgstr "" - -#. Tag: para -#: preparing.xml:2039 -#, no-c-format -msgid "" -"Many people have tried operating their 90 MHz CPU at 100 MHz, etc. It " -"sometimes works, but is sensitive to temperature and other factors and can " -"actually damage your system. One of the authors of this document over-" -"clocked his own system for a year, and then the system started aborting the " -"<command>gcc</command> program with an unexpected signal while it was " -"compiling the operating system kernel. Turning the CPU speed back down to " -"its rated value solved the problem." -msgstr "" - -#. Tag: para -#: preparing.xml:2049 -#, no-c-format -msgid "" -"The <command>gcc</command> compiler is often the first thing to die from bad " -"memory modules (or other hardware problems that change data unpredictably) " -"because it builds huge data structures that it traverses repeatedly. An " -"error in these data structures will cause it to execute an illegal " -"instruction or access a non-existent address. The symptom of this will be " -"<command>gcc</command> dying from an unexpected signal." -msgstr "" - -#. Tag: para -#: preparing.xml:2059 -#, no-c-format -msgid "" -"Atari TT RAM boards are notorious for RAM problems under Linux; if you " -"encounter any strange problems, try running at least the kernel in ST-RAM. " -"Amiga users may need to exclude RAM using a booter memfile. <phrase " -"condition=\"FIXME\"><emphasis> FIXME: more description of this needed. </" -"emphasis></phrase>" -msgstr "" - -#. Tag: para -#: preparing.xml:2071 -#, no-c-format -msgid "" -"The very best motherboards support parity RAM and will actually tell you if " -"your system has a single-bit error in RAM. Unfortunately, they don't have a " -"way to fix the error, thus they generally crash immediately after they tell " -"you about the bad RAM. Still, it's better to be told you have bad memory " -"than to have it silently insert errors in your data. Thus, the best systems " -"have motherboards that support parity and true-parity memory modules; see " -"<xref linkend=\"Parity-RAM\"/>." -msgstr "" - -#. Tag: para -#: preparing.xml:2082 -#, no-c-format -msgid "" -"If you do have true-parity RAM and your motherboard can handle it, be sure " -"to enable any BIOS settings that cause the motherboard to interrupt on " -"memory parity errors." -msgstr "" - -#. Tag: title -#: preparing.xml:2090 -#, no-c-format -msgid "The Turbo Switch" -msgstr "" - -#. Tag: para -#: preparing.xml:2091 -#, no-c-format -msgid "" -"Many systems have a <emphasis>turbo</emphasis> switch that controls the " -"speed of the CPU. Select the high-speed setting. If your BIOS allows you to " -"disable software control of the turbo switch (or software control of CPU " -"speed), do so and lock the system in high-speed mode. We have one report " -"that on a particular system, while Linux is auto-probing (looking for " -"hardware devices) it can accidentally touch the software control for the " -"turbo switch." -msgstr "" - -#. Tag: title -#: preparing.xml:2104 -#, no-c-format -msgid "Cyrix CPUs and Floppy Disk Errors" -msgstr "" - -#. Tag: para -#: preparing.xml:2105 -#, no-c-format -msgid "" -"Many users of Cyrix CPUs have had to disable the cache in their systems " -"during installation, because the floppy disk has errors if they do not. If " -"you have to do this, be sure to re-enable your cache when you are finished " -"with installation, as the system runs <emphasis>much</emphasis> slower with " -"the cache disabled." -msgstr "" - -#. Tag: para -#: preparing.xml:2113 -#, no-c-format -msgid "" -"We don't think this is necessarily the fault of the Cyrix CPU. It may be " -"something that Linux can work around. We'll continue to look into the " -"problem. For the technically curious, we suspect a problem with the cache " -"being invalid after a switch from 16-bit to 32-bit code." -msgstr "" - -#. Tag: title -#: preparing.xml:2123 -#, no-c-format -msgid "Peripheral Hardware Settings" -msgstr "" - -#. Tag: para -#: preparing.xml:2124 -#, no-c-format -msgid "" -"You may have to change some settings or jumpers on your computer's " -"peripheral cards. Some cards have setup menus, while others rely on jumpers. " -"This document cannot hope to provide complete information on every hardware " -"device; what it hopes to provide is useful tips." -msgstr "" - -#. Tag: para -#: preparing.xml:2131 -#, no-c-format -msgid "" -"If any cards provide <quote>mapped memory</quote>, the memory should be " -"mapped somewhere between 0xA0000 and 0xFFFFF (from 640K to just below 1 " -"megabyte) or at an address at least 1 megabyte greater than the total amount " -"of RAM in your system." -msgstr "" - -#. Tag: title -#: preparing.xml:2142 -#, no-c-format -msgid "USB BIOS support and keyboards" -msgstr "" - -#. Tag: para -#: preparing.xml:2143 -#, no-c-format -msgid "" -"If you have no AT-style keyboard and only a USB model, you may need to " -"enable legacy AT keyboard emulation in your BIOS setup. Only do this if the " -"installation system fails to use your keyboard in USB mode. Conversely, for " -"some systems (especially laptops) you may need to disable legacy USB support " -"if your keyboard does not respond. Consult your main board manual and look " -"in the BIOS for <quote>Legacy keyboard emulation</quote> or <quote>USB " -"keyboard support</quote> options." -msgstr "" - -#. Tag: title -#: preparing.xml:2156 -#, no-c-format -msgid "More than 64 MB RAM" -msgstr "" - -#. Tag: para -#: preparing.xml:2157 -#, no-c-format -msgid "" -"The Linux Kernel cannot always detect what amount of RAM you have. If this " -"is the case please look at <xref linkend=\"boot-parms\"/>." -msgstr "" diff --git a/po/pl/preseed.po b/po/pl/preseed.po deleted file mode 100644 index b12e0e6f3..000000000 --- a/po/pl/preseed.po +++ /dev/null @@ -1,1360 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-04-12 19:05+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: preseed.xml:16 -#, no-c-format -msgid "Automating the installation using preseeding" -msgstr "" - -#. Tag: para -#: preseed.xml:18 -#, no-c-format -msgid "" -"This appendix explains the intricacies of preseeding answers to questions in " -"&d-i; to automate your installation." -msgstr "" - -#. Tag: para -#: preseed.xml:23 preseed.xml:484 -#, no-c-format -msgid "" -"The configuration fragments used in this appendix are also available as an " -"example preconfiguration file from &urlset-example-preseed;." -msgstr "" - -#. Tag: title -#: preseed.xml:31 -#, no-c-format -msgid "Introduction" -msgstr "" - -#. Tag: para -#: preseed.xml:32 -#, no-c-format -msgid "" -"Preseeding provides a way to set answers to questions asked during the " -"installation process, without having to manually enter the answers while the " -"installation is running. This makes it possible to fully automate most types " -"of installation and even offers some features not available during normal " -"installations." -msgstr "" - -#. Tag: title -#: preseed.xml:43 -#, no-c-format -msgid "Preseeding methods" -msgstr "" - -#. Tag: para -#: preseed.xml:44 -#, no-c-format -msgid "" -"There are three methods that can be used for preseeding: <firstterm>initrd</" -"firstterm>, <firstterm>file</firstterm> and <firstterm>network</firstterm>. " -"Initrd preseeding will work with any installation method and supports " -"preseeding of more things, but it requires the most preparation. File and " -"network preseeding each can be used with different installation methods. " -"With file and network preseeding the first few installer questions cannot be " -"preseeded because the preconfiguration file is only loaded after they have " -"been asked." -msgstr "" - -#. Tag: para -#: preseed.xml:55 -#, no-c-format -msgid "" -"The following table shows which preseeding methods can be used with which " -"installation methods." -msgstr "" - -#. Tag: entry -#: preseed.xml:64 -#, no-c-format -msgid "Installation method" -msgstr "" - -#. Tag: entry -#: preseed.xml:64 -#, no-c-format -msgid "initrd" -msgstr "" - -#. Tag: entry -#: preseed.xml:65 -#, no-c-format -msgid "file" -msgstr "" - -#. Tag: entry -#: preseed.xml:65 -#, no-c-format -msgid "network" -msgstr "" - -#. Tag: entry -#: preseed.xml:71 -#, no-c-format -msgid "CD/DVD" -msgstr "" - -#. Tag: entry -#: preseed.xml:72 preseed.xml:73 preseed.xml:77 preseed.xml:79 preseed.xml:82 -#: preseed.xml:83 preseed.xml:87 preseed.xml:88 preseed.xml:92 preseed.xml:94 -#: preseed.xml:97 preseed.xml:99 -#, no-c-format -msgid "<entry>yes</entry>" -msgstr "" - -#. Tag: entry -#: preseed.xml:74 preseed.xml:78 preseed.xml:84 preseed.xml:89 preseed.xml:93 -#: preseed.xml:98 -#, no-c-format -msgid "<entry>no</entry>" -msgstr "" - -#. Tag: entry -#: preseed.xml:76 -#, no-c-format -msgid "netboot" -msgstr "" - -#. Tag: entry -#: preseed.xml:81 -#, no-c-format -msgid "" -"hd-media <phrase condition=\"bootable-usb\">(including usb-stick)</phrase>" -msgstr "" - -#. Tag: entry -#: preseed.xml:86 -#, no-c-format -msgid "floppy based (cd-drivers)" -msgstr "" - -#. Tag: entry -#: preseed.xml:91 -#, no-c-format -msgid "floppy based (net-drivers)" -msgstr "" - -#. Tag: entry -#: preseed.xml:96 -#, no-c-format -msgid "generic/tape" -msgstr "" - -#. Tag: para -#: preseed.xml:105 -#, no-c-format -msgid "" -"An important difference between the preseeding methods is the point at which " -"the preconfiguration file is loaded and processed. For initrd preseeding " -"this is right at the start of the installation, before the first question is " -"even asked. For file preseeding this is after the CD or CD image has been " -"loaded. For network preseeding it is only after the network has been " -"configured." -msgstr "" - -#. Tag: para -#: preseed.xml:114 -#, no-c-format -msgid "" -"In practical terms this means for file and network preseeding that the " -"questions about language, country and keyboard selection will already have " -"been asked. For network preseeding add to that any questions related to " -"network configuration. Some other questions that are only displayed at " -"medium or low priority (like the first hardware detection run) will also " -"already have been processed." -msgstr "" - -#. Tag: para -#: preseed.xml:123 -#, no-c-format -msgid "" -"Obviously, any questions that have been processed before the " -"preconfiguration file is loaded cannot be preseeded. <xref linkend=\"preseed-" -"bootparms\"/> offers a way to avoid these questions being asked." -msgstr "" - -#. Tag: title -#: preseed.xml:134 -#, no-c-format -msgid "Limitations" -msgstr "" - -#. Tag: para -#: preseed.xml:135 -#, no-c-format -msgid "" -"Although most questions used by &d-i; can be preseeded using this method, " -"there are some notable exceptions. You must (re)partition an entire disk or " -"use available free space on a disk; it is not possible to use existing " -"partitions. You currently cannot use preseeding to set up RAID." -msgstr "" - -#. Tag: title -#: preseed.xml:207 -#, no-c-format -msgid "Running custom commands during the installation" -msgstr "" - -#. Tag: para -#: preseed.xml:208 -#, no-c-format -msgid "" -"A very powerful and flexible option offered by the preconfiguration tools is " -"the ability to run commands or scripts at certain points in the " -"installation. See <xref linkend=\"preseed-shell\"/> for details." -msgstr "" - -#. Tag: para -#: preseed.xml:217 -#, no-c-format -msgid "" -"<userinput>preseed/early_command</userinput>: is run as soon as the " -"preconfiguration file has been loaded" -msgstr "" - -#. Tag: para -#: preseed.xml:221 -#, no-c-format -msgid "" -"<userinput>preseed/late_command</userinput>: is run just before the reboot " -"at the end of the install, but before the <filename>/target</filename> " -"filesystem has been unmounted" -msgstr "" - -#. Tag: title -#: preseed.xml:231 -#, no-c-format -msgid "Using preseeding to change default values" -msgstr "" - -#. Tag: para -#: preseed.xml:232 -#, no-c-format -msgid "" -"It is possible to use preseeding to change the default answer for a " -"question, but still have the question asked. To do this the <firstterm>seen</" -"firstterm> flag must be reset to <quote>false</quote> after setting the " -"value for a template." -msgstr "" - -#. Tag: screen -#: preseed.xml:241 -#, no-c-format -msgid "" -"d-i foo/bar string value\n" -"d-i foo/bar seen false" -msgstr "" - -#. Tag: title -#: preseed.xml:247 -#, no-c-format -msgid "Using preseeding" -msgstr "" - -#. Tag: para -#: preseed.xml:248 -#, no-c-format -msgid "" -"Of course you will first need to create a preconfiguration file and place it " -"in the location from where you want to use it. Creating the preconfiguration " -"file is covered later in this appendix. Putting it in the correct location " -"is fairly straightforward for network preseeding or if you want to read the " -"file off a floppy or usb-stick. If you want to include the file on a CD or " -"DVD, you will have to remaster the ISO image. How to get the " -"preconfiguration file included in the initrd is outside the scope of this " -"document; please consult the developers documentation for &d-i;." -msgstr "" - -#. Tag: para -#: preseed.xml:259 -#, no-c-format -msgid "" -"An example preconfiguration file that you can use as basis for your own " -"preconfiguration file is available from &urlset-example-preseed;. This file " -"is based on the configuration fragments included in this appendix." -msgstr "" - -#. Tag: title -#: preseed.xml:268 -#, no-c-format -msgid "Loading the preconfiguration file" -msgstr "" - -#. Tag: para -#: preseed.xml:269 -#, no-c-format -msgid "" -"If you are using initrd preseeding, you only have to make sure a file named " -"<filename>preseed.cfg</filename> is included in the root directory of the " -"initrd. The installer will automatically check if this file is present and " -"load it." -msgstr "" - -#. Tag: para -#: preseed.xml:276 -#, no-c-format -msgid "" -"For the other preseeding methods you need to tell the installer what file to " -"use when you boot it. This is normally done by passing the kernel a boot " -"parameter, either manually at boot time or by editing the bootloader " -"configuration file (e.g. <filename>syslinux.cfg</filename>) and adding the " -"parameter to the end of the append line(s) for the kernel." -msgstr "" - -#. Tag: para -#: preseed.xml:284 -#, no-c-format -msgid "" -"If you do specify the preconfiguration file in the bootloader configuration, " -"you might change the configuration so you don't need to hit enter to boot " -"the installer. For syslinux this means setting the timeout to <literal>1</" -"literal> in <filename>syslinux.cfg</filename>." -msgstr "" - -#. Tag: para -#: preseed.xml:291 -#, no-c-format -msgid "" -"To make sure the installer gets the right preconfiguration file, you can " -"optionally specify a checksum for the file. Currently this needs to be a " -"md5sum, and if specified it must match the preconfiguration file or the " -"installer will refuse to use it." -msgstr "" - -#. Tag: screen -#: preseed.xml:300 -#, no-c-format -msgid "" -"Boot parameters to specify:\n" -"- if you're netbooting:\n" -" preseed/url=http://host/path/to/preseed.cfg\n" -" preseed/url/checksum=5da499872becccfeda2c4872f9171c3d\n" -"\n" -"- if you're booting a remastered CD:\n" -" preseed/file=/cdrom/preseed.cfg\n" -" preseed/file/checksum=5da499872becccfeda2c4872f9171c3d\n" -"\n" -"- if you're installing from USB media (put the preconfiguration file in the\n" -" toplevel directory of the USB stick):\n" -" preseed/file=/hd-media/preseed.cfg\n" -" preseed/file/checksum=5da499872becccfeda2c4872f9171c3d" -msgstr "" - -#. Tag: para -#: preseed.xml:302 -#, no-c-format -msgid "" -"While you're at it, you may want to add a boot parameter <userinput>debconf/" -"priority=critical</userinput>. This will avoid most questions even if the " -"preseeding below misses some." -msgstr "" - -#. Tag: title -#: preseed.xml:312 -#, no-c-format -msgid "Using a DHCP server to specify preconfiguration files" -msgstr "" - -#. Tag: para -#: preseed.xml:313 -#, no-c-format -msgid "" -"It's also possible to use DHCP to specify a preconfiguration file to " -"download from the network. DHCP allows specifying a filename. Normally this " -"is a file to netboot, but if it appears to be an URL then installation media " -"that support network preseeding will download the file from the URL and use " -"it as a preconfiguration file. Here is an example of how to set it up in the " -"dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server Debian " -"package)." -msgstr "" - -#. Tag: screen -#: preseed.xml:324 -#, no-c-format -msgid "" -"if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" -" filename \"http://host/preseed.cfg\";\n" -"}" -msgstr "" - -#. Tag: para -#: preseed.xml:326 -#, no-c-format -msgid "" -"Note that the above example limits this filename to DHCP clients that " -"identify themselves as \"d-i\", so it will not affect regular DHCP clients, " -"but only the installer. You can also put the text in a stanza for only one " -"particular host to avoid preseeding all installs on your network." -msgstr "" - -#. Tag: para -#: preseed.xml:333 -#, no-c-format -msgid "" -"A good way to use the DHCP preseeding is to only preseed values specific to " -"your network, such as the Debian mirror to use. This way installs on your " -"network will automatically get a good mirror selected, but the rest of the " -"installation can be performed interactively. Using DHCP preseeding to fully " -"automate Debian installs should only be done with care." -msgstr "" - -#. Tag: title -#: preseed.xml:345 -#, no-c-format -msgid "Using boot parameters to supplement preseeding" -msgstr "" - -#. Tag: para -#: preseed.xml:346 -#, no-c-format -msgid "" -"Some parts of the installation process cannot be automated using some forms " -"of preseeding because the questions are asked before the preconfiguration " -"file is loaded. For example, if the preconfiguration file is downloaded over " -"the network, the network setup must be done first. One reason to use initrd " -"preseeding is that it allows preseeding of even these early steps of the " -"installation process." -msgstr "" - -#. Tag: para -#: preseed.xml:355 -#, no-c-format -msgid "" -"If a preconfiguration file cannot be used to preseed some steps, the install " -"can still be fully automated, since you can pass preseed values to the " -"kernel on the command line. Just pass <userinput>path/to/var=value</" -"userinput> for any of the preseed variables listed in the examples." -msgstr "" - -#. Tag: para -#: preseed.xml:363 -#, no-c-format -msgid "" -"The 2.4 kernel accepts a maximum of 8 command line options and 8 environment " -"options (including any options added by default for the installer). If these " -"numbers are exceeded, 2.4 kernels will drop any excess options and 2.6 " -"kernels will panic. For kernel 2.6.9 and later, you can use 32 command line " -"options and 32 environment options." -msgstr "" - -#. Tag: para -#: preseed.xml:372 -#, no-c-format -msgid "" -"For most installations some of the default options in your bootloader " -"configuration file, like <literal>vga=normal</literal>, may be safely " -"removed which may allow you to add more options for preseeding." -msgstr "" - -#. Tag: para -#: preseed.xml:379 -#, no-c-format -msgid "" -"It may not always be possible to specify values with spaces for boot " -"parameters, even if you delimit them with quotes." -msgstr "" - -#. Tag: title -#: preseed.xml:389 -#, no-c-format -msgid "Creating a preconfiguration file" -msgstr "" - -#. Tag: para -#: preseed.xml:390 -#, no-c-format -msgid "" -"The preconfiguration file is in the format used by the <command>debconf-set-" -"selections</command> command. The general format of a line in a " -"preconfiguration file is:" -msgstr "" - -#. Tag: screen -#: preseed.xml:396 -#, no-c-format -msgid "<owner> <template name> <template type> <value>" -msgstr "" - -#. Tag: para -#: preseed.xml:398 -#, no-c-format -msgid "" -"There are a few rules to keep in mind when writing a preconfiguration file." -msgstr "" - -#. Tag: para -#: preseed.xml:405 -#, no-c-format -msgid "" -"Put only a single space or tab between type and value: any additional " -"whitespace will be interpreted as belonging to the value." -msgstr "" - -#. Tag: para -#: preseed.xml:409 -#, no-c-format -msgid "" -"A line can be split into multiple lines by appending a backslash " -"(<quote><literal>\\</literal></quote>) as the line continuation character. A " -"good place to split a line is after the template name; a bad place is " -"between type and value." -msgstr "" - -#. Tag: para -#: preseed.xml:415 -#, no-c-format -msgid "" -"Most templates need to be preseeded using the values valid in English and " -"not the translated values. However, there are some templates (for example in " -"<classname>partman</classname> where the translated values need to be used." -msgstr "" - -#. Tag: para -#: preseed.xml:421 -#, no-c-format -msgid "" -"Some templates take a code as value instead of the English text that is " -"shown during installation." -msgstr "" - -#. Tag: para -#: preseed.xml:427 -#, no-c-format -msgid "" -"The easiest way to create a preconfiguration file is to use the example file " -"linked in <xref linkend=\"preseed-contents\"/> as basis and work from there." -msgstr "" - -#. Tag: para -#: preseed.xml:432 -#, no-c-format -msgid "" -"An alternative method is to do a manual installation and then, after " -"rebooting, use the <command>debconf-get-selections</command> from the " -"<classname>debconf-utils</classname> package to dump both the debconf " -"database and the installer's cdebconf database to a single file:" -msgstr "" - -#. Tag: screen -#: preseed.xml:439 -#, no-c-format -msgid "" -"$ debconf-get-selections --installer > <replaceable>file</replaceable>\n" -"$ debconf-get-selections >> <replaceable>file</replaceable>" -msgstr "" - -#. Tag: para -#: preseed.xml:441 -#, no-c-format -msgid "" -"However, a file generated in this manner will have some items that should " -"not be preseeded, and the example file is a better starting place for most " -"users." -msgstr "" - -#. Tag: para -#: preseed.xml:449 -#, no-c-format -msgid "" -"This method relies on the fact that, at the end of the installation, the " -"installer's cdebconf database is saved to the installed system in <filename>/" -"var/log/installer/cdebconf</filename>. However, because the database may " -"contain sensitive information, by default the files are only readable by " -"root." -msgstr "" - -#. Tag: para -#: preseed.xml:457 -#, no-c-format -msgid "" -"The directory <filename>/var/log/installer</filename> and all files in it " -"will be deleted from your system if you purge the package " -"<classname>installation-report</classname>." -msgstr "" - -#. Tag: para -#: preseed.xml:465 -#, no-c-format -msgid "" -"To check possible values for templates, you can use <command>nano</command> " -"to examine the files in <filename>/var/lib/cdebconf</filename> while an " -"installation is in progress. View <filename>templates.dat</filename> for the " -"raw templates and <filename>questions.dat</filename> for the current values " -"and for the values assigned to variables." -msgstr "" - -#. Tag: para -#: preseed.xml:473 -#, no-c-format -msgid "" -"To check if the format of your preconfiguration file is valid before " -"performing an install, you can use the command <command>debconf-set-" -"selections -c <replaceable>preseed.cfg</replaceable></command>." -msgstr "" - -#. Tag: title -#: preseed.xml:483 -#, no-c-format -msgid "Contents of the preconfiguration file" -msgstr "" - -#. Tag: para -#: preseed.xml:489 -#, no-c-format -msgid "" -"Note that this example is based on an installation for the Intel x86 " -"architecture. If you are installing a different architecture, some of the " -"examples (like keyboard selection and bootloader installation) may not be " -"relevant and will need to be replaced by debconf settings appropriate for " -"your architecture." -msgstr "" - -#. Tag: title -#: preseed.xml:500 -#, no-c-format -msgid "Localization" -msgstr "" - -#. Tag: para -#: preseed.xml:501 -#, no-c-format -msgid "" -"Setting localization values will only work if you are using initrd " -"preseeding. With all other methods the preconfiguration file will only be " -"loaded after these questions have been asked." -msgstr "" - -#. Tag: para -#: preseed.xml:507 -#, no-c-format -msgid "" -"The locale can be used to specify both language and country. To specify the " -"locale as a boot parameter, use <userinput>debian-installer/" -"locale=<replaceable>en_US</replaceable></userinput>." -msgstr "" - -#. Tag: screen -#: preseed.xml:513 -#, no-c-format -msgid "" -"# Locale sets language and country.\n" -"d-i debian-installer/locale string en_US" -msgstr "" - -#. Tag: para -#: preseed.xml:515 -#, no-c-format -msgid "" -"Keyboard configuration consists of selecting a keyboard architecture and a " -"keymap. In most cases the correct keyboard architecture is selected by " -"default, so there's normally no need to preseed it. The keymap must be valid " -"for the selected keyboard architecture." -msgstr "" - -#. Tag: screen -#: preseed.xml:522 -#, no-c-format -msgid "" -"# Keyboard selection.\n" -"#d-i console-tools/archs select at\n" -"d-i console-keymaps-at/keymap select us\n" -"# Example for a different keyboard architecture\n" -"#d-i console-keymaps-usb/keymap select mac-usb-us" -msgstr "" - -#. Tag: para -#: preseed.xml:524 -#, no-c-format -msgid "" -"To skip keyboard configuration, preseed <classname>console-tools/archs</" -"classname> with <userinput>skip-config</userinput>. This will result in the " -"kernel keymap remaining active." -msgstr "" - -#. Tag: para -#: preseed.xml:533 -#, no-c-format -msgid "" -"The changes in the input layer for 2.6 kernels have made the keyboard " -"architecture virtually obsolete. For 2.6 kernels normally a <quote>PC</" -"quote> (<userinput>at</userinput>) keymap should be selected." -msgstr "" - -#. Tag: title -#: preseed.xml:543 -#, no-c-format -msgid "Network configuration" -msgstr "" - -#. Tag: para -#: preseed.xml:544 -#, no-c-format -msgid "" -"Of course, preseeding the network configuration won't work if you're loading " -"your preconfiguration file from the network. But it's great when you're " -"booting from CD or USB stick. If you are loading preconfiguration files from " -"the network, you can pass network config parameters by using kernel boot " -"parameters." -msgstr "" - -#. Tag: para -#: preseed.xml:552 -#, no-c-format -msgid "" -"If you need to pick a particular interface when netbooting before loading a " -"preconfiguration file from the network, use a boot parameter such as " -"<userinput>netcfg/choose_interface=<replaceable>eth1</replaceable></" -"userinput>." -msgstr "" - -#. Tag: screen -#: preseed.xml:560 -#, no-c-format -msgid "" -"# netcfg will choose an interface that has link if possible. This makes it\n" -"# skip displaying a list if there is more than one interface.\n" -"d-i netcfg/choose_interface select auto\n" -"\n" -"# To pick a particular interface instead:\n" -"#d-i netcfg/choose_interface select eth1\n" -"\n" -"# If you have a slow dhcp server and the installer times out waiting for\n" -"# it, this might be useful.\n" -"#d-i netcfg/dhcp_timeout string 60\n" -"\n" -"# If you prefer to configure the network manually, uncomment this line and\n" -"# the static network configuration below.\n" -"#d-i netcfg/disable_dhcp boolean true\n" -"\n" -"# If you want the preconfiguration file to work on systems both with and\n" -"# without a dhcp server, uncomment these lines and the static network\n" -"# configuration below.\n" -"#d-i netcfg/dhcp_failed note\n" -"#d-i netcfg/dhcp_options select Configure network manually\n" -"\n" -"# Static network configuration.\n" -"#d-i netcfg/get_nameservers string 192.168.1.1\n" -"#d-i netcfg/get_ipaddress string 192.168.1.42\n" -"#d-i netcfg/get_netmask string 255.255.255.0\n" -"#d-i netcfg/get_gateway string 192.168.1.1\n" -"#d-i netcfg/confirm_static boolean true\n" -"\n" -"# Any hostname and domain names assigned from dhcp take precedence over\n" -"# values set here. However, setting the values still prevents the questions\n" -"# from being shown, even if values come from dhcp.\n" -"d-i netcfg/get_hostname string unassigned-hostname\n" -"d-i netcfg/get_domain string unassigned-domain\n" -"\n" -"# Disable that annoying WEP key dialog.\n" -"d-i netcfg/wireless_wep string\n" -"# The wacky dhcp hostname that some ISPs use as a password of sorts.\n" -"#d-i netcfg/dhcp_hostname string radish" -msgstr "" - -#. Tag: title -#: preseed.xml:565 -#, no-c-format -msgid "Mirror settings" -msgstr "" - -#. Tag: para -#: preseed.xml:566 -#, 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." -msgstr "" - -#. Tag: para -#: preseed.xml:573 -#, no-c-format -msgid "" -"The parameter <classname>mirror/suite</classname> determines the suite for " -"the installed system." -msgstr "" - -#. Tag: para -#: preseed.xml:578 -#, no-c-format -msgid "" -"The parameter <classname>mirror/udeb/suite</classname> determines the suite " -"for additional components for the installer. It is only useful to set this " -"if components are actually downloaded over the network and should match the " -"suite that was used to build the initrd for the installation method used for " -"the installation. By default the value for <classname>mirror/udeb/suite</" -"classname> is the same as <classname>mirror/suite</classname>." -msgstr "" - -#. Tag: screen -#: preseed.xml:590 -#, no-c-format -msgid "" -"d-i mirror/country string enter information manually\n" -"d-i mirror/http/hostname string http.us.debian.org\n" -"d-i mirror/http/directory string /debian\n" -"d-i mirror/http/proxy string\n" -"\n" -"# Suite to install.\n" -"#d-i mirror/suite string testing\n" -"# Suite to use for loading installer components (optional).\n" -"#d-i mirror/udeb/suite string testing" -msgstr "" - -#. Tag: title -#: preseed.xml:595 -#, no-c-format -msgid "Partitioning" -msgstr "" - -#. Tag: para -#: preseed.xml:596 -#, 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 nor to " -"set up RAID." -msgstr "" - -#. Tag: para -#: preseed.xml:608 -#, no-c-format -msgid "" -"The identification of disks is dependent on the order in which their drivers " -"are loaded. If there are multiple disks in the system, make very sure the " -"correct one will be selected before using preseeding." -msgstr "" - -#. Tag: screen -#: preseed.xml:616 -#, no-c-format -msgid "" -"# If the system has free space you can choose to only partition that space.\n" -"# Note: this template must be preseeded with a localized (translated) " -"value.\n" -"#d-i partman-auto/init_automatically_partition \\\n" -"# select Use the largest continuous free space\n" -"\n" -"# Alternatively, you can specify a disk to partition. The device name can\n" -"# be given in either devfs or traditional non-devfs format.\n" -"# For example, to use the first disk devfs knows of:\n" -"d-i partman-auto/disk string /dev/discs/disc0/disc\n" -"\n" -"# You can choose from any of the predefined partitioning recipes.\n" -"# Note: this template must be preseeded with a localized (translated) " -"value.\n" -"d-i partman-auto/choose_recipe \\\n" -" select All files in one partition (recommended for new users)\n" -"#d-i partman-auto/choose_recipe \\\n" -"# select Separate /home partition\n" -"#d-i partman-auto/choose_recipe \\\n" -"# select Separate /home, /usr, /var, and /tmp partitions\n" -"\n" -"# Or provide a recipe of your own...\n" -"# The recipe format is documented in the file devel/partman-auto-recipe." -"txt.\n" -"# If you have a way to get a recipe file into the d-i environment, you can\n" -"# just point at it.\n" -"#d-i partman-auto/expert_recipe_file string /hd-media/recipe\n" -"\n" -"# If not, you can put an entire recipe the preconfiguration file in one\n" -"# (logical) line. This example creates a small /boot partition, suitable\n" -"# swap, and uses the rest of the space for the root partition:\n" -"#d-i partman-auto/expert_recipe string \\\n" -"# boot-root :: \\\n" -"# 40 50 100 ext3 \\\n" -"# $primary{ } $bootable{ } \\\n" -"# method{ format } format{ } \\\n" -"# use_filesystem{ } filesystem{ ext3 } \\\n" -"# mountpoint{ /boot } \\\n" -"# . \\\n" -"# 500 10000 1000000000 ext3 \\\n" -"# method{ format } format{ } \\\n" -"# use_filesystem{ } filesystem{ ext3 } \\\n" -"# mountpoint{ / } \\\n" -"# . \\\n" -"# 64 512 300% linux-swap \\\n" -"# method{ swap } format{ } \\\n" -"# .\n" -"\n" -"# This makes partman automatically partition without confirmation.\n" -"d-i partman/confirm_write_new_label boolean true\n" -"d-i partman/choose_partition \\\n" -" select Finish partitioning and write changes to disk\n" -"d-i partman/confirm boolean true" -msgstr "" - -#. Tag: title -#: preseed.xml:621 -#, no-c-format -msgid "Clock and time zone setup" -msgstr "" - -#. Tag: screen -#: preseed.xml:623 -#, no-c-format -msgid "" -"# Controls whether or not the hardware clock is set to UTC.\n" -"d-i clock-setup/utc boolean true\n" -"\n" -"# You may set this to any valid setting for $TZ; see the contents of\n" -"# /usr/share/zoneinfo/ for valid values.\n" -"d-i time/zone string US/Eastern" -msgstr "" - -#. Tag: title -#: preseed.xml:628 -#, no-c-format -msgid "Apt setup" -msgstr "" - -#. Tag: para -#: preseed.xml:629 -#, no-c-format -msgid "" -"Setup of the <filename>/etc/apt/sources.list</filename> and basic " -"configuration options is fully automated based on your installation method " -"and answers to earlier questions. You can optionally add other (local) " -"repositories." -msgstr "" - -#. Tag: screen -#: preseed.xml:637 -#, no-c-format -msgid "" -"# You can choose to install non-free and contrib software.\n" -"#d-i apt-setup/non-free boolean true\n" -"#d-i apt-setup/contrib boolean true\n" -"# Uncomment this to avoid adding security sources, or\n" -"# add a hostname to use a different server than security.debian.org.\n" -"#d-i apt-setup/security_host string\n" -"\n" -"# Additional repositories, local[0-9] available\n" -"#d-i apt-setup/local0/comment string local server\n" -"#d-i apt-setup/local0/repository string \\\n" -"# deb http://local.server/debian stable main\n" -"# URL to the public key of the local repository\n" -"#d-i apt-setup/local0/key string http://local.server/key" -msgstr "" - -#. Tag: title -#: preseed.xml:642 -#, no-c-format -msgid "Account setup" -msgstr "" - -#. Tag: para -#: preseed.xml:643 -#, no-c-format -msgid "" -"The password for the root account and name and password for a first regular " -"user's account can be preseeded. For the passwords you can use either clear " -"text values or MD5 <emphasis>hashes</emphasis>." -msgstr "" - -#. Tag: para -#: preseed.xml:650 -#, no-c-format -msgid "" -"Be aware that preseeding passwords is not completely secure as everyone with " -"access to the preconfiguration file will have the knowledge of these " -"passwords. Using MD5 hashes is considered slightly better in terms of " -"security but it might also give a false sense of security as access to a MD5 " -"hash allows for brute force attacks." -msgstr "" - -#. Tag: screen -#: preseed.xml:660 -#, no-c-format -msgid "" -"# Skip creation of a root account (normal user account will be able to\n" -"# use sudo).\n" -"#d-i passwd/root-login boolean false\n" -"# Alternatively, to skip creation of a normal user account.\n" -"#d-i passwd/make-user boolean false\n" -"\n" -"# Root password, either in clear text\n" -"#d-i passwd/root-password password r00tme\n" -"#d-i passwd/root-password-again password r00tme\n" -"# or encrypted using an MD5 hash.\n" -"#d-i passwd/root-password-crypted password [MD5 hash]\n" -"\n" -"# To create a normal user account.\n" -"#d-i passwd/user-fullname string Debian User\n" -"#d-i passwd/username string debian\n" -"# Normal user's password, either in clear text\n" -"#d-i passwd/user-password password insecure\n" -"#d-i passwd/user-password-again password insecure\n" -"# or encrypted using an MD5 hash.\n" -"#d-i passwd/user-password-crypted password [MD5 hash]" -msgstr "" - -#. Tag: para -#: preseed.xml:662 -#, no-c-format -msgid "" -"The <classname>passwd/root-password-crypted</classname> and " -"<classname>passwd/user-password-crypted</classname> variables can also be " -"preseeded with <quote>!</quote> as their value. In that case, the " -"corresponding account is disabled. This may be convenient for the root " -"account, provided of course that an alternative method is setup to allow " -"administrative activities or root login (for instance by using SSH key " -"authentication or <command>sudo</command>)." -msgstr "" - -#. Tag: para -#: preseed.xml:672 -#, no-c-format -msgid "" -"An MD5 hash for a password can be generated using the following command." -msgstr "" - -#. Tag: screen -#: preseed.xml:676 -#, no-c-format -msgid "$ echo \"r00tme\" | mkpasswd -s -H MD5" -msgstr "" - -#. Tag: title -#: preseed.xml:682 -#, no-c-format -msgid "Base system installation" -msgstr "" - -#. Tag: para -#: preseed.xml:683 -#, no-c-format -msgid "" -"There is actually not very much that can be preseeded for this stage of the " -"installation. The only questions asked concern the installation of the " -"kernel." -msgstr "" - -#. Tag: screen -#: preseed.xml:690 -#, no-c-format -msgid "" -"# Select the initramfs generator used to generate the initrd for 2.6 " -"kernels.\n" -"#d-i base-installer/kernel/linux/initramfs-generators string yaird" -msgstr "" - -#. Tag: title -#: preseed.xml:695 -#, no-c-format -msgid "Boot loader installation" -msgstr "" - -#. Tag: screen -#: preseed.xml:697 -#, no-c-format -msgid "" -"# Grub is the default boot loader (for x86). If you want lilo installed\n" -"# instead, uncomment this:\n" -"#d-i grub-installer/skip boolean true\n" -"\n" -"# This is fairly safe to set, it makes grub install automatically to the " -"MBR\n" -"# 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" -"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" -"# uncomment and edit these lines:\n" -"#d-i grub-installer/bootdev string (hd0,0)\n" -"#d-i grub-installer/only_debian boolean false\n" -"#d-i grub-installer/with_other_os boolean false" -msgstr "" - -#. Tag: title -#: preseed.xml:702 -#, no-c-format -msgid "Package selection" -msgstr "" - -#. Tag: para -#: preseed.xml:703 -#, no-c-format -msgid "" -"You can choose to install any combination of tasks that are available. " -"Available tasks as of this writing include:" -msgstr "" - -#. Tag: userinput -#: preseed.xml:712 -#, no-c-format -msgid "Standard system" -msgstr "" - -#. Tag: userinput -#: preseed.xml:715 -#, no-c-format -msgid "Desktop environment" -msgstr "" - -#. Tag: userinput -#: preseed.xml:718 -#, no-c-format -msgid "Web server" -msgstr "" - -#. Tag: userinput -#: preseed.xml:721 -#, no-c-format -msgid "Print server" -msgstr "" - -#. Tag: userinput -#: preseed.xml:724 -#, no-c-format -msgid "DNS server" -msgstr "" - -#. Tag: userinput -#: preseed.xml:727 -#, no-c-format -msgid "File server" -msgstr "" - -#. Tag: userinput -#: preseed.xml:730 -#, no-c-format -msgid "Mail server" -msgstr "" - -#. Tag: userinput -#: preseed.xml:733 -#, no-c-format -msgid "SQL database" -msgstr "" - -#. Tag: userinput -#: preseed.xml:736 -#, no-c-format -msgid "Laptop" -msgstr "" - -#. Tag: para -#: preseed.xml:740 -#, no-c-format -msgid "" -"You can also choose to install no tasks, and force the installation of a set " -"of packages in some other way. We recommend always including the " -"<userinput>Standard system</userinput> task." -msgstr "" - -#. Tag: screen -#: preseed.xml:748 -#, no-c-format -msgid "" -"tasksel tasksel/first multiselect Standard system, Desktop environment\n" -"#tasksel tasksel/first multiselect Standard system, Web server\n" -"\n" -"# Some versions of the installer can report back on what software you have\n" -"# installed, and what software you use. The default is not to report back,\n" -"# but sending reports helps the project determine what software is most\n" -"# popular and include it on CDs.\n" -"#popularity-contest popularity-contest/participate boolean false" -msgstr "" - -#. Tag: title -#: preseed.xml:753 -#, no-c-format -msgid "Finishing up the first stage install" -msgstr "" - -#. Tag: screen -#: preseed.xml:755 -#, no-c-format -msgid "" -"# Avoid that last message about the install being complete.\n" -"d-i prebaseconfig/reboot_in_progress note\n" -"\n" -"# This will prevent the installer from ejecting the CD during the reboot,\n" -"# which is useful in some situations.\n" -"#d-i cdrom-detect/eject boolean false" -msgstr "" - -#. Tag: title -#: preseed.xml:760 -#, no-c-format -msgid "Mailer configuration" -msgstr "" - -#. Tag: para -#: preseed.xml:761 -#, no-c-format -msgid "" -"During a normal install, exim asks only a few questions. Here's how to avoid " -"even those. More complicated preseeding is possible." -msgstr "" - -#. Tag: screen -#: preseed.xml:768 -#, no-c-format -msgid "" -"exim4-config exim4/dc_eximconfig_configtype \\\n" -" select no configuration at this time\n" -"exim4-config exim4/no_config boolean true\n" -"exim4-config exim4/no_config boolean true\n" -"exim4-config exim4/dc_postmaster string" -msgstr "" - -#. Tag: title -#: preseed.xml:773 -#, no-c-format -msgid "X configuration" -msgstr "" - -#. Tag: para -#: preseed.xml:774 -#, no-c-format -msgid "" -"Preseeding Debian's X config is possible, but you probably need to know some " -"details about the video hardware of the machine, since Debian's X " -"configurator does not do fully automatic configuration of everything." -msgstr "" - -#. Tag: screen -#: preseed.xml:782 -#, no-c-format -msgid "" -"# X can detect the right driver for some cards, but if you're preseeding,\n" -"# you override whatever it chooses. Still, vesa will work most places.\n" -"#xserver-xorg xserver-xorg/config/device/driver select vesa\n" -"\n" -"# A caveat with mouse autodetection is that if it fails, X will retry it\n" -"# over and over. So if it's preseeded to be done, there is a possibility of\n" -"# an infinite loop if the mouse is not autodetected.\n" -"#xserver-xorg xserver-xorg/autodetect_mouse boolean true\n" -"\n" -"# Monitor autodetection is recommended.\n" -"xserver-xorg xserver-xorg/autodetect_monitor boolean true\n" -"# Uncomment if you have an LCD display.\n" -"#xserver-xorg xserver-xorg/config/monitor/lcd boolean true\n" -"# X has three configuration paths for the monitor. Here's how to preseed\n" -"# the \"medium\" path, which is always available. The \"simple\" path may " -"not\n" -"# be available, and the \"advanced\" path asks too many questions.\n" -"xserver-xorg xserver-xorg/config/monitor/selection-method \\\n" -" select medium\n" -"xserver-xorg xserver-xorg/config/monitor/mode-list \\\n" -" select 1024x768 @ 60 Hz" -msgstr "" - -#. Tag: title -#: preseed.xml:787 -#, no-c-format -msgid "Preseeding other packages" -msgstr "" - -#. Tag: screen -#: preseed.xml:789 -#, no-c-format -msgid "" -"# Depending on what software you choose to install, or if things go wrong\n" -"# during the installation process, it's possible that other questions may\n" -"# be asked. You can preseed those too, of course. To get a list of every\n" -"# possible question that could be asked during an install, do an\n" -"# installation, and then run these commands:\n" -"# debconf-get-selections --installer > file\n" -"# debconf-get-selections >> file" -msgstr "" - -#. Tag: title -#: preseed.xml:795 -#, no-c-format -msgid "Advanced options" -msgstr "" - -#. Tag: title -#: preseed.xml:798 -#, no-c-format -msgid "Shell commands" -msgstr "" - -#. Tag: screen -#: preseed.xml:800 -#, no-c-format -msgid "" -"# d-i preseeding is inherently not secure. Nothing in the installer checks\n" -"# for attempts at buffer overflows or other exploits of the values of a\n" -"# preconfiguration file like this one. Only use preconfiguration files from\n" -"# trusted locations! To drive that home, and because it's generally useful,\n" -"# here's a way to run any shell command you'd like inside the installer,\n" -"# automatically.\n" -"\n" -"# This first command is run as early as possible, just after\n" -"# preseeding is read.\n" -"#d-i preseed/early_command string anna-install some-udeb\n" -"\n" -"# This command is run just before the install finishes, but when there is\n" -"# still a usable /target directory. You can chroot to /target and use it\n" -"# directly, or use the apt-install and in-target commands to easily install\n" -"# packages and run commands in the target system.\n" -"#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh" -msgstr "" - -#. Tag: title -#: preseed.xml:805 -#, no-c-format -msgid "Chainloading preconfiguration files" -msgstr "" - -#. Tag: para -#: preseed.xml:806 -#, no-c-format -msgid "" -"It is possible to include other preconfiguration files from a " -"preconfiguration file. Any settings in those files will override pre-" -"existing settings from files loaded earlier. This makes it possible to put, " -"for example, general networking settings for your location in one file and " -"more specific settings for certain configurations in other files." -msgstr "" - -#. Tag: screen -#: preseed.xml:816 -#, no-c-format -msgid "" -"# More that one file can be listed, separated by spaces; all will be\n" -"# loaded. The included files can have preseed/include directives of their\n" -"# own as well. Note that if the filenames are relative, they are taken from\n" -"# the same directory as the preconfiguration file that includes them.\n" -"#d-i preseed/include string x.cfg\n" -"\n" -"# The installer can optionally verify checksums of preconfiguration files\n" -"# before using them. Currently only md5sums are supported, list the md5sums\n" -"# in the same order as the list of files to include.\n" -"#d-i preseed/include/checksum string 5da499872becccfeda2c4872f9171c3d\n" -"\n" -"# More flexibly, this runs a shell command and if it outputs the names of\n" -"# preconfiguration files, includes those files. \n" -"#d-i preseed/include_command \\\n" -"# string echo if [ \"`hostname`\" = bob ]; then echo bob.cfg; fi" -msgstr "" diff --git a/po/pl/random-bits.po b/po/pl/random-bits.po deleted file mode 100644 index 73c1e9916..000000000 --- a/po/pl/random-bits.po +++ /dev/null @@ -1,1350 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-02-07 15:07+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: random-bits.xml:4 -#, no-c-format -msgid "Random Bits" -msgstr "" - -#. Tag: title -#: random-bits.xml:11 -#, no-c-format -msgid "Linux Devices" -msgstr "" - -#. Tag: para -#: random-bits.xml:12 -#, no-c-format -msgid "" -"In Linux you have various special files in <filename>/dev</filename>. These " -"files are called device files. In the Unix world accessing hardware is " -"different. There you have a special file which actually runs a driver which " -"in turn accesses the hardware. The device file is an interface to the actual " -"system component. Files under <filename>/dev</filename> also behave " -"differently than ordinary files. Below are the most important device files " -"listed." -msgstr "" - -#. Tag: filename -#: random-bits.xml:27 -#, no-c-format -msgid "<filename>fd0</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:28 -#, no-c-format -msgid "First Floppy Drive" -msgstr "" - -#. Tag: filename -#: random-bits.xml:30 -#, no-c-format -msgid "<filename>fd1</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:31 -#, no-c-format -msgid "Second Floppy Drive" -msgstr "" - -#. Tag: filename -#: random-bits.xml:37 -#, no-c-format -msgid "<filename>hda</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:38 -#, no-c-format -msgid "IDE Hard disk / CD-ROM on the first IDE port (Master)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:40 -#, no-c-format -msgid "<filename>hdb</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:41 -#, no-c-format -msgid "IDE Hard disk / CD-ROM on the first IDE port (Slave)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:43 -#, no-c-format -msgid "<filename>hdc</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:44 -#, no-c-format -msgid "IDE Hard disk / CD-ROM on the second IDE port (Master)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:46 -#, no-c-format -msgid "<filename>hdd</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:47 -#, no-c-format -msgid "IDE Hard disk / CD-ROM on the second IDE port (Slave)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:49 -#, no-c-format -msgid "hda1" -msgstr "" - -#. Tag: entry -#: random-bits.xml:50 -#, no-c-format -msgid "First partition of the first IDE hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:52 -#, no-c-format -msgid "hdd15" -msgstr "" - -#. Tag: entry -#: random-bits.xml:53 -#, no-c-format -msgid "Fifteenth partition of the fourth IDE hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:59 -#, no-c-format -msgid "<filename>sda</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:60 -#, no-c-format -msgid "SCSI Hard disk with lowest SCSI ID (e.g. 0)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:62 -#, no-c-format -msgid "<filename>sdb</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:63 -#, no-c-format -msgid "SCSI Hard disk with next higher SCSI ID (e.g. 1)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:65 -#, no-c-format -msgid "<filename>sdc</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:66 -#, no-c-format -msgid "SCSI Hard disk with next higher SCSI ID (e.g. 2)" -msgstr "" - -#. Tag: filename -#: random-bits.xml:68 -#, no-c-format -msgid "sda1" -msgstr "" - -#. Tag: entry -#: random-bits.xml:69 -#, no-c-format -msgid "First partition of the first SCSI hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:71 -#, no-c-format -msgid "sdd10" -msgstr "" - -#. Tag: entry -#: random-bits.xml:72 -#, no-c-format -msgid "Tenth partition of the fourth SCSI hard disk" -msgstr "" - -#. Tag: filename -#: random-bits.xml:78 -#, no-c-format -msgid "<filename>sr0</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:79 -#, no-c-format -msgid "SCSI CD-ROM with the lowest SCSI ID" -msgstr "" - -#. Tag: filename -#: random-bits.xml:81 -#, no-c-format -msgid "<filename>sr1</filename>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:82 -#, no-c-format -msgid "SCSI CD-ROM with the next higher SCSI ID" -msgstr "" - -#. Tag: filename -#: random-bits.xml:88 -#, no-c-format -msgid "ttyS0" -msgstr "" - -#. Tag: entry -#: random-bits.xml:89 -#, no-c-format -msgid "Serial port 0, COM1 under MS-DOS" -msgstr "" - -#. Tag: filename -#: random-bits.xml:91 -#, no-c-format -msgid "ttyS1" -msgstr "" - -#. Tag: entry -#: random-bits.xml:92 -#, no-c-format -msgid "Serial port 1, COM2 under MS-DOS" -msgstr "" - -#. Tag: filename -#: random-bits.xml:94 -#, no-c-format -msgid "psaux" -msgstr "" - -#. Tag: entry -#: random-bits.xml:95 -#, no-c-format -msgid "PS/2 mouse device" -msgstr "" - -#. Tag: filename -#: random-bits.xml:97 -#, no-c-format -msgid "gpmdata" -msgstr "" - -#. Tag: entry -#: random-bits.xml:98 -#, no-c-format -msgid "Pseudo device, repeater data from GPM (mouse) daemon" -msgstr "" - -#. Tag: filename -#: random-bits.xml:104 -#, no-c-format -msgid "cdrom" -msgstr "" - -#. Tag: entry -#: random-bits.xml:105 -#, no-c-format -msgid "Symbolic link to the CD-ROM drive" -msgstr "" - -#. Tag: filename -#: random-bits.xml:107 -#, no-c-format -msgid "mouse" -msgstr "" - -#. Tag: entry -#: random-bits.xml:108 -#, no-c-format -msgid "Symbolic link to the mouse device file" -msgstr "" - -#. Tag: filename -#: random-bits.xml:114 -#, no-c-format -msgid "null" -msgstr "" - -#. Tag: entry -#: random-bits.xml:115 -#, no-c-format -msgid "Everything pointed to this device will disappear" -msgstr "" - -#. Tag: filename -#: random-bits.xml:117 -#, no-c-format -msgid "zero" -msgstr "" - -#. Tag: entry -#: random-bits.xml:118 -#, no-c-format -msgid "One can endlessly read zeros out of this device" -msgstr "" - -#. Tag: title -#: random-bits.xml:125 -#, no-c-format -msgid "Setting Up Your Mouse" -msgstr "" - -#. Tag: para -#: random-bits.xml:127 -#, no-c-format -msgid "" -"The mouse can be used in both the Linux console (with gpm) and the X window " -"environment. The two uses can be made compatible if the gpm repeater is used " -"to allow the signal to flow to the X server as shown: " -"<informalexample><screen>\n" -"mouse => /dev/psaux => gpm => /dev/gpmdata -> /dev/mouse => " -"X\n" -" /dev/ttyS0 (repeater) (symlink)\n" -" /dev/ttyS1\n" -"</screen></informalexample> Set the repeater protocol to be raw (in " -"<filename>/etc/gpm.conf</filename>) while setting X to the original mouse " -"protocol in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/X11/" -"XF86Config-4</filename>." -msgstr "" - -#. Tag: para -#: random-bits.xml:139 -#, no-c-format -msgid "" -"This approach to use gpm even in X has advantages when the mouse is " -"unplugged inadvertently. Simply restarting gpm with " -"<informalexample><screen>\n" -"# /etc/init.d/gpm restart\n" -"</screen></informalexample> will re-connect the mouse in software without " -"restarting X." -msgstr "" - -#. Tag: para -#: random-bits.xml:148 -#, no-c-format -msgid "" -"If gpm is disabled or not installed with some reason, make sure to set X to " -"read directly from the mouse device such as /dev/psaux. For details, refer " -"to the 3-Button Mouse mini-Howto at <filename>/usr/share/doc/HOWTO/en-txt/" -"mini/3-Button-Mouse.gz</filename>, <userinput>man gpm</userinput>, " -"<filename>/usr/share/doc/gpm/FAQ.gz</filename>, and <ulink url=\"&url-xorg;" -"current/doc/html/mouse.html\">README.mouse</ulink>." -msgstr "" - -#. Tag: para -#: random-bits.xml:158 -#, no-c-format -msgid "" -"For PowerPC, in <filename>/etc/X11/XF86Config</filename> or <filename>/etc/" -"X11/XF86Config-4</filename>, set the mouse device to <userinput>\"/dev/input/" -"mice\"</userinput>." -msgstr "" - -#. Tag: para -#: random-bits.xml:164 -#, no-c-format -msgid "" -"Modern kernels give you the capability to emulate a three-button mouse when " -"your mouse only has one button. Just add the following lines to <filename>/" -"etc/sysctl.conf</filename> file." -msgstr "" - -#. Tag: screen -#: random-bits.xml:170 -#, no-c-format -msgid "" -"# 3-button mouse emulation\n" -"# turn on emulation\n" -"/dev/mac_hid/mouse_button_emulation = 1\n" -"# Send middle mouse button signal with the F11 key\n" -"/dev/mac_hid/mouse_button2_keycode = 87\n" -"# Send right mouse button signal with the F12 key\n" -"/dev/mac_hid/mouse_button3_keycode = 88\n" -"# For different keys, use showkey to tell you what the code is." -msgstr "" - -#. Tag: title -#: random-bits.xml:177 -#, no-c-format -msgid "Disk Space Needed for Tasks" -msgstr "" - -#. Tag: para -#: random-bits.xml:189 -#, no-c-format -msgid "" -"The base installation for i386 using the default 2.4 kernel, including all " -"standard packages, requires 573MB of disk space." -msgstr "" - -#. Tag: para -#: random-bits.xml:194 -#, no-c-format -msgid "" -"The following table lists sizes reported by aptitude for the tasks listed in " -"tasksel. Note that some tasks have overlapping constituents, so the total " -"installed size for two tasks together may be less than the total obtained by " -"adding up the numbers." -msgstr "" - -#. Tag: para -#: random-bits.xml:201 -#, no-c-format -msgid "" -"Note that you will need to add the sizes listed in the table to the size of " -"the base installation when determining the size of partitions. Most of the " -"size listed as <quote>Installed size</quote> will end up in <filename>/usr</" -"filename>; the size listed as <quote>Download size</quote> is (temporarily) " -"required in <filename>/var</filename>." -msgstr "" - -#. Tag: entry -#: random-bits.xml:214 -#, no-c-format -msgid "Task" -msgstr "" - -#. Tag: entry -#: random-bits.xml:215 -#, no-c-format -msgid "Installed size (MB)" -msgstr "" - -#. Tag: entry -#: random-bits.xml:216 -#, no-c-format -msgid "Download size (MB)" -msgstr "" - -#. Tag: entry -#: random-bits.xml:217 -#, no-c-format -msgid "Space needed to install (MB)" -msgstr "" - -#. Tag: entry -#: random-bits.xml:223 -#, no-c-format -msgid "Desktop" -msgstr "" - -#. Tag: entry -#: random-bits.xml:224 -#, no-c-format -msgid "1392" -msgstr "" - -#. Tag: entry -#: random-bits.xml:225 -#, no-c-format -msgid "<entry>460</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:226 -#, no-c-format -msgid "1852" -msgstr "" - -#. Tag: entry -#: random-bits.xml:230 -#, no-c-format -msgid "Web server" -msgstr "" - -#. Tag: entry -#: random-bits.xml:231 -#, no-c-format -msgid "<entry>36</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:232 -#, no-c-format -msgid "<entry>12</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:233 -#, no-c-format -msgid "<entry>48</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:237 -#, no-c-format -msgid "Print server" -msgstr "" - -#. Tag: entry -#: random-bits.xml:238 -#, no-c-format -msgid "<entry>168</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:239 -#, no-c-format -msgid "<entry>58</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:240 -#, no-c-format -msgid "<entry>226</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:244 -#, no-c-format -msgid "DNS server" -msgstr "" - -#. Tag: entry -#: random-bits.xml:245 -#, no-c-format -msgid "<entry>2</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:246 -#, no-c-format -msgid "<entry>1</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:247 random-bits.xml:260 -#, no-c-format -msgid "<entry>3</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:251 -#, no-c-format -msgid "File server" -msgstr "" - -#. Tag: entry -#: random-bits.xml:252 -#, no-c-format -msgid "<entry>47</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:253 -#, no-c-format -msgid "<entry>24</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:254 -#, no-c-format -msgid "<entry>71</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:258 -#, no-c-format -msgid "Mail server" -msgstr "" - -#. Tag: entry -#: random-bits.xml:259 -#, no-c-format -msgid "<entry>10</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:261 -#, no-c-format -msgid "<entry>13</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:265 -#, no-c-format -msgid "SQL database" -msgstr "" - -#. Tag: entry -#: random-bits.xml:266 -#, no-c-format -msgid "<entry>66</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:267 -#, no-c-format -msgid "<entry>21</entry>" -msgstr "" - -#. Tag: entry -#: random-bits.xml:268 -#, no-c-format -msgid "<entry>87</entry>" -msgstr "" - -#. Tag: para -#: random-bits.xml:274 -#, no-c-format -msgid "" -"The <emphasis>Desktop</emphasis> task will install both the Gnome and KDE " -"desktop environments." -msgstr "" - -#. Tag: para -#: random-bits.xml:281 -#, no-c-format -msgid "" -"If you install in a language other than English, <command>tasksel</command> " -"may automatically install a <firstterm>localization task</firstterm>, if one " -"is available for your language. Space requirements differ per language; you " -"should allow up to 200MB in total for download and installation." -msgstr "" - -#. Tag: title -#: random-bits.xml:296 -#, no-c-format -msgid "Installing &debian; from a Unix/Linux System" -msgstr "" - -#. Tag: para -#: random-bits.xml:298 -#, no-c-format -msgid "" -"This section explains how to install &debian; from an existing Unix or Linux " -"system, without using the menu-driven installer as explained in the rest of " -"the manual. This <quote>cross-install</quote> HOWTO has been requested by " -"users switching to &debian; from Red Hat, Mandrake, and SUSE. In this " -"section some familiarity with entering *nix commands and navigating the file " -"system is assumed. In this section, <prompt>$</prompt> symbolizes a command " -"to be entered in the user's current system, while <prompt>#</prompt> refers " -"to a command entered in the Debian chroot." -msgstr "" - -#. Tag: para -#: random-bits.xml:310 -#, no-c-format -msgid "" -"Once you've got the new Debian system configured to your preference, you can " -"migrate your existing user data (if any) to it, and keep on rolling. This is " -"therefore a <quote>zero downtime</quote> &debian; install. It's also a " -"clever way for dealing with hardware that otherwise doesn't play friendly " -"with various boot or installation media." -msgstr "" - -#. Tag: title -#: random-bits.xml:322 -#, no-c-format -msgid "Getting Started" -msgstr "" - -#. Tag: para -#: random-bits.xml:323 -#, 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." -msgstr "" - -#. Tag: para -#: random-bits.xml:330 -#, no-c-format -msgid "" -"To 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" -"</screen></informalexample> To create an ext2 file system instead, omit " -"<userinput>-j</userinput>." -msgstr "" - -#. Tag: para -#: random-bits.xml:340 -#, 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" -"# sync; sync; sync\n" -"# swapon /dev/hda5\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:352 -#, no-c-format -msgid "" -"# mkdir /mnt/debinst\n" -"# mount /dev/hda6 /mnt/debinst" -msgstr "" - -#. Tag: para -#: random-bits.xml:355 -#, 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:365 -#, no-c-format -msgid "Install <command>debootstrap</command>" -msgstr "" - -#. Tag: para -#: random-bits.xml:366 -#, no-c-format -msgid "" -"The tool that the Debian installer uses, which is 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:396 -#, 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" -"# mkdir work\n" -"# cd work\n" -"</screen></informalexample> The <command>debootstrap</command> binary is " -"located in the Debian archive (be sure to select the proper file for your " -"architecture). Download the <command>debootstrap</command> .deb from the " -"<ulink url=\"http://ftp.debian.org/debian/pool/main/d/debootstrap/\"> pool</" -"ulink>, copy the package to the work folder, and extract the binary files " -"from it. You will need to have root privileges to install the binaries." -msgstr "" - -#. Tag: screen -#: random-bits.xml:411 -#, no-c-format -msgid "" -"# ar -x debootstrap_0.X.X_arch.deb\n" -"# cd /\n" -"# zcat /full-path-to-work/work/data.tar.gz | tar xv" -msgstr "" - -#. Tag: para -#: random-bits.xml:413 -#, no-c-format -msgid "" -"Note that running <command>debootstrap</command> may require you to have a " -"minimal version of <classname>glibc</classname> installed (currently " -"GLIBC_2.3). <command>debootstrap</command> itself is a shell script, but it " -"calls various utilities that require <classname>glibc</classname>." -msgstr "" - -#. Tag: title -#: random-bits.xml:424 -#, no-c-format -msgid "Run <command>debootstrap</command>" -msgstr "" - -#. Tag: para -#: random-bits.xml:425 -#, 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:434 -#, 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:440 -#, 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>." -msgstr "" - -#. Tag: screen -#: random-bits.xml:457 -#, no-c-format -msgid "" -"# /usr/sbin/debootstrap --arch ARCH &releasename; \\\n" -" /mnt/debinst http://http.us.debian.org/debian" -msgstr "" - -#. Tag: title -#: random-bits.xml:463 -#, no-c-format -msgid "Configure The Base System" -msgstr "" - -#. Tag: para -#: random-bits.xml:464 -#, no-c-format -msgid "" -"Now you've got a real Debian system, though rather lean, on disk. " -"<command>Chroot</command> into it:" -msgstr "" - -#. Tag: screen -#: random-bits.xml:469 -#, no-c-format -msgid "# LANG= chroot /mnt/debinst /bin/bash" -msgstr "" - -#. Tag: title -#: random-bits.xml:474 -#, no-c-format -msgid "Mount Partitions" -msgstr "" - -#. Tag: para -#: random-bits.xml:475 -#, no-c-format -msgid "" -"You need to create <filename>/etc/fstab</filename>. " -"<informalexample><screen>\n" -"# editor /etc/fstab\n" -"</screen></informalexample> Here is a sample you can modify to suit: " -"<informalexample><screen>\n" -"# /etc/fstab: static file system information.\n" -"#\n" -"# file system mount point type options dump pass\n" -"/dev/XXX / ext3 defaults 0 1\n" -"/dev/XXX /boot ext3 ro,nosuid,nodev 0 2\n" -"\n" -"/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" -"\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" -"# mount /path # e.g.: mount /usr\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:495 -#, no-c-format -msgid "# mount -t proc proc /proc" -msgstr "" - -#. Tag: para -#: random-bits.xml:497 -#, 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:503 -#, no-c-format -msgid "# mount -t proc proc /mnt/debinst/proc" -msgstr "" - -#. Tag: title -#: random-bits.xml:509 -#, no-c-format -msgid "Configure Keyboard" -msgstr "" - -#. Tag: para -#: random-bits.xml:510 -#, no-c-format -msgid "To configure your keyboard:" -msgstr "" - -#. Tag: screen -#: random-bits.xml:514 -#, no-c-format -msgid "# dpkg-reconfigure console-data" -msgstr "" - -#. Tag: para -#: random-bits.xml:516 -#, 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:525 -#, no-c-format -msgid "Configure Networking" -msgstr "" - -#. Tag: para -#: random-bits.xml:526 -#, no-c-format -msgid "" -"To configure networking, edit <filename>/etc/network/interfaces</filename>, " -"<filename>/etc/resolv.conf</filename>, and <filename>/etc/hostname</" -"filename>. <informalexample><screen>\n" -"# editor /etc/network/interfaces\n" -"</screen></informalexample> Here are some simple examples from <filename>/" -"usr/share/doc/ifupdown/examples</filename>: <informalexample><screen>\n" -"######################################################################\n" -"# /etc/network/interfaces -- configuration file for ifup(8), ifdown(8)\n" -"# See the interfaces(5) manpage for information on what options are\n" -"# available.\n" -"######################################################################\n" -"\n" -"# We always want the loopback interface.\n" -"#\n" -"auto lo\n" -"iface lo inet loopback\n" -"\n" -"# To use dhcp:\n" -"#\n" -"# auto eth0\n" -"# iface eth0 inet dhcp\n" -"\n" -"# An example static IP setup: (broadcast and gateway are optional)\n" -"#\n" -"# auto eth0\n" -"# iface eth0 inet static\n" -"# address 192.168.0.42\n" -"# network 192.168.0.0\n" -"# netmask 255.255.255.0\n" -"# broadcast 192.168.0.255\n" -"# gateway 192.168.0.1\n" -"</screen></informalexample> Enter your nameserver(s) and search directives " -"in <filename>/etc/resolv.conf</filename>: <informalexample><screen>\n" -"# editor /etc/resolv.conf\n" -"</screen></informalexample> A simple <filename>/etc/resolv.conf</filename>: " -"<informalexample><screen>\n" -"search hqdom.local\\000\n" -"nameserver 10.1.1.36\n" -"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> 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:562 -#, no-c-format -msgid "Configure Locales" -msgstr "" - -#. Tag: para -#: random-bits.xml:563 -#, no-c-format -msgid "" -"To configure your locale settings to use a language other than English, " -"install the locales support package and configure it: " -"<informalexample><screen>\n" -"# apt-get install locales\n" -"# dpkg-reconfigure locales\n" -"</screen></informalexample> NOTE: Apt must be configured beforehand by " -"creating a sources.list and running apt-get update. Before using locales " -"with character sets other than ASCII or latin1, please consult the " -"appropriate localization HOWTO." -msgstr "" - -#. Tag: title -#: random-bits.xml:580 -#, no-c-format -msgid "Install a Kernel" -msgstr "" - -#. Tag: para -#: random-bits.xml:581 -#, 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" -"# apt-cache search kernel-image\n" -"</screen></informalexample> Then install your choice using its package name." -msgstr "" - -#. Tag: screen -#: random-bits.xml:590 -#, no-c-format -msgid "" -"# apt-get install kernel-image-<replaceable>2.X.X-arch-etc</replaceable>" -msgstr "" - -#. Tag: title -#: random-bits.xml:596 -#, no-c-format -msgid "Set up the Boot Loader" -msgstr "" - -#. Tag: para -#: random-bits.xml:597 -#, 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 debootstrap does " -"not install a boot loader, though you can use apt-get inside your Debian " -"chroot to do so." -msgstr "" - -#. Tag: para -#: random-bits.xml:604 -#, 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)." -msgstr "" - -#. Tag: para -#: random-bits.xml:615 -#, no-c-format -msgid "Here is a basic <filename>/etc/lilo.conf</filename> as an example:" -msgstr "" - -#. Tag: screen -#: random-bits.xml:619 -#, no-c-format -msgid "" -"boot=/dev/hda6\n" -"root=/dev/hda6\n" -"install=menu\n" -"delay=20\n" -"lba32\n" -"image=/vmlinuz\n" -"label=Debian" -msgstr "" - -#. Tag: para -#: random-bits.xml:621 -#, 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:631 -#, no-c-format -msgid "" -"Here is a basic <filename>/etc/yaboot.conf</filename> as an example: " -"<informalexample><screen>\n" -"boot=/dev/hda2\n" -"device=hd:\n" -"partition=6\n" -"root=/dev/hda6\n" -"magicboot=/usr/lib/yaboot/ofboot\n" -"timeout=50\n" -"image=/vmlinux\n" -"label=Debian\n" -"</screen></informalexample> On some machines, you may need to use " -"<userinput>ide0:</userinput> instead of <userinput>hd:</userinput>." -msgstr "" - -#. Tag: title -#: random-bits.xml:649 -#, no-c-format -msgid "Installing &debian; over Parallel Line IP (PLIP)" -msgstr "" - -#. Tag: para -#: random-bits.xml:651 -#, no-c-format -msgid "" -"This section explains how to install &debian; on a computer without 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:659 -#, 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:667 -#, 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:672 -#, 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:682 -#, no-c-format -msgid "Requirements" -msgstr "" - -#. Tag: para -#: random-bits.xml:685 -#, no-c-format -msgid "" -"A target computer, called <emphasis>target</emphasis>, where Debian will be " -"installed." -msgstr "" - -#. Tag: para -#: random-bits.xml:691 -#, no-c-format -msgid "System installation media; see <xref linkend=\"installation-media\"/>." -msgstr "" - -#. Tag: para -#: random-bits.xml:696 -#, 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:702 -#, 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:714 -#, no-c-format -msgid "Setting up source" -msgstr "" - -#. Tag: para -#: random-bits.xml:715 -#, 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:720 -#, no-c-format -msgid "" -"#!/bin/sh\n" -"\n" -"# We remove running modules from kernel to avoid conflicts and to\n" -"# reconfigure them manually.\n" -"modprobe -r lp parport_pc\n" -"modprobe parport_pc io=<replaceable>0x378</replaceable> irq=<replaceable>7</" -"replaceable>\n" -"modprobe plip\n" -"\n" -"# Configure the plip interface (plip0 for me, see dmesg | grep plip)\n" -"ifconfig <replaceable>plip0 192.168.0.2</replaceable> pointopoint " -"<replaceable>192.168.0.1</replaceable> netmask 255.255.255.255 up\n" -"\n" -"# Configure gateway\n" -"modprobe iptable_nat\n" -"iptables -t nat -A POSTROUTING -o <replaceable>ppp0</replaceable> -j " -"MASQUERADE\n" -"echo 1 > /proc/sys/net/ipv4/ip_forward" -msgstr "" - -#. Tag: title -#: random-bits.xml:726 -#, no-c-format -msgid "Installing target" -msgstr "" - -#. Tag: para -#: random-bits.xml:727 -#, 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. Below are the " -"answers that should be given during various stages of the installation." -msgstr "" - -#. Tag: guimenuitem -#: random-bits.xml:739 -#, no-c-format -msgid "Load installer components" -msgstr "" - -#. Tag: para -#: random-bits.xml:741 -#, 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:749 -#, no-c-format -msgid "Detect network hardware" -msgstr "" - -#. Tag: para -#: random-bits.xml:754 -#, 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:763 -#, no-c-format -msgid "Prompt for module parameters: Yes" -msgstr "" - -#. Tag: para -#: random-bits.xml:768 -#, 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: para -#: random-bits.xml:775 -#, no-c-format -msgid "" -"Additional parameters for module parport_pc: " -"<userinput><replaceable>io=0x378 irq=7</replaceable></userinput>" -msgstr "" - -#. Tag: para -#: random-bits.xml:781 -#, no-c-format -msgid "Additional parameters for module plip: leave empty" -msgstr "" - -#. Tag: guimenuitem -#: random-bits.xml:791 -#, no-c-format -msgid "Configure the network" -msgstr "" - -#. Tag: para -#: random-bits.xml:794 -#, no-c-format -msgid "Auto-configure network with DHCP: No" -msgstr "" - -#. Tag: para -#: random-bits.xml:799 -#, no-c-format -msgid "" -"IP address: <userinput><replaceable>192.168.0.1</replaceable></userinput>" -msgstr "" - -#. Tag: para -#: random-bits.xml:804 -#, no-c-format -msgid "" -"Point-to-point address: <userinput><replaceable>192.168.0.2</replaceable></" -"userinput>" -msgstr "" - -#. Tag: para -#: random-bits.xml:810 -#, 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/pl/using-d-i.po b/po/pl/using-d-i.po deleted file mode 100644 index 78db9fbd4..000000000 --- a/po/pl/using-d-i.po +++ /dev/null @@ -1,2892 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-03-19 13:45+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: using-d-i.xml:5 -#, no-c-format -msgid "Using the Debian Installer" -msgstr "" - -#. Tag: title -#: using-d-i.xml:7 -#, no-c-format -msgid "How the Installer Works" -msgstr "" - -#. Tag: para -#: using-d-i.xml:8 -#, no-c-format -msgid "" -"The Debian Installer consists of a number of special-purpose components to " -"perform each installation task. Each component performs its task, asking the " -"user questions as necessary to do its job. The questions themselves are " -"given priorities, and the priority of questions to be asked is set when the " -"installer is started." -msgstr "" - -#. Tag: para -#: using-d-i.xml:16 -#, no-c-format -msgid "" -"When a default installation is performed, only essential (high priority) " -"questions will be asked. This results in a highly automated installation " -"process with little user interaction. Components are automatically run in " -"sequence; which components are run depends mainly on the installation method " -"you use and on your hardware. The installer will use default values for " -"questions that are not asked." -msgstr "" - -#. Tag: para -#: using-d-i.xml:25 -#, no-c-format -msgid "" -"If there is a problem, the user will see an error screen, and the installer " -"menu may be shown in order to select some alternative action. If there are " -"no problems, the user will never see the installer menu, but will simply " -"answer questions for each component in turn. Serious error notifications are " -"set to priority <quote>critical</quote> so the user will always be notified." -msgstr "" - -#. Tag: para -#: using-d-i.xml:34 -#, no-c-format -msgid "" -"Some of the defaults that the installer uses can be influenced by passing " -"boot arguments when &d-i; is started. If, for example, you wish to force " -"static network configuration (DHCP is used by default if available), you " -"could add the boot parameter <userinput>netcfg/disable_dhcp=true</" -"userinput>. See <xref linkend=\"installer-args\"/> for available options." -msgstr "" - -#. Tag: para -#: using-d-i.xml:42 -#, no-c-format -msgid "" -"Power users may be more comfortable with a menu-driven interface, where each " -"step is controlled by the user rather than the installer performing each " -"step automatically in sequence. To use the installer in a manual, menu-" -"driven way, add the boot argument <userinput>debconf/priority=medium</" -"userinput>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:50 -#, no-c-format -msgid "" -"If your hardware requires you to pass options to kernel modules as they are " -"installed, you will need to start the installer in <quote>expert</quote> " -"mode. This can be done by either using the <command>expert</command> command " -"to start the installer or by adding the boot argument <userinput>debconf/" -"priority=low</userinput>. Expert mode gives you full control over &d-i;." -msgstr "" - -#. Tag: para -#: using-d-i.xml:59 -#, no-c-format -msgid "" -"The normal installer display is character-based (as opposed to the now more " -"familiar graphical interface). The mouse is not operational in this " -"environment. Here are the keys you can use to navigate within the various " -"dialogs. The <keycap>Tab</keycap> or <keycap>right</keycap> arrow keys move " -"<quote>forward</quote>, and the <keycombo> <keycap>Shift</keycap> " -"<keycap>Tab</keycap> </keycombo> or <keycap>left</keycap> arrow keys move " -"<quote>backward</quote> between displayed buttons and selections. The " -"<keycap>up</keycap> and <keycap>down</keycap> arrow select different items " -"within a scrollable list, and also scroll the list itself. In addition, in " -"long lists, you can type a letter to cause the list to scroll directly to " -"the section with items starting with the letter you typed and use <keycap>Pg-" -"Up</keycap> and <keycap>Pg-Down</keycap> to scroll the list in sections. The " -"<keycap>space bar</keycap> selects an item such as a checkbox. Use " -"&enterkey; to activate choices." -msgstr "" - -#. Tag: para -#: using-d-i.xml:77 -#, no-c-format -msgid "" -"S/390 does not support virtual consoles. You may open a second and third ssh " -"session to view the logs described below." -msgstr "" - -#. Tag: para -#: using-d-i.xml:82 -#, no-c-format -msgid "" -"Error messages and logs are redirected to the fourth console. You can access " -"this console by pressing <keycombo><keycap>Left Alt</keycap><keycap>F4</" -"keycap></keycombo> (hold the left <keycap>Alt</keycap> key while pressing " -"the <keycap>F4</keycap> function key); get back to the main installer " -"process with <keycombo><keycap>Left Alt</keycap><keycap>F1</keycap></" -"keycombo>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:92 -#, no-c-format -msgid "" -"These messages can also be found in <filename>/var/log/syslog</filename>. " -"After installation, this log is copied to <filename>/var/log/installer/" -"syslog</filename> on your new system. Other installation messages may be " -"found in <filename>/var/log/</filename> during the installation, and " -"<filename>/var/log/debian/</filename> after the computer has been booted " -"into the installed system." -msgstr "" - -#. Tag: title -#: using-d-i.xml:106 -#, no-c-format -msgid "Components Introduction" -msgstr "" - -#. Tag: para -#: using-d-i.xml:107 -#, no-c-format -msgid "" -"Here is a list of installer components with a brief description of each " -"component's purpose. Details you might need to know about using a particular " -"component are in <xref linkend=\"module-details\"/>." -msgstr "" - -#. Tag: term -#: using-d-i.xml:118 -#, no-c-format -msgid "main-menu" -msgstr "" - -#. Tag: para -#: using-d-i.xml:118 -#, no-c-format -msgid "" -"Shows the list of components to the user during installer operation, and " -"starts a component when it is selected. Main-menu's questions are set to " -"priority medium, so if your priority is set to high or critical (high is the " -"default), you will not see the menu. On the other hand, if there is an error " -"which requires your intervention, the question priority may be downgraded " -"temporarily to allow you to resolve the problem, and in that case the menu " -"may appear." -msgstr "" - -#. Tag: para -#: using-d-i.xml:128 -#, no-c-format -msgid "" -"You can get to the main menu by selecting the <quote>Back</quote> button " -"repeatedly to back all the way out of the currently running component." -msgstr "" - -#. Tag: term -#: using-d-i.xml:137 -#, no-c-format -msgid "localechooser" -msgstr "" - -#. Tag: para -#: using-d-i.xml:137 -#, no-c-format -msgid "" -"Allows the user to select localization options for the installation and the " -"installed system: language, country and locales. The installer will display " -"messages in the selected language, unless the translation for that language " -"is not complete in which case some messages may be shown in English." -msgstr "" - -#. Tag: term -#: using-d-i.xml:149 -#, no-c-format -msgid "kbd-chooser" -msgstr "" - -#. Tag: para -#: using-d-i.xml:149 -#, no-c-format -msgid "" -"Shows a list of keyboards, from which the user chooses the model which " -"matches his own." -msgstr "" - -#. Tag: term -#: using-d-i.xml:158 -#, no-c-format -msgid "hw-detect" -msgstr "" - -#. Tag: para -#: using-d-i.xml:158 -#, no-c-format -msgid "" -"Automatically detects most of the system's hardware, including network " -"cards, disk drives, and PCMCIA." -msgstr "" - -#. Tag: term -#: using-d-i.xml:167 -#, no-c-format -msgid "cdrom-detect" -msgstr "" - -#. Tag: para -#: using-d-i.xml:167 -#, no-c-format -msgid "Looks for and mounts a Debian installation CD." -msgstr "" - -#. Tag: term -#: using-d-i.xml:175 -#, no-c-format -msgid "netcfg" -msgstr "" - -#. Tag: para -#: using-d-i.xml:175 -#, no-c-format -msgid "" -"Configures the computer's network connections so it can communicate over the " -"internet." -msgstr "" - -#. Tag: term -#: using-d-i.xml:184 -#, no-c-format -msgid "iso-scan" -msgstr "" - -#. Tag: para -#: using-d-i.xml:184 -#, no-c-format -msgid "" -"Looks for ISO file systems, which may be on a CD-ROM or on the hard drive." -msgstr "" - -#. Tag: term -#: using-d-i.xml:193 -#, no-c-format -msgid "choose-mirror" -msgstr "" - -#. Tag: para -#: using-d-i.xml:193 -#, no-c-format -msgid "" -"Presents a list of Debian archive mirrors. The user may choose the source of " -"his installation packages." -msgstr "" - -#. Tag: term -#: using-d-i.xml:202 -#, no-c-format -msgid "cdrom-checker" -msgstr "" - -#. Tag: para -#: using-d-i.xml:202 -#, no-c-format -msgid "" -"Checks integrity of a CD-ROM. This way the user may assure him/herself that " -"the installation CD-ROM was not corrupted." -msgstr "" - -#. Tag: term -#: using-d-i.xml:211 -#, no-c-format -msgid "lowmem" -msgstr "" - -#. Tag: para -#: using-d-i.xml:211 -#, no-c-format -msgid "" -"Lowmem tries to detect systems with low memory and then does various tricks " -"to remove unnecessary parts of &d-i; from the memory (at the cost of some " -"features)." -msgstr "" - -#. Tag: term -#: using-d-i.xml:221 -#, no-c-format -msgid "anna" -msgstr "" - -#. Tag: para -#: using-d-i.xml:221 -#, no-c-format -msgid "" -"Anna's Not Nearly APT. Installs packages which have been retrieved from the " -"chosen mirror or CD." -msgstr "" - -#. Tag: term -#: using-d-i.xml:230 -#, no-c-format -msgid "partman" -msgstr "" - -#. Tag: para -#: using-d-i.xml:230 -#, no-c-format -msgid "" -"Allows the user to partition disks attached to the system, create file " -"systems on the selected partitions, and attach them to the mountpoints. " -"Included are also interesting features like a fully automatic mode or LVM " -"support. This is the preferred partitioning tool in Debian." -msgstr "" - -#. Tag: term -#: using-d-i.xml:242 -#, no-c-format -msgid "autopartkit" -msgstr "" - -#. Tag: para -#: using-d-i.xml:242 -#, no-c-format -msgid "" -"Automatically partitions an entire disk according to preset user preferences." -msgstr "" - -#. Tag: term -#: using-d-i.xml:251 -#, no-c-format -msgid "partitioner" -msgstr "" - -#. Tag: para -#: using-d-i.xml:251 -#, no-c-format -msgid "" -"Allows the user to partition disks attached to the system. A partitioning " -"program appropriate to your computer's architecture is chosen." -msgstr "" - -#. Tag: term -#: using-d-i.xml:261 -#, no-c-format -msgid "partconf" -msgstr "" - -#. Tag: para -#: using-d-i.xml:261 -#, no-c-format -msgid "" -"Displays a list of partitions, and creates file systems on the selected " -"partitions according to user instructions." -msgstr "" - -#. Tag: term -#: using-d-i.xml:270 -#, no-c-format -msgid "lvmcfg" -msgstr "" - -#. Tag: para -#: using-d-i.xml:270 -#, no-c-format -msgid "" -"Helps the user with the configuration of the <firstterm>LVM</firstterm> " -"(Logical Volume Manager)." -msgstr "" - -#. Tag: term -#: using-d-i.xml:279 -#, no-c-format -msgid "mdcfg" -msgstr "" - -#. Tag: para -#: using-d-i.xml:279 -#, no-c-format -msgid "" -"Allows the user to setup Software <firstterm>RAID</firstterm> (Redundant " -"Array of Inexpensive Disks). This Software RAID is usually superior to the " -"cheap IDE (pseudo hardware) RAID controllers found on newer motherboards." -msgstr "" - -#. Tag: term -#: using-d-i.xml:290 -#, no-c-format -msgid "tzsetup" -msgstr "" - -#. Tag: para -#: using-d-i.xml:290 -#, no-c-format -msgid "Selects the time zone, based on the location selected earlier." -msgstr "" - -#. Tag: term -#: using-d-i.xml:298 -#, no-c-format -msgid "clock-setup" -msgstr "" - -#. Tag: para -#: using-d-i.xml:298 -#, no-c-format -msgid "Determines whether the clock is set to UTC or not." -msgstr "" - -#. Tag: term -#: using-d-i.xml:306 -#, no-c-format -msgid "user-setup" -msgstr "" - -#. Tag: para -#: using-d-i.xml:306 -#, no-c-format -msgid "Sets up the root password, and adds a non-root user." -msgstr "" - -#. Tag: term -#: using-d-i.xml:314 -#, no-c-format -msgid "base-installer" -msgstr "" - -#. Tag: para -#: using-d-i.xml:314 -#, no-c-format -msgid "" -"Installs the most basic set of packages which would allow the computer to " -"operate under Linux when rebooted." -msgstr "" - -#. Tag: term -#: using-d-i.xml:323 -#, no-c-format -msgid "apt-setup" -msgstr "" - -#. Tag: para -#: using-d-i.xml:323 -#, no-c-format -msgid "" -"Configures apt, mostly automatically, based on what media the installer is " -"running from." -msgstr "" - -#. Tag: term -#: using-d-i.xml:332 -#, no-c-format -msgid "pkgsel" -msgstr "" - -#. Tag: para -#: using-d-i.xml:332 -#, no-c-format -msgid "" -"Uses <classname>tasksel</classname> to select and install additional " -"software." -msgstr "" - -#. Tag: term -#: using-d-i.xml:340 -#, no-c-format -msgid "os-prober" -msgstr "" - -#. Tag: para -#: using-d-i.xml:340 -#, no-c-format -msgid "" -"Detects currently installed operating systems on the computer and passes " -"this information to the bootloader-installer, which may offer you an ability " -"to add discovered operating systems to the bootloader's start menu. This way " -"the user could easily choose at the boot time which operating system to " -"start." -msgstr "" - -#. Tag: term -#: using-d-i.xml:352 -#, no-c-format -msgid "bootloader-installer" -msgstr "" - -#. Tag: para -#: using-d-i.xml:352 -#, no-c-format -msgid "" -"The various bootloader installers each install a boot loader program on the " -"hard disk, which is necessary for the computer to start up using Linux " -"without using a floppy or CD-ROM. Many boot loaders allow the user to choose " -"an alternate operating system each time the computer boots." -msgstr "" - -#. Tag: term -#: using-d-i.xml:363 -#, no-c-format -msgid "shell" -msgstr "" - -#. Tag: para -#: using-d-i.xml:363 -#, no-c-format -msgid "" -"Allows the user to execute a shell from the menu, or in the second console." -msgstr "" - -#. Tag: term -#: using-d-i.xml:372 -#, no-c-format -msgid "save-logs" -msgstr "" - -#. Tag: para -#: using-d-i.xml:372 -#, no-c-format -msgid "" -"Provides a way for the user to record information on a floppy disk, network, " -"hard disk, or other media when trouble is encountered, in order to " -"accurately report installer software problems to Debian developers later." -msgstr "" - -#. Tag: title -#: using-d-i.xml:390 -#, no-c-format -msgid "Using Individual Components" -msgstr "" - -#. Tag: para -#: using-d-i.xml:391 -#, no-c-format -msgid "" -"In this section we will describe each installer component in detail. The " -"components have been grouped into stages that should be recognizable for " -"users. They are presented in the order they appear during the install. Note " -"that not all modules will be used for every installation; which modules are " -"actually used depends on the installation method you use and on your " -"hardware." -msgstr "" - -#. Tag: title -#: using-d-i.xml:403 -#, no-c-format -msgid "Setting up Debian Installer and Hardware Configuration" -msgstr "" - -#. Tag: para -#: using-d-i.xml:404 -#, no-c-format -msgid "" -"Let's assume the Debian Installer has booted and you are facing its first " -"screen. At this time, the capabilities of &d-i; are still quite limited. It " -"doesn't know much about your hardware, preferred language, or even the task " -"it should perform. Don't worry. Because &d-i; is quite clever, it can " -"automatically probe your hardware, locate the rest of its components and " -"upgrade itself to a capable installation system. However, you still need to " -"help &d-i; with some information it can't determine automatically (like " -"selecting your preferred language, keyboard layout or desired network " -"mirror)." -msgstr "" - -#. Tag: para -#: using-d-i.xml:417 -#, no-c-format -msgid "" -"You will notice that &d-i; performs <firstterm>hardware detection</" -"firstterm> several times during this stage. The first time is targeted " -"specifically at the hardware needed to load installer components (e.g. your " -"CD-ROM or network card). As not all drivers may be available during this " -"first run, hardware detection needs to be repeated later in the process." -msgstr "" - -#. Tag: title -#: using-d-i.xml:432 -#, no-c-format -msgid "Check available memory" -msgstr "" - -#. Tag: para -#: using-d-i.xml:434 -#, no-c-format -msgid "" -"One of the first things &d-i; does, is to check available memory. If the " -"available memory is limited, this component will make some changes in the " -"installation process which hopefully will allow you to install &debian; on " -"your system." -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." -msgstr "" - -#. Tag: title -#: using-d-i.xml:456 -#, no-c-format -msgid "Selecting Localization Options" -msgstr "" - -#. Tag: para -#: using-d-i.xml:458 -#, 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 -#, 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 -#, 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 -#, 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 -#, 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 -#, 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 -#, no-c-format -msgid "Choosing a Keyboard" -msgstr "" - -#. Tag: para -#: using-d-i.xml:526 -#, 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 -#, 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 -#, 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 -#, 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: para -#: using-d-i.xml:564 -#, no-c-format -msgid "" -"If you are installing on a system that has a Sun USB keyboard and have " -"booted the installer with the default 2.4 kernel, the keyboard will not be " -"identified correctly by the installation system. The installer will show you " -"a list of Sun type keymaps to choose from, but selecting one of these will " -"result in a non-working keyboard. If you are installing with the 2.6 kernel, " -"there is no problem." -msgstr "" - -#. Tag: para -#: using-d-i.xml:573 -#, no-c-format -msgid "" -"To get a working keyboard, you should boot the installer with parameter " -"<userinput>debconf/priority=medium</userinput>. When you get to keyboard " -"selection<footnote> <para> If you are installing at default priority you " -"should use the <userinput>Go Back</userinput> button to return to the " -"installer menu when you are shown the list of Sun type keymaps. </para> </" -"footnote>, choose <quote>No keyboard to configure</quote> if you have a " -"keyboard with an American (US) layout, or choose <quote>USB keyboard</quote> " -"if you have a keyboard with a localized layout. Selecting <quote>No keyboard " -"to configure</quote> will leave the kernel keymap in place, which is correct " -"for US keyboards." -msgstr "" - -#. Tag: title -#: using-d-i.xml:611 -#, no-c-format -msgid "Looking for the Debian Installer ISO Image" -msgstr "" - -#. Tag: para -#: using-d-i.xml:612 -#, 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:619 -#, 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:636 -#, 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:643 -#, 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:664 -#, no-c-format -msgid "Configuring Network" -msgstr "" - -#. Tag: para -#: using-d-i.xml:666 -#, 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:677 -#, 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:689 -#, 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:703 -#, 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>. Alternatively, you can install <classname>etherconf</classname>, " -"which will step you through your network setup." -msgstr "" - -#. Tag: title -#: using-d-i.xml:742 -#, no-c-format -msgid "Partitioning and Mount Point Selection" -msgstr "" - -#. Tag: para -#: using-d-i.xml:743 -#, 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:765 -#, no-c-format -msgid "Partitioning Your Disks" -msgstr "" - -#. Tag: para -#: using-d-i.xml:767 -#, 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:773 -#, no-c-format -msgid "" -"First you will be given the opportunity to automatically partition either an " -"entire drive, or free space on a drive. This is also called <quote>guided</" -"quote> partitioning. If you do not want to autopartition, choose " -"<guimenuitem>Manually edit partition table</guimenuitem> from the menu." -msgstr "" - -#. Tag: para -#: using-d-i.xml:781 -#, no-c-format -msgid "" -"If you choose guided partitioning, you will be able to choose from the " -"schemes listed in the table below. All schemes have their pros and cons, " -"some of which are discussed in <xref linkend=\"partitioning\"/>. If you are " -"unsure, choose the first one. Bear in mind, that guided partitioning needs " -"certain minimal amount of free space to operate with. If you don't give it " -"at least about 1GB of space (depends on chosen scheme), guided partitioning " -"will fail." -msgstr "" - -#. Tag: entry -#: using-d-i.xml:797 -#, no-c-format -msgid "Partitioning scheme" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:798 -#, no-c-format -msgid "Minimum space" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:799 -#, no-c-format -msgid "Created partitions" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:805 -#, no-c-format -msgid "All files in one partition" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:806 -#, no-c-format -msgid "600MB" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:807 -#, no-c-format -msgid "<filename>/</filename>, swap" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:809 -#, no-c-format -msgid "Desktop machine" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:810 -#, no-c-format -msgid "500MB" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:811 -#, no-c-format -msgid "<filename>/</filename>, <filename>/home</filename>, swap" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:815 -#, no-c-format -msgid "Multi-user workstation" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:816 -#, no-c-format -msgid "<entry>1GB</entry>" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:817 -#, 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:826 -#, no-c-format -msgid "" -"If you chose an automatic partitioning for your IA64 system, there will be " -"an additional partition, formatted as a FAT16 bootable filesystem, for the " -"EFI boot loader. There is also an additional menu item in the formatting " -"menu to manually set up a partition as an EFI boot partition." -msgstr "" - -#. Tag: para -#: using-d-i.xml:834 -#, no-c-format -msgid "" -"If you chose an automatic partitioning for your Alpha system, an additional, " -"unformatted partition will be allocated at the beginning of your disk to " -"reserve this space for the aboot boot loader." -msgstr "" - -#. Tag: para -#: using-d-i.xml:840 -#, 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:846 -#, no-c-format -msgid "" -"The list of partitions might look like this: <informalexample><screen>\n" -" IDE1 master (hda) - 6.4 GB WDC AC36400L\n" -" #1 primary 16.4 MB ext2 /boot\n" -" #2 primary 551.0 MB swap swap\n" -" #3 primary 5.8 GB ntfs\n" -" pri/log 8.2 MB FREE SPACE\n" -"\n" -" IDE1 slave (hdb) - 80.0 GB ST380021A\n" -" #1 primary 15.9 MB ext3\n" -" #2 primary 996.0 MB fat16\n" -" #3 primary 3.9 GB xfs /home\n" -" #5 logical 6.0 GB ext3 /\n" -" #6 logical 1.0 GB ext3 /var\n" -" #7 logical 498.8 MB ext3\n" -" #8 logical 551.5 MB swap swap\n" -" #9 logical 65.8 GB ext2\n" -"</screen></informalexample> This example shows two IDE harddrives divided " -"into several partitions; the first disk has some free space. Each partition " -"line consists of the partition number, its type, size, optional flags, file " -"system, and mountpoint (if any)." -msgstr "" - -#. Tag: para -#: using-d-i.xml:858 -#, 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>, to run guided partitioning again or modify the proposed " -"changes as described below for manual partitioning." -msgstr "" - -#. Tag: para -#: using-d-i.xml:868 -#, 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:876 -#, no-c-format -msgid "" -"If you select a pristine disk which doesn't have neither partitions nor free " -"space on it, you will be offered to create a new partition table (this is " -"needed so you can create new partitions). After this a new line entitled " -"<quote>FREE SPACE</quote> should appear under the selected disk." -msgstr "" - -#. Tag: para -#: using-d-i.xml:884 -#, 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 the <command>partman</command>'s main screen." -msgstr "" - -#. Tag: para -#: using-d-i.xml:902 -#, 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." -msgstr "" - -#. Tag: para -#: using-d-i.xml:913 -#, 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:921 -#, 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:927 -#, 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:935 -#, 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:963 -#, no-c-format -msgid "Configuring Logical Volume Manager (LVM)" -msgstr "" - -#. Tag: para -#: using-d-i.xml:964 -#, 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:972 -#, 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 disc (so called " -"<firstterm>volume group</firstterm>), which can then be divided into virtual " -"partitions (<firstterm>logical volumes</firstterm>). The point is that " -"logical volumes (and of course underlying volume groups) can span across " -"several physical discs." -msgstr "" - -#. Tag: para -#: using-d-i.xml:982 -#, 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 disc to the computer, " -"join it with your existing volume group and then resize the logical volume " -"which holds your <filename>/home</filename> filesystem and voila — " -"your users have some room again on their renewed 460GB partition. This " -"example is of course a bit oversimplified. If you haven't read it yet, you " -"should consult the <ulink url=\"&url-lvm-howto;\">LVM HOWTO</ulink>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:993 -#, no-c-format -msgid "" -"LVM setup in &d-i; is quite simple. At first, you have to mark your " -"partitions to be used as physical volumes for LVM. (This is done in " -"<command>partman</command> in the <guimenu>Partition settings</guimenu> menu " -"where you should select <menuchoice> <guimenu>Use as:</guimenu> " -"<guimenuitem>physical volume for LVM</guimenuitem> </menuchoice>.) Then " -"start the <command>lvmcfg</command> module (either directly from " -"<command>partman</command> or from the &d-i;'s main menu) and combine " -"physical volumes to volume group(s) under the <guimenuitem>Modify volume " -"groups (VG)</guimenuitem> menu. After that, you should create logical " -"volumes on the top of volume groups from the menu <guimenuitem>Modify " -"logical volumes (LV)</guimenuitem>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1008 -#, no-c-format -msgid "" -"After returning from <command>lvmcfg</command> back to <command>partman</" -"command>, you will see any created logical volumes in the same way as " -"ordinary partitions (and you should treat them like that)." -msgstr "" - -#. Tag: title -#: using-d-i.xml:1023 -#, no-c-format -msgid "Configuring Multidisk Device (Software RAID)" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1024 -#, 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:1038 -#, 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:1046 -#, 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:" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1124 -#, no-c-format -msgid "Type" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1125 -#, no-c-format -msgid "Minimum Devices" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1126 -#, no-c-format -msgid "Spare Device" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1127 -#, no-c-format -msgid "Survives disk failure?" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1128 -#, no-c-format -msgid "Available Space" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1134 -#, no-c-format -msgid "RAID0" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1135 using-d-i.xml:1143 -#, no-c-format -msgid "<entry>2</entry>" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1136 using-d-i.xml:1137 -#, no-c-format -msgid "<entry>no</entry>" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1138 -#, no-c-format -msgid "Size of the smallest partition multiplied by number of devices in RAID" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1142 -#, no-c-format -msgid "RAID1" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1144 using-d-i.xml:1152 -#, no-c-format -msgid "optional" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1145 using-d-i.xml:1153 -#, no-c-format -msgid "<entry>yes</entry>" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1146 -#, no-c-format -msgid "Size of the smallest partition in RAID" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1150 -#, no-c-format -msgid "RAID5" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1151 -#, no-c-format -msgid "<entry>3</entry>" -msgstr "" - -#. Tag: entry -#: using-d-i.xml:1154 -#, 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:1162 -#, 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>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1167 -#, 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:1176 -#, 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:1185 -#, no-c-format -msgid "" -"Next, you should choose <guimenuitem>Configure software RAID</guimenuitem> " -"from the main <command>partman</command> menu. On the first screen of " -"<command>mdcfg</command> simply select <guimenuitem>Create MD device</" -"guimenuitem>. You will be presented with a list of supported types of MD " -"devices, from which you should choose one (e.g. RAID1). What follows depends " -"on the type of MD you selected." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1196 -#, 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:1203 -#, 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:1215 -#, 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:1223 -#, 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 disk into the " -"RAID0 (fast 300 GB video editing partition) and use the other three " -"partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition " -"for <filename>/home</filename>)." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1232 -#, 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:1245 -#, no-c-format -msgid "Setting up the System" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1246 -#, 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:1258 -#, no-c-format -msgid "Configuring Your Time Zone" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1260 -#, 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:1276 -#, no-c-format -msgid "Configuring the Clock" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1278 -#, 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:1285 -#, 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=\"i386\">Systems that (also) run Dos " -"or Windows are normally set to local time. If you want to dual-boot, select " -"local time instead of GMT.</phrase>" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1296 -#, 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:1312 -#, no-c-format -msgid "Setting Up Users And Passwords" -msgstr "" - -#. Tag: title -#: using-d-i.xml:1315 -#, no-c-format -msgid "Set the Root Password" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1317 -#, 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:1325 -#, 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:1333 -#, 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:1343 -#, no-c-format -msgid "Create an Ordinary User" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1345 -#, 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:1352 -#, 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:1362 -#, 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:1369 -#, 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:1381 -#, no-c-format -msgid "Installing the Base System" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1382 -#, 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:1396 -#, no-c-format -msgid "Base System Installation" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1398 -#, 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>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1408 -#, 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." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1414 -#, 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:1427 -#, no-c-format -msgid "Installing Additional Software" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1428 -#, 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." -msgstr "" - -#. Tag: title -#: using-d-i.xml:1442 -#, no-c-format -msgid "Configuring apt" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1444 -#, 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." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1468 -#, 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:1484 -#, no-c-format -msgid "Selecting and Installing Software" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1486 -#, 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:1495 -#, 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 (or remove) " -"more packages, or you can use a more fine-grained tool such as " -"<command>aptitude</command>. If you are looking for a specific single " -"package, after installation is complete, simply run <userinput>aptitude " -"install <replaceable>package</replaceable></userinput>, where " -"<replaceable>package</replaceable> is the name of the package you are " -"looking for. </para> </footnote>. <xref linkend=\"tasksel-size-list\"/> " -"lists the space requirements for the available tasks." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1520 -#, no-c-format -msgid "" -"Once you've selected your tasks, select <guibutton>Ok</guibutton>. At this " -"point, <command>aptitude</command> will install the packages you've selected." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1527 -#, 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:1534 -#, no-c-format -msgid "" -"Note that some tasks may be pre-selected based on the characteristics of the " -"computer you are installing. If you disagree with these selections you can " -"un-select the tasks. You can even opt to install no tasks at all at this " -"point." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1542 -#, 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:1551 -#, no-c-format -msgid "Configuring Your Mail Transport Agent" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1553 -#, 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:1561 -#, 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:1569 -#, 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:1578 -#, no-c-format -msgid "internet site" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1579 -#, 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:1590 -#, no-c-format -msgid "mail sent by smarthost" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1591 -#, 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:1604 -#, no-c-format -msgid "local delivery only" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1605 -#, 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:1618 -#, no-c-format -msgid "no configuration at this time" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1619 -#, 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:1630 -#, 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:1645 -#, no-c-format -msgid "Making Your System Bootable" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1647 -#, 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:1655 -#, 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." -msgstr "" - -#. Tag: title -#: using-d-i.xml:1670 -#, no-c-format -msgid "Detecting other operating systems" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1672 -#, 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:1680 -#, 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:1698 -#, no-c-format -msgid "Install <command>aboot</command> on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1699 -#, 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." -msgstr "" - -#. Tag: title -#: using-d-i.xml:1719 -#, no-c-format -msgid "<command>palo</command>-installer" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1720 -#, 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:1729 -#, no-c-format -msgid "hppa FIXME ( need more info )" -msgstr "" - -#. Tag: title -#: using-d-i.xml:1741 -#, no-c-format -msgid "Install the <command>Grub</command> Boot Loader on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1743 -#, 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:1749 -#, 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:1755 -#, 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:1769 -#, no-c-format -msgid "Install the <command>LILO</command> Boot Loader on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1771 -#, 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:1781 -#, 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:1789 -#, no-c-format -msgid "" -"&d-i; presents you three choices where to install the <command>LILO</" -"command> boot loader:" -msgstr "" - -#. Tag: term -#: using-d-i.xml:1796 -#, no-c-format -msgid "Master Boot Record (MBR)" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1796 -#, 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:1803 -#, no-c-format -msgid "new Debian partition" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1803 -#, 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:1812 -#, no-c-format -msgid "Other choice" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1812 -#, 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:1824 -#, 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! For more information on this please read <xref linkend=" -"\"reactivating-win\"/>." -msgstr "" - -#. Tag: title -#: using-d-i.xml:1841 -#, no-c-format -msgid "Install the <command>ELILO</command> Boot Loader on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1843 -#, 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." -msgstr "" - -#. Tag: para -#: using-d-i.xml:1859 -#, 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:1871 -#, no-c-format -msgid "Choose the correct partition!" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1873 -#, 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!" -msgstr "" - -#. Tag: title -#: using-d-i.xml:1888 -#, no-c-format -msgid "EFI Partition Contents" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1890 -#, 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:1912 -#, no-c-format -msgid "elilo.conf" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1913 -#, 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:1922 -#, no-c-format -msgid "elilo.efi" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1923 -#, 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:1933 -#, no-c-format -msgid "initrd.img" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1934 -#, 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:1946 -#, no-c-format -msgid "readme.txt" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1947 -#, 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:1957 -#, no-c-format -msgid "vmlinuz" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1958 -#, 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:1978 -#, no-c-format -msgid "<command>arcboot</command>-installer" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1979 -#, 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" -"<userinput> setenv SystemPartition scsi(<replaceable>scsi</replaceable>)disk" -"(<replaceable>disk</replaceable>)rdisk(0)partition(0)</userinput>\n" -"<userinput> setenv OSLoadPartition scsi(<replaceable>scsi</replaceable>)disk" -"(<replaceable>disk</replaceable>)rdisk(0)partition(<replaceable>partnr</" -"replaceable>)</userinput>\n" -"<userinput> setenv OSLoader arcboot</userinput>\n" -"<userinput> setenv OSLoadFilename <replaceable>config</replaceable></" -"userinput>\n" -"<userinput> setenv AutoLoad yes</userinput>\n" -"</screen></informalexample> on the firmware prompt, and then typing " -"<command>boot</command>." -msgstr "" - -#. Tag: replaceable -#: using-d-i.xml:1998 -#, no-c-format -msgid "scsi" -msgstr "" - -#. Tag: para -#: using-d-i.xml:1999 -#, 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:2007 -#, no-c-format -msgid "disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2008 -#, 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:2016 using-d-i.xml:2085 -#, no-c-format -msgid "partnr" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2017 -#, 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:2025 -#, no-c-format -msgid "config" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2026 -#, 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:2047 -#, no-c-format -msgid "<command>delo</command>-installer" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2048 -#, 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" -"<userinput>boot <replaceable>#</replaceable>/rz<replaceable>id</replaceable> " -"<replaceable>partnr</replaceable>/<replaceable>name</replaceable></" -"userinput>\n" -"</screen></informalexample> on the firmware prompt." -msgstr "" - -#. Tag: replaceable -#: using-d-i.xml:2067 -#, no-c-format -msgid "<replaceable>#</replaceable>" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2068 -#, 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:2076 -#, no-c-format -msgid "<replaceable>id</replaceable>" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2077 -#, 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:2086 -#, 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:2094 -#, no-c-format -msgid "name" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2095 -#, 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:2105 -#, 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:2111 -#, no-c-format -msgid "<userinput>boot #/rz<replaceable>id</replaceable></userinput>" -msgstr "" - -#. Tag: title -#: using-d-i.xml:2121 -#, no-c-format -msgid "Install <command>Yaboot</command> on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2122 -#, 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:2140 -#, no-c-format -msgid "Install <command>Quik</command> on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2141 -#, 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:2157 -#, no-c-format -msgid "<command>zipl</command>-installer" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2158 -#, 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:2175 -#, no-c-format -msgid "Install the <command>SILO</command> Boot Loader on a Hard Disk" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2177 -#, 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:2202 -#, no-c-format -msgid "Continue Without Boot Loader" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2204 -#, 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:2213 -#, 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:2230 -#, no-c-format -msgid "Finishing the Installation" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2231 -#, 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:2243 -#, no-c-format -msgid "Finish the Installation and Reboot" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2245 -#, 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:2252 -#, 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:2266 -#, no-c-format -msgid "Miscellaneous" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2267 -#, 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:2280 -#, no-c-format -msgid "Saving the installation logs" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2282 -#, 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:2289 -#, 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:2309 -#, no-c-format -msgid "Using the Shell and Viewing the Logs" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2312 -#, 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>." -msgstr "" - -#. Tag: para -#: using-d-i.xml:2324 -#, 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." -msgstr "" - -#. Tag: para -#: using-d-i.xml:2333 -#, 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." -msgstr "" - -#. Tag: title -#: using-d-i.xml:2352 -#, no-c-format -msgid "Installation Over the Network" -msgstr "" - -#. Tag: para -#: using-d-i.xml:2354 -#, 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:2364 -#, 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:2377 -#, 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:2382 -#, 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:2394 -#, 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:2400 -#, 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" -"<prompt>$</prompt> <userinput>ssh -l installer <replaceable>install_host</" -"replaceable></userinput>\n" -"</screen></informalexample> Where <replaceable>install_host</replaceable> is " -"either the name or IP address of the computer being installed. Before the " -"actual login the fingerprint of the remote system will be displayed and you " -"will have to confirm that it is correct." -msgstr "" - -#. Tag: para -#: using-d-i.xml:2417 -#, 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:2426 -#, 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:2436 -#, 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:2444 -#, 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 "" diff --git a/po/pl/welcome.po b/po/pl/welcome.po deleted file mode 100644 index cf0eee9ef..000000000 --- a/po/pl/welcome.po +++ /dev/null @@ -1,676 +0,0 @@ -# SOME DESCRIPTIVE TITLE. -# Copyright (C) YEAR Free Software Foundation, Inc. -# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. -# -#, fuzzy -msgid "" -msgstr "" -"Project-Id-Version: PACKAGE VERSION\n" -"Report-Msgid-Bugs-To: http://bugs.kde.org\n" -"POT-Creation-Date: 2006-01-31 23:11+0000\n" -"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" -"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n" -"Language-Team: LANGUAGE <LL@li.org>\n" -"MIME-Version: 1.0\n" -"Content-Type: application/x-xml2pot; charset=UTF-8\n" -"Content-Transfer-Encoding: ENCODING\n" - -#. Tag: title -#: welcome.xml:4 -#, no-c-format -msgid "Welcome to Debian" -msgstr "" - -#. Tag: para -#: welcome.xml:5 -#, no-c-format -msgid "" -"This chapter provides an overview of the Debian Project and &debian;. If you " -"already know about the Debian Project's history and the &debian; " -"distribution, feel free to skip to the next chapter." -msgstr "" - -#. Tag: title -#: welcome.xml:19 -#, no-c-format -msgid "What is Debian?" -msgstr "" - -#. Tag: para -#: welcome.xml:20 -#, no-c-format -msgid "" -"Debian is an all-volunteer organization dedicated to developing free " -"software and promoting the ideals of the Free Software Foundation. The " -"Debian Project began in 1993, when Ian Murdock issued an open invitation to " -"software developers to contribute to a complete and coherent software " -"distribution based on the relatively new Linux kernel. That relatively small " -"band of dedicated enthusiasts, originally funded by the <ulink url=\"&url-" -"fsf-intro;\">Free Software Foundation</ulink> and influenced by the <ulink " -"url=\"&url-gnu-intro;\">GNU</ulink> philosophy, has grown over the years " -"into an organization of around &num-of-debian-developers; <firstterm>Debian " -"Developers</firstterm>." -msgstr "" - -#. Tag: para -#: welcome.xml:35 -#, no-c-format -msgid "" -"Debian Developers are involved in a variety of activities, including <ulink " -"url=\"&url-debian-home;\">Web</ulink> and <ulink url=\"&url-debian-ftp;" -"\">FTP</ulink> site administration, graphic design, legal analysis of " -"software licenses, writing documentation, and, of course, maintaining " -"software packages." -msgstr "" - -#. Tag: para -#: welcome.xml:44 -#, no-c-format -msgid "" -"In the interest of communicating our philosophy and attracting developers " -"who believe in the principles that Debian stands for, the Debian Project has " -"published a number of documents that outline our values and serve as guides " -"to what it means to be a Debian Developer:" -msgstr "" - -#. Tag: para -#: welcome.xml:52 -#, no-c-format -msgid "" -"The <ulink url=\"&url-social-contract;\">Debian Social Contract</ulink> is a " -"statement of Debian's commitments to the Free Software Community. Anyone who " -"agrees to abide to the Social Contract may become a <ulink url=\"&url-new-" -"maintainer;\">maintainer</ulink>. Any maintainer can introduce new software " -"into Debian — provided that the software meets our criteria for being " -"free, and the package follows our quality standards." -msgstr "" - -#. Tag: para -#: welcome.xml:64 -#, no-c-format -msgid "" -"The <ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink> are a " -"clear and concise statement of Debian's criteria for free software. The DFSG " -"is a very influential document in the Free Software Movement, and was the " -"foundation of the <ulink url=\"&url-osd;\">The Open Source Definition</" -"ulink>." -msgstr "" - -#. Tag: para -#: welcome.xml:74 -#, no-c-format -msgid "" -"The <ulink url=\"&url-debian-policy;\">Debian Policy Manual</ulink> is an " -"extensive specification of the Debian Project's standards of quality." -msgstr "" - -#. Tag: para -#: welcome.xml:82 -#, no-c-format -msgid "" -"Debian developers are also involved in a number of other projects; some " -"specific to Debian, others involving some or all of the Linux community. " -"Some examples include:" -msgstr "" - -#. Tag: para -#: welcome.xml:89 -#, no-c-format -msgid "" -"The <ulink url=\"&url-lsb-org;\">Linux Standard Base</ulink> (LSB) is a " -"project aimed at standardizing the basic GNU/Linux system, which will enable " -"third-party software and hardware developers to easily design programs and " -"device drivers for Linux-in-general, rather than for a specific GNU/Linux " -"distribution." -msgstr "" - -#. Tag: para -#: welcome.xml:99 -#, no-c-format -msgid "" -"The <ulink url=\"&url-fhs-home;\">Filesystem Hierarchy Standard</ulink> " -"(FHS) is an effort to standardize the layout of the Linux file system. The " -"FHS will allow software developers to concentrate their efforts on designing " -"programs, without having to worry about how the package will be installed in " -"different GNU/Linux distributions." -msgstr "" - -#. Tag: para -#: welcome.xml:109 -#, no-c-format -msgid "" -"<ulink url=\"&url-debian-jr;\">Debian Jr.</ulink> is an internal project, " -"aimed at making sure Debian has something to offer to our youngest users." -msgstr "" - -#. Tag: para -#: welcome.xml:118 -#, no-c-format -msgid "" -"For more general information about Debian, see the <ulink url=\"&url-debian-" -"faq;\">Debian FAQ</ulink>." -msgstr "" - -#. Tag: title -#: welcome.xml:133 -#, no-c-format -msgid "What is GNU/Linux?" -msgstr "" - -#. Tag: para -#: welcome.xml:134 -#, no-c-format -msgid "" -"Linux is an operating system: a series of programs that let you interact " -"with your computer and run other programs." -msgstr "" - -#. Tag: para -#: welcome.xml:139 -#, no-c-format -msgid "" -"An operating system consists of various fundamental programs which are " -"needed by your computer so that it can communicate and receive instructions " -"from users; read and write data to hard disks, tapes, and printers; control " -"the use of memory; and run other software. The most important part of an " -"operating system is the kernel. In a GNU/Linux system, Linux is the kernel " -"component. The rest of the system consists of other programs, many of which " -"were written by or for the GNU Project. Because the Linux kernel alone does " -"not form a working operating system, we prefer to use the term <quote>GNU/" -"Linux</quote> to refer to systems that many people casually refer to as " -"<quote>Linux</quote>." -msgstr "" - -#. Tag: para -#: welcome.xml:153 -#, no-c-format -msgid "" -"Linux is modelled on the Unix operating system. From the start, Linux was " -"designed to be a multi-tasking, multi-user system. These facts are enough to " -"make Linux different from other well-known operating systems. However, Linux " -"is even more different than you might imagine. In contrast to other " -"operating systems, nobody owns Linux. Much of its development is done by " -"unpaid volunteers." -msgstr "" - -#. Tag: para -#: welcome.xml:162 -#, no-c-format -msgid "" -"Development of what later became GNU/Linux began in 1984, when the <ulink " -"url=\"http://www.gnu.org/\">Free Software Foundation</ulink> began " -"development of a free Unix-like operating system called GNU." -msgstr "" - -#. Tag: para -#: welcome.xml:168 -#, no-c-format -msgid "" -"The GNU Project has developed a comprehensive set of free software tools for " -"use with Unix™ and Unix-like operating systems such as Linux. These " -"tools enable users to perform tasks ranging from the mundane (such as " -"copying or removing files from the system) to the arcane (such as writing " -"and compiling programs or doing sophisticated editing in a variety of " -"document formats)." -msgstr "" - -#. Tag: para -#: welcome.xml:177 -#, no-c-format -msgid "" -"While many groups and individuals have contributed to Linux, the largest " -"single contributor is still the Free Software Foundation, which created not " -"only most of the tools used in Linux, but also the philosophy and the " -"community that made Linux possible." -msgstr "" - -#. Tag: para -#: welcome.xml:184 -#, no-c-format -msgid "" -"The <ulink url=\"&url-kernel-org;\">Linux kernel</ulink> first appeared in " -"1991, when a Finnish computing science student named Linus Torvalds " -"announced an early version of a replacement kernel for Minix to the Usenet " -"newsgroup <userinput>comp.os.minix</userinput>. See Linux International's " -"<ulink url=\"&url-linux-history;\">Linux History Page</ulink>." -msgstr "" - -#. Tag: para -#: welcome.xml:193 -#, no-c-format -msgid "" -"Linus Torvalds continues to coordinate the work of several hundred " -"developers with the help of a few trusty deputies. An excellent weekly " -"summary of discussions on the <userinput>linux-kernel</userinput> mailing " -"list is <ulink url=\"&url-kernel-traffic;\">Kernel Traffic</ulink>. More " -"information about the <userinput>linux-kernel</userinput> mailing list can " -"be found on the <ulink url=\"&url-linux-kernel-list-faq;\">linux-kernel " -"mailing list FAQ</ulink>." -msgstr "" - -#. Tag: para -#: welcome.xml:204 -#, no-c-format -msgid "" -"Linux users have immense freedom of choice in their software. For example, " -"Linux users can choose from a dozen different command line shells and " -"several graphical desktops. This selection is often bewildering to users of " -"other operating systems, who are not used to thinking of the command line or " -"desktop as something that they can change." -msgstr "" - -#. Tag: para -#: welcome.xml:213 -#, no-c-format -msgid "" -"Linux is also less likely to crash, better able to run more than one program " -"at the same time, and more secure than many operating systems. With these " -"advantages, Linux is the fastest growing operating system in the server " -"market. More recently, Linux has begun to be popular among home and business " -"users as well." -msgstr "" - -#. Tag: title -#: welcome.xml:231 -#, no-c-format -msgid "What is &debian;?" -msgstr "" - -#. Tag: para -#: welcome.xml:232 -#, no-c-format -msgid "" -"The combination of Debian's philosophy and methodology and the GNU tools, " -"the Linux kernel, and other important free software, form a unique software " -"distribution called &debian;. This distribution is made up of a large number " -"of software <emphasis>packages</emphasis>. Each package in the distribution " -"contains executables, scripts, documentation, and configuration information, " -"and has a <emphasis>maintainer</emphasis> who is primarily responsible for " -"keeping the package up-to-date, tracking bug reports, and communicating with " -"the upstream author(s) of the packaged software. Our extremely large user " -"base, combined with our bug tracking system ensures that problems are found " -"and fixed quickly." -msgstr "" - -#. Tag: para -#: welcome.xml:246 -#, no-c-format -msgid "" -"Debian's attention to detail allows us to produce a high-quality, stable, " -"and scalable distribution. Installations can be easily configured to serve " -"many roles, from stripped-down firewalls to desktop scientific workstations " -"to high-end network servers." -msgstr "" - -#. Tag: para -#: welcome.xml:253 -#, no-c-format -msgid "" -"Debian is especially popular among advanced users because of its technical " -"excellence and its deep commitment to the needs and expectations of the " -"Linux community. Debian also introduced many features to Linux that are now " -"commonplace." -msgstr "" - -#. Tag: para -#: welcome.xml:260 -#, no-c-format -msgid "" -"For example, Debian was the first Linux distribution to include a package " -"management system for easy installation and removal of software. It was also " -"the first Linux distribution that could be upgraded without requiring " -"reinstallation." -msgstr "" - -#. Tag: para -#: welcome.xml:267 -#, no-c-format -msgid "" -"Debian continues to be a leader in Linux development. Its development " -"process is an example of just how well the Open Source development model can " -"work — even for very complex tasks such as building and maintaining a " -"complete operating system." -msgstr "" - -#. Tag: para -#: welcome.xml:274 -#, no-c-format -msgid "" -"The feature that most distinguishes Debian from other Linux distributions is " -"its package management system. These tools give the administrator of a " -"Debian system complete control over the packages installed on that system, " -"including the ability to install a single package or automatically update " -"the entire operating system. Individual packages can also be protected from " -"being updated. You can even tell the package management system about " -"software you have compiled yourself and what dependencies it fulfills." -msgstr "" - -#. Tag: para -#: welcome.xml:285 -#, no-c-format -msgid "" -"To protect your system against <quote>Trojan horses</quote> and other " -"malevolent software, Debian's servers verify that uploaded packages come " -"from their registered Debian maintainers. Debian packagers also take great " -"care to configure their packages in a secure manner. When security problems " -"in shipped packages do appear, fixes are usually available very quickly. " -"With Debian's simple update options, security fixes can be downloaded and " -"installed automatically across the Internet." -msgstr "" - -#. Tag: para -#: welcome.xml:295 -#, no-c-format -msgid "" -"The primary, and best, method of getting support for your &debian; system " -"and communicating with Debian Developers is through the many mailing lists " -"maintained by the Debian Project (there are more than &num-of-debian-" -"maillists; at this writing). The easiest way to subscribe to one or more of " -"these lists is visit <ulink url=\"&url-debian-lists-subscribe;\"> Debian's " -"mailing list subscription page</ulink> and fill out the form you'll find " -"there." -msgstr "" - -#. Tag: title -#: welcome.xml:317 -#, no-c-format -msgid "What is Debian GNU/Hurd?" -msgstr "" - -#. Tag: para -#: welcome.xml:319 -#, no-c-format -msgid "" -"Debian GNU/Hurd is a Debian GNU system that replaces the Linux monolithic " -"kernel with the GNU Hurd — a set of servers running on top of the GNU " -"Mach microkernel. The Hurd is still unfinished, and is unsuitable for day-to-" -"day use, but work is continuing. The Hurd is currently only being developed " -"for the i386 architecture, although ports to other architectures will be " -"made once the system becomes more stable." -msgstr "" - -#. Tag: para -#: welcome.xml:329 -#, no-c-format -msgid "" -"For more information, see the <ulink url=\"http://www.debian.org/ports/hurd/" -"\"> Debian GNU/Hurd ports page</ulink> and the <email>debian-hurd@lists." -"debian.org</email> mailing list." -msgstr "" - -#. Tag: title -#: welcome.xml:346 -#, no-c-format -msgid "Getting Debian" -msgstr "" - -#. Tag: para -#: welcome.xml:348 -#, no-c-format -msgid "" -"For information on how to download &debian; from the Internet or from whom " -"official Debian CDs can be purchased, see the <ulink url=\"&url-debian-" -"distrib;\">distribution web page</ulink>. The <ulink url=\"&url-debian-" -"mirrors;\">list of Debian mirrors</ulink> contains a full set of official " -"Debian mirrors, so you can easily find the nearest one." -msgstr "" - -#. Tag: para -#: welcome.xml:357 -#, no-c-format -msgid "" -"Debian can be upgraded after installation very easily. The installation " -"procedure will help set up the system so that you can make those upgrades " -"once installation is complete, if need be." -msgstr "" - -#. Tag: title -#: welcome.xml:372 -#, no-c-format -msgid "Getting the Newest Version of This Document" -msgstr "" - -#. Tag: para -#: welcome.xml:374 -#, no-c-format -msgid "" -"This document is constantly being revised. Be sure to check the <ulink url=" -"\"&url-release-area;\"> Debian &release; pages</ulink> for any last-minute " -"information about the &release; release of the &debian; system. Updated " -"versions of this installation manual are also available from the <ulink url=" -"\"&url-install-manual;\">official Install Manual pages</ulink>." -msgstr "" - -#. Tag: title -#: welcome.xml:392 -#, no-c-format -msgid "Organization of This Document" -msgstr "" - -#. Tag: para -#: welcome.xml:394 -#, no-c-format -msgid "" -"This document is meant to serve as a manual for first-time Debian users. It " -"tries to make as few assumptions as possible about your level of expertise. " -"However, we do assume that you have a general understanding of how the " -"hardware in your computer works." -msgstr "" - -#. Tag: para -#: welcome.xml:401 -#, no-c-format -msgid "" -"Expert users may also find interesting reference information in this " -"document, including minimum installation sizes, details about the hardware " -"supported by the Debian installation system, and so on. We encourage expert " -"users to jump around in the document." -msgstr "" - -#. Tag: para -#: welcome.xml:408 -#, no-c-format -msgid "" -"In general, this manual is arranged in a linear fashion, walking you through " -"the installation process from start to finish. Here are the steps in " -"installing &debian;, and the sections of this document which correlate with " -"each step:" -msgstr "" - -#. Tag: para -#: welcome.xml:416 -#, no-c-format -msgid "" -"Determine whether your hardware meets the requirements for using the " -"installation system, in <xref linkend=\"hardware-req\"/>." -msgstr "" - -#. Tag: para -#: welcome.xml:422 -#, no-c-format -msgid "" -"Backup your system, perform any necessary planning and hardware " -"configuration prior to installing Debian, in <xref linkend=\"preparing\"/>. " -"If you are preparing a multi-boot system, you may need to create partition-" -"able space on your hard disk for Debian to use." -msgstr "" - -#. Tag: para -#: welcome.xml:430 -#, no-c-format -msgid "" -"In <xref linkend=\"install-methods\"/>, you will obtain the necessary " -"installation files for your method of installation." -msgstr "" - -#. Tag: para -#: welcome.xml:436 -#, no-c-format -msgid "" -"describes booting into the installation system. This chapter also discusses " -"troubleshooting procedures in case you have problems with this step." -msgstr "" - -#. Tag: para -#: welcome.xml:443 -#, no-c-format -msgid "" -"Perform the actual installation according to <xref linkend=\"d-i-intro\"/>. " -"This involves choosing your language, configuring peripheral driver modules, " -"configuring your network connection, so that remaining installation files " -"can be obtained directly from a Debian server (if you are not installing " -"from a CD), partitioning your hard drives and installation of a base system, " -"then selection and installation of tasks. (Some background about setting up " -"the partitions for your Debian system is explained in <xref linkend=" -"\"partitioning\"/>.)" -msgstr "" - -#. Tag: para -#: welcome.xml:456 -#, no-c-format -msgid "" -"Boot into your newly installed base system, from <xref linkend=\"boot-new\"/" -">." -msgstr "" - -#. Tag: para -#: welcome.xml:464 -#, no-c-format -msgid "" -"Once you've got your system installed, you can read <xref linkend=\"post-" -"install\"/>. That chapter explains where to look to find more information " -"about Unix and Debian, and how to replace your kernel." -msgstr "" - -#. Tag: para -#: welcome.xml:474 -#, no-c-format -msgid "" -"Finally, information about this document and how to contribute to it may be " -"found in <xref linkend=\"administrivia\"/>." -msgstr "" - -#. Tag: title -#: welcome.xml:484 -#, no-c-format -msgid "Your Documentation Help is Welcome" -msgstr "" - -#. Tag: para -#: welcome.xml:486 -#, no-c-format -msgid "" -"Any help, suggestions, and especially, patches, are greatly appreciated. " -"Working versions of this document can be found at <ulink url=\"&url-d-i-" -"alioth-manual;\"></ulink>. There you will find a list of all the different " -"architectures and languages for which this document is available." -msgstr "" - -#. Tag: para -#: welcome.xml:493 -#, no-c-format -msgid "" -"Source is also available publicly; look in <xref linkend=\"administrivia\"/> " -"for more information concerning how to contribute. We welcome suggestions, " -"comments, patches, and bug reports (use the package <classname>installation-" -"guide</classname> for bugs, but check first to see if the problem is already " -"reported)." -msgstr "" - -#. Tag: title -#: welcome.xml:509 -#, no-c-format -msgid "About Copyrights and Software Licenses" -msgstr "" - -#. Tag: para -#: welcome.xml:512 -#, no-c-format -msgid "" -"We're sure that you've read some of the licenses that come with most " -"commercial software — they usually say that you can only use one copy " -"of the software on a single computer. This system's license isn't like that " -"at all. We encourage you to put a copy of on every computer in your school " -"or place of business. Lend your installation media to your friends and help " -"them install it on their computers! You can even make thousands of copies " -"and <emphasis>sell</emphasis> them — albeit with a few restrictions. " -"Your freedom to install and use the system comes directly from Debian being " -"based on <emphasis>free software</emphasis>." -msgstr "" - -#. Tag: para -#: welcome.xml:525 -#, no-c-format -msgid "" -"Calling software <emphasis>free</emphasis> doesn't mean that the software " -"isn't copyrighted, and it doesn't mean that CDs containing that software " -"must be distributed at no charge. Free software, in part, means that the " -"licenses of individual programs do not require you to pay for the privilege " -"of distributing or using those programs. Free software also means that not " -"only may anyone extend, adapt, and modify the software, but that they may " -"distribute the results of their work as well." -msgstr "" - -#. Tag: para -#: welcome.xml:536 -#, no-c-format -msgid "" -"The Debian project, as a pragmatic concession to its users, does make some " -"packages available that do not meet our criteria for being free. These " -"packages are not part of the official distribution, however, and are only " -"available from the <userinput>contrib</userinput> or <userinput>non-free</" -"userinput> areas of Debian mirrors or on third-party CD-ROMs; see the <ulink " -"url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>The Debian FTP " -"archives</quote>, for more information about the layout and contents of the " -"archives." -msgstr "" - -#. Tag: para -#: welcome.xml:550 -#, no-c-format -msgid "" -"Many of the programs in the system are licensed under the <emphasis>GNU</" -"emphasis> <emphasis>General Public License</emphasis>, often simply referred " -"to as <quote>the GPL</quote>. The GPL requires you to make the " -"<emphasis>source code</emphasis> of the programs available whenever you " -"distribute a binary copy of the program; that provision of the license " -"ensures that any user will be able to modify the software. Because of this " -"provision, the source code<footnote> <para> For information on how to " -"locate, unpack, and build binaries from Debian source packages, see the " -"<ulink url=\"&url-debian-faq;\">Debian FAQ</ulink>, under <quote>Basics of " -"the Debian Package Management System</quote>. </para> </footnote> for all " -"such programs is available in the Debian system." -msgstr "" - -#. Tag: para -#: welcome.xml:569 -#, no-c-format -msgid "" -"There are several other forms of copyright statements and software licenses " -"used on the programs in Debian. You can find the copyrights and licenses for " -"every package installed on your system by looking in the file <filename>/usr/" -"share/doc/<replaceable>package-name</replaceable>/copyright </filename> once " -"you've installed a package on your system." -msgstr "" - -#. Tag: para -#: welcome.xml:579 -#, no-c-format -msgid "" -"For more information about licenses and how Debian determines whether " -"software is free enough to be included in the main distribution, see the " -"<ulink url=\"&url-dfsg;\">Debian Free Software Guidelines</ulink>." -msgstr "" - -#. Tag: para -#: welcome.xml:585 -#, no-c-format -msgid "" -"The most important legal notice is that this software comes with " -"<emphasis>no warranties</emphasis>. The programmers who have created this " -"software have done so for the benefit of the community. No guarantee is made " -"as to the suitability of the software for any given purpose. However, since " -"the software is free, you are empowered to modify that software to suit your " -"needs — and to enjoy the benefits of the changes made by others who " -"have extended the software in this way." -msgstr "" |