From d3e34466bca0ffe9f3509131f44523c0fdae24ff Mon Sep 17 00:00:00 2001 From: Frans Pop Date: Mon, 25 Dec 2006 20:13:13 +0000 Subject: Update of POT and PO files for the manual --- po/el/boot-installer.po | 8902 ++++++++++++++++++++++++------------------ po/el/preparing.po | 69 +- po/el/using-d-i.po | 155 +- po/fi/boot-installer.po | 9036 ++++++++++++++++++++++++------------------- po/fi/preparing.po | 624 ++- po/fi/using-d-i.po | 155 +- po/hu/boot-installer.po | 6462 +++++++++++++++++++++---------- po/hu/preparing.po | 1691 ++++++-- po/hu/using-d-i.po | 155 +- po/ko/boot-installer.po | 8194 +++++++++++++++++++++++---------------- po/ko/preparing.po | 65 +- po/ko/using-d-i.po | 155 +- po/pot/boot-installer.pot | 2618 ++++++++++++- po/pot/preparing.pot | 36 +- po/pot/using-d-i.pot | 152 +- po/pt/boot-installer.po | 9219 +++++++++++++++++++++++++------------------- po/pt/preparing.po | 91 +- po/pt/using-d-i.po | 155 +- po/ro/using-d-i.po | 153 +- po/ru/boot-installer.po | 9184 ++++++++++++++++++++++++------------------- po/ru/preparing.po | 108 +- po/ru/using-d-i.po | 155 +- po/sv/boot-installer.po | 9137 ++++++++++++++++++++++++------------------- po/sv/preparing.po | 2307 +++++++++-- po/sv/using-d-i.po | 155 +- po/vi/boot-installer.po | 8521 +++++++++++++++++++++++----------------- po/vi/preparing.po | 67 +- po/vi/using-d-i.po | 155 +- po/zh_CN/boot-installer.po | 8183 ++++++++++++++++++++++----------------- po/zh_CN/preparing.po | 71 +- po/zh_CN/using-d-i.po | 155 +- po/zh_TW/boot-installer.po | 7415 +++++++++++++++++++++-------------- po/zh_TW/preparing.po | 63 +- po/zh_TW/using-d-i.po | 155 +- 34 files changed, 56685 insertions(+), 37233 deletions(-) (limited to 'po') diff --git a/po/el/boot-installer.po b/po/el/boot-installer.po index ff7a9443b..5e4350d05 100644 --- a/po/el/boot-installer.po +++ b/po/el/boot-installer.po @@ -16,7 +16,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-10-16 16:14+0300\n" "Last-Translator: QUAD-nrg.net \n" "Language-Team: Greek \n" @@ -28,3858 +28,5238 @@ msgstr "" "X-Generator: KBabel 1.11.4\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" -#~ msgid "Booting the Installation System" -#~ msgstr "Εκκίνηση του Συστήματος Εγκατάστασης" - -#~ msgid "Booting the Installer on &arch-title;" -#~ msgstr "Ξεκινώντας τον εγκαταστάτη στην αρχιτεκτονική &arch-title;" - -#~ msgid "Alpha Console Firmware" -#~ msgstr "Κονσόλα Firmware σε Alpha" - -#~ 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 "" -#~ "Το firmware της κονσόλας αποθηκεύεται σε μια μνήμη flash ROM και ξεκινά " -#~ "όταν ένα σύστημα Alpha μπαίνει σε λειτουργία ή επαναξεκινά. Υπάρχουν δυο " -#~ "διαφορετικές προδιαγραφές για τις κονσόλες που χρησιμοποιούνται στα " -#~ "συστήματα Alpha, και κατά συνέπειαν είναι διαθέσιμες δυο διαφορετικές " -#~ "κλάσεις firmware για κονσόλα:" - -#~ msgid "" -#~ "SRM console, based on the Alpha Console Subsystem " -#~ "specification, which provides an operating environment for OpenVMS, Tru64 " -#~ "UNIX, and Linux operating systems." -#~ msgstr "" -#~ "κονσόλα SRM, βασισμένη στις προδιαγραφές του Alpha " -#~ "Console Subsystem, που παρέχει ένα λειτουργικό περιβάλλον για τα " -#~ "λειτουργικά συστήματα OpenVMS, Tru64 UNIX, και Linux." - -#~ msgid "" -#~ "ARC, AlphaBIOS, or ARCSBIOS console, based on the " -#~ "Advanced RISC Computing (ARC) specification, which provides an operating " -#~ "environment for Windows NT." -#~ msgstr "" -#~ "Κονσόλες ARC, AlphaBIOS, ή ARCSBIOS, βασισμένες στις " -#~ "προδιαγραφές Advanced RISC Computing (ARC), και παρέχουν ένα λειτουργικό " -#~ "περιβάλλον για Windows NT." - -#~ 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 "" -#~ "Από τη σκοπιά του χρήστη, η σπουδαιότερη διαφορά ανάμεσα στα περιβάλλοντα " -#~ "SRM και ARC είναι ότι η επιλογή της κονσόλας περιορίζει (δεσμεύει) το " -#~ "πιθανό σχήμα διαμέρισης για τον δίσκο από τον οποίο επιθυμείτε να " -#~ "εκκινήσετε." - -#~ msgid "" -#~ "ARC requires that you use an MS-DOS partition table (as created by " -#~ "cfdisk) for the boot disk. Therefore MS-DOS partition " -#~ "tables are the native 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 "" -#~ "Η ARC απαιτεί να χρησιμοποιήσετε έναν MS-DOS πίνακα διαμέρισης (καθώς " -#~ "δημιουργείται με την εντολή cfdisk) για το δίσκο " -#~ "εκκίνησης. Συνεπώς πίνακες διαμέρισης MS-DOS είναι η φυσική μορφή διαμέρισης για εκκίνηση από ARC. Στην πραγματικότητα, καθώς " -#~ "το AlphaBIOS περιλαμβάνει ένα εργαλείο διαμέρισης δίσκων, πιθανόν να " -#~ "προτιμήσετε να διαμερίσετε τους δίσκους σας από τα μενού για το firmware " -#~ "πριν την εγκατάσταση του Linux." - -#~ msgid "" -#~ "Conversely, SRM is incompatible " -#~ "Specifically, the bootsector format required by the Console Subsystem " -#~ "Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " -#~ "BSD disklabel format, this is the native partition format " -#~ "for SRM installations." -#~ msgstr "" -#~ "Αντίθετα, η κονσόλα SRM είναι ασύμβατη με πίνακες " -#~ "διαμέρισης MS-DOS. Συγκεκριμένα, ο τύπος του bootsector " -#~ "που προϋποθέτει η προδιαγραφή Console Subsystem Specification συγκρούεται " -#~ "με την τοποθέτηση του πίνακα διαμέρισης από το DOS. " -#~ "Μιας και το Tru64 Unix χρησιμοποιεί τον τύπο επικεφαλίδας δίσκου " -#~ "(disklabel) του BSD, αυτός είναι και ο φυσικός τύπος " -#~ "διαμέρισης για εγκαταστάσεις σε SRM." - -#~ 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 "" -#~ "Επειδή το GNU/Linux είναι το μοναδικό λειτουργικό σύστημα για την " -#~ "αρχιτεκτονική Alpha που μπορεί να εκκινήσει και από τους δύο τύπους " -#~ "κονσόλας, η επιλογή σας θα εξαρτάται επίσης από το ποια άλλα λειτουργικά " -#~ "συστήματα θα θέλατε να χρησιμοποιήσετε στο ίδιο μηχάνημα. Όλα τα άλλα " -#~ "τύπου UNIX λειτουργικά συστήματα (Tru64 Unix, FreeBSD, OpenBSD, και " -#~ "NetBSD) και το OpenVMS μπορούν να ξεκινήσουν μόνο από την κονσόλα SRM, " -#~ "ενώ τα Windows NT μπορούν να εκκινήσουν μόνο από ARC." - -#~ msgid "" -#~ "Because MILO 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 "" -#~ "Επειδή ο φορτωτής MILO δεν είναι διαθέσιμος για κανένα " -#~ "από τα συστήματα Alpha σε παραγωγή αυτή τη στιγμή (τον Φεβρουάριο του " -#~ "2000), και καθώς δεν είναι πια απαραίτητο να αγοράσετε μια άδεια OpenVMS " -#~ "ή Tru64 Unix για να έχετε SRM firmware στο παλιότερο σύστημά σας Alpha, " -#~ "σας συνιστούμε να χρησιμοποιήσετε την κονσόλα SRM." - -#~ msgid "" -#~ "The following table summarizes available and supported system type/" -#~ "console combinations (see for the system " -#~ "type names). The word ARC below denotes any of the ARC-" -#~ "compliant consoles." -#~ msgstr "" -#~ "Ο επόμενος πίνακας συνοψίζει τους διαθέσιμους και υποστηριζόμενους " -#~ "συνδυασμούς τύπου συστήματος/κονσόλας (δείτε για τα ονόματα των τύπων συστημάτων). Η λέξη ARC " -#~ "παρακάτω δηλώνει οποιαδήποτε συμβατή με ARC κονσόλα." - -#~ msgid "System Type" -#~ msgstr "Τύπος Συστήματος" - -#~ msgid "Console Type Supported" -#~ msgstr "Υποστηριζόμενη Κονσόλα" - -#~ msgid "alcor" -#~ msgstr "alcor " - -#~ msgid "ARC or SRM" -#~ msgstr "ARC ή SRM" - -#~ msgid "avanti" -#~ msgstr "avanti " - -#~ msgid "book1" -#~ msgstr "book1 " - -#~ msgid "SRM only" -#~ msgstr "μόνο SRM" - -#~ msgid "cabriolet" -#~ msgstr "cabriolet " - -#~ msgid "dp264" -#~ msgstr "dp264 " - -#~ msgid "eb164" -#~ msgstr "eb164 " - -#~ msgid "eb64p" -#~ msgstr "eb64p " - -#~ msgid "eb66" -#~ msgstr "eb66 " - -#~ msgid "eb66p" -#~ msgstr "eb66p " - -#~ msgid "jensen" -#~ msgstr "jensen " - -#~ msgid "lx164" -#~ msgstr "lx164 " - -#~ msgid "miata" -#~ msgstr "miata " - -#~ msgid "mikasa" -#~ msgstr "mikasa " - -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p " - -#~ msgid "nautilus" -#~ msgstr "nautilus " - -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (βλ. εγχειρίδιο μητρικής) ή SRM" - -#~ msgid "noname" -#~ msgstr "noname " - -#~ msgid "noritake" -#~ msgstr "noritake " - -#~ msgid "noritake-p" -#~ msgstr "noritake-p " - -#~ msgid "pc164" -#~ msgstr "pc164 " - -#~ msgid "rawhide" -#~ msgstr "rawhide " - -#~ msgid "ruffian" -#~ msgstr "ruffian " - -#~ msgid "ARC only" -#~ msgstr "μόνο ARC" - -#~ msgid "sable" -#~ msgstr "sable " - -#~ msgid "sable-g" -#~ msgstr "sable-g " - -#~ msgid "sx164" -#~ msgstr "sx164 " - -#~ msgid "takara" -#~ msgstr "takara " - -#~ msgid "xl" -#~ msgstr "xl" - -#~ msgid "xlt" -#~ msgstr "xlt" - -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, aboot, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." -#~ msgstr "" -#~ "Γενικά, καμία από τις κονσόλες αυτές δεν μπορεί να εκκινήσει το Linux " -#~ "κατευθείαν, επομένως απαιτείται η βοήθεια ενός ενδιάμεσου φορτωτή " -#~ "εκκίνησης. Για την κονσόλα SRM, χρησιμοποιείται το aboot, ένας μικρός, ανεξάρτητος πλατφόρμας φορτωτής εκκίνησης. Δείτε " -#~ "επίσης και το (δυστυχώς ξεπερασμένο) SRM " -#~ "HOWTO για περισσότερες πληροφορίες για το aboot." - -#~ 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 "" -#~ "Οι ακόλουθες παράγραφοι έχουν παρθεί από το εγχειρίδιο εγκατάστασης του " -#~ "woody, και συμπεριλαμβάνονται για λόγους αναφοράς, πιθανόν να " -#~ "χρησιμεύσουν σε κάποιον αργότερα όταν το Debian υποστηρίξει ξανά " -#~ "εγκατάσταση με MILO." - -#~ 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: MILO and aboot." -#~ msgstr "" -#~ "Γενικά, καμία από τις κονσόλες αυτές δεν μπορεί να εκκινήσει το Linux " -#~ "κατευθείαν, επομένως απαιτείται η βοήθεια ενός ενδιάμεσου φορτωτή " -#~ "εκκίνησης. Υπάρχουν δυο κύριοι φορτωτές Linux: MILO " -#~ "και aboot." - -#~ msgid "" -#~ "MILO is itself a console, which replaces ARC or SRM in " -#~ "memory. MILO can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." -#~ msgstr "" -#~ "Ο MILO είναι ο ίδιος μια κονσόλα, που αντικαθιστά την " -#~ "ARC ή την SRM στην μνήμη. Ο MILO μπορεί να ξεκινήσει " -#~ "τόσο από την ARC όσο και την SRM και είναι ο μόνος τρόπος να ξεκινήσει " -#~ "(bootstrap) το Linux από την κονσόλα ARC. Ο MILO " -#~ "εξαρτάται από την συγκεκριμένη πλατφόρμα (οπότε ένας διαφορετικός " -#~ "MILO χρειάζεται για κάθε τύπο συστήματος) και υπάρχει " -#~ "μόνο για εκείνα τα συστήματα στον παραπάνω πίνακα όπου εμφανίζεται " -#~ "υποστήριξη για ARC. Δείτε επίσης και το (δυστυχώς ξεπερασμένο) MILO HOWTO." - -#~ msgid "" -#~ "aboot is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " -#~ "aboot." -#~ msgstr "" -#~ "Το aboot είναι ένας μικρός, ανεξάρτητος από την " -#~ "πλατφόρμα, φορτωτής εκκίνησης, που τρέχει μόνο στην κονσόλα SRM. Δείτε " -#~ "επίσης το (επίσης δυστυχώς ξεπερασμένο) SRM HOWTO για περισσότερες πληροφορίες σχετικά με το " -#~ "aboot." - -#~ msgid "" -#~ "Thus, three scenarios are generally possible, depending on the system's " -#~ "console firmware and whether or not MILO is available: " -#~ "\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Because MILO 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 aboot on new " -#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -#~ msgstr "" -#~ "Έτσι, υπάρχουν γενικά τρία πιθανά σενάρια, ανάλογα με το firmware της " -#~ "κονσόλας του συστήματος και το κατά πόσον είναι διαθέσιμος ο " -#~ "MILO: \n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Επειδή ο φορτωτής MILO δεν " -#~ "είναι διαθέσιμος για κανένα από τα συστήματα Alpha σε παραγωγή αυτή τη " -#~ "στιγμή (τον Φεβρουάριο του 2000), και καθώς δεν είναι πια απαραίτητο να " -#~ "αγοράσετε μια άδεια OpenVMS ή Tru64 Unix για να έχετε SRM firmware στο " -#~ "παλιότερο σύστημά σας Alpha, σας συνιστούμε να χρησιμοποιήσετε την " -#~ "κονσόλα SRM και τον aboot σε νέες εγκαταστάσεις του " -#~ "GNU/Linux, εκτός και αν επιθυμείτε να έχετε διπλή-εκκίνηση με Windows NT." - -#~ msgid "" -#~ "The majority of AlphaServers and all current server and workstation " -#~ "products contain both SRM and AlphaBIOS in their firmware. For " -#~ "half-flash 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 arc command). " -#~ "For the reasons mentioned above, we recommend switching to SRM before " -#~ "installing &debian;." -#~ msgstr "" -#~ "Η πλειοψηφία των AlphaServers και όλων των τωρινών προϊόντων διακομιστών " -#~ "και σταθμών εργασίας περιλαμβάνουν και την SRM και AlphaBIOS στο firmware " -#~ "τους. Για μηχανήματα half-flash όπως διάφορες πλατφόρμες " -#~ "δοκιμών, είναι δυνατόν να αλλάξει κανείς από την μια στην άλλη με " -#~ "επαναρχικοποίηση (reflashing) του firmware. Επίσης, από τη στιγμή της " -#~ "εγκατάστασης της SRM, είναι δυνατόν να τρέξει κανείς ARC/AlphaBIOS από " -#~ "μια δισκέττα (χρησιμοποιώντας την εντολή arc). Για " -#~ "τουςλόγους που αναφέρθηκαν παραπάνω, συνιστούμε να αλλάξετε στην κονσόλα " -#~ "SRM πριν την εγκατάσταση του &debian;." - -#~ msgid "" -#~ "As on other architectures, you should install the newest available " -#~ "revision of the firmware Except on Jensen, where Linux " -#~ "is not supported on firmware versions newer than 1.7 — see for more information. before installing &debian;. For Alpha, firmware updates can be " -#~ "obtained from Alpha Firmware Updates." -#~ msgstr "" -#~ "Όπως και με άλλες αρχιτεκτονικές, θα πρέπει να εγκαταστήσετε τις πιο " -#~ "πρόσφατες διαθέσιμες εκδόσεις του firmware Με εξαίρεση " -#~ "την Jensen, όπου το Linux δεν υποστηρίζεται για εκδόσεις του firmware " -#~ "μεταγενέστερες από την 1.7 - δείτε τη σελίδα για περισσότερες πληροφορίες πριν " -#~ "εγκαταστήσετε το &debian;. Για την Alpha, αναβαθμίσεις του firmware " -#~ "μπορούν να ληφθούν από τη σελίδα Alpha Firmware Updates." - -#~ msgid "Booting with TFTP" -#~ msgstr "Εκκίνηση μέσω TFTP" - -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the ewa " -#~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " -#~ "\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" -#~ " You first need to set the boot protocol: " -#~ "\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Then check the medium type is correct: " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " You can get a listing of valid modes with " -#~ ">>>set ewa0_mode." -#~ msgstr "" -#~ "Στην SRM, οι διεπαφές Ethernet ονοματοδοτούνται με το πρόθεμα " -#~ "ewa, και θα εμφανιστούν στην έξοδο της εντολής " -#~ "show dev κάπως έτσι (ελαφρά διορθωμένα ): " -#~ "\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" -#~ " Πρέπει κατ' αρχήν να ορίσετε το πρωτόκολλο " -#~ "εκκίνησης: \n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Στη συνέχεια ελέγξτε ότι ο τύπος του μέσου " -#~ "είναι ο σωστός: >>> set ewa0_mode " -#~ "mode\n" -#~ " Μπορείτε να πάρετε μια λίστα των έγκυρων " -#~ "τύπων με την εντολή >>>set ewa0_mode." - -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "Μετά, για να εκκινήσετε από το πρώτο Ethernet interface, θα πρέπει να " -#~ "τυπώσετε: \n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " Αυτό θα δώσει εκκίνηση με τις προκαθορισμένες " -#~ "παραμέτρους στον πυρήνα όπως περιλαμβάνεται στην εικόνα του netboot." - -#~ msgid "" -#~ "If you wish to use a serial console, you must pass " -#~ "the console= parameter to the kernel. This can be " -#~ "done using the -flags argument to the SRM " -#~ "boot command. The serial ports are named the same " -#~ "as their corresponding files in /dev. 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 " -#~ "ewa0 and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "Αν θέλετε να χρησιμοποιήσετε μια σειριακή κονσόλα, θα πρέπει να περάσετε την παράμετρο console= στον " -#~ "πυρήνα. Αυτό μπορεί να γίνει χρησιμοποιώντας το όρισμα -flagsστην εντολή boot της κονσόλας SRM. Oι " -#~ "σειριακές θύρες έχουν τα ονόματα των αντίστοιχων τους αρχείων στον " -#~ "κατάλογο /dev. Για παράδειγμα, για να ξεκινήσετε " -#~ "από το interface ewa0 και να χρησιμοποιήσετε μια " -#~ "κονσόλα στην πρώτη σειριακή θύρα θα πρέπει να πληκτρολογήσετε:" - -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0" " - -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "Εκκινώντας από CD-ROM με την κονσόλα SRM" - -#~ msgid "" -#~ "Type \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " where xxxx is your " -#~ "CD-ROM drive in SRM notation." -#~ msgstr "" -#~ "Τυπώστε \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " όπου xxxx είναι η " -#~ "μονάδα CD-ROM σε μορφή κατάλληλη για το SRM." - -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "Εκκίνηση από CD-ROM με την κονσόλα ARC ή AlphaBIOS" - -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see ), then enter \\milo" -#~ "\\linload.exe as the boot loader and \\milo" -#~ "\\subarch (where " -#~ "subarch is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use \\milo\\ldmilo.exe as boot loader." -#~ msgstr "" -#~ "Για να εκκινήσετε ένα CD-ROM από κονσόλα ARC, βρείτε το κωδικό όνομα της " -#~ "υποαρχιτεκτονικής σας (δείτε το ), στη " -#~ "συνέχεια πληκτρολογήστε \\milo\\linload.exe σαν τον " -#~ "φορτωτή εκκίνησης καθώς και \\milo\\subarch (όπου subarch είναι το " -#~ "κανονικό όνομα της υποαρχιτεκτονικής σας) σαν το OS Path στο μενού `OS " -#~ "Selection Setup'. Τα Ruffians αποτελούν εξαίρεση:θα πρέπει να " -#~ "χρησιμοποιήσετε \\milo\\ldmilo.exe σαν φορτωτή " -#~ "εκκίνησης." - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "Εκκίνηση από δισκέττες με την κονσόλα SRM" - -#~ msgid "" -#~ "At the SRM prompt (>>>), issue the following " -#~ "command: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possibly replacing dva0 " -#~ "with the actual device name. Usually, dva0 is the " -#~ "floppy; type \n" -#~ ">>> show dev\n" -#~ " to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, -" -#~ "flags argument is ignored, so you can just type boot " -#~ "dva0. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "Στην προτροπή της SRM (>>>), δώστε την παρακάτω " -#~ "εντολή: \n" -#~ ">>> boot dva0 -flags 0n πιθανόν " -#~ "αντικαθιστώντας το dva0 με το όνομα της πραγματικής " -#~ "συσκευής. Συνήθως dva0 είναι η συσκευή δισκέττας. " -#~ "Πληκτρολογήστε \n" -#~ ">>> show dev\n" -#~ " για να δείτε τη λίστα των συσκευών (πχ., αν " -#~ "θέλετε να εκκινήσετε από ένα CD). Σημειώστε ότι αν εκκινείτε μέσω MILO, " -#~ "το όρισμα -flags δεν λαμβάνεται υπόψιν, οπότε μπορείτε " -#~ "απλά να πληκτρολογήσετε boot dva0. Αν όλα πάνε καλά, " -#~ "θα δείτε τελικά τον πυρήνα του Linux να ξεκινά." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for dva0, " -#~ "the Linux boot device name for fd0, and the desired " -#~ "kernel parameters for arguments." -#~ msgstr "" -#~ "Αν θέλετε να προσδιορίσετε κάποιες παραμέτρους του πυρήνα όταν εκκινείτε " -#~ "μέσω του aboot, χρησιμοποιήστε την ακόλουθη εντολή: " -#~ "\n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (δοσμένη σε μια γραμμή),αντικαθιστώντας, αν " -#~ "είναι απαραίτητο, το όνομα της πραγματικής SRM συσκευής αντί του " -#~ "dva0, το όνομα της συσκευής εκκίνησης στο Linux αντί " -#~ "του fd0, και τις επιθυμητές παραμέτρους του πυρήνα " -#~ "για τα ορίσματα arguments." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " -#~ "See ." -#~ msgstr "" -#~ "Αν θέλετε να προσδιορίσετε παραμέτρους για τον πυρήνα ενώ ξεκινάτε με το " -#~ "MILO, θα πρέπει να διακόψετε την διαδικασία " -#~ "πρωτοεκκίνησης (bootstrap) μόλις μπείτε στο MILO. Δείτε το ." - -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "Εκκινώντας από δισκέττες με την κονσόλα ARC ή AlphaBIOS" - -#~ msgid "" -#~ "In the OS Selection menu, set linload.exe as the boot " -#~ "loader, and milo as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "Στο μενού OS Selection, ορίστε το linload.exe σαν " -#~ "φορτωτή εκκίνησης, και το milo σαν OS Path. Ξεκινήστε " -#~ "(bootstrap) χρησιμοποιώντας την επιλογή που μόλις δώσατε." - -#~ msgid "Booting with MILO" -#~ msgstr "Εκκίνηση με MILO" - -#~ 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 "" -#~ "Ο MILO που περιλαμβάνεται στα μέσα της πρωτοεκκίνησης είναι ρυθμισμένος " -#~ "ώστε αυτόματα να προχωρά στο Linux κατευθείαν. Σε περίπτωση που θα θέλατε " -#~ "να παρέμβετε στη διαδικασία, το μόνο που χρειάζεται να κάνετε είναι να " -#~ "πατήσετε το πλήκτρο space στη διάρκεια της αντίστροφης μέτρησης του MILΟ." - -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" -#~ " αν εκκινείτε από κάτι άλλο εκτός από " -#~ "δισκέττα, αντικαταστήστε το fd0 στο παραπάνω " -#~ "παράδειγμα με το κατάλληλο όνομα της συσκευής με το συμβολισμό του " -#~ "Linux. Η εντολή help μπορεί να σας δώσει ένα σύντομο " -#~ "οδηγό αναφοράς για τις εντολές του MILO." - -#~ msgid "Booting from TFTP" -#~ msgstr "Εκκίνηση από TFTP" - -#~ msgid "" -#~ "Booting from the network requires that you have a network connection and " -#~ "a TFTP network boot server (DHCP, RARP, or BOOTP)." -#~ msgstr "" -#~ "H εκκίνηση από το δίκτυο προαπαιτεί ότι διαθέτετε μια δικτυακή σύνδεση " -#~ "και έναν δικτυακό TFTP server εκκίνησης (DHCP, RARP, ή BOOTP)." - -#~ msgid "" -#~ "Older systems such as the 715 might require the use of an RBOOT server " -#~ "instead of a BOOTP server." -#~ msgstr "" -#~ "Παλιότερα συστήματα όπως τα 715 πιθανόν να απαιτούν τη χρήση ενός " -#~ "διακομιστή RBOOT αντί ενός BOOTP." - -#~ msgid "" -#~ "The installation method to support network booting is described in ." -#~ msgstr "" -#~ "Η μέθοδος εγκατάστασης με υποστήριξη δικτυακής εκκίνησης περιγράφεται " -#~ "στην ενότητα ." - -#~ msgid "Booting from TFTP on Netwinder" -#~ msgstr "Εκκίνηση με TFTP σε NetWinder" - -#~ msgid "" -#~ "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " -#~ "(which is generally referred to as eth0) 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 interface (the " -#~ "one labeled with 10 Base-T)." -#~ msgstr "" -#~ "Τα Netwinders έχουν δυο διεπαφές δικτύου: Μία κάρτα 10Μbps συμβατή με " -#~ "NE2000 (που γενικά αναφέρεται σαν eth0) και μία κάρτα " -#~ "Tulip των 100Μbps. Πιθανόν να συναντήσετε προβλήματα προσπαθώντας να " -#~ "φορτώσετε την εικόνα μέσω TFTP χρησιμοποιώντας την κάρτα των 100Mbps " -#~ "οπότε συνίσταται να χρησιμοποιήσετε αυτήν των 10Mbps (είναι η κάρτα που " -#~ "επιγράφεται σαν 10 Base-T)." - -#~ 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 ." -#~ msgstr "" -#~ "Χρειάζεστε έκδοση NeTTrom 2.2.1 ή μεταγενέστερη για να εκκινήσετε το " -#~ "σύστημα εγκατάστασης, η έκδοση NeTTrom 2.3.3 είναι η συνιστώμενη. " -#~ "Δυστυχώς τα αρχεία για το firmware δεν είναι αυτή τη στιγμή διαθέσιμα " -#~ "λόγω προβλημάτων με τις άδειες.10 Base-T). " -#~ "μπορείτε10 Base-T). να πάρετε τα αρχεία αυτά από το: " -#~ ":" - -#~ 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: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Furthermore, you must configure the network, " -#~ "either with a static address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " where 24 is the number of set bits in the " -#~ "netmask, or a dynamic address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " You may also need to configure the " -#~ "route1 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. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Now you have to tell the firmware that the " -#~ "TFTP image should be booted: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " If you use a serial console to install your " -#~ "Netwinder, you need to add the following setting: " -#~ "\n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Alternatively, for installations using a " -#~ "keyboard and monitor you have to set: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " You can use the printenv " -#~ "command to review your environment settings. After you have verified that " -#~ "the settings are correct, you can load the image: " -#~ "\n" -#~ " NeTTrom command-> boot\n" -#~ " In case you run into any problems, a detailed " -#~ "HOWTO is available." -#~ msgstr "" -#~ "Κατά την εκκίνηση του συστήματος Netwinder θα πρέπει να διακόψετε την " -#~ "διαδικασία εκκίνησης κατά την αντίστροφη μέτρηση. Αυτό σας επιτρέπει να " -#~ "ορίσετε έναν αριθμό από ρυθμίσεις του firmware που είναι απαραίτητες για " -#~ "την εκκίνηση του εγκαταστάτη. Ξεκινήστε, πρώτα απ' όλα, φορτώνοντας τις " -#~ "προκαθορισμένες ρυθμίσεις: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Επιπλέον, θα πρέπει να ρυθμίσετε το δίκτυο " -#~ "είτε με μια στατική διεύθυνση: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " όπου 24 είναι ο αριθμός των bit στην μάσκα " -#~ "δικτύου, ή μια δυναμική διεύθυνση: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " Πιθανόν να χρειαστεί να καθορίσετε τις " -#~ "ρυθμίσεις διαδρομής route1 σε περίπτωση που ο " -#~ "server TFTP δεν βρίσκεται στο τοπικό υποδίκτυο. Μετά από τις ρυθμίσεις " -#~ "αυτές θα πρέπει να προσδιορίσετε τον server TFTP και την τοποθεσία της " -#~ "εικόνας. Μπορείτε τότε να αποθηκεύσετε τις ρυθμίσεις σας στην μνήμη " -#~ "flash. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Θα πρέπει τώρα να πείτε στο firmware ότι θα " -#~ "πρέπει να εκκινήσει την εικόνα TFTP: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " Αν χρησιμοποιείτε μια σειριακή κονσόλα για " -#~ "την εγκατάσταση στο σύστημα Netwinder, θα πρέπει να προσθέσετε και την " -#~ "ακόλουθη ρύθμιση: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Εναλλακτικά, για εγακταστάσεις με χρήση ενός " -#~ "πληκτρολογίου και οθόνης θα πρέπει να ορίσετε: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " Μπορείτε να χρησιμοποιήσετε την εντολή " -#~ "printenv για την ανασκόπηση των ρυθμίσεων του " -#~ "περιβάλλοντός σας. Αφού επιβεβαιώσετε ότι οι ρυθμίσεις είναι σωστές, " -#~ "μπορείτε να φορτώσετε την εικόνα: \n" -#~ " NeTTrom command-> boot\n" -#~ " Σε περίπτωση που συναντήσετε οποιεσδήποτε " -#~ "δυσκολίες είναι διαθέσιμο ένα αναλυτικό HOWTO." - -#~ msgid "Booting from TFTP on CATS" -#~ msgstr "Εκκίνηση από TFTP σε CATS" - -#~ msgid "" -#~ "On CATS machines, use boot de0: or similar at the " -#~ "Cyclone prompt." -#~ msgstr "" -#~ "Σε μηχανήματα CATS, χρησιμοποιήστε boot de0: ή κάτι " -#~ "αντίστοιχο στην προτροπή του Cyclone." - -#~ msgid "Booting from CD-ROM" -#~ msgstr "Εκκίνηση από CD-ROM" - -#~ 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 configure your system for booting " -#~ "off a CD as described in , " -#~ "insert your CD, reboot, and proceed to the next chapter." -#~ msgstr "" -#~ "Ο ευκολότερος τρόπος για τους περισσότερους χρήστες είναι να " -#~ "χρησιμοποιήσουν ένα σετ με τα CD του Debian. Αν έχετε ένα τέτοιο σετ και " -#~ "αν το μηχάνημά σας υποστηρίζει απευθείας εκκίνηση από το CD τότε είστε " -#~ "εντάξει! Απλά ρυθμίστε το σύστημά σας για εκκίνηση " -#~ "από το CD όπως περιγράφεται στην ενότητα , βάλτε το CD σας στη συσκευή, επανεκκινήστε και προχωρήστε " -#~ "στο επόμενο κεφάλαιο." - -#~ 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 "" -#~ "Σημειώστε ότι κάποιες συσκευές CD πιθανόν να απαιτούν συγκεκριμένους " -#~ "οδηγούς και έτσι να μην είναι προσβάσιμες στα πρώτα στάδια της " -#~ "εγκατάστασης. Αν συμβεί λοιπόν ο συνηθισμένος τρόπος εκκίνησης από το CD " -#~ "να μην δουλέψει για το σύστημά σας,ξαναεπισκεφθείτε το κεφάλαιο αυτό και " -#~ "διαβάστε για πιθανούς εναλλακτικούς πυρήνες και μεθόδους εγκατάστασης που " -#~ "ίσως δουλέψουν στην περίπτωσή σας." - -#~ 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 "" -#~ "Ακόμα και αν δεν μπορείτε να εκκινήσετε από το CD-ROM, έχετε τη " -#~ "δυνατότητα ίσως να εγκαταστήσετε μέρη του Debian συστήματος και " -#~ "οποιαδήποτε πακέτα θέλετε από το CD-ROM. Απλά εκκινήστε χρησιμοποιώντας " -#~ "ένα άλλο μέσο, όπως δισκέττες. Όταν έρθει η στιγμή για να εγκαταστήσετε " -#~ "το λειτουργικό σύστημα, το βασικό σύστημα και οποιαδήποτε επιπλέον πακέτα " -#~ "θα πρέπει να υποδείξετε στο σύστημα εγκατάστασης να χρησιμοποιήσει τον " -#~ "οδηγό του CD-ROM." - -#~ msgid "" -#~ "If you have problems booting, see ." -#~ msgstr "" -#~ "Αν έχετε προβλήματα κατά την εκκίνηση, δείτε το ." - -#~ msgid "" -#~ "To boot a CD-ROM from the Cyclone console prompt, use the command " -#~ "boot cd0:cats.bin" -#~ msgstr "" -#~ "Για να εκκινήσετε ένα CD-ROM από το προτρεπτικό της κονσόλας του Cyclone, " -#~ "χρησιμοποιήστε την εντολή boot cd0:cats.bin" - -#~ msgid "Booting from Firmware" -#~ msgstr "Εκκίνηση από το Firmware" - -#~ 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 "" -#~ "Υπάρχει ένας διαρκώς αυξανόμενος αριθμός από καταναλωτικές συσκευές που " -#~ "εκκινούν κατευθείαν από ένα τσιπ flash στην ίδια την συσκευή. Ο " -#~ "εγκαταστάτης μπορεί να αποθηκευτεί στην flash ώστε να ξεκινήσει αυτόματα " -#~ "όταν επανεκκινήσετε τα μηχανήματά σας." - -#~ 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 "" -#~ "Σε πολλές περιπτώσεις, η αλλαγή του firmware μιας embedded συσκευής " -#~ "ακυρώνει την εγγύηση που έχετε. " - -#~ msgid "Booting the NSLU2" -#~ msgstr "Εκκίνηση του NSLU2" - -#~ msgid "There are three ways how to put the installer firmware into flash:" -#~ msgstr "" -#~ "Υπάρχουν τρεις τρόποι για να τοποθετήσετε τον εγκαταστάτη του firmware " -#~ "στην μνήμη flash:" - -#~ msgid "Using the NSLU2 web interface" -#~ msgstr "Χρησιμοποιώντας το web interface του NSLU2 " - -#~ msgid "" -#~ "Go to the administration section and choose the menu item " -#~ "Upgrade. You can then browse your disk for the " -#~ "installer image you have previously downloaded. Then press the " -#~ "Start Upgrade button, confirm, wait for a few minutes " -#~ "and confirm again. The system will then boot straight into the installer." -#~ msgstr "" -#~ "Πηγαίνετε τστην ενότητα Διαχείρισης και επιλέξτε Upgrade από το μενού. Μπορείτε τότε να πλοηγηθείτε στον δίσκο σας για " -#~ "την εικόνα του εγκαταστάτη που έχετε \"κατεβάσει\" από πριν. Πατήστε στην " -#~ "συνέχεια το κουμπί Start Upgrade, επιβεβαιώστε, " -#~ "περιμένετε για μερικά λεπτά και επιβεβαιώστε ξανά. Το σύστημα θα " -#~ "ξεκινήσει τότε κατευθείαν από τον εγκαταστάτη." - -#~ msgid "Via the network using Linux/Unix" -#~ msgstr "Μέσω του δικτύουχρησιμοποιώντας Linux/Unix" - -#~ msgid "" -#~ "You can use upslug2 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: " -#~ " Disconnect any disks and/or devices from the USB ports. " -#~ " Power off the NSLU2 Press and hold the reset button (accessible " -#~ "through the small hole on the back just above the power input). Press and release the power button to power on " -#~ "the NSLU2. Wait for 10 seconds " -#~ "watching the ready/status LED. After 10 seconds it will change from amber " -#~ "to red. Immediately release the reset button. " -#~ " 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. See the NSLU2-Linux " -#~ "pages if you have problems with this. Once your NSLU2 is in " -#~ "upgrade mode, you can flash the new image: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " 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 "" -#~ "Μπορείτε να χρησιμοποιήσετε την εντολή upslug2 από " -#~ "οποιοδήποτε μηχάνημα Linux ή Unix για να αναβαθμίσετε το μηχάνημα μέσω " -#~ "του δικτύου. Το λογισμικό αυτό διατίθεται και σαν πακέτο για το Debian. " -#~ "Καταρχήν, θα πρέπει να θέσετε το σύστημά σας NSLU2 σε κατάσταση " -#~ "αναβάθμισης: Αποσυνδέστε οποιουσδήποτε " -#~ "δίσκους και/ή συσκευές από τις θύρες USB. " -#~ " Σβήστε το σύστημα NSLU2 " -#~ " Πιέστε και κρατήστε πατημένο το κουμπί reset (που είναι " -#~ "προσβάσιμο μέσω της μικρής οπής στο πίσω μέρος του συστήματος ακριβώς " -#~ "πάνω από την είσοδο τροφοδοσίας). " -#~ "Πιέστε και αφήστε το κουμπί power για να θέσετε σε " -#~ "λειτουργία το NSLU2. Περιμένετε για " -#~ "10 δευτερόλεπτα προσέχοντας για την φωτεινή ένδειξη (LED) ready/status. " -#~ "Μετά από τα 10 δευτερόλεπτα θα αλλάξει από πορτοκαλί σε κόκκινο. Αμέσως " -#~ "αφήστε ελεύθερο το κουμπί reset. Η " -#~ "φωτεινή ένδειξη ready/status του NSLU2 θα μεταβληθεί εναλλάξ σε κόκκινο/" -#~ "πράσινο (υπάρχει ένα διάστημα αναμονής ενός δευτερολέπτου πριν από την " -#~ "πρώτη εμφάνιση του πράσινου). Το σύστημα NSLU2 είναι τώρα σε κατάσταση " -#~ "αναβάθμισης. Δείτε την σελίδα NSLU2-" -#~ "Linux pages αν αντιμετωπίσετε οποιαδήποτε προβλήματα σ' αυτό. " -#~ "Μόλις το σύστημα NSLU2 βρεθεί σε κατάσταση αναβάθμισης, μπορείτε να " -#~ "κάνετε flash την καινούρια εικόνα: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " Σημειώστε ότι το εργαλείο αυτό δείχνει επίσης " -#~ "την διεύθυνση MAC του συστήματός σας NSLU2, που μπορεί να σας φανεί " -#~ "χρήσιμη στην ρύθμιση του server DHCP. Μετά την εγγραφή και επαλήθευση " -#~ "ολόκληρης της εικόνας, το σύστημα θα επανεκκινήσει αυτόματα. Βεβαιωθείτε " -#~ "ότι συνδέσατε ξανά τον δίσκο σας USB, διαφορετικά ο εγκαταστάτης δεν θα " -#~ "μπορέσει να τον εντοπίσει." - -#~ msgid "Via the network using Windows" -#~ msgstr "Μέσω του δικτύου χρησιμοποιώντας Windows" - -#~ msgid "" -#~ "There is a tool for Windows to upgrade " -#~ "the firmware via the network." -#~ msgstr "" -#~ "Υπάρχει ένα εργαλείο για Windows που " -#~ "επιτρέπει την αναβάθμιση του firmware μέσω του δικτύου." - -#~ msgid "Booting from a CD-ROM" -#~ msgstr "Εκκίνηση από CD-ROM" - -#~ msgid "" -#~ "Booting from Linux Using LILO or GRUB" -#~ msgstr "" -#~ "Ξεκινώντας από το Linux με LILO ή GRUB" - -#~ msgid "" -#~ "To boot the installer from hard disk, you must first download and place " -#~ "the needed files as described in ." -#~ msgstr "" -#~ "Για να ξεκινήσετε τον εγκαταστάτη από τον σκληρό δίσκο θα πρέπει πρώτα να " -#~ "κατεβάσετε και να τοποθετήσετε τα απαραίτητα αρχεία όπως περιγράφεται " -#~ "στην ενότητα ." - -#, fuzzy -#~ msgid "" -#~ "If you intend to use the hard drive only for booting and then download " -#~ "everything over the network, you should download the netboot/" -#~ "debian-installer/i386/initrd.gz file and its corresponding " -#~ "kernel netboot/debian-installer/i386/linux. This " -#~ "will allow you to repartition the hard disk from which you boot the " -#~ "installer, although you should do so with care." -#~ msgstr "" -#~ "Αν σκοπεύετε να χρησιμοποιήσετε τον σκληρό δίσκο μόνο για την εκκίνηση " -#~ "και στη συνέχεια να κατεβάσετε ο,οτιδήποτε άλλο από το δίκτυο, θα πρέπει " -#~ "να κατεβάσετε το αρχείο netboot/debian-installer/i386/initrd." -#~ "gz και τον αντίστοιχο πυρήνα. Αυτό θα σας επιτρέψει να " -#~ "επανακατατμήσετε το δίσκο από τον οποίο θα εκκινήσετε τον εγκαταστάτη, αν " -#~ "και θα πρέπει να κάνετε κάτι τέτοιο με προσοχή." - -#~ msgid "" -#~ "Alternatively, if you intend to keep an existing partition on the hard " -#~ "drive unchanged during the install, you can download the hd-" -#~ "media/initrd.gz file and its kernel, as well as copy a CD iso " -#~ "to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from " -#~ "the CD image, without needing the network." -#~ msgstr "" -#~ "Εναλλακτικά, αν σκοπεύετε να κρατήσετε αμετάβλητη μια υπάρχουσα διαμέριση " -#~ "στον σκληρό δίσκο κατά τη διάρκεια της εγκατάστασης, μπορείτε να " -#~ "κατεβάσετε το αρχείο hd-media/initrd.gz και τον " -#~ "πυρήνα του, καθώς και να αντιγράψετε την εικόνα iso ενός CD (βεβαιωθείτε " -#~ "ότι το αρχείο έχει κατάληξη σε.iso). Ο εγκαταστάτης " -#~ "μπορεί τότε να εκκινήσει από τη συσκευή του CD-ROM και να κάνει την " -#~ "εγκατάσταση από την εικόνα του CD, χωρίς την ανάγκη δικτύου." - -#~ msgid "" -#~ "For LILO, you will need to configure two essential " -#~ "things in /etc/lilo.conf: " -#~ " to load the initrd.gz installer at " -#~ "boot time; have the " -#~ "vmlinuz kernel use a RAM disk as its root partition. " -#~ " Here is a /etc/lilo.conf example:" -#~ msgstr "" -#~ "Για το LILO, θα πρέπει να ρυθμίσετε δυο ουσιαστικά " -#~ "στοιχεία στο αρχείο /etc/lilo.conf: " -#~ " να φορτώσει τον εγκαταστάτη " -#~ "initrd.gz κατά τη διάρκεια της εκκίνησης. να κάνετε τον πυρήνα vmlinuz να χρησιμοποιήσει έναν δίσκο RAM σαν το ριζικό τμήμα του " -#~ "δίσκου. Εδώ είναι ένα παράδειγμα " -#~ "αρχείου /etc/lilo.conf:" - -#~ msgid "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" -#~ msgstr "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\" " - -#~ msgid "" -#~ "For more details, refer to the initrd 4 and " -#~ "lilo.conf 5 man pages. Now run lilo " -#~ "and reboot." -#~ msgstr "" -#~ "Για περισσότερες λεπτομέρειες, αναφερθείτε στις σελίδες χρήσης των " -#~ "initrd4 και lilo.conf 5. Τρέξτε τώρα το " -#~ "lilo και επανεκκινήστε." - -#~ msgid "" -#~ "The procedure for GRUB is quite similar. Locate your " -#~ "menu.lst in the /boot/grub/ " -#~ "directory (sometimes in the /boot/boot/grub/), add " -#~ "the following lines: \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" -#~ " and reboot." -#~ msgstr "" -#~ "Η διαδικασία για το GRUB είναι αρκετά παρόμοια. " -#~ "Εντοπίστε το αρχείο menu.lst στον κατάλογο " -#~ "/boot/grub/ (μερικές φορές στον κατάλογο/" -#~ "boot/boot/grub/), και προσθέστε τις ακόλουθες γραμμές: " -#~ "\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" -#~ " και επανεκκινήστε." - -#~ msgid "" -#~ "Note that the value of the ramdisk_size may need " -#~ "to be adjusted for the size of the initrd image. From here on, there " -#~ "should be no difference between GRUB or LILO." -#~ msgstr "" -#~ "Σημειώστε ότι η τιμή ramdisksize πιθανόν να " -#~ "χρειάζεται προσαρμογή για το μέγεθος της εικόνας initrd. Από το σημείο " -#~ "αυτό και μετά, δεν θα υπάρχει διαφορά ανάμεσα στα GRUB " -#~ "και LILO." - -#~ msgid "Booting from USB Memory Stick" -#~ msgstr "Εκκίνηση από USB stick μνήμης " - -#~ msgid "" -#~ "Let's assume you have prepared everything from and . 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 boot: prompt. Here you can enter optional boot arguments, or just hit " -#~ "&enterkey;." -#~ msgstr "" -#~ "Ας υποθέσουμε ότι έχετε προετοιμάσει όσα υποδεικνύονται στις ενότητες " -#~ " και . Τώρα απλά συνδέστε το USB stick σε μια ελεύθερη θύρα σύνδεσης USB και " -#~ "επανεκκινήστε τον υπολογιστή. Το σύστημα θα πρέπει να ξεκινήσει, και θα " -#~ "εμφανιστεί μπροστά σας η προτροπή boot:. Εδώ μπορείτε " -#~ "να εισάγετε προαιρετικά ορίσματα για την εκκίνηση ή απλά να πατήσετε " -#~ "&enterkey;." - -#~ msgid "Booting from Floppies" -#~ msgstr "Εκκίνηση από Δισκέττες" - -#~ msgid "" -#~ "You will have already downloaded the floppy images you needed and created " -#~ "floppies from the images in ." -#~ msgstr "" -#~ "Θα έχετε ήδη κατεβάσει τις εικόνες των δισκεττών που χρειάζεστε και θα " -#~ "έχετε δημιουργήσει από αυτές τις αντίστοιχες δισκέττες στο ." - -#~ 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 "" -#~ "Για να εκκινήσετε από τη δισκέττα εκκίνησης του εγκαταστάτη, τοποθετήστε " -#~ "τη δισκέττα στην κύρια συσκευή δισκέττας, κλείστε το σύστημα κατά το " -#~ "συνηθισμένο τρόπο, και μετά ξανανοίξτε το." - -#, fuzzy -#~ 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 root= 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 linux root=/dev/hdc at the " -#~ "boot prompt." -#~ msgstr "" -#~ "Για εγκατάσταση από έναν οδηγό LS-120 (έκδοση ATAPI) με ένα σετ από " -#~ "δισκέττες, θα πρέπει να προσδιορίσετε την εικονική τοποθεσία της συσκευής " -#~ "δισκέττας. Αυτό γίνεται με το όρισμα root= στην " -#~ "εκκίνηση, δίνοντας τη συσκευή στην οποία απεικονίζει ο οδηγός ide-floppy " -#~ "την αρχική συσκευή. Για παράδειγμα, αν η συσκευή σας LS-120 είναι " -#~ "συνδεδεμένη σαν πρώτη συσκευή IDE (κύρια) στο δεύτερο καλώδιο, θα πρέπει " -#~ "να βάλετε linux root=/dev/hdc στο προτρεπτικό της " -#~ "εκκίνησης. Εγκατάσταση από LS-120 υποστηρίζεται μόνο από πυρήνες 2.4 και " -#~ "μεταγενέστερους." - -#~ msgid "" -#~ "Note that on some machines, Control " -#~ "Alt Delete does not properly " -#~ "reset the machine, so a hard 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 "" -#~ "Σημειώστε ότι σε μερικά μηχανήματα ο συνδυασμός πλήκτρων " -#~ "ControlAlt Deleteδεν επανεκκινεί το μηχάνημα κανονικά, οπότε συνίσταται " -#~ "μια σκληρή επανεκκίνηση. Αν κάνετε την εγκατάσταση από ένα " -#~ "υπάρχον λειτουργικό σύστημα (πχ., από ένα κουτί DOS) δεν " -#~ "έχετε επιλογή. Διαφορετικά, παρακαλούμε να κάνετε μια σκληρή επανεκκίνηση " -#~ "κατά τη διαδικασία της εκκίνησης." - -#~ msgid "" -#~ "The floppy disk will be accessed, and you should then see a screen that " -#~ "introduces the boot floppy and ends with the boot: " -#~ "prompt." -#~ msgstr "" -#~ "Στη συνέχεια η δισκέττα θα είναι προσβάσιμη και θα δείτε μια οθόνη που " -#~ "εισάγει τη δισκέττα και τελειώνει με την προτροπή boot:." - -#~ msgid "" -#~ "Once you press &enterkey;, you should see the message " -#~ "Loading..., followed by " -#~ "Uncompressing Linux..., 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 ." -#~ msgstr "" -#~ "Όταν πληκτρολογήσετε &enterkey;, θα δείτε το μήνυμα " -#~ "Loading..., ακολουθούμενο από " -#~ "τοUncompressing Linux..., και στη " -#~ "συνέχεια μια γεμάτη οθόνη από πληροφορίες σχετικά με το υλικό του " -#~ "συστήματος. Περισσότερες πληροφορίες γι' αυτή τη φάση της διαδικασίας " -#~ "μπορούν να βρεθούν στο ." - -#~ 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 debian-installer is " -#~ "automatically launched." -#~ msgstr "" -#~ "Μετά την εκκίνηση από τη δισκέττα εκκίνησης θα ζητηθεί η δισκέττα root. " -#~ "Εισάγετε τη δισκέττα αυτή και πατήστε &enterkey; το περιεχόμενό της " -#~ "δισκέττας αρχίζει να φορτώνεται στην μνήμη. Το πρόγραμμα του εγκαταστάτη " -#~ "debian-installer ξεκινά αυτόματα." - -#~ msgid "There are various ways to do a TFTP boot on i386." -#~ msgstr "" -#~ "Υπάρχουν διάφοροι τρόποι για να κάνετε μια εκκίνηση με TFTP στην " -#~ "αρχιτεκτονική i386." - -#~ msgid "NIC or Motherboard that support PXE" -#~ msgstr "Κάρτα δικτύου ή μητρική που υποστηρίζουν PXE" - -#~ msgid "" -#~ "It could be that your Network Interface Card or Motherboard provides PXE " -#~ "boot functionality. This is a Intel re-implementation of TFTP boot. If so you may be able to " -#~ "configure your BIOS to boot from the network." -#~ msgstr "" -#~ "Πιθανόν η κάρτα δικτύου σας (Network Interface Card) ή η μητρική σας να " -#~ "παρέχουν τη δυνατότητα/λειτουργικότητα για εκκίνηση με PXE. Αυτή είναι " -#~ "μια νέα υλοποίηση από την Intel " -#~ "της εκκίνησης με TFTP. Αν αυτό συμβαίνει πιθανόν να μπορείτε να ρυθμίσετε " -#~ "το BIOS του συστήματος σας ώστε να εκκινεί από το δίκτυο." - -#~ msgid "NIC with Network BootROM" -#~ msgstr "Κάρτα δικτύου (NIC) με δικτυακή bootROM " - -#~ msgid "" -#~ "It could be that your Network Interface Card provides TFTP boot " -#~ "functionality." -#~ msgstr "" -#~ "Υπάρχει περίπτωση η κάρτα δικτύου σας να παρέχει πιθανόν τη δυνατότητα " -#~ "εκκίνησης με TFTP." - -#~ msgid "" -#~ "Let us (&email-debian-boot-list;) know how did you manage " -#~ "it. Please refer to this document." -#~ msgstr "" -#~ "Ενημερώστε μας (&email-debian-boot-list;) για τον τρόπο " -#~ "που τα καταφέρατε. Παρακαλούμε αναφερθείτε στο κείμενο αυτό." - -#~ msgid "Etherboot" -#~ msgstr "Etherboot " - -#~ msgid "" -#~ "The etherboot project " -#~ "provides bootdiskettes and even bootroms that do a TFTPboot." -#~ msgstr "" -#~ "Tο etherboot project " -#~ "διαθέτει δισκέττες εκκίνησης και ίσως ακόμα bootroms που να " -#~ "πραγματοποιούν μια εκκίνηση με TFTPboot." - -#~ msgid "The Boot Prompt" -#~ msgstr "Παράμετροι εκκίνησης " - -#~ msgid "" -#~ "When the installer boots, you should be presented with a friendly " -#~ "graphical screen showing the Debian logo and the boot prompt: " -#~ "\n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " 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 "" -#~ "Στο ξεκίνημα του εγκαταστάτη θα δείτε μια φιλική γραφική οθόνη με το " -#~ "λογότυπο του Debian και το προτρεπτικό εκκίνησης: " -#~ "\n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " Στο προτρεπτικό εκκίνησης μπορείτε είτε να " -#~ "πιέσετε απλά το &enterkey; για να ξεκινήσετε τον εγκαταστάτη με τις " -#~ "προκαθορισμένες επιλογές είτε να εισάγετε μια συγκεκριμένη μέθοδο " -#~ "εκκίνησης και, προαιρετικά, κάποιες παραμέτρους εκκίνησης." - -#~ msgid "" -#~ "Information on available boot methods and on boot parameters which might " -#~ "be useful can be found by pressing F2 through " -#~ "F8. If you add any parameters to the boot command line, " -#~ "be sure to type the boot method (the default is linux) and a space before the first parameter (e.g., " -#~ "linux fb=false)." -#~ msgstr "" -#~ "Πληροφορίες σχετικά με τις διαθέσιμες μεθόδους εκκίνησης και τις " -#~ "παραμέτρους εκκίνησης που ίσως είναι χρήσιμες μπορούν να βρεθούν πατώντας " -#~ "τα πλήκτρα F2 έως F8. Αν προσθέσετε " -#~ "οποιεσδήποτε παραμέτρους στην γραμμή εντολών εκκίνησης, βεβαιωθείτε να " -#~ "πληκτρολογήσετε την μέθοδο εκκίνησης (η προκαθορισμένη είναι η " -#~ "linux) και έναν κενό διάστημα πριν από την πρώτη " -#~ "παράμετρο (πχ., linux fb=false)." - -#~ 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 integrated Lights Out (iLO) and HP's " -#~ "Integrated Remote Assistant (IRA). You can blindly press " -#~ "F1 In some cases these devices will require special " -#~ "escape sequences to enact this keypress, for example the IRA uses " -#~ " Ctrl F , " -#~ "1. 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 fb=false to the boot " -#~ "prompt, as described in the help text." -#~ msgstr "" -#~ "Αν εγκαθιστάτε το σύστημα μέσω μιας συσκευής διαχείρισης από απόσταση που " -#~ "παρέχει ένα interface κειμένου στην κονσόλα VGA, ίσως να μην μπορέσετε να " -#~ "δείτε την αρχική γραφική οθόνη εκκίνησης κατά την έναρξη του εγκαταστάτη. " -#~ "Είναι πιθανόν να μην μπορείτε να δείτε καν το προτρεπτικό εκκίνησης. " -#~ "Παραδείγματα τέτοιων συσκευών περιλαμβάνουν την κονσόλα κειμένου στα " -#~ "συστήματα integrated Lights Out (iLO) της Compaq και τα " -#~ "Integrated Remote Assistant (IRA) της HP. Μπορείτε να " -#~ "πατήσετε στα \"τυφλά\" το πλήκτρο F1 Σε μερικές " -#~ "περιπτώσεις οι συσκευές αυτές πιθανόν να απαιτούν είδικούς συνδυασμούς " -#~ "πλήκτρων \"απόδρασης\" (escape sequences) για την ενεργοποίηση αυτού του " -#~ "πατήματος πλήκτρου. Για παράδειγμα, τα συστήματα IRA χρησιμοποιούν τον " -#~ "συνδυασμό Ctrl F ," -#~ " 1. για να προσπεράσετε αυτή " -#~ "την αρχική οθόνη και να δείτε το κείμενο βοήθειας. Από τη στιγμή που " -#~ "ξεπεράσετε την γραφική οθόνη κι ενώ είσαστε στο κείμενο βοήθειας ό,τι " -#~ "πληκτρολογείτε θα εμφανίζεται κανονικά στο προτρεπτικό ως συνήθως. Για να " -#~ "αποτρέψετε την χρήση του framebuffer από τον εγκαταστάτη για το υπόλοιπο " -#~ "της εγκατάστασης, θα χρειαστείτε επίσης να προσθέσετε το όρισμα " -#~ "fb=false στο προτρεπτικό εκκίνησης, όπως " -#~ "περιγράφεται και στο κείμενο βοήθειας." - -#~ msgid "CD Contents" -#~ msgstr "Περιεχόμενα CD" - -#~ msgid "" -#~ "There are three basic variations of Debian Install CDs. The " -#~ "Business Card 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 Network Install 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 "" -#~ "Υπάρχουν τρεις βασικές παραλλαγές CD της εγκατάστασης του Debian. Το " -#~ "Business Card CD παρέχει μια ελάχιστη εγκατάσταση " -#~ "που χωράει σε ένα CD μικρού σχήματος. Απαιτεί μια δικτυακή σύνδεση για " -#~ "την ολοκλήρωση του υπόλοιπου της βασικής εγκατάστασης και τη δημιουργία " -#~ "ενός χρηστικού συστήματος. Το CD Network Install " -#~ "έχει όλα τα πακέτα για μια βασική εγκατάσταση αλλά απαιτεί και μια " -#~ "δικτυακή σύνδεση σε έναν καθρέφτη του Debian για την εγκατάσταση των " -#~ "επιπλέον πακέτων που θα ήθελε κάποιος για να έχει ένα πλήρες σύστημα. Το " -#~ "σετ των CD του Debian μπορεί να εγκαταστήσει ένα πλήρες σύστημα από την " -#~ "ευρεία συλλογή των πακέτων χωρίς την ανάγκη πρόσβασης στο δίκτυο." - -#~ 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 "" -#~ "Η αρχιτεκτονική IA-64 χρησιμοποιεί το επόμενης γενιάς Extensible Firmware " -#~ "Interface (EFI) από την Intel. Σε αντίθεση με το παραδοσιακό x86 BIOS που " -#~ "ξέρει πολύ λίγα πράγματα για τη συσκευή εκκίνησης πέρα από τον πίνακα " -#~ "διαμέρισης και το Master Boot Record (MBR), το EFI μπορεί να διαβάσει και " -#~ "να γράψει αρχεία από τμήματα δίσκου με μορφοποίηση σε FAT16 ή FAT32.Αυτό " -#~ "απλοποιεί την συχνά παρωχημένη διαδικασία της έναρξης ενός συστήματος. Ο " -#~ "φορτωτής εκκίνησης του συστήματος και το EFI firmware που τον υποστηρίζει " -#~ "έχουν ένα πλήρες σύστημα αρχείων για την αποθήκευση των απαραίτητων " -#~ "αρχείων για την εκκίνηση του μηχανήματος. Αυτό σημαίνει ότι ο δίσκος του " -#~ "συστήματος σε ένα σύστημα IA-64 έχει ένα επιπλέον τμήμα αφιερωμένη στο " -#~ "EFI αντί του απλού MBR ή του μπλοκ εκκίνησης στα περισσότερα συμβατικά " -#~ "συστήματα." - -#~ msgid "" -#~ "The Debian Installer CD contains a small EFI partition where the " -#~ "ELILO 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 "" -#~ "Το CD της εγκατάστασης του Debian περιέχει μια μικρή διαμέριση EFI όπου " -#~ "βρίσκονται ο φορτωτής εκκίνησης ELILO, το αρχείο " -#~ "ρύθμισης του, ο πυρήνας του εγκαταστάτη και ένα αρχικό σύστημα αρχείων " -#~ "(initrd). Το τρέχον σύστημα περιέχει επίσης ένα τμήμα EFI όπου βρίσκονται " -#~ "τα απαραίτητα για την εκκίνηση του συστήματος αρχεία. Τα αρχεία αυτά " -#~ "είναι αναγνώσιμα από το κέλυφος EFI όπως περιγράφεται στη συνέχεια." - -#~ msgid "" -#~ "Most of the details of how ELILO 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 ELILO 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 "" -#~ "Οι περισσότερες λεπτομέρειες για το πώς το ELILO " -#~ "φορτώνει και ξεκινά στην πραγματικότητα ένα σύστημα είναι διαφανείς στον " -#~ "εγκαταστάτη του συστήματος. Όμως. ο εγκατάστασης πρέπει να ορίσει μια " -#~ "διαμέριση EFI πριν τηνεγκατάσταση του βασικού συστήματος. Διαφορετικά, η " -#~ "εγκατάσταση του ELILO θα αποτύχει, καθιστώντας το " -#~ "σύστημα μη εκκινήσιμο. Το τμήμα EFI προσδιορίζεται και μορφοποιείται στη " -#~ "φάση της διαμέρισης κατά την εγκατάσταση και πριν τη φόρτωση οποιονδήποτε " -#~ "πακέτων στο δίσκο του συστήματος. Η φάση της κατάτμησης επαληθεύει επίσης " -#~ "ότι ένα κατάλληλο τμήμα EFI όντως υπάρχει πριν επιτρέψει την συνέχιση της " -#~ "εγκατάστασης." - -#~ 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, Boot " -#~ "Option Maintenance Menu and EFI Shell (Built-in). 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 "" -#~ "Ο Διαχειριστής εκκίνησης του EFI εμφανίζεται σαν το τελευταίο βήμα της " -#~ "αρχικοποίησης του firmware. Παρουσιάζει μια λίστα επιλογών από την οποία " -#~ "μπορεί ο χρήστης να διαλέξει. Ανάλογα με το μοντέλο του συστήματος και το " -#~ "υπόλοιπο λογισμικό που έχει φορτωθεί σε αυτό, το μενού των επιλογών " -#~ "μπορεί να διαφέρει από το ένα σύστημα στο άλλο. Θα πρέπει όμως να " -#~ "υπάρχουν τουλάχιστον δυο αντικείμενα στην εμφανιζόμενη λίστα, τα " -#~ "Boot Option Maintenance Menu καιEFI Shell " -#~ "(Built-in). Η χρήση της πρώτης επιλογής προτιμάται, αλλά αν δεν " -#~ "είναι διαθέσιμη ή αν το CD για κάποιο λόγο δεν εκκινεί με αυτήν, " -#~ "χρησιμοποιείστε την δεύτερη." - -#~ msgid "IMPORTANT" -#~ msgstr "ΣΗΜΑΝΤΙΚΟ" - -#~ 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 exit at the shell prompt." -#~ msgstr "" -#~ "Ο Διαχειριστής εκκίνησης του EFI θα επιλέξει μια προκαθορισμένη ενέργεια " -#~ "για την εκκίνηση, συνήθως την πρώτη επιλογή του μενού, μέσα σε ένα " -#~ "προκαθορισμένο αριθμό δευτερολέπτων. Κάτι που υποδεικνύεται από την " -#~ "αντίστροφη μέτρηση στην βάση τηςοθόνης .Από τη στιγμή που ο χρόνος αυτός " -#~ "τελειώσει και το σύστημα ξεκινά με την προκαθορισμένη ενέργεια, πιθανόν " -#~ "να πρέπει να επανεκκινήσετε το μηχάνημα για να συνεχίσετε την " -#~ "εγκατάσταση. Αν η προκαθορισμένη ενέργεια είναι το κέλυφος EFI,μπορείτε " -#~ "να επιστρέψετε στον Διαχειριστή της εκκίνησης τρέχοντας exit στο προτρεπτικό του κελύφους." - -#~ msgid "Option 1: Booting from the Boot Option Maintenance Menu" -#~ msgstr "Επιλογή 1: Εκκίνηση από το Μενού Συντήρησης Επιλογής Εκκίνησης" - -#~ 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 "" -#~ "Εισάγετε το CD στη συσκευή DVD/CD και επανεκκινήστε το μηχάνημα. Το " -#~ "firmware θα εμφανίσει τη σελίδα και το μενού του Διαχειριστή Εκκίνησης " -#~ "του EFI αφού ολοκληρώσει την αρχικοποίηση του συστήματος." - -#~ msgid "" -#~ "Select Boot Maintenance Menu from the menu with the " -#~ "arrow keys and press ENTER. This will display a new " -#~ "menu." -#~ msgstr "" -#~ "Επιλέξτε Boot Maintenance Menu από το μενού με τα " -#~ "πλήκτρα κατεύθυνσης (arrow keys) και πατήστε ENTER. " -#~ "Αυτό θα εμφανίσει ένα καινούριο μενού." - -#~ msgid "" -#~ "Select Boot From a File from the menu with the arrow " -#~ "keys and press ENTER. This will display a list of " -#~ "devices probed by the firmware. You should see two menu lines containing " -#~ "either the label Debian Inst [Acpi ... or " -#~ "Removable Media Boot. If you examine the rest of the " -#~ "menu line, you will notice that the device and controller information " -#~ "should be the same." -#~ msgstr "" -#~ "Επιλέξτε Boot From a File από το μενού με τα πλήκτρα " -#~ "κατεύθυνσης και πατήστε ENTER. Αυτό θα εμφανίσει μια " -#~ "λίστα με τις συσκευές που εξετάζονται από το firmware. Θα δείτε δύο " -#~ "γραμμές από το μενού που περιέχουν είτε την επικεφαλίδα Debian " -#~ "Inst [Acpi ... ή Removable Media Boot. " -#~ "Εξετάζοντας το υπόλοιπο της γραμμής του μενού θα διαπιστώσετε ότι η " -#~ "πληροφορία για τη συσκευή και τον ελεγκτή θα πρέπει να είναι η ίδια." - -#~ msgid "" -#~ "You can choose either of the entries that refer to the CD/DVD drive. " -#~ "Select your choice with the arrow keys and press ENTER. If you choose Removable Media Boot the " -#~ "machine will immediately start the boot load sequence. If you choose " -#~ "Debian Inst [Acpi ... instead, it will display a " -#~ "directory listing of the bootable portion of the CD, requiring you to " -#~ "proceed to the next (additional) step." -#~ msgstr "" -#~ "Μπορείτε να επιλέξετε οποιαδήποτε από τις δυο επιλογές που αναφέρονται " -#~ "στη συσκευή CD/DVD. Κάντε την επιλογή σας με τα πλήκτρα και πατήστε " -#~ "ENTER. Αν επιλέξετε Removable Media Boot το μηχάνημα θα ξεκινήσει αμέσως την ακολουθία της εκκίνησης. Αν " -#~ "αντίθετα επιλέξετε Debian Inst [Acpi ..., θα σας " -#~ "εμφανίσει μια λίστα καταλόγων του εκκινήσιμου μέρους του, ζητώντας σας να " -#~ "προχωρήσετε στο επόμενο (επιπρόσθετο) βήμα." - -#~ msgid "" -#~ "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " -#~ "Removable Media Boot] on the next to the last line. Select this " -#~ "line with the arrow keys and press ENTER. This will " -#~ "start the boot load sequence." -#~ msgstr "" -#~ "Θα χρειαστείτε αυτό το βήμα μόνο αν επιλέξετε το Debian Inst " -#~ "[Acpi .... Η λίστα των καταλόγων θα σας δείξει επίσης " -#~ "[Treat like Removable Media Boot] μετά την τελευταία γραμμή του " -#~ "μενού.Επιλέξτε τη γραμμή με τα πλήκτρα και πατήστε ENTER. Αυτό θα ξεκινήσει την ακολουθία της εκκίνησης." - -#~ 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 "" -#~ "Τα βήματα αυτά θα ξεκινήσουν τον φορτωτή εκκίνησης του Debian που θα " -#~ "εμφανίσει μια σελίδα του μενού για να διαλέξετε έναν πυρήνα για την " -#~ "εκκίνηση και να δώσετε άλλες επιλογές. Προχωρήστε στις επιλογές αυτές." - -#~ msgid "Option 2: Booting from the EFI Shell" -#~ msgstr "Επιλογή 2: Εκκίνηση από το κέλυφος του EFI" - -#~ 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 EFI Shell [Built-in]. Boot the Debian Installer " -#~ "CD with the following steps:" -#~ msgstr "" -#~ "Αν, για κάποιο λόγο, η επιλογή 1 δεν είναι επιτυχής επανεκκινήστε το " -#~ "μηχάνημα και όταν εμφανιστεί η οθόνη του διαχειριστή εκκίνησης του EFI θα " -#~ "πρέπει να υπάρχει μια επιλογή με τίτλο EFI Shell [Built-in]. Εκκινήστε το CD του εγκαταστάτη του Debian με τα ακόλουθα " -#~ "βήματα:" - -#~ 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 "" -#~ "Εισάγετε το CD στη συσκευή DVD/CD και επανεκκινήστε το μηχάνημα. Το " -#~ "firmware θα εμφανίσει τη σελίδα και το μενού του διαχειριστή εκκίνησης " -#~ "του EFI και μετά από αυτό ολοκληρώνει την αρχικοποίηση του συστήματος." - -#~ msgid "" -#~ "Select EFI Shell from the menu with the arrow keys and " -#~ "press ENTER. 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 fsn:. All " -#~ "other recognized partitions will be named blkn:. If you inserted the CD just before entering the " -#~ "shell, this may take a few extra seconds as it initializes the CD drive." -#~ msgstr "" -#~ "Επιλέξτε EFI Shell από το μενού με τα πλήκτρα και " -#~ "πατήστε ENTER.Το κέλυφος EFI θα ανιχνεύσει όλες τις " -#~ "εκκινήσιμες συσκευές και θα τις εμφανίσει στην κονσόλα πριν από την " -#~ "εμφάνιση της γραμμής εντολών του. Οι αναγνωρισμένες εκκινήσιμες " -#~ "διαμερίσεις στις συσκευές εμφανίζονται με ένα όνομα " -#~ "fsn:. Όλες οι υπόλοιπες " -#~ "αναγνωρισμένες διαμερίσεις ονομάζονταιblkn:" -#~ ". Αν εισάγατε το CD μόλις πριν την είσοδο στο κέλυφος, αυτό " -#~ "ίσως πάρει μερικά δευτερόλεπτα επιπλέον καθώς γίνεται η εκκίνηση της " -#~ "συσκευής του." - -#~ msgid "" -#~ "Examine the output from the shell looking for the CDROM drive. It is most " -#~ "likely the fs0: device although other devices with " -#~ "bootable partitions will also show up as fsn." -#~ msgstr "" -#~ "Εξετάστε το αποτέλεσμα από το κέλυφος για το όνομα της συσκευής του CD-" -#~ "ROM. Το πιο πιθανόν είναι η συσκευή fs0: αν και " -#~ "άλλες συσκευές με εκκινήσιμες διαμερίσεις θα εμφανίζονται " -#~ "σανfsn." - -#~ msgid "" -#~ "Enter fsn: and press " -#~ "ENTER to select that device where n is the partition number for the CDROM. The shell will now " -#~ "display the partition number as its prompt." -#~ msgstr "" -#~ "Εισάγετε fsn: και πατήστε " -#~ "ENTER για να επιλέξετε τη συσκευή όπου n είναι ο αριθμός της διαμέρισης για το CDROM. Το κέλυφος θα " -#~ "εμφανίσει τώρα τοναριθμό της διαμέρισης σαν την προτροπή του." - -#~ msgid "" -#~ "Enter elilo and press ENTER. This " -#~ "will start the boot load sequence." -#~ msgstr "" -#~ "Εισάγετε elilo και πατήστε ENTER. " -#~ "Αυτό θα ξεκινήσει την ακολουθία της εκκίνησης." - -#~ 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot " -#~ "kernel and options." -#~ msgstr "" -#~ "Όπως και με την επιλογή 1, τα βήματα αυτά ξεκινούν τον φορτωτή εκκίνησης " -#~ "του Debian που θα εμφανίσει μια σελίδα του μενού για να διαλέξετε πυρήνα " -#~ "για την εκκίνηση και άλλες επιλογές. Μπορείτε επίσης να εισάγετε τη " -#~ "συντομότερη fsn:elilo εντολή στην " -#~ "προτροπή του κελύφους. Προχωρήστε στην επιλογή πυρήνα εκκίνησης καθώς και " -#~ "άλλων δυνατοτήτων." - -#~ msgid "Installing using a Serial Console" -#~ msgstr "Εγκατάσταση μέσω Σειριακής Κονσόλας" - -#~ 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 [BAUD baud serial console], where BAUD " -#~ "is the speed of your serial console. Menu items for the most typical baud " -#~ "rate settings on the ttyS0 device are preconfigured." -#~ msgstr "" -#~ "Πιθανόν να θέλετε να κάνετε μια εγκατάσταση χρησιμοποιώντας οθόνη και " -#~ "πληκτρολόγιο ή μια σειριακή σύνδεση. Για να χρησιμοποιήσετε ένα τέτοιο " -#~ "συνδυασμό οθόνης/πληκτρολογίου επιλέξτε την δυνατότητα που περιέχει την " -#~ "συμβολοσειρά [VGAconsole]. Για εγκατάσταση πάνω από μια σειριακή " -#~ "σύνδεση, διαλέξτε την επιλογή που περιέχει τη συμβολοσειρά " -#~ "[BAUD baud serial console], όπου " -#~ "BAUD είναι η ταχύτητα της σειριακής κονσόλας " -#~ "σας. Δίνονται προκαθορισμένες οι επιλογές στο μενού για τις πιο τυπικές " -#~ "ρυθμίσεις των ταχυτήτων για τη συσκευή ttyS0." - -#~ 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 baud " -#~ "at the EFI shell." -#~ msgstr "" -#~ "Στις περισσότερες περιπτώσεις, θα θέλετε ο εγκαταστάτης να χρησιμοποιήσει " -#~ "την ίδια ταχύτητα σύνδεσης με αυτήν της σύνδεσής σας με την κονσόλα EFI. " -#~ "Αν δεν είσαστε βέβαιοι για τη ρύθμιση αυτή, μπορείτε να την πάρετε " -#~ "χρησιμοποιώντας την εντολήbaud στο κέλυφος EFI." - -#~ 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 console=ttyS1,57600n8 into the Boot: text window." -#~ msgstr "" -#~ "Αν δεν υπάρχει διαθέσιμη επιλογή με ρύθμιση για τη σειριακή συσκευή ή " -#~ "ταχύτητα σύνδεσης που θα θέλατε να χρησιμοποιήσετε, μπορείτε να " -#~ "υπερκεράσετε τη ρύθμιση της κονσόλας με μια από τις υπάρχουσες επιλογές " -#~ "στο μενού. Για παράδειγμα, για να χρησιμοποιήσετε μια κονσόλα με ταχύτητα " -#~ "57600 baud πάνω από τη συσκευή ttyS1, εισάγετε το " -#~ "console=ttyS1,57600n8 στο παράθυρο κειμένου " -#~ "Boot:." - -#~ 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 Params help menu for instructions on starting the installer in Text " -#~ "Mode." -#~ msgstr "" -#~ "Τα περισσότερα συστήματα IA-64 έρχονται με μια προκαθορισμένη ρύθμισης " -#~ "ταχύτητας για την κονσόλα στα 9600 baud. Αυτή η ρύθμιση είναι μάλλον " -#~ "αργή, και η κανονική διαδικασία της εγκατάστασης θα χρειαστεί σημαντικό " -#~ "χρόνο για να αποτυπώσει την κάθε οθόνη. Θα πρέπει λοιπόν να θεωρήσετε την " -#~ "περίπτωση είτε να αυξήσετε την ταχύτητα που χρησιμοποιείται για την " -#~ "εγκατάσταση ή να κάνετε μια εγκατάσταση σε \"κατάσταση κειμένου\". Δείτε " -#~ "το μενού βοήθειας Params για οδηγίες σχετικά με " -#~ "το ξεκίνημα του εγκαταστάτη σε \"Κατάσταση Κειμένου\"." - -#~ 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 "" -#~ "Αν επιλέξετε λάθος τύπο κονσόλας, θα είσαστε σε θέση να επιλέξετε το " -#~ "πυρήνα και να βάλετε παραμέτρους αλλά τόσο η οθόνη όσο και η είσοδος σας " -#~ "θα παγώσουν με το ξεκίνημα του πυρήνα απαιτώντας έτσι την επανεκκίνηση " -#~ "του συστήματος για να μπορέσει να ξεκινήσει η εγκατάσταση." - -#~ msgid "Selecting the Boot Kernel and Options" -#~ msgstr "Επιλογή του πυρήνα εκκίνησης και των άλλων επιλογών" - -#~ msgid "" -#~ "The boot loader will display a form with a menu list and a text window " -#~ "with a Boot: 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 General help " -#~ "screen explains the menu choices and the Params " -#~ "screen explains the common command line options." -#~ msgstr "" -#~ "Ο φορτωτής εκκίνησης θα εμφανίσει μια φόρμα με ένα μενού-λίστα και ένα " -#~ "παράθυρο κειμένου με το προτρεπτικό Boot:. Τα " -#~ "πλήκτρα επιλέγουν ένα αντικείμενο από το μενού αυτό και οποιοδήποτε " -#~ "κείμενοπληκτρολογείται θα εμφανιστεί στο παράθυρο για κείμενο. Υπάρχουν " -#~ "επίσης οθόνες βοήθειας που εμφανίζονται με το πάτημα του αντίστοιχου " -#~ "πλήκτρου συνάρτησης.. Η οθόνη βοήθειας General " -#~ "εξηγεί τις επιλογές από το μενούκαι η οθόνη Params " -#~ "επεξηγεί τις πιο κοινές επιλογές για τη γραμμή εντολών." - -#~ msgid "" -#~ "Consult the General help screen for the " -#~ "description of the kernels and install modes most appropriate for your " -#~ "installation. You should also consult " -#~ "below for any additional parameters that you may want to set in the " -#~ "Boot: 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 "" -#~ "Συμβουλευτείτε την οθόνη βοήθειας General για την " -#~ "περιγραφή των πυρήνων και των τύπων εγκατάστασης των πιο κατάλληλων για " -#~ "την εγκατάστασή σας. Μπορείτε επίσης να συμβουλευτείτε την ενότητα στη συνέχεια για επιπρόσθετες παραμέτρους που " -#~ "ίσως να θέλετε να βάλετε στο παράθυρο κειμένου Boot:. Η έκδοση του πυρήνα που θα διαλέξετε επιλέγει την έκδοση του " -#~ "πυρήνα που θα χρησιμοποιηθεί τόσο κατά τη διαδικασία εγκατάστασης όσο και " -#~ "από το εγκατεστημένο σύστημα. Αν αντιμετωπίσετε προβλήματα με τον πυρήνα " -#~ "στην εγκατάσταση πιθανόν να έχετε τα ίδια προβλήματα και με το " -#~ "εγκαταστημένο σύστημα. Τα επόμενα δυο βήματα θα επιλέξουν και θα " -#~ "ξεκινήσουν την εγκατάσταση:" - -#~ msgid "" -#~ "Select the kernel version and installation mode most appropriate to your " -#~ "needs with the arrow keys." -#~ msgstr "" -#~ "Διαλέξτε την έκδοση του πυρήνα και τον τρόπο εγκατάστασης που " -#~ "ταιριάζειπερισσότερο στις ανάγκες σας με τα βελάκια του πληκτρολογίου." - -#~ 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 "" -#~ "Εισάγετε οποιεσδήποτε παραμέτρους εκκίνησης πληκτρολογώντας τις. Το " -#~ "κείμενο θα εμφανιστεί άμεσα στο παράθυρο. Εκεί προσδιορίζονται και οι " -#~ "παράμετροι του πυρήνα (όπως για παράδειγμα οι ρυθμίσεις της σειριακής " -#~ "κονσόλας)." - -#~ msgid "" -#~ "Press ENTER. 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 "" -#~ "Πατήστε ENTER. Αυτό θα φορτώσει και θα ξεκινήσει τον " -#~ "πυρήνα. Ο πυρήνας θα εμφανίσει τα συνηθισμένα μηνύματα εκκίνησης " -#~ "ακολουθούμενα από την πρώτη οθόνη του εγκαταστάτη." - -#~ msgid "" -#~ "Proceed to the next chapter to continue the installation where you will " -#~ "set up the language locale, network, and disk partitions." -#~ msgstr "" -#~ "Προχωρήστε στο επόμενο κεφάλαιο για να συνεχίσετε την εγκατάσταση όπου " -#~ "και θα κάνετε τις ρυθμίσεις της τοπικής γλώσσας, του δικτύου και των " -#~ "διαμερίσεων του δίσκου." - -#, fuzzy -#~ msgid "" -#~ "Booting an IA-64 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 "" -#~ "Η εκκίνηση ενός συστήματος IA64 από το δίκτυο είναι ανάλογη της εκκίνησης " -#~ "από ένα CD. Η μόνη διαφορά βρίσκεται στον τρόπο φόρτωσης του πυρήνα. Ο " -#~ "Διαχειριστής εκκίνησης του EFI μπορεί να φορτώσει και να ξεκινήσει " -#~ "προγράμματα από έναν διακομιστή στο δίκτυο. Από τη στιγμή που ο πυρήνας " -#~ "της εγκατάστασης φορτωθεί και ξεκινήσει η εγκατάσταση του συστήματος θα " -#~ "προχωρήσει μέσα από τα ίδια βήματα όπως και η εγκατάσταση από το CD με τη " -#~ "διαφορά ότι τα πακέτα της βασικής εγκατάστασης θα φορτωθούν από το δίκτυο " -#~ "αντί για το CD." - -#, fuzzy -#~ msgid "" -#~ "Network booting an IA-64 system requires two architecture-specific " -#~ "actions. On the boot server, DHCP and TFTP must be configured to deliver " -#~ "elilo. On the client a new boot option must be defined " -#~ "in the EFI boot manager to enable loading over a network." -#~ msgstr "" -#~ "Η εκκίνηση από το δίκτυο σε ένα σύστημα ia64 απαιτεί δυο ενέργειες " -#~ "συγκεκριμένα για την αρχιτεκτονική αυτή. Στον διακομιστή εκκίνησης, οι " -#~ "DHCP και ΤFTP πρέπει να ρυθμιστούν ώστε να δίνουν το elilo. Στην πλευρά του πελάτη, μια καινούρια επιλογή για την εκκίνηση " -#~ "πρέπει να προσδιοριστεί στον διαχειριστή εκκίνησης του EFI για να " -#~ "επιτρέψει την φόρτωση από το δίκτυο." - -#~ msgid "Configuring the Server" -#~ msgstr "Ρύθμιση του Server" - -#, fuzzy -#~ msgid "" -#~ "A suitable TFTP entry for network booting an IA-64 system looks something " -#~ "like this: \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" -#~ " Note that the goal is to get elilo." -#~ "efi running on the client." -#~ msgstr "" -#~ "Μια κατάλληλη διαμόρφωση του TFTP για εκκίνηση από το δίκτυο ενός " -#~ "συστήματος ia64 μοιάζει κάπως έτσι: \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" -#~ " Σημειώστε ότι ο στόχος είναι να πετύχουμε την " -#~ "εκτέλεση του elilo.efi στην πλευρά του πελάτη." - -#~ msgid "" -#~ "Extract the netboot.tar.gz file into the directory " -#~ "used as the root for your tftp server. Typical tftp root directories " -#~ "include /var/lib/tftp and /tftpboot. This will create a debian-installer " -#~ "directory tree containing the boot files for an IA-64 system." -#~ msgstr "" -#~ "Αποσυμπιέστε το αρχείο netboot.tar.gz στον κατάλογο " -#~ "που χρησιμοποιήσατε σαν root στον διακομιστή σας tftp. Τυπικοί ριζικοί " -#~ "κατάλογοι για tftp περιλαμβάνουν τους: /var/lib/tftp " -#~ "και /tftpboot. Αυτό θα δημιουργήσει ένα δέντρο " -#~ "κατάλογων debian-installerπου θα περιέχει τα αρχεία " -#~ "εκκίνησης για ένα σύστημα IA-64." - -#~ msgid "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" -#~ msgstr "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...] " - -#~ msgid "" -#~ "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should " -#~ "you need to make changes to this file, you can find it in the " -#~ "debian-installer/ia64/ 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 .conf " -#~ "instead of elilo.conf. See documentation provided in " -#~ "the elilo package for details." -#~ msgstr "" -#~ "Tο αρχείο netboot.tar.gz περιέχει ένα αρχείο " -#~ "elilo.conf που πρέπει να δουλεύει στις περισσότερες " -#~ "περιπτώσεις. Αν όμως για κάποιο λόγο χρειαστεί να κάνετε κάποιες αλλαγές " -#~ "στο αρχείο μπορείτε να το βρείτε στον κατάλογο debian-installer/" -#~ "ia64/. Είναι δυνατόν να έχετε διαφορετικά αρχεία ρύθμισης για " -#~ "διαφορετικούς πελάτες ονομάζοντάς τα με την διεύθυνση IP του συστήματος " -#~ "σε δεκαεξαδική μορφή και την κατάληξη .conf αντί " -#~ "για elilo.conf. Δείτε την τεκμηρίωση που δίνεται με " -#~ "το πακέτο elilo για λεπτομέρειες." - -#~ msgid "Configuring the Client" -#~ msgstr "Ρύθμιση του πελάτη" - -#~ msgid "" -#~ "To configure the client to support TFTP booting, start by booting to EFI " -#~ "and entering the Boot Option Maintenance Menu. " -#~ " Add a boot option. " -#~ " You should see one or more lines with the text " -#~ "Load File [Acpi()/.../Mac()]. 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. Name " -#~ "the entry Netboot or something similar, save, and " -#~ "exit back to the boot options menu. " -#~ "You should see the new boot option you just created, and selecting it " -#~ "should initiate a DHCP query, leading to a TFTP load of elilo." -#~ "efi from the server." -#~ msgstr "" -#~ "Για να ρυθμίσετε τον πελάτη ώστε να υποστηρίζει εκκίνηση με TFTP, αρχίστε " -#~ "με εκκίνηση στο EFI και μπείτε στο μενού Boot Option " -#~ "Maintenance Menu. Προσθέστε μια " -#~ "επιλογή εκκίνησης.Θα δείτε μια ή " -#~ "περισσότερες γραμμές με το κείμενο Load File [Acpi()/.../Mac" -#~ "()]. Αν υπάρχουν περισσότερες από μια τέτοιες επιλογές, " -#~ "διαλέξτε αυτήν που περιέχει την διεύθυνση MAC του interface από το οποίο " -#~ "θα εκκινήσετε. Χρησιμοποιήστε τα βελάκια στο πληκτρολόγιο για να τονίσετε " -#~ "την επιλογή σας και στη συνέχεια πατήστε enter. Ονομάστε την επιλογή σας Netboot ή κάτι ανάλογο, αποθηκεύστε και βγείτε πάλι στο μενού των " -#~ "επιλογών εκκίνησης. Θα δείτε την " -#~ "καινούρια επιλογή που μόλις δημιουργήσατε και επιλέγοντας την θα " -#~ "ξεκινήσει μια αναζήτηση DHCP, οδηγώντας στο φόρτωμα μέσω του TFTP του " -#~ "αρχείου elilo.efi από τον διακομιστή." - -#~ 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 "" -#~ "Ο φορτωτής εκκίνησης θα εμφανίσει το προτρεπτικό του μετά το κατέβασμα " -#~ "και την επεξεργασία του αρχείου ρυθμίσεων. Στο σημείο αυτό η διαδικασία " -#~ "της εγκατάστασης θα προχωρήσει με τα ίδια βήματα όπως και η εγκατάσταση " -#~ "με το CD. Διαλέξτε μια επιλογή εκκίνησης όπως και παραπάνω και όταν " -#~ "τελειώσει η εγκατάσταση του πυρήνα από το δίκτυο θα ξεκινήσει ο " -#~ "εγκαταστάτης του Debian." - -#~ msgid "Choosing an Installation Method" -#~ msgstr "Επιλέγοντας Μέθοδο Εγκατάστασης" - -#~ 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 "" -#~ "Μερικές υπο-αρχιτεκτονικές της &arch-title; έχουν την επιλογή της " -#~ "εκκίνησης χρησιμοποιώντας είτε έναν πυρήνα 2.4.x είτε έναν 2.2.x. Όταν " -#~ "έχετε μια τέτοια δυνατότητα δοκιμάστε τον πυρήνα 2.4.x. O εγκαταστάτης " -#~ "επιπλέον απαιτεί λιγότερη μνήμη όταν χρησιμοποιεί τον πυρήνα 2.4.x καθώς " -#~ "η υποστήριξη του πυρήνα 2.2.x απαιτεί μια σταθερού μεγέθους ramdisk ενώ ο " -#~ "πυρήνας 2.4.x χρησιμοποιεί tmpfs." - -#~ msgid "" -#~ "If you are using a 2.2.x linux kernel, then you need to use the " -#~ "&ramdisksize; kernel parameter." -#~ msgstr "" -#~ "Αν χρησιμοποιείτε έναν πυρήνα 2.2.x kernel, ίσως χρειαστεί να ρυθμίσετε " -#~ "την παράμετρο πυρήνα &ramdisksize;." - -#~ msgid "" -#~ "Make sure root=/dev/ram is one of your kernel " -#~ "parameters." -#~ msgstr "" -#~ "Βεβαιωθείτε ότι η root=/dev/ram είναι μια από τις " -#~ "παραμέτρους του πυρήνα σας." - -#~ msgid "" -#~ "If you're having trouble, check cts's " -#~ "&arch-title; debian-installer FAQ." -#~ msgstr "" -#~ "Αν έχετε πρόβλημα ελέγξτε τις συχνές ερωτήσεις στο cts's &arch-title; debian-installer FAQ." - -#~ msgid "Amiga" -#~ msgstr "Amiga" - -#~ msgid "" -#~ "The only method of installation available to amiga is the hard drive (see " -#~ "). In other words the cdrom is " -#~ "not bootable." -#~ msgstr "" -#~ "Η μόνη διαθέσιμη μέθοδος εγκατάστασης για την amiga είναι από τον σκληρό " -#~ "δίσκο (δείτε το ). Με άλλα " -#~ "λόγια το cdrom δεν είναι εκκινήσιμο. " - -#~ msgid "" -#~ "Amiga does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Συστήματα Amiga δεν δουλεύουν προς το παρόν με το bogl, επομένως αν δείτε " -#~ "μηνύματα λάθους από το bogl, θα πρέπει να συμπεριλάβετε την παράμετρο " -#~ "εκκίνησης fb=false." - -#~ msgid "Atari" -#~ msgstr "Atari " - -#~ msgid "" -#~ "The installer for atari may be started from either the hard drive (see " -#~ ") or from floppies (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "Ο εγκαταστάτης για τον atari μπορεί να ξεκινήσει είτε από τον σκληρό " -#~ "δίσκο (δείτε το ) ή από δισκέττες (δείτε " -#~ "το ). Με άλλα λόγια το " -#~ "cdrom δεν είναι εκκινήσιμο. " - -#~ msgid "" -#~ "Atari does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Συστήματα Atari δεν δουλεύουν προς το παρόν με το bogl, επομένως αν δείτε " -#~ "μηνύματα λάθους από το bogl, θα πρέπει να συμπεριλάβετε την παράμετρο " -#~ "εκκίνησηςfb=false για τον πυρήνα." - -#~ msgid "BVME6000" -#~ msgstr "BVME6000 " - -#~ msgid "" -#~ "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." -#~ msgstr "" -#~ "Ο εγκαταστάτης για BVME6000 μπορεί να ξεκινήσει είτε από ένα cdrom (δείτε " -#~ "), είτε από δισκέττες (δείτε ), είτε από το δίκτυο (δείτε )." - -#~ msgid "Macintosh" -#~ msgstr "Macintosh " - -#~ msgid "" -#~ "The only method of installation available to mac is from the hard drive " -#~ "(see ). In other words the " -#~ "cdrom is not bootable. Macs do not have a working 2.4.x kernel." -#~ msgstr "" -#~ "Η μοναδική διαθέσιμη μέθοδος εγκατάστασης στον mac είναι από το σκληρό " -#~ "δίσκο (δείτε ).Με άλλα λόγια το " -#~ "cdrom δεν είναι εκκινήσιμο. Για τους Mac δεν υπάρχει κάποιος " -#~ "πυρήνας 2.4.x που να δουλεύει." - -#~ msgid "" -#~ "If your hardware uses a 53c9x-based scsi bus, then you may need to " -#~ "include the kernel parameter mac53c9x=1,0. " -#~ "Hardware with two such scsi buses, such as the Quadra 950, will need " -#~ "mac53c9x=2,0 instead. Alternatively, the parameter " -#~ "can be specified as mac53c9x=-1,0 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 "" -#~ "Εάν το υλικό σας χρησιμοποιεί scsi δίαυλο βασισμένο στο 53c9x, τότε " -#~ "πρέπει να συμπεριλάβετε την παράμετρο πυρήνα mac53c9x=1. Για υλικό με δυο τέτοιους διαύλους scsi, όπως το Quadra 950, " -#~ "θα χρειαστεί αντί της προηγουμένης παραμέτρου την mac53c9x=2. Εναλλακτικά, η παράμετρος μπορεί να χρησιμοποιηθεί σαν " -#~ "mac53c9x=-1,0 που θα αφήσει ενεργή την αυτόματη " -#~ "ανίχνευση, απενεργοποιώντας, όμως, αποσυνδέσεις των διαύλων SCSI. " -#~ "Σημειώστε ότι ο προσδιορισμός αυτής της παραμέτρου είναι αναγκαίος μόνο " -#~ "αν έχετε περισσότερους από έναν σκληρούς δίσκους. Σε διαφορετική " -#~ "περίπτωση, το σύστημά σας θα είναι γενικά γρηγορότερο αν δεν καθορίσετε " -#~ "την συγκεκριμένη παράμετρο." - -#~ msgid "MVME147 and MVME16x" -#~ msgstr "MVME147 και MVME16x" - -#~ msgid "" -#~ "The installer for MVME147 and MVME16x may be started from either floppies " -#~ "(see ) or the net (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "O εγκαταστάτης για MVEM147 και MVEM16x μπορεί να ξεκινήσει είτε από " -#~ "δισκέττες (δείτε ) ή από το δίκτυο " -#~ "(δείτε ). Με άλλα λόγια το cdrom " -#~ "δεν είναι εκκινήσιμο. " - -#~ msgid "Q40/Q60" -#~ msgstr "Q40/Q60 " - -#~ msgid "" -#~ "The only method of installation available to Q40/Q60 is from the hard " -#~ "drive (see ). In other words " -#~ "the cdrom is not bootable." -#~ msgstr "" -#~ "Η μόνη διαθέσιμη μέθοδος εγκατάστασης για Q40/Q60 είναι από το σκληρό " -#~ "δίσκο (δείτε ).Με άλλα λόγια το " -#~ "cdrom δεν είναι εκκινήσιμο. " - -#~ msgid "Booting from a Hard Disk" -#~ msgstr "Εκκίνηση από Σκληρό Δίσκο" - -#~ msgid "" -#~ "Booting from an existing operating system is often a convenient option; " -#~ "for some systems it is the only supported method of installation." -#~ msgstr "" -#~ "Η εκκίνηση από ένα υπάρχον λειτουργικό σύστημα είναι συχνά μια βολική " -#~ "μέθοδος. Για κάποια συστήματα είναι η μοναδική υποστηριζόμενη μέθοδος " -#~ "εγκατάστασης." - -#~ msgid "" -#~ "To boot the installer from hard disk, you will have already completed " -#~ "downloading and placing the needed files in ." -#~ msgstr "" -#~ "Για να ξεκινήσετε τον εγκαταστάτη από ένα σκληρό δίσκο, θα πρέπει να " -#~ "έχετε ήδη ολοκληρώσει το κατέβασμα και την τοποθέτηση των απαραίτητων " -#~ "αρχείων στο ." - -#~ 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 MANIFEST for details)." -#~ msgstr "" -#~ "Τουλάχιστον έξι διαφορετικές ramdisk μπορούν να χρησιμοποιηθούν για " -#~ "εκκίνηση από το σκληρό δίσκο, τρεις διαφορετικοί τύποι κάθε ένας με κα " -#~ "χωρίς υποστήριξη για έναν πυρήνα 2.2.x (δείτε το MANIFEST " -#~ "για λεπτομέρειες)." - -#~ msgid "" -#~ "The three different types of ramdisks are cdrom, " -#~ "hd-media, and nativehd. These " -#~ "ramdisks differ only in their source for installation packages. The " -#~ "cdrom ramdisk uses a cdrom to get debian-installer " -#~ "packages. The hd-media ramdisk uses an iso image " -#~ "file of a cdrom currently residing on a hard disk. Finally, the " -#~ "nativehd ramdisk uses the net to install packages." -#~ msgstr "" -#~ "Οι τρεις διαφορετικοί τύποι ramdisk είναι οι cdrom, " -#~ "hd-media, και nativehd. Αυτοί " -#~ "διαφέρουν μόνο στην πηγή τους για τα πακέτα της εγκατάστασης. Η " -#~ "cdrom ramdisk χρησιμοποιεί ένα cdrom για την " -#~ "απόκτηση των πακέτων του debian-installer. Η hd-media ramdisk χρησιμοποιεί το αρχείο μιας εικόνας iso ενός cdrom που " -#~ "βρίσκεται σε έναν σκληρό δίσκο. Τέλος, η nativehd " -#~ "ramdisk χρησιμοποιεί το δίκτυο για την εγκατάσταση των πακέτων." - -#~ msgid "Booting from AmigaOS" -#~ msgstr "Εκκίνηση από το AmigaOS" - -#~ msgid "" -#~ "In the Workbench, start the Linux installation process " -#~ "by double-clicking on the StartInstall icon in the " -#~ "debian directory." -#~ msgstr "" -#~ "Ευρισκόμενοι στο Workbench, ξεκινήστε τη διαδικασία " -#~ "της εγκατάστασης του Linux με διπλό κλικ στο εικονίδιο " -#~ "StartInstall στον κατάλογο debian." - -#~ 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 ." -#~ msgstr "" -#~ "Ίσως να πρέπει να πατήσετε το &enterkey; μετά την εμφάνιση σε ένα " -#~ "παράθυρο πληροφορίας αποσφαλμάτωσης από το πρόγραμμα του εγκαταστάτη στην " -#~ "Amiga. Μετά από αυτό η οθόνη θα γίνει γκρι, και θα υπάρξει μια " -#~ "καθυστέρηση μερικών δευτερολέπτων. Στη συνέχεια θα εμφανιστεί μια μαύρη " -#~ "οθόνη με άσπρο κείμενο που εμφανίζει κάθε είδους πληροφορία " -#~ "αποσφαλμάτωσης από την εκκίνηση του πυρήνα. Τα μηνύματα αυτά πιθανόν να " -#~ "τρέχουν πολυ γρήγορα για να τα διαβάσετε αλλά αυτό είναι εντάξει. Μετά " -#~ "από ένα-δύο δευτερόλεπτα, το πρόγραμμα εγκατάστασης θα ξεκινήσει αυτόματα " -#~ "οπότε μπορείτε να συνεχίσετε παρακάτω στο ." - -#~ msgid "Booting from Atari TOS" -#~ msgstr "Ξεκινώντας από το Atari TOS" - -#~ msgid "" -#~ "At the GEM desktop, start the Linux installation process by double-" -#~ "clicking on the bootstra.prg icon in the " -#~ "debian directory and clicking Ok at the program options dialog box." -#~ msgstr "" -#~ "Στο περιβάλλον εργασίας GEM, ξεκινήστε τη διαδικασία εγκατάστασης του " -#~ "Linux με διπλό-κλικ στο εικονίδιο bootstra.prg στον " -#~ "κατάλογο debian και πληκτρολογώντας Ok στο πλαίσιο διαλόγου των επιλογών του προγράμματος." - -#~ 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 ." -#~ msgstr "" -#~ "Ίσως να πρέπει να πατήσετε το &enterkey; μετά την εμφάνιση σε ένα " -#~ "παράθυρο πληροφορίας αποσφαλμάτωσης από το πρόγραμμα του εγκαταστάτη στον " -#~ "Atari. Μετά από αυτό η οθόνη θα γίνει γκρι, και θα υπάρξει μια " -#~ "καθυστέρηση μερικώνδευτερολέπτων. Στη συνέχεια θα εμφανιστεί μια μαύρη " -#~ "οθόνη με άσπρο κείμενο που εμφανίζει κάθε είδους πληροφορία " -#~ "αποσφαλμάτωσης από την εκκίνηση του πυρήνα. Τα μηνύματα αυτά πιθανόν να " -#~ "τρέχουν πολυ γρήγορα για να τα διαβάσετε αλλά αυτό είναι εντάξει. Μετά " -#~ "από ένα-δύο δευτερόλεπτα, το πρόγραμμα εγκατάστασης θα ξεκινήσει αυτόματα " -#~ "οπότε μπορείτε να συνεχίσετε παρακάτω στο ." - -#~ msgid "Booting from MacOS" -#~ msgstr "Ξεκινώντας από το MacOS" - -#~ msgid "" -#~ "You must retain the original Mac system and boot from it. It is " -#~ "essential that, when booting MacOS in preparation " -#~ "for booting the Penguin linux loader, you hold the shift " -#~ "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 "" -#~ "Πρέπει να διατηρήσετε το αρχικό Mac σύστημα και να εκκινήσετε από αυτό. " -#~ "Είναι ουσιώδες όταν ξεκινάτε το MacOS " -#~ "προετοιμάζοντας την εκκίνηση του φορτωτή Penguin linux, να κρατήσετε " -#~ "πατημένο το πλήκτρο shift ώστε να αποτρέψετε το φόρτωμα " -#~ "των επεκτάσεων του MacOS. Αν δεν χρησιμοποιήσετε το MacOS παρά μόνο για " -#~ "το φόρτωμα του linux, μπορείτε να πετύχετε το ίδιο αποτέλεσμα " -#~ "απομακρύνοντας όλες τις επεκτάσεις και τα πάνελ ρυθμίσεων από τον φάκελο " -#~ "Συστήματος του Mac. Διαφορετικά είναι πιθανό οι επεκτάσεις να " -#~ "εξακολουθούν να τρέχουν προκαλώντας έτσι απρόβλεπτα προβλήματα με τον " -#~ "τρέχοντα πυρήνα του linux." - -#~ msgid "" -#~ "Macs require the Penguin bootloader. If you do not " -#~ "have the tools to handle a Stuffit archive, &penguin19." -#~ "hfs; is an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." -#~ msgstr "" -#~ "Οι Mac απαιτούν τον φορτωτή εκκίνησης Penguin. Αν δεν " -#~ "έχετε τα εργαλεία για το χειρισμό ενός αρχείου Stuffit, το &penguin19.hfs; είναι μια εικόνα δίσκου hfs με " -#~ "αποσυμπιεσμένο τον φορτωτή Penguin. Η ενότητα περιγράφει πώς μπορείτε νααντιγράψετε αυτή " -#~ "την εικόνα σε μια δισκέττα." - -#~ msgid "" -#~ "At the MacOS desktop, start the Linux installation process by double-" -#~ "clicking on the Penguin Prefs icon in the " -#~ "Penguin directory. The Penguin " -#~ "booter will start up. Go to the Settings item " -#~ "in the File menu, click the Kernel tab. Select the kernel (vmlinuz) and " -#~ "ramdisk (initrd.gz) images in the install directory by clicking on the corresponding buttons in the upper " -#~ "right corner, and navigating the file select dialogs to locate the files." -#~ msgstr "" -#~ "Ενώ είσαστε στο MacOS desktop, ξεκινήστε τη διαδικασία της εγκατάστασης " -#~ "του Linux με διπλό-κλικ στο εικονίδιο Penguin Prefs " -#~ "στον κατάλογο Penguin. Ο φορτωτής Penguin θα ξεκινήσει. Πηγαίνετε στο αντικείμενο Settings στο μενού File, και πατήστε το " -#~ "Kernel tab. Επιλέξτε τον πυρήνα (vmlinuz) και τις εικόνες ramdisk (initrd.gz) στον " -#~ "κατάλογο install πατώντας τα αντίστοιχα κουμπιά στην " -#~ "πάνω δεξιάγωνία και κινούμενοι ανάμεσα στους διαλόγους επιλογής αρχείων " -#~ "για να εντοπίσετε τα συγκεκριμένα αρχεία." - -#~ msgid "" -#~ "To set the boot parameters in Penguin, choose File -" -#~ "> Settings..., then switch to the " -#~ "Options tab. Boot parameters may be typed in to the " -#~ "text entry area. If you will always want to use these settings, select " -#~ "File -> Save Settings as Default." -#~ msgstr "" -#~ "Για να θέσετε τις παραμέτρους εκκίνησης στο Penguin, επιλέξτε " -#~ "File -> Settings..., και " -#~ "μετά πηγαίνετε στο Options tab. Οι παράμετροι " -#~ "εκκίνησης μπορούν να τυπωθούν στην περιοχή εισόδου κειμένου. Αν θέλετε να " -#~ "χρησιμοποιείτε μόνιμα αυτές τις ρυθμίσεις επιλέξτε File -> Save Settings as Default." - -#~ msgid "" -#~ "Close the Settings dialog, save the settings and " -#~ "start the bootstrap using the Boot Now item in " -#~ "the File menu." -#~ msgstr "" -#~ "Κλείστε το διάλογο Settings dialog, αποθηκεύστε τις " -#~ "ρυθμίσεις και ξεκινήστε την διαδικασία εκκίνησης χρησιμοποιώντας το " -#~ "αντικείμενο Boot Now στο μενού File." - -#~ msgid "" -#~ "The Penguin 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 ." -#~ msgstr "" -#~ "Ο φορτωτής Penguin θα εμφανίσει κάποιες πληροφορίες " -#~ "αποσφαλμάτωσης σε ένα παράθυρο. Μετά από αυτό η οθόνη θα γίνει γκρι, και " -#~ "θα υπάρξει μια καθυστέρηση μερικών δευτερολέπτων. Στη συνέχεια θα " -#~ "εμφανιστεί μια μαύρη οθόνη με άσπρο κείμενο που εμφανίζει κάθε είδους " -#~ "πληροφορία αποσφαλμάτωσης από την εκκίνηση του πυρήνα. Τα μηνύματα αυτά " -#~ "πιθανόν να τρέχουν πολυ γρήγορα για να τα διαβάσετε αλλά αυτό είναι " -#~ "εντάξει. Μετά από ένα-δύο δευτερόλεπτα, το πρόγραμμα εγκατάστασης θα " -#~ "ξεκινήσει αυτόματα οπότε μπορείτε να συνεχίσετε παρακάτω στο ." - -#~ msgid "Booting from Q40/Q60" -#~ msgstr "Ξεκινώντας από το Q40/Q60" - -#~ msgid "FIXME" -#~ msgstr "ΔΙΟΡΘΩΣΕ ΜΕ" - -#~ msgid "" -#~ "The installation program should start automatically, so you can continue " -#~ "below at ." -#~ msgstr "" -#~ "Το πρόγραμμα εγκατάστασης θα ξεκινήσει αυτόματα οπότε μπορείτε να " -#~ "προχωρήσετε παρακάτω στο ." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitecture that supports CD-ROM " -#~ "booting is the BVME6000." -#~ msgstr "" -#~ "Προς το παρόν η μόνη &arch-title; υπο-αρχιτεκτονική που υποστηρίζει " -#~ "εκκίνηση από CD-ROM είναι η BVME6000." - -#~ msgid "" -#~ "After booting the VMEbus systems you will be presented with the LILO " -#~ "Boot: 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 "" -#~ "Μετά την εκκίνηση των συστημάτων VMEbus θα βρεθείτε μπροστά στο " -#~ "προτρεπτικό Boot: του LILO. Εκεί πληκτρολογήσετε ένα από " -#~ "τα ακόλουθα για να εκκινήσετε το Linux και να αρχίσετε την κανονική " -#~ "διαδικασία εγκατάστασης τουλογισμικού του Debian χρησιμοποιώντας " -#~ "προσομοίωση τερματικού vt102:" - -#~ msgid "type i6000 &enterkey; to install a BVME4000/6000" -#~ msgstr "" -#~ "πληκτρολογήστε i6000 &enterkey; για εγκατάσταση σε ένα " -#~ "BVME4000/6000" - -#~ msgid "type i162 &enterkey; to install an MVME162" -#~ msgstr "" -#~ "πληκτρολογήστε i162 &enterkey; για εγκατάσταση σε ένα " -#~ "MVME162" - -#~ msgid "type i167 &enterkey; to install an MVME166/167" -#~ msgstr "" -#~ "πληκτρολογήστε i167 &enterkey; για εγκατάσταση σε ένα " -#~ "MVME166/167" - -#~ msgid "" -#~ "You may additionally append the string TERM=vt100 to use " -#~ "vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." -#~ msgstr "" -#~ "Μπορείτε επιπρόσθετα να παραθέσετε τη συμβολοσειρά TERM=vt100 για χρήση προσομοίωσης τερματικού vt100, πχ., i6000 " -#~ "TERM=vt100 &enterkey;." - -#~ msgid "" -#~ "For most &arch-title; architectures, booting from a local filesystem is " -#~ "the recommended method." -#~ msgstr "" -#~ "Για τις περισσότερες &arch-title; υπο-αρχιτεκτονικές, η εκκίνηση από ένα " -#~ "τοπικό σύστημα αρχείων είναι η προτεινόμενη μέθοδος." - -#~ msgid "" -#~ "Booting from the boot floppy is supported only for Atari and VME (with a " -#~ "SCSI floppy drive on VME) at this time." -#~ msgstr "" -#~ "Αυτή τη στιγμή εκκίνηση από δισκέττα υποστηρίζεται μόνο για Atari και VME " -#~ "(με έναν οδηγό SCSI για δισκέττα στην VME)." - -#~ msgid "SGI TFTP Booting" -#~ msgstr "Εκκίνηση SGI Indy με TFTP" - -#~ msgid "" -#~ "After entering the command monitor use \n" -#~ "bootp():\n" -#~ " 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 netaddr environment variable. Type " -#~ "\n" -#~ "unsetenv netaddr\n" -#~ " in the command monitor to do this." -#~ msgstr "" -#~ "Σε συστήματα SGI Indys, μετά την είσοδο σας στην οθόνη εντολών, " -#~ "χρησιμοποιήστε την εντολή \n" -#~ " bootp():\n" -#~ " για να εκκινήσετε το linux και να αρχίσετε " -#~ "την εγκατάσταση του λογισμικού του Debian. Για να το πετύχετε αυτό ίσως " -#~ "να πρέπει να αφαιρέσετε την μεταβλητή περιβάλλοντος netaddr. Πληκτρολογήστε \n" -#~ "unsetenv netaddr\n" -#~ " στην οθόνη εντολών για να το κάνετε." - -#~ msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" -#~ msgstr "Εκκίνηση με TFTP για Broadcom BCM91250A και BCM91480B" - -#~ 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: " -#~ "\n" -#~ "ifconfig eth0 -auto\n" -#~ " Once you have obtained an IP address, you can " -#~ "load SiByl with the following command: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " 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 "" -#~ "Στις δοκιμαστικές μητρικές της Broadcom BCM91250A και BCM91480B , θα " -#~ "πρέπει αρχικά να φορτώσετε τον φορτωτή εκκίνησης SiByl μέσω TFTP που με " -#~ "τη σειρά του θα φορτώσει και θα ξεκινήσει τον εγκαταστάτη του Debian. " -#~ "Στις περισσότερες περιπτώσεις, θα πρέπει να πάρετε πρώτα μια διεύθυνση IP " -#~ "μέσω DHCP αλλά είναι πιθανόν να ρυθμίσετε και μια στατική διεύθυνση. Για " -#~ "να χρησιμοποιήσετε το DHCP, μπορείτε να δώσετε την ακόλουθη εντολή στο " -#~ "προτρεπτικό του CFE: \n" -#~ "ifconfig eth0 -auto\n" -#~ ". Έχοντας πάρει μια διεύθυνση IP, μπορείτε να " -#~ "φορτώσετε το SiByl με την ακόλουθη εντολή: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ ". Θα πρέπει να αντικαταστήσετε την διεύθυνση " -#~ "IP που αναφέρεται στο παράδειγμα είτε με το όνομα είτε με την IP " -#~ "διεύθυνση του TFTP server. Όταν δώσετε αυτή την εντολή, ο εγκαταστάτης θα " -#~ "ξεκινήσει αυτόματα." - -#~ msgid "Boot Parameters" -#~ msgstr "Παράμετροι εκκίνησης" - -#~ msgid "" -#~ "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." -#~ msgstr "" -#~ "Σε συστήματα SGI μπορείτε να παραθέσετε παραμέτρους εκκίνησης στην εντολή " -#~ "bootp(): στην οθόνη εντολών." - -#~ msgid "" -#~ "Following the bootp(): 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: \n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Further kernel parameters can be passed via " -#~ "append:" -#~ msgstr "" -#~ "Στο τέλος της εντολής bootp(): πορείτε να δώσετε " -#~ "τηνδιαδρομή και το όνομα του αρχείου εκκίνησης σε περίπτωση που δεν " -#~ "δώσατε ένα συγκεκριμένο όνομα μέσω του bootp/dhcp διακομιστή σας. Για " -#~ "παράδειγμα: \n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Επιπλέον παράμετροι του πυρήνα μπορούν να " -#~ "δωθούν μέσω της εντολής append:" - -#~ msgid "bootp(): append=\"root=/dev/sda1\"" -#~ msgstr "bootp(): append=\"root=/dev/sda1\" " - -#~ msgid "" -#~ "You cannot pass any boot parameters directly from the CFE prompt. " -#~ "Instead, you have to edit the /boot/sibyl.conf file " -#~ "on the TFTP server and add your parameters to the " -#~ "extra_args variable." -#~ msgstr "" -#~ "Δεν μπορείτε να περάσετε οποιεσδήποτε παραμέτρους εκκίνησης απυεθείας " -#~ "στοπροτρεπτικό CFE. Αντίθετα, θα πρέπει να επεξεργαστείτε τοαρχείο " -#~ "/boot/sibyl.conf που βρίσκεται στον διακομιστή TFTP " -#~ "και να προσθέσετε τις παραμέτρους σας στην μεταβλητή " -#~ "extra_args." - -#~ msgid "Cobalt TFTP Booting" -#~ msgstr "Εκκίνηση Cobalt με TFTP" - -#~ 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 /nfsroot. 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 "" -#~ "Αυστηρά μιλώντας, συστήματα Cobalt δεν χρησιμοποιούν TFTP αλλά NFS για " -#~ "την εκκίνησή τους. Θα πρέπει να εγκαταστήσετε έναν server NFS και να " -#~ "τοποθετήσετε τα αρχεία του εγκαταστάτη στο /nfsroot. " -#~ "Όταν ξεκινάτε το σύστημα Cobalt, θα πρέπει να πιέσετε το αριστερό και το " -#~ "δεξί κουμπί του κέρσορα ταυτόχρονα και το μηχάνημα θα εκκινήσει μέσω του " -#~ "δικτύου με NFS. Στην συνέχεια θα εμφανιστούν διάφορες επιλογές στην " -#~ "οθόνη. Υπάρχουν οι ακόλουθες δύο μέθοδοι εγκατάστασης:" - -#~ 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 "" -#~ "Μέσω SSH (προεπιλεγμένη): Στην περίπτωση αυτή, ο εγκαταστάτης θα ρυθμίσει " -#~ "το δίκτυο μέσω DHCP και θα ξεκινήσει έναν server SSH. Θα εμφανίσει τότε " -#~ "έναν τυχαίο κωδικό πρόσβασης και άλλες πληροφορίες πρόσβασης (όπως η " -#~ "διεύθυνση IP) στην οθόνη LCD του Cobalt. Όταν συνδεθείτε με το μηχάνημα " -#~ "μέσω ενός πελάτη SSH μπορείτε να ξεκινήσετε με την εγκατάσταση." - -#~ 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 "" -#~ "Μέσω σειριακής κονσόλας: Χρησιμοποιώντας ένα καλώδιο null modem, μπορείτε " -#~ "να συνδεθείτε στην σειριακή θύρα του μηχανήματός σας Cobalt " -#~ "(χρησιμοποιώντας ταχύτητα 115200 bps) και να κάνετε την εγκατάσταση μ' " -#~ "αυτόν τον τρόπο. Η επιλογή αυτή δεν είναι διαθέσιμη σε συστήματα Qube " -#~ "2700 (Qube1) αφού δεν διαθέτουν σειριακή θύρα." - -#~ msgid "" -#~ "You cannot pass any boot parameters directly. Instead, you have to edit " -#~ "the /nfsroot/default.colo file on the NFS server and " -#~ "add your parameters to the args variable." -#~ msgstr "" -#~ "Δεν μπορείτε να περάσετε παραμέτρους εκκίνησης απυεθείας. Αντίθετα, θα " -#~ "πρέπει να επεξεργαστείτε το αρχείο /nfsroot/default.colo στον server NFS και να προσθέσετε τις δικές σας παραμέτρους " -#~ "στην μεταβλητή args." - -#~ msgid "s390 Limitations" -#~ msgstr "Περιορισμοί των υπολογιστικών συστημάτων s390" - -#~ msgid "" -#~ "In order to run the installation system a working network setup and ssh " -#~ "session is needed on S/390." -#~ msgstr "" -#~ "Για να κάνετε την εγκατάσταση σε ένα σύστημα S/390 χρειάζεστε ένα σωστά " -#~ "ρυθμισμένοδίκτυο και δυνατότητα για ssh σύνδεση." - -#~ 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 an ssh session which will launch the standard " -#~ "installation system." -#~ msgstr "" -#~ "H διαδικασία εκκίνησης ξεκινά με τη ρύθμιση του δικτύου που σας προτρέπει " -#~ "ναδώσετε διάφορες παραμέτρους για το δίκτυο. Αν η ρύθμιση είναι επιτυχής, " -#~ "τότεθα μπείτε στο σύστημα ξεκινώντας μια σύνοδο ssh η οποία θα θέσει σε " -#~ "εκκίνηση τοκανονικό σύστημα εγκατάστασης ." - -#~ msgid "s390 Boot Parameters" -#~ msgstr "Παράμετροι Εκκίνησης για s390 " - -#~ 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 Device Drivers and Installation Commands for more " -#~ "information about S/390-specific boot parameters." -#~ msgstr "" -#~ "Σε συστήματα S/390 μπορείτε να παραθέσετε παραμέτρους εκκίνησης στο " -#~ "αρχείο parm.Το αρχείο αυτό μπορεί να είναι είτε σε ASCII είτε σε EBCDIC " -#~ "μορφή. Παρακαλούμε,διαβάστε το Device " -#~ "Drivers and Installation Commands για περισσότερες πληροφορίες " -#~ "σχετικά με παραμέτρους εκκίνησης συγκεκριμένα για συστήματα S/390." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitectures that support CD-ROM " -#~ "booting are PReP and New World PowerMacs. On PowerMacs, hold the " -#~ "c key, or else the combination of Command, Option, Shift, and " -#~ "Delete keys together while booting to boot from the CD-" -#~ "ROM." -#~ msgstr "" -#~ "Προς το παρόν, οι μόνες υπο-αρχιτεκτονικές &arch-title; που υποστηρίζουν " -#~ "εκκίνησηαπό CD-ROM είναι οι PReP και New World PowerMac. Σε έναν " -#~ "PowerMac, κρατήστεκάτω το πλήκτρο c , ή αλλιώς τον " -#~ "συνδυασμό των πλήκτρωνCommand, Option," -#~ "Shift, και Deleteκατά την εκκίνηση του " -#~ "μηχανήματος για να ξεκινήσετε από το CD-ROM." - -#~ 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 "" -#~ "Οι OldWorld PowerMac δεν θα ξεκινήσουν από ένα Debian CD, γιατί αυτοί " -#~ "οιυπολογιστές εξαρτώνται από την παρουσία ενός MacOS ROM οδηγού για το CD " -#~ "στο CD καιγια τον οποίον δεν υπάρχει προς το παρόν διαθέσιμη μια ελεύθερη " -#~ "έκδοση. Όλα τασυστήματα όμως OldWorld έχουν συσκευές δισκέττας οπότε " -#~ "χρησιμοποιήστε τονοδηγό της δισκέττας για την εκκίνηση του εγκαταστάτη " -#~ "και στη συνέχειακατευθύνετε τον εγκαταστάτη στο CD για την λήψη των " -#~ "απαραίτητων αρχείων." - -#~ 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 for booting from the " -#~ "hard disk, except use the path to yaboot on the CD at " -#~ "the OF prompt, such as" -#~ msgstr "" -#~ "Αν το σύστημά σας δεν ξεκινά κατευθείαν από το CD-ROM, παρ'ολ'αυτα " -#~ "μπορείτε ναχρησιμοποιήσετε το CD-ROM για να εγκαταστήσετε το σύστημα. Σε " -#~ "συστήματα NewWorld, μπορείτε να χρησιμοποιήσετε μια εντολή του " -#~ "OpenFirmwareγια να εκκινήσετε από το CD-ROM χειροκίνητα. Ακολουθήστε τις " -#~ "οδηγίες στο για εκκίνηση από τον σκληρό " -#~ "δίσκο, με τη διαφορά ότιπρέπει να δώσετε στο προτρεπτικό του OpenFirmware " -#~ "τη διαδρομή για το yaboot στo CD, για παράδειγμα" - -#~ msgid "0 > boot cd:,\\install\\yaboot" -#~ msgstr "0 > boot cd:,\\install\\yaboot " - -#~ msgid "Booting from Hard Disk" -#~ msgstr "Εκκίνηση από τον σκληρό δίσκο" - -#~ msgid "Booting CHRP from OpenFirmware" -#~ msgstr "Εκκίνηση της CHRP από το OpenFirmware" - -#~ msgid "Not yet written." -#~ msgstr "Δεν έχει γραφτεί ακόμη." - -#~ msgid "Booting OldWorld PowerMacs from MacOS" -#~ msgstr "Εκκίνηση OldWorld PowerMac από το MacOS" - -#~ msgid "" -#~ "If you set up BootX in , you can use it " -#~ "to boot into the installation system. Double click the BootX application icon. Click on the Options " -#~ "button and select Use Specified RAM Disk. This will " -#~ "give you the chance to select the ramdisk.image.gz " -#~ "file. You may need to select the No Video Driver " -#~ "checkbox, depending on your hardware. Then click the Linux button to shut down MacOS and launch the installer." -#~ msgstr "" -#~ "Αν ρυθμίσετε το BootX όπως στην ενότητα , μπορείτε να το χρησιμοποιήσετε για να εκκινήσετε το σύστημα " -#~ "εγκαταστάσης. Κάντε διπλό κλικ στο εικονίδιο της εφαρμογής " -#~ "BootX. Πατήστε το κουμπί Options και επιλέξτε Use Specified RAM Disk. Αυτό " -#~ "θα σας δώσει την ευκαιρία να διαλέξετε το αρχείο ramdisk.image." -#~ "gz. 'ισως χρειαστεί να τσεκάρετε την επιλογή No " -#~ "Video Driver, ανάλογα με το hardware του συστήματός σας. " -#~ "Πατήστε στην συνέχεια το κουμπί Linux για να " -#~ "σταματήσετε το MacOS και ξεκινήστε τον εγκαταστάτη." - -#~ msgid "Booting NewWorld Macs from OpenFirmware" -#~ msgstr "Εκκίνηση ενός NewWorld Mac από το OpenFirmware" - -#~ msgid "" -#~ "You will have already placed the vmlinux, " -#~ "initrd.gz, yaboot, and " -#~ "yaboot.conf files at the root level of your HFS " -#~ "partition in . Restart the computer, " -#~ "and immediately (during the chime) hold down the Option, " -#~ "Command (cloverleaf/Apple), o, and " -#~ "f keys all together. After a few seconds you will be " -#~ "presented with the Open Firmware prompt. At the prompt, type " -#~ "\n" -#~ "0 > boot hd:x,yaboot\n" -#~ " replacing x 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 ide0: instead of hd:. In a few more seconds you will see a yaboot prompt " -#~ "\n" -#~ "boot:\n" -#~ " At yaboot's boot: prompt, " -#~ "type either install or install " -#~ "video=ofonly followed by a &enterkey;. The " -#~ "video=ofonly argument is for maximum " -#~ "compatibility; you can try it if install doesn't " -#~ "work. The Debian installation program should start." -#~ msgstr "" -#~ "Θα έχετε ήδη τοποθετήσει τα αρχεία vmlinux, " -#~ "initrd.gz, yaboot, και " -#~ "yaboot.conf στη ρίζα της HFS διαμέρισής σας σύμφωνα " -#~ "με την ενότητα . Ξαναξεκινήστε τιον " -#~ "υπολογιστή, και αμέσως (κατά τη διάρκεια της επανεκκίνησης)κρατήστε " -#~ "ταυτόχρονα κάτω τα πλήκτρα Option, Command " -#~ "(cloverleaf/Apple),o, και f. " -#~ "Μετά από λίγα δευτερόλεπτα θα δείτε μπροστά σας το προτρεπτικό του Open " -#~ "Firmware. Εκεί, πληκτρολογήστε \n" -#~ "0 > boot hd:x,yaboot\n" -#~ " αντικαθιστώντας το x με τον αριθμό της HFS διαμέρισης όπου βρίσκονται τα αρχεία " -#~ "του πυρήνα και του yaboot, και στη συνέχεια πατήστε το &enterkey;. Σε " -#~ "μερικά μηχανήματα ίσως χρειαστεί να χρησιμοποιήσετε ide0: αντί για hd:. Σε μερικά ακόμα " -#~ "δευτερόλεπτα θα δείτε το προτρεπτικό του yaboot." -#~ "\n" -#~ "boot:\n" -#~ " Στο προτρεπτικό του yaboot boot:, πληκτρολογήστε είτε install ή " -#~ "install video=ofonly και στη συνέχεια &enterkey;. " -#~ "Το όρισμαvideo=ofonly είναι για μέγιστη " -#~ "συμβατότητα. Μπορείτε να τη δοκιμάσετε σε περίπτωση που η " -#~ "επιλογήinstall δεν δουλέψει. Το πρόγραμμα " -#~ "εγκατάστασης του Debian θα πρέπει τότε να ξεκινήσει." - -#~ msgid "Booting from USB memory stick" -#~ msgstr "Εκκίνηση από USB stick μνήμης" - -#~ msgid "" -#~ "Currently, NewWorld PowerMac systems are known to support USB booting." -#~ msgstr "" -#~ "Αυτήν την περίοδο, τα συστήματα NewWorld PowerMac είναι γνωστό οτι " -#~ "υποστηρίζουν εκκίνηση μέσω USB." - -#~ msgid "" -#~ "Make sure you have prepared everything from . 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 " -#~ "Command Option o f all together while booting (see " -#~ ")." -#~ msgstr "" -#~ "Σιγουρευτείτε ότι έχετε εφαρμόσει όλα όσα αναφέρονται στο . Για να εκκινήσετε ένα σύστημα Macintosh μέσω " -#~ "συσκευής μνήμης USB stick, θα πρέπει να χρησιμοποιήσετε την γραμμή " -#~ "εντολών του Open Firmware, αφού εξ ορισμού το Open Firmware δεν μπορεί να " -#~ "ψάξει για ανεύρεση συσκευών αποθήκευσης USB. Για να μεταβείτε στη γραμμή " -#~ "εντολών, στην διάρκεια της εκκίνησης του συστήματος Macintosh, κρατήστε " -#~ "πατημένα ταυτόχρονα τα πλήκτρα Command " -#~ "Option o f " -#~ "(see )." - -#~ msgid "" -#~ "You will need to work out where the USB storage device appears in the " -#~ "device tree, since at the moment ofpath cannot work " -#~ "that out automatically. Type dev / ls and " -#~ "devalias 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 usb0/disk, " -#~ "usb0/hub/disk, /pci@f2000000/usb@1b,1/" -#~ "disk@1, and /pci@f2000000/usb@1b,1/hub@1/disk@1 work." -#~ msgstr "" -#~ "Πρέπει να βρείτε που εμφανίζεται η συσκευή αποθήκευσης USB στο δένδρο των " -#~ "συσκευών, αφού προς το παρόν η εντολή ofpath δεν " -#~ "μπορεί να βρει αυτόματα αυτές τις συσκευές. Για να πάρεις ένα κατάλογο " -#~ "από όλες τις γνωστές συσκευές και τα ψευδώνυμα συσκευών πρέπει να " -#~ "γράψεις στην προτροπή του Open Firmware dev / ls " -#~ "και devalias. Στο σύστημα του συγγραφέα με " -#~ "διάφορους τύπους συσκευών μνήμης USB stick, το επιθυμητό αποτέλεσμα " -#~ "επιτυγχάνεται χρησιμοποιώντας ονόματα καταλόγων όπως usb0/disk,usb0/hub/disk,/pci@f2000000/" -#~ "usb@1b,1/disk@1, and /pci@f2000000/usb@1b,1/hub@1/" -#~ "disk@1." - -#~ msgid "" -#~ "Having worked out the device path, use a command like this to boot the " -#~ "installer: \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " The 2 matches the " -#~ "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot " -#~ "image earlier, and the ,\\\\:tbxi part instructs " -#~ "Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i." -#~ "e. yaboot) in the directory previously blessed with " -#~ "hattrib -b." -#~ msgstr "" -#~ "Έχοντας πλέον βρει τον κατάλογο της συσκευές, χρησιμοποιήστε μια εντολή " -#~ "σαν την παρακάτω για την εκκίνηση του εγκαστάτη: " -#~ "\n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " To 2 είναι το " -#~ "Apple_HFS ή Apple_Bootstrap τμήμα στο οποίο έχει αντιγραφεί πριν το " -#~ "είδωλο εκκίνησης, και το τμήμα ,\\\\:tbxi δίνει " -#~ "εντολή στο Open Firmware να εκκινήσει απ'αυτό το αρχείο με ένα HFS " -#~ "σύστημα αρχείων του \"tbxi\" (για παράδειγμα yaboot) " -#~ "στο κατάλογο τον προσδιορισμένο με ακρίβεια μέσω της hattrib -b." - -#~ msgid "" -#~ "The system should now boot up, and you should be presented with the " -#~ "boot: prompt. Here you can enter optional boot " -#~ "arguments, or just hit &enterkey;." -#~ msgstr "" -#~ "Τώρα το σύστημα θα πρέπει να εκκινήσει και θα παρουσιαστεί η προτροπή " -#~ "boot:. Σε αυτή την προτροπή μπορείτε να εισάγετε " -#~ "προαιρετικά ορίσματα εκκίνησης ή απλώς να πατήσετε το &enterkey;." - -#~ 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 ." -#~ msgstr "" -#~ "Αυτή η μέθοδος εκκίνησης είναι καινούργια και μπορεί, σε μερικά συστήματα " -#~ "NewWorld, να αντιμετωπίσετε δυσκολίες στην εφαρμογή της. Αν " -#~ "αντιμετωπίσετε προβλήματα , παρακαλώ να αρχειοθετήσετε μια έκθεση " -#~ "εγκατάστασης, όπως εξηγείται στο ." +#. 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 "Ξεκινώντας τον εγκαταστάτη στην αρχιτεκτονική &arch-title;" + +#. Tag: title +#: boot-installer.xml:20 +#, no-c-format +msgid "Alpha Console Firmware" +msgstr "Κονσόλα Firmware σε Alpha" + +#. 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 "" +"Το firmware της κονσόλας αποθηκεύεται σε μια μνήμη flash ROM και ξεκινά όταν " +"ένα σύστημα Alpha μπαίνει σε λειτουργία ή επαναξεκινά. Υπάρχουν δυο " +"διαφορετικές προδιαγραφές για τις κονσόλες που χρησιμοποιούνται στα " +"συστήματα Alpha, και κατά συνέπειαν είναι διαθέσιμες δυο διαφορετικές " +"κλάσεις firmware για κονσόλα:" + +#. Tag: para +#: boot-installer.xml:31 +#, no-c-format +msgid "" +"SRM console, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." +msgstr "" +"κονσόλα SRM, βασισμένη στις προδιαγραφές του Alpha " +"Console Subsystem, που παρέχει ένα λειτουργικό περιβάλλον για τα λειτουργικά " +"συστήματα OpenVMS, Tru64 UNIX, και Linux." -#~ msgid "Currently, PReP and New World PowerMac systems support netbooting." -#~ msgstr "" -#~ "Προς το παρόν, μόνο συστήματα PReP και New World PowerMac υποστηρίζουν " -#~ "εκκίνηση από το δίκτυο." +#. Tag: para +#: boot-installer.xml:38 +#, no-c-format +msgid "" +"ARC, AlphaBIOS, or ARCSBIOS console, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." +msgstr "" +"Κονσόλες ARC, AlphaBIOS, ή ARCSBIOS, βασισμένες στις " +"προδιαγραφές Advanced RISC Computing (ARC), και παρέχουν ένα λειτουργικό " +"περιβάλλον για Windows NT." -#~ msgid "" -#~ "On machines with Open Firmware, such as NewWorld Power Macs, enter the " -#~ "boot monitor (see ) and use the " -#~ "command boot enet:0. PReP and CHRP boxes may have " -#~ "different ways of addressing the network. On a PReP machine, you should " -#~ "try boot server_ipaddr," -#~ "file,client_ipaddr." -#~ msgstr "" -#~ "Σε μηχανήματα με Open Firmware, όπως NewWorld Power Mac, μπείτε στην " -#~ "οθόνη εκκίνησης (δείτε το ) και " -#~ "χρησιμοποιήστε την εντολή boot enet:0. Τα συστήματα " -#~ "PReP και CHRP ίσως να έχουν διαφορετικούς τρόπους χειρισμού του δικτύου. " -#~ "Σε ένα μηχάνημα PReP, θα μπορούσατε να δοκιμάσετε boot " -#~ "server_ipaddr,file," -#~ "client_ipaddr." +#. 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 "" +"Από τη σκοπιά του χρήστη, η σπουδαιότερη διαφορά ανάμεσα στα περιβάλλοντα " +"SRM και ARC είναι ότι η επιλογή της κονσόλας περιορίζει (δεσμεύει) το πιθανό " +"σχήμα διαμέρισης για τον δίσκο από τον οποίο επιθυμείτε να εκκινήσετε." -#~ 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 "" -#~ "Εκκίνηση από δισκέττες υποστηρίζεται από την αρχιτεκτονική &arch-title;, " -#~ "αν και γενικά είναι εφαρμόσιμη στα συστήματα OldWorld. Τα συστήματα " -#~ "NewWorld δεν είναι εφοδιασμένα με συσκευές δισκέττας και δεν " -#~ "υποστηρίζονται για εκκίνηση προσαρτώμενες USB συσκευές δισκέττας." +#. Tag: para +#: boot-installer.xml:54 +#, no-c-format +msgid "" +"ARC requires that you use an MS-DOS partition table (as created by " +"cfdisk) for the boot disk. Therefore MS-DOS partition " +"tables are the native 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 "" +"Η ARC απαιτεί να χρησιμοποιήσετε έναν MS-DOS πίνακα διαμέρισης (καθώς " +"δημιουργείται με την εντολή cfdisk) για το δίσκο " +"εκκίνησης. Συνεπώς πίνακες διαμέρισης MS-DOS είναι η φυσική " +"μορφή διαμέρισης για εκκίνηση από ARC. Στην πραγματικότητα, καθώς το " +"AlphaBIOS περιλαμβάνει ένα εργαλείο διαμέρισης δίσκων, πιθανόν να " +"προτιμήσετε να διαμερίσετε τους δίσκους σας από τα μενού για το firmware " +"πριν την εγκατάσταση του Linux." + +#. Tag: para +#: boot-installer.xml:63 +#, no-c-format +msgid "" +"Conversely, SRM is incompatible " +"Specifically, the bootsector format required by the Console Subsystem " +"Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " +"BSD disklabel format, this is the native partition format for " +"SRM installations." +msgstr "" +"Αντίθετα, η κονσόλα SRM είναι ασύμβατη με πίνακες " +"διαμέρισης MS-DOS. Συγκεκριμένα, ο τύπος του bootsector που " +"προϋποθέτει η προδιαγραφή Console Subsystem Specification συγκρούεται με την " +"τοποθέτηση του πίνακα διαμέρισης από το DOS. Μιας και το " +"Tru64 Unix χρησιμοποιεί τον τύπο επικεφαλίδας δίσκου (disklabel) του BSD, " +"αυτός είναι και ο φυσικός τύπος διαμέρισης για εγκαταστάσεις " +"σε SRM." + +#. 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 "" +"Επειδή το GNU/Linux είναι το μοναδικό λειτουργικό σύστημα για την " +"αρχιτεκτονική Alpha που μπορεί να εκκινήσει και από τους δύο τύπους " +"κονσόλας, η επιλογή σας θα εξαρτάται επίσης από το ποια άλλα λειτουργικά " +"συστήματα θα θέλατε να χρησιμοποιήσετε στο ίδιο μηχάνημα. Όλα τα άλλα τύπου " +"UNIX λειτουργικά συστήματα (Tru64 Unix, FreeBSD, OpenBSD, και NetBSD) και το " +"OpenVMS μπορούν να ξεκινήσουν μόνο από την κονσόλα SRM, ενώ τα Windows NT " +"μπορούν να εκκινήσουν μόνο από ARC." + +#. Tag: para +#: boot-installer.xml:87 +#, no-c-format +msgid "" +"Because MILO 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 "" +"Επειδή ο φορτωτής MILO δεν είναι διαθέσιμος για κανένα " +"από τα συστήματα Alpha σε παραγωγή αυτή τη στιγμή (τον Φεβρουάριο του 2000), " +"και καθώς δεν είναι πια απαραίτητο να αγοράσετε μια άδεια OpenVMS ή Tru64 " +"Unix για να έχετε SRM firmware στο παλιότερο σύστημά σας Alpha, σας " +"συνιστούμε να χρησιμοποιήσετε την κονσόλα SRM." + +#. Tag: para +#: boot-installer.xml:95 +#, no-c-format +msgid "" +"The following table summarizes available and supported system type/console " +"combinations (see for the system type names). " +"The word ARC below denotes any of the ARC-compliant consoles." +msgstr "" +"Ο επόμενος πίνακας συνοψίζει τους διαθέσιμους και υποστηριζόμενους " +"συνδυασμούς τύπου συστήματος/κονσόλας (δείτε " +"για τα ονόματα των τύπων συστημάτων). Η λέξη ARC παρακάτω " +"δηλώνει οποιαδήποτε συμβατή με ARC κονσόλα." + +#. 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 "alcor " + +#. 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 "ARC ή SRM" + +#. Tag: entry +#: boot-installer.xml:117 +#, no-c-format +msgid "avanti" +msgstr "avanti " + +#. Tag: entry +#: boot-installer.xml:120 +#, no-c-format +msgid "book1" +msgstr "book1 " + +#. 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 "μόνο SRM" + +#. Tag: entry +#: boot-installer.xml:123 +#, no-c-format +msgid "cabriolet" +msgstr "cabriolet " + +#. Tag: entry +#: boot-installer.xml:126 +#, no-c-format +msgid "dp264" +msgstr "dp264 " + +#. Tag: entry +#: boot-installer.xml:129 +#, no-c-format +msgid "eb164" +msgstr "eb164 " + +#. Tag: entry +#: boot-installer.xml:132 +#, no-c-format +msgid "eb64p" +msgstr "eb64p " + +#. Tag: entry +#: boot-installer.xml:135 +#, no-c-format +msgid "eb66" +msgstr "eb66 " + +#. Tag: entry +#: boot-installer.xml:138 +#, no-c-format +msgid "eb66p" +msgstr "eb66p " + +#. Tag: entry +#: boot-installer.xml:141 +#, no-c-format +msgid "jensen" +msgstr "jensen " + +#. Tag: entry +#: boot-installer.xml:144 +#, no-c-format +msgid "lx164" +msgstr "lx164 " + +#. Tag: entry +#: boot-installer.xml:147 +#, no-c-format +msgid "miata" +msgstr "miata " + +#. Tag: entry +#: boot-installer.xml:150 +#, no-c-format +msgid "mikasa" +msgstr "mikasa " + +#. Tag: entry +#: boot-installer.xml:153 +#, no-c-format +msgid "mikasa-p" +msgstr "mikasa-p " + +#. Tag: entry +#: boot-installer.xml:156 +#, no-c-format +msgid "nautilus" +msgstr "nautilus " + +#. Tag: entry +#: boot-installer.xml:157 +#, no-c-format +msgid "ARC (see motherboard manual) or SRM" +msgstr "ARC (βλ. εγχειρίδιο μητρικής) ή SRM" + +#. Tag: entry +#: boot-installer.xml:159 +#, no-c-format +msgid "noname" +msgstr "noname " + +#. Tag: entry +#: boot-installer.xml:162 +#, no-c-format +msgid "noritake" +msgstr "noritake " + +#. Tag: entry +#: boot-installer.xml:165 +#, no-c-format +msgid "noritake-p" +msgstr "noritake-p " + +#. Tag: entry +#: boot-installer.xml:168 +#, no-c-format +msgid "pc164" +msgstr "pc164 " + +#. Tag: entry +#: boot-installer.xml:171 +#, no-c-format +msgid "rawhide" +msgstr "rawhide " + +#. Tag: entry +#: boot-installer.xml:174 +#, no-c-format +msgid "ruffian" +msgstr "ruffian " + +#. Tag: entry +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#, no-c-format +msgid "ARC only" +msgstr "μόνο ARC" + +#. Tag: entry +#: boot-installer.xml:177 +#, no-c-format +msgid "sable" +msgstr "sable " + +#. Tag: entry +#: boot-installer.xml:180 +#, no-c-format +msgid "sable-g" +msgstr "sable-g " + +#. Tag: entry +#: boot-installer.xml:183 +#, no-c-format +msgid "sx164" +msgstr "sx164 " + +#. Tag: entry +#: boot-installer.xml:186 +#, no-c-format +msgid "takara" +msgstr "takara " + +#. Tag: entry +#: boot-installer.xml:189 +#, no-c-format +msgid "xl" +msgstr "xl" + +#. Tag: entry +#: boot-installer.xml:192 +#, no-c-format +msgid "xlt" +msgstr "xlt" + +#. 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, " +"aboot, a small, platform-independent bootloader, is used. " +"See the (unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"Γενικά, καμία από τις κονσόλες αυτές δεν μπορεί να εκκινήσει το Linux " +"κατευθείαν, επομένως απαιτείται η βοήθεια ενός ενδιάμεσου φορτωτή εκκίνησης. " +"Για την κονσόλα SRM, χρησιμοποιείται το aboot, ένας " +"μικρός, ανεξάρτητος πλατφόρμας φορτωτής εκκίνησης. Δείτε επίσης και το " +"(δυστυχώς ξεπερασμένο) SRM HOWTO για " +"περισσότερες πληροφορίες για το aboot." + +#. 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 "" +"Οι ακόλουθες παράγραφοι έχουν παρθεί από το εγχειρίδιο εγκατάστασης του " +"woody, και συμπεριλαμβάνονται για λόγους αναφοράς, πιθανόν να χρησιμεύσουν " +"σε κάποιον αργότερα όταν το Debian υποστηρίξει ξανά εγκατάσταση με MILO." -#~ msgid "" -#~ "To boot from the boot-floppy-hfs.img floppy, place " -#~ "it in floppy drive after shutting the system down, and before pressing " -#~ "the power-on button." -#~ msgstr "" -#~ "Για εκκίνηση από την εικόνα δισκέττας boot-floppy-hfs.img, βάλτε τη δισκέττα στον οδηγό μετά το σβήσιμο του μηχανήματος " -#~ "και πριν πατήσετε τον διακόπτη για την επανεκκίνηση." +#. 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: MILO and aboot." +msgstr "" +"Γενικά, καμία από τις κονσόλες αυτές δεν μπορεί να εκκινήσει το Linux " +"κατευθείαν, επομένως απαιτείται η βοήθεια ενός ενδιάμεσου φορτωτή εκκίνησης. " +"Υπάρχουν δυο κύριοι φορτωτές Linux: MILO και " +"aboot." + +#. Tag: para +#: boot-installer.xml:221 +#, no-c-format +msgid "" +"MILO is itself a console, which replaces ARC or SRM in " +"memory. MILO can be booted from both ARC and SRM and is " +"the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) " +"MILO HOWTO." +msgstr "" +"Ο MILO είναι ο ίδιος μια κονσόλα, που αντικαθιστά την ARC " +"ή την SRM στην μνήμη. Ο MILO μπορεί να ξεκινήσει τόσο από " +"την ARC όσο και την SRM και είναι ο μόνος τρόπος να ξεκινήσει (bootstrap) το " +"Linux από την κονσόλα ARC. Ο MILO εξαρτάται από την " +"συγκεκριμένη πλατφόρμα (οπότε ένας διαφορετικός MILO " +"χρειάζεται για κάθε τύπο συστήματος) και υπάρχει μόνο για εκείνα τα " +"συστήματα στον παραπάνω πίνακα όπου εμφανίζεται υποστήριξη για ARC. Δείτε " +"επίσης και το (δυστυχώς ξεπερασμένο) MILO " +"HOWTO." + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "" +"aboot is a small, platform-independent bootloader, which " +"runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"Το aboot είναι ένας μικρός, ανεξάρτητος από την " +"πλατφόρμα, φορτωτής εκκίνησης, που τρέχει μόνο στην κονσόλα SRM. Δείτε " +"επίσης το (επίσης δυστυχώς ξεπερασμένο) SRM " +"HOWTO για περισσότερες πληροφορίες σχετικά με το aboot." + +#. 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 MILO is available: " +"\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Because MILO 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 aboot on new installations of GNU/Linux, " +"unless you wish to dual-boot with Windows NT." +msgstr "" +"Έτσι, υπάρχουν γενικά τρία πιθανά σενάρια, ανάλογα με το firmware της " +"κονσόλας του συστήματος και το κατά πόσον είναι διαθέσιμος ο MILO: \n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Επειδή ο φορτωτής MILO δεν " +"είναι διαθέσιμος για κανένα από τα συστήματα Alpha σε παραγωγή αυτή τη " +"στιγμή (τον Φεβρουάριο του 2000), και καθώς δεν είναι πια απαραίτητο να " +"αγοράσετε μια άδεια OpenVMS ή Tru64 Unix για να έχετε SRM firmware στο " +"παλιότερο σύστημά σας Alpha, σας συνιστούμε να χρησιμοποιήσετε την κονσόλα " +"SRM και τον aboot σε νέες εγκαταστάσεις του GNU/Linux, " +"εκτός και αν επιθυμείτε να έχετε διπλή-εκκίνηση με Windows NT." + +#. 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 half-flash 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 arc command). For the reasons mentioned above, " +"we recommend switching to SRM before installing &debian;." +msgstr "" +"Η πλειοψηφία των AlphaServers και όλων των τωρινών προϊόντων διακομιστών και " +"σταθμών εργασίας περιλαμβάνουν και την SRM και AlphaBIOS στο firmware τους. " +"Για μηχανήματα half-flash όπως διάφορες πλατφόρμες δοκιμών, " +"είναι δυνατόν να αλλάξει κανείς από την μια στην άλλη με επαναρχικοποίηση " +"(reflashing) του firmware. Επίσης, από τη στιγμή της εγκατάστασης της SRM, " +"είναι δυνατόν να τρέξει κανείς ARC/AlphaBIOS από μια δισκέττα " +"(χρησιμοποιώντας την εντολή arc). Για τουςλόγους που " +"αναφέρθηκαν παραπάνω, συνιστούμε να αλλάξετε στην κονσόλα SRM πριν την " +"εγκατάσταση του &debian;." + +#. Tag: para +#: boot-installer.xml:264 +#, no-c-format +msgid "" +"As on other architectures, you should install the newest available revision " +"of the firmware Except on Jensen, where Linux is not " +"supported on firmware versions newer than 1.7 — see for more information. before " +"installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." +msgstr "" +"Όπως και με άλλες αρχιτεκτονικές, θα πρέπει να εγκαταστήσετε τις πιο " +"πρόσφατες διαθέσιμες εκδόσεις του firmware Με εξαίρεση την " +"Jensen, όπου το Linux δεν υποστηρίζεται για εκδόσεις του firmware " +"μεταγενέστερες από την 1.7 - δείτε τη σελίδα για περισσότερες πληροφορίες πριν " +"εγκαταστήσετε το &debian;. Για την Alpha, αναβαθμίσεις του firmware μπορούν " +"να ληφθούν από τη σελίδα Alpha Firmware " +"Updates." + +#. Tag: title +#: boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 +#: boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 +#: boot-installer.xml:2500 boot-installer.xml:2596 +#, no-c-format +msgid "Booting with TFTP" +msgstr "Εκκίνηση μέσω TFTP" + +#. Tag: para +#: boot-installer.xml:284 +#, no-c-format +msgid "" +"In SRM, Ethernet interfaces are named with the ewa " +"prefix, and will be listed in the output of the show dev command, like this (edited slightly): \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" +" You first need to set the boot protocol: " +"\n" +">>> set ewa0_protocols bootp\n" +" Then check the medium type is correct: " +"\n" +">>> set ewa0_mode mode\n" +" You can get a listing of valid modes with " +">>>set ewa0_mode." +msgstr "" +"Στην SRM, οι διεπαφές Ethernet ονοματοδοτούνται με το πρόθεμα " +"ewa, και θα εμφανιστούν στην έξοδο της εντολής " +"show dev κάπως έτσι (ελαφρά διορθωμένα ): " +"\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" +" Πρέπει κατ' αρχήν να ορίσετε το πρωτόκολλο " +"εκκίνησης: \n" +">>> set ewa0_protocols bootp\n" +" Στη συνέχεια ελέγξτε ότι ο τύπος του μέσου είναι " +"ο σωστός: >>> set ewa0_mode " +"mode\n" +" Μπορείτε να πάρετε μια λίστα των έγκυρων τύπων " +"με την εντολή >>>set ewa0_mode." + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "" +"Then, to boot from the first Ethernet interface, you would type: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" This will boot using the default kernel " +"parameters as included in the netboot image." +msgstr "" +"Μετά, για να εκκινήσετε από το πρώτο Ethernet interface, θα πρέπει να " +"τυπώσετε: \n" +">>> boot ewa0 -flags \"\"\n" +" Αυτό θα δώσει εκκίνηση με τις προκαθορισμένες " +"παραμέτρους στον πυρήνα όπως περιλαμβάνεται στην εικόνα του netboot." + +#. Tag: para +#: boot-installer.xml:311 +#, no-c-format +msgid "" +"If you wish to use a serial console, you must pass the " +"console= parameter to the kernel. This can be done " +"using the -flags argument to the SRM boot command. The serial ports are named the same as their " +"corresponding files in /dev. 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 ewa0 and use a console on the first serial port, you would type:" +msgstr "" +"Αν θέλετε να χρησιμοποιήσετε μια σειριακή κονσόλα, θα πρέπει να περάσετε την παράμετρο console= στον " +"πυρήνα. Αυτό μπορεί να γίνει χρησιμοποιώντας το όρισμα -flagsστην εντολή boot της κονσόλας SRM. Oι " +"σειριακές θύρες έχουν τα ονόματα των αντίστοιχων τους αρχείων στον κατάλογο " +"/dev. Για παράδειγμα, για να ξεκινήσετε από το " +"interface ewa0 και να χρησιμοποιήσετε μια κονσόλα " +"στην πρώτη σειριακή θύρα θα πρέπει να πληκτρολογήσετε:" + +#. Tag: screen +#: boot-installer.xml:323 +#, no-c-format +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0" " + +#. Tag: title +#: boot-installer.xml:328 +#, no-c-format +msgid "Booting from CD-ROM with the SRM Console" +msgstr "Εκκινώντας από CD-ROM με την κονσόλα SRM" + +#. Tag: para +#: boot-installer.xml:329 +#, no-c-format +msgid "" +"Type \n" +">>> boot xxxx -flags 0\n" +" where xxxx is your CD-" +"ROM drive in SRM notation." +msgstr "" +"Τυπώστε \n" +">>> boot xxxx -flags 0\n" +" όπου xxxx είναι η " +"μονάδα CD-ROM σε μορφή κατάλληλη για το SRM." + +#. Tag: title +#: boot-installer.xml:341 +#, no-c-format +msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" +msgstr "Εκκίνηση από CD-ROM με την κονσόλα ARC ή AlphaBIOS" + +#. 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 ), then enter \\milo\\linload." +"exe as the boot loader and \\milo" +"\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS " +"Selection Setup' menu. Ruffians make an exception: You need to use " +"\\milo\\ldmilo.exe as boot loader." +msgstr "" +"Για να εκκινήσετε ένα CD-ROM από κονσόλα ARC, βρείτε το κωδικό όνομα της " +"υποαρχιτεκτονικής σας (δείτε το ), στη " +"συνέχεια πληκτρολογήστε \\milo\\linload.exe σαν τον " +"φορτωτή εκκίνησης καθώς και \\milo\\subarch (όπου subarch είναι το " +"κανονικό όνομα της υποαρχιτεκτονικής σας) σαν το OS Path στο μενού `OS " +"Selection Setup'. Τα Ruffians αποτελούν εξαίρεση:θα πρέπει να " +"χρησιμοποιήσετε \\milo\\ldmilo.exe σαν φορτωτή " +"εκκίνησης." + +#. Tag: title +#: boot-installer.xml:358 +#, no-c-format +msgid "Booting from Floppies with the SRM Console" +msgstr "Εκκίνηση από δισκέττες με την κονσόλα SRM" + +#. Tag: para +#: boot-installer.xml:359 +#, no-c-format +msgid "" +"At the SRM prompt (>>>), issue the following " +"command: \n" +">>> boot dva0 -flags 0\n" +" possibly replacing dva0 " +"with the actual device name. Usually, dva0 is the " +"floppy; type \n" +">>> show dev\n" +" to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. If everything works OK, you will eventually see the Linux kernel " +"boot." +msgstr "" +"Στην προτροπή της SRM (>>>), δώστε την παρακάτω " +"εντολή: \n" +">>> boot dva0 -flags 0n πιθανόν " +"αντικαθιστώντας το dva0 με το όνομα της πραγματικής " +"συσκευής. Συνήθως dva0 είναι η συσκευή δισκέττας. " +"Πληκτρολογήστε \n" +">>> show dev\n" +" για να δείτε τη λίστα των συσκευών (πχ., αν " +"θέλετε να εκκινήσετε από ένα CD). Σημειώστε ότι αν εκκινείτε μέσω MILO, το " +"όρισμα -flags δεν λαμβάνεται υπόψιν, οπότε μπορείτε απλά " +"να πληκτρολογήσετε boot dva0. Αν όλα πάνε καλά, θα δείτε " +"τελικά τον πυρήνα του Linux να ξεκινά." + +#. Tag: para +#: boot-installer.xml:376 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via aboot, use the following command: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (typed on one line), substituting, if necessary, " +"the actual SRM boot device name for dva0, the Linux " +"boot device name for fd0, and the desired kernel " +"parameters for arguments." +msgstr "" +"Αν θέλετε να προσδιορίσετε κάποιες παραμέτρους του πυρήνα όταν εκκινείτε " +"μέσω του aboot, χρησιμοποιήστε την ακόλουθη εντολή: " +"\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (δοσμένη σε μια γραμμή),αντικαθιστώντας, αν " +"είναι απαραίτητο, το όνομα της πραγματικής SRM συσκευής αντί του " +"dva0, το όνομα της συσκευής εκκίνησης στο Linux αντί " +"του fd0, και τις επιθυμητές παραμέτρους του πυρήνα για " +"τα ορίσματα arguments." + +#. Tag: para +#: boot-installer.xml:388 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See " +"." +msgstr "" +"Αν θέλετε να προσδιορίσετε παραμέτρους για τον πυρήνα ενώ ξεκινάτε με το " +"MILO, θα πρέπει να διακόψετε την διαδικασία " +"πρωτοεκκίνησης (bootstrap) μόλις μπείτε στο MILO. Δείτε το ." + +#. Tag: title +#: boot-installer.xml:398 +#, no-c-format +msgid "Booting from Floppies with the ARC or AlphaBIOS Console" +msgstr "Εκκινώντας από δισκέττες με την κονσόλα ARC ή AlphaBIOS" + +#. Tag: para +#: boot-installer.xml:400 +#, no-c-format +msgid "" +"In the OS Selection menu, set linload.exe as the boot " +"loader, and milo as the OS Path. Bootstrap using the " +"newly created entry." +msgstr "" +"Στο μενού OS Selection, ορίστε το linload.exe σαν φορτωτή " +"εκκίνησης, και το milo σαν OS Path. Ξεκινήστε (bootstrap) " +"χρησιμοποιώντας την επιλογή που μόλις δώσατε." + +#. Tag: title +#: boot-installer.xml:409 +#, no-c-format +msgid "Booting with MILO" +msgstr "Εκκίνηση με MILO" + +#. 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 "" +"Ο MILO που περιλαμβάνεται στα μέσα της πρωτοεκκίνησης είναι ρυθμισμένος ώστε " +"αυτόματα να προχωρά στο Linux κατευθείαν. Σε περίπτωση που θα θέλατε να " +"παρέμβετε στη διαδικασία, το μόνο που χρειάζεται να κάνετε είναι να πατήσετε " +"το πλήκτρο space στη διάρκεια της αντίστροφης μέτρησης του MILΟ." + +#. 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: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Αν θέλετε να προσδιορίσετε όλα τα στοιχεία εκπεφρασμένα (για παράδειγμα, να " +"δώσετε επιπλέον παραμέτρους), μπορείτε να χρησιμοποιήσετε μια εντολή όπως " +"αυτή: \n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Haluttaessa määrittää kaikki yksityiskohdat tarkkaan (esimerkiksi antaa " +"lisäparametreja), voidaan käyttää tämän tapaista komentoa: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" -#~ " Jos käynnistetään muulta laitteelta kuin " -#~ "levyke, kirjoita yllä olevassa esimerkissä fd0:n " -#~ "tilalle oikean laitteen nimi Linuxin merkintätavalla. Komennolla " -#~ "help näkee lyhyen MILO:n komentojen luettelon." - -#~ msgid "Booting from TFTP" -#~ msgstr "Käynnistäminen TFTP:llä" - -#~ msgid "" -#~ "Booting from the network requires that you have a network connection and " -#~ "a TFTP network boot server (DHCP, RARP, or BOOTP)." -#~ msgstr "" -#~ "Käynnistäminen verkosta edellyttää verkkoyhteyttä ja TFTP-" -#~ "käynnistyspalvelinta (DHCP, RARP, tai BOOTP)." - -#~ msgid "" -#~ "Older systems such as the 715 might require the use of an RBOOT server " -#~ "instead of a BOOTP server." -#~ msgstr "" -#~ "Vanhoissa järjestelmissä kuten 715 saatetaan joutua käyttämään RBOOT-" -#~ "palvelinta BOOTP:n tilalla." - -#~ msgid "" -#~ "The installation method to support network booting is described in ." -#~ msgstr "" -#~ "Verkosta käynnistämistä tukeva asennustapa kuvataan kohdassa ." - -#~ msgid "Booting from TFTP on Netwinder" -#~ msgstr "Käynnistäminen TFTP:llä Netwinderissa" - -#~ msgid "" -#~ "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " -#~ "(which is generally referred to as eth0) 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 interface (the " -#~ "one labeled with 10 Base-T)." -#~ msgstr "" -#~ "Netwindereissa on kaksi verkkoliitäntää: 10 Mbit NE2000-yhteensoiva " -#~ "kortti (johon yleensä viitataan nimellä eth0) ja 100 " -#~ "Mbit Tulip-kortti. Otoksen noutamisessa 100 Mbit-kortilla saattaa olla " -#~ "pulmia, joten suositellaan käytettävän 10 Mbit-liitäntää (se, jossa lukee " -#~ "10 Base-T)." - -#~ 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 ." -#~ msgstr "" -#~ "Asennusjärjestelmän käynnistämiseen tarvitaan NeTTrom 2.2.1 tai uudempi, " -#~ "suositellaan versiota 2.3.3. Harmittavasti laiteohjelmatiedostoja ei " -#~ "tällä hetkellä ole saatavilla käyttöoikeussyistä. Jos tämä tilanne " -#~ "muuttuu, uudet otokset saattavat löytyä osoitteesta ." - -#~ 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: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Furthermore, you must configure the network, " -#~ "either with a static address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " where 24 is the number of set bits in the " -#~ "netmask, or a dynamic address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " You may also need to configure the " -#~ "route1 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. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Now you have to tell the firmware that the " -#~ "TFTP image should be booted: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " If you use a serial console to install your " -#~ "Netwinder, you need to add the following setting: " -#~ "\n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Alternatively, for installations using a " -#~ "keyboard and monitor you have to set: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " You can use the printenv " -#~ "command to review your environment settings. After you have verified that " -#~ "the settings are correct, you can load the image: " -#~ "\n" -#~ " NeTTrom command-> boot\n" -#~ " In case you run into any problems, a detailed " -#~ "HOWTO is available." -#~ msgstr "" -#~ "Kun Netwinderia käynnistetään on käynnistysprosessi keskeytettävä " -#~ "lähtölaskennan aikana. Tällöin päästään muuttamaan muutamia " -#~ "laiteohjelmisto asetuksia joilla asennin saadaan käynnistettyä. Ensiksi, " -#~ "ladataan oletusasetukset: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Lisäksi on tehtävä verkkoasetukset, joko " -#~ "kiinteällä osoitteella: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " missä 24 on verkon peiton bittien lukumäärä, " -#~ "tai vaihtuvalla osoitteella: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " Mahdollisesti on tehtävä myös " -#~ "route1-asetukset jos TFTP-palvelin ei ole " -#~ "paikallisessa aliverkossa. Katso mallia näistä asetuksista ja anna TFTP-" -#~ "palvelimen osoite ja otoksen sijainti. Asetukset voi sitten tallentaa " -#~ "flash-muistiin. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Nyt on laiteohjelmistolle kerrottava että " -#~ "pitää käynnistää TFTP-otos: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " Jos Netwinderin asennuksessa käytetään " -#~ "sarjapäätettä, on lisättävä seuraava asetus: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Toinen tapa on käyttää näppäimistöä ja " -#~ "näyttöä jolloin käytetään asetuksia: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " Komennolla printenv näkee " -#~ "ympäristömuuttujien arvot. Kun on varmistettu asetusten olevan oikein, " -#~ "voidaan otos ladata: \n" -#~ " NeTTrom command-> boot\n" -#~ " Jos tulee pulmia on ohje detailed HOWTO " -#~ "saatavilla." - -#~ msgid "Booting from TFTP on CATS" -#~ msgstr "Käynnistäminen TFTP:llä CATS:illa" - -#~ msgid "" -#~ "On CATS machines, use boot de0: or similar at the " -#~ "Cyclone prompt." -#~ msgstr "" -#~ "Käytä CATS-koneilla komentoa boot de0: tai vastaavaa " -#~ "Cyclonen kehotteessa." - -#~ msgid "Booting from CD-ROM" -#~ msgstr "Käynnistys rompulta" - -#~ 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 configure your system for booting " -#~ "off a CD as described in , " -#~ "insert your CD, reboot, and proceed to the next chapter." -#~ msgstr "" -#~ "Useimmille käyttäjille on helpointa käyttää Debianin romppusettiä. Jos " -#~ "käsillä on romppusetti, ja jos tietokone tukee käynnistystä suoraan " -#~ "rompulta, hienoa! Riittää kun teet koneen asetukset " -#~ "siten, että se käynnistyy rompulta kuten neuvotaan kohdassa , asetat rompun asemaan, käynnistät ja " -#~ "jatkat seuraavaan lukuun." - -#~ 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 "" -#~ "Huomaa, että jotkin romppuasemat saattavat vaatia erikoisajureita, eikä " -#~ "niitä niin ollen voi käyttää asennuksen alkuvaiheissa. Jos ilmenee, ettei " -#~ "tavallinen rompulta käynnistämistapa toimi tietokoneella, lue tästä " -#~ "luvusta uudestaan kohdat vaihtoehtoisista ytimistä ja asennustavoista " -#~ "jotka saattaisivat tässä tilanteessa toimia." - -#~ 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 "" -#~ "Vaikka käynnistäminen rompulta ei toimisikaan, voitaneen Debianin " -#~ "järjestelmän osat ja tarvittavat paketit asentaa rompulta. Riittää kun " -#~ "käynnistää joltain muulta taltiolta, esimerkiksi levykkeeltä. Kun on aika " -#~ "asentaa käyttöjärjestelmä, peruskokoonpano ja lisäpaketteja, säädetään " -#~ "asennusjärjestelmä asentamaan ne rompulta." - -#~ msgid "" -#~ "If you have problems booting, see ." -#~ msgstr "" -#~ "Jos ilmenee pulmia, katso kohtaa ." - -#~ msgid "" -#~ "To boot a CD-ROM from the Cyclone console prompt, use the command " -#~ "boot cd0:cats.bin" -#~ msgstr "" -#~ "Cyclonen konsolin kehotteesta käynnistetään rompulta komennolla " -#~ "boot cd0:cats.bin" - -#~ msgid "Booting from Firmware" -#~ msgstr "Käynnistäminen laiteohjelmistosta" - -#~ 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 "" -#~ "Kuluttajalaitteet jotka käynnistyvät suoraan laitteen flash-muistilta " -#~ "ovat yleistymässä. Asennin voidaan kirjoittaa flash-muistiin, jolloin se " -#~ "käynnistyy automaattisesti kun laite käynnistetään uudelleen." - -#~ 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 "" -#~ "Useissa tapauksissa ei takuu ole voimassa enää sulautetun laitteen " -#~ "laiteohjelmiston muuttamisen jälkeen. Joskus ei myöskään ole mahdollista " -#~ "palauttaa alkuperäistä laiteohjelmistoa jos flashille kirjoituksessa " -#~ "ilmenee ongelmia. Tästä syystä on oltava huolellinen ja noudatettava " -#~ "ohjeita tarkkaan." - -#~ msgid "Booting the NSLU2" -#~ msgstr "NSLU2:n käynnistäminen" - -#~ msgid "There are three ways how to put the installer firmware into flash:" -#~ msgstr "" -#~ "Asentimen laiteohjelmisto voidaan tallentaa flashiin kolmella tavalla:" - -#~ msgid "Using the NSLU2 web interface" -#~ msgstr "Käytetään NSLU2:n webbikäyttöliittymää" - -#~ msgid "" -#~ "Go to the administration section and choose the menu item " -#~ "Upgrade. You can then browse your disk for the " -#~ "installer image you have previously downloaded. Then press the " -#~ "Start Upgrade button, confirm, wait for a few minutes " -#~ "and confirm again. The system will then boot straight into the installer." -#~ msgstr "" -#~ "Mene \"administration\"-osaan ja valitse valikosta Upgrade. Levyltä voidaan nyt selata aiemmin noudettu asennusotos. Sitten " -#~ "painetaan Start Upgrade-painiketta, vahvistetaan, " -#~ "odotetaan muutama minuutti ja vahvistetaan taas. Laite käynnistyy suoraan " -#~ "asentimeen." - -#~ msgid "Via the network using Linux/Unix" -#~ msgstr "Verkon kautta Linuxista/Unixista" - -#~ msgid "" -#~ "You can use upslug2 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: " -#~ " Disconnect any disks and/or devices from the USB ports. " -#~ " Power off the NSLU2 Press and hold the reset button (accessible " -#~ "through the small hole on the back just above the power input). Press and release the power button to power on " -#~ "the NSLU2. Wait for 10 seconds " -#~ "watching the ready/status LED. After 10 seconds it will change from amber " -#~ "to red. Immediately release the reset button. " -#~ " 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. See the NSLU2-Linux " -#~ "pages if you have problems with this. Once your NSLU2 is in " -#~ "upgrade mode, you can flash the new image: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " 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 "" -#~ "Miltä tahansa Linux- tai Unix-koneelta voidaan komennolla " -#~ "upslug2 päivittää laite verkon kautta. Tämä ohjelmisto " -#~ "on paketoitu Debianiin. Ensiksi on NSLU2 asetettava päivitystilaan:" -#~ " Irrota kaikki levyt ja laitteet USB-" -#~ "porteista. Sammuta NSLU2 Paina ja pidä pohjassa reset-nappula (pieni " -#~ "reikä takana aivan virtaliittimen yläpuolella). " -#~ " Paina ja päästä ylös käynnistysnappula, NSLU2 " -#~ "käynnistyy. Katsele ready/status " -#~ "lediä, 10 sekunnin kuluttua se vaihtuu keltaisesta punaiseksi. Päästä " -#~ "reset-nappula heti ylös. NSLU2:n " -#~ "ready/status-ledi välkyy vuorotellen punaisena ja vihreänä (ennen " -#~ "ensimmäistä vihreää on yhden sekunnin viive). NSLU2 on nyt " -#~ "päivitystilassa. Lue NSLU2-Linux " -#~ "pages -ohje jos tässä on pulmia. Kun NSLU2 on päivitystilassa, " -#~ "uusi otos voidaan kirjoittaa flashiin: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " Huomaa, että työkalu näyttää myös NSLU2:n MAC-" -#~ "osoitteen, josta saattaa olla hyötyä DHCP-palvelimen asetuksia " -#~ "kirjoitettaessa. Kun koko otos on kirjoitettu ja varmennettu, käynnistyy " -#~ "laite automaattisesti uudelleen. Muista kytkeä USB-levy takaisin tässä " -#~ "kohtaa, muuten asennin ei löydä sitä." - -#~ msgid "Via the network using Windows" -#~ msgstr "Verkon kautta Windowsista" - -#~ msgid "" -#~ "There is a tool for Windows to upgrade " -#~ "the firmware via the network." -#~ msgstr "" -#~ "Windowsille on työkalu laiteohjelmiston " -#~ "päivittämiseen verkon kautta." - -#~ msgid "Booting from a CD-ROM" -#~ msgstr "Käynnistäminen rompulta" - -#~ msgid "" -#~ "Booting from Linux Using LILO or GRUB" -#~ msgstr "" -#~ "Käynnistäminen Linuxista LILO:lla tai GRUB:lla" - -#~ msgid "" -#~ "To boot the installer from hard disk, you must first download and place " -#~ "the needed files as described in ." -#~ msgstr "" -#~ "Asentimen käynnistämiseksi kiintolevyltä on tarvittavat tiedostot ensin " -#~ "noudettava ja tallennettava, kuten neuvotaan kohdasssa ." - -#~ msgid "" -#~ "If you intend to use the hard drive only for booting and then download " -#~ "everything over the network, you should download the netboot/" -#~ "debian-installer/i386/initrd.gz file and its corresponding " -#~ "kernel netboot/debian-installer/i386/linux. This " -#~ "will allow you to repartition the hard disk from which you boot the " -#~ "installer, although you should do so with care." -#~ msgstr "" -#~ "Jos tarkoitus on käyttää kiintolevyä vain käynnistämiseen ja noutaa " -#~ "sitten kaikki verkosta, olisi noudettava tiedosto netboot/" -#~ "debian-installer/i386/initrd.gz ja sitä vastaava ydin " -#~ "netboot/debian-installer/i386/linux. Tällöin on " -#~ "mahdollista osioida uudelleen levy josta asennin käynnistetään, vaikkakin " -#~ "tämä olisi tehtävä huolella." - -#~ msgid "" -#~ "Alternatively, if you intend to keep an existing partition on the hard " -#~ "drive unchanged during the install, you can download the hd-" -#~ "media/initrd.gz file and its kernel, as well as copy a CD iso " -#~ "to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from " -#~ "the CD image, without needing the network." -#~ msgstr "" -#~ "Toinen mahdollisuus, mikäli on tarkoitus pitää kiintolevyllä oleva osio " -#~ "ennallaan asennuksen aikana, on noutaa tiedosto hd-media/initrd." -#~ "gz ja sitä vastaava ydin, sekä kopioida rompun ISO-otos " -#~ "levylle (varmista tiedoston nimen lopussa olevan .iso). Asennin voi tällöin käynnistyä levyltä ja asentaa " -#~ "romppuotoksesta, eikä verkkoa tarvita." - -#~ msgid "" -#~ "For LILO, you will need to configure two essential " -#~ "things in /etc/lilo.conf: " -#~ " to load the initrd.gz installer at " -#~ "boot time; have the " -#~ "vmlinuz kernel use a RAM disk as its root partition. " -#~ " Here is a /etc/lilo.conf example:" -#~ msgstr "" -#~ "LILO:a varten on tehtävä kaksi välttämätöntä asetusta " -#~ "tiedostossa /etc/lilo.conf: " -#~ " jotta initrd.gz-asennin ladataan " -#~ "käynnistyksen aikana; jotta " -#~ "vmlinuz-ydin käyttää muistilevyä juuriosionaan. Tässä on esimerkki tiedostosta " -#~ "/etc/lilo.conf:" - -#~ msgid "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" -#~ msgstr "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" - -#~ msgid "" -#~ "For more details, refer to the initrd 4 and " -#~ "lilo.conf 5 man pages. Now run lilo " -#~ "and reboot." -#~ msgstr "" -#~ "Yksityiskohtaisempaa tietoa löytyy man-sivuilta " -#~ "initrd 4 ja lilo.conf 5. Käynnistä nyt " -#~ "lilo ja käynnistä sitten tietokone uudelleen." - -#~ msgid "" -#~ "The procedure for GRUB is quite similar. Locate your " -#~ "menu.lst in the /boot/grub/ " -#~ "directory (sometimes in the /boot/boot/grub/), add " -#~ "the following lines: \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" -#~ " and reboot." -#~ msgstr "" -#~ "GRUB:n käyttö on hyvin samantapaista. Etsi tiedosto " -#~ "menu.lst hakemistosta /boot/grub/ (joskus se on hakemistossa /boot/boot/grub/), lisää seuraavat rivit: \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" -#~ " ja käynnistä uudelleen." - -#~ msgid "" -#~ "Note that the value of the ramdisk_size may need " -#~ "to be adjusted for the size of the initrd image. From here on, there " -#~ "should be no difference between GRUB or LILO." -#~ msgstr "" -#~ "Huomaa, että ramdisk_size-arvoa voidaan joutua " -#~ "muuttamaan vastaamaan initrd-otoksen kokoa. Tästä eteenpäin ei pitäisi " -#~ "olla mitään eroa GRUB:n ja LILO:n " -#~ "välillä." - -#~ msgid "Booting from USB Memory Stick" -#~ msgstr "Käynnistys USB-muistilta" - -#~ msgid "" -#~ "Let's assume you have prepared everything from and . 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 boot: prompt. Here you can enter optional boot arguments, or just hit " -#~ "&enterkey;." -#~ msgstr "" -#~ "Oletetaan että kaikki kohdissa ja " -#~ " mainitut valmistelut on tehty. Nyt " -#~ "vain asetetaan USB-muisti johonkin vapaaseen USB-liittimeen ja " -#~ "käynnistetään tietokone. Järjestelmän pitäisi käynnistyä ja näkyä kehote " -#~ "boot:. Tässä voidaan kirjoittaa käynnistysparametreja, " -#~ "tai painaa vain &enterkey;." - -#~ msgid "Booting from Floppies" -#~ msgstr "Käynnistäminen levykkeiltä" - -#~ msgid "" -#~ "You will have already downloaded the floppy images you needed and created " -#~ "floppies from the images in ." -#~ msgstr "" -#~ "Tarvittavat levykeotokset on jo noudettu ja kirjoitettu levykkeille " -#~ "kohdassa ." - -#~ 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 "" -#~ "Asentimen boot-levykkeeltä käynnistetään asettamalla se ensisijaiseen " -#~ "levykeasemaan, sammuttamalla järjestelmä tavanomaiseen tapaan ja " -#~ "kytkemällä virta takaisin." - -#~ 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 root= 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 linux root=/dev/hdc at the " -#~ "boot prompt." -#~ msgstr "" -#~ "Asennettaessa LS-120-asemalta (ATAPI-versio) levykkeitä käyttäen, on " -#~ "määritettävä levykeaseman virtuaalinen sijainti. Tämä tehdään " -#~ "käynnistysparametrilla root=, johon annetaan laite " -#~ "johon ide-floppy laitteen kuvaa. Jos LS-120 on kytkettynä esimerkiksi " -#~ "ensimmäisenä IDE-laitteena (master) toisessa IDE-liitännässä, " -#~ "kirjoitetaan käynnistyskehotteessa linux root=/dev/hdc." - -#~ msgid "" -#~ "Note that on some machines, Control " -#~ "Alt Delete does not properly " -#~ "reset the machine, so a hard 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 "" -#~ "Huomaa, että joissakin koneissa Control " -#~ "Alt Delete ei palauta " -#~ "konetta kunnolliseen alkutilaan, joten suositellaan virtanappulan käyttöä. Jos asennetaan koneella olevasta käyttöjärjestelmästä " -#~ "(esim. DOS-ikkunasta) ei vaihtoehtoa ole. Muussa tapauksessa, käytä " -#~ "virtanappulaa kun laitetta käynnistetään." - -#~ msgid "" -#~ "The floppy disk will be accessed, and you should then see a screen that " -#~ "introduces the boot floppy and ends with the boot: " -#~ "prompt." -#~ msgstr "" -#~ "Tietoja ladataan levykkeeltä ja näkyviin pitäisi tulla ruutu, jossa " -#~ "levyke esitellään ja jonka alareunassa on kehote boot:." - -#~ msgid "" -#~ "Once you press &enterkey;, you should see the message " -#~ "Loading..., followed by " -#~ "Uncompressing Linux..., 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 ." -#~ msgstr "" -#~ "Kun on painettu &enterkey;, pitäisi näkyä Loading..., jonka jälkeen tulee Uncompressing " -#~ "Linux..., ja sitten suunnilleen ruudullinen tietoja " -#~ "laitteistosta. Lisää tietoa tästä asennusprosessin vaiheesta löytyy " -#~ "kohdasta ." - -#~ 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 debian-installer is " -#~ "automatically launched." -#~ msgstr "" -#~ "Kun on käynnistetty boot-levykkeeltä, pyydetään root-levykettä. Aseta " -#~ "root-levyke asemaan ja paina &enterkey;, jolloin sen sisältö ladataan " -#~ "muistiin. Asennusohjelma debian-installer eli Debianin " -#~ "asennin käynnistyy automaattisesti." - -#~ msgid "There are various ways to do a TFTP boot on i386." -#~ msgstr "i386:lla on erilaisia tapoja käynnistää TFTP:llä" - -#~ msgid "NIC or Motherboard that support PXE" -#~ msgstr "NIC tai emolevy joka tukee PXE:tä" - -#~ msgid "" -#~ "It could be that your Network Interface Card or Motherboard provides PXE " -#~ "boot functionality. This is a Intel re-implementation of TFTP boot. If so you may be able to " -#~ "configure your BIOS to boot from the network." -#~ msgstr "" -#~ "Mahdollisesti verkkokortilla tai emolevyllä on PXE-käynnistys. Se on " -#~ "Intelin muokkaama TFTP-käynnistys. " -#~ "Jos PXE löytyy, voi olla mahdollista asettaa BIOS käynnistymään verkosta." - -#~ msgid "NIC with Network BootROM" -#~ msgstr "NIC jossa on BootROM verkosta käynnistämiseen" - -#~ msgid "" -#~ "It could be that your Network Interface Card provides TFTP boot " -#~ "functionality." -#~ msgstr "Verkkokortti osaa ehkä käynnistyä TFTP:llä." - -#~ msgid "" -#~ "Let us (&email-debian-boot-list;) know how did you manage " -#~ "it. Please refer to this document." -#~ msgstr "" -#~ "Kerro meille (&email-debian-boot-list;) kuinka se " -#~ "onnistui. Viittaa tähän ohjeeseen." - -#~ msgid "Etherboot" -#~ msgstr "Etherboot" - -#~ msgid "" -#~ "The etherboot project " -#~ "provides bootdiskettes and even bootroms that do a TFTPboot." -#~ msgstr "" -#~ "etherboot project tarjoaa " -#~ "käynnistyslevykkeitä, ja jopa bootrommeja, jotka osaavat käynnistyä " -#~ "TFTPbootilla." - -#~ msgid "The Boot Prompt" -#~ msgstr "Käynnistyskehote" - -#~ msgid "" -#~ "When the installer boots, you should be presented with a friendly " -#~ "graphical screen showing the Debian logo and the boot prompt: " -#~ "\n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " 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 "" -#~ "Kun asennin käynnistyy, pitäisi näkyä ystävällinen grafiikkaruutu jossa " -#~ "on Debianin logo ja käynnistyskehote: \n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " Käynnistyskehotteessa voi joko vain painaa " -#~ "&enterkey;, jolloin asennin käynnistyy oletusarvoilla tai kirjoittaa " -#~ "haluttu käynnistystapa ja halutut käynnistysparametrit." - -#~ msgid "" -#~ "Information on available boot methods and on boot parameters which might " -#~ "be useful can be found by pressing F2 through " -#~ "F8. If you add any parameters to the boot command line, " -#~ "be sure to type the boot method (the default is linux) and a space before the first parameter (e.g., " -#~ "linux fb=false)." -#~ msgstr "" -#~ "Tietoa käytettävissä olevista käynnistystavoista ja mahdollisesti " -#~ "hyödyllisistä käynnistysparametreista löytyy painamalla näppäimiä " -#~ "F2:stä F8:aan. Lisättäessä " -#~ "käynnistysriville parametreja, on muistettava kirjoittaa myös " -#~ "käynnistystapa (oletustapa on linux) ja välilyönti " -#~ "ennen ensimmäistä parametria (esim. linux fb=false)." - -#~ 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 integrated Lights Out (iLO) and HP's " -#~ "Integrated Remote Assistant (IRA). You can blindly press " -#~ "F1 In some cases these devices will require special " -#~ "escape sequences to enact this keypress, for example the IRA uses " -#~ " Ctrl F , " -#~ "1. 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 fb=false to the boot " -#~ "prompt, as described in the help text." -#~ msgstr "" -#~ "Asennettaessa konetta tekstiliittymän VGA-konsoliin tarjoavalla " -#~ "etähallintalaitteella, ei ehkä nähdä ensimmäistä graafista ruutua " -#~ "asentimen käynnistyessä; mahdollisesti ei näy käynnistyskehotettakaan. " -#~ "Näitä laitteita ovat esimerkiksi Compaqin integrated Lights Out (iLO) ja HP:n Integrated Remote Assistant (IRA). " -#~ "Voit painaa sokkona F1 Joissakin " -#~ "tapauksissa nämä laitteet vaativat erikoisnäppäilyjä tähän toimintoon, " -#~ "esimerkiksi IRA käyttää Ctrl F , 1. " -#~ "ohittaaksesi tämän ruudun ja nähdäksesi opastustekstin. Kun alkuruutu on " -#~ "ohitettu ja ollaan opastustekstissä, näppäimien painallukset kaiutetaan " -#~ "kehotteessa tavanomaiseen tapaan. Jotta asenninta estettäisiin " -#~ "käyttämästä ruutupuskurointia tästä eteenpäin, on käytettävä " -#~ "käynnistysparametria fb=false kuten ohjeteksti " -#~ "neuvoo." - -#~ msgid "CD Contents" -#~ msgstr "Rompun sisältö" - -#~ msgid "" -#~ "There are three basic variations of Debian Install CDs. The " -#~ "Business Card 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 Network Install 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 "" -#~ "Debianin asennusromppuja on kolmea perusmallia. Business Card -rompulla on mahdollisimman pieni asennus joka mahtuu " -#~ "käyntikortin kokoiselle rompulle. Sitä käytettäessä on oltava " -#~ "verkkoyhteys jonka kautta asennetaan loput peruskokoonpanosta ja saadaan " -#~ "käyttökelpoinen järjestelmä. Network Install -" -#~ "rompulla on kaikki peruskokoonpanoon tarvittavat paketit, mutta " -#~ "verkkoyhteydellä noudetaan Debianin asennuspalvelimesta kokonaiseen " -#~ "järjestelmään haluttavat lisäpaketit. Debianin asennusromppujen " -#~ "setiltä voidaan asentaa kokonainen järjestelmä suuresta " -#~ "valikoimasta paketteja käyttämättä verkkoyhteyttä." - -#~ 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 "" -#~ "IA-64-suoritinperhe käyttää Intelin seuraavan sukupolven Extensible " -#~ "Firmware Interfacea (EFI). Toisin kuin perinteinen x86 BIOS, joka tietää " -#~ "käynnistyslaitteesta vain osiotaulun ja pääkäynnistyslohkon (MBR), EFI " -#~ "pystyy lukemaan ja kirjoittamaan tiedostoja osioista joilla on " -#~ "tiedostojärjestelmänä FAT16 tai FAT32. Tämä yksinkertaistaa usein " -#~ "mystistä järjestelmän käynnistämisprosessia. Järjestelmän " -#~ "käynnistyslataimella ja sitä tukevalla EFI-laiteohjelmistolla on " -#~ "kokonainen tiedostojärjestelmä johon tallentaa koneen käynnistämisessä " -#~ "tarpeelliset tiedostot. Tämä tarkoittaa, että IA-64-järjestelmän " -#~ "järjestelmälevyllä on ylimääräinen levyosio EFI:n käytössä eikä vain " -#~ "yksinkertainen pääkäynnistyslohko kuten tavanomaisemmissa järjestelmissä." - -#~ msgid "" -#~ "The Debian Installer CD contains a small EFI partition where the " -#~ "ELILO 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 "" -#~ "Debianin asennusrompulla on pieni EFI-osio missä ovat käynnistyslatain " -#~ "ELILO, sen asetustiedostot, asentimen ydin ja " -#~ "ensimmäinen muistilevy (initrd). Myös ajossa olevalla järjestelmällä on " -#~ "EFI-osio. Siellä ovat järjestelmän käynnistämiseen tarvittavat tiedostot. " -#~ "Tiedostot ovat luettavissa EFI:n komentotulkista kuten alla selitetään. " - -#~ msgid "" -#~ "Most of the details of how ELILO 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 ELILO 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 "" -#~ "Useimmat ELILO toiminnan yksityiskohdat sen ladatessa " -#~ "ja käynnistäessä järjestelmää ovat läpinäkyviä järjestelmän asentimelle. " -#~ "Asentimen on kuitenkin tehtävä EFI-osio ennen peruskokoonpanon " -#~ "asentamista. Muuten ELILO:n asennus epäonnistuu, " -#~ "jolloin järjestelmää ei voi käynnistää kiintolevyltä. EFI-osiolle " -#~ "varataan tila ja sille tehdään tiedostojärjestelmä asentimen " -#~ "osiointivaiheessa, ennen kuin mitään paketteja ladataan " -#~ "järjestelmälevylle. Osiointivaihe varmistaa myös, että sopiva EFI-osio " -#~ "löytyy ennen kuin se päästää asennuksen jatkumaan." - -#~ 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, Boot " -#~ "Option Maintenance Menu and EFI Shell (Built-in). 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 "" -#~ "EFI-alkulatausohjelma näytetään viimeisena kohtana laiteohjelmiston " -#~ "alkuasetuksissa. Se näyttää valikon, josta käyttäjä voi valita asetuksen. " -#~ "Riippuen mallista ja muista järjestelmään ladatuista ohjelmistoista tämä " -#~ "valikko vaihtelee järjestelmittäin. Valikossa pitäisi näkyä ainakin kaksi " -#~ "kohtaa, Boot Option Maintenance Menu ja EFI " -#~ "Shell (Built-in). Olisi parempi käyttää ensimmäistä kohtaa, " -#~ "mutta jos tuo valinta ei ole käytettävissä tai romppu ei sitä käyttäen " -#~ "syystä tai toisesta käynnisty, käytä toista vaihtoehtoa." - -#~ msgid "IMPORTANT" -#~ msgstr "TÄRKEÄÄ" - -#~ 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 exit at the shell prompt." -#~ msgstr "" -#~ "EFI-alkulatausohjelma valitsee oletustoiminnon käynnistykseen, yleensä se " -#~ "on valikon ensimmäinen kohta, ennalta määritellyn ajan kuluttua " -#~ "(sekunteina). Tämä näkyy ruudun alareunassa lähtölaskentana. Kun aika on " -#~ "kulunut ja järjestelmä käynnistyy oletustoiminnolla, on kone ehkä " -#~ "käynnistettävä uudelleen jotta asennusta voidaan jatkaa. Jos " -#~ "oletustoiminto on EFI Shell, voidaan alkulatausohjelmaan palata " -#~ "komennolla exit EFI Shellin kehotteessa." - -#~ msgid "Option 1: Booting from the Boot Option Maintenance Menu" -#~ msgstr "Valinta 1: Käynnistäminen Boot Option Maintenance -valikosta" - -#~ 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 "" -#~ "Aseta romppu DVD/CD-asemaan ja käynnistä kone. Laiteohjelmisto näyttää " -#~ "EFI Boot Manager -sivun kun järjestelmän alkuasetukset ovat valmiit." - -#~ msgid "" -#~ "Select Boot Maintenance Menu from the menu with the " -#~ "arrow keys and press ENTER. This will display a new " -#~ "menu." -#~ msgstr "" -#~ "Valitse Boot Maintenance Menu nuolinäppäimillä ja " -#~ "paina &enterkey;. Tällöin näytetään uusi valikko." - -#~ msgid "" -#~ "Select Boot From a File from the menu with the arrow " -#~ "keys and press ENTER. This will display a list of " -#~ "devices probed by the firmware. You should see two menu lines containing " -#~ "either the label Debian Inst [Acpi ... or " -#~ "Removable Media Boot. If you examine the rest of the " -#~ "menu line, you will notice that the device and controller information " -#~ "should be the same." -#~ msgstr "" -#~ "Valitse Boot From a File nuolinäppäimillä ja paina " -#~ "&enterkey;. Tällöin näytetään luettelo laiteohjelmiston tunnistamista " -#~ "laitteista. Näkyvissä pitäisi olla kaksi valikon riviä joissa on joko " -#~ "Debian Inst [Acpi ... tai Removable Media " -#~ "Boot. Jos tutkit valikon rivin loppuosan, huomaat että laitteen " -#~ "ja ohjaimen tietojen pitäisi olla samat." - -#~ msgid "" -#~ "You can choose either of the entries that refer to the CD/DVD drive. " -#~ "Select your choice with the arrow keys and press ENTER. If you choose Removable Media Boot the " -#~ "machine will immediately start the boot load sequence. If you choose " -#~ "Debian Inst [Acpi ... instead, it will display a " -#~ "directory listing of the bootable portion of the CD, requiring you to " -#~ "proceed to the next (additional) step." -#~ msgstr "" -#~ "Voidaan valita jompi kumpi CD/DVD-asemaan viittaavista riveistä. Valitse " -#~ "nuolinäppäimillä ja painamalla &enterkey;. Jos valitaan " -#~ "Removable Media Boot kone tekee heti " -#~ "alkukäynnistyksen. Jos sitävastoin valitaan Debian Inst [Acpi ..." -#~ ", se näyttää rompun käynnistysosion hakemistolistauksen, " -#~ "jolloin on edettävä seuraavaan lisäkohtaan." - -#~ msgid "" -#~ "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " -#~ "Removable Media Boot] on the next to the last line. Select this " -#~ "line with the arrow keys and press ENTER. This will " -#~ "start the boot load sequence." -#~ msgstr "" -#~ "Tämä kohta on tehtävä vain jos valittiin Debian Inst [Acpi .... Hakemistolistaus näyttää myös [Treat like Removable " -#~ "Media Boot] toiseksi viimeisellä rivillä. Valitse tämä rivi " -#~ "nuolinäppäimillä ja painamalla &enterkey;. Tämä aloittaa " -#~ "käynnistyslatauksen." - -#~ 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 "" -#~ "Nämä vaiheet käynnistävät Debianin käynnistyslataimen joka näyttää " -#~ "valikon, josta valitaan käynnistysydin ja valitsimia. Jatka valitsemaan " -#~ "käynnistysydin ja valitsimia." - -#~ msgid "Option 2: Booting from the EFI Shell" -#~ msgstr "Valinta 2: Käynnistäminen EFI Shell:stä" - -#~ 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 EFI Shell [Built-in]. Boot the Debian Installer " -#~ "CD with the following steps:" -#~ msgstr "" -#~ "Jos valinta 1 ei jostain syystä toimi, käynnistä kone uudelleen ja kun " -#~ "EFI Boot Manager -ruutu näkyy siinä pitäisi olla valinta EFI " -#~ "Shell [Built-in]. Käynnistä Debianin asennusromppu seuraavasti:" - -#~ 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 "" -#~ "Aseta romppu DVD/CD-asemaan ja käynnistä kone. Laiteohjelmisto näyttää " -#~ "EFI Boot Manager -sivun ja valikon kun järjestelmän alkuasetukset on " -#~ "tehty." - -#~ msgid "" -#~ "Select EFI Shell from the menu with the arrow keys and " -#~ "press ENTER. 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 fsn:. All " -#~ "other recognized partitions will be named blkn:. If you inserted the CD just before entering the " -#~ "shell, this may take a few extra seconds as it initializes the CD drive." -#~ msgstr "" -#~ "Valitse EFI Shell nuolinäppäimillä ja paina " -#~ "&enterkey;. EFI Shell tutkii kaikki käynnistyskelpoiset laitteet ja " -#~ "näyttää ne konsolissa ennen kehotetta. Laitteiden tunnistetuista " -#~ "käynnistyskelpoisista osioista näytetään laitenimi " -#~ "fsn:. Kaikkien muiden " -#~ "tunnistettujen osioiden nimenä on blkn:. Jos romppu asetettiin asemaan juuri ennen " -#~ "komentotulkin käynnistymistä, tämä voi kestää muutaman ylimääräisen " -#~ "sekunnin kun asema käynnistyy." - -#~ msgid "" -#~ "Examine the output from the shell looking for the CDROM drive. It is most " -#~ "likely the fs0: device although other devices with " -#~ "bootable partitions will also show up as fsn." -#~ msgstr "" -#~ "Etsi komentotulkin tulosteesta romppuasemaa. Sen on todennäköisesti laite " -#~ "fs0: vaikkakin mutkin laitteet joissa on " -#~ "käynnystyskelpoisia osioita näkyvät muodossa fsn." - -#~ msgid "" -#~ "Enter fsn: and press " -#~ "ENTER to select that device where n is the partition number for the CDROM. The shell will now " -#~ "display the partition number as its prompt." -#~ msgstr "" -#~ "Komennolla fsn: ja " -#~ "painamalla &enterkey; valitaan laite jossa n " -#~ "on osion numero rompulla. Komentotulkki näyttää nyt osion numeron " -#~ "kehotteena." - -#~ msgid "" -#~ "Enter elilo and press ENTER. This " -#~ "will start the boot load sequence." -#~ msgstr "" -#~ "Kirjoita komento elilo ja paina &enterkey;. Tämä " -#~ "käynnistää käynnistyslatauksen." - -#~ 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot " -#~ "kernel and options." -#~ msgstr "" -#~ "Kuten valinnalla 1, nämä vaiheet käynnistävät Debianin " -#~ "käynnistyslataimen. Se näyttää valikkoruudun josta valitaan " -#~ "käynnistysydin ja asetuksia. Voidaan käyttää myös lyhyemään komentoa " -#~ "fsn:elilo komentotulkin " -#~ "kehotteessa. Jatka valitsemaan käynnistysydin ja asetukset." - -#~ msgid "Installing using a Serial Console" -#~ msgstr "Asentaminen sarjapäätteen avulla" - -#~ 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 [BAUD baud serial console], where BAUD " -#~ "is the speed of your serial console. Menu items for the most typical baud " -#~ "rate settings on the ttyS0 device are preconfigured." -#~ msgstr "" -#~ "Asennus voidaan tehdä näyttöä ja näppäimistöä käyttäen tai " -#~ "sarjapäätteeltä. Näyttö/näppäimistö valitaan kohdasta jossa lukee [VGA " -#~ "console]. Sarjaportin kautta olevalla yhteydellä asennetaan valitsemalla " -#~ "kohta jossa lukee [BAUDIT baud serial " -#~ "console], missä BAUDIT on sarjayhteyden " -#~ "nopeus. Valikossa on valmiiksi yleisimmin käytetyt nopeusasetukset " -#~ "laitteelle ttyS0." - -#~ 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 baud " -#~ "at the EFI shell." -#~ msgstr "" -#~ "Useimmiten halutaan asentimen käyttävän samaan nopeusasetusta kuin on " -#~ "yhteydellä EFI-konsolliin. Jos et ole varma mikä tämä nopeus on, sen voi " -#~ "katsoa komennolla baud EFI:n komentotulkissa." - -#~ 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 console=ttyS1,57600n8 into the Boot: text window." -#~ msgstr "" -#~ "Jos valikossa ei ole valmiina haluttua sarjaporttia tai nopeusasetusta, " -#~ "voidaan jonkin valikon rivin asetukset korvata. Esimerkiksi käytettäessä " -#~ "57600 baudin yhteyttä laitteella ttyS1, kirjoitetaan " -#~ "console=ttyS1,57600n8 teksti-ikkunaan Boot:" -#~ "." - -#~ 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 Params help menu for instructions on starting the installer in Text " -#~ "Mode." -#~ msgstr "" -#~ "Useimmat IA-64-koneet toimitetaan konsolin oletusasetuksella 9600 baudia. " -#~ "Tämä asetus on hitaahko, ja asennusprosessi kirjoittaa jokaista ruutua " -#~ "merkittävän ajan. Kannattaa harkita joko nopeuden nostamista tai " -#~ "asennusta tekstitilassa. Katso ohjevalikosta Params miten asennin käynnistetään tekstitilassa." - -#~ 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 "" -#~ "Jos valitaan väärä konsolityyppi, päästään valitsemaan ydin ja " -#~ "käynnistysparametrit, mutta sekä näyttö että näppäimistö lakkaavat " -#~ "toimimasta heti ytimen käynnistyttyä, jolloin on tehtävä " -#~ "uudelleenkäynnistys ennen kuin asennus voidaan alottaa." - -#~ msgid "Selecting the Boot Kernel and Options" -#~ msgstr "Käynnistysytimen ja parametrien valinta" - -#~ msgid "" -#~ "The boot loader will display a form with a menu list and a text window " -#~ "with a Boot: 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 General help " -#~ "screen explains the menu choices and the Params " -#~ "screen explains the common command line options." -#~ msgstr "" -#~ "Käynnistyslatain näyttää lomakkeen jossa on valikko ja teksti-ikkunan " -#~ "jossa on Boot:-kehote. Nuolinäppäimillä valitaan " -#~ "valikon kohta ja näppäimistöllä kirjoitettu teksti tulee teksti-ikkunaan. " -#~ "Ohjetekstiruudut saa näkyviin painamalla funktionäppäimiä. Ohjeteksti " -#~ "General selittää valikon kohdat ja ohjeteksti " -#~ "Params yleiset komentorivin parametrit." - -#~ msgid "" -#~ "Consult the General help screen for the " -#~ "description of the kernels and install modes most appropriate for your " -#~ "installation. You should also consult " -#~ "below for any additional parameters that you may want to set in the " -#~ "Boot: 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 "" -#~ "Tutustu General-ohjeruudussa ytimien ja " -#~ "asennukseen sopivimpien asennustilojen kuvauksiin. Myöskin olisi luettava " -#~ "kohdasta mitä lisäparametreja haluttaisiin " -#~ "asettaa teksti-ikkunassa Boot:. Valittua ytimen " -#~ "versiota käytetään sekä asennusprosessissa että asennettavassa " -#~ "järjestelmässä. Jos asennuksen aikana ilmenee olgelmia ytimen kanssa, " -#~ "lienevät samat ongelmat edessä myös asennetussa järjestelmässä. " -#~ "Seuraavat vaiheet valitsevat ja käynnistävät asennuksen:" - -#~ msgid "" -#~ "Select the kernel version and installation mode most appropriate to your " -#~ "needs with the arrow keys." -#~ msgstr "" -#~ "Valitse nuolinäppäimillä tarpeisiisi parhaiten sopiva ytimen versio ja " -#~ "asennustapa." - -#~ 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 "" -#~ "Kirjoita asennusparametrit näppäimistöllä. Teksti näytetään heti teksti-" -#~ "ikkunassa. Tämä on se paikka mihin ytimen parametrit (kuten sarjakonsolin " -#~ "asetukset) kirjoitetaan." - -#~ msgid "" -#~ "Press ENTER. 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 "" -#~ "Paina &enterkey;. Tällöin ydin ladataan ja käynnistetään. Ydin näyttää " -#~ "tavanomaiset käynnistysviestinsä ja niiden jälkeen tulee Debian " -#~ "Installerin ensimmäisen ruutu." - -#~ msgid "" -#~ "Proceed to the next chapter to continue the installation where you will " -#~ "set up the language locale, network, and disk partitions." -#~ msgstr "" -#~ "Asennusta jatketaan seuraavassa luvussa missä tehdään kieliasetukset, " -#~ "verkkoasetukset ja levyosiot." - -#~ msgid "" -#~ "Booting an IA-64 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 "" -#~ "IA-64-järjestelmän käynnistäminen verkosta tehdään samaan tapaan kuin " -#~ "käynnistäminen rompulta. Ainoa ero on asennusytimen lataustapa. EFI Boot " -#~ "Manager osaa ladata ja käynnistää ohjelmia verkossa olevalta " -#~ "palvelimelta. Kun asennusydin on ladattu ja käynnistyy, järjestelmän " -#~ "asennus käy läpi samat vaiheet kuin rompulta asennettaessa, paitsi että " -#~ "peruskokoonpanon paketit asennetaan verkosta eikä rompulta." - -#~ msgid "" -#~ "Network booting an IA-64 system requires two architecture-specific " -#~ "actions. On the boot server, DHCP and TFTP must be configured to deliver " -#~ "elilo. On the client a new boot option must be defined " -#~ "in the EFI boot manager to enable loading over a network." -#~ msgstr "" -#~ "IA-64-järjestelmän käynnistäminen verkosta vaatii kaksi " -#~ "suoritinperhekohtaista toimenpidettä. Käynnistyspalvelimella on DHCP:n " -#~ "tai TFTP:n asetuksissa noudettavaksi ohjelmaksi asetettava " -#~ "elilo. Asiakaskoneessa on EFI-alkulatausohjelmassa " -#~ "määritettävä uusi asetus, jotta lataus verkosta on käytössä." - -#~ msgid "Configuring the Server" -#~ msgstr "Palvelimen asetukset" - -#~ msgid "" -#~ "A suitable TFTP entry for network booting an IA-64 system looks something " -#~ "like this: \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" -#~ " Note that the goal is to get elilo." -#~ "efi running on the client." -#~ msgstr "" -#~ "Sopiva asetus TFTP:lle IA-64-järjestelmän käynnistämiseksi verkosta " -#~ "näyttää suunnilleen tältä: \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" -#~ " Huomaa, että tavoitteena on saada ohjelma " -#~ "elilo.efi käynnistettyä asiakaskoneella." - -#~ msgid "" -#~ "Extract the netboot.tar.gz file into the directory " -#~ "used as the root for your tftp server. Typical tftp root directories " -#~ "include /var/lib/tftp and /tftpboot. This will create a debian-installer " -#~ "directory tree containing the boot files for an IA-64 system." -#~ msgstr "" -#~ "Pura tiedosto netboot.tar.gz tftp-palvelimen juurena " -#~ "käytettävään hakemistoon. Tavallisia tftp:n juurihakemistoja ovat " -#~ "/var/lib/tftp ja /tftpboot. " -#~ "Tämä luo hakemistopuun debian-installer jossa on IA-" -#~ "64-järjestelmän käynnistystiedostot." - -#~ msgid "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" -#~ msgstr "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" - -#~ msgid "" -#~ "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should " -#~ "you need to make changes to this file, you can find it in the " -#~ "debian-installer/ia64/ 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 .conf " -#~ "instead of elilo.conf. See documentation provided in " -#~ "the elilo package for details." -#~ msgstr "" -#~ "Tiedostossa netboot.tar.gz on asetustiedosto " -#~ "elilo.conf, jonka pitäisi toimia useimmissa " -#~ "kokoonpanoissa. Jos tähän tiedostoon kuitenkin joudutaan tekemään " -#~ "muutoksia, se löytyy hakemistosta debian-installer/ia64/. On mahdollista käyttää jokaiselle asiakaskoneelle omaa " -#~ "asetustiedostoa nimeämällä ne asiakaskoneen IP-osoitteella " -#~ "heksajärjestelmässä ja lisäämällä sukunimi .conf. " -#~ "Tällöin ei käytetä tiedostoa nimeltä elilo.conf. " -#~ "Katso lisätietoja paketin elilo mukana tulevista " -#~ "ohjeista." - -#~ msgid "Configuring the Client" -#~ msgstr "Asiakaskoneen asetukset" - -#~ msgid "" -#~ "To configure the client to support TFTP booting, start by booting to EFI " -#~ "and entering the Boot Option Maintenance Menu. " -#~ " Add a boot option. " -#~ " You should see one or more lines with the text " -#~ "Load File [Acpi()/.../Mac()]. 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. Name " -#~ "the entry Netboot or something similar, save, and " -#~ "exit back to the boot options menu. " -#~ "You should see the new boot option you just created, and selecting it " -#~ "should initiate a DHCP query, leading to a TFTP load of elilo." -#~ "efi from the server." -#~ msgstr "" -#~ "Asiakaskoneen asetuksien teko tukemaan käynnistystä TFTP:llä aloitetaan " -#~ "käynnistämällä EFI:in ja menemällä valikkoon Boot Option " -#~ "Maintenance Menu. Lisää " -#~ "käynnistykselle valinta. Pitäisi " -#~ "näkyä yksi tai useampia rivejä joissa on teksti Load File " -#~ "[Acpi()/.../Mac()]. Mikäli näitä rivejä on useampi, valitse " -#~ "se jossa on käynnistettäessä käytettävän verkkoliitännän MAC-osoite. " -#~ "Siirrä nuolinäppäimillä korostus valinnnan kohdalle ja paina &enterkey;. " -#~ " Pistä käynnistysvalinnan nimeksi " -#~ "Netboot tai vastaavaa, tallenna ja poistu takaisin " -#~ "käynnistysvalintojen valikkoon. Nyt " -#~ "pitäisi näkyä juuri tehty käynnistysvalinta, ja sen valitsemisen pitäisi " -#~ "käynnistää DHCP-kysely, joka johtaa tiedoston elilo.efi noutamiseen TFTP:Llä palvelimelta." - -#~ 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 "" -#~ "Käynnistyslatain näyttää kehotteensa sen jälkeen kun sen on noutanut ja " -#~ "käsitellyt asetustiedostonsa. Tässä eteenpäin asennuksessa on samat " -#~ "vaiheet kuin asennettaessa rompulta. Valitse käynnistysvalinta kuten yllä " -#~ "ja kun ytimen lataus verkosta on valmis, se käynnistää Debian Installerin." - -#~ msgid "Choosing an Installation Method" -#~ msgstr "Asennustavan valinta" - -#~ 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 "" -#~ "Joissakin suoritinperheen &arch-title; suoritinarkkitehtuureissa on " -#~ "mahdollista käynnistää joko 2.4.x- tai 2.2.x-ydin. Kun valinta on " -#~ "mahdollinen, yritä käyttää 2.4.x-ydintä. Asentimen pitäisi käyttää " -#~ "vähemmän muistia 2.4.x-ytimellä, koska 2.2.x-ytimen tuki vaatii kiintän " -#~ "kokoisen muistilevyn ja 2.4.x käyttää tmpfs:ää." - -#~ msgid "" -#~ "If you are using a 2.2.x linux kernel, then you need to use the " -#~ "&ramdisksize; kernel parameter." -#~ msgstr "" -#~ "Jos käytät linux-ydintä 2.2.x, on annettava ytimen parametri " -#~ "&ramdisksize;." - -#~ msgid "" -#~ "Make sure root=/dev/ram is one of your kernel " -#~ "parameters." -#~ msgstr "" -#~ "Varmista, että yksi ytimen parametreista on root=/dev/ram." - -#~ msgid "" -#~ "If you're having trouble, check cts's " -#~ "&arch-title; debian-installer FAQ." -#~ msgstr "" -#~ "Lue cts's &arch-title; debian-installer " -#~ "FAQ jos on vaikeuksia." - -#~ msgid "Amiga" -#~ msgstr "Amiga" - -#~ msgid "" -#~ "The only method of installation available to amiga is the hard drive (see " -#~ "). In other words the cdrom is " -#~ "not bootable." -#~ msgstr "" -#~ "Amigalla ainoa asennustapa on kiintolevyltä (katso ). Toisin sanoen rompulta ei voi käynnistää." - -#~ msgid "" -#~ "Amiga does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Amigalla ei tällä hetkellä bogl toimi, joten bogl-virheiden ilmetessa on " -#~ "lisättävä käynnistysparametri fb=false." - -#~ msgid "Atari" -#~ msgstr "Atari" - -#~ msgid "" -#~ "The installer for atari may be started from either the hard drive (see " -#~ ") or from floppies (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "Atarin asennin voidaan käynnistää joko kiintolevyltä (katso ) tai levykkeiltä (katso ). Toisin sanoen rompulta ei voi käynnistää." - -#~ msgid "" -#~ "Atari does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Atarilla ei tällä hetkellä bogl toimi, joten bogl-virheiden ilmetessa on " -#~ "lisättävä käynnistysparametri fb=false." - -#~ msgid "BVME6000" -#~ msgstr "BVME6000" - -#~ msgid "" -#~ "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." -#~ msgstr "" -#~ "BVME6000:lla asennin voidaan käynnistää rompulta (katso ), levykkeiltä (see ) tai verkosta (katso )." - -#~ msgid "Macintosh" -#~ msgstr "Macintosh" - -#~ msgid "" -#~ "The only method of installation available to mac is from the hard drive " -#~ "(see ). In other words the " -#~ "cdrom is not bootable. Macs do not have a working 2.4.x kernel." -#~ msgstr "" -#~ "Macilla ainoa asennustapa on kiintolevyltä (katso ). Toisin sanoen rompulta ei voi käynnistää. Maceille ei ole toimivaa 2.4.x-ydintä." - -#~ msgid "" -#~ "If your hardware uses a 53c9x-based scsi bus, then you may need to " -#~ "include the kernel parameter mac53c9x=1,0. " -#~ "Hardware with two such scsi buses, such as the Quadra 950, will need " -#~ "mac53c9x=2,0 instead. Alternatively, the parameter " -#~ "can be specified as mac53c9x=-1,0 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 "" -#~ "Mikäli laitteistossa on 53c9x-piirillä toimiva SCSI-väylä, saatetaan " -#~ "joutua käyttämään ytimen parametria mac53c9x=1,0. " -#~ "Quadra 950 tapaisilla koneilla, joissa on kaksi SCSI-väylää, on " -#~ "sitävastoin käytettävä mac53c9x=2,0. Toinen tapa " -#~ "on antaa parametri muodossa mac53c9x=-1,0 jolloin " -#~ "automaattitunnistus jää päälle, mutta SCSI disconnect otetaan pois " -#~ "päältä. Huomaa, että tämä parametri on tarpeellinen vain jos kiintolevyjä " -#~ "on enemmän kuin yksi; muussa tapauksessa järjestelmä toimii nopeammin jos " -#~ "sitä ei käytetä." - -#~ msgid "MVME147 and MVME16x" -#~ msgstr "MVME147 ja MVME16x" - -#~ msgid "" -#~ "The installer for MVME147 and MVME16x may be started from either floppies " -#~ "(see ) or the net (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "MVME147:lle ja MVME16x:lle asennin voidaan käynnistää joko levykkeiltä " -#~ "(katso ) tai verkosta (katso ). Toisin sanoen rompulta ei voi " -#~ "käynnistää." - -#~ msgid "Q40/Q60" -#~ msgstr "Q40/Q60" - -#~ msgid "" -#~ "The only method of installation available to Q40/Q60 is from the hard " -#~ "drive (see ). In other words " -#~ "the cdrom is not bootable." -#~ msgstr "" -#~ "Q40/Q60:lle ainoa asennustapa on kiintolevyltä (katso ). Toisin sanoen rompulta ei voi käynnistää." - -#~ msgid "Booting from a Hard Disk" -#~ msgstr "Käynnistäminen kiintolevyltä" - -#~ msgid "" -#~ "Booting from an existing operating system is often a convenient option; " -#~ "for some systems it is the only supported method of installation." -#~ msgstr "" -#~ "Käynnistäminen koneessa jo olevasta käyttöjärjestelmäst on usein kätevä " -#~ "tapa; joillekin järjestelmille se on ainoa tuettu asennustapa." - -#~ msgid "" -#~ "To boot the installer from hard disk, you will have already completed " -#~ "downloading and placing the needed files in ." -#~ msgstr "" -#~ "Käynnistettäessä asennin kiintolevyltä on tarvittavat tiedostot pitänyt " -#~ "jo noutaa ja tallentaa kohdassa ." - -#~ 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 MANIFEST for details)." -#~ msgstr "" -#~ "Kiintolevyltä käynnistettäessä voidaan käyttää ainakin kuutta erilaista " -#~ "muistilevyä, kolmea eri tyyppiä ja jokainen joko 2.2.x-linuxytimen tuen " -#~ "kera tai ilman (katso MANIFEST:istä " -#~ "lisätietoja)." - -#~ msgid "" -#~ "The three different types of ramdisks are cdrom, " -#~ "hd-media, and nativehd. These " -#~ "ramdisks differ only in their source for installation packages. The " -#~ "cdrom ramdisk uses a cdrom to get debian-installer " -#~ "packages. The hd-media ramdisk uses an iso image " -#~ "file of a cdrom currently residing on a hard disk. Finally, the " -#~ "nativehd ramdisk uses the net to install packages." -#~ msgstr "" -#~ "Kolme eri muistilevyn tyyppiä ovat cdrom, " -#~ "hd-media, ja nativehd. Näiden " -#~ "muistilevyjen erona on vain se, mistä ne hakevat asennettavat paketit. " -#~ "Muistilevy cdrom noutaa debianin asentimen paketit " -#~ "rompulta. hd-media käyttää kiintolevyllä olevaa " -#~ "tiedostoa, joka on rompun ISO-otos. Lopuksi nativehd " -#~ "noutaa paketit verkosta." - -#~ msgid "Booting from AmigaOS" -#~ msgstr "Käynnistäminen AmigaOS:stä" - -#~ msgid "" -#~ "In the Workbench, start the Linux installation process " -#~ "by double-clicking on the StartInstall icon in the " -#~ "debian directory." -#~ msgstr "" -#~ "Käynnistä Workbench:ssä Linuxin asennusprosessi " -#~ "kaksoisnapsauttamalla kuvaketta StartInstall " -#~ "hakemistossa debian." - -#~ 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 ." -#~ msgstr "" -#~ "Joudut ehkä painamaan &enterkey; kahdesti kun Amigan asennusohjelma on " -#~ "tulostanut joitakin virheenjäljitystietoja ikkunaan. Tämän jälkeen on " -#~ "muutaman sekunnin viive. Seuraavaksi pitäisi näkyä musta ruutu jossa on " -#~ "valkoista tekstiä, siinä näkyy kaikenlaista ytimen virheenjäljitystietoa. " -#~ "Ruudun vieritys saattaa toimia niin nopeasti, ettei viestejä ehdi lukea, " -#~ "mutta sillä ei ole väliä. Muutaman sekunnin kuluttua asennusohjelman " -#~ "pitäisi käynnistyä automaattisesti, joten voidaan jatkaa kohtaan ." - -#~ msgid "Booting from Atari TOS" -#~ msgstr "Käynnistäminen Atari TOS:sta" - -#~ msgid "" -#~ "At the GEM desktop, start the Linux installation process by double-" -#~ "clicking on the bootstra.prg icon in the " -#~ "debian directory and clicking Ok at the program options dialog box." -#~ msgstr "" -#~ "Käynnistä GEM-työpöydällä Linuxin asennusprosessi kaksoisnapsauttamalla " -#~ "kuvaketta bootstra.prg hakemistossa debian ja napsauttamalla painiketta Ok ohjelman " -#~ "asetusten valintaikkunassa." - -#~ 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 ." -#~ msgstr "" -#~ "Joudut ehkä painamaan &enterkey; kahdesti kun Atarin käynnistyslatain on " -#~ "tulostanut joitakin virheenjäljitystietoja ikkunaan. Tämän jälkeen ruutu " -#~ "muuttuu harmaaksi, ja tulee muutaman sekunnin viive. Seuraavaksi pitäisi " -#~ "näkyä musta ruutu jossa on valkoista tekstiä, siinä näkyy kaikenlaista " -#~ "ytimen virheenjäljitystietoa. Ruudun vieritys saattaa toimia niin " -#~ "nopeasti, ettei viestejä ehdi lukea, mutta sillä ei ole väliä. Muutaman " -#~ "sekunnin kuluttua asennusohjelman pitäisi käynnistyä automaattisesti, " -#~ "joten voidaan jatkaa kohtaan ." - -#~ msgid "Booting from MacOS" -#~ msgstr "Käynnistäminen MacOS:stä" - -#~ msgid "" -#~ "You must retain the original Mac system and boot from it. It is " -#~ "essential that, when booting MacOS in preparation " -#~ "for booting the Penguin linux loader, you hold the shift " -#~ "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 "" -#~ "Alkuperäinen Mac-järjestelmä on säilytettävä ja käynnistettävä siitä. " -#~ "Olennaista on, että käynnistettäessä MacOS:ää " -#~ "valmisteltaessa Penguin-linuxlataimen käynnistämistä, pidetään " -#~ "Vaihto-näppäintä pohjassa jotta estetään laajennosten " -#~ "lataaminen. Jos MacOS:ää käytetään vain linuxin lataamiseen, voidaan " -#~ "poistaa kaikki laajennokset ja järjestelmäikkunat Macin " -#~ "Järjestelmäkansiosta, tällöin ei tarvitse pitää Vaihto-" -#~ "näppäintä pohjassa. Muutoin laajennokset saattavat jäädä käyntiin ja " -#~ "aiheuttavat satunnaisia ongelmia ajossa olevalle linux-ytimelle." - -#~ msgid "" -#~ "Macs require the Penguin bootloader. If you do not " -#~ "have the tools to handle a Stuffit archive, &penguin19." -#~ "hfs; is an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." -#~ msgstr "" -#~ "Maceissä on käytettävä Penguin-käynnistyslatainta. " -#~ "Mikäli käytettävissä ei ole työkaluja Stuffit-arkiston " -#~ "käsittelyyn, on Penguin purettuna &penguin19.hfs; hfs-" -#~ "levyotoksessa. Kohdassa kerrotaan miten " -#~ "tämä otos kopiodaan levykkeelle." - -#~ msgid "" -#~ "At the MacOS desktop, start the Linux installation process by double-" -#~ "clicking on the Penguin Prefs icon in the " -#~ "Penguin directory. The Penguin " -#~ "booter will start up. Go to the Settings item " -#~ "in the File menu, click the Kernel tab. Select the kernel (vmlinuz) and " -#~ "ramdisk (initrd.gz) images in the install directory by clicking on the corresponding buttons in the upper " -#~ "right corner, and navigating the file select dialogs to locate the files." -#~ msgstr "" -#~ "Käynnistä MacOS:n työpöydällä Linuxin asennusprosessi " -#~ "kaksoisnapsauttamalla kuvaketta Penguin Prefs " -#~ "hakemistossa Penguin. Penguin-" -#~ "käynnistin käynnistyy. Valitse File-valikossa kohta " -#~ "Settings, napsauta välilehteä " -#~ "Kernel. Valitse ytimen (vmlinuz) ja muistilevyn (initrd.gz) otokset " -#~ "hakemistossa install painamalla niitä vastaavia " -#~ "painikkeita oikeassa yläkulmassa, ja etenemällä " -#~ "tiedostonvalintaikkunoissa niiden kohdalle." - -#~ msgid "" -#~ "To set the boot parameters in Penguin, choose File -" -#~ "> Settings..., then switch to the " -#~ "Options tab. Boot parameters may be typed in to the " -#~ "text entry area. If you will always want to use these settings, select " -#~ "File -> Save Settings as Default." -#~ msgstr "" -#~ "Käynnistysparametrit asetetaan Penguinissa valitsemalla File -> Settings..., sitten vaihdetaan " -#~ "välilehteen Options. Käynnistysparametrit voidaan " -#~ "kirjoittaa tekstinsyöttöalueeseen. Mikäli näitä asetuksia halutaan " -#~ "käyttää aina, valitaan File -> Save " -#~ "Settings as Default." - -#~ msgid "" -#~ "Close the Settings dialog, save the settings and " -#~ "start the bootstrap using the Boot Now item in " -#~ "the File menu." -#~ msgstr "" -#~ "Sulje Settings-valintaikkuna, tallenna asetukset ja " -#~ "käynnistä alkulataus valikon File kohdasta " -#~ "Boot Now." - -#~ msgid "" -#~ "The Penguin 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 ." -#~ msgstr "" -#~ "Penguin-käynnistin tulostaa joitakin " -#~ "virheenjäljitystietoja ikkunaan. Tämän jälkeen ruutu muuttuu harmaaksi, " -#~ "ja tulee muutaman sekunnin viive. Seuraavaksi näkyy musta ruutu jossa on " -#~ "valkoista tekstiä, siinä näkyy kaikenlaista ytimen " -#~ "virheenjäljitystietoa. Ruudun vieritys saattaa toimia niin nopeasti, " -#~ "ettei viestejä ehdi lukea, mutta sillä ei ole väliä. Muutaman sekunnin " -#~ "kuluttua asennusohjelman pitäisi käynnistyä automaattisesti, joten " -#~ "voidaan jatkaa kohtaan ." - -#~ msgid "Booting from Q40/Q60" -#~ msgstr "Käynnistäminen Q40/Q60:stä" - -#~ msgid "FIXME" -#~ msgstr "FIXME" - -#~ msgid "" -#~ "The installation program should start automatically, so you can continue " -#~ "below at ." -#~ msgstr "" -#~ "Asennusohjelman pitäisi käynnistyä automaattisesti, joten voidaan jatkaa " -#~ "kohtaan " - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitecture that supports CD-ROM " -#~ "booting is the BVME6000." -#~ msgstr "" -#~ "Tällä hetkellä suoritinperheen &arch-title; ainoa rompulta käynnistystä " -#~ "tukeva suoritinarkkitehtuuri on BVME6000." - -#~ msgid "" -#~ "After booting the VMEbus systems you will be presented with the LILO " -#~ "Boot: 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 "" -#~ "VMEbus-järjestelmien käynnistyttyä näkyy LILO:n kehote Boot:. Käynnistä Linux ja varsinainen Debianin asennus vt102-pääte-" -#~ "emulaatiota käyttäen kirjoittamalla kehotteeseen joku seuraavista:" - -#~ msgid "type i6000 &enterkey; to install a BVME4000/6000" -#~ msgstr "" -#~ "Kirjoittamalla i6000 &enterkey; asennetaan BVME4000/6000" - -#~ msgid "type i162 &enterkey; to install an MVME162" -#~ msgstr "kirjoittamalla i162 &enterkey; asennetaan MVME162" - -#~ msgid "type i167 &enterkey; to install an MVME166/167" -#~ msgstr "" -#~ "kirjoittamalla i167 &enterkey; asennetaan MVME166/167" - -#~ msgid "" -#~ "You may additionally append the string TERM=vt100 to use " -#~ "vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." -#~ msgstr "" -#~ "Loppuun voidaan lisätä merkkijono TERM=vt100 jolloin " -#~ "käytetään vt100-pääte-emulointia, esim. i6000 TERM=vt100 " -#~ "&enterkey;." - -#~ msgid "" -#~ "For most &arch-title; architectures, booting from a local filesystem is " -#~ "the recommended method." -#~ msgstr "" -#~ "Useimmille suoritinperheen &arch-title; laitteille suositellaan " -#~ "käynnistämistä koneen omasta tiedostojärjestelmästä." - -#~ msgid "" -#~ "Booting from the boot floppy is supported only for Atari and VME (with a " -#~ "SCSI floppy drive on VME) at this time." -#~ msgstr "" -#~ "Tällä hetkellä tuetaan levykkeeltä käynnistämistä vain Atarilla ja VME:" -#~ "llä (VME:llä on oltava SCSI-levykeasema)." - -#~ msgid "SGI TFTP Booting" -#~ msgstr "SGI:n käynnistäminen TFTP:llä" - -#~ msgid "" -#~ "After entering the command monitor use \n" -#~ "bootp():\n" -#~ " 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 netaddr environment variable. Type " -#~ "\n" -#~ "unsetenv netaddr\n" -#~ " in the command monitor to do this." -#~ msgstr "" -#~ "SGI:n koneilla käynnistetään linux ja aloitetaan Debianin asennus " -#~ "kirjoittamalla komentotulkkiin \n" -#~ "bootp():\n" -#~ ". Jotta tämä toimisi, voidaan joutua ensin " -#~ "poistamaan ympäristömuuttuja netaddr. Kirjoita " -#~ "komentotulkissa \n" -#~ "unsetenv netaddr\n" -#~ "." - -#~ msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" -#~ msgstr "Broadcom BCM91250A: ja BCM91480B:n käynnistäminen TFTP:llä" - -#~ 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: " -#~ "\n" -#~ "ifconfig eth0 -auto\n" -#~ " Once you have obtained an IP address, you can " -#~ "load SiByl with the following command: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " 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 "" -#~ "Broadcomin testiemolevyillä BCM91250A ja BCM91480B on ladattava SiByl-" -#~ "käynnistyslatain TFTP:llä, se sitten lataa ja käynnistää Debianin " -#~ "asentimen. Useimmissa tapauksissa noudetaan ensin IP-osoite DHCP:llä " -#~ "mutta on mahdollista asettaa kiinteä osoite. DHCP otetaan käyttöön " -#~ "seuraavalla CFE-kehotteeseen kirjoitettavalla komennolla:" -#~ "\n" -#~ "ifconfig eth0 -auto\n" -#~ " Kun IP-osoite on saatu, ladataan SiByl tällä " -#~ "komennolla: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " Komennossa oleva IP-osoite on korvattava TFTP-" -#~ "palvelimen nimellä tai IP-osoitteella. Tämän komennon jälkeen asennin " -#~ "ladataan automaattisesti." - -#~ msgid "Boot Parameters" -#~ msgstr "Käynnistysparametrit" - -#~ msgid "" -#~ "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." -#~ msgstr "" -#~ "SGI:n koneilla voidaan käynnistysparametreja lisätä komentotulkissa " -#~ "bootp():-komennon loppuun." - -#~ msgid "" -#~ "Following the bootp(): 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: \n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Further kernel parameters can be passed via " -#~ "append:" -#~ msgstr "" -#~ "bootp():-komennon jälkeen voidaan kirjoittaa " -#~ "käynnistettävän tiedoston polkunimi, jos bootp/dhcp-palvelin ei nimeä " -#~ "antanut. Esimerkki:\n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Ytimelle voi antaa lisää parametreja " -#~ "append:n avulla:" - -#~ msgid "bootp(): append=\"root=/dev/sda1\"" -#~ msgstr "bootp(): append=\"root=/dev/sda1\"" - -#~ msgid "" -#~ "You cannot pass any boot parameters directly from the CFE prompt. " -#~ "Instead, you have to edit the /boot/sibyl.conf file " -#~ "on the TFTP server and add your parameters to the " -#~ "extra_args variable." -#~ msgstr "" -#~ "CFE-kehotteessa ei voi suoraan antaa käynnistysparametreja. On muokattava " -#~ "tiedostoa /boot/sibyl.conf TFTP-palvelimella ja " -#~ "lisättävä parametrit muuttujaan extra_args." - -#~ msgid "Cobalt TFTP Booting" -#~ msgstr "Cobaltin käynnistys TFTP:llä" - -#~ 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 /nfsroot. 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 "" -#~ "Tarkkaan ottaen Cobalt ei käytä TFTP:tä vaan NFS:ää. On asennettava NFS-" -#~ "palvelin ja tallennettava asentimen tiedostot hakemistoon /" -#~ "nfsroot. Cobaltia käynnistettäessä on painettava oikeaa ja " -#~ "vasenta kohdistinnäppäintä samaan ajkaa jolloin laite käynnistyy verkosta " -#~ "NFS:llä. Sitten ruudulla näkyy useita valintoja. Asennustapoja on " -#~ "seuraavat kaksi:" - -#~ 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 "" -#~ "SSH:lla (oletus): tässä tapauksessa asennin tekee verkkoasetukset DHCP:" -#~ "llä ja käynnistää SSH-palvelimen. Se näyttää sitten satunnaisen salasanan " -#~ "ja muuta kirjautumistietoa (kuten IP-osoitteen) Cobaltin LCD-näytöllä. " -#~ "Kun laitteeseen kirjaudutaan SSH:lla voidaan asennus aloittaa." - -#~ 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 "" -#~ "Sarjapäätteellä: Käytä nollamodeemikaapelia Cobaltin sarjaportissa (käytä " -#~ "115200 bittiä sekunnissa) ja tee asennus tällä tavoin. Tämä ei ole " -#~ "mahdollista Qube 2700 (Qube1) -koneilla, koska niissä ei ole sarjaporttia." - -#~ msgid "" -#~ "You cannot pass any boot parameters directly. Instead, you have to edit " -#~ "the /nfsroot/default.colo file on the NFS server and " -#~ "add your parameters to the args variable." -#~ msgstr "" -#~ "Käynnistysparametreja ei voi antaa suoraan. On muokattava tiedostoa " -#~ "/nfsroot/default.colo NFS-palvelimella ja lisättävä " -#~ "parametrit muuttujaan args." - -#~ msgid "s390 Limitations" -#~ msgstr "s390:n rajoitukset" - -#~ msgid "" -#~ "In order to run the installation system a working network setup and ssh " -#~ "session is needed on S/390." -#~ msgstr "" -#~ "Jotta asennusjärjestelmää voitaisiin käyttää S/390:lla, on oltava " -#~ "toimivat verkkoasetukset ja ssh-istunto." - -#~ 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 an ssh session which will launch the standard " -#~ "installation system." -#~ msgstr "" -#~ "Käynnistysprosessi alkaa verkkoasetuksilla, tulee kehote useista verkon " -#~ "asetuksista. Jos asetukset onnistuvat, kirjaudutaan järjestelmään " -#~ "käynnistämällä ssh-istunto, joka käynnistää tavanomaisen " -#~ "asennusjärjestelmän." - -#~ msgid "s390 Boot Parameters" -#~ msgstr "s390:n käynnistysparametrit" - -#~ 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 Device Drivers and Installation Commands for more " -#~ "information about S/390-specific boot parameters." -#~ msgstr "" -#~ "S/390:lla käynnistysparametrit voidaan lisätä parm-tiedostoon. " -#~ "Tiedostossa voi käyttää joko ACSII- tai EBCDIC-merkkejä. Lue Device Drivers and Installation Commands-" -#~ "ohjeesta lisätietoja S/390:n käynnistysparametreista." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitectures that support CD-ROM " -#~ "booting are PReP and New World PowerMacs. On PowerMacs, hold the " -#~ "c key, or else the combination of Command, Option, Shift, and " -#~ "Delete keys together while booting to boot from the CD-" -#~ "ROM." -#~ msgstr "" -#~ "Tällä hetkellä ainoat suoritinperheen &arch-title; suoritinarkkitehturit " -#~ "jotka tukevat rompulta käynnistämistä ovat PReP ja New World PowerMacit. " -#~ "PowerMaceilla pidä pohjassa näppäintä c, tai näppäimiä " -#~ "Command, Option, Shift, ja Delete käynnistyksen aikana jotta käynnistys " -#~ "tapahtuu rompulta." - -#~ 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 "" -#~ "OldWorld PowerMacit eivät käynnisty Debian-rompulta, koska OldWorld-" -#~ "tietokoneissa on Mac OS ROM CD -latausajurin oltava rompulla, eikä tästä " -#~ "ajurista ole saatavilla vapaata versiota. Kaikissa OldWorld-koneissa on " -#~ "levykeasema, joten käynnistä asennin levykkeeltä ja pistä sitten asennin " -#~ "noutamaan tarvittavat tiedostot rompulta." - -#~ 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 for booting from the " -#~ "hard disk, except use the path to yaboot on the CD at " -#~ "the OF prompt, such as" -#~ msgstr "" -#~ "Jos tietokone ei käynnisty suoraan rompulta, on silti mahdollista käyttää " -#~ "romppua asennuksessa. NewWorld-koneilla voidaan myös OpenFirmwaren " -#~ "komennolla tehdä käynnistys rompulta. Seuraa kohdan ohjeita kiintolevyltä käynnistämiseen, paitsi että OF:n " -#~ "kehotteessa käytetään polkua komentoon yaboot " -#~ "rompulla, kuten tässä" - -#~ msgid "0 > boot cd:,\\install\\yaboot" -#~ msgstr "0 > boot cd:,\\install\\yaboot" - -#~ msgid "Booting from Hard Disk" -#~ msgstr "Käynnistys kiintolevyltä" - -#~ msgid "Booting CHRP from OpenFirmware" -#~ msgstr "CHRP:n käynnistys OpenFirmwaresta" - -#~ msgid "Not yet written." -#~ msgstr "Tätä ei ole vielä kirjoitettu." - -#~ msgid "Booting OldWorld PowerMacs from MacOS" -#~ msgstr "OldWorld PowerMacien käynnistäminen MacOS:stä" - -#~ msgid "" -#~ "If you set up BootX in , you can use it " -#~ "to boot into the installation system. Double click the BootX application icon. Click on the Options " -#~ "button and select Use Specified RAM Disk. This will " -#~ "give you the chance to select the ramdisk.image.gz " -#~ "file. You may need to select the No Video Driver " -#~ "checkbox, depending on your hardware. Then click the Linux button to shut down MacOS and launch the installer." -#~ msgstr "" -#~ "Jos BootX otettiin käyttöön kohdassa , " -#~ "voidaan sitä käyttää asennusjärjestelmän käynnistämiseen. Kaksoisnapsauta " -#~ "sovelluksen BootX kuvaketta. Napsauta painiketta " -#~ "Options ja valitse Use Specified RAM " -#~ "Disk. Tällöin pääsee valitsemaan tiedoston ramdisk." -#~ "image.gz. Tietokoneen ominaisuudet saattavat vaatia " -#~ "valintaruudun No Video Driver merkitsemistä. Sammuta " -#~ "sitten MacOS painikkeella Linux, se käynnistää " -#~ "asentimen." - -#~ msgid "Booting NewWorld Macs from OpenFirmware" -#~ msgstr "NewWorld Macien käynnistäminen OpenFirmwaresta" - -#~ msgid "" -#~ "You will have already placed the vmlinux, " -#~ "initrd.gz, yaboot, and " -#~ "yaboot.conf files at the root level of your HFS " -#~ "partition in . Restart the computer, " -#~ "and immediately (during the chime) hold down the Option, " -#~ "Command (cloverleaf/Apple), o, and " -#~ "f keys all together. After a few seconds you will be " -#~ "presented with the Open Firmware prompt. At the prompt, type " -#~ "\n" -#~ "0 > boot hd:x,yaboot\n" -#~ " replacing x 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 ide0: instead of hd:. In a few more seconds you will see a yaboot prompt " -#~ "\n" -#~ "boot:\n" -#~ " At yaboot's boot: prompt, " -#~ "type either install or install " -#~ "video=ofonly followed by a &enterkey;. The " -#~ "video=ofonly argument is for maximum " -#~ "compatibility; you can try it if install doesn't " -#~ "work. The Debian installation program should start." -#~ msgstr "" -#~ "Tiedostot vmlinux, initrd.gz, " -#~ "yaboot, ja yaboot.conf on " -#~ "tallennettu paikoilleen HFS-osion juureen jo kohdassa . Käynnistä tietokone uudelleen, ja pidä heti " -#~ "(heläyksen aikana) pohjassa näppäimiä Option, " -#~ "Command (neliapila/Apple), o, ja " -#~ "f samaan aikaan. Muutaman sekunnin päästä näkyy Open " -#~ "Firmwaren kehote. Kirjoita kehotteeseen \n" -#~ "0 > boot hd:x,yaboot\n" -#~ " korvaten x sen HFS-" -#~ "osion numerolla, johon ydin ja yabootin tiedoston tallennettiin. Paina " -#~ "rivin lopuksi &enterkey;. Joillakin koneilla on kirjoitettava " -#~ "ide0: eikä hd:. Kuluu " -#~ "muutama sekunti lisää, ja näkyy yabootin kehote:" -#~ "\n" -#~ "boot:\n" -#~ " Yabootin boot:-kehotteessa " -#~ "kirjoitetaan joko install tai install " -#~ "video=ofonly, ja painetaan &enterkey;. Parametrilla " -#~ "video=ofonly saadaan suurin mahdollinen " -#~ "yhteensopivuus; käytä sitä jos install ei toimi. " -#~ "Seuraavaksi pitäisi Debianin asentimen käynnistyä." - -#~ msgid "Booting from USB memory stick" -#~ msgstr "Käynnistys USB-muistilta" - -#~ msgid "" -#~ "Currently, NewWorld PowerMac systems are known to support USB booting." -#~ msgstr "" -#~ "Tämänhetkisen tiedon mukaan NewWorld PowerMacit tukevat käynnistystä USB-" -#~ "muistilta." - -#~ msgid "" -#~ "Make sure you have prepared everything from . 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 " -#~ "Command Option o f all together while booting (see " -#~ ")." -#~ msgstr "" -#~ "Varmistu, että kaikki kohdan " -#~ "valmistelut on tehty. Macintoshin käynnistämiseksi USB-muistilta on " -#~ "käytettävä Open Firmwaren kehotetta, koska Open Firmwaren oletusarvo on, " -#~ "ettei USB-muistilaitteita etsitä. Kehotteen saa näkyviin pitämällä " -#~ "pohjassa näppäimiä Command Option o f samaan aikaan " -#~ "kun kone käynnistyy (katso )." - -#~ msgid "" -#~ "You will need to work out where the USB storage device appears in the " -#~ "device tree, since at the moment ofpath cannot work " -#~ "that out automatically. Type dev / ls and " -#~ "devalias 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 usb0/disk, " -#~ "usb0/hub/disk, /pci@f2000000/usb@1b,1/" -#~ "disk@1, and /pci@f2000000/usb@1b,1/hub@1/disk@1 work." -#~ msgstr "" -#~ "On selvitettävä mihin kohtaan laitepuuta USB-muistilaitteet ilmaantuvat, " -#~ "koska tällä hetkellä ofpath ei osaa löytää niitä " -#~ "automaattisesti. Open Firmwaren kehotteessa saa komennoilla " -#~ "dev / ls ja devalias " -#~ "luettelon kaikista tunnetuista laitteista ja laitteiden toisista nimistä. " -#~ "Tekijän laitteistossa, jossa on erilaisia USB-muisteja, toimivat " -#~ "seuraavan kaltaiset polkunimet: usb0/disk, " -#~ "usb0/hub/disk, /pci@f2000000/usb@1b,1/" -#~ "disk@1, ja /pci@f2000000/usb@1b,1/hub@1/disk@1" - -#~ msgid "" -#~ "Having worked out the device path, use a command like this to boot the " -#~ "installer: \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " The 2 matches the " -#~ "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot " -#~ "image earlier, and the ,\\\\:tbxi part instructs " -#~ "Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i." -#~ "e. yaboot) in the directory previously blessed with " -#~ "hattrib -b." -#~ msgstr "" -#~ "Kun USB-muistin kohta laitepuussa on selvinnyt, käynnistä asennin " -#~ "tämäntapaisella komennolla: \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " 2 tarkoittaa " -#~ "Apple_HFS- tai Apple_Bootstrap-osiota johon käynnistys otos aiemmin " -#~ "kopioitiin, ja ,\\\\:tbxi saa Open Firmwaren " -#~ "käynnistämään tiedoston jonka HFS-tiedostotyyppi on \"tbxi\" (ts. " -#~ "yaboot) hakemistossa johon aiemmin kohdistettiin " -#~ "komento hattrib -b." - -#~ msgid "" -#~ "The system should now boot up, and you should be presented with the " -#~ "boot: prompt. Here you can enter optional boot " -#~ "arguments, or just hit &enterkey;." -#~ msgstr "" -#~ "Järjestelmän pitäisi nyt käynnistyä, ja näkyviin tulla kehote " -#~ "boot:. Tässä voidaan kirjoittaa valinnaisia " -#~ "käynnistysparametreja tai painaa vaan &enterkey;." - -#~ 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 ." -#~ msgstr "" -#~ "Tämä käynnistystapa on uutuus, ja voi olla vaikea saada toimimaan " -#~ "joissakin NewWorld-koneissa. Jos pulmia ilmenee, ole hyvä ja tee " -#~ "asennusraportti. Asennusraportin teko selitetään kohdassa ." - -#~ msgid "Currently, PReP and New World PowerMac systems support netbooting." -#~ msgstr "" -#~ "Tällä hetkellä PReP ja New World PowerMacit tukevat käynnistystä verkosta." - -#~ msgid "" -#~ "On machines with Open Firmware, such as NewWorld Power Macs, enter the " -#~ "boot monitor (see ) and use the " -#~ "command boot enet:0. PReP and CHRP boxes may have " -#~ "different ways of addressing the network. On a PReP machine, you should " -#~ "try boot server_ipaddr," -#~ "file,client_ipaddr." -#~ msgstr "" -#~ "Koneilla joissa on Open Firmware, kuten NewWorld Power Macit, mene boot " -#~ "monitoriin (katso ) ja kirjoita " -#~ "komento boot enet:0. PReP- ja CHRP-koneissa voi olla " -#~ "erilaisia tapoja verkon nimeämiseen. PReP-koneella olisi kokeiltava " -#~ "boot palvelimen_ip-osoite," -#~ "tiedosto,asiakaskoneen_ip-osoite." - -#~ 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 "" -#~ "Käynnistäminen levykkeiltä on tuettu suoritinperheellä &arch-title;, " -#~ "vaikkakin se yleensä soveltuu vain OldWorld-koneille. NewWorld-koneissa " -#~ "ei ole levykeasemaa, ja koneeseen liitetyltä USB-levykeasemalta " -#~ "käynnistystä ei ole tuettu." - -#~ msgid "" -#~ "To boot from the boot-floppy-hfs.img floppy, place " -#~ "it in floppy drive after shutting the system down, and before pressing " -#~ "the power-on button." -#~ msgstr "" -#~ "Levykkeeltä boot-floppy-hfs.img käynnistetään " -#~ "asettamalla se levykeasemaan kun laite on sammutettu, ja painamalla " -#~ "sitten virtanappulaa." - -#~ 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 "" -#~ "Niille joille Macintoshin levyketoiminnot eivät ole tuttuja: ennen " -#~ "käynnistystä koneeseen asetettu levyke on se josta laitteisto " -#~ "ensimmäiseksi käynnistyy. Jos levykkeellä ei ole kunnollista " -#~ "käynnistystiedostoa, se poistetaan asemasta ja laite etsii " -#~ "käynnistyskelpoisia osioita kiintolevyltä." - -#~ msgid "" -#~ "After booting, the root.bin 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 "" -#~ "Käynnistyksen jälkeen pyydetään levykettä root.bin. " -#~ "Aseta levyke asemaan ja paina &enterkey;. Asennusohjelma käynnistyy " -#~ "automaattisesti kun juuritiedostojärjestelmä on ladattu muistiin." - -#~ msgid "PowerPC Boot Parameters" -#~ msgstr "PowerPC:n käynnistysparametrit" - -#~ 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 " -#~ "video=atyfb:vmode:6 , which will select that mode " -#~ "for most Mach64 and Rage video hardware. For Rage 128 hardware, this " -#~ "changes to video=aty128fb:vmode:6 ." -#~ msgstr "" -#~ "Useat vanhat Applen näytöt käyttivät 640x480 67Hz -toimintatilaa. Jos " -#~ "kuva on vinksallaan vanhassa Applen näytössä, kokeile lisätä " -#~ "käynnistysparametri video=atyfb:vmode:6, joka " -#~ "valitsee tuon toimintatilan useimmissa Mach64- ja Rage-näytönohjaimissa. " -#~ "Jos näytönohjain on Rage 128, käytä video=aty128fb:vmode:6." - -#~ msgid "" -#~ "On machines with OpenBoot, simply enter the boot monitor on the machine " -#~ "which is being installed (see ). Use " -#~ "the command boot net to boot from a TFTP and RARP " -#~ "server, or try boot net:bootp or boot " -#~ "net:dhcp to boot from a TFTP and BOOTP or DHCP server. Some " -#~ "older OpenBoot revisions require using the device name, such as " -#~ "boot le(); these probably don't support BOOTP nor " -#~ "DHCP." -#~ msgstr "" -#~ "Koneissa joissa on OpenBoot, riittää käynnistää asennettavan koneen boot " -#~ "monitor (katso ). Komennolla " -#~ "boot net käynnistetään TFTP- tai RARP-" -#~ "palvelimelta. Komennolla boot net:bootp tai " -#~ "boot net:dhcp käynnistetään TFTP- ja BOOTP- tai " -#~ "DHCP-palvelimelta. Joissakin vanhoissa OpenBootin versioissa on " -#~ "käytettävä laitenimeä, kuten boot le(); nämä eivät " -#~ "luultavasti tue BOOTP:tä eikä DHCP:tä." - -#~ msgid "" -#~ "Most OpenBoot versions support the boot cdrom " -#~ "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 "" -#~ "Useimmat OpenBootin versiot tukevat komentoa boot cdrom, joka on vain toinen nimi käynnistykselle SCSI-laitteelta " -#~ "jonka ID on 6 (tai toissijaisen IDE-liitännän isäntälevyltä IDE-levyjä " -#~ "käyttävässä koneessa). Vanhoissa OpenBootin versiossa voi joutua " -#~ "käyttämään varsinaista laitenimeä, koska ne eivät tue tätä " -#~ "erikoiskomentoa. Huomaa, että on ilmoitettu ongelmista sun4m-koneilla " -#~ "(esim. Sparc 10 ja Sparc 20) rompulta käynnistettäessä." - -#~ msgid "" -#~ "To boot from floppy on a Sparc, use \n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Be warned that the newer Sun4u (ultra) " -#~ "architecture does not support floppy booting. A typical error message is " -#~ "Bad magic number in disk label - Can't open disk label " -#~ "package. 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 "" -#~ "Sparc käynnistetään levykkeeltä komentamalla\n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Varoitamme, että uusi sun4u-suoritinperhe " -#~ "(ultra) ei tue levykkeeltä käynnistämistä. Tavallinen virheilmoitus on " -#~ "Bad magic number in disk label - Can't open disk label " -#~ "package. Lisäksi jotkin sun4c-mallit (kuten IPX) eivät " -#~ "tue pakattuja otoksia joita levykkeillä käytetään, eli myöskään sun4c ei " -#~ "ole tuettu." - -#~ 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 ." -#~ msgstr "" -#~ "Useissa Sparceissa (esim. Ultra 10) on OBP-vika, joka estää niitä " -#~ "käynnistymästä (vaikka käynnistäminen on tuettu). Sopiva OBP-päivitys " -#~ "voidaan noutaa tuotenumerona ID 106121 osoitteesta ." - -#~ msgid "" -#~ "If you are booting from the floppy, and you see messages such as " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " then it is possible that floppy booting is " -#~ "simply not supported on your machine." -#~ msgstr "" -#~ "Mikäli levykkeeltä käynnistettäessä näkyy viestejä kuten " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " on mahdollista, että levykkeeltä " -#~ "käynnistämistä ei lainkaan tueta tällä koneella." - -#~ msgid "IDPROM Messages" -#~ msgstr "IDPRO:min viestit" - -#~ msgid "" -#~ "If you cannot boot because you get messages about a problem with " -#~ "IDPROM, then it's possible that your NVRAM battery, which " -#~ "holds configuration information for you firmware, has run out. See the " -#~ "Sun NVRAM FAQ for more " -#~ "information." -#~ msgstr "" -#~ "Jos käynnistäminen ei onnistu, ja vikailmoitukset koskevat IDPROM:ia, on mahdollista etä NVRAM:in paristo on tyhjentynyt. NVRAM:iin " -#~ "tallennetaan laitteiston asetukset. Katso lisätietoja osoitteesta Sun NVRAM FAQ." - -#~ 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 "" -#~ "Käynnistysparametrit ovat Linuxin ytimen parametreja, joilla varmistetaan " -#~ "oheislaitteita käytettävän asianmukaisesti. Enimmäkseen ydin osaa " -#~ "tunnistaa oheislaitteiden tiedot automaattisesti. Joissain tapauksissa on " -#~ "ydintä kuitenkin hieman autettava." - -#~ 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 "" -#~ "Jos järjestelmän käynnistämistä yritetään ensimmäistä kertaa, kokeile " -#~ "käynnistysparametrien oletusarvoja (eli älä anna mitään parametreja) ja " -#~ "katso toimiiko kaikki oikein. Luultavasti toimii. Jos ei toimi, voidaan " -#~ "myöhemmin käynnistää uudestaan ja etsiä erikoisparametreja jotka kertovat " -#~ "järjestelmälle laitteistosta." - -#~ msgid "" -#~ "Information on many boot parameters can be found in the Linux BootPrompt " -#~ "HOWTO, including tips for obscure hardware. This section contains " -#~ "only a sketch of the most salient parameters. Some common gotchas are " -#~ "included below in ." -#~ msgstr "" -#~ " Linux " -#~ "BootPrompt HOWTO:sta löytyy tietoa monista " -#~ "käynnistysparametreista, mukaan lukien vinkkejä epämääräisille " -#~ "laitteille. Tämä luku on vain luonnos tärkeimmistä parametreista. " -#~ "Joitakin yleisiä kompastuskiviä on selitetty kohdassa ." - -#~ msgid "" -#~ "When the kernel boots, a message \n" -#~ "Memory:availk/totalk available\n" -#~ " should be emitted early in the process. " -#~ "total 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 mem=ram parameter, where ram " -#~ "is set to the amount of memory, suffixed with k for " -#~ "kilobytes, or m for megabytes. For example, both " -#~ "mem=65536k and mem=64m mean " -#~ "64MB of RAM." -#~ msgstr "" -#~ "Kun ydin käynnistyy, viestin \n" -#~ "Memory:availk/totalk available\n" -#~ " pitäisi näkyä kohtalaisen alussa. " -#~ "total pitäisi olla koneen kaiken keskusmuistin " -#~ "määrä kilotavuissa. Jos tämä ei vastaa koneeseen asennettua muistia, on " -#~ "käytettävä parametria mem=ram, missä ram on muistin määrä. " -#~ "Yksikkö ilmoitetaan kirjaimella k kilotavuille ja " -#~ "m:llä megatavuille. Esimerkiksi sekä " -#~ "mem=65536k että mem=64m " -#~ "tarkoittavat 64 Mt keskusmuistia." - -#~ msgid "" -#~ "If you are booting with a serial console, generally the kernel will " -#~ "autodetect this (although not on DECstations). 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 console=device argument to the kernel, where " -#~ "device is your serial device, which is usually " -#~ "something like ttyS0." -#~ msgstr "" -#~ "Käytettäessä käynnistyksessä sarjapäätettä, osaa ydin yleensä havaita " -#~ "tämän automaattisesti (tosin DECstationeilla ei " -#~ "havaita). Jos myös näytönohjain (framebuffer) ja näppäimistö " -#~ "ovat kiinni sarjapäätettä käyttäen käynnistettävässä tietokoneessa, pitää " -#~ "ehkä antaa ytimelle parametri console=laite, missä laite on " -#~ "sarjaportti, joka yleensä on suunnilleen ttyS0." - -#~ msgid "" -#~ "For &arch-title; the serial devices are ttya or " -#~ "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " -#~ "ttya." -#~ msgstr "" -#~ "Suoritinperheellä &arch-title; sarjaporttien laitenimet ovat " -#~ "ttya tai ttyb. Toinen tapa " -#~ "antaa OpenPROM:n muuttujille input-device ja output-" -#~ "device arvoksi ttya." - -#~ msgid "Debian Installer Parameters" -#~ msgstr "Debianin asentimen parametrit" - -#~ msgid "" -#~ "The installation system recognizes a few additional boot " -#~ "parameters With current kernels (2.6.9 or newer) you can " -#~ "use 32 command line options and 32 environment options. If these numbers " -#~ "are exceeded, the kernel will panic. which may be " -#~ "useful." -#~ msgstr "" -#~ "Asennusjärjestelmä tunnistää muutamia lisäparametreja " -#~ "Nykyisillä ytimillä (versio 2.6.9 tai uudempi) voidaan käyttää 32:ta " -#~ "komentorivin parametriä ja 32:ta ympäristömuuttujaa. Jos nämä rajat " -#~ "ylitetään, tapahtuu kernel panic. , jotka voivat olla " -#~ "hyödyllisiä." - -#~ msgid "debconf/priority" -#~ msgstr "debconf/priority" - -#~ msgid "" -#~ "This parameter sets the lowest priority of messages to be displayed. " -#~ "Short form: priority" -#~ msgstr "" -#~ "Tämä parametri määrää, kuinka alhaisen prioriteetin viestit näytetään. " -#~ "Lyhyt muoto: priority" - -#~ msgid "" -#~ "The default installation uses priority=high. 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 "" -#~ "Oletusasennus käyttää asetusta priority=high. Tämä " -#~ "tarkoittaa, että näytetään viestit, joiden prioriteetti on korkea tai " -#~ "kriittinen, mutta prioriteetin keskitaso ja matala viestit ohitetaan. Jos " -#~ "tulee pulmia, asennin säätää prioriteettia tarpeen mukaan." - -#~ msgid "" -#~ "If you add priority=medium as boot parameter, you " -#~ "will be shown the installation menu and gain more control over the " -#~ "installation. When priority=low is used, all " -#~ "messages are shown (this is equivalent to the expert " -#~ "boot method). With priority=critical, the " -#~ "installation system will display only critical messages and try to do the " -#~ "right thing without fuss." -#~ msgstr "" -#~ "Jos käynnistysparametriksi lisätään priority=medium, näytetään asennusvalikko ja pystytään tarkemmin säätämään " -#~ "asennusta. Kun käytetään priority=low, näytetään " -#~ "kaikki viestit (tämä on sama kuin käynnistystapa expert). Kun asetus on priority=critical, " -#~ "asennusjärjestelmä näyttää vain kriittiset viestit ja yrittää tehdä " -#~ "oikeat valinnat kyselemättä turhia." - -#~ msgid "DEBIAN_FRONTEND" -#~ msgstr "DEBIAN_FRONTEND" - -#~ msgid "" -#~ "This boot parameter controls the type of user interface used for the " -#~ "installer. The current possible parameter settings are: " -#~ " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " -#~ "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk The default frontend is " -#~ "DEBIAN_FRONTEND=newt. " -#~ "DEBIAN_FRONTEND=text may be preferable for serial " -#~ "console installs. Generally only the newt frontend " -#~ "is available on default install media. On architectures which support it, " -#~ "the graphical installer uses the gtk frontend." -#~ msgstr "" -#~ "Tämä parametri määrää asentimen käyttämän käyttöliittymän tyypin. Tällä " -#~ "hetkellä ovat mahdollisia parametrin arvot: " -#~ "DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " -#~ "DEBIAN_FRONTEND=gtk Käyttöliittymän oletusarvo on " -#~ "DEBIAN_FRONTEND=newt. " -#~ "DEBIAN_FRONTEND=text saattaa olla parempi " -#~ "sarjapäättellä tehtäville asennuksille. Yleensä vain newt on saatavilla oletusasennustaltioilla, joten tämä asetus ei " -#~ "ole järin hyödyllinen juuri nyt. Graafista asenninta tukevilla " -#~ "suoritinperheillä graafinen asennin käyttää gtk-" -#~ "käyttöliittymää." - -#~ msgid "BOOT_DEBUG" -#~ msgstr "BOOT_DEBUG" - -#~ 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 "" -#~ "Asettamalla tämän käynnistysparametrin arvoksi 2 asentimen " -#~ "käynnistysprosessi tekee yksityiskohtaisen lokin. Arvolla 3 ovat " -#~ "vianjäljitykseen tarkoitetut komentotulkit käytössä asennusprosessin " -#~ "tärkeissä vaiheissa. (Käynnistystä jatketaan poistumalla komentotulkista.)" - -#~ msgid "BOOT_DEBUG=0" -#~ msgstr "BOOT_DEBUG=0" - -#~ msgid "This is the default." -#~ msgstr "Tämä on oletusarvo" - -#~ msgid "BOOT_DEBUG=1" -#~ msgstr "BOOT_DEBUG=1" - -#~ msgid "More verbose than usual." -#~ msgstr "Tavallista yksityiskohtaisempi." - -#~ msgid "BOOT_DEBUG=2" -#~ msgstr "BOOT_DEBUG=2" - -#~ msgid "Lots of debugging information." -#~ msgstr "Paljon vianjäljitystietoa." - -#~ msgid "BOOT_DEBUG=3" -#~ msgstr "BOOT_DEBUG=3" - -#~ msgid "" -#~ "Shells are run at various points in the boot process to allow detailed " -#~ "debugging. Exit the shell to continue the boot." -#~ msgstr "" -#~ "Käynnistysprosessin valikoiduissa kohdissa käynnistetään komentotulkki. " -#~ "Jatka käynnistystä poistumalla komentotulkista." - -#~ msgid "INSTALL_MEDIA_DEV" -#~ msgstr "INSTALL_MEDIA_DEV" - -#~ msgid "" -#~ "The value of the parameter is the path to the device to load the Debian " -#~ "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ msgstr "" -#~ "Tämän parametrin arvo on sen laitteen polkunimi, josta Debianin asennin " -#~ "ladataan. Esimerkiksi INSTALL_MEDIA_DEV=/dev/floppy/0" - -#~ msgid "" -#~ "The boot floppy, which normally scans all floppies it can to find the " -#~ "root floppy, can be overridden by this parameter to only look at the one " -#~ "device." -#~ msgstr "" -#~ "Normaalisti käynnistyslevyke etsii root-levykettä kaikista " -#~ "levykeasemista. Tällä parametrilla saadaan etsintä kohdistumaan vain " -#~ "yhteen nimettyyn laitteeseen." - -#~ msgid "debian-installer/framebuffer" -#~ msgstr "debian-installer/framebuffer" - -#~ 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 debian-installer/" -#~ "framebuffer=false, or fb=false for " -#~ "short. Problem symptoms are error messages about bterm or bogl, a blank " -#~ "screen, or a freeze within a few minutes after starting the install." -#~ msgstr "" -#~ "Joissakin suoritinperheissä käytetään ruutupuskuria (framebuffer), jotta " -#~ "asennus olisi saatavilla useilla kielillä. Jos ruutupuskuri aiheuttaa " -#~ "pulmia, se voidaan ottaa pois käytöstä parametrilla debian-" -#~ "installer/framebuffer=false, tai lyhyemmällä muodolla " -#~ "fb=false. Pulman oireita ovat virheilmoitukset " -#~ "btermistä tai bogl:stä, tyhjä ruutu tai jumittuminen muutaman minuutin " -#~ "sisällä asennuksen alusta." - -#~ msgid "" -#~ "The video=vga16:off argument may also be used to " -#~ "disable the kernel's use of the framebuffer. Such problems have been " -#~ "reported on a Dell Inspiron with Mobile Radeon card." -#~ msgstr "" -#~ "Myöskin parametrilla video=vga16:off saadaan ydin " -#~ "jättämään ruutupuskuri käyttämättä. Pulmista on ilmoitettu Dell " -#~ "Inspironeilla joissa on näytönohjaimena Mobile Radeon." - -#~ msgid "Such problems have been reported on the Amiga 1200 and SE/30." -#~ msgstr "Pulmista on ilmoitettu Amiga 1200:lla ja SE/30:llä." - -#~ msgid "Such problems have been reported on hppa." -#~ msgstr "Pulmista on ilmoitettu hppa:lla." - -#~ msgid "" -#~ "Because of display problems on some systems, framebuffer support is " -#~ "disabled by default 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 " -#~ "debian-installer/framebuffer=true or " -#~ "fb=true for short." -#~ msgstr "" -#~ "Joillakin järjestelmillä ilmenneiden näyttöpulmien vuoksi on " -#~ "ruutupuskkuri oletusarvona pois käytöstä " -#~ "suoritinperheellä &arch-title;. Tästä voi olla seurauksena ruma ruutu " -#~ "laitteissa jotka tukisivat ruutupuskuria kunnolla, kuten ATI:n " -#~ "näytönohjainta käyttävät mallit. Jos asentimessa näkyy näyttöpulmia, " -#~ "voidaan kokeilla käynnistämistä parametrilla debian-installer/" -#~ "framebuffer=true tai lyhyemmin fb=true." - -#~ msgid "debian-installer/theme" -#~ msgstr "debian-installer/theme" - -#~ msgid "" -#~ "A theme determines how the user interface of the installer looks (colors, " -#~ "icons, etc.). What themes are available differs per frontend. Currently " -#~ "both the newt and gtk frontends only have a dark theme " -#~ "that was designed for visually impaired users. Set the theme by booting " -#~ "with parameter debian-installer/theme=dark or theme=dark." -#~ msgstr "" -#~ "Teema määrää asentimen käyttöliittymän ulkonäön (värit, kuvakkeet, jne.). " -#~ "Saatavilla olevat teemat ovat käyttöliittymäkohtaisia. Tällä hetkellä " -#~ "vain käyttöliittymillä newt ja gtk on teema dark, joka " -#~ "suunniteltiin näkövammaisille. Aseta teema käynnistämällä parametrilla " -#~ "debian-installer/theme=dark tai theme=dark." - -#~ msgid "debian-installer/probe/usb" -#~ msgstr "debian-installer/probe/usb" - -#~ msgid "" -#~ "Set to false to prevent probing for USB on boot, " -#~ "if that causes problems." -#~ msgstr "" -#~ "Asettamalla arvoksi false ei USB-laitteita tutkita " -#~ "käynnistyksessä, eli vältytään USB-pulmilta." - -#~ msgid "netcfg/disable_dhcp" -#~ msgstr "netcfg/disable_dhcp" - -#~ 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 "" -#~ "Oletusarvona &d-i; yrittää automaattisesti noutaa verkkoasetukset DHCP:" -#~ "llä. Jos tämä onnistuu, ei saatuja asetuksia pääse näkemään ja " -#~ "muuttamaan. Verkkoasetukset pääsee tekemään itse vain jos DHCP " -#~ "epäonnistuu." - -#~ 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 " -#~ "netcfg/disable_dhcp=true to prevent configuring " -#~ "the network with DHCP and to enter the information manually." -#~ msgstr "" -#~ "Mikäli paikallisverkossa on DHCP-palvelin, mutta sen käyttöä halutaan " -#~ "välttää, esimerkiksi koska sen antamat verkkoasetukset ovat väärin, " -#~ "voidaan käyttää parametria netcfg/disable_dhcp=true. Tämä estää verkkoasetusten noutamisen DHCP:llä ja tiedot voi " -#~ "kirjoittaa itse." - -#~ msgid "hw-detect/start_pcmcia" -#~ msgstr "hw-detect/start_pcmcia" - -#~ msgid "" -#~ "Set to false to prevent starting PCMCIA services, " -#~ "if that causes problems. Some laptops are well known for this misbehavior." -#~ msgstr "" -#~ "Mikäli PCMCIA-palvelut aiheuttavat pulmia, aseta tämä arvoon " -#~ "false. Tämä on tunnetusti tarpeen jollakin " -#~ "läppäreillä." - -#~ msgid "preseed/url" -#~ msgstr "preseed/url" - -#~ msgid "" -#~ "Specify the url to a preconfiguration file to download and use in " -#~ "automating the install. See . Short " -#~ "form: url." -#~ msgstr "" -#~ "Anna url noudettavaan valmiiden vastausten tiedostoon. Tiedosto noudetaan " -#~ "käytettäessä automaattista asennusta. Katso . Lyhyt muoto: url" - -#~ msgid "preseed/file" -#~ msgstr "preseed/file" - -#~ msgid "" -#~ "Specify the path to a preconfiguration file to load to automating the " -#~ "install. See . Short form: " -#~ "file." -#~ msgstr "" -#~ "Anna valmiiden vastausten tiedoston polkunimi. Tiedosto noudetaan " -#~ "käytettäessä automaattista asennusta. Katso . Lyhyt muoto: tiedosto" - -#~ msgid "auto-install/enabled" -#~ msgstr "auto-install/enabled" - -#~ msgid "" -#~ "Delay questions that are normally asked before preseeding is possible " -#~ "until after the network is configured. Short form: auto=true See for details about using " -#~ "this to automate installs." -#~ msgstr "" -#~ "Viivästä, jos mahdollista, normaalisti ennen valmiita vastauksia " -#~ "kysyttäviä kysymyksiä, kunnes verkon asetukset on tehty. Lyhyt muoto: " -#~ "auto=true. Katso kohdasta yksityiskohtaisempia ohjeita tämän hyödyntämisestä asennuksen " -#~ "automatisoinnissa." - -#~ msgid "cdrom-detect/eject" -#~ msgstr "cdrom-detect/eject" - -#~ 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 "" -#~ "Oletusarvona &d-i; poistaa automaattisesti asennuksessa käytetyn rompun " -#~ "asemasta ennen uudelleenkäynnistystä. Tämä saattaa olla tarpeetonta, jos " -#~ "tietokone ei automaattisesti käynnisty rompulta. Joissakin tapauksissa se " -#~ "voi olla jopa ei-toivottavaa, esimerkiksi jos romppuasema ei osaa vetää " -#~ "romppua takaisin sisään eikä käyttäjä ole paikalla työntämässä sitä " -#~ "asemaan. Monet kelkattomat, ohuet ja caddyä käyttävät romppuasemat eivät " -#~ "osaa ladata romppua asemaan automaattisesti." - -#~ msgid "" -#~ "Set to false 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 "" -#~ "Automaattinen rompun poisto asemasta estetään asettamalla arvoksi " -#~ "false, ja huomaa, että joutunet varmistamaan ettei " -#~ "kone käynnisty automaattisesti romppuasemalta asennuksen ensimmäisen " -#~ "vaiheen jälkeen." - -#~ msgid "ramdisk_size" -#~ msgstr "ramdisk_size" - -#~ msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -#~ msgstr "" -#~ "Jos käytetään ytimen versiota 2.2.x, saattaa olla tarpeen asettaa " -#~ "&ramdisksize;." - -#~ msgid "mouse/left" -#~ msgstr "mouse/left" - -#~ msgid "" -#~ "For the gtk frontend (graphical installer), users can switch the mouse to " -#~ "left-handed operation by setting this parameter to true." -#~ msgstr "" -#~ "Gtk-käyttöliittymään (graafinen asennin) voidaan hiiri vaihtaa " -#~ "vasenkätiseksi asettamalla tämän parametrin arvoksi true." - -#~ msgid "directfb/hw-accel" -#~ msgstr "directfb/hw-accel" - -#~ msgid "" -#~ "For the gtk frontend (graphical installer), hardware acceleration in " -#~ "directfb is disabled by default. To enable it, set this parameter to " -#~ "true when booting the installer." -#~ msgstr "" -#~ "Gtk-käyttöliittymässä (graafinen asennin) on directfb:n " -#~ "laitteistokiihdytys oletusarvona pois päältä. Sen saa päälle asettamalla " -#~ "tämän parametrin arvoksi true asenninta " -#~ "käynnistettäessä." - -#~ msgid "rescue/enable" -#~ msgstr "rescue/enable" - -#~ msgid "" -#~ "Set to true to enter rescue mode rather than " -#~ "performing a normal installation. See ." -#~ msgstr "" -#~ "Asettamalla arvoksi true käynnistetään " -#~ "pelastustila eikä tavallinen asennus. Katso ." - -#~ msgid "Using boot parameters to answer questions" -#~ msgstr "Valmiita vastauksia käynnistysparametreilla" - -#~ msgid "" -#~ "With some exceptions, a value can be set at the boot prompt for any " -#~ "question asked during the installation, though this is only really useful " -#~ "in specific cases. General instructions how to do this can be found in " -#~ ". Some specific examples are listed " -#~ "below." -#~ msgstr "" -#~ "Muutamaa poikkeusta lukuunottamatta käynnistysparametrilla voidaan antaa " -#~ "arvo mihin tahansa asennuksen aikana kysyttävään kysymykseen. Tosin tämä " -#~ "on hyödyllistä vain erikoistapauksissa. Yleisiä ohjeita tämän tekemisestä " -#~ "löytyy kohdasta . Esimerkkejä " -#~ "joistakin tapauksista on seuraavassa luettelossa." - -#~ msgid "debian-installer/locale" -#~ msgstr "debian-installer/locale" - -#~ msgid "" -#~ "Can be used to set both the language and country for the installation. " -#~ "This will only work if the locale is supported in Debian. Short form: " -#~ "locale. For example, use locale=de_CH to select German as language and Switserland as country." -#~ msgstr "" -#~ "Voidaan käyttää antamaan asennukselle sekä kieli että maa. Tämä toimii " -#~ "vain jos maa-asetusto on tuettu Debianissa. Lyhyt muoto: " -#~ "locale. Käytä esimerkiksi locale=sv_FI valitsemaan kieleksi ruotsi ja maaksi Suomi." - -#~ msgid "" -#~ "Set to true if you want to disable DHCP and " -#~ "instead force static network configuration." -#~ msgstr "" -#~ "Aseta arvoksi true, jos DHCP halutaan pois " -#~ "käytöstä ja pakotetaan kiinteät verkkoasetukset." - -#~ msgid "tasksel:tasksel/first" -#~ msgstr "tasksel:tasksel/first" - -#~ msgid "" -#~ "Can be used to select tasks that are not available from the interactive " -#~ "task list, such as the kde-desktop task. See for additional information. Short form: " -#~ "tasks." -#~ msgstr "" -#~ "Voidaan käyttää valitsemaan tehtäviä, jotka eivät ole käytettävissä " -#~ "vuorovaikutteisessa tehtävälistassa, kuten tehtävä kde-desktop. Katso lisätietoja kohdasta . Lyhyt " -#~ "muoto: tasks." - -#~ msgid "Passing parameters to kernel modules" -#~ msgstr "Parametrien välittäminen ytimen moduuleille" - -#~ msgid "" -#~ "If drivers are compiled into the kernel, you can pass parameters to them " -#~ "as described in the kernel documentation. However, if drivers are " -#~ "compiled as modules and because kernel modules are loaded a bit " -#~ "differently during an installation than when booting an installed system, " -#~ "it is not possible to pass parameters to modules as you would normally " -#~ "do. Instead, you need to use a special syntax recognized by the installer " -#~ "which will then make sure that the parameters are saved in the proper " -#~ "configuration files and will thus be used when the modules are actually " -#~ "loaded. The parameters will also be propagated automatically to the " -#~ "configuration for the installed system." -#~ msgstr "" -#~ "Jos ajurit on käännetty mukaan ytimeen, niille voidaan välittää " -#~ "parametreja ytimen ohjeissa kuvatulla tavalla. Jos ajurit kuitenkin on " -#~ "käännetty moduuleina, ja koska moduulit ladataan asennuksen aikana hieman " -#~ "eri tavalla kuin käynnistettäessä asennettua järjestelmää, ei parametreja " -#~ "ole mahdollista välittää tavalliseen tapaan. Sen sijaan on käytettävä " -#~ "asentimen tunnistamaa erikoismerkintää. Asennin varmistaa asetusten " -#~ "tallentuvan oikeisiin asetustiedostoihin ja tulevan sitä kautta käyttöön " -#~ "myös kun moduulit oikeasti ladataan. Parametrit välitetään " -#~ "automaattisesti myös asennetun järjestelmän asetustiedostoihin." - -#~ msgid "" -#~ "Note that it is now quite rare that parameters need to be passed to " -#~ "modules. In most cases the kernel will be able to probe the hardware " -#~ "present in a system and set good defaults that way. However, in some " -#~ "situations it may still be needed to set parameters manually." -#~ msgstr "" -#~ "Huomaa, että nykyään on harvinaista jos moduuleille on pakko välittää " -#~ "parametreja. Useimmissa tapauksissa ydin osaa tunnistaa järjestelmän " -#~ "laitteiston ja asettaa hyvät oletusarvot. Joissakin tapauksissa saattaa " -#~ "kuitenkin olla välttämätöntä asettaa parametrien arvo itse." - -#~ msgid "" -#~ "The syntax to use to set parameters for modules is: " -#~ "\n" -#~ "module_name.parameter_name=value\n" -#~ " If you need to pass multiple parameters to " -#~ "the same or different modules, just repeat this. For example, to set an " -#~ "old 3Com network interface card to use the BNC (coax) connector and IRQ " -#~ "10, you would pass:" -#~ msgstr "" -#~ "Moduulien paremetrit annetaan tässä muodossa: \n" -#~ "moduulin_nimi.parametrin_nimi=arvo\n" -#~ " Jos on annettava useita parametreja samalle " -#~ "tai eri moduuleille, toista vaan yllä olevaa. Esimerkiksi vanha 3Comin " -#~ "verkkokortti asetetaan käyttämään BNC-liitäntää (coax) ja keskeytystä IRQ " -#~ "10 seuraavasti:" - -#~ msgid "3c509.xcvr=3 3c509.irq=10" -#~ msgstr "3c509.xcvr=3 3c509.irq=10" - -#~ msgid "Troubleshooting the Installation Process" -#~ msgstr "Asennusprosessin vianetsintä" - -#~ msgid "CD-ROM Reliability" -#~ msgstr "Romppujen luetettavuus" - -#~ msgid "" -#~ "Sometimes, especially with older CD-ROM drives, the installer may fail to " -#~ "boot from a CD-ROM. The installer may also — even after booting " -#~ "successfully from CD-ROM — fail to recognize the CD-ROM or return " -#~ "errors while reading from it during the installation." -#~ msgstr "" -#~ "Joskus asennin ei käynnisty romppulta. Erityisesti näin voi käydä " -#~ "vanhoilla romppuasemilla. Myöskin voi sattua, että vaikka asennin on " -#~ "käynnistynyt rompulta, se ei tunnista romppuasemaa tai tulee lukuvirheitä " -#~ "asennuksen aikana. " - -#~ msgid "" -#~ "There are a many different possible causes for these problems. We can " -#~ "only list some common issues and provide general suggestions on how to " -#~ "deal with them. The rest is up to you." -#~ msgstr "" -#~ "Näihin pulmiin on monia mahdollisia syitä. Tässä luetellaan vain joitakin " -#~ "yleisiä tapauksia ja yleisiä toimintaohjeita. Lopusta saat huolehtia itse." - -#~ msgid "There are two very simple things that you should try first." -#~ msgstr "Ensiksi kannattaa kokeilla kahta hyvin yksinkertaista juttua." - -#~ msgid "" -#~ "If the CD-ROM does not boot, check that it was inserted correctly and " -#~ "that it is not dirty." -#~ msgstr "" -#~ "Jos romppu ei käynnisty, tarkista että se asetettiin asemaan oikein ja " -#~ "ettei se ole likainen." - -#~ msgid "" -#~ "If the installer fails to recognize a CD-ROM, try just running the option " -#~ " Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM " -#~ "drives are known to be resolved in this way." -#~ msgstr "" -#~ "Mikäli asennin ei tunnista romppua, yritä käynnistää uudelleen valikosta " -#~ " Detect and mount CD-ROM . Jotkin DMA:han liittyvät jutut vanhoissa romppuasemissa " -#~ "ratkeavat tunnetusti tällä tavalla." - -#~ msgid "" -#~ "If this does not work, then try the suggestions in the subsections below. " -#~ "Most, but not all, suggestions discussed there are valid for both CD-ROM " -#~ "and DVD, but we'll use the term CD-ROM for simplicity." -#~ msgstr "" -#~ "Jos tämä ei toimi, kokeile seuraavien alilukujen ehdotuksia. Useimmat, " -#~ "mutta eivät kaikki, ehdotukset kelpaavat sekä CD-ROMille että DVD:lle, " -#~ "mutta käytämme yksinkertaisuuden vuoksi termiä romppu." - -#~ msgid "" -#~ "If you cannot get the installation working from CD-ROM, try one of the " -#~ "other installation methods that are available." -#~ msgstr "" -#~ "Jos asennus ei onnistu rompulta, kokeile muita saatavilla olevia " -#~ "asennustapoja." - -#~ msgid "Common issues" -#~ msgstr "Yleisiä pulmia" - -#~ msgid "" -#~ "Some older CD-ROM drives do not support reading from discs that were " -#~ "burned at high speeds using a modern CD writer." -#~ msgstr "" -#~ "Jotkut vanhat romppuasemat eivät tue uusilla kirjoittavilla " -#~ "romppuasemilla suurilla nopeuksilla kirjoitettujen romppujen lukemista." - -#~ msgid "" -#~ "If your system boots correctly from the CD-ROM, it does not necessarily " -#~ "mean that Linux also supports the CD-ROM (or, more correctly, the " -#~ "controller that your CD-ROM drive is connected to)." -#~ msgstr "" -#~ "Vaikka tietokone käynnistyisikin rompulta ongelmitta, ei se välttämättä " -#~ "tarkoita Linuxin tukevan kyseistä romppuasemaa (tai täsmällisemmin, " -#~ "ohjainta jossa romppuasema on kiinni)." - -#~ msgid "" -#~ "Some older CD-ROM drives do not work correctly if direct memory " -#~ "access (DMA) is enabled." -#~ msgstr "" -#~ "Jotkut vanhat romppuasemat eivät toimi oikein jos direct memory " -#~ "access (DMA) on käytössä." - -#~ msgid "How to investigate and maybe solve issues" -#~ msgstr "Miten pulmia tutkitaan ja ehkä selvitetään" - -#~ msgid "If the CD-ROM fails to boot, try the suggestions listed below." -#~ msgstr "Jos romppu ei käynnisty, kokeile alla lueteltuja ehdotuksia." +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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 "" +"Mikäli laitteistossa on 53c9x-piirillä toimiva SCSI-väylä, saatetaan joutua " +"käyttämään ytimen parametria mac53c9x=1,0. Quadra 950 " +"tapaisilla koneilla, joissa on kaksi SCSI-väylää, on sitävastoin käytettävä " +"mac53c9x=2,0. Toinen tapa on antaa parametri muodossa " +"mac53c9x=-1,0 jolloin automaattitunnistus jää päälle, " +"mutta SCSI disconnect otetaan pois päältä. Huomaa, että tämä parametri on " +"tarpeellinen vain jos kiintolevyjä on enemmän kuin yksi; muussa tapauksessa " +"järjestelmä toimii nopeammin jos sitä ei käytetä." + +#. Tag: title +#: boot-installer.xml:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "MVME147 ja MVME16x" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" +"MVME147:lle ja MVME16x:lle asennin voidaan käynnistää joko levykkeiltä " +"(katso ) tai verkosta (katso ). Toisin sanoen rompulta ei voi käynnistää." +"" + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" +"Q40/Q60:lle ainoa asennustapa on kiintolevyltä (katso ). Toisin sanoen rompulta ei voi käynnistää." + +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "Käynnistäminen kiintolevyltä" + +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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 "" +"Käynnistäminen koneessa jo olevasta käyttöjärjestelmäst on usein kätevä " +"tapa; joillekin järjestelmille se on ainoa tuettu asennustapa." -#~ msgid "" -#~ "Check that your BIOS actually supports booting from CD-ROM (older systems " -#~ "possibly don't) and that your CD-ROM drive supports the media you are " -#~ "using." -#~ msgstr "" -#~ "Tarkista että BIOS oikeasti tukee rompulta käynnistämistä (vanhat koneet " -#~ "luultavasti eivät tue) ja että romppuasema tukee käytettyä taltiota." +#. Tag: para +#: boot-installer.xml:1769 boot-installer.xml:2367 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"Käynnistettäessä asennin kiintolevyltä on tarvittavat tiedostot pitänyt jo " +"noutaa ja tallentaa kohdassa ." -#~ msgid "" -#~ "If you downloaded an iso image, check that the md5sum of that image " -#~ "matches the one listed for the image in the MD5SUMS " -#~ "file that should be present in the same location as where you downloaded " -#~ "the image from. \n" -#~ "$ md5sum debian-testing-i386-netinst.iso\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-" -#~ "netinst.iso\n" -#~ " Next, check that the md5sum of the burned CD-" -#~ "ROM matches as well. The following command should work. It uses the size " -#~ "of the image to read the correct number of bytes from the CD-ROM." -#~ msgstr "" -#~ "Jos noudit ISO-otoksen, tarkista otoksen md5sum-tarkistussumman vastaavan " -#~ "otoksen summaa tiedostossa MD5SUMS. Tiedoston " -#~ "pitäisi olla samassa paikassa kuin noudettu otos. " -#~ "\n" -#~ "$ md5sum debian-testing-i386-netinst.iso\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-" -#~ "netinst.iso\n" -#~ " Seuraavaksi kannattaa tarkistaa, että myöskin " -#~ "poltetun rompun md5sum täsmää. Seuraavan komennon pitäisi toimia. Se " -#~ "käyttää otoksen kokoa lukeakseen oikean määrän tavuja rompulta." +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" +"Kiintolevyltä käynnistettäessä voidaan käyttää ainakin kuutta erilaista " +"muistilevyä, kolmea eri tyyppiä ja jokainen joko 2.2.x-linuxytimen tuen kera " +"tai ilman (katso MANIFEST:istä lisätietoja)." + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" +"Kolme eri muistilevyn tyyppiä ovat cdrom, hd-" +"media, ja nativehd. Näiden muistilevyjen " +"erona on vain se, mistä ne hakevat asennettavat paketit. Muistilevy " +"cdrom noutaa debianin asentimen paketit rompulta. " +"hd-media käyttää kiintolevyllä olevaa tiedostoa, joka " +"on rompun ISO-otos. Lopuksi nativehd noutaa paketit " +"verkosta." + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "Käynnistäminen AmigaOS:stä" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"Käynnistä Workbench:ssä Linuxin asennusprosessi " +"kaksoisnapsauttamalla kuvaketta StartInstall hakemistossa " +"debian." -#~ msgid "" -#~ "$ dd if=/dev/cdrom | \\\n" -#~ "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" -#~ "> md5sum\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 -\n" -#~ "262668+0 records in\n" -#~ "262668+0 records out\n" -#~ "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" -#~ msgstr "" -#~ "$ dd if=/dev/cdrom | \\\n" -#~ "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" -#~ "> md5sum\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 -\n" -#~ "262668+0 records in\n" -#~ "262668+0 records out\n" -#~ "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" +"Joudut ehkä painamaan &enterkey; kahdesti kun Amigan asennusohjelma on " +"tulostanut joitakin virheenjäljitystietoja ikkunaan. Tämän jälkeen on " +"muutaman sekunnin viive. Seuraavaksi pitäisi näkyä musta ruutu jossa on " +"valkoista tekstiä, siinä näkyy kaikenlaista ytimen virheenjäljitystietoa. " +"Ruudun vieritys saattaa toimia niin nopeasti, ettei viestejä ehdi lukea, " +"mutta sillä ei ole väliä. Muutaman sekunnin kuluttua asennusohjelman pitäisi " +"käynnistyä automaattisesti, joten voidaan jatkaa kohtaan ." + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "Käynnistäminen Atari TOS:sta" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" +"Käynnistä GEM-työpöydällä Linuxin asennusprosessi kaksoisnapsauttamalla " +"kuvaketta bootstra.prg hakemistossa debian ja napsauttamalla painiketta Ok ohjelman " +"asetusten valintaikkunassa." + +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" +"Joudut ehkä painamaan &enterkey; kahdesti kun Atarin käynnistyslatain on " +"tulostanut joitakin virheenjäljitystietoja ikkunaan. Tämän jälkeen ruutu " +"muuttuu harmaaksi, ja tulee muutaman sekunnin viive. Seuraavaksi pitäisi " +"näkyä musta ruutu jossa on valkoista tekstiä, siinä näkyy kaikenlaista " +"ytimen virheenjäljitystietoa. Ruudun vieritys saattaa toimia niin nopeasti, " +"ettei viestejä ehdi lukea, mutta sillä ei ole väliä. Muutaman sekunnin " +"kuluttua asennusohjelman pitäisi käynnistyä automaattisesti, joten voidaan " +"jatkaa kohtaan ." + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "Käynnistäminen MacOS:stä" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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 "" +"Alkuperäinen Mac-järjestelmä on säilytettävä ja käynnistettävä siitä. " +"Olennaista on, että käynnistettäessä MacOS:ää " +"valmisteltaessa Penguin-linuxlataimen käynnistämistä, pidetään " +"Vaihto-näppäintä pohjassa jotta estetään laajennosten " +"lataaminen. Jos MacOS:ää käytetään vain linuxin lataamiseen, voidaan poistaa " +"kaikki laajennokset ja järjestelmäikkunat Macin Järjestelmäkansiosta, " +"tällöin ei tarvitse pitää Vaihto-näppäintä pohjassa. " +"Muutoin laajennokset saattavat jäädä käyntiin ja aiheuttavat satunnaisia " +"ongelmia ajossa olevalle linux-ytimelle." + +#. Tag: para +#: boot-installer.xml:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" +"Maceissä on käytettävä Penguin-käynnistyslatainta. Mikäli " +"käytettävissä ei ole työkaluja Stuffit-arkiston " +"käsittelyyn, on Penguin purettuna &penguin19.hfs; hfs-" +"levyotoksessa. Kohdassa kerrotaan miten " +"tämä otos kopiodaan levykkeelle." + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." +msgstr "" +"Käynnistä MacOS:n työpöydällä Linuxin asennusprosessi kaksoisnapsauttamalla " +"kuvaketta Penguin Prefs hakemistossa Penguin. Penguin-käynnistin käynnistyy. Valitse " +"File-valikossa kohta Settings, " +"napsauta välilehteä Kernel. Valitse ytimen " +"(vmlinuz) ja muistilevyn (initrd.gz) otokset hakemistossa install painamalla " +"niitä vastaavia painikkeita oikeassa yläkulmassa, ja etenemällä " +"tiedostonvalintaikkunoissa niiden kohdalle." + +#. Tag: para +#: boot-installer.xml:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" +"Käynnistysparametrit asetetaan Penguinissa valitsemalla File -> Settings..., sitten vaihdetaan " +"välilehteen Options. Käynnistysparametrit voidaan " +"kirjoittaa tekstinsyöttöalueeseen. Mikäli näitä asetuksia halutaan käyttää " +"aina, valitaan File -> Save Settings as " +"Default." + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"Sulje Settings-valintaikkuna, tallenna asetukset ja " +"käynnistä alkulataus valikon File kohdasta " +"Boot Now." -#~ msgid "" -#~ "If, after the installer has been booted successfully, the CD-ROM is not " -#~ "detected, sometimes simply trying again may solve the problem. If you " -#~ "have more than one CD-ROM drive, try changing the CD-ROM to the other " -#~ "drive. If that does not work or if the CD-ROM is recognized but there are " -#~ "errors when reading from it, try the suggestions listed below. Some basic " -#~ "knowledge of Linux is required for this. To execute any of the commands, " -#~ "you should first switch to the second virtual console (VT2) and activate " -#~ "the shell there." -#~ msgstr "" -#~ "Jos järjestelmä ei havaitse romppua kun asennin on käynnistynyt " -#~ "onnistuneesti, auttaa joskus kun vaan koitetaan uudestaan. Jos " -#~ "romppuasemia on useita, yritä vaihtaa romppu toiseen asemaan. Jos se ei " -#~ "toimi, tai jos romppu tunnistetaan mutta tulee lukuvirheitä, yritä alla " -#~ "lueteltuja ehdotuksia. Tähän tarvitaan perustiedot Linuxista. Komentojen " -#~ "antamiseksi on ensin vaihdettava toiseen virtuaalikonsoliin (VT2) ja " -#~ "käynnistettävä siihen komentotulkki." +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" +"Penguin-käynnistin tulostaa joitakin " +"virheenjäljitystietoja ikkunaan. Tämän jälkeen ruutu muuttuu harmaaksi, ja " +"tulee muutaman sekunnin viive. Seuraavaksi näkyy musta ruutu jossa on " +"valkoista tekstiä, siinä näkyy kaikenlaista ytimen virheenjäljitystietoa. " +"Ruudun vieritys saattaa toimia niin nopeasti, ettei viestejä ehdi lukea, " +"mutta sillä ei ole väliä. Muutaman sekunnin kuluttua asennusohjelman " +"pitäisi käynnistyä automaattisesti, joten voidaan jatkaa kohtaan ." + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "Käynnistäminen Q40/Q60:stä" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "FIXME" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"Asennusohjelman pitäisi käynnistyä automaattisesti, joten voidaan jatkaa " +"kohtaan " -#~ msgid "" -#~ "Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any " -#~ "specific error messages. After that, also check the output of " -#~ "dmesg." -#~ msgstr "" -#~ "Vaihtamalla konsoliin VT4 tai lukemalla tiedostoa /var/log/" -#~ "syslog (käytä komentoa nano teksturina) " -#~ "näkee tarkat virheilmoitukset. Tämän jälkeen katso myös komennon " -#~ "dmesg tuloste." +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" +"Tällä hetkellä suoritinperheen &arch-title; ainoa rompulta käynnistystä " +"tukeva suoritinarkkitehtuuri on BVME6000." -#~ msgid "" -#~ "Check in the output of dmesg if your CD-ROM drive was " -#~ "recognized. You should see something like (the lines do not necessarily " -#~ "have to be consecutive): \n" -#~ "Probing IDE interface ide1...\n" -#~ "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" -#~ "ide1 at 0x170-0x177,0x376 on irq 15\n" -#~ "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" -#~ "Uniform CD-ROM driver Revision: 3.20\n" -#~ " If you don't see something like that, chances " -#~ "are the controller your CD-ROM is connected to was not recognized or may " -#~ "be not supported at all. If you know what driver is needed for the " -#~ "controller, you can try loading it manually using modprobe." -#~ msgstr "" -#~ "Tarkista komennon dmesg tulosteesta tunnistuiko " -#~ "romppuasema. Pitäisi näkyä jotain seuraavan kaltaista (rivit eivät " -#~ "välttämättä ole suoraan peräkkäin): \n" -#~ "Probing IDE interface ide1...\n" -#~ "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" -#~ "ide1 at 0x170-0x177,0x376 on irq 15\n" -#~ "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" -#~ "Uniform CD-ROM driver Revision: 3.20\n" -#~ " Jos tuollaista ei näy, on todennäköistä ettei " -#~ "linux tunnistanut ohjainta jossa romppuasema on kiinni, tai sitä ei ehkä " -#~ "tueta lainkaan. Jos tiedät mikä ajuri ohjeimelle tarvitaan, voit kokeilla " -#~ "sen lataamista itse komennolla modprobe." +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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 "" +"VMEbus-järjestelmien käynnistyttyä näkyy LILO:n kehote Boot:. Käynnistä Linux ja varsinainen Debianin asennus vt102-pääte-" +"emulaatiota käyttäen kirjoittamalla kehotteeseen joku seuraavista:" + +#. Tag: para +#: boot-installer.xml:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "" +"Kirjoittamalla i6000 &enterkey; asennetaan BVME4000/6000" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "kirjoittamalla i162 &enterkey; asennetaan MVME162" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "kirjoittamalla i167 &enterkey; asennetaan MVME166/167" + +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"Loppuun voidaan lisätä merkkijono TERM=vt100 jolloin " +"käytetään vt100-pääte-emulointia, esim. i6000 TERM=vt100 &enterkey;." -#~ msgid "" -#~ "Check that there is a device node for your CD-ROM drive under /" -#~ "dev/. In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." -#~ msgstr "" -#~ "Tarkista romppuasemalle olevan laitetiedosto hakemistossa /dev/" -#~ ". Alla olevassa esimerkissä se olisi tiedosto /dev/" -#~ "hdc. Pitäisi olla myös /dev/cdroms/cdrom0." +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" +"Useimmille suoritinperheen &arch-title; laitteille suositellaan " +"käynnistämistä koneen omasta tiedostojärjestelmästä." -#~ msgid "" -#~ "Use the mount command to check if the CD-ROM is " -#~ "already mounted; if not, try mounting it manually: " -#~ "\n" -#~ "$ mount /dev/hdc /cdrom\n" -#~ " Check if there are any error messages after " -#~ "that command." -#~ msgstr "" -#~ "Tarkista komennolla mount onko romppu jo liitetty; jos " -#~ "ei ole, kokeile sen liittämistä itse: \n" -#~ "$ mount /dev/hdc /cdrom\n" -#~ " Tarkista tuleeko komennon jälkeen " -#~ "virheilmoituksia." +#. Tag: para +#: boot-installer.xml:2054 +#, 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 "" +"Tällä hetkellä tuetaan levykkeeltä käynnistämistä vain Atarilla ja VME:llä " +"(VME:llä on oltava SCSI-levykeasema)." + +#. Tag: title +#: boot-installer.xml:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "SGI:n käynnistäminen TFTP:llä" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" +"After entering the command monitor use \n" +"bootp():\n" +" 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 netaddr environment variable. Type " +"\n" +"unsetenv netaddr\n" +" in the command monitor to do this." +msgstr "" +"SGI:n koneilla käynnistetään linux ja aloitetaan Debianin asennus " +"kirjoittamalla komentotulkkiin \n" +"bootp():\n" +". Jotta tämä toimisi, voidaan joutua ensin " +"poistamaan ympäristömuuttuja netaddr. Kirjoita " +"komentotulkissa \n" +"unsetenv netaddr\n" +"." + +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 +#: boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "Broadcom BCM91250A: ja BCM91480B:n käynnistäminen TFTP:llä" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: " +"\n" +"ifconfig eth0 -auto\n" +" Once you have obtained an IP address, you can " +"load SiByl with the following command: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 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 "" +"Broadcomin testiemolevyillä BCM91250A ja BCM91480B on ladattava SiByl-" +"käynnistyslatain TFTP:llä, se sitten lataa ja käynnistää Debianin asentimen. " +"Useimmissa tapauksissa noudetaan ensin IP-osoite DHCP:llä mutta on " +"mahdollista asettaa kiinteä osoite. DHCP otetaan käyttöön seuraavalla CFE-" +"kehotteeseen kirjoitettavalla komennolla:\n" +"ifconfig eth0 -auto\n" +" Kun IP-osoite on saatu, ladataan SiByl tällä " +"komennolla: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" Komennossa oleva IP-osoite on korvattava TFTP-" +"palvelimen nimellä tai IP-osoitteella. Tämän komennon jälkeen asennin " +"ladataan automaattisesti." + +#. Tag: title +#: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "Käynnistysparametrit" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" +"SGI:n koneilla voidaan käynnistysparametreja lisätä komentotulkissa " +"bootp():-komennon loppuun." -#~ msgid "" -#~ "Check if DMA is currently enabled: \n" -#~ "$ cd /proc/ide/hdc\n" -#~ "$ grep using_dma settings\n" -#~ "using_dma 1 0 1 rw\n" -#~ " A 1 in the first column after " -#~ "using_dma means it is enabled. If it is, try disabling " -#~ "it: \n" -#~ "$ echo -n \"using_dma:0\" >settings\n" -#~ " Make sure that you are in the directory for " -#~ "the device that corresponds to your CD-ROM drive." -#~ msgstr "" -#~ "Tarkista onko DMA päällä: \n" -#~ "$ cd /proc/ide/hdc\n" -#~ "$ grep dma settings\n" -#~ "using_dma 1 0 1 rw\n" -#~ " 1 ensimmäisessä sarakkeessa " -#~ "using_dma:n jälkeen tarkoittaa sen olevan päällä. Jos " -#~ "se on, kokeile sen ottamista pois käytöstä: \n" -#~ "$ echo -n \"using_dma:0\" >settings\n" -#~ " Varmistu, että ollaan romppuasemaa vastaavan " -#~ "laitteen hakemistossa." +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" +"Following the bootp(): 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: \n" +"bootp():/boot/tftpboot.img\n" +" Further kernel parameters can be passed via " +"append:" +msgstr "" +"bootp():-komennon jälkeen voidaan kirjoittaa " +"käynnistettävän tiedoston polkunimi, jos bootp/dhcp-palvelin ei nimeä " +"antanut. Esimerkki:\n" +"bootp():/boot/tftpboot.img\n" +" Ytimelle voi antaa lisää parametreja " +"append:n avulla:" + +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "bootp(): append=\"root=/dev/sda1\"" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the /boot/sibyl.conf file on the TFTP " +"server and add your parameters to the extra_args " +"variable." +msgstr "" +"CFE-kehotteessa ei voi suoraan antaa käynnistysparametreja. On muokattava " +"tiedostoa /boot/sibyl.conf TFTP-palvelimella ja " +"lisättävä parametrit muuttujaan extra_args." + +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "Cobaltin käynnistys TFTP:llä" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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 "" +"Tarkkaan ottaen Cobalt ei käytä TFTP:tä vaan NFS:ää. On asennettava NFS-" +"palvelin ja tallennettava asentimen tiedostot hakemistoon /" +"nfsroot. Cobaltia käynnistettäessä on painettava oikeaa ja " +"vasenta kohdistinnäppäintä samaan ajkaa jolloin laite käynnistyy verkosta " +"NFS:llä. Sitten ruudulla näkyy useita valintoja. Asennustapoja on seuraavat " +"kaksi:" + +#. Tag: para +#: boot-installer.xml:2170 +#, 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 "" +"SSH:lla (oletus): tässä tapauksessa asennin tekee verkkoasetukset DHCP:llä " +"ja käynnistää SSH-palvelimen. Se näyttää sitten satunnaisen salasanan ja " +"muuta kirjautumistietoa (kuten IP-osoitteen) Cobaltin LCD-näytöllä. Kun " +"laitteeseen kirjaudutaan SSH:lla voidaan asennus aloittaa." + +#. Tag: para +#: boot-installer.xml:2179 +#, 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 "" +"Sarjapäätteellä: Käytä nollamodeemikaapelia Cobaltin sarjaportissa (käytä " +"115200 bittiä sekunnissa) ja tee asennus tällä tavoin. Tämä ei ole " +"mahdollista Qube 2700 (Qube1) -koneilla, koska niissä ei ole sarjaporttia." -#~ msgid "" -#~ "If there are any problems during the installation, try checking the " -#~ "integrity of the CD-ROM using the option near the bottom of the " -#~ "installer's main menu. This option can also be used as a general test if " -#~ "the CD-ROM can be read reliably." -#~ msgstr "" -#~ "Jos asennuksen aikana ilmenee pulmia, yritä tarkistaa onko romppu " -#~ "kunnollinen lähellä asentimen päävalikon alariviä olevalla toiminnolla. " -#~ "Tätä toimintoa voidaan käyttää myös yleistestinä, jolla nähdään saadaanko " -#~ "romppu luettua luotettavasti." +#. Tag: para +#: boot-installer.xml:2222 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"/nfsroot/default.colo file on the NFS server and add " +"your parameters to the args variable." +msgstr "" +"Käynnistysparametreja ei voi antaa suoraan. On muokattava tiedostoa " +"/nfsroot/default.colo NFS-palvelimella ja lisättävä " +"parametrit muuttujaan args." + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "s390:n rajoitukset" + +#. Tag: para +#: boot-installer.xml:2251 +#, no-c-format +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" +"Jotta asennusjärjestelmää voitaisiin käyttää S/390:lla, on oltava toimivat " +"verkkoasetukset ja ssh-istunto." -#~ msgid "Floppy Disk Reliability" -#~ msgstr "Levykkeen luotettavuus" +#. Tag: para +#: boot-installer.xml:2256 +#, 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 an ssh session which will launch the standard installation " +"system." +msgstr "" +"Käynnistysprosessi alkaa verkkoasetuksilla, tulee kehote useista verkon " +"asetuksista. Jos asetukset onnistuvat, kirjaudutaan järjestelmään " +"käynnistämällä ssh-istunto, joka käynnistää tavanomaisen asennusjärjestelmän." + +#. Tag: title +#: boot-installer.xml:2267 +#, no-c-format +msgid "s390 Boot Parameters" +msgstr "s390:n käynnistysparametrit" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more " +"information about S/390-specific boot parameters." +msgstr "" +"S/390:lla käynnistysparametrit voidaan lisätä parm-tiedostoon. Tiedostossa " +"voi käyttää joko ACSII- tai EBCDIC-merkkejä. Lue Device Drivers and Installation Commands-ohjeesta " +"lisätietoja S/390:n käynnistysparametreista." + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, " +"Option, Shift, and Delete " +"keys together while booting to boot from the CD-ROM." +msgstr "" +"Tällä hetkellä ainoat suoritinperheen &arch-title; suoritinarkkitehturit " +"jotka tukevat rompulta käynnistämistä ovat PReP ja New World PowerMacit. " +"PowerMaceilla pidä pohjassa näppäintä c, tai näppäimiä " +"Command, Option, Shift, " +"ja Delete käynnistyksen aikana jotta käynnistys tapahtuu " +"rompulta." + +#. Tag: para +#: boot-installer.xml:2331 +#, 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 "" +"OldWorld PowerMacit eivät käynnisty Debian-rompulta, koska OldWorld-" +"tietokoneissa on Mac OS ROM CD -latausajurin oltava rompulla, eikä tästä " +"ajurista ole saatavilla vapaata versiota. Kaikissa OldWorld-koneissa on " +"levykeasema, joten käynnistä asennin levykkeeltä ja pistä sitten asennin " +"noutamaan tarvittavat tiedostot rompulta." + +#. Tag: para +#: boot-installer.xml:2340 +#, 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 for booting from the hard disk, except use the " +"path to yaboot on the CD at the OF prompt, such as" +msgstr "" +"Jos tietokone ei käynnisty suoraan rompulta, on silti mahdollista käyttää " +"romppua asennuksessa. NewWorld-koneilla voidaan myös OpenFirmwaren " +"komennolla tehdä käynnistys rompulta. Seuraa kohdan ohjeita kiintolevyltä käynnistämiseen, paitsi että OF:n " +"kehotteessa käytetään polkua komentoon yaboot rompulla, " +"kuten tässä" + +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "0 > boot cd:,\\install\\yaboot" + +#. Tag: title +#: boot-installer.xml:2355 +#, no-c-format +msgid "Booting from Hard Disk" +msgstr "Käynnistys kiintolevyltä" + +#. Tag: title +#: boot-installer.xml:2376 +#, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "CHRP:n käynnistys OpenFirmwaresta" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "Tätä ei ole vielä kirjoitettu." + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "OldWorld PowerMacien käynnistäminen MacOS:stä" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"If you set up BootX in , you can use it to " +"boot into the installation system. Double click the BootX " +"application icon. Click on the Options button and " +"select Use Specified RAM Disk. This will give you the " +"chance to select the ramdisk.image.gz file. You may " +"need to select the No Video Driver checkbox, depending " +"on your hardware. Then click the Linux button to shut " +"down MacOS and launch the installer." +msgstr "" +"Jos BootX otettiin käyttöön kohdassa , " +"voidaan sitä käyttää asennusjärjestelmän käynnistämiseen. Kaksoisnapsauta " +"sovelluksen BootX kuvaketta. Napsauta painiketta " +"Options ja valitse Use Specified RAM Disk. Tällöin pääsee valitsemaan tiedoston ramdisk.image.gz. Tietokoneen ominaisuudet saattavat vaatia valintaruudun " +"No Video Driver merkitsemistä. Sammuta sitten MacOS " +"painikkeella Linux, se käynnistää asentimen." + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "NewWorld Macien käynnistäminen OpenFirmwaresta" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" +"You will have already placed the vmlinux, " +"initrd.gz, yaboot, and " +"yaboot.conf files at the root level of your HFS " +"partition in . Restart the computer, and " +"immediately (during the chime) hold down the Option, " +"Command (cloverleaf/Apple), o, and " +"f keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"\n" +"0 > boot hd:x,yaboot\n" +" replacing x 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 " +"ide0: instead of hd:. In a few " +"more seconds you will see a yaboot prompt \n" +"boot:\n" +" At yaboot's boot: prompt, type " +"either install or install video=ofonly followed by a &enterkey;. The video=ofonly " +"argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" +"Tiedostot vmlinux, initrd.gz, " +"yaboot, ja yaboot.conf on " +"tallennettu paikoilleen HFS-osion juureen jo kohdassa . Käynnistä tietokone uudelleen, ja pidä heti (heläyksen aikana) " +"pohjassa näppäimiä Option, Command (neliapila/Apple)" +", o, ja f samaan aikaan. Muutaman " +"sekunnin päästä näkyy Open Firmwaren kehote. Kirjoita kehotteeseen " +"\n" +"0 > boot hd:x,yaboot\n" +" korvaten x sen HFS-" +"osion numerolla, johon ydin ja yabootin tiedoston tallennettiin. Paina rivin " +"lopuksi &enterkey;. Joillakin koneilla on kirjoitettava ide0: eikä hd:. Kuluu muutama sekunti lisää, ja " +"näkyy yabootin kehote:\n" +"boot:\n" +" Yabootin boot:-kehotteessa " +"kirjoitetaan joko install tai install " +"video=ofonly, ja painetaan &enterkey;. Parametrilla " +"video=ofonly saadaan suurin mahdollinen " +"yhteensopivuus; käytä sitä jos install ei toimi. " +"Seuraavaksi pitäisi Debianin asentimen käynnistyä." + +#. Tag: title +#: boot-installer.xml:2440 +#, no-c-format +msgid "Booting from USB memory stick" +msgstr "Käynnistys USB-muistilta" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" +"Tämänhetkisen tiedon mukaan NewWorld PowerMacit tukevat käynnistystä USB-" +"muistilta." -#~ msgid "" -#~ "The biggest problem for people using floppy disks to install Debian seems " -#~ "to be floppy disk reliability." -#~ msgstr "" -#~ "Levykkeeltä Debianin asentavilla näyttäisi suurin ongelma olevan " -#~ "levykkeiden luotettavuus." +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "" +"Make sure you have prepared everything from . 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 " +"Command Option o f all together while booting (see )." +msgstr "" +"Varmistu, että kaikki kohdan valmistelut " +"on tehty. Macintoshin käynnistämiseksi USB-muistilta on käytettävä Open " +"Firmwaren kehotetta, koska Open Firmwaren oletusarvo on, ettei USB-" +"muistilaitteita etsitä. Kehotteen saa näkyviin pitämällä pohjassa näppäimiä " +"Command Option o f samaan aikaan kun kone käynnistyy " +"(katso )." + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment ofpath cannot work that out " +"automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " +"/pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" +"On selvitettävä mihin kohtaan laitepuuta USB-muistilaitteet ilmaantuvat, " +"koska tällä hetkellä ofpath ei osaa löytää niitä " +"automaattisesti. Open Firmwaren kehotteessa saa komennoilla dev / " +"ls ja devalias luettelon kaikista " +"tunnetuista laitteista ja laitteiden toisista nimistä. Tekijän " +"laitteistossa, jossa on erilaisia USB-muisteja, toimivat seuraavan kaltaiset " +"polkunimet: usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, ja /" +"pci@f2000000/usb@1b,1/hub@1/disk@1" + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" +"Having worked out the device path, use a command like this to boot the " +"installer: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" The 2 matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the ,\\\\:tbxi part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"yaboot) in the directory previously blessed with " +"hattrib -b." +msgstr "" +"Kun USB-muistin kohta laitepuussa on selvinnyt, käynnistä asennin " +"tämäntapaisella komennolla: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" 2 tarkoittaa " +"Apple_HFS- tai Apple_Bootstrap-osiota johon käynnistys otos aiemmin " +"kopioitiin, ja ,\\\\:tbxi saa Open Firmwaren " +"käynnistämään tiedoston jonka HFS-tiedostotyyppi on \"tbxi\" (ts. " +"yaboot) hakemistossa johon aiemmin kohdistettiin komento " +"hattrib -b." + +#. Tag: para +#: boot-installer.xml:2485 +#, no-c-format +msgid "" +"The system should now boot up, and you should be presented with the " +"boot: prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." +msgstr "" +"Järjestelmän pitäisi nyt käynnistyä, ja näkyviin tulla kehote boot:. Tässä voidaan kirjoittaa valinnaisia käynnistysparametreja tai " +"painaa vaan &enterkey;." -#~ 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 "" -#~ "Käynnistyslevykkeen kanssa on eniten vaikeuksia, koska laitteisto lukee " -#~ "sitä suoraan ennen kuin Linux käynnistyy. Usein laitteisto ei lue yhtä " -#~ "luotettavasti kuin Linuxin levykeajuri, ja saattaa yksinkertaisesti " -#~ "lopettaa antamatta virheilmoitusta jos tulee lukuvirheitä. Myöskin " -#~ "ajurilevykkeiden kanssa voi tulla vikoja, joista useimmat ilmenevät " -#~ "syöttöä ja tulostusta koskevien virheilmoitusten tulvana." +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" +"Tämä käynnistystapa on uutuus, ja voi olla vaikea saada toimimaan joissakin " +"NewWorld-koneissa. Jos pulmia ilmenee, ole hyvä ja tee asennusraportti. " +"Asennusraportin teko selitetään kohdassa ." + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "" +"Tällä hetkellä PReP ja New World PowerMacit tukevat käynnistystä verkosta." -#~ msgid "" -#~ "If you are having the installation stall at a particular floppy, the " -#~ "first thing you should do is write the image to a different floppy and see if that solves the problem. 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 "" -#~ "Jos asennus jumittuu jonkin tietyn levykkeen kohdalla, kannattaa " -#~ "ensimmäiseksi yrittää sen kirjoittamista toiselle " -#~ "levykkeelle, tämä ehkä poistaa vian. Vanhan levykkeen alustus uudelleen " -#~ "ei ehkä riitä, vaikka levykeen alustus ja kirjoitus näyttäisi sujuvan " -#~ "virheittä. Joskus kannattaa levyke kirjoittaa toisella koneella." +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see ) and use the command " +"boot enet:0. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try boot " +"server_ipaddr,file," +"client_ipaddr." +msgstr "" +"Koneilla joissa on Open Firmware, kuten NewWorld Power Macit, mene boot " +"monitoriin (katso ) ja kirjoita " +"komento boot enet:0. PReP- ja CHRP-koneissa voi olla " +"erilaisia tapoja verkon nimeämiseen. PReP-koneella olisi kokeiltava " +"boot palvelimen_ip-osoite," +"tiedosto,asiakaskoneen_ip-osoite." + +#. Tag: para +#: boot-installer.xml:2543 +#, 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 "" +"Käynnistäminen levykkeiltä on tuettu suoritinperheellä &arch-title;, " +"vaikkakin se yleensä soveltuu vain OldWorld-koneille. NewWorld-koneissa ei " +"ole levykeasemaa, ja koneeseen liitetyltä USB-levykeasemalta käynnistystä ei " +"ole tuettu." + +#. Tag: para +#: boot-installer.xml:2555 +#, no-c-format +msgid "" +"To boot from the boot-floppy-hfs.img floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." +msgstr "" +"Levykkeeltä boot-floppy-hfs.img käynnistetään " +"asettamalla se levykeasemaan kun laite on sammutettu, ja painamalla sitten " +"virtanappulaa." -#~ msgid "" -#~ "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " -#~ "third floppy." -#~ msgstr "" -#~ "Eräs käyttäjä ilmoittaa, että hänen piti kirjoittaa otos levykkeelle " -#~ "kolme kertaa ennen kuin yksi levyke vihdoin toimi." +#. Tag: para +#: boot-installer.xml:2561 +#, 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 "" +"Niille joille Macintoshin levyketoiminnot eivät ole tuttuja: ennen " +"käynnistystä koneeseen asetettu levyke on se josta laitteisto ensimmäiseksi " +"käynnistyy. Jos levykkeellä ei ole kunnollista käynnistystiedostoa, se " +"poistetaan asemasta ja laite etsii käynnistyskelpoisia osioita kiintolevyltä." + +#. Tag: para +#: boot-installer.xml:2568 +#, no-c-format +msgid "" +"After booting, the root.bin 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 "" +"Käynnistyksen jälkeen pyydetään levykettä root.bin. " +"Aseta levyke asemaan ja paina &enterkey;. Asennusohjelma käynnistyy " +"automaattisesti kun juuritiedostojärjestelmä on ladattu muistiin." + +#. Tag: title +#: boot-installer.xml:2579 +#, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "PowerPC:n käynnistysparametrit" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 " +"video=atyfb:vmode:6 , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"video=aty128fb:vmode:6 ." +msgstr "" +"Useat vanhat Applen näytöt käyttivät 640x480 67Hz -toimintatilaa. Jos kuva " +"on vinksallaan vanhassa Applen näytössä, kokeile lisätä käynnistysparametri " +"video=atyfb:vmode:6, joka valitsee tuon toimintatilan " +"useimmissa Mach64- ja Rage-näytönohjaimissa. Jos näytönohjain on Rage 128, " +"käytä video=aty128fb:vmode:6." + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see ). Use " +"the command boot net to boot from a TFTP and RARP " +"server, or try boot net:bootp or boot net:" +"dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " +"OpenBoot revisions require using the device name, such as boot le" +"(); these probably don't support BOOTP nor DHCP." +msgstr "" +"Koneissa joissa on OpenBoot, riittää käynnistää asennettavan koneen boot " +"monitor (katso ). Komennolla " +"boot net käynnistetään TFTP- tai RARP-palvelimelta. " +"Komennolla boot net:bootp tai boot net:" +"dhcp käynnistetään TFTP- ja BOOTP- tai DHCP-palvelimelta. " +"Joissakin vanhoissa OpenBootin versioissa on käytettävä laitenimeä, kuten " +"boot le(); nämä eivät luultavasti tue BOOTP:tä eikä " +"DHCP:tä." + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "" +"Most OpenBoot versions support the boot cdrom 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 "" +"Useimmat OpenBootin versiot tukevat komentoa boot cdrom, joka on vain toinen nimi käynnistykselle SCSI-laitteelta jonka " +"ID on 6 (tai toissijaisen IDE-liitännän isäntälevyltä IDE-levyjä käyttävässä " +"koneessa). Vanhoissa OpenBootin versiossa voi joutua käyttämään varsinaista " +"laitenimeä, koska ne eivät tue tätä erikoiskomentoa. Huomaa, että on " +"ilmoitettu ongelmista sun4m-koneilla (esim. Sparc 10 ja Sparc 20) rompulta " +"käynnistettäessä." + +#. Tag: para +#: boot-installer.xml:2691 +#, no-c-format +msgid "" +"To boot from floppy on a Sparc, use \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"Bad magic number in disk label - Can't open disk label " +"package. 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 "" +"Sparc käynnistetään levykkeeltä komentamalla\n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Varoitamme, että uusi sun4u-suoritinperhe " +"(ultra) ei tue levykkeeltä käynnistämistä. Tavallinen virheilmoitus on " +"Bad magic number in disk label - Can't open disk label " +"package. Lisäksi jotkin sun4c-mallit (kuten IPX) eivät tue " +"pakattuja otoksia joita levykkeillä käytetään, eli myöskään sun4c ei ole " +"tuettu." + +#. Tag: para +#: boot-installer.xml:2703 +#, 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 ." +msgstr "" +"Useissa Sparceissa (esim. Ultra 10) on OBP-vika, joka estää niitä " +"käynnistymästä (vaikka käynnistäminen on tuettu). Sopiva OBP-päivitys " +"voidaan noutaa tuotenumerona ID 106121 osoitteesta ." + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"If you are booting from the floppy, and you see messages such as " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" then it is possible that floppy booting is " +"simply not supported on your machine." +msgstr "" +"Mikäli levykkeeltä käynnistettäessä näkyy viestejä kuten " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" on mahdollista, että levykkeeltä käynnistämistä " +"ei lainkaan tueta tällä koneella." + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "IDPRO:min viestit" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"IDPROM, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"Sun NVRAM FAQ for more " +"information." +msgstr "" +"Jos käynnistäminen ei onnistu, ja vikailmoitukset koskevat IDPROM:ia, on mahdollista etä NVRAM:in paristo on tyhjentynyt. NVRAM:iin " +"tallennetaan laitteiston asetukset. Katso lisätietoja osoitteesta Sun NVRAM FAQ." + +#. Tag: para +#: boot-installer.xml:2742 +#, 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 "" +"Käynnistysparametrit ovat Linuxin ytimen parametreja, joilla varmistetaan " +"oheislaitteita käytettävän asianmukaisesti. Enimmäkseen ydin osaa tunnistaa " +"oheislaitteiden tiedot automaattisesti. Joissain tapauksissa on ydintä " +"kuitenkin hieman autettava." + +#. Tag: para +#: boot-installer.xml:2749 +#, 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 "" +"Jos järjestelmän käynnistämistä yritetään ensimmäistä kertaa, kokeile " +"käynnistysparametrien oletusarvoja (eli älä anna mitään parametreja) ja " +"katso toimiiko kaikki oikein. Luultavasti toimii. Jos ei toimi, voidaan " +"myöhemmin käynnistää uudestaan ja etsiä erikoisparametreja jotka kertovat " +"järjestelmälle laitteistosta." + +#. Tag: para +#: boot-installer.xml:2756 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +" Linux " +"BootPrompt HOWTO:sta löytyy tietoa monista käynnistysparametreista, " +"mukaan lukien vinkkejä epämääräisille laitteille. Tämä luku on vain luonnos " +"tärkeimmistä parametreista. Joitakin yleisiä kompastuskiviä on selitetty " +"kohdassa ." + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" +"When the kernel boots, a message \n" +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total 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 mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" +"Kun ydin käynnistyy, viestin \n" +"Memory:availk/totalk " +"available\n" +" pitäisi näkyä kohtalaisen alussa. " +"total pitäisi olla koneen kaiken keskusmuistin " +"määrä kilotavuissa. Jos tämä ei vastaa koneeseen asennettua muistia, on " +"käytettävä parametria mem=ram, missä ram on muistin määrä. Yksikkö " +"ilmoitetaan kirjaimella k kilotavuille ja m:" +"llä megatavuille. Esimerkiksi sekä mem=65536k että " +"mem=64m tarkoittavat 64 Mt keskusmuistia." + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this (although not on DECstations). 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 console=device " +"argument to the kernel, where device is your " +"serial device, which is usually something like ttyS0." +msgstr "" +"Käytettäessä käynnistyksessä sarjapäätettä, osaa ydin yleensä havaita tämän " +"automaattisesti (tosin DECstationeilla ei havaita). Jos myös näytönohjain (framebuffer) ja näppäimistö ovat kiinni " +"sarjapäätettä käyttäen käynnistettävässä tietokoneessa, pitää ehkä antaa " +"ytimelle parametri console=laite, missä laite on sarjaportti, joka " +"yleensä on suunnilleen ttyS0." + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"Suoritinperheellä &arch-title; sarjaporttien laitenimet ovat ttya tai ttyb. Toinen tapa antaa OpenPROM:n " +"muuttujille input-device ja output-device " +"arvoksi ttya." + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "Debianin asentimen parametrit" + +#. Tag: para +#: boot-installer.xml:2806 +#, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"Asennusjärjestelmä tunnistää muutamia lisäparametreja " +"Nykyisillä ytimillä (versio 2.6.9 tai uudempi) voidaan käyttää 32:ta " +"komentorivin parametriä ja 32:ta ympäristömuuttujaa. Jos nämä rajat " +"ylitetään, tapahtuu kernel panic. , jotka voivat olla " +"hyödyllisiä." + +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "debconf/priority" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"Tämä parametri määrää, kuinka alhaisen prioriteetin viestit näytetään. Lyhyt " +"muoto: priority" -#~ msgid "" -#~ "Normally you should not have to download a floppy image again, but if you " -#~ "are experiencing problems it is always useful to verify that the images " -#~ "were downloaded correctly by verifying their md5sums." -#~ msgstr "" -#~ "Tavallisesti ei tarvitse noutaa levykeotoksia uudelleen, mutta jos pulmia " -#~ "ilmenee on aina hyödyllistä tarkistaa, että levykkeet noudettiin oikein " -#~ "tarkistamalla niiden md5sum-tarkistussummat." +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "" +"The default installation uses priority=high. 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 "" +"Oletusasennus käyttää asetusta priority=high. Tämä " +"tarkoittaa, että näytetään viestit, joiden prioriteetti on korkea tai " +"kriittinen, mutta prioriteetin keskitaso ja matala viestit ohitetaan. Jos " +"tulee pulmia, asennin säätää prioriteettia tarpeen mukaan." + +#. Tag: para +#: boot-installer.xml:2836 +#, no-c-format +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"Jos käynnistysparametriksi lisätään priority=medium, " +"näytetään asennusvalikko ja pystytään tarkemmin säätämään asennusta. Kun " +"käytetään priority=low, näytetään kaikki viestit " +"(tämä on sama kuin käynnistystapa expert). Kun asetus " +"on priority=critical, asennusjärjestelmä näyttää vain " +"kriittiset viestit ja yrittää tehdä oikeat valinnat kyselemättä turhia." + +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "DEBIAN_FRONTEND" + +#. Tag: para +#: boot-installer.xml:2851 +#, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " +" The default frontend is " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text may be preferable for serial " +"console installs. Generally only the newt frontend is " +"available on default install media. On architectures which support it, the " +"graphical installer uses the gtk frontend." +msgstr "" +"Tämä parametri määrää asentimen käyttämän käyttöliittymän tyypin. Tällä " +"hetkellä ovat mahdollisia parametrin arvot: " +"DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +" DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk Käyttöliittymän oletusarvo on " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text saattaa olla parempi " +"sarjapäättellä tehtäville asennuksille. Yleensä vain newt on saatavilla oletusasennustaltioilla, joten tämä asetus ei ole " +"järin hyödyllinen juuri nyt. Graafista asenninta tukevilla suoritinperheillä " +"graafinen asennin käyttää gtk-käyttöliittymää." + +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "BOOT_DEBUG" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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 "" +"Asettamalla tämän käynnistysparametrin arvoksi 2 asentimen " +"käynnistysprosessi tekee yksityiskohtaisen lokin. Arvolla 3 ovat " +"vianjäljitykseen tarkoitetut komentotulkit käytössä asennusprosessin " +"tärkeissä vaiheissa. (Käynnistystä jatketaan poistumalla komentotulkista.)" + +#. Tag: userinput +#: boot-installer.xml:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "BOOT_DEBUG=0" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "Tämä on oletusarvo" + +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "BOOT_DEBUG=1" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "Tavallista yksityiskohtaisempi." + +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "BOOT_DEBUG=2" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "Paljon vianjäljitystietoa." + +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "BOOT_DEBUG=3" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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 "" +"Käynnistysprosessin valikoiduissa kohdissa käynnistetään komentotulkki. " +"Jatka käynnistystä poistumalla komentotulkista." + +#. Tag: term +#: boot-installer.xml:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "INSTALL_MEDIA_DEV" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"Tämän parametrin arvo on sen laitteen polkunimi, josta Debianin asennin " +"ladataan. Esimerkiksi INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ 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 "" -#~ "Toiset käyttäjät ovat ilmoittaneet, että vain käynnistämällä muutaman " -#~ "kerran sama levyke asemassa saattaa käynnistys vihdoin onnistua. Kaikki " -#~ "tämä johtuu viallisista laitteista tai laiteohjelmiston levykeajureista." +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." +msgstr "" +"Normaalisti käynnistyslevyke etsii root-levykettä kaikista levykeasemista. " +"Tällä parametrilla saadaan etsintä kohdistumaan vain yhteen nimettyyn " +"laitteeseen." + +#. Tag: term +#: boot-installer.xml:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "debian-installer/framebuffer" + +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/" +"framebuffer=false, or fb=false for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." +msgstr "" +"Joissakin suoritinperheissä käytetään ruutupuskuria (framebuffer), jotta " +"asennus olisi saatavilla useilla kielillä. Jos ruutupuskuri aiheuttaa " +"pulmia, se voidaan ottaa pois käytöstä parametrilla debian-" +"installer/framebuffer=false, tai lyhyemmällä muodolla " +"fb=false. Pulman oireita ovat virheilmoitukset " +"btermistä tai bogl:stä, tyhjä ruutu tai jumittuminen muutaman minuutin " +"sisällä asennuksen alusta." + +#. Tag: para +#: boot-installer.xml:2948 +#, no-c-format +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"Myöskin parametrilla video=vga16:off saadaan ydin " +"jättämään ruutupuskuri käyttämättä. Pulmista on ilmoitettu Dell " +"Inspironeilla joissa on näytönohjaimena Mobile Radeon." + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "Pulmista on ilmoitettu Amiga 1200:lla ja SE/30:llä." + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "Pulmista on ilmoitettu hppa:lla." + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"disabled by default 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 debian-installer/" +"framebuffer=true or fb=true for short." +msgstr "" +"Joillakin järjestelmillä ilmenneiden näyttöpulmien vuoksi on ruutupuskkuri " +"oletusarvona pois käytöstä suoritinperheellä &arch-" +"title;. Tästä voi olla seurauksena ruma ruutu laitteissa jotka tukisivat " +"ruutupuskuria kunnolla, kuten ATI:n näytönohjainta käyttävät mallit. Jos " +"asentimessa näkyy näyttöpulmia, voidaan kokeilla käynnistämistä parametrilla " +"debian-installer/framebuffer=true tai lyhyemmin " +"fb=true." + +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a dark theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter debian-installer/theme=dark or theme=dark." +msgstr "" +"Teema määrää asentimen käyttöliittymän ulkonäön (värit, kuvakkeet, jne.). " +"Saatavilla olevat teemat ovat käyttöliittymäkohtaisia. Tällä hetkellä vain " +"käyttöliittymillä newt ja gtk on teema dark, joka " +"suunniteltiin näkövammaisille. Aseta teema käynnistämällä parametrilla " +"debian-installer/theme=dark tai theme=dark." + +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "debian-installer/probe/usb" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "" +"Asettamalla arvoksi false ei USB-laitteita tutkita " +"käynnistyksessä, eli vältytään USB-pulmilta." + +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "netcfg/disable_dhcp" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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 "" +"Oletusarvona &d-i; yrittää automaattisesti noutaa verkkoasetukset DHCP:llä. " +"Jos tämä onnistuu, ei saatuja asetuksia pääse näkemään ja muuttamaan. " +"Verkkoasetukset pääsee tekemään itse vain jos DHCP epäonnistuu." -#~ msgid "Boot Configuration" -#~ msgstr "Käynnistysasetukset" +#. Tag: para +#: boot-installer.xml:3008 +#, 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 " +"netcfg/disable_dhcp=true to prevent configuring the " +"network with DHCP and to enter the information manually." +msgstr "" +"Mikäli paikallisverkossa on DHCP-palvelin, mutta sen käyttöä halutaan " +"välttää, esimerkiksi koska sen antamat verkkoasetukset ovat väärin, voidaan " +"käyttää parametria netcfg/disable_dhcp=true. Tämä " +"estää verkkoasetusten noutamisen DHCP:llä ja tiedot voi kirjoittaa itse." + +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "hw-detect/start_pcmcia" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"Mikäli PCMCIA-palvelut aiheuttavat pulmia, aseta tämä arvoon " +"false. Tämä on tunnetusti tarpeen jollakin " +"läppäreillä." + +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "preseed/url" + +#. Tag: para +#: boot-installer.xml:3031 +#, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url." +msgstr "" +"Anna url noudettavaan valmiiden vastausten tiedostoon. Tiedosto noudetaan " +"käytettäessä automaattista asennusta. Katso . Lyhyt muoto: url" + +#. Tag: term +#: boot-installer.xml:3041 +#, no-c-format +msgid "preseed/file" +msgstr "preseed/file" + +#. Tag: para +#: boot-installer.xml:3042 +#, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file." +msgstr "" +"Anna valmiiden vastausten tiedoston polkunimi. Tiedosto noudetaan " +"käytettäessä automaattista asennusta. Katso . Lyhyt muoto: tiedosto" + +#. Tag: term +#: boot-installer.xml:3052 +#, no-c-format +msgid "auto-install/enabled" +msgstr "auto-install/enabled" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" +"Viivästä, jos mahdollista, normaalisti ennen valmiita vastauksia kysyttäviä " +"kysymyksiä, kunnes verkon asetukset on tehty. Lyhyt muoto: " +"auto=true. Katso kohdasta yksityiskohtaisempia ohjeita tämän hyödyntämisestä asennuksen " +"automatisoinnissa." + +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "cdrom-detect/eject" + +#. Tag: para +#: boot-installer.xml:3065 +#, 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 "" +"Oletusarvona &d-i; poistaa automaattisesti asennuksessa käytetyn rompun " +"asemasta ennen uudelleenkäynnistystä. Tämä saattaa olla tarpeetonta, jos " +"tietokone ei automaattisesti käynnisty rompulta. Joissakin tapauksissa se " +"voi olla jopa ei-toivottavaa, esimerkiksi jos romppuasema ei osaa vetää " +"romppua takaisin sisään eikä käyttäjä ole paikalla työntämässä sitä asemaan. " +"Monet kelkattomat, ohuet ja caddyä käyttävät romppuasemat eivät osaa ladata " +"romppua asemaan automaattisesti." + +#. Tag: para +#: boot-installer.xml:3074 +#, no-c-format +msgid "" +"Set to false 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 "" +"Automaattinen rompun poisto asemasta estetään asettamalla arvoksi " +"false, ja huomaa, että joutunet varmistamaan ettei " +"kone käynnisty automaattisesti romppuasemalta asennuksen ensimmäisen vaiheen " +"jälkeen." + +#. Tag: term +#: boot-installer.xml:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "ramdisk_size" + +#. Tag: para +#: boot-installer.xml:3086 +#, no-c-format +msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgstr "" +"Jos käytetään ytimen versiota 2.2.x, saattaa olla tarpeen asettaa " +"&ramdisksize;." + +#. Tag: term +#: boot-installer.xml:3094 +#, no-c-format +msgid "mouse/left" +msgstr "mouse/left" + +#. Tag: para +#: boot-installer.xml:3095 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to true." +msgstr "" +"Gtk-käyttöliittymään (graafinen asennin) voidaan hiiri vaihtaa " +"vasenkätiseksi asettamalla tämän parametrin arvoksi true." + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "directfb/hw-accel" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"true when booting the installer." +msgstr "" +"Gtk-käyttöliittymässä (graafinen asennin) on directfb:n laitteistokiihdytys " +"oletusarvona pois päältä. Sen saa päälle asettamalla tämän parametrin " +"arvoksi true asenninta käynnistettäessä." + +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "rescue/enable" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"Asettamalla arvoksi true käynnistetään pelastustila " +"eikä tavallinen asennus. Katso ." + +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "Valmiita vastauksia käynnistysparametreilla" + +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" +"Muutamaa poikkeusta lukuunottamatta käynnistysparametrilla voidaan antaa " +"arvo mihin tahansa asennuksen aikana kysyttävään kysymykseen. Tosin tämä on " +"hyödyllistä vain erikoistapauksissa. Yleisiä ohjeita tämän tekemisestä " +"löytyy kohdasta . Esimerkkejä joistakin " +"tapauksista on seuraavassa luettelossa." + +#. Tag: term +#: boot-installer.xml:3140 +#, no-c-format +msgid "debian-installer/locale" +msgstr "debian-installer/locale" + +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. Short form: " +"locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" +"Voidaan käyttää antamaan asennukselle sekä kieli että maa. Tämä toimii vain " +"jos maa-asetusto on tuettu Debianissa. Lyhyt muoto: locale. Käytä esimerkiksi locale=sv_FI " +"valitsemaan kieleksi ruotsi ja maaksi Suomi." + +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "" +"Set to true if you want to disable DHCP and instead " +"force static network configuration." +msgstr "" +"Aseta arvoksi true, jos DHCP halutaan pois käytöstä " +"ja pakotetaan kiinteät verkkoasetukset." + +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "tasksel:tasksel/first" + +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" +"Voidaan käyttää valitsemaan tehtäviä, jotka eivät ole käytettävissä " +"vuorovaikutteisessa tehtävälistassa, kuten tehtävä kde-desktop. Katso lisätietoja kohdasta . Lyhyt " +"muoto: tasks." + +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "Parametrien välittäminen ytimen moduuleille" + +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" +"Jos ajurit on käännetty mukaan ytimeen, niille voidaan välittää parametreja " +"ytimen ohjeissa kuvatulla tavalla. Jos ajurit kuitenkin on käännetty " +"moduuleina, ja koska moduulit ladataan asennuksen aikana hieman eri tavalla " +"kuin käynnistettäessä asennettua järjestelmää, ei parametreja ole " +"mahdollista välittää tavalliseen tapaan. Sen sijaan on käytettävä asentimen " +"tunnistamaa erikoismerkintää. Asennin varmistaa asetusten tallentuvan " +"oikeisiin asetustiedostoihin ja tulevan sitä kautta käyttöön myös kun " +"moduulit oikeasti ladataan. Parametrit välitetään automaattisesti myös " +"asennetun järjestelmän asetustiedostoihin." + +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" +"Huomaa, että nykyään on harvinaista jos moduuleille on pakko välittää " +"parametreja. Useimmissa tapauksissa ydin osaa tunnistaa järjestelmän " +"laitteiston ja asettaa hyvät oletusarvot. Joissakin tapauksissa saattaa " +"kuitenkin olla välttämätöntä asettaa parametrien arvo itse." + +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" +"Moduulien paremetrit annetaan tässä muodossa: \n" +"moduulin_nimi.parametrin_nimi=arvo\n" +" Jos on annettava useita parametreja samalle tai " +"eri moduuleille, toista vaan yllä olevaa. Esimerkiksi vanha 3Comin " +"verkkokortti asetetaan käyttämään BNC-liitäntää (coax) ja keskeytystä IRQ 10 " +"seuraavasti:" + +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "3c509.xcvr=3 3c509.irq=10" + +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "Asennusprosessin vianetsintä" + +#. Tag: title +#: boot-installer.xml:3226 +#, no-c-format +msgid "CD-ROM Reliability" +msgstr "Romppujen luetettavuus" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" +"Joskus asennin ei käynnisty romppulta. Erityisesti näin voi käydä vanhoilla " +"romppuasemilla. Myöskin voi sattua, että vaikka asennin on käynnistynyt " +"rompulta, se ei tunnista romppuasemaa tai tulee lukuvirheitä asennuksen " +"aikana. " + +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" +"Näihin pulmiin on monia mahdollisia syitä. Tässä luetellaan vain joitakin " +"yleisiä tapauksia ja yleisiä toimintaohjeita. Lopusta saat huolehtia itse." + +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "Ensiksi kannattaa kokeilla kahta hyvin yksinkertaista juttua." + +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" +"Jos romppu ei käynnisty, tarkista että se asetettiin asemaan oikein ja ettei " +"se ole likainen." -#~ 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 ." -#~ msgstr "" -#~ "Jos ilmenee pulmia ja ydin jumittuu käynnistyksen aikana, ei tunnista " -#~ "oheislaitteita joita koneessa oikeasti on, tai asemia ei tunnisteta " -#~ "kunnolla, on ensiksi tarkistettava käynnistysparametrit, kuten kerrotaan " -#~ "kohdassa ." +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" +"Mikäli asennin ei tunnista romppua, yritä käynnistää uudelleen valikosta " +" Detect and mount CD-ROM . Jotkin DMA:han liittyvät jutut vanhoissa romppuasemissa " +"ratkeavat tunnetusti tällä tavalla." + +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" +"Jos tämä ei toimi, kokeile seuraavien alilukujen ehdotuksia. Useimmat, mutta " +"eivät kaikki, ehdotukset kelpaavat sekä CD-ROMille että DVD:lle, mutta " +"käytämme yksinkertaisuuden vuoksi termiä romppu." -#~ msgid "" -#~ "If you are booting with your own kernel instead of the one supplied with " -#~ "the installer, be sure that CONFIG_DEVFS is set in " -#~ "your kernel. The installer requires CONFIG_DEVFS." -#~ msgstr "" -#~ "Jos käynnistetään omalla ytimellä eikä asentimen mukana tulleella, " -#~ "varmista että ytimessäsi on CONFIG_DEVFS päällä. " -#~ "Asennin vaatii CONFIG_DEVFS:n." +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" +"Jos asennus ei onnistu rompulta, kokeile muita saatavilla olevia " +"asennustapoja." + +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "Yleisiä pulmia" + +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" +"Jotkut vanhat romppuasemat eivät tue uusilla kirjoittavilla romppuasemilla " +"suurilla nopeuksilla kirjoitettujen romppujen lukemista." -#~ msgid "" -#~ "Often, problems can be solved by removing add-ons and peripherals, and " -#~ "then trying booting again. Internal modems, sound " -#~ "cards, and Plug-n-Play devices can be especially problematic." -#~ msgstr "" -#~ "Usein pulmat katoavat poistamalla lisälaitekortit ja oheislaitteet, ja " -#~ "yrittämällä käynnistystä uudelleen. Korttimodeemit, " -#~ "äänikortit ja Plug-n-Play-laitteet ovat erityisiä ongelmapesiä." +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" +"Vaikka tietokone käynnistyisikin rompulta ongelmitta, ei se välttämättä " +"tarkoita Linuxin tukevan kyseistä romppuasemaa (tai täsmällisemmin, ohjainta " +"jossa romppuasema on kiinni)." -#~ 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 mem=512m." -#~ msgstr "" -#~ "Jos koneessa on asennettuna paljon muistia, enemmän kuin 512 Mt, ja " -#~ "asennin jumittuu ydintä käynnistettäessä, voi olla tarpeen antaa " -#~ "käynnistysparametri rajoittamaan ytimen näkemän muistin määrää, kuten " -#~ "mem=512m." +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" +"Jotkut vanhat romppuasemat eivät toimi oikein jos direct memory " +"access (DMA) on käytössä." + +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "Miten pulmia tutkitaan ja ehkä selvitetään" + +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "Jos romppu ei käynnisty, kokeile alla lueteltuja ehdotuksia." + +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" +"Tarkista että BIOS oikeasti tukee rompulta käynnistämistä (vanhat koneet " +"luultavasti eivät tue) ja että romppuasema tukee käytettyä taltiota." -#~ msgid "Common &arch-title; Installation Problems" -#~ msgstr "Yleisiä suoritinperheen &arch-title; asennuspulmia" +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" +"Jos noudit ISO-otoksen, tarkista otoksen md5sum-tarkistussumman vastaavan " +"otoksen summaa tiedostossa MD5SUMS. Tiedoston pitäisi " +"olla samassa paikassa kuin noudettu otos. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Seuraavaksi kannattaa tarkistaa, että myöskin " +"poltetun rompun md5sum täsmää. Seuraavan komennon pitäisi toimia. Se käyttää " +"otoksen kokoa lukeakseen oikean määrän tavuja rompulta." + +#. Tag: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" + +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" +"Jos järjestelmä ei havaitse romppua kun asennin on käynnistynyt " +"onnistuneesti, auttaa joskus kun vaan koitetaan uudestaan. Jos romppuasemia " +"on useita, yritä vaihtaa romppu toiseen asemaan. Jos se ei toimi, tai jos " +"romppu tunnistetaan mutta tulee lukuvirheitä, yritä alla lueteltuja " +"ehdotuksia. Tähän tarvitaan perustiedot Linuxista. Komentojen antamiseksi on " +"ensin vaihdettava toiseen virtuaalikonsoliin (VT2) ja käynnistettävä siihen " +"komentotulkki." + +#. Tag: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" +"Vaihtamalla konsoliin VT4 tai lukemalla tiedostoa /var/log/syslog (käytä komentoa nano teksturina) näkee tarkat " +"virheilmoitukset. Tämän jälkeen katso myös komennon dmesg " +"tuloste." + +#. Tag: para +#: boot-installer.xml:3351 +#, no-c-format +msgid "" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using modprobe." +msgstr "" +"Tarkista komennon dmesg tulosteesta tunnistuiko " +"romppuasema. Pitäisi näkyä jotain seuraavan kaltaista (rivit eivät " +"välttämättä ole suoraan peräkkäin): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" Jos tuollaista ei näy, on todennäköistä ettei " +"linux tunnistanut ohjainta jossa romppuasema on kiinni, tai sitä ei ehkä " +"tueta lainkaan. Jos tiedät mikä ajuri ohjeimelle tarvitaan, voit kokeilla " +"sen lataamista itse komennolla modprobe." + +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" +"Tarkista romppuasemalle olevan laitetiedosto hakemistossa /dev/. Alla olevassa esimerkissä se olisi tiedosto /dev/hdc. Pitäisi olla myös /dev/cdroms/cdrom0." -#~ msgid "" -#~ "There are some common installation problems that can be solved or avoided " -#~ "by passing certain boot parameters to the installer." -#~ msgstr "" -#~ "Muutamat yleiset asennuspulmat voidaan selvittää tai välttää antamalla " -#~ "asentimelle sopivia käynnistysparametreja." +#. Tag: para +#: boot-installer.xml:3373 +#, no-c-format +msgid "" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" +"$ mount /dev/hdc /cdrom\n" +" Check if there are any error messages after that " +"command." +msgstr "" +"Tarkista komennolla mount onko romppu jo liitetty; jos ei " +"ole, kokeile sen liittämistä itse: \n" +"$ mount /dev/hdc /cdrom\n" +" Tarkista tuleeko komennon jälkeen " +"virheilmoituksia." + +#. Tag: para +#: boot-installer.xml:3383 +#, no-c-format +msgid "" +"Check if DMA is currently enabled: \n" +"$ cd /proc/ide/hdc\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +" A 1 in the first column after " +"using_dma means it is enabled. If it is, try disabling " +"it: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." +msgstr "" +"Tarkista onko DMA päällä: \n" +"$ cd /proc/ide/hdc\n" +"$ grep dma settings\n" +"using_dma 1 0 1 rw\n" +" 1 ensimmäisessä sarakkeessa " +"using_dma:n jälkeen tarkoittaa sen olevan päällä. Jos se " +"on, kokeile sen ottamista pois käytöstä: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Varmistu, että ollaan romppuasemaa vastaavan " +"laitteen hakemistossa." + +#. Tag: para +#: boot-installer.xml:3398 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" +"Jos asennuksen aikana ilmenee pulmia, yritä tarkistaa onko romppu " +"kunnollinen lähellä asentimen päävalikon alariviä olevalla toiminnolla. Tätä " +"toimintoa voidaan käyttää myös yleistestinä, jolla nähdään saadaanko romppu " +"luettua luotettavasti." + +#. Tag: title +#: boot-installer.xml:3413 +#, no-c-format +msgid "Floppy Disk Reliability" +msgstr "Levykkeen luotettavuus" + +#. Tag: para +#: boot-installer.xml:3415 +#, no-c-format +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"Levykkeeltä Debianin asentavilla näyttäisi suurin ongelma olevan levykkeiden " +"luotettavuus." -#~ msgid "" -#~ "Some systems have floppies with inverted DCLs. If you " -#~ "receive errors reading from the floppy, even when you know the floppy is " -#~ "good, try the parameter floppy=thinkpad." -#~ msgstr "" -#~ "Joissakin tietokoneissa levykeasemassa on inverted DCL. " -#~ "Jos levykkeestä tulee lukuvirheitä, vaikka levyke tiedetään " -#~ "kunnolliseksi, kokeile parametria floppy=thinkpad." +#. Tag: para +#: boot-installer.xml:3420 +#, 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 "" +"Käynnistyslevykkeen kanssa on eniten vaikeuksia, koska laitteisto lukee sitä " +"suoraan ennen kuin Linux käynnistyy. Usein laitteisto ei lue yhtä " +"luotettavasti kuin Linuxin levykeajuri, ja saattaa yksinkertaisesti lopettaa " +"antamatta virheilmoitusta jos tulee lukuvirheitä. Myöskin ajurilevykkeiden " +"kanssa voi tulla vikoja, joista useimmat ilmenevät syöttöä ja tulostusta " +"koskevien virheilmoitusten tulvana." + +#. Tag: para +#: boot-installer.xml:3429 +#, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. 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 "" +"Jos asennus jumittuu jonkin tietyn levykkeen kohdalla, kannattaa " +"ensimmäiseksi yrittää sen kirjoittamista toiselle " +"levykkeelle, tämä ehkä poistaa vian. Vanhan levykkeen alustus uudelleen ei " +"ehkä riitä, vaikka levykeen alustus ja kirjoitus näyttäisi sujuvan " +"virheittä. Joskus kannattaa levyke kirjoittaa toisella koneella." + +#. Tag: para +#: boot-installer.xml:3438 +#, no-c-format +msgid "" +"One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " +"third floppy." +msgstr "" +"Eräs käyttäjä ilmoittaa, että hänen piti kirjoittaa otos levykkeelle " +"kolme kertaa ennen kuin yksi levyke vihdoin toimi." -#~ 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 hd=cylinders,heads,sectors." -#~ msgstr "" -#~ "Joissakin tietokoneissa, kuten IBM PS/1 tai ValuePoint (joissa on ST-506-" -#~ "levyajurit), ei IDE-levyä ehkä tunnisteta oikein. Yritä taas ensin ilman " -#~ "parametreja ja kokeile josko IDE-asema tunnistuu oikein. Jos ei, selvitä " -#~ "levyn geometria (sylinterit, päät ja sektorit) ja käytä parametria " -#~ "hd=sylinterit,päät,sektorit." +#. Tag: para +#: boot-installer.xml:3444 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Tavallisesti ei tarvitse noutaa levykeotoksia uudelleen, mutta jos pulmia " +"ilmenee on aina hyödyllistä tarkistaa, että levykkeet noudettiin oikein " +"tarkistamalla niiden md5sum-tarkistussummat." -#~ msgid "" -#~ "If you have a very old machine, and the kernel hangs after saying " -#~ "Checking 'hlt' instruction..., then you " -#~ "should try the no-hlt boot argument, which " -#~ "disables this test." -#~ msgstr "" -#~ "Jos kone on hyvin vanha, ja ydin jumittuu kun se on tulostanut rivin " -#~ "Checking 'hlt' instruction..., olisi " -#~ "kokeiltava käynnistysparametria no-hlt, joka ottaa " -#~ "tämän testin pois käytöstä." +#. Tag: para +#: boot-installer.xml:3450 +#, 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 "" +"Toiset käyttäjät ovat ilmoittaneet, että vain käynnistämällä muutaman kerran " +"sama levyke asemassa saattaa käynnistys vihdoin onnistua. Kaikki tämä johtuu " +"viallisista laitteista tai laiteohjelmiston levykeajureista." + +#. Tag: title +#: boot-installer.xml:3459 +#, no-c-format +msgid "Boot Configuration" +msgstr "Käynnistysasetukset" + +#. Tag: para +#: boot-installer.xml:3461 +#, 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 " +"." +msgstr "" +"Jos ilmenee pulmia ja ydin jumittuu käynnistyksen aikana, ei tunnista " +"oheislaitteita joita koneessa oikeasti on, tai asemia ei tunnisteta " +"kunnolla, on ensiksi tarkistettava käynnistysparametrit, kuten kerrotaan " +"kohdassa ." + +#. Tag: para +#: boot-installer.xml:3468 +#, no-c-format +msgid "" +"If you are booting with your own kernel instead of the one supplied with the " +"installer, be sure that CONFIG_DEVFS is set in your " +"kernel. The installer requires CONFIG_DEVFS." +msgstr "" +"Jos käynnistetään omalla ytimellä eikä asentimen mukana tulleella, varmista " +"että ytimessäsi on CONFIG_DEVFS päällä. Asennin " +"vaatii CONFIG_DEVFS:n." -#~ 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 fb=false " -#~ "video=vga16:off to disable the framebuffer console. Only the " -#~ "English language will be available during the installation due to limited " -#~ "console features. See for details." -#~ msgstr "" -#~ "Jos näytön kuva on pielessä ytimen käynnistyessä, esimerkiksi kokonaan " -#~ "valkoinen, kokonaan musta tai värillistä pistemössöä, saattaa koneessa " -#~ "olla hankala näytönohjain, joka ei vaihda ruutupuskuroituun tilaan " -#~ "kunnolla. Tällöin voidaan käynnistysparametrilla fb=false " -#~ "video=vga16:off ottaa ruutupuskuroitu konsoli pois käytöstä. " -#~ "Konsolin ominaisuuksien rajoitukset sallivat vain englannin kielen " -#~ "asennuksen aikana. Katso yksityiskohtia kohdasta ." - -#~ msgid "System Freeze During the PCMCIA Configuration Phase" -#~ msgstr "Järjestelmä jumittuu PCMCIA:n asetuksia tehtäessä" +#. Tag: para +#: boot-installer.xml:3475 +#, no-c-format +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic." +msgstr "" +"Usein pulmat katoavat poistamalla lisälaitekortit ja oheislaitteet, ja " +"yrittämällä käynnistystä uudelleen. Korttimodeemit, " +"äänikortit ja Plug-n-Play-laitteet ovat erityisiä ongelmapesiä." -#~ 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 hw-detect/start_pcmcia=false boot parameter. " -#~ "You can then configure PCMCIA after the installation is completed and " -#~ "exclude the resource range causing the problems." -#~ msgstr "" -#~ "Joidenkin Dellin tekemien läppärimallien tiedetään kaatuvan, kun PCMCIA-" -#~ "laitteiden tunnistus yrittää käsitellä tiettyjä laiteosoitteita. " -#~ "Muissakin läppäreissä saattaa esiintyä vastaavia vikoja. Jos tämmöinen " -#~ "vika ilmenee, eikä PCMCIA-tukea tarvita asennuksen aikana, voidaan PCMCIA " -#~ "ottaa pois käytöstä käynnistysparametrilla hw-detect/" -#~ "start_pcmcia=false. PCMCIA:n asetukset voidaan tehdä kun " -#~ "asennus on valmis ja poistaa pulmia aiheuttavien osoitteiden arvoalue " -#~ "pois käytöstä." +#. Tag: para +#: boot-installer.xml:3481 +#, 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 mem=512m." +msgstr "" +"Jos koneessa on asennettuna paljon muistia, enemmän kuin 512 Mt, ja asennin " +"jumittuu ydintä käynnistettäessä, voi olla tarpeen antaa käynnistysparametri " +"rajoittamaan ytimen näkemän muistin määrää, kuten mem=512m." + +#. Tag: title +#: boot-installer.xml:3492 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "Yleisiä suoritinperheen &arch-title; asennuspulmia" + +#. Tag: para +#: boot-installer.xml:3493 +#, 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 "" +"Muutamat yleiset asennuspulmat voidaan selvittää tai välttää antamalla " +"asentimelle sopivia käynnistysparametreja." -#~ 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 exclude port 0x800-0x8ff here. There is also " -#~ "a list of some common resource range options in the System " -#~ "resource settings section of the PCMCIA HOWTO. Note that you have " -#~ "to omit the commas, if any, when you enter this value in the installer." -#~ msgstr "" -#~ "Toinen tapa on käynnistää asennin expert-tilassa. Tällöin kysytään " -#~ "laitteiston tarvitsemia asetuksia osoitteiden arvoalueista. Jos " -#~ "asennettava kone on esimerkiksi yksi yllä mainituista Dellin läppäreistä, " -#~ "pitäisi siihen kirjoittaa exclude port 0x800-0x8ff. Saatavilla on myös luettelo yleisistä osoitteiden " -#~ "arvoalueiden asetuksista ohjeessa System resource " -#~ "settings section of the PCMCIA HOWTO. Huomaa, että pilkut, jos " -#~ "niitä on, on jätettävä pois kun tätä arvoa kirjoitetaan asentimelle." - -#~ msgid "System Freeze while Loading the USB Modules" -#~ msgstr "Järjestelmä jumittuu ladattaessa USB-moduuleita" +#. Tag: para +#: boot-installer.xml:3498 +#, no-c-format +msgid "" +"Some systems have floppies with inverted DCLs. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter floppy=thinkpad." +msgstr "" +"Joissakin tietokoneissa levykeasemassa on inverted DCL. Jos " +"levykkeestä tulee lukuvirheitä, vaikka levyke tiedetään kunnolliseksi, " +"kokeile parametria floppy=thinkpad." -#~ 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 debian-installer/" -#~ "probe/usb=false parameter at the boot prompt, which will " -#~ "prevent the modules from being loaded." -#~ msgstr "" -#~ "Normaalisti ydin yrittää asentaa USB-moduuleita ja USB-näppäimistön " -#~ "ajurin tukeakseen joitakin ei-standardeja USB-näppäimistöjä. Joissakin " -#~ "risoissa USB-järjestelmissä ajuri jumittuu sitä ladattaessa. Pulman voi " -#~ "ehkä kiertää ottamalla USB-ohjaimen pois käytöstä emolevyn BIOS:ssa. " -#~ "Toinen tapa on käynnistysparametri debian-installer/probe/" -#~ "usb=false, joka estää moduulien lataamisen." +#. Tag: para +#: boot-installer.xml:3504 +#, 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 hd=cylinders," +"heads,sectors." +msgstr "" +"Joissakin tietokoneissa, kuten IBM PS/1 tai ValuePoint (joissa on ST-506-" +"levyajurit), ei IDE-levyä ehkä tunnisteta oikein. Yritä taas ensin ilman " +"parametreja ja kokeile josko IDE-asema tunnistuu oikein. Jos ei, selvitä " +"levyn geometria (sylinterit, päät ja sektorit) ja käytä parametria " +"hd=sylinterit,päät,sektorit." + +#. Tag: para +#: boot-installer.xml:3513 +#, no-c-format +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"Checking 'hlt' instruction..., then you " +"should try the no-hlt boot argument, which disables " +"this test." +msgstr "" +"Jos kone on hyvin vanha, ja ydin jumittuu kun se on tulostanut rivin " +"Checking 'hlt' instruction..., olisi " +"kokeiltava käynnistysparametria no-hlt, joka ottaa " +"tämän testin pois käytöstä." + +#. Tag: para +#: boot-installer.xml:3520 +#, 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 fb=false " +"video=vga16:off to disable the framebuffer console. Only the " +"English language will be available during the installation due to limited " +"console features. See for details." +msgstr "" +"Jos näytön kuva on pielessä ytimen käynnistyessä, esimerkiksi kokonaan " +"valkoinen, kokonaan musta tai värillistä pistemössöä, saattaa koneessa olla " +"hankala näytönohjain, joka ei vaihda ruutupuskuroituun tilaan kunnolla. " +"Tällöin voidaan käynnistysparametrilla fb=false video=vga16:off ottaa ruutupuskuroitu konsoli pois käytöstä. Konsolin " +"ominaisuuksien rajoitukset sallivat vain englannin kielen asennuksen aikana. " +"Katso yksityiskohtia kohdasta ." + +#. Tag: title +#: boot-installer.xml:3534 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "Järjestelmä jumittuu PCMCIA:n asetuksia tehtäessä" + +#. Tag: para +#: boot-installer.xml:3535 +#, 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 " +"hw-detect/start_pcmcia=false boot parameter. You can " +"then configure PCMCIA after the installation is completed and exclude the " +"resource range causing the problems." +msgstr "" +"Joidenkin Dellin tekemien läppärimallien tiedetään kaatuvan, kun PCMCIA-" +"laitteiden tunnistus yrittää käsitellä tiettyjä laiteosoitteita. Muissakin " +"läppäreissä saattaa esiintyä vastaavia vikoja. Jos tämmöinen vika ilmenee, " +"eikä PCMCIA-tukea tarvita asennuksen aikana, voidaan PCMCIA ottaa pois " +"käytöstä käynnistysparametrilla hw-detect/start_pcmcia=false. PCMCIA:n asetukset voidaan tehdä kun asennus on valmis ja " +"poistaa pulmia aiheuttavien osoitteiden arvoalue pois käytöstä." + +#. Tag: para +#: boot-installer.xml:3545 +#, 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 " +"exclude port 0x800-0x8ff here. There is also a list " +"of some common resource range options in the System resource " +"settings section of the PCMCIA HOWTO. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." +msgstr "" +"Toinen tapa on käynnistää asennin expert-tilassa. Tällöin kysytään " +"laitteiston tarvitsemia asetuksia osoitteiden arvoalueista. Jos asennettava " +"kone on esimerkiksi yksi yllä mainituista Dellin läppäreistä, pitäisi siihen " +"kirjoittaa exclude port 0x800-0x8ff. Saatavilla on " +"myös luettelo yleisistä osoitteiden arvoalueiden asetuksista ohjeessa System resource settings section of the PCMCIA HOWTO. Huomaa, " +"että pilkut, jos niitä on, on jätettävä pois kun tätä arvoa kirjoitetaan " +"asentimelle." + +#. Tag: title +#: boot-installer.xml:3562 +#, no-c-format +msgid "System Freeze while Loading the USB Modules" +msgstr "Järjestelmä jumittuu ladattaessa USB-moduuleita" + +#. Tag: para +#: boot-installer.xml:3563 +#, 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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " +"being loaded." +msgstr "" +"Normaalisti ydin yrittää asentaa USB-moduuleita ja USB-näppäimistön ajurin " +"tukeakseen joitakin ei-standardeja USB-näppäimistöjä. Joissakin risoissa USB-" +"järjestelmissä ajuri jumittuu sitä ladattaessa. Pulman voi ehkä kiertää " +"ottamalla USB-ohjaimen pois käytöstä emolevyn BIOS:ssa. Toinen tapa on " +"käynnistysparametri debian-installer/probe/usb=false, " +"joka estää moduulien lataamisen." + +#. Tag: title +#: boot-installer.xml:3577 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "Ytimen käynnistysviestien tulkinta" + +#. Tag: para +#: boot-installer.xml:3579 +#, no-c-format +msgid "" +"During the boot sequence, you may see many messages in the form " +"can't find something , or something " +"not present, can't initialize " +"something , or even " +"this driver release depends on something . 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 )." +msgstr "" +"Käynnistyksen aikana saattaa näkyä useita tämän tapaisia viestejä: " +"can't find jotain , tai jotain not " +"present, can't initialize " +"jotain , tai jopa " +"this driver release depends on jotain . Useimmat näistä viesteistä ovat harmittomia. " +"Niitä näkyy, koska asennusydin on tehty toimimaan useiden erilaisten " +"oheislaitteiden kanssa. Tietenkään missään tietokoneessa ei ole kaikkia " +"mahdollisia oheislaitteita, joten ydin saattaa näyttää muutamia valituksia " +"oheislaitteista joita koneessa ei ole. Järjestelmä saattaa myös seisahtua " +"hetkeksi. Näin tapahtuu kun odotetaan jonkin laitteen vastausta, eikä sitä " +"laitetta ole tietokoneessa. Jos järjestelmän käynnistäminen kestää " +"sietämättömän kauan, voit myöhemmin tehdä muokatun ytimen (katso )." + +#. Tag: title +#: boot-installer.xml:3604 +#, fuzzy, no-c-format +msgid "Reporting Installation Problems" +msgstr "Yleisiä suoritinperheen &arch-title; asennuspulmia" + +#. Tag: para +#: boot-installer.xml:3605 +#, fuzzy, no-c-format +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the menu option Save debug logs may be helpful. " +"It lets you store system error logs and configuration information from the " +"installer to a floppy, or download them using 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 "" +"Jos asennusta ei saa tehtyä loppuun vaikka käynnistysvaihe toimi, saattaa " +"valikon toiminto Bug Reporter olla hyödyllinen. Sillä voidaan järjestelmän " +"virhelokit ja asentimen asetustiedostot tallentaa levykkelle, tai noutaa ne " +"webbiselaimella. Tämä tieto saattaa auttaa vikojen jäljittämisessä ja " +"korjaamisessa. Jos lähetät vikailmoitukset, halunnet liittää nämä tiedot " +"vikailmoitukseen." + +#. Tag: para +#: boot-installer.xml:3616 +#, no-c-format +msgid "" +"Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" +"Muut asiaankuuluvat asennusviestit löytyvät asennuksen aikana hakemistosta " +"/var/log/, ja hakemistosta /var/log/installer/" +" kun tietokone on käynnistynyt asennettuun järjestelmään." + +#. Tag: title +#: boot-installer.xml:3627 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "Asennusraporttien lähettäminen" + +#. Tag: para +#: boot-installer.xml:3628 +#, 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 "" +"Jos pulmia on vieläkin, ole hyvä ja lähetä asennusraportti. Olisi hyvä " +"lähettää asennusraportti myös onnistuneesta asennuksesta, jotta saamme " +"mahdollisimman paljon tietoa mahdollisimman monista laitteistokokoonpanoista." -#~ msgid "Interpreting the Kernel Startup Messages" -#~ msgstr "Ytimen käynnistysviestien tulkinta" +#. Tag: para +#: boot-installer.xml:3635 +#, no-c-format +msgid "" +"Note that your installation report will be published in the Debian Bug " +"Tracking System (BTS) and forwarded to a public mailing list. Make sure that " +"you use an E-Mail address that you do not mind being made public." +msgstr "" -#~ msgid "" -#~ "During the boot sequence, you may see many messages in the form " -#~ "can't find something , or something " -#~ "not present, can't initialize " -#~ "something , or even " -#~ "this driver release depends on something . 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 )." -#~ msgstr "" -#~ "Käynnistyksen aikana saattaa näkyä useita tämän tapaisia viestejä: " -#~ "can't find jotain , tai jotain " -#~ "not present, can't initialize " -#~ "jotain , tai jopa " -#~ "this driver release depends on jotain . Useimmat näistä viesteistä ovat " -#~ "harmittomia. Niitä näkyy, koska asennusydin on tehty toimimaan useiden " -#~ "erilaisten oheislaitteiden kanssa. Tietenkään missään tietokoneessa ei " -#~ "ole kaikkia mahdollisia oheislaitteita, joten ydin saattaa näyttää " -#~ "muutamia valituksia oheislaitteista joita koneessa ei ole. Järjestelmä " -#~ "saattaa myös seisahtua hetkeksi. Näin tapahtuu kun odotetaan jonkin " -#~ "laitteen vastausta, eikä sitä laitetta ole tietokoneessa. Jos " -#~ "järjestelmän käynnistäminen kestää sietämättömän kauan, voit myöhemmin " -#~ "tehdä muokatun ytimen (katso )." +#. Tag: para +#: boot-installer.xml:3641 +#, 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 " +"(apt-get install installation-report reportbug) and run " +"the command reportbug installation-report." +msgstr "" +"Jos käytössä on toimiva Debian-järjestelmä, on helpoin tapa asennusraportin " +"lähettämiseen pakettien installation-report ja " +"reportbug asentaminen (apt-get install " +"installation-report reportbug). Tämän jälkeen kirjoitetaan komento " +"reportbug installation-report." + +#. Tag: para +#: boot-installer.xml:3648 +#, fuzzy, no-c-format +msgid "" +"Alternatively you can use this template when filling out installation " +"reports, and file the report as a bug report against the " +"installation-reports pseudo package, by sending it to " +"submit@bugs.debian.org. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD? floppy? network?>\n" +"Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect CD: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\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" +" 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 "" +"Käytä mieluiten tätä lomaketta asennusraporttina, ja lähetä se " +"vikailmoituksena näennäispaketille installation-reports, sähköpostittamalla se osoitteella submit@bugs.debian.org. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD? floppy? network?>\n" +"Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect CD: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\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" +" Kerro vikailmoituksessa mikä vika on, ja liitä " +"mukaan viimeiset näkyvät ytimen ilmoitukset mikäli ydin jumittui. Kuvaa mitä " +"tekemällä sait järjestelmän vikatilanteeseen." #~ msgid "Bug Reporter" #~ msgstr "Vikailmoitustyökalu" -#~ 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 "" -#~ "Jos asennusta ei saa tehtyä loppuun vaikka käynnistysvaihe toimi, saattaa " -#~ "valikon toiminto Bug Reporter olla hyödyllinen. Sillä voidaan " -#~ "järjestelmän virhelokit ja asentimen asetustiedostot tallentaa " -#~ "levykkelle, tai noutaa ne webbiselaimella. Tämä tieto saattaa auttaa " -#~ "vikojen jäljittämisessä ja korjaamisessa. Jos lähetät vikailmoitukset, " -#~ "halunnet liittää nämä tiedot vikailmoitukseen." - -#~ msgid "" -#~ "Other pertinent installation messages may be found in /var/log/" -#~ " during the installation, and /var/log/installer/ after the computer has been booted into the installed system." -#~ msgstr "" -#~ "Muut asiaankuuluvat asennusviestit löytyvät asennuksen aikana " -#~ "hakemistosta /var/log/, ja hakemistosta /" -#~ "var/log/installer/ kun tietokone on käynnistynyt asennettuun " -#~ "järjestelmään." - -#~ msgid "Submitting Installation Reports" -#~ msgstr "Asennusraporttien lähettäminen" - -#~ 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 "" -#~ "Jos pulmia on vieläkin, ole hyvä ja lähetä asennusraportti. Olisi hyvä " -#~ "lähettää asennusraportti myös onnistuneesta asennuksesta, jotta saamme " -#~ "mahdollisimman paljon tietoa mahdollisimman monista " -#~ "laitteistokokoonpanoista." - -#~ 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 (apt-get install installation-report reportbug) and run the command reportbug installation-report." -#~ msgstr "" -#~ "Jos käytössä on toimiva Debian-järjestelmä, on helpoin tapa " -#~ "asennusraportin lähettämiseen pakettien installation-report ja reportbug asentaminen (apt-" -#~ "get install installation-report reportbug). Tämän jälkeen " -#~ "kirjoitetaan komento reportbug installation-report." - -#~ msgid "" -#~ "Please use this template when filling out installation reports, and file " -#~ "the report as a bug report against the installation-reports pseudo package, by sending it to submit@bugs.debian." -#~ "org. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <How did you boot the installer? CD? floppy? network?" -#~ ">\n" -#~ "Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" -#~ "\n" -#~ "Base System Installation Checklist:\n" -#~ "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" -#~ "\n" -#~ "Initial boot: [ ]\n" -#~ "Detect network card: [ ]\n" -#~ "Configure network: [ ]\n" -#~ "Detect CD: [ ]\n" -#~ "Load installer modules: [ ]\n" -#~ "Detect hard drives: [ ]\n" -#~ "Partition hard drives: [ ]\n" -#~ "Install base system: [ ]\n" -#~ "Clock/timezone setup: [ ]\n" -#~ "User/password setup: [ ]\n" -#~ "Install tasks: [ ]\n" -#~ "Install boot loader: [ ]\n" -#~ "Overall install: [ ]\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" -#~ " 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 "" -#~ "Käytä mieluiten tätä lomaketta asennusraporttina, ja lähetä se " -#~ "vikailmoituksena näennäispaketille installation-reports, sähköpostittamalla se osoitteella submit@bugs.debian." -#~ "org. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <How did you boot the installer? CD? floppy? network?" -#~ ">\n" -#~ "Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" -#~ "\n" -#~ "Base System Installation Checklist:\n" -#~ "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" -#~ "\n" -#~ "Initial boot: [ ]\n" -#~ "Detect network card: [ ]\n" -#~ "Configure network: [ ]\n" -#~ "Detect CD: [ ]\n" -#~ "Load installer modules: [ ]\n" -#~ "Detect hard drives: [ ]\n" -#~ "Partition hard drives: [ ]\n" -#~ "Install base system: [ ]\n" -#~ "Clock/timezone setup: [ ]\n" -#~ "User/password setup: [ ]\n" -#~ "Install tasks: [ ]\n" -#~ "Install boot loader: [ ]\n" -#~ "Overall install: [ ]\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" -#~ " Kerro vikailmoituksessa mikä vika on, ja " -#~ "liitä mukaan viimeiset näkyvät ytimen ilmoitukset mikäli ydin jumittui. " -#~ "Kuvaa mitä tekemällä sait järjestelmän vikatilanteeseen." - #~ msgid "" #~ "Proceed to the next chapter to continue the installation where you will " #~ "set up the language locale, network, and the disk partitions." diff --git a/po/fi/preparing.po b/po/fi/preparing.po index e33b200e0..cc56b9ef0 100644 --- a/po/fi/preparing.po +++ b/po/fi/preparing.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: Debian Installation Guide preparing\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-26 16:20+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-12-11 16:15+0200\n" "Last-Translator: Tapio Lehtonen \n" "Language-Team: Finnish \n" @@ -58,7 +58,12 @@ msgid "" "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 "Useiden paljon käytettyjen käyttöjärjestelmien kanssa voidaan joutua asentamaan alusta asti kun on tapahtunut vakava virhe tai kun päivitetään uuteen käyttöjärjestelmän versioon. Vaikka täysin uutta asennusta ei tarvitsisikaan tehdä, joutuu usein asentamaan käytetyt ohjelmat uudelleen, jotta ne toimisivat kunnolla uudessa käyttöjärjestelmässä." +msgstr "" +"Useiden paljon käytettyjen käyttöjärjestelmien kanssa voidaan joutua " +"asentamaan alusta asti kun on tapahtunut vakava virhe tai kun päivitetään " +"uuteen käyttöjärjestelmän versioon. Vaikka täysin uutta asennusta ei " +"tarvitsisikaan tehdä, joutuu usein asentamaan käytetyt ohjelmat uudelleen, " +"jotta ne toimisivat kunnolla uudessa käyttöjärjestelmässä." #. Tag: para #: preparing.xml:35 @@ -73,7 +78,18 @@ msgid "" "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 " "not designed to re-install over an existing system." -msgstr "Käytettäessä &debian;ia, on paljon todennäköisempää, että vikatilanteessa käyttöjärjestelmä voidaan korjata eikä sitä tarvitse asentaa uudelleen. Päivitykset eivät koskaan vaadi kaiken asentamista uudelleen; Debian osaa aina päivittää itse itsensä. Lisäksi ohjelmat ovat melkein aina yhteensopivia peräkkäisissä Debianin julkaisuissa. Jos ohjelman uusi versio vaatii uudempia tukiohjelmia, Debianin paketointijärjestelmä varmistaa kaikkien tarpeellisten ohjelmien löytyvän ja tulevan asennetuiksi automaattisesti. Korostetaan vielä, että paljon työtä on tehty, jotta uuudelleen asennus ei olisi välttämätöntä, joten uudelleenasennusta olisi pidettävä viimeisenä vaihtoehtona. Asenninta ei ole tarkoitettu uudelleenasennukseen jo asennetun järjestelmän päälle. " +msgstr "" +"Käytettäessä &debian;ia, on paljon todennäköisempää, että vikatilanteessa " +"käyttöjärjestelmä voidaan korjata eikä sitä tarvitse asentaa uudelleen. " +"Päivitykset eivät koskaan vaadi kaiken asentamista uudelleen; Debian osaa " +"aina päivittää itse itsensä. Lisäksi ohjelmat ovat melkein aina " +"yhteensopivia peräkkäisissä Debianin julkaisuissa. Jos ohjelman uusi versio " +"vaatii uudempia tukiohjelmia, Debianin paketointijärjestelmä varmistaa " +"kaikkien tarpeellisten ohjelmien löytyvän ja tulevan asennetuiksi " +"automaattisesti. Korostetaan vielä, että paljon työtä on tehty, jotta " +"uuudelleen asennus ei olisi välttämätöntä, joten uudelleenasennusta olisi " +"pidettävä viimeisenä vaihtoehtona. Asenninta ei ole " +"tarkoitettu uudelleenasennukseen jo asennetun järjestelmän päälle. " #. Tag: para #: preparing.xml:48 @@ -114,7 +130,9 @@ msgstr "Luo Debianille osioitavaksi kelpaavaa tilaa kiintolevylle." msgid "" "Locate and/or download the installer software and any specialized driver " "files your machine requires (except Debian CD users)." -msgstr "Etsi ja/tai nouda asennusohjelmisto ja tietokoneen tarvitsemat erikoisajurit (asennettaessa Debian-rompulta ei erikoisajureista tarvitse välittää)" +msgstr "" +"Etsi ja/tai nouda asennusohjelmisto ja tietokoneen tarvitsemat erikoisajurit " +"(asennettaessa Debian-rompulta ei erikoisajureista tarvitse välittää)" #. Tag: para #: preparing.xml:79 @@ -122,7 +140,10 @@ msgstr "Etsi ja/tai nouda asennusohjelmisto ja tietokoneen tarvitsemat erikoisaj msgid "" "Set up boot tapes/floppies/USB sticks, or place boot files (most Debian CD " "users can boot from one of the CDs)." -msgstr "Valmistele käynnistysnauhat/-levykkeet tai USB-muistit, tai tallenna käynnistystiedostot kiintolevylle (asennettaessa Debian-rompulta voidaan useimmiten käynnistää rompulta)." +msgstr "" +"Valmistele käynnistysnauhat/-levykkeet tai USB-muistit, tai tallenna " +"käynnistystiedostot kiintolevylle (asennettaessa Debian-rompulta voidaan " +"useimmiten käynnistää rompulta)." #. Tag: para #: preparing.xml:85 @@ -215,7 +236,14 @@ msgid "" "system packages. Many more actors play smaller parts in this process, but " "debian-installer has completed its task when you load " "the new system for the first time." -msgstr "Tämä ohje on pääasiassa Debianin asentimen, debian-installer, käyttöohje. Asennin tunnistaa laitteiston ja lataa sopivat ajurit, tekee verkkoasetukset dhcp-client:n avulla ja käynnistää debootstrapin asentamaan peruskokoonpanon paketit. Useat muut ohjelmat näyttelevät pienempiä osia tässä prosessissa, mutta debian-installerin työ on päättynyt, kun uusi järjestelmä käynnistetään ensimmäisen kerran." +msgstr "" +"Tämä ohje on pääasiassa Debianin asentimen, debian-installer, käyttöohje. Asennin tunnistaa laitteiston ja lataa sopivat " +"ajurit, tekee verkkoasetukset dhcp-client:n avulla ja " +"käynnistää debootstrapin asentamaan peruskokoonpanon " +"paketit. Useat muut ohjelmat näyttelevät pienempiä osia tässä prosessissa, " +"mutta debian-installerin työ on päättynyt, kun uusi " +"järjestelmä käynnistetään ensimmäisen kerran." #. Tag: para #: preparing.xml:157 @@ -224,7 +252,10 @@ msgid "" "To tune the system to your needs, tasksel allows you " "to choose to install various predefined bundles of software like a Web " "server or a Desktop environment." -msgstr "Järjestelmää voi sovittaa omiin tarpeisiinsa valitsemalla taskselin avulla erilaisia esimääriteltyjä ohjelmakokoelmia, kuten webbipalvelin tai työpöytäympäristö." +msgstr "" +"Järjestelmää voi sovittaa omiin tarpeisiinsa valitsemalla " +"taskselin avulla erilaisia esimääriteltyjä " +"ohjelmakokoelmia, kuten webbipalvelin tai työpöytäympäristö." #. Tag: para #: preparing.xml:163 @@ -236,7 +267,13 @@ msgid "" "installed unless you select it with tasksel. 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 "Kun debian-installer lopettaa, on ennen uuden järjestelmän ensimmäistä käynnistystä käytettävissä vain komentoriviltä käytettävä peruskokoonpano. Ikkunoita näytön ruudulla näyttävää graafista käyttöliittymää ei asenneta jos sitä ei taskselillä valita. Se on valinnainen, koska useat &debian; -järjestelmät ovat palvelinkoneita, joissa ei ole mitään tarvetta graafiselle käyttöliittymälle." +msgstr "" +"Kun debian-installer lopettaa, on ennen uuden " +"järjestelmän ensimmäistä käynnistystä käytettävissä vain komentoriviltä " +"käytettävä peruskokoonpano. Ikkunoita näytön ruudulla näyttävää graafista " +"käyttöliittymää ei asenneta jos sitä ei taskselillä " +"valita. Se on valinnainen, koska useat &debian; -järjestelmät ovat " +"palvelinkoneita, joissa ei ole mitään tarvetta graafiselle käyttöliittymälle." #. Tag: para #: preparing.xml:172 @@ -920,7 +957,10 @@ msgid "" "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 "Jos verkon vastuuhenkilö kertoo DHCP-palvelimen olevan käytettävissä ja että sen käyttö on suositeltavaa, ei näitä tietoja tarvita, koska DHCP-palvelin tarjoaa tiedot asennuksen aikana suoraan tietokoneelle." +msgstr "" +"Jos verkon vastuuhenkilö kertoo DHCP-palvelimen olevan käytettävissä ja että " +"sen käyttö on suositeltavaa, ei näitä tietoja tarvita, koska DHCP-palvelin " +"tarjoaa tiedot asennuksen aikana suoraan tietokoneelle." #. Tag: para #: preparing.xml:626 @@ -964,7 +1004,10 @@ 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 "Käyttötarkoitus saattaa sallia laitteiston, joka ei täytä alla olevassa taulukossa mainittuja suosituksia. Useimmat käyttäjät kuitenkin turhautuvat jos jättävät huomiotta nämä suositukset." +msgstr "" +"Käyttötarkoitus saattaa sallia laitteiston, joka ei täytä alla olevassa " +"taulukossa mainittuja suosituksia. Useimmat käyttäjät kuitenkin turhautuvat " +"jos jättävät huomiotta nämä suositukset." #. Tag: para #: preparing.xml:666 @@ -1174,7 +1217,17 @@ msgid "" "installed packages) can easily consume 20MB. Also, apt-get puts downloaded packages here before they are installed. You should " "usually allocate at least 100MB for /var." -msgstr "Huomaa, ettei näihin kokoihin ole laskettu mukaan muuta tietokoneella tavallisesti olevaa tietoa, kuten käyttäjien tiedostot, sähköpostit ja tiedot. On aina parasta mitoittaa omien tiedostojen ja tietojen tila yläkanttiin. Erityisesti /var-osio sisältää paljon Debianin omaa tilatietoa tavallisten tietojen kuten lokitiedostojen lisäksi. Sovelluksen dpkg tiedostot (joissa on tiedot kaikista asennetuista paketeista) voivat helposti viedä 20 Mt. Lisäksi apt-get tallentaa noudetut paketit /var-osioon ennen kuin ne asennetaan. Osiolle /var olisi tavallisesti annettava tilaa ainakin 100 Mt." +msgstr "" +"Huomaa, ettei näihin kokoihin ole laskettu mukaan muuta tietokoneella " +"tavallisesti olevaa tietoa, kuten käyttäjien tiedostot, sähköpostit ja " +"tiedot. On aina parasta mitoittaa omien tiedostojen ja tietojen tila " +"yläkanttiin. Erityisesti /var-osio sisältää paljon " +"Debianin omaa tilatietoa tavallisten tietojen kuten lokitiedostojen lisäksi. " +"Sovelluksen dpkg tiedostot (joissa on tiedot kaikista " +"asennetuista paketeista) voivat helposti viedä 20 Mt. Lisäksi apt-" +"get tallentaa noudetut paketit /var-osioon " +"ennen kuin ne asennetaan. Osiolle /var olisi " +"tavallisesti annettava tilaa ainakin 100 Mt." #. Tag: title #: preparing.xml:790 @@ -1304,7 +1357,18 @@ msgid "" "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 "Jos tietokoneessa on vain yksi kiintolevy, ja levyllä oleva käyttöjärjestelmä halutaan kokonaan korvata &debian;illa, voidaan tässäkin tapauksessa tehdä osiot asennusprosessin osana (), kun asennusjärjestelmä on käynnistetty. Tämä kuitenkin toimii vain jos asennusjärjestelmä on tarkoitus käynnistää nauhalta, rompulta tai verkkokäynnistyksellä. Mieti tätä: jos käynnistetään kiintolevyllä olevilta tiedostoilta, ja sitten asennusjärjestelmä osioi saman levyn pyyhkien asennustiedostot pois, on parasta toivoa asennuksen onnistuvan ensimmäisellä yrittämällä. Ainakin tässä tapauksessa olisi oltava vaihtoehtoinen tapa herättää tietokone taas toimintaan, esimerkiksi alkuperäisen käyttöjärjestelmän asennusnauhoilta tai -rompuilta." +msgstr "" +"Jos tietokoneessa on vain yksi kiintolevy, ja levyllä oleva " +"käyttöjärjestelmä halutaan kokonaan korvata &debian;illa, voidaan tässäkin " +"tapauksessa tehdä osiot asennusprosessin osana (), kun asennusjärjestelmä on käynnistetty. Tämä kuitenkin toimii vain jos " +"asennusjärjestelmä on tarkoitus käynnistää nauhalta, rompulta tai " +"verkkokäynnistyksellä. Mieti tätä: jos käynnistetään kiintolevyllä olevilta " +"tiedostoilta, ja sitten asennusjärjestelmä osioi saman levyn pyyhkien " +"asennustiedostot pois, on parasta toivoa asennuksen onnistuvan ensimmäisellä " +"yrittämällä. Ainakin tässä tapauksessa olisi oltava vaihtoehtoinen tapa " +"herättää tietokone taas toimintaan, esimerkiksi alkuperäisen " +"käyttöjärjestelmän asennusnauhoilta tai -rompuilta." #. Tag: para #: preparing.xml:875 @@ -1316,7 +1380,14 @@ msgid "" "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 "Jos tietokoneella on jo useita levyosioita, ja saadaan riittävästi tilaa poistamalla tai korvaamalla niistä yksi tai useampia, ei tässäkään tapauksessa ole tarpeen tehdä osioita etukäteen, vaan voidaan odottaa ja käyttää Debianin asentimen osiointisovellusta. Alla olevat ohjeet olisi silti luettava läpi, koska useissa erikoistilanteissa, joihin vaikuttaa esimerkiksi osioiden järjestys osiotaulussa, on kaikesta huolimatta pakko osioida ennen asennusta." +msgstr "" +"Jos tietokoneella on jo useita levyosioita, ja saadaan riittävästi tilaa " +"poistamalla tai korvaamalla niistä yksi tai useampia, ei tässäkään " +"tapauksessa ole tarpeen tehdä osioita etukäteen, vaan voidaan odottaa ja " +"käyttää Debianin asentimen osiointisovellusta. Alla olevat ohjeet olisi " +"silti luettava läpi, koska useissa erikoistilanteissa, joihin vaikuttaa " +"esimerkiksi osioiden järjestys osiotaulussa, on kaikesta huolimatta pakko " +"osioida ennen asennusta." #. Tag: para #: preparing.xml:885 @@ -1425,7 +1496,11 @@ msgid "" "tapes. When booting from a MacOS CD, hold the " "c key while booting to force the CD to become the active " "MacOS system." -msgstr "Käynnistetään koneen oman käyttöjärjestelmän asennustaltiolta, esimerkiksi romppu tai nauha. Kun käynnistetään MacOS-rompulta, pidä näppäintä c alhaalla koneen käynnistyessä. Tämä pakottaa koneen käyttämään rompulla olevaa MacOS-järjestelmää." +msgstr "" +"Käynnistetään koneen oman käyttöjärjestelmän asennustaltiolta, esimerkiksi " +"romppu tai nauha. Kun käynnistetään MacOS-rompulta, " +"pidä näppäintä c alhaalla koneen käynnistyessä. Tämä " +"pakottaa koneen käyttämään rompulla olevaa MacOS-järjestelmää." #. Tag: para #: preparing.xml:950 @@ -1671,7 +1746,16 @@ msgid "" " Manual partitioning, " "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 "Yksi yleisimpiä asennuksia on asennus tietokoneeseen jossa on jo DOS (mukaan lukien Windows 3.1), Win32 (kuten Windows 95, 98, Me, NT, 2000, XP) tai OS/2, ja Debian halutaan asentaa samalle levylle tuhoamatta aikaisempaa käyttöjärjestelmää. Huomaa asentimen tukevan DOS:n ja Windowsin käyttämien FAT- ja NTFS-tiedostojärjestelmien koon muuttamista. Asennin vain käynnistetään, valitaan Osioi itse , valitaan osio jonka kokoa muutetaan ja määritetään sen uusi koko. Niinpä useimmissa tapauksissa ei ole tarpeen käyttää alla kuvauttua menettelyä." +msgstr "" +"Yksi yleisimpiä asennuksia on asennus tietokoneeseen jossa on jo DOS (mukaan " +"lukien Windows 3.1), Win32 (kuten Windows 95, 98, Me, NT, 2000, XP) tai " +"OS/2, ja Debian halutaan asentaa samalle levylle tuhoamatta aikaisempaa " +"käyttöjärjestelmää. Huomaa asentimen tukevan DOS:n ja Windowsin käyttämien " +"FAT- ja NTFS-tiedostojärjestelmien koon muuttamista. Asennin vain " +"käynnistetään, valitaan Osioi itse , valitaan osio jonka kokoa muutetaan ja määritetään sen uusi " +"koko. Niinpä useimmissa tapauksissa ei ole tarpeen käyttää alla kuvauttua " +"menettelyä." #. Tag: para #: preparing.xml:1105 @@ -1771,7 +1855,9 @@ msgstr "" msgid "" "Note that there are many other partition managers out there, in case " "fips doesn't do the trick for you." -msgstr "Huomaa, että saatavilla on monia muita sovelluksia osioiden muokkaukseen, jos fips ei sattuisi toimimaan." +msgstr "" +"Huomaa, että saatavilla on monia muita sovelluksia osioiden muokkaukseen, " +"jos fips ei sattuisi toimimaan." #. Tag: title #: preparing.xml:1160 @@ -2150,7 +2236,19 @@ msgid "" "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 "Mikäli tarkoituksena on asentaa sekä MacOS 9 että OS X, on parasta luoda erilliset osiot kummallekin. Jos ne asennetaan samaan osioon, sovellusta Startup Disk (ja uudelleenkäynnistystä) on käytettävä valitsemaan käyttöjärjestelmien välillä; käynnistyvää järjestelmää ei voi valita käynnistyksen aikana. Kun ne on asennettu erillisiin osioihin, näkyy oma valinta sekä OS 9:lle että OS X:lle kun näppäintä option pidettään pohjassa käynnistyksen aikana. Myös yabootin käynnistysvalikkoon voidaan asentaan kummallekin oma valinta. Startup Disk myöskin piilottaa kaikki muut liitettävät osiot, joka voi vaikuttaa GNU/Linuxin käynnistämiseen. Sekä OS 9 että OS X -osiot ovat käytettävissä molemmista käyttöjärjestelmistä OS 9 ja OS X." +msgstr "" +"Mikäli tarkoituksena on asentaa sekä MacOS 9 että OS X, on parasta luoda " +"erilliset osiot kummallekin. Jos ne asennetaan samaan osioon, sovellusta " +"Startup Disk (ja uudelleenkäynnistystä) on " +"käytettävä valitsemaan käyttöjärjestelmien välillä; käynnistyvää " +"järjestelmää ei voi valita käynnistyksen aikana. Kun ne on asennettu " +"erillisiin osioihin, näkyy oma valinta sekä OS 9:lle että OS X:lle kun " +"näppäintä option pidettään pohjassa käynnistyksen aikana. " +"Myös yabootin käynnistysvalikkoon voidaan " +"asentaan kummallekin oma valinta. Startup Disk myöskin piilottaa kaikki muut " +"liitettävät osiot, joka voi vaikuttaa GNU/Linuxin käynnistämiseen. Sekä OS 9 " +"että OS X -osiot ovat käytettävissä molemmista käyttöjärjestelmistä OS 9 ja " +"OS X." #. Tag: para #: preparing.xml:1391 @@ -2162,7 +2260,14 @@ msgid "" "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 "GNU/Linux ei voi käyttää UFS-osioilla olevia tietoja, mutta tukee HFS+ (eli MacOS Extended) -osioita. OS X vaatiin jomman kumman näistä tyypeistä käynnistysosiokseen. MacOS 9 voidaan asentaa joko HFS (eli MacOS Standard) tai HFS+ -osiolle. Jotta tiedostoja voi vaihtaa MacOS- ja GNU/Linux-järjestelmien välillä, on kätevää tehdä tiedostojen vaihtoon tarkoitettu osio. Osiotyypit HFS, HFS+ ja MS-DOS FAT ovat kaikki tuettuja sekä MacOS:ssä että Linuxissa." +msgstr "" +"GNU/Linux ei voi käyttää UFS-osioilla olevia tietoja, mutta tukee HFS+ (eli " +"MacOS Extended) -osioita. OS X vaatiin jomman kumman näistä tyypeistä " +"käynnistysosiokseen. MacOS 9 voidaan asentaa joko HFS (eli MacOS Standard) " +"tai HFS+ -osiolle. Jotta tiedostoja voi vaihtaa MacOS- ja GNU/Linux-" +"järjestelmien välillä, on kätevää tehdä tiedostojen vaihtoon tarkoitettu " +"osio. Osiotyypit HFS, HFS+ ja MS-DOS FAT ovat kaikki tuettuja sekä MacOS:ssä " +"että Linuxissa." #. Tag: title #: preparing.xml:1411 @@ -2181,7 +2286,14 @@ msgid "" "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 "Tässä luvussa käydään askel askeleeltä läpi laiteasetukset, jos niitä on, jotka on tehtävä ennen Debianin asennusta. Yleensä on tarkistettava ja ehkä muutettava tietokoneen laiteohjelmiston asetuksia. Laiteohjelmisto on laitteiston käyttämä perusohjelmisto; sen tärkein tehtävä on alkulatauksen yhteydessä (kun laitteistoon on kytketty virta). Myös tiedossa olevat laiteiston ominaisuudet jotka vaikuttavat &debian;in luotettavuuteen on korostettu." +msgstr "" +"Tässä luvussa käydään askel askeleeltä läpi laiteasetukset, jos niitä on, " +"jotka on tehtävä ennen Debianin asennusta. Yleensä on tarkistettava ja ehkä " +"muutettava tietokoneen laiteohjelmiston asetuksia. Laiteohjelmisto on laitteiston käyttämä perusohjelmisto; sen tärkein tehtävä on " +"alkulatauksen yhteydessä (kun laitteistoon on kytketty virta). Myös tiedossa " +"olevat laiteiston ominaisuudet jotka vaikuttavat &debian;in luotettavuuteen " +"on korostettu." #. Tag: title #: preparing.xml:1434 @@ -2198,7 +2310,13 @@ msgid "" "BIOS set-up menu, which is used to configure the BIOS. Before installing, " "you must ensure that your BIOS is setup correctly; not " "doing so can lead to intermittent crashes or an inability to install Debian." -msgstr "BIOS toteuttaa perustoiminnallisuuden tietokoneen käynnistämiseen. Sen avulla käyttöjärjestelmä pääsee käsiksi laitteistoon. Luultavimmin tietokoneessa on BIOS-valikko, josta BIOSin asetukset tehdään. Ennen asennusta on varmistuttava BIOSin asetusten olevan oikein; väärät asetukset saattavat johtaa satunnaisiin kaatumisiin tai Debianin asennus ei onnistu." +msgstr "" +"BIOS toteuttaa perustoiminnallisuuden tietokoneen käynnistämiseen. Sen " +"avulla käyttöjärjestelmä pääsee käsiksi laitteistoon. Luultavimmin " +"tietokoneessa on BIOS-valikko, josta BIOSin asetukset tehdään. Ennen " +"asennusta on varmistuttava BIOSin asetusten olevan " +"oikein; väärät asetukset saattavat johtaa satunnaisiin kaatumisiin tai " +"Debianin asennus ei onnistu." #. Tag: para #: preparing.xml:1445 @@ -2208,7 +2326,11 @@ msgid "" "ulink>, answering the question, How do I enter the CMOS configuration " "menu?. How you access the BIOS (or CMOS) " "configuration menu depends on who wrote your BIOS software:" -msgstr "Tämän luvun loppu on kopioitu ohjeesta , jossa kerrotaan Miten pääsen CMOS-asetusten valikkoon?. Miten BIOS-asetuksiin (eli CMOSiin) päästään riippuu BIOS-ohjelmiston valmistajasta:" +msgstr "" +"Tämän luvun loppu on kopioitu ohjeesta , jossa kerrotaan Miten pääsen CMOS-asetusten valikkoon?. Miten BIOS-asetuksiin (eli CMOSiin) päästään riippuu " +"BIOS-ohjelmiston valmistajasta:" #. Tag: term #: preparing.xml:1459 @@ -2234,7 +2356,9 @@ msgstr "Award BIOS" msgid "" " CtrlAltEsc , or Delete key during the POST" -msgstr " CtrlAltEsc , tai Delete POSTin aikana" +msgstr "" +" CtrlAltEsc , tai Delete POSTin aikana" #. Tag: term #: preparing.xml:1478 @@ -2261,7 +2385,10 @@ msgid "" " CtrlAltInsert " " after CtrlAltDelete " -msgstr " CtrlAltInsert kun ensin on painettu CtrlAltDelete " +msgstr "" +" CtrlAltInsert " +" kun ensin on painettu CtrlAltDelete " #. Tag: term #: preparing.xml:1501 @@ -2276,7 +2403,10 @@ msgid "" " CtrlAltEsc or CtrlAltS or F1" -msgstr " CtrlAltEsc tai CtrlAltS tai F1" +msgstr "" +" CtrlAltEsc tai CtrlAltS tai F1" #. Tag: para #: preparing.xml:1518 @@ -2284,7 +2414,9 @@ msgstr " CtrlAltEsc msgid "" "Information on invoking other BIOS routines can be found in ." -msgstr "Muiden BIOS-toimintojen käynnistämisestä löytyy tietoa osoitteesta ." +msgstr "" +"Muiden BIOS-toimintojen käynnistämisestä löytyy tietoa osoitteesta ." #. Tag: para #: preparing.xml:1523 @@ -2295,7 +2427,12 @@ msgid "" "Installation and/or Diagnostics diskette for your machine, you can try using " "a shareware/freeware program. Try looking in ." -msgstr "Joissakin prosessoriperheen &arch-title; koneissa ei ole CMOS-asetusten tekoa BIOSissa. Niissä tarvitaan sovellus CMOSin asetusten muuttamiseen. Jos konetta varten ei ole Asennus- tai Diagnostics-levykettä, voi kokeilla jotain shareware/freeware-ohjelmaa. Yritä etsiä osoitteesta ." +msgstr "" +"Joissakin prosessoriperheen &arch-title; koneissa ei ole CMOS-asetusten " +"tekoa BIOSissa. Niissä tarvitaan sovellus CMOSin asetusten muuttamiseen. Jos " +"konetta varten ei ole Asennus- tai Diagnostics-levykettä, voi kokeilla " +"jotain shareware/freeware-ohjelmaa. Yritä etsiä osoitteesta ." #. Tag: title #: preparing.xml:1534 preparing.xml:1878 @@ -2314,7 +2451,14 @@ msgid "" "), and then from C: (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 "BIOS-valikoissa on usein mahdollista valita miltä laitteelta käynnistetään. Tee asetus siten, että käynnistettävää järjestelmää etsitään laitteelta A: (ensimmäinen levykeasema), sitten valinnaisesti ensimmäiseltä romppuasemalta (saattaa olla laitteena D: tai E:), ja sitten laitteelta C: (ensimmäinen kiintolevy). Tällä asetuksella voi käynnistää joko levykkeeltä tai rompulta, jotka ovat Debianin kaksi yleisintä asennustaltiota." +msgstr "" +"BIOS-valikoissa on usein mahdollista valita miltä laitteelta käynnistetään. " +"Tee asetus siten, että käynnistettävää järjestelmää etsitään laitteelta " +"A: (ensimmäinen levykeasema), sitten valinnaisesti " +"ensimmäiseltä romppuasemalta (saattaa olla laitteena D: " +"tai E:), ja sitten laitteelta C: " +"(ensimmäinen kiintolevy). Tällä asetuksella voi käynnistää joko levykkeeltä " +"tai rompulta, jotka ovat Debianin kaksi yleisintä asennustaltiota." #. Tag: para #: preparing.xml:1547 @@ -2323,7 +2467,10 @@ 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 "Jos tietokoneessa on uudehko SCSI-ohjain johon on liitetty romppuasema, on tavallisesti mahdollista käynnistää rompulta. Riittää kun ohjaimen SCSI-BIOS:ssa otetaan käyttöön rompulta käynnistäminen." +msgstr "" +"Jos tietokoneessa on uudehko SCSI-ohjain johon on liitetty romppuasema, on " +"tavallisesti mahdollista käynnistää rompulta. Riittää kun ohjaimen SCSI-BIOS:" +"ssa otetaan käyttöön rompulta käynnistäminen." #. Tag: para #: preparing.xml:1554 @@ -2334,7 +2481,12 @@ msgid "" "storage device, but some cannot. You may need to configure your BIOS to boot " "from a Removable drive or even from USB-ZIP to " "get it to boot from the USB device." -msgstr "Toinen suosittu tapa on käynnistää USB-muistilta (käytetään myös nimeä USB-muistitikku). Jotkin BIOSit osaavat käynnistää suoraan USB-laitteelta, jotkut eivät osaa. BIOS on ehkä asetettava käynnistymään laitteelta Removable drive tai jopa USB-ZIP jotta USB-laitteelta voi käynnistää." +msgstr "" +"Toinen suosittu tapa on käynnistää USB-muistilta (käytetään myös nimeä USB-" +"muistitikku). Jotkin BIOSit osaavat käynnistää suoraan USB-laitteelta, " +"jotkut eivät osaa. BIOS on ehkä asetettava käynnistymään laitteelta " +"Removable drive tai jopa USB-ZIP jotta USB-" +"laitteelta voi käynnistää." #. Tag: para #: preparing.xml:1562 @@ -2343,7 +2495,10 @@ 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 "Tässä on muutamia ohjeita käynnistysjärjestyksen asettamisesta. Muista palauttaa käynnistysjärjestys kun Linux on asennettu, jotta tietokone käynnistyy taas kiintolevyltä." +msgstr "" +"Tässä on muutamia ohjeita käynnistysjärjestyksen asettamisesta. Muista " +"palauttaa käynnistysjärjestys kun Linux on asennettu, jotta tietokone " +"käynnistyy taas kiintolevyltä." #. Tag: title #: preparing.xml:1571 @@ -2358,7 +2513,10 @@ msgid "" "As your computer starts, press the keys to enter the BIOS utility. Often, it " "is the Delete key. However, consult the hardware " "documentation for the exact keystrokes." -msgstr "Kun tietokone käynnistyy, paina näppäimiä joilla pääsee BIOSin asetusohjelmaan. Näppäin on usein Delete. Katso oikea näppäin tai näppäimet kuitenkin laitteen ohjeista." +msgstr "" +"Kun tietokone käynnistyy, paina näppäimiä joilla pääsee BIOSin " +"asetusohjelmaan. Näppäin on usein Delete. Katso oikea " +"näppäin tai näppäimet kuitenkin laitteen ohjeista." #. Tag: para #: preparing.xml:1581 @@ -2366,7 +2524,9 @@ msgstr "Kun tietokone käynnistyy, paina näppäimiä joilla pääsee BIOSin ase 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 "Etsi asetusohjelmasta käynnistysjärjestys. Eri BIOSeissa se on eri paikassa, mutta yritä etsiä kenttää jossa on luettelo levyasemista." +msgstr "" +"Etsi asetusohjelmasta käynnistysjärjestys. Eri BIOSeissa se on eri paikassa, " +"mutta yritä etsiä kenttää jossa on luettelo levyasemista." #. Tag: para #: preparing.xml:1586 @@ -2387,7 +2547,10 @@ msgid "" "Change the boot sequence setting so that the CD-ROM or the floppy is first. " "Usually, the Page Up or Page Down keys " "cycle through the possible choices." -msgstr "Vaihda käynnistysjärjestystä siten että romppu tai levyke on ensimmäisenä. Tavallisesti näppäimillä Page Up tai Page Down näkee mahdolliset valinnat." +msgstr "" +"Vaihda käynnistysjärjestystä siten että romppu tai levyke on ensimmäisenä. " +"Tavallisesti näppäimillä Page Up tai Page Down näkee mahdolliset valinnat." #. Tag: para #: preparing.xml:1605 @@ -2395,7 +2558,9 @@ msgstr "Vaihda käynnistysjärjestystä siten että romppu tai levyke on ensimm msgid "" "Save your changes. Instructions on the screen tell you how to save the " "changes on your computer." -msgstr "Tallenna muutokset. Näytöllä näkyvistä ohjeista ilmenee miten muutokset tallennetaan tällä tietokoneella." +msgstr "" +"Tallenna muutokset. Näytöllä näkyvistä ohjeista ilmenee miten muutokset " +"tallennetaan tällä tietokoneella." #. Tag: title #: preparing.xml:1615 @@ -2408,7 +2573,9 @@ msgstr "Käynnistysjärjestyksen vaihtaminen SCSI-levyjä käyttävässä konees #, no-c-format msgid "" "As your computer starts, press the keys to enter the SCSI setup utility." -msgstr "Paina SCSI-asetukset tekevään ohjelmaan vievää näppäintä koneen käynnistyessä." +msgstr "" +"Paina SCSI-asetukset tekevään ohjelmaan vievää näppäintä koneen " +"käynnistyessä." #. Tag: para #: preparing.xml:1624 @@ -2416,7 +2583,10 @@ msgstr "Paina SCSI-asetukset tekevään ohjelmaan vievää näppäintä koneen k 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 "SCSI-asetukset tekevä ohjelman voidaan käynnistää koneen käynnistyttyä muistin tarkistuksen jälkeen ja kun ruudulla näkyy miten BIOSin asetuksiin pääsee." +msgstr "" +"SCSI-asetukset tekevä ohjelman voidaan käynnistää koneen käynnistyttyä " +"muistin tarkistuksen jälkeen ja kun ruudulla näkyy miten BIOSin asetuksiin " +"pääsee." #. Tag: para #: preparing.xml:1630 @@ -2425,7 +2595,10 @@ msgid "" "The keystrokes you need depend on the utility. Often, it is " "CtrlF2. However, " "consult your hardware documentation for the exact keystrokes." -msgstr "Käytettävä näppäin vaihtelee ohjelmittain. Se on usein CtrlF2. Katso oikea näppäin tai näppäimet kuitenkin laitteen ohjeista." +msgstr "" +"Käytettävä näppäin vaihtelee ohjelmittain. Se on usein " +"CtrlF2. Katso oikea " +"näppäin tai näppäimet kuitenkin laitteen ohjeista." #. Tag: para #: preparing.xml:1638 @@ -2438,7 +2611,9 @@ msgstr "Etsi käynnistysjärjestystä muuttava toiminto." #, no-c-format msgid "" "Set the utility so that the SCSI ID of the CD drive is first on the list." -msgstr "Aseta käynnistysjärjestys siten, että romppuaseman SCSI ID on luettelossa ensimmäisenä." +msgstr "" +"Aseta käynnistysjärjestys siten, että romppuaseman SCSI ID on luettelossa " +"ensimmäisenä." #. Tag: para #: preparing.xml:1649 @@ -2446,7 +2621,10 @@ msgstr "Aseta käynnistysjärjestys siten, että romppuaseman SCSI ID on luettel msgid "" "Save your changes. Instructions on the screen tell you how to save the " "changes on your computer. Often, you must press F10." -msgstr "Tallenna muutokset. Näytöllä näkyvistä ohjeista ilmenee kuinka muutokset tallennetaan tällä tietokoneella. Usein on painettava näppäintä F10." +msgstr "" +"Tallenna muutokset. Näytöllä näkyvistä ohjeista ilmenee kuinka muutokset " +"tallennetaan tällä tietokoneella. Usein on painettava näppäintä F10." #. Tag: title #: preparing.xml:1663 @@ -2468,7 +2646,11 @@ msgid "" "speed. You should avoid that, and instead set it to, say, the lowest speed. " "If you get seek failed error messages, this may be " "your problem." -msgstr "Jotkin BIOSit (kuten Award BIOS) sallivat rompun nopeuden asettamisen automaattisesti. Tätä olisi vältettävä, ja asetettava nopeus esimerkiksi hitaimpaan arvoon. Jos tulee seek failed -virheitä, tämä asetus saataa olla syynä." +msgstr "" +"Jotkin BIOSit (kuten Award BIOS) sallivat rompun nopeuden asettamisen " +"automaattisesti. Tätä olisi vältettävä, ja asetettava nopeus esimerkiksi " +"hitaimpaan arvoon. Jos tulee seek failed -virheitä, " +"tämä asetus saataa olla syynä." #. Tag: title #: preparing.xml:1676 @@ -2484,7 +2666,12 @@ msgid "" "expanded 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 "Jos tietokoneessa on sekä jatkettua muistia (extended) että laajennettua muistia (expanded), tee asetukset niin, että jatkettua muistia on mahdollisimman paljon ja laajennettua muistia mahdollisimman vähän. Linux tarvitsee jatkettua muistia eikä voi käyttää laajennettua muistia." +msgstr "" +"Jos tietokoneessa on sekä jatkettua muistia (extended) " +"että laajennettua muistia (expanded), tee asetukset " +"niin, että jatkettua muistia on mahdollisimman paljon ja laajennettua " +"muistia mahdollisimman vähän. Linux tarvitsee jatkettua muistia eikä voi " +"käyttää laajennettua muistia." #. Tag: title #: preparing.xml:1687 @@ -2505,7 +2692,17 @@ msgid "" "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. ." -msgstr "Ota pois päältä kaikki BIOSin virustorjuntaominaisuudet. Jos tietokoneessa on virusten torjuntaan lisälaitekortti tai muu erikoislaite, varmista sen olevan pois käytöstä tai poista se koneesta kun GNU/Linux on käynnissä. Ne eivät ole yhteensopivia GNU/Linuxin kanssa; lisäksi tiedostojärjestelmän oikeuksien ja Linux-ytimen suojatun muistin ansiosta virukset ovat lähes tuntemattomia Haluttaessa voidaan käynnistyssektorin suojaus ottaa käyttöön asennuksen jälkeen. Tästä ei ole Linuxissa lisäturvaa mutta jos koneessa käytetään myös Windowsia se saattaa estää katastrofin. Pääkäynnistyslohkoon (MBR) ei ole mitään tarvetta kajotan sen jälkeen kun alkulatausohjelma on siihen asennettu. " +msgstr "" +"Ota pois päältä kaikki BIOSin virustorjuntaominaisuudet. Jos tietokoneessa " +"on virusten torjuntaan lisälaitekortti tai muu erikoislaite, varmista sen " +"olevan pois käytöstä tai poista se koneesta kun GNU/Linux on käynnissä. Ne " +"eivät ole yhteensopivia GNU/Linuxin kanssa; lisäksi tiedostojärjestelmän " +"oikeuksien ja Linux-ytimen suojatun muistin ansiosta virukset ovat lähes " +"tuntemattomia Haluttaessa voidaan käynnistyssektorin suojaus " +"ottaa käyttöön asennuksen jälkeen. Tästä ei ole Linuxissa lisäturvaa mutta " +"jos koneessa käytetään myös Windowsia se saattaa estää katastrofin. " +"Pääkäynnistyslohkoon (MBR) ei ole mitään tarvetta kajotan sen jälkeen kun " +"alkulatausohjelma on siihen asennettu. " #. Tag: title #: preparing.xml:1709 @@ -2526,7 +2723,17 @@ msgid "" "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 "Emolevy saattaa tarjota käyttöön varjomuistia (shadow RAM) tai BIOSin välimuistia (BIOS caching). Asetuksissa voi olla Video BIOS Shadow, C800-CBFF Shadow, jne. Ota pois käytöstä (Disable) kaikki varjomuistit. Varjomuisti nopeuttaa emolevyn ja joidenkin ohjainkorttien lukumuistin käyttöä. Linux ei käynnistyttyään käytä näitä lukumuisteja koska se käyttää omia nopeampia 32-bittiä ohjelmiaan eikä lukumuisteissa olevia 16-bittisiä ohjelmia. Varjomuistin ottaminen pois käytöstä saattaa vapauttaa osan muistista ohjelmien käyttöön tavallisena muistina. Varjomuistin pitäminen käytössä saattaa sotkea oheislaitteiden käyttöä Linuxissa." +msgstr "" +"Emolevy saattaa tarjota käyttöön varjomuistia " +"(shadow RAM) tai BIOSin välimuistia (BIOS caching). " +"Asetuksissa voi olla Video BIOS Shadow, C800-CBFF " +"Shadow, jne. Ota pois käytöstä (Disable) kaikki " +"varjomuistit. Varjomuisti nopeuttaa emolevyn ja joidenkin ohjainkorttien " +"lukumuistin käyttöä. Linux ei käynnistyttyään käytä näitä lukumuisteja koska " +"se käyttää omia nopeampia 32-bittiä ohjelmiaan eikä lukumuisteissa olevia 16-" +"bittisiä ohjelmia. Varjomuistin ottaminen pois käytöstä saattaa vapauttaa " +"osan muistista ohjelmien käyttöön tavallisena muistina. Varjomuistin " +"pitäminen käytössä saattaa sotkea oheislaitteiden käyttöä Linuxissa." #. Tag: title #: preparing.xml:1727 @@ -2541,7 +2748,10 @@ msgid "" "If your BIOS offers something like 15–16 MB Memory Hole, please disable that. Linux expects to find memory there if you have " "that much RAM." -msgstr "Jos BIOS-asetuksissa on jotain tämän tapaista: 15–16 MB Memory Hole, ota se pois käytöstä. Linux odottaa löytävänsä tuosta kohtaa muistia jos tietokoneessa on muistia noin paljon." +msgstr "" +"Jos BIOS-asetuksissa on jotain tämän tapaista: 15–16 MB Memory " +"Hole, ota se pois käytöstä. Linux odottaa löytävänsä tuosta kohtaa " +"muistia jos tietokoneessa on muistia noin paljon." #. Tag: para #: preparing.xml:1734 @@ -2554,7 +2764,14 @@ msgid "" "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 "Olemme saaneet ilmoituksen Intel Endeavor -emolevystä jossa on asetus LFB eli Linear Frame Buffer. Asetuksella on kaksi arvoa: Disabled ja 1 Megabyte. Käytä arvoa 1 Megabyte. Kun asetus oli Disabled, järjestelmä ei lukenut asennuslevykettä oikein, ja kaatui lopulta. Tätä kirjoitettaessa emme ymmärrä mitä oikein tapahtuu — se toimi tuolla asetuksella ja ilman sitä ei toiminut." +msgstr "" +"Olemme saaneet ilmoituksen Intel Endeavor -emolevystä jossa on asetus " +"LFB eli Linear Frame Buffer. Asetuksella on " +"kaksi arvoa: Disabled ja 1 Megabyte. Käytä " +"arvoa 1 Megabyte. Kun asetus oli Disabled, järjestelmä ei " +"lukenut asennuslevykettä oikein, ja kaatui lopulta. Tätä kirjoitettaessa " +"emme ymmärrä mitä oikein tapahtuu — se toimi tuolla asetuksella ja " +"ilman sitä ei toiminut." #. Tag: title #: preparing.xml:1750 @@ -2571,7 +2788,12 @@ msgid "" "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 "Jos emolevy osaa edistyneen virranhallinnan (Advanced Power Management), tee sen asetukset siten että APM säätelee virranhallintaa. Ota pois käytöstä doze, standby, suspend, nap ja sleep, ja ota pois kiintolevyn ajastettu pysäytys. Linux pystyy säätämään nämä tilat ja osaa tehdä virranhallinnan paremmin kuin BIOS." +msgstr "" +"Jos emolevy osaa edistyneen virranhallinnan (Advanced Power Management), tee " +"sen asetukset siten että APM säätelee virranhallintaa. Ota pois käytöstä " +"doze, standby, suspend, nap ja sleep, ja ota pois kiintolevyn ajastettu " +"pysäytys. Linux pystyy säätämään nämä tilat ja osaa tehdä virranhallinnan " +"paremmin kuin BIOS." #. Tag: title #: preparing.xml:1769 @@ -2592,7 +2814,17 @@ msgid "" "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 "Suoritinperheen &arch-title; koneet osaavat tavallisesti tehdä asetukset automaattisesti eikä laiteohjelmiston asetuksiin tarvitse koskea. Olisi kuitenkin varmistuttava käytettävän soveltuvia ROMmeja ja järjestelmän korjaustiedostoja. Macintoshilla suositellaan MacOS:n versiota >= 7.1 koska versiossa 7.0.1 on videoajureissa vika joka estää käynnistyslatainta poistamasta videokeskeytyksiä käytöstä, mistä syystä käynnistys jumittuu. BVM:n VMEbus-järjestelmissä olisi varmistuttava käytettävän käynnistys-ROMien versiota BVMBug G tai suurempi. BVMBug käynnistys-ROMit eivät kuulu BVM-järjestelmien vakiokokoonpanoon, mutta ovat pyynnöstä saatavilla BVM:ltä maksutta." +msgstr "" +"Suoritinperheen &arch-title; koneet osaavat tavallisesti tehdä asetukset " +"automaattisesti eikä laiteohjelmiston asetuksiin tarvitse koskea. Olisi " +"kuitenkin varmistuttava käytettävän soveltuvia ROMmeja ja järjestelmän " +"korjaustiedostoja. Macintoshilla suositellaan MacOS:n versiota >= 7.1 koska " +"versiossa 7.0.1 on videoajureissa vika joka estää käynnistyslatainta " +"poistamasta videokeskeytyksiä käytöstä, mistä syystä käynnistys jumittuu. " +"BVM:n VMEbus-järjestelmissä olisi varmistuttava käytettävän käynnistys-" +"ROMien versiota BVMBug G tai suurempi. BVMBug käynnistys-ROMit eivät kuulu " +"BVM-järjestelmien vakiokokoonpanoon, mutta ovat pyynnöstä saatavilla BVM:ltä " +"maksutta." #. Tag: title #: preparing.xml:1794 @@ -2609,7 +2841,11 @@ msgid "" "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 "Tavallisesti BIOS-asetusten muuttaminen suoritinperheen &arch-title; koneilla ei ole tarpeen (BIOS = OpenFirmware). PReP ja CHRP käyttävät OpenFirmwarea, mutta harmittavasti OpenFirmwaren käynnistamistapa vaihtelee valmistajittain. On luettava koneen mukana tullutta laitteiston ohjekirjaa." +msgstr "" +"Tavallisesti BIOS-asetusten muuttaminen suoritinperheen &arch-title; " +"koneilla ei ole tarpeen (BIOS = OpenFirmware). PReP ja CHRP käyttävät " +"OpenFirmwarea, mutta harmittavasti OpenFirmwaren käynnistamistapa vaihtelee " +"valmistajittain. On luettava koneen mukana tullutta laitteiston ohjekirjaa." #. Tag: para #: preparing.xml:1803 @@ -2621,7 +2857,13 @@ msgid "" "for these keystrokes after the chime, but the exact timing varies from model " "to model. See for more " "hints." -msgstr "Suoritinperheen &arch-title; Macintosheissa, OpenFirmware käynnistetään näppäilemällä Command option O F koneen käynnistyessä. Yleensä näppäimien painalluksia tarkistetaan kellon heläyksen jälkeen, mutta tämä vaihtelee malleittain. Katso osoitteesta lisää vinkkejä." +msgstr "" +"Suoritinperheen &arch-title; Macintosheissa, OpenFirmware käynnistetään " +"näppäilemällä Command option " +"O F koneen käynnistyessä. " +"Yleensä näppäimien painalluksia tarkistetaan kellon heläyksen jälkeen, mutta " +"tämä vaihtelee malleittain. Katso osoitteesta lisää vinkkejä." #. Tag: para #: preparing.xml:1812 @@ -2640,7 +2882,11 @@ msgstr "" "OpenFirmwaren kehote on tämän näköinen: \n" "ok\n" "0 >\n" -" Huomaa, että vanhemman mallisilla suoritinperheen &arch-title; Maceilla OpenFirmwaren oletuskonsoli ja joskus ainoa mahdollinen konsoli on sarjaportti (modeemiportti). Jos OpenFirmware käynnistetään näissä koneissa, näkyy vain musta ruutu. Tällöin OpenFirmwarea on käytettävä modeemiporttiin yhdistetystä toisesta koneesta pääteohjelmalla." +" Huomaa, että vanhemman mallisilla " +"suoritinperheen &arch-title; Maceilla OpenFirmwaren oletuskonsoli ja joskus " +"ainoa mahdollinen konsoli on sarjaportti (modeemiportti). Jos OpenFirmware " +"käynnistetään näissä koneissa, näkyy vain musta ruutu. Tällöin OpenFirmwarea " +"on käytettävä modeemiporttiin yhdistetystä toisesta koneesta pääteohjelmalla." #. Tag: para #: preparing.xml:1825 @@ -2654,7 +2900,15 @@ msgid "" "SystemDisk2.3.1.smi.bin\">. After unpacking the utility in MacOS, " "and launching it, select the Save button to have the " "firmware patches installed to nvram." -msgstr "OldWorld Beige G3 -koneilla OpenFirmware on rikki, OF:n versiot 2.0f1 ja 2.4. Nämä koneet luultavimmin eivät osaa käynnistyä kiintolevyltä päivittämättömällä laiteohjelmistolla. Apuohjelman System Disk 2.3.1 mukana on korjauspäivitys, se on saatavilla Applelta osoitteesta . Kun apuohjelma on purettu MacOS:ssä ja käynnistetty, valitaan Save button jolloin laiteohjelmiston korjaukset asennetaan nvram:iin." +msgstr "" +"OldWorld Beige G3 -koneilla OpenFirmware on rikki, OF:n versiot 2.0f1 ja " +"2.4. Nämä koneet luultavimmin eivät osaa käynnistyä kiintolevyltä " +"päivittämättömällä laiteohjelmistolla. Apuohjelman System Disk " +"2.3.1 mukana on korjauspäivitys, se on saatavilla Applelta " +"osoitteesta . Kun apuohjelma on purettu " +"MacOS:ssä ja käynnistetty, valitaan Save button " +"jolloin laiteohjelmiston korjaukset asennetaan nvram:iin." #. Tag: title #: preparing.xml:1845 @@ -2671,7 +2925,12 @@ msgid "" "architecture, although much nicer. The Sun boot PROMs have a built-in forth " "interpreter which lets you do quite a number of things with your machine, " "such as diagnostics and simple scripts." -msgstr "OpenBoot toteuttaa perustoiminnallisuuden suoritinperheen &arch-title; tietokoneen käynnistämiseen. Tämä on samantapaista kuin BIOS:n tehtävät x86-suoritinperheessä, vaikkakin paljon hienommin tehty. Sunin käynnistys-PROMeissa on mukana forth-tulkki. Sen avulla voi tehdä monenlaisia jutskia kuten vianmääritystä ja yksinkertaisia komentosarjoja." +msgstr "" +"OpenBoot toteuttaa perustoiminnallisuuden suoritinperheen &arch-title; " +"tietokoneen käynnistämiseen. Tämä on samantapaista kuin BIOS:n tehtävät x86-" +"suoritinperheessä, vaikkakin paljon hienommin tehty. Sunin käynnistys-" +"PROMeissa on mukana forth-tulkki. Sen avulla voi tehdä monenlaisia jutskia " +"kuten vianmääritystä ja yksinkertaisia komentosarjoja." #. Tag: para #: preparing.xml:1855 @@ -2684,7 +2943,15 @@ msgid "" "ok or >. It is preferred to " "have the ok prompt. So if you get the old style " "prompt, hit the n key to get the new style prompt." -msgstr "Käynnistyskehotteeseen pääsee pitämällä näppäintä Stop pohjassa (vanhoissa type 4 -näppäimistöissä käytetään L1-näppäintä. Jos on PC-näppäimistön sovitin, käytetään näppäintä Break) ja painetaan näppäintä A. Käynnistys-PROM näyttää kehotteen, joko ok tai >. Suositellaan kehotteen ok käyttämistä. Jos näkyy vanhanmallinen kehote, saadaan näppäintä n painamalla uudenmallinen." +msgstr "" +"Käynnistyskehotteeseen pääsee pitämällä näppäintä Stop " +"pohjassa (vanhoissa type 4 -näppäimistöissä käytetään L1-" +"näppäintä. Jos on PC-näppäimistön sovitin, käytetään näppäintä " +"Break) ja painetaan näppäintä A. " +"Käynnistys-PROM näyttää kehotteen, joko ok tai " +">. Suositellaan kehotteen ok käyttämistä. Jos näkyy vanhanmallinen kehote, saadaan näppäintä " +"n painamalla uudenmallinen." #. Tag: para #: preparing.xml:1867 @@ -2694,7 +2961,11 @@ msgid "" "Minicom, use Ctrl-A F, with cu, hit Enter, " "then type %~break. Consult the documentation of your " "terminal emulator if you are using a different program." -msgstr "Jos käytetään sarjapäätettä konsolina, on tietokoneelle lähetettävä break. Minicomin käyttäjä näppäilee Ctrl-A F, cu:n käyttäjä Enter, sitten kirjoitetaan %~break. Jos käytät jotain muuta pääteohjelmaa, lue sen ohjeet." +msgstr "" +"Jos käytetään sarjapäätettä konsolina, on tietokoneelle lähetettävä break. " +"Minicomin käyttäjä näppäilee Ctrl-A F, cu:n käyttäjä " +"Enter, sitten kirjoitetaan %~break. " +"Jos käytät jotain muuta pääteohjelmaa, lue sen ohjeet." #. Tag: para #: preparing.xml:1880 @@ -2707,7 +2978,14 @@ msgid "" "will vary a bit, depending on what version of OpenBoot you have. More " "information about OpenBoot can be found in the Sun OpenBoot Reference." -msgstr "OpenBootilla voidaan määrittää käynnistyslaite ja myös vaihtaa oletuskäynnistyslaitetta. On kuitenkin tiedettävä joitakin yksityiskohtia OpenBootin laitenimistä: ne ovat hyvin erilainen kuin Linuxin käyttämät laitenimet, joita kerrotaan kohdassa . Lisäksi komento on hieman erilainen eri OpenBootin versioissa. Lisää tietoa OpenBootista löytyy ohjeesta Sun OpenBoot Reference." +msgstr "" +"OpenBootilla voidaan määrittää käynnistyslaite ja myös vaihtaa " +"oletuskäynnistyslaitetta. On kuitenkin tiedettävä joitakin yksityiskohtia " +"OpenBootin laitenimistä: ne ovat hyvin erilainen kuin Linuxin käyttämät " +"laitenimet, joita kerrotaan kohdassa . " +"Lisäksi komento on hieman erilainen eri OpenBootin versioissa. Lisää tietoa " +"OpenBootista löytyy ohjeesta Sun OpenBoot " +"Reference." #. Tag: para #: preparing.xml:1890 @@ -2732,11 +3010,25 @@ msgid "" "devices. For full information, whatever your revision, see the Sun OpenBoot Reference." msgstr "" -"Uusilla versioilla käytetään tavallisesti OpenBootilla laitenimiä kuten floppy, cdrom, net, disk, tai disk2. Nimillä on ilmeinen merkityksensä; net tarkoittaa käynnistämistä verkosta. Lisäksi laitenimi voi määrittää levyltä tietyn osion, kuten disk2:a jolla käynnistetään levyn disk2 ensimmäiseltä osiolta. Tässä on OpenBootin kokonaisen laitenimen malli \n" +"Uusilla versioilla käytetään tavallisesti OpenBootilla laitenimiä kuten " +"floppy, cdrom, net, " +"disk, tai disk2. Nimillä on ilmeinen " +"merkityksensä; net tarkoittaa käynnistämistä verkosta. " +"Lisäksi laitenimi voi määrittää levyltä tietyn osion, kuten disk2:a jolla käynnistetään levyn disk2 ensimmäiseltä osiolta. Tässä on " +"OpenBootin kokonaisen laitenimen malli \n" "driver-name@\n" "unit-address:\n" "device-arguments\n" -". OpenBootin vanhemmissa versioiossa laitteiden nimeäminen menee hieman eri tavalla: levykeaseman nimi on /fd, ja SCSI-levylaitteiden nimet ovat muotoa sd(controller, disk-target-id, disk-lun). Uusien OpenBootin versioiden komento show-devs näyttää kätevästi ne laitteet joiden asetukset on tehty. Kaikki tiedot kaikista versioista löytyvät oppaaasta Sun OpenBoot Reference." +". OpenBootin vanhemmissa versioiossa laitteiden " +"nimeäminen menee hieman eri tavalla: levykeaseman nimi on /fd, ja SCSI-levylaitteiden nimet ovat muotoa sd" +"(controller, disk-target-id, disk-lun). Uusien " +"OpenBootin versioiden komento show-devs näyttää " +"kätevästi ne laitteet joiden asetukset on tehty. Kaikki tiedot kaikista " +"versioista löytyvät oppaaasta Sun OpenBoot " +"Reference." #. Tag: para #: preparing.xml:1913 @@ -2755,7 +3047,17 @@ msgid "" "# echo disk1:1 > /proc/openprom/options/boot-device\n" " and under Solaris:" msgstr "" -"Käynnistys tietyltä laitteelta tapahtuu komennolla boot device. Laitteesta tehdään oletuskäynnistyslaite komennolla setenv. Muutettavan muuttujan nimi kuitenkin vaihtelee OpenBootin versioiden mukaan. OpenBootin versioissa 1.x käytetään komentoa setenv boot-from device. Uudemmissa OpenBootin versioissa komento on setenv boot-device device. Huomaa, että nämä asetukset voi tehdä myös Solariksen komennolla eeprom, tai muokkaamalla sopivia tiedostoja hakemistossa /proc/openprom/options/, Linuxissa esimerkiksi: \n" +"Käynnistys tietyltä laitteelta tapahtuu komennolla boot " +"device. Laitteesta tehdään " +"oletuskäynnistyslaite komennolla setenv. Muutettavan " +"muuttujan nimi kuitenkin vaihtelee OpenBootin versioiden mukaan. OpenBootin " +"versioissa 1.x käytetään komentoa setenv boot-from " +"device. Uudemmissa OpenBootin " +"versioissa komento on setenv boot-device device. Huomaa, että nämä asetukset voi tehdä myös " +"Solariksen komennolla eeprom, tai muokkaamalla sopivia " +"tiedostoja hakemistossa /proc/openprom/options/, " +"Linuxissa esimerkiksi: \n" "# echo disk1:1 > /proc/openprom/options/boot-device\n" " ja Solariksessa:" @@ -2783,7 +3085,15 @@ msgid "" "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 "&debian;in asentamiseksi suoritinperheen &arch-title; koneelle tai zSeries-koneelle on järjestelmään ensimmäiseksi käynnistettävä ydin. Tämän laitealustan käynnistystapa on olennaisesti muista poikkeava, erityisesti se on erilainen kuin PC-koneissa: levykeasemia ei ole lainkaan. Laitealustan parissa työskennellessä huomaa toisenkin ison eron: enimmäkseen (tai aina) työskennellään etäkäyttönä telnetin tapaisen pääteohjelman tai selaimen avulla. Tämä johtuu erikoisesta järjestelmäarkkitehtuurista jossa 3215/3270-konsoli on rivipohjainen eikä merkkipohjainen." +msgstr "" +"&debian;in asentamiseksi suoritinperheen &arch-title; koneelle tai zSeries-" +"koneelle on järjestelmään ensimmäiseksi käynnistettävä ydin. Tämän " +"laitealustan käynnistystapa on olennaisesti muista poikkeava, erityisesti se " +"on erilainen kuin PC-koneissa: levykeasemia ei ole lainkaan. Laitealustan " +"parissa työskennellessä huomaa toisenkin ison eron: enimmäkseen (tai aina) " +"työskennellään etäkäyttönä telnetin tapaisen pääteohjelman tai selaimen " +"avulla. Tämä johtuu erikoisesta järjestelmäarkkitehtuurista jossa 3215/3270-" +"konsoli on rivipohjainen eikä merkkipohjainen." #. Tag: para #: preparing.xml:1955 @@ -2796,7 +3106,14 @@ msgid "" "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 "Tällä laitealustalla Linux toimii joko suoraan raudalla, niin kutsutussa LPAR:ssa (Logical Partition), tai VM-järjestelmän tarjoamassa virtuaalikoneessa. Kaikilla järjestelmillä voidaan käynnistää nauhalta; muutakin käynnistysmediaa voi käyttää, mutta muita ei yleensä ole käytettävissä. Esimerkiksi voidaan käyttää virtuaalikoneen virtuaalista kortinlukijaa, tai käynnistää LPAR:n HMC:ltä (Hardware Management Console) jos HMC ja tämä toiminto on käytettävissä." +msgstr "" +"Tällä laitealustalla Linux toimii joko suoraan raudalla, niin kutsutussa " +"LPAR:ssa (Logical Partition), tai VM-järjestelmän tarjoamassa " +"virtuaalikoneessa. Kaikilla järjestelmillä voidaan käynnistää nauhalta; " +"muutakin käynnistysmediaa voi käyttää, mutta muita ei yleensä ole " +"käytettävissä. Esimerkiksi voidaan käyttää virtuaalikoneen virtuaalista " +"kortinlukijaa, tai käynnistää LPAR:n HMC:ltä (Hardware Management Console) " +"jos HMC ja tämä toiminto on käytettävissä." #. Tag: para #: preparing.xml:1965 @@ -2811,7 +3128,16 @@ msgid "" "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 "Ennen varsinaisen asennuksen aloittamista, on tehtävä joitakin suunnittelu- ja valmisteluvaiheita. IBM:ltä on saatavilla ohjeet koko prosessista, ts. miten asennustaltio valmistetaan ja miten taltiolta käynnistetään. Tuon tiedon toistaminen tässä ei ole mahdollista eikä tarpeen. Tässä kuitenkin kerrotaan minkälaisia nimenomaan Debianiin liittyviä tietoja tarvitaan ja mistä ne löytää. Molempien tietolähteiden avulla on laite ja asennustaltio valmisteltava ja käynnistettävä taltiolta. Kun ruudulla näkyy istunnon tervetulotoivotus, jatketaan tämän ohjeen seuraamista Debianin asennuksen parissa." +msgstr "" +"Ennen varsinaisen asennuksen aloittamista, on tehtävä joitakin suunnittelu- " +"ja valmisteluvaiheita. IBM:ltä on saatavilla ohjeet koko prosessista, ts. " +"miten asennustaltio valmistetaan ja miten taltiolta käynnistetään. Tuon " +"tiedon toistaminen tässä ei ole mahdollista eikä tarpeen. Tässä kuitenkin " +"kerrotaan minkälaisia nimenomaan Debianiin liittyviä tietoja tarvitaan ja " +"mistä ne löytää. Molempien tietolähteiden avulla on laite ja asennustaltio " +"valmisteltava ja käynnistettävä taltiolta. Kun ruudulla näkyy istunnon " +"tervetulotoivotus, jatketaan tämän ohjeen seuraamista Debianin asennuksen " +"parissa." #. Tag: title #: preparing.xml:1982 @@ -2828,7 +3154,12 @@ msgid "" "and chapter 3.2 of the Linux for IBM eServer zSeries and &arch-title;: " "Distributions Redbook on how to set up an LPAR for Linux." -msgstr "Lue luvusta viisi kirjasta Linux for &arch-title; Redbook ja luvusta 3.2 kirjasta Linux for IBM eServer zSeries and &arch-title;: Distributions Redbook ohjeet kuinka LPAR tehdään Linuxille." +msgstr "" +"Lue luvusta viisi kirjasta Linux for &arch-title; Redbook ja " +"luvusta 3.2 kirjasta Linux for IBM eServer zSeries and &arch-title;: " +"Distributions Redbook ohjeet kuinka LPAR tehdään Linuxille." #. Tag: title #: preparing.xml:1997 @@ -2845,7 +3176,12 @@ msgid "" "and chapter 3.1 of the Linux for IBM eServer zSeries and &arch-title;: " "Distributions Redbook on how to set up a VM guest for running Linux." -msgstr "Lue luvusta 6 kirjasta Linux for &arch-title; Redbook ja luvusta 3.1 kirjasta Linux for IBM eServer zSeries and &arch-title;: Distributions Redbook ohjeet kuinka VM vieras tehdään Linuxille." +msgstr "" +"Lue luvusta 6 kirjasta Linux for &arch-title; Redbook ja luvusta " +"3.1 kirjasta Linux for IBM eServer zSeries and &arch-title;: " +"Distributions Redbook ohjeet kuinka VM vieras tehdään Linuxille." #. Tag: para #: preparing.xml:2009 @@ -2855,7 +3191,11 @@ msgid "" "directory to your CMS disk. Be sure to transfer kernel.debian and initrd.debian in binary mode with a fixed " "record length of 80 characters." -msgstr "Kaikki tiedostot alihakemistosta generic on kopioitava CMS-levylle. Muista kopioida kernel.debian ja initrd.debian binäärimuodossa kiinteällä 80 merkin tietueen pituudella." +msgstr "" +"Kaikki tiedostot alihakemistosta generic on kopioitava " +"CMS-levylle. Muista kopioida kernel.debian ja " +"initrd.debian binäärimuodossa kiinteällä 80 merkin " +"tietueen pituudella." #. Tag: title #: preparing.xml:2021 @@ -2871,7 +3211,11 @@ msgid "" "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 "Mikäli Internet-yhteyttä ei ole käytettävissä (suoraan tai www-sovelluskäytävän kautta), on luotava paikallinen asennuspalvelin joka on käytettävissä S/390-koneesta. Tässä palvelimessa on kaikki asennettavat paketit ja niiden on oltava käytettävissä NFS:llä, HTTP:llä tai FTP:llä." +msgstr "" +"Mikäli Internet-yhteyttä ei ole käytettävissä (suoraan tai www-" +"sovelluskäytävän kautta), on luotava paikallinen asennuspalvelin joka on " +"käytettävissä S/390-koneesta. Tässä palvelimessa on kaikki asennettavat " +"paketit ja niiden on oltava käytettävissä NFS:llä, HTTP:llä tai FTP:llä." #. Tag: para #: preparing.xml:2031 @@ -2881,7 +3225,11 @@ msgid "" "&debian; mirror, but only the s390 and architecture-independent files are " "required. You can also copy the contents of all installation CDs into such a " "directory tree." -msgstr "Asennuspalvelimeen on kopioitava jonkin &debian;in asennuspalvelimen tarkka hakemistorakenne, mutta vain s390:n tiedostot ja suoritinperheestä riippumattomat tiedostot tarvitaan. Kaikkien asennusromppujen sisältö voidaan myös kopioida tuollaiseen hakemistopuuhun." +msgstr "" +"Asennuspalvelimeen on kopioitava jonkin &debian;in asennuspalvelimen tarkka " +"hakemistorakenne, mutta vain s390:n tiedostot ja suoritinperheestä " +"riippumattomat tiedostot tarvitaan. Kaikkien asennusromppujen sisältö " +"voidaan myös kopioida tuollaiseen hakemistopuuhun." #. Tag: emphasis #: preparing.xml:2040 @@ -2906,7 +3254,14 @@ msgid "" "gcc 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 "Useat käyttäjät ovat yrittäneet käyttää 90 MHz suoritintaan 100 MHz taajuudella, jne. Joskus se toimii, mutta riippuu lämpötilasta ja muista tekijöitä ja voi oikeasti vahingoittaa laitteistoa. Yksi tämän ohjeen kirjoittajista ylikellotti tietokonettaan yli vuoden, ja sitten kone alkoi keskeyttämään komennon gcc odottamattomalla signaalilla käännettäessä käyttöjärjestelmän ydintä. Suorittimen kellotaajuuden pudottaminen takaisin nimellisarvoonsa korjasi vian." +msgstr "" +"Useat käyttäjät ovat yrittäneet käyttää 90 MHz suoritintaan 100 MHz " +"taajuudella, jne. Joskus se toimii, mutta riippuu lämpötilasta ja muista " +"tekijöitä ja voi oikeasti vahingoittaa laitteistoa. Yksi tämän ohjeen " +"kirjoittajista ylikellotti tietokonettaan yli vuoden, ja sitten kone alkoi " +"keskeyttämään komennon gcc odottamattomalla signaalilla " +"käännettäessä käyttöjärjestelmän ydintä. Suorittimen kellotaajuuden " +"pudottaminen takaisin nimellisarvoonsa korjasi vian." #. Tag: para #: preparing.xml:2057 @@ -2918,7 +3273,14 @@ msgid "" "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 " "gcc dying from an unexpected signal." -msgstr "gcc-käännin on usein ensimmäinen viallisten muistikampojen (tai muiden satunnaisesti tietoja muuttavien laitevikojen) kaatama sovellus, koska se rakentaan keskusmuistiin valtavia tietorakenteita joita kuljetaan ristiin rastiin jatkuvasti. Näissä tietorakenteissa oleva virhe saa kääntimen suorittamaan kelvottoman käskyn tai käyttämään muistiosoitetta jota ei ole olemassa. Tästä on oireena gcc:n kaatuminen odottamattomaan signaaliin." +msgstr "" +"gcc-käännin on usein ensimmäinen viallisten " +"muistikampojen (tai muiden satunnaisesti tietoja muuttavien laitevikojen) " +"kaatama sovellus, koska se rakentaan keskusmuistiin valtavia tietorakenteita " +"joita kuljetaan ristiin rastiin jatkuvasti. Näissä tietorakenteissa oleva " +"virhe saa kääntimen suorittamaan kelvottoman käskyn tai käyttämään " +"muistiosoitetta jota ei ole olemassa. Tästä on oireena gcc:n kaatuminen odottamattomaan signaaliin." #. Tag: para #: preparing.xml:2067 @@ -2929,38 +3291,33 @@ msgid "" "Amiga users may need to exclude RAM using a booter memfile. FIXME: more description of this needed. " -msgstr "Atari TT RAM -muistikortit ovat Linuxissa pahamaineisia muistivikojen pesiä; mikäli ilmenee outoja pulmia, yritä ajaa ainakin ydin ST-RAM:sta. Amigan käyttäjät saattavat joutua rajaamaan pois muistia booter memfileä käyttämällä. FIXME: more description of this needed. " +msgstr "" +"Atari TT RAM -muistikortit ovat Linuxissa pahamaineisia muistivikojen pesiä; " +"mikäli ilmenee outoja pulmia, yritä ajaa ainakin ydin ST-RAM:sta. Amigan " +"käyttäjät saattavat joutua rajaamaan pois muistia booter memfileä " +"käyttämällä. FIXME: more description " +"of this needed. " #. Tag: para #: preparing.xml:2079 #, 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 " -"." -msgstr "Parhaat emolevyt tukevat pariteettimuistia ja osaavat oikeasti kertoa jos muistissa on yhden bitin virhe. Harmittavasti ne eivät osaa korjata virhettä, useimmiten kaatuen heti muistivirheestä ilmoitettuaan. Silti on parempi saada tietää muistiviasta kuin antaa muistin kaikessa hiljaisuudessa lisäillä virheitä tietoihin. Niinpä parhaissa järjestelmissä on emolevy joka tukee pariteettimuistia ja oikeaa pariteettia tukevia muistikampoja; katso ." - -#. Tag: para -#: preparing.xml:2090 -#, 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 "Jos koneessa on oikeaa pariteettia tukevaa muistia ja emolevy osaa sitä käyttää, varmistu että emolevy on BIOS:ssa asetettu tekemään keskeytys muistin pariteettivirheistä." +msgstr "" +"Jos koneessa on oikeaa pariteettia tukevaa muistia ja emolevy osaa sitä " +"käyttää, varmistu että emolevy on BIOS:ssa asetettu tekemään keskeytys " +"muistin pariteettivirheistä." #. Tag: title -#: preparing.xml:2098 +#: preparing.xml:2087 #, no-c-format msgid "The Turbo Switch" msgstr "Turbokytkin" #. Tag: para -#: preparing.xml:2099 +#: preparing.xml:2088 #, no-c-format msgid "" "Many systems have a turbo switch that controls the " @@ -2970,16 +3327,22 @@ msgid "" "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 "Useissa koneissa on turbo-kytkin joka säätää suorittimen nopeutta. Valitse suurempi nopeus. Jos BIOS:ssa voi ottaa pois käytöstä turbokytkimen ohjelmallisen käytön, (tai software control of CPU speed), tee niin ja lukitse järjestelmä suurempaan nopeuteen. Olemme saaneet yhden ilmoituksen järjestelmästä, jossa Linux tunnistaessaan laitteistoa vahingossa muuttaa turbokytkintä ohjelmallisesti." +msgstr "" +"Useissa koneissa on turbo-kytkin joka säätää " +"suorittimen nopeutta. Valitse suurempi nopeus. Jos BIOS:ssa voi ottaa pois " +"käytöstä turbokytkimen ohjelmallisen käytön, (tai software control of CPU " +"speed), tee niin ja lukitse järjestelmä suurempaan nopeuteen. Olemme saaneet " +"yhden ilmoituksen järjestelmästä, jossa Linux tunnistaessaan laitteistoa " +"vahingossa muuttaa turbokytkintä ohjelmallisesti." #. Tag: title -#: preparing.xml:2112 +#: preparing.xml:2101 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "Cyrix-suorittimet ja levykevirheet" #. Tag: para -#: preparing.xml:2113 +#: preparing.xml:2102 #, no-c-format msgid "" "Many users of Cyrix CPUs have had to disable the cache in their systems " @@ -2987,52 +3350,69 @@ msgid "" "you have to do this, be sure to re-enable your cache when you are finished " "with installation, as the system runs much slower with " "the cache disabled." -msgstr "Useiden Cyrixin suorittimen käyttäjien on otettava järjestelmän välimuisti pois käytöstä asennuksen ajaksi, koska muuten tulee levykevirheitä. Jos joudut näin tekemään, muista ottaa välimuisti taas käyttöön kun asennus on valmis, sillä järjestelmän nopeus on paljon hitaampi jos välimuisti ei ole käytössä." +msgstr "" +"Useiden Cyrixin suorittimen käyttäjien on otettava järjestelmän välimuisti " +"pois käytöstä asennuksen ajaksi, koska muuten tulee levykevirheitä. Jos " +"joudut näin tekemään, muista ottaa välimuisti taas käyttöön kun asennus on " +"valmis, sillä järjestelmän nopeus on paljon hitaampi " +"jos välimuisti ei ole käytössä." #. Tag: para -#: preparing.xml:2121 +#: preparing.xml:2110 #, no-c-format msgid "" "We don't think this is necessarily the fault of the Cyrix CPU. It may be " "something that Linux can work around. We'll continue to look into the " "problem. For the technically curious, we suspect a problem with the cache " "being invalid after a switch from 16-bit to 32-bit code." -msgstr "Mielestämme tämä ei välttämättä ole Cyrixin suorittimen vika. Kyseessä voi olla vika jonka Linux voisi kiertää. Jatkamme vian tutkimista. Tekniikasta kiinnostuneille kerrottakoon epäiltynä olevan välimuistin määrittelemätön tila kun on vaihdettu 16-bittisestä 32-bittiseen tilaan." +msgstr "" +"Mielestämme tämä ei välttämättä ole Cyrixin suorittimen vika. Kyseessä voi " +"olla vika jonka Linux voisi kiertää. Jatkamme vian tutkimista. Tekniikasta " +"kiinnostuneille kerrottakoon epäiltynä olevan välimuistin määrittelemätön " +"tila kun on vaihdettu 16-bittisestä 32-bittiseen tilaan." #. Tag: title -#: preparing.xml:2131 +#: preparing.xml:2120 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "Oheislaitteiden asetukset" #. Tag: para -#: preparing.xml:2132 +#: preparing.xml:2121 #, no-c-format msgid "" "You may have to change some settings or jumpers on your computer's " "peripheral cards. Some cards have setup menus, while others rely on jumpers. " "This document cannot hope to provide complete information on every hardware " "device; what it hopes to provide is useful tips." -msgstr "Tietokoneen lisälaitekorttien asetuksia tai siltaimia voi joutua muuttamaan. Joillakin korteilla on asetusvalikko, kun toiset luottavat siltaimiin. Tämä ohje ei voi toivoakaan sisältävänsä täydelliset tiedot kaikista oheislaitteesta; tarkoitus on kertoa hyödyllisiä vinkkejä." +msgstr "" +"Tietokoneen lisälaitekorttien asetuksia tai siltaimia voi joutua muuttamaan. " +"Joillakin korteilla on asetusvalikko, kun toiset luottavat siltaimiin. Tämä " +"ohje ei voi toivoakaan sisältävänsä täydelliset tiedot kaikista " +"oheislaitteesta; tarkoitus on kertoa hyödyllisiä vinkkejä." #. Tag: para -#: preparing.xml:2139 +#: preparing.xml:2128 #, no-c-format msgid "" "If any cards provide mapped memory, 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 "Jos jokin kortti tarjoaa semmoista kuin mapped memory, muistiosoitteen olisi oltava välillä 0xA0000 – 0xFFFFF (640K – alle 1 Mt) tai osoitteessa joka on ainakin 1 Mt suurempi kuin laitteiston keskusmuistin koko." +msgstr "" +"Jos jokin kortti tarjoaa semmoista kuin mapped memory, " +"muistiosoitteen olisi oltava välillä 0xA0000 – 0xFFFFF (640K – " +"alle 1 Mt) tai osoitteessa joka on ainakin 1 Mt suurempi kuin laitteiston " +"keskusmuistin koko." #. Tag: title -#: preparing.xml:2150 +#: preparing.xml:2139 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "Tuki USB BIOS:lle ja näppäimistöille" #. Tag: para -#: preparing.xml:2151 +#: preparing.xml:2140 #, no-c-format msgid "" "If you have no AT-style keyboard and only a USB model, you may need to " @@ -3042,30 +3422,39 @@ msgid "" "if your keyboard does not respond. Consult your main board manual and look " "in the BIOS for Legacy keyboard emulation or USB " "keyboard support options." -msgstr "Jos käytettävissä ei ole AT-tyylistä näppäimistöä vaan USB-malli, on ehkä otettava käyttöön AT-näppäimistön emulointi BIOS-asetuksissa. Tee tämä vain jos asennusjärjestelmä ei osaa käyttää näppäimistöä USB-tilassa. Päinvastainen tilanne on joissakin järjestelmissä (erityisesti läppäreissä), joissa on ehkä poistettava käytöstä legacy USB support jos näppäimistö ei toimi. Tutki emolevyn käsikirjaa ja etsi BIOS:sta kohtia Legacy keyboard emulation tai USB keyboard support." +msgstr "" +"Jos käytettävissä ei ole AT-tyylistä näppäimistöä vaan USB-malli, on ehkä " +"otettava käyttöön AT-näppäimistön emulointi BIOS-asetuksissa. Tee tämä vain " +"jos asennusjärjestelmä ei osaa käyttää näppäimistöä USB-tilassa. " +"Päinvastainen tilanne on joissakin järjestelmissä (erityisesti läppäreissä), " +"joissa on ehkä poistettava käytöstä legacy USB support jos näppäimistö ei " +"toimi. Tutki emolevyn käsikirjaa ja etsi BIOS:sta kohtia Legacy " +"keyboard emulation tai USB keyboard support." #. Tag: title -#: preparing.xml:2164 +#: preparing.xml:2153 #, no-c-format msgid "More than 64 MB RAM" msgstr "Muistia enemmän kuin 64 Mt" #. Tag: para -#: preparing.xml:2165 +#: preparing.xml:2154 #, no-c-format msgid "" "The Linux Kernel cannot always detect what amount of RAM you have. If this " "is the case please look at ." -msgstr "Linux-ydin ei aina osaa tunnista muistin määrää. Jos näin käy, katso ." +msgstr "" +"Linux-ydin ei aina osaa tunnista muistin määrää. Jos näin käy, katso ." #. Tag: title -#: preparing.xml:2174 +#: preparing.xml:2163 #, no-c-format msgid "Display visibility on OldWorld Powermacs" msgstr "Näyttöpulmia OldWorld Powermaceissa" #. Tag: para -#: preparing.xml:2175 +#: preparing.xml:2164 #, no-c-format msgid "" "Some OldWorld Powermacs, most notably those with the control " @@ -3077,4 +3466,29 @@ msgid "" "black after booting the installer instead of showing you the user interface, " "try changing your display settings under MacOS to use 256 colors instead of " "thousands or millions." -msgstr "Jotkin OldWorld Powermacit, erityisesti ne joissa on control-näyttöajuri mutta mahdollisesti muutkin, eivät ehkä tee värikarttaa joka luotettavasti näyttäisi värit Linuxissa kun värisyvyys on enemmän kuin 256 väriä. Jos tämmöistä ilmenee näytöllä kun järjestelmä on käynnistetty uudelleen (joskus näytöllä näkyy kuva ja teksti, joskus ei mitään) tai jos näyttö menee mustaksi asentimen käynnistyksen jälkeen eikä käyttöliittymää näy, yritä muuttaa näytön värisyvyydeksi 256 väriä eikä tuhansia tai miljoonia." +msgstr "" +"Jotkin OldWorld Powermacit, erityisesti ne joissa on control-" +"näyttöajuri mutta mahdollisesti muutkin, eivät ehkä tee värikarttaa joka " +"luotettavasti näyttäisi värit Linuxissa kun värisyvyys on enemmän kuin 256 " +"väriä. Jos tämmöistä ilmenee näytöllä kun järjestelmä on käynnistetty " +"uudelleen (joskus näytöllä näkyy kuva ja teksti, joskus ei mitään) tai jos " +"näyttö menee mustaksi asentimen käynnistyksen jälkeen eikä käyttöliittymää " +"näy, yritä muuttaa näytön värisyvyydeksi 256 väriä eikä tuhansia tai miljoonia." + +#~ 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 ." +#~ msgstr "" +#~ "Parhaat emolevyt tukevat pariteettimuistia ja osaavat oikeasti kertoa jos " +#~ "muistissa on yhden bitin virhe. Harmittavasti ne eivät osaa korjata " +#~ "virhettä, useimmiten kaatuen heti muistivirheestä ilmoitettuaan. Silti on " +#~ "parempi saada tietää muistiviasta kuin antaa muistin kaikessa " +#~ "hiljaisuudessa lisäillä virheitä tietoihin. Niinpä parhaissa " +#~ "järjestelmissä on emolevy joka tukee pariteettimuistia ja oikeaa " +#~ "pariteettia tukevia muistikampoja; katso ." diff --git a/po/fi/using-d-i.po b/po/fi/using-d-i.po index 9995813b1..2f7a4ef79 100644 --- a/po/fi/using-d-i.po +++ b/po/fi/using-d-i.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: Installation Guide using-d-i\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-12-15 17:30+0200\n" "Last-Translator: Tapio Lehtonen \n" "Language-Team: Finnish \n" @@ -3664,14 +3664,13 @@ msgstr "" #. Tag: para #: using-d-i.xml:2302 -#, no-c-format +#, fuzzy, 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 fdisk /" "mbr 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 ." +"Debian!" msgstr "" "Jos Windows 9x:n (tai MS-DOS:n) käynnistäminen ei enää onnistu tämän " "jälkeen, on käytettävä Windows 9x:n (tai MS-DOS:n) käynnistyslevykettä ja " @@ -3681,13 +3680,13 @@ msgstr "" "kohdasta ." #. Tag: title -#: using-d-i.xml:2319 +#: using-d-i.xml:2318 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "Asennetaan käynnistyslatain ELILO kiintolevylle" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2320 #, no-c-format msgid "" "The &architecture; boot loader is called elilo. It is modeled " @@ -3715,7 +3714,7 @@ msgstr "" "käynnistämään Linux-ytimen." #. Tag: para -#: using-d-i.xml:2337 +#: using-d-i.xml:2336 #, no-c-format msgid "" "The elilo configuration and installation is done as the last " @@ -3732,13 +3731,13 @@ msgstr "" "tiedostojärjestelmä." #. Tag: title -#: using-d-i.xml:2349 +#: using-d-i.xml:2348 #, no-c-format msgid "Choose the correct partition!" msgstr "Valitse oikea levyosio!" #. Tag: para -#: using-d-i.xml:2351 +#: using-d-i.xml:2350 #, no-c-format msgid "" "The criteria for selecting a partition is that it is FAT format filesystem " @@ -3757,13 +3756,13 @@ msgstr "" "tiedostojärjestelmän." #. Tag: title -#: using-d-i.xml:2366 +#: using-d-i.xml:2365 #, no-c-format msgid "EFI Partition Contents" msgstr "EFI-osion sisältö" #. Tag: para -#: using-d-i.xml:2368 +#: using-d-i.xml:2367 #, no-c-format msgid "" "The EFI partition is a FAT filesystem format partition on one of the hard " @@ -3803,13 +3802,13 @@ msgstr "" "niitä kertyy järjestelmää päivitettäessä tai asetuksia muokattaessa." #. Tag: filename -#: using-d-i.xml:2390 +#: using-d-i.xml:2389 #, no-c-format msgid "elilo.conf" msgstr "elilo.conf" #. Tag: para -#: using-d-i.xml:2391 +#: using-d-i.xml:2390 #, no-c-format msgid "" "This is the configuration file read by the boot loader when it starts. It is " @@ -3824,13 +3823,13 @@ msgstr "" "tiedostoihin." #. Tag: filename -#: using-d-i.xml:2400 +#: using-d-i.xml:2399 #, no-c-format msgid "elilo.efi" msgstr "elilo.efi" #. Tag: para -#: using-d-i.xml:2401 +#: using-d-i.xml:2400 #, no-c-format msgid "" "This is the boot loader program that the EFI Boot Manager " @@ -3844,13 +3843,13 @@ msgstr "" "valinta." #. Tag: filename -#: using-d-i.xml:2411 +#: using-d-i.xml:2410 #, no-c-format msgid "initrd.img" msgstr "initrd.img" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2411 #, no-c-format msgid "" "This is the initial root filesystem used to boot the kernel. It is a copy of " @@ -3865,13 +3864,13 @@ msgstr "" "hakemistossa /boot." #. Tag: filename -#: using-d-i.xml:2424 +#: using-d-i.xml:2423 #, no-c-format msgid "readme.txt" msgstr "readme.txt" #. Tag: para -#: using-d-i.xml:2425 +#: using-d-i.xml:2424 #, no-c-format msgid "" "This is a small text file warning you that the contents of the directory are " @@ -3883,13 +3882,13 @@ msgstr "" "elilo suoritetaan seuraavan kerran." #. Tag: filename -#: using-d-i.xml:2435 +#: using-d-i.xml:2434 #, no-c-format msgid "vmlinuz" msgstr "vmlinuz" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2435 #, no-c-format msgid "" "This is the compressed kernel itself. It is a copy of the file referenced in " @@ -3903,13 +3902,13 @@ msgstr "" "filename> osoitettu tiedosto hakemistossa /boot." #. Tag: title -#: using-d-i.xml:2456 +#: using-d-i.xml:2455 #, no-c-format msgid "arcboot-installer" msgstr "Käynnistyslataimen arcboot asennin" #. Tag: para -#: using-d-i.xml:2457 +#: using-d-i.xml:2456 #, no-c-format msgid "" "The boot loader on SGI machines is arcboot. It has to be " @@ -3954,13 +3953,13 @@ msgstr "" "sitten boot." #. Tag: replaceable -#: using-d-i.xml:2476 +#: using-d-i.xml:2475 #, no-c-format msgid "scsi" msgstr "scsi" #. Tag: para -#: using-d-i.xml:2477 +#: using-d-i.xml:2476 #, no-c-format msgid "" "is the SCSI bus to be booted from, this is 0 for the " @@ -3970,13 +3969,13 @@ msgstr "" "yhdysrakenteisille ohjaimille" #. Tag: replaceable -#: using-d-i.xml:2485 +#: using-d-i.xml:2484 #, no-c-format msgid "disk" msgstr "levy" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2485 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which arcboot is " @@ -3984,13 +3983,13 @@ msgid "" msgstr "on SCSI ID sille levylle johon arcboot on asennettu" #. Tag: replaceable -#: using-d-i.xml:2494 using-d-i.xml:2563 +#: using-d-i.xml:2493 using-d-i.xml:2562 #, no-c-format msgid "partnr" msgstr "partnr" #. Tag: para -#: using-d-i.xml:2495 +#: using-d-i.xml:2494 #, no-c-format msgid "" "is the number of the partition on which /etc/arcboot.conf/etc/arcboot.conf sijaitsee" #. Tag: replaceable -#: using-d-i.xml:2503 +#: using-d-i.xml:2502 #, no-c-format msgid "config" msgstr "config" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2503 #, no-c-format msgid "" "is the name of the configuration entry in /etc/arcboot.conflinux." #. Tag: title -#: using-d-i.xml:2525 +#: using-d-i.xml:2524 #, no-c-format msgid "delo-installer" msgstr "Käynnistyslataimen delo asennin" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2525 #, no-c-format msgid "" "The boot loader on DECstations is DELO. It has to be " @@ -4052,13 +4051,13 @@ msgstr "" "varusohjelmiston kehotteeseen." #. Tag: replaceable -#: using-d-i.xml:2545 +#: using-d-i.xml:2544 #, no-c-format msgid "#" msgstr "#" #. Tag: para -#: using-d-i.xml:2546 +#: using-d-i.xml:2545 #, no-c-format msgid "" "is the TurboChannel device to be booted from, on most DECstations this is " @@ -4068,20 +4067,20 @@ msgstr "" "on 3 yhdysrakenteisille ohjaimille." #. Tag: replaceable -#: using-d-i.xml:2554 +#: using-d-i.xml:2553 #, no-c-format msgid "id" msgstr "id" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2554 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which DELO is installed" msgstr "on SCSI ID sille levylle johon DELO on asennettu" #. Tag: para -#: using-d-i.xml:2564 +#: using-d-i.xml:2563 #, no-c-format msgid "" "is the number of the partition on which /etc/delo.conf " @@ -4090,13 +4089,13 @@ msgstr "" "on sen osion numero jossa /etc/delo.conf sijaitsee" #. Tag: replaceable -#: using-d-i.xml:2572 +#: using-d-i.xml:2571 #, no-c-format msgid "name" msgstr "name" #. Tag: para -#: using-d-i.xml:2573 +#: using-d-i.xml:2572 #, no-c-format msgid "" "is the name of the configuration entry in /etc/delo.conflinux." #. Tag: para -#: using-d-i.xml:2583 +#: using-d-i.xml:2582 #, no-c-format msgid "" "In case /etc/delo.conf is on the first partition on the " @@ -4116,19 +4115,19 @@ msgstr "" "ja käynnistetäään oletuskokoonpano, riittää käyttää" #. Tag: screen -#: using-d-i.xml:2589 +#: using-d-i.xml:2588 #, no-c-format msgid "boot #/rzid" msgstr "boot #/rzid" #. Tag: title -#: using-d-i.xml:2599 +#: using-d-i.xml:2598 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "Asennetaan käynnistyslatain Yaboot kiintolevylle" #. Tag: para -#: using-d-i.xml:2600 +#: using-d-i.xml:2599 #, no-c-format msgid "" "Newer (mid 1998 and on) PowerMacs use yaboot as their " @@ -4148,13 +4147,13 @@ msgstr "" "käynnistämään &debian;." #. Tag: title -#: using-d-i.xml:2618 +#: using-d-i.xml:2617 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "Asennetaan käynnistyslatain Quik kiintolevylle" #. Tag: para -#: using-d-i.xml:2619 +#: using-d-i.xml:2618 #, no-c-format msgid "" "The boot loader for OldWorld Power Macintosh machines is quikzipl-installer" msgstr "Käynnistyslataimen zipl asennin" #. Tag: para -#: using-d-i.xml:2636 +#: using-d-i.xml:2635 #, no-c-format msgid "" "The boot loader on &arch-title; is zipl. ZIPLZIPL enemmän." #. Tag: title -#: using-d-i.xml:2653 +#: using-d-i.xml:2652 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "Asennetaan käynnistyslatain SILO kiintolevylle" #. Tag: para -#: using-d-i.xml:2655 +#: using-d-i.xml:2654 #, no-c-format msgid "" "The standard &architecture; boot loader is called silo. It is " @@ -4228,13 +4227,13 @@ msgstr "" "SunOS/Solaris-asennuksen rinnalle." #. Tag: title -#: using-d-i.xml:2680 +#: using-d-i.xml:2679 #, no-c-format msgid "Continue Without Boot Loader" msgstr "Jatketaan ilman käynnistyslatainta" #. Tag: para -#: using-d-i.xml:2682 +#: using-d-i.xml:2681 #, no-c-format msgid "" "This option can be used to complete the installation even when no boot " @@ -4253,7 +4252,7 @@ msgstr "" "koska GNU/Linux käynnistetään sen kautta." #. Tag: para -#: using-d-i.xml:2691 +#: using-d-i.xml:2690 #, no-c-format msgid "" "If you plan to manually configure your bootloader, you should check the name " @@ -4274,13 +4273,13 @@ msgstr "" "osio." #. Tag: title -#: using-d-i.xml:2708 +#: using-d-i.xml:2707 #, no-c-format msgid "Finishing the Installation" msgstr "Päätetään asennus" #. Tag: para -#: using-d-i.xml:2709 +#: using-d-i.xml:2708 #, no-c-format msgid "" "These are the last bits to do before rebooting to your new system. It mostly " @@ -4290,13 +4289,13 @@ msgstr "" "Pääasiassa siistitään työn jälkiä jotka &d-i; jätti." #. Tag: title -#: using-d-i.xml:2721 +#: using-d-i.xml:2720 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "Päätetään asennus ja käynnistetään" #. Tag: para -#: using-d-i.xml:2723 +#: using-d-i.xml:2722 #, no-c-format msgid "" "This is the last step in the initial Debian installation process. You will " @@ -4310,7 +4309,7 @@ msgstr "" "järjestelmä." #. Tag: para -#: using-d-i.xml:2730 +#: using-d-i.xml:2729 #, no-c-format msgid "" "Select the Finish the installation menu item " @@ -4325,13 +4324,13 @@ msgstr "" "aikana." #. Tag: title -#: using-d-i.xml:2744 +#: using-d-i.xml:2743 #, no-c-format msgid "Miscellaneous" msgstr "Sekalaista" #. Tag: para -#: using-d-i.xml:2745 +#: using-d-i.xml:2744 #, no-c-format msgid "" "The components listed in this section are usually not involved in the " @@ -4342,13 +4341,13 @@ msgstr "" "ovat käytettävissä jos jotain menee pieleen." #. Tag: title -#: using-d-i.xml:2758 +#: using-d-i.xml:2757 #, no-c-format msgid "Saving the installation logs" msgstr "Asentimen lokien tallentaminen" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2759 #, no-c-format msgid "" "If the installation is successful, the logfiles created during the " @@ -4360,7 +4359,7 @@ msgstr "" "installer/." #. Tag: para -#: using-d-i.xml:2767 +#: using-d-i.xml:2766 #, no-c-format msgid "" "Choosing Save debug logs from the main menu " @@ -4376,13 +4375,13 @@ msgstr "" "tai liittää lokit asennusraporttiin." #. Tag: title -#: using-d-i.xml:2787 +#: using-d-i.xml:2786 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "Komentotulkin käyttö ja lokien lukeminen" #. Tag: para -#: using-d-i.xml:2790 +#: using-d-i.xml:2789 #, no-c-format msgid "" "There is an Execute a Shell item on the menu. If " @@ -4405,7 +4404,7 @@ msgstr "" "komentotulkin klooni nimeltä ash." #. Tag: para -#: using-d-i.xml:2802 +#: using-d-i.xml:2801 #, no-c-format msgid "" "At this point you are booted from the RAM disk, and there is a limited set " @@ -4423,7 +4422,7 @@ msgstr "" "komentohistoria." #. Tag: para -#: using-d-i.xml:2811 +#: using-d-i.xml:2810 #, no-c-format msgid "" "Use the menus to perform any task that they are able to do — the shell " @@ -4443,13 +4442,13 @@ msgstr "" "exit jos komentotulkki käynnistettiin valikosta." #. Tag: title -#: using-d-i.xml:2830 +#: using-d-i.xml:2829 #, no-c-format msgid "Installation Over the Network" msgstr "Etäasennus" #. Tag: para -#: using-d-i.xml:2832 +#: using-d-i.xml:2831 #, no-c-format msgid "" "One of the more interesting components is network-console.)" #. Tag: para -#: using-d-i.xml:2842 +#: using-d-i.xml:2841 #, no-c-format msgid "" "This component is not loaded into the main installation menu by default, so " @@ -4488,7 +4487,7 @@ msgstr "" "SSH:ta.." #. Tag: para -#: using-d-i.xml:2855 +#: using-d-i.xml:2854 #, no-c-format msgid "" "For installations on &arch-title;, this is the default method after setting " @@ -4498,7 +4497,7 @@ msgstr "" "tultua tehdyksi." #. Tag: para -#: using-d-i.xml:2860 +#: using-d-i.xml:2859 #, no-c-format msgid "" "After selecting this new entry, you " @@ -4520,7 +4519,7 @@ msgstr "" "tietoturvallisesti etäasennuksen tekevälle henkilölle." #. Tag: para -#: using-d-i.xml:2872 +#: using-d-i.xml:2871 #, no-c-format msgid "" "Should you decide to continue with the installation locally, you can always " @@ -4532,7 +4531,7 @@ msgstr "" "toinen asentimen osa." #. Tag: para -#: using-d-i.xml:2878 +#: using-d-i.xml:2877 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need " @@ -4564,7 +4563,7 @@ msgstr "" "on vahvistettava se oikeaksi." #. Tag: para -#: using-d-i.xml:2895 +#: using-d-i.xml:2894 #, no-c-format msgid "" "If you install several computers in turn and they happen to have the same IP " @@ -4581,7 +4580,7 @@ msgstr "" "tiedostosta ~/.ssh/known_hosts ja yrittää uudelleen." #. Tag: para -#: using-d-i.xml:2904 +#: using-d-i.xml:2903 #, no-c-format msgid "" "After the login you will be presented with an initial screen where you have " @@ -4601,7 +4600,7 @@ msgstr "" "useampia." #. Tag: para -#: using-d-i.xml:2914 +#: using-d-i.xml:2913 #, no-c-format msgid "" "After you have started the installation remotely over SSH, you should not go " @@ -4617,7 +4616,7 @@ msgstr "" "järjestelmä toimii huonosti." #. Tag: para -#: using-d-i.xml:2922 +#: using-d-i.xml:2921 #, no-c-format msgid "" "Also, if you are running the SSH session from an X terminal, you should not " diff --git a/po/hu/boot-installer.po b/po/hu/boot-installer.po index e40521336..39b271775 100644 --- a/po/hu/boot-installer.po +++ b/po/hu/boot-installer.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-11-30 08:45+0100\n" "Last-Translator: SZERVÁC Attila \n" "Language-Team: Hungarian\n" @@ -16,2063 +16,4441 @@ msgstr "" "X-Poedit-Country: HUNGARY\n" "X-Poedit-Language: Hungarian\n" -#~ msgid "Booting the Installation System" -#~ msgstr "A telepítő rendszer indítása" +#. Tag: title +#: boot-installer.xml:4 +#, no-c-format +msgid "Booting the Installation System" +msgstr "A telepítő rendszer indítása" + +#. Tag: title +#: boot-installer.xml:9 +#, no-c-format +msgid "Booting the Installer on &arch-title;" +msgstr "A telepítő indítása &arch-title; architektúrán" + +#. 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 "" +"SRM console, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." +msgstr "" +"Az Alpha konzol alrendszer specifikációra épülő SRM konzol egy OpenVMS, Tru64 UNIX és GNU/Linux operációs rendszerre való " +"kezelő-környezetet ad." + +#. Tag: para +#: boot-installer.xml:38 +#, no-c-format +msgid "" +"ARC, AlphaBIOS, or ARCSBIOS console, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." +msgstr "" +"Az Advanced RISC Computing (ARC) specifikációra épülő ARC, " +"AlphaBIOS és ARCSBIOS konzol egy Windows NT-hez készült kezelő-" +"környezetet ad." + +#. 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 " +"cfdisk) for the boot disk. Therefore MS-DOS partition " +"tables are the native 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 incompatible " +"Specifically, the bootsector format required by the Console Subsystem " +"Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " +"BSD disklabel format, this is the native 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 MILO 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 for the system type names). " +"The word ARC below denotes any of the ARC-compliant consoles." +msgstr "" +"Az alábbi tábla összefoglalja az elérhető és támogatott rendszer-típus/" +"konzol párokat (lásd az oldalt a rendszer-" +"típus nevekért). Az ARC szó bármely ARC-kompatibilis konzolt " +"jelöli." + +#. Tag: entry +#: boot-installer.xml:107 +#, no-c-format +msgid "System Type" +msgstr "Rendszer típus" + +#. Tag: entry +#: boot-installer.xml:108 +#, no-c-format +msgid "Console Type Supported" +msgstr "Támogatott konzol típus" + +#. Tag: entry +#: boot-installer.xml:114 +#, no-c-format +msgid "alcor" +msgstr "alcor" + +#. 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 "ARC vagy SRM" + +#. Tag: entry +#: boot-installer.xml:117 +#, no-c-format +msgid "avanti" +msgstr "avanti" + +#. Tag: entry +#: boot-installer.xml:120 +#, no-c-format +msgid "book1" +msgstr "book1" + +#. 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 "csak SRM" + +#. Tag: entry +#: boot-installer.xml:123 +#, no-c-format +msgid "cabriolet" +msgstr "cabriolet" + +#. Tag: entry +#: boot-installer.xml:126 +#, no-c-format +msgid "dp264" +msgstr "dp264" + +#. Tag: entry +#: boot-installer.xml:129 +#, no-c-format +msgid "eb164" +msgstr "eb164" + +#. Tag: entry +#: boot-installer.xml:132 +#, no-c-format +msgid "eb64p" +msgstr "eb64p" + +#. Tag: entry +#: boot-installer.xml:135 +#, no-c-format +msgid "eb66" +msgstr "eb66" + +#. Tag: entry +#: boot-installer.xml:138 +#, no-c-format +msgid "eb66p" +msgstr "eb66p" + +#. Tag: entry +#: boot-installer.xml:141 +#, no-c-format +msgid "jensen" +msgstr "jensen" + +#. Tag: entry +#: boot-installer.xml:144 +#, no-c-format +msgid "lx164" +msgstr "lx164" + +#. Tag: entry +#: boot-installer.xml:147 +#, no-c-format +msgid "miata" +msgstr "miata" + +#. Tag: entry +#: boot-installer.xml:150 +#, no-c-format +msgid "mikasa" +msgstr "mikasa" + +#. Tag: entry +#: boot-installer.xml:153 +#, no-c-format +msgid "mikasa-p" +msgstr "mikasa-p" + +#. Tag: entry +#: boot-installer.xml:156 +#, no-c-format +msgid "nautilus" +msgstr "nautilus" + +#. Tag: entry +#: boot-installer.xml:157 +#, no-c-format +msgid "ARC (see motherboard manual) or SRM" +msgstr "ARC (lásd az alaplap kézikönyvet) vagy SRM" + +#. Tag: entry +#: boot-installer.xml:159 +#, no-c-format +msgid "noname" +msgstr "névtelen" + +#. Tag: entry +#: boot-installer.xml:162 +#, no-c-format +msgid "noritake" +msgstr "noritake" + +#. Tag: entry +#: boot-installer.xml:165 +#, no-c-format +msgid "noritake-p" +msgstr "noritake-p" + +#. Tag: entry +#: boot-installer.xml:168 +#, no-c-format +msgid "pc164" +msgstr "pc164" + +#. Tag: entry +#: boot-installer.xml:171 +#, no-c-format +msgid "rawhide" +msgstr "rawhide" + +#. Tag: entry +#: boot-installer.xml:174 +#, no-c-format +msgid "ruffian" +msgstr "ruffian" + +#. Tag: entry +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#, no-c-format +msgid "ARC only" +msgstr "csak ARC" + +#. Tag: entry +#: boot-installer.xml:177 +#, no-c-format +msgid "sable" +msgstr "sable" + +#. Tag: entry +#: boot-installer.xml:180 +#, no-c-format +msgid "sable-g" +msgstr "sable-g" + +#. Tag: entry +#: boot-installer.xml:183 +#, no-c-format +msgid "sx164" +msgstr "sx164" + +#. Tag: entry +#: boot-installer.xml:186 +#, no-c-format +msgid "takara" +msgstr "takara" + +#. Tag: entry +#: boot-installer.xml:189 +#, no-c-format +msgid "xl" +msgstr "xl" + +#. Tag: entry +#: boot-installer.xml:192 +#, no-c-format +msgid "xlt" +msgstr "xlt" + +#. 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, " +"aboot, a small, platform-independent bootloader, is used. " +"See the (unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " +"szükséges. Az SRM konzolokhoz az aboot, egy kis, platform-" +"független boot-betöltő használatos. Lásd az (immár sajnos elavult) SRM HOGYAN aboot leírást." + +#. 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 "" +"Az alábbi bekezdések a woody telepítő kézikönyvből valók, melyre itt " +"hivatkozunk; hasznosak lesznek később, mikor a Debian ismét támogatja a MILO-" +"alapú telepítést." + +#. 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: MILO and aboot." +msgstr "" +"Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " +"szükséges. 2 népszerű van: a MILO és az aboot." + +#. Tag: para +#: boot-installer.xml:221 +#, no-c-format +msgid "" +"MILO is itself a console, which replaces ARC or SRM in " +"memory. MILO can be booted from both ARC and SRM and is " +"the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) " +"MILO HOWTO." +msgstr "" +"A MILO maga egy konzol, mely az ARC vagy SRM helyére " +"kerül a memóriában. A MILO ARC és SRM alól is indítható " +"és ARC konzolról csak ezzel indítható a Linux. A MILO " +"platform-függő (külön MILO kell minden rebdszer-típushoz) " +"és csak a fenti táblában ARC-támogatást mutató rendszerekhez van. Lásd a " +"(sajnos elavult) MILO HOGYAN-t is." + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "" +"aboot is a small, platform-independent bootloader, which " +"runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"Az aboot egy kis, platform-független boot betöltő, mely " +"csak SRM alól fut. Lásd az (immár sajnos elavult) SRM HOGYAN aboot leírást." + +#. 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 MILO is available: " +"\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Because MILO 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 aboot 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 half-flash 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 arc 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 Except on Jensen, where Linux is not " +"supported on firmware versions newer than 1.7 — see for more information. before " +"installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." +msgstr "" + +#. Tag: title +#: boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 +#: boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 +#: boot-installer.xml:2500 boot-installer.xml:2596 +#, no-c-format +msgid "Booting with TFTP" +msgstr "Indítás TFTP segítségével" + +#. Tag: para +#: boot-installer.xml:284 +#, no-c-format +msgid "" +"In SRM, Ethernet interfaces are named with the ewa " +"prefix, and will be listed in the output of the show dev command, like this (edited slightly): \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" +" You first need to set the boot protocol: " +"\n" +">>> set ewa0_protocols bootp\n" +" Then check the medium type is correct: " +"\n" +">>> set ewa0_mode mode\n" +" You can get a listing of valid modes with " +">>>set ewa0_mode." +msgstr "" +"SRM esetén az Ethernet csatolók ewa előtagot kapnak " +"és a show dev parancs kiírja őket így (kissé " +"szerkesztve):\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" +" Először be kell állítani az indító protokollt: " +"\n" +">>> set ewa0_protocols bootp\n" +" Majd ellenőrizni a médium típust:" +"\n" +">>> set ewa0_mode mód\n" +" Az érvényes módok így írhatók ki: >" +">>set ewa0_mode." + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "" +"Then, to boot from the first Ethernet interface, you would type: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" This will boot using the default kernel " +"parameters as included in the netboot image." +msgstr "" +"Majd az 1. Ethernet csatolóról való indításhoz ezt kell beírni: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" Ez netboot képben lévő alap kernel " +"paraméterekkel indít." + +#. Tag: para +#: boot-installer.xml:311 +#, no-c-format +msgid "" +"If you wish to use a serial console, you must pass the " +"console= parameter to the kernel. This can be done " +"using the -flags argument to the SRM boot command. The serial ports are named the same as their " +"corresponding files in /dev. 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 ewa0 and use a console on the first serial port, you would type:" +msgstr "" +"Soros konzol esetén át kell adni a console= paramétert a kernelnek. Ez az SRM boot " +"parancsnak adott -flags argumentummal tehető. A soros " +"portok a /dev könyvtárban lévő megfelelő fájlokkal " +"nevezhetők. További kernel paraméterek megadásakor meg kell ismételni egyes " +"alapértelmezett opciókat, melyek kellenek a &d-i; képekhez. Például az " +"ewa0 eszközről indításhoz az 1. soros port " +"használatakor ezt kell beírni:" + +#. Tag: screen +#: boot-installer.xml:323 +#, no-c-format +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" + +#. Tag: title +#: boot-installer.xml:328 +#, no-c-format +msgid "Booting from CD-ROM with the SRM Console" +msgstr "Indítás CD-ROM lemezről az SRM konzollal" + +#. Tag: para +#: boot-installer.xml:329 +#, no-c-format +msgid "" +"Type \n" +">>> boot xxxx -flags 0\n" +" where xxxx is your CD-" +"ROM drive in SRM notation." +msgstr "" +"Írd be ezt: \n" +">>> boot xxxx -flags 0\n" +" ahol az xxxx a CD-ROM " +"meghajtó SRM szerint." + +#. Tag: title +#: boot-installer.xml:341 +#, no-c-format +msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" +msgstr "Indítás CD-ROM lemezről az ARC vagy AlphaBIOS konzollal" + +#. 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 ), then enter \\milo\\linload." +"exe as the boot loader and \\milo" +"\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS " +"Selection Setup' menu. Ruffians make an exception: You need to use " +"\\milo\\ldmilo.exe as boot loader." +msgstr "" +"Egy CD-ROM indításakor az ARC konzolról, keresd meg az al-architektúra kód " +"nevet (lásd az leírást), majd add meg a " +"\\milo\\linload.exe fájlt mint boot betöltő és a " +"\\milo\\subarch fájlt (ahol " +"a subarch a helyes al-architektúra név) mint OS " +"útvonal az `OS Selection Setup' menüben. A Ruffian kivétel: a " +"\\milo\\ldmilo.exe fájl kell mint boot betöltő." + +#. Tag: title +#: boot-installer.xml:358 +#, no-c-format +msgid "Booting from Floppies with the SRM Console" +msgstr "Indítás flopiról az SRM konzollal" + +#. Tag: para +#: boot-installer.xml:359 +#, no-c-format +msgid "" +"At the SRM prompt (>>>), issue the following " +"command: \n" +">>> boot dva0 -flags 0\n" +" possibly replacing dva0 " +"with the actual device name. Usually, dva0 is the " +"floppy; type \n" +">>> show dev\n" +" to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. If everything works OK, you will eventually see the Linux kernel " +"boot." +msgstr "" +"Az SRM jelnél (>>>) add ki az alábbi parancsot: " +"\n" +">>> boot dva0 -flags 0\n" +" ha kell cserélve a dva0-t " +"az aktuális eszköz nevével. Általában a dva0 a flopi; a " +"\n" +">>> show dev\n" +" sorolja fel az eszközöket (például ha CD-" +"lemezről akarsz indítani). A MILO általi indításkor a -flags argumentum nem számít, csak a boot dva0 parancs " +"kell. Ha minden jól működik, a Linux kernel azonnal elindul." + +#. Tag: para +#: boot-installer.xml:376 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via aboot, use the following command: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (typed on one line), substituting, if necessary, " +"the actual SRM boot device name for dva0, the Linux " +"boot device name for fd0, and the desired kernel " +"parameters for arguments." +msgstr "" +"Ha kernel paramétereket akarsz megadni az aboot " +"indításkor, használd az alábbi parancsot:\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (egy sorban), cseréld, ha kell, a " +"dva0 aktuális SRM indító eszköz nevet, az " +"fd0 Linux indító eszköz nevet és az " +"arguments kívánt kernel paramétereket." + +#. Tag: para +#: boot-installer.xml:388 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See " +"." +msgstr "" +"Ha kernel paramétereket akarsz megadni az MILO " +"indításkor, a MILO betöltőbe lépve egyszer meg kell szakítanod az indítást. " +"Lásd a leírást." + +#. Tag: title +#: boot-installer.xml:398 +#, no-c-format +msgid "Booting from Floppies with the ARC or AlphaBIOS Console" +msgstr "Indítás flopiról az ARC vagy AlphaBIOS konzollal" + +#. Tag: para +#: boot-installer.xml:400 +#, no-c-format +msgid "" +"In the OS Selection menu, set linload.exe as the boot " +"loader, and milo as the OS Path. Bootstrap using the " +"newly created entry." +msgstr "" +"Az OS Választás menüben állítsd be a linload.exe fájlt " +"boot betöltőként és a milo-t OS útvonalként. Indíts az " +"újonnan létrehozott beállításokkal." + +#. Tag: title +#: boot-installer.xml:409 +#, no-c-format +msgid "Booting with MILO" +msgstr "Indítás MILO segítségével" + +#. 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 "" +"AZ indító médián lévő MILO eleve Linux indításra állított. Ha mégis " +"beavatkoznál csak a szóközt kell leütnöd a MILO visszaszámlálás alatt." + +#. 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: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Ha mindent magad akarsz megadni (például további paramétereket) hasonló " +"parancs használható:\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" Ha flopi helyett mást indítsz, cseréld a fenti " +"példa fd0 nevet a megfelelő eszköz nevére Linux " +"szerint. A help parancs röviden leírja a MILO parancsait." + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "Indítás TFTP segítségével" + +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"A hálózati indítás egy hálózati kapcsolatot és egy TFTP hálózati indító " +"kiszolgálót igényel (DHCP, RARP vagy BOOTP)." + +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"A régebbi rendszerek, például a 715 egy RBOOT kiszolgálót kérhetnek BOOTP " +"helyett." + +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "" +"A hálózati indítást támogató telepítő mód leírása itt található: ." + +#. Tag: title +#: boot-installer.xml:459 +#, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "TFTP indítás Netwinder gépen" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" +"A Netwinder gépeknek 2 hálózati csatolója van: egy 10Mbps NE2000-" +"kompatibilis kártya (általában eth0) és egy 100Mbps Tulip " +"kártya. Utóbbival gondok lehetnek a kép TFTP letöltésekor így ajánlott a " +"10Mbps csatoló használata (a 10 Base-T címkéjű)." + +#. 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 ." +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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" + +#. Tag: title +#: boot-installer.xml:529 +#, fuzzy, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "Indítás TFTP segítségével" + +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" + +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "Indítás CD-ROM lemezről" + +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"A legtöbb felhasználó számára a legegyszerűbb mód a Debian CD-készlet " +"használata. Ha van egy CD-készleted és a géped támogatja a CD-lemezről " +"indítást, akkor minden csodás. Egyszerűen állítsd be a " +"gépet, hogy CD-lemezről induljon, ahogy a részben is leírjuk, tedd be a CD-lemezt, indítsd róla a gépet és " +"végezd el a telepítést, erről a következő fejezet súg." + +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"Egyes CD-eszközök különleges meghajtókat igényelnek és elérhetetlenek " +"lehetnek a telepítő első lépéseiben. Ha a CD-lemezről indítás szokásos módja " +"nem működik a gépeden, nézd át újra e fejezetet és olvasd el az eltérő " +"kernelekről és telepítő módokról szóló részeket, mely megoldja ezt." + +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"Még abban az esetben is, ha nem tudsz CD-ROM lemezről indítani, valószínűleg " +"képes leszel a Debian rendszer összetevőit és a kívánt csomagokat telepíteni " +"ezekről. Egyszerűen indíts más médiumról, például flopiról. Az operációs " +"rendszer, alaprendszer és tetszőleges további csomagok telepítésekor a " +"telepítő rendszert a CD-ROM meghajtóra irányíthatod." + +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"Ha gondjaid vannak ez indítással, lásd az részt." + +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"Egy CD-ROM indításához Cyclone konzol jelről, használd a boot cd0:" +"cats.bin parancsot" + +#. Tag: title +#: boot-installer.xml:589 +#, fuzzy, no-c-format +msgid "Booting from Firmware" +msgstr "Indítás flopikról" + +#. 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 +#, fuzzy, no-c-format +msgid "Booting the NSLU2" +msgstr "Indítás MILO segítségével" + +#. 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 Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"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 upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" + +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "Indítás egy CD-ROM lemezről" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "" +"Indítás Linuxból LILO vagy GRUB " +"használatával" + +#. 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 ." +msgstr "" +"A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a " +" részben írt fájlokat." + +#. 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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"Ha a merevlemez csak indításra a többi letöltésre pedig a hálózat szolgál, a " +"netboot/debian-installer/i386/initrd.gz fájl és a " +"megfelelő netboot/debian-installer/i386/linux kernel " +"letöltése kell. Ezzel átparticionálható a telepítő indítására használt " +"merevlemez, körültekintően." + +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"Ha egy merevlemez-partíció változatlan marad a telepítés során, lehetőség " +"nyílik a hd-media/initrd.gz fájl, hozzávaló kernel és " +"egy CD iso letöltésére (az utóbbi fájl nevének vége maradjon .iso). A telepítő indíthat a meghajtóról és képes telepíteni a CD képről " +"hálózat nélkül." + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"LILO esetén 2 dolgot kell beállítani a /etc/" +"lilo.conf fájlban, melyek: az " +"initrd.gz telepítő betöltése induláskor; a vmlinuz kernel egy RAM " +"lemezt használjon gyökér-partícióként. " +"Itt egy példa /etc/lilo.conf:" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"További részletekért lásd az initrd 4 és " +"lilo.conf 5 man oldalakat. Futtasd a lilo-t és indíts újra." + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"A GRUB hasonló. Menj a menu.lst " +"fájlra a /boot/grub/ (néha a /boot/boot/grub/" +") könyvtárban és add hozzá a következő sorokat: " +"\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" +" és indíts újra." + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"A ramdisk_size értéke természetesen nem lehet kisebb, " +"mint ami az initrd képhez szükséges. Innentől nincs különbség a " +"GRUB vagy LILO között." + +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "Indítás USB tárról" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +"A korábbi és részben írtak elkészültét feltételezzük. Dugd be az USB tárolót " +"egy szabad USB csatlakozóba és indítsd újra a gépet. Ha minden rendben, a " +"rendszer erről fog indulni és erről ad egy boot: jelet. A 2 " +"lehetőség: további indító argumentumok megadása vagy az &enterkey; leütése." + +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "Indítás flopikról" + +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"Itt szükség lesz a már letöltött flopi-képekre és a képekből a részben létrehozott flopikra." + +#. Tag: para +#: boot-installer.xml:949 +#, 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 "" +"A telepítő flopi indításához, tedd az elsődleges flopi meghajtóba, állítsd " +"le a rendszert, ahogy egyébként tennéd és indítsd újra a gépet." + +#. Tag: para +#: boot-installer.xml:955 +#, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"Egy LS-120 meghajtóról (ATAPI változat) indításhoz egy flopi-készlettel, meg " +"kell adni a flopi eszköz virtuális helyét. Ez a root= " +"indító argumentummal tehető, megadva az eszközt, melyre az ide-floppy " +"meghajtó helyezze. Például, ha az LS-120 meghajtó az 1. IDE eszköz (mester) " +"a második kábelen, írd be ezt: linux root=/dev/hdc az " +"indító jelnél." + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"Egyes gépeken a Control Alt " +"Delete nem indítja újra helyesen a gépet, így " +"egy hideg újraindítás ajánlott. Ha egy létező rendszerről " +"telepítesz (például DOS alól), nincs választásod. Általában, ha lehet, " +"végezz hidegindítást." + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"A flopi lemez elindul és ekkor látnod kell egy képernyőt, mely bemutatja az " +"indító flopit és egy boot: jellel zárul." + +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"Az &enterkey; lenyomásakor a Loading... " +"üzenetnek kell jönnie, ezt követi ez: Uncompressing Linux..." +", majd sok-sok adat a gépben lévő hardverről. A telepítő " +"folyamat e szakaszáról több adat az alábbi: " +"részben található." + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"Az indító flopi után az a root flopit kéri. Tedd be a root flopit és üsd le " +"az &enterkey;-t, ekkor tartalma a memóriába olvasásra kerül. A " +"debian-installer telepítő program elindul." + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "i386 gépen több mód van a TFTP indításra." + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "PXE-támogató hálózati kártya vagy alaplap" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"Lehet, hogy a hálózati csatoló kártya vagy alaplap PXE indítást is támogat. " +"Ez a TFTP indítás egy Intel " +"megvalósítása. Ha így van, lehetőség van a BIOS hálózati indításra " +"állítására." + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "NIC hálózati indító ROM-mal" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "Lehet, hogy hálózati csatoló kártyád TFTP indítást kínál." + +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Tudasd velünk (&email-debian-boot-list;) hogyan kezelted. " +"Hivatkozz e dokumentumra." + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"Az etherboot project TFTP " +"indítást adó indító lemezeket és indító romokat ad." + +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "Az indító jel" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"A telepítő indulásakor egy barátságos grafikus képernyőt látsz a Debian " +"logóval és az indító jellel: \n" +"Press F1 for help, or ENTER to boot:\n" +" Az indító jelnél leütheted az &enterkey; " +"billentyűt a telepítő alap lehetőségeivel indításhoz vagy beírhatsz egy " +"adott indító módot és, tetszőlegesen, indító paramétereket." + +#. Tag: para +#: boot-installer.xml:1078 +#, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"Az elérhető indító módok és paraméterek, melyek hasznosak lehetnek az " +"F2 és F8 közti billentyűk leütésével " +"érhetők el. Ha paramétert adsz az indító parancs sorhoz, írd be az indító " +"módot (az alap a linux) és egy szóközt az 1. " +"paraméter előtt (például linux fb=false)." + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"Ha a rendszert távoli kezelő eszközön át telepíted, mely szöveges felületet " +"ad a VGA konzolhoz, talán nem látod a kezdő grafikus üdvözlő képernyőt a " +"telepítő indításakor és az indító jelet. Ezek közütt van a Compaq's " +"integrated Lights Out (iLO) és HP's Integrated Remote " +"Assistant (IRA). Vakon nyomd meg az F1 billentyűt " +"Néha ehhez különleges escape sor kell, például IRA esetén " +"Ctrl F , 1. a képernyő átugrásával a súgóra lépéshez. " +"Ezután a leütött billentyűk már a várkozásnak megfelelően megjelennek a " +"beviteli jelnél. A framebuffer tiltásához a telepítéskor a " +"fb=false hozzáadása kell az indító jelnél, ahogy azt " +"a súgó is írja." + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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:1180 +#, 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:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. 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:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... 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:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1302 +#, 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:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1324 +#, 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:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. 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:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD 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:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1419 +#, 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:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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:1460 +#, 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:1465 +#, 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:1472 +#, no-c-format +msgid "" +"Press ENTER. 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:1481 boot-installer.xml:1617 +#, 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:1492 +#, no-c-format +msgid "" +"Booting an IA-64 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:1526 +#, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. 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:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1538 +#, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1608 +#, 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: title +#: boot-installer.xml:1630 +#, fuzzy, no-c-format +msgid "Choosing an Installation Method" +msgstr "A telepítő rendszer indítása" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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:1640 +#, fuzzy, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "2.2.x kernel esetén a &ramdisksize; beállítandó." + +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1667 +#, fuzzy, no-c-format +msgid "Amiga" +msgstr "miata" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "" +"Amiga does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "" +"The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "" +"Atari does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"). In other words the cdrom is not " +"bootable. Macs do not have a working 2.4.x kernel." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1757 +#, fuzzy, no-c-format +msgid "Booting from a Hard Disk" +msgstr "Indítás egy CD-ROM lemezről" + +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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:1769 boot-installer.xml:2367 +#, fuzzy, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"A telepítő merevlemezről indításához először le kell tölteni és elhelyezni a " +" részben írt fájlokat." + +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1807 +#, fuzzy, no-c-format +msgid "Booting from AmigaOS" +msgstr "Indítás egy CD-ROM lemezről" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1829 +#, fuzzy, no-c-format +msgid "Booting from Atari TOS" +msgstr "Indítás egy CD-ROM lemezről" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1852 +#, fuzzy, no-c-format +msgid "Booting from MacOS" +msgstr "Indítás egy CD-ROM lemezről" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"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:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1919 +#, fuzzy, no-c-format +msgid "Booting from Q40/Q60" +msgstr "Indítás TFTP segítségével" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2054 +#, 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:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" +"After entering the command monitor use \n" +"bootp():\n" +" 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 netaddr environment variable. Type " +"\n" +"unsetenv netaddr\n" +" in the command monitor to do this." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 +#: boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: " +"\n" +"ifconfig eth0 -auto\n" +" Once you have obtained an IP address, you can " +"load SiByl with the following command: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 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:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "Indító paraméterek" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" +"Following the bootp(): 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: \n" +"bootp():/boot/tftpboot.img\n" +" Further kernel parameters can be passed via " +"append:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the /boot/sibyl.conf file on the TFTP " +"server and add your parameters to the extra_args " +"variable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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:2170 +#, 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:2179 +#, 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:2222 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"/nfsroot/default.colo file on the NFS server and add " +"your parameters to the args variable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2251 +#, 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:2256 +#, 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 an ssh session which will launch the standard installation " +"system." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2267 +#, fuzzy, no-c-format +msgid "s390 Boot Parameters" +msgstr "Indító paraméterek" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more " +"information about S/390-specific boot parameters." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, " +"Option, Shift, and Delete " +"keys together while booting to boot from the CD-ROM." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2331 +#, 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:2340 +#, 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 for booting from the hard disk, except use the " +"path to yaboot on the CD at the OF prompt, such as" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "" + +#. Tag: title +#: boot-installer.xml:2355 +#, fuzzy, no-c-format +msgid "Booting from Hard Disk" +msgstr "Indítás egy CD-ROM lemezről" + +#. Tag: title +#: boot-installer.xml:2376 +#, fuzzy, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "Indítás flopikról" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"If you set up BootX in , you can use it to " +"boot into the installation system. Double click the BootX " +"application icon. Click on the Options button and " +"select Use Specified RAM Disk. This will give you the " +"chance to select the ramdisk.image.gz file. You may " +"need to select the No Video Driver checkbox, depending " +"on your hardware. Then click the Linux button to shut " +"down MacOS and launch the installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" +"You will have already placed the vmlinux, " +"initrd.gz, yaboot, and " +"yaboot.conf files at the root level of your HFS " +"partition in . Restart the computer, and " +"immediately (during the chime) hold down the Option, " +"Command (cloverleaf/Apple), o, and " +"f keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"\n" +"0 > boot hd:x,yaboot\n" +" replacing x 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 " +"ide0: instead of hd:. In a few " +"more seconds you will see a yaboot prompt \n" +"boot:\n" +" At yaboot's boot: prompt, type " +"either install or install video=ofonly followed by a &enterkey;. The video=ofonly " +"argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2440 +#, fuzzy, no-c-format +msgid "Booting from USB memory stick" +msgstr "Indítás USB tárról" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "" +"Make sure you have prepared everything from . 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 " +"Command Option o f all together while booting (see )." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment ofpath cannot work that out " +"automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " +"/pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" +"Having worked out the device path, use a command like this to boot the " +"installer: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" The 2 matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the ,\\\\:tbxi part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"yaboot) in the directory previously blessed with " +"hattrib -b." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2485 +#, fuzzy, no-c-format +msgid "" +"The system should now boot up, and you should be presented with the " +"boot: prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." +msgstr "" +"A korábbi és részben írtak elkészültét feltételezzük. Dugd be az USB tárolót " +"egy szabad USB csatlakozóba és indítsd újra a gépet. Ha minden rendben, a " +"rendszer erről fog indulni és erről ad egy boot: jelet. A 2 " +"lehetőség: további indító argumentumok megadása vagy az &enterkey; leütése." + +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see ) and use the command " +"boot enet:0. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try boot " +"server_ipaddr,file," +"client_ipaddr." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2543 +#, 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:2555 +#, fuzzy, no-c-format +msgid "" +"To boot from the boot-floppy-hfs.img floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." +msgstr "" +"A telepítő flopi indításához, tedd az elsődleges flopi meghajtóba, állítsd " +"le a rendszert, ahogy egyébként tennéd és indítsd újra a gépet." + +#. Tag: para +#: boot-installer.xml:2561 +#, 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:2568 +#, fuzzy, no-c-format +msgid "" +"After booting, the root.bin 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 "" +"Az indító flopi után az a root flopit kéri. Tedd be a root flopit és üsd le " +"az &enterkey;-t, ekkor tartalma a memóriába olvasásra kerül. A " +"debian-installer telepítő program elindul." + +#. Tag: title +#: boot-installer.xml:2579 +#, fuzzy, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "Indító paraméterek" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 " +"video=atyfb:vmode:6 , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"video=aty128fb:vmode:6 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see ). Use " +"the command boot net to boot from a TFTP and RARP " +"server, or try boot net:bootp or boot net:" +"dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " +"OpenBoot revisions require using the device name, such as boot le" +"(); these probably don't support BOOTP nor DHCP." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "" +"Most OpenBoot versions support the boot cdrom 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:2691 +#, no-c-format +msgid "" +"To boot from floppy on a Sparc, use \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"Bad magic number in disk label - Can't open disk label " +"package. 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:2703 +#, 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 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"If you are booting from the floppy, and you see messages such as " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" then it is possible that floppy booting is " +"simply not supported on your machine." +msgstr "" +"Ha flopiról indítanál, de ehhez hasonló üzeneteket kapsz:" +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" lehet, hogy a flopi indítás egyszerűen nem " +"támogatott e gépen." + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "IDPROM üzenetek" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"IDPROM, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"Sun NVRAM FAQ for more " +"information." +msgstr "" +"Ha IDPROM gondokról szóló üzenetek miatt nem tudsz indítani, " +"lehet, hogy az NVRAM elem, mely a firmware beállításait tartalmazza, " +"lemerült. Lásd a Sun NVRAM GYIK " +"címet több adatért." + +#. Tag: para +#: boot-installer.xml:2742 +#, 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 "" +"Az indító paraméterek Linux kernel paraméterek, melyek általában a " +"perifériák helyes használatára szolgálnak. A kernel általában képes ezek " +"adatainak automatikus érzékelésére. Egyes esetekben azonban egy kis segítség " +"szükséges." + +#. Tag: para +#: boot-installer.xml:2749 +#, 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 "" +"A rendszert 1. ízben az alap paraméterekkel jó indítani (vagyis továbbiak " +"megadása nélkül) és meggyőződni arról, működése helyes-e. Ha nem, egy " +"későbbi újraindításkor megadhatók különleges paraméterek, melyek a rendszert " +"kisegítik egyes adatokkal a hardverről." + +#. Tag: para +#: boot-installer.xml:2756 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +"Sok indító paraméterről szóló adat van a Linux BootPrompt HOGYAN leírásban, " +"benne kétes hardverekről szólók is. Ez csak egy vázlatos szakasz a " +"legáltalánosabb paraméterekről. Néhány szokásos találat megtalálható az " +"alábbi: részben." + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" +"When the kernel boots, a message \n" +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total 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 mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" +"A kernel indulásakor egy \n" +"Memory:availk/totalk " +"available\n" +" üzenet látható a folyamat elején. A " +"total a RAM teljes méretét adja kilobájtban. Ha " +"nem pontos, a mem=ram " +"paraméter használandó, ahol a ram a memória " +"mérete, melyet k követ kilobájtokhoz, vagy m " +"megabájtokhoz. Például a mem=65536k és " +"mem=64m jelentése egyaránt 64MB RAM." + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this (although not on DECstations). 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 console=device " +"argument to the kernel, where device is your " +"serial device, which is usually something like ttyS0." +msgstr "" +"Soros konzollal indításkor a kernel általában automatikusan felismeri " +"ezt (DECstation esetén nem). Ha van videó " +"kártya (framebuffer) és billentyűzet a soros konzol által indítandó gépen, " +"át kell adni a console=eszköz argumentumot a kernelnek, ahol az eszköz a soros eszköz, mely általában valami ilyesmi: ttyS0." + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"&arch-title; architektúrán a soros eszközök neve ttya " +"vagy ttyb. Vagy állítsd be, hogy az input-" +"device és output-device OpenPROM változók értéke " +"legyen ttya." + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "Debian Telepítő paraméterek" + +#. Tag: para +#: boot-installer.xml:2806 +#, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"A telepítő rendszer pár további indító paramétert is ismer " +"A jelenlegi kernelekkel (2.6.9 vagy újabb) 32 parancssori opció és 32 " +"környezeti opció használható. Ennek túllépése kernel pánikot okoz. mely hasznos lehet." + +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "debconf/priority" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"E paraméter adja meg a megjelenítendő üzenetek legkisebb elsőbbségét. Rövid " +"forma: priority" + +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "" +"The default installation uses priority=high. 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 "" +"Az alap telepítés a priority=high. érteket használja. " +"Ekkor a kritikus és magas elsőbbségű üzenetek jelennek meg, a közepes és " +"alacsony elsőbbségű üzenetek nem. Hibák esetén a telepítő a szükséges " +"szintre állítja ezt." + +#. Tag: para +#: boot-installer.xml:2836 +#, no-c-format +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"A priority=medium részletesebb irányítást ad a " +"telepítéshez. A priority=low mindent kérdez (ez " +"ugyanaz, mint az expert indítás mód). A " +"priority=critical esetén a rendszer csak a kritikus " +"üzeneteket jeleníti meg és ha minden rendben, nem kérdez." + +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "DEBIAN_FRONTEND" + +#. Tag: para +#: boot-installer.xml:2851 +#, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " +" The default frontend is " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text may be preferable for serial " +"console installs. Generally only the newt frontend is " +"available on default install media. On architectures which support it, the " +"graphical installer uses the gtk frontend." +msgstr "" +"Ez szabja meg a telepítő által használt felhasználó felületet. A jelenlegi " +"lehetséges paraméter beállítások: " +"DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +" DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk Az alapfelület a " +"DEBIAN_FRONTEND=newt. A " +"DEBIAN_FRONTEND=text soros konzolos telepítésekhez " +"jó. Általában csak a newt felület elérhető az alap " +"telepítő médián. Az támogató architektúrákon a grafikus telepítő a " +"gtk felületet használja." + +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "BOOT_DEBUG" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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 "" +"Ha e paraméter értéke 2, a telepítő indító folyamat részletesebb naplózásra " +"kerül. Ha 3, hibakereső héjakat tesz elérhetővé az indító folyamat fő " +"pontjain. (Lépj ki a héjakból az indító folyamat folytatásához.)" + +#. Tag: userinput +#: boot-installer.xml:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "BOOT_DEBUG=0" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "Ez az alap." + +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "BOOT_DEBUG=1" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "Átlagnál bővebb." + +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "BOOT_DEBUG=2" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "Sok hibakereső adat." + +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "BOOT_DEBUG=3" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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 "" +"A héjak az indító folyamat különböző pontjain futnak részletes hibák " +"visszaadásához. Lépj ki a héjból az indítás folytatásához." + +#. Tag: term +#: boot-installer.xml:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "INSTALL_MEDIA_DEV" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"E paraméter értéke a Debian telepítőt betöltő eszköz útvonala. Például " +"INSTALL_MEDIA_DEV=/dev/floppy/0" + +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." +msgstr "" +"Az indító flopi, ami alapban végignézi az összes flopit a gyökér flopi " +"megtalálásához felülírható e paraméterrel, hogy csak 1 eszközt nézzen." + +#. Tag: term +#: boot-installer.xml:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "debian-installer/framebuffer" + +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/" +"framebuffer=false, or fb=false for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." +msgstr "" +"Egyes architektúrák használják a kernel framebuffert a telepítő több-nyelvű " +"támogatásához. Ha ez gondot okoz, kikapcsolható a debian-" +"installer/framebuffer=false vagy röviden fb=false paraméterrel. A szokásos gondok hibaüzenetek a bterm és bogl " +"körül, üres képernyő vagy fagyás a telepítés indítása után pár perccel." + +#. Tag: para +#: boot-installer.xml:2948 +#, no-c-format +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"A video=vga16:off argumentum szintén használható a " +"kernel framebuffer kikapcsolására. Ilyen gondok vannak a Dell Inspiron " +"gépeken Mobil Radeon kártya esetén." + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "Hasonló problémákról érkezett jelentés az Amiga 1200 és SE/30 gépeken." + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "Hasonló problémákról érkezett jelentés egyes hppa gépeken." + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"disabled by default 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 debian-installer/" +"framebuffer=true or fb=true for short." +msgstr "" +"Egyes rendszerek kijelző-gondjai miatt a framebuffer támogatás " +"alapból kikapcsolt &arch-title; architektúránál. Ez " +"kissé csúf megjelenést okozhat ott, ahol a támogatás amúgy működne, például " +"ATI kártyák esetén. A kijelző problémákat látsz a telepítőben, indíthatsz a " +"debian-installer/framebuffer=true vagy röviden " +"fb=true paraméterrel." + +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a dark theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter debian-installer/theme=dark or theme=dark." +msgstr "" +"Egy téma meghatározza, hogyan nézzen ki a telepítő felhasználói felülete " +"(színek, ikonok, stb.). Az elérhető témák a felülettől függenek. A newt és " +"gtk felületek is támogatják a dark témát, mely gyengén " +"látóknak is megfelelő. A téma így állítható be: debian-installer/" +"theme=dark vagy " +"theme=dark." + +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "debian-installer/probe/usb" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "A false tiltja az USB indítást, ha gondot okoz." + +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "netcfg/disable_dhcp" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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 "" +"Alapértelmezetten a &d-i; önműködően megpróbálja a hálózatot beállítani DHCP-" +"n át. Ha sikerül, valószínűleg nem lesz esély a kapott beállítások " +"módosítására. A hálózat kézi beállítása csak a DHCP meghiúsulásakor " +"lehetséges." + +#. Tag: para +#: boot-installer.xml:3008 +#, 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 " +"netcfg/disable_dhcp=true to prevent configuring the " +"network with DHCP and to enter the information manually." +msgstr "" +"Ha van egy DHCP kiszolgáló a helyi hálózaton, de nem akarod használni, mert " +"például rossz választ ad, használhatod a netcfg/" +"disable_dhcp=true paramétert a hálózati DHCP-beállítás tiltására " +"és megadhatod az adatokat kézzel." + +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "hw-detect/start_pcmcia" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"A false tiltja a PCMCIA szolgáltatások indítását, ha " +"gondot okoznak. Egyes laptopok híresek erről." + +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "preseed/url" + +#. Tag: para +#: boot-installer.xml:3031 +#, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url." +msgstr "" +"Megadja az automata telepítéshez letöltendő és használandó elő-beállító " +"fájlra mutató url-t. Lásd a részt. " +"Rövid forma: url." + +#. Tag: term +#: boot-installer.xml:3041 +#, no-c-format +msgid "preseed/file" +msgstr "preseed/file" + +#. Tag: para +#: boot-installer.xml:3042 +#, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file." +msgstr "" +"Megadja az automata telepítéshez betöltendő elő-beállító fájl útvonalát. " +"Lásd a részt. Rövid forma: " +"file." + +#. Tag: term +#: boot-installer.xml:3052 +#, no-c-format +msgid "auto-install/enabled" +msgstr "auto-install/enabled" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" +"Az elő-beállítások végrehajtása előtt felteendő kérdések megválaszolása " +"elhalasztható a hálózat beállításáig. Rövid forma: auto=true Lásd a részt ennek használatához " +"az automata telepítésben." + +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "cdrom-detect/eject" + +#. Tag: para +#: boot-installer.xml:3065 +#, 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 "" +"Alapban az újraindítás előtt a &d-i; önműködően kiadja a telepítés alatt " +"használt optikai médiát. Ez szükségtelen, ha a rendszer nem indul önműködően " +"a CD-lemezről. Néha kimondottan rossz, például, ha az optikai meghajtó nem " +"teszi be újra a médiát és a felhasználó nincs ott. Sok rés-töltős, karcsú és " +"fentről-töltős stílusú meghajtó nem tudja automatikusan újratölteni a médiát." + +#. Tag: para +#: boot-installer.xml:3074 +#, no-c-format +msgid "" +"Set to false 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 "" +"Legyen false az automata kiadás kikapcsolásához, " +"ekkor magadnak kell biztosítani, hogy a rendszer ne induljon önműködően az " +"optikai meghajtóról a telepítés után." + +#. Tag: term +#: boot-installer.xml:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "ramdisk_size" + +#. Tag: para +#: boot-installer.xml:3086 +#, no-c-format +msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgstr "2.2.x kernel esetén a &ramdisksize; beállítandó." + +#. Tag: term +#: boot-installer.xml:3094 +#, no-c-format +msgid "mouse/left" +msgstr "mouse/left" + +#. Tag: para +#: boot-installer.xml:3095 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to true." +msgstr "" +"A gtk felülethez (grafikus telepítő) a felhasználók az egeret bal-kezesre " +"válthatják e paraméter true értékre állításával." + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "directfb/hw-accel" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"true when booting the installer." +msgstr "" +"A gtk felülethez (grafikus telepítő) a directfb hardveres gyorsítás alapból " +"kikapcsolt. Bekapcsolásához, legyen a paraméter true " +"a telepítő indításakor." + +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "rescue/enable" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"Legyen true a rendes telepítés helyett mentő módba " +"lépéshez. Lásd: ." + +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "Indító paraméterek használata kérdések megválaszolására" + +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" +"Pár kivétellel az indító jelnél bármely telepítés alatt feltett kérdés " +"értéke beállítható, ez csak egyes esetekben igazán hasznos. Általános leírás " +"erről a részben. Íme pár példa." + +#. Tag: term +#: boot-installer.xml:3140 +#, no-c-format +msgid "debian-installer/locale" +msgstr "debian-installer/locale" + +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. Short form: " +"locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" +"A nyelv és ország beállítására használható. Minden Debian által támogatott " +"helyi helyi beállításra működik. Rövid forma: locale. " +"Például a locale=de_CH német nyelvet választ, " +"országnak pedig Svájcot." + +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "" +"Set to true if you want to disable DHCP and instead " +"force static network configuration." +msgstr "" +"Állítsd true értékre a DHCP kikapcsolásához és " +"helyette statikus hálózati beállítás kikényszerítéséhez." + +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "tasksel:tasksel/first" + +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" +"Az interaktív listából el nem érhető feladatok kiválasztására használható, " +"fontos például a hungarian-desktop használata. Lásd a " +" részt további adatokért. Rövid forma: " +"tasks." + +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "Paraméterek átadása kernel moduloknak" + +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" +"Kernelbe fordított meghajtók számára lehetséges a kernel dokumentációja " +"szerinti paraméterek átadása. Ám akkor, ha modulokként fordítottak, mivel " +"ezek kissé másképp töltődnek be a telepítéskor, mint a telepített " +"rendszeren, nem adhatók át úgy paraméterek, mint rendesen. A telepítő által " +"ismert különleges szintaxist kell használni, így ezek a helyes beállító " +"fájlba kerülnek és felhasználásra kerülnek a modulok tényleges betöltésekor. " +"E paraméterek átkerülnek a telepített rendszerbe is." + +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" +"Erre ritkán van szükség. A kernel szinte mindig képes a rendszeren lévő " +"hardvert kipróbálni és jó alapértelmezett értékeket beállítani. De egyes " +"esetekben jól jöhet paraméterek kézi beállítása." -#~ msgid "Booting the Installer on &arch-title;" -#~ msgstr "A telepítő indítása &arch-title; architektúrán" +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" +"A modulokhoz beállítandó paraméterek nyelvtana:\n" +"modul_név.paraméter_név=érték\n" +" Ha több paramétert akarsz átadni egy vagy több " +"modulhoz, csak ismételd ezt. Például egy régi 3Com hálózati csatoló kártya " +"beállítása a BNC (koax) csatlakozó és IRQ 10 használatához:" + +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "3c509.xcvr=3 3c509.irq=10" + +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "Hibák elhárítása a telepítő folyamat során" + +#. Tag: title +#: boot-installer.xml:3226 +#, no-c-format +msgid "CD-ROM Reliability" +msgstr "CD-ROM megbízhatóság" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" +"Néha, főleg régi CD-ROM meghajtókkal, a telepítő CD-ROM lemezről indítása " +"meghiúsulhat. A telepítő — akár a CD-ROM lemezről való sikeres indítás " +"után — talán nem ismeri fel a CD-ROM eszközt vagy hibákat ad a " +"telepítés alatti olvasásakor." + +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" +"Ennek sok eltérő oka lehet. Csak néhány szokásos hibát és kezelésükről szóló " +"általános tanácsokat írunk le. A többi tőled függ." + +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "Először 2 egyszerű dolgot érdemes kipróbálni." + +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" +"Ha a CD-ROM nem indul, ellenőrizd, helyesen van-e betéve és nem piszkos-e." + +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" +"Ha a telepítő nem ismeri fel a CD-ROM meghajtót, először próbáld meg a " +" CD-ROM felismerése és csatolása pont futtatását másodszor. Több régi CD-ROM meghajtónál ismert " +"DMA hiba megoldható így." + +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" +"Ha ez nem megy, próbáld az alábbi javaslatokat. Általában az ott tárgyalt " +"javaslatok a CD-ROM és DVD eszközökre egyaránt érvényesek, de az egyszerűség " +"kedvéért mindig a CD-ROM szót használjuk." + +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" +"Ha a telepítés semmiképp nem megy a CD-ROM eszközről, próbálj egy másik " +"elérhető telepítő módot." + +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "Általános hibák" + +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" +"Néhány régi CD-ROM meghajtó nem támogatja a korszerű CD-írók használatával " +"nagy sebességgel írt lemezek olvasását." + +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" +"Ha a rendszer elindul a CD-ROM eszközről, ez nem feltétlenül jelenti azt, " +"hogy a Linux is támogatja azt (vagy, pontosabban a vezérlőt, melyre a CD-ROM " +"meghajtó kötve van)." + +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" +"Pár régi CD-ROM meghajtó nem működik rendesen a direkt memória " +"elérés (DMA) bekapcsolt volta esetén." + +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "Hogyan vizsgálj ki és oldj meg gondokat" + +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" +"Ha a CD-ROM eszköz indítása sikertelen, próbáld ki az alább adott " +"javaslatokat." -#~ msgid "" -#~ "SRM console, based on the Alpha Console Subsystem " -#~ "specification, which provides an operating environment for OpenVMS, Tru64 " -#~ "UNIX, and Linux operating systems." -#~ msgstr "" -#~ "Az Alpha konzol alrendszer specifikációra épülő SRM konzol egy OpenVMS, Tru64 UNIX és GNU/Linux operációs rendszerre való " -#~ "kezelő-környezetet ad." +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" +"Ellenőrizd, hogy a BIOS támogatja a CD-ROM indítást (a régebbiek nem) és " +"hogy a CD-rom meghajtó támogatja a használt médiát." -#~ msgid "" -#~ "ARC, AlphaBIOS, or ARCSBIOS console, based on the " -#~ "Advanced RISC Computing (ARC) specification, which provides an operating " -#~ "environment for Windows NT." -#~ msgstr "" -#~ "Az Advanced RISC Computing (ARC) specifikációra épülő ARC, " -#~ "AlphaBIOS és ARCSBIOS konzol egy Windows NT-hez készült kezelő-" -#~ "környezetet ad." +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" +"Ha letöltöttél egy iso képet, ellenőrizd, hogy az md5sum egyezik az " +"MD5SUMS fájlban lévővel, mely ugyanott van, ahonnan " +"letöltötted. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Ezután ellenőrizd, hogy megírt CD-ROM is " +"egyezik. Az alábbi parancs kiváló. Használja a kép méretét helyes számú bájt " +"olvasására a CD-ROM lemezről." + +#. Tag: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 rekord beolvasva\n" +"262668+0 rekord kiírva\n" +"134486016 bájt (134 MB) másolva, 97.474 másodperc, 1.4 MB/s" + +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" +"Ha a telepítő indulása után a CD-ROM érzékelése sikertelen, sokszor az " +"ismételt kísérlet sikerül. Ha egynél több CD-ROM meghajtód van, tedd a " +"lemezt a másikba. Ha ez sem válik be vagy a CD-ROM felismerésre kerül de " +"hibák történnek az olvasáskor, próbáld a lenti javaslatokat. Ehhez kis Linux-" +"ismeret kell. Parancsok használatához előbb válts a második virtuális " +"terminálra (VT2), melyen aktiváld a héjat." + +#. Tag: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" +"Válts a VT4 terminálra vagy nézd meg a /var/log/syslog " +"tartalmát (használd a nano-t szerkesztőként) a hibák " +"ellenőrzéséhez. Ezután ellenőrizd a dmesg kimenetét is." -#~ msgid "" -#~ "The following table summarizes available and supported system type/" -#~ "console combinations (see for the system " -#~ "type names). The word ARC below denotes any of the ARC-" -#~ "compliant consoles." -#~ msgstr "" -#~ "Az alábbi tábla összefoglalja az elérhető és támogatott rendszer-típus/" -#~ "konzol párokat (lásd az oldalt a rendszer-" -#~ "típus nevekért). Az ARC szó bármely ARC-kompatibilis " -#~ "konzolt jelöli." +#. Tag: para +#: boot-installer.xml:3351 +#, fuzzy, no-c-format +msgid "" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using modprobe." +msgstr "" +"Ellenőrizd a dmesg kimenetét, ha a CD-ROM meghajtó " +"felismerése sikerült. Ilyesmit kell látnod benne (a sorok nem feltétlenül " +"egymás utániak): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" Ha nincs ilyesmi, lehet, hogy a vezérlő " +"felismerése nem sikerült vagy egyáltalán nem támogatott. Ha tudod, milyen " +"meghajtót igényel, kézzel is betöltheted a modprobe " +"paranccsal." + +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" +"Ellenőrizd, van-e megfelelő eszköz-leíró fájl a CD-ROM meghajtóhoz a " +"/dev/ könyvtárban. A fenti példában ez a /dev/" +"hdc. Lehet ez is: /dev/cdroms/cdrom0." -#~ msgid "System Type" -#~ msgstr "Rendszer típus" +#. Tag: para +#: boot-installer.xml:3373 +#, no-c-format +msgid "" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" +"$ mount /dev/hdc /cdrom\n" +" Check if there are any error messages after that " +"command." +msgstr "" +"Használd a mount parancsot a CD-ROM csatolt voltának " +"ellenőrzésére; ha nincs, próbáld kézzel csatolni: \n" +"$ mount /dev/hdc /cdrom\n" +" Ellenőrizd, ír-e hibát." + +#. Tag: para +#: boot-installer.xml:3383 +#, fuzzy, no-c-format +msgid "" +"Check if DMA is currently enabled: \n" +"$ cd /proc/ide/hdc\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +" A 1 in the first column after " +"using_dma means it is enabled. If it is, try disabling " +"it: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." +msgstr "" +"Ellenőrizd a DMA állapotát: \n" +"$ cd /proc/ide/hdc\n" +"$ grep dma settings\n" +"using_dma 1 0 1 rw\n" +" Az 1 az jelenti: bekapcsolva. Ha " +"így van, próbáld kikapcsolni: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Győződj meg, hogy a CD-ROM meghajtónak megfelelő " +"könyvtárban vagy." + +#. Tag: para +#: boot-installer.xml:3398 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" +"Ha gond támad a telepítés alatt, próbáld ki a CD-ROM épségének ellenőrzését " +"a telepítő fő-menü vége felé található lehetőséggel. E lehetőség a CD-ROM " +"eszközről való olvasás megbízhatóságának általános ellenőrzésére is " +"használható." + +#. Tag: title +#: boot-installer.xml:3413 +#, no-c-format +msgid "Floppy Disk Reliability" +msgstr "Flopi lemezek megbízhatósága" + +#. Tag: para +#: boot-installer.xml:3415 +#, no-c-format +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"A Debian rendszert flopiról telepítők számára a legnagyobb gond a flopi " +"megbízhatatlansága." -#~ msgid "Console Type Supported" -#~ msgstr "Támogatott konzol típus" +#. Tag: para +#: boot-installer.xml:3420 +#, 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 "" +"Az indító flopival van a legtöbb gond, mert azt a gép közvetlenül olvassa a " +"Linux indítása előtt. Ez pedig általában nem olvassa olyan megbízhatóan, " +"mint a Linux flopi meghajtó és még üzenet nélkül is leállhat hibás adatok " +"olvasásakor. Nagyon rossz az is, mikor a meghajtó flopikkal van gond, melyek " +"ezt tömeges lemez I/O hiba üzenettel jelzik." + +#. Tag: para +#: boot-installer.xml:3429 +#, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. 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 "" +"Ha a telepítés elakad egy flopinál, legelőször írd a képet egy " +"másik flopira, és nézd meg, ez megoldja-e a gondot. A " +"régi flopi újraformázása általában akkor sem elég, ha nem írt hibát. Sok " +"esetben csak az oldja meg, ha egy másik gépen írod meg." + +#. Tag: para +#: boot-installer.xml:3438 +#, no-c-format +msgid "" +"One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " +"third floppy." +msgstr "" +"Többször előfordult, hogy egy felhasználó három " +"teljesen új flopit használt fel, mire az egyik végre hibátlan volt és " +"sikeresen telepített." -#~ msgid "alcor" -#~ msgstr "alcor" +#. Tag: para +#: boot-installer.xml:3444 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Általában nem kell újra letöltened a flopi képet, de ha gondokat észlelsz, " +"mindig hasznos ellenőrizni a képek helyesen letöltött voltát md5-összegük " +"ellenőrzésével." -#~ msgid "ARC or SRM" -#~ msgstr "ARC vagy SRM" +#. Tag: para +#: boot-installer.xml:3450 +#, 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 "" +"Sokak gépe pedig csak többszöri indítás után tudta pontosan elolvasni a " +"flopit és így ez csak ekkor tudott sikeresen elindulni. Ezt mind hibás " +"hardver vagy firmware flopi meghajtók okozzák." + +#. Tag: title +#: boot-installer.xml:3459 +#, no-c-format +msgid "Boot Configuration" +msgstr "Indító beállítás" + +#. Tag: para +#: boot-installer.xml:3461 +#, 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 " +"." +msgstr "" +"Ha kernel megáll az indító folyamat során, nem ismer fel perifériákat vagy " +"meghajtókat helyesen, először az indító paramétereket kell ellenőrizni a " +"korábbi szerint." -#~ msgid "avanti" -#~ msgstr "avanti" +#. Tag: para +#: boot-installer.xml:3468 +#, no-c-format +msgid "" +"If you are booting with your own kernel instead of the one supplied with the " +"installer, be sure that CONFIG_DEVFS is set in your " +"kernel. The installer requires CONFIG_DEVFS." +msgstr "" +"Ha a telepítő által adott helyett saját kernelt indítasz, fontos, hogy a " +"CONFIG_DEVFS be legyen állítva a kernelben. A " +"telepítő a CONFIG_DEVFS meglétét igényli." -#~ msgid "book1" -#~ msgstr "book1" +#. Tag: para +#: boot-installer.xml:3475 +#, no-c-format +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic." +msgstr "" +"Bizonyos gondok gyakran megoldhatók kiegészítők és perifériák " +"eltávolításával és újraindítással. Egyes belső " +"modemek, hangkártyák és Plug-n-Play eszközök sok gondot adnak." -#~ msgid "SRM only" -#~ msgstr "csak SRM" +#. Tag: para +#: boot-installer.xml:3481 +#, 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 mem=512m." +msgstr "" +"Ha több, mint 512M memória van a gépen és a telepítő megáll a kernel " +"indításakor, előfordulhat, hogy egy indító argumentumot kell megadni a " +"kernel által nézett memória korlátozására így: mem=512m." + +#. Tag: title +#: boot-installer.xml:3492 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "Gyakori &arch-title; telepítő gondok" + +#. Tag: para +#: boot-installer.xml:3493 +#, 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 "" +"Van pár gyakori telepítő gond, mely megoldható vagy elkerülhető egyes indító " +"paraméterek átadásával a telepítőnek." -#~ msgid "cabriolet" -#~ msgstr "cabriolet" +#. Tag: para +#: boot-installer.xml:3498 +#, no-c-format +msgid "" +"Some systems have floppies with inverted DCLs. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter floppy=thinkpad." +msgstr "" +"Egyes rendszereken fordított DCL flopik vannak. Ha hibákat " +"kapsz a flopiról olvasáskor, pedig tudod, hogy a flopi jó, próbáld a " +"floppy=thinkpad paramétert." -#~ msgid "dp264" -#~ msgstr "dp264" +#. Tag: para +#: boot-installer.xml:3504 +#, 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 hd=cylinders," +"heads,sectors." +msgstr "" +"Egyes rendszereken, ilyen például az IBM PS/1 vagy ValuePoint (melyben ST-" +"506 lemez meghajtók vannak), az IDE meghajtó felismerése hibás lehet. Előbb " +"paraméterek nélkül próbáld, és nézd meg, az IDE meghajtó felismerése helyes-" +"e. Ha nem, ellenőrizd a meghajtó geometriáját (cilinderek, fejek, szektorok) " +"és használd a hd=cilinderek," +"fejek,szektorok paramétert." + +#. Tag: para +#: boot-installer.xml:3513 +#, no-c-format +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"Checking 'hlt' instruction..., then you " +"should try the no-hlt boot argument, which disables " +"this test." +msgstr "" +"Nagyon régi gépnél, ha a kernel megáll itt: Checking 'hlt' " +"instruction..., próbáld a no-hlt " +"indító argumentumot, mely kikapcsolja ezt a tesztet." -#~ msgid "eb164" -#~ msgstr "eb164" +#. Tag: para +#: boot-installer.xml:3520 +#, 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 fb=false " +"video=vga16:off to disable the framebuffer console. Only the " +"English language will be available during the installation due to limited " +"console features. See for details." +msgstr "" +"Ha a képernyő fura képet ad a kernel indításakor, például tiszta fehér, " +"tiszta fekete vagy színes kavar, a rendszer problematikus videó kártyát " +"tartalmazhat, mely hibásan vált framebuffer módra. Ekkor használható a " +"fb=false video=vga16:off ennek kikapcsolására. Ekkor " +"csak az angol nyelv érhető el a telepítés alatt. Lásd ezt: a részletekért." + +#. Tag: title +#: boot-installer.xml:3534 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "A rendszer fagyása a PCMCIA beállító szakaszban" + +#. Tag: para +#: boot-installer.xml:3535 +#, 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 " +"hw-detect/start_pcmcia=false boot parameter. You can " +"then configure PCMCIA after the installation is completed and exclude the " +"resource range causing the problems." +msgstr "" +"Egyes Dell laptopok összeomlanak, mikor a PCMCIA eszköz-érzékelő megpróbál " +"elérni egyes hardver-címeket. Pár más laptop is haszonló. Ha ilyen gondot " +"tapasztalsz és nincs szükséged PCMCIA támogatásra a telepítéskor, kapcsold " +"ki a hw-detect/start_pcmcia=false indító " +"paraméterrel. A telepítés után beállíthatod és kizárhatod a gondot adó " +"erőforrás-tartományokat." + +#. Tag: para +#: boot-installer.xml:3545 +#, 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 " +"exclude port 0x800-0x8ff here. There is also a list " +"of some common resource range options in the System resource " +"settings section of the PCMCIA HOWTO. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." +msgstr "" +"A telepítő szakértő módban is indítható. Ekkor lehetőség nyílik a hardver " +"igényeinek megfelelő erőforrás-tartományok bevitelére. Például a fenti Dell " +"laptopokon megadható ez: exclude port 0x800-0x8ff. " +"Van egy lista is néhány általános erőforrás-tartomány lehetőségről itt: " +"PCMCIA HOGYAN rendszer erőforrás-beállítások szakasz. " +"A vesszőket el kell hagyni, ha vannak, mikor beírod ezt az értéket a " +"telepítőben." + +#. Tag: title +#: boot-installer.xml:3562 +#, no-c-format +msgid "System Freeze while Loading the USB Modules" +msgstr "A rendszer fagyása az USB modulok betöltésekor" + +#. Tag: para +#: boot-installer.xml:3563 +#, 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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " +"being loaded." +msgstr "" +"A kernel alapban megpróbálja telepíteni az USB modulokat és az USB billentyű " +"meghajtót pár nem-szabványos USB billentyű támogatásához. De van pár hibás " +"USB rendszer, ahol a meghajtó lefagy betöltéskor. Ennek egyik elkerülése az " +"USB vezérlő kikapcsolása a BIOS beállításban. Egy másik lehetőség a " +"debian-installer/probe/usb=false paraméter átadása az " +"indító jelnél, mely meggátolja e modulok betöltését." + +#. Tag: title +#: boot-installer.xml:3577 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "A kernel indító üzenetek értelmezése" + +#. Tag: para +#: boot-installer.xml:3579 +#, no-c-format +msgid "" +"During the boot sequence, you may see many messages in the form " +"can't find something , or something " +"not present, can't initialize " +"something , or even " +"this driver release depends on something . 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 )." +msgstr "" +"Az indítás alatt, sok ilyen üzenetet láthatsz: can't find " +"valami , vagy " +"valami not present, " +"can't initialize valami , vagy akár this driver release depends on " +"valami . A legtöbb ilyen nem " +"számít. Azért látod, mert a telepítőben lévő kernel úgy készült, hogy a " +"legkülönbözőbb eszközöket támogassa. Persze egy gépen sincs az összes " +"lehetséges eszköz, és az operációs rendszer jelezheti, ha olyat keres, ami " +"nem található. Ez akkor történik, ha vár egy eszköz válaszára, az adott " +"rendszer pedig nem tartalmaz olyat. Ha ezt túl hosszúnak találod, később " +"egyéni kernelt is készíthetsz (lásd a " +"részt)." + +#. Tag: title +#: boot-installer.xml:3604 +#, fuzzy, no-c-format +msgid "Reporting Installation Problems" +msgstr "Gyakori &arch-title; telepítő gondok" + +#. Tag: para +#: boot-installer.xml:3605 +#, fuzzy, no-c-format +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the menu option Save debug logs may be helpful. " +"It lets you store system error logs and configuration information from the " +"installer to a floppy, or download them using 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 "" +"Ha túljutottál a kezdő indító szakaszon, de nem futott le teljesen végig a " +"telepítés, a hibajelentő menü segíthet. Eltárolhatod a rendszer hiba naplóit " +"és beállításait a telepítőből egy flopira, vagy letöltheted egy böngészőben. " +"Ezek megadják a felmerült hibákat és javításukat. Ha jelentést küldesz, " +"csatolhatod hozzá ezeket." + +#. Tag: para +#: boot-installer.xml:3616 +#, no-c-format +msgid "" +"Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" +"További telepítő üzenetek találhatók a /var/log/ " +"könyvtárban a telepítés során és a /var/log/installer/ " +"könyvtárban, miután a gép a telepített rendszert elindította." + +#. Tag: title +#: boot-installer.xml:3627 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "Telepítő jelentések küldése" + +#. Tag: para +#: boot-installer.xml:3628 +#, 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 "" +"Ha még mindig gondjaid vannak, kérjük, küldj telepítő jelentést. Siker " +"esetén és kérünk erre, mert így a lehető legtöbb adatot kapjuk a legtöbb " +"hardver összeállításról." -#~ msgid "eb64p" -#~ msgstr "eb64p" +#. Tag: para +#: boot-installer.xml:3635 +#, no-c-format +msgid "" +"Note that your installation report will be published in the Debian Bug " +"Tracking System (BTS) and forwarded to a public mailing list. Make sure that " +"you use an E-Mail address that you do not mind being made public." +msgstr "" -#~ msgid "eb66" -#~ msgstr "eb66" - -#~ msgid "eb66p" -#~ msgstr "eb66p" - -#~ msgid "jensen" -#~ msgstr "jensen" - -#~ msgid "lx164" -#~ msgstr "lx164" - -#~ msgid "miata" -#~ msgstr "miata" - -#~ msgid "mikasa" -#~ msgstr "mikasa" - -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p" - -#~ msgid "nautilus" -#~ msgstr "nautilus" - -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (lásd az alaplap kézikönyvet) vagy SRM" - -#~ msgid "noname" -#~ msgstr "névtelen" - -#~ msgid "noritake" -#~ msgstr "noritake" - -#~ msgid "noritake-p" -#~ msgstr "noritake-p" - -#~ msgid "pc164" -#~ msgstr "pc164" - -#~ msgid "rawhide" -#~ msgstr "rawhide" - -#~ msgid "ruffian" -#~ msgstr "ruffian" - -#~ msgid "ARC only" -#~ msgstr "csak ARC" - -#~ msgid "sable" -#~ msgstr "sable" - -#~ msgid "sable-g" -#~ msgstr "sable-g" - -#~ msgid "sx164" -#~ msgstr "sx164" - -#~ msgid "takara" -#~ msgstr "takara" - -#~ msgid "xl" -#~ msgstr "xl" - -#~ msgid "xlt" -#~ msgstr "xlt" - -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, aboot, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." -#~ msgstr "" -#~ "Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " -#~ "szükséges. Az SRM konzolokhoz az aboot, egy kis, " -#~ "platform-független boot-betöltő használatos. Lásd az (immár sajnos " -#~ "elavult) SRM HOGYAN " -#~ "aboot leírást." - -#~ 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 "" -#~ "Az alábbi bekezdések a woody telepítő kézikönyvből valók, melyre itt " -#~ "hivatkozunk; hasznosak lesznek később, mikor a Debian ismét támogatja a " -#~ "MILO-alapú telepítést." - -#~ 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: MILO and aboot." -#~ msgstr "" -#~ "Általában e konzolok nem indítanak Linuxot, így egy köztes boot betöltő " -#~ "szükséges. 2 népszerű van: a MILO és az " -#~ "aboot." - -#~ msgid "" -#~ "MILO is itself a console, which replaces ARC or SRM in " -#~ "memory. MILO can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." -#~ msgstr "" -#~ "A MILO maga egy konzol, mely az ARC vagy SRM helyére " -#~ "kerül a memóriában. A MILO ARC és SRM alól is " -#~ "indítható és ARC konzolról csak ezzel indítható a Linux. A MILO platform-függő (külön MILO kell minden " -#~ "rebdszer-típushoz) és csak a fenti táblában ARC-támogatást mutató " -#~ "rendszerekhez van. Lásd a (sajnos elavult) MILO HOGYAN-t is." - -#~ msgid "" -#~ "aboot is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " -#~ "aboot." -#~ msgstr "" -#~ "Az aboot egy kis, platform-független boot betöltő, " -#~ "mely csak SRM alól fut. Lásd az (immár sajnos elavult) SRM HOGYAN aboot leírást." - -#~ msgid "Booting with TFTP" -#~ msgstr "Indítás TFTP segítségével" - -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the ewa " -#~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " -#~ "\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" -#~ " You first need to set the boot protocol: " -#~ "\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Then check the medium type is correct: " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " You can get a listing of valid modes with " -#~ ">>>set ewa0_mode." -#~ msgstr "" -#~ "SRM esetén az Ethernet csatolók ewa előtagot " -#~ "kapnak és a show dev parancs kiírja őket így " -#~ "(kissé szerkesztve):\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" -#~ " Először be kell állítani az indító " -#~ "protokollt: \n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Majd ellenőrizni a médium típust:" -#~ "\n" -#~ ">>> set ewa0_mode mód\n" -#~ " Az érvényes módok így írhatók ki: " -#~ ">>>set ewa0_mode." - -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "Majd az 1. Ethernet csatolóról való indításhoz ezt kell beírni: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " Ez netboot képben lévő alap kernel " -#~ "paraméterekkel indít." - -#~ msgid "" -#~ "If you wish to use a serial console, you must pass " -#~ "the console= parameter to the kernel. This can be " -#~ "done using the -flags argument to the SRM " -#~ "boot command. The serial ports are named the same " -#~ "as their corresponding files in /dev. 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 " -#~ "ewa0 and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "Soros konzol esetén át kell adni a " -#~ "console= paramétert a kernelnek. Ez az SRM " -#~ "boot parancsnak adott -flags argumentummal tehető. A soros portok a /dev könyvtárban lévő megfelelő fájlokkal nevezhetők. További " -#~ "kernel paraméterek megadásakor meg kell ismételni egyes alapértelmezett " -#~ "opciókat, melyek kellenek a &d-i; képekhez. Például az ewa0 eszközről indításhoz az 1. soros port használatakor ezt kell " -#~ "beírni:" - -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" - -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "Indítás CD-ROM lemezről az SRM konzollal" - -#~ msgid "" -#~ "Type \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " where xxxx is your " -#~ "CD-ROM drive in SRM notation." -#~ msgstr "" -#~ "Írd be ezt: \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " ahol az xxxx a CD-" -#~ "ROM meghajtó SRM szerint." - -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "Indítás CD-ROM lemezről az ARC vagy AlphaBIOS konzollal" - -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see ), then enter \\milo" -#~ "\\linload.exe as the boot loader and \\milo" -#~ "\\subarch (where " -#~ "subarch is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use \\milo\\ldmilo.exe as boot loader." -#~ msgstr "" -#~ "Egy CD-ROM indításakor az ARC konzolról, keresd meg az al-architektúra " -#~ "kód nevet (lásd az leírást), majd add meg " -#~ "a \\milo\\linload.exe fájlt mint boot betöltő és a " -#~ "\\milo\\subarch fájlt " -#~ "(ahol a subarch a helyes al-architektúra név) " -#~ "mint OS útvonal az `OS Selection Setup' menüben. A Ruffian kivétel: a " -#~ "\\milo\\ldmilo.exe fájl kell mint boot betöltő." - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "Indítás flopiról az SRM konzollal" - -#~ msgid "" -#~ "At the SRM prompt (>>>), issue the following " -#~ "command: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possibly replacing dva0 " -#~ "with the actual device name. Usually, dva0 is the " -#~ "floppy; type \n" -#~ ">>> show dev\n" -#~ " to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, -" -#~ "flags argument is ignored, so you can just type boot " -#~ "dva0. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "Az SRM jelnél (>>>) add ki az alábbi parancsot: " -#~ "\n" -#~ ">>> boot dva0 -flags 0\n" -#~ " ha kell cserélve a dva0-" -#~ "t az aktuális eszköz nevével. Általában a dva0 a " -#~ "flopi; a \n" -#~ ">>> show dev\n" -#~ " sorolja fel az eszközöket (például ha CD-" -#~ "lemezről akarsz indítani). A MILO általi indításkor a -flags argumentum nem számít, csak a boot dva0 " -#~ "parancs kell. Ha minden jól működik, a Linux kernel azonnal elindul." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for dva0, " -#~ "the Linux boot device name for fd0, and the desired " -#~ "kernel parameters for arguments." -#~ msgstr "" -#~ "Ha kernel paramétereket akarsz megadni az aboot " -#~ "indításkor, használd az alábbi parancsot:\n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (egy sorban), cseréld, ha kell, a " -#~ "dva0 aktuális SRM indító eszköz nevet, az " -#~ "fd0 Linux indító eszköz nevet és az " -#~ "arguments kívánt kernel paramétereket." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " -#~ "See ." -#~ msgstr "" -#~ "Ha kernel paramétereket akarsz megadni az MILO " -#~ "indításkor, a MILO betöltőbe lépve egyszer meg kell szakítanod az " -#~ "indítást. Lásd a leírást." - -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "Indítás flopiról az ARC vagy AlphaBIOS konzollal" - -#~ msgid "" -#~ "In the OS Selection menu, set linload.exe as the boot " -#~ "loader, and milo as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "Az OS Választás menüben állítsd be a linload.exe fájlt " -#~ "boot betöltőként és a milo-t OS útvonalként. Indíts az " -#~ "újonnan létrehozott beállításokkal." - -#~ msgid "Booting with MILO" -#~ msgstr "Indítás MILO segítségével" - -#~ 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 "" -#~ "AZ indító médián lévő MILO eleve Linux indításra állított. Ha mégis " -#~ "beavatkoznál csak a szóközt kell leütnöd a MILO visszaszámlálás alatt." - -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"모든 부분을 하나 하나 지정하려면 (예를 들어, 파라미터를 추가로 지정하려면), " +"다음과 같은 명령을 사용하십시오: \n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" 플로피 외에 다른 장치에서 부팅하는 경우에는, 위" +"의 예에서 fd0을 적당한 리눅스 장치 이름으로 바꾸십시오. " +"help 명령을 실행하면 간단한 MILO 명령어 도움말을 볼 수 있" +"습니다." + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "TFTP에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"네트워크에서 부팅하려면, 네트워크에 연결되어 있어야 하고 TFTP 네트워크 부트 " +"서버가 (DHCP, RARP 혹은 BOOTP) 필요합니다." -#~ msgid "" -#~ "The system should now boot up, and you should be presented with the " -#~ "boot: prompt. Here you can enter optional boot " -#~ "arguments, or just hit &enterkey;." -#~ msgstr "" -#~ "시스템이 부팅하고, boot: 프롬프트가 나타납니다. 여기서 다" -#~ "른 부팅 파라미터가 필요하면 입력하고, 아니면 그냥 &enterkey;를 누르십시오." +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"715처럼 오래된 시스템의 경우에는 BOOTP 서버 대신에 RBOOT 서버를 사용해야 할 " +"수도 있습니다." -#~ 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 ." -#~ msgstr "" -#~ "이 부팅 방법은 새로운 방법으로, 일부 NewWorld 시스템에서는 어려울 수도 있" -#~ "습니다. 문제가 있으면 설치 보고서를 에 설명" -#~ "되어 있는 대로 제출해 주십시오." +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "" +"네트워크 부팅을 지원하는 설치 방법은 에 설명" +"되어 있습니다." + +#. Tag: title +#: boot-installer.xml:459 +#, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "NetWinder에서 TFTP에서 부팅하기" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" +"Netwinder에 네트워크 인터페이스가 2개 있습니다. 하나는 10Mbps NE2000과 호환되" +"는 카드로, 주로 eth0라고 일컫습니다. 다른 하나는 100Mbps " +"Tulip 카드입니다. 100Mbps 카드를 통해 TFTP로 이미지를 로드할 때 문제가 발생" +"할 수 있으므로 10 Base-T라는 라벨이 붙어있는 10Mbps 인터페" +"이스를 사용하기를 권장합니다." + +#. 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 ." +msgstr "" +"설치 시스템을 부팅하려면 NeTTrom 2.2.1 혹은 그 이후의 버전을 사용해야 합니" +"다. 2.3.3버전을 권장합니다. 불행히도, 펌웨어 파일은 라이선스 문제로 인해 다운" +"로드가 불가능합니다. 이 상황이 바뀌면, 에서 새 이미지를 찾을 수 있을 것입니다." + +#. 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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" +"Netwinder 장치를 부팅할 때 카운트다운 과정이 끝나기 전에 부팅 과정을 중단시켜" +"야합니다. 부팅 과정을 중단시켜야 설치 프로그램으로 부팅하기 위해 설정해야할 " +"펌웨어 설정을 변경할 수 있기 때문입니다. 우선 다음 명령을 입력하여 기본 설정" +"을 로드시킵니다: \n" +" NeTTrom command-> load-defaults\n" +" 그 다음 네트워크 주소를 설정해야합니다. 네트워주" +"소를 설정하는 방법에는 몇 가지가 있습니다. 우선 정적 주소를 설정하는 방법은 " +"다음과 같습니다: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" 이 때 24는 넷마스크에서 1로 설정된 비트의 개수를 " +"뜻합니다. 동적 주소를 사용하려면 다음과 같이 입력하시면 됩니다: " +"\n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" 로컬 서브넷에 TFTP서버가 없는 경우 " +"route1도 설정해야합니다. 다음 과정에 따라 TFTP 서버와 " +"이미지 파일의 경로를 설정하십시오. 설정을 바꾼 다음에 플래시에 저장하시면 됩" +"니다.\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" 다음에 할 일을 펌웨어가 TFTP 이미지를 부팅하도록 " +"하는 일입니다. \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" 시리얼 콘솔을 이용하여 Netwinder를 설치하는 중이" +"라면, 다음 설정도 추가하셔야합니다: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" 시리얼 콘솔이 아니라 키보드와 모니터를 이용하여 " +"설치하는 중이라면: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" 환경 설정을 보려면 printenv 명" +"령을 사용하시며 된니다. 모두 정확하다면 다음 명령으로 이미지를 로드하십시오: " +"\n" +" NeTTrom command-> boot\n" +" 설치 도중 문제가 발생할 경우 Netwinder 펌웨어 HOWTO" +"를 참조하십시오." + +#. Tag: title +#: boot-installer.xml:529 +#, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "CATS에서 TFTP에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"CATS 기계에서는 Cyclone 프롬프트에서 boot de0:과 같은 명령" +"을 사용하십시오." + +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "CD-ROM에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"대부분의 사람들에게 가장 쉬운 방법은 데비안 CD 세트를 이용하는 것입니다. CD " +"세트를 가지고 있고, 기계에서 직접 CD 부팅을 할 수 있다면 매우 좋은 경우입니" +"다. 에 설명되어 있는 " +"대로 CD에서 시스템을 부팅할 수 있도록 설정하고, CD를 넣은 다음, 다" +"시 부팅하고, 다음 장으로 넘어가십시오." + +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"일부 CD 드라이브의 경우에는 특별한 드라이버가 필요하므로, 설치 단계의 앞 부분" +"에서는 CD 드라이브에 접근할 수 없을 수도 있습니다. 하드웨어에서 표준적인 방법" +"의 CD 부팅이 동작하지 않는다면, 이 장을 다시 보시고 이 경우에 동작하는 다른 " +"커널 및 설치 방법을 읽어보십시오." + +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"CD-ROM에서 부팅할 수 없는 경우에도, CD-ROM에서 데비안 시스템 구성 요소와 꾸러" +"미를 설치할 수 있습니다. 일단 플로피같은 다른 미디어를 이용해 부팅하십시오. " +"운영 체제, 베이스 시스템 및 다른 추가 꾸러미를 설치할 때가 되면 설치 시스템" +"을 CD-ROM 드라이브로 맞춰 놓으십시오." + +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"부팅하는 데 문제가 있으면, 부분을 참" +"고하십시오." -#~ msgid "Currently, PReP and New World PowerMac systems support netbooting." -#~ msgstr "현재, PReP 및 New World PowerMac 시스템은 네트부팅을 지원합니다." +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"Cyclone 콘솔 프롬프트에서 CD-ROM 부팅을 하려면, boot cd0:cats.bin 명령을 사용하십시오." + +#. Tag: title +#: boot-installer.xml:589 +#, no-c-format +msgid "Booting from Firmware" +msgstr "Firmware에서 부팅하기" + +#. 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 "" +"최근에는 플래시에서 직접 부팅을 수행하는 컨슈머 장치가 점점 많아지고 있습니" +"다. 설치 프로그램을 플래서에 기록하여 주부팅할 때 설치 프로그램을 자동으로 실" +"행하고 할 수 있습니다. " -#~ msgid "" -#~ "On machines with Open Firmware, such as NewWorld Power Macs, enter the " -#~ "boot monitor (see ) and use the " -#~ "command boot enet:0. PReP and CHRP boxes may have " -#~ "different ways of addressing the network. On a PReP machine, you should " -#~ "try boot server_ipaddr," -#~ "file,client_ipaddr." -#~ msgstr "" -#~ "NewWorld Power Mac과 같은 Open Firmware 기계에서는, 부트 모니터로 들어가" -#~ "서 ( 참고) boot enet:0 명령을 사용하십시오. PReP 및 CHRP 컴퓨터는 네트워크 위치를 지정하" -#~ "는 방법이 다릅니다. PReP 기계에서는, boot " -#~ "server_ipaddr,file," -#~ "client_ipaddr라고 시도해 보십시오." +#. 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 "NSLU2로 부팅하기" + +#. 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 "NSLU2 웹 인터페이스를 사용하기" + +#. Tag: para +#: boot-installer.xml:620 +#, no-c-format +msgid "" +"Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." +msgstr "" +"관리 섹션으로 가서 Upgrade 메뉴를 선택하십시오. 이 메뉴를 " +"선택하면 이전에 디스크에서 다운로드받은 설치 프로그램의 이미지 파일을 찾을 " +"수 있습니다. 그 다음 Start Upgrade 버튼을 누른 후, 확인을 " +"한 다음, 몇 분을 기다린 후 다시 확인을 누르십시오. 시스템이 이제 설치 프로그" +"램으로 바로 부팅하게 됩니다." + +#. 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 upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 "" +"다른 리눅스나 유닉스 머신에서 upslug2를 사용할 수 있습니" +"다. 이 소프트웨어는 데비안 꾸러미가 있습니다. 우선 NSLU2를 업그레이드 모드로 " +"놓습니다. USB 포트에서 모든 디스크나 장치를 연" +"결해제합니다. NSLU2를 종료합니다. 리셋 버튼을 눌러서 고정합니다.(accessible " +"through the small hole on the back just above the power input). NSLU2를 켜기 위해 파워 버튼을 눌렀다 놓습니다. ready/status LED를 보면서 10초간 기다립니" +"다. 10초후에는 불이 호박색에서 빨간색으로 바뀔 것입니다. 이 때 빠르게 리셋 버" +"튼을 놓습니다. NSLU2의 ready/status LED " +"는 빨간색과 녹색으로 깜빡일 것입니다.(처음 녹색이 되기 전에 1초의 딜레이가 있" +"습니다.) 이제 NSLU2는 업그레이드 모드입니다. " +"이 과정에서 문제가 생긴다면 NSLU2-Linux pages를 보십시오.NSLU2가 업그레" +"이드 모드에 있다면 새 이미지를 플래시에 써 넣을 수 있습니다:" +"\n" +"sudo upslug2 -i di-nslu2.bin\n" +" Note that the tool also shows the MAC address of " +"이 도구는 DHCP서버를 설정할 때 유용하게 쓸 수 있도록 NSLU2의 MAC 주소도 보여" +"줍니다. 전체 이미지가 쓰여지고 검사된 이후에는 자동적으로 시스템을 재시작합니" +"다. USB 디스크가 잘 연결되었는지 확인하십시요, 그렇지 않으면 설치프로그램이 " +"실패할 것입니다." + +#. 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 a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" +"네트워크를 통해 윈도우에서 펌웨어를 업그레이드할 수 있는 도구" +"가 있습니다. " + +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "CD-ROM에서 부팅하기" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "" +"LILO 혹은 GRUB을 사용해 리눅스 부팅하기" -#~ 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 "" -#~ "플로피 부팅은 &arch-title;에서 지원하지만, 보통 OldWorld 시스템에서만 사" -#~ "용 가능합니다. NewWorld 시스템에는 플로피 드라이브가 없고, 부팅을 지원하" -#~ "지 않는 USB 플로피 드라이브만 붙어 있습니다." +#. 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 ." +msgstr "" +"하드 디스크에서 설치 프로그램을 부팅하려면, 먼저 에서 설명한 필요한 파일들을 내려 받아 하드에 저장해야 합니다." -#~ msgid "" -#~ "To boot from the boot-floppy-hfs.img floppy, place " -#~ "it in floppy drive after shutting the system down, and before pressing " -#~ "the power-on button." -#~ msgstr "" -#~ "boot-floppy-hfs.img 플로피에서 부팅하려면, 시스템을 " -#~ "끄고 전원 단추를 누르기 전에 플로피 드라이브에 넣으십시오." +#. Tag: para +#: boot-installer.xml:856 +#, fuzzy, 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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"하드 드라이브를 부팅용으로만 사용하고 나머지는 모두 네트워크에서 받으려고 한" +"다면, netboot/debian-installer/i386/initrd.gz 파일 및 해" +"당 커널을 받아야 합니다. 설치 프로그램을 부팅한 다음에 하드 디스크를 다시 파" +"티션할 수 있습니다. 단 주의를 기울여야 합니다." + +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"다른 방법으로, 하드 드라이브의 현재 파티션을 바꾸지 않고 유지하려면, " +"hd-media/initrd.gz 파일과 그 커널을 받으시고, CD iso 파" +"일도 드라이브에 복사해 놓으십시오 (파일 이름이 .iso로 끝나" +"도록 하십시오). 그러면 설치 프로그램이 이 드라이브에서 부팅한 다음 네트워크 " +"없이 그 CD 이미지에서 설치할 수 있습니다." + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"LILO의 경우, /etc/lilo.conf에 있는 " +"두 가지 중요한 부분을 설정해야 합니다: 부팅" +"할 때 initrd.gz 설치 프로그램을 읽어들여야 하고 vmlinuz 커널의 루트 파" +"티션으로 램 디스크를 사용하도록 합니다. 여" +"기 예제 /etc/lilo.conf 파일이 있습니다:" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"더 자세한 정보는, initrd " +"4 및 lilo." +"conf 5 맨페이지를 참고" +"하십시오. 이제 lilo를 실행하고 다시 부팅하십시오." + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"GRUB 사용법은 아주 비슷합니다. menu.lst 파일을 /boot/grub/ 디렉토리에 (어떤 경우는 " +"/boot/boot/grub/) 놓고, 다음 줄을 추가하십시오: " +"\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" +" 그리고 다시 부팅하십시오." + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"ramdisk_size의 값을 initrd 이미지 크기에 따라 조정해" +"야 할 수도 있습니다. 이 이후부터는 GRUB와 LILO 사이에 차이점이 없습니다." + +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "USB 메모리 스틱에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +" 및 의 " +"모든 것을 준비했다고 하면, USB 스틱을 빈 USB 커넥터에 꼽고 컴퓨터를 다시 부팅" +"하십시오. 시스템이 부팅해서 boot: 프롬프트가 나와야 합니다. " +"거기에서 부팅 파라미터를 추가로 넣을 수도 있고, 그냥 &enterkey;를 누를 수도 " +"있습니다." + +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "플로피에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"필요한 플로피 이미지를 내려받아서 에 설명한 " +"대로 이미지에서 플로피를 만듭니다." -#~ 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 "" -#~ "Macintosh 플로피 작업에 익숙하지 않은 분들을 위해: 부팅하기 전에 넣은 플로" -#~ "피가 첫 번째 부팅 우선 순위를 가집니다. 부팅 시스템이 없는 플로피는 튀어 " -#~ "나오게 되고, 부팅 가능한 하드 디스크 파티션을 찾게 됩니다." +#. Tag: para +#: boot-installer.xml:949 +#, 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 "" +"설치 프로그램의 부트 플로피에서 부팅하려면, 플로피를 첫 번째 플로피 드라이브" +"에 넣고, 평소에 하던 방법대로 시스템을 끈 다음 다시 켜십시오." -#~ msgid "" -#~ "After booting, the root.bin 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 "" -#~ "부팅한 다음, root.bin 플로피를 요청합니다. 루트 플로" -#~ "피를 넣고 &enterkey;를 누르십시오. 루트 시스템을 메모리에 읽어들이면 설치 " -#~ "프로그램을 자동으로 시작합니다." +#. Tag: para +#: boot-installer.xml:955 +#, fuzzy, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"플로피를 이용해 LS-120 드라이브에서 (ATAPI 버전) 설치하는 경우, 플로피 장치" +"의 가상 위치를 지정해야 합니다. root= 부팅 파라미터를 사" +"용해, ide-floppy 드라이버가 어느 장치로 매핑되는 지 장치를 지정합니다. 예를 " +"들어, LS-120 드라이브가 두 번째 케이블의 첫 번째 (master) IDE 장치에 연결되" +"어 있는 경우, 부팅 프롬프트에서 linux root=/dev/hdc라" +"고 입력합니다. LS-120에서 설치하는 건 2.4 이후의 커널에서만 지원합니다." + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"몇몇 기계에서는 Control Alt " +"Delete 키를 눌러도 컴퓨터를 리셋하지 않기 때문" +"에, 하드 리부팅을 권장합니다. 기존 운영 체제에서 설치하는 경우" +"에는 (예를 들어 DOS에서) 다른 방법이 없습니다. 그 외의 경우에는 항상 부팅할 " +"때 하드 리부팅을 하십시오." + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"플로피 디스크를 읽게 됩니다. 그 다음에 부트 플로피에 대해 소개하는 화면이 나" +"오고 마지막에 boot: 프롬프트가 나옵니다." -#~ msgid "PowerPC Boot Parameters" -#~ msgstr "PowerPC 부팅 파라미터" +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"&enterkey;를 누르면, Loading... 메세지 다음" +"에, Uncompressing Linux...라고 나오고, 시스" +"템의 하드웨어에 관한 여러가지 정보가 화면 가득히 나옵니다. 이 부팅 과정에 대" +"한 더 자세한 정보는 아래의 에 있습니다." + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"부트 플로피에서 부팅한 다음, 루트 플로피를 요청합니다. 루트 플로피를 넣고 " +"&enterkey;를 누르십시오. 그러면 루트 플로피의 내용을 메모리에 읽어들입니다. " +"설치 프로그램 debian-installer를 자동으로 실행합니다." + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "i386에서 TFTP 부팅을 하는 여러 가지 방법이 있습니다." + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "PXE를 지원하는 NIC 혹은 마더보드" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"네트워크 인터페이스 카드나 마더보드에서 PXE 부팅 기능을 지원할 수도 있습니" +"다. PXE는 Intel에서 TFTP 부팅을 다시 " +"만든 것입니다. PXE를 지원하는 경우 네트워크 부팅을 하도록 BIOS를 설정할 수 있" +"을 것입니다." + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "네트워크 부트롬이 들어 있는 NIC" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "네트워크 인터페이스 카드에서 TFTP 부팅 기능을 지원할 수도 있습니다." -#~ 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 " -#~ "video=atyfb:vmode:6 , which will select that mode " -#~ "for most Mach64 and Rage video hardware. For Rage 128 hardware, this " -#~ "changes to video=aty128fb:vmode:6 ." -#~ msgstr "" -#~ "오래된 Apple 모니터는 다수가 640x480 67Hz 모드를 사용합니다. 오래된 Apple " -#~ "모니터에서 화면이 찌그러진다면, video=atyfb:vmode:6 부팅 파라미터를 추가해 보십시오. 그러면 대부분의 Mach64와 Rage " -#~ "비디오 하드웨어에 맞는 비디오 모드를 선택합니다. Rage 128 하드웨어의 경우" -#~ "에는, video=aty128fb:videomode:6이라고 하십시오." +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"어떻게 했는 지 알려 주십시오 (&email-debian-boot-list;). 이 문" +"서를 언급해 주십시오." + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"etherboot project에는 " +"TFTPboot를 할 수 있는 부팅 디스켓과 부트롬이 있습니다." + +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "부팅 프롬프트" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"설치 프로그램이 부팅할 때, 데비안 로고와 다음 부팅 프롬프트가 표시되는 친근" +"한 그래픽 화면이 나타납니다: \n" +"Press F1 for help, or ENTER to boot:\n" +" 부팅 프롬프트에서 그냥 &enterkey; 키를 눌러 기본 " +"옵션으로 설치 프로그램을 부팅할 수도 있고, 특정 부팅 방법이나 부팅 파라미터" +"를 입력할 수도 있습니다." + +#. Tag: para +#: boot-installer.xml:1078 +#, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"F2에서 F8까지 누르다 보면 유용한 부팅 방법" +"과 부팅 파라미터에 대한 정보를 볼 수 있습니다. 부팅 명령행에 파라미터를 넣으" +"려면, 부팅 방법을 입력하는 걸 잊지 마시고 (기본값은 linux), 첫 번째 파라미터 앞에 공백을 넣으십시오 (예를 들어, " +"linux fb=false)." + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"VGA 콘솔 텍스트 인터페이스 기능이 들어 있는 원격 관리 장치를 이용해 시스템을 " +"설치하는 경우에는, 설치 프로그램이 부팅할 때 나타나는 최초의 그래픽 스플래시 " +"화면을 볼 수 없을 수도 있습니다. 부팅 프롬프트조차 볼 수 없을 수도 있습니다. " +"그러한 장치는 Compaq의 integrated Lights Out (iLO) 및 HP의 " +"integrated Remote Assistant가 있습니다. 화면을 보지 못하더라" +"도 F1 어떤 경우 이스케이프 시퀀스를 이용해야 이 키를 누를 " +"수 있습니다. 예를 들어 IRA는 Ctrl F , 1을 사용합니다. 을 누르면 그래픽 화면을 넘어가고 도움말 텍스트를 볼 수 있습니다. 스" +"플래시 스크린이 넘어가면 도움말 텍스트에서 키를 누르면 그 키가 프롬프트에 쓰" +"여집니다. 설치할 때 프레임버퍼를 사용하지 않으려면 도움말 텍스트에 표시된 것" +"처럼 fb=false 옵션을 부팅 프롬프트에 넘깁니다." + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "CD 내용" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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 "" +"세 가지 종류의 데비안 설치 CD가 있습니다. Business Card " +"CD는 작은 CD 미디어에 맞도록 만든 최소한의 설치 미디어입니다. 베이스를 설치하" +"고 쓸만한 시스템을 만들려면 네트워크 연결이 필요합니다. Network " +"Install CD는 베이스 설치에 필요한 모든 꾸러미가 들어 있지만 완전" +"한 시스템에 필요한 추가 꾸러미를 설치하려면 데비안 미러 사이트에 네트워크 연" +"결이 필요합니다. 데비안 CD 세트는 네트워크 접근 없이 여러 가지 꾸러미들을 완" +"전히 설치할 수 있습니다." + +#. Tag: para +#: boot-installer.xml:1180 +#, 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 "" +"IA-64 아키텍처에는 인텔에서 나온 차세대 Extensible Firmware Interface가 " +"(EFI) 들어 있습니다. 전통적인 x86 BIOS는 파티션 테이블과 Master Boot Record " +"(MBR) 외에는 부팅 장치에 대해 거의 아무것도 모르지만, EFI는 FAT16 혹은 FAT32 " +"포맷된 디스크 파티션에 파일을 읽고 쓸 수 있습니다. 이 기능때문에 아주 복잡한 " +"방법으로 시스템을 시작하는 과정도 단순하게 할 수 있습니다. EFI를 지원하는 시" +"스템 부트 로더 및 EFI 펌웨어는 기계를 부팅하는 데 필요한 파일들을 저장하는 완" +"전한 파일 시스템이 따로 있습니다. 즉 IA-64 시스템의 시스템 디스크에는 전통적" +"인 시스템에서 쓰는 단순한 MBR이나 부트 블록이 아닌 EFI만 사용하는 전용 디스" +"크 파티션이 있습니다." + +#. Tag: para +#: boot-installer.xml:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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 "" +"데비안 설치 CD에는 작은 EFI 파티션이 들어 있어서, 거기에 ELILO 부트로더, 그 설정 파일, 설치 프로그램 커널, 파일 시스템(initrd)이 들" +"어 있습니다. 시스템에도 부팅하는 데 필요한 파일들이 들어 있는 EFI 파티션이 들" +"어 있습니다. 이 파일은 아래에 설명한 방법으로 EFI Shell에서 읽을 수 있습니다." + +#. Tag: para +#: boot-installer.xml:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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 "" +"ELILO에서 실제로 어떻게 시스템을 읽어들여서 시작하는 지에 " +"대한 것들은 시스템 설치 프로그램과는 관련이 없습니다. 하지만 설치 프로그램에" +"서는 베이스 시스템을 설치하기 전에 EFI 파티션을 설정해야 합니다. 그렇지 않으" +"면 ELILO 설치가 실패해서, 시스템을 부팅할 수 없게 됩니다. " +"설치할 때 꾸러미를 설치하기 전에 파티션하는 단계에서 EFI 파티션을 만들고 포맷" +"하게 됩니다. 설치를 계속하기 전에 파티션 작업에서 EFI 파티션이 있는 지 검사" +"도 합니다." + +#. Tag: para +#: boot-installer.xml:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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 "" +"펌웨어 초기화의 마지막 단계에서 EFI 부트 매니저가 나타납니다. 메뉴 목록이 나" +"와서 사용자가 그 중의 하나를 선택합니다. 시스템의 모델과 어떤 소프트웨어를 읽" +"어들였느냐에 따라, 이 메뉴는 시스템마다 다릅니다. 최소한 두 개의 메뉴 항목이 " +"있어야 합니다. Boot Option Maintenance Menu 및 " +"EFI Shell (Built-in)입니다. 첫 번째 옵션을 사용하는 게 좋" +"지만, 그 옵션이 없거나 CD가 부팅하지 않는다면 두 번째 옵션을 사용하십시오." + +#. Tag: title +#: boot-installer.xml:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "중요" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" +"EFI Boot Manager에서 정해진 몇 초가 지나면 기본 부팅 동작을 (보통 메뉴에서 " +"첫 번째) 선택합니다. 화면 아래의 카운트다운을 보면 알 수 있습니다. 타이머가 " +"다 되면 기본 동작을 시작하고, 그러면 설치를 계속하기 위해 기계를 다시 부팅해" +"야 할 수도 있습니다. 기본 액션이 EFI Shell인 경우 쉘 프롬프트에서 " +"exit 명령을 실행해 Boot Manager로 돌아오십시오." + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "방법 1: Boot Option Maintenance Menu에서 부팅" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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 "" +"CD를 DVD/CD 드라이브에 넣고 기계를 다시 부팅하십시오. 펌웨어가 시스템 초기화" +"를 마치면 EFI Boot Manager 페이지와 메뉴를 표시합니다." -#~ msgid "" -#~ "On machines with OpenBoot, simply enter the boot monitor on the machine " -#~ "which is being installed (see ). Use " -#~ "the command boot net to boot from a TFTP and RARP " -#~ "server, or try boot net:bootp or boot " -#~ "net:dhcp to boot from a TFTP and BOOTP or DHCP server. Some " -#~ "older OpenBoot revisions require using the device name, such as " -#~ "boot le(); these probably don't support BOOTP nor " -#~ "DHCP." -#~ msgstr "" -#~ "OpenBoot 기계의 경우, 설치하려는 기계의 부트 모니터로 들어가십시오 (). boot net 명령으" -#~ "로 TFTP 및 RARP 서버에서 부팅하거나 boot net:bootp" -#~ "나 boot net:dhcp 명령으로 TFTP와 BOOTP 혹은 DHCP 서" -#~ "버에서 부팅하십시오. 일부 오래된 OpenBoot 버전에서는 boot le()" -#~ "처럼 장치 이름을 써야 합니다; 그러한 버전에서는 BOOTP나 DHCP" -#~ "를 지원하지 않을 것입니다." +#. Tag: para +#: boot-installer.xml:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"메뉴에서 화살표로 Boot Maintenance Menu를 선택해 " +"ENTER를 누르십시오. 그러면 다른 메뉴가 나타납니다." -#~ msgid "" -#~ "Most OpenBoot versions support the boot cdrom " -#~ "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 "" -#~ "대부분의 OpenBoot 버전은 boot cdrom 명령을 지원합니" -#~ "다. 그러면 SCSI 장치의 6번 ID에서 (아니면 IDE 기반 시스템의 경우 " -#~ "secondary master에서) 부팅합니다. 이 명령을 지원하지 않는 옛날 OpenBoot 버" -#~ "전에서는 실제 장치 이름을 써야 할 수도 있습니다. Sun4m에서 (예를 들어 " -#~ "Sparc 10s 및 Sparc 20s) CD-ROM에서 부팅할 때 문제가 발견되었습니다." +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" +"메뉴에서 화살표로 Boot From a File을 선택해 " +"ENTER를 누르십시오. 그러면 펌웨어가 찾은 장치의 목록이 나" +"옵니다. 메뉴에서 Debian Inst [Acpi ... 혹은 " +"Removable Media Boot라고 되어 있는 두 줄이 나옵니다. 그 메" +"뉴 항목의 나머지를 보면, 장치와 컨트롤러 정보가 같은 지 알 수 있습니다." + +#. Tag: para +#: boot-installer.xml:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" +"CD/DVD 드라이브를 가리키는 어떤 항목이든 선택할 수 있습니다. 화살표 키로 선택" +"해서 ENTER를 누릅니다. Removable Media Boot를 선택한 경우 기계가 즉시 부팅 단계로 들어갑니다. 그게 아니라 " +"Debian Inst [Acpi ...를 선택한 경우, CD의 부팅 가능 영역 " +"디렉토리의 내용을 표시하고, 다음 단계로 진행할 수 있습니다." + +#. Tag: para +#: boot-installer.xml:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" +"이 단계는 Debian Inst [Acpi ...를 선택한 경우에만 필요합니" +"다. 디렉토리 목록에서는 마지막 줄 다음에 [Treat like Removable " +"Media Boot]도 표시합니다. 이 줄을 화살표로 선택해 ENTER를 누르십시오. 그러면 부팅 과정을 시작합니다." + +#. Tag: para +#: boot-installer.xml:1302 +#, 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:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "방법 2: EFI Shell에서 부팅" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" +"어떤 이유에서든 방법 1이 실패하면, 기계를 다시 부팅하십시오. EFI Boot " +"Manager 화면에서 EFI Shell [Built-in]이라는 옵션이 있습니" +"다. 다음 과정을 통해 데비안 설치 CD를 부팅하십시오:" -#~ msgid "" -#~ "To boot from floppy on a Sparc, use \n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Be warned that the newer Sun4u (ultra) " -#~ "architecture does not support floppy booting. A typical error message is " -#~ "Bad magic number in disk label - Can't open disk label " -#~ "package. 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 "" -#~ "Sparc에서 플로피에서 부팅하려면, 다음 명령을 사용하십시오: " -#~ "\n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " 단 새로운 Sun4u (ultra) 아키텍처의 경우 플로" -#~ "피 부팅을 지원하지 않습니다. 보통 오류 메세지는 Bad magic " -#~ "number in disk label - Can't open disk label package입니" -#~ "다. 게다가, 많은 Sun4c 모델은 (예를 들어 IPX) 압축한 이미지를 지원하지 않" -#~ "고, 그래서 그러한 모델들은 지원하지 않습니다." +#. Tag: para +#: boot-installer.xml:1324 +#, 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 "" +"CD를 DVD/CD 드라이브에 넣고 기계를 다시 부팅하십시오. 펌웨어가 시스템 초기화" +"를 마치면 EFI Boot Manager 페이지와 메뉴가 나타납니다." -#~ 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 ." -#~ msgstr "" -#~ "일부 Sparc에서는 (예를 들어 Ultra 10) OBP 버그때문에 부팅하지 못합니다. " -#~ "OBP 업데이트는 의 product " -#~ "ID 106121에서 내려받을 수 있습니다." +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" +"메뉴에서 화살표로 EFI Shell을 선택하고 ENTER를 누르십시오. EFI Shell은 부팅 가능한 장치를 모두 검색하고 명령어 프" +"롬프트 앞에 장치 목록을 표시합니다. 찾아낸 부팅 가능 파티션은 " +"fsn: 식으로 이름을 표시합니" +"다. 그 외에 찾아낸 파티션은 blkn: 모양입니다. CD를 넣었다면 쉘에 들어가면서 CD 드라이브를 초기화하는 " +"데 몇 초가 더 걸릴 수 있습니다." + +#. Tag: para +#: boot-installer.xml:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" +"쉘에서 CD-ROM 드라이브를 찾을 때 출력을 잘 살펴보십시오. 다른 장치는 " +"fsn이라고 나올 때 CD-ROM 드라" +"이브는 fs0:이라고 나올 것입니다." -#~ msgid "" -#~ "If you are booting from the floppy, and you see messages such as " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " then it is possible that floppy booting is " -#~ "simply not supported on your machine." -#~ msgstr "" -#~ "플로피에서 부팅하는 경우에 다음과 같은 메세지를 본다면 " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " 플로피 부팅을 지원하지 않는 경우일 수도 있습니" -#~ "다." +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"fsn:이라고 입력하고 " +"ENTER를 눌러 선택하십시오. 여기서 n은 CD-ROM의 파티션 번호입니다. 그러면 파티션 번호가 쉘의 프롬프트" +"에 표시됩니다." + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"elilo라고 입력하고 ENTER를 누르십시오. " +"그러면 부팅 과정을 시작합니다." -#~ msgid "IDPROM Messages" -#~ msgstr "IDPROM 메세지" +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"방법 1과 마찬가지로, 데비안 부트 로더가 시작하면 부트 커널과 옵션을 선택하는 " +"메뉴 페이지를 표시합니다. 쉘 프롬프트에서 더 간단히 " +"fsn:elilo 명령을 입력할 수도 있" +"습니다. 계속해서 부팅 커널과 옵션을 선택하십시오." + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "시리얼 콘솔을 사용해 설치하기" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"설치할 때 모니터와 키보드를 사용할 수도 있고 시리얼 연결을 사용할 수도 있습니" +"다. 모니터/키보드 설정을 이용하려면, [VGA console]이 들어 있는 옵션을 선택하" +"십시오. 시리얼 연결을 통해 설치하려면, [BAUD baud " +"serial console]이 들어 있는 옵션을 선택하십시오. 여기서 BAUD는 시리얼 콘솔의 속도입니다. ttyS0 장치가 가장 일반적인 속도로 설" +"정되어 있는 메뉴 항목이 이미 설정되어 있습니다." + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"대부분의 경우, 설치 프로그램의 속도를 EFI 콘솔 연결과 같게 해야 합니다. 설정" +"을 어떻게 해야 할 지 잘 모르겠다면, EFI 쉘에서 baud 명령으" +"로 알아낼 수 있습니다." -#~ msgid "" -#~ "If you cannot boot because you get messages about a problem with " -#~ "IDPROM, then it's possible that your NVRAM battery, which " -#~ "holds configuration information for you firmware, has run out. See the " -#~ "Sun NVRAM FAQ for more " -#~ "information." -#~ msgstr "" -#~ "IDPROM 관련된 문제에 관한 메세지가 나오면서 부팅하지 못한다" -#~ "면, 펌웨어의 설정 정보가 들어 있는 NVRAM의 배터리가 방전된 경우일 수 있습" -#~ "니다. 자세한 정보는 Sun NVRAM FAQ를 참고하십시오." +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"사용하려는 시리얼 장치나 속도에 맞춰 설정된 옵션이 없다면, 기존 메뉴 옵션의 " +"콘솔 설정을 바꿀 수 있습니다. 예를 들어, ttyS1 장치에 57600 baud 콘솔을 사용" +"하려면, Boot: 텍스트 창에 " +"console=ttyS1,57600n8이라고 입력하십시오." + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" +"대부분의 IA-64 컴퓨터는 기본 콘솔 설정이 9600bps로 되어 있습니다. 이 속도는 " +"상당히 느려서, 기본 설치 과정에서 각 화면을 그릴 때 상당한 시간을 소모하게 됩" +"니다. 설치 과정에서 사용하는 속도를 빠르게 하거나, 텍스트 모드 설치를 고려해 " +"봐야 합니다. 텍스트 모드에서 설치를 시작하려면 Params " +"도움말 메뉴를 참고하십시오." + +#. Tag: para +#: boot-installer.xml:1419 +#, 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:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "부팅 커널과 옵션 선택하기" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" +"부트 로더에서 메뉴 목록과 Boot: 프롬프트가 있는 텍스" +"트 창을 표시합니다. 화살표 키로 메뉴의 항목을 선택할 수 있고 키보드로 입력한 " +"텍스트도 텍스트 창에 나타납니다. 각 펑션 키를 누르면 도움말 화면도 나타납니" +"다. General 도움말 화면은 메뉴 선택에 대해 설명하고 " +"Params 화면은 일반적인 명령행 옵션에 대해 설명합니다." + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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 "" +"General 도움말 화면을 보면 설치하는 데 가장 적합한 커" +"널과 설치 모드에 대한 설명이 있습니다. 또 아래의 에 보면 Boot: 텍스트 창에서 입력할 수 있는 추가 파" +"라미터에 대한 설명이 있습니다. 커널 버전은 설치 과정과 설치된 시스템 모두에 " +"사용할 커널의 버전을 설정합니다. 그래서 설치할 때 커널 문제가 발생하면, 설치" +"한 시스템에서도 같은 문제가 발생할 것입니다. 다음 두 단계에서 설치 모드를 선" +"택하고 설치를 시작합니다:" + +#. Tag: para +#: boot-installer.xml:1460 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "화살표 키로 가장 적합한 커널 버전과 설치 모드를 선택하십시오." -#~ 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:1465 +#, 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 "" +"키보드로 부팅 파라미터가 있으면 입력하십시오. 입력한 텍스트가 텍스트 창에 직" +"접 표시됩니다. 여기에서 커널 파라미터를 지정합니다 (예를 들어 시리얼 콘솔 설" +"정)." -#~ 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:1472 +#, no-c-format +msgid "" +"Press ENTER. 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 "" +"ENTER를 누르십시오. 그러면 커널을 읽어들여서 시작합니다. " +"커널에서 초기화 메세지를 표시한 다음에 데비안 설치 프로그램의 첫 번째 화면이 " +"나타납니다." -#~ msgid "" -#~ "Information on many boot parameters can be found in the Linux BootPrompt " -#~ "HOWTO, including tips for obscure hardware. This section contains " -#~ "only a sketch of the most salient parameters. Some common gotchas are " -#~ "included below in ." -#~ msgstr "" -#~ "부팅 파라미터에 관한 정보는 Linux BootPrompt HOWTO에 (여러가지 보기드" -#~ "문 하드웨어에 대한 정보 포함) 있습니다. 여기서는 몇 가지 많이 이용하는 파" -#~ "라미터에 대한 대략만 다룹니다. 많이 발생하는 문제점 몇 개는 에 들어 있습니다." +#. Tag: para +#: boot-installer.xml:1481 boot-installer.xml:1617 +#, 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 "" +"다음 장으로 가서 언어 로케일, 네트워크, 디스크 파티션 설정을 계속 하십시오." -#~ msgid "" -#~ "When the kernel boots, a message \n" -#~ "Memory:availk/totalk available\n" -#~ " should be emitted early in the process. " -#~ "total 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 mem=ram parameter, where ram " -#~ "is set to the amount of memory, suffixed with k for " -#~ "kilobytes, or m for megabytes. For example, both " -#~ "mem=65536k and mem=64m mean " -#~ "64MB of RAM." -#~ msgstr "" -#~ "커널이 부팅할 때 다음과 같은 메세지가 나와야 합니다: " -#~ "\n" -#~ "Memory:availk/totalk available \n" -#~ " 여기서 total은 전" -#~ "체 RAM의 크기입니다(킬로바이트 단위). 이 숫자가 실제 설치한 RAM의 용량과 " -#~ "다르다면, mem=ram 파라미" -#~ "터를 사용해야 합니다. 여기서 ram은 메모리의 양" -#~ "이고, 킬로바이트의 경우 ``k'', 메가바이트의 경우 ``m''을 뒤에 붙입니다. 예" -#~ "를 들어, mem=65536k나 mem=64m은 모두 64MB의 RAM을 뜻합니다." +#. Tag: para +#: boot-installer.xml:1492 +#, fuzzy, no-c-format +msgid "" +"Booting an IA-64 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 "" +"네트워크에서 IA64 시스템을 부팅하는 건 CD 부팅과 비슷합니다. 차이점은 설치 커" +"널을 읽어들이는 방법입니다. EFI 부트 관리자는 네트워크에 있는 서버에서 프로그" +"램을 읽어들여서 실행할 수 있습니다. 일단 설치 커널을 읽어들이고 실행하면, CD " +"설치와 마찬가지로 시스템 설치를 진행합니다. 차이점은 베이스 설치 꾸러미를 CD " +"드라이브가 아니라 네트워크에서 가져온다는 점입니다." + +#. Tag: para +#: boot-installer.xml:1526 +#, fuzzy, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" +"IA64 시스템에서 네트워크 부팅은 두 가지 아키텍처 전용 작업이 필요합니다. 부" +"트 서버에서는 DHCP와 TFTP에서 elilo를 전송하도록 설정해야 " +"합니다. 클라이언트에서는 EFI 부트 매니저가 네트워크에서 읽어들이게 하는 부트 " +"옵션을 정의해야 합니다." + +#. Tag: title +#: boot-installer.xml:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "서버 설정하기" + +#. Tag: para +#: boot-installer.xml:1538 +#, fuzzy, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" +"IA64 시스템에서 네트워크 부팅을 위한 TFTP 엔트리는 다음과 같습니다: " +"\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" +" 목표는 elilo.efi를 클라이언트" +"에서 실행하는 것입니다." + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" +"netboot.tar.gz 파일을 TFTP 서버의 루트에 쓸 디렉토리에 " +"풀어 놓으십시오. TFTP 루트 디렉토리는 보통 /var/lib/tftp 및 /tftpboot입니다. 파일을 풀면 " +"debian-installer 디렉토리 밑에 IA64 시스템용 부팅 파일들" +"이 들어 있습니다." + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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 "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" + +#. Tag: para +#: boot-installer.xml:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" +"netboot.tar.gz 안에는, 대부분의 경우에 동작하는 " +"elilo.conf 파일이 들어 있습니다. 하지만 이 파일을 수정해" +"야 하는 경우에는, debian-installer/ia64/ 디렉토리 안에 " +"있습니다. 각각의 클라이언트에 대해 다른 설정 파일을 이용하려면 파일이름을 " +"elilo.conf 대신에 클라이언트의 IP 주소를 16진수로 쓰고 " +".conf를 뒤에 붙이면 됩니다. 자세한 설명은 " +"elilo 꾸러미에 들어 있는 문서를 참고하십시오." + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "클라이언트 설정하기" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" +"TFTP 부팅을 지원하도록 클라이언트를 설정하려면, EFI를 부팅해서 Boot " +"Option Maintenance Menu로 들어가십시오. " +" 부트 옵션을 추가하십시오. " +" Load File [Acpi()/.../Mac()] 텍스" +"트가 들어 있는 줄을 볼 수 있을 것입니다. 이런 항목이 여러 줄 있을 때, 부팅하" +"려는 인터페이스의 MAC 주소가 들어 있는 항목을 선택하십시오. 화살표 키로 반전" +"시킨 다음 enter를 누르십시오. 그 항목을 " +"Netboot와 같이 이름 짓고, 저장하고, 부트 옵션 메뉴로 " +"나가십시오. 이제 방금 만든 새로운 부트 옵" +"션을 볼 수 있을 것입니다. 그 옵션을 선택하면 DHCP 쿼리를 하고, 서버에서 " +"elilo.efi 파일을 서버에서 가져옵니다." + +#. Tag: para +#: boot-installer.xml:1608 +#, 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 "" +"부트로더에서 설정 파일을 내려받고 관련된 처리를 한 다음 프롬프트를 표시합니" +"다. 여기까지 오면, CD 설치와 마찬가지로 설치를 진행합니다. 위에서와 같이 부" +"트 옵션을 선택하시고 네트워크에서 커널 설치를 마치면, 데비안 설치 프로그램이 " +"시작합니다." + +#. Tag: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "설치 방법 고르기" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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 "" +"몇몇 &arch-title; 서브 아키텍처는 2.4.x 아니면 2.2.x 리눅스 커널중에 하나를 " +"선택해 부팅하는 옵션이 있습니다. 그렇게 선택할 수 있는 경우, 2.4.x 리눅스 커" +"널을 선택하십시오. 2.4.x 리눅스 커널을 사용할 때 오히려 더 작은 메모리를 사용" +"합니다. 2.2.x는 고정된 크기의 램디스크를 사용하고 2.4.x는 tmpfs를 사용하기 때" +"문입니다." + +#. Tag: para +#: boot-installer.xml:1640 +#, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "" +"2.2.x 커널을 사용한다면, &ramdisksize; 커널 변수를 설정할 필요가 있습니다." -#~ msgid "" -#~ "If you are booting with a serial console, generally the kernel will " -#~ "autodetect this (although not on DECstations). 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 console=device argument to the kernel, where " -#~ "device is your serial device, which is usually " -#~ "something like ttyS0." -#~ msgstr "" -#~ "시리얼 콘솔로 부팅하는 경우, 보통 자동으로 찾아냅니다. (DECstation에서는 아닙니다.) 시리얼 콘솔로 부팅하려는 " -#~ "컴퓨터에 비디오 카드와 (프레임버퍼) 키보드가 붙어 있다면, " -#~ "console=device 파라미터" -#~ "를 커널에 넘겨야 할 수 있습니다. 여기서 device" -#~ "는 시리얼 장치이고, ttyS0과 같이 씁니다." +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "root=/dev/ram을 커널 파라미터로 사용하십시오." -#~ msgid "" -#~ "For &arch-title; the serial devices are ttya or " -#~ "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " -#~ "ttya." -#~ msgstr "" -#~ "&arch-title;에서 시리얼 장치는 ttya 혹은 " -#~ "ttyb입니다. 다른 방법으로, input-device 및 output-device OpenPROM 변수를 ttya로 맞출 수도 있습니다." +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"문제가 있으면, cts's &arch-title; debian-" +"installer FAQ를 참고하십시오." + +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "Amiga" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"Amiga에서 설치하는 유일한 방법은 하드 드라이브입니다. ( 참고) 즉 CD-ROM에서 부팅할 수 없습니다." -#~ msgid "Debian Installer Parameters" -#~ msgstr "데비안 설치 프로그램 파라미터" +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "" +"Amiga does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"현재 Amiga에서는 bogl이 동작하지 않습니다. bogl 오류가 있으면, 커널 파라미터" +"에 fb=false를 포함해야 합니다." + +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "Atari" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "" +"The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" +"Atari용 설치 프로그램은 하드 드라이브에서 시작할 수도 있고 ( 참고) 플로피에서 시작할 수도 있습니다 ( 참고). 즉 CD-ROM에서 부팅할 수 없습니다." + +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "" +"Atari does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"현재 Atari에서는 bogl이 동작하지 않습니다. bogl 오류가 있으면, 커널 파라미터" +"에 fb=false를 포함해야 합니다." + +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "BVME6000" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" +"BVME6000용 설치 프로그램은 CD-ROM ( 참" +"고), 플로피 ( 참고), 혹은 네트워크에서 " +"( 참고) 실행할 수 있습니다." + +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "Macintosh" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"). In other words the cdrom is not " +"bootable. Macs do not have a working 2.4.x kernel." +msgstr "" +"Mac에서 사용할 수 있는 유일한 설치 방법은 하드 드라이브에서 설치하는 것입니" +"다 ( 참고). 즉 CD-ROM에서 부팅할 " +"수 없습니다. Mac에서는 2.4.x 커널이 동작하지 않습니다." -#, fuzzy -#~ msgid "" -#~ "The installation system recognizes a few additional boot " -#~ "parameters With current kernels (2.6.9 or newer) you can " -#~ "use 32 command line options and 32 environment options. If these numbers " -#~ "are exceeded, the kernel will panic. which may be " -#~ "useful." -#~ msgstr "" -#~ "설치 시스템에서는 유용하게 쓸 수도 있는 부팅 파라미터 몇 개를 더 인식합니" -#~ "다 2.4 커널에서는 최대 8개의 명령행 옵션과 8개의 환경 옵" -#~ "션만 사용할 수 있습니다 (설치 프로그램에서 기본으로 사용하는 옵션 포함). " -#~ "이 개수가 넘어가면 2.4 커널에서는 넘어가는 파라미터를 버리고, 2.6 커널은 " -#~ "멎어 버립니다. 커널 2.6.9 이후인 경우 32개의 명령행 옵션과 32개의 환경변수" -#~ "를 사용할 수 있습니다. ." +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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 "" +"53c9x 기반 SCSI 버스를 사용하는 경우, mac53c9x=1 커널 " +"파라미터를 써야 할 수 있습니다. Quadra 950처럼 그런 SCSI 버스가 두 개 있는 하" +"드웨어의 경우 mac53c9x=2 파라미터를 사용해야 합니다.대" +"신,자동발견을 켜기 위해 mac53c9x=-1,0로 설정할 수 있습" +"니다. 하지만 이는 SCSI 연결해제를 불가능하게 할 수있습니다. 이 인수를 설정하" +"는 것은 하나이상의 하드 디스크가 있을때 설정해야 합니다. 그외의 경우, 설정하" +"지 않을 때 시스템이 더 빠르게 동작합니다." + +#. Tag: title +#: boot-installer.xml:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "MVME147 및 MVME16x" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" +"MVME147 및 MVME16x용 설치 프로그램은 플로피 ( 참고) 혹은 네트워크에서 ( 참고) 설" +"치할 수 있습니다. 즉 CD-ROM에서 부팅할 수 없습니다." + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" +"Q40/Q60에서 설치하는 유일한 방법은 하드 드라이브에서 설치하는 것입니다 " +"( 참고). 즉 CD-ROM에서 부팅할 수 없" +"습니다." + +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "하드 디스크에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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 "" +"기존 운영 체제에서 부팅하는 게 가장 편리한 방법입니다. 몇몇 시스템의 경우에" +"는 이게 유일한 설치 방법입니다." -#~ msgid "debconf/priority" -#~ msgstr "debconf/priority" +#. Tag: para +#: boot-installer.xml:1769 boot-installer.xml:2367 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"하드 디스크에서 설치 프로그램을 부팅하려면, 에서 필요한 파일들을 내려 받아서 하드 디스크에 저장해 놓습니다." -#~ msgid "" -#~ "This parameter sets the lowest priority of messages to be displayed. " -#~ "Short form: priority" -#~ msgstr "" -#~ "이 파라미터는 표시할 메시지의 가장 낮은 우선순위를 설정합니다.짧은 형식: " -#~ "priority" +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" +"하드 드라이브에서 부팅하려면 최소한 여섯 가지의 램디스크를 사용할 수 있습니" +"다. 2.2.x 리눅스 커널이 지원하는 3가지와 지원하지 않는 3가지가 있습니다. (자" +"세한 설명은 MANIFEST 참고)" + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" +"세 가지 종류의 램 디스크는 cdrom, hd-media, nativehd입니다. 이 램디스크는 설치 꾸러미의 " +"위치만 다릅니다. cdrom 램디스크는 debian-installer 꾸러" +"미를 CD-ROM에서 가져옵니다. hd-media 램디스크는 하드 디" +"스크에 들어 있는 CD-ROM의 ISO 이미지를 사용합니다. 마지막으로, " +"nativehd 램디스크는 꾸러미를 설치하는 데 네트워크를 사용" +"합니다." + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "AmigaOS에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"Workbench에서는, debian 디렉토리 안" +"의 StartInstall 아이콘을 더블클릭해서 리눅스 설치를 시작하" +"십시오." -#~ msgid "" -#~ "The default installation uses priority=high. 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 "" -#~ "기본 설치에서는 priority=high를 사용합니다. 즉, 높" -#~ "음 우선 순위와 필수 우선순위의 메세지를 표시하지만, 보통과 낮음 우선 순위 " -#~ "메세지는 넘어갑니다. 문제가 발생할 경우에는 설치 프로그램에서 우선순위를 " -#~ "필요에 따라 조정합니다." +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" +"Amiga 설치 프로그램에서 디버깅 정보를 창에 출력하면 &enterkey;를 두 번 눌러" +"야 합니다. 그 다음에 화면이 없어지면 몇 초간 딜레이가 있을 것입니다. 그 다음" +"에 흰 글자의 검은 화면이 나타나고, 커널 디버깅 정보를 표시합니다. 이 메세지" +"는 읽기에는 너무 빠르게 스크롤 되겠지만, 상관없습니다. 몇 초 후에 설치 프로그" +"램이 자동으로 시작하고, 부분으로 넘어가실 수 있" +"습니다." + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "Atari TOS에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" +"GEM 데스크탑에서, debian 디렉토리의 bootstra." +"prg 아이콘을 더블 클릭하고 프로그램 옵션 대화 상자의 " +"Ok를 클릭해 리눅스 설치를 시작하십시오." -#~ msgid "" -#~ "If you add priority=medium as boot parameter, you " -#~ "will be shown the installation menu and gain more control over the " -#~ "installation. When priority=low is used, all " -#~ "messages are shown (this is equivalent to the expert " -#~ "boot method). With priority=critical, the " -#~ "installation system will display only critical messages and try to do the " -#~ "right thing without fuss." -#~ msgstr "" -#~ "priority=medium을 부팅 파라미터로 쓴 경우, 설치 메" -#~ "뉴에서 설치 메뉴에서 더 많은 조정을 할 수 있습니다. " -#~ "priority=low라고 쓴 경우, 모든 메세지를 볼 수 있습" -#~ "니다. (expert 부팅 방법과 동일합니다.) " -#~ "priority=critical의 경우, 필수 메세지만 표시하고 질" -#~ "문들에 신경 쓰지 않고 설치를 진행합니다." +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" +"Atari 부팅 프로그램에서 디버깅 정보를 창에 출력하면 &enterkey;를 눌러야 합니" +"다. 그 다음에 화면이 없어지면 몇 초간 딜레이가 있을 것입니다. 그 다음에 흰 글" +"자의 검은 화면이 나타나고, 커널 디버깅 정보를 표시합니다. 이 메세지는 읽기에" +"는 너무 빠르게 스크롤 되겠지만, 상관없습니다. 몇 초 후에, 설치 프로그램이 자" +"동으로 시작하고, 부분으로 넘어가실 수 있습니다." + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "MacOS에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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 "" +"원래 Mac 시스템을 유지하면서 그 시스템에서 부팅해야 합니다. MacOS가 부팅하면" +"서 Penguin 리눅스 로더 부팅 준비를 할 때, shift 키를 눌러 확" +"장 기능을 읽어들이지 않도록 해야 하는 게 중요합니다. 리" +"눅스를 읽어들이는 것 이외에 MacOS를 사용하지 않는다면, Mac의 시스템 폴더에서 " +"모든 확장 기능과 컨트롤 패널을 지우면 됩니다. 그렇지 않으면 확장 기능을 실행" +"해서 리눅스 커널 실행에 여러 가지 문제가 발생할 수 있습니다." + +#. Tag: para +#: boot-installer.xml:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" +"Mac에서는 Penguin 부트로더가 필요합니다. " +"Stuffit 아카이브를 다루는 도구가 없다면, &penguin19.hfs;" +"가 Penguin이 들어 있는 HFS 디스크 이미지입니다. 에서 이미지를 플로피로 복사하는 방법을 설명합니다." + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." +msgstr "" +"MacOS 데스크탑에서는 Penguin 디렉토리 안의 " +"Penguin Prefs 아이콘을 더블클릭해 리눅스 설치를 시작하십시" +"오. Penguin 부팅 프로그램이 시작합니다. File 메뉴에서 Settings 항목으로 가서, " +"Kernel 탭을 클릭하십시오. 커널과 (vmlinuz) 램디스크 (initrd.gz) 이미지를 " +"install 디렉토리에서 위의 오른쪽의 해당 단추를 클릭해 선" +"택하십시오. 그리고 파일 선택 대화 상자를 이용해 파일을 찾으십시오." + +#. Tag: para +#: boot-installer.xml:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" +"Penguin에서 부팅 파라미터를 설정하려면, File -> " +"Settings...을 선택하시고, Options 탭으로 바꾸십시오. 텍스트 입력 창에서 부팅 파라미터를 입력할 수 있" +"습니다. 항상 그 설정을 이용하려면, File -> " +"Save Settings as Default를 선택하십시오." + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"Settings 대화 상자를 닫고, 설정을 저장하고 " +"File 메뉴의 Boot Now 항목을 이" +"용해 부팅을 시작하십시오." -#~ msgid "DEBIAN_FRONTEND" -#~ msgstr "DEBIAN_FRONTEND" +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" +"Penguin 부팅 프로그램에서 디버깅 정보를 창에 출력합니다. " +"그 다음에 화면이 회색으로 변하고, 몇 초간 딜레이가 있을 것입니다. 그 다음에 " +"흰 글자의 검은 화면이 나타나고, 커널 디버깅 정보를 표시합니다. 이 메세지는 읽" +"기에는 너무 빠르게 스크롤 되겠지만, 상관없습니다. 몇 초 후에, 설치 프로그램" +"이 자동으로 시작하고, 부분으로 넘어가실 수 있습" +"니다." + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "Q40/Q60에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "FIXME" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"설치 프로그램이 자동으로 시작합니다. 부분으로 " +"넘어가실 수 있습니다." -#, fuzzy -#~ msgid "" -#~ "This boot parameter controls the type of user interface used for the " -#~ "installer. The current possible parameter settings are: " -#~ " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " -#~ "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk The default frontend is " -#~ "DEBIAN_FRONTEND=newt. " -#~ "DEBIAN_FRONTEND=text may be preferable for serial " -#~ "console installs. Generally only the newt frontend " -#~ "is available on default install media. On architectures which support it, " -#~ "the graphical installer uses the gtk frontend." -#~ msgstr "" -#~ "이 부팅 파라미터는 설치 프로그램에서 사용할 사용자 인터페이스 종류를 설정" -#~ "합니다. 현재 가능한 파라미터 값은: " -#~ "DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " -#~ "DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses DEBIAN_FRONTEND=bogl " -#~ "DEBIAN_FRONTEND=gtk DEBIAN_FRONTEND=corba 기본 프론트엔드는 " -#~ "DEBIAN_FRONTEND=newt입니다. 시리얼 콘솔 설치의 경" -#~ "우 DEBIAN_FRONTEND=text가 더 좋을 수도 있습니다. 보" -#~ "통 기본 설치 미디어에서는 newt 프론트엔드만 사용할 " -#~ "수 있기 때문에, 이 파라미터는 현재 별로 쓸모가 없습니다." - -#~ msgid "BOOT_DEBUG" -#~ msgstr "BOOT_DEBUG" +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" +"현재 CD-ROM 부팅을 지원하는 &arch-title; 서브 아키텍처는 BVME6000뿐입니다." -#~ 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 "" -#~ "이 부트 파라미터를 2로 설정하면 설치프로그램의 부트 절차를 자세하게 기록" -#~ "할 것입니다. 이 값을 3으로 지정하면 부트 프로세스의 전략적인 부분에서 디버" -#~ "그 셸을 동작합니다. ( 부팅을 계속하려면 이 셸을 종료합니다.)" +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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 "" +"VMEbus 시스템이 부팅하면, LILO Boot: 프롬프트가 나타납니다. " +"프롬프트에서 다음 중의 하나를 입력하면 리눅스를 부팅하고 vt102 터미널 에뮬레" +"이션을 이용해 데비안 설치를 시작합니다." + +#. Tag: para +#: boot-installer.xml:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "" +"BVME4000/6000에 설치하려면 i6000 &enterkey;라고 입력하십시오" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "MVME162에 설치하려면 i162 &enterkey;라고 입력하십시오" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "" +"MVME166/167에 설치하려면 i167 &enterkey;라고 입력하십시오" -#~ msgid "BOOT_DEBUG=0" -#~ msgstr "BOOT_DEBUG=0" +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"vt100 터미널 에뮬레이션을 이용하려면 TERM=vt100 파라미터를 " +"붙일 수 있습니다. 예를 들어, i6000 TERM=vt100 &enterkey;." -#~ msgid "This is the default." -#~ msgstr "기본값입니다." +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" +"대부분의 &arch-title; 아키텍처의 경우, 로컬 파일시스템에서 부팅하는 게 가장 " +"권장하는 방법입니다." -#~ msgid "BOOT_DEBUG=1" -#~ msgstr "BOOT_DEBUG=1" +#. Tag: para +#: boot-installer.xml:2054 +#, 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 "" +"부트 플로피에서 부팅은 현재 Atari와 VMW에서만 (VME의 경우 SCSI 플로피 드라이" +"브가 있으면) 동작합니다." + +#. Tag: title +#: boot-installer.xml:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "SGI TFTP 부팅" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" +"After entering the command monitor use \n" +"bootp():\n" +" 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 netaddr environment variable. Type " +"\n" +"unsetenv netaddr\n" +" in the command monitor to do this." +msgstr "" +"SGI 머신에서 리눅스를 부팅하고 데비안의 설치를 시작하려면 커맨드 모니터로 들" +"어간 다음 다음 명령을 사용하십시오: \n" +"bootp():\n" +" 이렇게 하려면, netaddr 환경 변수" +"를 지워야 할 수도 있습니다. 지우려면 커맨드 모니터에서 다음 명령을 타이프하십" +"시오: \n" +"unsetenv netaddr\n" +"" + +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 +#: boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "Broadcom BCM91250A 과 BCM9140B TFTP 부팅" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: " +"\n" +"ifconfig eth0 -auto\n" +" Once you have obtained an IP address, you can " +"load SiByl with the following command: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 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 "" +"Broadcom BCM91250A 과 BCM9140B 평가보드에서는 TFTP를 통해 SiByl 부트 로더를 " +"읽어들여야 합니다. 그러면 데비안 설치 프로그램을 읽어들여서 시작합니다. 대부" +"분의 경우 DHCP를 통해 IP 주소를 받지만 고정 주소를 설정할 수도 있습니다. DHCP" +"를 사용하려면, CFE 프롬프트에서 다음 명령을 입력하십시오: " +"\n" +"ifconfig eth0 -auto\n" +" IP 주소를 받으면, 다음 명령으로 SiByl을 읽어들일 " +"수 있습니다: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 위의 예에서 IP 주소는 TFTP 주소의 이름 혹은 IP 주" +"소로 바꿔야 합니다. 일단 이 명령을 실행하면, 설치 프로그램을 자동으로 읽어들" +"입니다." + +#. Tag: title +#: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "부팅 파라미터" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" +"SGI에서는 커맨드 모니터에서 부팅 파라미터를 bootp(): 명령" +"어 뒤에 붙일 수 있습니다." -#~ msgid "More verbose than usual." -#~ msgstr "보통때보다 많은 디버깅 정보." +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" +"Following the bootp(): 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: \n" +"bootp():/boot/tftpboot.img\n" +" Further kernel parameters can be passed via " +"append:" +msgstr "" +"bootp/dhcp 서버에서 부팅할 파일을 지정하지 않았다면, bootp(): 명령 뒤에 부팅할 파일의 경로와 이름을 지정할 수 있습니다. 예를 들" +"어: \n" +"bootp():/boot/tftpboot.img\n" +" 그 외의 커널 파라미터는 append" +"를 통해 넘길 수 있습니다:" + +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "bootp(): append=\"root=/dev/sda1\"" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the /boot/sibyl.conf file on the TFTP " +"server and add your parameters to the extra_args " +"variable." +msgstr "" +"CFE 프롬프트에서는 부트 파라미터를 직접 넘길 수 없습니다. 대신에 TFTP 서버에 " +"있는 /boot/sibyl.conf 파일을 편집해서 " +"extra_args 변수에 파라미터를 추가해야 합니다." + +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "Cobalt TFTP 부팅" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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 "" +"엄격히 말해서, Cobalt는 TFTP를 사용하지 않습니다. 대신 NFS를 이용해서 부팅합" +"니다. NFS 서버를 설치하고 설치프로그램 파일을 /nfsroot" +"에 놓을 필요가 있습니다. Cobalt가 부팅할 때, 왼쪽과 오른쪽 커서 버튼을 동시" +"에 누르면 NFS로부터 네트워크 부팅을 할 것입니다. 화면에 여러 옵션이 표시될 것" +"입니다. 다음 두 가지 방법이 있습니다." + +#. Tag: para +#: boot-installer.xml:2170 +#, 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 "" +"SSH를 이용해서(default): 이 경우 설치프로그램은 DHCP를 이용해서 네트워크를 설" +"정하고 SSH 서버를 시작할 것입니다. Cobalt LCD에 임의의 열쇠글과 다른 로그인 " +"정보(IP 주소 같은)를 표시할 것입니다. SSH 클라이언트를 이용해서 머신에 접속하" +"면 설치를 시작할 수 있습니다." + +#. Tag: para +#: boot-installer.xml:2179 +#, 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 "" +"시리얼 콘솔을 이용해서: 널모뎀 케이블을 이용하면 Cobalt 머신의 시리얼 포트로" +"(115200 bps 속도로) 접속하여 설치를 수행할 수 있습니다. 이 옵션은 Qube 2700 " +"(Qube1) 머신에서는 사용할 수 없습니다. 이 머신에는 시리얼 포트가 없기 떄문입" +"니다." + +#. Tag: para +#: boot-installer.xml:2222 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"/nfsroot/default.colo file on the NFS server and add " +"your parameters to the args variable." +msgstr "" +"CFE 프롬프트에서는 부트 파라미터를 직접 넘길 수 없습니다. 대신, NFS 서버에서 " +"/nfsroot/default.colo을 편집해서 args에 파라미터를 추가하면 됩니다" + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "s390 한계" + +#. Tag: para +#: boot-installer.xml:2251 +#, no-c-format +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" +"S/390에서 설치 시스템을 실행하려면 제대로 동작하는 네트워크 설정이 있어야 하" +"고 SSH 세션이 필요합니다." -#~ msgid "BOOT_DEBUG=2" -#~ msgstr "BOOT_DEBUG=2" +#. Tag: para +#: boot-installer.xml:2256 +#, 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 an ssh session which will launch the standard installation " +"system." +msgstr "" +"부팅 과정은 몇 가지 네트워크 파라미터를 설정하는 네트워크 설정으로 시작합니" +"다. 설정이 성공하면, SSH 세션으로 로그인해서 거기에서 표준 설치 시스템을 시작" +"합니다." + +#. Tag: title +#: boot-installer.xml:2267 +#, no-c-format +msgid "s390 Boot Parameters" +msgstr "s390 부팅 파라미터" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more " +"information about S/390-specific boot parameters." +msgstr "" +"S/390에서는 parm 파일에 부팅 파라미터를 추가할 수 있습니다. ASCII나 EBCDIC 형" +"식을 쓸 수 있습니다. S/390 관련 부팅 파라미터에 관한 더 자세한 정보는 Device Drivers and Installation Commands" +"를 읽어 보십시오." + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, " +"Option, Shift, and Delete " +"keys together while booting to boot from the CD-ROM." +msgstr "" +"현재, &arch-title; 서브 아키텍처중에서 CD-ROM 부팅을 지원하는 경우는 PReP 및 " +"New World PowerMac뿐입니다. PowerMac에서 CD-ROM 부팅을 하려면, c 키를 누르고 있거나, Command, Option, Shift, Delete 키를 동시에 누르고 " +"있으십시오." + +#. Tag: para +#: boot-installer.xml:2331 +#, 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 "" +"OldWorld PowerMacs은 데비안 CD를 부팅하지 못합니다. OldWorld 컴퓨터는 CD에 있" +"는 Mac OS ROM CD 부트 드라이버에 의존하기 때문입니다. 그리고 이 드라이버는 자" +"유 소프트웨어 버전이 없습니다. 모든 OldWorld 시스템에는 플로피 드라이브가 있" +"으므로, 이 플로피 드라이브로 설치 프로그램을 실행하십시오. 그 다음에 설치 프" +"로그램에서 필요한 파일이 있으면 CD를 지정하십시오." + +#. Tag: para +#: boot-installer.xml:2340 +#, 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 for booting from the hard disk, except use the " +"path to yaboot on the CD at the OF prompt, such as" +msgstr "" +"시스템이 CD-ROM에서 직접 부팅하지 못하는 경우에도, CD-ROM을 사용해 시스템을 " +"설치할 수 있습니다. NewWorld에서는 OpenFirmware 명령을 이용해 CD-ROM을 수동으" +"로 부팅할 수 있습니다. 하드디스크에 부팅하려면 에 있는 설명을 따라하십시오. 단 다음과 같이 CD에 있는 yaboot 경로를 사용하십시오" + +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "0 > boot cd:,\\install\\yaboot" + +#. Tag: title +#: boot-installer.xml:2355 +#, no-c-format +msgid "Booting from Hard Disk" +msgstr "하드 디스크에서 부팅하기" + +#. Tag: title +#: boot-installer.xml:2376 +#, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "OpenFirmware에서 CHRP 부팅하기" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "Not yet written." + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "MacOS에서 OldWorld PowerMac 부팅하기" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"If you set up BootX in , you can use it to " +"boot into the installation system. Double click the BootX " +"application icon. Click on the Options button and " +"select Use Specified RAM Disk. This will give you the " +"chance to select the ramdisk.image.gz file. You may " +"need to select the No Video Driver checkbox, depending " +"on your hardware. Then click the Linux button to shut " +"down MacOS and launch the installer." +msgstr "" +"의 BootX를 설정하는 경우, BootX를 이용해 설" +"치 시스템을 부팅할 수 있습니다. BootX 애플리케이션 아이콘" +"을 더블 클릭하십시오. Options 단추를 클릭해 " +"Use Specified RAM Disk를 선택하십시오. 그러면 " +"ramdisk.image.gz 파일을 선택할 수 있습니다. 하드웨어에 " +"따라서는 No Video Driver 체크박스를 선택해야 할 수도 있" +"습니다. 그리고 Linux 단추를 눌러 MacOS를 끝내고 설치 " +"프로그램을 시작하십시오." + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "OpenFirmware에서 NewWorld Mac 부팅하기" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" +"You will have already placed the vmlinux, " +"initrd.gz, yaboot, and " +"yaboot.conf files at the root level of your HFS " +"partition in . Restart the computer, and " +"immediately (during the chime) hold down the Option, " +"Command (cloverleaf/Apple), o, and " +"f keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"\n" +"0 > boot hd:x,yaboot\n" +" replacing x 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 " +"ide0: instead of hd:. In a few " +"more seconds you will see a yaboot prompt \n" +"boot:\n" +" At yaboot's boot: prompt, type " +"either install or install video=ofonly followed by a &enterkey;. The video=ofonly " +"argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" +"의 vmlinux, " +"initrd.gz, yaboot, " +"yaboot.conf 파일을 HFS 파티션의 맨 위에 저장해 놓으십시" +"오. 컴퓨터를 다시 시작하고, 즉시 (삐 소리가 날 때) Option, " +"Command (클로버잎/Apple), o, f 키를 동시에 누르고 있으십시오. 몇 초 후에 Open Firmware 프롬프트가 나" +"타납니다. 프롬프트에서 다음을 입력하십시오: \n" +"0 > boot hd:x,yaboot\n" +" 여기서 x를 커널과 " +"yaboot 파일이 들어 있는 HFS 파티션의 파티션 번호로 바꾸시고, &enterkey;를 누" +"르십시오. 일부 시스템에서는, hd: 대신에 " +"ide0:을 써야 할 수도 있습니다. 몇 초 안에 yaboot 프롬" +"프트를 볼 수 있을 겁니다 \n" +"boot:\n" +" yaboot의 boot: 프롬프트에서 " +"install 혹은 install video=ofonly 명령을 입력하고 &enterkey;를 누르십시오. video=ofonly 인수는 install이 동작하지 않을 때에 호환성" +"을 최대화하기 위해 시도해 볼 수 있습니다. 그러면 데비안 설치 프로그램이 시작" +"합니다." + +#. Tag: title +#: boot-installer.xml:2440 +#, no-c-format +msgid "Booting from USB memory stick" +msgstr "USB 메모리 스틱에서 부팅하기" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" +"현재 NewWorld PowerMacs 시스템은 USB 부팅을 지원한다고 알려져 있습니다." -#~ msgid "Lots of debugging information." -#~ msgstr "디버깅 정보 아주 많이." +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "" +"Make sure you have prepared everything from . 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 " +"Command Option o f all together while booting (see )." +msgstr "" +"에 있는 모든 걸 준비해야 합니다. Macintosh " +"시스템을 USB 스틱에서 부팅하려면, Open Firmware는 USB 저장 장치를 검색하지 않" +"기 때문에 프롬프트를 직접 사용해야 합니다. 프롬프트가 나오게 하려면, " +"Command Option o f 키를 부팅하는 동안 동시에 누르고 계십시" +"오. ( 참고)" + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment ofpath cannot work that out " +"automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " +"/pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" +"장치 트리에서 USB 저장 장치가 나타나는 위치를 조정할 필요가 있습니다. 현재는 " +"ofpath에서 자동으로 조정하지 못하기 때문입니다. Open " +"Firmware 프롬프트에서 dev / ls 및 " +"devalias 명령으로 모든 장치와 장치 별명의 목록을 보십" +"시오. 예를 들어 문서 저자의 시스템에는 usb0/disk, " +"usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, 그리고 /pci@f2000000/usb@1b,1/hub@1/disk@1이 " +"동작하고 있습니다." + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" +"Having worked out the device path, use a command like this to boot the " +"installer: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" The 2 matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the ,\\\\:tbxi part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"yaboot) in the directory previously blessed with " +"hattrib -b." +msgstr "" +"장치 경로를 조정하고 나면, 다음과 같은 명령으로 설치 프로그램을 시작하십시" +"오: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" 여기서 2는 앞에서 부" +"트 이미지를 복사해 놓은 Apple_HFS 혹은 Apple_Bootstrap 파티션이고, " +",\\\\:tbxi 부분은 전에 hattrib -b " +"해 놓은 디렉토리에 있는 \"tbxi\" 타입의 HFS 파일에서 (예를 들어 " +"yaboot) 부팅하도록 Open Firmware에 알려 주는 역할을 합니" +"다." + +#. Tag: para +#: boot-installer.xml:2485 +#, no-c-format +msgid "" +"The system should now boot up, and you should be presented with the " +"boot: prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." +msgstr "" +"시스템이 부팅하고, boot: 프롬프트가 나타납니다. 여기서 다른 " +"부팅 파라미터가 필요하면 입력하고, 아니면 그냥 &enterkey;를 누르십시오." -#~ msgid "BOOT_DEBUG=3" -#~ msgstr "BOOT_DEBUG=3" +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" +"이 부팅 방법은 새로운 방법으로, 일부 NewWorld 시스템에서는 어려울 수도 있습니" +"다. 문제가 있으면 설치 보고서를 에 설명되어 있" +"는 대로 제출해 주십시오." + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "현재, PReP 및 New World PowerMac 시스템은 네트부팅을 지원합니다." + +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see ) and use the command " +"boot enet:0. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try boot " +"server_ipaddr,file," +"client_ipaddr." +msgstr "" +"NewWorld Power Mac과 같은 Open Firmware 기계에서는, 부트 모니터로 들어가서 " +"( 참고) boot enet:0 명령을 사용하십시오. PReP 및 CHRP 컴퓨터는 네트워크 위치를 지정하는 " +"방법이 다릅니다. PReP 기계에서는, boot " +"server_ipaddr,file," +"client_ipaddr라고 시도해 보십시오." + +#. Tag: para +#: boot-installer.xml:2543 +#, 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 "" +"플로피 부팅은 &arch-title;에서 지원하지만, 보통 OldWorld 시스템에서만 사용 가" +"능합니다. NewWorld 시스템에는 플로피 드라이브가 없고, 부팅을 지원하지 않는 " +"USB 플로피 드라이브만 붙어 있습니다." -#~ msgid "" -#~ "Shells are run at various points in the boot process to allow detailed " -#~ "debugging. Exit the shell to continue the boot." -#~ msgstr "" -#~ "부팅 과정의 곳곳에서 쉘을 실행해서 자세히 디버깅을 할 수 있습니다. 부팅을 " -#~ "계속하려면 쉘을 나가면 됩니다." +#. Tag: para +#: boot-installer.xml:2555 +#, no-c-format +msgid "" +"To boot from the boot-floppy-hfs.img floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." +msgstr "" +"boot-floppy-hfs.img 플로피에서 부팅하려면, 시스템을 끄" +"고 전원 단추를 누르기 전에 플로피 드라이브에 넣으십시오." -#~ msgid "INSTALL_MEDIA_DEV" -#~ msgstr "INSTALL_MEDIA_DEV" +#. Tag: para +#: boot-installer.xml:2561 +#, 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 "" +"Macintosh 플로피 작업에 익숙하지 않은 분들을 위해: 부팅하기 전에 넣은 플로피" +"가 첫 번째 부팅 우선 순위를 가집니다. 부팅 시스템이 없는 플로피는 튀어 나오" +"게 되고, 부팅 가능한 하드 디스크 파티션을 찾게 됩니다." -#~ msgid "" -#~ "The value of the parameter is the path to the device to load the Debian " -#~ "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ msgstr "" -#~ "이 파라미터의 값은 데비안 설치 프로그램을 읽어들일 장치의 경로입니다. 예" -#~ "를 들어 INSTALL_MEDIA_DEV=/dev/floppy/0" +#. Tag: para +#: boot-installer.xml:2568 +#, no-c-format +msgid "" +"After booting, the root.bin 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 "" +"부팅한 다음, root.bin 플로피를 요청합니다. 루트 플로피" +"를 넣고 &enterkey;를 누르십시오. 루트 시스템을 메모리에 읽어들이면 설치 프로" +"그램을 자동으로 시작합니다." + +#. Tag: title +#: boot-installer.xml:2579 +#, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "PowerPC 부팅 파라미터" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 " +"video=atyfb:vmode:6 , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"video=aty128fb:vmode:6 ." +msgstr "" +"오래된 Apple 모니터는 다수가 640x480 67Hz 모드를 사용합니다. 오래된 Apple 모" +"니터에서 화면이 찌그러진다면, video=atyfb:vmode:6 부" +"팅 파라미터를 추가해 보십시오. 그러면 대부분의 Mach64와 Rage 비디오 하드웨어" +"에 맞는 비디오 모드를 선택합니다. Rage 128 하드웨어의 경우에는, " +"video=aty128fb:videomode:6이라고 하십시오." + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see ). Use " +"the command boot net to boot from a TFTP and RARP " +"server, or try boot net:bootp or boot net:" +"dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " +"OpenBoot revisions require using the device name, such as boot le" +"(); these probably don't support BOOTP nor DHCP." +msgstr "" +"OpenBoot 기계의 경우, 설치하려는 기계의 부트 모니터로 들어가십시오 (). boot net 명령으로 " +"TFTP 및 RARP 서버에서 부팅하거나 boot net:bootp나 " +"boot net:dhcp 명령으로 TFTP와 BOOTP 혹은 DHCP 서버에" +"서 부팅하십시오. 일부 오래된 OpenBoot 버전에서는 boot le()처럼 장치 이름을 써야 합니다; 그러한 버전에서는 BOOTP나 DHCP를 지원" +"하지 않을 것입니다." + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "" +"Most OpenBoot versions support the boot cdrom 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 "" +"대부분의 OpenBoot 버전은 boot cdrom 명령을 지원합니" +"다. 그러면 SCSI 장치의 6번 ID에서 (아니면 IDE 기반 시스템의 경우 secondary " +"master에서) 부팅합니다. 이 명령을 지원하지 않는 옛날 OpenBoot 버전에서는 실" +"제 장치 이름을 써야 할 수도 있습니다. Sun4m에서 (예를 들어 Sparc 10s 및 " +"Sparc 20s) CD-ROM에서 부팅할 때 문제가 발견되었습니다." + +#. Tag: para +#: boot-installer.xml:2691 +#, no-c-format +msgid "" +"To boot from floppy on a Sparc, use \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"Bad magic number in disk label - Can't open disk label " +"package. 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 "" +"Sparc에서 플로피에서 부팅하려면, 다음 명령을 사용하십시오: " +"\n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" 단 새로운 Sun4u (ultra) 아키텍처의 경우 플로피 부" +"팅을 지원하지 않습니다. 보통 오류 메세지는 Bad magic number " +"in disk label - Can't open disk label package입니다. 게다" +"가, 많은 Sun4c 모델은 (예를 들어 IPX) 압축한 이미지를 지원하지 않고, 그래서 " +"그러한 모델들은 지원하지 않습니다." + +#. Tag: para +#: boot-installer.xml:2703 +#, 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 ." +msgstr "" +"일부 Sparc에서는 (예를 들어 Ultra 10) OBP 버그때문에 부팅하지 못합니다. OBP " +"업데이트는 의 product ID " +"106121에서 내려받을 수 있습니다." -#~ msgid "" -#~ "The boot floppy, which normally scans all floppies it can to find the " -#~ "root floppy, can be overridden by this parameter to only look at the one " -#~ "device." -#~ msgstr "" -#~ "부트 플로피는 루트 플로피를 찾으면서, 검색할 수 있는 모든 플로피 장치를 검" -#~ "색합니다. 이 파라미터를 재지정해서 장치 한 개만 검색하도록 만들 수 있습니" -#~ "다." +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"If you are booting from the floppy, and you see messages such as " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" then it is possible that floppy booting is " +"simply not supported on your machine." +msgstr "" +"플로피에서 부팅하는 경우에 다음과 같은 메세지를 본다면 " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" 플로피 부팅을 지원하지 않는 경우일 수도 있습니다." + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "IDPROM 메세지" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"IDPROM, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"Sun NVRAM FAQ for more " +"information." +msgstr "" +"IDPROM 관련된 문제에 관한 메세지가 나오면서 부팅하지 못한다" +"면, 펌웨어의 설정 정보가 들어 있는 NVRAM의 배터리가 방전된 경우일 수 있습니" +"다. 자세한 정보는 Sun NVRAM FAQ를 " +"참고하십시오." + +#. Tag: para +#: boot-installer.xml:2742 +#, 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 "" +"부팅 파라미터는 리눅스 커널 파라미터로 보통 주변 장치를 제대로 동작하도록 제" +"어하는 데 이용합니다. 대부분 커널에서 주변 장치에 관한 정보를 자동으로 찾아 " +"냅니다. 하지만 몇몇 경우에는 파라미터로 커널을 조금 도와줘야 합니다." -#~ msgid "debian-installer/framebuffer" -#~ msgstr "debian-installer/framebuffer" +#. Tag: para +#: boot-installer.xml:2749 +#, 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:2756 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +"부팅 파라미터에 관한 정보는 Linux BootPrompt HOWTO에 (여러가지 보기드문 " +"하드웨어에 대한 정보 포함) 있습니다. 여기서는 몇 가지 많이 이용하는 파라미터" +"에 대한 대략만 다룹니다. 많이 발생하는 문제점 몇 개는 에 들어 있습니다." + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" +"When the kernel boots, a message \n" +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total 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 mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" +"커널이 부팅할 때 다음과 같은 메세지가 나와야 합니다: " +"\n" +"Memory:availk/totalk " +"available \n" +" 여기서 total은 전체 " +"RAM의 크기입니다(킬로바이트 단위). 이 숫자가 실제 설치한 RAM의 용량과 다르다" +"면, mem=ram 파라미터를 사용" +"해야 합니다. 여기서 ram은 메모리의 양이고, 킬로바" +"이트의 경우 ``k'', 메가바이트의 경우 ``m''을 뒤에 붙입니다. 예를 들어, " +"mem=65536k나 mem=64m은 모두 " +"64MB의 RAM을 뜻합니다." + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this (although not on DECstations). 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 console=device " +"argument to the kernel, where device is your " +"serial device, which is usually something like ttyS0." +msgstr "" +"시리얼 콘솔로 부팅하는 경우, 보통 자동으로 찾아냅니다. (DECstation에서는 아닙니다.) 시리얼 콘솔로 부팅하려는 컴퓨터에 비" +"디오 카드와 (프레임버퍼) 키보드가 붙어 있다면, " +"console=device 파라미터를 " +"커널에 넘겨야 할 수 있습니다. 여기서 device는 시리" +"얼 장치이고, ttyS0과 같이 씁니다." + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"&arch-title;에서 시리얼 장치는 ttya 혹은 " +"ttyb입니다. 다른 방법으로, input-device " +"및 output-device OpenPROM 변수를 ttya로 " +"맞출 수도 있습니다." + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "데비안 설치 프로그램 파라미터" + +#. Tag: para +#: boot-installer.xml:2806 +#, fuzzy, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"설치 시스템에서는 유용하게 쓸 수도 있는 부팅 파라미터 몇 개를 더 인식합니다" +" 2.4 커널에서는 최대 8개의 명령행 옵션과 8개의 환경 옵션만 " +"사용할 수 있습니다 (설치 프로그램에서 기본으로 사용하는 옵션 포함). 이 개수" +"가 넘어가면 2.4 커널에서는 넘어가는 파라미터를 버리고, 2.6 커널은 멎어 버립니" +"다. 커널 2.6.9 이후인 경우 32개의 명령행 옵션과 32개의 환경변수를 사용할 수 " +"있습니다. ." + +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "debconf/priority" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"이 파라미터는 표시할 메시지의 가장 낮은 우선순위를 설정합니다.짧은 형식: " +"priority" -#~ 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 debian-installer/" -#~ "framebuffer=false, or fb=false for " -#~ "short. Problem symptoms are error messages about bterm or bogl, a blank " -#~ "screen, or a freeze within a few minutes after starting the install." -#~ msgstr "" -#~ "어떤 아키텍처에서는 커널 프레임 버퍼를 사용해 여러 가지 언어로 설치를 지원" -#~ "합니다. 프레임버퍼가 문제가 있는 경우 debian-installer/" -#~ "framebuffer=false 혹은 fb=false 파라미" -#~ "터를 통해 프레임버퍼를 끌 수 있습니다. 문제의 증상은 bterm이나 bogl 관련" -#~ "된 오류 메세지, 검은 화면, 설치를 시작하고 몇 분 후에 멈추는 증상입니다." +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "" +"The default installation uses priority=high. 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 "" +"기본 설치에서는 priority=high를 사용합니다. 즉, 높음 " +"우선 순위와 필수 우선순위의 메세지를 표시하지만, 보통과 낮음 우선 순위 메세지" +"는 넘어갑니다. 문제가 발생할 경우에는 설치 프로그램에서 우선순위를 필요에 따" +"라 조정합니다." + +#. Tag: para +#: boot-installer.xml:2836 +#, no-c-format +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"priority=medium을 부팅 파라미터로 쓴 경우, 설치 메뉴에" +"서 설치 메뉴에서 더 많은 조정을 할 수 있습니다. priority=low라고 쓴 경우, 모든 메세지를 볼 수 있습니다. (expert 부팅 방법과 동일합니다.) priority=critical" +"의 경우, 필수 메세지만 표시하고 질문들에 신경 쓰지 않고 설치를 진행합니다." + +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "DEBIAN_FRONTEND" + +#. Tag: para +#: boot-installer.xml:2851 +#, fuzzy, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " +" The default frontend is " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text may be preferable for serial " +"console installs. Generally only the newt frontend is " +"available on default install media. On architectures which support it, the " +"graphical installer uses the gtk frontend." +msgstr "" +"이 부팅 파라미터는 설치 프로그램에서 사용할 사용자 인터페이스 종류를 설정합니" +"다. 현재 가능한 파라미터 값은: " +"DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +" DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=slang " +"DEBIAN_FRONTEND=ncurses DEBIAN_FRONTEND=bogl " +" DEBIAN_FRONTEND=gtk DEBIAN_FRONTEND=corba 기본 프론트엔드는 " +"DEBIAN_FRONTEND=newt입니다. 시리얼 콘솔 설치의 경우 " +"DEBIAN_FRONTEND=text가 더 좋을 수도 있습니다. 보통 기" +"본 설치 미디어에서는 newt 프론트엔드만 사용할 수 있기 " +"때문에, 이 파라미터는 현재 별로 쓸모가 없습니다." + +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "BOOT_DEBUG" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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 "" +"이 부트 파라미터를 2로 설정하면 설치프로그램의 부트 절차를 자세하게 기록할 것" +"입니다. 이 값을 3으로 지정하면 부트 프로세스의 전략적인 부분에서 디버그 셸을 " +"동작합니다. ( 부팅을 계속하려면 이 셸을 종료합니다.)" + +#. Tag: userinput +#: boot-installer.xml:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "BOOT_DEBUG=0" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "기본값입니다." + +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "BOOT_DEBUG=1" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "보통때보다 많은 디버깅 정보." + +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "BOOT_DEBUG=2" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "디버깅 정보 아주 많이." + +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "BOOT_DEBUG=3" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "INSTALL_MEDIA_DEV" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"이 파라미터의 값은 데비안 설치 프로그램을 읽어들일 장치의 경로입니다. 예를 들" +"어 INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ msgid "" -#~ "The video=vga16:off argument may also be used to " -#~ "disable the kernel's use of the framebuffer. Such problems have been " -#~ "reported on a Dell Inspiron with Mobile Radeon card." -#~ msgstr "" -#~ "video=vga16:off 파라미터로 커널이 프레임버퍼를 사용" -#~ "하지 않도록 만들 수 있습니다. 그러한 문제는 Mobile Radeon 카드를 사용하는 " -#~ "Dell Inspiron에서 보고되었습니다." +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "" +"The boot floppy, which normally scans all floppies 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:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "debian-installer/framebuffer" + +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/" +"framebuffer=false, or fb=false for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." +msgstr "" +"어떤 아키텍처에서는 커널 프레임 버퍼를 사용해 여러 가지 언어로 설치를 지원합" +"니다. 프레임버퍼가 문제가 있는 경우 debian-installer/" +"framebuffer=false 혹은 fb=false 파라미터" +"를 통해 프레임버퍼를 끌 수 있습니다. 문제의 증상은 bterm이나 bogl 관련된 오" +"류 메세지, 검은 화면, 설치를 시작하고 몇 분 후에 멈추는 증상입니다." + +#. Tag: para +#: boot-installer.xml:2948 +#, no-c-format +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"video=vga16:off 파라미터로 커널이 프레임버퍼를 사용하" +"지 않도록 만들 수 있습니다. 그러한 문제는 Mobile Radeon 카드를 사용하는 Dell " +"Inspiron에서 보고되었습니다." + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "Amiga 1200과 SE/30에서 그러한 문제가 보고되었습니다." + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "hppa에서 그러한 문제가 보고되었습니다." + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"disabled by default 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 debian-installer/" +"framebuffer=true or fb=true for short." +msgstr "" +"일부 시스템의 화면 표시 문제때문에, &arch-title;에서는 프레임 버퍼를 " +"기본으로 지원하지 않습니다. 그 때문에 ATI 그래픽 카드같" +"은 게 있어서 프레임버퍼를 지원하는 시스템에서조차 화면 표시가 보기가 안 좋을 " +"수도 있습니다. 설치 프로그램에서 화면 표시 문제가 발생하면, " +"debian-installer/framebuffer=true 혹은 짧은 형식으로 " +"fb=true 파라미터를 넣고 부팅해 보십시오." + +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a dark theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter debian-installer/theme=dark or theme=dark." +msgstr "" +"테마는 설치 프로그램의 사용자 환경(색상,아이콘, 등등)을 어떻게 보여줄 것인가" +"를 결정합니다. 프런트엔드에 따라 사용할 수 있는 테마가 달라집니다. 현재 newt" +"와 gtk 프런트엔드에서는 시각장애인을 위한 dark테마만 있습니" +"다. 이 테마를 설정하려면 부팅시에 debian-installer/" +"theme=dark 또는 " +"theme=dark를 인수로 주면 됩" +"니다." + +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "debian-installer/probe/usb" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "" +"부팅할 때 USB 검색이 문제가 있는 경우, false로 설정해 " +"USB 검색을 하지 않습니다." + +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "netcfg/disable_dhcp" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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 "" +"기본값으로, &d-i;는 DHCP를 통해 네트워크 설정을 검색합니다. 검색이 성공하면, " +"그 설정을 검사해 보거나 바꿀 기회가 없습니다. DHCP 검색이 실패할 경우에만 수" +"동 네트워크 셋업을 할 수 있습니다." -#~ msgid "Such problems have been reported on the Amiga 1200 and SE/30." -#~ msgstr "Amiga 1200과 SE/30에서 그러한 문제가 보고되었습니다." +#. Tag: para +#: boot-installer.xml:3008 +#, 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 " +"netcfg/disable_dhcp=true to prevent configuring the " +"network with DHCP and to enter the information manually." +msgstr "" +"랜에 DHCP 서버가 있지만 DHCP를 사용하고 싶지 않을 때 (예를 들어 잘못된 응답" +"을 한다든지 때문에), netcfg/disable_dhcp=true 파라미터" +"를 사용하면 DHCP 네트워크 설정을 막고 수동으로 정보를 입력할 수 있습니다." + +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "hw-detect/start_pcmcia" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"PCMCIA에 문제가 있을 때 false로 하면 PCMCIA 서비스를 " +"시작하지 않습니다. 일부 노트북 컴퓨터에서 이와 관련해 문제가 발생합니다." + +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "preseed/url" + +#. Tag: para +#: boot-installer.xml:3031 +#, fuzzy, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url." +msgstr "" +"미리 설정해 놓은 파일을 내려받을 URL을 지정합니다. 이 파일을 이용해 설치를 자" +"동화합니다. 참고. 짧은 형식: " +"url" + +#. Tag: term +#: boot-installer.xml:3041 +#, no-c-format +msgid "preseed/file" +msgstr "preseed/file" + +#. Tag: para +#: boot-installer.xml:3042 +#, fuzzy, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file." +msgstr "" +"미리 설정해 놓은 파일을 읽어들일 URL을 지정합니다. 이 파일을 이용해 자동 설치" +"를 합니다. 참고. 짧은 형식: " +"file" + +#. Tag: term +#: boot-installer.xml:3052 +#, fuzzy, no-c-format +msgid "auto-install/enabled" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" -#~ msgid "Such problems have been reported on hppa." -#~ msgstr "hppa에서 그러한 문제가 보고되었습니다." +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "cdrom-detect/eject" -#~ msgid "" -#~ "Because of display problems on some systems, framebuffer support is " -#~ "disabled by default 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 " -#~ "debian-installer/framebuffer=true or " -#~ "fb=true for short." -#~ msgstr "" -#~ "일부 시스템의 화면 표시 문제때문에, &arch-title;에서는 프레임 버퍼를 " -#~ "기본으로 지원하지 않습니다. 그 때문에 ATI 그래픽 카드" -#~ "같은 게 있어서 프레임버퍼를 지원하는 시스템에서조차 화면 표시가 보기가 안 " -#~ "좋을 수도 있습니다. 설치 프로그램에서 화면 표시 문제가 발생하면, " -#~ "debian-installer/framebuffer=true 혹은 짧은 형식으" -#~ "로 fb=true 파라미터를 넣고 부팅해 보십시오." +#. Tag: para +#: boot-installer.xml:3065 +#, 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 "" +"기본적으로 &d-i;에서는 다시 시작하기 전에 설치할 때 사용했던 광학 미디어를 자" +"동으로 뺍니다. 시스템이 CD에서 자동으로 부팅하는 경우가 아니라면 이럴 필요가 " +"없을 수도 있습니다. 어떤 경우에는 이렇게 하지 않는 게 좋을 때도 있습니다. 예" +"를 들어, 해당 광학 드라이브가 미디어를 다시 집어넣지 못하는 경우나 사용자가 " +"그 자리에 없기 때문에 수동으로 미디어를 집어넣지 못하는 경우입니다. 많은 슬" +"롯 스타일의 드라이브는 미디어를 자동으로 다시 집어넣지 못합니다." + +#. Tag: para +#: boot-installer.xml:3074 +#, no-c-format +msgid "" +"Set to false 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 "" +"자동으로 미디어를 꺼내지 않으려면 false로 설정합니다. " +"단 설치한 후에 시스템이 광학 드라이브에서 자동으로 부팅하지 않도록 하십시오." + +#. Tag: term +#: boot-installer.xml:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "ramdisk_size" + +#. Tag: para +#: boot-installer.xml:3086 +#, no-c-format +msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgstr "2.2.x 커널을 사용한다면, &ramdisksize;로 설정해야 합니다." + +#. Tag: term +#: boot-installer.xml:3094 +#, no-c-format +msgid "mouse/left" +msgstr "" -#~ msgid "debian-installer/theme" -#~ msgstr "debian-installer/theme" +#. Tag: para +#: boot-installer.xml:3095 +#, fuzzy, no-c-format +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to true." +msgstr "" +"GTK 프런트엔드(그래픽 설치프로그램)에서는, 기본적으로 directfb에서 하드웨어 " +"가속이 사용하지 않습니다. 이를 활성화하기 위해서는 설치 프로그램을 시작할 때 " +"이 파라미터를 true로 설정하면 됩니다." + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "directfb/hw-accel" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"true when booting the installer." +msgstr "" +"GTK 프런트엔드(그래픽 설치프로그램)에서는, 기본적으로 directfb에서 하드웨어 " +"가속이 사용하지 않습니다. 이를 활성화하기 위해서는 설치 프로그램을 시작할 때 " +"이 파라미터를 true로 설정하면 됩니다." + +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "rescue/enable" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"일반적인 설치를 하지 않고 복구 모드로 변경하려면 true" +"로 설정하십시오(참고: )." -#~ msgid "" -#~ "A theme determines how the user interface of the installer looks (colors, " -#~ "icons, etc.). What themes are available differs per frontend. Currently " -#~ "both the newt and gtk frontends only have a dark theme " -#~ "that was designed for visually impaired users. Set the theme by booting " -#~ "with parameter debian-installer/theme=dark or theme=dark." -#~ msgstr "" -#~ "테마는 설치 프로그램의 사용자 환경(색상,아이콘, 등등)을 어떻게 보여줄 것인" -#~ "가를 결정합니다. 프런트엔드에 따라 사용할 수 있는 테마가 달라집니다. 현재 " -#~ "newt와 gtk 프런트엔드에서는 시각장애인을 위한 dark테마만 있" -#~ "습니다. 이 테마를 설정하려면 부팅시에 debian-installer/" -#~ "theme=dark 또는 " -#~ "theme=dark를 인수로 주" -#~ "면 됩니다." +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "" -#~ msgid "debian-installer/probe/usb" -#~ msgstr "debian-installer/probe/usb" +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" -#~ msgid "" -#~ "Set to false to prevent probing for USB on boot, " -#~ "if that causes problems." -#~ msgstr "" -#~ "부팅할 때 USB 검색이 문제가 있는 경우, false로 설정" -#~ "해 USB 검색을 하지 않습니다." +#. Tag: term +#: boot-installer.xml:3140 +#, fuzzy, no-c-format +msgid "debian-installer/locale" +msgstr "debian-installer/theme" -#~ msgid "netcfg/disable_dhcp" -#~ msgstr "netcfg/disable_dhcp" +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. Short form: " +"locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" -#~ 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 "" -#~ "기본값으로, &d-i;는 DHCP를 통해 네트워크 설정을 검색합니다. 검색이 성공하" -#~ "면, 그 설정을 검사해 보거나 바꿀 기회가 없습니다. DHCP 검색이 실패할 경우" -#~ "에만 수동 네트워크 셋업을 할 수 있습니다." +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "" +"Set to true if you want to disable DHCP and instead " +"force static network configuration." +msgstr "" -#~ 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 " -#~ "netcfg/disable_dhcp=true to prevent configuring " -#~ "the network with DHCP and to enter the information manually." -#~ msgstr "" -#~ "랜에 DHCP 서버가 있지만 DHCP를 사용하고 싶지 않을 때 (예를 들어 잘못된 응" -#~ "답을 한다든지 때문에), netcfg/disable_dhcp=true 파" -#~ "라미터를 사용하면 DHCP 네트워크 설정을 막고 수동으로 정보를 입력할 수 있습" -#~ "니다." +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "" -#~ msgid "hw-detect/start_pcmcia" -#~ msgstr "hw-detect/start_pcmcia" +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" -#~ msgid "" -#~ "Set to false to prevent starting PCMCIA services, " -#~ "if that causes problems. Some laptops are well known for this misbehavior." -#~ msgstr "" -#~ "PCMCIA에 문제가 있을 때 false로 하면 PCMCIA 서비스" -#~ "를 시작하지 않습니다. 일부 노트북 컴퓨터에서 이와 관련해 문제가 발생합니" -#~ "다." +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "" -#~ msgid "preseed/url" -#~ msgstr "preseed/url" +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" -#, fuzzy -#~ msgid "" -#~ "Specify the url to a preconfiguration file to download and use in " -#~ "automating the install. See . Short " -#~ "form: url." -#~ msgstr "" -#~ "미리 설정해 놓은 파일을 내려받을 URL을 지정합니다. 이 파일을 이용해 설치" -#~ "를 자동화합니다. 참고. 짧은 형식: " -#~ "url" +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" -#~ msgid "preseed/file" -#~ msgstr "preseed/file" +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" -#, fuzzy -#~ msgid "" -#~ "Specify the path to a preconfiguration file to load to automating the " -#~ "install. See . Short form: " -#~ "file." -#~ msgstr "" -#~ "미리 설정해 놓은 파일을 읽어들일 URL을 지정합니다. 이 파일을 이용해 자동 " -#~ "설치를 합니다. 참고. 짧은 형식: " -#~ "file" +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "" -#~ msgid "cdrom-detect/eject" -#~ msgstr "cdrom-detect/eject" +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "설치 과정의 문제 해결" + +#. Tag: title +#: boot-installer.xml:3226 +#, fuzzy, no-c-format +msgid "CD-ROM Reliability" +msgstr "플로피 디스크 신뢰성" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" -#~ 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 "" -#~ "기본적으로 &d-i;에서는 다시 시작하기 전에 설치할 때 사용했던 광학 미디어" -#~ "를 자동으로 뺍니다. 시스템이 CD에서 자동으로 부팅하는 경우가 아니라면 이" -#~ "럴 필요가 없을 수도 있습니다. 어떤 경우에는 이렇게 하지 않는 게 좋을 때도 " -#~ "있습니다. 예를 들어, 해당 광학 드라이브가 미디어를 다시 집어넣지 못하는 경" -#~ "우나 사용자가 그 자리에 없기 때문에 수동으로 미디어를 집어넣지 못하는 경우" -#~ "입니다. 많은 슬롯 스타일의 드라이브는 미디어를 자동으로 다시 집어넣지 못합" -#~ "니다." +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" -#~ msgid "" -#~ "Set to false 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 "" -#~ "자동으로 미디어를 꺼내지 않으려면 false로 설정합니" -#~ "다. 단 설치한 후에 시스템이 광학 드라이브에서 자동으로 부팅하지 않도록 하" -#~ "십시오." +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "" -#~ msgid "ramdisk_size" -#~ msgstr "ramdisk_size" +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" -#~ msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -#~ msgstr "2.2.x 커널을 사용한다면, &ramdisksize;로 설정해야 합니다." +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" -#, fuzzy -#~ msgid "" -#~ "For the gtk frontend (graphical installer), users can switch the mouse to " -#~ "left-handed operation by setting this parameter to true." -#~ msgstr "" -#~ "GTK 프런트엔드(그래픽 설치프로그램)에서는, 기본적으로 directfb에서 하드웨" -#~ "어 가속이 사용하지 않습니다. 이를 활성화하기 위해서는 설치 프로그램을 시작" -#~ "할 때 이 파라미터를 true로 설정하면 됩니다." +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" -#~ msgid "directfb/hw-accel" -#~ msgstr "directfb/hw-accel" +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" -#~ msgid "" -#~ "For the gtk frontend (graphical installer), hardware acceleration in " -#~ "directfb is disabled by default. To enable it, set this parameter to " -#~ "true when booting the installer." -#~ msgstr "" -#~ "GTK 프런트엔드(그래픽 설치프로그램)에서는, 기본적으로 directfb에서 하드웨" -#~ "어 가속이 사용하지 않습니다. 이를 활성화하기 위해서는 설치 프로그램을 시작" -#~ "할 때 이 파라미터를 true로 설정하면 됩니다." +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "" -#~ msgid "rescue/enable" -#~ msgstr "rescue/enable" +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" -#~ msgid "" -#~ "Set to true to enter rescue mode rather than " -#~ "performing a normal installation. See ." -#~ msgstr "" -#~ "일반적인 설치를 하지 않고 복구 모드로 변경하려면 true로 설정하십시오(참고: )." +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" -#, fuzzy -#~ msgid "debian-installer/locale" -#~ msgstr "debian-installer/theme" +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" -#~ msgid "Troubleshooting the Installation Process" -#~ msgstr "설치 과정의 문제 해결" +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "" -#, fuzzy -#~ msgid "CD-ROM Reliability" -#~ msgstr "플로피 디스크 신뢰성" +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" -#~ msgid "Floppy Disk Reliability" -#~ msgstr "플로피 디스크 신뢰성" +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" -#~ msgid "" -#~ "The biggest problem for people using floppy disks to install Debian seems " -#~ "to be floppy disk reliability." -#~ msgstr "" -#~ "플로피 디스크를 사용해 설치하는 사람이 겪는 가장 큰 문제는 플로피 디스크 " -#~ "신뢰성 문제일 것입니다." +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" -#, fuzzy -#~ 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 "" -#~ "부트 플로피가 가장 문제가 많은 플로피입니다. 부트 플로피는 리눅스가 아니" -#~ "라 하드웨어에서 직접 읽어들이기 때문입니다. 가끔 하드웨어는 리눅스 플로피 " -#~ "디스크 드라이버가 하는 것 만큼 안정적으로 플로피를 읽지 못합니다. 또 잘못" -#~ "된 데이터를 읽은 경우에도 오류 메세지를 표시하지 않고 멈춰버리기도 합니" -#~ "다. 드라이버 플로피에서도 디스크 입출력 오류 메세지만 가득 나오는 문제가 " -#~ "발생하기도 합니다." - -#, fuzzy -#~ msgid "" -#~ "If you are having the installation stall at a particular floppy, the " -#~ "first thing you should do is write the image to a different floppy and see if that solves the problem. 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: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" -#~ msgid "" -#~ "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " -#~ "third floppy." -#~ msgstr "" -#~ "어떤 사용자는 플로피가 제대로 동작할 때까지 이미지를 무려 세 번" -#~ " 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다." +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" -#~ 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: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" -#~ msgid "Boot Configuration" -#~ msgstr "부팅 설정" +#. Tag: para +#: boot-installer.xml:3351 +#, no-c-format +msgid "" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using modprobe." +msgstr "" -#~ 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 ." -#~ msgstr "" -#~ "문제가 생겨서 커널이 부팅 과정에서 멈추거나, 주변 장치를 인식하지 못하거" -#~ "나, 드라이브를 제대로 인식하지 못하거나 하는 경우, 먼저 부팅 파라미터가 " -#~ "에 쓰여 있는 것처럼 제대로 되었는 지 확인하" -#~ "십시오." +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" -#~ msgid "" -#~ "If you are booting with your own kernel instead of the one supplied with " -#~ "the installer, be sure that CONFIG_DEVFS is set in " -#~ "your kernel. The installer requires CONFIG_DEVFS." -#~ msgstr "" -#~ "설치 프로그램에 들어 있는 커널 대신에 직접 만든 커널로 부팅하려면, " -#~ "CONFIG_DEVFS를 꼭 설정하십시오. 설치 프로그램에서 " -#~ "CONFIG_DEVFS가 필요합니다." +#. Tag: para +#: boot-installer.xml:3373 +#, no-c-format +msgid "" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" +"$ mount /dev/hdc /cdrom\n" +" Check if there are any error messages after that " +"command." +msgstr "" -#~ msgid "" -#~ "Often, problems can be solved by removing add-ons and peripherals, and " -#~ "then trying booting again. Internal modems, sound " -#~ "cards, and Plug-n-Play devices can be especially problematic." -#~ msgstr "" -#~ "추가 장치나 주변 기기를 없앤 다음에 다시 부팅하면 문제가 없어질 수도 있습" -#~ "니다. 내장 모뎀, 사운드 카드 및 플러그앤플레이 장치들" -#~ "이 특히 문제가 많습니다." +#. Tag: para +#: boot-installer.xml:3383 +#, no-c-format +msgid "" +"Check if DMA is currently enabled: \n" +"$ cd /proc/ide/hdc\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +" A 1 in the first column after " +"using_dma means it is enabled. If it is, try disabling " +"it: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." +msgstr "" -#~ 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 mem=512m." -#~ msgstr "" -#~ "기계에 512M 보다 더 많은 메모리가 붙어 있는 경우에 설치 프로그램의 커널이 " -#~ "부팅할 때 멈춘다면, 커널에 보이는 메모리 양을 제한하는 부팅 파라미터를 써" -#~ "야 할 수도 있습니다. 예를 들어 mem=512m과 같이 씁니" -#~ "다." +#. Tag: para +#: boot-installer.xml:3398 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" -#~ msgid "Common &arch-title; Installation Problems" -#~ msgstr "자주 발생하는 &arch-title; 설치 문제" +#. Tag: title +#: boot-installer.xml:3413 +#, no-c-format +msgid "Floppy Disk Reliability" +msgstr "플로피 디스크 신뢰성" -#~ 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:3415 +#, no-c-format +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"플로피 디스크를 사용해 설치하는 사람이 겪는 가장 큰 문제는 플로피 디스크 신뢰" +"성 문제일 것입니다." -#~ msgid "" -#~ "Some systems have floppies with inverted DCLs. If you " -#~ "receive errors reading from the floppy, even when you know the floppy is " -#~ "good, try the parameter floppy=thinkpad." -#~ msgstr "" -#~ "일부 시스템에는 ``DCL이 뒤바뀐'' 플로피가 달려 있습니다. 플로피가 문제가 " -#~ "없는 게 분명한데도 플로피를 읽다가 오류가 발생하면, " -#~ "floppy=thinkpad 파라미터를 시도해 보십시오." +#. Tag: para +#: boot-installer.xml:3420 +#, fuzzy, 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:3429 +#, fuzzy, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. 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:3438 +#, no-c-format +msgid "" +"One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " +"third floppy." +msgstr "" +"어떤 사용자는 플로피가 제대로 동작할 때까지 이미지를 무려 세 번 써야 했다고 하고, 세 번째 플로피에서 제대로 동작했다고 합니다." -#~ 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 hd=cylinders,heads,sectors." -#~ msgstr "" -#~ "IBM PS/1이나 ValuePoint같은 (ST-506 디스크 드라이버가 있는) 일부 시스템에" -#~ "서는 IDE 드라이브를 제대로 인식하지 못하기도 합니다. 먼저 파라미터 없이 " -#~ "IDE 드라이버를 제대로 인식하는 지 시도해 보십시오. 제대로 인식하지 못하" -#~ "면, 드라이브 크기를 (실린더, 헤드, 섹터) 알아보고, " -#~ "hd=cylinders,heads,sectors 파라미터를 사" -#~ "용하십시오." +#. Tag: para +#: boot-installer.xml:3444 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" -#~ msgid "" -#~ "If you have a very old machine, and the kernel hangs after saying " -#~ "Checking 'hlt' instruction..., then you " -#~ "should try the no-hlt boot argument, which " -#~ "disables this test." -#~ msgstr "" -#~ "아주 오래된 기계에서 Checking 'hlt' instruction...라고 나오면서 커널이 멈춘다면, hlt 인스트럭션 테스트를 하" -#~ "지 않도록 no-hlt 파라미터를 시도해 보십시오." +#. Tag: para +#: boot-installer.xml:3450 +#, 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:3459 +#, no-c-format +msgid "Boot Configuration" +msgstr "부팅 설정" + +#. Tag: para +#: boot-installer.xml:3461 +#, 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 " +"." +msgstr "" +"문제가 생겨서 커널이 부팅 과정에서 멈추거나, 주변 장치를 인식하지 못하거나, " +"드라이브를 제대로 인식하지 못하거나 하는 경우, 먼저 부팅 파라미터가 에 쓰여 있는 것처럼 제대로 되었는 지 확인하십시오." -#~ 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 fb=false " -#~ "video=vga16:off to disable the framebuffer console. Only the " -#~ "English language will be available during the installation due to limited " -#~ "console features. See for details." -#~ msgstr "" -#~ "커널이 부팅할 때 화면에 괴상한 그림이 나온다면, 예를 들어 전부 하얀 색이 " -#~ "되거나 전부 검은 색이 되거나 가지가지 색의 픽셀 쓰레기가 나오거나 하면, 프" -#~ "레임버퍼 모드로 제대로 전환하지 못하는 문제 있는 비디오 카드가 붙어 있다" -#~ "는 뜻입니다. 그러면 fb=false video=vga16:off 부팅 " -#~ "파라미터로 프레임버퍼 콘솔을 사용하지 않을 수 있습니다. 그러면 콘솔 기능" -#~ "의 한계때문에 설치할 때 언어는 영어만 사용할 수 있습니다. 자세한 방법은 " -#~ " 부분을 참고하십시오." +#. Tag: para +#: boot-installer.xml:3468 +#, no-c-format +msgid "" +"If you are booting with your own kernel instead of the one supplied with the " +"installer, be sure that CONFIG_DEVFS is set in your " +"kernel. The installer requires CONFIG_DEVFS." +msgstr "" +"설치 프로그램에 들어 있는 커널 대신에 직접 만든 커널로 부팅하려면, " +"CONFIG_DEVFS를 꼭 설정하십시오. 설치 프로그램에서 " +"CONFIG_DEVFS가 필요합니다." -#~ msgid "System Freeze During the PCMCIA Configuration Phase" -#~ msgstr "PCMCIA 설정 단계에서 시스템 멈춤" +#. Tag: para +#: boot-installer.xml:3475 +#, no-c-format +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic." +msgstr "" +"추가 장치나 주변 기기를 없앤 다음에 다시 부팅하면 문제가 없어질 수도 있습니" +"다. 내장 모뎀, 사운드 카드 및 플러그앤플레이 장치들이 특" +"히 문제가 많습니다." -#~ 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 hw-detect/start_pcmcia=false boot parameter. " -#~ "You can then configure PCMCIA after the installation is completed and " -#~ "exclude the resource range causing the problems." -#~ msgstr "" -#~ "Dell에서 제조한 일부 노트북 모델은 PCMCIA 장치를 찾을 때 특정 하드웨어 주" -#~ "소에 접근하는 순간 멈춰 버립니다. 그 외의 노트북 모델도 비슷한 현상이 나타" -#~ "날 수 있습니다. 만약 그러한 문제가 발생하고 설치할 때 PCMCIA 기능이 필요없" -#~ "다면, hw-detect/start_pcmcia=false 부팅 파라미터로 " -#~ "PCMCIA를 끌 수 있습니다. 설치를 마친 다음에 PCMCIA를 설정해서 문제가 발생" -#~ "하는 구간을 제외할 수 있습니다." +#. Tag: para +#: boot-installer.xml:3481 +#, 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 mem=512m." +msgstr "" +"기계에 512M 보다 더 많은 메모리가 붙어 있는 경우에 설치 프로그램의 커널이 부" +"팅할 때 멈춘다면, 커널에 보이는 메모리 양을 제한하는 부팅 파라미터를 써야 할 " +"수도 있습니다. 예를 들어 mem=512m과 같이 씁니다." + +#. Tag: title +#: boot-installer.xml:3492 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "자주 발생하는 &arch-title; 설치 문제" + +#. Tag: para +#: boot-installer.xml:3493 +#, 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 "" +"자주 발생하는 설치 문제중에 몇 개는 설치 프로그램에 부팅 파라미터를 넘기는 방" +"법으로 해결할 수 있습니다." -#~ 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 exclude port 0x800-0x8ff here. There is also " -#~ "a list of some common resource range options in the System " -#~ "resource settings section of the PCMCIA HOWTO. Note that you have " -#~ "to omit the commas, if any, when you enter this value in the installer." -#~ msgstr "" -#~ "다른 방법으로, 전문가 모드에서 설치 프로그램을 부팅할 수 있습니다. 그 다음" -#~ "에 하드웨어에 필요한 리소스 범위를 입력합니다. 예를 들어, 위에서 말한 " -#~ "Dell 노트북을 가지고 있다면, 여기서 exclude port 0x800-0x8ff라고 입력합니다. System resource settings section of " -#~ "the PCMCIA HOWTO에 보면 리소스 범위 관련 옵션의 목록이 있습니다. " -#~ "설치 프로그램에서 이 값을 입력할 때, 쉼표를 쓰지 않는다는 것에 유의하십시" -#~ "오." +#. Tag: para +#: boot-installer.xml:3498 +#, no-c-format +msgid "" +"Some systems have floppies with inverted DCLs. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter floppy=thinkpad." +msgstr "" +"일부 시스템에는 ``DCL이 뒤바뀐'' 플로피가 달려 있습니다. 플로피가 문제가 없" +"는 게 분명한데도 플로피를 읽다가 오류가 발생하면, " +"floppy=thinkpad 파라미터를 시도해 보십시오." -#~ msgid "System Freeze while Loading the USB Modules" -#~ msgstr "USB 모듈을 읽어들이다가 시스템 멈춤" +#. Tag: para +#: boot-installer.xml:3504 +#, 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 hd=cylinders," +"heads,sectors." +msgstr "" +"IBM PS/1이나 ValuePoint같은 (ST-506 디스크 드라이버가 있는) 일부 시스템에서" +"는 IDE 드라이브를 제대로 인식하지 못하기도 합니다. 먼저 파라미터 없이 IDE 드" +"라이버를 제대로 인식하는 지 시도해 보십시오. 제대로 인식하지 못하면, 드라이" +"브 크기를 (실린더, 헤드, 섹터) 알아보고, " +"hd=cylinders,heads,sectors 파라미터를 사용하" +"십시오." + +#. Tag: para +#: boot-installer.xml:3513 +#, no-c-format +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"Checking 'hlt' instruction..., then you " +"should try the no-hlt boot argument, which disables " +"this test." +msgstr "" +"아주 오래된 기계에서 Checking 'hlt' instruction...라고 나오면서 커널이 멈춘다면, hlt 인스트럭션 테스트를 하지 않" +"도록 no-hlt 파라미터를 시도해 보십시오." -#~ 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 debian-installer/" -#~ "probe/usb=false parameter at the boot prompt, which will " -#~ "prevent the modules from being loaded." -#~ msgstr "" -#~ "일부 표준이 아닌 USB 키보드를 지원하기 위해 커널에서 USB 모듈과 USB 키보" -#~ "드 드라이버를 읽어들입니다. 하지만 일부 문제 있는 USB 시스템에서는 드라이" -#~ "버를 읽어들일 때 멈춥니다. 한 가지 방법은 메인보드의 BIOS 설정에서 USB 컨" -#~ "트롤러를 끄는 것입니다. 또 다른 방법은 debian-installer/probe/" -#~ "usb=false 파라미터를 부팅 프롬프트에 써서, USB 모듈을 읽어들이" -#~ "지 못하게 하는 것입니다." +#. Tag: para +#: boot-installer.xml:3520 +#, 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 fb=false " +"video=vga16:off to disable the framebuffer console. Only the " +"English language will be available during the installation due to limited " +"console features. See for details." +msgstr "" +"커널이 부팅할 때 화면에 괴상한 그림이 나온다면, 예를 들어 전부 하얀 색이 되거" +"나 전부 검은 색이 되거나 가지가지 색의 픽셀 쓰레기가 나오거나 하면, 프레임버" +"퍼 모드로 제대로 전환하지 못하는 문제 있는 비디오 카드가 붙어 있다는 뜻입니" +"다. 그러면 fb=false video=vga16:off 부팅 파라미터로 프" +"레임버퍼 콘솔을 사용하지 않을 수 있습니다. 그러면 콘솔 기능의 한계때문에 설치" +"할 때 언어는 영어만 사용할 수 있습니다. 자세한 방법은 부분을 참고하십시오." + +#. Tag: title +#: boot-installer.xml:3534 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "PCMCIA 설정 단계에서 시스템 멈춤" + +#. Tag: para +#: boot-installer.xml:3535 +#, 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 " +"hw-detect/start_pcmcia=false boot parameter. You can " +"then configure PCMCIA after the installation is completed and exclude the " +"resource range causing the problems." +msgstr "" +"Dell에서 제조한 일부 노트북 모델은 PCMCIA 장치를 찾을 때 특정 하드웨어 주소" +"에 접근하는 순간 멈춰 버립니다. 그 외의 노트북 모델도 비슷한 현상이 나타날 " +"수 있습니다. 만약 그러한 문제가 발생하고 설치할 때 PCMCIA 기능이 필요없다면, " +"hw-detect/start_pcmcia=false 부팅 파라미터로 PCMCIA를 " +"끌 수 있습니다. 설치를 마친 다음에 PCMCIA를 설정해서 문제가 발생하는 구간을 " +"제외할 수 있습니다." + +#. Tag: para +#: boot-installer.xml:3545 +#, 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 " +"exclude port 0x800-0x8ff here. There is also a list " +"of some common resource range options in the System resource " +"settings section of the PCMCIA HOWTO. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." +msgstr "" +"다른 방법으로, 전문가 모드에서 설치 프로그램을 부팅할 수 있습니다. 그 다음에 " +"하드웨어에 필요한 리소스 범위를 입력합니다. 예를 들어, 위에서 말한 Dell 노트" +"북을 가지고 있다면, 여기서 exclude port 0x800-0x8ff라" +"고 입력합니다. System resource settings section of the PCMCIA HOWTO에 보면 리소스 범위 관련 옵션의 목록이 있습니다. 설치 프로그램에서 이 " +"값을 입력할 때, 쉼표를 쓰지 않는다는 것에 유의하십시오." + +#. Tag: title +#: boot-installer.xml:3562 +#, no-c-format +msgid "System Freeze while Loading the USB Modules" +msgstr "USB 모듈을 읽어들이다가 시스템 멈춤" + +#. Tag: para +#: boot-installer.xml:3563 +#, 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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " +"being loaded." +msgstr "" +"일부 표준이 아닌 USB 키보드를 지원하기 위해 커널에서 USB 모듈과 USB 키보드 드" +"라이버를 읽어들입니다. 하지만 일부 문제 있는 USB 시스템에서는 드라이버를 읽어" +"들일 때 멈춥니다. 한 가지 방법은 메인보드의 BIOS 설정에서 USB 컨트롤러를 끄" +"는 것입니다. 또 다른 방법은 debian-installer/probe/usb=false 파라미터를 부팅 프롬프트에 써서, USB 모듈을 읽어들이지 못하게 하" +"는 것입니다." + +#. Tag: title +#: boot-installer.xml:3577 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "커널 시작 메세지 해석하기" + +#. Tag: para +#: boot-installer.xml:3579 +#, no-c-format +msgid "" +"During the boot sequence, you may see many messages in the form " +"can't find something , or something " +"not present, can't initialize " +"something , or even " +"this driver release depends on something . 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 )." +msgstr "" +"부팅 과정에서, can't find something 혹은 something not present, can't initialize " +"something , 아니면 심지어는 " +"this driver release depends on something 형식의 메세지를 볼 수 있을 것입니다. 이러한 메" +"세지의 대부분은 아무런 문제를 일으키지 않습니다. 설치 시스템은 여러 가지 주" +"변 장치가 달린 컴퓨터에서 동작하도록 만들어졌기 때문에 이런 메세지가 나옵니" +"다. 당연히 그 어떤 컴퓨터라고 해도 모든 주변 장치를 가진 컴퓨터는 없으므로, " +"운영체제에서는 찾으려는 주변 장치가 없을 때 이러한 메세지를 내보냅니다. 또 시" +"스템이 일시적으로 멈추는 현상이 일어날 수도 있습니다. 이러한 현상은 어떤 장치" +"가 응답할 때까지 기다리는데, 그 장치가 없을 때 발생합니다. 이런 시간이 너무 " +"오래 걸린다고 생각한다면, 나중에 직접 설정한 커널을 사용할 수 있습니다. " +"( 참고.)" + +#. Tag: title +#: boot-installer.xml:3604 +#, fuzzy, no-c-format +msgid "Reporting Installation Problems" +msgstr "자주 발생하는 &arch-title; 설치 문제" + +#. Tag: para +#: boot-installer.xml:3605 +#, fuzzy, no-c-format +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the menu option Save debug logs may be helpful. " +"It lets you store system error logs and configuration information from the " +"installer to a floppy, or download them using 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:3616 +#, no-c-format +msgid "" +"Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" +"그 외의 설치 메세지는 설치할 때 /var/log/에 들어 있고, " +"설치된 시스템으로 부팅한 다음에는 /var/log/installer/에 " +"들어 있습니다." + +#. Tag: title +#: boot-installer.xml:3627 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "설치 보고 제출" + +#. Tag: para +#: boot-installer.xml:3628 +#, 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 "" +"그래도 문제가 있다면, 설치 리포트를 보내 주십시오. 설치가 성공했을 경우에도 " +"설치 리포트를 보내 주시는 게 좋습니다. 그래야 사용자가 어떤 하드웨어 설정을 " +"사용하는 지에 대한 정보를 많이 얻을 수 있습니다." -#~ msgid "Interpreting the Kernel Startup Messages" -#~ msgstr "커널 시작 메세지 해석하기" +#. Tag: para +#: boot-installer.xml:3635 +#, no-c-format +msgid "" +"Note that your installation report will be published in the Debian Bug " +"Tracking System (BTS) and forwarded to a public mailing list. Make sure that " +"you use an E-Mail address that you do not mind being made public." +msgstr "" -#~ msgid "" -#~ "During the boot sequence, you may see many messages in the form " -#~ "can't find something , or something " -#~ "not present, can't initialize " -#~ "something , or even " -#~ "this driver release depends on something . 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 )." -#~ msgstr "" -#~ "부팅 과정에서, can't find something 혹은 " -#~ "something not present, " -#~ "can't initialize something , 아니면 심지어는 this driver release " -#~ "depends on something 형식의 " -#~ "메세지를 볼 수 있을 것입니다. 이러한 메세지의 대부분은 아무런 문제를 일으" -#~ "키지 않습니다. 설치 시스템은 여러 가지 주변 장치가 달린 컴퓨터에서 동작하" -#~ "도록 만들어졌기 때문에 이런 메세지가 나옵니다. 당연히 그 어떤 컴퓨터라고 " -#~ "해도 모든 주변 장치를 가진 컴퓨터는 없으므로, 운영체제에서는 찾으려는 주" -#~ "변 장치가 없을 때 이러한 메세지를 내보냅니다. 또 시스템이 일시적으로 멈추" -#~ "는 현상이 일어날 수도 있습니다. 이러한 현상은 어떤 장치가 응답할 때까지 기" -#~ "다리는데, 그 장치가 없을 때 발생합니다. 이런 시간이 너무 오래 걸린다고 생" -#~ "각한다면, 나중에 직접 설정한 커널을 사용할 수 있습니다. ( 참고.)" +#. Tag: para +#: boot-installer.xml:3641 +#, 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 " +"(apt-get install installation-report reportbug) and run " +"the command reportbug installation-report." +msgstr "" +"이미 동작하고 있는 데비안 시스템이 있다면, 설치 리포트를 보내는 가장 쉬운 방" +"법은 installation-report 및 reportbug 꾸러미를 설치하고 (apt-get " +"install installation-report reportbug) reportbug " +"installation-report 명령을 실행하는 것입니다." + +#. Tag: para +#: boot-installer.xml:3648 +#, fuzzy, no-c-format +msgid "" +"Alternatively you can use this template when filling out installation " +"reports, and file the report as a bug report against the " +"installation-reports pseudo package, by sending it to " +"submit@bugs.debian.org. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD? floppy? network?>\n" +"Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect CD: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\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" +" 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 "" +"설치 보고서를 작성하실 때 아래 형식을 이용하시고, installation-" +"reports\" 꾸러미에 대한 버그를 submit@bugs.debian.org로 메일을 보내 제출해 주십시오. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <설치 프로그램을 어떻게 부팅했는지? CD? 플로피? 네트워크?" +">\n" +"Image version: <설치 이미지를 받은 날짜와 이미지를 받은 곳을 넣으십시오" +">\n" +"Date: <설치한 날짜 및 시각>\n" +"\n" +"Machine: <기계 설명 (예, IBM Thinkpad R32)>\n" +"Processor:\n" +"Memory:\n" +"Partitions: >df -Tl 명령어의 결과. 파티션 테이블의 raw 정보가 좋습니다." +">\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" +"<설치 과정을 문장으로 설명하십시오. 그리고 처음에 설치했을 때 \n" +" 들었던 생각, 평가, 아이디어 따위도 써 주십시오.>\n" +" 버그 보고서에 문제가 무엇인지 설명하시고, 커널이 " +"멈춘 경우에 마지막으로 볼 수 있는 커널 메세지를 포함하십시오. 문제가 발생할 " +"때 어떤 과정을 거쳤는 지 설명하십시오." #~ msgid "Bug Reporter" #~ msgstr "버그 보고" -#~ 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 "" -#~ "최초 부팅 단계를 지나갔지만 설치를 마치지 못했다면, 버그 보고 메뉴가 도움" -#~ "이 될 수도 있습니다. 이 메뉴는 시스템 오류 로그와 설정 정보를 설치 프로그" -#~ "램에서 플로피로 복사하거나, 웹브라우저로 다운로드할 수 있습니다. 이 정보" -#~ "는 무엇이 잘못되었는지 및 어떻게 고치는 지에 대한 단서가 들어 있습니다. 버" -#~ "그를 보고할 때 이 정보를 버그 보고에 첨부해 주십시오." - -#~ msgid "" -#~ "Other pertinent installation messages may be found in /var/log/" -#~ " during the installation, and /var/log/installer/ after the computer has been booted into the installed system." -#~ msgstr "" -#~ "그 외의 설치 메세지는 설치할 때 /var/log/에 들어 있" -#~ "고, 설치된 시스템으로 부팅한 다음에는 /var/log/installer/에 들어 있습니다." - -#~ msgid "Submitting Installation Reports" -#~ msgstr "설치 보고 제출" - -#~ 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 "" -#~ "그래도 문제가 있다면, 설치 리포트를 보내 주십시오. 설치가 성공했을 경우에" -#~ "도 설치 리포트를 보내 주시는 게 좋습니다. 그래야 사용자가 어떤 하드웨어 설" -#~ "정을 사용하는 지에 대한 정보를 많이 얻을 수 있습니다." - -#~ 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 (apt-get install installation-report reportbug) and run the command reportbug installation-report." -#~ msgstr "" -#~ "이미 동작하고 있는 데비안 시스템이 있다면, 설치 리포트를 보내는 가장 쉬운 " -#~ "방법은 installation-report 및 reportbug 꾸러미를 설치하고 (apt-" -#~ "get install installation-report reportbug) reportbug " -#~ "installation-report 명령을 실행하는 것입니다." - -#, fuzzy -#~ msgid "" -#~ "Please use this template when filling out installation reports, and file " -#~ "the report as a bug report against the installation-reports pseudo package, by sending it to submit@bugs.debian." -#~ "org. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <How did you boot the installer? CD? floppy? network?" -#~ ">\n" -#~ "Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" -#~ "\n" -#~ "Base System Installation Checklist:\n" -#~ "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" -#~ "\n" -#~ "Initial boot: [ ]\n" -#~ "Detect network card: [ ]\n" -#~ "Configure network: [ ]\n" -#~ "Detect CD: [ ]\n" -#~ "Load installer modules: [ ]\n" -#~ "Detect hard drives: [ ]\n" -#~ "Partition hard drives: [ ]\n" -#~ "Install base system: [ ]\n" -#~ "Clock/timezone setup: [ ]\n" -#~ "User/password setup: [ ]\n" -#~ "Install tasks: [ ]\n" -#~ "Install boot loader: [ ]\n" -#~ "Overall install: [ ]\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" -#~ " 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 "" -#~ "설치 보고서를 작성하실 때 아래 형식을 이용하시고, installation-" -#~ "reports\" 꾸러미에 대한 버그를 submit@bugs.debian.org로 메일을 보내 제출해 주십시오. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <설치 프로그램을 어떻게 부팅했는지? CD? 플로피? 네트워크?" -#~ ">\n" -#~ "Image version: <설치 이미지를 받은 날짜와 이미지를 받은 곳을 넣으십시오" -#~ ">\n" -#~ "Date: <설치한 날짜 및 시각>\n" -#~ "\n" -#~ "Machine: <기계 설명 (예, IBM Thinkpad R32)>\n" -#~ "Processor:\n" -#~ "Memory:\n" -#~ "Partitions: >df -Tl 명령어의 결과. 파티션 테이블의 raw 정보가 좋습니다." -#~ ">\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" -#~ "<설치 과정을 문장으로 설명하십시오. 그리고 처음에 설치했을 때 \n" -#~ " 들었던 생각, 평가, 아이디어 따위도 써 주십시오.>\n" -#~ " 버그 보고서에 문제가 무엇인지 설명하시고, 커널" -#~ "이 멈춘 경우에 마지막으로 볼 수 있는 커널 메세지를 포함하십시오. 문제가 발" -#~ "생할 때 어떤 과정을 거쳤는 지 설명하십시오." - #~ msgid "" #~ "Proceed to the next chapter to continue the installation where you will " #~ "set up the language locale, network, and the disk partitions." diff --git a/po/ko/preparing.po b/po/ko/preparing.po index 517e1ddc6..ae2969c28 100644 --- a/po/ko/preparing.po +++ b/po/ko/preparing.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: preparing.xml\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-26 16:20+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-08-08 23:17+0900\n" "Last-Translator: Changwoo Ryu \n" "Language-Team: Korean \n" @@ -3191,25 +3191,6 @@ msgstr "" #: preparing.xml:2079 #, 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 " -"." -msgstr "" -"아주 좋은 마더보드는 패리티 RAM을 지원하고 RAM에 한 비트 오류가 발생했을 때 " -"알려줍니다. 아쉽게도, 그 오류를 고칠 수 있는 방법은 없기 때문에, 그 RAM이 있" -"다는 사실을 알자 마자 죽어 버립니다. 그래도 데이터에 오류를 집어 넣는 것보다" -"는 메모리가 잘못되었다고 알려주는 편이 낫습니다. 아주 좋은 시스템에는 마더보" -"드가 패리티를 지원하고 진짜 패리티 메모리 모듈이 들어 있습니다. 부분을 참고하십시오." - -#. Tag: para -#: preparing.xml:2090 -#, 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." @@ -3218,13 +3199,13 @@ msgstr "" "그 기능을 켜서 메모리 패리티 오류가 발생했을 때 인터럽트를 내도록 하십시오." #. Tag: title -#: preparing.xml:2098 +#: preparing.xml:2087 #, no-c-format msgid "The Turbo Switch" msgstr "Turbo 스위치" #. Tag: para -#: preparing.xml:2099 +#: preparing.xml:2088 #, no-c-format msgid "" "Many systems have a turbo switch that controls the " @@ -3243,13 +3224,13 @@ msgstr "" "다." #. Tag: title -#: preparing.xml:2112 +#: preparing.xml:2101 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "Cyrix CPU 및 플로피 디스크 오류" #. Tag: para -#: preparing.xml:2113 +#: preparing.xml:2102 #, no-c-format msgid "" "Many users of Cyrix CPUs have had to disable the cache in their systems " @@ -3264,7 +3245,7 @@ msgstr "" "emphasis> 더 느리게 동작합니다." #. Tag: para -#: preparing.xml:2121 +#: preparing.xml:2110 #, no-c-format msgid "" "We don't think this is necessarily the fault of the Cyrix CPU. It may be " @@ -3278,13 +3259,13 @@ msgstr "" "시가 무효화되면서 발생하는 문제라고 추정됩니다." #. Tag: title -#: preparing.xml:2131 +#: preparing.xml:2120 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "주변 장치 하드웨어 설정" #. Tag: para -#: preparing.xml:2132 +#: preparing.xml:2121 #, no-c-format msgid "" "You may have to change some settings or jumpers on your computer's " @@ -3298,7 +3279,7 @@ msgstr "" "들을 전달하길 바랄 뿐입니다." #. Tag: para -#: preparing.xml:2139 +#: preparing.xml:2128 #, no-c-format msgid "" "If any cards provide mapped memory, the memory should be " @@ -3311,13 +3292,13 @@ msgstr "" "보다 최소 1메가바이트 큰 위치에 들어 있어야 합니다." #. Tag: title -#: preparing.xml:2150 +#: preparing.xml:2139 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "USB BIOS 지원 및 키보드" #. Tag: para -#: preparing.xml:2151 +#: preparing.xml:2140 #, no-c-format msgid "" "If you have no AT-style keyboard and only a USB model, you may need to " @@ -3336,13 +3317,13 @@ msgstr "" "emulation이나 USB keyboard support 옵션을 찾으십시오." #. Tag: title -#: preparing.xml:2164 +#: preparing.xml:2153 #, no-c-format msgid "More than 64 MB RAM" msgstr "64 MB RAM 이상" #. Tag: para -#: preparing.xml:2165 +#: preparing.xml:2154 #, no-c-format msgid "" "The Linux Kernel cannot always detect what amount of RAM you have. If this " @@ -3352,13 +3333,13 @@ msgstr "" "에 있는 내용을 참고하십시오." #. Tag: title -#: preparing.xml:2174 +#: preparing.xml:2163 #, no-c-format msgid "Display visibility on OldWorld Powermacs" msgstr "OldWorld PowerMac에서 디스플레이 보기" #. Tag: para -#: preparing.xml:2175 +#: preparing.xml:2164 #, no-c-format msgid "" "Some OldWorld Powermacs, most notably those with the control " @@ -3379,3 +3360,19 @@ msgstr "" "가 나오기 전에 화면이 검은색으로 변하는 경우, MacOS에서 디스플레이 설정을 " "thousands나 millions 대신에 256색으로 맞추십시" "오." + +#~ 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 ." +#~ msgstr "" +#~ "아주 좋은 마더보드는 패리티 RAM을 지원하고 RAM에 한 비트 오류가 발생했을 " +#~ "때 알려줍니다. 아쉽게도, 그 오류를 고칠 수 있는 방법은 없기 때문에, 그 RAM" +#~ "이 있다는 사실을 알자 마자 죽어 버립니다. 그래도 데이터에 오류를 집어 넣" +#~ "는 것보다는 메모리가 잘못되었다고 알려주는 편이 낫습니다. 아주 좋은 시스템" +#~ "에는 마더보드가 패리티를 지원하고 진짜 패리티 메모리 모듈이 들어 있습니" +#~ "다. 부분을 참고하십시오." diff --git a/po/ko/using-d-i.po b/po/ko/using-d-i.po index f977f5080..86f27d0c6 100644 --- a/po/ko/using-d-i.po +++ b/po/ko/using-d-i.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: using-d-i.xml\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-08-08 23:17+0900\n" "Last-Translator: Changwoo Ryu \n" "Language-Team: Korean \n" @@ -3511,14 +3511,13 @@ msgstr "" #. Tag: para #: using-d-i.xml:2302 -#, no-c-format +#, fuzzy, 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 fdisk /" "mbr 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 ." +"Debian!" msgstr "" "이 단계를 거친 다음에 Windows 9x로 (아니면 DOS로) 부팅할 수 없게 된다면, " "Windows 9x (MS-DOS) 부팅 디스크를 이용해서 fdisk /mbr " @@ -3528,13 +3527,13 @@ msgstr "" "하십시오." #. Tag: title -#: using-d-i.xml:2319 +#: using-d-i.xml:2318 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "하드 디스크에 ELILO 부트로더 설치" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2320 #, no-c-format msgid "" "The &architecture; boot loader is called elilo. It is modeled " @@ -3561,7 +3560,7 @@ msgstr "" "는 일을 합니다." #. Tag: para -#: using-d-i.xml:2337 +#: using-d-i.xml:2336 #, no-c-format msgid "" "The elilo configuration and installation is done as the last " @@ -3577,13 +3576,13 @@ msgstr "" "은 디스크의 파티션입니다." #. Tag: title -#: using-d-i.xml:2349 +#: using-d-i.xml:2348 #, no-c-format msgid "Choose the correct partition!" msgstr "올바른 파티션을 고르십시오!" #. Tag: para -#: using-d-i.xml:2351 +#: using-d-i.xml:2350 #, no-c-format msgid "" "The criteria for selecting a partition is that it is FAT format filesystem " @@ -3600,13 +3599,13 @@ msgstr "" "는 동안 해당 파티션을 포맷할 수도 있고, 그러면 이전의 내용이 모두 지워집니다!" #. Tag: title -#: using-d-i.xml:2366 +#: using-d-i.xml:2365 #, no-c-format msgid "EFI Partition Contents" msgstr "EFI 파티션 내용" #. Tag: para -#: using-d-i.xml:2368 +#: using-d-i.xml:2367 #, no-c-format msgid "" "The EFI partition is a FAT filesystem format partition on one of the hard " @@ -3635,13 +3634,13 @@ msgstr "" "이 파일 시스템에는 다른 파일이 들어갈 수 있습니다." #. Tag: filename -#: using-d-i.xml:2390 +#: using-d-i.xml:2389 #, no-c-format msgid "elilo.conf" msgstr "elilo.conf" #. Tag: para -#: using-d-i.xml:2391 +#: using-d-i.xml:2390 #, no-c-format msgid "" "This is the configuration file read by the boot loader when it starts. It is " @@ -3653,13 +3652,13 @@ msgstr "" "의 파일이름을 바꾼 것입니다." #. Tag: filename -#: using-d-i.xml:2400 +#: using-d-i.xml:2399 #, no-c-format msgid "elilo.efi" msgstr "elilo.efi" #. Tag: para -#: using-d-i.xml:2401 +#: using-d-i.xml:2400 #, no-c-format msgid "" "This is the boot loader program that the EFI Boot Manager " @@ -3673,13 +3672,13 @@ msgstr "" "입니다." #. Tag: filename -#: using-d-i.xml:2411 +#: using-d-i.xml:2410 #, no-c-format msgid "initrd.img" msgstr "initrd.img" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2411 #, no-c-format msgid "" "This is the initial root filesystem used to boot the kernel. It is a copy of " @@ -3693,13 +3692,13 @@ msgstr "" "filename> 심볼릭 링크가 그 파일을 가리킵니다." #. Tag: filename -#: using-d-i.xml:2424 +#: using-d-i.xml:2423 #, no-c-format msgid "readme.txt" msgstr "readme.txt" #. Tag: para -#: using-d-i.xml:2425 +#: using-d-i.xml:2424 #, no-c-format msgid "" "This is a small text file warning you that the contents of the directory are " @@ -3711,13 +3710,13 @@ msgstr "" "어진다는 사실을 알리는 내용이 들어 있습니다." #. Tag: filename -#: using-d-i.xml:2435 +#: using-d-i.xml:2434 #, no-c-format msgid "vmlinuz" msgstr "vmlinuz" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2435 #, no-c-format msgid "" "This is the compressed kernel itself. It is a copy of the file referenced in " @@ -3731,13 +3730,13 @@ msgstr "" "을 가리킵니다." #. Tag: title -#: using-d-i.xml:2456 +#: using-d-i.xml:2455 #, no-c-format msgid "arcboot-installer" msgstr "arcboot-installer" #. Tag: para -#: using-d-i.xml:2457 +#: using-d-i.xml:2456 #, no-c-format msgid "" "The boot loader on SGI machines is arcboot. It has to be " @@ -3779,13 +3778,13 @@ msgstr "" "면 시스템을 하드 디스크에서 부팅할 수 있습니다." #. Tag: replaceable -#: using-d-i.xml:2476 +#: using-d-i.xml:2475 #, no-c-format msgid "scsi" msgstr "scsi" #. Tag: para -#: using-d-i.xml:2477 +#: using-d-i.xml:2476 #, no-c-format msgid "" "is the SCSI bus to be booted from, this is 0 for the " @@ -3795,13 +3794,13 @@ msgstr "" "니다" #. Tag: replaceable -#: using-d-i.xml:2485 +#: using-d-i.xml:2484 #, no-c-format msgid "disk" msgstr "disk" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2485 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which arcboot is " @@ -3809,13 +3808,13 @@ msgid "" msgstr "arcboot를 설치한 하드디스크의 SCSI ID" #. Tag: replaceable -#: using-d-i.xml:2494 using-d-i.xml:2563 +#: using-d-i.xml:2493 using-d-i.xml:2562 #, no-c-format msgid "partnr" msgstr "partnr" #. Tag: para -#: using-d-i.xml:2495 +#: using-d-i.xml:2494 #, no-c-format msgid "" "is the number of the partition on which /etc/arcboot.conf/etc/arcboot.conf 파일이 들어 있는 파티션 번호" #. Tag: replaceable -#: using-d-i.xml:2503 +#: using-d-i.xml:2502 #, no-c-format msgid "config" msgstr "config" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2503 #, no-c-format msgid "" "is the name of the configuration entry in /etc/arcboot.conflinux입니다." #. Tag: title -#: using-d-i.xml:2525 +#: using-d-i.xml:2524 #, no-c-format msgid "delo-installer" msgstr "delo-installer" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2525 #, no-c-format msgid "" "The boot loader on DECstations is DELO. It has to be " @@ -3873,13 +3872,13 @@ msgstr "" "" #. Tag: replaceable -#: using-d-i.xml:2545 +#: using-d-i.xml:2544 #, no-c-format msgid "#" msgstr "#" #. Tag: para -#: using-d-i.xml:2546 +#: using-d-i.xml:2545 #, no-c-format msgid "" "is the TurboChannel device to be booted from, on most DECstations this is " @@ -3889,20 +3888,20 @@ msgstr "" "3입니다" #. Tag: replaceable -#: using-d-i.xml:2554 +#: using-d-i.xml:2553 #, no-c-format msgid "id" msgstr "id" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2554 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which DELO is installed" msgstr "DELO를 설치한 하드 디스크의 SCSI ID" #. Tag: para -#: using-d-i.xml:2564 +#: using-d-i.xml:2563 #, no-c-format msgid "" "is the number of the partition on which /etc/delo.conf " @@ -3910,13 +3909,13 @@ msgid "" msgstr "/etc/delo.conf 파일이 들어 있는 파티션 번호" #. Tag: replaceable -#: using-d-i.xml:2572 +#: using-d-i.xml:2571 #, no-c-format msgid "name" msgstr "name" #. Tag: para -#: using-d-i.xml:2573 +#: using-d-i.xml:2572 #, no-c-format msgid "" "is the name of the configuration entry in /etc/delo.conflinux입니다." #. Tag: para -#: using-d-i.xml:2583 +#: using-d-i.xml:2582 #, no-c-format msgid "" "In case /etc/delo.conf is on the first partition on the " @@ -3936,19 +3935,19 @@ msgstr "" "본 설정으로 부팅하는 경우, 다음을 사용하면 충분합니다:" #. Tag: screen -#: using-d-i.xml:2589 +#: using-d-i.xml:2588 #, no-c-format msgid "boot #/rzid" msgstr "boot #/rzid" #. Tag: title -#: using-d-i.xml:2599 +#: using-d-i.xml:2598 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "하드 디스크에 yaboot 설치" #. Tag: para -#: using-d-i.xml:2600 +#: using-d-i.xml:2599 #, no-c-format msgid "" "Newer (mid 1998 and on) PowerMacs use yaboot as their " @@ -3967,13 +3966,13 @@ msgstr "" "크가 부팅 가능하게 되고 OpenFirmware에서 &debian; 부팅 준비가 끝납니다." #. Tag: title -#: using-d-i.xml:2618 +#: using-d-i.xml:2617 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "하드 디스크에 Quik 설치" #. Tag: para -#: using-d-i.xml:2619 +#: using-d-i.xml:2618 #, no-c-format msgid "" "The boot loader for OldWorld Power Macintosh machines is quikzipl-installer" msgstr "zipl-installer" #. Tag: para -#: using-d-i.xml:2636 +#: using-d-i.xml:2635 #, no-c-format msgid "" "The boot loader on &arch-title; is zipl. ZIPL를 보십시오." #. Tag: title -#: using-d-i.xml:2653 +#: using-d-i.xml:2652 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "하드 디스크에 SILO 부트로더 설치" #. Tag: para -#: using-d-i.xml:2655 +#: using-d-i.xml:2654 #, no-c-format msgid "" "The standard &architecture; boot loader is called silo. It is " @@ -4045,13 +4044,13 @@ msgstr "" "Solaris와 같이 설치할 때 유용합니다." #. Tag: title -#: using-d-i.xml:2680 +#: using-d-i.xml:2679 #, no-c-format msgid "Continue Without Boot Loader" msgstr "부트로더 없이 계속" #. Tag: para -#: using-d-i.xml:2682 +#: using-d-i.xml:2681 #, no-c-format msgid "" "This option can be used to complete the installation even when no boot " @@ -4068,7 +4067,7 @@ msgstr "" "지하면서 기존 운영체제에서 GNU/리눅스를 부팅하는 경우에 사용합니다." #. Tag: para -#: using-d-i.xml:2691 +#: using-d-i.xml:2690 #, no-c-format msgid "" "If you plan to manually configure your bootloader, you should check the name " @@ -4089,13 +4088,13 @@ msgstr "" "시스템의 디스크 및 파티션도 알아야 합니다." #. Tag: title -#: using-d-i.xml:2708 +#: using-d-i.xml:2707 #, no-c-format msgid "Finishing the Installation" msgstr "설치 마치기" #. Tag: para -#: using-d-i.xml:2709 +#: using-d-i.xml:2708 #, no-c-format msgid "" "These are the last bits to do before rebooting to your new system. It mostly " @@ -4105,13 +4104,13 @@ msgstr "" "&d-i;를 정리하는 작업들입니다." #. Tag: title -#: using-d-i.xml:2721 +#: using-d-i.xml:2720 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "설치 마치기 및 다시 시작하기" #. Tag: para -#: using-d-i.xml:2723 +#: using-d-i.xml:2722 #, no-c-format msgid "" "This is the last step in the initial Debian installation process. You will " @@ -4124,7 +4123,7 @@ msgstr "" "작업을 다 마친 다음에, 새로 설치한 데비안 시스템으로 다시 시작합니다." #. Tag: para -#: using-d-i.xml:2730 +#: using-d-i.xml:2729 #, no-c-format msgid "" "Select the Finish the installation menu item " @@ -4138,13 +4137,13 @@ msgstr "" "팅하면 (IPL) 됩니다." #. Tag: title -#: using-d-i.xml:2744 +#: using-d-i.xml:2743 #, no-c-format msgid "Miscellaneous" msgstr "기타" #. Tag: para -#: using-d-i.xml:2745 +#: using-d-i.xml:2744 #, no-c-format msgid "" "The components listed in this section are usually not involved in the " @@ -4155,13 +4154,13 @@ msgstr "" "하지만 백그라운드에서 기다리면서 잘못된 부분이 있을 때 도움이 됩니다." #. Tag: title -#: using-d-i.xml:2758 +#: using-d-i.xml:2757 #, no-c-format msgid "Saving the installation logs" msgstr "설치 로그 저장" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2759 #, no-c-format msgid "" "If the installation is successful, the logfiles created during the " @@ -4172,7 +4171,7 @@ msgstr "" "/var/log/installer/ 파일에 자동으로 저장합니다." #. Tag: para -#: using-d-i.xml:2767 +#: using-d-i.xml:2766 #, no-c-format msgid "" "Choosing Save debug logs from the main menu " @@ -4187,13 +4186,13 @@ msgstr "" "로그를 설치 보고서에 첨부할 때 유용합니다." #. Tag: title -#: using-d-i.xml:2787 +#: using-d-i.xml:2786 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "쉘 사용하기 및 로그 보기" #. Tag: para -#: using-d-i.xml:2790 +#: using-d-i.xml:2789 #, no-c-format msgid "" "There is an Execute a Shell item on the menu. If " @@ -4215,7 +4214,7 @@ msgstr "" "다." #. Tag: para -#: using-d-i.xml:2802 +#: using-d-i.xml:2801 #, no-c-format msgid "" "At this point you are booted from the RAM disk, and there is a limited set " @@ -4232,7 +4231,7 @@ msgstr "" "같은 훌륭한 기능도 좀 있습니다." #. Tag: para -#: using-d-i.xml:2811 +#: using-d-i.xml:2810 #, no-c-format msgid "" "Use the menus to perform any task that they are able to do — the shell " @@ -4251,13 +4250,13 @@ msgstr "" "한 경우에는 exit 명령을 실행하면 메뉴로 돌아갑니다." #. Tag: title -#: using-d-i.xml:2830 +#: using-d-i.xml:2829 #, no-c-format msgid "Installation Over the Network" msgstr "네트워크를 통해 설치" #. Tag: para -#: using-d-i.xml:2832 +#: using-d-i.xml:2831 #, no-c-format msgid "" "One of the more interesting components is network-consoleAfter selecting this new entry, you " @@ -4325,7 +4324,7 @@ msgstr "" "치할 사람에게 안전하게 전달해야 합니다." #. Tag: para -#: using-d-i.xml:2872 +#: using-d-i.xml:2871 #, no-c-format msgid "" "Should you decide to continue with the installation locally, you can always " @@ -4336,7 +4335,7 @@ msgstr "" "주 메뉴로 돌아갈 수 있습니다. 주 메뉴에서 다른 구성 요소를 선택하면 됩니다." #. Tag: para -#: using-d-i.xml:2878 +#: using-d-i.xml:2877 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need " @@ -4366,7 +4365,7 @@ msgstr "" "핑거프린트가 표시될 것이고, 이 핑거프린트가 올바른 지 확인해야 합니다." #. Tag: para -#: using-d-i.xml:2895 +#: using-d-i.xml:2894 #, no-c-format msgid "" "If you install several computers in turn and they happen to have the same IP " @@ -4383,7 +4382,7 @@ msgstr "" "당 줄을 지우고 다시 연결하면 됩니다." #. Tag: para -#: using-d-i.xml:2904 +#: using-d-i.xml:2903 #, no-c-format msgid "" "After the login you will be presented with an initial screen where you have " @@ -4402,7 +4401,7 @@ msgstr "" "야 합니다. 하지만 쉘의 경우에는 여러 개를 열어도 됩니다." #. Tag: para -#: using-d-i.xml:2914 +#: using-d-i.xml:2913 #, no-c-format msgid "" "After you have started the installation remotely over SSH, you should not go " @@ -4417,7 +4416,7 @@ msgstr "" "발생할 수 있습니다." #. Tag: para -#: using-d-i.xml:2922 +#: using-d-i.xml:2921 #, no-c-format msgid "" "Also, if you are running the SSH session from an X terminal, you should not " diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index 6ee43bf31..b4048e6c9 100644 --- a/po/pot/boot-installer.pot +++ b/po/pot/boot-installer.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -14,3 +14,2619 @@ msgstr "" "Content-Type: application/x-xml2pot; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\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 "SRM console, 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 "ARC, AlphaBIOS, or ARCSBIOS console, 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 cfdisk) for the boot disk. Therefore MS-DOS partition tables are the native 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 incompatible Specifically, the bootsector format required by the Console Subsystem Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the BSD disklabel format, this is the native 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 MILO 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 for the system type names). The word ARC 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 "xl" +msgstr "" + +#. Tag: entry +#: boot-installer.xml:192 +#, no-c-format +msgid "xlt" +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, aboot, a small, platform-independent bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." +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: MILO and aboot." +msgstr "" + +#. Tag: para +#: boot-installer.xml:221 +#, no-c-format +msgid "MILO is itself a console, which replaces ARC or SRM in memory. MILO can be booted from both ARC and SRM and is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." +msgstr "" + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "aboot is a small, platform-independent bootloader, which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." +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 MILO is available: \n" + "SRM -> aboot\n" + "SRM -> MILO\n" + "ARC -> MILO\n" + " Because MILO 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 aboot 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 half-flash 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 arc 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 Except on Jensen, where Linux is not supported on firmware versions newer than 1.7 — see for more information. before installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." +msgstr "" + +#. Tag: title +#: boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 boot-installer.xml:2500 boot-installer.xml:2596 +#, 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 ewa prefix, and will be listed in the output of the show dev command, like this (edited slightly): \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" + " You first need to set the boot protocol: \n" + ">>> set ewa0_protocols bootp\n" + " Then check the medium type is correct: \n" + ">>> set ewa0_mode mode\n" + " You can get a listing of valid modes with >>>set ewa0_mode." +msgstr "" + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "" + "Then, to boot from the first Ethernet interface, you would type: \n" + ">>> boot ewa0 -flags \"\"\n" + " 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 must pass the console= parameter to the kernel. This can be done using the -flags argument to the SRM boot command. The serial ports are named the same as their corresponding files in /dev. 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 ewa0 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 \n" + ">>> boot xxxx -flags 0\n" + " where xxxx 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 ), then enter \\milo\\linload.exe as the boot loader and \\milo\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: You need to use \\milo\\ldmilo.exe 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 (>>>), issue the following command: \n" + ">>> boot dva0 -flags 0\n" + " possibly replacing dva0 with the actual device name. Usually, dva0 is the floppy; type \n" + ">>> show dev\n" + " to see the list of devices (e.g., if you want to boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. 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 aboot, use the following command: \n" + ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 load_ramdisk=1 arguments\"\n" + " (typed on one line), substituting, if necessary, the actual SRM boot device name for dva0, the Linux boot device name for fd0, and the desired kernel parameters for arguments." +msgstr "" + +#. Tag: para +#: boot-installer.xml:388 +#, no-c-format +msgid "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See ." +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 linload.exe as the boot loader, and milo 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: \n" + "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" + " If you are booting from something other than a floppy, substitute fd0 in the above example with the appropriate device name in Linux notation. The help 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:1005 boot-installer.xml:1508 boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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:1010 boot-installer.xml:1513 boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, 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:1015 boot-installer.xml:1518 boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "The installation method to support network booting is described in ." +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 eth0) 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 interface (the one labeled with 10 Base-T)." +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 ." +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: \n" + " NeTTrom command-> load-defaults\n" + " Furthermore, you must configure the network, either with a static address: \n" + " NeTTrom command-> setenv netconfig_eth0 flash\n" + " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" + " where 24 is the number of set bits in the netmask, or a dynamic address: \n" + " NeTTrom command-> setenv netconfig_eth0 dhcp\n" + " You may also need to configure the route1 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. \n" + " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" + " NeTTrom command-> setenv kerntftpfile boot.img\n" + " NeTTrom command-> save-all\n" + " Now you have to tell the firmware that the TFTP image should be booted: \n" + " NeTTrom command-> setenv kernconfig tftp\n" + " NeTTrom command-> setenv rootdev /dev/ram\n" + " If you use a serial console to install your Netwinder, you need to add the following setting: \n" + " NeTTrom command-> setenv cmdappend root=/dev/ram console=ttyS0,115200\n" + " Alternatively, for installations using a keyboard and monitor you have to set: \n" + " NeTTrom command-> setenv cmdappend root=/dev/ram\n" + " You can use the printenv command to review your environment settings. After you have verified that the settings are correct, you can load the image: \n" + " NeTTrom command-> boot\n" + " In case you run into any problems, a detailed HOWTO 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 boot de0: 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:1127 boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a CD as described in , insert your CD, reboot, and proceed to the next chapter." +msgstr "" + +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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:1146 boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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:1154 boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "If you have problems booting, see ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "To boot a CD-ROM from the Cyclone console prompt, use the command boot cd0:cats.bin" +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 Upgrade. You can then browse your disk for the installer image you have previously downloaded. Then press the Start Upgrade 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 upslug2 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: Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 Press and hold the reset button (accessible through the small hole on the back just above the power input). Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/status LED. After 10 seconds it will change from amber to red. Immediately release the reset button. 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. See the NSLU2-Linux pages if you have problems with this. Once your NSLU2 is in upgrade mode, you can flash the new image: \n" + "sudo upslug2 -i di-nslu2.bin\n" + " 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 a tool for Windows to upgrade the firmware via the network." +msgstr "" + +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "Booting from Linux Using LILO or GRUB" +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 ." +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 netboot/debian-installer/i386/initrd.gz file and its corresponding kernel netboot/debian-installer/i386/linux. 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:866 +#, 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 hd-media/initrd.gz file and its kernel, as well as copy a CD iso to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from the CD image, without needing the network." +msgstr "" + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "For LILO, you will need to configure two essential things in /etc/lilo.conf: to load the initrd.gz installer at boot time; have the vmlinuz kernel use a RAM disk as its root partition. Here is a /etc/lilo.conf example:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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:896 +#, no-c-format +msgid "For more details, refer to the initrd 4 and lilo.conf 5 man pages. Now run lilo and reboot." +msgstr "" + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" + "The procedure for GRUB is quite similar. Locate your menu.lst in the /boot/grub/ directory (sometimes in the /boot/boot/grub/), add the following lines: \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" + " and reboot." +msgstr "" + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "Note that the value of the ramdisk_size may need to be adjusted for the size of the initrd image. From here on, there should be no difference between GRUB or LILO." +msgstr "" + +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "Let's assume you have prepared everything from and . 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 boot: prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" + +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "" + +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "You will have already downloaded the floppy images you needed and created floppies from the images in ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:949 +#, 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:955 +#, 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 root= 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 linux root=/dev/hdc at the boot prompt." +msgstr "" + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "Note that on some machines, Control Alt Delete does not properly reset the machine, so a hard 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:974 +#, 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 boot: prompt." +msgstr "" + +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "Once you press &enterkey;, you should see the message Loading..., followed by Uncompressing Linux..., 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 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically launched." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "It could be that your Network Interface Card or Motherboard provides PXE boot functionality. This is a Intel 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:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "It could be that your Network Interface Card provides TFTP boot functionality." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "Let us (&email-debian-boot-list;) know how did you manage it. Please refer to this document." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "The etherboot project provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: \n" + "Press F1 for help, or ENTER to boot:\n" + " 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:1078 +#, no-c-format +msgid "Information on available boot methods and on boot parameters which might be useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type the boot method (the default is linux) and a space before the first parameter (e.g., linux fb=false)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's Integrated Remote Assistant (IRA). You can blindly press F1 In some cases these devices will require special escape sequences to enact this keypress, for example the IRA uses Ctrl F , 1. 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 fb=false to the boot prompt, as described in the help text." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "There are three basic variations of Debian Install CDs. The Business Card 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 Network Install 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:1180 +#, 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:1196 +#, no-c-format +msgid "The Debian Installer CD contains a small EFI partition where the ELILO 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:1205 +#, no-c-format +msgid "Most of the details of how ELILO 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 ELILO 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:1217 +#, 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, Boot Option Maintenance Menu and EFI Shell (Built-in). 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:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the shell prompt." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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:1262 +#, no-c-format +msgid "Select Boot Maintenance Menu from the menu with the arrow keys and press ENTER. This will display a new menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "Select Boot From a File from the menu with the arrow keys and press ENTER. This will display a list of devices probed by the firmware. You should see two menu lines containing either the label Debian Inst [Acpi ... or Removable Media Boot. 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:1279 +#, 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 ENTER. If you choose Removable Media Boot the machine will immediately start the boot load sequence. If you choose Debian Inst [Acpi ... 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:1290 +#, no-c-format +msgid "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like Removable Media Boot] on the next to the last line. Select this line with the arrow keys and press ENTER. This will start the boot load sequence." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1302 +#, 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:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 EFI Shell [Built-in]. Boot the Debian Installer CD with the following steps:" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1324 +#, 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:1330 +#, no-c-format +msgid "Select EFI Shell from the menu with the arrow keys and press ENTER. 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 fsn:. All other recognized partitions will be named blkn:. 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:1344 +#, no-c-format +msgid "Examine the output from the shell looking for the CDROM drive. It is most likely the fs0: device although other devices with bootable partitions will also show up as fsn." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "Enter fsn: and press ENTER to select that device where n is the partition number for the CDROM. The shell will now display the partition number as its prompt." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "Enter elilo and press ENTER. This will start the boot load sequence." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel and options." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud serial console], where BAUD 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:1392 +#, 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 baud at the EFI shell." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into the Boot: text window." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for instructions on starting the installer in Text Mode." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1419 +#, 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:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "The boot loader will display a form with a menu list and a text window with a Boot: 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 General help screen explains the menu choices and the Params screen explains the common command line options." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "Consult the General help screen for the description of the kernels and install modes most appropriate for your installation. You should also consult below for any additional parameters that you may want to set in the Boot: 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:1460 +#, 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:1465 +#, 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:1472 +#, no-c-format +msgid "Press ENTER. 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:1481 boot-installer.xml:1617 +#, 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:1492 +#, no-c-format +msgid "Booting an IA-64 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:1526 +#, no-c-format +msgid "Network booting an IA-64 system requires two architecture-specific actions. On the boot server, DHCP and TFTP must be configured to deliver elilo. 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:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1538 +#, no-c-format +msgid "" + "A suitable TFTP entry for network booting an IA-64 system looks something like this: \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" + " Note that the goal is to get elilo.efi running on the client." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "Extract the netboot.tar.gz file into the directory used as the root for your tftp server. Typical tftp root directories include /var/lib/tftp and /tftpboot. This will create a debian-installer directory tree containing the boot files for an IA-64 system." +msgstr "" + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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:1558 +#, no-c-format +msgid "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you need to make changes to this file, you can find it in the debian-installer/ia64/ 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 .conf instead of elilo.conf. See documentation provided in the elilo package for details." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "To configure the client to support TFTP booting, start by booting to EFI and entering the Boot Option Maintenance Menu. Add a boot option. You should see one or more lines with the text Load File [Acpi()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options menu. You should see the new boot option you just created, and selecting it should initiate a DHCP query, leading to a TFTP load of elilo.efi from the server." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1608 +#, 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: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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:1640 +#, 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:1645 +#, no-c-format +msgid "Make sure root=/dev/ram is one of your kernel parameters." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "If you're having trouble, check cts's &arch-title; debian-installer FAQ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "The only method of installation available to amiga is the hard drive (see ). In other words the cdrom is not bootable." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "Amiga does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter fb=false." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "Atari does not currently work with bogl, so if you are seeing bogl errors, you need to include the boot parameter fb=false." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "The only method of installation available to mac is from the hard drive (see ). In other words the cdrom is not bootable. Macs do not have a working 2.4.x kernel." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "If your hardware uses a 53c9x-based scsi bus, then you may need to include the kernel parameter mac53c9x=1,0. Hardware with two such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as mac53c9x=-1,0 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:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "The installer for MVME147 and MVME16x may be started from either floppies (see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "The only method of installation available to Q40/Q60 is from the hard drive (see ). In other words the cdrom is not bootable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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:1769 boot-installer.xml:2367 +#, no-c-format +msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files in ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "The three different types of ramdisks are cdrom, hd-media, and nativehd. These ramdisks differ only in their source for installation packages. The cdrom ramdisk uses a cdrom to get debian-installer packages. The hd-media ramdisk uses an iso image file of a cdrom currently residing on a hard disk. Finally, the nativehd ramdisk uses the net to install packages." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "In the Workbench, start the Linux installation process by double-clicking on the StartInstall icon in the debian directory." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "At the GEM desktop, start the Linux installation process by double-clicking on the bootstra.prg icon in the debian directory and clicking Ok at the program options dialog box." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "You must retain the original Mac system and boot from it. It is essential that, when booting MacOS in preparation for booting the Penguin linux loader, you hold the shift 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:1864 +#, no-c-format +msgid "Macs require the Penguin bootloader. If you do not have the tools to handle a Stuffit archive, &penguin19.hfs; is an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "At the MacOS desktop, start the Linux installation process by double-clicking on the Penguin Prefs icon in the Penguin directory. The Penguin booter will start up. Go to the Settings item in the File menu, click the Kernel tab. Select the kernel (vmlinuz) and ramdisk (initrd.gz) images in the install 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:1888 +#, no-c-format +msgid "To set the boot parameters in Penguin, choose File -> Settings..., then switch to the Options tab. Boot parameters may be typed in to the text entry area. If you will always want to use these settings, select File -> Save Settings as Default." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "Close the Settings dialog, save the settings and start the bootstrap using the Boot Now item in the File menu." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "The Penguin 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 ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "The installation program should start automatically, so you can continue below at ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "Currently, the only &arch-title; subarchitecture that supports CD-ROM booting is the BVME6000." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "After booting the VMEbus systems you will be presented with the LILO Boot: 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:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "You may additionally append the string TERM=vt100 to use vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "For most &arch-title; architectures, booting from a local filesystem is the recommended method." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2054 +#, 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:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" + "After entering the command monitor use \n" + "bootp():\n" + " 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 netaddr environment variable. Type \n" + "unsetenv netaddr\n" + " in the command monitor to do this." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: \n" + "ifconfig eth0 -auto\n" + " Once you have obtained an IP address, you can load SiByl with the following command: \n" + "boot 192.168.1.1:/boot/sibyl\n" + " 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:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" + "Following the bootp(): 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: \n" + "bootp():/boot/tftpboot.img\n" + " Further kernel parameters can be passed via append:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "You cannot pass any boot parameters directly from the CFE prompt. Instead, you have to edit the /boot/sibyl.conf file on the TFTP server and add your parameters to the extra_args variable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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:2170 +#, 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:2179 +#, 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:2222 +#, no-c-format +msgid "You cannot pass any boot parameters directly. Instead, you have to edit the /nfsroot/default.colo file on the NFS server and add your parameters to the args variable." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2251 +#, 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:2256 +#, 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 an ssh session which will launch the standard installation system." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2267 +#, no-c-format +msgid "s390 Boot Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more information about S/390-specific boot parameters." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, Option, Shift, and Delete keys together while booting to boot from the CD-ROM." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2331 +#, 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:2340 +#, 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 for booting from the hard disk, except use the path to yaboot on the CD at the OF prompt, such as" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "" + +#. Tag: title +#: boot-installer.xml:2355 +#, no-c-format +msgid "Booting from Hard Disk" +msgstr "" + +#. Tag: title +#: boot-installer.xml:2376 +#, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "If you set up BootX in , you can use it to boot into the installation system. Double click the BootX application icon. Click on the Options button and select Use Specified RAM Disk. This will give you the chance to select the ramdisk.image.gz file. You may need to select the No Video Driver checkbox, depending on your hardware. Then click the Linux button to shut down MacOS and launch the installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" + "You will have already placed the vmlinux, initrd.gz, yaboot, and yaboot.conf files at the root level of your HFS partition in . Restart the computer, and immediately (during the chime) hold down the Option, Command (cloverleaf/Apple), o, and f keys all together. After a few seconds you will be presented with the Open Firmware prompt. At the prompt, type \n" + "0 > boot hd:x,yaboot\n" + " replacing x 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 ide0: instead of hd:. In a few more seconds you will see a yaboot prompt \n" + "boot:\n" + " At yaboot's boot: prompt, type either install or install video=ofonly followed by a &enterkey;. The video=ofonly argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2440 +#, no-c-format +msgid "Booting from USB memory stick" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "Make sure you have prepared everything from . 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 Command Option o f all together while booting (see )." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "You will need to work out where the USB storage device appears in the device tree, since at the moment ofpath cannot work that out automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and /pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" + "Having worked out the device path, use a command like this to boot the installer: \n" + "boot usb0/disk:2,\\\\:tbxi\n" + " The 2 matches the Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image earlier, and the ,\\\\:tbxi part instructs Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. yaboot) in the directory previously blessed with hattrib -b." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2485 +#, no-c-format +msgid "The system should now boot up, and you should be presented with the boot: prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see ) and use the command boot enet:0. PReP and CHRP boxes may have different ways of addressing the network. On a PReP machine, you should try boot server_ipaddr,file,client_ipaddr." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2543 +#, 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:2555 +#, no-c-format +msgid "To boot from the boot-floppy-hfs.img floppy, place it in floppy drive after shutting the system down, and before pressing the power-on button." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2561 +#, 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:2568 +#, no-c-format +msgid "After booting, the root.bin 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:2579 +#, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 video=atyfb:vmode:6 , which will select that mode for most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to video=aty128fb:vmode:6 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "On machines with OpenBoot, simply enter the boot monitor on the machine which is being installed (see ). Use the command boot net to boot from a TFTP and RARP server, or try boot net:bootp or boot net:dhcp to boot from a TFTP and BOOTP or DHCP server. Some older OpenBoot revisions require using the device name, such as boot le(); these probably don't support BOOTP nor DHCP." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "Most OpenBoot versions support the boot cdrom 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:2691 +#, no-c-format +msgid "" + "To boot from floppy on a Sparc, use \n" + "Stop-A -> OpenBoot: \"boot floppy\"\n" + " Be warned that the newer Sun4u (ultra) architecture does not support floppy booting. A typical error message is Bad magic number in disk label - Can't open disk label package. 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:2703 +#, 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 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" + "If you are booting from the floppy, and you see messages such as \n" + "Fatal error: Cannot read partition\n" + "Illegal or malformed device name\n" + " then it is possible that floppy booting is simply not supported on your machine." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "If you cannot boot because you get messages about a problem with IDPROM, then it's possible that your NVRAM battery, which holds configuration information for you firmware, has run out. See the Sun NVRAM FAQ for more information." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2742 +#, 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:2749 +#, 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:2756 +#, no-c-format +msgid "Information on many boot parameters can be found in the Linux BootPrompt HOWTO, including tips for obscure hardware. This section contains only a sketch of the most salient parameters. Some common gotchas are included below in ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" + "When the kernel boots, a message \n" + "Memory:availk/totalk available\n" + " should be emitted early in the process. total 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 mem=ram parameter, where ram is set to the amount of memory, suffixed with k for kilobytes, or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "If you are booting with a serial console, generally the kernel will autodetect this (although not on DECstations). 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 console=device argument to the kernel, where device is your serial device, which is usually something like ttyS0." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "For &arch-title; the serial devices are ttya or ttyb. Alternatively, set the input-device and output-device OpenPROM variables to ttya." +msgstr "" + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2806 +#, no-c-format +msgid "The installation system recognizes a few additional boot parameters With current kernels (2.6.9 or newer) you can use 32 command line options and 32 environment options. If these numbers are exceeded, the kernel will panic. which may be useful." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "This parameter sets the lowest priority of messages to be displayed. Short form: priority" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "The default installation uses priority=high. 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:2836 +#, no-c-format +msgid "If you add priority=medium as boot parameter, you will be shown the installation menu and gain more control over the installation. When priority=low is used, all messages are shown (this is equivalent to the expert boot method). With priority=critical, the installation system will display only critical messages and try to do the right thing without fuss." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2851 +#, no-c-format +msgid "This boot parameter controls the type of user interface used for the installer. The current possible parameter settings are: DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk The default frontend is DEBIAN_FRONTEND=newt. DEBIAN_FRONTEND=text may be preferable for serial console installs. Generally only the newt frontend is available on default install media. On architectures which support it, the graphical installer uses the gtk frontend." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "" + +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "The value of the parameter is the path to the device to load the Debian installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "The boot floppy, which normally scans all floppies 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:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/framebuffer=false, or fb=false for short. 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:2948 +#, no-c-format +msgid "The video=vga16:off argument may also be used to disable the kernel's use of the framebuffer. Such problems have been reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "Because of display problems on some systems, framebuffer support is disabled by default 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 debian-installer/framebuffer=true or fb=true for short." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "A theme determines how the user interface of the installer looks (colors, icons, etc.). What themes are available differs per frontend. Currently both the newt and gtk frontends only have a dark theme that was designed for visually impaired users. Set the theme by booting with parameter debian-installer/theme=dark or theme=dark." +msgstr "" + +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "Set to false to prevent probing for USB on boot, if that causes problems." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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:3008 +#, 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 netcfg/disable_dhcp=true to prevent configuring the network with DHCP and to enter the information manually." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "Set to false to prevent starting PCMCIA services, if that causes problems. Some laptops are well known for this misbehavior." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3031 +#, no-c-format +msgid "Specify the url to a preconfiguration file to download and use in automating the install. See . Short form: url." +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 . Short form: file." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3052 +#, no-c-format +msgid "auto-install/enabled" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. Short form: auto=true See for details about using this to automate installs." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3065 +#, 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:3074 +#, no-c-format +msgid "Set to false 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:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3086 +#, 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:3094 +#, no-c-format +msgid "mouse/left" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3095 +#, no-c-format +msgid "For the gtk frontend (graphical installer), users can switch the mouse to left-handed operation by setting this parameter to true." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "For the gtk frontend (graphical installer), hardware acceleration in directfb is disabled by default. To enable it, set this parameter to true when booting the installer." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "Set to true to enter rescue mode rather than performing a normal installation. See ." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "With some exceptions, a value can be set at the boot prompt for any question asked during the installation, though this is only really useful in specific cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3140 +#, no-c-format +msgid "debian-installer/locale" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "Can be used to set both the language and country for the installation. This will only work if the locale is supported in Debian. Short form: locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "Set to true if you want to disable DHCP and instead force static network configuration." +msgstr "" + +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "Can be used to select tasks that are not available from the interactive task list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "If drivers are compiled into the kernel, you can pass parameters to them as described in the kernel documentation. However, if drivers are compiled as modules and because kernel modules are loaded a bit differently during an installation than when booting an installed system, it is not possible to pass parameters to modules as you would normally do. Instead, you need to use a special syntax recognized by the installer which will then make sure that the parameters are saved in the proper configuration files and will thus be used when the modules are actually loaded. The parameters will also be propagated automatically to the configuration for the installed system." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "Note that it is now quite rare that parameters need to be passed to modules. In most cases the kernel will be able to probe the hardware present in a system and set good defaults that way. However, in some situations it may still be needed to set parameters manually." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" + "The syntax to use to set parameters for modules is: \n" + "module_name.parameter_name=value\n" + " If you need to pass multiple parameters to the same or different modules, just repeat this. For example, to set an old 3Com network interface card to use the BNC (coax) connector and IRQ 10, you would pass:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "" + +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "" + +#. Tag: title +#: boot-installer.xml:3226 +#, no-c-format +msgid "CD-ROM Reliability" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "Sometimes, especially with older CD-ROM drives, the installer may fail to boot from a CD-ROM. The installer may also — even after booting successfully from CD-ROM — fail to recognize the CD-ROM or return errors while reading from it during the installation." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "There are a many different possible causes for these problems. We can only list some common issues and provide general suggestions on how to deal with them. The rest is up to you." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "If the CD-ROM does not boot, check that it was inserted correctly and that it is not dirty." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "If the installer fails to recognize a CD-ROM, try just running the option Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives are known to be resolved in this way." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "If this does not work, then try the suggestions in the subsections below. Most, but not all, suggestions discussed there are valid for both CD-ROM and DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "If you cannot get the installation working from CD-ROM, try one of the other installation methods that are available." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "Some older CD-ROM drives do not support reading from discs that were burned at high speeds using a modern CD writer." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that Linux also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "Some older CD-ROM drives do not work correctly if direct memory access (DMA) is enabled." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "Check that your BIOS actually supports booting from CD-ROM (older systems possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" + "If you downloaded an iso image, check that the md5sum of that image matches the one listed for the image in the MD5SUMS file that should be present in the same location as where you downloaded the image from. \n" + "$ md5sum debian-testing-i386-netinst.iso\n" + "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst.iso\n" + " Next, check that the md5sum of the burned CD-ROM matches as well. The following command should work. It uses the size of the image to read the correct number of bytes from the CD-ROM." +msgstr "" + +#. Tag: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" + "$ dd if=/dev/cdrom | \\\n" + "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" + "> md5sum\n" + "a20391b12f7ff22ef705cee4059c6b92 -\n" + "262668+0 records in\n" + "262668+0 records out\n" + "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "If, after the installer has been booted successfully, the CD-ROM is not detected, sometimes simply trying again may solve the problem. If you have more than one CD-ROM drive, try changing the CD-ROM to the other drive. If that does not work or if the CD-ROM is recognized but there are errors when reading from it, try the suggestions listed below. Some basic knowledge of Linux is required for this. To execute any of the commands, you should first switch to the second virtual console (VT2) and activate the shell there." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any specific error messages. After that, also check the output of dmesg." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3351 +#, no-c-format +msgid "" + "Check in the output of dmesg if your CD-ROM drive was recognized. You should see something like (the lines do not necessarily have to be consecutive): \n" + "Probing IDE interface ide1...\n" + "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" + "ide1 at 0x170-0x177,0x376 on irq 15\n" + "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" + "Uniform CD-ROM driver Revision: 3.20\n" + " If you don't see something like that, chances are the controller your CD-ROM is connected to was not recognized or may be not supported at all. If you know what driver is needed for the controller, you can try loading it manually using modprobe." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "Check that there is a device node for your CD-ROM drive under /dev/. In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3373 +#, no-c-format +msgid "" + "Use the mount command to check if the CD-ROM is already mounted; if not, try mounting it manually: \n" + "$ mount /dev/hdc /cdrom\n" + " Check if there are any error messages after that command." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3383 +#, no-c-format +msgid "" + "Check if DMA is currently enabled: \n" + "$ cd /proc/ide/hdc\n" + "$ grep using_dma settings\n" + "using_dma 1 0 1 rw\n" + " A 1 in the first column after using_dma means it is enabled. If it is, try disabling it: \n" + "$ echo -n \"using_dma:0\" >settings\n" + " Make sure that you are in the directory for the device that corresponds to your CD-ROM drive." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3398 +#, no-c-format +msgid "If there are any problems during the installation, try checking the integrity of the CD-ROM using the option near the bottom of the installer's main menu. This option can also be used as a general test if the CD-ROM can be read reliably." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3413 +#, no-c-format +msgid "Floppy Disk Reliability" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3415 +#, 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:3420 +#, 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:3429 +#, no-c-format +msgid "If you are having the installation stall at a particular floppy, the first thing you should do is write the image to a different floppy and see if that solves the problem. 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:3438 +#, no-c-format +msgid "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the third floppy." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3444 +#, no-c-format +msgid "Normally you should not have to download a floppy image again, but if you are experiencing problems it is always useful to verify that the images were downloaded correctly by verifying their md5sums." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3450 +#, 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:3459 +#, no-c-format +msgid "Boot Configuration" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3461 +#, 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 ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3468 +#, no-c-format +msgid "If you are booting with your own kernel instead of the one supplied with the installer, be sure that CONFIG_DEVFS is set in your kernel. The installer requires CONFIG_DEVFS." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3475 +#, no-c-format +msgid "Often, problems can be solved by removing add-ons and peripherals, and then trying booting again. Internal modems, sound cards, and Plug-n-Play devices can be especially problematic." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3481 +#, 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 mem=512m." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3492 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3493 +#, 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:3498 +#, no-c-format +msgid "Some systems have floppies with inverted DCLs. If you receive errors reading from the floppy, even when you know the floppy is good, try the parameter floppy=thinkpad." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3504 +#, 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 hd=cylinders,heads,sectors." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3513 +#, no-c-format +msgid "If you have a very old machine, and the kernel hangs after saying Checking 'hlt' instruction..., then you should try the no-hlt boot argument, which disables this test." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3520 +#, 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 fb=false video=vga16:off to disable the framebuffer console. Only the English language will be available during the installation due to limited console features. See for details." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3534 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3535 +#, 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 hw-detect/start_pcmcia=false 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:3545 +#, 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 exclude port 0x800-0x8ff here. There is also a list of some common resource range options in the System resource settings section of the PCMCIA HOWTO. Note that you have to omit the commas, if any, when you enter this value in the installer." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3562 +#, no-c-format +msgid "System Freeze while Loading the USB Modules" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3563 +#, 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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from being loaded." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3577 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3579 +#, no-c-format +msgid "During the boot sequence, you may see many messages in the form can't find something , or something not present, can't initialize something , or even this driver release depends on something . 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 )." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3604 +#, no-c-format +msgid "Reporting Installation Problems" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3605 +#, no-c-format +msgid "If you get through the initial boot phase but cannot complete the install, the menu option Save debug logs may be helpful. It lets you store system error logs and configuration information from the installer to a floppy, or download them using 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:3616 +#, no-c-format +msgid "Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" + +#. Tag: title +#: boot-installer.xml:3627 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "" + +#. Tag: para +#: boot-installer.xml:3628 +#, 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:3635 +#, no-c-format +msgid "Note that your installation report will be published in the Debian Bug Tracking System (BTS) and forwarded to a public mailing list. Make sure that you use an E-Mail address that you do not mind being made public." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3641 +#, 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 (apt-get install installation-report reportbug) and run the command reportbug installation-report." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3648 +#, no-c-format +msgid "" + "Alternatively you can use this template when filling out installation reports, and file the report as a bug report against the installation-reports pseudo package, by sending it to submit@bugs.debian.org. \n" + "Package: installation-reports\n" + "\n" + "Boot method: <How did you boot the installer? CD? floppy? network?>\n" + "Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" + "\n" + "Base System Installation Checklist:\n" + "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" + "\n" + "Initial boot: [ ]\n" + "Detect network card: [ ]\n" + "Configure network: [ ]\n" + "Detect CD: [ ]\n" + "Load installer modules: [ ]\n" + "Detect hard drives: [ ]\n" + "Partition hard drives: [ ]\n" + "Install base system: [ ]\n" + "Clock/timezone setup: [ ]\n" + "User/password setup: [ ]\n" + "Install tasks: [ ]\n" + "Install boot loader: [ ]\n" + "Overall install: [ ]\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" + " 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/pot/preparing.pot b/po/pot/preparing.pot index 6b44895a8..7232e9aa4 100644 --- a/po/pot/preparing.pot +++ b/po/pot/preparing.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-26 16:20+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1823,95 +1823,89 @@ msgstr "" #. Tag: para #: preparing.xml:2079 #, 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 ." -msgstr "" - -#. Tag: para -#: preparing.xml:2090 -#, 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:2098 +#: preparing.xml:2087 #, no-c-format msgid "The Turbo Switch" msgstr "" #. Tag: para -#: preparing.xml:2099 +#: preparing.xml:2088 #, no-c-format msgid "Many systems have a turbo 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:2112 +#: preparing.xml:2101 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "" #. Tag: para -#: preparing.xml:2113 +#: preparing.xml:2102 #, no-c-format msgid "Many users of Cyrix CPUs have had to disable the cache in their systems during installation, because the floppy disk has errors if they do not. If you have to do this, be sure to re-enable your cache when you are finished with installation, as the system runs much slower with the cache disabled." msgstr "" #. Tag: para -#: preparing.xml:2121 +#: preparing.xml:2110 #, no-c-format msgid "We don't think this is necessarily the fault of the Cyrix CPU. It may be something that Linux can work around. We'll continue to look into the problem. For the technically curious, we suspect a problem with the cache being invalid after a switch from 16-bit to 32-bit code." msgstr "" #. Tag: title -#: preparing.xml:2131 +#: preparing.xml:2120 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "" #. Tag: para -#: preparing.xml:2132 +#: preparing.xml:2121 #, no-c-format msgid "You may have to change some settings or jumpers on your computer's peripheral cards. Some cards have setup menus, while others rely on jumpers. This document cannot hope to provide complete information on every hardware device; what it hopes to provide is useful tips." msgstr "" #. Tag: para -#: preparing.xml:2139 +#: preparing.xml:2128 #, no-c-format msgid "If any cards provide mapped memory, 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:2150 +#: preparing.xml:2139 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "" #. Tag: para -#: preparing.xml:2151 +#: preparing.xml:2140 #, no-c-format msgid "If you have no AT-style keyboard and only a USB model, you may need to enable legacy AT keyboard emulation in your BIOS setup. Only do this if the installation system fails to use your keyboard in USB mode. Conversely, for some systems (especially laptops) you may need to disable legacy USB support if your keyboard does not respond. Consult your main board manual and look in the BIOS for Legacy keyboard emulation or USB keyboard support options." msgstr "" #. Tag: title -#: preparing.xml:2164 +#: preparing.xml:2153 #, no-c-format msgid "More than 64 MB RAM" msgstr "" #. Tag: para -#: preparing.xml:2165 +#: preparing.xml:2154 #, no-c-format msgid "The Linux Kernel cannot always detect what amount of RAM you have. If this is the case please look at ." msgstr "" #. Tag: title -#: preparing.xml:2174 +#: preparing.xml:2163 #, no-c-format msgid "Display visibility on OldWorld Powermacs" msgstr "" #. Tag: para -#: preparing.xml:2175 +#: preparing.xml:2164 #, no-c-format msgid "Some OldWorld Powermacs, most notably those with the control display driver but possibly others as well, may not produce a colormap with reliably results in visible output under Linux when the display is configured for more than 256 colors. If you are experiencing such issues with your display after rebooting (you can sometimes see data on the monitor, but on other occasions cannot see anything) or, if the screen turns black after booting the installer instead of showing you the user interface, try changing your display settings under MacOS to use 256 colors instead of thousands or millions." msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index bb67ec27f..af8eca9b4 100644 --- a/po/pot/using-d-i.pot +++ b/po/pot/using-d-i.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -1847,119 +1847,119 @@ msgstr "" #. Tag: para #: using-d-i.xml:2302 #, 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 fdisk /mbr 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 ." +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 fdisk /mbr command to reinstall the MS-DOS master boot record — however, this means that you'll need to use some other way to get back into Debian!" msgstr "" #. Tag: title -#: using-d-i.xml:2319 +#: using-d-i.xml:2318 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2320 #, no-c-format msgid "The &architecture; boot loader is called elilo. It is modeled on the lilo 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 EFI Boot Manager menu in the firmware to point to the files in the EFI partition. The elilo boot loader is really in two parts. The /usr/sbin/elilo command manages the partition and copies file into it. The elilo.efi program is copied into the EFI partition and then run by the EFI Boot Manager to actually do the work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2337 +#: using-d-i.xml:2336 #, no-c-format msgid "The elilo 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 root filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2349 +#: using-d-i.xml:2348 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2351 +#: using-d-i.xml:2350 #, no-c-format msgid "The criteria for selecting a partition is that it is FAT format filesystem with its boot 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 elilo may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2366 +#: using-d-i.xml:2365 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2368 +#: using-d-i.xml:2367 #, 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 root filesystem. It is normally not mounted on a running system as it is only needed by the EFI Boot Manager to load the system and the installer part of the elilo writes to the filesystem directly. The /usr/sbin/elilo utility writes the following files into the efi/debian directory of the EFI partition during the installation. Note that the EFI Boot Manager would find these files using the path fsn:\\efi\\debian. 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:2390 +#: using-d-i.xml:2389 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2391 +#: using-d-i.xml:2390 #, no-c-format msgid "This is the configuration file read by the boot loader when it starts. It is a copy of the /etc/elilo.conf with the filenames re-written to refer to files in the EFI partition." msgstr "" #. Tag: filename -#: using-d-i.xml:2400 +#: using-d-i.xml:2399 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2401 +#: using-d-i.xml:2400 #, no-c-format msgid "This is the boot loader program that the EFI Boot Manager runs to boot the system. It is the program behind the Debian GNU/Linux menu item of the EFI Boot Manager command menu." msgstr "" #. Tag: filename -#: using-d-i.xml:2411 +#: using-d-i.xml:2410 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2411 #, 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 /etc/elilo.conf. In a standard Debian installation it would be the file in /boot pointed to by the symbolic link /initrd.img." msgstr "" #. Tag: filename -#: using-d-i.xml:2424 +#: using-d-i.xml:2423 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2425 +#: using-d-i.xml:2424 #, no-c-format msgid "This is a small text file warning you that the contents of the directory are managed by the elilo and that any local changes would be lost at the next time /usr/sbin/elilo is run." msgstr "" #. Tag: filename -#: using-d-i.xml:2435 +#: using-d-i.xml:2434 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2435 #, no-c-format msgid "This is the compressed kernel itself. It is a copy of the file referenced in the /etc/elilo.conf. In a standard Debian installation it would be the file in /boot pointed to by the symbolic link /vmlinuz." msgstr "" #. Tag: title -#: using-d-i.xml:2456 +#: using-d-i.xml:2455 #, no-c-format msgid "arcboot-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2457 +#: using-d-i.xml:2456 #, no-c-format msgid "" "The boot loader on SGI machines is arcboot. 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 /etc/arcboot.conf. Each configuration has a unique name, the default setup as created by the installer is linux. After arcboot has been installed, the system can be booted from hard disk by setting some firmware environment variables entering \n" @@ -1972,61 +1972,61 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2476 +#: using-d-i.xml:2475 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2477 +#: using-d-i.xml:2476 #, no-c-format msgid "is the SCSI bus to be booted from, this is 0 for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2485 +#: using-d-i.xml:2484 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2485 #, no-c-format msgid "is the SCSI ID of the hard disk on which arcboot is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2494 using-d-i.xml:2563 +#: using-d-i.xml:2493 using-d-i.xml:2562 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2495 +#: using-d-i.xml:2494 #, no-c-format msgid "is the number of the partition on which /etc/arcboot.conf resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2503 +#: using-d-i.xml:2502 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2503 #, no-c-format msgid "is the name of the configuration entry in /etc/arcboot.conf, which is linux by default." msgstr "" #. Tag: title -#: using-d-i.xml:2525 +#: using-d-i.xml:2524 #, no-c-format msgid "delo-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2525 #, no-c-format msgid "" "The boot loader on DECstations is DELO. 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 /etc/delo.conf. Each configuration has a unique name, the default setup as created by the installer is linux. After DELO has been installed, the system can be booted from hard disk by entering \n" @@ -2035,247 +2035,247 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2545 +#: using-d-i.xml:2544 #, no-c-format msgid "#" msgstr "" #. Tag: para -#: using-d-i.xml:2546 +#: using-d-i.xml:2545 #, no-c-format msgid "is the TurboChannel device to be booted from, on most DECstations this is 3 for the onboard controllers" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2554 +#: using-d-i.xml:2553 #, no-c-format msgid "id" msgstr "" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2554 #, no-c-format msgid "is the SCSI ID of the hard disk on which DELO is installed" msgstr "" #. Tag: para -#: using-d-i.xml:2564 +#: using-d-i.xml:2563 #, no-c-format msgid "is the number of the partition on which /etc/delo.conf resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2572 +#: using-d-i.xml:2571 #, no-c-format msgid "name" msgstr "" #. Tag: para -#: using-d-i.xml:2573 +#: using-d-i.xml:2572 #, no-c-format msgid "is the name of the configuration entry in /etc/delo.conf, which is linux by default." msgstr "" #. Tag: para -#: using-d-i.xml:2583 +#: using-d-i.xml:2582 #, no-c-format msgid "In case /etc/delo.conf 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:2589 +#: using-d-i.xml:2588 #, no-c-format msgid "boot #/rzid" msgstr "" #. Tag: title -#: using-d-i.xml:2599 +#: using-d-i.xml:2598 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2600 +#: using-d-i.xml:2599 #, no-c-format msgid "Newer (mid 1998 and on) PowerMacs use yaboot as their boot loader. The installer will set up yaboot automatically, so all you need is a small 820k partition named bootstrap with type Apple_Bootstrap 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:2618 +#: using-d-i.xml:2617 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2619 +#: using-d-i.xml:2618 #, no-c-format msgid "The boot loader for OldWorld Power Macintosh machines is quik. You can also use it on CHRP. The installer will attempt to set up quik 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:2635 +#: using-d-i.xml:2634 #, no-c-format msgid "zipl-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2636 +#: using-d-i.xml:2635 #, no-c-format msgid "The boot loader on &arch-title; is zipl. ZIPL is similar in configuration and usage to LILO, with a few exceptions. Please take a look at LINUX for &arch-title; Device Drivers and Installation Commands from IBM's developerWorks web site if you want to know more about ZIPL." msgstr "" #. Tag: title -#: using-d-i.xml:2653 +#: using-d-i.xml:2652 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2655 +#: using-d-i.xml:2654 #, no-c-format msgid "The standard &architecture; boot loader is called silo. It is documented in /usr/share/doc/silo/. SILO is similar in configuration and usage to LILO, with a few exceptions. First of all, SILO allows you to boot any kernel image on your drive, even if it is not listed in /etc/silo.conf. This is because SILO can actually read Linux partitions. Also, /etc/silo.conf is read at boot time, so there is no need to rerun silo after installing a new kernel like you would with LILO. SILO 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:2680 +#: using-d-i.xml:2679 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:2682 +#: using-d-i.xml:2681 #, 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). 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." msgstr "" #. Tag: para -#: using-d-i.xml:2691 +#: using-d-i.xml:2690 #, no-c-format msgid "If you plan to manually configure your bootloader, you should check the name of the installed kernel in /target/boot. You should also check that directory for the presence of an initrd; 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 / filesystem and, if you chose to install /boot on a separate partition, also your /boot filesystem." msgstr "" #. Tag: title -#: using-d-i.xml:2708 +#: using-d-i.xml:2707 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:2709 +#: using-d-i.xml:2708 #, 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:2721 +#: using-d-i.xml:2720 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "" #. Tag: para -#: using-d-i.xml:2723 +#: using-d-i.xml:2722 #, 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:2730 +#: using-d-i.xml:2729 #, no-c-format msgid "Select the Finish the installation 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:2744 +#: using-d-i.xml:2743 #, no-c-format msgid "Miscellaneous" msgstr "" #. Tag: para -#: using-d-i.xml:2745 +#: using-d-i.xml:2744 #, 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:2758 +#: using-d-i.xml:2757 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2759 #, no-c-format msgid "If the installation is successful, the logfiles created during the installation process will be automatically saved to /var/log/installer/ on your new Debian system." msgstr "" #. Tag: para -#: using-d-i.xml:2767 +#: using-d-i.xml:2766 #, no-c-format msgid "Choosing Save debug logs 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:2787 +#: using-d-i.xml:2786 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:2790 +#: using-d-i.xml:2789 #, no-c-format msgid "There is an Execute a Shell item on the menu. If the menu is not available when you need to use the shell, press Left Alt F2 (on a Mac keyboard, Option F2 ) to switch to the second virtual console. That's the Alt key on the left-hand side of the space bar, and the F2 function key, at the same time. This is a separate window running a Bourne shell clone called ash." msgstr "" #. Tag: para -#: using-d-i.xml:2802 +#: using-d-i.xml:2801 #, no-c-format msgid "At this point you are booted from the RAM disk, and there is a limited set of Unix utilities available for your use. You can see what programs are available with the command ls /bin /sbin /usr/bin /usr/sbin and by typing help. The text editor is nano. The shell has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:2811 +#: using-d-i.xml:2810 #, no-c-format msgid "Use the menus to perform any task that they are able to do — the shell and commands are only there in case something goes wrong. In particular, you should always use the menus, not the shell, to activate your swap partition, because the menu software can't detect that you've done this from the shell. Press Left Alt F1 to get back to menus, or type exit if you used a menu item to open the shell." msgstr "" #. Tag: title -#: using-d-i.xml:2830 +#: using-d-i.xml:2829 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:2832 +#: using-d-i.xml:2831 #, no-c-format msgid "One of the more interesting components is network-console. 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 .)" msgstr "" #. Tag: para -#: using-d-i.xml:2842 +#: using-d-i.xml:2841 #, 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 Load installer components from CD and from the list of additional components select network-console: Continue installation remotely using SSH. Successful load is indicated by a new menu entry called Continue installation remotely using SSH." msgstr "" #. Tag: para -#: using-d-i.xml:2855 +#: using-d-i.xml:2854 #, 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:2860 +#: using-d-i.xml:2859 #, no-c-format msgid "After selecting this new entry, you You 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 installer 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 person who will continue the installation remotely." msgstr "" #. Tag: para -#: using-d-i.xml:2872 +#: using-d-i.xml:2871 #, 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:2878 +#: using-d-i.xml:2877 #, 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: \n" @@ -2284,25 +2284,25 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2895 +#: using-d-i.xml:2894 #, no-c-format msgid "If you install several computers in turn and they happen to have the same IP address or hostname, ssh 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 ~/.ssh/known_hosts and try again." msgstr "" #. Tag: para -#: using-d-i.xml:2904 +#: using-d-i.xml:2903 #, no-c-format msgid "After the login you will be presented with an initial screen where you have two possibilities called Start menu and Start shell. 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:2914 +#: using-d-i.xml:2913 #, 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:2922 +#: using-d-i.xml:2921 #, 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/pt/boot-installer.po b/po/pt/boot-installer.po index 25165006a..0e435270c 100644 --- a/po/pt/boot-installer.po +++ b/po/pt/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-12-12 22:48+0000\n" "Last-Translator: Miguel Figueiredo \n" "Language-Team: Portuguese \n" @@ -14,4100 +14,5241 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#~ msgid "Booting the Installation System" -#~ msgstr "Iniciar a Instalação do sistema" - -#~ msgid "Booting the Installer on &arch-title;" -#~ msgstr "Iniciar o Instalador em &arch-title;" - -#~ msgid "Alpha Console Firmware" -#~ msgstr "Consola de Firmware Alpha" - -#~ 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 "" -#~ "A consola de firmware está guardada numa flash ROM e é iniciada quando um " -#~ "sistema Alpha é ligado ou reiniciado. Existem duas especificações " -#~ "diferentes de consolas utilizadas em sistemas Alpha, e assim, duas " -#~ "classes de consolas de firmware disponíveis." - -#~ msgid "" -#~ "SRM console, based on the Alpha Console Subsystem " -#~ "specification, which provides an operating environment for OpenVMS, Tru64 " -#~ "UNIX, and Linux operating systems." -#~ msgstr "" -#~ "As consolas SRM, baseadas na especificação do Alpha " -#~ "Console Subsystem, que disponibiliza um ambiente operacional para " -#~ "sistemas operativos OpenVMS, Tru64, UNIX e Linux." - -#~ msgid "" -#~ "ARC, AlphaBIOS, or ARCSBIOS console, based on the " -#~ "Advanced RISC Computing (ARC) specification, which provides an operating " -#~ "environment for Windows NT." -#~ msgstr "" -#~ "As consolas ARC, AlphaBIOS, ou ARCSBIOS, baseadas na " -#~ "especificação Advanced RISC Computing (ARC), que providencia um ambiente " -#~ "operacional para Windows NT." - -#~ 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 "" -#~ "Da perspectiva do utilizador, a diferença mais importante entre SRM e ARC " -#~ "é que a escolha da consola restringe o possível esquema de partição do " -#~ "disco a partir do qual deseja arrancar." - -#~ msgid "" -#~ "ARC requires that you use an MS-DOS partition table (as created by " -#~ "cfdisk) for the boot disk. Therefore MS-DOS partition " -#~ "tables are the native 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 "" -#~ "ARC requer que utilize uma tabela de partições MS-DOS (como as criadas " -#~ "pelo cfdisk) para o disco de arranque. Assim, as " -#~ "tabelas de partições MS-DOS são do formato nativo quando " -#~ "se arranca a partir de ARC. De facto, como o AlphaBIOS contém um " -#~ "utilitário de particionamento de disco, você poderá preferir particionar " -#~ "os seus discos a partir dos menus do firmware, antes de instalar Linux." - -#~ msgid "" -#~ "Conversely, SRM is incompatible " -#~ "Specifically, the bootsector format required by the Console Subsystem " -#~ "Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " -#~ "BSD disklabel format, this is the native partition format " -#~ "for SRM installations." -#~ msgstr "" -#~ "Inversamente, SRM é incompatível " -#~ "Especificamente, o formato do sector de boot necessário pela Console " -#~ "Subsystem Specification entra em conflito com a colocação da tabela de " -#~ "partições do DOS. com as tabelas de partições MS-DOS. " -#~ "Como o Tru64 Unix utiliza o formato disklabel BSD, este é o formato de " -#~ "partição nativo para instalações SRM." - -#~ 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 "" -#~ "GNU/Linux é o único sistema operativo em Alpha que pode ser iniciado a " -#~ "partir de ambos os tipos de consola, mas &debian; &release; apenas " -#~ "suporta arranque em sistemas baseados em SRM (SRM-based). Se tem um Alpha " -#~ "para o qual nenhuma versão de SRM está disponível, se irá fazer dual-boot " -#~ "do sistema com Windows NT, ou se o seu periférico de boot requer suporte " -#~ "para uma consola ARC para inicialização por BIOS, não lhe irá ser " -#~ "possível correr o instalador de &debian; &release;. Será, no entanto, " -#~ "possível correr &debian; &release; em tais sistemas usando outro meio " -#~ "para instalar; por exemplo, poderá instalar o Debian woody com recurso ao " -#~ "MILO e fazendo upgrade." - -#~ msgid "" -#~ "Because MILO 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 "" -#~ "Uma vez que o MILO não está disponível para nenhum dos " -#~ "sistemas Alpha em produção corrente (em Fevereiro de 2000), e uma vez que " -#~ "já não é necessário comprar uma licença OpenVMS ou Tru64 Unix para ter " -#~ "firmware SRM no seu antigo Alpha, é recomendado que utilize SRM quando " -#~ "possível." - -#~ msgid "" -#~ "The following table summarizes available and supported system type/" -#~ "console combinations (see for the system " -#~ "type names). The word ARC below denotes any of the ARC-" -#~ "compliant consoles." -#~ msgstr "" -#~ "A tabela seguinte sumariza as combinações disponíveis e suportadas do " -#~ "tipo de sistema/consola (ver a para os " -#~ "nomes dos tipos de sistema). A palavra ARC abaixo denota " -#~ "qualquer das consolas compatíveis com ARC." - -#~ msgid "System Type" -#~ msgstr "Tipo de Sistema" +#. Tag: title +#: boot-installer.xml:4 +#, no-c-format +msgid "Booting the Installation System" +msgstr "Iniciar a Instalação do sistema" + +#. Tag: title +#: boot-installer.xml:9 +#, no-c-format +msgid "Booting the Installer on &arch-title;" +msgstr "Iniciar o Instalador em &arch-title;" + +#. Tag: title +#: boot-installer.xml:20 +#, no-c-format +msgid "Alpha Console Firmware" +msgstr "Consola de Firmware Alpha" + +#. 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 "" +"A consola de firmware está guardada numa flash ROM e é iniciada quando um " +"sistema Alpha é ligado ou reiniciado. Existem duas especificações diferentes " +"de consolas utilizadas em sistemas Alpha, e assim, duas classes de consolas " +"de firmware disponíveis." + +#. Tag: para +#: boot-installer.xml:31 +#, no-c-format +msgid "" +"SRM console, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." +msgstr "" +"As consolas SRM, baseadas na especificação do Alpha " +"Console Subsystem, que disponibiliza um ambiente operacional para sistemas " +"operativos OpenVMS, Tru64, UNIX e Linux." -#~ msgid "Console Type Supported" -#~ msgstr "Tipo de Consola Suportada" +#. Tag: para +#: boot-installer.xml:38 +#, no-c-format +msgid "" +"ARC, AlphaBIOS, or ARCSBIOS console, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." +msgstr "" +"As consolas ARC, AlphaBIOS, ou ARCSBIOS, baseadas na " +"especificação Advanced RISC Computing (ARC), que providencia um ambiente " +"operacional para Windows NT." -#~ msgid "alcor" -#~ msgstr "alcor" +#. 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 "" +"Da perspectiva do utilizador, a diferença mais importante entre SRM e ARC é " +"que a escolha da consola restringe o possível esquema de partição do disco a " +"partir do qual deseja arrancar." -#~ msgid "ARC or SRM" -#~ msgstr "ARC ou SRM" +#. Tag: para +#: boot-installer.xml:54 +#, no-c-format +msgid "" +"ARC requires that you use an MS-DOS partition table (as created by " +"cfdisk) for the boot disk. Therefore MS-DOS partition " +"tables are the native 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 "" +"ARC requer que utilize uma tabela de partições MS-DOS (como as criadas pelo " +"cfdisk) para o disco de arranque. Assim, as tabelas de " +"partições MS-DOS são do formato nativo quando se arranca a " +"partir de ARC. De facto, como o AlphaBIOS contém um utilitário de " +"particionamento de disco, você poderá preferir particionar os seus discos a " +"partir dos menus do firmware, antes de instalar Linux." + +#. Tag: para +#: boot-installer.xml:63 +#, no-c-format +msgid "" +"Conversely, SRM is incompatible " +"Specifically, the bootsector format required by the Console Subsystem " +"Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " +"BSD disklabel format, this is the native partition format for " +"SRM installations." +msgstr "" +"Inversamente, SRM é incompatível " +"Especificamente, o formato do sector de boot necessário pela Console " +"Subsystem Specification entra em conflito com a colocação da tabela de " +"partições do DOS. com as tabelas de partições MS-DOS. " +"Como o Tru64 Unix utiliza o formato disklabel BSD, este é o formato de " +"partição nativo para instalações SRM." + +#. 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 "" +"GNU/Linux é o único sistema operativo em Alpha que pode ser iniciado a " +"partir de ambos os tipos de consola, mas &debian; &release; apenas suporta " +"arranque em sistemas baseados em SRM (SRM-based). Se tem um Alpha para o " +"qual nenhuma versão de SRM está disponível, se irá fazer dual-boot do " +"sistema com Windows NT, ou se o seu periférico de boot requer suporte para " +"uma consola ARC para inicialização por BIOS, não lhe irá ser possível correr " +"o instalador de &debian; &release;. Será, no entanto, possível correr " +"&debian; &release; em tais sistemas usando outro meio para instalar; por " +"exemplo, poderá instalar o Debian woody com recurso ao MILO e fazendo " +"upgrade." + +#. Tag: para +#: boot-installer.xml:87 +#, no-c-format +msgid "" +"Because MILO 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 "" +"Uma vez que o MILO não está disponível para nenhum dos " +"sistemas Alpha em produção corrente (em Fevereiro de 2000), e uma vez que já " +"não é necessário comprar uma licença OpenVMS ou Tru64 Unix para ter firmware " +"SRM no seu antigo Alpha, é recomendado que utilize SRM quando possível." + +#. Tag: para +#: boot-installer.xml:95 +#, no-c-format +msgid "" +"The following table summarizes available and supported system type/console " +"combinations (see for the system type names). " +"The word ARC below denotes any of the ARC-compliant consoles." +msgstr "" +"A tabela seguinte sumariza as combinações disponíveis e suportadas do tipo " +"de sistema/consola (ver a para os nomes dos " +"tipos de sistema). A palavra ARC abaixo denota qualquer das " +"consolas compatíveis com ARC." + +#. Tag: entry +#: boot-installer.xml:107 +#, no-c-format +msgid "System Type" +msgstr "Tipo de Sistema" + +#. Tag: entry +#: boot-installer.xml:108 +#, no-c-format +msgid "Console Type Supported" +msgstr "Tipo de Consola Suportada" + +#. Tag: entry +#: boot-installer.xml:114 +#, no-c-format +msgid "alcor" +msgstr "alcor" + +#. 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 "ARC ou SRM" + +#. Tag: entry +#: boot-installer.xml:117 +#, no-c-format +msgid "avanti" +msgstr "avanti" + +#. Tag: entry +#: boot-installer.xml:120 +#, no-c-format +msgid "book1" +msgstr "book1" + +#. 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 "só SRM" + +#. Tag: entry +#: boot-installer.xml:123 +#, no-c-format +msgid "cabriolet" +msgstr "cabriolet" + +#. Tag: entry +#: boot-installer.xml:126 +#, no-c-format +msgid "dp264" +msgstr "dp264" + +#. Tag: entry +#: boot-installer.xml:129 +#, no-c-format +msgid "eb164" +msgstr "eb164" + +#. Tag: entry +#: boot-installer.xml:132 +#, no-c-format +msgid "eb64p" +msgstr "eb64p" + +#. Tag: entry +#: boot-installer.xml:135 +#, no-c-format +msgid "eb66" +msgstr "eb66" + +#. Tag: entry +#: boot-installer.xml:138 +#, no-c-format +msgid "eb66p" +msgstr "eb66p" + +#. Tag: entry +#: boot-installer.xml:141 +#, no-c-format +msgid "jensen" +msgstr "jensen" + +#. Tag: entry +#: boot-installer.xml:144 +#, no-c-format +msgid "lx164" +msgstr "lx164" + +#. Tag: entry +#: boot-installer.xml:147 +#, no-c-format +msgid "miata" +msgstr "miata" + +#. Tag: entry +#: boot-installer.xml:150 +#, no-c-format +msgid "mikasa" +msgstr "mikasa" + +#. Tag: entry +#: boot-installer.xml:153 +#, no-c-format +msgid "mikasa-p" +msgstr "mikasa-p" + +#. Tag: entry +#: boot-installer.xml:156 +#, no-c-format +msgid "nautilus" +msgstr "nautilus" + +#. Tag: entry +#: boot-installer.xml:157 +#, no-c-format +msgid "ARC (see motherboard manual) or SRM" +msgstr "ARC (veja o manual da motherboard) ou SRM" + +#. Tag: entry +#: boot-installer.xml:159 +#, no-c-format +msgid "noname" +msgstr "noname" + +#. Tag: entry +#: boot-installer.xml:162 +#, no-c-format +msgid "noritake" +msgstr "noritake" + +#. Tag: entry +#: boot-installer.xml:165 +#, no-c-format +msgid "noritake-p" +msgstr "noritake-p" + +#. Tag: entry +#: boot-installer.xml:168 +#, no-c-format +msgid "pc164" +msgstr "pc164" + +#. Tag: entry +#: boot-installer.xml:171 +#, no-c-format +msgid "rawhide" +msgstr "rawhide" + +#. Tag: entry +#: boot-installer.xml:174 +#, no-c-format +msgid "ruffian" +msgstr "ruffian" + +#. Tag: entry +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#, no-c-format +msgid "ARC only" +msgstr "só ARC" + +#. Tag: entry +#: boot-installer.xml:177 +#, no-c-format +msgid "sable" +msgstr "sable" + +#. Tag: entry +#: boot-installer.xml:180 +#, no-c-format +msgid "sable-g" +msgstr "sable-g" + +#. Tag: entry +#: boot-installer.xml:183 +#, no-c-format +msgid "sx164" +msgstr "sx164" + +#. Tag: entry +#: boot-installer.xml:186 +#, no-c-format +msgid "takara" +msgstr "takara" + +#. Tag: entry +#: boot-installer.xml:189 +#, no-c-format +msgid "xl" +msgstr "xl" + +#. Tag: entry +#: boot-installer.xml:192 +#, no-c-format +msgid "xlt" +msgstr "xlt" + +#. 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, " +"aboot, a small, platform-independent bootloader, is used. " +"See the (unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"Geralmente, nenhuma destas consolas pode iniciar o Linux directamente, " +"portanto é necessária a assistência de um gestor de arranque. Para a consola " +"SRM, é usado o aboot, um gestor de arranque pequeno e " +"independente da plataforma usada. Ver o (infelizmente desactualizado) SRM HOWTO para mais informações acerca do " +"aboot." + +#. 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 "" +"Os parágrafos seguintes são referentes ao manual de instalação do woody, e " +"são aqui incluídos para referência; podem vir a ser úteis mais à frente, " +"quando o Debian voltar a suportar instalações baseadas em MILO." -#~ msgid "avanti" -#~ msgstr "avanti" +#. 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: MILO and aboot." +msgstr "" +"Geralmente, nenhuma destas consolas pode arrancar o Linux directamente, " +"portanto é necessário o recurso a um gestor de arranque intermediário. Há " +"dois gestores de arranque de Linux muito populares: MILO " +"e aboot." + +#. Tag: para +#: boot-installer.xml:221 +#, no-c-format +msgid "" +"MILO is itself a console, which replaces ARC or SRM in " +"memory. MILO can be booted from both ARC and SRM and is " +"the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) " +"MILO HOWTO." +msgstr "" +"MILO é em si mesmo uma consola, que substitui a ARC ou a " +"SRM em memória. MILO pode ser iniciado tanto a partir da " +"ARC como da SRM e é a única maneira de fazer o bootstrap a partir da consola " +"ARC. MILO é específico de uma plataforma (são necessários " +"diferentes MILO para cada tipo de sistema) e existe " +"apenas para esses sistemas, para os quais o suporte ARC é mostrado na tabela " +"acima. Ver também o (infelizmente desactualizado) MILO HOWTO." + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "" +"aboot is a small, platform-independent bootloader, which " +"runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"aboot é um pequeno e independente gestor de arranque, que " +"apenas corre a partir de SRM. Ver também o (infelizmente desactualizado) " +"SRM HOWTO para mais informação acerca " +"do aboot." + +#. 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 MILO is available: " +"\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Because MILO 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 aboot on new installations of GNU/Linux, " +"unless you wish to dual-boot with Windows NT." +msgstr "" +"Assim, três cenários são normalmente possíveis, dependendo da consola do " +"firmware do sistema e se o MILO está ou não disponível: " +"\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Como MILO não está disponível " +"para nenhum dos sistemas Alpha correntemente em produção (em Fevereiro de " +"2000), e porque não é mais necessário comprar uma licença Unix OpenVMS ou " +"Tru64 para ter firmware SRM no seu Alpha mais antigo, é recomendado que use " +"SRM e aboot nas novas instalações de GNU/Linux, a não ser " +"que deseje fazer dual-boot com Windows NT." + +#. 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 half-flash 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 arc command). For the reasons mentioned above, " +"we recommend switching to SRM before installing &debian;." +msgstr "" +"A maioria dos AlphaServers e todos os produtos actuais para servidores e " +"estações de trabalho contém tanto SRM como AlphaBIOS no seu firmware. Para " +"máquinas half-flash tais como as várias placas de avaliação, " +"é possível mudar de uma versão para outra apenas fazendo novamente o flash " +"ao firmware. Além disso, uma vez o SRM esteja instalado, é possível correr o " +"ARC/AlphaBIOS a partir de uma disquete (usando o comando arc). Pelas razões mencionadas acima, nós recomendamos que mude para " +"SRM antes de instalar &debian;." + +#. Tag: para +#: boot-installer.xml:264 +#, no-c-format +msgid "" +"As on other architectures, you should install the newest available revision " +"of the firmware Except on Jensen, where Linux is not " +"supported on firmware versions newer than 1.7 — see for more information. before " +"installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." +msgstr "" +"Assim como noutras arquitecturas, deverá instalar a revisão de firmware mais " +"recente Excepto em Jensen, onde o Linux não é suportado nas " +"versões superiores a 1.7 — ver para mais informação. antes de instalar &debian;. " +"Para Alpha, os updates de firmware podem ser obtidos a partir de Alpha Firmware Updates ." + +#. Tag: title +#: boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 +#: boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 +#: boot-installer.xml:2500 boot-installer.xml:2596 +#, no-c-format +msgid "Booting with TFTP" +msgstr "Iniciar com TFTP" + +#. Tag: para +#: boot-installer.xml:284 +#, no-c-format +msgid "" +"In SRM, Ethernet interfaces are named with the ewa " +"prefix, and will be listed in the output of the show dev command, like this (edited slightly): \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" +" You first need to set the boot protocol: " +"\n" +">>> set ewa0_protocols bootp\n" +" Then check the medium type is correct: " +"\n" +">>> set ewa0_mode mode\n" +" You can get a listing of valid modes with " +">>>set ewa0_mode." +msgstr "" +"Em SRM, as interfaces Ethernet são nomeados com o prefixo ewa, e serão listados na saída do comando show dev, tal como se mostra em seguida (ligeiramente editado): " +"\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" +" Primeiro, necessita de estabelecer o protocolo " +"de arranque: \n" +">>> set ewa0_protocol bootp\n" +"De seguida verificar se o tipo de media é " +"correcto:\n" +">>> set ewa0_mode mode\n" +"Pode obter uma lista dos modos válidos através de " +">>>set ewa0_mode." + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "" +"Then, to boot from the first Ethernet interface, you would type: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" This will boot using the default kernel " +"parameters as included in the netboot image." +msgstr "" +"Depois, para iniciar a primeira interface de Ethernet, deverá digitar: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" Isto irá iniciar os parâmetros de kernel pré-" +"definidos, como foram incluídos na imagem netboot." + +#. Tag: para +#: boot-installer.xml:311 +#, no-c-format +msgid "" +"If you wish to use a serial console, you must pass the " +"console= parameter to the kernel. This can be done " +"using the -flags argument to the SRM boot command. The serial ports are named the same as their " +"corresponding files in /dev. 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 ewa0 and use a console on the first serial port, you would type:" +msgstr "" +"Se deseja usar a consola de série, tem de passar o " +"parâmetro console= para o kernel. Isto pode ser feito " +"usado o argumento -flags para o comando " +"boot do SRM.As portas série são nomeadas da mesma " +"maneira que o seu correspondente em ficheiros em /dev. Também, quando especificar parâmetros de kernel adicionais, terá " +"de repetir certas opções pré-definias que são necessárias pelas imagens do " +"&d-i;. Por exemplo, para arrancar a partir de ewa0 e " +"usar uma consola na primeira porta série, deverá digitar:" + +#. Tag: screen +#: boot-installer.xml:323 +#, no-c-format +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" + +#. Tag: title +#: boot-installer.xml:328 +#, no-c-format +msgid "Booting from CD-ROM with the SRM Console" +msgstr "Iniciar a partir de CD-ROM com a Consola SRM" + +#. Tag: para +#: boot-installer.xml:329 +#, no-c-format +msgid "" +"Type \n" +">>> boot xxxx -flags 0\n" +" where xxxx is your CD-" +"ROM drive in SRM notation." +msgstr "" +"Escreva \n" +">>> boot xxxx -flags 0\n" +"onde xxxx é a sua " +"drive de CD-ROM na notação SRM." + +#. Tag: title +#: boot-installer.xml:341 +#, no-c-format +msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" +msgstr "Iniciar a partir de CD-ROM com a Consola ARC ou AlphaBIOS" + +#. 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 ), then enter \\milo\\linload." +"exe as the boot loader and \\milo" +"\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS " +"Selection Setup' menu. Ruffians make an exception: You need to use " +"\\milo\\ldmilo.exe as boot loader." +msgstr "" +"Para iniciar um CD-ROM a partir da consola ARC, encontre o nome de código da " +"sua sub-arquitectura (veja a ), seguidamente " +"insira \\milo\\linload.exe como gestor de arranque e " +"\\milo\\subarch (onde " +"subarch é o nome correcto da sub-arquitectura) " +"como o caminho do SO no menu `OS Selection Setup'. Ruffians são as " +"excepções: necessita do \\milo\\ldmilo.exe como gestor " +"de arranque." + +#. Tag: title +#: boot-installer.xml:358 +#, no-c-format +msgid "Booting from Floppies with the SRM Console" +msgstr "Iniciar a partir de Disquetes com a Consola SRM" + +#. Tag: para +#: boot-installer.xml:359 +#, no-c-format +msgid "" +"At the SRM prompt (>>>), issue the following " +"command: \n" +">>> boot dva0 -flags 0\n" +" possibly replacing dva0 " +"with the actual device name. Usually, dva0 is the " +"floppy; type \n" +">>> show dev\n" +" to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. If everything works OK, you will eventually see the Linux kernel " +"boot." +msgstr "" +"Na prompt da SRM (>>>), digite o seguinte comando: " +"\n" +">>> boot dva0 -flags 0\n" +" possivelmente substituindo dva0 pelo nome do dispositivo correcto. Normalmente, dva0 é a disquete; digite \n" +">>> show dev\n" +" para ver a lista de dispositivos (e.g, se quer " +"iniciar a partir de um CD). Note que se está a arrancar via MILO, o " +"argumento -flags é ignorado, para que possa apenas " +"digitar boot dva0. Se tudo estiver OK, irá eventualmente " +"ver o arranque do kernel Linux." + +#. Tag: para +#: boot-installer.xml:376 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via aboot, use the following command: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (typed on one line), substituting, if necessary, " +"the actual SRM boot device name for dva0, the Linux " +"boot device name for fd0, and the desired kernel " +"parameters for arguments." +msgstr "" +"Se desejar especificar os parâmetros do kernel quando iniciado via " +"aboot, use o seguinte comando:\n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (escrito numa linha), substituindo, se " +"necessário, o nome do dispositivo actual de boot SRM para dva0, o nome do dispositivo de arranque do Linux para fd0, e os parâmetros desejados para o kernel para arguments." + +#. Tag: para +#: boot-installer.xml:388 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See " +"." +msgstr "" +"Se desejar especificar os parâmetros do kernel quando iniciar via " +"MILO, terá de interromper o bootstrap mal chegue ao MILO. " +"veja a ." + +#. Tag: title +#: boot-installer.xml:398 +#, no-c-format +msgid "Booting from Floppies with the ARC or AlphaBIOS Console" +msgstr "Iniciar a partir de Disquetes com a Consola ARC ou AlphaBIOS" + +#. Tag: para +#: boot-installer.xml:400 +#, no-c-format +msgid "" +"In the OS Selection menu, set linload.exe as the boot " +"loader, and milo as the OS Path. Bootstrap using the " +"newly created entry." +msgstr "" +"No menu de selecção do SO, defina linload.exe como o " +"gestor de arranque, e milo como o OS Path. Faça o " +"bootstrap usando a entrada recentemente criada." + +#. Tag: title +#: boot-installer.xml:409 +#, no-c-format +msgid "Booting with MILO" +msgstr "Iniciar com o MILO" + +#. 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 "" +"O MILO contido na bootstrap media está configurado automaticamente para " +"proceder automaticamente para Linux. Caso deseje intervir, tudo o que " +"necessita fazer é pressionar a tecla de espaço durante a contagem " +"decrescente do MILO." + +#. 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: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Se deseja especificar todos os bits explicitamente (por exemplo, para " +"fornecer parâmetros adicionais), poderá usar um comando como o seguinte: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" Se está a fazer o arranque a partir de algo que " +"não seja uma disquete, substitua fd0 no exemplo acima, " +"pelo nome do dispositivo apropriado, na notação Linux. O comando " +"help dar-lhe-á uma breve referência do comando MILO." + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "Iniciar com TFTP" + +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"Iniciar pela rede, requer que tenha uma ligação de rede configurada e um " +"servidor de arranque de rede TFTP (DHCP, RARP ou BOOTP)." -#~ msgid "book1" -#~ msgstr "book1" +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"Sistemas mais antigos como o 715 poderão necessitar do uso de um servidor " +"RBOOT em vez de um servidor BOOTP." -#~ msgid "SRM only" -#~ msgstr "só SRM" +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "" +"O método de instalação para suportar o arranque pela rede é descrito na " +"." + +#. Tag: title +#: boot-installer.xml:459 +#, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "Iniciar a partir de TFTP em NetWinder" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" +"Os Netwinder têm dois interfaces de rede: uma placa compatível com NE2000 a " +"10Mbps (que é normalmente referenciada como eth0 e uma " +"placa Tulip a 100Mbps. Poderá haver problemas em carregar a imagem via TFTP " +"utilizando a placa a 100Mbps por isso é recomendado que utilize o interface " +"a 10Mbps (a que está identiticada como 10 Base-T)." + +#. 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 ." +msgstr "" +"Necessita do NeTTrom 2.2.1 ou posterior para arrancar o sistema de " +"instalação, é recomendada a versão 2.3.3. Infelizmente, os ficheiros de " +"firmware actualmente não estão disponíveis para download por razões de " +"licenciamento. Se esta situação se modificar, poderá encontrar as novas " +"imagens " + +#. 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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" +"Quando arrancar o seu Netwinder você tem de interromper o processo de " +"arranque durante a contagem decrescente. Isto permite-lhe definir uma série " +"de configurações de firmware necessárias para arrancar com o instalador. Em " +"primeiro lugar, começe por carregar as configurações de omissão: " +"\n" +" NeTTrom command-> load-defaults\n" +" De seguida, tem de configurar a rede, quer com " +"endereço estático: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" onde 24 é número de set bits na netmask, ou um " +"endereço dinâmico: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +"Se o servidor de TFTP não estiver na subrede " +"local pode também necessitar de configurar as configurações " +"route1, tem de especificar o servidor TFTP e a " +"localização da imagem. Depois pode guardar as suas configurações para a " +"flash.\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Agora tem de dizer ao firmware que a imagem TFTP " +"tem de ser iniciada:\n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" Se utilizar uma consola série para instalar o " +"seu Netwinder, tem de adicionar a seguinte configuração: " +"\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Em alternativa, para instalações com um teclado " +"e monitor tem de definir: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" Pode utilizar o comando printenv para rever as suas configurações. Depois de ter verificado que as " +"configurações estão correctas, pode carregar a imagem: " +"\n" +" NeTTrom command-> boot\n" +" No caso de ter algum problema, está disponível " +"um HOWTO " +"detalhado" + +#. Tag: title +#: boot-installer.xml:529 +#, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "Iniciar a partir de TFTP em CATS" + +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"Em máquinas CATS, use o comando boot de0: ou similar na " +"prompt Cyclone." + +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "Iniciar a partir de CD-ROM" + +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"O melhor caminho para a maioria das pessoas será usar um conjunto de CDs " +"Debian. Se tem um conjunto de CDs, e se a sua máquina suporta arranque " +"directamente a partir do CD, fantástico! Simplesmente " +"configure o seu sistema para arrancar a partir de um CD como descrito na " +", insira o seu CD, reinicie, e " +"proceda para o próximo capítulo." + +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"Note que determinadas drives de CD podem necessitar de drivers especiais, e " +"portanto estarem inacessíveis nas fases iniciais da instalação. Se se " +"verificar que a maneira comum de iniciar a partir do CD não funciona no seu " +"hardware, visite novamente este capítulo e leia sobre métodos alternativos " +"para instalar e kernels alternativos que poderão funcionar consigo." + +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"Mesmo se não conseguir iniciar a partir do CD-ROM, poderá provavelmente " +"instalar os componentes do Debian e qualquer pacote que deseje a partir do " +"CD-ROM. Simplesmente arranque utilizando uma media diferente, tal como " +"disquetes. Quanto for altura de instalar o sistema operativo, sistema base, " +"e qualquer pacote adicional, aponte o sistema de instalação para a drive de " +"CD-ROM." + +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"Se tiver problemas com o arranque, veja a ." -#~ msgid "cabriolet" -#~ msgstr "cabriolet" +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"Para iniciar de um CD-ROM a partir da prompt da consola Cyclone, use o " +"comando boot cd0:cats.bin" + +#. Tag: title +#: boot-installer.xml:589 +#, no-c-format +msgid "Booting from Firmware" +msgstr "Arrancar a partir de Firmware" + +#. 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 "" +"Existe um número cada vez maior de dispositivos para os consumidores que " +"arrancam directamente a partir de um chip flash no dispositivo. O instalador " +"pode ser escrito para flash de modo a que arranque automaticamente quando " +"reiniciar as suas máquinas." + +#. 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 "" +"em muitos casos, mudar o firmware de um dispositivo embebido inutiliza a sua " +"garantia. Por vezes nem sequer consegue recuperar o seu dispositivo se " +"ocorrerem problemas durante o processo de flash. Por isso, tenha cuidado e " +"siga os passos com cuidado." + +#. Tag: title +#: boot-installer.xml:612 +#, no-c-format +msgid "Booting the NSLU2" +msgstr "Arrancar o NSLU2" + +#. Tag: para +#: boot-installer.xml:613 +#, no-c-format +msgid "There are three ways how to put the installer firmware into flash:" +msgstr "Existem três formas de colocar o firmware do instalador em flash:" + +#. Tag: title +#: boot-installer.xml:619 +#, no-c-format +msgid "Using the NSLU2 web interface" +msgstr "Utilizando o interface web NSLU2" + +#. Tag: para +#: boot-installer.xml:620 +#, no-c-format +msgid "" +"Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." +msgstr "" +"Vá à secção de administração e escolha o item do menu Upgrade. Depois pode navegar pelo seu disco à procura da imagem do " +"instalador de que fez download anteriormente. Depois carregue no botão " +"Start Upgrade, confirme, espere alguns minutos e confirme " +"novamente. Então o sistema irá arrancar directo para o instalador." + +#. Tag: title +#: boot-installer.xml:631 +#, no-c-format +msgid "Via the network using Linux/Unix" +msgstr "Através da rede utilizando Linux/Unix" + +#. Tag: para +#: boot-installer.xml:632 +#, no-c-format +msgid "" +"You can use upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 "" +"Pode utilizar upslug2 a partir de qualquer máquina Linux " +"ou Unix para actualizar a máquina a partir da rede. Este software está " +"empacotado em Debian. Primeiro, tem de colocar o seu NLSU2 em modo de " +"upgrade: Desligar quaisquer discos e/ou " +"dispositivos das portas USB. Desligar o " +"NSLU2 Carregar e manter pressionado o " +"botão de reset (acessível através de um pequeno buraco atrás, mesmo acima da " +"entrada para alimentação). Carregue e " +"largue o botão de ligar para ligar o NSLU2. " +"Espere 10 segundos olhando para o LED ready/status. Após 10 " +"segundos mudará de âmbar para vermelho. Solte imediatamente o botão de " +"reset. O LED ready/status irá piscar " +"alternanado vermelho/verde (existe uma espera de 1 segundo antes do primeiro " +"verde). O NLSU2 está agora em modo de actualização. Se tiver problemas com isto veja as páginas Linux-NSLU2. " +"Uma vez estando o NLSU2 em modo de actualização, pode flashar a nova imagem: " +"\n" +"sudo upslug2 -i di-nslu2.bin\n" +" Note que a ferramenta também mostra o endereço " +"MAC da seu NSLU2, que pode ser útil para configurar o seu servidor DHCP. " +"Após toda a imagem estar escrita e verificada, o sistema irá reiniciar " +"automaticamente. Assegure-se que liga novamente o seu disco USB, caso " +"contrário o instalador não conseguirá encontra-lo." + +#. Tag: title +#: boot-installer.xml:693 +#, no-c-format +msgid "Via the network using Windows" +msgstr "Através da rede utilizando Windows" + +#. Tag: para +#: boot-installer.xml:694 +#, no-c-format +msgid "" +"There is a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" +"Para Windows existe uma ferramenta para " +"actualizar o firmware via rede." + +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "Iniciar a partir de CD-ROM" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "" +"Iniciar a partir de Linux utilizando o lilo ou o " +"GRUB" -#~ msgid "dp264" -#~ msgstr "dp264" +#. 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 ." +msgstr "" +"Para arrancar o instalador a partir do disco rígido, terá primeiro de fazer " +"o download e colocar os ficheiros necessários, como descrito na ." -#~ msgid "eb164" -#~ msgstr "eb164" +#. 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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"Se tenciona usar o disco rígido para arrancar e depois fazer o download de " +"tudo através da rede, deverá fazer o download do ficheiro netboot/" +"debian-installer/i386/initrd.gz e do correspondente kernel " +"netboot/debian-installer/i386/linux. Isto permitir-lhe-" +"á reparticionar o disco rígido a partir do qual o instalador inicia, " +"portanto você deverá fazer isto com bastante cuidado." + +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"Em alternativa, se pretende manter uma partição, existente no disco rígido, " +"inalterada durante a instalação, poderá fazer o download do ficheiro " +"hd-media/initrd.gz e do seu kernel, assim como uma " +"copia do iso de CD para a drive (garanta que o ficheiro tem o nome que " +"termine em .iso). O instalador poderá então arrancar a " +"partir da drive e instalar a partir da imagem do CD, sem necessitar da rede." + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"Para o LILO, necessitará de configurar 2 coisas " +"essenciais em /etc/lilo.conf: " +" para carregar o instalador do initrd.gz em tempo de arranque; ter o " +"kernel vmlinuz a usar uma RAM disk como partição de " +"root. Aqui está um exemplo do /" +"etc/lilo.conf:" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"Para mais detalhes, veja as páginas do man " +"initrd 4 e lilo.conf 5. Agora execute " +"lilo e reinicie." + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"O procedimento para o GRUB é bastante semelhante. " +"Localize o seu menu.lst no directório /boot/" +"grub/ (por vezes em /boot/boot/grub/), e " +"adicione as seguintes linhas: \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" +" e reinicie." + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"Note que para o valor de ramdisk_size poderá " +"necessitar de ser ajustado para o tamanho da imagem do initrd. A partir " +"daqui, não deverá haver diferenças entre o GRUB ou o " +"LILO." + +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "Iniciar a partir de um Stick de Memória USB" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +"Vamos assumir que tem tudo preparado a partir na e da . Agora basta ligar a sua " +"pen USB em algum dos conectores USB e reiniciar o computador. O sistema " +"deverá arrancar e você deverá ser presenteado com a linha de comandos " +"boot:. Aqui poderá introduzir argumentos de arranque " +"opcionais, ou então simplesmente pressionar &enterkey;." + +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "Iniciar a partir de Disquetes" + +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"Poderá já ter feito download das imagens das disquete que necessita e ter " +"criado as disquetes a partir das imagens na ." -#~ msgid "eb64p" -#~ msgstr "eb64p" +#. Tag: para +#: boot-installer.xml:949 +#, 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 "" +"Para arrancar a partir da disquete de arranque do instalador, coloque a " +"disquete na drive de disquetes primária, desligue o sistema como faria " +"normalmente, e de seguida lige-o outra vez." -#~ msgid "eb66" -#~ msgstr "eb66" +#. Tag: para +#: boot-installer.xml:955 +#, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"Para instalar a partir de uma drive LS-120 (versão ATAPI) com um conjunto de " +"disquetes, necessita de especificar a localização virtual para o dispositivo " +"de disquetes. Isto é feito com o argumento de arranque root=, dando o dispositivo para onde o driver ide-floppy mapeia o " +"dispositivo. Por exemplo, se a sua drive LS-120 está conectada no primeiro " +"dispositivo IDE (master) no segundo cabo, deverá introduzir linux " +"root=/dev/hdc na linha de comandos de arranque." + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"Note que em algumas máquinas, Control " +"Alt Delete não faz reset à " +"máquina portanto é recomendado um hard reboot. Se está a " +"instalar a partir de um sistema operativo já existente (p.e., a partir de " +"uma máquina com DOS) não terá escolha. Caso contrário, por favor, faça um " +"hard reboot quando arrancar." + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"A disquete irá ser acedida e deverá ver um ecrã que introduz a disquete de " +"arranque e acaba com a prompt boot:." -#~ msgid "eb66p" -#~ msgstr "eb66p" +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"Uma vez pressionado &enterkey; deverá ver a mensagem " +"Loading..., seguida de " +"Uncompressing Linux..., e depois um ecrã de " +"informação sobre o hardware no seu sistema. Mais informação deste passo do " +"processo de arranque pode ser encontrada na ." + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"Após arrancar a partir da disquete de arranque, a disquete de root é pedida. " +"Insira a disquete root e pressione &enterkey;, e os conteúdos serão " +"carregados para a memória. O programa instalador debian-installer é lançado automaticamente." + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "Existem várias maneiras fazer um arranque TFTP em i386." + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "NIC ou Motherboards que suportam PXE" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"Pode acontecer que a sua Network Interface Card (NIC, ou placa de rede), ou " +"a sua Motherboard providencie a funcionalidade de arranque PXE. Isto é uma " +"re-implementação da Intel do arranque " +"TFTP. Se tal acontecer, ser-lhe-á possível configurar a sua BIOS para " +"arrancar pela rede." + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "NIC (placa de rede) com Network bootROM" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "" +"Poderá acontecer que a sua Network Interface Card (NIC, ou placa de rede), " +"providencie a funcionalidade de arranque TFTP." -#~ msgid "jensen" -#~ msgstr "jensen" +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Diga-nos(&email-debian-boot-list;) como o conseguiu fazer. " +"Por favor, refira-se a este documento." + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"O projecto etherboot " +"providencia disquetes de arranque e mesmo bootroms que fazem TFTPboot." + +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "A prompt de Arranque" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"Quando o instalador inicia, ser-lhe-á apresentado um ecrã gráfico amistoso " +"que mostra o logo de Debian e a linha de comandos de arranque: " +"\n" +"Carregue em F1 para ajuda, ou ENTER para iniciar:\n" +" Na linha de comandos de arranque você pode " +"apenas carregar em &enterkey; para iniciar o instalador com as opções por " +"omissão ou pode escrever um método de arranque específico e, opcionalmente, " +"parâmetros de arranque." + +#. Tag: para +#: boot-installer.xml:1078 +#, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"A informação dos métodos de arranque e dos parâmetros de arranque " +"disponíveis que podem ser úteis, podem ser encontrados ao pressionar desde " +"F2 até F8. Se adicionar algum parâmetro à " +"linha de comandos do arranque, garanta que escreve o método de arranque (o " +"pré-definido é linux) e um espaço antes do primeiro " +"parâmetro (e.g., linux fb=false)." + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"Se está a instalar o sistema através de um dispositivo de gestão remota que " +"disponibiliza um interface de texto na consola VGA, você pode não conseguir " +"ver o ecrã gráfico inicial quando iniciar o instalador; pode mesmo não ver a " +"linha de comandos. Exemplos destes dispositivos incluem a consola de texto " +"integrated Lights Out (iLO) da Compaq e a Integrated " +"Remote Assistant (IRA) da HP. Você pode carregar às cegas em F1 " +" Em alguns casos estes dispositivos podem necessitar de " +"sequências de escape especiais para fingir este pressionar de tecla, por " +"exemplo a IRA utiliza Ctrl F , 1. para ultrapassar " +"este ecrã e ver o texto de ajuda. Uma vez ultrapassado o ecrã inicial e " +"estando no ecrã de ajuda as suas tecla serão ecoados para a linha de " +"comandos como é de esperar. Para prevenir o instalador de utilizar o " +"framebuffer para o resto da instalação, você também vai querer adicionar à " +"linha de comandos de arranque fb=false, conforme é " +"descrito no texto de ajuda." + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "Conteúdo do CD" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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 "" +"Há três variações básicas dos CDs de Instalação Debian. O CD " +"Business Card tem a instalação mínima que irá caber nos " +"mini-CDs. Requer uma ligação à rede, por forma a instalar o resto da " +"instalação base e fazer um sistema utilizável. O CD Network " +"Install tem todos os pacotes necessários para a instalação base, " +"mas requer uma ligação à rede para um mirror Debian, por forma a instalar os " +"pacotes extra que deseje para ter um sistema Debian completo. O conjunto de " +"CDs Debian pode instalar o sistema completo a partir de uma variedade de " +"pacotes sem necessitar de aceder à rede." + +#. Tag: para +#: boot-installer.xml:1180 +#, 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 "" +"A arquitectura IA-64 usa a nova geração de Extensible Firmware Interface " +"(EFI) da Intel. Ao contrário das BIOS dos x86 tradicionais, que conhece " +"pouco acerca do dispositivo de arranque que não seja a tabela de partições e " +"o Master Boot Record (MBR), EFI pode ler e escrever ficheiros a partir de " +"partições de disco em FAT16 ou FAT32. Isto simplifica os arcaicos processos " +"de iniciar um sistema mais comuns. O sistema de arranque e o firmware EFI " +"que o suporta tem um sistema de ficheiros completo para guardar os ficheiros " +"necessários ao arranque da máquina. Isto significa que o sistema de discos " +"num sistema IA-64 tem uma partição de disco adicional dedicado ao EFI em vez " +"do simples MBR ou do bloco de arranque em sistemas mais convencionais." + +#. Tag: para +#: boot-installer.xml:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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 "" +"O Debian Installer CD contém uma partição EFI pequena, onde o gestor de " +"arranqueELILO , o seu ficheiro de configuração, o kernel " +"do instalador e o sistema de ficheiros iniciar (initrd) estão localizados. O " +"sistema em execução também contém uma partição EFI onde os ficheiros " +"necessários são lidos a partir da shell EFI descrita em baixo." + +#. Tag: para +#: boot-installer.xml:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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 "" +"A maioria dos detalhes de como o ELILO carrega e inicia " +"um sistema são transparentes para o instalador do sistema. No entanto, o " +"instalador terá de configurar uma partição EFI antes de instalar o sistema " +"base, De outra forma, a instalação do ELILO irá falhar, " +"criando um sistema incapaz de arrancar. A partição EFI está alocada e " +"formatada no passo relativo à partição da instalação anterior ao " +"carregamento de quaisquer pacotes do disco de sistema. A tarefa de " +"particionamento também verifica que uma partição EFI apropriada está " +"presente antes de autorizar a continuação da instalação." + +#. Tag: para +#: boot-installer.xml:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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 "" +"O gestor de arranque EFI está presente como o último passo da inicialização " +"do firmware. Mostra uma lista sob a forma de menu a partir da qual o " +"utilizador pode seleccionar uma opção. Dependendo do modelo do sistema e " +"qual o software carregado no sistema, este menu pode ser diferente de " +"sistema para sistema. Deverá haver pelo menos dois itens mostrados, " +"Boot Option Maintenance Menu e EFI Shell (Built-" +"in). O uso da primeira opção é preferível, no entanto, se tal " +"opção não estiver disponível ou o CD, por alguma razão não a iniciar, use a " +"segunda opção." + +#. Tag: title +#: boot-installer.xml:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "IMPORTANTE" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" +"O gestor de arranque EFI irá seleccionar uma acção de arranque por pré-" +"definição, tipicamente a primeira escolha do menu, dentro de um tempo pré-" +"determinado. Isto é indicado por uma contagem decrescente no fundo do ecrã. " +"Mal o temporizador expire e o sistema inicia a acção pré-definida, poderá " +"ter de reiniciar a máquina por forma a continuar a instalação. Se a acção " +"por omissão for a shell EFI, poderá voltar ao gesto de arranque, se executar " +"exit na prompt da shell." + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "Opção 1: Iniciar a partir do Menu de Manutenção das Opções de Arranque" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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 "" +"Insira o CD na drive CD/DVD e reinicie a máquina. O firmware irá mostrar a " +"página e menu do gestor de arranque EFI após completar o seu sistema de " +"inicialização." -#~ msgid "lx164" -#~ msgstr "lx164" +#. Tag: para +#: boot-installer.xml:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"Seleccione Boot Maintenance Menu a partir do menu, usando " +"as setas do seu teclado e pressionando ENTER. Isto irá " +"mostrar um novo menu." -#~ msgid "miata" -#~ msgstr "miata" +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" +"Seleccione Boot From a File a partir do menu, usando as " +"setas do seu teclado e pressione ENTER. Isto irá listar " +"os dispositivos testados pelo firmware. Deverá conseguir ver duas linhas do " +"menu, contendo ou a etiqueta Debian Inst [Acpi ... ou a " +"etiqueta Removable Media Boot. Se examinar o resto das " +"linhas do menu, deverá notar que a informação do dispositivo e do " +"controlador deverá ser a mesma." + +#. Tag: para +#: boot-installer.xml:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" +"Poderá escolher qualquer uma das entradas que se referem à drive de CD/DVD. " +"Seleccione a sua escolha com as setas do seu teclado e pressione " +"ENTER. Se escolher Removable Media Boot, a máquina irá imediatamente iniciar a sequência de carregamento no " +"arranque. Se em vez disso escolher Debian Inst [Acpi ..., " +"irá mostrar uma lista de directórios da parte de arranque do CD, requerendo " +"que proceda para o próximo passo (adicional)." + +#. Tag: para +#: boot-installer.xml:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" +"Apenas irá necessitar deste passo se escolher Debian Inst [Acpi ..." +". A lista de directórios irá também mostrar [Treat like " +"Removable Media Boot] ao lado da linha a seguir à última. " +"Seleccione esta linha com as setas do seu teclado e pressioneENTER. Isto irá iniciar a sequência de arranque." + +#. Tag: para +#: boot-installer.xml:1302 +#, 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 "" +"Estas etapas iniciam o gestor de arranque de Debian que irá mostrar uma " +"página de menu, para você escolher um kernel e opções para arranque. " +"Continue com a selecção do kernel e opções de arranque." + +#. Tag: title +#: boot-installer.xml:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "Opção 2: Iniciar a partir de uma Shell EFI" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" +"Se, por alguma razão, a opção 1 não for bem sucedida, reinicie a máquina e " +"quando aparecer o ecrã de EFI Boot Manager deve haver uma opção chamada " +"EFI Shell [Built-in]. Inicie o CD do Instalador Debian " +"com as seguintes etapas:" + +#. Tag: para +#: boot-installer.xml:1324 +#, 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 "" +"Insira o CD na drive de DVD/CD e reinicie a máquina. O firmware irá mostrar " +"a página do EFI Boot Manager e o menu após completar a inicialização do " +"sistema." -#~ msgid "mikasa" -#~ msgstr "mikasa" +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" +"Escolha EFI Shell a partir do menu com as teclas de setas " +"e carregue em ENTER. A EFI Shell irá procurar todos os " +"seus dispositivos de arranque e mostra-los na consola antes de mostrar a sua " +"linha de comandos. As partições de arranque reconhecidas nos dispositivos " +"irão mostrar um nome de dispositivo de fsn:. Todas as outras partições reconhecidas serão " +"chamadas blkn:. Se você " +"inseriu um CD mesmo antes de entrar na shell, desta forma poderá demorar " +"alguns segundos extra enquanto inicializa a drive de CD." + +#. Tag: para +#: boot-installer.xml:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" +"Examine o output da consola a procurar a drive de CDROM. É muito provável " +"que seja o dispositivo fs0: embora possam também " +"aparecer outros dispositivos com partições de arranque como " +"fsn." + +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"Introduza fsn: e carregue em " +"ENTER para seleccionar qual o dispositivo onde " +"n é o número da partição para o CDROM. A shell " +"irá agora mostrar o número da partição assim que aparecer a linha de " +"comandos." + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"Introduza elilo e pressione ENTER. " +"Isto irá iniciar a sequência de arranque." -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p" +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"Tal como a opção 1, estes passos iniciam o gestor de arranque de Debian que " +"irá mostrar uma página de menu para você escolher um kernel e opções de " +"arranque. Você pode também introduzir o comando mais curto " +"fsn:elilo na linha de comando. " +"Continue para seleccionar o kernel e as opções de arranque." + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "Instalar utilizando uma Consola Série" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"Você pode escolher fazer uma instalação utilizando um monitor e teclado ou " +"utilizando uma ligação série. Para utilizar uma configuração monitor/" +"teclado, escolha uma opção que contém a string [consola VGA]. Para instalar " +"através de uma ligação série, escolha uma opção que contenha a string " +"[BAUD consola série baud], onde " +"BAUD é a velocidade da sua consola série. Os " +"itens do menu para as definições de baud rate mais típicas no dispositivo " +"ttyS0 são pré-configuradas." + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"Na maioria das circunstâncias, você irá querer que o instalador utilize o " +"mesmo baud rate que a sua ligação para a consola EFI. Se você não tiver a " +"certeza qual á a definição, pode obtê-la utilizando o comando baud na shell EFI." + +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"Se não tiver disponível uma opção que é configurada para o dispositivo série " +"ou baus rate que você gostaria de utilizar, você pode pode ultrapassar a " +"configuração da consola para uma ou mais das opções do menu. Por exemplo, " +"para utilizar uma consola a 57600 baud no dispositivo ttyS1, introduza " +"console=ttyS1,57600n8 na janela de texto Boot:" +"." + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" +"A maioria das máquinas IA-64 vem com uma configuração de consola por omissão " +"de 9600 baud. Esta configuração é um bocado lenta, e o processo de " +"instalação normal irá demorar um tempo significativo a desenhar cada ecrã. " +"Você deve considerar aumentar o baud rate utilizado para fazer a instalação, " +"ou fazer uma instalação em Modo Texto. Veja o menu de ajuda " +"Paramspara instruções de como iniciar o instalador em " +"Modo Texto." + +#. Tag: para +#: boot-installer.xml:1419 +#, 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 "" +"Se escolheu o tipo de consola errado, você será capaz de escolher o kernel e " +"introduzir os parâmetros mas o display e o seu input estarão mortos logo que " +"o kernel inicie, e você terá de reiniciar antes de conseguir iniciar a " +"instalação." + +#. Tag: title +#: boot-installer.xml:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "Escolher o Kernel e Opções de Arranque" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" +"O gestor de arranque irá mostrar um formulário com um menu em lista e uma " +"janela de texto com uma linha de comandos Boot:. As " +"teclas com as setas seleccionam um item a partir do menu e qualquer texto " +"escrito no teclado irá aparecer na janela de texto. Existem também ecrãs de " +"ajuda que podem ser mostrados pressionando a tecla de função apropriada. O " +"ecrã de ajuda General explica as escolhas do menu e o " +"ecrã Params explica as opções comuns da linha de " +"comandos." + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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 "" +"Consulte o ecrã de ajuda Geral para a descrição dos " +"kernel e modos de instalação mais apropriados para a sua instalação. Você " +"também deve consultar a abaixo para quaisquer " +"parâmetros adicionais que você queira definir na janela de texto " +"Boot:. A versão do kernel que você escolher " +"seleccione a versão do kernel que será utilizada para o processo de " +"instalação e para o sistema instalado, você também pode ter esses problemas " +"com o sistema que instalar. Os dois passos seguintes irão seleccionar e " +"iniciar a instalação:" + +#. Tag: para +#: boot-installer.xml:1460 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "" +"Escolha a versão do kernel e o modo de instalação mais apropriado para as " +"suas necessidades com as teclas com as setas." -#~ msgid "nautilus" -#~ msgstr "nautilus" +#. Tag: para +#: boot-installer.xml:1465 +#, 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 "" +"Introduza quaisquer parâmetros de arranque escrevendo-os com o teclado. O " +"texto será mostrado directamente na janela de texto. Isto é onde são " +"especificados os parâmetros do kernel (tais como configurações da consola " +"série)." + +#. Tag: para +#: boot-installer.xml:1472 +#, no-c-format +msgid "" +"Press ENTER. 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 "" +"Carregue em ENTER. Isto irá carregar e iniciar o kernel. " +"O kernel irá mostrar as suas típicas mensagens de inicialização seguidas do " +"primeiro ecrã do Instalador Debian." -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (veja o manual da motherboard) ou SRM" +#. Tag: para +#: boot-installer.xml:1481 boot-installer.xml:1617 +#, 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 "" +"Continue para o próximo capítulo para continuar com a instalação onde você " +"irá configurar o idioma, rede, e partições de disco." -#~ msgid "noname" -#~ msgstr "noname" +#. Tag: para +#: boot-installer.xml:1492 +#, no-c-format +msgid "" +"Booting an IA-64 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 "" +"Arrancar um sistema IA-64 a partir da rede é idêntico a arrancar a partir de " +"um CD. A única diferença é a forma como como é carregado o kernel de " +"instalação. O EFI Boot Manager pode carregar e iniciar programas a partir de " +"um servidor na rede. Uma vez que o kernel de instalação esteja carregado e " +"inicie, a instalação do sistema irá continuar através dos mesmos passos do " +"que a instalação de CD com a excepção que os pacotes da instalação base " +"serão carregados a partir da rede em vez da drive de CD." + +#. Tag: para +#: boot-installer.xml:1526 +#, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" +"Iniciar a partir da rede num sistema IA-64 necessita de duas acções " +"específicas da arquitectura. No servidor de arranque, DHCP e TFTP têm de " +"estar configurados para entregarem o elilo. No cliente " +"tem de ser definida uma nova opção de arranque no gestor de arranque EFI " +"para permitir carregar através da rede." + +#. Tag: title +#: boot-installer.xml:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "Configurar o Servidor" + +#. Tag: para +#: boot-installer.xml:1538 +#, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" +"Uma entrada TFTP adequada para iniciar a partir da rede num sistema IA-64 " +"parece-se um pouco como isto: \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" +" Note que o objectivo é pôr elilo.efi a correr no cliente." + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" +"Extraia o ficheiro netboot.tar.gz para o directório " +"utilizado como raiz do seu servidor tftp. Tipicamente os directórios raiz de " +"tftp incluem /var/lib/tftp e /tftpboot. Isto irá criar uma árvore de directórios debian-" +"installer que contém os ficheiros de arranque para um sistema IA-" +"64." + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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 "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" + +#. Tag: para +#: boot-installer.xml:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" +"O netboot.tar.gz contém um elilo.conf que deve funcionar com a maioria das configurações. No entanto, se " +"você necessitar de fazer modificações no ficheiro pode encontra-lo no " +"directório debian-installer/ia64/. É possível ter " +"vários ficheiros de configuração para diferentes clientes dando-lhes o nome " +"do endereço IP do cliente em hexadecimal com o sufixo .conf em vez de elilo.conf. Para mais detalhes veja " +"a documentação fornecida pelo pacote elilo." + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "Configurar o Cliente" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" +"Para configurar o cliente para suportar arranque por TFTP, comece por " +"arrancar em EFI e entre em Boot Option Maintenance Menu. " +" Adicione uma opção de arranque. Deve ver uma ou mais linhas com o texto " +"Load File [Acpi ()/.../Mac()]. Se existir mais de " +"uma destas entradas, escolha a que tem o endereço MAC do seu interface a " +"partir do qual você irá arrancar. Utilize as teclas com setas para indicar a " +"sua escolha, de seguida carregue em enter. " +" Dê o nome Netboot ou algo similar, " +"grave, e saia de novo para o menu de opções de arranque. " +" Você deve ver a nova opção de arranque acabada de criar, e " +"ao selecciona-la deve iniciar um query DHCP, levando a carregar " +"elilo.efi via TFTP a partir do servidor." + +#. Tag: para +#: boot-installer.xml:1608 +#, 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 "" +"O gestor de arranque irá mostrar a sua linha de comandos após ter feito o " +"download e processado o seu ficheiro de configuração. Neste ponto, a " +"instalação continua com os mesmos passos do que a instalação por CD. Escolha " +"uma opção de arranque tal como em cima quando o kernel completar de se " +"instalar a ele próprio a partir da rede, e irá iniciar o Instalador Debian." + +#. Tag: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "Escolher um Método de Instalação" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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 "" +"Algumas sub-arquitecturas &arch-title; têm a opção de iniciar utilizando " +"qualquer kernel linux seja 2.4.x ou 2.2.x. Quando existem tais escolhas, " +"tente o kernel linux 2.4.x. O instalador requer menos memória utilizando um " +"kernel linux 2.4.x o suporte para o kernel linux 2.2.x requerem um tamanho " +"fixo de ramdisk e o 2.4.x utilizam tmpfs." + +#. Tag: para +#: boot-installer.xml:1640 +#, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "" +"Se está a utilizar um kernel linux 2.2.x, então necessita utilizar " +"&ramdisksize;." -#~ msgid "noritake" -#~ msgstr "noritake" +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "" +"Certifique-se que root=/dev/ram é um dos parâmetros " +"do kernel." -#~ msgid "noritake-p" -#~ msgstr "noritake-p" +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"Se está a ter dificuldades, verifique cts's &arch-title; debian-installer FAQ." + +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "Amiga" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"O único método de instalação disponível para o amiga através do disco rígido " +"(veja a ). Por outras palavras " +"não é possível iniciar a partir de cdrom." -#~ msgid "pc164" -#~ msgstr "pc164" - -#~ msgid "rawhide" -#~ msgstr "rawhide" - -#~ msgid "ruffian" -#~ msgstr "ruffian" - -#~ msgid "ARC only" -#~ msgstr "só ARC" - -#~ msgid "sable" -#~ msgstr "sable" - -#~ msgid "sable-g" -#~ msgstr "sable-g" - -#~ msgid "sx164" -#~ msgstr "sx164" - -#~ msgid "takara" -#~ msgstr "takara" - -#~ msgid "xl" -#~ msgstr "xl" - -#~ msgid "xlt" -#~ msgstr "xlt" - -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, aboot, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." -#~ msgstr "" -#~ "Geralmente, nenhuma destas consolas pode iniciar o Linux directamente, " -#~ "portanto é necessária a assistência de um gestor de arranque. Para a " -#~ "consola SRM, é usado o aboot, um gestor de arranque " -#~ "pequeno e independente da plataforma usada. Ver o (infelizmente " -#~ "desactualizado) SRM HOWTO para " -#~ "mais informações acerca do aboot." - -#~ 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 "" -#~ "Os parágrafos seguintes são referentes ao manual de instalação do woody, " -#~ "e são aqui incluídos para referência; podem vir a ser úteis mais à " -#~ "frente, quando o Debian voltar a suportar instalações baseadas em MILO." - -#~ 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: MILO and aboot." -#~ msgstr "" -#~ "Geralmente, nenhuma destas consolas pode arrancar o Linux directamente, " -#~ "portanto é necessário o recurso a um gestor de arranque intermediário. Há " -#~ "dois gestores de arranque de Linux muito populares: MILO e aboot." - -#~ msgid "" -#~ "MILO is itself a console, which replaces ARC or SRM in " -#~ "memory. MILO can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." -#~ msgstr "" -#~ "MILO é em si mesmo uma consola, que substitui a ARC ou " -#~ "a SRM em memória. MILO pode ser iniciado tanto a " -#~ "partir da ARC como da SRM e é a única maneira de fazer o bootstrap a " -#~ "partir da consola ARC. MILO é específico de uma " -#~ "plataforma (são necessários diferentes MILO para cada " -#~ "tipo de sistema) e existe apenas para esses sistemas, para os quais o " -#~ "suporte ARC é mostrado na tabela acima. Ver também o (infelizmente " -#~ "desactualizado) MILO HOWTO." - -#~ msgid "" -#~ "aboot is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " -#~ "aboot." -#~ msgstr "" -#~ "aboot é um pequeno e independente gestor de arranque, " -#~ "que apenas corre a partir de SRM. Ver também o (infelizmente " -#~ "desactualizado) SRM HOWTO para " -#~ "mais informação acerca do aboot." - -#~ msgid "" -#~ "Thus, three scenarios are generally possible, depending on the system's " -#~ "console firmware and whether or not MILO is available: " -#~ "\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Because MILO 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 aboot on new " -#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -#~ msgstr "" -#~ "Assim, três cenários são normalmente possíveis, dependendo da consola do " -#~ "firmware do sistema e se o MILO está ou não " -#~ "disponível: \n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Como MILO não está " -#~ "disponível para nenhum dos sistemas Alpha correntemente em produção (em " -#~ "Fevereiro de 2000), e porque não é mais necessário comprar uma licença " -#~ "Unix OpenVMS ou Tru64 para ter firmware SRM no seu Alpha mais antigo, é " -#~ "recomendado que use SRM e aboot nas novas instalações " -#~ "de GNU/Linux, a não ser que deseje fazer dual-boot com Windows NT." - -#~ msgid "" -#~ "The majority of AlphaServers and all current server and workstation " -#~ "products contain both SRM and AlphaBIOS in their firmware. For " -#~ "half-flash 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 arc command). " -#~ "For the reasons mentioned above, we recommend switching to SRM before " -#~ "installing &debian;." -#~ msgstr "" -#~ "A maioria dos AlphaServers e todos os produtos actuais para servidores e " -#~ "estações de trabalho contém tanto SRM como AlphaBIOS no seu firmware. " -#~ "Para máquinas half-flash tais como as várias placas de " -#~ "avaliação, é possível mudar de uma versão para outra apenas fazendo " -#~ "novamente o flash ao firmware. Além disso, uma vez o SRM esteja " -#~ "instalado, é possível correr o ARC/AlphaBIOS a partir de uma disquete " -#~ "(usando o comando arc). Pelas razões mencionadas " -#~ "acima, nós recomendamos que mude para SRM antes de instalar &debian;." - -#~ msgid "" -#~ "As on other architectures, you should install the newest available " -#~ "revision of the firmware Except on Jensen, where Linux " -#~ "is not supported on firmware versions newer than 1.7 — see for more information. before installing &debian;. For Alpha, firmware updates can be " -#~ "obtained from Alpha Firmware Updates." -#~ msgstr "" -#~ "Assim como noutras arquitecturas, deverá instalar a revisão de firmware " -#~ "mais recente Excepto em Jensen, onde o Linux não é " -#~ "suportado nas versões superiores a 1.7 — ver para mais informação. antes " -#~ "de instalar &debian;. Para Alpha, os updates de firmware podem ser " -#~ "obtidos a partir de Alpha Firmware " -#~ "Updates ." - -#~ msgid "Booting with TFTP" -#~ msgstr "Iniciar com TFTP" - -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the ewa " -#~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " -#~ "\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" -#~ " You first need to set the boot protocol: " -#~ "\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Then check the medium type is correct: " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " You can get a listing of valid modes with " -#~ ">>>set ewa0_mode." -#~ msgstr "" -#~ "Em SRM, as interfaces Ethernet são nomeados com o prefixo ewa, e serão listados na saída do comando show dev, tal como se mostra em seguida (ligeiramente editado): " -#~ "\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" -#~ " Primeiro, necessita de estabelecer o " -#~ "protocolo de arranque: \n" -#~ ">>> set ewa0_protocol bootp\n" -#~ "De seguida verificar se o tipo de media é " -#~ "correcto:\n" -#~ ">>> set ewa0_mode mode\n" -#~ "Pode obter uma lista dos modos válidos através " -#~ "de >>>set ewa0_mode." - -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "Depois, para iniciar a primeira interface de Ethernet, deverá digitar: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " Isto irá iniciar os parâmetros de kernel pré-" -#~ "definidos, como foram incluídos na imagem netboot." - -#~ msgid "" -#~ "If you wish to use a serial console, you must pass " -#~ "the console= parameter to the kernel. This can be " -#~ "done using the -flags argument to the SRM " -#~ "boot command. The serial ports are named the same " -#~ "as their corresponding files in /dev. 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 " -#~ "ewa0 and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "Se deseja usar a consola de série, tem de passar o " -#~ "parâmetro console= para o kernel. Isto pode ser " -#~ "feito usado o argumento -flags para o comando " -#~ "boot do SRM.As portas série são nomeadas da mesma " -#~ "maneira que o seu correspondente em ficheiros em /dev. Também, quando especificar parâmetros de kernel adicionais, " -#~ "terá de repetir certas opções pré-definias que são necessárias pelas " -#~ "imagens do &d-i;. Por exemplo, para arrancar a partir de ewa0 e usar uma consola na primeira porta série, deverá digitar:" - -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" - -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "Iniciar a partir de CD-ROM com a Consola SRM" - -#~ msgid "" -#~ "Type \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " where xxxx is your " -#~ "CD-ROM drive in SRM notation." -#~ msgstr "" -#~ "Escreva \n" -#~ ">>> boot xxxx -flags 0\n" -#~ "onde xxxx é a sua " -#~ "drive de CD-ROM na notação SRM." - -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "Iniciar a partir de CD-ROM com a Consola ARC ou AlphaBIOS" - -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see ), then enter \\milo" -#~ "\\linload.exe as the boot loader and \\milo" -#~ "\\subarch (where " -#~ "subarch is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use \\milo\\ldmilo.exe as boot loader." -#~ msgstr "" -#~ "Para iniciar um CD-ROM a partir da consola ARC, encontre o nome de código " -#~ "da sua sub-arquitectura (veja a ), " -#~ "seguidamente insira \\milo\\linload.exe como gestor " -#~ "de arranque e \\milo\\subarch (onde subarch é o nome correcto da " -#~ "sub-arquitectura) como o caminho do SO no menu `OS Selection Setup'. " -#~ "Ruffians são as excepções: necessita do \\milo\\ldmilo.exe como gestor de arranque." - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "Iniciar a partir de Disquetes com a Consola SRM" - -#~ msgid "" -#~ "At the SRM prompt (>>>), issue the following " -#~ "command: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possibly replacing dva0 " -#~ "with the actual device name. Usually, dva0 is the " -#~ "floppy; type \n" -#~ ">>> show dev\n" -#~ " to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, -" -#~ "flags argument is ignored, so you can just type boot " -#~ "dva0. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "Na prompt da SRM (>>>), digite o seguinte " -#~ "comando: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possivelmente substituindo dva0 pelo nome do dispositivo correcto. Normalmente, dva0 é a disquete; digite \n" -#~ ">>> show dev\n" -#~ " para ver a lista de dispositivos (e.g, se " -#~ "quer iniciar a partir de um CD). Note que se está a arrancar via MILO, o " -#~ "argumento -flags é ignorado, para que possa apenas " -#~ "digitar boot dva0. Se tudo estiver OK, irá " -#~ "eventualmente ver o arranque do kernel Linux." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for dva0, " -#~ "the Linux boot device name for fd0, and the desired " -#~ "kernel parameters for arguments." -#~ msgstr "" -#~ "Se desejar especificar os parâmetros do kernel quando iniciado via " -#~ "aboot, use o seguinte comando:" -#~ "\n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (escrito numa linha), substituindo, se " -#~ "necessário, o nome do dispositivo actual de boot SRM para dva0, o nome do dispositivo de arranque do Linux para fd0, e os parâmetros desejados para o kernel para " -#~ "arguments." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " -#~ "See ." -#~ msgstr "" -#~ "Se desejar especificar os parâmetros do kernel quando iniciar via " -#~ "MILO, terá de interromper o bootstrap mal chegue ao " -#~ "MILO. veja a ." - -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "Iniciar a partir de Disquetes com a Consola ARC ou AlphaBIOS" - -#~ msgid "" -#~ "In the OS Selection menu, set linload.exe as the boot " -#~ "loader, and milo as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "No menu de selecção do SO, defina linload.exe como o " -#~ "gestor de arranque, e milo como o OS Path. Faça o " -#~ "bootstrap usando a entrada recentemente criada." - -#~ msgid "Booting with MILO" -#~ msgstr "Iniciar com o MILO" - -#~ 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 "" -#~ "O MILO contido na bootstrap media está configurado automaticamente para " -#~ "proceder automaticamente para Linux. Caso deseje intervir, tudo o que " -#~ "necessita fazer é pressionar a tecla de espaço durante a contagem " -#~ "decrescente do MILO." - -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Если вы хотите задать все параметры явно (например, чтобы добавить свои " +"параметры), то можете использовать такую команду: \n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" Если вы загружаетесь не с дискеты, замените " +"fd0 в приведённом выше примере на соответствующее имя " +"устройства в Linux. Команда help выводит краткую справку " +"о командах MILO." + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "Загрузка по TFTP" # index.docbook:427, index.docbook:872, index.docbook:1420, index.docbook:1892, index.docbook:2246, index.docbook:2354 -#~ msgid "" -#~ "Booting from the network requires that you have a network connection and " -#~ "a TFTP network boot server (DHCP, RARP, or BOOTP)." -#~ msgstr "" -#~ "Загрузка по сети требует наличия сетевого подключения и сетевого " -#~ "загрузочного сервера TFTP (DHCP, RARP или BOOTP)." +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"Загрузка по сети требует наличия сетевого подключения и сетевого " +"загрузочного сервера TFTP (DHCP, RARP или BOOTP)." # index.docbook:432, index.docbook:877, index.docbook:1425, index.docbook:1897, index.docbook:2251, index.docbook:2359 -#~ msgid "" -#~ "Older systems such as the 715 might require the use of an RBOOT server " -#~ "instead of a BOOTP server." -#~ msgstr "" -#~ "Для старых систем, например, 715-х, может потребоваться использование " -#~ "RBOOT сервера вместо сервера BOOTP." +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"Для старых систем, например, 715-х, может потребоваться использование RBOOT " +"сервера вместо сервера BOOTP." # index.docbook:437, index.docbook:882, index.docbook:1430, index.docbook:1902, index.docbook:2256, index.docbook:2364 -#~ msgid "" -#~ "The installation method to support network booting is described in ." -#~ msgstr "" -#~ "Метод установки с загрузкой из сети описан в ." - -#~ msgid "Booting from TFTP on Netwinder" -#~ msgstr "Загрузка Netwinder по TFTP" - -#~ msgid "" -#~ "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " -#~ "(which is generally referred to as eth0) 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 interface (the " -#~ "one labeled with 10 Base-T)." -#~ msgstr "" -#~ "Системы Netwinder имеют два сетевых интерфейса: 10Мбитная NE2000-" -#~ "совместимая карта (к которой обычно обращаются через eth0) и 100Мбитная карта Tulip. При загрузке образа по TFTP через " -#~ "100Мбитную карту могут возникнуть проблемы, поэтому рекомендуется " -#~ "использовать 10Мбитный интерфейс (помеченный как 10 Base-T)." - -#~ 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 ." -#~ msgstr "" -#~ "Вам потребуется NeTTrom версии 2.2.1 или новее для загрузки системы, но " -#~ "рекомендуется версия 2.3.3. К сожалению, из-за лицензионных проблем файлы " -#~ "микропрограмм недоступны для загрузки. Если ситуация изменится, вы можете " -#~ "найти новые образы на ." - -#~ 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: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Furthermore, you must configure the network, " -#~ "either with a static address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " where 24 is the number of set bits in the " -#~ "netmask, or a dynamic address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " You may also need to configure the " -#~ "route1 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. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Now you have to tell the firmware that the " -#~ "TFTP image should be booted: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " If you use a serial console to install your " -#~ "Netwinder, you need to add the following setting: " -#~ "\n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Alternatively, for installations using a " -#~ "keyboard and monitor you have to set: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " You can use the printenv " -#~ "command to review your environment settings. After you have verified that " -#~ "the settings are correct, you can load the image: " -#~ "\n" -#~ " NeTTrom command-> boot\n" -#~ " In case you run into any problems, a detailed " -#~ "HOWTO is available." -#~ msgstr "" -#~ "При загрузке Netwinder вы можете прервать этот процесс во время отсчёта " -#~ "времени. Это позволит настроить параметры микропрограммы, необходимые для " -#~ "загрузки программы установки. Во-первых, начните с загрузки значений по " -#~ "умолчанию: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Кроме этого, вы должны настроить сетевые " -#~ "параметры, или указав статический адрес: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ ", где 24 — это число бит в маске сети, " -#~ "или динамический адрес: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " Также вам может потребоваться настроить " -#~ "параметр route1, если TFTP сервер находится в " -#~ "другой подсети. После этих настроек, укажите TFTP сервер и место " -#~ "размещения образа. Затем сохраните настройки во флеш памяти. " -#~ "\n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Теперь нужно указать микропрограмме, что " -#~ "образ должен быть загружен по TFTP: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " Если для установки вы хотите использовать " -#~ "последовательную консоль Netwinder, то нужно добавить следующую " -#~ "настройку: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Если для установки используются клавиатура и " -#~ "монитор нужно указать: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " Чтобы просмотреть настройки используйте " -#~ "команду printenv. После проверки правильности " -#~ "настроек, загрузите образ: \n" -#~ " NeTTrom command-> boot\n" -#~ " При возникновении проблем, обратитесь к " -#~ "подробному HOWTO." - -#~ msgid "Booting from TFTP on CATS" -#~ msgstr "Загрузка по TFTP на CATS" - -#~ msgid "" -#~ "On CATS machines, use boot de0: or similar at the " -#~ "Cyclone prompt." -#~ msgstr "" -#~ "На машинах CATS в приглашении Cyclone введите boot de0: или нечто подобное." - -#~ msgid "Booting from CD-ROM" -#~ msgstr "Загрузка с CD-ROM" +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "" +"Метод установки с загрузкой из сети описан в ." + +#. Tag: title +#: boot-installer.xml:459 +#, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "Загрузка Netwinder по TFTP" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" +"Системы Netwinder имеют два сетевых интерфейса: 10Мбитная NE2000-совместимая " +"карта (к которой обычно обращаются через eth0) и " +"100Мбитная карта Tulip. При загрузке образа по TFTP через 100Мбитную карту " +"могут возникнуть проблемы, поэтому рекомендуется использовать 10Мбитный " +"интерфейс (помеченный как 10 Base-T)." + +#. 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 ." +msgstr "" +"Вам потребуется NeTTrom версии 2.2.1 или новее для загрузки системы, но " +"рекомендуется версия 2.3.3. К сожалению, из-за лицензионных проблем файлы " +"микропрограмм недоступны для загрузки. Если ситуация изменится, вы можете " +"найти новые образы на ." + +#. 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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" +"При загрузке Netwinder вы можете прервать этот процесс во время отсчёта " +"времени. Это позволит настроить параметры микропрограммы, необходимые для " +"загрузки программы установки. Во-первых, начните с загрузки значений по " +"умолчанию: \n" +" NeTTrom command-> load-defaults\n" +" Кроме этого, вы должны настроить сетевые " +"параметры, или указав статический адрес: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +", где 24 — это число бит в маске сети, или " +"динамический адрес: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" Также вам может потребоваться настроить параметр " +"route1, если TFTP сервер находится в другой подсети. " +"После этих настроек, укажите TFTP сервер и место размещения образа. Затем " +"сохраните настройки во флеш памяти. \n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Теперь нужно указать микропрограмме, что образ " +"должен быть загружен по TFTP: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" Если для установки вы хотите использовать " +"последовательную консоль Netwinder, то нужно добавить следующую настройку: " +"\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Если для установки используются клавиатура и " +"монитор нужно указать: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" Чтобы просмотреть настройки используйте команду " +"printenv. После проверки правильности настроек, загрузите " +"образ: \n" +" NeTTrom command-> boot\n" +" При возникновении проблем, обратитесь к подробному HOWTO." + +#. Tag: title +#: boot-installer.xml:529 +#, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "Загрузка по TFTP на CATS" + +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"На машинах CATS в приглашении Cyclone введите boot de0: " +"или нечто подобное." + +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "Загрузка с CD-ROM" # index.docbook:526, index.docbook:578, index.docbook:1043, index.docbook:1849, index.docbook:2090, index.docbook:2394 -#~ 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 configure your system for booting " -#~ "off a CD as described in , " -#~ "insert your CD, reboot, and proceed to the next chapter." -#~ msgstr "" -#~ "Для большинства пользователей проще всего будет использовать набор " -#~ "компакт-дисков Debian. Если у вас есть набор компакт-дисков и ваш " -#~ "компьютер поддерживает загрузку с компакт-диска, прекрасно! Просто " -#~ " настройте ваш компьютер для загрузки с компакт-" -#~ "диска как описано в , " -#~ "вставьте компакт-диск, перезагрузите компьютер и переходите к следующей " -#~ "главе." +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"Для большинства пользователей проще всего будет использовать набор компакт-" +"дисков Debian. Если у вас есть набор компакт-дисков и ваш компьютер " +"поддерживает загрузку с компакт-диска, прекрасно! Просто настройте ваш компьютер для загрузки с компакт-диска как описано в , вставьте компакт-диск, " +"перезагрузите компьютер и переходите к следующей главе." # index.docbook:537, index.docbook:589, index.docbook:1054, index.docbook:1860, index.docbook:2101, index.docbook:2405 -#~ 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 "" -#~ "Заметим, что некоторым приводам компакт-дисков нужны специальные драйверы " -#~ "и поэтому, они недоступны на ранних стадиях установки. Если производимая " -#~ "стандартная последовательность загрузки с CD не работает, обратитесь к " -#~ "этой главе снова и прочитайте об альтернативных ядрах и методах " -#~ "установки, которые доступны для вашей машины." +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"Заметим, что некоторым приводам компакт-дисков нужны специальные драйверы и " +"поэтому, они недоступны на ранних стадиях установки. Если производимая " +"стандартная последовательность загрузки с CD не работает, обратитесь к этой " +"главе снова и прочитайте об альтернативных ядрах и методах установки, " +"которые доступны для вашей машины." # index.docbook:545, index.docbook:597, index.docbook:1062, index.docbook:1868, index.docbook:2109, index.docbook:2413 -#~ 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 "" -#~ "Даже если не удалось загрузиться с CD-ROM, вероятно, вы ещё сможете " -#~ "установить с CD-ROM компоненты системы Debian и пакеты. Просто " -#~ "загрузитесь с другого носителя, например, с дискет. Когда придёт время " -#~ "установки операционной системы, базовой системы или дополнительных " -#~ "пакетов, укажите программе установки на привод CD-ROM." +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"Даже если не удалось загрузиться с CD-ROM, вероятно, вы ещё сможете " +"установить с CD-ROM компоненты системы Debian и пакеты. Просто загрузитесь с " +"другого носителя, например, с дискет. Когда придёт время установки " +"операционной системы, базовой системы или дополнительных пакетов, укажите " +"программе установки на привод CD-ROM." # index.docbook:553, index.docbook:605, index.docbook:1070, index.docbook:1876, index.docbook:2117, index.docbook:2421 -#~ msgid "" -#~ "If you have problems booting, see ." -#~ msgstr "" -#~ "При возникновении проблем с загрузкой смотрите ." - -#~ msgid "" -#~ "To boot a CD-ROM from the Cyclone console prompt, use the command " -#~ "boot cd0:cats.bin" -#~ msgstr "" -#~ "Чтобы загрузиться с CD-ROM из консоли Cyclone, используйте команду " -#~ "boot cd0:cats.bin" +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"При возникновении проблем с загрузкой смотрите ." + +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"Чтобы загрузиться с CD-ROM из консоли Cyclone, используйте команду " +"boot cd0:cats.bin" # index.docbook:807, index.docbook:1949, index.docbook:2282, index.docbook:2442 -#~ msgid "Booting from Firmware" -#~ msgstr "Загрузка из микропрограммы" - -#~ 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 "" -#~ "В настоящее время растёт число бытовых устройств, которые загружаются " -#~ "непосредственно из флеш памяти устройства. Для них программа установки " -#~ "может быть записана во флеш, для автоматического запуска при перезагрузке " -#~ "устройства." - -#~ 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: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 "" +"В большинстве случаев такое изменение микропрограммы устройства лишает " +"гарантии. Также, иногда невозможно починить устройство, если возникнут " +"проблемы при записи во флеш. Поэтому точно следуйте указаниям." # index.docbook:254, index.docbook:866, index.docbook:1402, index.docbook:1886, index.docbook:1969, index.docbook:2240, index.docbook:2348 -#~ msgid "Booting the NSLU2" -#~ msgstr "Загрузка NSLU2" - -#~ msgid "There are three ways how to put the installer firmware into flash:" -#~ msgstr "Есть три способа заливки микропрограммы установки в флеш:" - -#~ msgid "Using the NSLU2 web interface" -#~ msgstr "С помощью веб интерфейса NSLU2" - -#~ msgid "" -#~ "Go to the administration section and choose the menu item " -#~ "Upgrade. You can then browse your disk for the " -#~ "installer image you have previously downloaded. Then press the " -#~ "Start Upgrade button, confirm, wait for a few minutes " -#~ "and confirm again. The system will then boot straight into the installer." -#~ msgstr "" -#~ "Перейдите в раздел управления и выберите пункт меню Upgrade. Затем выберите с диска образ программы установки. Нажмите " -#~ "кнопку Start Upgrade, подтвердите, подождите несколько " -#~ "минут и подтвердите ещё раз. Система будет перезагружена прямо в " -#~ "программу установки." - -#~ msgid "Via the network using Linux/Unix" -#~ msgstr "По сети с помощью Linux/Unix" - -#~ msgid "" -#~ "You can use upslug2 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: " -#~ " Disconnect any disks and/or devices from the USB ports. " -#~ " Power off the NSLU2 Press and hold the reset button (accessible " -#~ "through the small hole on the back just above the power input). Press and release the power button to power on " -#~ "the NSLU2. Wait for 10 seconds " -#~ "watching the ready/status LED. After 10 seconds it will change from amber " -#~ "to red. Immediately release the reset button. " -#~ " 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. See the NSLU2-Linux " -#~ "pages if you have problems with this. Once your NSLU2 is in " -#~ "upgrade mode, you can flash the new image: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " 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 "" -#~ "Для обновления по сети вы можете использовать upslug2 " -#~ "с любой Linux или Unix машины. Эта программа существует в виде пакета " -#~ "Debian. Во-первых, переведите NSLU2 в режим обновления: " -#~ " Отключите диски и/или другие устройства из портов USB. Выключите питание NSLU2 Нажмите и удерживайте кнопку сброса ( она " -#~ "находится в маленьком отверстии на задней стенке над разъёмом питания). Нажмите и отпустите кнопку питания " -#~ "NSLU2. Подождите 10 секунд, наблюдая " -#~ "за индикатором готовности/состояния. По прошествии 10 секунд его " -#~ "состояние изменится с жёлтого на красный. Немедленно отпустите кнопку " -#~ "сброса. Лампочка индикатора " -#~ "готовности/состояния NSLU2 заморгает попеременно красным/зелёным (будет " -#~ "задержка в 1 секунду перед первым появлением зелёного цвета). Теперь " -#~ "NSLU2 находится в режиме обновления. " -#~ "При возникновении проблем обратитесь к странице NSLU2-Linux. " -#~ "После того как NSLU2 в режиме обновления, вы можете записать новый образ " -#~ "во флеш память: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " Заметим, что эта утилита также показывать MAC " -#~ "адрес NSLU2, который может пригодиться при настройке DHCP сервера. После " -#~ "записи и проверки образа, система будет автоматически перезагружена. " -#~ "Убедитесь, что обратно вставили USB диск, иначе программа установки не " -#~ "сможет найти его." - -#~ msgid "Via the network using Windows" -#~ msgstr "По сети с помощью Windows" - -#~ msgid "" -#~ "There is a tool for Windows to upgrade " -#~ "the firmware via the network." -#~ msgstr "" -#~ "Для обновления микропрограммы по сети существует утилита для Windows." +#. Tag: title +#: boot-installer.xml:612 +#, no-c-format +msgid "Booting the NSLU2" +msgstr "Загрузка NSLU2" + +#. 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 "С помощью веб интерфейса NSLU2" + +#. Tag: para +#: boot-installer.xml:620 +#, no-c-format +msgid "" +"Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." +msgstr "" +"Перейдите в раздел управления и выберите пункт меню Upgrade. Затем выберите с диска образ программы установки. Нажмите кнопку " +"Start Upgrade, подтвердите, подождите несколько минут и " +"подтвердите ещё раз. Система будет перезагружена прямо в программу установки." + +#. Tag: title +#: boot-installer.xml:631 +#, no-c-format +msgid "Via the network using Linux/Unix" +msgstr "По сети с помощью Linux/Unix" + +#. Tag: para +#: boot-installer.xml:632 +#, no-c-format +msgid "" +"You can use upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 "" +"Для обновления по сети вы можете использовать upslug2 с " +"любой Linux или Unix машины. Эта программа существует в виде пакета Debian. " +"Во-первых, переведите NSLU2 в режим обновления: " +" Отключите диски и/или другие устройства из портов USB. Выключите питание NSLU2 " +" Нажмите и удерживайте кнопку сброса ( она находится в " +"маленьком отверстии на задней стенке над разъёмом питания). Нажмите и отпустите кнопку питания NSLU2. Подождите 10 секунд, наблюдая за " +"индикатором готовности/состояния. По прошествии 10 секунд его состояние " +"изменится с жёлтого на красный. Немедленно отпустите кнопку сброса. Лампочка индикатора готовности/состояния NSLU2 " +"заморгает попеременно красным/зелёным (будет задержка в 1 секунду перед " +"первым появлением зелёного цвета). Теперь NSLU2 находится в режиме " +"обновления. При возникновении проблем " +"обратитесь к странице NSLU2-Linux. После того как NSLU2 в режиме " +"обновления, вы можете записать новый образ во флеш память: " +"\n" +"sudo upslug2 -i di-nslu2.bin\n" +" Заметим, что эта утилита также показывать MAC " +"адрес NSLU2, который может пригодиться при настройке DHCP сервера. После " +"записи и проверки образа, система будет автоматически перезагружена. " +"Убедитесь, что обратно вставили USB диск, иначе программа установки не " +"сможет найти его." + +#. Tag: title +#: boot-installer.xml:693 +#, no-c-format +msgid "Via the network using Windows" +msgstr "По сети с помощью Windows" + +#. Tag: para +#: boot-installer.xml:694 +#, no-c-format +msgid "" +"There is a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" +"Для обновления микропрограммы по сети существует утилита для Windows." # index.docbook:572, index.docbook:1037, index.docbook:1837, index.docbook:2084, index.docbook:2388 -#~ msgid "Booting from a CD-ROM" -#~ msgstr "Загрузка с CD-ROM" - -#~ msgid "" -#~ "Booting from Linux Using LILO or GRUB" -#~ msgstr "" -#~ "Загрузка из Linux с помощью LILO или GRUB" +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "Загрузка с CD-ROM" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "" +"Загрузка из Linux с помощью LILO или GRUB" # index.docbook:1670, index.docbook:2168 -#~ msgid "" -#~ "To boot the installer from hard disk, you must first download and place " -#~ "the needed files as described in ." -#~ msgstr "" -#~ "Для загрузки программы установки с жёсткого диска у вас уже должны быть " -#~ "полностью полученные и размещённые на диске необходимые файлы (смотрите " -#~ ")." - -#~ msgid "" -#~ "If you intend to use the hard drive only for booting and then download " -#~ "everything over the network, you should download the netboot/" -#~ "debian-installer/i386/initrd.gz file and its corresponding " -#~ "kernel netboot/debian-installer/i386/linux. This " -#~ "will allow you to repartition the hard disk from which you boot the " -#~ "installer, although you should do so with care." -#~ msgstr "" -#~ "Если вы намереваетесь использовать жёсткий диск только для загрузки, а " -#~ "затем выполнять установку по сети, то вы должны получить файл " -#~ "netboot/debian-installer/i386/initrd.gz и " -#~ "соответствующее ему ядро netboot/debian-installer/i386/linux. Это позволит вам переразметить жёсткий диск с которого вы " -#~ "загрузились, хотя вы должны делать это осторожно." - -#~ msgid "" -#~ "Alternatively, if you intend to keep an existing partition on the hard " -#~ "drive unchanged during the install, you can download the hd-" -#~ "media/initrd.gz file and its kernel, as well as copy a CD iso " -#~ "to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from " -#~ "the CD image, without needing the network." -#~ msgstr "" -#~ "Или же, если вы намереваетесь сохранить существующий раздел жёсткого " -#~ "диска неизменным, то можете получить файл hd-media/initrd.gz и ядро, а также скопировать файл образа CD на жёсткий диск " -#~ "(проверьте, что имя заканчивается на .iso). Затем " -#~ "программу установки можно загрузить с диска и установить из образа CD без " -#~ "использования сети." - -#~ msgid "" -#~ "For LILO, you will need to configure two essential " -#~ "things in /etc/lilo.conf: " -#~ " to load the initrd.gz installer at " -#~ "boot time; have the " -#~ "vmlinuz kernel use a RAM disk as its root partition. " -#~ " Here is a /etc/lilo.conf example:" -#~ msgstr "" -#~ "В LILO нужно настроить две важные вещи в файле " -#~ "/etc/lilo.conf: " -#~ "загружать программу установки из initrd.gz; ядро vmlinuz использует " -#~ "RAM диск в качестве корневого раздела. " -#~ "Вот пример /etc/lilo.conf:" - -#~ msgid "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" -#~ msgstr "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" - -#~ msgid "" -#~ "For more details, refer to the initrd 4 and " -#~ "lilo.conf 5 man pages. Now run lilo " -#~ "and reboot." -#~ msgstr "" -#~ "Подробней смотрите на страницах руководства " -#~ "initrd 4 и lilo.conf 5. Теперь запустите " -#~ "lilo и перезагрузите машину." - -#~ msgid "" -#~ "The procedure for GRUB is quite similar. Locate your " -#~ "menu.lst in the /boot/grub/ " -#~ "directory (sometimes in the /boot/boot/grub/), add " -#~ "the following lines: \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" -#~ " and reboot." -#~ msgstr "" -#~ "Процедура для GRUB очень похожа. Найдите файл " -#~ "menu.lst в каталоге /boot/grub/ " -#~ "(иногда в /boot/boot/grub/), добавьте строчки: " -#~ "\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" -#~ " и перезагрузите машину." - -#~ msgid "" -#~ "Note that the value of the ramdisk_size may need " -#~ "to be adjusted for the size of the initrd image. From here on, there " -#~ "should be no difference between GRUB or LILO." -#~ msgstr "" -#~ "Заметим, что значение ramdisksize может " -#~ "потребоваться привести в соответствие с размером образа initrd. В " -#~ "дальнейшем нет никакой разницы в использовании GRUB " -#~ "или LILO." - -#~ msgid "Booting from USB Memory Stick" -#~ msgstr "Загрузка с карты памяти USB" - -#~ msgid "" -#~ "Let's assume you have prepared everything from and . 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 boot: prompt. Here you can enter optional boot arguments, or just hit " -#~ "&enterkey;." -#~ msgstr "" -#~ "Предположим, что вы уже приготовили всё как написано в и . Теперь " -#~ "вставьте карту памяти USB в свободное USB гнездо и перезагрузите " -#~ "компьютер. Система должна загрузиться и вы должны увидеть приглашение " -#~ "boot:. Здесь вы можете ввести необязательные параметры " -#~ "загрузки, или просто нажать &enterkey;." +#. 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 ." +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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"Если вы намереваетесь использовать жёсткий диск только для загрузки, а затем " +"выполнять установку по сети, то вы должны получить файл netboot/" +"debian-installer/i386/initrd.gz и соответствующее ему ядро " +"netboot/debian-installer/i386/linux. Это позволит вам " +"переразметить жёсткий диск с которого вы загрузились, хотя вы должны делать " +"это осторожно." + +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"Или же, если вы намереваетесь сохранить существующий раздел жёсткого диска " +"неизменным, то можете получить файл hd-media/initrd.gz и ядро, а также скопировать файл образа CD на жёсткий диск " +"(проверьте, что имя заканчивается на .iso). Затем " +"программу установки можно загрузить с диска и установить из образа CD без " +"использования сети." + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"В LILO нужно настроить две важные вещи в файле /" +"etc/lilo.conf: загружать " +"программу установки из initrd.gz; " +" ядро vmlinuz использует RAM диск в " +"качестве корневого раздела. Вот пример " +"/etc/lilo.conf:" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"Подробней смотрите на страницах руководства " +"initrd 4 и lilo.conf 5. Теперь запустите " +"lilo и перезагрузите машину." + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"Процедура для GRUB очень похожа. Найдите файл " +"menu.lst в каталоге /boot/grub/ " +"(иногда в /boot/boot/grub/), добавьте строчки: " +"\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" +" и перезагрузите машину." + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"Заметим, что значение ramdisksize может потребоваться " +"привести в соответствие с размером образа initrd. В дальнейшем нет никакой " +"разницы в использовании GRUB или LILO." + +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "Загрузка с карты памяти USB" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +"Предположим, что вы уже приготовили всё как написано в и . Теперь вставьте карту " +"памяти USB в свободное USB гнездо и перезагрузите компьютер. Система должна " +"загрузиться и вы должны увидеть приглашение boot:. Здесь вы " +"можете ввести необязательные параметры загрузки, или просто нажать " +"&enterkey;." # index.docbook:807, index.docbook:1949, index.docbook:2282, index.docbook:2442 -#~ msgid "Booting from Floppies" -#~ msgstr "Загрузка с дискет" +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "Загрузка с дискет" # index.docbook:808, index.docbook:2290 -#~ msgid "" -#~ "You will have already downloaded the floppy images you needed and created " -#~ "floppies from the images in ." -#~ msgstr "" -#~ "Предполагается, что вы уже получили образы дискет и сделали из них " -#~ "загрузочные дискеты как описано в ." - -#~ 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 "" -#~ "Для загрузки программы установки с дискет, вставьте первую из них в " -#~ "дисковод, выключите систему как обычно и включите питание." - -#~ 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 root= 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 linux root=/dev/hdc at the " -#~ "boot prompt." -#~ msgstr "" -#~ "При установке с привода LS-120 (ATAPI версия), вам нужно задать " -#~ "виртуальный путь к дисководу. Он указывается в параметре загрузки " -#~ "root=, где указывается устройство, на которое " -#~ "драйвер ide-floppy назначит привод. Например, если привод LS-120 " -#~ "подключён как первое IDE устройство (мастер) на второй кабель, введите в " -#~ "приглашении к загрузке linux root=/dev/hdc." - -#~ msgid "" -#~ "Note that on some machines, Control " -#~ "Alt Delete does not properly " -#~ "reset the machine, so a hard 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 "" -#~ "Заметим, что на некоторых машинах, комбинация клавиш " -#~ "Control Alt Delete не по-настоящему перезагружает машину, поэтому " -#~ "рекомендуется аппаратная перезагрузка. Если вы производите " -#~ "установку из существующей операционной системы (например, из DOS), то у " -#~ "вас нет выбора. Иначе, выполните аппаратную перезагрузку перед загрузкой." - -#~ msgid "" -#~ "The floppy disk will be accessed, and you should then see a screen that " -#~ "introduces the boot floppy and ends with the boot: " -#~ "prompt." -#~ msgstr "" -#~ "Далее, будет произведён доступ к дискете, и далее вы должны увидеть " -#~ "экран, который показывает загрузку с дискеты и в конце появляется " -#~ "приглашение boot:." - -#~ msgid "" -#~ "Once you press &enterkey;, you should see the message " -#~ "Loading..., followed by " -#~ "Uncompressing Linux..., 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 ." -#~ msgstr "" -#~ "После нажатия &enterkey;, вы должны увидеть сообщение " -#~ "Loading..., потом " -#~ "Uncompressing Linux..., и затем " -#~ "несколько экранов с информацией о найденном оборудовании. Подробную " -#~ "информацию об этом этапе процесса загрузки можно найти в ." - -#~ 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 debian-installer is " -#~ "automatically launched." -#~ msgstr "" -#~ "После загрузки с загрузочной дискеты, вас попросят вставить дискету с " -#~ "корневой файловой системой. Вставьте нужную дискету, нажмите &enterkey;, " -#~ "и её содержимое загрузится в память. В конце автоматически запустится " -#~ "программа установки debian-installer." - -#~ msgid "There are various ways to do a TFTP boot on i386." -#~ msgstr "Есть несколько возможностей выполнить загрузку по TFTP на i386." - -#~ msgid "NIC or Motherboard that support PXE" -#~ msgstr "Сетевая карта или материнская плата с поддержкой PXE" - -#~ msgid "" -#~ "It could be that your Network Interface Card or Motherboard provides PXE " -#~ "boot functionality. This is a Intel re-implementation of TFTP boot. If so you may be able to " -#~ "configure your BIOS to boot from the network." -#~ msgstr "" -#~ "Возможно, ваша сетевая карта (NIC) или материнская плата предоставляют " -#~ "возможность загрузки через PXE. Так названа реализация TFTP загрузки от " -#~ "компании Intel. В этом случае вы " -#~ "можете настроить BIOS на загрузку по сети." - -#~ msgid "NIC with Network BootROM" -#~ msgstr "Сетевая карта с сетевым BootROM" - -#~ msgid "" -#~ "It could be that your Network Interface Card provides TFTP boot " -#~ "functionality." -#~ msgstr "" -#~ "Возможно, что сетевая карта (NIC) предоставляет возможность загрузки по " -#~ "TFTP." - -#~ msgid "" -#~ "Let us (&email-debian-boot-list;) know how did you manage " -#~ "it. Please refer to this document." -#~ msgstr "" -#~ "Напишите нам (&email-debian-boot-list;) как вам удалось " -#~ "сделать это. Пожалуйста, упомяните в заголовке этот документ." - -#~ msgid "Etherboot" -#~ msgstr "Etherboot" - -#~ msgid "" -#~ "The etherboot project " -#~ "provides bootdiskettes and even bootroms that do a TFTPboot." -#~ msgstr "" -#~ "Проект etherboot " -#~ "предоставляет загрузочные дискеты и даже прошивки (bootrom) для TFTPboot." - -# index.docbook:2012, index.docbook:2491 -#~ msgid "The Boot Prompt" -#~ msgstr "Приглашение к загрузке" - -#~ msgid "" -#~ "When the installer boots, you should be presented with a friendly " -#~ "graphical screen showing the Debian logo and the boot prompt: " -#~ "\n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " 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 "" -#~ "В самом начале загрузки программы установки на экране появится логотип " -#~ "Debian и приглашение к загрузке: \n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " В приглашении к загрузке вы можете или просто " -#~ "нажать &enterkey; для загрузки программы установки с параметрами по " -#~ "умолчанию, или ввести желаемый метод загрузки и, если нужно, загрузочные " -#~ "параметры." - -#~ msgid "" -#~ "Information on available boot methods and on boot parameters which might " -#~ "be useful can be found by pressing F2 through " -#~ "F8. If you add any parameters to the boot command line, " -#~ "be sure to type the boot method (the default is linux) and a space before the first parameter (e.g., " -#~ "linux fb=false)." -#~ msgstr "" -#~ "Информацию о доступных параметрах загрузки можно увидеть нажимая клавиши " -#~ "с F2 по F8. При добавлении параметров " -#~ "загрузки в командную строку убедитесь, что ввели метод загрузки (по " -#~ "умолчанию linux) и пробел перед первым параметром " -#~ "(например, linux fb=false)." - -#~ 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 integrated Lights Out (iLO) and HP's " -#~ "Integrated Remote Assistant (IRA). You can blindly press " -#~ "F1 In some cases these devices will require special " -#~ "escape sequences to enact this keypress, for example the IRA uses " -#~ " Ctrl F , " -#~ "1. 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 fb=false to the boot " -#~ "prompt, as described in the help text." -#~ msgstr "" -#~ "Если вы производите установку через удалённое управляющее устройство, " -#~ "которое выводит текстовый интерфейс на VGA консоль, то скорее всего, вы " -#~ "не увидите графическую начальную заставку перед загрузкой программы " -#~ "установки; вы даже можете не увидеть приглашение к загрузке. Например, " -#~ "так будет на устройствах с текстовыми консолями Compaq integrated " -#~ "Lights Out (iLO) и HP Integrated Remote Assistant " -#~ "(IRA). Можно вслепую нажать F1, В некоторых случаях на " -#~ "таких устройствах нужно ввести специальную комбинацию нажатий, которая " -#~ "работает как F1, например, для IRA это Ctrl " -#~ "F , 1. , чтобы пропустить этот экран и увидеть экран с подсказкой. " -#~ "После прохождения момента с начальной заставкой и вывода экрана с " -#~ "подсказкой вводимые символы будут отображаться как обычно. Чтобы указать " -#~ "программе установки не использовать framebuffer при установке, нужно " -#~ "добавить параметр загрузки fb=false, как описано в " -#~ "подсказке." - -#~ msgid "CD Contents" -#~ msgstr "Содержимое компакт-диска" - -#~ msgid "" -#~ "There are three basic variations of Debian Install CDs. The " -#~ "Business Card 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 Network Install 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 "" -#~ "Существует три основные вариации установочных компакт-дисков Debian. Диск-" -#~ "визитка содержит минимальную установку, которая " -#~ "помещается на носителе маленького формата. Он требует сетевого соединения " -#~ "для установки остальной части базовой установки и создания пригодной для " -#~ "работы системы. Диск сетевой установки содержит все " -#~ "пакеты для базовой установки, но требует сетевого соединения с зеркалами " -#~ "Debian для установки дополнительных пакетов, если вам хочется получить " -#~ "полноценную систему. А весь комплект компакт-дисков Debian может " -#~ "установить полноценную систему с большим выбором пакетов безо всякого " -#~ "доступа к сети." - -#~ 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 "" -#~ "Архитектура IA-64 использует интерфейс следующего поколения Extensible " -#~ "Firmware Interface (EFI) от Intel. В отличие от традиционного BIOS x86, " -#~ "который ничего не знает о загрузочном устройстве кроме таблицы разделов и " -#~ "главной загрузочной записи (MBR), EFI может читать и записывать файлы из " -#~ "разделов отформатированных в FAT16 или FAT32. Это упрощает зачастую " -#~ "просто чародейский процесс старта системы. Системный загрузчик и " -#~ "микропрограмма EFI, которая поддерживает его, получают целую файловую " -#~ "систему для хранения файлов, необходимых для загрузки машины. Это значит, " -#~ "что системный диск на системе IA-64 содержит дополнительный дисковый " -#~ "раздел, выделенный под EFI, вместо простой MBR или загрузочного сектора " -#~ "на обычных системах." - -#~ msgid "" -#~ "The Debian Installer CD contains a small EFI partition where the " -#~ "ELILO 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 "" -#~ "Компакт-диск Debian содержит небольшую версию раздела EFI, в котором " -#~ "находятся программа ELILO, её файл конфигурации, ядро " -#~ "программы установки и начальная файловая система (initrd). Работающая " -#~ "система тоже содержит раздел EFI, в котором располагаются необходимые для " -#~ "загрузки системы файлы. Эти файлы доступны для чтения из командной " -#~ "оболочки EFI Shell, как описано ниже." - -#~ msgid "" -#~ "Most of the details of how ELILO 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 ELILO 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 "" -#~ "Большинство деталей того, как ELILO на самом деле " -#~ "загружает и запускает систему, прозрачны для программы установки. Однако, " -#~ "программа установки должна настроить раздел EFI перед установкой базовой " -#~ "системы. В противном случае, установка ELILO " -#~ "завершится неудачно, что сделает систему незагружаемой. Раздел EFI " -#~ "создаётся и форматируется на этапе разметки дисков процесса установки, " -#~ "перед загрузкой пакетов на системный диск. На этапе разметки дисков также " -#~ "проверяется существование пригодного к использованию раздела EFI перед " -#~ "тем, как разрешить установке продолжиться." - -#~ 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, Boot " -#~ "Option Maintenance Menu and EFI Shell (Built-in). 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 "" -#~ "Системный загрузчик EFI запускается на последнем шаге инициализации " -#~ "микропрограммы. Он отображает список меню, из которого пользователь может " -#~ "выбрать вариант. В зависимости от модели системы и установленных " -#~ "программ, это меню может выглядеть по-разному. Должно быть отображено два " -#~ "пункта меню, Boot Option Maintenance Menu и " -#~ "EFI Shell (Built-in). Использование первого " -#~ "предпочтительнее, однако , если он недоступен или компакт-диск по каким-" -#~ "то причинам не загрузился с ним, используйте второй." - -#~ msgid "IMPORTANT" -#~ msgstr "ВАЖНО" - -#~ 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 exit at the shell prompt." -#~ msgstr "" -#~ "Системный загрузчик EFI выполнит команду загрузки по умолчанию, обычно из " -#~ "первого пункта меню, через заданное число секунд. На это указывает " -#~ "обратный отсчёт внизу экрана. Как только время закончится и запустится " -#~ "система по умолчанию, для продолжения установки вам придётся " -#~ "перезагрузить машину. Если командой по умолчанию является EFI Shell, то " -#~ "вы можете вернуться в системный загрузчик выполнив exit из командной строки." - -#~ msgid "Option 1: Booting from the Boot Option Maintenance Menu" -#~ msgstr "Вариант 1: Загрузка из Boot Option Maintenance Menu" - -#~ 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 "" -#~ "Вставьте CD в DVD/CD привод и перезагрузите машину. После завершения " -#~ "инициализации системы firmware покажет страницу системного загрузчика EFI " -#~ "и меню." - -#~ msgid "" -#~ "Select Boot Maintenance Menu from the menu with the " -#~ "arrow keys and press ENTER. This will display a new " -#~ "menu." -#~ msgstr "" -#~ "Выберите Boot Maintenance Menu из меню с помощью " -#~ "клавиш управления курсором и нажмите ENTER. Вы " -#~ "попадёте в следующее меню." - -#~ msgid "" -#~ "Select Boot From a File from the menu with the arrow " -#~ "keys and press ENTER. This will display a list of " -#~ "devices probed by the firmware. You should see two menu lines containing " -#~ "either the label Debian Inst [Acpi ... or " -#~ "Removable Media Boot. If you examine the rest of the " -#~ "menu line, you will notice that the device and controller information " -#~ "should be the same." -#~ msgstr "" -#~ "Выберите Boot From a File из меню с помощью клавиш " -#~ "управления курсором и нажмите ENTER. Вы увидите список " -#~ "устройств, протестированных firmware. Вы должны увидеть две строки меню, " -#~ "содержащих или Debian Inst [Acpi ... или " -#~ "Removable Media Boot. Если вы посмотрите на остальную " -#~ "часть строки меню, то заметите, что информация об устройстве и " -#~ "контроллере будет одинаковой." - -#~ msgid "" -#~ "You can choose either of the entries that refer to the CD/DVD drive. " -#~ "Select your choice with the arrow keys and press ENTER. If you choose Removable Media Boot the " -#~ "machine will immediately start the boot load sequence. If you choose " -#~ "Debian Inst [Acpi ... instead, it will display a " -#~ "directory listing of the bootable portion of the CD, requiring you to " -#~ "proceed to the next (additional) step." -#~ msgstr "" -#~ "Вы можете выбрать одну из записей, которые указывают на CD/DVD привод. " -#~ "Выделите одну с помощью клавиш управления курсором и нажмите " -#~ "ENTER. Если вы выберете Removable Media Boot, то машина немедленно запустит процедуру начальной загрузки. " -#~ "Если вы выберете Debian Inst [Acpi ..., то появится " -#~ "список частей CD, с которых можно загрузиться и потребуется выполнить " -#~ "следующий (дополнительный) шаг." - -#~ msgid "" -#~ "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " -#~ "Removable Media Boot] on the next to the last line. Select this " -#~ "line with the arrow keys and press ENTER. This will " -#~ "start the boot load sequence." -#~ msgstr "" -#~ "Этот шаг нужен только если вы выбрали Debian Inst [Acpi .... Список также появится после строки [Treat like " -#~ "Removable Media Boot]. Выберите эту строку с помощью клавиш " -#~ "управления курсором и нажмите ENTER.Это запустит " -#~ "процедуру начальной загрузки." - -#~ 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 "" -#~ "Эти шаги запустят начальный загрузчик Debian, которая выведет страницу " -#~ "меню для выбора загружаемого ядра и параметров. Чтобы продолжить, " -#~ "выберите ядро и параметры." - -#~ msgid "Option 2: Booting from the EFI Shell" -#~ msgstr "Вариант 2: Загрузка из EFI Shell" - -#~ 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 EFI Shell [Built-in]. Boot the Debian Installer " -#~ "CD with the following steps:" -#~ msgstr "" -#~ "Если по каким-то причинам вариант 1 не сработал, перезагрузите машину и " -#~ "когда появится меню системного загрузчика EFI, то в нём должен быть ещё " -#~ "один пунктEFI Shell [Built-in]. Загрузите программу " -#~ "установки Debian с CD с помощью следующих шагов:" - -#~ 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 "" -#~ "Вставьте CD в DVD/CD привод и перезагрузите машину. После завершения " -#~ "инициализации системы firmware покажет страницу системного загрузчика EFI " -#~ "и меню." - -#~ msgid "" -#~ "Select EFI Shell from the menu with the arrow keys and " -#~ "press ENTER. 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 fsn:. All " -#~ "other recognized partitions will be named blkn:. If you inserted the CD just before entering the " -#~ "shell, this may take a few extra seconds as it initializes the CD drive." -#~ msgstr "" -#~ "Выберите EFI Shell из меню с помощью клавиш управления " -#~ "курсором и нажмите ENTER. EFI Shell просканирует все " -#~ "устройства, с которых можно загрузиться и покажет их в консоли, перед " -#~ "приглашением к вводу из командной строки. Распознанные загрузочные " -#~ "разделы устройств отображаются как fsn:. Все остальные распознанные разделы называются " -#~ "blkn:. Если вы вставили " -#~ "CD только перед входом в EFI shell, то может потребоваться несколько " -#~ "дополнительных секунд для инициализации привода компакт-дисков." - -#~ msgid "" -#~ "Examine the output from the shell looking for the CDROM drive. It is most " -#~ "likely the fs0: device although other devices with " -#~ "bootable partitions will also show up as fsn." -#~ msgstr "" -#~ "Найдите в выводе EFI shell привод компакт-дисков. По всей вероятности " -#~ "устройство называется fs0:, хотя другие устройства с " -#~ "загрузочными разделами тоже могут отображаться как " -#~ "fsn." - -#~ msgid "" -#~ "Enter fsn: and press " -#~ "ENTER to select that device where n is the partition number for the CDROM. The shell will now " -#~ "display the partition number as its prompt." -#~ msgstr "" -#~ "Чтобы выбрать устройство, введите fsn:" -#~ " и нажмите ENTER, где n номер раздела для CDROM. EFI shell теперь покажет этот номер " -#~ "в своём приглашении." - -#~ msgid "" -#~ "Enter elilo and press ENTER. This " -#~ "will start the boot load sequence." -#~ msgstr "" -#~ "Введите elilo и нажмите ENTER. Это " -#~ "запустит процедуру начальной загрузки." - -#~ 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot " -#~ "kernel and options." -#~ msgstr "" -#~ "Как и в варианте 1, эти шаги запускают начальный загрузчик Debian, " -#~ "который показывает страницу меню для выбора загружаемого ядра и " -#~ "параметров. Также вы можете ввести короткую команду " -#~ "fsn:elilo в командной " -#~ "строке.Чтобы продолжить, выберите ядро и параметры." - -#~ msgid "Installing using a Serial Console" -#~ msgstr "Установка с консоли на последовательном порту" - -#~ 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 [BAUD baud serial console], where BAUD " -#~ "is the speed of your serial console. Menu items for the most typical baud " -#~ "rate settings on the ttyS0 device are preconfigured." -#~ msgstr "" -#~ "Вы можете выбрать выполнение установки с помощью монитора и клавиатуры " -#~ "или через последовательный порт. Чтобы использовать монитор/клавиатурную " -#~ "установку, выберите пункт содержащий строку [VGA console]. Для установки " -#~ "через последовательный порт, выберите пункт, содержащий строку " -#~ "[BAUD baud serial console], где " -#~ "BAUD это скорость вашего последовательного " -#~ "порта. Типичные настройки скорости устройства ttyS0 выделены в отдельные " -#~ "пункты меню." - -#~ 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 baud " -#~ "at the EFI shell." -#~ msgstr "" -#~ "В большинстве случаев вам нужно чтобы скорость программы установки была " -#~ "равной с подключённой консолью EFI. Если вы не знаете какой она должна " -#~ "быть, то можете получить скорость с помощью команды baud в EFI shell." - -#~ 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 console=ttyS1,57600n8 into the Boot: text window." -#~ msgstr "" -#~ "Если в меню нет пунктов со скоростями для последовательного порта или нет " -#~ "скорости, которая вам требуется, то вы можете изменить настройки консоли " -#~ "одного из существующих пунктов меню. Например, чтобы использовать на " -#~ "консоли 57600 бод через устройство ttyS1, введите " -#~ "console=ttyS1,57600n8 в текстовом окне с приглашением " -#~ "Boot:." - -#~ 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 Params help menu for instructions on starting the installer in Text " -#~ "Mode." -#~ msgstr "" -#~ "Большинство машин IA-64 продаётся настроенными по умолчанию консолями на " -#~ "9600 бод. Эта настройка довольно медленна, и займёт значительное время " -#~ "для прорисовки каждого экрана при обычном процессе установки. Вам, " -#~ "вероятно, стоит увеличить скорость, используемую при установке или " -#~ "выполнять установку в текстовом режиме. Смотрите в меню помощи " -#~ "Params инструкции по запуску программы установки в " -#~ "текстовом режиме." - -#~ 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 "" -#~ "Если вы выберете неверный тип консоли, то сможете выбрать ядро и задать " -#~ "параметры, но после запуска ядра через монитор и клавиатуру станет " -#~ "невозможно работать и потребуется перезапуск перед началом установки." - -#~ msgid "Selecting the Boot Kernel and Options" -#~ msgstr "Выбор загружаемого ядра и параметров" - -#~ msgid "" -#~ "The boot loader will display a form with a menu list and a text window " -#~ "with a Boot: 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 General help " -#~ "screen explains the menu choices and the Params " -#~ "screen explains the common command line options." -#~ msgstr "" -#~ "Начальный загрузчик выводит меню и текстовое окно с приглашением " -#~ "Boot:. Клавишами управления курсором выбирается " -#~ "строка меню, а в текстовое окно вводится всё набранное на клавиатуре. " -#~ "Есть также экраны с помощью, в которые можно попасть нажав " -#~ "соответствующую функциональную клавишу. На экране помощи " -#~ "General объясняются пункты меню, а " -#~ "экранParams рассказывает об общих параметрах " -#~ "командной строки." - -#~ msgid "" -#~ "Consult the General help screen for the " -#~ "description of the kernels and install modes most appropriate for your " -#~ "installation. You should also consult " -#~ "below for any additional parameters that you may want to set in the " -#~ "Boot: 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 "" -#~ "Прочитав экран помощи General, выберите ядро и " -#~ "режим установки, которые наиболее вам подходят. Также вы должны прочитать " -#~ "в про любой дополнительный параметр, " -#~ "который вам может потребоваться ввести в приглашении Boot:. Выбираемая версия ядра будет использована для процесса " -#~ "установки и в установленной системе. Если вы испытываете проблемы с ядром " -#~ "во время установки, то скорее всего вы получите те же проблемы в " -#~ "установленной системе. В следующих двух шагах выбирается и запускается " -#~ "установка:" - -#~ msgid "" -#~ "Select the kernel version and installation mode most appropriate to your " -#~ "needs with the arrow keys." -#~ msgstr "" -#~ "С помощью клавиш управления курсором выберите наиболее подходящие вам " -#~ "версию ядра и режим установки." - -#~ 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 "" -#~ "Введите любые параметры, набрав их с клавиатуры. Текст будет отображаться " -#~ "прямо в текстовом окне. Здесь же задаются параметры ядра (такие как " -#~ "консоль на последовательном порту)." - -#~ msgid "" -#~ "Press ENTER. 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 "" -#~ "Нажмите ENTER. Загрузится и запустится ядро. Ядро " -#~ "выведет обычные сообщения инициализации, а затем появится первый экран " -#~ "программы установки Debian." - -#~ msgid "" -#~ "Proceed to the next chapter to continue the installation where you will " -#~ "set up the language locale, network, and disk partitions." -#~ msgstr "" -#~ "Переходите к следующей главе, чтобы продолжить процесс установки, где вы " -#~ "настроите язык, сеть и дисковые разделы." - -#~ msgid "" -#~ "Booting an IA-64 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 "" -#~ "Загрузка системы IA-64 по сети похожа на загрузку с CD. Единственное " -#~ "отличие — это способ загрузки ядра. Менеджер загрузки EFI может " -#~ "загружать и запускать программы с сервера из сети. Как только ядро " -#~ "установки загружено и запустилось, установка системы происходит также как " -#~ "и с CD за исключением, того что пакеты базовой установки будут получены " -#~ "по сети, а не с привода CD." - -#~ msgid "" -#~ "Network booting an IA-64 system requires two architecture-specific " -#~ "actions. On the boot server, DHCP and TFTP must be configured to deliver " -#~ "elilo. On the client a new boot option must be defined " -#~ "in the EFI boot manager to enable loading over a network." -#~ msgstr "" -#~ "Для загрузки по сети системы IA-64 требуется два специальных действия. " -#~ "DHCP и TFTP на загрузочном сервере должны быть настроены на доставку " -#~ "elilo. На клиенте должен быть задан дополнительный " -#~ "параметр загрузки в менеджере загрузки EFI, включающий загрузку по сети." - -#~ msgid "Configuring the Server" -#~ msgstr "Настройка сервера" - -#~ msgid "" -#~ "A suitable TFTP entry for network booting an IA-64 system looks something " -#~ "like this: \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" -#~ " Note that the goal is to get elilo." -#~ "efi running on the client." -#~ msgstr "" -#~ "Соответствующая запись TFTP для загрузки по сети системы IA-64 выглядит " -#~ "так: \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" -#~ " Заметьте, что цель — получить " -#~ "запущенный elilo.efi на клиенте." - -#~ msgid "" -#~ "Extract the netboot.tar.gz file into the directory " -#~ "used as the root for your tftp server. Typical tftp root directories " -#~ "include /var/lib/tftp and /tftpboot. This will create a debian-installer " -#~ "directory tree containing the boot files for an IA-64 system." -#~ msgstr "" -#~ "Распакуйте файл netboot.tar.gz в каталог, " -#~ "используемый как корневой на tftp сервере. Обычно корень tftp содержится " -#~ "в /var/lib/tftp или /tftpboot. " -#~ "Создастся дерево каталогов debian-installer, " -#~ "содержащее загрузочные файлы для системы IA-64." - -#~ msgid "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" -#~ msgstr "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" - -#~ msgid "" -#~ "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should " -#~ "you need to make changes to this file, you can find it in the " -#~ "debian-installer/ia64/ 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 .conf " -#~ "instead of elilo.conf. See documentation provided in " -#~ "the elilo package for details." -#~ msgstr "" -#~ "Файл netboot.tar.gz содержит файл elilo." -#~ "conf, который должен работать на большинстве машин. Однако, " -#~ "если вам нужно изменить этот файл, то он находится в каталоге " -#~ "debian-installer/ia64/. Можно создать различные " -#~ "конфигурационные файлы для различных клиентов, назвав их по IP-адресу " -#~ "клиента, записанном в шестнадцатеричной системе и с суффиксом ." -#~ "conf. Подробней смотрите документацию в пакете " -#~ "elilo." - -#~ msgid "Configuring the Client" -#~ msgstr "Настройка клиента" - -#~ msgid "" -#~ "To configure the client to support TFTP booting, start by booting to EFI " -#~ "and entering the Boot Option Maintenance Menu. " -#~ " Add a boot option. " -#~ " You should see one or more lines with the text " -#~ "Load File [Acpi()/.../Mac()]. 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. Name " -#~ "the entry Netboot or something similar, save, and " -#~ "exit back to the boot options menu. " -#~ "You should see the new boot option you just created, and selecting it " -#~ "should initiate a DHCP query, leading to a TFTP load of elilo." -#~ "efi from the server." -#~ msgstr "" -#~ "Для настройки клиента на загрузку по TFTP, загрузитесь в EFI и войдите в " -#~ "Boot Option Maintenance Menu. " -#~ " Add a boot option. " -#~ "Там вы должны увидеть одну или более строк с текстом Load " -#~ "File [Acpi()/.../Mac()]. Если есть более одной строки, " -#~ "выберите ту, которая содержит MAC адрес интерфейса с которого вы будете " -#~ "загружаться. Используйте клавиши стрелок, затем нажмите enter. Введите имя записи Netboot и нечто подобное, сохраните, и выйдите обратно в загрузочное " -#~ "меню. Вы должны увидеть только что " -#~ "созданную запись, а её выбор должен инициировать DHCP запрос, после чего " -#~ "загрузку по TFTP файла elilo.efi с сервера." - -#~ 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 "" -#~ "Системный загрузчик покажет своё приглашение после получения и обработки " -#~ "своего файла настройки. С этого момента установка продолжится также как и " -#~ "установка с CD. Выберите пункт загрузки, который приведён выше и когда " -#~ "ядро полностью установится из сети, запустится программа установки Debian." - -#~ msgid "Choosing an Installation Method" -#~ msgstr "Выбор способа установки" - -#~ 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 "" -#~ "На некоторых субархитектурах &arch-title; есть вариант загрузки с " -#~ "использованием либо ядра linux 2.4.x, либо 2.2.x. Когда такой выбор " -#~ "существует, попробуйте ядро 2.4.x. Программа установки должна требовать " -#~ "меньше памяти, когда используется ядро 2.4.x, потому что поддержка 2.2.x " -#~ "требует ramdisk фиксированного размера, а 2.4.x использует tmpfs." - -#~ msgid "" -#~ "If you are using a 2.2.x linux kernel, then you need to use the " -#~ "&ramdisksize; kernel parameter." -#~ msgstr "" -#~ "Если вы используете ядро версии 2.2.x, может потребоваться установить " -#~ "параметр ядра &ramdisksize;." - -#~ msgid "" -#~ "Make sure root=/dev/ram is one of your kernel " -#~ "parameters." -#~ msgstr "" -#~ "Убедитесь, что одним из параметров вашего ядра является root=/" -#~ "dev/ram." - -#~ msgid "" -#~ "If you're having trouble, check cts's " -#~ "&arch-title; debian-installer FAQ." -#~ msgstr "" -#~ "При возникновении трудностей почитайте cts's &arch-title; debian-installer FAQ." - -#~ msgid "Amiga" -#~ msgstr "Amiga" - -#~ msgid "" -#~ "The only method of installation available to amiga is the hard drive (see " -#~ "). In other words the cdrom is " -#~ "not bootable." -#~ msgstr "" -#~ "Единственным способом установки на amiga является жёсткий диск (смотрите " -#~ "). Другими словами, с компакт-" -#~ "диска загрузиться не удастся." - -#~ msgid "" -#~ "Amiga does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Amiga в данный момент не работает с bogl, так что если вы видите ошибки " -#~ "bogl, добавьте параметр ядра fb=false." - -#~ msgid "Atari" -#~ msgstr "Atari" - -#~ msgid "" -#~ "The installer for atari may be started from either the hard drive (see " -#~ ") or from floppies (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "Программа установки для atari может быть запущена с жёсткого диска " -#~ "(смотрите ) или с дискет (смотрите ). Другими словами, с компакт-" -#~ "диска загрузиться не удастся." - -#~ msgid "" -#~ "Atari does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Atari в данный момент не работает с bogl, так что если вы видите ошибки " -#~ "bogl, добавьте параметр ядра fb=false." - -#~ msgid "BVME6000" -#~ msgstr "BVME6000" - -#~ msgid "" -#~ "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." -#~ msgstr "" -#~ "Программа установки для BVME6000 может быть запущена с компакт-диска " -#~ "(смотрите ), с дискет (смотрите ) или по сети (смотрите )." - -#~ msgid "Macintosh" -#~ msgstr "Macintosh" - -#~ msgid "" -#~ "The only method of installation available to mac is from the hard drive " -#~ "(see ). In other words the " -#~ "cdrom is not bootable. Macs do not have a working 2.4.x kernel." -#~ msgstr "" -#~ "Единственным способом установки на mac является жёсткий диск (смотрите " -#~ "). Другими словами, с компакт-" -#~ "диска загрузиться не удастся. Для mac нет работоспособного " -#~ "ядра 2.4.x." - -#~ msgid "" -#~ "If your hardware uses a 53c9x-based scsi bus, then you may need to " -#~ "include the kernel parameter mac53c9x=1,0. " -#~ "Hardware with two such scsi buses, such as the Quadra 950, will need " -#~ "mac53c9x=2,0 instead. Alternatively, the parameter " -#~ "can be specified as mac53c9x=-1,0 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 "" -#~ "Если в вашем аппаратном обеспечении используется scsi шина, основанная на " -#~ "чипе 53c9x, то вам может понадобиться добавить параметр ядра " -#~ "mac53c9x=1,0. Для аппаратуры с двумя scsi шинами, " -#~ "например, Quadra 950, нужно указать mac53c9x=2,0. " -#~ "Или же можно указать параметр mac53c9x=-1,0, при " -#~ "котором автоопределение остаётся включённым, но запрещаются SCSI " -#~ "отключения. Заметим, что такой параметр требуется указывать только если " -#~ "имеется более одного жёсткого диска; без параметра система будет работать " -#~ "быстрее." - -#~ msgid "MVME147 and MVME16x" -#~ msgstr "MVME147 и MVME16x" - -#~ msgid "" -#~ "The installer for MVME147 and MVME16x may be started from either floppies " -#~ "(see ) or the net (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "Программа установки для MVEM147 и MVEM16x может быть запущена с дискет" -#~ "(смотрите ) или из сети (смотрите " -#~ "). Другими словами, с компакт-" -#~ "диска загрузиться не удастся." - -#~ msgid "Q40/Q60" -#~ msgstr "Q40/Q60" - -#~ msgid "" -#~ "The only method of installation available to Q40/Q60 is from the hard " -#~ "drive (see ). In other words " -#~ "the cdrom is not bootable." -#~ msgstr "" -#~ "Единственным способом установки на Q40/Q60 является жёсткий диск " -#~ "(смотрите ). Другими словами, с " -#~ "компакт-диска загрузиться не удастся." - -#~ msgid "Booting from a Hard Disk" -#~ msgstr "Загрузка с жёсткого диска" +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"Предполагается, что вы уже получили образы дискет и сделали из них " +"загрузочные дискеты как описано в ." -# index.docbook:1664, index.docbook:2162 -#~ 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:949 +#, 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 "" +"Для загрузки программы установки с дискет, вставьте первую из них в " +"дисковод, выключите систему как обычно и включите питание." -# index.docbook:1670, index.docbook:2168 -#~ msgid "" -#~ "To boot the installer from hard disk, you will have already completed " -#~ "downloading and placing the needed files in ." -#~ msgstr "" -#~ "Чтобы загрузить программу установки с жёсткого диска, вы уже должны были " -#~ "скачать и положить в нужное место требуемые файлы, как описано в ." - -#~ 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 MANIFEST for details)." -#~ msgstr "" -#~ "Как минимум шесть различных ramdisk могут быть использованы для загрузки " -#~ "с жёсткого диска, каждый из них имеет три различных типа с поддержкой и " -#~ "без ядра версии 2.2.x (смотрите MANIFEST)." - -#~ msgid "" -#~ "The three different types of ramdisks are cdrom, " -#~ "hd-media, and nativehd. These " -#~ "ramdisks differ only in their source for installation packages. The " -#~ "cdrom ramdisk uses a cdrom to get debian-installer " -#~ "packages. The hd-media ramdisk uses an iso image " -#~ "file of a cdrom currently residing on a hard disk. Finally, the " -#~ "nativehd ramdisk uses the net to install packages." -#~ msgstr "" -#~ "Есть три различных типа ramdisk: cdrom, hd-" -#~ "media и nativehd. Они отличаются только " -#~ "источниками установки пакетов. cdrom ramdisk " -#~ "использует cdrom для получения пакетов debian-installer .hd-" -#~ "media ramdisk использует файл iso образа cdrom, расположенный " -#~ "на жёстком диске. И наконец, nativehd ramdisk " -#~ "использует сеть для получения пакетов." - -#~ msgid "Booting from AmigaOS" -#~ msgstr "Загрузка из AmigaOS" - -#~ msgid "" -#~ "In the Workbench, start the Linux installation process " -#~ "by double-clicking on the StartInstall icon in the " -#~ "debian directory." -#~ msgstr "" -#~ "В Workbench, запустите процесс установки Linux двойным " -#~ "нажатием на иконку StartInstall в каталоге " -#~ "debian." - -#~ 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 ." -#~ msgstr "" -#~ "Возможно, вам придётся дважды нажать клавишу &enterkey; после того как " -#~ "программа установки Amiga выведет некоторую отладочную информацию в окно. " -#~ "После этого, через несколько секунд, экран станет серым. Затем, должен " -#~ "появиться чёрный экран с белым текстом отладочной информации ядра. Эти " -#~ "экраны могут проскочить очень быстро и вы не сможете их прочесть, но это " -#~ "нормально. Через пару секунд должна автоматически загрузиться программа " -#~ "установки, так что вы можете продолжить чтение руководства с ." - -#~ msgid "Booting from Atari TOS" -#~ msgstr "Загрузка из Atari TOS" - -#~ msgid "" -#~ "At the GEM desktop, start the Linux installation process by double-" -#~ "clicking on the bootstra.prg icon in the " -#~ "debian directory and clicking Ok at the program options dialog box." -#~ msgstr "" -#~ "На рабочем столе GEM, процесс установки Linux запускается двойным " -#~ "нажатием на иконку bootstra.prg в каталоге " -#~ "debian и нажатием Ok в окне " -#~ "диалога выбора параметров." - -#~ 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 ." -#~ msgstr "" -#~ "Возможно, вам придётся дважды нажать клавишу &enterkey; после того как " -#~ "программа установки Atari выведет некоторую отладочную информацию в окно. " -#~ "После этого, через несколько секунд, экран станет серым. Затем, должен " -#~ "появиться чёрный экран с белым текстом отладочной информации ядра. Эти " -#~ "экраны могут проскочить очень быстро и вы не сможете их прочесть, но это " -#~ "нормально. Через пару секунд должна автоматически загрузиться программа " -#~ "установки, так что вы может продолжить чтение руководства с ." - -#~ msgid "Booting from MacOS" -#~ msgstr "Загрузка из MacOS" - -#~ msgid "" -#~ "You must retain the original Mac system and boot from it. It is " -#~ "essential that, when booting MacOS in preparation " -#~ "for booting the Penguin linux loader, you hold the shift " -#~ "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 "" -#~ "Вы должны оставить изначальную Mac систему и загрузиться из неё. " -#~ "Существенная деталь: когда MacOS приготовится " -#~ "загрузить загрузчик Penguin linux, держите нажатой клавишу shift, чтобы предотвратить загрузку расширений. Если вы не используете " -#~ "MacOS кроме как для загрузки linux, то можете добиться того же удалив все " -#~ "расширения из Mac System Folder. Иначе, расширения могут оказаться " -#~ "загруженными, что вызовет проблемы запуска ядра linux." - -#~ msgid "" -#~ "Macs require the Penguin bootloader. If you do not " -#~ "have the tools to handle a Stuffit archive, &penguin19." -#~ "hfs; is an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." -#~ msgstr "" -#~ "Для Mac нужен системный загрузчик Penguin. Если у вас " -#~ "нет программ для работы с архивом Stuffit, " -#~ "воспользуйтесь &penguin19.hfs; — это образ диска hfs с " -#~ "распакованным Penguin. В описано, как скопировать этот образ на дискету." - -#~ msgid "" -#~ "At the MacOS desktop, start the Linux installation process by double-" -#~ "clicking on the Penguin Prefs icon in the " -#~ "Penguin directory. The Penguin " -#~ "booter will start up. Go to the Settings item " -#~ "in the File menu, click the Kernel tab. Select the kernel (vmlinuz) and " -#~ "ramdisk (initrd.gz) images in the install directory by clicking on the corresponding buttons in the upper " -#~ "right corner, and navigating the file select dialogs to locate the files." -#~ msgstr "" -#~ "Для запуска процесса установки Linux на рабочем столе MacOS , выполните " -#~ "двойной щелчок по иконке Penguin Prefs в каталоге " -#~ "Penguin. Запустится загрузчик Penguin. Выберите Settings из меню " -#~ "File, щёлкните по вкладке Kernel. " -#~ "Выберите образы ядра (vmlinuz) и ramdisk " -#~ "(initrd.gz) в каталоге install, " -#~ "нажав соответствующие кнопки в верхнем правом углу, чтобы добраться до " -#~ "диалогового окна выбора файлов." - -#~ msgid "" -#~ "To set the boot parameters in Penguin, choose File -" -#~ "> Settings..., then switch to the " -#~ "Options tab. Boot parameters may be typed in to the " -#~ "text entry area. If you will always want to use these settings, select " -#~ "File -> Save Settings as Default." -#~ msgstr "" -#~ "Для задания параметров в Penguin, выберите File -> " -#~ "Settings..., затем перейдите на вкладку " -#~ "Options. Параметры загрузки можно ввести в текстовом " -#~ "поле. Если вы всегда хотите передавать эти параметры, то выберите " -#~ "File -> Save Settings as Default." - -#~ msgid "" -#~ "Close the Settings dialog, save the settings and " -#~ "start the bootstrap using the Boot Now item in " -#~ "the File menu." -#~ msgstr "" -#~ "Закройте диалог Settings, сохраните настройки и " -#~ "запустите процедуру начала загрузки с помощью Boot Nowиз меню File." - -#~ msgid "" -#~ "The Penguin 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 ." -#~ msgstr "" -#~ "Загрузчик Penguin выдаст некоторую отладочную " -#~ "информацию в окно. После этого через несколько секунд, экран станет " -#~ "серым. Затем, должен появиться чёрный экран с белым текстом отладочной " -#~ "информации ядра. Эти экраны могут проскочить очень быстро и вы не сможете " -#~ "их прочесть, но это нормально. Через пару секунд должна автоматически " -#~ "загрузиться программа установки, так что вы может продолжить чтение " -#~ "руководства с ." - -#~ msgid "Booting from Q40/Q60" -#~ msgstr "Загрузка из Q40/Q60" - -#~ msgid "FIXME" -#~ msgstr "FIXME" - -#~ msgid "" -#~ "The installation program should start automatically, so you can continue " -#~ "below at ." -#~ msgstr "" -#~ "Программа должна запуститься автоматически, так что вы можете продолжить " -#~ "читать с ." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitecture that supports CD-ROM " -#~ "booting is the BVME6000." -#~ msgstr "" -#~ "В настоящий момент, единственной субархитектурой &arch-title;, " -#~ "поддерживающей загрузку с CD-ROM является BVME6000." - -#~ msgid "" -#~ "After booting the VMEbus systems you will be presented with the LILO " -#~ "Boot: 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 "" -#~ "После загрузки системы VMEbus появляется приглашение LILO Boot:. Для загрузки Linux и начала установки соответствующего " -#~ "программного обеспечения Debian с помощью эмулирующего vt102 терминала, в " -#~ "приглашении введите одно из:" - -#~ msgid "type i6000 &enterkey; to install a BVME4000/6000" -#~ msgstr "i6000 &enterkey; для установки на BVME4000/6000" - -#~ msgid "type i162 &enterkey; to install an MVME162" -#~ msgstr "i162 &enterkey; для установки на MVME162" - -#~ msgid "type i167 &enterkey; to install an MVME166/167" -#~ msgstr "i167 &enterkey; для установки на MVME166/167" - -#~ msgid "" -#~ "You may additionally append the string TERM=vt100 to use " -#~ "vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." -#~ msgstr "" -#~ "Вы можете дополнительно добавить строку TERM=vt100 , " -#~ "чтобы использовать эмуляцию терминала vt100, например, i6000 " -#~ "TERM=vt100 &enterkey;." - -#~ msgid "" -#~ "For most &arch-title; architectures, booting from a local filesystem is " -#~ "the recommended method." -#~ msgstr "" -#~ "Для большинства архитектур &arch-title; рекомендуется загрузка с " -#~ "локальной файловой системы." - -#~ msgid "" -#~ "Booting from the boot floppy is supported only for Atari and VME (with a " -#~ "SCSI floppy drive on VME) at this time." -#~ msgstr "" -#~ "На данный момент, загрузка с загрузочной дискеты поддерживается только " -#~ "для Atari и VME (с дисководом гибких дисков SCSI на VME)." +#. Tag: para +#: boot-installer.xml:955 +#, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"При установке с привода LS-120 (ATAPI версия), вам нужно задать виртуальный " +"путь к дисководу. Он указывается в параметре загрузки root=, где указывается устройство, на которое драйвер ide-floppy " +"назначит привод. Например, если привод LS-120 подключён как первое IDE " +"устройство (мастер) на второй кабель, введите в приглашении к загрузке " +"linux root=/dev/hdc." + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"Заметим, что на некоторых машинах, комбинация клавиш " +"Control Alt Delete не по-настоящему перезагружает машину, поэтому " +"рекомендуется аппаратная перезагрузка. Если вы производите " +"установку из существующей операционной системы (например, из DOS), то у вас " +"нет выбора. Иначе, выполните аппаратную перезагрузку перед загрузкой." + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"Далее, будет произведён доступ к дискете, и далее вы должны увидеть экран, " +"который показывает загрузку с дискеты и в конце появляется приглашение " +"boot:." -# index.docbook:1972, index.docbook:2015 -#~ msgid "SGI TFTP Booting" -#~ msgstr "Загрузка SGI с сервера TFTP" - -#~ msgid "" -#~ "After entering the command monitor use \n" -#~ "bootp():\n" -#~ " 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 netaddr environment variable. Type " -#~ "\n" -#~ "unsetenv netaddr\n" -#~ " in the command monitor to do this." -#~ msgstr "" -#~ "На компьютерах SGI для загрузки linux и начала установки Debianпосле " -#~ "входа в командный монитор используйте \n" -#~ "bootp():\n" -#~ ". Чтобы сделать это, вам может понадобиться " -#~ "сбросить переменную среды netaddr. Для этого наберите " -#~ "\n" -#~ "unsetenv netaddr\n" -#~ " в командном мониторе." +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"После нажатия &enterkey;, вы должны увидеть сообщение " +"Loading..., потом " +"Uncompressing Linux..., и затем несколько " +"экранов с информацией о найденном оборудовании. Подробную информацию об этом " +"этапе процесса загрузки можно найти в ." + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"После загрузки с загрузочной дискеты, вас попросят вставить дискету с " +"корневой файловой системой. Вставьте нужную дискету, нажмите &enterkey;, и " +"её содержимое загрузится в память. В конце автоматически запустится " +"программа установки debian-installer." + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "Есть несколько возможностей выполнить загрузку по TFTP на i386." + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "Сетевая карта или материнская плата с поддержкой PXE" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"Возможно, ваша сетевая карта (NIC) или материнская плата предоставляют " +"возможность загрузки через PXE. Так названа реализация TFTP загрузки от " +"компании Intel. В этом случае вы " +"можете настроить BIOS на загрузку по сети." + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "Сетевая карта с сетевым BootROM" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "" +"Возможно, что сетевая карта (NIC) предоставляет возможность загрузки по TFTP." -# index.docbook:1988, index.docbook:2035 -#~ msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" -#~ msgstr "Загрузка Broadcom BCM91250A и BCM91480B с сервера TFTP" - -#~ 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: " -#~ "\n" -#~ "ifconfig eth0 -auto\n" -#~ " Once you have obtained an IP address, you can " -#~ "load SiByl with the following command: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " 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 "" -#~ "На платах Broadcom BCM91250A и eBCM91480B с сервера TFTP загружается " -#~ "системный загрузчик SiByl, который затем загружает и запускает программу " -#~ "установки Debian. В большинстве случаев, сначала вам нужно получить IP-" -#~ "адрес по DHCP, но также возможно настроить адрес статически. Чтобы " -#~ "использовать DHCP, вы можете ввести следующую команду в строке " -#~ "приглашения CFE: \n" -#~ "ifconfig eth0 -auto\n" -#~ " После получения IP-адреса, вы можете " -#~ "загрузить SiByl с помощью следующей команды: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " Вместо приведённого в этом примере IP-адреса " -#~ "вам нужно указать или имя или IP-адрес TFTP сервера. После выполнения " -#~ "этой команды, программа установки будет загружена автоматически." +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Напишите нам (&email-debian-boot-list;) как вам удалось " +"сделать это. Пожалуйста, упомяните в заголовке этот документ." + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"Проект etherboot " +"предоставляет загрузочные дискеты и даже прошивки (bootrom) для TFTPboot." # index.docbook:2012, index.docbook:2491 -#~ msgid "Boot Parameters" -#~ msgstr "Параметры загрузки" - -#~ msgid "" -#~ "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." -#~ msgstr "" -#~ "На компьютерах SGI вы можете добавлять параметры загрузки в команду " -#~ "bootp(): в мониторе команд." - -#~ msgid "" -#~ "Following the bootp(): 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: \n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Further kernel parameters can be passed via " -#~ "append:" -#~ msgstr "" -#~ "После команды bootp(): вы можете задать путь и имя " -#~ "загружаемого файла, если вы не получаете это имя явно с bootp/dhcp " -#~ "сервера. Пример: \n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Дополнительные параметры ядра могут быть " -#~ "указаны через append:" - -#~ msgid "bootp(): append=\"root=/dev/sda1\"" -#~ msgstr "bootp(): append=\"root=/dev/sda1\"" - -#~ msgid "" -#~ "You cannot pass any boot parameters directly from the CFE prompt. " -#~ "Instead, you have to edit the /boot/sibyl.conf file " -#~ "on the TFTP server and add your parameters to the " -#~ "extra_args variable." -#~ msgstr "" -#~ "Вы не можете передавать параметры прямо из приглашения CFE. Вместо этого, " -#~ "вы должны отредактировать файл /boot/sibyl.conf на " -#~ "TFTP сервере и добавить ваши параметры в переменную " -#~ "extra_args." +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "Приглашение к загрузке" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"В самом начале загрузки программы установки на экране появится логотип " +"Debian и приглашение к загрузке: \n" +"Press F1 for help, or ENTER to boot:\n" +" В приглашении к загрузке вы можете или просто " +"нажать &enterkey; для загрузки программы установки с параметрами по " +"умолчанию, или ввести желаемый метод загрузки и, если нужно, загрузочные " +"параметры." + +#. Tag: para +#: boot-installer.xml:1078 +#, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"Информацию о доступных параметрах загрузки можно увидеть нажимая клавиши с " +"F2 по F8. При добавлении параметров " +"загрузки в командную строку убедитесь, что ввели метод загрузки (по " +"умолчанию linux) и пробел перед первым параметром " +"(например, linux fb=false)." + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"Если вы производите установку через удалённое управляющее устройство, " +"которое выводит текстовый интерфейс на VGA консоль, то скорее всего, вы не " +"увидите графическую начальную заставку перед загрузкой программы установки; " +"вы даже можете не увидеть приглашение к загрузке. Например, так будет на " +"устройствах с текстовыми консолями Compaq integrated Lights Out (iLO) и HP Integrated Remote Assistant (IRA). Можно " +"вслепую нажать F1, В некоторых случаях на таких устройствах " +"нужно ввести специальную комбинацию нажатий, которая работает как F1, " +"например, для IRA это Ctrl F , 1. , чтобы пропустить " +"этот экран и увидеть экран с подсказкой. После прохождения момента с " +"начальной заставкой и вывода экрана с подсказкой вводимые символы будут " +"отображаться как обычно. Чтобы указать программе установки не использовать " +"framebuffer при установке, нужно добавить параметр загрузки " +"fb=false, как описано в подсказке." + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "Содержимое компакт-диска" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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 "" +"Существует три основные вариации установочных компакт-дисков Debian. Диск-" +"визитка содержит минимальную установку, которая " +"помещается на носителе маленького формата. Он требует сетевого соединения " +"для установки остальной части базовой установки и создания пригодной для " +"работы системы. Диск сетевой установки содержит все " +"пакеты для базовой установки, но требует сетевого соединения с зеркалами " +"Debian для установки дополнительных пакетов, если вам хочется получить " +"полноценную систему. А весь комплект компакт-дисков Debian может установить " +"полноценную систему с большим выбором пакетов безо всякого доступа к сети." + +#. Tag: para +#: boot-installer.xml:1180 +#, 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 "" +"Архитектура IA-64 использует интерфейс следующего поколения Extensible " +"Firmware Interface (EFI) от Intel. В отличие от традиционного BIOS x86, " +"который ничего не знает о загрузочном устройстве кроме таблицы разделов и " +"главной загрузочной записи (MBR), EFI может читать и записывать файлы из " +"разделов отформатированных в FAT16 или FAT32. Это упрощает зачастую просто " +"чародейский процесс старта системы. Системный загрузчик и микропрограмма " +"EFI, которая поддерживает его, получают целую файловую систему для хранения " +"файлов, необходимых для загрузки машины. Это значит, что системный диск на " +"системе IA-64 содержит дополнительный дисковый раздел, выделенный под EFI, " +"вместо простой MBR или загрузочного сектора на обычных системах." + +#. Tag: para +#: boot-installer.xml:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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 "" +"Компакт-диск Debian содержит небольшую версию раздела EFI, в котором " +"находятся программа ELILO, её файл конфигурации, ядро " +"программы установки и начальная файловая система (initrd). Работающая " +"система тоже содержит раздел EFI, в котором располагаются необходимые для " +"загрузки системы файлы. Эти файлы доступны для чтения из командной оболочки " +"EFI Shell, как описано ниже." + +#. Tag: para +#: boot-installer.xml:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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 "" +"Большинство деталей того, как ELILO на самом деле " +"загружает и запускает систему, прозрачны для программы установки. Однако, " +"программа установки должна настроить раздел EFI перед установкой базовой " +"системы. В противном случае, установка ELILO завершится " +"неудачно, что сделает систему незагружаемой. Раздел EFI создаётся и " +"форматируется на этапе разметки дисков процесса установки, перед загрузкой " +"пакетов на системный диск. На этапе разметки дисков также проверяется " +"существование пригодного к использованию раздела EFI перед тем, как " +"разрешить установке продолжиться." + +#. Tag: para +#: boot-installer.xml:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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 "" +"Системный загрузчик EFI запускается на последнем шаге инициализации " +"микропрограммы. Он отображает список меню, из которого пользователь может " +"выбрать вариант. В зависимости от модели системы и установленных программ, " +"это меню может выглядеть по-разному. Должно быть отображено два пункта меню, " +"Boot Option Maintenance Menu и EFI Shell (Built-" +"in). Использование первого предпочтительнее, однако , если он " +"недоступен или компакт-диск по каким-то причинам не загрузился с ним, " +"используйте второй." + +#. Tag: title +#: boot-installer.xml:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "ВАЖНО" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" +"Системный загрузчик EFI выполнит команду загрузки по умолчанию, обычно из " +"первого пункта меню, через заданное число секунд. На это указывает обратный " +"отсчёт внизу экрана. Как только время закончится и запустится система по " +"умолчанию, для продолжения установки вам придётся перезагрузить машину. Если " +"командой по умолчанию является EFI Shell, то вы можете вернуться в системный " +"загрузчик выполнив exit из командной строки." + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "Вариант 1: Загрузка из Boot Option Maintenance Menu" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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 "" +"Вставьте CD в DVD/CD привод и перезагрузите машину. После завершения " +"инициализации системы firmware покажет страницу системного загрузчика EFI и " +"меню." -# index.docbook:1972, index.docbook:2015 -#~ msgid "Cobalt TFTP Booting" -#~ msgstr "Загрузка Cobalt с сервера TFTP" - -#~ 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 /nfsroot. 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 "" -#~ "Собственно говоря, Cobalt использует для загрузки NFS, а не TFTP. Вам " -#~ "потребуется установить NFS сервер и положить файлы программы установки в " -#~ "каталог /nfsroot. При загрузки Cobalt, нужно " -#~ "одновременно нажать левую и правую клавиши курсора и машина будет " -#~ "загружена по сети с NFS сервера. На экране будут показаны несколько " -#~ "параметров. Есть два метода установки:" - -#~ 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 "" -#~ "По SSH (по умолчанию): В этом случае, программа установки выполнит " -#~ "настройку сети по DHCP и запустит SSH сервер. Затем она покажет случайный " -#~ "пароль и другую информацию для входа (например, IP-адрес) на Cobalt LCD. " -#~ "После подключения к машине с помощью SSH клиента, вы можете начать " -#~ "установку." - -#~ 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 "" -#~ "Через последовательный порт: С помощью нуль-модемного кабеля, вы можете " -#~ "подключиться к последовательному порту Cobalt (на скорости 115200 bps) и " -#~ "выполнить установку. Этот способ не работает на машинах Qube 2700 " -#~ "(Qube1), так как они не имеют последовательного порта." - -#~ msgid "" -#~ "You cannot pass any boot parameters directly. Instead, you have to edit " -#~ "the /nfsroot/default.colo file on the NFS server and " -#~ "add your parameters to the args variable." -#~ msgstr "" -#~ "Вы не можете передать параметры загрузки напрямую. Вместо этого, вы " -#~ "должны отредактировать файл /nfsroot/default.colo на " -#~ "NFS сервере и добавить параметры в переменную args." - -#~ msgid "s390 Limitations" -#~ msgstr "Ограничения s390" - -#~ msgid "" -#~ "In order to run the installation system a working network setup and ssh " -#~ "session is needed on S/390." -#~ msgstr "" -#~ "Для запуска системы установки на S/390 необходима работающая настройка " -#~ "сети и ssh-сессия." - -#~ 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 an ssh session which will launch the standard " -#~ "installation system." -#~ msgstr "" -#~ "Процесс загрузки начинается с настройки сети, запрашивая у вас некоторые " -#~ "параметры. Если настройка прошла успешна, вы войдете в систему через ssh-" -#~ "сессию, которая запустит стандартную систему установки." +#. Tag: para +#: boot-installer.xml:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"Выберите Boot Maintenance Menu из меню с помощью клавиш " +"управления курсором и нажмите ENTER. Вы попадёте в " +"следующее меню." -# index.docbook:2012, index.docbook:2491 -#~ msgid "s390 Boot Parameters" -#~ msgstr "Параметры загрузки s390" - -#~ 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 Device Drivers and Installation Commands for more " -#~ "information about S/390-specific boot parameters." -#~ msgstr "" -#~ "На S/390 вы можете добавить параметры загрузки в файле parm. Этот файл " -#~ "может быть как в ASCII так и в EBCDIC формате. Подробную информацию о " -#~ "параметрах загрузки для S/390 читайте в Device Drivers and Installation Commands." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitectures that support CD-ROM " -#~ "booting are PReP and New World PowerMacs. On PowerMacs, hold the " -#~ "c key, or else the combination of Command, Option, Shift, and " -#~ "Delete keys together while booting to boot from the CD-" -#~ "ROM." -#~ msgstr "" -#~ "В настоящее время на &arch-title; только субархитектуры PReP и New World " -#~ "PowerMacs поддерживают загрузку с компакт-диска. На PowerMacs нажмите " -#~ "клавишу c, или комбинацию клавиш Command, Option, Shift, и " -#~ "Delete вместе во время загрузки для того, чтобы " -#~ "загрузиться с компакт-диска." - -#~ 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 "" -#~ "Компьютеры OldWorld Powermac не загружаются с компакт-диска Debian, " -#~ "потому что компьютеры OldWorld полагаются на присутствие на компакт-диске " -#~ "загрузочного драйвера Mac OS ROM, а свободно доступной версии этого " -#~ "драйвера нет. На всех системах OldWorld есть приводы для дискет, так что " -#~ "используйте дискету, чтобы запустить программу установки, а затем укажите " -#~ "ей компакт-диск с нужными файлами." - -#~ 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 for booting from the " -#~ "hard disk, except use the path to yaboot on the CD at " -#~ "the OF prompt, such as" -#~ msgstr "" -#~ "Если ваша система не загружается напрямую с компакт-диска, вы всё ещё " -#~ "можете использовать его для установки системы. На NewWorld вы также " -#~ "можете использовать команду OpenFirmware для загрузки с компакт-диска " -#~ "вручную. Следуйте инструкциям из для " -#~ "загрузки с жёсткого диска, за исключением использования пути к " -#~ "yaboot на компакт-диске в подсказке OF, такой как" - -#~ msgid "0 > boot cd:,\\install\\yaboot" -#~ msgstr "0 > boot cd:,\\install\\yaboot" - -#~ msgid "Booting from Hard Disk" -#~ msgstr "Загрузка с жёсткого диска" +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" +"Выберите Boot From a File из меню с помощью клавиш " +"управления курсором и нажмите ENTER. Вы увидите список " +"устройств, протестированных firmware. Вы должны увидеть две строки меню, " +"содержащих или Debian Inst [Acpi ... или " +"Removable Media Boot. Если вы посмотрите на остальную " +"часть строки меню, то заметите, что информация об устройстве и контроллере " +"будет одинаковой." + +#. Tag: para +#: boot-installer.xml:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" +"Вы можете выбрать одну из записей, которые указывают на CD/DVD привод. " +"Выделите одну с помощью клавиш управления курсором и нажмите ENTER. Если вы выберете Removable Media Boot, то " +"машина немедленно запустит процедуру начальной загрузки. Если вы выберете " +"Debian Inst [Acpi ..., то появится список частей CD, с " +"которых можно загрузиться и потребуется выполнить следующий (дополнительный) " +"шаг." + +#. Tag: para +#: boot-installer.xml:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" +"Этот шаг нужен только если вы выбрали Debian Inst [Acpi .... Список также появится после строки [Treat like Removable " +"Media Boot]. Выберите эту строку с помощью клавиш управления " +"курсором и нажмите ENTER.Это запустит процедуру начальной " +"загрузки." + +#. Tag: para +#: boot-installer.xml:1302 +#, 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 "" +"Эти шаги запустят начальный загрузчик Debian, которая выведет страницу меню " +"для выбора загружаемого ядра и параметров. Чтобы продолжить, выберите ядро и " +"параметры." + +#. Tag: title +#: boot-installer.xml:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "Вариант 2: Загрузка из EFI Shell" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" +"Если по каким-то причинам вариант 1 не сработал, перезагрузите машину и " +"когда появится меню системного загрузчика EFI, то в нём должен быть ещё один " +"пунктEFI Shell [Built-in]. Загрузите программу установки " +"Debian с CD с помощью следующих шагов:" + +#. Tag: para +#: boot-installer.xml:1324 +#, 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 "" +"Вставьте CD в DVD/CD привод и перезагрузите машину. После завершения " +"инициализации системы firmware покажет страницу системного загрузчика EFI и " +"меню." -# index.docbook:807, index.docbook:1949, index.docbook:2282, index.docbook:2442 -#~ msgid "Booting CHRP from OpenFirmware" -#~ msgstr "Загрузка CHRP из OpenFirmware" - -#~ msgid "Not yet written." -#~ msgstr "Ещё не написано." - -#~ msgid "Booting OldWorld PowerMacs from MacOS" -#~ msgstr "Загрузка OldWorld PowerMac из MacOS" - -#~ msgid "" -#~ "If you set up BootX in , you can use it " -#~ "to boot into the installation system. Double click the BootX application icon. Click on the Options " -#~ "button and select Use Specified RAM Disk. This will " -#~ "give you the chance to select the ramdisk.image.gz " -#~ "file. You may need to select the No Video Driver " -#~ "checkbox, depending on your hardware. Then click the Linux button to shut down MacOS and launch the installer." -#~ msgstr "" -#~ "Если вы настроите BootX в , то сможете " -#~ "использовать его для загрузки системы установки. Выполните двойной щелчок " -#~ "на иконке приложения BootX. Нажмите кнопку " -#~ "Options и выберите Use Specified RAM " -#~ "Disk. Это позволит выбрать файл ramdisk.image.gz. Вам может понадобиться установить галочку в No Video " -#~ "Driver, в зависимости от аппаратного обеспечения. Затем " -#~ "нажмите кнопку Linux для выключения MacOS и " -#~ "запуска программы установки." - -#~ msgid "Booting NewWorld Macs from OpenFirmware" -#~ msgstr "Загрузка NewWorld Mac из OpenFirmware" - -#~ msgid "" -#~ "You will have already placed the vmlinux, " -#~ "initrd.gz, yaboot, and " -#~ "yaboot.conf files at the root level of your HFS " -#~ "partition in . Restart the computer, " -#~ "and immediately (during the chime) hold down the Option, " -#~ "Command (cloverleaf/Apple), o, and " -#~ "f keys all together. After a few seconds you will be " -#~ "presented with the Open Firmware prompt. At the prompt, type " -#~ "\n" -#~ "0 > boot hd:x,yaboot\n" -#~ " replacing x 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 ide0: instead of hd:. In a few more seconds you will see a yaboot prompt " -#~ "\n" -#~ "boot:\n" -#~ " At yaboot's boot: prompt, " -#~ "type either install or install " -#~ "video=ofonly followed by a &enterkey;. The " -#~ "video=ofonly argument is for maximum " -#~ "compatibility; you can try it if install doesn't " -#~ "work. The Debian installation program should start." -#~ msgstr "" -#~ "Вы должны были уже скопировать файлы vmlinux, " -#~ "initrd.gz, yaboot и " -#~ "yaboot.conf в корень раздела HFS как описано в . Перезагрузите компьютер и быстро(во время " -#~ "звукового сигнала) одновременно зажмите клавиши Option, " -#~ "Command (cloverleaf/Apple), o и " -#~ "f. Через несколько секунд вы увидите приглашение Open " -#~ "Firmware. Наберите \n" -#~ "0 > boot hd:x,yaboot\n" -#~ " заменив x номером " -#~ "раздела HFS, на котором лежат файлы ядра и yaboot и нажмите &enterkey;. " -#~ "На некоторых машинах, вам нужно использовать ide0:, а не hd:. Ещё через несколько секунд " -#~ "вы увидите приглашение yaboot \n" -#~ "boot:\n" -#~ " В приглашении yaboot boot: " -#~ "введите или install или install " -#~ "video=ofonly и нажмите &enterkey;. Параметр " -#~ "video=ofonly нужен для максимальной совместимости; " -#~ "вы можете попробовать указать его, если install не " -#~ "сработает. После должна запуститься программа установки Debian." - -#~ msgid "Booting from USB memory stick" -#~ msgstr "Загрузка с карты памяти USB" - -#~ msgid "" -#~ "Currently, NewWorld PowerMac systems are known to support USB booting." -#~ msgstr "" -#~ "В настоящий момент системы NewWorld PowerMac можно загружать с USB " -#~ "устройств." - -#~ msgid "" -#~ "Make sure you have prepared everything from . 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 " -#~ "Command Option o f all together while booting (see " -#~ ")." -#~ msgstr "" -#~ "Проверьте, что вы сделали всё как написано в . Для загрузки системы Macintosh с карт памяти USB нужно " -#~ "использовать микропрограмму Open Firmware, так как по умолчанию Open " -#~ "Firmware не ищет загрузочные устройства среди USB носителей. Чтобы " -#~ "получить приглашение к вводу команд во время загрузки держите " -#~ "одновременно нажатыми клавиши Command " -#~ "Option o f " -#~ "(смотрите )." - -#~ msgid "" -#~ "You will need to work out where the USB storage device appears in the " -#~ "device tree, since at the moment ofpath cannot work " -#~ "that out automatically. Type dev / ls and " -#~ "devalias 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 usb0/disk, " -#~ "usb0/hub/disk, /pci@f2000000/usb@1b,1/" -#~ "disk@1, and /pci@f2000000/usb@1b,1/hub@1/disk@1 work." -#~ msgstr "" -#~ "Далее, вам необходимо выяснить, в каком месте дерева устройств появилась " -#~ "карта памяти USB, так как в настоящее время ofpath не " -#~ "может выяснить этого автоматически. Введите dev / ls и devalias в приглашении Open Firmware, " -#~ "чтобы получить список всех найденных устройств и их псевдонимов. У автора " -#~ "этого документа на системе различные типы карт памяти USB были доступны " -#~ "по следующим путям: usb0/disk, usb0/hub/" -#~ "disk, /pci@f2000000/usb@1b,1/disk@1 и " -#~ "/pci@f2000000/usb@1b,1/hub@1/disk@1." - -#~ msgid "" -#~ "Having worked out the device path, use a command like this to boot the " -#~ "installer: \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " The 2 matches the " -#~ "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot " -#~ "image earlier, and the ,\\\\:tbxi part instructs " -#~ "Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i." -#~ "e. yaboot) in the directory previously blessed with " -#~ "hattrib -b." -#~ msgstr "" -#~ "После выяснения пути к устройству, запустите команду загрузки программы " -#~ "установки: \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " Цифра 2 " -#~ "соответствует разделу Apple_HFS или Apple_Bootstrap, на который вы ранее " -#~ "скопировали загрузочный образ, а ,\\\\:tbxi " -#~ "говорит Open Firmware загружать из файла с типом HFS \"tbxi\" (то есть " -#~ "yaboot) из каталога ранее установленного с помощью " -#~ "hattrib -b." - -#~ msgid "" -#~ "The system should now boot up, and you should be presented with the " -#~ "boot: prompt. Here you can enter optional boot " -#~ "arguments, or just hit &enterkey;." -#~ msgstr "" -#~ "Система должна загрузиться и вы должны увидеть приглашение boot:. Здесь вы можете ввести необязательные параметры загрузки, или " -#~ "просто нажать &enterkey;." - -#~ 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 ." -#~ msgstr "" -#~ "Это новый метод загрузки и с ним могут возникнуть некоторые трудности на " -#~ "некоторых системах NewWorld. Если у вас есть проблемы, пожалуйста, " -#~ "отправьте отчёт об установке, как описано в ." - -#~ msgid "Currently, PReP and New World PowerMac systems support netbooting." -#~ msgstr "" -#~ "В настоящий момент, для систем PReP и New World PowerMac поддерживается " -#~ "загрузка по сети." - -#~ msgid "" -#~ "On machines with Open Firmware, such as NewWorld Power Macs, enter the " -#~ "boot monitor (see ) and use the " -#~ "command boot enet:0. PReP and CHRP boxes may have " -#~ "different ways of addressing the network. On a PReP machine, you should " -#~ "try boot server_ipaddr," -#~ "file,client_ipaddr." -#~ msgstr "" -#~ "На машинах с Open Firmware, например, NewWorld Power Mac, войдите в " -#~ "загрузочный монитор (смотрите ) " -#~ "и воспользуйтесь командой boot enet:0. Машины PReP и " -#~ "CHRP могут загружаться по сети другим способом. На машине PReP, вы должны " -#~ "попробовать boot server_ipaddr," -#~ "file,client_ipaddr." - -#~ 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 "" -#~ "Для &arch-title; поддерживается загрузка с дискет, хотя она применяется " -#~ "только для систем OldWorld. Системы NewWorld не имеют приводы гибких " -#~ "дисков, а с подключённых по USB приводов гибких дисков загрузка не " -#~ "поддерживается." - -#~ msgid "" -#~ "To boot from the boot-floppy-hfs.img floppy, place " -#~ "it in floppy drive after shutting the system down, and before pressing " -#~ "the power-on button." -#~ msgstr "" -#~ "Для загрузки с помощью дискеты boot-floppy-hfs.img, " -#~ "вставьте её в дисковод после выключения системы и перед включением " -#~ "питания." - -#~ 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 "" -#~ "Для тех, кто не знает как работать с дискетами на Macintosh: дискета " -#~ "вставленная в машину перед загрузкой, будет иметь приоритет при загрузке " -#~ "системы. Незагрузочная дискета будет извлечена из дисковода, а затем " -#~ "машина проверит на загружаемость разделы жёсткого диска." - -#~ msgid "" -#~ "After booting, the root.bin 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 "" -#~ "После загрузки, появится запрос дискеты root.bin. " -#~ "Вставьте соответствующую дискету и нажмите &enterkey;. Программа " -#~ "установки запустится автоматически после загрузки корневой файловой " -#~ "системы в память." +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" +"Выберите EFI Shell из меню с помощью клавиш управления " +"курсором и нажмите ENTER. EFI Shell просканирует все " +"устройства, с которых можно загрузиться и покажет их в консоли, перед " +"приглашением к вводу из командной строки. Распознанные загрузочные разделы " +"устройств отображаются как fsn:. Все остальные распознанные разделы называются " +"blkn:. Если вы вставили CD " +"только перед входом в EFI shell, то может потребоваться несколько " +"дополнительных секунд для инициализации привода компакт-дисков." + +#. Tag: para +#: boot-installer.xml:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" +"Найдите в выводе EFI shell привод компакт-дисков. По всей вероятности " +"устройство называется fs0:, хотя другие устройства с " +"загрузочными разделами тоже могут отображаться как " +"fsn." + +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"Чтобы выбрать устройство, введите fsn: и нажмите ENTER, где n номер раздела для CDROM. EFI shell теперь покажет этот номер в " +"своём приглашении." + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"Введите elilo и нажмите ENTER. Это " +"запустит процедуру начальной загрузки." -# index.docbook:2012, index.docbook:2491 -#~ msgid "PowerPC Boot Parameters" -#~ msgstr "Параметры загрузки PowerPC" - -#~ 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 " -#~ "video=atyfb:vmode:6 , which will select that mode " -#~ "for most Mach64 and Rage video hardware. For Rage 128 hardware, this " -#~ "changes to video=aty128fb:vmode:6 ." -#~ msgstr "" -#~ "Многие старые мониторы Apple работают в режиме 640x480 67Гц. Если на " -#~ "старом мониторе Apple изображение выводится перекошенным, попробуйте " -#~ "добавить параметр загрузки video=atyfb:vmode:6 , " -#~ "который включает этот режим на большинстве видеокарт Mach64 и Rage. Для " -#~ "Rage 128 нужно использовать параметр video=aty128fb:vmode:6." - -#~ msgid "" -#~ "On machines with OpenBoot, simply enter the boot monitor on the machine " -#~ "which is being installed (see ). Use " -#~ "the command boot net to boot from a TFTP and RARP " -#~ "server, or try boot net:bootp or boot " -#~ "net:dhcp to boot from a TFTP and BOOTP or DHCP server. Some " -#~ "older OpenBoot revisions require using the device name, such as " -#~ "boot le(); these probably don't support BOOTP nor " -#~ "DHCP." -#~ msgstr "" -#~ "На машинах с OpenBoot, просто войдите в загрузочный монитор машины, на " -#~ "которую производится установка (смотрите ). Используйте команду boot net для загрузки с " -#~ "TFTP и RARP сервера, или попробуйте boot net:bootp " -#~ "или boot net:dhcp для загрузки с TFTP и BOOTP или " -#~ "DHCP сервера. Некоторые старые версии OpenBoot требуют указывать имя " -#~ "устройства, например, boot le(); вероятно, на них " -#~ "не работает поддержка BOOTP и DHCP." - -#~ msgid "" -#~ "Most OpenBoot versions support the boot cdrom " -#~ "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 "" -#~ "Большинство версий OpenBoot поддерживают команду boot cdrom, которая является простым псевдонимом загрузки с устройства " -#~ "SCSI с ID 6 (или вторичного мастера для систем с IDE). Возможно придётся " -#~ "использовать настоящее имя устройства в старых версиях OpenBoot, которые " -#~ "не поддерживают эту специальную команду. Заметим, что при загрузке с CD-" -#~ "ROM на системах Sun4m (например, Sparc 10s и Sparc 20s) иногда возникают " -#~ "проблемы." - -#~ msgid "" -#~ "To boot from floppy on a Sparc, use \n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Be warned that the newer Sun4u (ultra) " -#~ "architecture does not support floppy booting. A typical error message is " -#~ "Bad magic number in disk label - Can't open disk label " -#~ "package. 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 "" -#~ "Для загрузки с дискеты на Sparc, используйте \n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Не забудьте, что новая архитектура Sun4u " -#~ "(ultra) не поддерживает загрузку с дискет. Обычно, выводится сообщение об " -#~ "ошибке: Bad magic number in disk label - Can't open disk " -#~ "label package. Кроме того, некоторые модели Sun4c (такие " -#~ "как IPX) не поддерживают сжатые образы дисков, поэтому загрузка с дискет " -#~ "также не поддерживается." - -#~ 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 ." -#~ msgstr "" -#~ "Некоторые Sparc (например, Ultra 10) имеют ошибку OBP, которая не даёт им " -#~ "загрузиться (они вообще отказываются загружаться). Соответствующее " -#~ "обновление OBP можно загрузить как продукт с ID 106121 с ." - -#~ msgid "" -#~ "If you are booting from the floppy, and you see messages such as " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " then it is possible that floppy booting is " -#~ "simply not supported on your machine." -#~ msgstr "" -#~ "Если вы загружаетесь с дискеты и видите такое " -#~ "сообщение\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ ", то возможно, загрузка с дискет просто не " -#~ "поддерживается на этой машине." - -#~ msgid "IDPROM Messages" -#~ msgstr "Сообщения IDPROM" - -#~ msgid "" -#~ "If you cannot boot because you get messages about a problem with " -#~ "IDPROM, then it's possible that your NVRAM battery, which " -#~ "holds configuration information for you firmware, has run out. See the " -#~ "Sun NVRAM FAQ for more " -#~ "information." -#~ msgstr "" -#~ "Если вы не можете загрузиться и получаете сообщение о проблеме с " -#~ "IDPROM, то возможно, это из-за севшей батарейки NVRAM, " -#~ "которая содержит конфигурационную информацию микропрограммы. Подробней " -#~ "смотрите в Sun NVRAM FAQ." - -#~ 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 "" -#~ "Параметры загрузки — это параметры ядра Linux, которые обычно " -#~ "используются для того, чтобы указать присутствующие периферийные " -#~ "устройства. В большинстве случаев ядро может определить периферийные " -#~ "устройства автоматически. Однако, иногда вы должны немного помочь ядру." - -#~ 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 "" -#~ "Если вы в первый раз загружаете систему, попробуйте параметры загрузки по " -#~ "умолчанию (то есть не пытайтесь их изменять) и посмотрите, корректно ли " -#~ "всё работает. Скорее всего, так оно и будет. Если нет, вы сможете позже " -#~ "перезагрузиться и поискать специальные параметры, которые помогут системе " -#~ "определить аппаратуру вашего компьютера." - -#~ msgid "" -#~ "Information on many boot parameters can be found in the Linux BootPrompt " -#~ "HOWTO, including tips for obscure hardware. This section contains " -#~ "only a sketch of the most salient parameters. Some common gotchas are " -#~ "included below in ." -#~ msgstr "" -#~ "Информацию о многих параметрах загрузки можно найти в Linux BootPrompt HOWTO, где можно найти советы советы и по нераспознанному оборудованию. " -#~ "В этом разделе содержатся только краткие сведения о наиболее важных " -#~ "параметрах. Некоторые распространённые ошибки включены ниже в ." - -#~ msgid "" -#~ "When the kernel boots, a message \n" -#~ "Memory:availk/totalk available\n" -#~ " should be emitted early in the process. " -#~ "total 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 mem=ram parameter, where ram " -#~ "is set to the amount of memory, suffixed with k for " -#~ "kilobytes, or m for megabytes. For example, both " -#~ "mem=65536k and mem=64m mean " -#~ "64MB of RAM." -#~ msgstr "" -#~ "В самом начале при загрузке ядра должно появиться сообщение: " -#~ "\n" -#~ "Memory:availk/totalk available \n" -#~ "Значение total " -#~ "должно совпадать с общим количеством ОЗУ в килобайтах. Если оно не " -#~ "соответствует действительно установленному объёму ОЗУ, вам надо " -#~ "использовать параметр mem=ram, где ram равно объёму памяти, " -#~ "дополненному буквой k, если объём задан в килобайтах или " -#~ "m, если в мегабайтах. Например, mem=65536k или mem=64m означают 64МБ ОЗУ." - -#~ msgid "" -#~ "If you are booting with a serial console, generally the kernel will " -#~ "autodetect this (although not on DECstations). 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 console=device argument to the kernel, where " -#~ "device is your serial device, which is usually " -#~ "something like ttyS0." -#~ msgstr "" -#~ "Если вы загружаетесь через консоль на последовательном порту, обычно ядро " -#~ "обнаруживает это автоматически (кроме DECstations)" -#~ ". Если к компьютеру подключёны видеокарта (framebuffer) и " -#~ "клавиатура, а вы хотите загрузиться через консоль на последовательном " -#~ "порту, вам надо передать ядру параметр " -#~ "console=device, где " -#~ "device — это имя последовательного " -#~ "порта, обычно ttyS0." - -#~ msgid "" -#~ "For &arch-title; the serial devices are ttya or " -#~ "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " -#~ "ttya." -#~ msgstr "" -#~ "Для &arch-title; последовательными устройствами являются ttya или ttyb. Или же установите переменные " -#~ "OpenPROM input-device и output-device " -#~ "равными ttya." - -#~ msgid "Debian Installer Parameters" -#~ msgstr "Параметры программы установки Debian" - -#~ msgid "" -#~ "The installation system recognizes a few additional boot " -#~ "parameters With current kernels (2.6.9 or newer) you can " -#~ "use 32 command line options and 32 environment options. If these numbers " -#~ "are exceeded, the kernel will panic. which may be " -#~ "useful." -#~ msgstr "" -#~ "Система установки анализирует некоторые дополнительные параметры " -#~ "загрузки Новые версии ядер (2.6.9 и новее) позволяют " -#~ "использовать 32 параметра в командной строке и 32 переменные среды. , что может быть полезно." - -#~ msgid "debconf/priority" -#~ msgstr "debconf/priority" - -#~ msgid "" -#~ "This parameter sets the lowest priority of messages to be displayed. " -#~ "Short form: priority" -#~ msgstr "" -#~ "Этот параметр задаёт низший приоритет отображаемых сообщений. Сокращённая " -#~ "форма: priority" - -#~ msgid "" -#~ "The default installation uses priority=high. 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 "" -#~ "Значение по умолчанию равно priority=high. Это " -#~ "означает, что будут показаны сообщения с высоким и с критическим " -#~ "приоритетами, а сообщения со средним и низким приоритетами будут " -#~ "пропущены. В случае возникновения проблем, программа установки " -#~ "подстраивает значение приоритета." - -#~ msgid "" -#~ "If you add priority=medium as boot parameter, you " -#~ "will be shown the installation menu and gain more control over the " -#~ "installation. When priority=low is used, all " -#~ "messages are shown (this is equivalent to the expert " -#~ "boot method). With priority=critical, the " -#~ "installation system will display only critical messages and try to do the " -#~ "right thing without fuss." -#~ msgstr "" -#~ "Если вы добавите priority=medium в качестве " -#~ "параметра загрузки, то увидите меню программы установки и получите " -#~ "больший контроль над установкой. При использовании " -#~ "priority=low показываются все сообщения " -#~ "(эквивалентно методу загрузки expert). Если указать " -#~ "priority=critical, то система установки будет " -#~ "показывать только критические сообщения и попробует всё сделать правильно " -#~ "самостоятельно." - -#~ msgid "DEBIAN_FRONTEND" -#~ msgstr "DEBIAN_FRONTEND" - -#~ msgid "" -#~ "This boot parameter controls the type of user interface used for the " -#~ "installer. The current possible parameter settings are: " -#~ " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " -#~ "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk The default frontend is " -#~ "DEBIAN_FRONTEND=newt. " -#~ "DEBIAN_FRONTEND=text may be preferable for serial " -#~ "console installs. Generally only the newt frontend " -#~ "is available on default install media. On architectures which support it, " -#~ "the graphical installer uses the gtk frontend." -#~ msgstr "" -#~ "Этот параметр загрузки контролирует тип пользовательского интерфейса, " -#~ "используемого программой установки. Возможные на текущий момент значения " -#~ "параметра: " -#~ "DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " -#~ "DEBIAN_FRONTEND=gtk По умолчанию выбран тип DEBIAN_FRONTEND=newt. Для установки через консоль на последовательном порту " -#~ "наиболее предпочтителен DEBIAN_FRONTEND=text . " -#~ "Вообще, с носителей установки по умолчанию в данный момент доступен " -#~ "только интерфейс newt. На некоторых архитектурах " -#~ "используется графический интерфейс программы установки gtk." - -#~ msgid "BOOT_DEBUG" -#~ msgstr "BOOT_DEBUG" - -#~ 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 "" -#~ "Присвоение этому загрузочному параметру значения 2 приводит к более " -#~ "подробному протоколированию процесса загрузки программы установки. " -#~ "Значение 3 приводит к запуску интерпретатора командной строки в наиболее " -#~ "важных точках процесса загрузки. (Завершение работы с интерпретатором " -#~ "приводит к продолжению процесса загрузки.)" - -#~ msgid "BOOT_DEBUG=0" -#~ msgstr "BOOT_DEBUG=0" - -#~ msgid "This is the default." -#~ msgstr "Значение по умолчанию." - -#~ msgid "BOOT_DEBUG=1" -#~ msgstr "BOOT_DEBUG=1" - -#~ msgid "More verbose than usual." -#~ msgstr "Подробней чем обычно." - -#~ msgid "BOOT_DEBUG=2" -#~ msgstr "BOOT_DEBUG=2" - -#~ msgid "Lots of debugging information." -#~ msgstr "Много отладочной информации." - -#~ msgid "BOOT_DEBUG=3" -#~ msgstr "BOOT_DEBUG=3" - -#~ msgid "" -#~ "Shells are run at various points in the boot process to allow detailed " -#~ "debugging. Exit the shell to continue the boot." -#~ msgstr "" -#~ "В различных точках процесса загрузки будет вызван интерпретатор командной " -#~ "строки, чтобы разрешить детальную отладку. При выходе из интерпретатора " -#~ "загрузка продолжится." - -#~ msgid "INSTALL_MEDIA_DEV" -#~ msgstr "INSTALL_MEDIA_DEV" - -#~ msgid "" -#~ "The value of the parameter is the path to the device to load the Debian " -#~ "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ msgstr "" -#~ "Значением этого параметра является путь к устройству, с которого " -#~ "загружается программа установки Debian. Например, " -#~ "INSTALL_MEDIA_DEV=/dev/floppy/0" - -#~ msgid "" -#~ "The boot floppy, which normally scans all floppies it can to find the " -#~ "root floppy, can be overridden by this parameter to only look at the one " -#~ "device." -#~ msgstr "" -#~ "Загрузочная дискета в поисках корневой дискеты сканирует все дискеты и " -#~ "USB устройства хранения. Этим параметром можно заставить её искать " -#~ "корневую дискету только на избранном устройстве." - -#~ msgid "debian-installer/framebuffer" -#~ msgstr "debian-installer/framebuffer" - -#~ 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 debian-installer/" -#~ "framebuffer=false, or fb=false for " -#~ "short. Problem symptoms are error messages about bterm or bogl, a blank " -#~ "screen, or a freeze within a few minutes after starting the install." -#~ msgstr "" -#~ "Некоторые архитектуры используют framebuffer ядра, чтобы предложить " -#~ "установку на нескольких языках. Если использование framebuffer вызывает " -#~ "проблемы на вашей системе, можно выключить его параметром " -#~ "debian-installer/framebuffer=false или сокращённое " -#~ "fb=false. Симптомы проблемы — сообщения об " -#~ "ошибках bterm или bogl, пустой экран или замирание на несколько минут в " -#~ "начале установки." - -#~ msgid "" -#~ "The video=vga16:off argument may also be used to " -#~ "disable the kernel's use of the framebuffer. Such problems have been " -#~ "reported on a Dell Inspiron with Mobile Radeon card." -#~ msgstr "" -#~ "Аргумент video=vga16:off также может быть " -#~ "использован для запрета framebuffer. Подобные проблемы замечены на Dell " -#~ "Inspiron с картой Mobile Radeon." - -#~ msgid "Such problems have been reported on the Amiga 1200 and SE/30." -#~ msgstr "Подобные проблемы замечены на Amiga 1200 и SE/30." - -#~ msgid "Such problems have been reported on hppa." -#~ msgstr "Подобные проблемы замечены на hppa." - -#~ msgid "" -#~ "Because of display problems on some systems, framebuffer support is " -#~ "disabled by default 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 " -#~ "debian-installer/framebuffer=true or " -#~ "fb=true for short." -#~ msgstr "" -#~ "Для &arch-title; поддержка framebuffer по умолчанию выключена из-за проблем с отображением на некоторых системах. В свою " -#~ "очередь это может привести к неправильному отображению на системах с " -#~ "нормально поддерживаемым framebuffer, типа графических карт ATI. Если у " -#~ "вас возникли проблемы с отображением в программе установки, можно " -#~ "попробовать загрузиться с параметром debian-installer/" -#~ "framebuffer=true или для краткости fb=true." - -#~ msgid "debian-installer/theme" -#~ msgstr "debian-installer/theme" - -#~ msgid "" -#~ "A theme determines how the user interface of the installer looks (colors, " -#~ "icons, etc.). What themes are available differs per frontend. Currently " -#~ "both the newt and gtk frontends only have a dark theme " -#~ "that was designed for visually impaired users. Set the theme by booting " -#~ "with parameter debian-installer/theme=dark or theme=dark." -#~ msgstr "" -#~ "Темой определяется вид пользовательского интерфейса программы установки " -#~ "(раскраска, иконки и т.д.). У каждого интерфейса есть свои темы. В " -#~ "настоящий момент для интерфейсов newt и gtk есть только одна тема " -#~ "dark, которая была специально разработана для людей с " -#~ "ослабленным зрением. Для установки темы загрузитесь с параметром " -#~ "debian-installer/theme=dark или theme=dark." - -#~ msgid "debian-installer/probe/usb" -#~ msgstr "debian-installer/probe/usb" - -#~ msgid "" -#~ "Set to false to prevent probing for USB on boot, " -#~ "if that causes problems." -#~ msgstr "" -#~ "Установите в false, чтобы избежать проверки USB " -#~ "при загрузке, если это вызывает проблемы." - -#~ msgid "netcfg/disable_dhcp" -#~ msgstr "netcfg/disable_dhcp" - -#~ 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 "" -#~ "По умолчанию, &d-i; автоматически пытается настроить сеть через DHCP. " -#~ "Если получение адреса прошло успешно, у вас не будет шанса пересмотреть и " -#~ "изменить полученные настройки. Вы сможете настроить сеть вручную только в " -#~ "случае ошибок при работе с DHCP." - -#~ 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 " -#~ "netcfg/disable_dhcp=true to prevent configuring " -#~ "the network with DHCP and to enter the information manually." -#~ msgstr "" -#~ "Если в вашей локальной сети есть DHCP сервер, но вы не хотите его " -#~ "использовать, потому что он, например, дает неправильные ответы, можете " -#~ "указать параметр netcfg/disable_dhcp=true, чтобы " -#~ "отключить настройку сети по DHCP и ввести информацию вручную." - -#~ msgid "hw-detect/start_pcmcia" -#~ msgstr "hw-detect/start_pcmcia" - -#~ msgid "" -#~ "Set to false to prevent starting PCMCIA services, " -#~ "if that causes problems. Some laptops are well known for this misbehavior." -#~ msgstr "" -#~ "Установите в false, чтобы избежать запуска PCMCIA " -#~ "сервисов, если это вызывает проблемы. Особенно полезно для некоторых " -#~ "ноутбуков." - -#~ msgid "preseed/url" -#~ msgstr "preseed/url" - -#~ msgid "" -#~ "Specify the url to a preconfiguration file to download and use in " -#~ "automating the install. See . Short " -#~ "form: url." -#~ msgstr "" -#~ "Задайте url для загрузки файла с настройками и использования " -#~ "автоматической установки. Смотрите . " -#~ "Сокращённая форма: url." - -#~ msgid "preseed/file" -#~ msgstr "preseed/file" - -#~ msgid "" -#~ "Specify the path to a preconfiguration file to load to automating the " -#~ "install. See . Short form: " -#~ "file." -#~ msgstr "" -#~ "Задайте файл для загрузки настроек автоматической установки. Смотрите " -#~ ". Сокращённая форма: " -#~ "file." - -#~ msgid "auto-install/enabled" -#~ msgstr "auto-install/enabled" - -#~ msgid "" -#~ "Delay questions that are normally asked before preseeding is possible " -#~ "until after the network is configured. Short form: auto=true See for details about using " -#~ "this to automate installs." -#~ msgstr "" -#~ "Отложить вопросы, которые обычно задаются перед автоматической " -#~ "установкой, которые можно задать после настройки сети. Сокращённая форма: " -#~ "auto=true Подробней об автоматизации установки " -#~ "смотрите в ." - -#~ msgid "cdrom-detect/eject" -#~ msgstr "cdrom-detect/eject" - -#~ 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 "" -#~ "По умолчанию перед перезагрузкой, &d-i; автоматически извлекает компакт-" -#~ "диск, который использовался при установке. Это делать необязательно, если " -#~ "система система не загружается с компакт-диска автоматически. В некоторых " -#~ "случаях это даже нежелательно, например, если устройство чтения не может " -#~ "самостоятельно загрузить компакт-диск и пользователь не может сделать это " -#~ "вручную. Многие устройства со слотовой загрузкой, slim-line и caddy не " -#~ "способны загружать носитель автоматически." - -#~ msgid "" -#~ "Set to false 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 "" -#~ "Чтобы запретить автоматическое извлечение задайте значение " -#~ "false, но проверьте, что система не загружается " -#~ "автоматически с компакт-диска после начальной установки." - -#~ msgid "ramdisk_size" -#~ msgstr "ramdisk_size" - -#~ msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -#~ msgstr "" -#~ "Если вы используете ядро 2.2.x, может потребоваться установить " -#~ "&ramdisksize;." - -#~ msgid "mouse/left" -#~ msgstr "mouse/left" - -#~ msgid "" -#~ "For the gtk frontend (graphical installer), users can switch the mouse to " -#~ "left-handed operation by setting this parameter to true." -#~ msgstr "" -#~ "В интерфейсе gtk (графическая программа установки) пользователи могут " -#~ "настроить мышь под левую руку, установив данный параметр равным " -#~ "true." - -#~ msgid "directfb/hw-accel" -#~ msgstr "directfb/hw-accel" - -#~ msgid "" -#~ "For the gtk frontend (graphical installer), hardware acceleration in " -#~ "directfb is disabled by default. To enable it, set this parameter to " -#~ "true when booting the installer." -#~ msgstr "" -#~ "В интерфейсе gtk (графическая программа установки), по умолчанию " -#~ "выключено аппаратное ускорение в directfb. Для включения установите " -#~ "данный параметр равным true при загрузке программы " -#~ "установки." - -#~ msgid "rescue/enable" -#~ msgstr "rescue/enable" - -#~ msgid "" -#~ "Set to true to enter rescue mode rather than " -#~ "performing a normal installation. See ." -#~ msgstr "" -#~ "Установка в true активирует режим восстановления, " -#~ "вместо обычного режима установки. Смотрите ." - -#~ msgid "Using boot parameters to answer questions" -#~ msgstr "Использование параметров загрузки для ответов на вопросы" - -#~ msgid "" -#~ "With some exceptions, a value can be set at the boot prompt for any " -#~ "question asked during the installation, though this is only really useful " -#~ "in specific cases. General instructions how to do this can be found in " -#~ ". Some specific examples are listed " -#~ "below." -#~ msgstr "" -#~ "За некоторым исключением, в приглашении к загрузке можно задать любые " -#~ "значения ответов на вопросы установки, хотя это полезно только в " -#~ "специфических случаях. Описание как это делать можно найти в . Некоторые специальные примеры даны ниже." - -#~ msgid "debian-installer/locale" -#~ msgstr "debian-installer/locale" - -#~ msgid "" -#~ "Can be used to set both the language and country for the installation. " -#~ "This will only work if the locale is supported in Debian. Short form: " -#~ "locale. For example, use locale=de_CH to select German as language and Switserland as country." -#~ msgstr "" -#~ "Может использоваться для указания языка и страны для установки. Это " -#~ "работает только если данная локаль поддерживается Debian. Сокращённая " -#~ "форма: locale. Например, введите " -#~ "locale=de_CH, чтобы выбрать немецкий язык и " -#~ "Швейцарию как страну." - -#~ msgid "" -#~ "Set to true if you want to disable DHCP and " -#~ "instead force static network configuration." -#~ msgstr "" -#~ "Установите в true, если хотите выключить DHCP и " -#~ "задать настройки сети статически." - -#~ msgid "tasksel:tasksel/first" -#~ msgstr "tasksel:tasksel/first" - -#~ msgid "" -#~ "Can be used to select tasks that are not available from the interactive " -#~ "task list, such as the kde-desktop task. See for additional information. Short form: " -#~ "tasks." -#~ msgstr "" -#~ "Может быть использована для выбора задач, которых нет в списке выбора в " -#~ "программе установки, например задача kde-desktop. " -#~ "Подробней смотрите в . Сокращённая форма: " -#~ "tasks." - -#~ msgid "Passing parameters to kernel modules" -#~ msgstr "Передача параметров модулям ядра" - -#~ msgid "" -#~ "If drivers are compiled into the kernel, you can pass parameters to them " -#~ "as described in the kernel documentation. However, if drivers are " -#~ "compiled as modules and because kernel modules are loaded a bit " -#~ "differently during an installation than when booting an installed system, " -#~ "it is not possible to pass parameters to modules as you would normally " -#~ "do. Instead, you need to use a special syntax recognized by the installer " -#~ "which will then make sure that the parameters are saved in the proper " -#~ "configuration files and will thus be used when the modules are actually " -#~ "loaded. The parameters will also be propagated automatically to the " -#~ "configuration for the installed system." -#~ msgstr "" -#~ "Если драйверы встроены в ядро, вы можете передать им параметры как это " -#~ "описано в документации к ядру. Если же драйверы собраны как модули и так " -#~ "как модули ядра загружаются немного по-другому чем при загрузке " -#~ "установленной системы, невозможно передать параметры модулям обычным " -#~ "способом. Вместо этого вам нужно использовать специальный синтаксис, " -#~ "распознаваемый программой установки, которая сохраняет эти параметры в " -#~ "нужные конфигурационные файлы, для того чтобы использовать их при " -#~ "загрузке модуля. Параметры также будут автоматически включены в " -#~ "конфигурацию установленной системы." - -#~ msgid "" -#~ "Note that it is now quite rare that parameters need to be passed to " -#~ "modules. In most cases the kernel will be able to probe the hardware " -#~ "present in a system and set good defaults that way. However, in some " -#~ "situations it may still be needed to set parameters manually." -#~ msgstr "" -#~ "Заметим, что теперь редко требуется указывать параметры модулям. В " -#~ "большинстве случаев ядро способно само определить имеющееся оборудование " -#~ "в системе и настроить его правильно. Однако иногда всё ещё может " -#~ "потребоваться установка параметров вручную." - -#~ msgid "" -#~ "The syntax to use to set parameters for modules is: " -#~ "\n" -#~ "module_name.parameter_name=value\n" -#~ " If you need to pass multiple parameters to " -#~ "the same or different modules, just repeat this. For example, to set an " -#~ "old 3Com network interface card to use the BNC (coax) connector and IRQ " -#~ "10, you would pass:" -#~ msgstr "" -#~ "Синтаксис установки параметров модулей: \n" -#~ "имя_модуля.имя_параметра=значение\n" -#~ " Если требуется передать несколько параметров " -#~ "одному или разным модулям, то выражение повторяют. Например, чтобы " -#~ "указать старым сетевым картам 3Com использовать BNC (коаксиальный) разъём " -#~ "и IRQ 10, вы должны написать:" - -#~ msgid "3c509.xcvr=3 3c509.irq=10" -#~ msgstr "3c509.xcvr=3 3c509.irq=10" - -#~ msgid "Troubleshooting the Installation Process" -#~ msgstr "Диагностика проблем процесса установки" - -#~ msgid "CD-ROM Reliability" -#~ msgstr "Надёжность CD-ROM" - -#~ msgid "" -#~ "Sometimes, especially with older CD-ROM drives, the installer may fail to " -#~ "boot from a CD-ROM. The installer may also — even after booting " -#~ "successfully from CD-ROM — fail to recognize the CD-ROM or return " -#~ "errors while reading from it during the installation." -#~ msgstr "" -#~ "Иногда, особенно в старых приводах CD-ROM, программа установки может не " -#~ "загрузиться с CD-ROM. Программа установки также может (даже после " -#~ "успешной загрузки с CD-ROM) не распознать CD-ROM или выдавать ошибки при " -#~ "чтении во время установки." - -#~ msgid "" -#~ "There are a many different possible causes for these problems. We can " -#~ "only list some common issues and provide general suggestions on how to " -#~ "deal with them. The rest is up to you." -#~ msgstr "" -#~ "Такие проблемы могут возникать по разным причинам. Мы можем описать " -#~ "только общие из них и предложить общие решения. Остальное зависит от вас." - -#~ msgid "There are two very simple things that you should try first." -#~ msgstr "" -#~ "Есть несколько простых вещей, которые вы можете попробовать сделать в " -#~ "первую очередь." - -#~ msgid "" -#~ "If the CD-ROM does not boot, check that it was inserted correctly and " -#~ "that it is not dirty." -#~ msgstr "" -#~ "Если с CD-ROM не получается загрузиться, проверьте, что он вставлен " -#~ "правильно и что диск не грязный." - -#~ msgid "" -#~ "If the installer fails to recognize a CD-ROM, try just running the option " -#~ " Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM " -#~ "drives are known to be resolved in this way." -#~ msgstr "" -#~ "Если программа установки не смогла определить CD-ROM, попробуйте " -#~ "выполнить пункт меню Поиск и монтирование CD-" -#~ "ROM второй раз. Некоторые проблемы с DMA на " -#~ "старых приводах CD-ROM решаются таким способом." - -#~ msgid "" -#~ "If this does not work, then try the suggestions in the subsections below. " -#~ "Most, but not all, suggestions discussed there are valid for both CD-ROM " -#~ "and DVD, but we'll use the term CD-ROM for simplicity." -#~ msgstr "" -#~ "Если это не сработало, попробуйте советы данные ниже. Хотя большинство, " -#~ "но не все, описываемые предложения работают и для CD-ROM и для DVD, для " -#~ "простоты мы будем использовать термин CD-ROM." - -#~ msgid "" -#~ "If you cannot get the installation working from CD-ROM, try one of the " -#~ "other installation methods that are available." -#~ msgstr "" -#~ "Если вы не можете заставить программу установки работать с CD-ROM, " -#~ "попробуйте, если возможно, другой метод установки." - -#~ msgid "Common issues" -#~ msgstr "Общие причины" - -#~ msgid "" -#~ "Some older CD-ROM drives do not support reading from discs that were " -#~ "burned at high speeds using a modern CD writer." -#~ msgstr "" -#~ "Некоторые старые приводы CD-ROM не поддерживают чтение с дисков, которые " -#~ "были записаны на высоких скоростях в современных устройствах записи CD." - -#~ msgid "" -#~ "If your system boots correctly from the CD-ROM, it does not necessarily " -#~ "mean that Linux also supports the CD-ROM (or, more correctly, the " -#~ "controller that your CD-ROM drive is connected to)." -#~ msgstr "" -#~ "Если система корректно загружается с CD-ROM, это совсем не значит, что " -#~ "Linux также поддерживает CD-ROM (или, если более точно, контроллер, к " -#~ "которому подключён привод CD-ROM)." - -#~ msgid "" -#~ "Some older CD-ROM drives do not work correctly if direct memory " -#~ "access (DMA) is enabled." -#~ msgstr "" -#~ "Некоторые старые приводы CD-ROM работают неправильно, если включён " -#~ "прямой доступ к памяти (DMA)." - -#~ msgid "How to investigate and maybe solve issues" -#~ msgstr "Как изучать и может быть решить проблему" - -#~ msgid "If the CD-ROM fails to boot, try the suggestions listed below." -#~ msgstr "" -#~ "Если с CD-ROM не удаётся загрузиться, попробуйте способы указанные ниже." - -#~ msgid "" -#~ "Check that your BIOS actually supports booting from CD-ROM (older systems " -#~ "possibly don't) and that your CD-ROM drive supports the media you are " -#~ "using." -#~ msgstr "" -#~ "Проверьте, что в BIOS включена загрузка с CD-ROM (возможно, старые машины " -#~ "этого не умеют), и что привод CD-ROM поддерживает используемый тип " -#~ "носителя." - -#~ msgid "" -#~ "If you downloaded an iso image, check that the md5sum of that image " -#~ "matches the one listed for the image in the MD5SUMS " -#~ "file that should be present in the same location as where you downloaded " -#~ "the image from. \n" -#~ "$ md5sum debian-testing-i386-netinst.iso\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-" -#~ "netinst.iso\n" -#~ " Next, check that the md5sum of the burned CD-" -#~ "ROM matches as well. The following command should work. It uses the size " -#~ "of the image to read the correct number of bytes from the CD-ROM." -#~ msgstr "" -#~ "Если вы скачивали образ iso, проверьте, что md5sum этого образа совпадает " -#~ "с суммой указанной в файле MD5SUMS, который должен " -#~ "лежать там же, где вы брали образ. \n" -#~ "$ md5sum debian-testing-i386-netinst.iso\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-" -#~ "netinst.iso\n" -#~ " Далее проверьте, что md5sum записанного CD-" -#~ "ROM также совпадает. Следующая команда должна сработать. Здесь считается " -#~ "сумма прочитанных с CD-ROM байт, составляющих образ." - -#~ msgid "" -#~ "$ dd if=/dev/cdrom | \\\n" -#~ "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" -#~ "> md5sum\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 -\n" -#~ "262668+0 records in\n" -#~ "262668+0 records out\n" -#~ "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" -#~ msgstr "" -#~ "$ dd if=/dev/cdrom | \\\n" -#~ "> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" -#~ "> md5sum\n" -#~ "a20391b12f7ff22ef705cee4059c6b92 -\n" -#~ "262668+0 records in\n" -#~ "262668+0 records out\n" -#~ "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" - -#~ msgid "" -#~ "If, after the installer has been booted successfully, the CD-ROM is not " -#~ "detected, sometimes simply trying again may solve the problem. If you " -#~ "have more than one CD-ROM drive, try changing the CD-ROM to the other " -#~ "drive. If that does not work or if the CD-ROM is recognized but there are " -#~ "errors when reading from it, try the suggestions listed below. Some basic " -#~ "knowledge of Linux is required for this. To execute any of the commands, " -#~ "you should first switch to the second virtual console (VT2) and activate " -#~ "the shell there." -#~ msgstr "" -#~ "Если после успешной загрузки программы установки не определяется CD-ROM, " -#~ "то иногда помогает просто попробовать ещё раз. Если у вас более одного " -#~ "привода CD-ROM, попробуйте загрузиться с другого CD-ROM. Если это не " -#~ "помогает или если CD-ROM определяется, но при чтении возникают ошибки, " -#~ "попробуйте выполнить предложения, данные ниже. Для этого потребуются азы " -#~ "работы в Linux. Перед тем как выполнить любую команду, сначала вы должны " -#~ "переключиться во вторую виртуальную консоль (VT2) и активировать оболочку " -#~ "командной строки." - -#~ msgid "" -#~ "Switch to VT4 or view the contents of /var/log/syslog (use nano as editor) to check for any " -#~ "specific error messages. After that, also check the output of " -#~ "dmesg." -#~ msgstr "" -#~ "Переключитесь в VT4 или посмотрите файл /var/log/syslog (в качестве редактора используется nano), " -#~ "чтобы найти сообщения о специфических ошибках. После этого также " -#~ "проверьте вывод команды dmesg." - -#~ msgid "" -#~ "Check in the output of dmesg if your CD-ROM drive was " -#~ "recognized. You should see something like (the lines do not necessarily " -#~ "have to be consecutive): \n" -#~ "Probing IDE interface ide1...\n" -#~ "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" -#~ "ide1 at 0x170-0x177,0x376 on irq 15\n" -#~ "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" -#~ "Uniform CD-ROM driver Revision: 3.20\n" -#~ " If you don't see something like that, chances " -#~ "are the controller your CD-ROM is connected to was not recognized or may " -#~ "be not supported at all. If you know what driver is needed for the " -#~ "controller, you can try loading it manually using modprobe." -#~ msgstr "" -#~ "В выводе dmesg проверьте, что привод CD-ROM был " -#~ "найден. Вы должны увидеть что-то типа этого (строки могут быть в другой " -#~ "последовательности): \n" -#~ "Probing IDE interface ide1...\n" -#~ "hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" -#~ "ide1 at 0x170-0x177,0x376 on irq 15\n" -#~ "hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" -#~ "Uniform CD-ROM driver Revision: 3.20\n" -#~ " Если вы не нашли подобных строк, это случай, " -#~ "когда контроллер, к которому подключён CD-ROM, не распознан или не " -#~ "поддерживается ядром вообще. Если вы знаете, какой драйвер требуется для " -#~ "привода, то можете попытаться загрузить его вручную с помощью команды " -#~ "modprobe." - -#~ msgid "" -#~ "Check that there is a device node for your CD-ROM drive under /" -#~ "dev/. In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." -#~ msgstr "" -#~ "Проверьте, что есть соответствующий файл устройства для привода CD-ROM в " -#~ "каталоге /dev/. Для примера выше, должен " -#~ "существовать файл /dev/hdc. Также может быть " -#~ "/dev/cdroms/cdrom0." - -#~ msgid "" -#~ "Use the mount command to check if the CD-ROM is " -#~ "already mounted; if not, try mounting it manually: " -#~ "\n" -#~ "$ mount /dev/hdc /cdrom\n" -#~ " Check if there are any error messages after " -#~ "that command." -#~ msgstr "" -#~ "С помощью команды mount проверьте, что CD-ROM уже " -#~ "смонтировать; если нет, попытайтесь смонтировать вручную: " -#~ "\n" -#~ "$ mount /dev/hdc /cdrom\n" -#~ " Проверьте, не появилось ли ошибок после этой " -#~ "команды." - -#~ msgid "" -#~ "Check if DMA is currently enabled: \n" -#~ "$ cd /proc/ide/hdc\n" -#~ "$ grep using_dma settings\n" -#~ "using_dma 1 0 1 rw\n" -#~ " A 1 in the first column after " -#~ "using_dma means it is enabled. If it is, try disabling " -#~ "it: \n" -#~ "$ echo -n \"using_dma:0\" >settings\n" -#~ " Make sure that you are in the directory for " -#~ "the device that corresponds to your CD-ROM drive." -#~ msgstr "" -#~ "Проверьте, включён ли DMA: \n" -#~ "$ cd /proc/ide/hdc\n" -#~ "$ grep using_dma settings\n" -#~ "using_dma 1 0 1 rw\n" -#~ " 1 означает включён. Если " -#~ "включён, попробуйте выключить его: \n" -#~ "$ echo -n \"using_dma:0\" >settings\n" -#~ " Удостоверьтесь, что находитесь в каталоге для " -#~ "устройства, соответствующего приводу CD-ROM." - -#~ msgid "" -#~ "If there are any problems during the installation, try checking the " -#~ "integrity of the CD-ROM using the option near the bottom of the " -#~ "installer's main menu. This option can also be used as a general test if " -#~ "the CD-ROM can be read reliably." -#~ msgstr "" -#~ "Если возникли проблемы во время установки, попробуйте проверить " -#~ "целостность CD-ROM с помощью пункта внизу главного меню программы " -#~ "установки. Этим также можно провести общую проверку надёжности чтения CD-" -#~ "ROM." - -#~ msgid "Floppy Disk Reliability" -#~ msgstr "Надёжность дискет" - -#~ msgid "" -#~ "The biggest problem for people using floppy disks to install Debian seems " -#~ "to be floppy disk reliability." -#~ msgstr "" -#~ "Надёжность дискет — это, похоже, самая большая проблема для людей, " -#~ "устанавливающих Debian." - -#~ 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 "" -#~ "Загрузочная дискета — это самая проблемная дискета, потому что она " -#~ "читается аппаратурой напрямую, до загрузки Linux. Часто аппаратура не " -#~ "может читать также надёжно, как драйвер дискет Linux, и может просто " -#~ "остановиться без вывода сообщения об ошибке, если прочитает неправильные " -#~ "данные. Ещё возможны неполадки с дисководом, большинство которых выглядят " -#~ "как поток сообщений об ошибках ввода-вывода (disk I/O error)." - -#~ msgid "" -#~ "If you are having the installation stall at a particular floppy, the " -#~ "first thing you should do is write the image to a different floppy and see if that solves the problem. 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 "" -#~ "Если установка замирает на какой-то дискете, сперва попробуйте записать " -#~ "образ на другую дискету. Простого переформатирования " -#~ "старой дискеты может быть недостаточно, даже если это случилось с " -#~ "дискетой, которую отформатировали и записали без ошибок. Иногда полезно " -#~ "попробовать записать дискету на другой системе." - -#~ msgid "" -#~ "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " -#~ "third floppy." -#~ msgstr "" -#~ "Один пользователь сообщил, что он записывал образ на дискету " -#~ "три раза, прежде чем она заработала, и затем всё " -#~ "пошло нормально." - -#~ msgid "" -#~ "Normally you should not have to download a floppy image again, but if you " -#~ "are experiencing problems it is always useful to verify that the images " -#~ "were downloaded correctly by verifying their md5sums." -#~ msgstr "" -#~ "Обычно не нужно скачивать образ дискет ещё раз, но если вы испытываете " -#~ "проблемы, всегда полезно проверить корректность загруженных образов " -#~ "сверив их md5sum." - -#~ 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 "" -#~ "Другие пользователи сообщали, что простая перезагрузка несколько раз с " -#~ "одной и той же дискеты в дисководе приводила к успешной загрузке. Всё это " -#~ "случается из-за плохо работающих дисководов и их микропрограмм." - -#~ msgid "Boot Configuration" -#~ msgstr "Настройка загрузки" - -#~ 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 ." -#~ msgstr "" -#~ "Если у вас возникли проблемы и ядро падает во время загрузки, не " -#~ "распознает имеющуюся периферию или неправильно распознаются диски, сперва " -#~ "проверьте параметры загрузки, как это обсуждается в ." - -#~ msgid "" -#~ "If you are booting with your own kernel instead of the one supplied with " -#~ "the installer, be sure that CONFIG_DEVFS is set in " -#~ "your kernel. The installer requires CONFIG_DEVFS." -#~ msgstr "" -#~ "Если вы загружаете самостоятельно собранное ядро вместо поставляемого с " -#~ "программной установки, проверьте, что в вашем ядре включён параметр " -#~ "CONFIG_DEVFS. Программе установки требуется " -#~ "CONFIG_DEVFS." - -#~ msgid "" -#~ "Often, problems can be solved by removing add-ons and peripherals, and " -#~ "then trying booting again. Internal modems, sound " -#~ "cards, and Plug-n-Play devices can be especially problematic." -#~ msgstr "" -#~ "Часто, проблемы можно решить, убрав дополнения и периферию, а затем " -#~ "попытаться загрузиться ещё раз. Особенно часто " -#~ "проблемы бывают с внутренними модемами, звуковыми картами и устройствами " -#~ "Plug-n-Play." - -#~ 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 mem=512m." -#~ msgstr "" -#~ "Если на вашей машине установлен большой объём памяти, более чем 512МБ и " -#~ "программа установки виснет при загрузке ядра, то вам может понадобиться " -#~ "указать параметр загрузки для ограничения объёма памяти видимого ядру " -#~ "— mem=512m." - -#~ msgid "Common &arch-title; Installation Problems" -#~ msgstr "Распространённые проблемы установки на &arch-title;" - -#~ msgid "" -#~ "There are some common installation problems that can be solved or avoided " -#~ "by passing certain boot parameters to the installer." -#~ msgstr "" -#~ "Есть некоторое количество распространённых проблем установки, которые " -#~ "можно решить или избежать с помощью передачи параметров загрузки " -#~ "программе установки." - -#~ msgid "" -#~ "Some systems have floppies with inverted DCLs. If you " -#~ "receive errors reading from the floppy, even when you know the floppy is " -#~ "good, try the parameter floppy=thinkpad." -#~ msgstr "" -#~ "Некоторые системы имеют дисковод гибких дисков с обратными DCL. Если вы получаете ошибки чтения с дискеты, даже когда знаете, что " -#~ "она хорошая, попробуйте задать параметр floppy=thinkpad." - -#~ 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 hd=cylinders,heads,sectors." -#~ msgstr "" -#~ "На некоторых системах, таких как IBM PS/1 или ValuePoint (имеющих " -#~ "дисковый драйвер ST-506), привод IDE может быть распознан неправильно. " -#~ "Сначала попробуйте загрузиться без параметров и посмотрите, правильно ли " -#~ "определяется привод IDE. Если нет, выясните геометрию диска (количество " -#~ "цилиндров, головок и секторов) и воспользуйтесь параметром " -#~ "hd=количество цилиндров, " -#~ "количество головок, количество " -#~ "секторов." - -#~ msgid "" -#~ "If you have a very old machine, and the kernel hangs after saying " -#~ "Checking 'hlt' instruction..., then you " -#~ "should try the no-hlt boot argument, which " -#~ "disables this test." -#~ msgstr "" -#~ "Если у вас очень старая машина и ядро зависает после надписи " -#~ "Checking 'hlt' instruction..., то вы " -#~ "должны попробовать параметр загрузки no-hlt, " -#~ "который выключает этот тест." - -#~ 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 fb=false " -#~ "video=vga16:off to disable the framebuffer console. Only the " -#~ "English language will be available during the installation due to limited " -#~ "console features. See for details." -#~ msgstr "" -#~ "Если во время загрузки ядра экран выглядит странно, например, он " -#~ "полностью белый, чёрный или замусорен разными цветами, то ваша система " -#~ "вероятно имеет проблемную видеокарту, которая неправильно переключается в " -#~ "режим фрейм-буфера. В этом случае, вы можете попробовать параметр " -#~ "загрузки fb=false или video=vga16:off, чтобы выключить фрейм-буфер на консоли. Из-за этого " -#~ "ограничения консоли установка будет доступна только на английском языке. " -#~ "Подробней смотрите в ." - -#~ msgid "System Freeze During the PCMCIA Configuration Phase" -#~ msgstr "Система подвисает во время настройки PCMCIA" - -#~ 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 hw-detect/start_pcmcia=false boot parameter. " -#~ "You can then configure PCMCIA after the installation is completed and " -#~ "exclude the resource range causing the problems." -#~ msgstr "" -#~ "Про некоторые модели ноутбуков Dell известно, что они виснут когда при " -#~ "определении PCMCIA устройства производится попытка доступа по некоторым " -#~ "аппаратным адресам. Похожие проблемы могут иметь и другие ноутбуки . Если " -#~ "у вас возникла такая проблема и вам не нужна поддержка PCMCIA во время " -#~ "установки, то вы можете выключить PCMCIA с помощью параметра загрузки " -#~ "hw-detect/start_pcmcia=false. После установки вы " -#~ "сможете настроить PCMCIA, исключив диапазон ресурсов, с которым возникают " -#~ "проблемы." - -#~ 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 exclude port 0x800-0x8ff here. There is also " -#~ "a list of some common resource range options in the System " -#~ "resource settings section of the PCMCIA HOWTO. Note that you have " -#~ "to omit the commas, if any, when you enter this value in the installer." -#~ msgstr "" -#~ "Другой вариант: вы можете загрузить программу установки в экспертном " -#~ "режиме. Вас попросят указать диапазон ресурсов, который используется " -#~ "аппаратным обеспечением. Например, если у вас один из ноутбуков Dell, " -#~ "упомянутых выше, то вы должны ввести exclude port 0x800-0x8ff. Также, есть список распространённых диапазонов ресурсов в " -#~ "System resource settings section of the PCMCIA HOWTO. Заметим, что при вводе значений в программу установки вы не " -#~ "должны указывать запятых, если они есть." - -#~ msgid "System Freeze while Loading the USB Modules" -#~ msgstr "Система подвисает во время загрузки USB модулей" - -#~ 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 debian-installer/" -#~ "probe/usb=false parameter at the boot prompt, which will " -#~ "prevent the modules from being loaded." -#~ msgstr "" -#~ "Обычно, ядро пытается установить модули USB и драйвер USB клавиатуры, " -#~ "чтобы обеспечить поддержку некоторых нестандартных клавиатур USB. Однако, " -#~ "есть несколько нестандартных USB систем, где драйвер подвисает при " -#~ "загрузке. Возможно, обходным решением может быть выключение контроллера " -#~ "USB в настройке BIOS материнской платы. Другим решением может служить " -#~ "передача параметра debian-installer/probe/usb=false в приглашении загрузки, который запрещает загрузку модулей." - -#~ msgid "Interpreting the Kernel Startup Messages" -#~ msgstr "Интерпретация загрузочных сообщений ядра" - -#~ msgid "" -#~ "During the boot sequence, you may see many messages in the form " -#~ "can't find something , or something " -#~ "not present, can't initialize " -#~ "something , or even " -#~ "this driver release depends on something . 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 )." -#~ msgstr "" -#~ "Во время загрузки вы можете увидеть много сообщений вида " -#~ "can't find ... или ... not " -#~ "present, can't initialize " -#~ "... или даже " -#~ "this driver release depends on ... . Большинство этих сообщений безвредны. Вы " -#~ "видите их потому что устанавливаемое ядро собрано так, чтобы запускаться " -#~ "на компьютерах с самыми различными периферийными устройствами. Очевидно, " -#~ "ни один компьютер не может содержать все доступные устройства, так что " -#~ "операционная система может немного пожаловаться во время поиска " -#~ "периферии, которой у вас нет. Также, вы можете заметить, что система " -#~ "иногда замирает. Это случается из-за ожидания ответа от устройства, " -#~ "которого нет в вашей системе. Если вы посчитаете, что загрузка системы " -#~ "занимает недопустимо долгое время, вы можете позже создать собственное " -#~ "ядро (смотрите )." +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"Как и в варианте 1, эти шаги запускают начальный загрузчик Debian, который " +"показывает страницу меню для выбора загружаемого ядра и параметров. Также вы " +"можете ввести короткую команду fsn:" +"elilo в командной строке.Чтобы продолжить, выберите ядро и " +"параметры." + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "Установка с консоли на последовательном порту" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"Вы можете выбрать выполнение установки с помощью монитора и клавиатуры или " +"через последовательный порт. Чтобы использовать монитор/клавиатурную " +"установку, выберите пункт содержащий строку [VGA console]. Для установки " +"через последовательный порт, выберите пункт, содержащий строку " +"[BAUD baud serial console], где " +"BAUD это скорость вашего последовательного порта. " +"Типичные настройки скорости устройства ttyS0 выделены в отдельные пункты " +"меню." + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"В большинстве случаев вам нужно чтобы скорость программы установки была " +"равной с подключённой консолью EFI. Если вы не знаете какой она должна быть, " +"то можете получить скорость с помощью команды baud в EFI " +"shell." + +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"Если в меню нет пунктов со скоростями для последовательного порта или нет " +"скорости, которая вам требуется, то вы можете изменить настройки консоли " +"одного из существующих пунктов меню. Например, чтобы использовать на консоли " +"57600 бод через устройство ttyS1, введите console=ttyS1,57600n8 в текстовом окне с приглашением Boot:." + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" +"Большинство машин IA-64 продаётся настроенными по умолчанию консолями на " +"9600 бод. Эта настройка довольно медленна, и займёт значительное время для " +"прорисовки каждого экрана при обычном процессе установки. Вам, вероятно, " +"стоит увеличить скорость, используемую при установке или выполнять установку " +"в текстовом режиме. Смотрите в меню помощи Params " +"инструкции по запуску программы установки в текстовом режиме." + +#. Tag: para +#: boot-installer.xml:1419 +#, 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:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "Выбор загружаемого ядра и параметров" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" +"Начальный загрузчик выводит меню и текстовое окно с приглашением " +"Boot:. Клавишами управления курсором выбирается " +"строка меню, а в текстовое окно вводится всё набранное на клавиатуре. Есть " +"также экраны с помощью, в которые можно попасть нажав соответствующую " +"функциональную клавишу. На экране помощи General " +"объясняются пункты меню, а экранParams рассказывает " +"об общих параметрах командной строки." + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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 "" +"Прочитав экран помощи General, выберите ядро и режим " +"установки, которые наиболее вам подходят. Также вы должны прочитать в про любой дополнительный параметр, который вам " +"может потребоваться ввести в приглашении Boot:. " +"Выбираемая версия ядра будет использована для процесса установки и в " +"установленной системе. Если вы испытываете проблемы с ядром во время " +"установки, то скорее всего вы получите те же проблемы в установленной " +"системе. В следующих двух шагах выбирается и запускается установка:" + +#. Tag: para +#: boot-installer.xml:1460 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "" +"С помощью клавиш управления курсором выберите наиболее подходящие вам версию " +"ядра и режим установки." -#~ msgid "Bug Reporter" -#~ msgstr "Отчёт об ошибках" +#. Tag: para +#: boot-installer.xml:1465 +#, 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:1472 +#, no-c-format +msgid "" +"Press ENTER. 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 "" +"Нажмите ENTER. Загрузится и запустится ядро. Ядро выведет " +"обычные сообщения инициализации, а затем появится первый экран программы " +"установки Debian." + +#. Tag: para +#: boot-installer.xml:1481 boot-installer.xml:1617 +#, 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 "" +"Переходите к следующей главе, чтобы продолжить процесс установки, где вы " +"настроите язык, сеть и дисковые разделы." -#~ 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 "" -#~ "Если вы прошли фазу начальной загрузки, но не смогли завершить установку, " -#~ "полезно войти в меню отчёта об ошибках. Из этого меню можно скопировать " -#~ "системные журналы ошибок и информацию о конфигурации из программы " -#~ "установки на дискету или загрузить через веб браузер. Эта информация " -#~ "поможет понять, что было не так и как это исправить. Если вы отправляете " -#~ "отчёт об ошибках, то можете приложить эту информацию к отчёту." - -#~ msgid "" -#~ "Other pertinent installation messages may be found in /var/log/" -#~ " during the installation, and /var/log/installer/ after the computer has been booted into the installed system." -#~ msgstr "" -#~ "Другие сообщения, имеющие отношение к установке, можно найти в /" -#~ "var/log/ во время установки, и в /var/log/installer/" -#~ " после того, как компьютер загрузит установленную систему." - -#~ msgid "Submitting Installation Reports" -#~ msgstr "Отправка отчётов об ошибках установки" - -#~ 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 "" -#~ "Если у вас возникли проблемы, отправьте отчёт об установке. Также, мы " -#~ "приветствуем отправку отчётов даже в случае успешной установки, чтобы " -#~ "получить побольше информации о разных аппаратных конфигурациях." - -#~ 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 (apt-get install installation-report reportbug) and run the command reportbug installation-report." -#~ msgstr "" -#~ "Если система Debian заработала, самый простой путь отправки отчёта об " -#~ "установке — установка пакетов installation-report и reportbug " -#~ "(apt-get install installation-report reportbug) и " -#~ "запуск команды reportbug installation-report." - -#~ msgid "" -#~ "Please use this template when filling out installation reports, and file " -#~ "the report as a bug report against the installation-reports pseudo package, by sending it to submit@bugs.debian." -#~ "org. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <How did you boot the installer? CD? floppy? network?" -#~ ">\n" -#~ "Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" -#~ "\n" -#~ "Base System Installation Checklist:\n" -#~ "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" -#~ "\n" -#~ "Initial boot: [ ]\n" -#~ "Detect network card: [ ]\n" -#~ "Configure network: [ ]\n" -#~ "Detect CD: [ ]\n" -#~ "Load installer modules: [ ]\n" -#~ "Detect hard drives: [ ]\n" -#~ "Partition hard drives: [ ]\n" -#~ "Install base system: [ ]\n" -#~ "Clock/timezone setup: [ ]\n" -#~ "User/password setup: [ ]\n" -#~ "Install tasks: [ ]\n" -#~ "Install boot loader: [ ]\n" -#~ "Overall install: [ ]\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" -#~ " 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 "" -#~ "Пожалуйста, используйте этот шаблон для заполнения отчёта об установке и " -#~ "отправьте отчёт как сообщение об ошибке псевдо-пакету " -#~ "installation-reports на адрес submit@bugs." -#~ "debian.org. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <Как запускалась программа установки? с CD? с дискет? из " -#~ "сети?>\n" -#~ "Image version: <Дата и место, откуда был взят образ>\n" -#~ "Date: <Дата и время установки>\n" -#~ "\n" -#~ "Machine: <Описание машины (например, IBM Thinkpad R32)>\n" -#~ "Processor:\n" -#~ "Memory:\n" -#~ "Partitions: < вывод результата команды df -Tl; лучше таблицу разделов " -#~ "в необработанном (raw) виде>\n" -#~ "\n" -#~ "Вывод результата команд lspci -nn и lspci -vnn:\n" -#~ "\n" -#~ "Base System Installation Checklist:\n" -#~ "[O] = OK, [E] = Ошибка (описать подробности ниже), [ ] = не пробовал\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" -#~ "Install base system: [ ]\n" -#~ "Clock/timezone setup: [ ]\n" -#~ "User/password setup: [ ]\n" -#~ "Install tasks: [ ]\n" -#~ "Install boot loader: [ ]\n" -#~ "Overall install: [ ]\n" -#~ "\n" -#~ "Comments/Problems:\n" -#~ "\n" -#~ "<Описание установки, комментарии, предложения возникшие в процессе." -#~ ">\n" -#~ " В отчёте об ошибках опишите, в чём состоит " -#~ "проблема, включая последние увиденные сообщения ядра в случае повисания " -#~ "ядра. Опишите шаги, которые вы делали, чтобы привести систему в " -#~ "проблемное состояние." +#. Tag: para +#: boot-installer.xml:1492 +#, no-c-format +msgid "" +"Booting an IA-64 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 "" +"Загрузка системы IA-64 по сети похожа на загрузку с CD. Единственное отличие " +"— это способ загрузки ядра. Менеджер загрузки EFI может загружать и " +"запускать программы с сервера из сети. Как только ядро установки загружено и " +"запустилось, установка системы происходит также как и с CD за исключением, " +"того что пакеты базовой установки будут получены по сети, а не с привода CD." + +#. Tag: para +#: boot-installer.xml:1526 +#, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" +"Для загрузки по сети системы IA-64 требуется два специальных действия. DHCP " +"и TFTP на загрузочном сервере должны быть настроены на доставку " +"elilo. На клиенте должен быть задан дополнительный " +"параметр загрузки в менеджере загрузки EFI, включающий загрузку по сети." + +#. Tag: title +#: boot-installer.xml:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "Настройка сервера" + +#. Tag: para +#: boot-installer.xml:1538 +#, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" +"Соответствующая запись TFTP для загрузки по сети системы IA-64 выглядит так: " +"\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" +" Заметьте, что цель — получить запущенный " +"elilo.efi на клиенте." + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" +"Распакуйте файл netboot.tar.gz в каталог, используемый " +"как корневой на tftp сервере. Обычно корень tftp содержится в /var/" +"lib/tftp или /tftpboot. Создастся дерево " +"каталогов debian-installer, содержащее загрузочные " +"файлы для системы IA-64." + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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 "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" + +#. Tag: para +#: boot-installer.xml:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" +"Файл netboot.tar.gz содержит файл elilo.conf, который должен работать на большинстве машин. Однако, если вам " +"нужно изменить этот файл, то он находится в каталоге debian-" +"installer/ia64/. Можно создать различные конфигурационные файлы " +"для различных клиентов, назвав их по IP-адресу клиента, записанном в " +"шестнадцатеричной системе и с суффиксом .conf. " +"Подробней смотрите документацию в пакете elilo." + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "Настройка клиента" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" +"Для настройки клиента на загрузку по TFTP, загрузитесь в EFI и войдите в " +"Boot Option Maintenance Menu. " +" Add a boot option. Там " +"вы должны увидеть одну или более строк с текстом Load File [Acpi" +"()/.../Mac()]. Если есть более одной строки, выберите ту, " +"которая содержит MAC адрес интерфейса с которого вы будете загружаться. " +"Используйте клавиши стрелок, затем нажмите enter. " +" Введите имя записи Netboot и нечто " +"подобное, сохраните, и выйдите обратно в загрузочное меню. Вы должны увидеть только что созданную запись, а " +"её выбор должен инициировать DHCP запрос, после чего загрузку по TFTP файла " +"elilo.efi с сервера." + +#. Tag: para +#: boot-installer.xml:1608 +#, 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 "" +"Системный загрузчик покажет своё приглашение после получения и обработки " +"своего файла настройки. С этого момента установка продолжится также как и " +"установка с CD. Выберите пункт загрузки, который приведён выше и когда ядро " +"полностью установится из сети, запустится программа установки Debian." + +#. Tag: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "Выбор способа установки" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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 "" +"На некоторых субархитектурах &arch-title; есть вариант загрузки с " +"использованием либо ядра linux 2.4.x, либо 2.2.x. Когда такой выбор " +"существует, попробуйте ядро 2.4.x. Программа установки должна требовать " +"меньше памяти, когда используется ядро 2.4.x, потому что поддержка 2.2.x " +"требует ramdisk фиксированного размера, а 2.4.x использует tmpfs." + +#. Tag: para +#: boot-installer.xml:1640 +#, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "" +"Если вы используете ядро версии 2.2.x, может потребоваться установить " +"параметр ядра &ramdisksize;." + +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "" +"Убедитесь, что одним из параметров вашего ядра является root=/dev/" +"ram." + +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"При возникновении трудностей почитайте cts's &arch-title; debian-installer FAQ." + +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "Amiga" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"Единственным способом установки на amiga является жёсткий диск (смотрите " +"). Другими словами, с компакт-" +"диска загрузиться не удастся." + +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "" +"Amiga does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"Amiga в данный момент не работает с bogl, так что если вы видите ошибки " +"bogl, добавьте параметр ядра fb=false." + +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "Atari" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "" +"The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" +"Программа установки для atari может быть запущена с жёсткого диска (смотрите " +") или с дискет (смотрите ). Другими словами, с компакт-диска " +"загрузиться не удастся." + +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "" +"Atari does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"Atari в данный момент не работает с bogl, так что если вы видите ошибки " +"bogl, добавьте параметр ядра fb=false." + +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "BVME6000" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" +"Программа установки для BVME6000 может быть запущена с компакт-диска " +"(смотрите ), с дискет (смотрите ) или по сети (смотрите )." + +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "Macintosh" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"). In other words the cdrom is not " +"bootable. Macs do not have a working 2.4.x kernel." +msgstr "" +"Единственным способом установки на mac является жёсткий диск (смотрите ). Другими словами, с компакт-диска " +"загрузиться не удастся. Для mac нет работоспособного ядра 2.4.x." + +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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 "" +"Если в вашем аппаратном обеспечении используется scsi шина, основанная на " +"чипе 53c9x, то вам может понадобиться добавить параметр ядра " +"mac53c9x=1,0. Для аппаратуры с двумя scsi шинами, " +"например, Quadra 950, нужно указать mac53c9x=2,0. Или " +"же можно указать параметр mac53c9x=-1,0, при котором " +"автоопределение остаётся включённым, но запрещаются SCSI отключения. " +"Заметим, что такой параметр требуется указывать только если имеется более " +"одного жёсткого диска; без параметра система будет работать быстрее." + +#. Tag: title +#: boot-installer.xml:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "MVME147 и MVME16x" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" +"Программа установки для MVEM147 и MVEM16x может быть запущена с дискет" +"(смотрите ) или из сети (смотрите " +"). Другими словами, с компакт-диска " +"загрузиться не удастся." + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" +"Единственным способом установки на Q40/Q60 является жёсткий диск (смотрите " +"). Другими словами, с компакт-" +"диска загрузиться не удастся." + +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "Загрузка с жёсткого диска" + +# index.docbook:1664, index.docbook:2162 +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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 "" +"Загрузка из существующей операционной системы часто самый удобный вариант; " +"для некоторых систем это единственный поддерживаемый метод установки." + +# index.docbook:1670, index.docbook:2168 +#. Tag: para +#: boot-installer.xml:1769 boot-installer.xml:2367 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"Чтобы загрузить программу установки с жёсткого диска, вы уже должны были " +"скачать и положить в нужное место требуемые файлы, как описано в ." + +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" +"Как минимум шесть различных ramdisk могут быть использованы для загрузки с " +"жёсткого диска, каждый из них имеет три различных типа с поддержкой и без " +"ядра версии 2.2.x (смотрите MANIFEST)." + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" +"Есть три различных типа ramdisk: cdrom, hd-" +"media и nativehd. Они отличаются только " +"источниками установки пакетов. cdrom ramdisk использует " +"cdrom для получения пакетов debian-installer .hd-media " +"ramdisk использует файл iso образа cdrom, расположенный на жёстком диске. И " +"наконец, nativehd ramdisk использует сеть для получения " +"пакетов." + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "Загрузка из AmigaOS" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"В Workbench, запустите процесс установки Linux двойным " +"нажатием на иконку StartInstall в каталоге " +"debian." + +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" +"Возможно, вам придётся дважды нажать клавишу &enterkey; после того как " +"программа установки Amiga выведет некоторую отладочную информацию в окно. " +"После этого, через несколько секунд, экран станет серым. Затем, должен " +"появиться чёрный экран с белым текстом отладочной информации ядра. Эти " +"экраны могут проскочить очень быстро и вы не сможете их прочесть, но это " +"нормально. Через пару секунд должна автоматически загрузиться программа " +"установки, так что вы можете продолжить чтение руководства с ." + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "Загрузка из Atari TOS" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" +"На рабочем столе GEM, процесс установки Linux запускается двойным нажатием " +"на иконку bootstra.prg в каталоге debian и нажатием Ok в окне диалога выбора " +"параметров." + +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" +"Возможно, вам придётся дважды нажать клавишу &enterkey; после того как " +"программа установки Atari выведет некоторую отладочную информацию в окно. " +"После этого, через несколько секунд, экран станет серым. Затем, должен " +"появиться чёрный экран с белым текстом отладочной информации ядра. Эти " +"экраны могут проскочить очень быстро и вы не сможете их прочесть, но это " +"нормально. Через пару секунд должна автоматически загрузиться программа " +"установки, так что вы может продолжить чтение руководства с ." + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "Загрузка из MacOS" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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 "" +"Вы должны оставить изначальную Mac систему и загрузиться из неё. " +"Существенная деталь: когда MacOS приготовится загрузить " +"загрузчик Penguin linux, держите нажатой клавишу shift, " +"чтобы предотвратить загрузку расширений. Если вы не используете MacOS кроме " +"как для загрузки linux, то можете добиться того же удалив все расширения из " +"Mac System Folder. Иначе, расширения могут оказаться загруженными, что " +"вызовет проблемы запуска ядра linux." + +#. Tag: para +#: boot-installer.xml:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" +"Для Mac нужен системный загрузчик Penguin. Если у вас нет " +"программ для работы с архивом Stuffit, воспользуйтесь " +"&penguin19.hfs; — это образ диска hfs с распакованным " +"Penguin. В описано, как " +"скопировать этот образ на дискету." + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." +msgstr "" +"Для запуска процесса установки Linux на рабочем столе MacOS , выполните " +"двойной щелчок по иконке Penguin Prefs в каталоге " +"Penguin. Запустится загрузчик Penguin. Выберите Settings из меню " +"File, щёлкните по вкладке Kernel. " +"Выберите образы ядра (vmlinuz) и ramdisk " +"(initrd.gz) в каталоге install, " +"нажав соответствующие кнопки в верхнем правом углу, чтобы добраться до " +"диалогового окна выбора файлов." + +#. Tag: para +#: boot-installer.xml:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" +"Для задания параметров в Penguin, выберите File -> " +"Settings..., затем перейдите на вкладку " +"Options. Параметры загрузки можно ввести в текстовом " +"поле. Если вы всегда хотите передавать эти параметры, то выберите " +"File -> Save Settings as Default." + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"Закройте диалог Settings, сохраните настройки и " +"запустите процедуру начала загрузки с помощью Boot Nowиз меню File." + +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" +"Загрузчик Penguin выдаст некоторую отладочную информацию " +"в окно. После этого через несколько секунд, экран станет серым. Затем, " +"должен появиться чёрный экран с белым текстом отладочной информации ядра. " +"Эти экраны могут проскочить очень быстро и вы не сможете их прочесть, но это " +"нормально. Через пару секунд должна автоматически загрузиться программа " +"установки, так что вы может продолжить чтение руководства с ." + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "Загрузка из Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "FIXME" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"Программа должна запуститься автоматически, так что вы можете продолжить " +"читать с ." + +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" +"В настоящий момент, единственной субархитектурой &arch-title;, " +"поддерживающей загрузку с CD-ROM является BVME6000." + +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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 "" +"После загрузки системы VMEbus появляется приглашение LILO Boot:. Для загрузки Linux и начала установки соответствующего программного " +"обеспечения Debian с помощью эмулирующего vt102 терминала, в приглашении " +"введите одно из:" + +#. Tag: para +#: boot-installer.xml:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "i6000 &enterkey; для установки на BVME4000/6000" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "i162 &enterkey; для установки на MVME162" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "i167 &enterkey; для установки на MVME166/167" + +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"Вы можете дополнительно добавить строку TERM=vt100 , чтобы " +"использовать эмуляцию терминала vt100, например, i6000 TERM=vt100 " +"&enterkey;." + +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" +"Для большинства архитектур &arch-title; рекомендуется загрузка с локальной " +"файловой системы." + +#. Tag: para +#: boot-installer.xml:2054 +#, 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 "" +"На данный момент, загрузка с загрузочной дискеты поддерживается только для " +"Atari и VME (с дисководом гибких дисков SCSI на VME)." + +# index.docbook:1972, index.docbook:2015 +#. Tag: title +#: boot-installer.xml:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "Загрузка SGI с сервера TFTP" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" +"After entering the command monitor use \n" +"bootp():\n" +" 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 netaddr environment variable. Type " +"\n" +"unsetenv netaddr\n" +" in the command monitor to do this." +msgstr "" +"На компьютерах SGI для загрузки linux и начала установки Debianпосле входа в " +"командный монитор используйте \n" +"bootp():\n" +". Чтобы сделать это, вам может понадобиться " +"сбросить переменную среды netaddr. Для этого наберите " +"\n" +"unsetenv netaddr\n" +" в командном мониторе." + +# index.docbook:1988, index.docbook:2035 +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 +#: boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "Загрузка Broadcom BCM91250A и BCM91480B с сервера TFTP" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: " +"\n" +"ifconfig eth0 -auto\n" +" Once you have obtained an IP address, you can " +"load SiByl with the following command: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 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 "" +"На платах Broadcom BCM91250A и eBCM91480B с сервера TFTP загружается " +"системный загрузчик SiByl, который затем загружает и запускает программу " +"установки Debian. В большинстве случаев, сначала вам нужно получить IP-адрес " +"по DHCP, но также возможно настроить адрес статически. Чтобы использовать " +"DHCP, вы можете ввести следующую команду в строке приглашения CFE: " +"\n" +"ifconfig eth0 -auto\n" +" После получения IP-адреса, вы можете загрузить " +"SiByl с помощью следующей команды: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" Вместо приведённого в этом примере IP-адреса вам " +"нужно указать или имя или IP-адрес TFTP сервера. После выполнения этой " +"команды, программа установки будет загружена автоматически." + +# index.docbook:2012, index.docbook:2491 +#. Tag: title +#: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "Параметры загрузки" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" +"На компьютерах SGI вы можете добавлять параметры загрузки в команду " +"bootp(): в мониторе команд." + +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" +"Following the bootp(): 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: \n" +"bootp():/boot/tftpboot.img\n" +" Further kernel parameters can be passed via " +"append:" +msgstr "" +"После команды bootp(): вы можете задать путь и имя " +"загружаемого файла, если вы не получаете это имя явно с bootp/dhcp сервера. " +"Пример: \n" +"bootp():/boot/tftpboot.img\n" +" Дополнительные параметры ядра могут быть указаны " +"через append:" + +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "bootp(): append=\"root=/dev/sda1\"" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the /boot/sibyl.conf file on the TFTP " +"server and add your parameters to the extra_args " +"variable." +msgstr "" +"Вы не можете передавать параметры прямо из приглашения CFE. Вместо этого, вы " +"должны отредактировать файл /boot/sibyl.conf на TFTP " +"сервере и добавить ваши параметры в переменную extra_args." + +# index.docbook:1972, index.docbook:2015 +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "Загрузка Cobalt с сервера TFTP" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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 "" +"Собственно говоря, Cobalt использует для загрузки NFS, а не TFTP. Вам " +"потребуется установить NFS сервер и положить файлы программы установки в " +"каталог /nfsroot. При загрузки Cobalt, нужно " +"одновременно нажать левую и правую клавиши курсора и машина будет загружена " +"по сети с NFS сервера. На экране будут показаны несколько параметров. Есть " +"два метода установки:" + +#. Tag: para +#: boot-installer.xml:2170 +#, 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 "" +"По SSH (по умолчанию): В этом случае, программа установки выполнит настройку " +"сети по DHCP и запустит SSH сервер. Затем она покажет случайный пароль и " +"другую информацию для входа (например, IP-адрес) на Cobalt LCD. После " +"подключения к машине с помощью SSH клиента, вы можете начать установку." + +#. Tag: para +#: boot-installer.xml:2179 +#, 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 "" +"Через последовательный порт: С помощью нуль-модемного кабеля, вы можете " +"подключиться к последовательному порту Cobalt (на скорости 115200 bps) и " +"выполнить установку. Этот способ не работает на машинах Qube 2700 (Qube1), " +"так как они не имеют последовательного порта." + +#. Tag: para +#: boot-installer.xml:2222 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"/nfsroot/default.colo file on the NFS server and add " +"your parameters to the args variable." +msgstr "" +"Вы не можете передать параметры загрузки напрямую. Вместо этого, вы должны " +"отредактировать файл /nfsroot/default.colo на NFS " +"сервере и добавить параметры в переменную args." + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "Ограничения s390" + +#. Tag: para +#: boot-installer.xml:2251 +#, no-c-format +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" +"Для запуска системы установки на S/390 необходима работающая настройка сети " +"и ssh-сессия." + +#. Tag: para +#: boot-installer.xml:2256 +#, 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 an ssh session which will launch the standard installation " +"system." +msgstr "" +"Процесс загрузки начинается с настройки сети, запрашивая у вас некоторые " +"параметры. Если настройка прошла успешна, вы войдете в систему через ssh-" +"сессию, которая запустит стандартную систему установки." + +# index.docbook:2012, index.docbook:2491 +#. Tag: title +#: boot-installer.xml:2267 +#, no-c-format +msgid "s390 Boot Parameters" +msgstr "Параметры загрузки s390" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more " +"information about S/390-specific boot parameters." +msgstr "" +"На S/390 вы можете добавить параметры загрузки в файле parm. Этот файл может " +"быть как в ASCII так и в EBCDIC формате. Подробную информацию о параметрах " +"загрузки для S/390 читайте в Device " +"Drivers and Installation Commands." + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, " +"Option, Shift, and Delete " +"keys together while booting to boot from the CD-ROM." +msgstr "" +"В настоящее время на &arch-title; только субархитектуры PReP и New World " +"PowerMacs поддерживают загрузку с компакт-диска. На PowerMacs нажмите " +"клавишу c, или комбинацию клавиш Command, " +"Option, Shift, и Delete " +"вместе во время загрузки для того, чтобы загрузиться с компакт-диска." + +#. Tag: para +#: boot-installer.xml:2331 +#, 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 "" +"Компьютеры OldWorld Powermac не загружаются с компакт-диска Debian, потому " +"что компьютеры OldWorld полагаются на присутствие на компакт-диске " +"загрузочного драйвера Mac OS ROM, а свободно доступной версии этого драйвера " +"нет. На всех системах OldWorld есть приводы для дискет, так что используйте " +"дискету, чтобы запустить программу установки, а затем укажите ей компакт-" +"диск с нужными файлами." + +#. Tag: para +#: boot-installer.xml:2340 +#, 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 for booting from the hard disk, except use the " +"path to yaboot on the CD at the OF prompt, such as" +msgstr "" +"Если ваша система не загружается напрямую с компакт-диска, вы всё ещё можете " +"использовать его для установки системы. На NewWorld вы также можете " +"использовать команду OpenFirmware для загрузки с компакт-диска вручную. " +"Следуйте инструкциям из для загрузки с " +"жёсткого диска, за исключением использования пути к yaboot на компакт-диске в подсказке OF, такой как" + +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "0 > boot cd:,\\install\\yaboot" + +#. Tag: title +#: boot-installer.xml:2355 +#, no-c-format +msgid "Booting from Hard Disk" +msgstr "Загрузка с жёсткого диска" + +# index.docbook:807, index.docbook:1949, index.docbook:2282, index.docbook:2442 +#. Tag: title +#: boot-installer.xml:2376 +#, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "Загрузка CHRP из OpenFirmware" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "Ещё не написано." + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "Загрузка OldWorld PowerMac из MacOS" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"If you set up BootX in , you can use it to " +"boot into the installation system. Double click the BootX " +"application icon. Click on the Options button and " +"select Use Specified RAM Disk. This will give you the " +"chance to select the ramdisk.image.gz file. You may " +"need to select the No Video Driver checkbox, depending " +"on your hardware. Then click the Linux button to shut " +"down MacOS and launch the installer." +msgstr "" +"Если вы настроите BootX в , то сможете " +"использовать его для загрузки системы установки. Выполните двойной щелчок на " +"иконке приложения BootX. Нажмите кнопку " +"Options и выберите Use Specified RAM Disk. Это позволит выбрать файл ramdisk.image.gz. " +"Вам может понадобиться установить галочку в No Video Driver, в зависимости от аппаратного обеспечения. Затем нажмите кнопку " +"Linux для выключения MacOS и запуска программы " +"установки." + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "Загрузка NewWorld Mac из OpenFirmware" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" +"You will have already placed the vmlinux, " +"initrd.gz, yaboot, and " +"yaboot.conf files at the root level of your HFS " +"partition in . Restart the computer, and " +"immediately (during the chime) hold down the Option, " +"Command (cloverleaf/Apple), o, and " +"f keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"\n" +"0 > boot hd:x,yaboot\n" +" replacing x 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 " +"ide0: instead of hd:. In a few " +"more seconds you will see a yaboot prompt \n" +"boot:\n" +" At yaboot's boot: prompt, type " +"either install or install video=ofonly followed by a &enterkey;. The video=ofonly " +"argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" +"Вы должны были уже скопировать файлы vmlinux, " +"initrd.gz, yaboot и " +"yaboot.conf в корень раздела HFS как описано в . Перезагрузите компьютер и быстро(во время " +"звукового сигнала) одновременно зажмите клавиши Option, " +"Command (cloverleaf/Apple), o и f. Через несколько секунд вы увидите приглашение Open Firmware. " +"Наберите \n" +"0 > boot hd:x,yaboot\n" +" заменив x номером " +"раздела HFS, на котором лежат файлы ядра и yaboot и нажмите &enterkey;. На " +"некоторых машинах, вам нужно использовать ide0:, а не " +"hd:. Ещё через несколько секунд вы увидите " +"приглашение yaboot \n" +"boot:\n" +" В приглашении yaboot boot: " +"введите или install или install " +"video=ofonly и нажмите &enterkey;. Параметр " +"video=ofonly нужен для максимальной совместимости; вы " +"можете попробовать указать его, если install не " +"сработает. После должна запуститься программа установки Debian." + +#. Tag: title +#: boot-installer.xml:2440 +#, no-c-format +msgid "Booting from USB memory stick" +msgstr "Загрузка с карты памяти USB" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" +"В настоящий момент системы NewWorld PowerMac можно загружать с USB устройств." + +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "" +"Make sure you have prepared everything from . 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 " +"Command Option o f all together while booting (see )." +msgstr "" +"Проверьте, что вы сделали всё как написано в . Для загрузки системы Macintosh с карт памяти USB нужно использовать " +"микропрограмму Open Firmware, так как по умолчанию Open Firmware не ищет " +"загрузочные устройства среди USB носителей. Чтобы получить приглашение к " +"вводу команд во время загрузки держите одновременно нажатыми клавиши " +"Command Option o f (смотрите )." + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment ofpath cannot work that out " +"automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " +"/pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" +"Далее, вам необходимо выяснить, в каком месте дерева устройств появилась " +"карта памяти USB, так как в настоящее время ofpath не " +"может выяснить этого автоматически. Введите dev / ls " +"и devalias в приглашении Open Firmware, чтобы " +"получить список всех найденных устройств и их псевдонимов. У автора этого " +"документа на системе различные типы карт памяти USB были доступны по " +"следующим путям: usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1 и /" +"pci@f2000000/usb@1b,1/hub@1/disk@1." + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" +"Having worked out the device path, use a command like this to boot the " +"installer: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" The 2 matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the ,\\\\:tbxi part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"yaboot) in the directory previously blessed with " +"hattrib -b." +msgstr "" +"После выяснения пути к устройству, запустите команду загрузки программы " +"установки: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" Цифра 2 соответствует " +"разделу Apple_HFS или Apple_Bootstrap, на который вы ранее скопировали " +"загрузочный образ, а ,\\\\:tbxi говорит Open Firmware " +"загружать из файла с типом HFS \"tbxi\" (то есть yaboot) " +"из каталога ранее установленного с помощью hattrib -b." + +#. Tag: para +#: boot-installer.xml:2485 +#, no-c-format +msgid "" +"The system should now boot up, and you should be presented with the " +"boot: prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." +msgstr "" +"Система должна загрузиться и вы должны увидеть приглашение boot:. Здесь вы можете ввести необязательные параметры загрузки, или " +"просто нажать &enterkey;." + +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" +"Это новый метод загрузки и с ним могут возникнуть некоторые трудности на " +"некоторых системах NewWorld. Если у вас есть проблемы, пожалуйста, отправьте " +"отчёт об установке, как описано в ." + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "" +"В настоящий момент, для систем PReP и New World PowerMac поддерживается " +"загрузка по сети." + +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see ) and use the command " +"boot enet:0. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try boot " +"server_ipaddr,file," +"client_ipaddr." +msgstr "" +"На машинах с Open Firmware, например, NewWorld Power Mac, войдите в " +"загрузочный монитор (смотрите ) и " +"воспользуйтесь командой boot enet:0. Машины PReP и CHRP " +"могут загружаться по сети другим способом. На машине PReP, вы должны " +"попробовать boot server_ipaddr," +"file,client_ipaddr." + +#. Tag: para +#: boot-installer.xml:2543 +#, 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 "" +"Для &arch-title; поддерживается загрузка с дискет, хотя она применяется " +"только для систем OldWorld. Системы NewWorld не имеют приводы гибких дисков, " +"а с подключённых по USB приводов гибких дисков загрузка не поддерживается." + +#. Tag: para +#: boot-installer.xml:2555 +#, no-c-format +msgid "" +"To boot from the boot-floppy-hfs.img floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." +msgstr "" +"Для загрузки с помощью дискеты boot-floppy-hfs.img, " +"вставьте её в дисковод после выключения системы и перед включением питания." + +#. Tag: para +#: boot-installer.xml:2561 +#, 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 "" +"Для тех, кто не знает как работать с дискетами на Macintosh: дискета " +"вставленная в машину перед загрузкой, будет иметь приоритет при загрузке " +"системы. Незагрузочная дискета будет извлечена из дисковода, а затем машина " +"проверит на загружаемость разделы жёсткого диска." + +#. Tag: para +#: boot-installer.xml:2568 +#, no-c-format +msgid "" +"After booting, the root.bin 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 "" +"После загрузки, появится запрос дискеты root.bin. " +"Вставьте соответствующую дискету и нажмите &enterkey;. Программа установки " +"запустится автоматически после загрузки корневой файловой системы в память." + +# index.docbook:2012, index.docbook:2491 +#. Tag: title +#: boot-installer.xml:2579 +#, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "Параметры загрузки PowerPC" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 " +"video=atyfb:vmode:6 , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"video=aty128fb:vmode:6 ." +msgstr "" +"Многие старые мониторы Apple работают в режиме 640x480 67Гц. Если на старом " +"мониторе Apple изображение выводится перекошенным, попробуйте добавить " +"параметр загрузки video=atyfb:vmode:6 , который " +"включает этот режим на большинстве видеокарт Mach64 и Rage. Для Rage 128 " +"нужно использовать параметр video=aty128fb:vmode:6." + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see ). Use " +"the command boot net to boot from a TFTP and RARP " +"server, or try boot net:bootp or boot net:" +"dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " +"OpenBoot revisions require using the device name, such as boot le" +"(); these probably don't support BOOTP nor DHCP." +msgstr "" +"На машинах с OpenBoot, просто войдите в загрузочный монитор машины, на " +"которую производится установка (смотрите ). Используйте команду boot net для загрузки с TFTP " +"и RARP сервера, или попробуйте boot net:bootp или " +"boot net:dhcp для загрузки с TFTP и BOOTP или DHCP " +"сервера. Некоторые старые версии OpenBoot требуют указывать имя устройства, " +"например, boot le(); вероятно, на них не работает " +"поддержка BOOTP и DHCP." + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "" +"Most OpenBoot versions support the boot cdrom 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 "" +"Большинство версий OpenBoot поддерживают команду boot cdrom, которая является простым псевдонимом загрузки с устройства SCSI " +"с ID 6 (или вторичного мастера для систем с IDE). Возможно придётся " +"использовать настоящее имя устройства в старых версиях OpenBoot, которые не " +"поддерживают эту специальную команду. Заметим, что при загрузке с CD-ROM на " +"системах Sun4m (например, Sparc 10s и Sparc 20s) иногда возникают проблемы." + +#. Tag: para +#: boot-installer.xml:2691 +#, no-c-format +msgid "" +"To boot from floppy on a Sparc, use \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"Bad magic number in disk label - Can't open disk label " +"package. 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 "" +"Для загрузки с дискеты на Sparc, используйте \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Не забудьте, что новая архитектура Sun4u (ultra) " +"не поддерживает загрузку с дискет. Обычно, выводится сообщение об ошибке: " +"Bad magic number in disk label - Can't open disk label " +"package. Кроме того, некоторые модели Sun4c (такие как IPX) " +"не поддерживают сжатые образы дисков, поэтому загрузка с дискет также не " +"поддерживается." + +#. Tag: para +#: boot-installer.xml:2703 +#, 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 ." +msgstr "" +"Некоторые Sparc (например, Ultra 10) имеют ошибку OBP, которая не даёт им " +"загрузиться (они вообще отказываются загружаться). Соответствующее " +"обновление OBP можно загрузить как продукт с ID 106121 с ." + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"If you are booting from the floppy, and you see messages such as " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" then it is possible that floppy booting is " +"simply not supported on your machine." +msgstr "" +"Если вы загружаетесь с дискеты и видите такое " +"сообщение\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +", то возможно, загрузка с дискет просто не " +"поддерживается на этой машине." + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "Сообщения IDPROM" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"IDPROM, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"Sun NVRAM FAQ for more " +"information." +msgstr "" +"Если вы не можете загрузиться и получаете сообщение о проблеме с " +"IDPROM, то возможно, это из-за севшей батарейки NVRAM, " +"которая содержит конфигурационную информацию микропрограммы. Подробней " +"смотрите в Sun NVRAM FAQ." + +#. Tag: para +#: boot-installer.xml:2742 +#, 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 "" +"Параметры загрузки — это параметры ядра Linux, которые обычно " +"используются для того, чтобы указать присутствующие периферийные устройства. " +"В большинстве случаев ядро может определить периферийные устройства " +"автоматически. Однако, иногда вы должны немного помочь ядру." + +#. Tag: para +#: boot-installer.xml:2749 +#, 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:2756 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +"Информацию о многих параметрах загрузки можно найти в Linux BootPrompt HOWTO, " +"где можно найти советы советы и по нераспознанному оборудованию. В этом " +"разделе содержатся только краткие сведения о наиболее важных параметрах. " +"Некоторые распространённые ошибки включены ниже в ." + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" +"When the kernel boots, a message \n" +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total 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 mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" +"В самом начале при загрузке ядра должно появиться сообщение: " +"\n" +"Memory:availk/totalk " +"available \n" +"Значение total должно " +"совпадать с общим количеством ОЗУ в килобайтах. Если оно не соответствует " +"действительно установленному объёму ОЗУ, вам надо использовать параметр " +"mem=ram, где " +"ram равно объёму памяти, дополненному буквой " +"k, если объём задан в килобайтах или m, если в " +"мегабайтах. Например, mem=65536k или " +"mem=64m означают 64МБ ОЗУ." + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this (although not on DECstations). 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 console=device " +"argument to the kernel, where device is your " +"serial device, which is usually something like ttyS0." +msgstr "" +"Если вы загружаетесь через консоль на последовательном порту, обычно ядро " +"обнаруживает это автоматически (кроме DECstations). Если к компьютеру подключёны видеокарта (framebuffer) и клавиатура, " +"а вы хотите загрузиться через консоль на последовательном порту, вам надо " +"передать ядру параметр console=device, где device — это имя " +"последовательного порта, обычно ttyS0." + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"Для &arch-title; последовательными устройствами являются ttya или ttyb. Или же установите переменные " +"OpenPROM input-device и output-device равными " +"ttya." + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "Параметры программы установки Debian" + +#. Tag: para +#: boot-installer.xml:2806 +#, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"Система установки анализирует некоторые дополнительные параметры " +"загрузки Новые версии ядер (2.6.9 и новее) позволяют " +"использовать 32 параметра в командной строке и 32 переменные среды. " +", что может быть полезно." + +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "debconf/priority" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"Этот параметр задаёт низший приоритет отображаемых сообщений. Сокращённая " +"форма: priority" + +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "" +"The default installation uses priority=high. 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 "" +"Значение по умолчанию равно priority=high. Это " +"означает, что будут показаны сообщения с высоким и с критическим " +"приоритетами, а сообщения со средним и низким приоритетами будут пропущены. " +"В случае возникновения проблем, программа установки подстраивает значение " +"приоритета." + +#. Tag: para +#: boot-installer.xml:2836 +#, no-c-format +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"Если вы добавите priority=medium в качестве параметра " +"загрузки, то увидите меню программы установки и получите больший контроль " +"над установкой. При использовании priority=low " +"показываются все сообщения (эквивалентно методу загрузки expert). Если указать priority=critical, то " +"система установки будет показывать только критические сообщения и попробует " +"всё сделать правильно самостоятельно." + +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "DEBIAN_FRONTEND" + +#. Tag: para +#: boot-installer.xml:2851 +#, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " +" The default frontend is " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text may be preferable for serial " +"console installs. Generally only the newt frontend is " +"available on default install media. On architectures which support it, the " +"graphical installer uses the gtk frontend." +msgstr "" +"Этот параметр загрузки контролирует тип пользовательского интерфейса, " +"используемого программой установки. Возможные на текущий момент значения " +"параметра: " +"DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +" DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk По умолчанию выбран тип " +"DEBIAN_FRONTEND=newt. Для установки через консоль на " +"последовательном порту наиболее предпочтителен " +"DEBIAN_FRONTEND=text . Вообще, с носителей установки " +"по умолчанию в данный момент доступен только интерфейс newt. На некоторых архитектурах используется графический интерфейс " +"программы установки gtk." + +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "BOOT_DEBUG" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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 "" +"Присвоение этому загрузочному параметру значения 2 приводит к более " +"подробному протоколированию процесса загрузки программы установки. Значение " +"3 приводит к запуску интерпретатора командной строки в наиболее важных " +"точках процесса загрузки. (Завершение работы с интерпретатором приводит к " +"продолжению процесса загрузки.)" + +#. Tag: userinput +#: boot-installer.xml:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "BOOT_DEBUG=0" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "Значение по умолчанию." + +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "BOOT_DEBUG=1" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "Подробней чем обычно." + +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "BOOT_DEBUG=2" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "Много отладочной информации." + +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "BOOT_DEBUG=3" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "INSTALL_MEDIA_DEV" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"Значением этого параметра является путь к устройству, с которого загружается " +"программа установки Debian. Например, INSTALL_MEDIA_DEV=/dev/" +"floppy/0" + +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." +msgstr "" +"Загрузочная дискета в поисках корневой дискеты сканирует все дискеты и USB " +"устройства хранения. Этим параметром можно заставить её искать корневую " +"дискету только на избранном устройстве." + +#. Tag: term +#: boot-installer.xml:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "debian-installer/framebuffer" + +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/" +"framebuffer=false, or fb=false for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." +msgstr "" +"Некоторые архитектуры используют framebuffer ядра, чтобы предложить " +"установку на нескольких языках. Если использование framebuffer вызывает " +"проблемы на вашей системе, можно выключить его параметром debian-" +"installer/framebuffer=false или сокращённое fb=false. Симптомы проблемы — сообщения об ошибках bterm или bogl, " +"пустой экран или замирание на несколько минут в начале установки." + +#. Tag: para +#: boot-installer.xml:2948 +#, no-c-format +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"Аргумент video=vga16:off также может быть использован " +"для запрета framebuffer. Подобные проблемы замечены на Dell Inspiron с " +"картой Mobile Radeon." + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "Подобные проблемы замечены на Amiga 1200 и SE/30." + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "Подобные проблемы замечены на hppa." + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"disabled by default 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 debian-installer/" +"framebuffer=true or fb=true for short." +msgstr "" +"Для &arch-title; поддержка framebuffer по умолчанию выключена из-за проблем с отображением на некоторых системах. В свою очередь " +"это может привести к неправильному отображению на системах с нормально " +"поддерживаемым framebuffer, типа графических карт ATI. Если у вас возникли " +"проблемы с отображением в программе установки, можно попробовать загрузиться " +"с параметром debian-installer/framebuffer=true или " +"для краткости fb=true." + +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a dark theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter debian-installer/theme=dark or theme=dark." +msgstr "" +"Темой определяется вид пользовательского интерфейса программы установки " +"(раскраска, иконки и т.д.). У каждого интерфейса есть свои темы. В настоящий " +"момент для интерфейсов newt и gtk есть только одна тема dark, " +"которая была специально разработана для людей с ослабленным зрением. Для " +"установки темы загрузитесь с параметром debian-installer/" +"theme=dark или " +"theme=dark." + +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "debian-installer/probe/usb" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "" +"Установите в false, чтобы избежать проверки USB при " +"загрузке, если это вызывает проблемы." + +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "netcfg/disable_dhcp" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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 "" +"По умолчанию, &d-i; автоматически пытается настроить сеть через DHCP. Если " +"получение адреса прошло успешно, у вас не будет шанса пересмотреть и " +"изменить полученные настройки. Вы сможете настроить сеть вручную только в " +"случае ошибок при работе с DHCP." + +#. Tag: para +#: boot-installer.xml:3008 +#, 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 " +"netcfg/disable_dhcp=true to prevent configuring the " +"network with DHCP and to enter the information manually." +msgstr "" +"Если в вашей локальной сети есть DHCP сервер, но вы не хотите его " +"использовать, потому что он, например, дает неправильные ответы, можете " +"указать параметр netcfg/disable_dhcp=true, чтобы " +"отключить настройку сети по DHCP и ввести информацию вручную." + +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "hw-detect/start_pcmcia" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"Установите в false, чтобы избежать запуска PCMCIA " +"сервисов, если это вызывает проблемы. Особенно полезно для некоторых " +"ноутбуков." + +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "preseed/url" + +#. Tag: para +#: boot-installer.xml:3031 +#, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url." +msgstr "" +"Задайте url для загрузки файла с настройками и использования автоматической " +"установки. Смотрите . Сокращённая " +"форма: url." + +#. Tag: term +#: boot-installer.xml:3041 +#, no-c-format +msgid "preseed/file" +msgstr "preseed/file" + +#. Tag: para +#: boot-installer.xml:3042 +#, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file." +msgstr "" +"Задайте файл для загрузки настроек автоматической установки. Смотрите . Сокращённая форма: file." + +#. Tag: term +#: boot-installer.xml:3052 +#, no-c-format +msgid "auto-install/enabled" +msgstr "auto-install/enabled" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" +"Отложить вопросы, которые обычно задаются перед автоматической установкой, " +"которые можно задать после настройки сети. Сокращённая форма: " +"auto=true Подробней об автоматизации установки " +"смотрите в ." + +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "cdrom-detect/eject" + +#. Tag: para +#: boot-installer.xml:3065 +#, 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 "" +"По умолчанию перед перезагрузкой, &d-i; автоматически извлекает компакт-" +"диск, который использовался при установке. Это делать необязательно, если " +"система система не загружается с компакт-диска автоматически. В некоторых " +"случаях это даже нежелательно, например, если устройство чтения не может " +"самостоятельно загрузить компакт-диск и пользователь не может сделать это " +"вручную. Многие устройства со слотовой загрузкой, slim-line и caddy не " +"способны загружать носитель автоматически." + +#. Tag: para +#: boot-installer.xml:3074 +#, no-c-format +msgid "" +"Set to false 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 "" +"Чтобы запретить автоматическое извлечение задайте значение false, но проверьте, что система не загружается автоматически с компакт-" +"диска после начальной установки." + +#. Tag: term +#: boot-installer.xml:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "ramdisk_size" + +#. Tag: para +#: boot-installer.xml:3086 +#, no-c-format +msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgstr "" +"Если вы используете ядро 2.2.x, может потребоваться установить &ramdisksize;." + +#. Tag: term +#: boot-installer.xml:3094 +#, no-c-format +msgid "mouse/left" +msgstr "mouse/left" + +#. Tag: para +#: boot-installer.xml:3095 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to true." +msgstr "" +"В интерфейсе gtk (графическая программа установки) пользователи могут " +"настроить мышь под левую руку, установив данный параметр равным " +"true." + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "directfb/hw-accel" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"true when booting the installer." +msgstr "" +"В интерфейсе gtk (графическая программа установки), по умолчанию выключено " +"аппаратное ускорение в directfb. Для включения установите данный параметр " +"равным true при загрузке программы установки." + +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "rescue/enable" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"Установка в true активирует режим восстановления, " +"вместо обычного режима установки. Смотрите ." + +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "Использование параметров загрузки для ответов на вопросы" + +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" +"За некоторым исключением, в приглашении к загрузке можно задать любые " +"значения ответов на вопросы установки, хотя это полезно только в " +"специфических случаях. Описание как это делать можно найти в . Некоторые специальные примеры даны ниже." + +#. Tag: term +#: boot-installer.xml:3140 +#, no-c-format +msgid "debian-installer/locale" +msgstr "debian-installer/locale" + +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. Short form: " +"locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" +"Может использоваться для указания языка и страны для установки. Это работает " +"только если данная локаль поддерживается Debian. Сокращённая форма: " +"locale. Например, введите locale=de_CH, чтобы выбрать немецкий язык и Швейцарию как страну." + +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "" +"Set to true if you want to disable DHCP and instead " +"force static network configuration." +msgstr "" +"Установите в true, если хотите выключить DHCP и " +"задать настройки сети статически." + +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "tasksel:tasksel/first" + +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" +"Может быть использована для выбора задач, которых нет в списке выбора в " +"программе установки, например задача kde-desktop. " +"Подробней смотрите в . Сокращённая форма: " +"tasks." + +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "Передача параметров модулям ядра" + +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" +"Если драйверы встроены в ядро, вы можете передать им параметры как это " +"описано в документации к ядру. Если же драйверы собраны как модули и так как " +"модули ядра загружаются немного по-другому чем при загрузке установленной " +"системы, невозможно передать параметры модулям обычным способом. Вместо " +"этого вам нужно использовать специальный синтаксис, распознаваемый " +"программой установки, которая сохраняет эти параметры в нужные " +"конфигурационные файлы, для того чтобы использовать их при загрузке модуля. " +"Параметры также будут автоматически включены в конфигурацию установленной " +"системы." + +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" +"Заметим, что теперь редко требуется указывать параметры модулям. В " +"большинстве случаев ядро способно само определить имеющееся оборудование в " +"системе и настроить его правильно. Однако иногда всё ещё может потребоваться " +"установка параметров вручную." + +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" +"Синтаксис установки параметров модулей: \n" +"имя_модуля.имя_параметра=значение\n" +" Если требуется передать несколько параметров " +"одному или разным модулям, то выражение повторяют. Например, чтобы указать " +"старым сетевым картам 3Com использовать BNC (коаксиальный) разъём и IRQ 10, " +"вы должны написать:" + +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "3c509.xcvr=3 3c509.irq=10" + +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "Диагностика проблем процесса установки" + +#. Tag: title +#: boot-installer.xml:3226 +#, no-c-format +msgid "CD-ROM Reliability" +msgstr "Надёжность CD-ROM" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" +"Иногда, особенно в старых приводах CD-ROM, программа установки может не " +"загрузиться с CD-ROM. Программа установки также может (даже после успешной " +"загрузки с CD-ROM) не распознать CD-ROM или выдавать ошибки при чтении во " +"время установки." + +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" +"Такие проблемы могут возникать по разным причинам. Мы можем описать только " +"общие из них и предложить общие решения. Остальное зависит от вас." + +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "" +"Есть несколько простых вещей, которые вы можете попробовать сделать в первую " +"очередь." + +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" +"Если с CD-ROM не получается загрузиться, проверьте, что он вставлен " +"правильно и что диск не грязный." + +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" +"Если программа установки не смогла определить CD-ROM, попробуйте выполнить " +"пункт меню Поиск и монтирование CD-ROM второй раз. Некоторые проблемы с DMA на старых " +"приводах CD-ROM решаются таким способом." + +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" +"Если это не сработало, попробуйте советы данные ниже. Хотя большинство, но " +"не все, описываемые предложения работают и для CD-ROM и для DVD, для " +"простоты мы будем использовать термин CD-ROM." + +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" +"Если вы не можете заставить программу установки работать с CD-ROM, " +"попробуйте, если возможно, другой метод установки." + +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "Общие причины" + +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" +"Некоторые старые приводы CD-ROM не поддерживают чтение с дисков, которые " +"были записаны на высоких скоростях в современных устройствах записи CD." + +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" +"Если система корректно загружается с CD-ROM, это совсем не значит, что Linux " +"также поддерживает CD-ROM (или, если более точно, контроллер, к которому " +"подключён привод CD-ROM)." + +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" +"Некоторые старые приводы CD-ROM работают неправильно, если включён " +"прямой доступ к памяти (DMA)." + +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "Как изучать и может быть решить проблему" + +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" +"Если с CD-ROM не удаётся загрузиться, попробуйте способы указанные ниже." + +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" +"Проверьте, что в BIOS включена загрузка с CD-ROM (возможно, старые машины " +"этого не умеют), и что привод CD-ROM поддерживает используемый тип носителя." + +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" +"Если вы скачивали образ iso, проверьте, что md5sum этого образа совпадает с " +"суммой указанной в файле MD5SUMS, который должен лежать " +"там же, где вы брали образ. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Далее проверьте, что md5sum записанного CD-ROM " +"также совпадает. Следующая команда должна сработать. Здесь считается сумма " +"прочитанных с CD-ROM байт, составляющих образ." + +#. Tag: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" + +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" +"Если после успешной загрузки программы установки не определяется CD-ROM, то " +"иногда помогает просто попробовать ещё раз. Если у вас более одного привода " +"CD-ROM, попробуйте загрузиться с другого CD-ROM. Если это не помогает или " +"если CD-ROM определяется, но при чтении возникают ошибки, попробуйте " +"выполнить предложения, данные ниже. Для этого потребуются азы работы в " +"Linux. Перед тем как выполнить любую команду, сначала вы должны " +"переключиться во вторую виртуальную консоль (VT2) и активировать оболочку " +"командной строки." + +#. Tag: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" +"Переключитесь в VT4 или посмотрите файл /var/log/syslog " +"(в качестве редактора используется nano), чтобы найти " +"сообщения о специфических ошибках. После этого также проверьте вывод команды " +"dmesg." + +#. Tag: para +#: boot-installer.xml:3351 +#, no-c-format +msgid "" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using modprobe." +msgstr "" +"В выводе dmesg проверьте, что привод CD-ROM был найден. " +"Вы должны увидеть что-то типа этого (строки могут быть в другой " +"последовательности): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" Если вы не нашли подобных строк, это случай, " +"когда контроллер, к которому подключён CD-ROM, не распознан или не " +"поддерживается ядром вообще. Если вы знаете, какой драйвер требуется для " +"привода, то можете попытаться загрузить его вручную с помощью команды " +"modprobe." + +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" +"Проверьте, что есть соответствующий файл устройства для привода CD-ROM в " +"каталоге /dev/. Для примера выше, должен существовать " +"файл /dev/hdc. Также может быть /dev/cdroms/" +"cdrom0." + +#. Tag: para +#: boot-installer.xml:3373 +#, no-c-format +msgid "" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" +"$ mount /dev/hdc /cdrom\n" +" Check if there are any error messages after that " +"command." +msgstr "" +"С помощью команды mount проверьте, что CD-ROM уже " +"смонтировать; если нет, попытайтесь смонтировать вручную: " +"\n" +"$ mount /dev/hdc /cdrom\n" +" Проверьте, не появилось ли ошибок после этой " +"команды." + +#. Tag: para +#: boot-installer.xml:3383 +#, no-c-format +msgid "" +"Check if DMA is currently enabled: \n" +"$ cd /proc/ide/hdc\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +" A 1 in the first column after " +"using_dma means it is enabled. If it is, try disabling " +"it: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." +msgstr "" +"Проверьте, включён ли DMA: \n" +"$ cd /proc/ide/hdc\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +" 1 означает включён. Если включён, " +"попробуйте выключить его: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Удостоверьтесь, что находитесь в каталоге для " +"устройства, соответствующего приводу CD-ROM." + +#. Tag: para +#: boot-installer.xml:3398 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" +"Если возникли проблемы во время установки, попробуйте проверить целостность " +"CD-ROM с помощью пункта внизу главного меню программы установки. Этим также " +"можно провести общую проверку надёжности чтения CD-ROM." + +#. Tag: title +#: boot-installer.xml:3413 +#, no-c-format +msgid "Floppy Disk Reliability" +msgstr "Надёжность дискет" + +#. Tag: para +#: boot-installer.xml:3415 +#, no-c-format +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"Надёжность дискет — это, похоже, самая большая проблема для людей, " +"устанавливающих Debian." + +#. Tag: para +#: boot-installer.xml:3420 +#, 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 "" +"Загрузочная дискета — это самая проблемная дискета, потому что она " +"читается аппаратурой напрямую, до загрузки Linux. Часто аппаратура не может " +"читать также надёжно, как драйвер дискет Linux, и может просто остановиться " +"без вывода сообщения об ошибке, если прочитает неправильные данные. Ещё " +"возможны неполадки с дисководом, большинство которых выглядят как поток " +"сообщений об ошибках ввода-вывода (disk I/O error)." + +#. Tag: para +#: boot-installer.xml:3429 +#, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. 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:3438 +#, no-c-format +msgid "" +"One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " +"third floppy." +msgstr "" +"Один пользователь сообщил, что он записывал образ на дискету три раза, прежде чем она заработала, и затем всё пошло нормально." + +#. Tag: para +#: boot-installer.xml:3444 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" +"Обычно не нужно скачивать образ дискет ещё раз, но если вы испытываете " +"проблемы, всегда полезно проверить корректность загруженных образов сверив " +"их md5sum." + +#. Tag: para +#: boot-installer.xml:3450 +#, 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:3459 +#, no-c-format +msgid "Boot Configuration" +msgstr "Настройка загрузки" + +#. Tag: para +#: boot-installer.xml:3461 +#, 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 " +"." +msgstr "" +"Если у вас возникли проблемы и ядро падает во время загрузки, не распознает " +"имеющуюся периферию или неправильно распознаются диски, сперва проверьте " +"параметры загрузки, как это обсуждается в ." + +#. Tag: para +#: boot-installer.xml:3468 +#, no-c-format +msgid "" +"If you are booting with your own kernel instead of the one supplied with the " +"installer, be sure that CONFIG_DEVFS is set in your " +"kernel. The installer requires CONFIG_DEVFS." +msgstr "" +"Если вы загружаете самостоятельно собранное ядро вместо поставляемого с " +"программной установки, проверьте, что в вашем ядре включён параметр " +"CONFIG_DEVFS. Программе установки требуется " +"CONFIG_DEVFS." + +#. Tag: para +#: boot-installer.xml:3475 +#, no-c-format +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic." +msgstr "" +"Часто, проблемы можно решить, убрав дополнения и периферию, а затем " +"попытаться загрузиться ещё раз. Особенно часто проблемы " +"бывают с внутренними модемами, звуковыми картами и устройствами Plug-n-Play." +"" + +#. Tag: para +#: boot-installer.xml:3481 +#, 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 mem=512m." +msgstr "" +"Если на вашей машине установлен большой объём памяти, более чем 512МБ и " +"программа установки виснет при загрузке ядра, то вам может понадобиться " +"указать параметр загрузки для ограничения объёма памяти видимого ядру " +"— mem=512m." + +#. Tag: title +#: boot-installer.xml:3492 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "Распространённые проблемы установки на &arch-title;" + +#. Tag: para +#: boot-installer.xml:3493 +#, 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:3498 +#, no-c-format +msgid "" +"Some systems have floppies with inverted DCLs. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter floppy=thinkpad." +msgstr "" +"Некоторые системы имеют дисковод гибких дисков с обратными DCL. Если вы получаете ошибки чтения с дискеты, даже когда знаете, что " +"она хорошая, попробуйте задать параметр floppy=thinkpad." + +#. Tag: para +#: boot-installer.xml:3504 +#, 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 hd=cylinders," +"heads,sectors." +msgstr "" +"На некоторых системах, таких как IBM PS/1 или ValuePoint (имеющих дисковый " +"драйвер ST-506), привод IDE может быть распознан неправильно. Сначала " +"попробуйте загрузиться без параметров и посмотрите, правильно ли " +"определяется привод IDE. Если нет, выясните геометрию диска (количество " +"цилиндров, головок и секторов) и воспользуйтесь параметром " +"hd=количество цилиндров, " +"количество головок, количество " +"секторов." + +#. Tag: para +#: boot-installer.xml:3513 +#, no-c-format +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"Checking 'hlt' instruction..., then you " +"should try the no-hlt boot argument, which disables " +"this test." +msgstr "" +"Если у вас очень старая машина и ядро зависает после надписи " +"Checking 'hlt' instruction..., то вы должны " +"попробовать параметр загрузки no-hlt, который " +"выключает этот тест." + +#. Tag: para +#: boot-installer.xml:3520 +#, 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 fb=false " +"video=vga16:off to disable the framebuffer console. Only the " +"English language will be available during the installation due to limited " +"console features. See for details." +msgstr "" +"Если во время загрузки ядра экран выглядит странно, например, он полностью " +"белый, чёрный или замусорен разными цветами, то ваша система вероятно имеет " +"проблемную видеокарту, которая неправильно переключается в режим фрейм-" +"буфера. В этом случае, вы можете попробовать параметр загрузки " +"fb=false или video=vga16:off, " +"чтобы выключить фрейм-буфер на консоли. Из-за этого ограничения консоли " +"установка будет доступна только на английском языке. Подробней смотрите в " +"." + +#. Tag: title +#: boot-installer.xml:3534 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "Система подвисает во время настройки PCMCIA" + +#. Tag: para +#: boot-installer.xml:3535 +#, 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 " +"hw-detect/start_pcmcia=false boot parameter. You can " +"then configure PCMCIA after the installation is completed and exclude the " +"resource range causing the problems." +msgstr "" +"Про некоторые модели ноутбуков Dell известно, что они виснут когда при " +"определении PCMCIA устройства производится попытка доступа по некоторым " +"аппаратным адресам. Похожие проблемы могут иметь и другие ноутбуки . Если у " +"вас возникла такая проблема и вам не нужна поддержка PCMCIA во время " +"установки, то вы можете выключить PCMCIA с помощью параметра загрузки " +"hw-detect/start_pcmcia=false. После установки вы " +"сможете настроить PCMCIA, исключив диапазон ресурсов, с которым возникают " +"проблемы." + +#. Tag: para +#: boot-installer.xml:3545 +#, 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 " +"exclude port 0x800-0x8ff here. There is also a list " +"of some common resource range options in the System resource " +"settings section of the PCMCIA HOWTO. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." +msgstr "" +"Другой вариант: вы можете загрузить программу установки в экспертном режиме. " +"Вас попросят указать диапазон ресурсов, который используется аппаратным " +"обеспечением. Например, если у вас один из ноутбуков Dell, упомянутых выше, " +"то вы должны ввести exclude port 0x800-0x8ff. Также, " +"есть список распространённых диапазонов ресурсов в System " +"resource settings section of the PCMCIA HOWTO. Заметим, что при " +"вводе значений в программу установки вы не должны указывать запятых, если " +"они есть." + +#. Tag: title +#: boot-installer.xml:3562 +#, no-c-format +msgid "System Freeze while Loading the USB Modules" +msgstr "Система подвисает во время загрузки USB модулей" + +#. Tag: para +#: boot-installer.xml:3563 +#, 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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " +"being loaded." +msgstr "" +"Обычно, ядро пытается установить модули USB и драйвер USB клавиатуры, чтобы " +"обеспечить поддержку некоторых нестандартных клавиатур USB. Однако, есть " +"несколько нестандартных USB систем, где драйвер подвисает при загрузке. " +"Возможно, обходным решением может быть выключение контроллера USB в " +"настройке BIOS материнской платы. Другим решением может служить передача " +"параметра debian-installer/probe/usb=false в " +"приглашении загрузки, который запрещает загрузку модулей." + +#. Tag: title +#: boot-installer.xml:3577 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "Интерпретация загрузочных сообщений ядра" + +#. Tag: para +#: boot-installer.xml:3579 +#, no-c-format +msgid "" +"During the boot sequence, you may see many messages in the form " +"can't find something , or something " +"not present, can't initialize " +"something , or even " +"this driver release depends on something . 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 )." +msgstr "" +"Во время загрузки вы можете увидеть много сообщений вида " +"can't find ... " +"или ... not present, can't initialize ... или даже this driver release " +"depends on ... . Большинство " +"этих сообщений безвредны. Вы видите их потому что устанавливаемое ядро " +"собрано так, чтобы запускаться на компьютерах с самыми различными " +"периферийными устройствами. Очевидно, ни один компьютер не может содержать " +"все доступные устройства, так что операционная система может немного " +"пожаловаться во время поиска периферии, которой у вас нет. Также, вы можете " +"заметить, что система иногда замирает. Это случается из-за ожидания ответа " +"от устройства, которого нет в вашей системе. Если вы посчитаете, что " +"загрузка системы занимает недопустимо долгое время, вы можете позже создать " +"собственное ядро (смотрите )." + +#. Tag: title +#: boot-installer.xml:3604 +#, fuzzy, no-c-format +msgid "Reporting Installation Problems" +msgstr "Распространённые проблемы установки на &arch-title;" + +#. Tag: para +#: boot-installer.xml:3605 +#, fuzzy, no-c-format +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the menu option Save debug logs may be helpful. " +"It lets you store system error logs and configuration information from the " +"installer to a floppy, or download them using 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:3616 +#, no-c-format +msgid "" +"Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" +"Другие сообщения, имеющие отношение к установке, можно найти в /" +"var/log/ во время установки, и в /var/log/installer/ после того, как компьютер загрузит установленную систему." + +#. Tag: title +#: boot-installer.xml:3627 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "Отправка отчётов об ошибках установки" + +#. Tag: para +#: boot-installer.xml:3628 +#, 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:3635 +#, no-c-format +msgid "" +"Note that your installation report will be published in the Debian Bug " +"Tracking System (BTS) and forwarded to a public mailing list. Make sure that " +"you use an E-Mail address that you do not mind being made public." +msgstr "" + +#. Tag: para +#: boot-installer.xml:3641 +#, 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 " +"(apt-get install installation-report reportbug) and run " +"the command reportbug installation-report." +msgstr "" +"Если система Debian заработала, самый простой путь отправки отчёта об " +"установке — установка пакетов installation-report и reportbug " +"(apt-get install installation-report reportbug) и запуск " +"команды reportbug installation-report." + +#. Tag: para +#: boot-installer.xml:3648 +#, fuzzy, no-c-format +msgid "" +"Alternatively you can use this template when filling out installation " +"reports, and file the report as a bug report against the " +"installation-reports pseudo package, by sending it to " +"submit@bugs.debian.org. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD? floppy? network?>\n" +"Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect CD: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\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" +" 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 "" +"Пожалуйста, используйте этот шаблон для заполнения отчёта об установке и " +"отправьте отчёт как сообщение об ошибке псевдо-пакету " +"installation-reports на адрес submit@bugs." +"debian.org. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <Как запускалась программа установки? с CD? с дискет? из " +"сети?>\n" +"Image version: <Дата и место, откуда был взят образ>\n" +"Date: <Дата и время установки>\n" +"\n" +"Machine: <Описание машины (например, IBM Thinkpad R32)>\n" +"Processor:\n" +"Memory:\n" +"Partitions: < вывод результата команды df -Tl; лучше таблицу разделов в " +"необработанном (raw) виде>\n" +"\n" +"Вывод результата команд lspci -nn и lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Ошибка (описать подробности ниже), [ ] = не пробовал\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" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\n" +"\n" +"Comments/Problems:\n" +"\n" +"<Описание установки, комментарии, предложения возникшие в процессе.>\n" +" В отчёте об ошибках опишите, в чём состоит " +"проблема, включая последние увиденные сообщения ядра в случае повисания " +"ядра. Опишите шаги, которые вы делали, чтобы привести систему в проблемное " +"состояние." + +#~ msgid "Bug Reporter" +#~ msgstr "Отчёт об ошибках" diff --git a/po/ru/preparing.po b/po/ru/preparing.po index cdabcd811..09b0e9255 100644 --- a/po/ru/preparing.po +++ b/po/ru/preparing.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: preparing\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-26 16:20+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-11-06 15:07+0300\n" "Last-Translator: Yuri Kozlov \n" "Language-Team: Russian \n" @@ -14,7 +14,8 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: KBabel 1.11.2\n" -"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" +"Plural-Forms: nplurals=3; plural=(n%10==1 && n%100!=11 ? 0 : n%10>=2 && n%" +"10<=4 && (n%100<10 || n%100>=20) ? 1 : 2);\n" #. Tag: title #: preparing.xml:5 @@ -383,7 +384,8 @@ msgstr "Руководство по установке" #: preparing.xml:239 #, no-c-format msgid "This document you are now reading, in plain ASCII, HTML or PDF format." -msgstr "Документ, который вы сейчас читаете, доступен в форматах ASCII, HTML или PDF." +msgstr "" +"Документ, который вы сейчас читаете, доступен в форматах ASCII, HTML или PDF." #. Tag: itemizedlist #: preparing.xml:245 @@ -425,7 +427,8 @@ msgstr "Техническая документация" #. Tag: para #: preparing.xml:273 #, no-c-format -msgid "Often contains useful information on configuring or using your hardware." +msgid "" +"Often contains useful information on configuring or using your hardware." msgstr "" "Часто содержит полезную информацию по настройке и использованию вашего " "аппаратного обеспечения." @@ -544,7 +547,8 @@ msgstr "Информацию по аппаратному обеспечению #: preparing.xml:386 #, no-c-format msgid "The manuals that come with each piece of hardware." -msgstr "В руководствах, которые были вместе с приобретённым аппаратным обеспечением." +msgstr "" +"В руководствах, которые были вместе с приобретённым аппаратным обеспечением." #. Tag: para #: preparing.xml:391 @@ -958,7 +962,8 @@ msgstr "" msgid "" "The system on your network that you should use as a DNS (Domain Name " "Service) server." -msgstr "Система в сети, которая используется как DNS (Domain Name Service) сервер." +msgstr "" +"Система в сети, которая используется как DNS (Domain Name Service) сервер." #. Tag: para #: preparing.xml:619 @@ -1538,7 +1543,8 @@ msgstr "" #: preparing.xml:968 #, no-c-format msgid "Boot the Debian installer to continue installing Debian." -msgstr "Загрузить программу установки Debian, чтобы продолжить установку Debian." +msgstr "" +"Загрузить программу установки Debian, чтобы продолжить установку Debian." #. Tag: title #: preparing.xml:982 @@ -1757,10 +1763,10 @@ msgstr "" "OS/2, и желательно разместить Debian на том же диске без уничтожения " "предыдущей системы. Заметим, что программа установки поддерживает изменение " "размера файловых систем FAT и NTFS, используемых DOS и Windows. Просто " -"запустите программу установки, выберите " -"Вручную , " -"изменяемый раздел и задайте новый размер. Поэтому в большинстве " -"случаев вы не должны использовать метод, описываемый ниже." +"запустите программу установки, выберите Вручную , изменяемый раздел и задайте новый размер. " +"Поэтому в большинстве случаев вы не должны использовать метод, описываемый " +"ниже." #. Tag: para #: preparing.xml:1105 @@ -2278,7 +2284,8 @@ msgstr "" #: preparing.xml:1411 #, no-c-format msgid "Pre-Installation Hardware and Operating System Setup" -msgstr "Настройка аппаратного обеспечения и операционной системы перед установкой" +msgstr "" +"Настройка аппаратного обеспечения и операционной системы перед установкой" #. Tag: para #: preparing.xml:1412 @@ -2578,7 +2585,8 @@ msgstr "Изменение порядка загрузки на компьюте #. Tag: para #: preparing.xml:1619 #, no-c-format -msgid "As your computer starts, press the keys to enter the SCSI setup utility." +msgid "" +"As your computer starts, press the keys to enter the SCSI setup utility." msgstr "" "Как только компьютер начнёт загружаться, нажмите клавиши для входа в меню " "настройки SCSI." @@ -2614,7 +2622,8 @@ msgstr "Найдите пункт изменения порядка загруз #. Tag: para #: preparing.xml:1643 #, no-c-format -msgid "Set the utility so that the SCSI ID of the CD drive is first on the list." +msgid "" +"Set the utility so that the SCSI ID of the CD drive is first on the list." msgstr "Настройте так, что SCSI ID привода компакт дисков был первым в списке." #. Tag: para @@ -2943,9 +2952,9 @@ msgid "" "have the ok prompt. So if you get the old style " "prompt, hit the n key to get the new style prompt." msgstr "" -"Чтобы попасть в приглашение к загрузке вам нужно удерживая клавишу Stop (на старых клавиатурах 4-го типа, используйте клавишу L1, если у вас адаптер PC клавиатуры, используйте клавишу " +"Чтобы попасть в приглашение к загрузке вам нужно удерживая клавишу " +"Stop (на старых клавиатурах 4-го типа, используйте клавишу " +"L1, если у вас адаптер PC клавиатуры, используйте клавишу " "Break) нажать клавишу A. Boot PROM выдаст " "приглашение: или ok или >. " "Желательно иметь приглашение ok. Поэтому, если у вас " @@ -3304,26 +3313,6 @@ msgstr "" #: preparing.xml:2079 #, 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 " -"." -msgstr "" -"Очень хорошие материнские платы поддерживают оперативную память с чётностью " -"и скажут вам, если в оперативной памяти вашей системы возникнет ошибка в " -"одном бите. К сожалению, они не могут исправить ошибку, то есть они обычно " -"вешают систему после того как скажут о плохой оперативной памяти. Всё равно " -"это лучше, чем просто молча вставить ошибки в ваши данные. То есть, очень " -"хорошими системами считаются материнские платы имеющие поддержку чётности и " -"модули с настоящей чётностью; смотрите ." - -#. Tag: para -#: preparing.xml:2090 -#, 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." @@ -3333,13 +3322,13 @@ msgstr "" "вызывает прерывание при ошибке чётности в памяти." #. Tag: title -#: preparing.xml:2098 +#: preparing.xml:2087 #, no-c-format msgid "The Turbo Switch" msgstr "Переключатель Тurbo" #. Tag: para -#: preparing.xml:2099 +#: preparing.xml:2088 #, no-c-format msgid "" "Many systems have a turbo switch that controls the " @@ -3360,13 +3349,13 @@ msgstr "" "переключателем." #. Tag: title -#: preparing.xml:2112 +#: preparing.xml:2101 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "Процессоры Cyrix и ошибки при работе с дискетами" #. Tag: para -#: preparing.xml:2113 +#: preparing.xml:2102 #, no-c-format msgid "" "Many users of Cyrix CPUs have had to disable the cache in their systems " @@ -3382,7 +3371,7 @@ msgstr "" "намного медленнее." #. Tag: para -#: preparing.xml:2121 +#: preparing.xml:2110 #, no-c-format msgid "" "We don't think this is necessarily the fault of the Cyrix CPU. It may be " @@ -3397,13 +3386,13 @@ msgstr "" "код." #. Tag: title -#: preparing.xml:2131 +#: preparing.xml:2120 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "Настройки периферийного оборудования" #. Tag: para -#: preparing.xml:2132 +#: preparing.xml:2121 #, no-c-format msgid "" "You may have to change some settings or jumpers on your computer's " @@ -3417,7 +3406,7 @@ msgstr "" "устройство; надеемся, что поможем вам полезными советами." #. Tag: para -#: preparing.xml:2139 +#: preparing.xml:2128 #, no-c-format msgid "" "If any cards provide mapped memory, the memory should be " @@ -3431,13 +3420,13 @@ msgstr "" "мегабайт больше, чем доступной оперативной памяти в системе." #. Tag: title -#: preparing.xml:2150 +#: preparing.xml:2139 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "Поддержка USB в BIOS и клавиатуры" #. Tag: para -#: preparing.xml:2151 +#: preparing.xml:2140 #, no-c-format msgid "" "If you have no AT-style keyboard and only a USB model, you may need to " @@ -3458,13 +3447,13 @@ msgstr "" "USB keyboard support." #. Tag: title -#: preparing.xml:2164 +#: preparing.xml:2153 #, no-c-format msgid "More than 64 MB RAM" msgstr "Больше чем 64 МБ оперативной памяти" #. Tag: para -#: preparing.xml:2165 +#: preparing.xml:2154 #, no-c-format msgid "" "The Linux Kernel cannot always detect what amount of RAM you have. If this " @@ -3474,13 +3463,13 @@ msgstr "" "оперативной памяти. В этом случае смотрите ." #. Tag: title -#: preparing.xml:2174 +#: preparing.xml:2163 #, no-c-format msgid "Display visibility on OldWorld Powermacs" msgstr "Изображение на мониторе OldWorld Powermac" #. Tag: para -#: preparing.xml:2175 +#: preparing.xml:2164 #, no-c-format msgid "" "Some OldWorld Powermacs, most notably those with the control " @@ -3502,3 +3491,20 @@ msgstr "" "интерфейса, попробуйте изменить настройки экрана в MacOS на использование " "256 цветов вместо тысяч или миллионов." +#~ 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 ." +#~ msgstr "" +#~ "Очень хорошие материнские платы поддерживают оперативную память с " +#~ "чётностью и скажут вам, если в оперативной памяти вашей системы возникнет " +#~ "ошибка в одном бите. К сожалению, они не могут исправить ошибку, то есть " +#~ "они обычно вешают систему после того как скажут о плохой оперативной " +#~ "памяти. Всё равно это лучше, чем просто молча вставить ошибки в ваши " +#~ "данные. То есть, очень хорошими системами считаются материнские платы " +#~ "имеющие поддержку чётности и модули с настоящей чётностью; смотрите ." diff --git a/po/ru/using-d-i.po b/po/ru/using-d-i.po index d528a85d1..df3afeaa9 100644 --- a/po/ru/using-d-i.po +++ b/po/ru/using-d-i.po @@ -5,7 +5,7 @@ msgid "" msgstr "" "Project-Id-Version: using-d-i\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-12-16 09:31+0300\n" "Last-Translator: Yuri Kozlov \n" "Language-Team: Russian \n" @@ -3722,14 +3722,13 @@ msgstr "" #. Tag: para #: using-d-i.xml:2302 -#, no-c-format +#, fuzzy, 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 fdisk /" "mbr 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 ." +"Debian!" msgstr "" "Если вы не смогли загрузить Windows 9x (или DOS) после этого шага, то вам " "нужно воспользоваться загрузочной дискетой с Windows 9x (MS-DOS) и запустить " @@ -3739,14 +3738,14 @@ msgstr "" "читайте в ." #. Tag: title -#: using-d-i.xml:2319 +#: using-d-i.xml:2318 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "" "Установка системного загрузчика ELILO на жёсткий диск" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2320 #, no-c-format msgid "" "The &architecture; boot loader is called elilo. It is modeled " @@ -3774,7 +3773,7 @@ msgstr "" "quote>, чтобы загрузить и выполнить ядро Linux." #. Tag: para -#: using-d-i.xml:2337 +#: using-d-i.xml:2336 #, no-c-format msgid "" "The elilo configuration and installation is done as the last " @@ -3791,13 +3790,13 @@ msgstr "" "диске что и корневая файловая система." #. Tag: title -#: using-d-i.xml:2349 +#: using-d-i.xml:2348 #, no-c-format msgid "Choose the correct partition!" msgstr "Выберите правильный раздел!" #. Tag: para -#: using-d-i.xml:2351 +#: using-d-i.xml:2350 #, no-c-format msgid "" "The criteria for selecting a partition is that it is FAT format filesystem " @@ -3815,13 +3814,13 @@ msgstr "" "установки, стерев его содержимое!" #. Tag: title -#: using-d-i.xml:2366 +#: using-d-i.xml:2365 #, no-c-format msgid "EFI Partition Contents" msgstr "Содержимое EFI раздела" #. Tag: para -#: using-d-i.xml:2368 +#: using-d-i.xml:2367 #, no-c-format msgid "" "The EFI partition is a FAT filesystem format partition on one of the hard " @@ -3851,13 +3850,13 @@ msgstr "" "настройки системы." #. Tag: filename -#: using-d-i.xml:2390 +#: using-d-i.xml:2389 #, no-c-format msgid "elilo.conf" msgstr "elilo.conf" #. Tag: para -#: using-d-i.xml:2391 +#: using-d-i.xml:2390 #, no-c-format msgid "" "This is the configuration file read by the boot loader when it starts. It is " @@ -3869,13 +3868,13 @@ msgstr "" "указывающими на файлы в EFI разделе." #. Tag: filename -#: using-d-i.xml:2400 +#: using-d-i.xml:2399 #, no-c-format msgid "elilo.efi" msgstr "elilo.efi" #. Tag: para -#: using-d-i.xml:2401 +#: using-d-i.xml:2400 #, no-c-format msgid "" "This is the boot loader program that the EFI Boot Manager " @@ -3889,13 +3888,13 @@ msgstr "" "менеджер загрузки EFI." #. Tag: filename -#: using-d-i.xml:2411 +#: using-d-i.xml:2410 #, no-c-format msgid "initrd.img" msgstr "initrd.img" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2411 #, no-c-format msgid "" "This is the initial root filesystem used to boot the kernel. It is a copy of " @@ -3910,13 +3909,13 @@ msgstr "" "символическая ссылка /initrd.img." #. Tag: filename -#: using-d-i.xml:2424 +#: using-d-i.xml:2423 #, no-c-format msgid "readme.txt" msgstr "readme.txt" #. Tag: para -#: using-d-i.xml:2425 +#: using-d-i.xml:2424 #, no-c-format msgid "" "This is a small text file warning you that the contents of the directory are " @@ -3928,13 +3927,13 @@ msgstr "" "будут уничтожены при следующем запуске /usr/sbin/elilo." #. Tag: filename -#: using-d-i.xml:2435 +#: using-d-i.xml:2434 #, no-c-format msgid "vmlinuz" msgstr "vmlinuz" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2435 #, no-c-format msgid "" "This is the compressed kernel itself. It is a copy of the file referenced in " @@ -3948,13 +3947,13 @@ msgstr "" "символическая ссылка /vmlinuz." #. Tag: title -#: using-d-i.xml:2456 +#: using-d-i.xml:2455 #, no-c-format msgid "arcboot-installer" msgstr "Системный загрузчик arcboot" #. Tag: para -#: using-d-i.xml:2457 +#: using-d-i.xml:2456 #, no-c-format msgid "" "The boot loader on SGI machines is arcboot. It has to be " @@ -3998,13 +3997,13 @@ msgstr "" "boot." #. Tag: replaceable -#: using-d-i.xml:2476 +#: using-d-i.xml:2475 #, no-c-format msgid "scsi" msgstr "scsi" #. Tag: para -#: using-d-i.xml:2477 +#: using-d-i.xml:2476 #, no-c-format msgid "" "is the SCSI bus to be booted from, this is 0 for the " @@ -4014,13 +4013,13 @@ msgstr "" "userinput> для встроенных контроллеров" #. Tag: replaceable -#: using-d-i.xml:2485 +#: using-d-i.xml:2484 #, no-c-format msgid "disk" msgstr "disk" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2485 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which arcboot is " @@ -4030,13 +4029,13 @@ msgstr "" # index.docbook:1600, index.docbook:1669 #. Tag: replaceable -#: using-d-i.xml:2494 using-d-i.xml:2563 +#: using-d-i.xml:2493 using-d-i.xml:2562 #, no-c-format msgid "partnr" msgstr "partnr" #. Tag: para -#: using-d-i.xml:2495 +#: using-d-i.xml:2494 #, no-c-format msgid "" "is the number of the partition on which /etc/arcboot.conf/etc/arcboot.conf" #. Tag: replaceable -#: using-d-i.xml:2503 +#: using-d-i.xml:2502 #, no-c-format msgid "config" msgstr "config" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2503 #, no-c-format msgid "" "is the name of the configuration entry in /etc/arcboot.conflinux." #. Tag: title -#: using-d-i.xml:2525 +#: using-d-i.xml:2524 #, no-c-format msgid "delo-installer" msgstr "Системный загрузчик delo" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2525 #, no-c-format msgid "" "The boot loader on DECstations is DELO. It has to be " @@ -4095,13 +4094,13 @@ msgstr "" " в приглашении микропрограммы." #. Tag: replaceable -#: using-d-i.xml:2545 +#: using-d-i.xml:2544 #, no-c-format msgid "#" msgstr "#" #. Tag: para -#: using-d-i.xml:2546 +#: using-d-i.xml:2545 #, no-c-format msgid "" "is the TurboChannel device to be booted from, on most DECstations this is " @@ -4112,13 +4111,13 @@ msgstr "" "встроенных контроллеров" #. Tag: replaceable -#: using-d-i.xml:2554 +#: using-d-i.xml:2553 #, no-c-format msgid "id" msgstr "id" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2554 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which DELO is installed" @@ -4126,7 +4125,7 @@ msgstr "" "это SCSI ID жёсткого диска, на котором установлен DELO" #. Tag: para -#: using-d-i.xml:2564 +#: using-d-i.xml:2563 #, no-c-format msgid "" "is the number of the partition on which /etc/delo.conf " @@ -4135,13 +4134,13 @@ msgstr "" "это номер раздела, на котором хранится /etc/delo.conf" #. Tag: replaceable -#: using-d-i.xml:2572 +#: using-d-i.xml:2571 #, no-c-format msgid "name" msgstr "name" #. Tag: para -#: using-d-i.xml:2573 +#: using-d-i.xml:2572 #, no-c-format msgid "" "is the name of the configuration entry in /etc/delo.conflinux." #. Tag: para -#: using-d-i.xml:2583 +#: using-d-i.xml:2582 #, no-c-format msgid "" "In case /etc/delo.conf is on the first partition on the " @@ -4161,20 +4160,20 @@ msgstr "" "должна быть загружена конфигурация по умолчанию, то достаточно набрать" #. Tag: screen -#: using-d-i.xml:2589 +#: using-d-i.xml:2588 #, no-c-format msgid "boot #/rzid" msgstr "boot #/rzid" #. Tag: title -#: using-d-i.xml:2599 +#: using-d-i.xml:2598 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "" "Установка системного загрузчика Yaboot на жёсткий диск" #. Tag: para -#: using-d-i.xml:2600 +#: using-d-i.xml:2599 #, no-c-format msgid "" "Newer (mid 1998 and on) PowerMacs use yaboot as their " @@ -4194,14 +4193,14 @@ msgstr "" "OpenFirmware установлена на загрузку &debian;." #. Tag: title -#: using-d-i.xml:2618 +#: using-d-i.xml:2617 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "" "Установка системного загрузчика Quik на жёсткий диск" #. Tag: para -#: using-d-i.xml:2619 +#: using-d-i.xml:2618 #, no-c-format msgid "" "The boot loader for OldWorld Power Macintosh machines is quikzipl-installer" msgstr "Установка системного загрузчика zipl" #. Tag: para -#: using-d-i.xml:2636 +#: using-d-i.xml:2635 #, no-c-format msgid "" "The boot loader on &arch-title; is zipl. ZIPLZIPL." #. Tag: title -#: using-d-i.xml:2653 +#: using-d-i.xml:2652 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "" "Установка системного загрузчика SILO на жёсткий диск" #. Tag: para -#: using-d-i.xml:2655 +#: using-d-i.xml:2654 #, no-c-format msgid "" "The standard &architecture; boot loader is called silo. It is " @@ -4276,13 +4275,13 @@ msgstr "" "Solaris." #. Tag: title -#: using-d-i.xml:2680 +#: using-d-i.xml:2679 #, no-c-format msgid "Continue Without Boot Loader" msgstr "Продолжение без системного загрузчика" #. Tag: para -#: using-d-i.xml:2682 +#: using-d-i.xml:2681 #, no-c-format msgid "" "This option can be used to complete the installation even when no boot " @@ -4301,7 +4300,7 @@ msgstr "" "phrase>" #. Tag: para -#: using-d-i.xml:2691 +#: using-d-i.xml:2690 #, no-c-format msgid "" "If you plan to manually configure your bootloader, you should check the name " @@ -4323,13 +4322,13 @@ msgstr "" "то также и раздел файловой системы с /boot." #. Tag: title -#: using-d-i.xml:2708 +#: using-d-i.xml:2707 #, no-c-format msgid "Finishing the Installation" msgstr "Завершение установки" #. Tag: para -#: using-d-i.xml:2709 +#: using-d-i.xml:2708 #, no-c-format msgid "" "These are the last bits to do before rebooting to your new system. It mostly " @@ -4339,13 +4338,13 @@ msgstr "" "уборка за &d-i;." #. Tag: title -#: using-d-i.xml:2721 +#: using-d-i.xml:2720 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "Завершение установки и перезагрузка" #. Tag: para -#: using-d-i.xml:2723 +#: using-d-i.xml:2722 #, no-c-format msgid "" "This is the last step in the initial Debian installation process. You will " @@ -4359,7 +4358,7 @@ msgstr "" "действия, а затем перезагрузит машину в новую систему Debian." #. Tag: para -#: using-d-i.xml:2730 +#: using-d-i.xml:2729 #, no-c-format msgid "" "Select the Finish the installation menu item " @@ -4373,13 +4372,13 @@ msgstr "" "качестве корневой файловой системы в самом начале установки." #. Tag: title -#: using-d-i.xml:2744 +#: using-d-i.xml:2743 #, no-c-format msgid "Miscellaneous" msgstr "Разное" #. Tag: para -#: using-d-i.xml:2745 +#: using-d-i.xml:2744 #, no-c-format msgid "" "The components listed in this section are usually not involved in the " @@ -4391,13 +4390,13 @@ msgstr "" "пойдёт не так." #. Tag: title -#: using-d-i.xml:2758 +#: using-d-i.xml:2757 #, no-c-format msgid "Saving the installation logs" msgstr "Сохранение протокола установки" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2759 #, no-c-format msgid "" "If the installation is successful, the logfiles created during the " @@ -4409,7 +4408,7 @@ msgstr "" "installer/ в новой системе Debian." #. Tag: para -#: using-d-i.xml:2767 +#: using-d-i.xml:2766 #, no-c-format msgid "" "Choosing Save debug logs from the main menu " @@ -4425,13 +4424,13 @@ msgstr "" "протокол на другой системе или послать его вместе с отчётом об ошибке." #. Tag: title -#: using-d-i.xml:2787 +#: using-d-i.xml:2786 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "Использование командной строки и просмотр журнальных файлов" #. Tag: para -#: using-d-i.xml:2790 +#: using-d-i.xml:2789 #, no-c-format msgid "" "There is an Execute a Shell item on the menu. If " @@ -4454,7 +4453,7 @@ msgstr "" "называемый ash." #. Tag: para -#: using-d-i.xml:2802 +#: using-d-i.xml:2801 #, no-c-format msgid "" "At this point you are booted from the RAM disk, and there is a limited set " @@ -4472,7 +4471,7 @@ msgstr "" "такие как автодополнение и история команд." #. Tag: para -#: using-d-i.xml:2811 +#: using-d-i.xml:2810 #, no-c-format msgid "" "Use the menus to perform any task that they are able to do — the shell " @@ -4493,13 +4492,13 @@ msgstr "" "меню для входа в режим командной строки." #. Tag: title -#: using-d-i.xml:2830 +#: using-d-i.xml:2829 #, no-c-format msgid "Installation Over the Network" msgstr "Установка по сети" #. Tag: para -#: using-d-i.xml:2832 +#: using-d-i.xml:2831 #, no-c-format msgid "" "One of the more interesting components is network-console.)" #. Tag: para -#: using-d-i.xml:2842 +#: using-d-i.xml:2841 #, no-c-format msgid "" "This component is not loaded into the main installation menu by default, so " @@ -4539,7 +4538,7 @@ msgstr "" "Продолжение установки через SSH." #. Tag: para -#: using-d-i.xml:2855 +#: using-d-i.xml:2854 #, no-c-format msgid "" "For installations on &arch-title;, this is the default method after setting " @@ -4549,7 +4548,7 @@ msgstr "" "после настройки сети." #. Tag: para -#: using-d-i.xml:2860 +#: using-d-i.xml:2859 #, no-c-format msgid "" "After selecting this new entry, you " @@ -4571,7 +4570,7 @@ msgstr "" "человеку, который будет продолжать установку удалённо." #. Tag: para -#: using-d-i.xml:2872 +#: using-d-i.xml:2871 #, no-c-format msgid "" "Should you decide to continue with the installation locally, you can always " @@ -4583,7 +4582,7 @@ msgstr "" "компоненту." #. Tag: para -#: using-d-i.xml:2878 +#: using-d-i.xml:2877 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need " @@ -4614,7 +4613,7 @@ msgstr "" "чтобы вы смогли убедиться, что это именно тот компьютер." #. Tag: para -#: using-d-i.xml:2895 +#: using-d-i.xml:2894 #, no-c-format msgid "" "If you install several computers in turn and they happen to have the same IP " @@ -4632,7 +4631,7 @@ msgstr "" "~/.ssh/known_hosts и попробовать подключиться ещё раз." #. Tag: para -#: using-d-i.xml:2904 +#: using-d-i.xml:2903 #, no-c-format msgid "" "After the login you will be presented with an initial screen where you have " @@ -4652,7 +4651,7 @@ msgstr "" "для установочного меню и несколько для оболочки командной строки." #. Tag: para -#: using-d-i.xml:2914 +#: using-d-i.xml:2913 #, no-c-format msgid "" "After you have started the installation remotely over SSH, you should not go " @@ -4667,7 +4666,7 @@ msgstr "" "завершению установки или проблемам в установленной системой." #. Tag: para -#: using-d-i.xml:2922 +#: using-d-i.xml:2921 #, no-c-format msgid "" "Also, if you are running the SSH session from an X terminal, you should not " diff --git a/po/sv/boot-installer.po b/po/sv/boot-installer.po index 8d9b47bf3..4ad736216 100644 --- a/po/sv/boot-installer.po +++ b/po/sv/boot-installer.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: installation-guide 20051025 boot-installer\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-12-16 14:43+0100\n" "Last-Translator: Daniel Nylander \n" "Language-Team: Swedish \n" @@ -14,4082 +14,5207 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#~ msgid "Booting the Installation System" -#~ msgstr "Starta upp installationssystemet" - -#~ msgid "Booting the Installer on &arch-title;" -#~ msgstr "Starta upp installeraren på &arch-title;" +#. Tag: title +#: boot-installer.xml:4 +#, no-c-format +msgid "Booting the Installation System" +msgstr "Starta upp installationssystemet" + +#. Tag: title +#: boot-installer.xml:9 +#, no-c-format +msgid "Booting the Installer on &arch-title;" +msgstr "Starta upp installeraren på &arch-title;" + +#. Tag: title +#: boot-installer.xml:20 +#, no-c-format +msgid "Alpha Console Firmware" +msgstr "Konsollfirmware för Alpha" + +#. 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 "" +"Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system slås " +"på eller startas om. Det finns två olika konsollspecifikationer som används " +"på Alpha-system och därav finns det två klasser av konsollfirmware " +"tillgängliga:" + +#. Tag: para +#: boot-installer.xml:31 +#, no-c-format +msgid "" +"SRM console, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." +msgstr "" +"SRM-konsoll, baserad på specifikationen Alpha Console " +"Subsystem, som tillhandahåller ett operativmiljö för operativsystemen " +"OpenVMS, Tru64 UNIX och Linux." -#~ msgid "Alpha Console Firmware" -#~ msgstr "Konsollfirmware för Alpha" +#. Tag: para +#: boot-installer.xml:38 +#, no-c-format +msgid "" +"ARC, AlphaBIOS, or ARCSBIOS console, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." +msgstr "" +"ARC, AlphaBIOS eller ARCSBIOS-konsoll, baserad på " +"specifikationen Advanced RISC Computing (ARC), som tillhandahåller en " +"operativmiljö för Windows NT." -#~ 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 "" -#~ "Konsollfirmware lagras i ett flash-rom och startas när ett Alpha-system " -#~ "slås på eller startas om. Det finns två olika konsollspecifikationer som " -#~ "används på Alpha-system och därav finns det två klasser av " -#~ "konsollfirmware tillgängliga:" +#. 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 "" +"Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och " +"ARC den att valet av konsoll begränsar den möjliga diskpartitionsplanen för " +"hårddisken som du önskar starta upp från." -#~ msgid "" -#~ "SRM console, based on the Alpha Console Subsystem " -#~ "specification, which provides an operating environment for OpenVMS, Tru64 " -#~ "UNIX, and Linux operating systems." -#~ msgstr "" -#~ "SRM-konsoll, baserad på specifikationen Alpha " -#~ "Console Subsystem, som tillhandahåller ett operativmiljö för " -#~ "operativsystemen OpenVMS, Tru64 UNIX och Linux." +#. Tag: para +#: boot-installer.xml:54 +#, no-c-format +msgid "" +"ARC requires that you use an MS-DOS partition table (as created by " +"cfdisk) for the boot disk. Therefore MS-DOS partition " +"tables are the native 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 "" +"ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av " +"cfdisk) för uppstartsdisken. Därför är MS-DOS-" +"partitionstabeller det ursprungliga partitionsformatet vid " +"uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett " +"diskpartitioneringsverktyg kanske du föredrar att partitionera dina diskar " +"från firmwaremenyerna före installation av Linux." + +#. Tag: para +#: boot-installer.xml:63 +#, no-c-format +msgid "" +"Conversely, SRM is incompatible " +"Specifically, the bootsector format required by the Console Subsystem " +"Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " +"BSD disklabel format, this is the native partition format for " +"SRM installations." +msgstr "" +"Motsatt är SRM inkompatibel Specifikt " +"är formatet på uppstartssektorn som krävs av Console Subsystem Specification " +"i konflikt med placeringen av DOS-partitionstabellen. " +"med MS-DOS-partitionstabeller. Eftersom Tru64 Unix använder formatet för BSD-" +"disketiketter, är det här det ursprungliga (native) " +"partitionsformatet för SRM-installationer." + +#. 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 "" +"GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från " +"båda konsolltyperna, men &debian; &release; har endast stöd för uppstart på " +"SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-version " +"tillgänglig för, om du vill använda dubbel-uppstart tillsammans med Windows " +"NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll för initiering " +"av BIOS kommer du inte kunna använda installeraren för &debian; &release;. " +"Du kan fortfarande köra &debian; &release; på sådana system genom att " +"använda andra installationsmedia, till exempel kan du installera Debian " +"woody med MILO och uppgradera." + +#. Tag: para +#: boot-installer.xml:87 +#, no-c-format +msgid "" +"Because MILO 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 "" +"På grund av att MILO inte finns tillgänglig för någon av " +"Alpha-systemen för tillfället i produktion (i februari 2000), och på grund " +"att det inte längre är nödvändigt att köra en licens för OpenVMS eller Tru64 " +"Unix för att få SRM-firmware på din äldre Alpha, rekommenderas det att du " +"använder SRM om möjligt." + +#. Tag: para +#: boot-installer.xml:95 +#, no-c-format +msgid "" +"The following table summarizes available and supported system type/console " +"combinations (see for the system type names). " +"The word ARC below denotes any of the ARC-compliant consoles." +msgstr "" +"Följande tabell sammanställer tillgängliga och systemtyper/" +"konsollkombinationer som stöds (se för namnen " +"på systemtyperna). Ordet ARC nedan below indikerar någon av " +"de ARC-godkända konsollerna." + +#. Tag: entry +#: boot-installer.xml:107 +#, no-c-format +msgid "System Type" +msgstr "Systemtyp" + +#. Tag: entry +#: boot-installer.xml:108 +#, no-c-format +msgid "Console Type Supported" +msgstr "Konsolltyper som stöds" + +#. Tag: entry +#: boot-installer.xml:114 +#, no-c-format +msgid "alcor" +msgstr "alcor" + +#. 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 "ARC eller SRM" + +#. Tag: entry +#: boot-installer.xml:117 +#, no-c-format +msgid "avanti" +msgstr "avanti" + +#. Tag: entry +#: boot-installer.xml:120 +#, no-c-format +msgid "book1" +msgstr "book1" + +#. 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 "Endast SRM" + +#. Tag: entry +#: boot-installer.xml:123 +#, no-c-format +msgid "cabriolet" +msgstr "cabriolet" + +#. Tag: entry +#: boot-installer.xml:126 +#, no-c-format +msgid "dp264" +msgstr "dp264" + +#. Tag: entry +#: boot-installer.xml:129 +#, no-c-format +msgid "eb164" +msgstr "eb164" + +#. Tag: entry +#: boot-installer.xml:132 +#, no-c-format +msgid "eb64p" +msgstr "eb64p" + +#. Tag: entry +#: boot-installer.xml:135 +#, no-c-format +msgid "eb66" +msgstr "eb66" + +#. Tag: entry +#: boot-installer.xml:138 +#, no-c-format +msgid "eb66p" +msgstr "eb66p" + +#. Tag: entry +#: boot-installer.xml:141 +#, no-c-format +msgid "jensen" +msgstr "jensen" + +#. Tag: entry +#: boot-installer.xml:144 +#, no-c-format +msgid "lx164" +msgstr "lx164" + +#. Tag: entry +#: boot-installer.xml:147 +#, no-c-format +msgid "miata" +msgstr "miata" + +#. Tag: entry +#: boot-installer.xml:150 +#, no-c-format +msgid "mikasa" +msgstr "mikasa" + +#. Tag: entry +#: boot-installer.xml:153 +#, no-c-format +msgid "mikasa-p" +msgstr "mikasa-p" + +#. Tag: entry +#: boot-installer.xml:156 +#, no-c-format +msgid "nautilus" +msgstr "nautilus" + +#. Tag: entry +#: boot-installer.xml:157 +#, no-c-format +msgid "ARC (see motherboard manual) or SRM" +msgstr "ARC (se handboken för moderkortet) eller SRM" + +#. Tag: entry +#: boot-installer.xml:159 +#, no-c-format +msgid "noname" +msgstr "noname" + +#. Tag: entry +#: boot-installer.xml:162 +#, no-c-format +msgid "noritake" +msgstr "noritake" + +#. Tag: entry +#: boot-installer.xml:165 +#, no-c-format +msgid "noritake-p" +msgstr "noritake-p" + +#. Tag: entry +#: boot-installer.xml:168 +#, no-c-format +msgid "pc164" +msgstr "pc164" + +#. Tag: entry +#: boot-installer.xml:171 +#, no-c-format +msgid "rawhide" +msgstr "rawhide" + +#. Tag: entry +#: boot-installer.xml:174 +#, no-c-format +msgid "ruffian" +msgstr "ruffian" + +#. Tag: entry +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#, no-c-format +msgid "ARC only" +msgstr "Endast ARC" + +#. Tag: entry +#: boot-installer.xml:177 +#, no-c-format +msgid "sable" +msgstr "sable" + +#. Tag: entry +#: boot-installer.xml:180 +#, no-c-format +msgid "sable-g" +msgstr "sable-g" + +#. Tag: entry +#: boot-installer.xml:183 +#, no-c-format +msgid "sx164" +msgstr "sx164" + +#. Tag: entry +#: boot-installer.xml:186 +#, no-c-format +msgid "takara" +msgstr "takara" + +#. Tag: entry +#: boot-installer.xml:189 +#, no-c-format +msgid "xl" +msgstr "xl" + +#. Tag: entry +#: boot-installer.xml:192 +#, no-c-format +msgid "xlt" +msgstr "xlt" + +#. 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, " +"aboot, a small, platform-independent bootloader, is used. " +"See the (unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så " +"behovet av en mellanliggande starthanterare finns. För SRM-konsollen används " +"aboot, en liten, plattformsoberoende starthanterare. Se " +"(tyvärr föråldrad) SRM HOWTO för mer " +"information om aboot." + +#. 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 "" +"Följande paragrafer kommer från installationshandboken för woody och " +"inkluderas här som referens: de kan vara användbara för någon vid ett senare " +"datum när Debian har stöd för MILO-baserade installationer igen." -#~ msgid "" -#~ "ARC, AlphaBIOS, or ARCSBIOS console, based on the " -#~ "Advanced RISC Computing (ARC) specification, which provides an operating " -#~ "environment for Windows NT." -#~ msgstr "" -#~ "ARC, AlphaBIOS eller ARCSBIOS-konsoll, baserad på " -#~ "specifikationen Advanced RISC Computing (ARC), som tillhandahåller en " -#~ "operativmiljö för Windows NT." +#. 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: MILO and aboot." +msgstr "" +"Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så " +"behovet av en mellanliggande starthanterare finns. Det finns två " +"huvudsakliga Linux-inläsare: MILO och aboot." + +#. Tag: para +#: boot-installer.xml:221 +#, no-c-format +msgid "" +"MILO is itself a console, which replaces ARC or SRM in " +"memory. MILO can be booted from both ARC and SRM and is " +"the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) " +"MILO HOWTO." +msgstr "" +"MILO är själv en konsoll, som ersätter ARC eller SRM i " +"minnet. MILO kan startas upp från både ARC och SRM och är " +"det enda sättet att bootstrapa Linux från ARC-konsollen. MILO är plattformsspecifik (olika MILO behövs för " +"varje systemtyp) och existerar för de systemen, för vilka ARC-stöd visas i " +"tabellen ovan.. Se även (tyvärr föråldrad) MILO HOWTO." + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "" +"aboot is a small, platform-independent bootloader, which " +"runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"aboot är en liten, plattformsoberoende starthanterare, " +"som endast körs från SRM. Se (även den föråldrad) SRM HOWTO för mer information om aboot." -#~ 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 "" -#~ "Från användarens perspektiv är den mest viktiga skillnaden mellan SRM och " -#~ "ARC den att valet av konsoll begränsar den möjliga diskpartitionsplanen " -#~ "för hårddisken som du önskar starta upp från." +#. 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 MILO is available: " +"\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Because MILO 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 aboot on new installations of GNU/Linux, " +"unless you wish to dual-boot with Windows NT." +msgstr "" +"Därav är tre scenarion generellt sett möjliga, beroende på systemets " +"konsollfirmware och huruvida MILO finns tillgänglig eller " +"inte: \n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Därför att MILO inte finns " +"tillgänglig för någon av de Alpha-system som för närvarande produceras (från " +"och med februari 2000), och på grund av att det inte längre är nödvändigt " +"att köpa en licens för OpenVMS eller Tru64 Unix för att få SRM-firmware på " +"din äldre Alpha, rekommenderas det att du använder SRM och aboot på nyare installationer av GNU/Linux, om inte du önskar att även " +"starta upp med Windows NT." + +#. 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 half-flash 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 arc command). For the reasons mentioned above, " +"we recommend switching to SRM before installing &debian;." +msgstr "" +"Majoriteten av de AlphaServer-modeller och alla nuvarande server- och " +"arbetsstationsprodukter innehåller både SRM och AlphaBIOS i sina firmware. " +"För half-flash-maskiner såsom de olika evalueringskorten, är " +"det möjligt att byta från en version till en annan genom att skriva om " +"firmware. När SRM har installerats, är det möjligt att köra ARC/AlphaBIOS " +"från en diskett (med kommandot arc). Med anledningarna " +"nämnda ovan, rekommenderar vi ett byte till SRM före installation av " +"&debian;." + +#. Tag: para +#: boot-installer.xml:264 +#, no-c-format +msgid "" +"As on other architectures, you should install the newest available revision " +"of the firmware Except on Jensen, where Linux is not " +"supported on firmware versions newer than 1.7 — see for more information. before " +"installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." +msgstr "" +"Som på andra arkitekturer, bör du installera de senaste tillgängliga " +"revisionen av firmware Utom på Jensen, där Linux inte stöds " +"på firmware-versioner senare än 1.7 — se för mer information. före installation " +"av &debian;. För Alpha, uppdateringar av firmware kan hämtas från Alpha Firmware Updates." + +#. Tag: title +#: boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 +#: boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 +#: boot-installer.xml:2500 boot-installer.xml:2596 +#, no-c-format +msgid "Booting with TFTP" +msgstr "Uppstart via TFTP" + +#. Tag: para +#: boot-installer.xml:284 +#, no-c-format +msgid "" +"In SRM, Ethernet interfaces are named with the ewa " +"prefix, and will be listed in the output of the show dev command, like this (edited slightly): \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" +" You first need to set the boot protocol: " +"\n" +">>> set ewa0_protocols bootp\n" +" Then check the medium type is correct: " +"\n" +">>> set ewa0_mode mode\n" +" You can get a listing of valid modes with " +">>>set ewa0_mode." +msgstr "" +"I SRM är Ethernet-gränssnitten namngivna med prefixet ewa, och kommer att listas i utskriften från kommandot " +"show dev, som denna (delvis redigerat): " +"\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" +" Du behöver först ställa in uppstartsprotokollet: " +"\n" +">>> set ewa0_protocol bootp\n" +" Kontrollera sedan att mediatypen är korrekt: " +"\n" +">>> set ewa0_mode läge\n" +" Du kan få en lista på giltiga lägen med " +">>>set ewa0_mode." + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "" +"Then, to boot from the first Ethernet interface, you would type: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" This will boot using the default kernel " +"parameters as included in the netboot image." +msgstr "" +"Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du " +"skriva: \n" +">>> boot ewa0 -flags \"\"\n" +" Det här kommer att starta upp med de " +"kärnparametrar som är standard och som inkluderats i netboot-avbilden." + +#. Tag: para +#: boot-installer.xml:311 +#, no-c-format +msgid "" +"If you wish to use a serial console, you must pass the " +"console= parameter to the kernel. This can be done " +"using the -flags argument to the SRM boot command. The serial ports are named the same as their " +"corresponding files in /dev. 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 ewa0 and use a console on the first serial port, you would type:" +msgstr "" +"Om du önskar att använda en seriekonsoll, måste du " +"skicka med parametern console= till kärnan. Det kan " +"göras med argumentet -flags till SRM-kommandot " +"boot. Serieportarna har samma namn som sina " +"motsvarande filer i /dev. När ytterligare " +"kärnparametrar anges, måste du upprepa vissa standardalternativ som behövs " +"av &d-i;-avbilderna. Till exempel, för att starta upp från ewa0 och använda en konsoll på första serieporten, skulle du skriva:" + +#. Tag: screen +#: boot-installer.xml:323 +#, no-c-format +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" + +#. Tag: title +#: boot-installer.xml:328 +#, no-c-format +msgid "Booting from CD-ROM with the SRM Console" +msgstr "Uppstart från cd-rom med SRM-konsoll" + +#. Tag: para +#: boot-installer.xml:329 +#, no-c-format +msgid "" +"Type \n" +">>> boot xxxx -flags 0\n" +" where xxxx is your CD-" +"ROM drive in SRM notation." +msgstr "" +"Ange \n" +">>> boot xxxx -flags 0\n" +" där xxxx är din cd-" +"rom-enhet i SRM-notation." + +#. Tag: title +#: boot-installer.xml:341 +#, no-c-format +msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" +msgstr "Uppstart från cd-rom med ARC eller AlphaBIOS-konsoll" + +#. 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 ), then enter \\milo\\linload." +"exe as the boot loader and \\milo" +"\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS " +"Selection Setup' menu. Ruffians make an exception: You need to use " +"\\milo\\ldmilo.exe as boot loader." +msgstr "" +"För att starta upp en cd-rom från ARC-konsollen, ta reda på kodnamnet för " +"din underarkitektur (se ), och ange sedan " +"\\milo\\linload.exe som starthanterare och " +"\\milo\\underarkitektur (där " +"underarkitektur är det korrekta namnet på " +"underarkitekturen) som sökväg till operativsystemet i menyn \"OS Selection " +"Setup\". Ett undantag för ägare av Ruffian-system: De måste använda " +"\\milo\\ldmilo.exe som starthanterare." + +#. Tag: title +#: boot-installer.xml:358 +#, no-c-format +msgid "Booting from Floppies with the SRM Console" +msgstr "Uppstart från startdisketter med SRM-konsoll" + +#. Tag: para +#: boot-installer.xml:359 +#, no-c-format +msgid "" +"At the SRM prompt (>>>), issue the following " +"command: \n" +">>> boot dva0 -flags 0\n" +" possibly replacing dva0 " +"with the actual device name. Usually, dva0 is the " +"floppy; type \n" +">>> show dev\n" +" to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. If everything works OK, you will eventually see the Linux kernel " +"boot." +msgstr "" +"På SRM-prompten (>>>), ange följande kommando: " +"\n" +">>> boot dva0 -flags 0\n" +" ersätt möjligen dva0 med " +"det faktiska enhetsnamnet. Vanligtvis är dva0 " +"diskettenheten; skriv \n" +">>> show dev\n" +" för att se listan på enheter (alltså, om du vill " +"starta upp från en cd). Observera att om du startar upp via MILO, ignoreras " +"argumentet -flags, så du kan helt enkelt skriva " +"boot dva0. Om allt fungerar som det ska kommer du till " +"slut se Linux-kärnan starta upp." + +#. Tag: para +#: boot-installer.xml:376 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via aboot, use the following command: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (typed on one line), substituting, if necessary, " +"the actual SRM boot device name for dva0, the Linux " +"boot device name for fd0, and the desired kernel " +"parameters for arguments." +msgstr "" +"Om du vill ange kärnparametrar vid uppstart med aboot, " +"använd följande kommando: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (angivet på en rad), som ersätter, om " +"nödvändigt, det faktiska namnet på uppstartsenheten i SRM för " +"dva0, namnet för uppstartsenheten för Linux för " +"fd0, och de önskade kärnparametrarna för " +"arguments." + +#. Tag: para +#: boot-installer.xml:388 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See " +"." +msgstr "" +"Om du vill ange kärnparametrar vid uppstart med MILO, " +"måste du avbryta bootstrap när du kommit in i MILO. Se ." + +#. Tag: title +#: boot-installer.xml:398 +#, no-c-format +msgid "Booting from Floppies with the ARC or AlphaBIOS Console" +msgstr "Uppstart från startdisketter med ARC eller AlphaBIOS-konsoll" + +#. Tag: para +#: boot-installer.xml:400 +#, no-c-format +msgid "" +"In the OS Selection menu, set linload.exe as the boot " +"loader, and milo as the OS Path. Bootstrap using the " +"newly created entry." +msgstr "" +"I valmenyn för operativsystem, ställ in linload.exe som " +"starthanterare, och milo som \"OS Path\". Kör bootstrap " +"med den nyligen skapade posten." + +#. Tag: title +#: boot-installer.xml:409 +#, no-c-format +msgid "Booting with MILO" +msgstr "Uppstart med MILO" + +#. 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 "" +"MILO som finns på bootstrap-mediumet är konfigurerad att automatiskt " +"fortsätta direkt till Linux. Om du önskar att avbryta är allt du behöver " +"göra att trycka på blanksteg under MILO-nedräkningen." -#~ msgid "" -#~ "ARC requires that you use an MS-DOS partition table (as created by " -#~ "cfdisk) for the boot disk. Therefore MS-DOS partition " -#~ "tables are the native 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 "" -#~ "ARC kräver att du använder en MS-DOS-partitionstabell (som skapas av " -#~ "cfdisk) för uppstartsdisken. Därför är MS-DOS-" -#~ "partitionstabeller det ursprungliga partitionsformatet vid " -#~ "uppstarter från ARC. Faktum är att eftersom AlphaBIOS innehåller ett " -#~ "diskpartitioneringsverktyg kanske du föredrar att partitionera dina " -#~ "diskar från firmwaremenyerna före installation av Linux." +#. 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: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Om du vill uttryckligen ange alla bitar (till exempel, för att skicka med " +"ytterligare parametrar), kan du använda ett kommando som denna: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" Om du startar upp från något annat än en " +"diskett, ersätt fd0 i exemplet ovan med lämpligt " +"enhetsnamn i Linux-notation. Kommandot help ger dig en " +"kort referens på MILO-kommandon." + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "Uppstart från TFTP" + +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"Uppstart från nätverket kräver att du har en nätverksanslutning och en TFTP-" +"server konfigurerad för uppstarter (DHCP, RARP eller BOOTP)." -#~ msgid "" -#~ "Conversely, SRM is incompatible " -#~ "Specifically, the bootsector format required by the Console Subsystem " -#~ "Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " -#~ "BSD disklabel format, this is the native partition format " -#~ "for SRM installations." -#~ msgstr "" -#~ "Motsatt är SRM inkompatibel " -#~ "Specifikt är formatet på uppstartssektorn som krävs av Console Subsystem " -#~ "Specification i konflikt med placeringen av DOS-partitionstabellen. med MS-DOS-partitionstabeller. Eftersom Tru64 Unix " -#~ "använder formatet för BSD-disketiketter, är det här det ursprungliga " -#~ "(native) partitionsformatet för SRM-installationer." +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "" +"Äldre system såsom 715 kan kräva att en RBOOT-server används istället för en " +"BOOTP-server." -#~ 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 "" -#~ "GNU/Linux är det enda operativsystemet på Alpha som kan startas upp från " -#~ "båda konsolltyperna, men &debian; &release; har endast stöd för uppstart " -#~ "på SRM-baserade system. Om du har en Alpha som det inte finns någon SRM-" -#~ "version tillgänglig för, om du vill använda dubbel-uppstart tillsammans " -#~ "med Windows NT, eller om din uppstartsenhet kräver stöd för ARC-konsoll " -#~ "för initiering av BIOS kommer du inte kunna använda installeraren för " -#~ "&debian; &release;. Du kan fortfarande köra &debian; &release; på sådana " -#~ "system genom att använda andra installationsmedia, till exempel kan du " -#~ "installera Debian woody med MILO och uppgradera." +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "" +"Installationsmetoden som har stöd för nätverksuppstart finns beskriven i " +"." + +#. Tag: title +#: boot-installer.xml:459 +#, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "Starta upp NetWinder via TFTP" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" +"Netwinder har två nätverksgränssnitt: Ett 10 Mbps NE2000-kompatibelt kort " +"(som generellt sett refereras till som eth0) och ett 100 " +"Mbps Tulip-kort. Det kan uppstå problem vid inläsning av avbilden via TFTP " +"med 100 Mbps-kortet så det rekommenderas att du använder 10 Mbps-" +"gränssnittet (det som är märkt som 10 Base-T)." + +#. 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 ." +msgstr "" +"Du behöver NeTTrom 2.2.1 eller senare för att starta upp " +"installationssystemet, och version 2.3.3 rekommenderas. Tyvärr finns inte " +"firmwarefilerna tillgängliga för hämtning för tillfället på grund av " +"licensproblem. Om denna situation ändras, kan du hitta nya avbilder på " +"." + +#. 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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" +"När du startar upp din Netwinder måste du avbryta uppstartsprocessen under " +"nedräkningen. Det här låter dig ställa in ett antal firmwareinställningar " +"som behövs för att kunna starta upp installeraren. Börja först med att läsa " +"in standardinställningarna: \n" +" NeTTrom command-> load-defaults\n" +" Sedan måste du konfigurera nätverket, antingen " +"med en statisk adress: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" där 24 är antalet bitar i nätmasken, eller en " +"dynamisk adress: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" Du kanske även behöver konfigurera inställningen " +"route1 om TFTP-servern inte finns på det lokala " +"subnätet. Om du följer dessa inställningar, måste du ange TFTP-servern och " +"avbildens plats. Du kan sedan lagra dina inställningar till flashminnet. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Nu måste du berätta för firmware att TFTP-" +"avbilden ska användas för att starta upp: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" Om du använder en seriekonsoll för att " +"installera din Netwinder, behöver du lägga till följande inställning: " +"\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternativt, för installationer med ett " +"tangentbord och skärm måste du ställa in: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" Du kan använda kommandot printenv för att granska dina miljöinställningar. Efter att du har validerat " +"att inställningarna är korrekta kan du läsa in avbilden: " +"\n" +" NeTTrom command-> boot\n" +" Om du springer på några problem, finns en detaljerad HOWTO tillgänglig." + +#. Tag: title +#: boot-installer.xml:529 +#, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "Uppstart från TFTP på CATS" + +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"På CATS-maskiner, använd boot de0: eller liknande på " +"Cyclone-prompten." + +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "Uppstart från cd-rom" + +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"Den enklaste vägen för de flesta personer är att använda en uppsättning " +"Debian-cd-skivor. Om du har en cd-uppsättning och om din maskin har stöd för " +"att starta upp direkt från cd, bra! Bara att " +"konfigurera ditt system för att starta upp från en cd som beskrivs i , mata in din cd-skiva, starta om och " +"fortsätt till nästa kapitel." + +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"Observera att vissa cd-enheter kan kräver speciella drivrutiner och kan " +"därför vara otillgängliga i de tidiga stegen av installationen. Om det visar " +"sig att det vanliga sättet att starta upp från en cd inte fungerar på din " +"maskinvara, besök det här kapitlet igen och läs om alternativa kärnor och " +"installationsmetoder som kan fungera för dig." + +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"Även om du inte kan starta upp från cd-rom kan du antagligen installera " +"Debians systemkomponenter och de paket du vill från cd-rom. Starta helt " +"enkelt upp på ett annat media, såsom disketter. När det är dags att " +"installera operativsystemet, grundsystemet och eventuellt andra paket, peka " +"installationssystemet till cd-rom-enheten." + +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"Om du har problem att starta upp, se ." -#~ msgid "" -#~ "Because MILO 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 "" -#~ "På grund av att MILO inte finns tillgänglig för någon " -#~ "av Alpha-systemen för tillfället i produktion (i februari 2000), och på " -#~ "grund att det inte längre är nödvändigt att köra en licens för OpenVMS " -#~ "eller Tru64 Unix för att få SRM-firmware på din äldre Alpha, " -#~ "rekommenderas det att du använder SRM om möjligt." +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"För att starta upp en cd-rom från Cyclones konsollprompt, använd kommandot " +"boot cd0:cats.bin" + +#. Tag: title +#: boot-installer.xml:589 +#, no-c-format +msgid "Booting from Firmware" +msgstr "Starta upp från firmware" + +#. 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 "" +"Det finns ett ökande antal konsumentenheter som startar upp direkt från ett " +"flashchip på enheten. Installeraren kan skrivas till flash så att den " +"automatiskt startar upp när du startar om dina maskiner." -#~ msgid "" -#~ "The following table summarizes available and supported system type/" -#~ "console combinations (see for the system " -#~ "type names). The word ARC below denotes any of the ARC-" -#~ "compliant consoles." -#~ msgstr "" -#~ "Följande tabell sammanställer tillgängliga och systemtyper/" -#~ "konsollkombinationer som stöds (se för " -#~ "namnen på systemtyperna). Ordet ARC nedan below indikerar " -#~ "någon av de ARC-godkända konsollerna." +#. 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 "" +"I många fall gäller inte din garanti när firmware i inbäddade enheter " +"ändras. Ibland kan du inte heller återhämta din enhet om det inträffar " +"problem under flashningsprocessen. Var därför försiktig och följ stegen noga." + +#. Tag: title +#: boot-installer.xml:612 +#, no-c-format +msgid "Booting the NSLU2" +msgstr "Starta upp NSLU2" + +#. Tag: para +#: boot-installer.xml:613 +#, no-c-format +msgid "There are three ways how to put the installer firmware into flash:" +msgstr "" +"Det finns tre sätt hur man lägger in installerarens firmware i flash-minnet:" -#~ msgid "System Type" -#~ msgstr "Systemtyp" +#. Tag: title +#: boot-installer.xml:619 +#, no-c-format +msgid "Using the NSLU2 web interface" +msgstr "Använda webbgränssnittet i NSLU2" -#~ msgid "Console Type Supported" -#~ msgstr "Konsolltyper som stöds" +#. Tag: para +#: boot-installer.xml:620 +#, no-c-format +msgid "" +"Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." +msgstr "" +"Gå till administrationsavsnittet och välj menyposten Upgrade. Du kan sedan bläddra på din disk efter installationsavbilden du " +"tidigare hämtade ner. Tryck sedan på knappen Start Upgrade, bekräfta, vänta ett par minuter och bekräfta igen. Systemet kommer " +"sedan att starta upp direkt in i installeraren." + +#. Tag: title +#: boot-installer.xml:631 +#, no-c-format +msgid "Via the network using Linux/Unix" +msgstr "Via nätverket med Linux/Unix" + +#. Tag: para +#: boot-installer.xml:632 +#, no-c-format +msgid "" +"You can use upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 "" +"Du kan använda upslug2 från valfri Linux- eller Unix-" +"maskin för att uppgradera maskinen via nätverket. Den här programvaran är " +"paketerad för Debian. Först måste du försätta din NSLU2 i uppgraderingsläge: " +" Koppla loss alla diskar och/eller enheter " +"från USB-portarna. Stäng av din NSLU2 Tryck och håll nere omstartsknappen " +"(tillgänglig genom ett litet hål på baksidan ovanför strömanslutningen). Tryck och släpp strömknappen för att " +"starta upp NSLU2. Vänta 10 sekunder och " +"se på ready-/status-lampan. Efter 10 sekunder kommer en att ändra färg från " +"orange till röd. Släpp omedelbart omstartsknappen. " +" Lampan på NSLU2 för ready/status kommer att blinka rött och " +"grönt (det är en sekunds fördröjning före den första gröna). NSLU2 är nu i " +"uppgraderingsläge. Se NSLU2-Linux-sidor " +"om du har problem med det här. När din NSLU2 är i uppgraderingsläge, kan du " +"lägga in den nya flashavbilden: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" Observera att verktyget även visar MAC-adressen " +"på din NSLU2, vilket kan vara användbart för att konfigurera din DHCP-" +"server. Efter att hela avbilden har skrivits och validerats kommer systemet " +"att automatiskt starta om. Se till att du ansluter din USB-disk igen nu, " +"annars kommer installeraren inte att kunna hitta den." + +#. Tag: title +#: boot-installer.xml:693 +#, no-c-format +msgid "Via the network using Windows" +msgstr "Via nätverket med Windows" + +#. Tag: para +#: boot-installer.xml:694 +#, no-c-format +msgid "" +"There is a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" +"Det finns ett verktyg för Windows för att uppgradera " +"firmware via nätverket." + +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "Uppstart från en cd-rom" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "" +"Uppstart från Linux med LILO eller GRUB" -#~ msgid "alcor" -#~ msgstr "alcor" +#. 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 ." +msgstr "" +"För att starta upp installeraren från hårddisk måste du första hämta och " +"placera de nödvändiga filerna som beskrivs i ." -#~ msgid "ARC or SRM" -#~ msgstr "ARC eller SRM" +#. 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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"Om du bara tänkte använda hårddisken för att starta upp och sedan hämta allt " +"över nätverket, bör du hämta filen netboot/debian-installer/i386/" +"initrd.gz och dess motsvarande kärna, netboot/debian-" +"installer/i386/linux. Den låter dig partionera om hårddisken från " +"vilken du startar upp installeraren, det bör du göra med försiktighet." + +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"Alternativt, om du tänker behålla en existerande partition på hårddisken i " +"oförändrat skick under installationen, kan du hämta filen hd-media/" +"initrd.gz och dess kärna, såväl som en kopia av en cd-avbild till " +"enheten (se till att filens namn slutar på .iso). " +"Installeraren kan sedan starta upp från enheten och installera från cd-" +"avbilden, utan behov av nätverk." + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"För LILO, behöver du konfigurera två viktiga saker i " +"/etc/lilo.conf: för att " +"läsa in initrd.gz installeraren vid uppstart; få kärnan vmlinuz att " +"använda en RAM-disk som sin rotpartition. " +"Här är ett exempel på en /etc/lilo.conf:" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"För fler detaljer, referera till manualsidorna " +"initrd 4 och lilo.conf 5. Kör nu " +"lilo och starta om." + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"Proceduren för GRUB är ganska lik. Leta upp din " +"menu.lst i katalogen /boot/grub/ " +"(ibland finns den i /boot/boot/grub/), lägg till " +"följande rader: \n" +"title Ny installation\n" +"kernel (hd0,0)/boot/newinstall/vmlinuz root=/dev/ram0 ramdisk_size=12000\n" +"initrd (hd0,0)/boot/newinstall/initrd.gz\n" +" och starta om." + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"Observera att värden för ramdisk_size kan behöva " +"justeras efter initrd-avbildens storlek. Från och med nu bör det inte vara " +"några skillnader mellan GRUB och LILO." + +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "Uppstart från USB-minne" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +"Låt oss anta att du har förberett allt från och . Anslut ditt USB-minne i någon " +"ledig USB-kontakt och starta om datorn. Systemet bör starta upp och du bör " +"se prompten boot:. Här kan du ange ytterligare " +"uppstartsargument eller bara trycka &enterkey;." + +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "Uppstart från startdisketter" + +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"Du ska redan ha hämtat diskettavbilderna du behövde och skapat disketterna " +"från avbilderna i ." -#~ msgid "avanti" -#~ msgstr "avanti" +#. Tag: para +#: boot-installer.xml:949 +#, 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 "" +"För att starta upp från installerarens startdiskett, placera den i primära " +"diskettenheten, stäng ner systemet som vanligt och starta upp det igen." -#~ msgid "book1" -#~ msgstr "book1" +#. Tag: para +#: boot-installer.xml:955 +#, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"För att installera från en LS-120-enhet (ATAPI-version) med en uppsättning " +"disketter, behöver du ange den virtuella platsen för diskettenheten. Det här " +"gör man med uppstartsargumentet root=, som anger " +"enheten som drivrutinen kan binda enheten till. Till exempel, om din LS-120-" +"enhet är ansluten som första IDE-enhet (master) på andra kabeln, anger du " +"linux root=/dev/hdc på uppstartsprompten." + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"Observera att på vissa maskiner, Control " +"Alt Delete återställer inte " +"korrekt maskinen, så en hård omstart rekommenderas. Om du " +"installerar från ett existerande operativsystem (exempelvis från en DOS-" +"burk) har du inget val. Om inte, gör en hård omstart vid uppstart." + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"Disketten kommer att läsas från och du bör sedan se en skärm som " +"introducerar startdisketten och slutar med prompten boot:." -#~ msgid "SRM only" -#~ msgstr "Endast SRM" +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"När du trycker &enterkey;, bör du se meddelandet Loading..., följt av Uncompressing Linux..., och sedan en skärm full av information om maskinvaran i " +"ditt system. Mer information angående den här fasen i uppstartsprocessen kan " +"hittas under i ." + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"Efter uppstart från startdisketten kommer rotdisketten att efterfrågas. Mata " +"in rotdisketten och tryck &enterkey;, och dess innehåll kommer att läsas in " +"i minnet. Installeringsprogrammet debian-installer " +"startas automatiskt." + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "Det finns olika sätt att göra en TFTP-uppstart på i386." + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "Nätverkskort eller moderkort med stöd för PXE" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"Det kan vara så att ditt nätverkskort eller moderkort erbjuder " +"funktionalitet för uppstart via PXE. Det är en återimplementation av TFTP-" +"uppstart från Intel. Om så är fallet " +"kan du konfigurera ditt BIOS att starta upp från nätverket." + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "Nätverkskort med Network BootROM" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "" +"Det kan vara så att ditt nätverkskort erbjuder funktionalitet för att starta " +"upp via TFTP." -#~ msgid "cabriolet" -#~ msgstr "cabriolet" +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"Låt oss (&email-debian-boot-list;) veta hur du gjorde det. " +"Referera till det här dokumentet." + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"Etherboot-projektet erbjuder " +"startdisketter och även ROM-filer som kan göra uppstarter via TFTP." + +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "Uppstartsprompten" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"När installeraren startar upp bör du presenteras med en snäll grafisk skärm " +"som visar Debians logotyp och en uppstartsprompt: \n" +"Press F1 for help, or ENTER to boot:\n" +" Vid uppstartsprompten kan du antingen bara " +"trycka &enterkey; för att starta upp installeraren med standardalternativ " +"eller ange en specifik uppstartsmetod och, valfritt, uppstartsparametrar." + +#. Tag: para +#: boot-installer.xml:1078 +#, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"Information om tillgängliga uppstartsmetoder och om uppstartsparametrar som " +"kan vara användbara kan hittas genom att trycka F2 till " +"F8. Om du lägger till några parametrar till kommandoraden, " +"tänk på att ange uppstartsmetoden (standard är linux) " +"och ett blanksteg före den första parametern (exempelvis linux " +"fb=false)." + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"Om du installerar systemet via en fjärrhanteringsenhet som tillhandahåller " +"ett textgränssnitt till VGA-konsollen, kan du inte se den initiala grafiska " +"uppstartsskärmen under uppstarten av installeraren; du kanske inte heller " +"kan se uppstartsprompten. Exempel på de här enheterna inkluderar " +"textkonsollen för Compaqs integrated Lights Out (iLO) och HP:" +"s Integrated Remote Assistant (IRA). Du kan helt blint trycka " +"F1 I vissa fall kräver de här enheterna en speciell " +"tangentsekvens för att göra den här tangenttryckningen, till exempel " +"använder IRA Ctrl F ," +" 1. för att komma förbi den här " +"skärmen och visa hjälptexten. När du har kommit förbi uppstartsskärmen och " +"är vid hjälptexten kommer dina tangenttryckningar att ekas vid prompten som " +"förväntat. För att förhindra att installeraren använder grafikkortet i " +"resten av installationen, kan du också lägga till fb=false till uppstartsprompten, som beskrivs i hjälptexten." + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "Cd-innehåll" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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 "" +"Det finns tre enkla variationer av Debians installationsskivor. Cd-skivan " +"Visitkort innehåller en minimal installation som passar " +"på ett minimalt cd-media. Den kräver en nätverksanslutning för att " +"installera resten av grundinstallationen och skapa ett användbart system. Cd-" +"skivan Nätinstallation har alla paket för en " +"grundinstallation men kräver en nätverksanslutningen till en Debian-spegel " +"för att installera de extra paket som man vill ha för ett komplett system. " +"Uppsättningen av Debian-cd-skivor kan installera ett komplett system från en " +"mängd olika paket utan behov av tillgång till nätverket." + +#. Tag: para +#: boot-installer.xml:1180 +#, 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 "" +"Arkitekturen IA-64 använder nästa generations Extensible Firmware Interface " +"(EFI) från Intel. Olik det traditionella x86 BIOS som inte känner till mer " +"om uppstartsenheten annat än partitionstabellen och huvudstartsektorn (MBR), " +"EFI kan läsa och skriva filer från FAT16- eller FAT32-formaterade " +"diskpartitioner. Det här förenklar den ofta mystiska processen hur ett " +"system startas upp. Starthanteraren och EFI-firmware som har stöd för det " +"har ett helt filsystem att lagra nödvändiga filer för att starta upp " +"maskinen. Det betyder att systemdisken på ett IA-64-system har ytterligare " +"en diskpartition som är dedicerad till EFI istället för den enkla MBR eller " +"uppstartsblock på mer konventionella system." + +#. Tag: para +#: boot-installer.xml:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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 "" +"Debian Installer-cd-skivan innehåller en liten EFI-partition där " +"starthanteraren ELILO, dess konfigurationsfil, " +"installerarens kärna, och initiala filsystem (initrd) finns. Det körande " +"systemet innehåller även en EFI-partition där de nödvändiga filerna för " +"uppstart av systemet finns. De här filerna är läsbara från EFI-skalet som " +"beskrivs nedan." + +#. Tag: para +#: boot-installer.xml:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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 "" +"De flesta detaljer för hur ELILO faktiskt läser in och " +"startar ett system är inte synliga för systeminstalleraren. Dock, " +"installeraren måste ställa in en EFI-partition före installation av " +"grundsystemet. Annars kommer installationen av ELILO att " +"misslyckas som resulterar i att systemet inte kan startas upp. EFI-" +"partitionen allokeras och formateras i partitioneringssteget av " +"installationen före inläsningen av paketen på systemdisken. " +"Partitioneringsfunktionen verifierar även att en lämplig EFI-partition finns " +"före den tillåter installationen att fortsätta." + +#. Tag: para +#: boot-installer.xml:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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 "" +"EFI Boot Manager visas som sista steget för initiering av firmware. Den " +"visar en menylista från vilken användaren kan välja ett alternativ. Beroende " +"på systemmodellen och vilken annan programvara som har lästs in på systemet " +"kan den här menyn skilja sig från system till system. Det bör finnas " +"åtminstone två menyposter, Boot Option Maintenance Menu " +"och EFI Shell (Built-in). Första alternativet föredras, " +"dock, om det alternativet inte finns tillgängligt eller att cd-skivan av " +"någon anledning inte startar upp med den, använd det andra alternativet." + +#. Tag: title +#: boot-installer.xml:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "VIKTIGT" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" +"EFI Boot Manager kommer att välja en standardåtgärd för uppstart, vanligtvis " +"det första menyvalet, inom ett förinställt antal sekunder. Det här indikeras " +"av en nedräkning i nedre delen av skärmen. När räknaren har räknat ned och " +"systemet startar standardåtgärden, kanske du måste starta om maskinen för " +"att fortsätta installationen. Om standardåtgärden är EFI-skalet kan du " +"återvända till Boot Manager genom att köra exit vid " +"skalprompten." + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "Alternativ 1: Starta upp från Boot Option Maintenance Menu" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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 "" +"Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer " +"att visa EFI Boot Manager-sidan och menyn efter den färdigställt sin " +"systeminitiering." -#~ msgid "dp264" -#~ msgstr "dp264" +#. Tag: para +#: boot-installer.xml:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"Välj Boot Maintenance Menu från menyn med piltangenterna " +"och tryck ENTER. Det här kommer att visa en ny meny." -#~ msgid "eb164" -#~ msgstr "eb164" +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" +"Välj Boot From a File från menyn med piltangenterna och " +"tryck ENTER. Det här kommer att visa en lista på enheter " +"som firmware har sökt efter. Du bör se två menyrader som innehåller antingen " +"etiketten Debian Inst [Acpi ... eller Removable " +"Media Boot. Om du undersöker resten av menyraden kommer du att se " +"att informationen för enheten och kontrollern är samma." + +#. Tag: para +#: boot-installer.xml:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" +"Du kan välja någon av posterna som refererar till cd/dvd-enheten. Välj med " +"piltangenterna och tryck sedan ENTER. Om du väljer " +"Removable Media Boot kommer maskinen att omedelbart " +"påbörja uppstartssekvensen. Om du istället väljer Debian Inst " +"[Acpi ..., kommer den att visa en kataloglistning på den startbara " +"delen av cd-skivan, som kräver att du fortsätter till nästa (ytterligare) " +"steg." + +#. Tag: para +#: boot-installer.xml:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" +"Du behöver endast det här steget om du valde Debian Inst [Acpi .... Kataloglistningen kommer även att visa [Treat like " +"Removable Media Boot] på den näst sista raden. Välj den raden med " +"piltangenterna och tryck ENTER. Det här kommer att starta " +"inläsningssekvensen för uppstarten." + +#. Tag: para +#: boot-installer.xml:1302 +#, 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 "" +"Dessa steg startar Debians starthanterare som kommer att visa en menysida " +"för dig att välja en uppstartskärna och flaggor. Fortsätt till valet av " +"uppstartskärna och flaggor." + +#. Tag: title +#: boot-installer.xml:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "Alternativ 2: Starta upp från EFI-skalet" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" +"Om, av någon anledning, alternativ 1 inte lyckas, starta om maskinen och när " +"EFI Boot Manager-skärmen visas bör det finnas ett alternativ kallat " +"EFI Shell [Built-in]. Starta upp Debian Installer-skivan " +"med följande steg:" + +#. Tag: para +#: boot-installer.xml:1324 +#, 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 "" +"Mata in cd-skivan i dvd/cd-enheten och starta om maskinen. Firmware kommer " +"att visa EFI Boot Manager-sidan och menyn efter den färdigställer " +"systeminitieringen." -#~ msgid "eb64p" -#~ msgstr "eb64p" +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" +"Välj EFI Shell från menyn med piltangenterna och tryck " +"ENTER. EFI-skalet kommer att söka av alla startbara " +"enheter och visa dem i konsollen före den visar sin kommandoprompt. De kända " +"partitioner som är startbara på enheterna kommer att visa enhetsnamnet " +"fsn:. Alla andra kända " +"partitioner kommer att namnges som blkn:" +". Om du matade in cd-skivan precis innan du gick in i skalet " +"kommer det ta några extra sekunder när den initierar cd-enheten." + +#. Tag: para +#: boot-installer.xml:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" +"Undersök utskriften från skalet som letar efter cd-rom-enheten. Det är " +"antagligen enheten fs0: även om andra enheter med " +"startbara partitioner också kommer att visas som fsn." + +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"Ange fsn: och tryck på " +"ENTER för att välja den enhet där n är partitionsnumret för cd-rom. Skalet kommer nu att visa " +"partitionsnumret som sin prompt." + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"Ange elilo och tryck på ENTER. Det " +"kommer att påbörja uppstartssekvensen." -#~ msgid "eb66" -#~ msgstr "eb66" +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"Som med alternativ 1, de här stegen startar Debians starthanterare som " +"kommer att visa en menysida för dig där du kan välja en uppstartskärna och " +"alternativ. Du kan även ange det kortare kommandot " +"fsn:elilo vid skalprompten. " +"Fortsätt till att välja uppstartskärna och alternativ." + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "Installation med en seriekonsoll" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"Du kan välja att genomföra en installation med en skärm och tangentbord " +"eller genom att använda en serieanslutning. För att använda skärm/" +"tangentbord, välj ett alternativ som innehåller strängen [VGA console]. För " +"att installera över en serieanslutning, välj ett alternativ som innehåller " +"strängen [BAUD baud serial console], där " +"BAUD är hastigheten för din seriekonsoll. " +"Menyposter för de mest vanliga hastigheterna för ttyS0-enheten är " +"förkonfigurerade." + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"I de flesta fall kommer att du vilja att installeraren använder samma " +"bithastighet som din anslutning till EFI-konsollen. Om du inte är säker på " +"vad den här inställningen är inställd till kan du hämta den med kommandot " +"baud i EFI-skalet." + +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"Om det inte finns ett alternativ tillgängligt som är konfigurerad för " +"serieenheten eller den hastighet du vill använda kan du åsidosätta " +"inställningarna för konsollen för en av de existerande menyalternativen. " +"Till exempel för att använda en konsoll på 57600 baud över enheten ttyS1, " +"ange console=ttyS1,57600n8 i textfönstretBoot:" +"." + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" +"De flesta IA-64-maskiner skeppas med en standardinställning för konsollen på " +"9600 baud. Den här inställningen är ganska långsam, och den normala " +"installationsprocessen kommer att ta mycket längre tid att rita upp varje " +"skärm. Du bör tänka på att antingen öka hastigheten som används för att " +"genomföra installationen, eller genomföra en installation i textläget. Se " +"hjälpmenyn Params för instruktioner för hur man " +"startar installeraren i textläge." + +#. Tag: para +#: boot-installer.xml:1419 +#, 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 "" +"Om du väljer fel konsolltyp kommer du kunna välja kärna och ange parametrar " +"men både skärmen och din inmatning kommer att försvinna så snart som kärnan " +"startat och kräver att du startar om före du kan påbörjar installationen." + +#. Tag: title +#: boot-installer.xml:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "Välj uppstartskärna och inställningar" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" +"Starthanteraren kommer att visa ett formulär med en menylista och ett " +"textfönster med en Boot:-prompt. Piltangenterna " +"väljer en post från menyn och all text som skrivs på tangentbordet visas i " +"textfönstret. Det finns även hjälpskärmar som kan visas genom att tryck på " +"lämplig funktionstangent. Hjälpskärmen General " +"förklarar menyvalet och skärmen Params förklarar de " +"vanliga kommandoradsflaggorna." + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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 "" +"Konsultera hjälpskärmen General för beskrivningen av " +"vilka kärnor och installationslägen som är mest lämpliga för din " +"installation. Du bör även konsultera nedan " +"för ytterligare parametrar som du kanske vill ställa in i textfönstret " +"Boot:. Kärnversionen du väljer kommer att välja den " +"kärnversion som kommer att användas för både installationsprocessen och det " +"installerade systemet. Om du påträffar problem med kärnan under " +"installationen, kommer du även att få de samma problem med systemet du " +"installerar. De följande två stegen kommer att välja och påbörja " +"installationen:" + +#. Tag: para +#: boot-installer.xml:1460 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "" +"Välj kärnversionen och installationsläget som är mest lämplig för dina behov " +"med piltangenterna." -#~ msgid "eb66p" -#~ msgstr "eb66p" +#. Tag: para +#: boot-installer.xml:1465 +#, 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 "" +"Ange valfri uppstartsparameter genom att skriva på tangentbordet. Texten " +"kommer att visas direkt i textfönstret. Det är här som kärnparametrar (såsom " +"inställningar för seriekonsoll) anges." -#~ msgid "jensen" -#~ msgstr "jensen" +#. Tag: para +#: boot-installer.xml:1472 +#, no-c-format +msgid "" +"Press ENTER. 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 "" +"Tryck ENTER. Det kommer att läsa in och starta kärnan. " +"Kärnan kommer att visa dess vanliga initieringsmeddelanden följt av första " +"skärmen av Debian Installer." -#~ msgid "lx164" -#~ msgstr "lx164" +#. Tag: para +#: boot-installer.xml:1481 boot-installer.xml:1617 +#, 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 "" +"Fortsätt till nästa kapitel för att fortsätta installationen där du kommer " +"att ställa in språkanpassning, nätverk och diskpartitioner." -#~ msgid "miata" -#~ msgstr "miata" +#. Tag: para +#: boot-installer.xml:1492 +#, no-c-format +msgid "" +"Booting an IA-64 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 "" +"Starta upp ett IA-64-system från nätverket liknar en uppstart från cd-skiva. " +"Den enda skillnaden är hur installationskärnan läses in. EFI Boot Manager " +"kan läsa in och starta program från en server på nätverket. När " +"installationskärnan är inläst och startar, kommer systeminstallationen att " +"fortsätta genom samma steg som för cd-installationen med undantaget av att " +"paketen för grundinstallationen kommer att läsas från nätverket istället för " +"cd-enheten." + +#. Tag: para +#: boot-installer.xml:1526 +#, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" +"Nätverksuppstart för IA-64-system kräver två arkitekturspecifika åtgärder. " +"På uppstartsservern måste DHCP och TFTP konfigureras för att leverera " +"elilo. På klienten måste ett nytt uppstartsalternativ " +"definieras i EFI-uppstartshanteraren för att aktivera inläsning över ett " +"nätverk." + +#. Tag: title +#: boot-installer.xml:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "Konfiguration av servern" + +#. Tag: para +#: boot-installer.xml:1538 +#, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" +"En lämplig TFTP-post för att starta upp via nätverket på ett IA-64-system " +"ser ut ungefär som den här: \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" +" Observera att målet är att få elilo." +"efi att köra på klienten." + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" +"Packa upp filen netboot.tar.gz i katalogen som används " +"som rot för din tftp-server. Vanliga rotkataloger för tftp är /var/" +"lib/tftp och /tftpboot. Det kommer att " +"skapas en debian-installer-katalog som innehåller " +"uppstartsfilerna för ett IA-64-system." + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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 "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" + +#. Tag: para +#: boot-installer.xml:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" +"Filen netboot.tar.gz innehåller en fil kallad " +"elilo.conf som bör fungera för de flesta " +"konfigurationer. Dock, om du behöver göra ändringar i denna fil kan du hitta " +"den i katalogen debian-installer/ia64/. Det är möjligt " +"att ha olika konfigurationsfiler för olika klienter genom att namnge dem med " +"klientens IP-adress hexadecimalt och ändelsen .conf " +"istället för elilo.conf. Se dokumentationen som " +"tillhandahålls av paketet elilo för detaljer." + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "Konfiguration av klienten" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" +"För att konfigurera stöd för klienten att starta upp via TFTP, börja genom " +"att starta upp till EFI och gå in i Boot Option Maintenance Menu. Lägg till ett uppstartsalternativ. " +" Du bör se en eller flera rader med " +"texten Load File [Acpi()/.../Mac()]. Om fler än " +"en av de här raderna finns, välj den som innehåller MAC-adressen för " +"gränssnittet från vilket du kommer att starta upp. Använd piltangenterna för " +"att markera ditt val, tryck sedan Enter. " +"Namnge posten Netboot eller något liknande, spara, " +"och gå tillbaka till menyn med uppstartsalternativ. Du bör se det nya uppstartsalternativet som du nyss skapade, " +"och att välja det för initiera en DHCP-fråga som leder till en inläsning av " +"elilo.efi från TFTP-servern." + +#. Tag: para +#: boot-installer.xml:1608 +#, 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 "" +"Starthanteraren kommer att visa sin prompt efter den har hämtat och " +"bearbetat sin konfigurationsfil. Vid denna punkt, fortsätter installationen " +"med samma steg som en cd-installation. Välj ett uppstartsalternativ som ovan " +"och när kärnan har installerat sig själv från nätverket, kommer den att " +"starta Debian Installer." + +#. Tag: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "Välja en installationsmetod" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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 "" +"Vissa underarkitekturer av &arch-title; har alternativet att starta upp med " +"antingen en Linuxkärna av version 2.4.x eller 2.2.x. När en sådan " +"valmöjlighet finns, prova 2.4.x-kärnan. Installeraren bör även kräva mindre " +"minne när 2.4.x-kärnan används eftersom 2.2.x kräver en fast storlek på " +"ramdisken och 2.4.x använder tmpfs." + +#. Tag: para +#: boot-installer.xml:1640 +#, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "" +"Om du använder en Linux-kärna med version 2.2.x, behöver du använda " +"kärnparametern &ramdisksize;." -#~ msgid "mikasa" -#~ msgstr "mikasa" +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "" +"Se till att root=/dev/ram är en av dina " +"kärnparametrar." -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p" +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"Om du får problem, ta en titt i cts's " +"&arch-title; debian-installer FAQ." + +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "Amiga" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"Den enda installationsmetoden tillgänglig för amiga är via hårddisken (se " +"). Med andra ord, cd-skivan är " +"inte startbar." -#~ msgid "nautilus" -#~ msgstr "nautilus" +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "" +"Amiga does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"Amiga fungerar för tillfället inte med bogl, så om du ser fel från bogl " +"behöver du inkludera uppstartsparametern fb=false." + +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "Atari" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "" +"The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" +"Installeraren för atari kan startas från antingen hårddisken (se ) eller från disketter (se ). Med andra ord, cd-skivan är inte startbar." + +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "" +"Atari does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"Atari fungerar för närvarande inte med bogl så om du ser fel från bogl " +"behöver du inkludera uppstartsparametern fb=false." + +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "BVME6000" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" +"Installeraren för BVME6000 kan behöva startas från en cd-rom (se ), startdisketter (se ), eller via nätverket (se )." + +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "Macintosh" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"). In other words the cdrom is not " +"bootable. Macs do not have a working 2.4.x kernel." +msgstr "" +"Den enda installationsmetoden som är tillgänglig för mac är från hårddisken " +"(se ). Med andra ord, cd-skivan är " +"inte startbar. Mac har ingen fungerande 2.4.x-kärna." -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (se handboken för moderkortet) eller SRM" - -#~ msgid "noname" -#~ msgstr "noname" +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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 "" +"Om din maskinvara använder en 53c9x-baserad scsi-buss, behöver du kanske " +"inkludera kärnparametern mac53c9x=1,0. Maskinvara med " +"två sådana scsi-bussar, såsom Quadra 950, behöver istället " +"mac53c9x=2,0. Alternativt kan parametern anges som " +"mac53c9x=-1,0 som lämnar automatisk identifiering " +"påslagen, men som inaktiverar SCSI-nedkopplingar. Observera att den här " +"parametern endast behöver anges om du har fler än en hårddisk; i annat fall " +"kommer systemet att köra snabbare än om du inte angav det." + +#. Tag: title +#: boot-installer.xml:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "MVME147 och MVME16x" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" +"Installeraren för MVME147 och MVME16x kan behöva startas från antingen " +"startdisketter (se ) eller via " +"nätverket (se ). Med andra ord är " +"inte cd-skivan startbar." + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" +"Den enda installationsmetoden som är tillgänglig för Q40/Q60 är från " +"hårddisken (se ). Med andra ord, " +"cd-skivan är inte startbar." + +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "Starta upp från en hårddisk" + +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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 "" +"Uppstart från ett existerande operativsystem är ofta ett bekvämt alternativ, " +"för vissa system är det den enda installationsmetoden som stöds." -#~ msgid "noritake" -#~ msgstr "noritake" +#. Tag: para +#: boot-installer.xml:1769 boot-installer.xml:2367 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"För att starta upp installeraren från hårddisk måste du redan ha hämtat och " +"placerat de filer som behövs i ." -#~ msgid "noritake-p" -#~ msgstr "noritake-p" +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" +"Åtminstone sex olika ramdiskar kan användas för att starta upp från " +"hårddisken, tre olika typer vardera med och utan stöd för en Linuxkärna " +"version 2.2.x (se MANIFEST för detaljer)." + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" +"De tre olika typer av ramdiskar är cdrom, hd-" +"media och nativehd. De här ramdiskarna " +"skiljer sig endast i sin källkod för installationspaketen. Ramdisken " +"cdrom använder en cd-rom för att hämta paket för debian-" +"installer. Ramdisken hd-media använder en iso-avbild av " +"en cd-rom som för närvarande ligger på en hårddisk. Till slut, ramdisken " +"nativehd använder nätet för att installera paket." + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "Starta upp från AmigaOS" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"I Workbench, start Linux-installationsprocessen genom att " +"dubbelklicka på ikonen StartInstall i katalogen " +"debian." -#~ msgid "pc164" -#~ msgstr "pc164" +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" +"Du kanske måste trycka på &enterkey;-tangenten två gånger efter att Amiga-" +"installationsprogrammet har skrivit ut viss felsökningsinformation i ett " +"fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders " +"fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar " +"alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla " +"förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska " +"installationsprogrammet startas automatiskt, så att du kan fortsätta på " +"." + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "Starta upp från Atari TOS" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" +"I skrivbordsmiljön GEM, starta Linux-installationsprocessen genom att " +"dubbelklicka på ikonen bootstra.prg i katalogen " +"debian och klicka Ok i " +"programmets inställningsruta." + +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" +"Du kanske måste trycka på &enterkey;-tangenten efter att Atari-" +"bootstrapprogrammet har skrivit ut viss felsökningsinformation i ett " +"fönster. Efter det här kommer skärmen att bli grå, sedan ett par sekunders " +"fördröjning. Härnäst kommer en svart skärm med vit text att visas, som visar " +"alla sorters felsökningsinformation för kärnan. De här meddelanden kan rulla " +"förbi för snabbt för dig att läsa, men det är OK. Efter ett par sekunder ska " +"installationsprogrammet startas automatiskt, så att du kan fortsätta på " +"." + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "Starta upp från MacOS" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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 "" +"Du måste bibehålla original Mac-systemet och starta upp från det. Det är " +"viktigt att starta upp MacOS för att förbereda en " +"uppstart av starthanteraren Penguin, att du håller ned tangenten " +"shift för att förhindra att utökningar läses in. Om du inte " +"använder MacOS annat än för att läsa in Linux, kan du åstadkomma samma sak " +"genom att ta bort alla utökningar och kontrollpaneler från Macens System-" +"mapp. Annars kan körande utökningar lämnas kvar och orsaka diverse problem " +"för den körande Linux-kärnan." + +#. Tag: para +#: boot-installer.xml:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" +"Mac kräver starthanteraren Penguin. Om du inte har " +"verktygen för att hantera ett Stuffit-arkiv, &penguin19." +"hfs; är en hfs-diskavbild med en uppackad Penguin. beskriver hur man kopierar den här avbilden till " +"en diskett." + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." +msgstr "" +"På MacOS-skrivbordet, starta Linux-installationsprocessen genom att " +"dubbelklicka på Penguin Prefs-ikonen i katalogen " +"Penguin. Uppstartaren Penguin kommer " +"att startas upp. Gå till posten Settings i menyn " +"File, klicka på fliken Kernel. Välj " +"kärnavbilden (vmlinuz) och ramdisk (initrd." +"gz) i katalogen install genom att klicka på " +"motsvarande knappar i övre högra hörnet, och navigera fram till filerna i " +"dialogrutan." + +#. Tag: para +#: boot-installer.xml:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" +"För att ställa in uppstartsparametrarna i Penguin, välj File -> Settings..., växla sedan till " +"fliken Options. Uppstartsparametrar kan anges i " +"textrutan. Om du alltid vill använda de här inställningarna, välj " +"File -> Save Settings as Default." + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"Stäng Settings-dialogen, spara inställningarna och " +"starta bootstrap med posten Boot Now i " +"File-menyn." -#~ msgid "rawhide" -#~ msgstr "rawhide" +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" +"Starthanteraren Penguin kommer att skriva ut viss " +"felsökningsinformation i ett fönster. Efter det här kommer skärmen att bli " +"grå, sedan ett par sekunders fördröjning. Härnäst kommer en svart skärm med " +"vit text att visas, som visar alla sorters felsökningsinformation för " +"kärnan. De här meddelanden kan rulla förbi för snabbt för dig att läsa, men " +"det är OK. Efter ett par sekunder ska installationsprogrammet startas " +"automatiskt, så att du kan fortsätta på ." + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "Starta upp från Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "FIXME" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"Installationsprogrammet ska starta automatiskt, så du kan fortsätta nedan i " +"." -#~ msgid "ruffian" -#~ msgstr "ruffian" +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" +"För närvarande, den enda underarkitekturen av &arch-title; som har stöd för " +"uppstart via cd-rom är BVME6000." -#~ msgid "ARC only" -#~ msgstr "Endast ARC" +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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 "" +"Efter uppstarten av VMEbus-systemen kommer du bli presenterad med LILO-" +"prompten Boot:. Vid prompten, ange en av följande för att " +"starta upp Linux och påbörja installationen av Debian-programvaran med " +"terminalemuleringen vt102." + +#. Tag: para +#: boot-installer.xml:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "" +"ange i6000 &enterkey; för att installera en BVME4000/6000" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "ange i162 &enterkey; för att installera en MVME162" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "" +"ange i167 &enterkey; för att installera en MVME166/167" -#~ msgid "sable" -#~ msgstr "sable" +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"Du kan även lägga till strängen TERM=vt100 för att använda " +"terminalemuleringen vt100, exempelvis i6000 TERM=vt100 &enterkey;." -#~ msgid "sable-g" -#~ msgstr "sable-g" +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" +"För de flesta &arch-title;-arkitekturer är uppstart från ett lokalt " +"filsystem den metod som rekommenderas." -#~ msgid "sx164" -#~ msgstr "sx164" +#. Tag: para +#: boot-installer.xml:2054 +#, 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 "" +"Uppstart från startdisketten stöds endast på Atari och VME (med en SCSI-" +"diskettenhet på VME) för tillfället." + +#. Tag: title +#: boot-installer.xml:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "Uppstart för SGI via TFTP" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" +"After entering the command monitor use \n" +"bootp():\n" +" 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 netaddr environment variable. Type " +"\n" +"unsetenv netaddr\n" +" in the command monitor to do this." +msgstr "" +"Efter man gått in i kommandomonitorn, använd \n" +"bootp():\n" +" på SGI-maskiner för att starta upp Linux och " +"påbörja installationen av Debian-programvaran. För att det här ska fungera " +"måste du rensa miljövariabeln netaddr. Ange " +"\n" +"unsetenv netaddr\n" +" i kommandomonitorn för att göra det." + +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 +#: boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "Uppstart för Broadcom BCM91250A och BCM91480B via TFTP" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: " +"\n" +"ifconfig eth0 -auto\n" +" Once you have obtained an IP address, you can " +"load SiByl with the following command: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 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 "" +"På evalueringskorten Broadcom BCM91250A och BCM91480B, måste du läsa in " +"starthanteraren SiByl via TFTP som sedan kommer att läsa in och starta " +"Debian-installer. I de flesta fall kommer du första att ta emot en IP-adress " +"via DHCP men det är även möjligt att konfigurera en statisk adress. För att " +"använda DHCP kan du ange följande kommando på CFE-prompten: " +"\n" +"ifconfig eth0 -auto\n" +" När du har tagit emot en IP-adress, kan du läsa " +"in SiByl med följande kommando: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" Du behöver ersätta IP-adressen som listas i " +"exemplet med antingen namnet eller IP-adressen för din TFTP-server. När du " +"kört det här kommandot kommer installeraren att läsas in automatiskt." + +#. Tag: title +#: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "Uppstartsparametrar" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" +"På SGI-maskiner kan du lägga till uppstartsparametrar till kommandot " +"bootp(): i kommandomonitorn." -#~ msgid "takara" -#~ msgstr "takara" +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" +"Following the bootp(): 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: \n" +"bootp():/boot/tftpboot.img\n" +" Further kernel parameters can be passed via " +"append:" +msgstr "" +"Efter kommandot bootp(): kan du ange sökvägen och namnet " +"på filen som ska starta upp om du inte har angivit ett namn via din bootp/" +"dhcpserver. Exempel: \n" +"bootp():/boot/tftpboot.img\n" +" Ytterligare kärnparametrar kan skickas med via " +"append:" + +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "bootp(): append=\"root=/dev/sda1\"" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the /boot/sibyl.conf file on the TFTP " +"server and add your parameters to the extra_args " +"variable." +msgstr "" +"Du kan inte skicka med några uppstartsparametrar direkt från CFE-prompten. " +"Istället kan du redigera filen /boot/sibyl.conf på TFTP-" +"servern och lägga till din parametrar till variabeln " +"extra_args." + +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "Starta upp Cobalt via TFTP" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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 "" +"Ärligt talat använder Cobalt inte TFTP utan NFS för att starta upp. Du " +"behöver installera en NFS-server och lägga installerarens filer i /" +"nfsroot. När du startar upp din Cobalt måste du trycka ned " +"vänstra och högra piltangenterna samtidigt för att maskinen ska starta upp " +"via nätverket. Den kommer då att visa flera alternativ på skärmen. Det finns " +"följande installationsmetoder:" + +#. Tag: para +#: boot-installer.xml:2170 +#, 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 "" +"Via SSH (standard): I det här fallet kommer installeraren att konfigurera " +"nätverket via DHCP och starta en SSH-server. Den kommer sedan att visa ett " +"slumpat lösenord och annan inloggningsinformation (som IP-adress) på Cobalts " +"LCD-skärm. När du ansluter till maskinen med en SSH-klient kan du påbörja " +"installationen." + +#. Tag: para +#: boot-installer.xml:2179 +#, 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 "" +"Via seriekonsoll: Med en nollmodem-kabel kan du ansluta till serieporten på " +"din Cobalt-maskin (med 115200 bps) och genomföra installationen på detta " +"sätt. Detta alternativ är inte tillgängligt för Qube 2700-maskiner (Qube1) " +"eftersom de inte har en serieport." + +#. Tag: para +#: boot-installer.xml:2222 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"/nfsroot/default.colo file on the NFS server and add " +"your parameters to the args variable." +msgstr "" +"Du kan inte skicka med några uppstartsparametrar direkt. Istället ska du " +"redigera filen /nfsroot/default.colo på NFS-servern och " +"lägga till dina parametrar till variabeln args." + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "Begränsningar för s390" + +#. Tag: para +#: boot-installer.xml:2251 +#, no-c-format +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" +"För att kunna köra installationssystemet på S/390 behövs en fungerande " +"nätverkskonfiguration och en ssh-session." -#~ msgid "xl" -#~ msgstr "xl" +#. Tag: para +#: boot-installer.xml:2256 +#, 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 an ssh session which will launch the standard installation " +"system." +msgstr "" +"Uppstartsprocessen startar med en nätverkskonfiguration som frågar dig efter " +"flera nätverksparametrar. Om konfigurationen lyckas kommer du kunna logga in " +"på systemet genom att starta en ssh-session som kommer att starta " +"standardinstallationssystemet." + +#. Tag: title +#: boot-installer.xml:2267 +#, no-c-format +msgid "s390 Boot Parameters" +msgstr "Uppstartsparametrar för s390" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more " +"information about S/390-specific boot parameters." +msgstr "" +"På S/390 kan du lägga till uppstartsparametrar i parm-filen. Denna fil kan " +"antingen vara i ASCII- eller EBCDIC-format. Läs Device Drivers and Installation Commands för mer " +"information om S/390-specifika uppstartsparametrar." + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, " +"Option, Shift, and Delete " +"keys together while booting to boot from the CD-ROM." +msgstr "" +"För närvarande är PReP och New World PowerMac de enda underarkitekturerna " +"för &arch-title; som har stöd för uppstart från cd-rom. På PowerMac, håll " +"ned c-tangenten, eller annars tangentkombinationen " +"Command, Option, Shift " +"och Delete tillsammans vid uppstart för att starta upp från " +"cd-rom." + +#. Tag: para +#: boot-installer.xml:2331 +#, 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 "" +"OldWorld PowerMac kommer inte att starta upp på en Debian-cd på grund av att " +"OldWorld-datorer förlitade sig på att en Mac OS ROM cd-uppstartsdrivrutin " +"skulle finnas på cd-skivan, och en fri version av den här drivrutinen finns " +"inte tillgänglig. Alla OldWorld-system har diskettenheter, så använd " +"diskettenheten för att starta installeraren, och peka sedan installeraren " +"till cd-enheten för de nödvändiga filerna." + +#. Tag: para +#: boot-installer.xml:2340 +#, 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 for booting from the hard disk, except use the " +"path to yaboot on the CD at the OF prompt, such as" +msgstr "" +"Om ditt system inte startar upp direkt från cd-rom, kan du fortfarande " +"använda cd-enheten för att installera systemet. På NewWorld kan du även " +"använde ett OpenFirmware-kommando för att manuellt starta upp från cd-rom. " +"Följ instruktionerna i för att starta upp " +"från hårddisken, använd dock sökvägen till yaboot på cd-" +"skivan vid OF-prompten, såsom" + +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "0 > boot cd:,\\install\\yaboot" + +#. Tag: title +#: boot-installer.xml:2355 +#, no-c-format +msgid "Booting from Hard Disk" +msgstr "Starta upp från hårddisk" + +#. Tag: title +#: boot-installer.xml:2376 +#, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "Starta upp CHRP från OpenFirmware" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "Ännu inte skriven." + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "Starta upp OldWorld PowerMac från MacOS" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"If you set up BootX in , you can use it to " +"boot into the installation system. Double click the BootX " +"application icon. Click on the Options button and " +"select Use Specified RAM Disk. This will give you the " +"chance to select the ramdisk.image.gz file. You may " +"need to select the No Video Driver checkbox, depending " +"on your hardware. Then click the Linux button to shut " +"down MacOS and launch the installer." +msgstr "" +"Om du ställer in en BootX i , kan du " +"använda den för att starta upp installationssystemet. Dubbelklicka på " +"programikonen BootX. Klicka på knappen " +"Options och välj Use Specified RAM Disk. Det här kommer att ge dig chansen att välja filen " +"ramdisk.image.gz. Du kan behöva att kryssa i rutan " +"No Video Driver, beroende på din maskinvara. Klicka " +"sedan på knappen Linux för att stänga ner MacOS och " +"starta upp installeraren." + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "Starta upp NewWorld Mac från OpenFirmware" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" +"You will have already placed the vmlinux, " +"initrd.gz, yaboot, and " +"yaboot.conf files at the root level of your HFS " +"partition in . Restart the computer, and " +"immediately (during the chime) hold down the Option, " +"Command (cloverleaf/Apple), o, and " +"f keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"\n" +"0 > boot hd:x,yaboot\n" +" replacing x 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 " +"ide0: instead of hd:. In a few " +"more seconds you will see a yaboot prompt \n" +"boot:\n" +" At yaboot's boot: prompt, type " +"either install or install video=ofonly followed by a &enterkey;. The video=ofonly " +"argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" +"Du har redan placerat filerna vmlinux, initrd." +"gz, yaboot och yaboot.conf i rotnivån av din HFS-partition i . Starta om datorn, och omedelbart (under klockljudet) håll ned tangenterna " +"Option, Command (klöverblad/Apple), " +"o och f samtidigt. Efter ett par sekunder " +"kommer du att komma till Open Firmware-prompten. Vid prompten, ange " +"\n" +"0 > boot hd:x,yaboot\n" +" ersätt x med " +"partitionsnumret för HFS-partitionen där kärnan och yaboot-filerna " +"placerades, följt av &enterkey;. På vissa maskiner kan du behöva använda " +"ide0: istället för hd:. Om ett " +"par sekunder kommer du att se en yaboot-prompt \n" +"boot:\n" +" Vid yaboots boot:-prompt, ange " +"antingen install eller install " +"video=ofonly följt av &enterkey;. Argumentet " +"video=ofonly är för maximal kompatibilitet; du kan " +"prova den om install inte fungerar. Debians " +"installationprogram ska nu starta." + +#. Tag: title +#: boot-installer.xml:2440 +#, no-c-format +msgid "Booting from USB memory stick" +msgstr "Starta upp från USB-minne" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" +"För närvarande är NewWorld PowerMac-system kända att ha stöd för uppstart " +"via USB." -#~ msgid "xlt" -#~ msgstr "xlt" +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "" +"Make sure you have prepared everything from . 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 " +"Command Option o f all together while booting (see )." +msgstr "" +"Se till att du har förberett allt från . " +"För att starta upp ett Macintosh-system från ett USB-minne behöver du " +"använda Open Firmware-prompten, eftersom Open Firmware inte söker efter USB-" +"lagringsenheter som standard. För att komma till prompten, håll ned " +"Command Option o f samtidigt vid uppstart (se )." + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment ofpath cannot work that out " +"automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " +"/pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" +"Du behöver ta reda på var USB-lagringsenheten visas i enhetsträdet, eftersom " +"ofpath för tillfället inte kan ta reda på det " +"automatiskt. Ange dev / ls och devalias vid Open Firmware-prompten för att gå en lista på alla kända " +"enheter och enhetsalias. På upphovsmannens system med olika typer av USB-" +"minnen, fungerar sökvägar såsom usb0/disk, " +"usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1 och /pci@f2000000/usb@1b,1/hub@1/disk@1." + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" +"Having worked out the device path, use a command like this to boot the " +"installer: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" The 2 matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the ,\\\\:tbxi part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"yaboot) in the directory previously blessed with " +"hattrib -b." +msgstr "" +"Efter att enhetssökvägen har fastställts, använd ett kommando liknande den " +"här för att starta upp installeraren: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" 2 matchar den " +"Apple_HFS- eller Apple_Bootstrap-partition på vilken du tidigare kopierade " +"in uppstartsavbilden, och delen ,\\\\:tbxi instruerar " +"Open Firmware att starta upp från filen med HFS-filtypen \"tbxi\" (alltså, " +"yaboot) i katalogen som tidigare välsignats med " +"hattrib -b." + +#. Tag: para +#: boot-installer.xml:2485 +#, no-c-format +msgid "" +"The system should now boot up, and you should be presented with the " +"boot: prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." +msgstr "" +"Systemet ska nu starta upp, och du ska se en boot:-prompt. " +"Här kan du ange ytterligare uppstartsargument, eller bara trycka &enterkey;." -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, aboot, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." -#~ msgstr "" -#~ "Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så " -#~ "behovet av en mellanliggande starthanterare finns. För SRM-konsollen " -#~ "används aboot, en liten, plattformsoberoende " -#~ "starthanterare. Se (tyvärr föråldrad) SRM " -#~ "HOWTO för mer information om aboot." +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" +"Denn uppstartsmetod är ny, och kan vara svårt att få att fungera på vissa " +"NewWorld-system. Om du har problem, skriv en installationsrapport, som " +"förklaras i ." + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "" +"För närvarande har PReP- och NewWorld PowerMac-systemen stöd för uppstart " +"via nätverk." -#~ 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 "" -#~ "Följande paragrafer kommer från installationshandboken för woody och " -#~ "inkluderas här som referens: de kan vara användbara för någon vid ett " -#~ "senare datum när Debian har stöd för MILO-baserade installationer igen." +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see ) and use the command " +"boot enet:0. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try boot " +"server_ipaddr,file," +"client_ipaddr." +msgstr "" +"På maskiner med Open Firmware, såsom NewWorld Power Mac, gå in i " +"uppstartsmonitorn (se ) och använd " +"kommandot boot enet:0. PReP- och CHRP-maskiner kan ha " +"olika sätt att adressera nätverket. På en PReP-maskin bör du prova med " +"boot server_ipadr,fil,klient_ipadr." + +#. Tag: para +#: boot-installer.xml:2543 +#, 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 "" +"Uppstart från disketter stöds för &arch-title;, fast det generellt sett " +"endast gäller för OldWorld-system. NewWorld-system är inte utrustade med " +"diskettenheter, och USB-diskettenheter stöds inte för uppstart." -#~ 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: MILO and aboot." -#~ msgstr "" -#~ "Generellt sett kan ingen av dessa konsoller starta upp Linux direkt, så " -#~ "behovet av en mellanliggande starthanterare finns. Det finns två " -#~ "huvudsakliga Linux-inläsare: MILO och aboot." +#. Tag: para +#: boot-installer.xml:2555 +#, no-c-format +msgid "" +"To boot from the boot-floppy-hfs.img floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." +msgstr "" +"För att starta upp från disketten boot-floppy-hfs.img, " +"placera den i diskettenheten efter att systemet har stängts ned, och slå " +"sedan på systemet." -#~ msgid "" -#~ "MILO is itself a console, which replaces ARC or SRM in " -#~ "memory. MILO can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." -#~ msgstr "" -#~ "MILO är själv en konsoll, som ersätter ARC eller SRM i " -#~ "minnet. MILO kan startas upp från både ARC och SRM och " -#~ "är det enda sättet att bootstrapa Linux från ARC-konsollen. " -#~ "MILO är plattformsspecifik (olika MILO behövs för varje systemtyp) och existerar för de systemen, för " -#~ "vilka ARC-stöd visas i tabellen ovan.. Se även (tyvärr föråldrad) MILO HOWTO." +#. Tag: para +#: boot-installer.xml:2561 +#, 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 "" +"För de som inte känner till hur Macintosh-disketter hanteras: en diskett som " +"placeras i maskinen före uppstart kommer att vara första prioritet för " +"systemet att starta upp från. En diskett utan ett giltigt uppstartssystem " +"kommer att matas ut, och maskinen kommer sedan att leta efter startbara " +"hårddiskpartitioner." + +#. Tag: para +#: boot-installer.xml:2568 +#, no-c-format +msgid "" +"After booting, the root.bin 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 "" +"Efter uppstart kommer disketten root.bin att begäras. " +"Mata in rotdisketten och tryck &enterkey;. Installeringsprogrammet startas " +"automatiskt efter att rotsystemet har lästs in i minnet." + +#. Tag: title +#: boot-installer.xml:2579 +#, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "Uppstartsparametrar för PowerPC" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 " +"video=atyfb:vmode:6 , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"video=aty128fb:vmode:6 ." +msgstr "" +"Många äldre Apple-skärmar använde läget 640x480 67Hz. Om din bild verkar " +"vara sned på en äldre Apple-skärm, prova att lägga till uppstartsargumentet " +"video=atyfb:vmode:6 , som kommer att välja det läget " +"för de flesta Mach64- och Rage-grafikmaskinvara. För Rage 128-maskinvara, " +"skall video=aty128fb:vmode:6 användas." + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see ). Use " +"the command boot net to boot from a TFTP and RARP " +"server, or try boot net:bootp or boot net:" +"dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " +"OpenBoot revisions require using the device name, such as boot le" +"(); these probably don't support BOOTP nor DHCP." +msgstr "" +"På maskiner med OpenBoot, gå helt enkelt in i uppstartsmonitorn på maskinen " +"som ska installeras (ee ). Använd " +"kommandot boot net för att starta upp från en TFTP- " +"och RARP-server, eller prova boot net:bootp eller " +"boot net:dhcp för att starta upp från en TFTP och " +"BOOTP eller DHCP-server. Vissa äldre OpenBoot-revisioner kräver att man " +"använder enhetsnamnet, såsom boot le(); de har " +"antagligen inte stöd för BOOTP eller DHCP." + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "" +"Most OpenBoot versions support the boot cdrom 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 "" +"De flesta OpenBoot-versioner stöder kommandot boot cdrom som helt enkelt är ett alias för att starta upp från SCSI-enheten " +"på ID 6 (eller sekundär master för IDE-baserade system). Du kanske måste " +"använda det faktiska enhetsnamnet för äldre OpenBoot-versioner som inte har " +"stöd för det här speciella kommandot. Observera att vissa problem har " +"rapporterats på Sun4m-system (alltså Sparc 10 och Sparc 20) vid uppstart " +"från cd-rom." + +#. Tag: para +#: boot-installer.xml:2691 +#, no-c-format +msgid "" +"To boot from floppy on a Sparc, use \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"Bad magic number in disk label - Can't open disk label " +"package. 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 "" +"För att starta upp från en diskett på en Sparc, använd " +"\n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Tänk på att nyare Sun4u-arkitekturen (ultra) " +"inte har stöd för uppstart på diskett. Ett typiskt felmeddelande är " +"Bad magic number in disk label - Can't open disk label " +"package. Vidare stöder inte ett antal Sun4c-modeller (såsom " +"IPX) komprimerade avbilder som finns på disketter." + +#. Tag: para +#: boot-installer.xml:2703 +#, 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 ." +msgstr "" +"Ett flertal Sparc (exempelvis Ultra 10) har ett OBP-fel som förhindrar dem " +"från att starta upp (istället för att inte stöda uppstart alls). Den " +"lämpliga uppdateringen för OBP kan hämtas som produkt-id 106121 från ." + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"If you are booting from the floppy, and you see messages such as " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" then it is possible that floppy booting is " +"simply not supported on your machine." +msgstr "" +"Om du startar upp från disketten, och du ser meddelanden såsom " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" är det möjligt att uppstart via diskett inte " +"stöds på din maskin." + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "IDPROM-meddelanden" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"IDPROM, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"Sun NVRAM FAQ for more " +"information." +msgstr "" +"Om du inte kan starta upp på grund av att får meddelanden om ett problem med " +"IDPROM, är det möjligt att ditt NVRAM-batteri, som " +"tillhandahåller konfigurationsinformation för ditt firmware, har slut på " +"ström. Se Sun NVRAM FAQ för mer " +"information." + +#. Tag: para +#: boot-installer.xml:2742 +#, 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 "" +"Uppstartsparametrar är parametrar för Linux-kärnan som generellt sett " +"används för att se till att kringutrustning hanteras korrekt. För det mesta " +"kan kärnan automatiskt identifiera information om din kringutrustning. Dock, " +"i vissa fall, behöver du hjälpa kärnan en bit på vägen." + +#. Tag: para +#: boot-installer.xml:2749 +#, 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 "" +"Om det här är första gången du startar upp systemet kan du prova de " +"uppstartsparametrar som är standard (alltså, ställ inte in några parametrar) " +"och se om det fungerar korrekt. Det kommer säkert att göra det. Om inte, kan " +"du starta om senare och leta efter några speciella parametrar som informerar " +"systemet om din maskinvara." + +#. Tag: para +#: boot-installer.xml:2756 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +"Information om många uppstartsparametrar kan hittas i Linux BootPrompt HOWTO, " +"inklusive tips för obskyr maskinvara. Det här avsnittet innehåller endast en " +"del av de mest vanliga parametrarna. Vissa vanliga problem finns beskrivna i " +"." + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" +"When the kernel boots, a message \n" +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total 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 mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" +"När kärnan startar upp bör meddelandet\n" +"Memory:tillgängligtk/totaltk available\n" +" visas tidigt i processen. totalt bör stämma med totalt RAM-minne i kilobyte. Om det inte stämmer " +"med den faktiska mängden RAM-minne du har installerad behöver du använda " +"parametern mem=ram, där " +"ram är inställd till mängden minne och ändelsen " +"k för kilobyte eller m för megabyte. Till " +"exempel, både mem=65536k och mem=64m betyder 64MB RAM-minne." + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this (although not on DECstations). 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 console=device " +"argument to the kernel, where device is your " +"serial device, which is usually something like ttyS0." +msgstr "" +"Om du startar upp på en seriekonsoll kommer generellt sett kärnan att " +"autodetektera det (dock inte på DECstation). Om du har ett grafikkort (framebuffer) och ett tangentbord anslutet " +"till datorn som du önskar starta upp via seriekonsoll, kan du skicka med " +"följande argument console=enhet till kärnan, där enhet är din " +"serieenhet, som vanligtvis är något liknande ttyS0." + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"För &arch-title; heter serieenheterna ttya eller " +"ttyb. Alternativt, ställ in OpenPROM-variablerna " +"input-device och output-device till " +"ttya." + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "Parametrar för Debian Installer" + +#. Tag: para +#: boot-installer.xml:2806 +#, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"Installationssystemet känner igen ytterligare ett antal " +"uppstartsparametrar Med aktuella kärnor (2.6.9 eller " +"senare) kan du använda 32 kommandoradsflaggor och 32 miljöflaggor. Om dessa " +"tal överstigs, kommer kärnan att få panik. som kan vara " +"användbara." + +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "debconf/priority" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"Den här parametern ställer in så att meddelanden med lägst prioritet visas. " +"Kort form: priority" -#~ msgid "" -#~ "aboot is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " -#~ "aboot." -#~ msgstr "" -#~ "aboot är en liten, plattformsoberoende starthanterare, " -#~ "som endast körs från SRM. Se (även den föråldrad) SRM HOWTO för mer information om aboot." +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "" +"The default installation uses priority=high. 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 "" +"Standardinstallationen använder priority=high. Det " +"betyder att både meddelanden med prioriteterna hög och kritisk visas, men " +"meddelanden med prioriteterna medium och låg hoppas över. Om problem " +"påträffas justerar installeraren prioriteten efter behov." + +#. Tag: para +#: boot-installer.xml:2836 +#, no-c-format +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"Om du lägger till priority=medium som " +"uppstartsparameter kommer du att få se installationsmenyn och få mer " +"kontroll över installationen. När priority=low " +"används kommer alla meddelanden visas (det här är likvärdigt med " +"uppstartsmetoden expert). Med " +"priority=critical kommer installationssystemet endast " +"att visa kritiska meddelanden och försöka göra det rätta utan att krångla " +"till det." + +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "DEBIAN_FRONTEND" + +#. Tag: para +#: boot-installer.xml:2851 +#, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " +" The default frontend is " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text may be preferable for serial " +"console installs. Generally only the newt frontend is " +"available on default install media. On architectures which support it, the " +"graphical installer uses the gtk frontend." +msgstr "" +"Den här uppstartsparametern kontrollerar den typ av användargränssnitt som " +"används för installeraren. De för närvarande möjliga parametervärdena är: " +" DEBIAN_FRONTEND=noninteractive " +"DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " +" DEBIAN_FRONTEND=gtk Standardgränssnitt är " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text kanske föredras för " +"installationer via seriekonsoll. Generellt sett är endast gränssnittet " +"newt tillgängligt på standardinstallationsmediet. På " +"arkitekturer som har stöd för det använder den grafiska installeraren " +"gtk." + +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "BOOT_DEBUG" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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 "" +"Ställ in den här uppstartsparametern till 2 innebär att installerarens " +"uppstartsprocess kommer att loggas på ett informativt sätt. Ställ in den " +"till 3 och felsökningsloggar blir tillgängliga på strategiska punkter i " +"uppstartsprocessen. (Avsluta skalen för att fortsätta uppstartsprocessen.)" + +#. Tag: userinput +#: boot-installer.xml:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "BOOT_DEBUG=0" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "Det här är standardinställningen." + +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "BOOT_DEBUG=1" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "Mer information än normalt." + +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "BOOT_DEBUG=2" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "Mycket felsökningsinformation." + +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "BOOT_DEBUG=3" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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 "" +"Skal kommer att köras på olika punkter i uppstartsprocessen för detaljerad " +"felsökning. Avsluta skalet för att fortsätta uppstarten." + +#. Tag: term +#: boot-installer.xml:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "INSTALL_MEDIA_DEV" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"Värdet för parametern är sökvägen till enheten som Debian Installer ska " +"läsas in från. Till exempel, INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ msgid "" -#~ "Thus, three scenarios are generally possible, depending on the system's " -#~ "console firmware and whether or not MILO is available: " -#~ "\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Because MILO 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 aboot on new " -#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -#~ msgstr "" -#~ "Därav är tre scenarion generellt sett möjliga, beroende på systemets " -#~ "konsollfirmware och huruvida MILO finns tillgänglig " -#~ "eller inte: \n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Därför att MILO inte finns " -#~ "tillgänglig för någon av de Alpha-system som för närvarande produceras " -#~ "(från och med februari 2000), och på grund av att det inte längre är " -#~ "nödvändigt att köpa en licens för OpenVMS eller Tru64 Unix för att få SRM-" -#~ "firmware på din äldre Alpha, rekommenderas det att du använder SRM och " -#~ "aboot på nyare installationer av GNU/Linux, om inte du " -#~ "önskar att även starta upp med Windows NT." +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." +msgstr "" +"Startdisketten, som normalt sett söker av alla disketter den kan hitta efter " +"rotdisketten, kan åsidosättas av den här parametern för att endast söka på " +"en enhet." -#~ msgid "" -#~ "The majority of AlphaServers and all current server and workstation " -#~ "products contain both SRM and AlphaBIOS in their firmware. For " -#~ "half-flash 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 arc command). " -#~ "For the reasons mentioned above, we recommend switching to SRM before " -#~ "installing &debian;." -#~ msgstr "" -#~ "Majoriteten av de AlphaServer-modeller och alla nuvarande server- och " -#~ "arbetsstationsprodukter innehåller både SRM och AlphaBIOS i sina " -#~ "firmware. För half-flash-maskiner såsom de olika " -#~ "evalueringskorten, är det möjligt att byta från en version till en annan " -#~ "genom att skriva om firmware. När SRM har installerats, är det möjligt " -#~ "att köra ARC/AlphaBIOS från en diskett (med kommandot arc). Med anledningarna nämnda ovan, rekommenderar vi ett byte till " -#~ "SRM före installation av &debian;." +#. Tag: term +#: boot-installer.xml:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "debian-installer/framebuffer" -#~ msgid "" -#~ "As on other architectures, you should install the newest available " -#~ "revision of the firmware Except on Jensen, where Linux " -#~ "is not supported on firmware versions newer than 1.7 — see for more information. before installing &debian;. For Alpha, firmware updates can be " -#~ "obtained from Alpha Firmware Updates." -#~ msgstr "" -#~ "Som på andra arkitekturer, bör du installera de senaste tillgängliga " -#~ "revisionen av firmware Utom på Jensen, där Linux inte " -#~ "stöds på firmware-versioner senare än 1.7 — se för mer information. före " -#~ "installation av &debian;. För Alpha, uppdateringar av firmware kan hämtas " -#~ "från Alpha Firmware Updates." +# Framebuffer. Bättre ord! +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/" +"framebuffer=false, or fb=false for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." +msgstr "" +"Vissa arkitekturer använder kärnans framebuffer för att erbjuda en " +"installation på ett antal olika språk. Om framebuffer orsakar ett problem på " +"ditt system kan du inaktivera funktionen genom parametern debian-" +"installer/framebuffer=false eller fb=false i kort form. Symptom på problemet är felmeddelanden om bterm " +"eller bogl, en blank skärm, eller en frysning inom ett par minuter efter " +"påbörjad installation." + +#. Tag: para +#: boot-installer.xml:2948 +#, no-c-format +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"Argumentet video=vga16:off kan också användas för att " +"inaktivera kärnans användning av framebuffer. Sådana problem har " +"rapporterats på en Dell Inspiron med Mobile Radeon-kort." + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "Liknande problem har rapporterats för Amiga 1200 och SE/30." + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "Liknande problem har blivit rapporterats för hppa." + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"disabled by default 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 debian-installer/" +"framebuffer=true or fb=true for short." +msgstr "" +"På grund av displayproblem på vissa system är stöd för framebuffer " +"inaktiverat som standard för &arch-title;. Det kan " +"resultera i en mindre vacker display på system som korrekt sett har stöd för " +"framebuffer, såsom de med ATI-grafikkort. Om du upplever displayproblem i " +"installeraren kan du försöka att starta upp med parametern debian-" +"installer/framebuffer=true eller fb=true." + +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a dark theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter debian-installer/theme=dark or theme=dark." +msgstr "" +"Ett tema bestämmer hur användargränssnittet för installeraren ser ut " +"(färger, ikoner, etc). Vilka teman som finns tillgängliga beror på " +"gränssnittet. För närvarande har endast gränssnitten newt och gtk ett " +"mörkt tema som blev designat för användare med nedsatt syn. " +"Ställ in temat genom att starta upp med parametern debian-" +"installer/theme=dark eller " +"theme=dark." + +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "debian-installer/probe/usb" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "" +"Ställ in till false för att förhindra sökning efter " +"USB vid uppstart, om det orsakar problem." + +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "netcfg/disable_dhcp" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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 "" +"Som standard söker &d-i; automatiskt efter nätverkskonfiguration via DHCP. " +"Om sökningen lyckas, har du ingen chans att granska och ändra de mottagna " +"inställningarna. Du kan komma åt de manuellt inställningarna endast om DHCP-" +"sökningen misslyckas." + +#. Tag: para +#: boot-installer.xml:3008 +#, 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 " +"netcfg/disable_dhcp=true to prevent configuring the " +"network with DHCP and to enter the information manually." +msgstr "" +"Om du har en DHCP-server på ditt lokala nätverk men du vill undvika den på " +"grund av att den, exempelvis ger fel svar, kan du använda parametern " +"netcfg/disable_dhcp=true för att förhindra att " +"nätverket konfigureras med DHCP och att informationen matas in manuellt." + +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "hw-detect/start_pcmcia" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"Ställ in till false för att förhindra att PCMCIA-" +"tjänster startas, om det orsakar problem. Vissa bärbara datorer är kända för " +"det här problemet." + +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "preseed/url" + +#. Tag: para +#: boot-installer.xml:3031 +#, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url." +msgstr "" +"Ange url:en till en förkonfigurationsfil att hämta ner och användas för att " +"automatisera installationen. Se . Kort " +"form: url." + +#. Tag: term +#: boot-installer.xml:3041 +#, no-c-format +msgid "preseed/file" +msgstr "preseed/file" + +#. Tag: para +#: boot-installer.xml:3042 +#, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file." +msgstr "" +"Ange sökvägen till den förkonfigurationsfil som ska läsas in för att " +"automatisera installationen. Se . Kort " +"form: file." + +#. Tag: term +#: boot-installer.xml:3052 +#, no-c-format +msgid "auto-install/enabled" +msgstr "auto-install/enabled" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" +"Fördröj frågor som vanligtvis frågas innan förinställning är möjlig efter " +"att nätverket har konfigurerats. Kort form: auto=true " +"Se för detaljer om hur man använder det här " +"för att automatisera installationer." + +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "cdrom-detect/eject" + +#. Tag: para +#: boot-installer.xml:3065 +#, 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 "" +"Som standard, före omstart, matar &d-i; automatiskt ut det optiska mediat " +"som användes under installationen. Det kan vara onödigt om systemet inte " +"startar upp automatiskt på cd. I vissa fall kan det inte vara önskvärt, till " +"exempel om den optiska enheten inte kan mata in mediat själv om användaren " +"inte finns där för att göra det manuellt. Många cd-läsare kan inte mata in " +"media automatiskt." + +#. Tag: para +#: boot-installer.xml:3074 +#, no-c-format +msgid "" +"Set to false 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 "" +"Ställ in till false för att inaktivera automatisk " +"utmatning och tänk på att du kan behöva se till att systemet inte startar " +"upp automatiskt från den optiska enheten efter den initiala installationen." + +#. Tag: term +#: boot-installer.xml:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "ramdisk_size" + +#. Tag: para +#: boot-installer.xml:3086 +#, no-c-format +msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgstr "" +"Om du använder en 2.2.x-kärna, kan du behöva att ställa in &ramdisksize;." -#~ msgid "Booting with TFTP" -#~ msgstr "Uppstart via TFTP" +#. Tag: term +#: boot-installer.xml:3094 +#, no-c-format +msgid "mouse/left" +msgstr "mus/vänster" -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the ewa " -#~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " -#~ "\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" -#~ " You first need to set the boot protocol: " -#~ "\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Then check the medium type is correct: " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " You can get a listing of valid modes with " -#~ ">>>set ewa0_mode." -#~ msgstr "" -#~ "I SRM är Ethernet-gränssnitten namngivna med prefixet ewa, och kommer att listas i utskriften från kommandot " -#~ "show dev, som denna (delvis redigerat): " -#~ "\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" -#~ " Du behöver först ställa in " -#~ "uppstartsprotokollet: \n" -#~ ">>> set ewa0_protocol bootp\n" -#~ " Kontrollera sedan att mediatypen är korrekt: " -#~ "\n" -#~ ">>> set ewa0_mode läge\n" -#~ " Du kan få en lista på giltiga lägen med " -#~ ">>>set ewa0_mode." +#. Tag: para +#: boot-installer.xml:3095 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to true." +msgstr "" +"För gtk-gränssnittet (grafiska installeraren) kan användare byta musen till " +"vänsterhänt hantering genom att ställa in den här parametern till " +"true." + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "directfb/hw-accel" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"true when booting the installer." +msgstr "" +"Hårdvaruaccelerering för gtk-gränssnittet (grafiska installeraren) i " +"directfb är inaktiverat som standard. Ställ in den här parametern till " +"true när installeraren startar upp för att aktivera " +"det." + +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "rescue/enable" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"Ställ in till true för att gå in i räddningsläget " +"istället för att genomföra en normal installation. Se ." + +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "Använding av uppstartsparametrar för att besvara frågor" + +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" +"Med några undantag kan ett värde ställas in vid uppstartsprompten för valfri " +"fråga som ställs under installationen, även om det här bara är verkligen " +"användbart i specifika fall. Allmänna instruktioner om hur man kan göra det " +"här kan hittas i . Några specifika " +"exempel listas här nedan." + +#. Tag: term +#: boot-installer.xml:3140 +#, no-c-format +msgid "debian-installer/locale" +msgstr "debian-installer/locale" + +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. Short form: " +"locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" +"Kan användas för att ställa in både språket och landet för installationen. " +"Det här kommer endast att fungera om lokalen stöds i Debian. Kort form: " +"locale. Använd till exempel locale=sv_FI för att välja svenska som språk och Finland som land." + +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "" +"Set to true if you want to disable DHCP and instead " +"force static network configuration." +msgstr "" +"Ställ in till true om du vill inaktivera DHCP och " +"istället tvinga fram statisk nätverkskonfiguration." + +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "tasksel:tasksel/first" + +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" +"Kan användas för att välja funktionerna som inte finns tillgängliga från den " +"interaktiva funktionslistan, såsom funktionen kde-desktop. Se för ytterligare information. Kort " +"form: tasks." + +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "Skicka parametrar till kärnmoduler" + +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" +"Om drivrutiner är kompilerade in i kärnan kan du skicka parametrar till dem " +"som beskrivs i dokumentationen för kärnan. Dock om drivrutinerna är byggda " +"som moduler och därför att kärnmoduler läses in lite annorlunda under en " +"installation än vid uppstart av ett installerat system, är det inte möjligt " +"att skicka parametrar till moduler kan samma sätt som du normalt gör. " +"Istället behöver du använda en speciell syntax som känns igen av " +"installeraren som ser till att parametrarna sparas i de korrekta " +"konfigurationsfilerna och på så sätt kommer att användas när modulerna " +"faktiskt läses in. Parametrarna kommer även att propageras automatiskt till " +"konfigurationen för det installerade systemet." + +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" +"Observera att det är nuförtiden ganska ovanligt att parametrar behöver " +"skickas till moduler. I de flesta fall kommer kärnan att söka av befintlig " +"hårdvara i ett system och ställa in bra standardvärden på det sättet. Dock, " +"i vissa fall, kan det fortfarande krävas att parametrar ställs in manuellt." + +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" +"Syntaxen att använda för att ställa in parametrar för moduler är: " +"\n" +"modulnamn.parameternamn=värde\n" +" Om du behöver skicka flera parametrar till samma " +"eller olika moduler är det bara att upprepa detta. Till exempel, för att " +"ställa in ett gammalt 3Com-nätverkskort till att använda BNC-kontakten " +"(coax) och IRQ 10, skulle du skicka:" + +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "3c509.xcvr=3 3c509.irq=10" + +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "Felsök installationsprocessen" + +#. Tag: title +#: boot-installer.xml:3226 +#, no-c-format +msgid "CD-ROM Reliability" +msgstr "Tillförlitlighet för cd-rom" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" +"Ibland, speciellt med äldre cd-rom-enhet, kan installeraren misslyckas att " +"starta upp från en cd-skiva. Installeraren kan även — även efter en " +"lyckad uppstart från cd-skiva — misslyckas att känna igen cd-rom-" +"enheten eller svara med fel vid läsning från den under installationen." + +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" +"Det finns många olika möjliga orsaker till dessa problem. Vi kan endast " +"lista några vanliga problem och tillhandahålla allmänna förslag på hur man " +"hanterar dem. Resten är upp till dig." + +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "Det finns två mycket enkla saker som du bör prova först." + +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" +"Om cd-skivan inte startar upp, kontrollera att den blev inmatad korrekt och " +"att den inte är smutsig." -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "Sedan, för att starta upp från det första Ethernet-gränssnittet, kan du " -#~ "skriva: \n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " Det här kommer att starta upp med de " -#~ "kärnparametrar som är standard och som inkluderats i netboot-avbilden." +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" +"Om installeraren misslyckas att känna igen en cd-rom, prova att köra " +"alternativet Identifiera och montera cd-rom en andra gång. Vissa DMA-relaterade problem med " +"äldre cd-rom-enheter kan lösas på detta sätt." + +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" +"Om det inte fungerar, prova nedanstående förslag. De flesta, men inte alla, " +"förslag som diskuteras där gäller för både cd-rom och dvd, men vi använder " +"termen cd-rom för enkelhet." -#~ msgid "" -#~ "If you wish to use a serial console, you must pass " -#~ "the console= parameter to the kernel. This can be " -#~ "done using the -flags argument to the SRM " -#~ "boot command. The serial ports are named the same " -#~ "as their corresponding files in /dev. 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 " -#~ "ewa0 and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "Om du önskar att använda en seriekonsoll, måste du " -#~ "skicka med parametern console= till kärnan. Det " -#~ "kan göras med argumentet -flags till SRM-kommandot " -#~ "boot. Serieportarna har samma namn som sina " -#~ "motsvarande filer i /dev. När ytterligare " -#~ "kärnparametrar anges, måste du upprepa vissa standardalternativ som " -#~ "behövs av &d-i;-avbilderna. Till exempel, för att starta upp från " -#~ "ewa0 och använda en konsoll på första serieporten, " -#~ "skulle du skriva:" +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" +"Om du inte kan få installationen att fungera från cd-rom, prova en av de " +"andra installationsmetoderna som finns tillgängliga." + +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "Vanliga problem" + +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" +"Några äldre cd-rom-enheter saknar stöd för att läsa från skivor som blev " +"brända med höga hastigheter med en modern cd-brännare." -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" +"Om ditt system startar upp korrekt från cd-rom, betyder inte det alltid att " +"Linux även har stöd för cd-enheten (eller, mer korrekt, kontrollern som din " +"cd-rom-enhet är ansluten till)." -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "Uppstart från cd-rom med SRM-konsoll" +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" +"Några äldre cd-rom-enheter fungerar inte korrekt om direkt " +"minnesåtkomst (DMA) är aktiverat." + +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "Hur man undersöker och kanske även löser problem" + +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" +"Prova förslagen som listas här nedan om uppstart med cd-rom misslyckas." -#~ msgid "" -#~ "Type \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " where xxxx is your " -#~ "CD-ROM drive in SRM notation." -#~ msgstr "" -#~ "Ange \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " där xxxx är din cd-" -#~ "rom-enhet i SRM-notation." +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" +"Kontrollera att ditt BIOS faktiskt har stöd för uppstart från cd-rom (äldre " +"system har inte alltid det) och att din cd-rom-enhet har stöd för det media " +"som du använder." -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "Uppstart från cd-rom med ARC eller AlphaBIOS-konsoll" +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" +"Om du hämtat en iso-avbild, kontrollera att md5-kontrollsumman för avbilder " +"matchar den som listas för avbilden i filen MD5SUMS som " +"bör finnas på samma plats som där du hämtade avbilden från. " +"\n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Kontrollera sedan att md5-kontrollsumman för den " +"brända cd-skivan matchar också. Följande kommando bör fungera. Det använder " +"storleken på avbilden för att läsa det korrekta antalet byte från cd-skivan." + +#. Tag: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 poster in\n" +"262668+0 poster ut\n" +"134486016 bytes (134 MB) kopierade, 97.474 sekunder, 1.4 MB/s" + +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" +"Om, efter att installeraren har startat upp korrekt, identifieras inte cd-" +"rom-enheten, kan ibland ett nytt försök lösa problemet. Om du har fler än en " +"cd-rom-enhet, prova att byta cd-rom-enheten till den andra enheten. Om det " +"inte fungerar eller om cd-rom-enheten identifieras men det uppstod fel vid " +"läsningen från den, prova förslagen som listas nedan. Viss grundläggande " +"kunskap om Linux krävs för det här. För att köra något av kommandona, bör du " +"först växla till den andra virtuella konsollen (VT2) och aktivera skalet där." + +#. Tag: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" +"Växla till VT4 eller visa innehållet i /var/log/syslog " +"(använd nano som redigerare) för att leta efter specifika " +"felmeddelenden. Efter det, kontrollera även utskriften för dmesg." + +#. Tag: para +#: boot-installer.xml:3351 +#, no-c-format +msgid "" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using modprobe." +msgstr "" +"Se efter i utdatat från dmesg om din cd-rom-enhet " +"identifierades. Du bör se någonting som liknar (raderna behöver inte " +"nödvändigtvis vara lika): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" Om du inte ser någonting som liknar det här, är " +"chansen att kontrollern som din cd-rom är ansluten till, inte känns igen " +"eller inte stöds alls. Om du vet vilken drivrutin som behövs för " +"kontrollern, kan du prova att läsa in den manuellt med modprobe." + +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" +"Kontrollera att det finns en enhetsnod för din cd-rom-enhet under /" +"dev/. I ovanstående exempel skulle detta vara /dev/hdc. Det bör även finnas en /dev/cdroms/cdrom0." -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see ), then enter \\milo" -#~ "\\linload.exe as the boot loader and \\milo" -#~ "\\subarch (where " -#~ "subarch is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use \\milo\\ldmilo.exe as boot loader." -#~ msgstr "" -#~ "För att starta upp en cd-rom från ARC-konsollen, ta reda på kodnamnet för " -#~ "din underarkitektur (se ), och ange sedan " -#~ "\\milo\\linload.exe som starthanterare och " -#~ "\\milo\\underarkitektur (där " -#~ "underarkitektur är det korrekta namnet på " -#~ "underarkitekturen) som sökväg till operativsystemet i menyn \"OS " -#~ "Selection Setup\". Ett undantag för ägare av Ruffian-system: De måste " -#~ "använda \\milo\\ldmilo.exe som starthanterare." - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "Uppstart från startdisketter med SRM-konsoll" - -#~ msgid "" -#~ "At the SRM prompt (>>>), issue the following " -#~ "command: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possibly replacing dva0 " -#~ "with the actual device name. Usually, dva0 is the " -#~ "floppy; type \n" -#~ ">>> show dev\n" -#~ " to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, -" -#~ "flags argument is ignored, so you can just type boot " -#~ "dva0. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "På SRM-prompten (>>>), ange följande kommando: " -#~ "\n" -#~ ">>> boot dva0 -flags 0\n" -#~ " ersätt möjligen dva0 med " -#~ "det faktiska enhetsnamnet. Vanligtvis är dva0 " -#~ "diskettenheten; skriv \n" -#~ ">>> show dev\n" -#~ " för att se listan på enheter (alltså, om du " -#~ "vill starta upp från en cd). Observera att om du startar upp via MILO, " -#~ "ignoreras argumentet -flags, så du kan helt enkelt " -#~ "skriva boot dva0. Om allt fungerar som det ska kommer " -#~ "du till slut se Linux-kärnan starta upp." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for dva0, " -#~ "the Linux boot device name for fd0, and the desired " -#~ "kernel parameters for arguments." -#~ msgstr "" -#~ "Om du vill ange kärnparametrar vid uppstart med aboot, " -#~ "använd följande kommando: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (angivet på en rad), som ersätter, om " -#~ "nödvändigt, det faktiska namnet på uppstartsenheten i SRM för " -#~ "dva0, namnet för uppstartsenheten för Linux för " -#~ "fd0, och de önskade kärnparametrarna för " -#~ "arguments." - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " -#~ "See ." -#~ msgstr "" -#~ "Om du vill ange kärnparametrar vid uppstart med MILO, " -#~ "måste du avbryta bootstrap när du kommit in i MILO. Se ." - -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "Uppstart från startdisketter med ARC eller AlphaBIOS-konsoll" - -#~ msgid "" -#~ "In the OS Selection menu, set linload.exe as the boot " -#~ "loader, and milo as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "I valmenyn för operativsystem, ställ in linload.exe " -#~ "som starthanterare, och milo som \"OS Path\". Kör " -#~ "bootstrap med den nyligen skapade posten." - -#~ msgid "Booting with MILO" -#~ msgstr "Uppstart med MILO" - -#~ 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 "" -#~ "MILO som finns på bootstrap-mediumet är konfigurerad att automatiskt " -#~ "fortsätta direkt till Linux. Om du önskar att avbryta är allt du behöver " -#~ "göra att trycka på blanksteg under MILO-nedräkningen." - -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"Nếu bạn muốn xác định riêng mỗi thứ (v.d. để cung cấp tham số thêm), bạn có " +"thể dùng lệnh như đây:\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" -#~ " Nếu bạn khởi động từ vật chứa khác đĩa mềm, " -#~ "hãy thay thế fd0 trong lời thí dụ bên trên bằng tên " -#~ "thiết bị thích hợp bằng kiểu ghi Linux. Lệnh help (trợ " -#~ "giúp) sẽ cung cấp một tham chiếu lệnh MILO ngắn." - -#~ msgid "Booting from TFTP" -#~ msgstr "Khởi động từ TFTP" +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"Nhập fsn: rồi bấm phím " +"&enterkey; để chọn thiết bị có số hiệu phân vùng của đĩa CD-ROM là " +"n. Sau đó, trình bao sẽ hiển thị số hiệu phân " +"vùng như là dấu nhắc." + +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"Nhập elilo rồi bấm phím &enterkey;. Việc này sẽ bắt đầu " +"tiến trình tải khởi động." -#~ msgid "" -#~ "Booting from the network requires that you have a network connection and " -#~ "a TFTP network boot server (DHCP, RARP, or BOOTP)." -#~ msgstr "" -#~ "Việc khởi động từ mạng cần thiết bạn có sự kết nối mạng và máy phục vụ " -#~ "khởi động mạng kiểu TFTP (DHCP, RARP, hay BOOTP)." - -#~ msgid "" -#~ "Older systems such as the 715 might require the use of an RBOOT server " -#~ "instead of a BOOTP server." -#~ msgstr "" -#~ "Hệ thống cũ hơn như 715 có thể cần thiết bạn dùng máy phục vụ kiểu RBOOT " -#~ "thay cho BOOTP." - -#~ msgid "" -#~ "The installation method to support network booting is described in ." -#~ msgstr "" -#~ "Phương pháp cài đặt để hỗ trợ khả năng khởi động qua mạng được diễn tả " -#~ "trong ." - -#~ msgid "Booting from TFTP on Netwinder" -#~ msgstr "Khởi động từ TFTP trên Netwinder" - -#~ msgid "" -#~ "Netwinders have two network interfaces: A 10Mbps NE2000-compatible card " -#~ "(which is generally referred to as eth0) 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 interface (the " -#~ "one labeled with 10 Base-T)." -#~ msgstr "" -#~ "Máy Netwinder có hai giao diện mạng: một thẻ tương thích với NE2000 " -#~ "10Mbps (thường được gọi như là eth0) và một thẻ Tulip " -#~ "100Mbps. Có thể gặp khó khăn khi tải ảnh thông qua TFTP bằng thẻ 100Mbps, " -#~ "vì vậy khuyên bạn dùng giao diện 10Mbps (điều có nhãn 10 Base-T)." - -#~ 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 ." -#~ msgstr "" -#~ "Bạn cần thiết NeTTrom phiên bản 2.2.1 hay sau để khởi động hệ thống cài " -#~ "đặt: khuyên bạn dùng phiên bản 2.3.3. Tiếc là tập tin phần vững hiện thời " -#~ "không sẵn sàng để tải xuống do vấn đề bản quyền. Nếu trường hợp này thay " -#~ "đổi, bạn có thể tìm ảnh mới tại ." - -#~ 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: \n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Furthermore, you must configure the network, " -#~ "either with a static address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " where 24 is the number of set bits in the " -#~ "netmask, or a dynamic address: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " You may also need to configure the " -#~ "route1 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. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Now you have to tell the firmware that the " -#~ "TFTP image should be booted: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " If you use a serial console to install your " -#~ "Netwinder, you need to add the following setting: " -#~ "\n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Alternatively, for installations using a " -#~ "keyboard and monitor you have to set: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " You can use the printenv " -#~ "command to review your environment settings. After you have verified that " -#~ "the settings are correct, you can load the image: " -#~ "\n" -#~ " NeTTrom command-> boot\n" -#~ " In case you run into any problems, a detailed " -#~ "HOWTO is available." -#~ msgstr "" -#~ "Khi bạn khởi động máy Netwinder, bạn cần phải ngắt tiến trình khởi động " -#~ "trong khi đếm ngược. Việc ngắt này cho bạn khả năng đặt một số giá trị " -#~ "phần vững cần thiết để khởi động bộ cài đặt. Trước tiên, bạn hãy tải " -#~ "thiết lập mặc định\n" -#~ " NeTTrom command-> load-defaults\n" -#~ " Hơn nữa, bạn cần phải cấu hình mạng, hoặc " -#~ "bằng một địa chỉ tĩnh: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 flash\n" -#~ " NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" -#~ " mà 24 là số bit được đặt trong mặt nạ mạng, " -#~ "hoặc một địa chỉ động: \n" -#~ " NeTTrom command-> setenv netconfig_eth0 dhcp\n" -#~ " Bạn cũng có thể cần phải cấu hình thiết lập " -#~ "route1 nếu máy phục vụ TFTP không nằm trên mạng " -#~ "phụ cục bộ. Sau thiết lập này, bạn cần phải xác định máy phục vụ TFTP và " -#~ "vị trí của ảnh. Sau đó, bạn có thể lưu toàn bộ thiết lập vào bộ nhớ cực " -#~ "nhanh. \n" -#~ " NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" -#~ " NeTTrom command-> setenv kerntftpfile boot.img\n" -#~ " NeTTrom command-> save-all\n" -#~ " Sau đó, bạn cần phải báo phần vững khởi động " -#~ "ảnh TFTP: \n" -#~ " NeTTrom command-> setenv kernconfig tftp\n" -#~ " NeTTrom command-> setenv rootdev /dev/ram\n" -#~ " Nếu bạn dùng bàn điều khiển nối tiếp để cài " -#~ "đặt máy Netwinder, bạn cần phải thêm thiết lập này: " -#~ "\n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram " -#~ "console=ttyS0,115200\n" -#~ " Hoặc, dành cho bản cài đặt dùng bàn phím và " -#~ "bộ trình bày, bạn cần phải đặt: \n" -#~ " NeTTrom command-> setenv cmdappend root=/dev/ram\n" -#~ " Bạn có thể dùng lệnh printenv (in ra môi trường) để xem lại thiết lập môi trường. Một khi bạn " -#~ "thẩm tra thiết lập là đúng, bạn có thể tải ảnh: " -#~ "\n" -#~ " NeTTrom command-> boot\n" -#~ " Trong trường hợp gặp khó khăn, có sẵn một tài " -#~ "liệu Cách Làm chi tiết." - -#~ msgid "Booting from TFTP on CATS" -#~ msgstr "Khởi động từ TFTP trên CATS" - -#~ msgid "" -#~ "On CATS machines, use boot de0: or similar at the " -#~ "Cyclone prompt." -#~ msgstr "" -#~ "Trên máy CATS, hãy dùng lệnh boot de0: hay tương tự, " -#~ "tại dấu nhắc Cyclone." - -#~ msgid "Booting from CD-ROM" -#~ msgstr "Khởi động từ đĩa CD-ROM" - -#~ 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 configure your system for booting " -#~ "off a CD as described in , " -#~ "insert your CD, reboot, and proceed to the next chapter." -#~ msgstr "" -#~ "Phương pháp dễ nhất cho phần lớn người là sử dụng một bộ đĩa CD Debian. " -#~ "Nếu bạn có một bộ đĩa CD như vậy, và nếu máy của bạn có hỗ trợ khả năng " -#~ "khởi động trực tiếp từ đĩa CD, hay quá ! Đơn giản hãy cấu hình hệ thống để khởi động từ đĩa CD, như được diễn tả trong " -#~ ", nạp đĩa CD, khởi động lại, " -#~ "và tiếp tục lại đến chương kế tiếp." - -#~ 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 "" -#~ "Ghi chú rằng một số ổ đĩa CD riêng có thể cần thiết trình điều khiển đặc " -#~ "biệt, vì vậy không thể được truy cập trong giao đoạn cài đặt ở đầu. Nếu " -#~ "phương pháp chuẩn khởi động từ đĩa CD không thích hợp với phần cứng của " -#~ "bạn, hãy xem lại chương này và đọc về hạt nhân xen kẽ và phương pháp cài " -#~ "đặt có thể là thích hợp hơn." - -#~ 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 "" -#~ "Thậm chí nếu bạn không thể khởi động từ đĩa CD-ROM, bạn thường có thể cài " -#~ "đặt các thành phần của hệ thống Debian và các gói phần mềm đã muốn từ đĩa " -#~ "CD-ROM đó. Đơn giản hãy khởi động bằng một vật chứa khác, như đĩa mềm. " -#~ "Vào lúc nên cài đặt hệ điều hành, hệ thống cơ bản và gói phần mềm thêm " -#~ "nào, hãy chỉ hệ thống cài đặt tới ổ đĩa CD-ROM." - -#~ msgid "" -#~ "If you have problems booting, see ." -#~ msgstr "" -#~ "Nếu bạn gặp khó khăn trong việc khởi động, xem ." - -#~ msgid "" -#~ "To boot a CD-ROM from the Cyclone console prompt, use the command " -#~ "boot cd0:cats.bin" -#~ msgstr "" -#~ "Để khởi động đĩa CD-ROM từ dấu nhắc bàn điều khiển Cyclone, hãy dùng lệnh " -#~ "boot cd0:cats.bin." - -#~ msgid "Booting from Firmware" -#~ msgstr "Khởi động từ phần vững" - -#~ 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 "" -#~ "Có số tăng dần, những thiết bị người tiêu dùng mà khởi động trực tiếp từ " -#~ "phiến tinh thể cực nhanh trên thiết bị đó. Bộ cài đặt có thể được ghi vào " -#~ "cực nhanh, để khởi chạy tự động khi bạn khởi đông lại máy." - -#~ 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 "" -#~ "Trong nhiều trường hợp, việc thay đổi phần vững của thiết bị nhúng sẽ bãi " -#~ "bỏ bảo hành. Đôi khi bạn cũng không thể phục hồi thiết bị nếu gặp khó " -#~ "khăn trong việc chớp. Vì vậy, hãy cẩn thận và theo những bước một cách " -#~ "chính xác." - -#~ msgid "Booting the NSLU2" -#~ msgstr "Khởi động NSLU2" - -#~ msgid "There are three ways how to put the installer firmware into flash:" -#~ msgstr "Có ba phương pháp chèn phần vững cài đặt vào bộ nhớ cực nhanh:" - -#~ msgid "Using the NSLU2 web interface" -#~ msgstr "Dùng giao diện Mạng của NSLU2" - -#~ msgid "" -#~ "Go to the administration section and choose the menu item " -#~ "Upgrade. You can then browse your disk for the " -#~ "installer image you have previously downloaded. Then press the " -#~ "Start Upgrade button, confirm, wait for a few minutes " -#~ "and confirm again. The system will then boot straight into the installer." -#~ msgstr "" -#~ "Đi tới phần quản lý và chọn mục trình đơn Upgrade " -#~ "(Nâng cấp). Sau đó bạn có thể duyệt qua đĩa tìm ảnh cài đặt đã được tải " -#~ "về trước. Một khi tìm nó, hãy bấm cái nút Start Upgrade (bắt đầu nâng cấp), xác nhận, đợi vài phút rồi xác nhận lần nữa. " -#~ "Sau đó, hệ thống sẽ khởi động trực tiếp vào trình cài đặt." - -#~ msgid "Via the network using Linux/Unix" -#~ msgstr "Qua mạng bằng Linux/UNIX" - -#~ msgid "" -#~ "You can use upslug2 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: " -#~ " Disconnect any disks and/or devices from the USB ports. " -#~ " Power off the NSLU2 Press and hold the reset button (accessible " -#~ "through the small hole on the back just above the power input). Press and release the power button to power on " -#~ "the NSLU2. Wait for 10 seconds " -#~ "watching the ready/status LED. After 10 seconds it will change from amber " -#~ "to red. Immediately release the reset button. " -#~ " 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. See the NSLU2-Linux " -#~ "pages if you have problems with this. Once your NSLU2 is in " -#~ "upgrade mode, you can flash the new image: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " 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 "" -#~ "Bạn có thể dùng tiện ích upslug2 từ bất kỳ máy Linux " -#~ "hay UNIX nào, để nâng cấp máy qua mạng. Phần mềm này đã được đóng gói " -#~ "dành cho Debian. Trước hết, bạn cần phải đặt máy NSLU2 trong chế độ nâng " -#~ "cấp: Ngắt kết nối các đĩa và/hay thiết bị " -#~ "ra cổng USB. Tắt điện của máy NSLU2 Bấm giữ cái nút đặt lại (có thể truy " -#~ "cập nó qua lỗ nhỏ về sau hộp, đúng bên trên cổng điện vào). Trong khi giữ nút đặt lại, bấm rồi buông cái " -#~ "nút điện để mở điện của máy NSLU2. " -#~ "Tiếp tục giữ nút đặt lại, đợi 10 giây trong khi theo dõi LED (đèn nhỏ) " -#~ "sẵn sàng/trạng thái. Sau 10 giây, nó sẽ thay đổi từ màu vàng thành màu " -#~ "đỏ. Lúc đó, bạn hãy buông ngay cái nút đặt lại. " -#~ " Sau đó, đèn LED sẵn sàng/trạng thái của máy NSLU2 sẽ " -#~ "chớp xen kẽ màu đỏ/xanh lá cây (có sự trễ 1 giây trước nó trở thành màu " -#~ "xanh lá cây lần đầu tiên). Lúc đó, máy NSLU2 đã vào chế độ nâng cấp. Xem các trang NSLU2-Linux nếu " -#~ "bạn gặp khó khan trong tiến trình này. Một khi máy NSLU2 đã vào chế độ " -#~ "nâng cấp, bạn có thể chớp ảnh mới: \n" -#~ "sudo upslug2 -i di-nslu2.bin\n" -#~ " Ghi chú rằng công cụ này cũng hiển thị địa " -#~ "chỉ MAC của máy NSLU2 của bạn, thông tin có ích khi bạn cấu hình trình " -#~ "phục vụ DHCP. Sau khi toàn bộ ảnh đã được ghi và thẩm tra, hệ thống sẽ " -#~ "khởi động lại tự động. Hãy kiểm tra xem bạn đã kết nối lại đĩa USB, nếu " -#~ "không thì trình cài đặt không tìm thấy nó." - -#~ msgid "Via the network using Windows" -#~ msgstr "Qua mạng bằng Windows" - -#~ msgid "" -#~ "There is a tool for Windows to upgrade " -#~ "the firmware via the network." -#~ msgstr "" -#~ "Có một công cụ Windows để nâng cấp phần vững " -#~ "qua mạng." - -#~ msgid "Booting from a CD-ROM" -#~ msgstr "Khởi động từ đĩa CD-ROM" - -#~ msgid "" -#~ "Booting from Linux Using LILO or GRUB" -#~ msgstr "" -#~ "Khởi động từ Linux bằng LILO hay GRUB" - -#~ msgid "" -#~ "To boot the installer from hard disk, you must first download and place " -#~ "the needed files as described in ." -#~ msgstr "" -#~ "Để khởi động trình cài đặt từ đĩa cứng, trước tiên bạn cần phải tải về và " -#~ "để các tập tin cần thiết, như được diễn tả trong ." - -#, fuzzy -#~ msgid "" -#~ "If you intend to use the hard drive only for booting and then download " -#~ "everything over the network, you should download the netboot/" -#~ "debian-installer/i386/initrd.gz file and its corresponding " -#~ "kernel netboot/debian-installer/i386/linux. This " -#~ "will allow you to repartition the hard disk from which you boot the " -#~ "installer, although you should do so with care." -#~ msgstr "" -#~ "Nếu bạn định dùng đĩa cứng chỉ để khởi động, rồi tải về mọi thứ qua mạng, " -#~ "bạn nên tải về tập tin netboot/debian-installer/i386/initrd.gz và hạt nhân tương ứng. Nó sẽ cho bạn khả năng phân vùng lại đĩa " -#~ "cứng nơi bạn khởi động trình cài đặt, dù bạn nên làm như thế một cách cẩn " -#~ "thận." - -#~ msgid "" -#~ "Alternatively, if you intend to keep an existing partition on the hard " -#~ "drive unchanged during the install, you can download the hd-" -#~ "media/initrd.gz file and its kernel, as well as copy a CD iso " -#~ "to the drive (make sure the file is named ending in .iso). The installer can then boot from the drive and install from " -#~ "the CD image, without needing the network." -#~ msgstr "" -#~ "Hoặc, nếu bạn định bao tồn một phân vùng đã có trên đĩa cứng, không thay " -#~ "đổi nó trong khi cài đặt, bạn có thể tải về tập tin hd-media/" -#~ "initrd.gz và hạt nhân tương ứng, cũng sao chép ảnh ISO đĩa CD " -#~ "vào ổ đĩa (kiểm tra xem tập tin có tên kết thúc bằng .iso). Sau đó, trình cài đặt có thể khởi động từ ổ đĩa đó, cũng cài " -#~ "đặt từ ảnh đĩa CD, không cần chạy mạng." - -#~ msgid "" -#~ "For LILO, you will need to configure two essential " -#~ "things in /etc/lilo.conf: " -#~ " to load the initrd.gz installer at " -#~ "boot time; have the " -#~ "vmlinuz kernel use a RAM disk as its root partition. " -#~ " Here is a /etc/lilo.conf example:" -#~ msgstr "" -#~ "Đối với LILO, bạn sẽ cần phải cấu hình hai thứ chủ yếu " -#~ "trong tập tin /etc/lilo.conf: " -#~ " để tải trình cài đặt initrd.gz vào " -#~ "lúc khởi động; làm cho hạt nhân " -#~ "vmlinuz dùng đĩa RAM như là phân vùng gốc. Đây là một lời thí dụ /etc/lilo.conf:" - -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" -#~ msgstr "" -#~ "image=/boot/newinstall/vmlinuz\n" -#~ " label=newinstall\n" -#~ " initrd=/boot/newinstall/initrd.gz\n" -#~ " root=/dev/ram0\n" -#~ " append=\"ramdisk_size=12000\"" - -#~ msgid "" -#~ "For more details, refer to the initrd 4 and " -#~ "lilo.conf 5 man pages. Now run lilo " -#~ "and reboot." -#~ msgstr "" -#~ "Để tìm chi tiết, xem trang hướng dẫn (man) " -#~ "initrd 4 và lilo.conf 5. Bây giờ hãy chạy " -#~ "lilo rồi khởi động lại." - -#~ msgid "" -#~ "The procedure for GRUB is quite similar. Locate your " -#~ "menu.lst in the /boot/grub/ " -#~ "directory (sometimes in the /boot/boot/grub/), add " -#~ "the following lines: \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" -#~ " and reboot." -#~ msgstr "" -#~ "Thủ tục đối với GRUB là hơi tương tự. Hãy tìm tập tin " -#~ "menu.lst nằm trong thư mục /boot/grub/ (đôi khi nằm trong thư mục /boot/boot/grub/), và thêm những dòng này: \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" -#~ " rồi khởi động lại." - -#~ msgid "" -#~ "Note that the value of the ramdisk_size may need " -#~ "to be adjusted for the size of the initrd image. From here on, there " -#~ "should be no difference between GRUB or LILO." -#~ msgstr "" -#~ "Ghi chú rằng giá trị của ramdisk_size (kích cỡ của " -#~ "đĩa RAM) có lẽ cần phải được điều chỉnh để thích hợp với ảnh initrd. Kể " -#~ "từ điểm này, không nên có sự khác nhau giữa tiến trình GRUB và LILO." - -#~ msgid "Booting from USB Memory Stick" -#~ msgstr "Khởi động từ thanh bộ nhớ USB" - -#~ msgid "" -#~ "Let's assume you have prepared everything from and . 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 boot: prompt. Here you can enter optional boot arguments, or just hit " -#~ "&enterkey;." -#~ msgstr "" -#~ "Giả sử bạn đã chuẩn bị mọi thứ được diễn tả trong và . Sau đó, hãy cầm " -#~ "thanh USB vào cổng USB còn rảnh nào, và khởi động lại máy tính. Hệ thống " -#~ "nên khởi động được, và bạn nên thấy dấu nhắc boot:. Vào " -#~ "đó bạn có thể nhập các đối số khởi động tùy chọn, hoặc chỉ bấm phím " -#~ "&enterkey;." - -#~ msgid "Booting from Floppies" -#~ msgstr "Khởi động từ đĩa mềm" - -#~ msgid "" -#~ "You will have already downloaded the floppy images you needed and created " -#~ "floppies from the images in ." -#~ msgstr "" -#~ "Trong bước , bạn đã tải về các ảnh đĩa " -#~ "mềm cần thiết và tạo đĩa mềm từ ảnh đó." - -#~ 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 "" -#~ "Để khởi động từ đĩa mềm khởi động trình cài đặt, hãy nạp nó vào ổ đĩa mềm " -#~ "chính, tắt hệ thống một cách bình thường, rồi mở nó lần nữa." - -#~ 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 root= 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 linux root=/dev/hdc at the " -#~ "boot prompt." -#~ msgstr "" -#~ "Để cài đặt từ ổ đĩa kiểu LS-120 (phiên bản ATAPI) với một bộ đĩa mềm, bạn " -#~ "cần phải xác định vị trí ảo cho thiết bị đĩa mềm. Việc này được làm bằng " -#~ "đối số root=, mà cung cấp tên thiết bị tới đó trình " -#~ "điều khiển ide-floppy (đĩa mềm IDE) ánh xạ thiết bị. Lấy thí dụ, nếu ổ " -#~ "đĩa LS-120 của bạn được kết nối như là thiết bị IDE thứ nhất (chủ) qua " -#~ "cáp thứ hai, bạn hãy nhập lệnh linux root=/dev/hdc " -#~ "ở dấu nhắc khởi động." - -#~ msgid "" -#~ "Note that on some machines, Control " -#~ "Alt Delete does not properly " -#~ "reset the machine, so a hard 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 "" -#~ "Ghi chú rằng trên một số máy nào đó, tổ hợp phím " -#~ "Control Alt Delete không phải đặt lại được máy tính, vậy khuyên bạn khởi " -#~ "động lại một cách cứng. Nếu bạn cài đặt từ một hệ điều " -#~ "hành đã có (v.d. từ một hộp DOS nào đó), bạn không thể chọn khác. Nếu " -#~ "không, hãy khởi động lại cứng khi khởi động máy." - -#~ msgid "" -#~ "The floppy disk will be accessed, and you should then see a screen that " -#~ "introduces the boot floppy and ends with the boot: " -#~ "prompt." -#~ msgstr "" -#~ "Lúc đó, đĩa mềm sẽ được truy cập, vậy bạn nên thấy màn hình giới thiệu " -#~ "đĩa mềm khởi động mà kết thúc bằng dấu nhắc khởi động boot:." - -#~ msgid "" -#~ "Once you press &enterkey;, you should see the message " -#~ "Loading..., followed by " -#~ "Uncompressing Linux..., 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 ." -#~ msgstr "" -#~ "Một khi bạn bấm phím &enterkey;, bạn nên thấy thông điệp " -#~ "Loading... (Đang tải...), với đoạn " -#~ "Uncompressing Linux... (Đang giải nén " -#~ "Linux) theo sau, rồi một màn hình đầy chứa thông tin về phần cứng của hệ " -#~ "thống đó. Thông tin thêm về giải đoạn này của tiến trình khởi động nằm " -#~ "bên dưới trong ." - -#~ 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 debian-installer is " -#~ "automatically launched." -#~ msgstr "" -#~ "Sau khi khởi động từ đĩa mềm khởi động, đĩa mềm gốc được yêu cầu. Hãy nạp " -#~ "đĩa mềm gốc rồi bấm phím &enterkey;, vậy nội dung của nó được tải vào bộ " -#~ "nhớ. Chương trình cài đặt debian-installer được khởi " -#~ "chạy tự động." - -#~ msgid "There are various ways to do a TFTP boot on i386." -#~ msgstr "Có vài cách khác nhau để khởi động qua TFTP trên i386." - -#~ msgid "NIC or Motherboard that support PXE" -#~ msgstr "NIC hay bo mạch chủ có hỗ trợ PXE" - -#~ msgid "" -#~ "It could be that your Network Interface Card or Motherboard provides PXE " -#~ "boot functionality. This is a Intel re-implementation of TFTP boot. If so you may be able to " -#~ "configure your BIOS to boot from the network." -#~ msgstr "" -#~ "Có lẽ thẻ giao diện mạng (NIC) hay bo mạch chủ của bạn cung cấp chức năng " -#~ "khởi động kiểu PXE. Nó là cách thực hiện lại chức năng khởi động qua TFTP " -#~ "của công ty Intel. Nếu máy bạn có " -#~ "chức năng này, có lẽ bạn có khả năng cấu hình BIOS để khởi động qua mạng." - -#~ msgid "NIC with Network BootROM" -#~ msgstr "NIC với BootROM mạng" - -#~ msgid "" -#~ "It could be that your Network Interface Card provides TFTP boot " -#~ "functionality." -#~ msgstr "" -#~ "Có lẽ thẻ giao diện mạng (NIC) của bạn cung cấp chức năng khởi động qua " -#~ "TFTP." - -#~ msgid "" -#~ "Let us (&email-debian-boot-list;) know how did you manage " -#~ "it. Please refer to this document." -#~ msgstr "" -#~ "Vui lòng cho chúng tôi (&email-debian-boot-list;) biết về " -#~ "phương pháp do bạn dùng, cũng tham khảo tài liệu này." - -# Name: don't translate / Tên: đừng dịch -#~ msgid "Etherboot" -#~ msgstr "Etherboot" - -#~ msgid "" -#~ "The etherboot project " -#~ "provides bootdiskettes and even bootroms that do a TFTPboot." -#~ msgstr "" -#~ "Dự án Etherboot cung cấp " -#~ "đĩa mềm khởi động, ngay cả bộ nhớ ROM khởi động, mà khởi động được qua " -#~ "TFTP." - -#~ msgid "The Boot Prompt" -#~ msgstr "Dấu nhắc khởi động" - -# Don't translate the screen example text / Đừng dịch đoạn mẫu màn hình -#~ msgid "" -#~ "When the installer boots, you should be presented with a friendly " -#~ "graphical screen showing the Debian logo and the boot prompt: " -#~ "\n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " 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 "" -#~ "Khi trình cài đặt khởi động, bạn nên thấy màn hình đồ họa thân thiện hiển " -#~ "thị biểu hình Debian và dấu nhắc khởi động:\n" -#~ "Press F1 for help, or ENTER to boot:\n" -#~ " (Hãy bấm phím chức năng F1 để xem trợ giúp, " -#~ "hay bấm phím ENTER để khởi động:) Tại dấu nhắc khởi động, bạn có thể hoặc " -#~ "bấm phím &enterkey; để khởi động trình cài đặt với các tùy chọn mặc định, " -#~ "hoặc nhập một phương pháp khởi động riêng với (tùy chọn) một số tham số " -#~ "khởi động." - -#~ msgid "" -#~ "Information on available boot methods and on boot parameters which might " -#~ "be useful can be found by pressing F2 through " -#~ "F8. If you add any parameters to the boot command line, " -#~ "be sure to type the boot method (the default is linux) and a space before the first parameter (e.g., " -#~ "linux fb=false)." -#~ msgstr "" -#~ "Thông tin về các phương pháp khởi động sẵn sàng, cũng về các tham số khởi " -#~ "động có ích sẽ được hiển thị khi bạn bấm phím chức năng nằm trong phạm vị " -#~ "F2 đến F8. Nếu bạn thêm tham số nào vào " -#~ "dòng lệnh khởi động, hãy kiểm tra xem bạn đã gõ phương pháp khởi động " -#~ "(mặc định là linux) và một dấu cách trước khi nhập " -#~ "tham số thứ nhất (v.d., linux fb=false)." - -#~ 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 integrated Lights Out (iLO) and HP's " -#~ "Integrated Remote Assistant (IRA). You can blindly press " -#~ "F1 In some cases these devices will require special " -#~ "escape sequences to enact this keypress, for example the IRA uses " -#~ " Ctrl F , " -#~ "1. 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 fb=false to the boot " -#~ "prompt, as described in the help text." -#~ msgstr "" -#~ "Nếu bạn cài đặt hệ thống thông qua một thiết bị quản lý từ xa mà cung cấp " -#~ "giao diện kiểu chữ với bàn điều khiển VGA, có lẽ bạn không thể thấy màn " -#~ "hình đồ họa giật gân ban đầu khi khởi động trình cài đặt; có lẽ bạn ngay " -#~ "cả không thấy dấu nhắc khởi động. Những thiết bị quản lý từ xa này gồm " -#~ "bàn điều khiển kiểu chữ của integrated Lights Out (iLO) " -#~ "của công ty Compaq, và Integrated Remote Assistant (IRA) " -#~ "của HP. Bạn có thể bấm phím chức năng F1 Trong một số " -#~ "trường hợp, những thiết bị này cần thiết bạn gõ dãy phím thoát đặc biệt " -#~ "để thực hiện việc bấm phím này, v.d. IRA sử dụng Ctrl F , 1. " -#~ " để đi vòng màn hình này và xem đoạn trợ giúp. Một khi bạn đã " -#~ "qua màn hình giật gân và tới đoạn trợ giúp, các cú bấm phím sẽ được phản " -#~ "hồi tại dấu nhắc như bình thường. Để ngăn cản trình cài đặt sử dụng bộ " -#~ "đệm khung trong phần còn lại của tiến trình cài đặt, bạn cũng cần phải " -#~ "thêm mục fb=false vào dấu nhắc khởi đông, như được " -#~ "diễn tả trong đoạn trợ giúp." - -#~ msgid "CD Contents" -#~ msgstr "Nội dung đĩa CD" - -#~ msgid "" -#~ "There are three basic variations of Debian Install CDs. The " -#~ "Business Card 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 Network Install 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 "" -#~ "Có ba kiểu khác nhau của đĩa CD cài đặt Debian. Đĩa CD Thẻ kinh " -#~ "doanh (Business Card) chứa bản cài đặt tối thiểu sẽ vừa được " -#~ "trên vật chứa kiểu đĩa CD thích hợp với kích cỡ thiết bị nhỏ. Nó cần " -#~ "thiết sự kết nối đến mạng để cài đặt phần còn lại của bản cài đặt cơ sở, " -#~ "xây dựng hệ thống có ích. Đĩa CD Cài đặt qua mạng " -#~ "(Network Install) chứa tất cả các gói cấu thành bản cài đặt cơ sở, còn " -#~ "cần thiết sự kết nối mạng đến máy nhân bản Debian để cài đặt các gói thêm " -#~ "cần thiết để xây dựng hệ thống hoàn toàn. Bộ đĩa CD Debian có khả năng " -#~ "cài đặt hệ thống hoàn toàn từ phạm vị gói rộng, không cần truy cập mạng " -#~ "nào." - -#~ 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 "" -#~ "Kiến trúc IA-64 dùng giao diện phần vững có khả năng kéo dài (EFI) thế hệ " -#~ "tới của công ty Intel™. Không như BIOS kiểu x86 truyền thống mà " -#~ "biết ít về thiết bị khởi động, trừ bảng phân vùng và rãnh ghi khởi động " -#~ "chủ (MBR), EFI có khả năng đọc và ghi tập tin từ phân vùng đĩa đã định " -#~ "dạng bằng FAT16 hay FAT32. Vậy nó giản dị hoá tiến trình khởi chạy hệ " -#~ "thống mà thường cần thiết kiến thức rất đặc biệt. Bộ tải khởi động hệ " -#~ "thống và phần vững EFI hỗ trợ nó có thể truy cập hệ thống tập tin đầy đủ " -#~ "để cất giữ các tập tin cần thiết để khởi động máy đó. Có nghĩa là đĩa hệ " -#~ "thống trên máy kiểu IA-64 chứa một phân vùng đĩa thêm dành cho EFI, thay " -#~ "cho MBR hay khối tin khởi động đơn giản trên hệ thống quy ước hơn." - -#~ msgid "" -#~ "The Debian Installer CD contains a small EFI partition where the " -#~ "ELILO 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 "" -#~ "Đĩa CD cài đặt Debian chứa một phân vùng EFI nhỏ chứa bộ tải khởi động " -#~ "ELILO, tập tin cấu hình của nó, hạt nhân của trình cài " -#~ "đặt, và hệ thống tập tin ban đầu (initrd). Hệ thống đang chạy cũng chứa " -#~ "một phân vùng EFI chứa những tập tin cần thiết để khởi động hệ thống. Các " -#~ "tập tin này có thể được đọc từ trình bao EFI như được diễn tả bên dưới." - -#~ msgid "" -#~ "Most of the details of how ELILO 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 ELILO 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 "" -#~ "Phần lớn chi tiết về phương pháp tải và khởi chạy hệ thống của " -#~ "ELILO là trong suốt cho trình cài đặt hệ thống. Tuy " -#~ "nhiên, trình cài đặt phải thiết lập một phân vùng EFI trước khi cài đặt " -#~ "hệ thống cơ bản. Nếu không, tiến trình cài đặt ELILO " -#~ "sẽ bị lỗi nên hệ thống không thể được khởi động. Phân vùng EFI được cấp " -#~ "phát và định dạng trong bước phân vùng của tiến trình cài đặt, trước khi " -#~ "tải gói nào vào đĩa hệ thống. Tác vụ phân vùng cũng thẩm tra có một phân " -#~ "vùng EFI thích hợp, trước khi cho phép tiến trình cài đặt tiếp tục lại." - -#~ 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, Boot " -#~ "Option Maintenance Menu and EFI Shell (Built-in). 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 "" -#~ "Bộ quản lý khởi động EFI được chạy như là bước cuối cùng trong tiến trình " -#~ "sở khởi phần vững. Nó hiển thị danh sách mục trình đơn nơi bạn có thể " -#~ "tuyển lựa một tùy chọn. Phụ thuộc vào mô hình hệ thống và phần mềm khác " -#~ "đã được tải vào hệ thống, trình đơn này có thể là khác nhau từ hệ thống " -#~ "này đến hệ thống đó. Nên có ít nhất hai mục trình đơn được hiển thị : " -#~ "Boot Option Maintenance Menu (Trình đơn bảo dưỡng tùy " -#~ "chọn khởi động) và EFI Shell (Built-in) (Trình bao EFI " -#~ "[có sẵn]). Đề nghị bạn bật tùy chọn thứ nhất; nếu nó không sẵn sàng, hoặc " -#~ "nếu đĩa CD vì lý do nào không khởi động được với nó, hãy bật tùy chọn thứ " -#~ "hai. " - -#~ msgid "IMPORTANT" -#~ msgstr "QUAN TRỌNG" - -#~ 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 exit at the shell prompt." -#~ msgstr "" -#~ "Bộ quản lý khởi động EFI sẽ bật một hành động khởi động mặc định, thường " -#~ "là mục trình đơn thứ nhất, trong vòng số giây định sẵn. Thời gian này " -#~ "được ngụ ý bằng con số đếm ngược bên dưới màn hình. Một khi bộ đếm thời " -#~ "gian này hết hạn, có lẽ bạn cần phải khởi động lại máy để tiếp tục lại " -#~ "cài đặt. Nếu hành động mặc định là Trình bao EFI, bạn có khả năng trở về " -#~ "Bộ quản lý khởi động bằng cách chạy lệnh exit (thoát) " -#~ "tại dấu nhắc trình bao." - -#~ msgid "Option 1: Booting from the Boot Option Maintenance Menu" -#~ msgstr "Tùy chọn 1: khởi động từ Trình đơn bảo dưỡng tùy chọn khởi động" - -#~ 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 "" -#~ "Hãy nạp đĩa CD vào ổ đĩa CD/DVD rồi khởi động lại máy. Phần vững sẽ hiển " -#~ "thị trang và trình đơn của Bộ quản lý khởi động EFI sau khi nó sở khởi " -#~ "xong hệ thống." - -#~ msgid "" -#~ "Select Boot Maintenance Menu from the menu with the " -#~ "arrow keys and press ENTER. This will display a new " -#~ "menu." -#~ msgstr "" -#~ "Hãy chọn mục Boot Maintenance Menu (Trình đơn bảo " -#~ "dưỡng khởi động) trong trình đơn bằng phím mũi tên, rồi bấm phím " -#~ "&enterkey;. Việc này sẽ hiển thị một trình đơn mới." - -#~ msgid "" -#~ "Select Boot From a File from the menu with the arrow " -#~ "keys and press ENTER. This will display a list of " -#~ "devices probed by the firmware. You should see two menu lines containing " -#~ "either the label Debian Inst [Acpi ... or " -#~ "Removable Media Boot. If you examine the rest of the " -#~ "menu line, you will notice that the device and controller information " -#~ "should be the same." -#~ msgstr "" -#~ "Hãy chọn mục Boot From a File (Khởi động từ tập tin) " -#~ "trong trình đơn bằng phím mũi tên, rồi bấm phím &enterkey;. Việc này sẽ " -#~ "hiển thị danh sách các thiết bị được thăm dò bởi phần vững. Bạn nên thấy " -#~ "hai dòng trình đơn chứa hoặc nhãn Debian Inst [Acpi ... hoặc Removable Media Boot (Khởi động từ vật " -#~ "chứa rời). Nếu bạn xem lại phần còn lại của dòng trình đơn, bạn nên thấy " -#~ "biết rằng thông tin về thiết bị và thông tin về trình điều khiển là trùng." - -#~ msgid "" -#~ "You can choose either of the entries that refer to the CD/DVD drive. " -#~ "Select your choice with the arrow keys and press ENTER. If you choose Removable Media Boot the " -#~ "machine will immediately start the boot load sequence. If you choose " -#~ "Debian Inst [Acpi ... instead, it will display a " -#~ "directory listing of the bootable portion of the CD, requiring you to " -#~ "proceed to the next (additional) step." -#~ msgstr "" -#~ "Bạn có thể chọn mục nhập nào tham chiếu đến ổ đĩa CD/DVD. Hãy chọn nó " -#~ "bằng phím mũi tên rồi bấm phím &enterkey;. Nếu bạn chọn mục " -#~ "Removable Media Boot (Khởi động từ vật chứa rời), máy " -#~ "sẽ bất đầu ngay tiến trình tải khởi động. Còn nếu bạn chọn mục " -#~ "Debian Inst [Acpi ..., nõ sẽ hiển thị danh sách các " -#~ "thư mục nằm trên phần đĩa CD có khả năng khởi động, cần thiết bạn tiếp " -#~ "tục đến bước kế tiếp (thêm)." - -#~ msgid "" -#~ "You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " -#~ "Removable Media Boot] on the next to the last line. Select this " -#~ "line with the arrow keys and press ENTER. This will " -#~ "start the boot load sequence." -#~ msgstr "" -#~ "Bạn sẽ cần phải theo bước này chỉ nếu bạn đã chọn mục Debian " -#~ "Inst [Acpi .... Danh sách thư mục sẽ cũng hiển thị mục " -#~ "[Treat like Removable Media Boot] (Xử lý như là việc khởi động " -#~ "từ vật chứa rời) trên dòng giáp cuối. Hãy chọn dòng này bằng phím mũi tên " -#~ "rồi bấm phím &enterkey;. Việc này sẽ khởi chạy tiến trình tải khởi động." - -#~ 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 "" -#~ "Những bước này khởi chạy bộ tải khởi Debian mà sẽ hiển thị một trang " -#~ "trình đơn cho bạn chọn một hạt nhân khởi động và các tùy chọn tương ứng. " -#~ "Hãy tiếp tục tới giai đoạn đó." - -#~ msgid "Option 2: Booting from the EFI Shell" -#~ msgstr "Tùy chọn 2: khởi động từ trình bao EFI" - -#~ 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 EFI Shell [Built-in]. Boot the Debian Installer " -#~ "CD with the following steps:" -#~ msgstr "" -#~ "Nếu, vì lý do nào, tùy chọn 1 bị lỗi, bạn hãy khởi động lại máy, và khi " -#~ "màn hình của bộ quản lý khởi động EFI xuất hiện, nên có một tùy chọn tên " -#~ "EFI Shell [Built-in] (Trình bao EFI [có sẵn]). Hãy " -#~ "khởi động đĩa CD cài đặt Debian bằng cách theo những bước này:" - -#~ 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 "" -#~ "Nạp đĩa CD vào ổ đĩa CD/DVD và khởi động lại máy. Phần vững sẽ hiển thị " -#~ "trang và trình đơn của Bộ quản lý khởi động EFI sau khi nó sở khởi xong " -#~ "hệ thống." - -#~ msgid "" -#~ "Select EFI Shell from the menu with the arrow keys and " -#~ "press ENTER. 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 fsn:. All " -#~ "other recognized partitions will be named blkn:. If you inserted the CD just before entering the " -#~ "shell, this may take a few extra seconds as it initializes the CD drive." -#~ msgstr "" -#~ "Chọn EFI Shell (Trình bao EFI) trong trình đơn bằng " -#~ "phím mũi tên, rồi bấm phím &enterkey;. Trình bao EFI sẽ quét tất cả các " -#~ "thiết bị có khả năng khởi động và hiển thị chúng trên bàn điều khiển " -#~ "trước khi hiển thị dấu nhắc lệnh của nó. Những phân vùng thiết bị có khả " -#~ "năng khởi động đã được nhận diện sẽ hiển thị tên thiết bị " -#~ "fsn:. Các phân vùng khác " -#~ "đã được nhận diện sẽ có tên blkn:. Nếu bạn đã nạp đĩa CD đúng trước khi vào trình bao, việc này " -#~ "có thể mất vài giây thêm trong khi nó sở khởi ổ đĩa CD." - -#~ msgid "" -#~ "Examine the output from the shell looking for the CDROM drive. It is most " -#~ "likely the fs0: device although other devices with " -#~ "bootable partitions will also show up as fsn." -#~ msgstr "" -#~ "Khám xét kết xuất của trình bao tìm ổ đĩa CD. Rất có thể nó là thiết bị " -#~ "fs0:, dù thiết bị khác có phân vùng khởi động được " -#~ "sẽ cũng hiển thị như là fsn." - -#~ msgid "" -#~ "Enter fsn: and press " -#~ "ENTER to select that device where n is the partition number for the CDROM. The shell will now " -#~ "display the partition number as its prompt." -#~ msgstr "" -#~ "Nhập fsn: rồi bấm phím " -#~ "&enterkey; để chọn thiết bị có số hiệu phân vùng của đĩa CD-ROM là " -#~ "n. Sau đó, trình bao sẽ hiển thị số hiệu phân " -#~ "vùng như là dấu nhắc." - -#~ msgid "" -#~ "Enter elilo and press ENTER. This " -#~ "will start the boot load sequence." -#~ msgstr "" -#~ "Nhập elilo rồi bấm phím &enterkey;. Việc này sẽ bắt " -#~ "đầu tiến trình tải khởi động." - -#~ 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot " -#~ "kernel and options." -#~ msgstr "" -#~ "Cũng như tùy chọn 1, những bước này khởi chạy bộ tải khởi động Debian mà " -#~ "sẽ hiển thị trang trình đơn cho bạn chọn hạt nhân và các tùy chọn tương " -#~ "ứng. Bạn cũng có khả năng nhập lệnh ngắn hơn fsn:elilo vào dấu nhắc trình bao. Hãy tiếp tục đến " -#~ "giai đoạn chọn hạt nhân khởi động và các tùy chọn tương ứng." - -#~ msgid "Installing using a Serial Console" -#~ msgstr "Cài đặt bằng bàn điều khiển nối tiếp" - -#~ 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 [BAUD baud serial console], where BAUD " -#~ "is the speed of your serial console. Menu items for the most typical baud " -#~ "rate settings on the ttyS0 device are preconfigured." -#~ msgstr "" -#~ "Bạn có thể chọn thực hiện tiến trình cài đặt bằng bộ trình bày và bàn " -#~ "phím, hay bằng sự kết nối kiểu nối tiếp. Để sử dụng thiết lập bộ trình " -#~ "bày và bàn phím, hãy bật một tùy chọn chứa chuỗi [VGA console] (bàn điều " -#~ "khiển VGA). Để cài đặt qua sự kết nối kiểu nối tiếp, hãy bật một tùy chọn " -#~ "chứa chuỗi [BỐT baud serial console], (bàn " -#~ "điều khiển nối tiếp bốt) mà BỐT là tốc độ " -#~ "truyền của bàn điều khiển nối tiếp đó. Trên thiết bị ttyS0, mục trình đơn " -#~ "cho những giá trị tốc độ truyền thường nhất đã được định sẵn." - -#~ 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 baud " -#~ "at the EFI shell." -#~ msgstr "" -#~ "Trong phần lớn hoàn cảnh, bạn sẽ muốn đặt bộ cài đặt sử dụng cùng một tốc " -#~ "độ truyền với sự kết nối đến bàn điều khiển EFI. Nếu bạn chưa biết được " -#~ "giá trị này, bạn có thể lấy nó bằng cách nhập lệnh baud (bốt) vào trình bao EFI." - -#~ 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 console=ttyS1,57600n8 into the Boot: text window." -#~ msgstr "" -#~ "Nếu không có tùy chọn sẵn sàng đã được cấu hình cho thiết bị nối tiếp hay " -#~ "tốc độ truyền bạn muốn dùng, bạn có khả năng đặt quyền cao hơn thiết lập " -#~ "bàn điều khiển dành cho một của những tùy chọn trình đơn đã có. Chẳng " -#~ "hạn, để dùng bàn điều khiển 57600 bốt qua thiết bị ttyS1, hãy nhập lệnh " -#~ "console=ttyS1,57600n8 vào cửa sổ nhập thô " -#~ "Boot: (khởi động)." - -#~ 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 Params help menu for instructions on starting the installer in Text " -#~ "Mode." -#~ msgstr "" -#~ "Phần lớn máy kiểu IA-64 có sẵn giá trị bàn điều khiển là 9600 bốt. Giá " -#~ "trị này hơi chậm nên tiến trình cài đặt bình thường sẽ mất thời gian đáng " -#~ "kể để vẽ mỗi màn hình. Đề nghị bạn hoặc tăng lên tốc độ truyền (bốt) được " -#~ "dùng để thi hành tiến trình cài đặt, hoặc thực hiện việc cài đặt kiểu Chế " -#~ "Độ Nhập Thô (Text Mode). Xem trình đơn trợ giúp Params (Tham số) để tìm hướng dẫn về cách khởi chạy trình cài đặt " -#~ "trong Chế Độ Nhập Thô." - -#~ 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 "" -#~ "Nếu bạn chọn kiểu bàn điều khiển không đúng, bạn vẫn còn có khả năng chọn " -#~ "hạt nhân và nhập tham số tương ứng, nhưng mà cả bộ trình bày lẫn cách " -#~ "nhập đều sẽ bị tắt một khi hạt nhân khởi chạy, nên cần thiết bạn khởi " -#~ "động lại để bất đầu cài đặt." - -#~ msgid "Selecting the Boot Kernel and Options" -#~ msgstr "Chọn hát nhân khởi động và các tùy chọn tương ứng" - -#~ msgid "" -#~ "The boot loader will display a form with a menu list and a text window " -#~ "with a Boot: 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 General help " -#~ "screen explains the menu choices and the Params " -#~ "screen explains the common command line options." -#~ msgstr "" -#~ "Bộ tải khởi động sẽ hiển thị đơn chứa danh sách trình đơn và cửa sổ nhập " -#~ "thô chứa dấu nhắc Boot: (khởi động). Phím mũi tên " -#~ "cho bạn chọn mục nào trong trình đơn, và đoạn nào được gõ bằng bàn phím " -#~ "sẽ xuất hiện trong cửa sổ nhập thô. Cũng có một số màn hình trợ giúp có " -#~ "thể được hiển thị bằng cách bấm phím chức năng (F1 ...) thích hợp. Màn " -#~ "hình trợ giúp General (Chung) diễn tả mỗi mục chọn " -#~ "trong trình đơn, còn màn hình Params (Tham số) " -#~ "giải thích những tùy chọn dòng lệnh thường dùng." - -#~ msgid "" -#~ "Consult the General help screen for the " -#~ "description of the kernels and install modes most appropriate for your " -#~ "installation. You should also consult " -#~ "below for any additional parameters that you may want to set in the " -#~ "Boot: 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 "" -#~ "Xem màn hình General (Chung) để tìm mô tả về các " -#~ "hạt nhân và chế độ cài đặt thích hợp nhất với tiến trình cài đặt vào máy " -#~ "của bạn. Xem thêm bên dưới, để tìm tham số " -#~ "thêm nào bạn muốn đặt trong cửa sổ nhập thô Boot: " -#~ "(khởi động). Bạn sẽ chọn một phiên bản hạt nhân quyết định phiên bản hạt " -#~ "nhân được dùng trong cả tiến trình cài đặt lẫn hệ thống sẽ được cài đặt. " -#~ "Nếu bạn gặp khó khăn trong tiến trình cài đặt, bạn sẽ có thể gặp cùng khó " -#~ "khăn khi chạy hệ thống được cài đặt." - -#~ msgid "" -#~ "Select the kernel version and installation mode most appropriate to your " -#~ "needs with the arrow keys." -#~ msgstr "" -#~ "Bằng phím mũi tên, hãy chọn phiên bản hạt nhân và chế độ cài đặt thích " -#~ "hợp nhất với điều kiện của máy tính của bạn." - -#~ 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 "" -#~ "Sau đó, hãy nhập tham số khởi động nào đã muốn bằng cách gõ vào bàn phím. " -#~ "Đoạn đã gõ sẽ được hiển thị trực tiếp trong cửa sổ nhập thô. Ở đây bạn có " -#~ "thể xác định tham số hạt nhân như thiết lập bàn điều khiển nối tiếp." - -#~ msgid "" -#~ "Press ENTER. 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 "" -#~ "Bấm phím &enterkey;. Cú này sẽ tải và khởi chạy hạt nhân. Hạt nhân sẽ " -#~ "hiển thị thông điệp sở khởi thường rồi màn hình thứ nhất của tiến trình " -#~ "cài đặt Debian." - -#~ msgid "" -#~ "Proceed to the next chapter to continue the installation where you will " -#~ "set up the language locale, network, and disk partitions." -#~ msgstr "" -#~ "Sau đó, hãy tới chương kế tiếp, để tiếp tục tiến trình cài đặt bằng cách " -#~ "thiết lập miền địa phương (gồm ngôn ngữ), mạng và phân vùng đĩa." - -#, fuzzy -#~ msgid "" -#~ "Booting an IA-64 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 "" -#~ "Việc khởi động hệ thống kiểu IA64 qua mạng giống như việc khởi động từ " -#~ "đĩa CD. Sự khác nhau duy nhất là cách tải hạt nhân cài đặt. Bộ quản lý " -#~ "khởi động EFI có khả năng tải và khởi chạy chương trình từ máy phục vụ " -#~ "trên mạng. Một khi hạt nhân cài đặt đã được tải và khởi động, tiến trình " -#~ "cài đặt hệ thống sẽ tiếp tục qua cùng những bước với tiến trình cài đặt " -#~ "từ đĩa CD, với ngoài lệ là các gói của bản cài đặt cơ sở sẽ được tải qua " -#~ "mạng hơn là qua ổ đĩa CD." - -#, fuzzy -#~ msgid "" -#~ "Network booting an IA-64 system requires two architecture-specific " -#~ "actions. On the boot server, DHCP and TFTP must be configured to deliver " -#~ "elilo. On the client a new boot option must be defined " -#~ "in the EFI boot manager to enable loading over a network." -#~ msgstr "" -#~ "Việc khởi động hệ thống kiểu ia64 qua mạng cần thiết hai hành động đặc " -#~ "trưng cho kiến trúc đó. Trên máy phục vụ khởi động, hai dịch vụ DHCP và " -#~ "TFTP phải được cấu hình để phát elilo. Còn trên máy " -#~ "khách, một tùy chọn khởi động mới phải được xác định trong bộ quản lý " -#~ "khởi động EFI để hiệu lực khả năng tải qua mạng." - -#~ msgid "Configuring the Server" -#~ msgstr "Cấu hình máy phục vụ" - -#, fuzzy -#~ msgid "" -#~ "A suitable TFTP entry for network booting an IA-64 system looks something " -#~ "like this: \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" -#~ " Note that the goal is to get elilo." -#~ "efi running on the client." -#~ msgstr "" -#~ "Một mục nhập TFTP thích hợp với khả năng khởi động hệ thống kiểu ia64 qua " -#~ "mạng có vẻ như :\n" -#~ "host banhdauxanh {\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" -#~ " Ghi chú rằng mục đích là làm cho " -#~ "elilo.efi chạy trên máy khách." - -#~ msgid "" -#~ "Extract the netboot.tar.gz file into the directory " -#~ "used as the root for your tftp server. Typical tftp root directories " -#~ "include /var/lib/tftp and /tftpboot. This will create a debian-installer " -#~ "directory tree containing the boot files for an IA-64 system." -#~ msgstr "" -#~ "Hãy giải nén tập tin netboot.tar.gz vào thư mục được " -#~ "dùng như là gốc của trình phục vụ TFTP. Các thư mục gốc TFTP thường bao " -#~ "gồm /var/lib/tftp và /tftpboot. " -#~ "Việc giải nén này sẽ tạo cây thư mục debian-installer (bản cài đặt Debian) chứa các tập tin khởi động thích hợp với " -#~ "hệ thống kiểu IA-64." - -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" -#~ msgstr "" -#~ "# cd /var/lib/tftp\n" -#~ "# tar xvfz /home/user/netboot.tar.gz\n" -#~ "./\n" -#~ "./debian-installer/\n" -#~ "./debian-installer/ia64/\n" -#~ "[...]" - -#~ msgid "" -#~ "The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should " -#~ "you need to make changes to this file, you can find it in the " -#~ "debian-installer/ia64/ 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 .conf " -#~ "instead of elilo.conf. See documentation provided in " -#~ "the elilo package for details." -#~ msgstr "" -#~ "Kho nén netboot.tar.gz chứa tập tin cấu hình " -#~ "elilo.conf nên hoạt động được với phần lớn tổ hợp " -#~ "phần cứng. Tuy nhiên, nếu bạn cần phải sửa đổi tập tin này, nó nằm trong " -#~ "thư mục debian-installer/ia64/. Có thể duy trì tập " -#~ "tin cấu hình riêng cho mỗi máy khách, bằng cách đặt tên là địa chỉ IP " -#~ "dạng thập lục của máy khách, cộng hậu tố .conf (cấu " -#~ "hình) thay cho tên tập tin gốc elilo.conf. Xem tài " -#~ "liệu có sẵn trong gói elilo để tìm chi tiết." - -#~ msgid "Configuring the Client" -#~ msgstr "Cấu hình máy khách" - -#~ msgid "" -#~ "To configure the client to support TFTP booting, start by booting to EFI " -#~ "and entering the Boot Option Maintenance Menu. " -#~ " Add a boot option. " -#~ " You should see one or more lines with the text " -#~ "Load File [Acpi()/.../Mac()]. 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. Name " -#~ "the entry Netboot or something similar, save, and " -#~ "exit back to the boot options menu. " -#~ "You should see the new boot option you just created, and selecting it " -#~ "should initiate a DHCP query, leading to a TFTP load of elilo." -#~ "efi from the server." -#~ msgstr "" -#~ "Để cấu hình máy khách để hỗ trợ khả năng khởi động qua dịch vụ TFTP, hãy " -#~ "bắt đầu bằng cách khởi động tới EFI rồi vào Boot Option " -#~ "Maintenance Menu (trình đơn bảo dưỡng tùy chọn khởi động). " -#~ " Thêm một tùy chọn khởi động. Sau đó, bạn nên thấy đoạn (một hay nhiều dòng) " -#~ "dạng Load File [Acpi()/.../Mac()]. Nếu có " -#~ "nhiều mục nhập như thế, hãy chọn điều chứa địa chỉ MAC của giao diện từ " -#~ "đó bạn sẽ khởi động. Dùng phím mũi tên để tô sáng sự chọn riêng, rồi bấm " -#~ "&enterkey;. Đặt mục nhập có tên " -#~ "Netboot (khởi động qua mạng) hay tương tự, lưu, " -#~ "rồi thoát về trình đơn tùy chọn khởi động. Lúc đó, bạn nên thấy tùy chọn khởi động mới đã được tạo. " -#~ "Việc chọn nó nên khởi đầu truy vấn DHCP, chỉ dẫn đến việc tải tập tin " -#~ "elilo.efi qua TFTP từ máy phục vụ." - -#~ 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 "" -#~ "Bộ tải khởi động sẽ hiển thị dấu nhắc riêng sau khi nó tải về và xử lý " -#~ "tập tin cấu hình riêng. Tại điểm thời này, tiến trình cài đặt theo cùng " -#~ "những bước với sự cài đặt từ đĩa CD. Hãy chọn một tùy chọn khởi động (như " -#~ "nêu trên) và, khi hạt nhân đã cài đặt chính nó qua mạng, nó sẽ khởi chạy " -#~ "trình cài đặt Debian." - -#~ msgid "Choosing an Installation Method" -#~ msgstr "Chọn phương pháp cài đặt" - -#~ 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 "" -#~ "Một số kiến trúc phụ kiểu &arch-title; có tùy chọn khởi động bằng hạt " -#~ "nhân phiên bản hoặc 2.4.x hoặc 2.2.x. Khi bạn gặp tùy chọn này, hãy thử " -#~ "dùng hạt nhân 2.4.x. Tiến trình cài đặt dùng hạt nhân 2.4.x nên cần thiết " -#~ "bộ nhớ ít hơn, vì khả năng hỗ trợ hạt nhân 2.2.x cần thiết đĩa RAM có " -#~ "kích cỡ cố định, còn 2.4.x dùng hệ thống tập tin tạm thời (tmpfs)." - -#~ msgid "" -#~ "If you are using a 2.2.x linux kernel, then you need to use the " -#~ "&ramdisksize; kernel parameter." -#~ msgstr "" -#~ "Nếu bạn dùng hạt nhân Linux phiên bản 2.2.x, bạn cũng cần phải xác định " -#~ "tham số hạt nhân kích cỡ đĩa bộ nhớ RAM &ramdisksize;." - -#~ msgid "" -#~ "Make sure root=/dev/ram is one of your kernel " -#~ "parameters." -#~ msgstr "" -#~ "Hãy kiểm tra xem bạn đã chọn tham số hạt nhân root=/dev/ram." - -#~ msgid "" -#~ "If you're having trouble, check cts's " -#~ "&arch-title; debian-installer FAQ." -#~ msgstr "" -#~ "Nếu bạn gặp khó khăn, xem Hỏi Đáp cts's " -#~ "&arch-title; debian-installer FAQ." - -# Name: don't translate / Tên: đừng dịch -#~ msgid "Amiga" -#~ msgstr "Amiga" - -#~ msgid "" -#~ "The only method of installation available to amiga is the hard drive (see " -#~ "). In other words the cdrom is " -#~ "not bootable." -#~ msgstr "" -#~ "Khi dùng máy kiểu Amiga, chỉ có sẵn sàng một phương pháp cài đặt: bằng " -#~ "đĩa cứng (xem ). Tức là không " -#~ "thể khởi động từ đĩa CD-ROM." - -#~ msgid "" -#~ "Amiga does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Máy kiểu Amiga hiện thời không hoạt động được với bogl, vậy nếu bạn gặp " -#~ "lỗi bogl, bạn cần phải nhập tham số hạt nhân fb=false." - -# Name: don't translate / Tên: đừng dịch -#~ msgid "Atari" -#~ msgstr "Atari" - -#~ msgid "" -#~ "The installer for atari may be started from either the hard drive (see " -#~ ") or from floppies (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "Khi dùng máy kiểu Atari, bạn có thể khởi chạy trình cài đặt Debian hoặc " -#~ "từ đĩa cứng (xem ) hoặc từ đĩa mềm (xem " -#~ "). Tức là không thể khởi " -#~ "động từ đĩa CD-ROM." - -#~ msgid "" -#~ "Atari does not currently work with bogl, so if you are seeing bogl " -#~ "errors, you need to include the boot parameter fb=false." -#~ msgstr "" -#~ "Máy kiểu Atari hiện thời không hoạt động được với bogl, vậy nếu bạn gặp " -#~ "lỗi bogl, bạn cần phải nhập tham số hạt nhân fb=false." - -# Name: don't translate / Tên: đừng dịch -#~ msgid "BVME6000" -#~ msgstr "BVME6000" - -#~ msgid "" -#~ "The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." -#~ msgstr "" -#~ "Đối với máy kiểu BVME6000, trình cài đặt có thể được khởi chạy hoặc từ " -#~ "đĩa CD-ROM (xem ), hoặc từ đĩa mềm " -#~ "(xem ), hoặc qua mạng (xem )." - -# Name: don't translate / Tên: đừng dịch -#~ msgid "Macintosh" -#~ msgstr "Macintosh (Apple Mac)" - -#~ msgid "" -#~ "The only method of installation available to mac is from the hard drive " -#~ "(see ). In other words the " -#~ "cdrom is not bootable. Macs do not have a working 2.4.x kernel." -#~ msgstr "" -#~ "Phương pháp cài đặt duy nhất sẵn sàng cho máy Mac là từ đĩa cứng (xem " -#~ "). Tức là không có khả năng " -#~ "khởi động được từ đĩa CD-ROM. Chưa có hạt nhân phiên bản 2.4.x " -#~ "hoạt động được với máy kiểu Mac." - -#~ msgid "" -#~ "If your hardware uses a 53c9x-based scsi bus, then you may need to " -#~ "include the kernel parameter mac53c9x=1,0. " -#~ "Hardware with two such scsi buses, such as the Quadra 950, will need " -#~ "mac53c9x=2,0 instead. Alternatively, the parameter " -#~ "can be specified as mac53c9x=-1,0 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 "" -#~ "Nếu phần cứng của bạn sử dụng một mạch nối SCSI dựa vào 53c9x, có lẽ bạn " -#~ "cần phải nhập tham số hạt nhân mac53c9x=1,0. Phần " -#~ "cứng có hai mạch nối SCSI như vậy, v.d. máy Quadra 950, cần thiết bạn " -#~ "nhập tham số mac53c9x=2,0 thay thế. Hoặc có thể " -#~ "xạc định tham số mac53c9x=-1,0, mà duy trì khả " -#~ "năng phát hiện tự động, còn tắt khả năng ngắt kết nối SCSI. Ghi chú rằng " -#~ "việc xác định tham số này cần thiết chỉ nếu bạn có nhiều đĩa cứng; nếu " -#~ "không (chỉ có một đĩa), hệ thống sẽ chạy nhanh hơn nếu bạn không xác định " -#~ "nó." - -#~ msgid "MVME147 and MVME16x" -#~ msgstr "MVME147 và MVME16x" - -#~ msgid "" -#~ "The installer for MVME147 and MVME16x may be started from either floppies " -#~ "(see ) or the net (see ). In other words the cdrom is not " -#~ "bootable." -#~ msgstr "" -#~ "Đối với máy kiểu MVME147 và MVME16x, trình cài đặt có thể được khởi chạy " -#~ "hoặc từ đĩa mềm (xem ) hoặc qua " -#~ "mạng (xem phần ). Tức là không có " -#~ "khả năng khởi động được từ đĩa CD-ROM." - -# Name: don't translate / Tên: đừng dịch -#~ msgid "Q40/Q60" -#~ msgstr "Q40/Q60" - -#~ msgid "" -#~ "The only method of installation available to Q40/Q60 is from the hard " -#~ "drive (see ). In other words " -#~ "the cdrom is not bootable." -#~ msgstr "" -#~ "Phương pháp cài đặt duy nhất sẵn sàng cho máy kiểu Q40/Q60 là từ đĩa cứng " -#~ "(xem ). Tức là không có khả " -#~ "năng khởi động được từ đĩa CD-ROM." - -#~ msgid "Booting from a Hard Disk" -#~ msgstr "Khởi động từ đĩa cứng" - -#~ msgid "" -#~ "Booting from an existing operating system is often a convenient option; " -#~ "for some systems it is the only supported method of installation." -#~ msgstr "" -#~ "Việc khởi động từ hệ điều hành tồn tại thường là một tùy chọn có ích; còn " -#~ "đối với một số hệ thống riêng, nó là phương pháp cài đặt duy nhất được hỗ " -#~ "trợ." - -#~ msgid "" -#~ "To boot the installer from hard disk, you will have already completed " -#~ "downloading and placing the needed files in ." -#~ msgstr "" -#~ "Trong ), bạn đã tải về và định vị " -#~ "những tập tin cần thiết để khởi chạy trình cài đặt từ đĩa cứng." - -#~ 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 MANIFEST for details)." -#~ msgstr "" -#~ "Ít nhất sáu đĩa bộ nhớ RAM khác nhau có thể được dùng để khởi động từ đĩa " -#~ "cứng: ba kiểu khác nhau, mỗi kiểu có và không có khả năng hỗ trợ hạt nhân " -#~ "phiên bản 2.2.x (xem bản kê khai để tìm chi tiết)." - -#~ msgid "" -#~ "The three different types of ramdisks are cdrom, " -#~ "hd-media, and nativehd. These " -#~ "ramdisks differ only in their source for installation packages. The " -#~ "cdrom ramdisk uses a cdrom to get debian-installer " -#~ "packages. The hd-media ramdisk uses an iso image " -#~ "file of a cdrom currently residing on a hard disk. Finally, the " -#~ "nativehd ramdisk uses the net to install packages." -#~ msgstr "" -#~ "Ba kiểu đĩa RAM khác nhau là cdrom (đĩa CD-ROM), " -#~ "hd-media (vật chứa đĩa cứng), và nativehd (đĩa cứng sở hữu). Những đĩa RAM này chỉ khác biệt trong nguồn " -#~ "của những gói cài đặt. Đĩa RAM kiểu cdrom sử dụng " -#~ "một đĩa CD-ROM để lấy các gói cài đặt Debian. Còn đĩa RAM kiểu " -#~ "hd-media sử dụng một tập tin ảnh ISO của đĩa CD-ROM " -#~ "hiện thời nằm trên đĩa cứng. Cuối cùng, đĩa RAM kiểu nativehd cài đặt gói qua mạng." - -#~ msgid "Booting from AmigaOS" -#~ msgstr "Khởi động từ AmigaOS" - -#~ msgid "" -#~ "In the Workbench, start the Linux installation process " -#~ "by double-clicking on the StartInstall icon in the " -#~ "debian directory." -#~ msgstr "" -#~ "Trong Workbench, hãy khởi chạy tiến trình cài đặt " -#~ "Linux bằng cách nhấn đôi vào biểu tượng StartInstall " -#~ "(bất đầu cài đặt) nằm trong thư mục debian." - -#~ 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 ." -#~ msgstr "" -#~ "Có lẽ bạn cần phải bấm phím &enterkey; hai lần sau khi chương trình cài " -#~ "đặt Amiga đã xuất vài thông tin gỡ lỗi vào cửa sổ. Sau đó, màn hình xảy " -#~ "ra màu xám, cần phải đợi vài giây. Tiếp sau, màn hình màu đen với đoạn " -#~ "màu trắng nên xuất hiện, hiển thị nhiều kiểu thông tin gỡ lỗi hạt nhân. " -#~ "Các thông điệp này có thể cuộn ra quá nhanh để đọc được: không có sao. " -#~ "Sau một hai giây, chương trình cài đặt nên khởi chạy tự động, vậy bạn có " -#~ "thể tiếp tục tới ." - -#~ msgid "Booting from Atari TOS" -#~ msgstr "Khởi động từ Atari TOS" - -#~ msgid "" -#~ "At the GEM desktop, start the Linux installation process by double-" -#~ "clicking on the bootstra.prg icon in the " -#~ "debian directory and clicking Ok at the program options dialog box." -#~ msgstr "" -#~ "Trong môi trường làm việc GEM, hãy khởi chạy tiến trình cài đặt Linux " -#~ "bằng cách nhấn đôi vào biểu tượng bootstra.prg nằm " -#~ "trong thư mục debian, rồi nhấn vào cái nút " -#~ "Ok (Được) trong hộp thoại tùy chọn chương trình." - -#~ 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 ." -#~ msgstr "" -#~ "Có lẽ bạn cần phải bấm phím &enterkey; sau khi chương trình tải khởi động " -#~ "Atari đã xuất vài thông tin gỡ lỗi vào cửa sổ. Sau đó, màn hình xảy ra " -#~ "màu xám, cần phải đợi vài giây. Tiếp sau, màn hình màu đen với đoạn màu " -#~ "trắng nên xuất hiện, hiển thị nhiều kiểu thông tin gỡ lỗi hạt nhân. Các " -#~ "thông điệp này có thể cuộn ra quá nhanh để đọc được: không có sao. Sau " -#~ "một hai giây, chương trình cài đặt nên khởi chạy tự động, vậy bạn có thể " -#~ "tiếp tục tới ." - -#~ msgid "Booting from MacOS" -#~ msgstr "Khởi động từ MacOS" - -#~ msgid "" -#~ "You must retain the original Mac system and boot from it. It is " -#~ "essential that, when booting MacOS in preparation " -#~ "for booting the Penguin linux loader, you hold the shift " -#~ "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 "" -#~ "Bạn cần phải giữ lại hệ điều hành Mac gốc và khởi động từ nó. " -#~ "Chủ yếu rằng khi bạn khởi động hệ điều hành MacOS để " -#~ "chuẩn bị khởi động bộ tải Linux Penguin, bạn bấm giữ phím dài để ngăn cản tải các phần mở rộng của HĐH Mac. Nếu bạn không sử " -#~ "dụng HĐH MacOS, trừ khi khởi động Linux, bạn có thể làm cùng công việc đó " -#~ "bằng cách gỡ bỏ mọi phần mở rộng (Extensions) và bảng điều khiển (Control " -#~ "Panels) ra thư mục hệ thống (System Folder) của HĐH MacOS. Nếu không, có " -#~ "lẽ một số phần mở rộng còn chạy lại thì gây ra lỗi ngẫu nhiên với hạt " -#~ "nhân Linux đang chạy." - -#~ msgid "" -#~ "Macs require the Penguin bootloader. If you do not " -#~ "have the tools to handle a Stuffit archive, &penguin19." -#~ "hfs; is an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." -#~ msgstr "" -#~ "Máy kiểu Mac cần thiết bộ tải khởi động Penguin. Nếu " -#~ "bạn không có công cụ giải nén kho kiểu Stuffit (phần " -#~ "mở rộng tập tin .sit), &penguin19.hfs; là một ảnh " -#~ "đĩa cung cấp Penguin đã được giải nén. diễn tả cách sao chép ảnh này vào đĩa mềm." - -#~ msgid "" -#~ "At the MacOS desktop, start the Linux installation process by double-" -#~ "clicking on the Penguin Prefs icon in the " -#~ "Penguin directory. The Penguin " -#~ "booter will start up. Go to the Settings item " -#~ "in the File menu, click the Kernel tab. Select the kernel (vmlinuz) and " -#~ "ramdisk (initrd.gz) images in the install directory by clicking on the corresponding buttons in the upper " -#~ "right corner, and navigating the file select dialogs to locate the files." -#~ msgstr "" -#~ "Trong môi trường Desktop của MacOS, hãy khởi chạy tiến trình cài đặt " -#~ "Linux bằng cách nhấn đôi vào biểu tượng Penguin Prefs " -#~ "(tùy thích Penguin) nằm trong thư mụcPenguin. Bộ " -#~ "khởi động Penguin sẽ khởi chạy. Hãy tới mục " -#~ "Settings (thiết lập) nằm trong trình đơn " -#~ "File (tập tin), nhấn vào thanh nhỏ Kernel (hạt nhân). Chọn ảnh kiểu hạt nhân (vmlinuz) và đĩa RAM (initrd.gz) đều nằm trong thư " -#~ "mục install (cài đặt) bằng cách nhấn vào cái nút " -#~ "tương ứng bên phải, góc trên, rồi duyệt qua hộp thoại chọn tập tin để tìm " -#~ "tập tin thích hợp." - -#~ msgid "" -#~ "To set the boot parameters in Penguin, choose File -" -#~ "> Settings..., then switch to the " -#~ "Options tab. Boot parameters may be typed in to the " -#~ "text entry area. If you will always want to use these settings, select " -#~ "File -> Save Settings as Default." -#~ msgstr "" -#~ "Để đặt các tham số khởi động trong Penguin, hãy đi tới trình đơn " -#~ "File (tập tin) và chọn mục Settings... (thiết lập), rồi bật thanh nhỏ Options " -#~ "(tùy chọn). Các tham số khởi động có thể được gõ vào vùng nhập chữ. Nếu " -#~ "bạn muốn sử dụng luôn thiết lập này, trong trình đơn File hãy chọn mục Save Settings as Default " -#~ "(lưu thiết lập này là mặc định)." - -#~ msgid "" -#~ "Close the Settings dialog, save the settings and " -#~ "start the bootstrap using the Boot Now item in " -#~ "the File menu." -#~ msgstr "" -#~ "Hãy đóng hộp thoại Settings, lưu thiết lập đó và " -#~ "khởi chạy tiến trình tải khởi động bằng cách chọn mục Boot " -#~ "Now (khởi động ngay bây giờ) nằm trong trình đơn " -#~ "File." - -#~ msgid "" -#~ "The Penguin 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 ." -#~ msgstr "" -#~ "Bộ khởi động Penguin sẽ xuất vài thông tin gỡ lỗi vào " -#~ "cửa sổ. Sau đó, màn hình xảy ra màu xám, cần phải đợi vài giây. Tiếp sau, " -#~ "màn hình màu đen với đoạn màu trắng nên xuất hiện, hiển thị nhiều kiểu " -#~ "thông tin gỡ lỗi hạt nhân. Các thông điệp này có thể cuộn ra quá nhanh để " -#~ "đọc được: không có sao. Sau một hai giây, chương trình cài đặt nên khởi " -#~ "chạy tự động, vậy bạn có thể tiếp tục tới ." - -#~ msgid "Booting from Q40/Q60" -#~ msgstr "Khởi động từ Q40/Q60" - -#~ msgid "FIXME" -#~ msgstr "FIXME (sửa đi: phần tiếng Anh chưa tạo)" - -#~ msgid "" -#~ "The installation program should start automatically, so you can continue " -#~ "below at ." -#~ msgstr "" -#~ "Chương trình cài đặt nên khởi chạy tự động, vậy bạn có thể tiếp tục tới " -#~ " bên dưới." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitecture that supports CD-ROM " -#~ "booting is the BVME6000." -#~ msgstr "" -#~ "Hiện thời, kiến trúc phụ kiểu &arch-title; duy nhất hỗ trợ được khả năng " -#~ "khởi động từ đĩa CD-ROM là máy BVME6000." - -#~ msgid "" -#~ "After booting the VMEbus systems you will be presented with the LILO " -#~ "Boot: 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 "" -#~ "Sau khi khởi động hệ thống kiểu VMEbus, bạn sẽ xem dấu nhắc Boot:" -#~ " (khởi động) của LILO. Tại dấu nhắc đó, hãy nhập một của những " -#~ "đoạn theo đây, để khởi động Linux và bắt đầu tiến trình cài đặt phần mềm " -#~ "Debian chính bằng khả năng mô phỏng thiết bị cuối VT102:" - -#~ msgid "type i6000 &enterkey; to install a BVME4000/6000" -#~ msgstr "" -#~ "gõ i6000 &enterkey; để cài đặt vào máy kiểu BVME4000/6000" - -#~ msgid "type i162 &enterkey; to install an MVME162" -#~ msgstr "gõ i162 &enterkey; để cài đặt vào máy kiểu MVME162" - -#~ msgid "type i167 &enterkey; to install an MVME166/167" -#~ msgstr "" -#~ "gõ i167 &enterkey; để cài đặt vào máy kiểu MVME166/167" - -#~ msgid "" -#~ "You may additionally append the string TERM=vt100 to use " -#~ "vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." -#~ msgstr "" -#~ "Bạn cũng có thể phụ thêm chuỗi TERM=vt100 để sử dụng khả " -#~ "năng mô phỏng thiết bị cuối VT100, v.d. i6000 TERM=vt100 " -#~ "&enterkey;." - -#~ msgid "" -#~ "For most &arch-title; architectures, booting from a local filesystem is " -#~ "the recommended method." -#~ msgstr "" -#~ "Đối với phần lớn kiến trúc kiểu &arch-title;, phương pháp khuyến khích là " -#~ "khởi động từ hệ thống tập tin cục bộ." - -#~ msgid "" -#~ "Booting from the boot floppy is supported only for Atari and VME (with a " -#~ "SCSI floppy drive on VME) at this time." -#~ msgstr "" -#~ "Khả năng khởi động từ đĩa mềm khởi động được hỗ trợ chỉ trên máy kiểu " -#~ "Atari và VME (với ổ đĩa mềm SCSI trên VME) vào lúc này." - -#~ msgid "SGI TFTP Booting" -#~ msgstr "Khởi động SGI qua TFTP" - -#~ msgid "" -#~ "After entering the command monitor use \n" -#~ "bootp():\n" -#~ " 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 netaddr environment variable. Type " -#~ "\n" -#~ "unsetenv netaddr\n" -#~ " in the command monitor to do this." -#~ msgstr "" -#~ "Sau khi vào bộ theo dõi lệnh, hãy nhập \n" -#~ "bootp():\n" -#~ " trên máy kiểu SGI để khởi động Linux và bất " -#~ "đầu cài đặt phần mềm Debian. Để làm cho việc này hoạt động được, có lẽ " -#~ "bạn cần phải bỏ đặt biến môi trường netaddr (địa chỉ " -#~ "mạng). Hãy gõ lệnh \n" -#~ "unsetenv netaddr\n" -#~ " trong bộ theo dõi lệnh để làm như thế." - -#~ msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" -#~ msgstr "Khởi động qua TFTP trên máy BCM91250A và BCM91480B Broadcom" - -#~ 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: " -#~ "\n" -#~ "ifconfig eth0 -auto\n" -#~ " Once you have obtained an IP address, you can " -#~ "load SiByl with the following command: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " 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 "" -#~ "Trên bo mạch ước lượng BCM91250A và BCM91480B của Broadcom, bạn cần phải " -#~ "tải bộ tải khởi động SiByl thông qua TFTP, mà lần lượt sẽ tải và khởi " -#~ "chạy trình cài đặt Debian. Trong phần lớn trường hợp, trước tiên bạn sẽ " -#~ "lấy một địa chỉ IP thông qua dịch vụ DHCP; cũng có thể cấu hình một địa " -#~ "chỉ tĩnh. Để sử dụng DHCP, bạn có khả năng nhập lệnh này tại dấu nhắc " -#~ "CFE: \n" -#~ "ifconfig eth0 -auto\n" -#~ " Một khi bạn giành một địa chỉ IP, bạn có thể " -#~ "tải SiByl bằng lệnh này: \n" -#~ "boot 192.168.1.1:/boot/sibyl\n" -#~ " Bạn cần phải thay thế địa chỉ IP của lời thí " -#~ "dụ này bằng hoặc tên hoặc địa chỉ IP của máy phục vụ TFTP của bạn. Một " -#~ "khi bạn thực hiện lệnh này, trình cài đặt sẽ được tải tự động." - -#~ msgid "Boot Parameters" -#~ msgstr "Tham số khởi động" - -#~ msgid "" -#~ "On SGI machines you can append boot parameters to the bootp(): command in the command monitor." -#~ msgstr "" -#~ "Trên máy kiểu SGI, bạn có khả năng phụ thêm một số tham số khởi động vào " -#~ "lệnh bootp(): trong bộ theo dõi lệnh." - -#~ msgid "" -#~ "Following the bootp(): 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: \n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Further kernel parameters can be passed via " -#~ "append:" -#~ msgstr "" -#~ "Sau khi thực hiện lệnh bootp():, bạn có khả năng nhập " -#~ "đường dẫn và tên của tập tin cần khởi động, nếu bạn chưa đưa ra một tên " -#~ "riêng thông qua máy phục vụ BOOTP/DHCP. Ví dụ : " -#~ "\n" -#~ "bootp():/boot/tftpboot.img\n" -#~ " Tham số hạt nhân thêm có thể được gởi bằng " -#~ "lệnh append (phụ thêm):" - -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "bootp(): append=\"root=/dev/sda1\"" -#~ msgstr "bootp(): append=\"root=/dev/sda1\"" - -#~ msgid "" -#~ "You cannot pass any boot parameters directly from the CFE prompt. " -#~ "Instead, you have to edit the /boot/sibyl.conf file " -#~ "on the TFTP server and add your parameters to the " -#~ "extra_args variable." -#~ msgstr "" -#~ "Bạn không thể gởi tham số hạt nhân nào một cách trực tiếp từ dấu nhắc " -#~ "CFE. Thay thế, bạn cần phải sửa đổi tập tin cấu hình /boot/" -#~ "sibyl.conf trên máy phục vụ TFTP, và thêm các tham số riêng " -#~ "của bạn vào biến extra_args (đối số thêm) " -#~ "trong nó." - -#~ msgid "Cobalt TFTP Booting" -#~ msgstr "Khởi động TFTP Cobalt" - -#~ 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 /nfsroot. 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 "" -#~ "Nói chính xác, máy kiểu Cobalt không sử dụng dịch vụ TFTP để khởi động: " -#~ "nó dùng NFS. Bạn cần phải cài đặt trình phục vụ NFS và chèn các tập tin " -#~ "cài đặt vào thư mục /nfsroot. Khi bạn khởi động máy " -#~ "Cobalt đó, bạn cần phải bấm cả hai cái nút con chạy (bên trái và bên " -#~ "phải) cùng lúc, rồi máy sẽ khởi động qua mạng từ NFS. Sau đó, nó sẽ hiển " -#~ "thị vài tùy chọn trên màn hình. Có những phương pháp cài đặt này:" - -#~ 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 "" -#~ "Bằng SSH (mặc định): trong trường hợp này, trình cài đặt sẽ cấu hình mạng " -#~ "bằng dịch vụ DHCP, và khởi chạy trình phục vụ SSH. Sau đó, nó sẽ hiển thị " -#~ "một mật khẩu ngẫu nhiên và thông tin đăng nhập khác (như địa chỉ IP) trên " -#~ "màn hình LCD (phẳng) của máy Cobalt. Khi bạn kết nối đến máy đó bằng ứng " -#~ "dụng khách SSH, bạn có thể khởi chạy tiến trình cài đặt." - -#~ 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 "" -#~ "Bằng bàn điều khiển nối tiếp: dùng một cáp bộ điều giải vô giá trị (null " -#~ "modem), bạn có thể kết nối đến cổng nối tiếp của máy Cobalt (bằng 115200 " -#~ "bps) và thực hiện tiến trình cài đặt bằng cách này này. Tùy chọn này " -#~ "không sẵn sàng trên máy Qube 2700 (Qube1) vì máy kiểu này không có cổng " -#~ "nối tiếp." - -#~ msgid "" -#~ "You cannot pass any boot parameters directly. Instead, you have to edit " -#~ "the /nfsroot/default.colo file on the NFS server and " -#~ "add your parameters to the args variable." -#~ msgstr "" -#~ "Bạn không thể gởi trực tiếp tham số khởi động nào. Thay thế, bạn cần phải " -#~ "sửa đổi tập tin /nfsroot/default.colo trên máy phục " -#~ "vụ NFS, và thêm các tham số riêng của bạn vào biến args (đối số) trong nó." - -#~ msgid "s390 Limitations" -#~ msgstr "Hạn chế S/390" - -#~ msgid "" -#~ "In order to run the installation system a working network setup and ssh " -#~ "session is needed on S/390." -#~ msgstr "" -#~ "Để chạy hệ thống cài đặt trên máy kiểu S/390, cần thiết một thiết lập " -#~ "mạng và phiên chạy SSH hoạt động." - -#~ 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 an ssh session which will launch the standard " -#~ "installation system." -#~ msgstr "" -#~ "Tiến trình khởi động bắt đầu với bước thiết lập mạng mà nhắc bạn với vài " -#~ "tham số mạng. Nếu việc thiết lập này là thành công, bạn sẽ đăng nhập vào " -#~ "hệ thống bằng cách sở khởi một phiên chạy SSH mà sẽ khởi chạy hệ thống " -#~ "cài đặt chuẩn." - -#~ msgid "s390 Boot Parameters" -#~ msgstr "Tham số khởi động S/390" - -#~ 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 Device Drivers and Installation Commands for more " -#~ "information about S/390-specific boot parameters." -#~ msgstr "" -#~ "Trên máy kiểu S/390, bạn có thể phụ thêm các tham số khởi động vào tập " -#~ "tin parm. Tập tin này có dạng thức hoặc ASCII hoặc " -#~ "EBCDIC. Xem Các trình điều khiển thiết " -#~ "bị và lệnh cài đất để tìm thông tin thêm về tham số khởi động đặc " -#~ "trưng cho máy kiểu S/390." - -#~ msgid "" -#~ "Currently, the only &arch-title; subarchitectures that support CD-ROM " -#~ "booting are PReP and New World PowerMacs. On PowerMacs, hold the " -#~ "c key, or else the combination of Command, Option, Shift, and " -#~ "Delete keys together while booting to boot from the CD-" -#~ "ROM." -#~ msgstr "" -#~ "Hiện thời, những kiến trúc phụ kiểu &arch-title; duy nhất hỗ trợ khả năng " -#~ "khởi động từ đĩa CD-ROM là máy PReP và PowerMac kiểu mới. Trên máy " -#~ "PowerMac, hãy bấm giữ hoặc phím c, hoặc tổ hợp phím " -#~ "Cmd, Option, Shift, và " -#~ "Delete trong khi khởi động, để khởi động từ đĩa CD-ROM." - -#~ 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 "" -#~ "Máy PowerMac kiểu cũ sẽ không khởi động từ đĩa CD-ROM Debian, vì máy kiểu " -#~ "cũ này ngờ một trình điều khiển khởi động đĩa CD bộ nhớ ROM của MacOS nằm " -#~ "trên đĩa CD khởi động, và chưa có phiên bản phần mềm tự do của trình điều " -#~ "khiển này. Mọi hệ thống kiểu cũ có ổ đĩa mềm, vậy bạn hãy sử dụng ổ đĩa " -#~ "mềm để khởi chạy trình cài đặt, rồi chỉ trình cài đặt tới đĩa CD để lấy " -#~ "các tập tin cần thiết." - -#~ 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 for booting from the " -#~ "hard disk, except use the path to yaboot on the CD at " -#~ "the OF prompt, such as" -#~ msgstr "" -#~ "Nếu hệ thống của bạn không khởi động trực tiếp từ đĩa CD-ROM, vẫn còn có " -#~ "khả năng sử dụng đĩa CD đó để cài đặt hệ thống. Trên máy Mac kiểu mới, " -#~ "bạn cũng có thể nhập một lệnh OpenFirmware để tự khởi động từ đĩa CD-ROM. " -#~ "Hãy theo hướng dẫn trong để khởi động " -#~ "từ đĩa cứng, trừ tại dấu nhắc OpenFirmware cần phải nhập đường dẫn đến " -#~ "yaboot nằm trên đĩa CD đó." - -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "0 > boot cd:,\\install\\yaboot" -#~ msgstr "0 > boot cd:,\\install\\yaboot" - -#~ msgid "Booting from Hard Disk" -#~ msgstr "Khởi động từ đĩa cứng" - -#~ msgid "Booting CHRP from OpenFirmware" -#~ msgstr "Khởi động CHRP từ OpenFirmware" - -#~ msgid "Not yet written." -#~ msgstr "Chưa ghi." - -#~ msgid "Booting OldWorld PowerMacs from MacOS" -#~ msgstr "Khởi động PowerMac kiểu cũ từ MacOS" - -#~ msgid "" -#~ "If you set up BootX in , you can use it " -#~ "to boot into the installation system. Double click the BootX application icon. Click on the Options " -#~ "button and select Use Specified RAM Disk. This will " -#~ "give you the chance to select the ramdisk.image.gz " -#~ "file. You may need to select the No Video Driver " -#~ "checkbox, depending on your hardware. Then click the Linux button to shut down MacOS and launch the installer." -#~ msgstr "" -#~ "Nếu bạn đã thiết lập BootX trong , lúc " -#~ "này bạn có thể sử dụng nó để khởi động vào hệ thống cài đặt. Hãy nhấn đôi " -#~ "vào biểu tượng ứng dụng BootX. Nhấn vào cái nút " -#~ "Options (tùy chọn) rồi chọn Use " -#~ "Specified RAM Disk (dùng đĩa bộ nhớ RAM đã xác định). Việc này " -#~ "cũng sẽ cho bạn có dịp chọn tập tin ramdisk.image.gz. Có lẽ bạn cần phải bật hộp chọn No Video Driver (không có trình điều khiển ảnh động), phụ thuộc vào phần cứng " -#~ "riêng của bạn. Sau đó, hãy nhấn vào cái nút Linux " -#~ "để tắt hệ điều hành MacOS và khởi chạy trình cài đặt &d-i;." - -#~ msgid "Booting NewWorld Macs from OpenFirmware" -#~ msgstr "Khởi động Mac kiểu mới từ OpenFirmware" - -#~ msgid "" -#~ "You will have already placed the vmlinux, " -#~ "initrd.gz, yaboot, and " -#~ "yaboot.conf files at the root level of your HFS " -#~ "partition in . Restart the computer, " -#~ "and immediately (during the chime) hold down the Option, " -#~ "Command (cloverleaf/Apple), o, and " -#~ "f keys all together. After a few seconds you will be " -#~ "presented with the Open Firmware prompt. At the prompt, type " -#~ "\n" -#~ "0 > boot hd:x,yaboot\n" -#~ " replacing x 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 ide0: instead of hd:. In a few more seconds you will see a yaboot prompt " -#~ "\n" -#~ "boot:\n" -#~ " At yaboot's boot: prompt, " -#~ "type either install or install " -#~ "video=ofonly followed by a &enterkey;. The " -#~ "video=ofonly argument is for maximum " -#~ "compatibility; you can try it if install doesn't " -#~ "work. The Debian installation program should start." -#~ msgstr "" -#~ "Trong , bạn đã chèn những tập tin " -#~ "vmlinux, initrd.gz, " -#~ "yaboot, và yaboot.conf tại lớp " -#~ "gốc của phân vùng HFS. Hãy khởi động lại máy tính, và bấm giữ ngay (trong " -#~ "khi máy tính rung chuông) tổ hợp phím Option, " -#~ "Command (⌘), o, và f " -#~ "đều cùng lúc. Sau vài giây, bạn sẽ xem dấu nhắc Open Firmware (phần vững " -#~ "mở). Tại dấu nhắc đó, hãy gõ \n" -#~ "0 > boot hd:x,yaboot\n" -#~ " thay thếx bằng số " -#~ "hiệu phân vùng HFS nơi bạn đã để tập tin hạt nhân và yaboot, rồi bấm phím " -#~ "&enterkey;. Trên một số máy riêng, có lẽ bạn cần phải nhập " -#~ "ide0: thay cho hd:. Sau vài " -#~ "giây nữa, bạn sẽ xem dấu nhắc yaboot \n" -#~ "boot:\n" -#~ " Tại dấu nhắc boot: (khởi " -#~ "động) của yaboot, hãy gõ hoặc install (cài đặt) " -#~ "hoặc install video=ofonly (cài đặt ảnh động=của " -#~ "chỉ) rồi bấm phím &enterkey;. Đối số video=ofonly " -#~ "có ích để tương thích tối đa; bạn có thể thử nó nếu lệnh " -#~ "install độc lập không hoạt động được. Sau đó, " -#~ "chương trình cài đặt Debian nên khởi chạy." - -#~ msgid "Booting from USB memory stick" -#~ msgstr "Khởi động từ thanh bộ nhớ USB" - -#~ msgid "" -#~ "Currently, NewWorld PowerMac systems are known to support USB booting." -#~ msgstr "" -#~ "Hiện thời, máy PowerMac kiểu mới được biết là hỗ trợ khả năng khởi động " -#~ "bằng USB." - -#~ msgid "" -#~ "Make sure you have prepared everything from . 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 " -#~ "Command Option o f all together while booting (see " -#~ ")." -#~ msgstr "" -#~ "Hãy kiểm tra xem bạn đã chuẩn bị mọi thứ được diễn tả trong . Để khởi động hệ thống Mac từ thanh USB, bạn sẽ cần " -#~ "phải sử dụng dấu nhắc Open Firmware, vì Open Firmware không tìm kiếm qua " -#~ "thiết bị sức chứa USB theo mặc định. Để truy cập dấu nhắc đó, hãy bấm giữ " -#~ "tổ hợp phím Cmd Option " -#~ "o f đều cùng lúc trong khi " -#~ "khởi động (xem )." - -#~ msgid "" -#~ "You will need to work out where the USB storage device appears in the " -#~ "device tree, since at the moment ofpath cannot work " -#~ "that out automatically. Type dev / ls and " -#~ "devalias 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 usb0/disk, " -#~ "usb0/hub/disk, /pci@f2000000/usb@1b,1/" -#~ "disk@1, and /pci@f2000000/usb@1b,1/hub@1/disk@1 work." -#~ msgstr "" -#~ "Bạn sẽ cần phải tìm biết vị trí của thiết bị sức chứa USB trong cây thiết " -#~ "bị, vì hiện thời công cụ ofpath không thể tính tự động " -#~ "thông tin này. Hãy gõ lệnh dev / ls (liệt kê thiết " -#~ "bị) và devalias (bí danh thiết bị) tại dấu nhắc " -#~ "Open Firmware, để xem danh sách các thiết bị và bí danh thiết bị đã biết. " -#~ "Trên máy tính của tác giả, dùng nhiều kiểu thanh USB khác nhau, đường dẫn " -#~ "như usb0/disk, usb0/hub/disk, " -#~ "/pci@f2000000/usb@1b,1/disk@1 và /" -#~ "pci@f2000000/usb@1b,1/hub@1/disk@1 hoạt động được." +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"Cũng như tùy chọn 1, những bước này khởi chạy bộ tải khởi động Debian mà sẽ " +"hiển thị trang trình đơn cho bạn chọn hạt nhân và các tùy chọn tương ứng. " +"Bạn cũng có khả năng nhập lệnh ngắn hơn fsn:elilo vào dấu nhắc trình bao. Hãy tiếp tục đến giai " +"đoạn chọn hạt nhân khởi động và các tùy chọn tương ứng." + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "Cài đặt bằng bàn điều khiển nối tiếp" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"Bạn có thể chọn thực hiện tiến trình cài đặt bằng bộ trình bày và bàn phím, " +"hay bằng sự kết nối kiểu nối tiếp. Để sử dụng thiết lập bộ trình bày và bàn " +"phím, hãy bật một tùy chọn chứa chuỗi [VGA console] (bàn điều khiển VGA). Để " +"cài đặt qua sự kết nối kiểu nối tiếp, hãy bật một tùy chọn chứa chuỗi " +"[BỐT baud serial console], (bàn điều khiển nối " +"tiếp bốt) mà BỐT là tốc độ truyền của bàn điều " +"khiển nối tiếp đó. Trên thiết bị ttyS0, mục trình đơn cho những giá trị tốc " +"độ truyền thường nhất đã được định sẵn." + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"Trong phần lớn hoàn cảnh, bạn sẽ muốn đặt bộ cài đặt sử dụng cùng một tốc độ " +"truyền với sự kết nối đến bàn điều khiển EFI. Nếu bạn chưa biết được giá trị " +"này, bạn có thể lấy nó bằng cách nhập lệnh baud (bốt) vào " +"trình bao EFI." + +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"Nếu không có tùy chọn sẵn sàng đã được cấu hình cho thiết bị nối tiếp hay " +"tốc độ truyền bạn muốn dùng, bạn có khả năng đặt quyền cao hơn thiết lập bàn " +"điều khiển dành cho một của những tùy chọn trình đơn đã có. Chẳng hạn, để " +"dùng bàn điều khiển 57600 bốt qua thiết bị ttyS1, hãy nhập lệnh " +"console=ttyS1,57600n8 vào cửa sổ nhập thô Boot:" +" (khởi động)." + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" +"Phần lớn máy kiểu IA-64 có sẵn giá trị bàn điều khiển là 9600 bốt. Giá trị " +"này hơi chậm nên tiến trình cài đặt bình thường sẽ mất thời gian đáng kể để " +"vẽ mỗi màn hình. Đề nghị bạn hoặc tăng lên tốc độ truyền (bốt) được dùng để " +"thi hành tiến trình cài đặt, hoặc thực hiện việc cài đặt kiểu Chế Độ Nhập " +"Thô (Text Mode). Xem trình đơn trợ giúp Params (Tham " +"số) để tìm hướng dẫn về cách khởi chạy trình cài đặt trong Chế Độ Nhập Thô." + +#. Tag: para +#: boot-installer.xml:1419 +#, 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 "" +"Nếu bạn chọn kiểu bàn điều khiển không đúng, bạn vẫn còn có khả năng chọn " +"hạt nhân và nhập tham số tương ứng, nhưng mà cả bộ trình bày lẫn cách nhập " +"đều sẽ bị tắt một khi hạt nhân khởi chạy, nên cần thiết bạn khởi động lại để " +"bất đầu cài đặt." + +#. Tag: title +#: boot-installer.xml:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "Chọn hát nhân khởi động và các tùy chọn tương ứng" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" +"Bộ tải khởi động sẽ hiển thị đơn chứa danh sách trình đơn và cửa sổ nhập thô " +"chứa dấu nhắc Boot: (khởi động). Phím mũi tên cho bạn " +"chọn mục nào trong trình đơn, và đoạn nào được gõ bằng bàn phím sẽ xuất hiện " +"trong cửa sổ nhập thô. Cũng có một số màn hình trợ giúp có thể được hiển thị " +"bằng cách bấm phím chức năng (F1 ...) thích hợp. Màn hình trợ giúp " +"General (Chung) diễn tả mỗi mục chọn trong trình đơn, " +"còn màn hình Params (Tham số) giải thích những tùy " +"chọn dòng lệnh thường dùng." + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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 "" +"Xem màn hình General (Chung) để tìm mô tả về các hạt " +"nhân và chế độ cài đặt thích hợp nhất với tiến trình cài đặt vào máy của " +"bạn. Xem thêm bên dưới, để tìm tham số thêm " +"nào bạn muốn đặt trong cửa sổ nhập thô Boot: (khởi " +"động). Bạn sẽ chọn một phiên bản hạt nhân quyết định phiên bản hạt nhân được " +"dùng trong cả tiến trình cài đặt lẫn hệ thống sẽ được cài đặt. Nếu bạn gặp " +"khó khăn trong tiến trình cài đặt, bạn sẽ có thể gặp cùng khó khăn khi chạy " +"hệ thống được cài đặt." + +#. Tag: para +#: boot-installer.xml:1460 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "" +"Bằng phím mũi tên, hãy chọn phiên bản hạt nhân và chế độ cài đặt thích hợp " +"nhất với điều kiện của máy tính của bạn." -#~ msgid "" -#~ "Having worked out the device path, use a command like this to boot the " -#~ "installer: \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " The 2 matches the " -#~ "Apple_HFS or Apple_Bootstrap partition onto which you copied the boot " -#~ "image earlier, and the ,\\\\:tbxi part instructs " -#~ "Open Firmware to boot from the file with an HFS file type of \"tbxi\" (i." -#~ "e. yaboot) in the directory previously blessed with " -#~ "hattrib -b." -#~ msgstr "" -#~ "Một khi bạn đã tìm biết đường dẫn thiết bị, để khởi động trình cài đặt " -#~ "hãy nhập lệnh như : \n" -#~ "boot usb0/disk:2,\\" -#~ "\\:tbxi\n" -#~ " Con số thay thế 2 " -#~ "khớp phân vùng kiểu Apple_HFS hay " -#~ "Apple_Bootstrap nơi bạn đã sao chép ảnh khởi động, " -#~ "còn phần ,\\\\:tbxi báo Open Firmware khởi động từ " -#~ "tập tin có kiểu tập tin HFS « tbxi » (tức là yaboot) " -#~ "nằm trong thư mục đã được hiệu lực bằng lệnh hattrib -b." +#. Tag: para +#: boot-installer.xml:1465 +#, 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 "" +"Sau đó, hãy nhập tham số khởi động nào đã muốn bằng cách gõ vào bàn phím. " +"Đoạn đã gõ sẽ được hiển thị trực tiếp trong cửa sổ nhập thô. Ở đây bạn có " +"thể xác định tham số hạt nhân như thiết lập bàn điều khiển nối tiếp." -#~ msgid "" -#~ "The system should now boot up, and you should be presented with the " -#~ "boot: prompt. Here you can enter optional boot " -#~ "arguments, or just hit &enterkey;." -#~ msgstr "" -#~ "Sau đó, hệ thống nên khởi động được, và bạn nên thấy dấu nhắc " -#~ "boot: (khởi động). Vào đây bạn có thể nhập một số đối số " -#~ "khởi động tùy chọn, hoặc chỉ bấm phím &enterkey;." +#. Tag: para +#: boot-installer.xml:1472 +#, no-c-format +msgid "" +"Press ENTER. 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 "" +"Bấm phím &enterkey;. Cú này sẽ tải và khởi chạy hạt nhân. Hạt nhân sẽ hiển " +"thị thông điệp sở khởi thường rồi màn hình thứ nhất của tiến trình cài đặt " +"Debian." -#~ 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 ." -#~ msgstr "" -#~ "Phương pháp khởi động này là mới, có lẽ bạn sẽ gặp khó khăn khi thử dùng " -#~ "nó trên một số hệ thống kiểu mới riêng. Nếu bạn có phải gặp khó khăn, xin " -#~ "hãy gởi báo cáo cài đặt, như được diễn tả trong ." +#. Tag: para +#: boot-installer.xml:1481 boot-installer.xml:1617 +#, 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 "" +"Sau đó, hãy tới chương kế tiếp, để tiếp tục tiến trình cài đặt bằng cách " +"thiết lập miền địa phương (gồm ngôn ngữ), mạng và phân vùng đĩa." -#~ msgid "Currently, PReP and New World PowerMac systems support netbooting." -#~ msgstr "" -#~ "Hiện thời, các hệ thống PReP và PowerMac kiểu mới có hỗ trợ khả năng khởi " -#~ "động qua mạng." +#. Tag: para +#: boot-installer.xml:1492 +#, fuzzy, no-c-format +msgid "" +"Booting an IA-64 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 "" +"Việc khởi động hệ thống kiểu IA64 qua mạng giống như việc khởi động từ đĩa " +"CD. Sự khác nhau duy nhất là cách tải hạt nhân cài đặt. Bộ quản lý khởi động " +"EFI có khả năng tải và khởi chạy chương trình từ máy phục vụ trên mạng. Một " +"khi hạt nhân cài đặt đã được tải và khởi động, tiến trình cài đặt hệ thống " +"sẽ tiếp tục qua cùng những bước với tiến trình cài đặt từ đĩa CD, với ngoài " +"lệ là các gói của bản cài đặt cơ sở sẽ được tải qua mạng hơn là qua ổ đĩa CD." + +#. Tag: para +#: boot-installer.xml:1526 +#, fuzzy, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" +"Việc khởi động hệ thống kiểu ia64 qua mạng cần thiết hai hành động đặc trưng " +"cho kiến trúc đó. Trên máy phục vụ khởi động, hai dịch vụ DHCP và TFTP phải " +"được cấu hình để phát elilo. Còn trên máy khách, một tùy " +"chọn khởi động mới phải được xác định trong bộ quản lý khởi động EFI để hiệu " +"lực khả năng tải qua mạng." + +#. Tag: title +#: boot-installer.xml:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "Cấu hình máy phục vụ" + +#. Tag: para +#: boot-installer.xml:1538 +#, fuzzy, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" +"Một mục nhập TFTP thích hợp với khả năng khởi động hệ thống kiểu ia64 qua " +"mạng có vẻ như :\n" +"host banhdauxanh {\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" +" Ghi chú rằng mục đích là làm cho elilo." +"efi chạy trên máy khách." + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" +"Hãy giải nén tập tin netboot.tar.gz vào thư mục được " +"dùng như là gốc của trình phục vụ TFTP. Các thư mục gốc TFTP thường bao gồm " +"/var/lib/tftp và /tftpboot. Việc " +"giải nén này sẽ tạo cây thư mục debian-installer (bản " +"cài đặt Debian) chứa các tập tin khởi động thích hợp với hệ thống kiểu IA-64." -#~ msgid "" -#~ "On machines with Open Firmware, such as NewWorld Power Macs, enter the " -#~ "boot monitor (see ) and use the " -#~ "command boot enet:0. PReP and CHRP boxes may have " -#~ "different ways of addressing the network. On a PReP machine, you should " -#~ "try boot server_ipaddr," -#~ "file,client_ipaddr." -#~ msgstr "" -#~ "Trên máy chứa Open Firmware, như PowerMac kiểu mới, hãy vào bộ theo dõi " -#~ "khởi động (xem ) và nhập lệnh " -#~ "boot enet:0. Máy kiểu PReP và CHRP có lẽ liên lạc với " -#~ "mạng bằng cách khác nhau. Trên máy kiểu PReP, bạn nên thử nhập lệnh " -#~ "boot địa_chỉ_IP_máy_phục_vụ," -#~ "tập_tin,địa_chỉ_IP_máy_khách." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: screen +#: boot-installer.xml:1558 +#, 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 "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" + +#. Tag: para +#: boot-installer.xml:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" +"Kho nén netboot.tar.gz chứa tập tin cấu hình " +"elilo.conf nên hoạt động được với phần lớn tổ hợp phần " +"cứng. Tuy nhiên, nếu bạn cần phải sửa đổi tập tin này, nó nằm trong thư mục " +"debian-installer/ia64/. Có thể duy trì tập tin cấu hình " +"riêng cho mỗi máy khách, bằng cách đặt tên là địa chỉ IP dạng thập lục của " +"máy khách, cộng hậu tố .conf (cấu hình) thay cho tên " +"tập tin gốc elilo.conf. Xem tài liệu có sẵn trong gói " +"elilo để tìm chi tiết." + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "Cấu hình máy khách" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" +"Để cấu hình máy khách để hỗ trợ khả năng khởi động qua dịch vụ TFTP, hãy bắt " +"đầu bằng cách khởi động tới EFI rồi vào Boot Option Maintenance " +"Menu (trình đơn bảo dưỡng tùy chọn khởi động). " +" Thêm một tùy chọn khởi động. " +" Sau đó, bạn nên thấy đoạn (một hay nhiều dòng) dạng " +"Load File [Acpi()/.../Mac()]. Nếu có nhiều mục " +"nhập như thế, hãy chọn điều chứa địa chỉ MAC của giao diện từ đó bạn sẽ khởi " +"động. Dùng phím mũi tên để tô sáng sự chọn riêng, rồi bấm &enterkey;. Đặt mục nhập có tên Netboot (khởi động qua mạng) hay tương tự, lưu, rồi thoát về trình đơn " +"tùy chọn khởi động. Lúc đó, bạn nên thấy " +"tùy chọn khởi động mới đã được tạo. Việc chọn nó nên khởi đầu truy vấn DHCP, " +"chỉ dẫn đến việc tải tập tin elilo.efi qua TFTP từ máy " +"phục vụ." + +#. Tag: para +#: boot-installer.xml:1608 +#, 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 "" +"Bộ tải khởi động sẽ hiển thị dấu nhắc riêng sau khi nó tải về và xử lý tập " +"tin cấu hình riêng. Tại điểm thời này, tiến trình cài đặt theo cùng những " +"bước với sự cài đặt từ đĩa CD. Hãy chọn một tùy chọn khởi động (như nêu " +"trên) và, khi hạt nhân đã cài đặt chính nó qua mạng, nó sẽ khởi chạy trình " +"cài đặt Debian." + +#. Tag: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "Chọn phương pháp cài đặt" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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 "" +"Một số kiến trúc phụ kiểu &arch-title; có tùy chọn khởi động bằng hạt nhân " +"phiên bản hoặc 2.4.x hoặc 2.2.x. Khi bạn gặp tùy chọn này, hãy thử dùng hạt " +"nhân 2.4.x. Tiến trình cài đặt dùng hạt nhân 2.4.x nên cần thiết bộ nhớ ít " +"hơn, vì khả năng hỗ trợ hạt nhân 2.2.x cần thiết đĩa RAM có kích cỡ cố định, " +"còn 2.4.x dùng hệ thống tập tin tạm thời (tmpfs)." + +#. Tag: para +#: boot-installer.xml:1640 +#, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "" +"Nếu bạn dùng hạt nhân Linux phiên bản 2.2.x, bạn cũng cần phải xác định tham " +"số hạt nhân kích cỡ đĩa bộ nhớ RAM &ramdisksize;." -#~ 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 "" -#~ "Khả năng khởi động từ đĩa mềm được hỗ trợ trên kiến trúc kiểu &arch-" -#~ "title;, dù nó thường thích hợp chỉ trên máy kiểu cũ. Máy kiểu mới không " -#~ "có ổ đĩa mềm, và khả năng khởi động từ ổ đĩa mềm USB đã gắn kết không " -#~ "được hỗ trợ." +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "" +"Hãy kiểm tra xem bạn đã chọn tham số hạt nhân root=/dev/ram." -#~ msgid "" -#~ "To boot from the boot-floppy-hfs.img floppy, place " -#~ "it in floppy drive after shutting the system down, and before pressing " -#~ "the power-on button." -#~ msgstr "" -#~ "Để khởi động từ đĩa mềm boot-floppy-hfs.img, hãy nạp " -#~ "nó vào ổ đĩa mềm sau khi tắt hệ thống, còn trước khi bấm cái nút mở điện." +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"Nếu bạn gặp khó khăn, xem Hỏi Đáp cts's " +"&arch-title; debian-installer FAQ." -#~ 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 "" -#~ "Khi khởi động máy Apple Mac có ổ đĩa mềm: đĩa mềm được nạp vào ổ đĩa " -#~ "trước khi khởi động sẽ có ưu tiên khởi động cao nhất. Đĩa mềm không chứa " -#~ "hệ thống khởi động hợp lệ sẽ bị đẩy ra, sau đó máy sẽ kiểm tra tìm phân " -#~ "vùng đĩa cứng có khả năng khởi động." +# Name: don't translate / Tên: đừng dịch +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "Amiga" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"Khi dùng máy kiểu Amiga, chỉ có sẵn sàng một phương pháp cài đặt: bằng đĩa " +"cứng (xem ). Tức là không thể khởi " +"động từ đĩa CD-ROM." -#~ msgid "" -#~ "After booting, the root.bin 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 "" -#~ "Sau khi khởi động, đĩa mềm root.bin được yêu cầu. " -#~ "Hãy nạp đĩa mềm gốc đó, rồi bấm phím &enterkey;. Chương trình cài đặt " -#~ "được khởi chạy tự động sau khi hệ thống gốc đã được tải vào bộ nhớ." +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "" +"Amiga does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"Máy kiểu Amiga hiện thời không hoạt động được với bogl, vậy nếu bạn gặp lỗi " +"bogl, bạn cần phải nhập tham số hạt nhân fb=false." -#~ msgid "PowerPC Boot Parameters" -#~ msgstr "Tham số khởi động máy PowerPC" +# Name: don't translate / Tên: đừng dịch +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "Atari" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "" +"The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" +"Khi dùng máy kiểu Atari, bạn có thể khởi chạy trình cài đặt Debian hoặc từ " +"đĩa cứng (xem ) hoặc từ đĩa mềm (xem ). Tức là không thể khởi động từ " +"đĩa CD-ROM." + +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "" +"Atari does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"Máy kiểu Atari hiện thời không hoạt động được với bogl, vậy nếu bạn gặp lỗi " +"bogl, bạn cần phải nhập tham số hạt nhân fb=false." -#~ 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 " -#~ "video=atyfb:vmode:6 , which will select that mode " -#~ "for most Mach64 and Rage video hardware. For Rage 128 hardware, this " -#~ "changes to video=aty128fb:vmode:6 ." -#~ msgstr "" -#~ "Nhiều bộ trình bày Apple cũ hơn sử dụng chế độ 640x480 67Hz. Nếu ảnh động " -#~ "có vẻ lệch trên một bộ trình bày Apple cũ hơn, hãy thử phụ thêm đối số " -#~ "khởi động video=atyfb:vmode:6, mà sẽ chọn chế độ " -#~ "đó cho phần lớn phần cứng ảnh động kiểu Mach64 và Rage. Đối với phần cứng " -#~ "kiểu Rage 128, đối số này thay đổi thành video=aty128fb:" -#~ "vmode:6 ." +# Name: don't translate / Tên: đừng dịch +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "BVME6000" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" +"Đối với máy kiểu BVME6000, trình cài đặt có thể được khởi chạy hoặc từ đĩa " +"CD-ROM (xem ), hoặc từ đĩa mềm (xem ), hoặc qua mạng (xem )." -#~ msgid "" -#~ "On machines with OpenBoot, simply enter the boot monitor on the machine " -#~ "which is being installed (see ). Use " -#~ "the command boot net to boot from a TFTP and RARP " -#~ "server, or try boot net:bootp or boot " -#~ "net:dhcp to boot from a TFTP and BOOTP or DHCP server. Some " -#~ "older OpenBoot revisions require using the device name, such as " -#~ "boot le(); these probably don't support BOOTP nor " -#~ "DHCP." -#~ msgstr "" -#~ "Trên máy chứa OpenBoot, đơn giản hãy vào bộ theo dõi khởi động trên máy " -#~ "nơi đang cài đặt (xem ). Hãy nhập " -#~ "lệnh boot net (khởi động mạng) để khởi động từ máy " -#~ "phục vụ TFTP và RARP, hoặc thử nhập boot net:bootp " -#~ "hay boot net:dhcp để khởi động từ máy phục vụ TFTP " -#~ "và BOOTP hay DHCP. Một số bản sửa đổi OpenBoot cũ hơn cần thiết bạn nhập " -#~ "tên của thiết bị, v.d. boot le(); rất có thể là " -#~ "chúng không hỗ trợ được BOOTP hay DHCP." +# Name: don't translate / Tên: đừng dịch +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "Macintosh (Apple Mac)" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"). In other words the cdrom is not " +"bootable. Macs do not have a working 2.4.x kernel." +msgstr "" +"Phương pháp cài đặt duy nhất sẵn sàng cho máy Mac là từ đĩa cứng (xem ). Tức là không có khả năng khởi động " +"được từ đĩa CD-ROM. Chưa có hạt nhân phiên bản 2.4.x hoạt động " +"được với máy kiểu Mac." + +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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 "" +"Nếu phần cứng của bạn sử dụng một mạch nối SCSI dựa vào 53c9x, có lẽ bạn cần " +"phải nhập tham số hạt nhân mac53c9x=1,0. Phần cứng có " +"hai mạch nối SCSI như vậy, v.d. máy Quadra 950, cần thiết bạn nhập tham số " +"mac53c9x=2,0 thay thế. Hoặc có thể xạc định tham số " +"mac53c9x=-1,0, mà duy trì khả năng phát hiện tự động, " +"còn tắt khả năng ngắt kết nối SCSI. Ghi chú rằng việc xác định tham số này " +"cần thiết chỉ nếu bạn có nhiều đĩa cứng; nếu không (chỉ có một đĩa), hệ " +"thống sẽ chạy nhanh hơn nếu bạn không xác định nó." + +#. Tag: title +#: boot-installer.xml:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "MVME147 và MVME16x" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" +"Đối với máy kiểu MVME147 và MVME16x, trình cài đặt có thể được khởi chạy " +"hoặc từ đĩa mềm (xem ) hoặc qua mạng " +"(xem phần ). Tức là không có khả năng " +"khởi động được từ đĩa CD-ROM." -#~ msgid "" -#~ "Most OpenBoot versions support the boot cdrom " -#~ "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 "" -#~ "Phần lớn phiên bản OpenBoot hỗ trợ lệnh boot cdrom " -#~ "(khởi động đĩa CD-ROM) mà đơn giản là bí danh để khởi động từ thiết bị " -#~ "SCSI trên ID 6 (hay cái chủ phụ trên máy dựa vào IDE). Có lẽ bạn cần phải " -#~ "nhập tên thiết bị thật với phiên bản OpenBoot cũ hơn không hỗ trợ lệnh " -#~ "đặc biệt này. Ghi chú rằng một số vấn đề đã được thông báo trên máy kiểu " -#~ "Sun4m (v.d. máy Sparc 10 và Sparc 20) khi khởi động từ đĩa CD-ROM." +# Name: don't translate / Tên: đừng dịch +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" +"Phương pháp cài đặt duy nhất sẵn sàng cho máy kiểu Q40/Q60 là từ đĩa cứng " +"(xem ). Tức là không có khả năng " +"khởi động được từ đĩa CD-ROM." + +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "Khởi động từ đĩa cứng" + +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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 "" +"Việc khởi động từ hệ điều hành tồn tại thường là một tùy chọn có ích; còn " +"đối với một số hệ thống riêng, nó là phương pháp cài đặt duy nhất được hỗ " +"trợ." -#~ msgid "" -#~ "To boot from floppy on a Sparc, use \n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Be warned that the newer Sun4u (ultra) " -#~ "architecture does not support floppy booting. A typical error message is " -#~ "Bad magic number in disk label - Can't open disk label " -#~ "package. 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 "" -#~ "Để khởi động từ đĩa mềm trên máy kiểu Sparc, hãy nhập lệnh: " -#~ "\n" -#~ "Stop-A -> OpenBoot: \"boot floppy\"\n" -#~ " Cảnh báo : kiến trúc Sun4u (ultra) mới hơn " -#~ "không hỗ trợ khả năng khởi động từ đĩa mềm. Thông điệp lỗi thường là " -#~ "Bad magic number in disk label - Can't open disk label " -#~ "package (số ma thuật sai nằm trong nhãn đĩa nên không " -#~ "thể mở gói nhãn đĩa). Hơn nữa, một số mô hình Sun4c riêng (v.d. IPX) " -#~ "không hỗ trợ ảnh được nén nằm trên đĩa đó nên các mô hình này cũng không " -#~ "được hỗ trợ." +#. Tag: para +#: boot-installer.xml:1769 boot-installer.xml:2367 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"Trong ), bạn đã tải về và định vị những " +"tập tin cần thiết để khởi chạy trình cài đặt từ đĩa cứng." -#~ 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 ." -#~ msgstr "" -#~ "Vài máy kiểu Sparc (v.d. Ultra 10) có lỗi OBP chặn khởi động (thay vào " -#~ "không hỗ trợ khả năng khởi động bằng cách nào cả). Bản cập nhật OBP thích " -#~ "hợp có thể được tải như là mã nhận diện sản phẩm ID 106121 xuống ." +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" +"Ít nhất sáu đĩa bộ nhớ RAM khác nhau có thể được dùng để khởi động từ đĩa " +"cứng: ba kiểu khác nhau, mỗi kiểu có và không có khả năng hỗ trợ hạt nhân " +"phiên bản 2.2.x (xem bản kê khai để tìm chi tiết)." + +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" +"Ba kiểu đĩa RAM khác nhau là cdrom (đĩa CD-ROM), " +"hd-media (vật chứa đĩa cứng), và nativehd (đĩa cứng sở hữu). Những đĩa RAM này chỉ khác biệt trong nguồn của " +"những gói cài đặt. Đĩa RAM kiểu cdrom sử dụng một đĩa " +"CD-ROM để lấy các gói cài đặt Debian. Còn đĩa RAM kiểu hd-media sử dụng một tập tin ảnh ISO của đĩa CD-ROM hiện thời nằm trên đĩa " +"cứng. Cuối cùng, đĩa RAM kiểu nativehd cài đặt gói qua " +"mạng." + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "Khởi động từ AmigaOS" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"Trong Workbench, hãy khởi chạy tiến trình cài đặt Linux " +"bằng cách nhấn đôi vào biểu tượng StartInstall (bất đầu " +"cài đặt) nằm trong thư mục debian." -#~ msgid "" -#~ "If you are booting from the floppy, and you see messages such as " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " then it is possible that floppy booting is " -#~ "simply not supported on your machine." -#~ msgstr "" -#~ "Nếu bạn đang khởi động từ đĩa mềm, và xem thông điệp như " -#~ "\n" -#~ "Fatal error: Cannot read partition\n" -#~ "Illegal or malformed device name\n" -#~ " (lỗi nghiêm trọng: không thể đọc phân vùng, " -#~ "tên thiết bị bất hợp pháp hay dạng sai), có lẽ khả năng khởi động từ đĩa " -#~ "mềm đơn giản không được hỗ trợ trên máy đó." +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" +"Có lẽ bạn cần phải bấm phím &enterkey; hai lần sau khi chương trình cài đặt " +"Amiga đã xuất vài thông tin gỡ lỗi vào cửa sổ. Sau đó, màn hình xảy ra màu " +"xám, cần phải đợi vài giây. Tiếp sau, màn hình màu đen với đoạn màu trắng " +"nên xuất hiện, hiển thị nhiều kiểu thông tin gỡ lỗi hạt nhân. Các thông điệp " +"này có thể cuộn ra quá nhanh để đọc được: không có sao. Sau một hai giây, " +"chương trình cài đặt nên khởi chạy tự động, vậy bạn có thể tiếp tục tới " +"." + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "Khởi động từ Atari TOS" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" +"Trong môi trường làm việc GEM, hãy khởi chạy tiến trình cài đặt Linux bằng " +"cách nhấn đôi vào biểu tượng bootstra.prg nằm trong thư " +"mục debian, rồi nhấn vào cái nút Ok (Được) trong hộp thoại tùy chọn chương trình." + +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" +"Có lẽ bạn cần phải bấm phím &enterkey; sau khi chương trình tải khởi động " +"Atari đã xuất vài thông tin gỡ lỗi vào cửa sổ. Sau đó, màn hình xảy ra màu " +"xám, cần phải đợi vài giây. Tiếp sau, màn hình màu đen với đoạn màu trắng " +"nên xuất hiện, hiển thị nhiều kiểu thông tin gỡ lỗi hạt nhân. Các thông điệp " +"này có thể cuộn ra quá nhanh để đọc được: không có sao. Sau một hai giây, " +"chương trình cài đặt nên khởi chạy tự động, vậy bạn có thể tiếp tục tới " +"." + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "Khởi động từ MacOS" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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 "" +"Bạn cần phải giữ lại hệ điều hành Mac gốc và khởi động từ nó. Chủ " +"yếu rằng khi bạn khởi động hệ điều hành MacOS để chuẩn bị khởi " +"động bộ tải Linux Penguin, bạn bấm giữ phím dài để ngăn " +"cản tải các phần mở rộng của HĐH Mac. Nếu bạn không sử dụng HĐH MacOS, trừ " +"khi khởi động Linux, bạn có thể làm cùng công việc đó bằng cách gỡ bỏ mọi " +"phần mở rộng (Extensions) và bảng điều khiển (Control Panels) ra thư mục hệ " +"thống (System Folder) của HĐH MacOS. Nếu không, có lẽ một số phần mở rộng " +"còn chạy lại thì gây ra lỗi ngẫu nhiên với hạt nhân Linux đang chạy." + +#. Tag: para +#: boot-installer.xml:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" +"Máy kiểu Mac cần thiết bộ tải khởi động Penguin. Nếu bạn " +"không có công cụ giải nén kho kiểu Stuffit (phần mở rộng " +"tập tin .sit), &penguin19.hfs; là một ảnh đĩa cung cấp " +"Penguin đã được giải nén. diễn tả cách sao chép ảnh này vào đĩa mềm." + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." +msgstr "" +"Trong môi trường Desktop của MacOS, hãy khởi chạy tiến trình cài đặt Linux " +"bằng cách nhấn đôi vào biểu tượng Penguin Prefs (tùy " +"thích Penguin) nằm trong thư mụcPenguin. Bộ khởi động " +"Penguin sẽ khởi chạy. Hãy tới mục Settings (thiết lập) nằm trong trình đơn File (tập " +"tin), nhấn vào thanh nhỏ Kernel (hạt nhân). Chọn ảnh " +"kiểu hạt nhân (vmlinuz) và đĩa RAM (initrd." +"gz) đều nằm trong thư mục install (cài đặt) " +"bằng cách nhấn vào cái nút tương ứng bên phải, góc trên, rồi duyệt qua hộp " +"thoại chọn tập tin để tìm tập tin thích hợp." + +#. Tag: para +#: boot-installer.xml:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" +"Để đặt các tham số khởi động trong Penguin, hãy đi tới trình đơn " +"File (tập tin) và chọn mục Settings... (thiết lập), rồi bật thanh nhỏ Options " +"(tùy chọn). Các tham số khởi động có thể được gõ vào vùng nhập chữ. Nếu bạn " +"muốn sử dụng luôn thiết lập này, trong trình đơn File hãy " +"chọn mục Save Settings as Default (lưu thiết lập " +"này là mặc định)." + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"Hãy đóng hộp thoại Settings, lưu thiết lập đó và khởi " +"chạy tiến trình tải khởi động bằng cách chọn mục Boot Now (khởi động ngay bây giờ) nằm trong trình đơn File." + +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" +"Bộ khởi động Penguin sẽ xuất vài thông tin gỡ lỗi vào cửa " +"sổ. Sau đó, màn hình xảy ra màu xám, cần phải đợi vài giây. Tiếp sau, màn " +"hình màu đen với đoạn màu trắng nên xuất hiện, hiển thị nhiều kiểu thông tin " +"gỡ lỗi hạt nhân. Các thông điệp này có thể cuộn ra quá nhanh để đọc được: " +"không có sao. Sau một hai giây, chương trình cài đặt nên khởi chạy tự động, " +"vậy bạn có thể tiếp tục tới ." + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "Khởi động từ Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "FIXME (sửa đi: phần tiếng Anh chưa tạo)" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"Chương trình cài đặt nên khởi chạy tự động, vậy bạn có thể tiếp tục tới " +" bên dưới." -#~ msgid "IDPROM Messages" -#~ msgstr "Thông điệp IDPROM" +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "" +"Hiện thời, kiến trúc phụ kiểu &arch-title; duy nhất hỗ trợ được khả năng " +"khởi động từ đĩa CD-ROM là máy BVME6000." -#~ msgid "" -#~ "If you cannot boot because you get messages about a problem with " -#~ "IDPROM, then it's possible that your NVRAM battery, which " -#~ "holds configuration information for you firmware, has run out. See the " -#~ "Sun NVRAM FAQ for more " -#~ "information." -#~ msgstr "" -#~ "Nếu bạn không thể khởi động vì nhận thông điệp lỗi IDPROM, " -#~ "có lẽ pin NVRAM, mà chứa thông tin cấu hình phần vững, đã hết điện. Xem " -#~ "Hỏi Đáp Sun NVRAM FAQ để tìm " -#~ "thông tin thêm." +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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 "" +"Sau khi khởi động hệ thống kiểu VMEbus, bạn sẽ xem dấu nhắc Boot: (khởi động) của LILO. Tại dấu nhắc đó, hãy nhập một của những đoạn " +"theo đây, để khởi động Linux và bắt đầu tiến trình cài đặt phần mềm Debian " +"chính bằng khả năng mô phỏng thiết bị cuối VT102:" + +#. Tag: para +#: boot-installer.xml:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "" +"gõ i6000 &enterkey; để cài đặt vào máy kiểu BVME4000/6000" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "gõ i162 &enterkey; để cài đặt vào máy kiểu MVME162" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "" +"gõ i167 &enterkey; để cài đặt vào máy kiểu MVME166/167" -#~ 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 "" -#~ "Tham số khởi động là tham số hạt nhân Linux thường được dùng để đảm bảo " -#~ "thiết bị ngoại vi được xử lý cho đúng. Bình thường, hạt nhân có khả năng " -#~ "phát hiện tự động thông tin về các ngoại của máy tính. Tuy nhiên, trong " -#~ "một số trường hợp, bạn cần phải giúp đỡ hạt nhân một ít." +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"Bạn cũng có thể phụ thêm chuỗi TERM=vt100 để sử dụng khả " +"năng mô phỏng thiết bị cuối VT100, v.d. i6000 TERM=vt100 &enterkey;." -#~ 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 "" -#~ "Nếu đây là lần đầu tiên khởi động hệ thống này, hãy thử nhập các tham số " -#~ "khởi động mặc định (tức là không thử đặt tham số thêm) và theo dõi hoạt " -#~ "động. Rất có thể là máy sẽ hoạt động được vậy bạn không cần thêm gì. Nếu " -#~ "không, bạn có thể khởi động lại sau, cũng tìm tham số đặc biệt có thể báo " -#~ "hệ thống biết về phần cứng đó." +#. Tag: para +#: boot-installer.xml:2049 +#, no-c-format +msgid "" +"For most &arch-title; architectures, booting from a local filesystem is the " +"recommended method." +msgstr "" +"Đối với phần lớn kiến trúc kiểu &arch-title;, phương pháp khuyến khích là " +"khởi động từ hệ thống tập tin cục bộ." -#~ msgid "" -#~ "Information on many boot parameters can be found in the Linux BootPrompt " -#~ "HOWTO, including tips for obscure hardware. This section contains " -#~ "only a sketch of the most salient parameters. Some common gotchas are " -#~ "included below in ." -#~ msgstr "" -#~ "Thông tin về nhiều tham số khởi động khác nhau nằm trong tài liệu dấu " -#~ "nhắc khởi động Linux Thế Nào Linux BootPrompt HOWTO, gồm có mẹo về " -#~ "phần cứng không thường. Phần này chứa chỉ bản tóm tắt các tham số nổi bật " -#~ "nhất. Một số vấn đề thường cũng được bao gồm bên dưới trong ." +#. Tag: para +#: boot-installer.xml:2054 +#, 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 "" +"Khả năng khởi động từ đĩa mềm khởi động được hỗ trợ chỉ trên máy kiểu Atari " +"và VME (với ổ đĩa mềm SCSI trên VME) vào lúc này." + +#. Tag: title +#: boot-installer.xml:2070 boot-installer.xml:2117 +#, no-c-format +msgid "SGI TFTP Booting" +msgstr "Khởi động SGI qua TFTP" + +#. Tag: para +#: boot-installer.xml:2071 +#, no-c-format +msgid "" +"After entering the command monitor use \n" +"bootp():\n" +" 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 netaddr environment variable. Type " +"\n" +"unsetenv netaddr\n" +" in the command monitor to do this." +msgstr "" +"Sau khi vào bộ theo dõi lệnh, hãy nhập \n" +"bootp():\n" +" trên máy kiểu SGI để khởi động Linux và bất đầu " +"cài đặt phần mềm Debian. Để làm cho việc này hoạt động được, có lẽ bạn cần " +"phải bỏ đặt biến môi trường netaddr (địa chỉ mạng). Hãy gõ " +"lệnh \n" +"unsetenv netaddr\n" +" trong bộ theo dõi lệnh để làm như thế." + +#. Tag: title +#: boot-installer.xml:2090 boot-installer.xml:2139 boot-installer.xml:2194 +#: boot-installer.xml:2233 +#, no-c-format +msgid "Broadcom BCM91250A and BCM91480B TFTP Booting" +msgstr "Khởi động qua TFTP trên máy BCM91250A và BCM91480B Broadcom" + +#. Tag: para +#: boot-installer.xml:2091 boot-installer.xml:2195 +#, 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: " +"\n" +"ifconfig eth0 -auto\n" +" Once you have obtained an IP address, you can " +"load SiByl with the following command: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" 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 "" +"Trên bo mạch ước lượng BCM91250A và BCM91480B của Broadcom, bạn cần phải tải " +"bộ tải khởi động SiByl thông qua TFTP, mà lần lượt sẽ tải và khởi chạy trình " +"cài đặt Debian. Trong phần lớn trường hợp, trước tiên bạn sẽ lấy một địa chỉ " +"IP thông qua dịch vụ DHCP; cũng có thể cấu hình một địa chỉ tĩnh. Để sử dụng " +"DHCP, bạn có khả năng nhập lệnh này tại dấu nhắc CFE: " +"\n" +"ifconfig eth0 -auto\n" +" Một khi bạn giành một địa chỉ IP, bạn có thể tải " +"SiByl bằng lệnh này: \n" +"boot 192.168.1.1:/boot/sibyl\n" +" Bạn cần phải thay thế địa chỉ IP của lời thí dụ " +"này bằng hoặc tên hoặc địa chỉ IP của máy phục vụ TFTP của bạn. Một khi bạn " +"thực hiện lệnh này, trình cài đặt sẽ được tải tự động." + +#. Tag: title +#: boot-installer.xml:2114 boot-installer.xml:2218 boot-installer.xml:2741 +#, no-c-format +msgid "Boot Parameters" +msgstr "Tham số khởi động" + +#. Tag: para +#: boot-installer.xml:2118 +#, no-c-format +msgid "" +"On SGI machines you can append boot parameters to the bootp(): command in the command monitor." +msgstr "" +"Trên máy kiểu SGI, bạn có khả năng phụ thêm một số tham số khởi động vào " +"lệnh bootp(): trong bộ theo dõi lệnh." -#~ msgid "" -#~ "When the kernel boots, a message \n" -#~ "Memory:availk/totalk available\n" -#~ " should be emitted early in the process. " -#~ "total 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 mem=ram parameter, where ram " -#~ "is set to the amount of memory, suffixed with k for " -#~ "kilobytes, or m for megabytes. For example, both " -#~ "mem=65536k and mem=64m mean " -#~ "64MB of RAM." -#~ msgstr "" -#~ "Khi hạt nhân khởi động, thông điệp \n" -#~ "Memory:rảnhk/tổngk " -#~ "available\n" -#~ " (bộ nhớ có rảnh) nên được hiển thị sớm trong " -#~ "tiến trình. Số tổng nên khớp với tổng số RAM " -#~ "theo kilobyte. Nếu nó không phải khớp với số lượng RAM thật đã được cài " -#~ "đặt, bạn cần phải nhập tham số mem=tổng_RAM, mà tổng_RAM được đặt " -#~ "thành số lượng bộ nhớ RAM, với hậu tố k đại diện kilobyte, " -#~ "hay m đại diện megabyte. Ví dụ, mỗi chuỗi " -#~ "mem=65536k và mem=64m có " -#~ "nghĩa là 64MB bộ nhớ RAM." +#. Tag: para +#: boot-installer.xml:2123 +#, no-c-format +msgid "" +"Following the bootp(): 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: \n" +"bootp():/boot/tftpboot.img\n" +" Further kernel parameters can be passed via " +"append:" +msgstr "" +"Sau khi thực hiện lệnh bootp():, bạn có khả năng nhập " +"đường dẫn và tên của tập tin cần khởi động, nếu bạn chưa đưa ra một tên " +"riêng thông qua máy phục vụ BOOTP/DHCP. Ví dụ : \n" +"bootp():/boot/tftpboot.img\n" +" Tham số hạt nhân thêm có thể được gởi bằng lệnh " +"append (phụ thêm):" -#~ msgid "" -#~ "If you are booting with a serial console, generally the kernel will " -#~ "autodetect this (although not on DECstations). 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 console=device argument to the kernel, where " -#~ "device is your serial device, which is usually " -#~ "something like ttyS0." -#~ msgstr "" -#~ "Nếu bạn khởi động bằng bàn điều khiển nối tiếp, thường hạt nhân sẽ phát " -#~ "hiện tự động trường hợp này (dù không phải trên " -#~ "máy kiểu DECstation). Nếu bạn có thẻ ảnh động (bộ đệm khung) và " -#~ "bàn phím cũng được gắn kết với máy tính bạn muốn khởi động bằng bàn điều " -#~ "khiển nối tiếp, có lẽ bạn cần phải gởi đối số bàn điều khiển " -#~ "console=thiết_bị cho " -#~ "hạt nhân, mà thiết_bị là thiết bị nối tiếp, mà " -#~ "thường như ttyS0." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: screen +#: boot-installer.xml:2133 +#, no-c-format +msgid "bootp(): append=\"root=/dev/sda1\"" +msgstr "bootp(): append=\"root=/dev/sda1\"" + +#. Tag: para +#: boot-installer.xml:2140 boot-installer.xml:2234 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly from the CFE prompt. Instead, " +"you have to edit the /boot/sibyl.conf file on the TFTP " +"server and add your parameters to the extra_args " +"variable." +msgstr "" +"Bạn không thể gởi tham số hạt nhân nào một cách trực tiếp từ dấu nhắc CFE. " +"Thay thế, bạn cần phải sửa đổi tập tin cấu hình /boot/sibyl.conf trên máy phục vụ TFTP, và thêm các tham số riêng của bạn vào biến " +"extra_args (đối số thêm) trong nó." + +#. Tag: title +#: boot-installer.xml:2159 boot-installer.xml:2221 +#, no-c-format +msgid "Cobalt TFTP Booting" +msgstr "Khởi động TFTP Cobalt" + +#. Tag: para +#: boot-installer.xml:2160 +#, 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 /nfsroot. 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 "" +"Nói chính xác, máy kiểu Cobalt không sử dụng dịch vụ TFTP để khởi động: nó " +"dùng NFS. Bạn cần phải cài đặt trình phục vụ NFS và chèn các tập tin cài đặt " +"vào thư mục /nfsroot. Khi bạn khởi động máy Cobalt đó, " +"bạn cần phải bấm cả hai cái nút con chạy (bên trái và bên phải) cùng lúc, " +"rồi máy sẽ khởi động qua mạng từ NFS. Sau đó, nó sẽ hiển thị vài tùy chọn " +"trên màn hình. Có những phương pháp cài đặt này:" + +#. Tag: para +#: boot-installer.xml:2170 +#, 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 "" +"Bằng SSH (mặc định): trong trường hợp này, trình cài đặt sẽ cấu hình mạng " +"bằng dịch vụ DHCP, và khởi chạy trình phục vụ SSH. Sau đó, nó sẽ hiển thị " +"một mật khẩu ngẫu nhiên và thông tin đăng nhập khác (như địa chỉ IP) trên " +"màn hình LCD (phẳng) của máy Cobalt. Khi bạn kết nối đến máy đó bằng ứng " +"dụng khách SSH, bạn có thể khởi chạy tiến trình cài đặt." + +#. Tag: para +#: boot-installer.xml:2179 +#, 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 "" +"Bằng bàn điều khiển nối tiếp: dùng một cáp bộ điều giải vô giá trị (null " +"modem), bạn có thể kết nối đến cổng nối tiếp của máy Cobalt (bằng 115200 " +"bps) và thực hiện tiến trình cài đặt bằng cách này này. Tùy chọn này không " +"sẵn sàng trên máy Qube 2700 (Qube1) vì máy kiểu này không có cổng nối tiếp." + +#. Tag: para +#: boot-installer.xml:2222 +#, no-c-format +msgid "" +"You cannot pass any boot parameters directly. Instead, you have to edit the " +"/nfsroot/default.colo file on the NFS server and add " +"your parameters to the args variable." +msgstr "" +"Bạn không thể gởi trực tiếp tham số khởi động nào. Thay thế, bạn cần phải " +"sửa đổi tập tin /nfsroot/default.colo trên máy phục vụ " +"NFS, và thêm các tham số riêng của bạn vào biến args (đối số) trong nó." + +#. Tag: title +#: boot-installer.xml:2250 +#, no-c-format +msgid "s390 Limitations" +msgstr "Hạn chế S/390" + +#. Tag: para +#: boot-installer.xml:2251 +#, no-c-format +msgid "" +"In order to run the installation system a working network setup and ssh " +"session is needed on S/390." +msgstr "" +"Để chạy hệ thống cài đặt trên máy kiểu S/390, cần thiết một thiết lập mạng " +"và phiên chạy SSH hoạt động." -#~ msgid "" -#~ "For &arch-title; the serial devices are ttya or " -#~ "ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " -#~ "ttya." -#~ msgstr "" -#~ "Đối với kiến trúc kiểu &arch-title; các thiết bị nối tiếp là " -#~ "ttya hay ttyb. Hoặc, hãy đặt " -#~ "biến OpenPROM thiết bị nhập input-device và thiết bị xuất " -#~ "output-device thành ttya." +#. Tag: para +#: boot-installer.xml:2256 +#, 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 an ssh session which will launch the standard installation " +"system." +msgstr "" +"Tiến trình khởi động bắt đầu với bước thiết lập mạng mà nhắc bạn với vài " +"tham số mạng. Nếu việc thiết lập này là thành công, bạn sẽ đăng nhập vào hệ " +"thống bằng cách sở khởi một phiên chạy SSH mà sẽ khởi chạy hệ thống cài đặt " +"chuẩn." + +#. Tag: title +#: boot-installer.xml:2267 +#, no-c-format +msgid "s390 Boot Parameters" +msgstr "Tham số khởi động S/390" + +#. Tag: para +#: boot-installer.xml:2268 +#, 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 Device Drivers and Installation Commands for more " +"information about S/390-specific boot parameters." +msgstr "" +"Trên máy kiểu S/390, bạn có thể phụ thêm các tham số khởi động vào tập tin " +"parm. Tập tin này có dạng thức hoặc ASCII hoặc EBCDIC. " +"Xem Các trình điều khiển thiết bị và lệnh " +"cài đất để tìm thông tin thêm về tham số khởi động đặc trưng cho máy " +"kiểu S/390." + +#. Tag: para +#: boot-installer.xml:2322 +#, 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 c key, or else the combination of Command, " +"Option, Shift, and Delete " +"keys together while booting to boot from the CD-ROM." +msgstr "" +"Hiện thời, những kiến trúc phụ kiểu &arch-title; duy nhất hỗ trợ khả năng " +"khởi động từ đĩa CD-ROM là máy PReP và PowerMac kiểu mới. Trên máy PowerMac, " +"hãy bấm giữ hoặc phím c, hoặc tổ hợp phím Cmd, Option, Shift, và Delete trong khi khởi động, để khởi động từ đĩa CD-ROM." + +#. Tag: para +#: boot-installer.xml:2331 +#, 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 "" +"Máy PowerMac kiểu cũ sẽ không khởi động từ đĩa CD-ROM Debian, vì máy kiểu cũ " +"này ngờ một trình điều khiển khởi động đĩa CD bộ nhớ ROM của MacOS nằm trên " +"đĩa CD khởi động, và chưa có phiên bản phần mềm tự do của trình điều khiển " +"này. Mọi hệ thống kiểu cũ có ổ đĩa mềm, vậy bạn hãy sử dụng ổ đĩa mềm để " +"khởi chạy trình cài đặt, rồi chỉ trình cài đặt tới đĩa CD để lấy các tập tin " +"cần thiết." + +#. Tag: para +#: boot-installer.xml:2340 +#, 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 for booting from the hard disk, except use the " +"path to yaboot on the CD at the OF prompt, such as" +msgstr "" +"Nếu hệ thống của bạn không khởi động trực tiếp từ đĩa CD-ROM, vẫn còn có khả " +"năng sử dụng đĩa CD đó để cài đặt hệ thống. Trên máy Mac kiểu mới, bạn cũng " +"có thể nhập một lệnh OpenFirmware để tự khởi động từ đĩa CD-ROM. Hãy theo " +"hướng dẫn trong để khởi động từ đĩa cứng, " +"trừ tại dấu nhắc OpenFirmware cần phải nhập đường dẫn đến yaboot nằm trên đĩa CD đó." -#~ msgid "Debian Installer Parameters" -#~ msgstr "Tham số trình cài đặt Debian" +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: screen +#: boot-installer.xml:2349 +#, no-c-format +msgid "0 > boot cd:,\\install\\yaboot" +msgstr "0 > boot cd:,\\install\\yaboot" + +#. Tag: title +#: boot-installer.xml:2355 +#, no-c-format +msgid "Booting from Hard Disk" +msgstr "Khởi động từ đĩa cứng" + +#. Tag: title +#: boot-installer.xml:2376 +#, no-c-format +msgid "Booting CHRP from OpenFirmware" +msgstr "Khởi động CHRP từ OpenFirmware" + +#. Tag: emphasis +#: boot-installer.xml:2380 +#, no-c-format +msgid "Not yet written." +msgstr "Chưa ghi." + +#. Tag: title +#: boot-installer.xml:2385 +#, no-c-format +msgid "Booting OldWorld PowerMacs from MacOS" +msgstr "Khởi động PowerMac kiểu cũ từ MacOS" + +#. Tag: para +#: boot-installer.xml:2386 +#, no-c-format +msgid "" +"If you set up BootX in , you can use it to " +"boot into the installation system. Double click the BootX " +"application icon. Click on the Options button and " +"select Use Specified RAM Disk. This will give you the " +"chance to select the ramdisk.image.gz file. You may " +"need to select the No Video Driver checkbox, depending " +"on your hardware. Then click the Linux button to shut " +"down MacOS and launch the installer." +msgstr "" +"Nếu bạn đã thiết lập BootX trong , lúc này " +"bạn có thể sử dụng nó để khởi động vào hệ thống cài đặt. Hãy nhấn đôi vào " +"biểu tượng ứng dụng BootX. Nhấn vào cái nút " +"Options (tùy chọn) rồi chọn Use Specified " +"RAM Disk (dùng đĩa bộ nhớ RAM đã xác định). Việc này cũng sẽ cho " +"bạn có dịp chọn tập tin ramdisk.image.gz. Có lẽ bạn cần " +"phải bật hộp chọn No Video Driver (không có trình điều " +"khiển ảnh động), phụ thuộc vào phần cứng riêng của bạn. Sau đó, hãy nhấn vào " +"cái nút Linux để tắt hệ điều hành MacOS và khởi chạy " +"trình cài đặt &d-i;." + +#. Tag: title +#: boot-installer.xml:2404 +#, no-c-format +msgid "Booting NewWorld Macs from OpenFirmware" +msgstr "Khởi động Mac kiểu mới từ OpenFirmware" + +#. Tag: para +#: boot-installer.xml:2405 +#, no-c-format +msgid "" +"You will have already placed the vmlinux, " +"initrd.gz, yaboot, and " +"yaboot.conf files at the root level of your HFS " +"partition in . Restart the computer, and " +"immediately (during the chime) hold down the Option, " +"Command (cloverleaf/Apple), o, and " +"f keys all together. After a few seconds you will be " +"presented with the Open Firmware prompt. At the prompt, type " +"\n" +"0 > boot hd:x,yaboot\n" +" replacing x 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 " +"ide0: instead of hd:. In a few " +"more seconds you will see a yaboot prompt \n" +"boot:\n" +" At yaboot's boot: prompt, type " +"either install or install video=ofonly followed by a &enterkey;. The video=ofonly " +"argument is for maximum compatibility; you can try it if install doesn't work. The Debian installation program should start." +msgstr "" +"Trong , bạn đã chèn những tập tin " +"vmlinux, initrd.gz, " +"yaboot, và yaboot.conf tại lớp gốc " +"của phân vùng HFS. Hãy khởi động lại máy tính, và bấm giữ ngay (trong khi " +"máy tính rung chuông) tổ hợp phím Option, Command " +"(⌘), o, và f đều cùng lúc. Sau " +"vài giây, bạn sẽ xem dấu nhắc Open Firmware (phần vững mở). Tại dấu nhắc đó, " +"hãy gõ \n" +"0 > boot hd:x,yaboot\n" +" thay thếx bằng số " +"hiệu phân vùng HFS nơi bạn đã để tập tin hạt nhân và yaboot, rồi bấm phím " +"&enterkey;. Trên một số máy riêng, có lẽ bạn cần phải nhập ide0: thay cho hd:. Sau vài giây nữa, bạn sẽ xem " +"dấu nhắc yaboot \n" +"boot:\n" +" Tại dấu nhắc boot: (khởi động) " +"của yaboot, hãy gõ hoặc install (cài đặt) hoặc " +"install video=ofonly (cài đặt ảnh động=của chỉ) rồi " +"bấm phím &enterkey;. Đối số video=ofonly có ích để " +"tương thích tối đa; bạn có thể thử nó nếu lệnh install độc lập không hoạt động được. Sau đó, chương trình cài đặt Debian " +"nên khởi chạy." + +#. Tag: title +#: boot-installer.xml:2440 +#, no-c-format +msgid "Booting from USB memory stick" +msgstr "Khởi động từ thanh bộ nhớ USB" + +#. Tag: para +#: boot-installer.xml:2441 +#, no-c-format +msgid "Currently, NewWorld PowerMac systems are known to support USB booting." +msgstr "" +"Hiện thời, máy PowerMac kiểu mới được biết là hỗ trợ khả năng khởi động bằng " +"USB." -#, fuzzy -#~ msgid "" -#~ "The installation system recognizes a few additional boot " -#~ "parameters With current kernels (2.6.9 or newer) you can " -#~ "use 32 command line options and 32 environment options. If these numbers " -#~ "are exceeded, the kernel will panic. which may be " -#~ "useful." -#~ msgstr "" -#~ "Hệ thống cài đặt này chấp nhận vài tham số khởi động thêm " -#~ " Ghi chú rằng hạt nhân phiên bản 2.4 chấp nhận số tối đa 8 tùy chọn " -#~ "dòng lệnh và 8 tùy chọn môi trường (gồm tùy chọn nào được thêm theo mặc " -#~ "định dành cho trình cài đặt). Nếu số này bị vượt quá, hạt nhân phiên bản " -#~ "2.4 sẽ bỏ qua tùy chọn thêm nào. Đối với hạt nhân phiên bản 2.6.9 hay " -#~ "sau, bạn có khả năng dùng số tối đa 32 tùy chọn dòng lệnh và 32 tùy chọn " -#~ "môi trường. mà có thể có ích." +#. Tag: para +#: boot-installer.xml:2447 +#, no-c-format +msgid "" +"Make sure you have prepared everything from . 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 " +"Command Option o f all together while booting (see )." +msgstr "" +"Hãy kiểm tra xem bạn đã chuẩn bị mọi thứ được diễn tả trong . Để khởi động hệ thống Mac từ thanh USB, bạn sẽ cần " +"phải sử dụng dấu nhắc Open Firmware, vì Open Firmware không tìm kiếm qua " +"thiết bị sức chứa USB theo mặc định. Để truy cập dấu nhắc đó, hãy bấm giữ tổ " +"hợp phím Cmd Option o f đều cùng lúc trong khi khởi động (xem " +")." + +#. Tag: para +#: boot-installer.xml:2459 +#, no-c-format +msgid "" +"You will need to work out where the USB storage device appears in the device " +"tree, since at the moment ofpath cannot work that out " +"automatically. Type dev / ls and devalias 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 usb0/disk, usb0/hub/disk, /pci@f2000000/usb@1b,1/disk@1, and " +"/pci@f2000000/usb@1b,1/hub@1/disk@1 work." +msgstr "" +"Bạn sẽ cần phải tìm biết vị trí của thiết bị sức chứa USB trong cây thiết " +"bị, vì hiện thời công cụ ofpath không thể tính tự động " +"thông tin này. Hãy gõ lệnh dev / ls (liệt kê thiết " +"bị) và devalias (bí danh thiết bị) tại dấu nhắc Open " +"Firmware, để xem danh sách các thiết bị và bí danh thiết bị đã biết. Trên " +"máy tính của tác giả, dùng nhiều kiểu thanh USB khác nhau, đường dẫn như " +"usb0/disk, usb0/hub/disk, " +"/pci@f2000000/usb@1b,1/disk@1 và /" +"pci@f2000000/usb@1b,1/hub@1/disk@1 hoạt động được." + +#. Tag: para +#: boot-installer.xml:2471 +#, no-c-format +msgid "" +"Having worked out the device path, use a command like this to boot the " +"installer: \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" The 2 matches the " +"Apple_HFS or Apple_Bootstrap partition onto which you copied the boot image " +"earlier, and the ,\\\\:tbxi part instructs Open " +"Firmware to boot from the file with an HFS file type of \"tbxi\" (i.e. " +"yaboot) in the directory previously blessed with " +"hattrib -b." +msgstr "" +"Một khi bạn đã tìm biết đường dẫn thiết bị, để khởi động trình cài đặt hãy " +"nhập lệnh như : \n" +"boot usb0/disk:2,\\\\:" +"tbxi\n" +" Con số thay thế 2 " +"khớp phân vùng kiểu Apple_HFS hay " +"Apple_Bootstrap nơi bạn đã sao chép ảnh khởi động, còn " +"phần ,\\\\:tbxi báo Open Firmware khởi động từ tập " +"tin có kiểu tập tin HFS « tbxi » (tức là yaboot) nằm " +"trong thư mục đã được hiệu lực bằng lệnh hattrib -b." + +#. Tag: para +#: boot-installer.xml:2485 +#, no-c-format +msgid "" +"The system should now boot up, and you should be presented with the " +"boot: prompt. Here you can enter optional boot arguments, " +"or just hit &enterkey;." +msgstr "" +"Sau đó, hệ thống nên khởi động được, và bạn nên thấy dấu nhắc boot: (khởi động). Vào đây bạn có thể nhập một số đối số khởi động tùy " +"chọn, hoặc chỉ bấm phím &enterkey;." -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "debconf/priority" -#~ msgstr "debconf/priority" +#. Tag: para +#: boot-installer.xml:2491 +#, 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 ." +msgstr "" +"Phương pháp khởi động này là mới, có lẽ bạn sẽ gặp khó khăn khi thử dùng nó " +"trên một số hệ thống kiểu mới riêng. Nếu bạn có phải gặp khó khăn, xin hãy " +"gởi báo cáo cài đặt, như được diễn tả trong ." + +#. Tag: para +#: boot-installer.xml:2524 +#, no-c-format +msgid "Currently, PReP and New World PowerMac systems support netbooting." +msgstr "" +"Hiện thời, các hệ thống PReP và PowerMac kiểu mới có hỗ trợ khả năng khởi " +"động qua mạng." -#~ msgid "" -#~ "This parameter sets the lowest priority of messages to be displayed. " -#~ "Short form: priority" -#~ msgstr "" -#~ "Tham số ưu tiên này đặt ưu tiên thấp nhất cho những thông điệp cần hiển " -#~ "thị. Dạng ngắn là priority." +#. Tag: para +#: boot-installer.xml:2528 +#, no-c-format +msgid "" +"On machines with Open Firmware, such as NewWorld Power Macs, enter the boot " +"monitor (see ) and use the command " +"boot enet:0. PReP and CHRP boxes may have different ways " +"of addressing the network. On a PReP machine, you should try boot " +"server_ipaddr,file," +"client_ipaddr." +msgstr "" +"Trên máy chứa Open Firmware, như PowerMac kiểu mới, hãy vào bộ theo dõi khởi " +"động (xem ) và nhập lệnh " +"boot enet:0. Máy kiểu PReP và CHRP có lẽ liên lạc với " +"mạng bằng cách khác nhau. Trên máy kiểu PReP, bạn nên thử nhập lệnh " +"boot địa_chỉ_IP_máy_phục_vụ," +"tập_tin,địa_chỉ_IP_máy_khách." + +#. Tag: para +#: boot-installer.xml:2543 +#, 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 "" +"Khả năng khởi động từ đĩa mềm được hỗ trợ trên kiến trúc kiểu &arch-title;, " +"dù nó thường thích hợp chỉ trên máy kiểu cũ. Máy kiểu mới không có ổ đĩa " +"mềm, và khả năng khởi động từ ổ đĩa mềm USB đã gắn kết không được hỗ trợ." -#~ msgid "" -#~ "The default installation uses priority=high. 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 "" -#~ "Bản cài đặt mặc định tùy theo ưu tiên cao debconf/" -#~ "priority=high. Có nghĩa là hiển thị những thông điệp có ưu " -#~ "tiên cả cao lẫn tới hạn, còn bỏ qua những thông điệp ưu tiên vừa và thấp. " -#~ "Nếu gặp lỗi, trình cài đặt điều chỉnh ưu tiên như cần thiết." +#. Tag: para +#: boot-installer.xml:2555 +#, no-c-format +msgid "" +"To boot from the boot-floppy-hfs.img floppy, place it " +"in floppy drive after shutting the system down, and before pressing the " +"power-on button." +msgstr "" +"Để khởi động từ đĩa mềm boot-floppy-hfs.img, hãy nạp nó " +"vào ổ đĩa mềm sau khi tắt hệ thống, còn trước khi bấm cái nút mở điện." -#~ msgid "" -#~ "If you add priority=medium as boot parameter, you " -#~ "will be shown the installation menu and gain more control over the " -#~ "installation. When priority=low is used, all " -#~ "messages are shown (this is equivalent to the expert " -#~ "boot method). With priority=critical, the " -#~ "installation system will display only critical messages and try to do the " -#~ "right thing without fuss." -#~ msgstr "" -#~ "Nếu bạn thêm ưu tiên vừa debconf/priority=medium " -#~ "là tham số khởi động, bạn sẽ thấy trình đơn cài đặt, giành thêm khả năng " -#~ "điều khiển tiến trình cài đặt. Còn khi dùng ưu tiên thấp " -#~ "debconf/priority=low, mọi thông điệp được hiển thị " -#~ "(nó tương đương với phương pháp khởi động nhà chuyên môn). Với ưu tiên tới hạn debconf/priority=critical, hệ thống cài đặt sẽ hiển thị chỉ những thông điệp nghiêm " -#~ "trọng, sẽ cố gắng làm việc đúng, không tương tác nhiều." +#. Tag: para +#: boot-installer.xml:2561 +#, 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 "" +"Khi khởi động máy Apple Mac có ổ đĩa mềm: đĩa mềm được nạp vào ổ đĩa trước " +"khi khởi động sẽ có ưu tiên khởi động cao nhất. Đĩa mềm không chứa hệ thống " +"khởi động hợp lệ sẽ bị đẩy ra, sau đó máy sẽ kiểm tra tìm phân vùng đĩa cứng " +"có khả năng khởi động." + +#. Tag: para +#: boot-installer.xml:2568 +#, no-c-format +msgid "" +"After booting, the root.bin 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 "" +"Sau khi khởi động, đĩa mềm root.bin được yêu cầu. Hãy " +"nạp đĩa mềm gốc đó, rồi bấm phím &enterkey;. Chương trình cài đặt được khởi " +"chạy tự động sau khi hệ thống gốc đã được tải vào bộ nhớ." + +#. Tag: title +#: boot-installer.xml:2579 +#, no-c-format +msgid "PowerPC Boot Parameters" +msgstr "Tham số khởi động máy PowerPC" + +#. Tag: para +#: boot-installer.xml:2580 +#, 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 " +"video=atyfb:vmode:6 , which will select that mode for " +"most Mach64 and Rage video hardware. For Rage 128 hardware, this changes to " +"video=aty128fb:vmode:6 ." +msgstr "" +"Nhiều bộ trình bày Apple cũ hơn sử dụng chế độ 640x480 67Hz. Nếu ảnh động có " +"vẻ lệch trên một bộ trình bày Apple cũ hơn, hãy thử phụ thêm đối số khởi " +"động video=atyfb:vmode:6, mà sẽ chọn chế độ đó cho " +"phần lớn phần cứng ảnh động kiểu Mach64 và Rage. Đối với phần cứng kiểu Rage " +"128, đối số này thay đổi thành video=aty128fb:vmode:6 ." + +#. Tag: para +#: boot-installer.xml:2620 +#, no-c-format +msgid "" +"On machines with OpenBoot, simply enter the boot monitor on the machine " +"which is being installed (see ). Use " +"the command boot net to boot from a TFTP and RARP " +"server, or try boot net:bootp or boot net:" +"dhcp to boot from a TFTP and BOOTP or DHCP server. Some older " +"OpenBoot revisions require using the device name, such as boot le" +"(); these probably don't support BOOTP nor DHCP." +msgstr "" +"Trên máy chứa OpenBoot, đơn giản hãy vào bộ theo dõi khởi động trên máy nơi " +"đang cài đặt (xem ). Hãy nhập lệnh " +"boot net (khởi động mạng) để khởi động từ máy phục vụ " +"TFTP và RARP, hoặc thử nhập boot net:bootp hay " +"boot net:dhcp để khởi động từ máy phục vụ TFTP và " +"BOOTP hay DHCP. Một số bản sửa đổi OpenBoot cũ hơn cần thiết bạn nhập tên " +"của thiết bị, v.d. boot le(); rất có thể là chúng " +"không hỗ trợ được BOOTP hay DHCP." + +#. Tag: para +#: boot-installer.xml:2676 +#, no-c-format +msgid "" +"Most OpenBoot versions support the boot cdrom 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 "" +"Phần lớn phiên bản OpenBoot hỗ trợ lệnh boot cdrom " +"(khởi động đĩa CD-ROM) mà đơn giản là bí danh để khởi động từ thiết bị SCSI " +"trên ID 6 (hay cái chủ phụ trên máy dựa vào IDE). Có lẽ bạn cần phải nhập " +"tên thiết bị thật với phiên bản OpenBoot cũ hơn không hỗ trợ lệnh đặc biệt " +"này. Ghi chú rằng một số vấn đề đã được thông báo trên máy kiểu Sun4m (v.d. " +"máy Sparc 10 và Sparc 20) khi khởi động từ đĩa CD-ROM." + +#. Tag: para +#: boot-installer.xml:2691 +#, no-c-format +msgid "" +"To boot from floppy on a Sparc, use \n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Be warned that the newer Sun4u (ultra) " +"architecture does not support floppy booting. A typical error message is " +"Bad magic number in disk label - Can't open disk label " +"package. 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 "" +"Để khởi động từ đĩa mềm trên máy kiểu Sparc, hãy nhập lệnh: " +"\n" +"Stop-A -> OpenBoot: \"boot floppy\"\n" +" Cảnh báo : kiến trúc Sun4u (ultra) mới hơn không " +"hỗ trợ khả năng khởi động từ đĩa mềm. Thông điệp lỗi thường là " +"Bad magic number in disk label - Can't open disk label " +"package (số ma thuật sai nằm trong nhãn đĩa nên không thể " +"mở gói nhãn đĩa). Hơn nữa, một số mô hình Sun4c riêng (v.d. IPX) không hỗ " +"trợ ảnh được nén nằm trên đĩa đó nên các mô hình này cũng không được hỗ trợ." + +#. Tag: para +#: boot-installer.xml:2703 +#, 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 ." +msgstr "" +"Vài máy kiểu Sparc (v.d. Ultra 10) có lỗi OBP chặn khởi động (thay vào không " +"hỗ trợ khả năng khởi động bằng cách nào cả). Bản cập nhật OBP thích hợp có " +"thể được tải như là mã nhận diện sản phẩm ID 106121 xuống ." + +#. Tag: para +#: boot-installer.xml:2710 +#, no-c-format +msgid "" +"If you are booting from the floppy, and you see messages such as " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" then it is possible that floppy booting is " +"simply not supported on your machine." +msgstr "" +"Nếu bạn đang khởi động từ đĩa mềm, và xem thông điệp như " +"\n" +"Fatal error: Cannot read partition\n" +"Illegal or malformed device name\n" +" (lỗi nghiêm trọng: không thể đọc phân vùng, tên " +"thiết bị bất hợp pháp hay dạng sai), có lẽ khả năng khởi động từ đĩa mềm đơn " +"giản không được hỗ trợ trên máy đó." + +#. Tag: title +#: boot-installer.xml:2722 +#, no-c-format +msgid "IDPROM Messages" +msgstr "Thông điệp IDPROM" + +#. Tag: para +#: boot-installer.xml:2723 +#, no-c-format +msgid "" +"If you cannot boot because you get messages about a problem with " +"IDPROM, then it's possible that your NVRAM battery, which " +"holds configuration information for you firmware, has run out. See the " +"Sun NVRAM FAQ for more " +"information." +msgstr "" +"Nếu bạn không thể khởi động vì nhận thông điệp lỗi IDPROM, có " +"lẽ pin NVRAM, mà chứa thông tin cấu hình phần vững, đã hết điện. Xem Hỏi Đáp " +"Sun NVRAM FAQ để tìm thông tin " +"thêm." + +#. Tag: para +#: boot-installer.xml:2742 +#, 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 "" +"Tham số khởi động là tham số hạt nhân Linux thường được dùng để đảm bảo " +"thiết bị ngoại vi được xử lý cho đúng. Bình thường, hạt nhân có khả năng " +"phát hiện tự động thông tin về các ngoại của máy tính. Tuy nhiên, trong một " +"số trường hợp, bạn cần phải giúp đỡ hạt nhân một ít." + +#. Tag: para +#: boot-installer.xml:2749 +#, 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 "" +"Nếu đây là lần đầu tiên khởi động hệ thống này, hãy thử nhập các tham số " +"khởi động mặc định (tức là không thử đặt tham số thêm) và theo dõi hoạt " +"động. Rất có thể là máy sẽ hoạt động được vậy bạn không cần thêm gì. Nếu " +"không, bạn có thể khởi động lại sau, cũng tìm tham số đặc biệt có thể báo hệ " +"thống biết về phần cứng đó." + +#. Tag: para +#: boot-installer.xml:2756 +#, no-c-format +msgid "" +"Information on many boot parameters can be found in the Linux BootPrompt HOWTO, " +"including tips for obscure hardware. This section contains only a sketch of " +"the most salient parameters. Some common gotchas are included below in ." +msgstr "" +"Thông tin về nhiều tham số khởi động khác nhau nằm trong tài liệu dấu nhắc " +"khởi động Linux Thế Nào Linux BootPrompt HOWTO, gồm có mẹo về phần cứng không " +"thường. Phần này chứa chỉ bản tóm tắt các tham số nổi bật nhất. Một số vấn " +"đề thường cũng được bao gồm bên dưới trong ." + +#. Tag: para +#: boot-installer.xml:2765 +#, no-c-format +msgid "" +"When the kernel boots, a message \n" +"Memory:availk/totalk " +"available\n" +" should be emitted early in the process. " +"total 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 mem=ram parameter, where ram is " +"set to the amount of memory, suffixed with k for kilobytes, " +"or m for megabytes. For example, both mem=65536k and mem=64m mean 64MB of RAM." +msgstr "" +"Khi hạt nhân khởi động, thông điệp \n" +"Memory:rảnhk/tổngk " +"available\n" +" (bộ nhớ có rảnh) nên được hiển thị sớm trong " +"tiến trình. Số tổng nên khớp với tổng số RAM theo " +"kilobyte. Nếu nó không phải khớp với số lượng RAM thật đã được cài đặt, bạn " +"cần phải nhập tham số mem=tổng_RAM, mà tổng_RAM được đặt thành số lượng " +"bộ nhớ RAM, với hậu tố k đại diện kilobyte, hay m đại diện megabyte. Ví dụ, mỗi chuỗi mem=65536k " +"và mem=64m có nghĩa là 64MB bộ nhớ RAM." + +#. Tag: para +#: boot-installer.xml:2781 +#, no-c-format +msgid "" +"If you are booting with a serial console, generally the kernel will " +"autodetect this (although not on DECstations). 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 console=device " +"argument to the kernel, where device is your " +"serial device, which is usually something like ttyS0." +msgstr "" +"Nếu bạn khởi động bằng bàn điều khiển nối tiếp, thường hạt nhân sẽ phát hiện " +"tự động trường hợp này (dù không phải trên máy kiểu " +"DECstation). Nếu bạn có thẻ ảnh động (bộ đệm khung) và bàn phím " +"cũng được gắn kết với máy tính bạn muốn khởi động bằng bàn điều khiển nối " +"tiếp, có lẽ bạn cần phải gởi đối số bàn điều khiển " +"console=thiết_bị cho hạt " +"nhân, mà thiết_bị là thiết bị nối tiếp, mà thường " +"như ttyS0." + +#. Tag: para +#: boot-installer.xml:2794 +#, no-c-format +msgid "" +"For &arch-title; the serial devices are ttya or " +"ttyb. Alternatively, set the input-device and output-device OpenPROM variables to " +"ttya." +msgstr "" +"Đối với kiến trúc kiểu &arch-title; các thiết bị nối tiếp là ttya hay ttyb. Hoặc, hãy đặt biến OpenPROM thiết " +"bị nhập input-device và thiết bị xuất output-device thành ttya." + +#. Tag: title +#: boot-installer.xml:2805 +#, no-c-format +msgid "Debian Installer Parameters" +msgstr "Tham số trình cài đặt Debian" + +#. Tag: para +#: boot-installer.xml:2806 +#, fuzzy, no-c-format +msgid "" +"The installation system recognizes a few additional boot " +"parameters With current kernels (2.6.9 or newer) you can " +"use 32 command line options and 32 environment options. If these numbers are " +"exceeded, the kernel will panic. which may be useful." +msgstr "" +"Hệ thống cài đặt này chấp nhận vài tham số khởi động thêm " +"Ghi chú rằng hạt nhân phiên bản 2.4 chấp nhận số tối đa 8 tùy chọn dòng lệnh " +"và 8 tùy chọn môi trường (gồm tùy chọn nào được thêm theo mặc định dành cho " +"trình cài đặt). Nếu số này bị vượt quá, hạt nhân phiên bản 2.4 sẽ bỏ qua tùy " +"chọn thêm nào. Đối với hạt nhân phiên bản 2.6.9 hay sau, bạn có khả năng " +"dùng số tối đa 32 tùy chọn dòng lệnh và 32 tùy chọn môi trường. mà có thể có ích." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "DEBIAN_FRONTEND" -#~ msgstr "DEBIAN_FRONTEND" +#. Tag: term +#: boot-installer.xml:2823 +#, no-c-format +msgid "debconf/priority" +msgstr "debconf/priority" + +#. Tag: para +#: boot-installer.xml:2824 +#, no-c-format +msgid "" +"This parameter sets the lowest priority of messages to be displayed. Short " +"form: priority" +msgstr "" +"Tham số ưu tiên này đặt ưu tiên thấp nhất cho những thông điệp cần hiển thị. " +"Dạng ngắn là priority." -#, fuzzy -#~ msgid "" -#~ "This boot parameter controls the type of user interface used for the " -#~ "installer. The current possible parameter settings are: " -#~ " DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " -#~ "DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk The default frontend is " -#~ "DEBIAN_FRONTEND=newt. " -#~ "DEBIAN_FRONTEND=text may be preferable for serial " -#~ "console installs. Generally only the newt frontend " -#~ "is available on default install media. On architectures which support it, " -#~ "the graphical installer uses the gtk frontend." -#~ msgstr "" -#~ "Tham số khởi động này (lối vào Debian) điều khiển kiểu giao diện người " -#~ "dùng được dùng để cài đặt. Các giá trị tham số hiện thời có thể : " -#~ " " -#~ "DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text DEBIAN_FRONTEND=newt " -#~ "DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses DEBIAN_FRONTEND=bogl " -#~ "DEBIAN_FRONTEND=gtk DEBIAN_FRONTEND=corba Lối vào mặc định là " -#~ "DEBIAN_FRONTEND=newt. " -#~ "DEBIAN_FRONTEND=text có lẽ thích hợp hơn với tiến " -#~ "trình cài đặt bằng bàn điều khiển nối tiếp. Thường chỉ lối vào " -#~ "newt có sẵn trên vật chứa cài đặt mặc định, vậy " -#~ "thông tin này không phải rất có ích vào lúc này." +#. Tag: para +#: boot-installer.xml:2829 +#, no-c-format +msgid "" +"The default installation uses priority=high. 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 "" +"Bản cài đặt mặc định tùy theo ưu tiên cao debconf/priority=high. Có nghĩa là hiển thị những thông điệp có ưu tiên cả cao lẫn tới " +"hạn, còn bỏ qua những thông điệp ưu tiên vừa và thấp. Nếu gặp lỗi, trình cài " +"đặt điều chỉnh ưu tiên như cần thiết." + +#. Tag: para +#: boot-installer.xml:2836 +#, no-c-format +msgid "" +"If you add priority=medium as boot parameter, you " +"will be shown the installation menu and gain more control over the " +"installation. When priority=low is used, all messages " +"are shown (this is equivalent to the expert boot " +"method). With priority=critical, the installation " +"system will display only critical messages and try to do the right thing " +"without fuss." +msgstr "" +"Nếu bạn thêm ưu tiên vừa debconf/priority=medium là " +"tham số khởi động, bạn sẽ thấy trình đơn cài đặt, giành thêm khả năng điều " +"khiển tiến trình cài đặt. Còn khi dùng ưu tiên thấp debconf/" +"priority=low, mọi thông điệp được hiển thị (nó tương đương với " +"phương pháp khởi động nhà chuyên môn). Với ưu tiên tới " +"hạn debconf/priority=critical, hệ thống cài đặt sẽ " +"hiển thị chỉ những thông điệp nghiêm trọng, sẽ cố gắng làm việc đúng, không " +"tương tác nhiều." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "BOOT_DEBUG" -#~ msgstr "BOOT_DEBUG" +#. Tag: term +#: boot-installer.xml:2850 +#, no-c-format +msgid "DEBIAN_FRONTEND" +msgstr "DEBIAN_FRONTEND" + +#. Tag: para +#: boot-installer.xml:2851 +#, fuzzy, no-c-format +msgid "" +"This boot parameter controls the type of user interface used for the " +"installer. The current possible parameter settings are: " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=gtk " +" The default frontend is " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text may be preferable for serial " +"console installs. Generally only the newt frontend is " +"available on default install media. On architectures which support it, the " +"graphical installer uses the gtk frontend." +msgstr "" +"Tham số khởi động này (lối vào Debian) điều khiển kiểu giao diện người dùng " +"được dùng để cài đặt. Các giá trị tham số hiện thời có thể : " +" DEBIAN_FRONTEND=noninteractive DEBIAN_FRONTEND=text " +"DEBIAN_FRONTEND=newt DEBIAN_FRONTEND=slang DEBIAN_FRONTEND=ncurses " +"DEBIAN_FRONTEND=bogl DEBIAN_FRONTEND=gtk " +" DEBIAN_FRONTEND=corba Lối vào mặc định là " +"DEBIAN_FRONTEND=newt. " +"DEBIAN_FRONTEND=text có lẽ thích hợp hơn với tiến " +"trình cài đặt bằng bàn điều khiển nối tiếp. Thường chỉ lối vào " +"newt có sẵn trên vật chứa cài đặt mặc định, vậy thông " +"tin này không phải rất có ích vào lúc này." -#~ 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 "" -#~ "Việc đặt tham số khởi động này (gỡ lỗi khởi động) thành 2 sẽ gây ra tiến " -#~ "trình khởi động trình cài đặt sẽ được ghi lưu một cách chi tiết. Còn việc " -#~ "đặt nó thành 3 làm cho trình bao gỡ lỗi sẵn sàng tại một số điểm thời có " -#~ "ích trong tiến trình khởi động. (Hãy thoát khỏi trình bao để tiếp tục lại " -#~ "tiến trình khởi động.)" +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:2880 +#, no-c-format +msgid "BOOT_DEBUG" +msgstr "BOOT_DEBUG" + +#. Tag: para +#: boot-installer.xml:2881 +#, 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 "" +"Việc đặt tham số khởi động này (gỡ lỗi khởi động) thành 2 sẽ gây ra tiến " +"trình khởi động trình cài đặt sẽ được ghi lưu một cách chi tiết. Còn việc " +"đặt nó thành 3 làm cho trình bao gỡ lỗi sẵn sàng tại một số điểm thời có ích " +"trong tiến trình khởi động. (Hãy thoát khỏi trình bao để tiếp tục lại tiến " +"trình khởi động.)" # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "BOOT_DEBUG=0" -#~ msgstr "BOOT_DEBUG=0" - -#~ msgid "This is the default." -#~ msgstr "Đây là giá trị mặc định." +#. Tag: userinput +#: boot-installer.xml:2890 +#, no-c-format +msgid "BOOT_DEBUG=0" +msgstr "BOOT_DEBUG=0" + +#. Tag: para +#: boot-installer.xml:2891 +#, no-c-format +msgid "This is the default." +msgstr "Đây là giá trị mặc định." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "BOOT_DEBUG=1" -#~ msgstr "BOOT_DEBUG=1" - -#~ msgid "More verbose than usual." -#~ msgstr "Chi tiết hơn cấp thường." +#. Tag: userinput +#: boot-installer.xml:2895 +#, no-c-format +msgid "BOOT_DEBUG=1" +msgstr "BOOT_DEBUG=1" + +#. Tag: para +#: boot-installer.xml:2896 +#, no-c-format +msgid "More verbose than usual." +msgstr "Chi tiết hơn cấp thường." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "BOOT_DEBUG=2" -#~ msgstr "BOOT_DEBUG=2" - -#~ msgid "Lots of debugging information." -#~ msgstr "Xuất rất nhiều thông tin gỡ lỗi." +#. Tag: userinput +#: boot-installer.xml:2900 +#, no-c-format +msgid "BOOT_DEBUG=2" +msgstr "BOOT_DEBUG=2" + +#. Tag: para +#: boot-installer.xml:2901 +#, no-c-format +msgid "Lots of debugging information." +msgstr "Xuất rất nhiều thông tin gỡ lỗi." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "BOOT_DEBUG=3" -#~ msgstr "BOOT_DEBUG=3" - -#~ msgid "" -#~ "Shells are run at various points in the boot process to allow detailed " -#~ "debugging. Exit the shell to continue the boot." -#~ msgstr "" -#~ "Chạy trình bao tại một số điểm thời khác nhau trong tiến trình khởi động, " -#~ "để cho khả năng gỡ lỗi chi tiết. Hãy thoát khỏi trình bao để tiếp tục lại " -#~ "khởi động." +#. Tag: userinput +#: boot-installer.xml:2905 +#, no-c-format +msgid "BOOT_DEBUG=3" +msgstr "BOOT_DEBUG=3" + +#. Tag: para +#: boot-installer.xml:2906 +#, 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 "" +"Chạy trình bao tại một số điểm thời khác nhau trong tiến trình khởi động, để " +"cho khả năng gỡ lỗi chi tiết. Hãy thoát khỏi trình bao để tiếp tục lại khởi " +"động." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "INSTALL_MEDIA_DEV" -#~ msgstr "INSTALL_MEDIA_DEV" - -#~ msgid "" -#~ "The value of the parameter is the path to the device to load the Debian " -#~ "installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" -#~ msgstr "" -#~ "Giá trị của tham số này (thiết bị vật chứa cài đặt) là đường dẫn đến " -#~ "thiết bị từ đó cần tải trình cài đặt Debian. Ví dụ, " -#~ "INSTALL_MEDIA_DEV=/dev/floppy/0" +#. Tag: term +#: boot-installer.xml:2920 +#, no-c-format +msgid "INSTALL_MEDIA_DEV" +msgstr "INSTALL_MEDIA_DEV" + +#. Tag: para +#: boot-installer.xml:2921 +#, no-c-format +msgid "" +"The value of the parameter is the path to the device to load the Debian " +"installer from. For example, INSTALL_MEDIA_DEV=/dev/floppy/0" +msgstr "" +"Giá trị của tham số này (thiết bị vật chứa cài đặt) là đường dẫn đến thiết " +"bị từ đó cần tải trình cài đặt Debian. Ví dụ, INSTALL_MEDIA_DEV=/" +"dev/floppy/0" -#~ msgid "" -#~ "The boot floppy, which normally scans all floppies it can to find the " -#~ "root floppy, can be overridden by this parameter to only look at the one " -#~ "device." -#~ msgstr "" -#~ "Đĩa mềm khởi động, mà thường quét mọi đĩa mềm có thể để tìm đĩa mềm gốc, " -#~ "có thể bị lọc bởi tham số này để phát hiện chỉ một thiết bị thôi." +#. Tag: para +#: boot-installer.xml:2927 +#, no-c-format +msgid "" +"The boot floppy, which normally scans all floppies it can to find the root " +"floppy, can be overridden by this parameter to only look at the one device." +msgstr "" +"Đĩa mềm khởi động, mà thường quét mọi đĩa mềm có thể để tìm đĩa mềm gốc, có " +"thể bị lọc bởi tham số này để phát hiện chỉ một thiết bị thôi." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "debian-installer/framebuffer" -#~ msgstr "debian-installer/framebuffer" - -#~ 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 debian-installer/" -#~ "framebuffer=false, or fb=false for " -#~ "short. Problem symptoms are error messages about bterm or bogl, a blank " -#~ "screen, or a freeze within a few minutes after starting the install." -#~ msgstr "" -#~ "Một số kiến trúc riêng sử dụng bộ đệm khung (framebuffer) của hạt nhân để " -#~ "cung cấp khả năng cài đặt bằng một số ngôn ngữ khác nhau. Nếu bộ đếm " -#~ "khung gây ra lỗi trên hệ thống, bạn có thể tắt tính năng này bằng tham số " -#~ "debian-installer/framebuffer=false (bộ đếm khung " -#~ "là sai), dạng ngắn là fb=false. Trường hợp ngụ ý " -#~ "sự khó là thông điệp lỗi về bterm hay " -#~ "bogl, màn hình trắng hay hệ thống đông đặc trong " -#~ "vòng vài phút sau khi khởi chạy tiến trình cài đặt." +#. Tag: term +#: boot-installer.xml:2937 +#, no-c-format +msgid "debian-installer/framebuffer" +msgstr "debian-installer/framebuffer" + +#. Tag: para +#: boot-installer.xml:2938 +#, 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 debian-installer/" +"framebuffer=false, or fb=false for short. " +"Problem symptoms are error messages about bterm or bogl, a blank screen, or " +"a freeze within a few minutes after starting the install." +msgstr "" +"Một số kiến trúc riêng sử dụng bộ đệm khung (framebuffer) của hạt nhân để " +"cung cấp khả năng cài đặt bằng một số ngôn ngữ khác nhau. Nếu bộ đếm khung " +"gây ra lỗi trên hệ thống, bạn có thể tắt tính năng này bằng tham số " +"debian-installer/framebuffer=false (bộ đếm khung là " +"sai), dạng ngắn là fb=false. Trường hợp ngụ ý sự khó " +"là thông điệp lỗi về bterm hay bogl, màn hình trắng hay hệ thống đông đặc trong vòng vài phút sau khi " +"khởi chạy tiến trình cài đặt." + +#. Tag: para +#: boot-installer.xml:2948 +#, no-c-format +msgid "" +"The video=vga16:off argument may also be used to " +"disable the kernel's use of the framebuffer. Such problems have been " +"reported on a Dell Inspiron with Mobile Radeon card." +msgstr "" +"Đối số video=vga16:off cũng có thể được dùng để tắt " +"khả năng dùng bộ đếm khung của hạt nhân. Lỗi như vậy đã được thông báo trên " +"máy kiểu Dell Inspiron chứa thẻ Mobile Radeon." + +#. Tag: para +#: boot-installer.xml:2954 +#, no-c-format +msgid "Such problems have been reported on the Amiga 1200 and SE/30." +msgstr "Lỗi như vậy đã được thông báo trên máy kiểu Amiga 1200 và SE/30." + +#. Tag: para +#: boot-installer.xml:2958 +#, no-c-format +msgid "Such problems have been reported on hppa." +msgstr "Lỗi như vậy đã được thông báo trên máy kiểu hppa." + +#. Tag: para +#: boot-installer.xml:2962 +#, no-c-format +msgid "" +"Because of display problems on some systems, framebuffer support is " +"disabled by default 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 debian-installer/" +"framebuffer=true or fb=true for short." +msgstr "" +"Do vấn đề trình bày trên một số hệ thống riêng, khả năng hỗ trợ bộ đếm khung " +"bị tắt theo mặc định đối với kiến trúc kiểu &arch-" +"title;. Trường hợp này có thể gây ra sự trình bày không đẹp trên hệ thống " +"không hỗ trợ đúng bộ đếm khung, v.d. máy chứa thẻ đồ họa ATI. Nếu bạn gặp " +"lỗi trình bày trong tiến trình cài đặt, bạn có thể thử khởi động với tham số " +"debian-installer/framebuffer=true (bộ đếm khung là " +"đúng); dạng ngắn là fb=true." -#~ msgid "" -#~ "The video=vga16:off argument may also be used to " -#~ "disable the kernel's use of the framebuffer. Such problems have been " -#~ "reported on a Dell Inspiron with Mobile Radeon card." -#~ msgstr "" -#~ "Đối số video=vga16:off cũng có thể được dùng để " -#~ "tắt khả năng dùng bộ đếm khung của hạt nhân. Lỗi như vậy đã được thông " -#~ "báo trên máy kiểu Dell Inspiron chứa thẻ Mobile Radeon." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:2976 +#, no-c-format +msgid "debian-installer/theme" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:2977 +#, no-c-format +msgid "" +"A theme determines how the user interface of the installer looks (colors, " +"icons, etc.). What themes are available differs per frontend. Currently both " +"the newt and gtk frontends only have a dark theme that was " +"designed for visually impaired users. Set the theme by booting with " +"parameter debian-installer/theme=dark or theme=dark." +msgstr "" +"Sắc thái xác định diện mạo của giao diện người dùng (màu sắc, biểu tượng v." +"v.). Những sắc thái có sẵn đặc trưng cho lối vào. HIện thời lối vào kiểu cả " +"newt lẫn gtk đều chỉ có một sắc thái dark (tối) được thiết kế " +"cho những người dùng thị lực kém. Hãy đặt sắc thái bằng cách khởi động với " +"tham số debian-installer/theme=dark hoặc theme=dark." -#~ msgid "Such problems have been reported on the Amiga 1200 and SE/30." -#~ msgstr "Lỗi như vậy đã được thông báo trên máy kiểu Amiga 1200 và SE/30." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:2990 +#, no-c-format +msgid "debian-installer/probe/usb" +msgstr "debian-installer/probe/usb" + +#. Tag: para +#: boot-installer.xml:2991 +#, no-c-format +msgid "" +"Set to false to prevent probing for USB on boot, if " +"that causes problems." +msgstr "" +"Đặt thành false (thăm dò USB là sai) để ngăn cản thăm " +"dò USB khi khởi động, nếu tính năng này gây ra lỗi." -#~ msgid "Such problems have been reported on hppa." -#~ msgstr "Lỗi như vậy đã được thông báo trên máy kiểu hppa." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:3000 boot-installer.xml:3153 +#, no-c-format +msgid "netcfg/disable_dhcp" +msgstr "netcfg/disable_dhcp" + +#. Tag: para +#: boot-installer.xml:3001 +#, 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 "" +"Mặc định là &d-i; thăm dò tự động cấu hình mạng qua dịch vụ DHCP. Nếu việc " +"thăm dò là thành công, bạn sẽ không có dịp xem lại và thay đổi thiết lập " +"được lấy. Bạn có thể tới bước tự thiết lập mạng chỉ trong trường hợp gặp lỗi " +"thăm dò DCHP." + +#. Tag: para +#: boot-installer.xml:3008 +#, 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 " +"netcfg/disable_dhcp=true to prevent configuring the " +"network with DHCP and to enter the information manually." +msgstr "" +"Nếu bạn có máy DHCP chạy trên mạng cục bộ, nhưng muốn tránh nó vì, lấy thí " +"dụ, nó trả lời sai, bạn có khả năng nhập tham số netcfg/" +"disable_dhcp=true (tắt DHCP là đúng) để ngăn cản cấu hình mạng " +"bằng DHCP, cũng để tự nhập thông tin đó." -#~ msgid "" -#~ "Because of display problems on some systems, framebuffer support is " -#~ "disabled by default 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 " -#~ "debian-installer/framebuffer=true or " -#~ "fb=true for short." -#~ msgstr "" -#~ "Do vấn đề trình bày trên một số hệ thống riêng, khả năng hỗ trợ bộ đếm " -#~ "khung bị tắt theo mặc định đối với kiến trúc kiểu " -#~ "&arch-title;. Trường hợp này có thể gây ra sự trình bày không đẹp trên hệ " -#~ "thống không hỗ trợ đúng bộ đếm khung, v.d. máy chứa thẻ đồ họa ATI. Nếu " -#~ "bạn gặp lỗi trình bày trong tiến trình cài đặt, bạn có thể thử khởi động " -#~ "với tham số debian-installer/framebuffer=true (bộ " -#~ "đếm khung là đúng); dạng ngắn là fb=true." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:3019 +#, no-c-format +msgid "hw-detect/start_pcmcia" +msgstr "hw-detect/start_pcmcia" + +#. Tag: para +#: boot-installer.xml:3020 +#, no-c-format +msgid "" +"Set to false to prevent starting PCMCIA services, if " +"that causes problems. Some laptops are well known for this misbehavior." +msgstr "" +"Đặt thành false (khởi chạy PCMCIA là sai) để ngăn cản " +"khởi chạy dịch vụ PCMCIA, nếu nó gây ra lỗi. Một số máy tính xách tay là nổi " +"tiếng do trường hợp lỗi này." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "debian-installer/theme" -#~ msgstr "debian-installer/theme" +#. Tag: term +#: boot-installer.xml:3030 +#, no-c-format +msgid "preseed/url" +msgstr "preseed/url" + +#. Tag: para +#: boot-installer.xml:3031 +#, fuzzy, no-c-format +msgid "" +"Specify the url to a preconfiguration file to download and use in automating " +"the install. See . Short form: " +"url." +msgstr "" +"Hãy xác định địa chỉ Mạng của tập tin cấu hình sẵn cần tải về và sử dụng khi " +"tự động hoá tiến trình cài đặt. Xem , " +"dạng ngắn là url." -#~ msgid "" -#~ "A theme determines how the user interface of the installer looks (colors, " -#~ "icons, etc.). What themes are available differs per frontend. Currently " -#~ "both the newt and gtk frontends only have a dark theme " -#~ "that was designed for visually impaired users. Set the theme by booting " -#~ "with parameter debian-installer/theme=dark or theme=dark." -#~ msgstr "" -#~ "Sắc thái xác định diện mạo của giao diện người dùng (màu sắc, biểu tượng " -#~ "v.v.). Những sắc thái có sẵn đặc trưng cho lối vào. HIện thời lối vào " -#~ "kiểu cả newt lẫn gtk đều chỉ có một sắc thái dark (tối) " -#~ "được thiết kế cho những người dùng thị lực kém. Hãy đặt sắc thái bằng " -#~ "cách khởi động với tham số debian-installer/" -#~ "theme=dark hoặc " -#~ "theme=dark." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:3041 +#, no-c-format +msgid "preseed/file" +msgstr "preseed/file" + +#. Tag: para +#: boot-installer.xml:3042 +#, fuzzy, no-c-format +msgid "" +"Specify the path to a preconfiguration file to load to automating the " +"install. See . Short form: " +"file." +msgstr "" +"Hãy xác đường dẫn đến tập tin cấu hình sẵn cần tải khi tự động hoá tiến " +"trình cài đặt. Xem , dạng ngắn là " +"file." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "debian-installer/probe/usb" -#~ msgstr "debian-installer/probe/usb" +#. Tag: term +#: boot-installer.xml:3052 +#, fuzzy, no-c-format +msgid "auto-install/enabled" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:3053 +#, no-c-format +msgid "" +"Delay questions that are normally asked before preseeding is possible until " +"after the network is configured. Short form: auto=true See for details about using this " +"to automate installs." +msgstr "" -#~ msgid "" -#~ "Set to false to prevent probing for USB on boot, " -#~ "if that causes problems." -#~ msgstr "" -#~ "Đặt thành false (thăm dò USB là sai) để ngăn cản " -#~ "thăm dò USB khi khởi động, nếu tính năng này gây ra lỗi." +# Literal: don't translate / Nghĩa chữ: đừng dịch +#. Tag: term +#: boot-installer.xml:3064 +#, no-c-format +msgid "cdrom-detect/eject" +msgstr "cdrom-detect/eject" + +#. Tag: para +#: boot-installer.xml:3065 +#, 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 "" +"(Phát hiện đĩa CD-ROM/đẩy ra) Mặc định là, trước khi khởi động lại, &d-i; " +"đẩy ra tự động vật chứa quang được dùng trong khi cài đặt. Ứng xử này có thể " +"không phải cần thiết nếu hệ thống không khởi động tự động từ đĩa CD. Trong " +"một số trường hợp riêng, ứng xử này ngay cả gây ra lỗi, ví dụ nếu ổ đĩa " +"quang không có khả năng nạp lại vật chứa còn người dùng không tại chỗ để tự " +"nạp. Nhiều ổ đĩa nạp khe, hình thon, và kiểu ngăn kéo không thể tải lại tự " +"động vật chứa." + +#. Tag: para +#: boot-installer.xml:3074 +#, no-c-format +msgid "" +"Set to false 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 "" +"Đặt thành false (sai) để tắt khả năng đầy ra tự động; " +"cũng ghi nhớ rằng bạn có lẽ sẽ cần phải đảm bảo hệ thống không khởi động tự " +"động từ ổ đĩa quang sau khi việc cài đặt ban đầu." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "netcfg/disable_dhcp" -#~ msgstr "netcfg/disable_dhcp" +#. Tag: term +#: boot-installer.xml:3085 +#, no-c-format +msgid "ramdisk_size" +msgstr "ramdisk_size" + +#. Tag: para +#: boot-installer.xml:3086 +#, no-c-format +msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." +msgstr "" +"Nếu bạn dùng hạt nhân phiên bản 2.2.x, bạn có thể cần phải đặt kích cỡ đĩa " +"RAM &ramdisksize;." -#~ 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 "" -#~ "Mặc định là &d-i; thăm dò tự động cấu hình mạng qua dịch vụ DHCP. Nếu " -#~ "việc thăm dò là thành công, bạn sẽ không có dịp xem lại và thay đổi thiết " -#~ "lập được lấy. Bạn có thể tới bước tự thiết lập mạng chỉ trong trường hợp " -#~ "gặp lỗi thăm dò DCHP." +#. Tag: term +#: boot-installer.xml:3094 +#, no-c-format +msgid "mouse/left" +msgstr "" -#~ 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 " -#~ "netcfg/disable_dhcp=true to prevent configuring " -#~ "the network with DHCP and to enter the information manually." -#~ msgstr "" -#~ "Nếu bạn có máy DHCP chạy trên mạng cục bộ, nhưng muốn tránh nó vì, lấy " -#~ "thí dụ, nó trả lời sai, bạn có khả năng nhập tham số netcfg/" -#~ "disable_dhcp=true (tắt DHCP là đúng) để ngăn cản cấu hình " -#~ "mạng bằng DHCP, cũng để tự nhập thông tin đó." +#. Tag: para +#: boot-installer.xml:3095 +#, fuzzy, no-c-format +msgid "" +"For the gtk frontend (graphical installer), users can switch the mouse to " +"left-handed operation by setting this parameter to true." +msgstr "" +"Đối với lối vào gtk (bộ cài đặt kiểu đồ họa), khả năng tăng tốc độ phần cứng " +"trong directfb bị tắt theo mặc định. Để bật nó, hãy đặt tham số này thành " +"true khi khởi động bộ cài đặt." + +#. Tag: term +#: boot-installer.xml:3104 +#, no-c-format +msgid "directfb/hw-accel" +msgstr "directfb/hw-accel" + +#. Tag: para +#: boot-installer.xml:3105 +#, no-c-format +msgid "" +"For the gtk frontend (graphical installer), hardware acceleration in " +"directfb is disabled by default. To enable it, set this parameter to " +"true when booting the installer." +msgstr "" +"Đối với lối vào gtk (bộ cài đặt kiểu đồ họa), khả năng tăng tốc độ phần cứng " +"trong directfb bị tắt theo mặc định. Để bật nó, hãy đặt tham số này thành " +"true khi khởi động bộ cài đặt." # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "hw-detect/start_pcmcia" -#~ msgstr "hw-detect/start_pcmcia" - -#~ msgid "" -#~ "Set to false to prevent starting PCMCIA services, " -#~ "if that causes problems. Some laptops are well known for this misbehavior." -#~ msgstr "" -#~ "Đặt thành false (khởi chạy PCMCIA là sai) để ngăn " -#~ "cản khởi chạy dịch vụ PCMCIA, nếu nó gây ra lỗi. Một số máy tính xách tay " -#~ "là nổi tiếng do trường hợp lỗi này." +#. Tag: term +#: boot-installer.xml:3115 +#, no-c-format +msgid "rescue/enable" +msgstr "rescue/enable" + +#. Tag: para +#: boot-installer.xml:3116 +#, no-c-format +msgid "" +"Set to true to enter rescue mode rather than " +"performing a normal installation. See ." +msgstr "" +"(Cứu/bật) Đặt thành true (đúng) để vào chế độ cứu, " +"hơn là chạy tiến trình cài đặt chuẩn. Xem ." -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "preseed/url" -#~ msgstr "preseed/url" +#. Tag: title +#: boot-installer.xml:3127 +#, no-c-format +msgid "Using boot parameters to answer questions" +msgstr "" -#, fuzzy -#~ msgid "" -#~ "Specify the url to a preconfiguration file to download and use in " -#~ "automating the install. See . Short " -#~ "form: url." -#~ msgstr "" -#~ "Hãy xác định địa chỉ Mạng của tập tin cấu hình sẵn cần tải về và sử dụng " -#~ "khi tự động hoá tiến trình cài đặt. Xem , dạng ngắn là url." +#. Tag: para +#: boot-installer.xml:3128 +#, no-c-format +msgid "" +"With some exceptions, a value can be set at the boot prompt for any question " +"asked during the installation, though this is only really useful in specific " +"cases. General instructions how to do this can be found in . Some specific examples are listed below." +msgstr "" # Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "preseed/file" -#~ msgstr "preseed/file" - -#, fuzzy -#~ msgid "" -#~ "Specify the path to a preconfiguration file to load to automating the " -#~ "install. See . Short form: " -#~ "file." -#~ msgstr "" -#~ "Hãy xác đường dẫn đến tập tin cấu hình sẵn cần tải khi tự động hoá tiến " -#~ "trình cài đặt. Xem , dạng ngắn là " -#~ "file." +#. Tag: term +#: boot-installer.xml:3140 +#, fuzzy, no-c-format +msgid "debian-installer/locale" +msgstr "debian-installer/theme" + +#. Tag: para +#: boot-installer.xml:3141 +#, no-c-format +msgid "" +"Can be used to set both the language and country for the installation. This " +"will only work if the locale is supported in Debian. Short form: " +"locale. For example, use locale=de_CH to select German as language and Switserland as country." +msgstr "" -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "cdrom-detect/eject" -#~ msgstr "cdrom-detect/eject" +#. Tag: para +#: boot-installer.xml:3154 +#, no-c-format +msgid "" +"Set to true if you want to disable DHCP and instead " +"force static network configuration." +msgstr "" -#~ 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 "" -#~ "(Phát hiện đĩa CD-ROM/đẩy ra) Mặc định là, trước khi khởi động lại, &d-i; " -#~ "đẩy ra tự động vật chứa quang được dùng trong khi cài đặt. Ứng xử này có " -#~ "thể không phải cần thiết nếu hệ thống không khởi động tự động từ đĩa CD. " -#~ "Trong một số trường hợp riêng, ứng xử này ngay cả gây ra lỗi, ví dụ nếu ổ " -#~ "đĩa quang không có khả năng nạp lại vật chứa còn người dùng không tại chỗ " -#~ "để tự nạp. Nhiều ổ đĩa nạp khe, hình thon, và kiểu ngăn kéo không thể tải " -#~ "lại tự động vật chứa." +#. Tag: term +#: boot-installer.xml:3163 +#, no-c-format +msgid "tasksel:tasksel/first" +msgstr "" -#~ msgid "" -#~ "Set to false 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 "" -#~ "Đặt thành false (sai) để tắt khả năng đầy ra tự " -#~ "động; cũng ghi nhớ rằng bạn có lẽ sẽ cần phải đảm bảo hệ thống không khởi " -#~ "động tự động từ ổ đĩa quang sau khi việc cài đặt ban đầu." +#. Tag: para +#: boot-installer.xml:3164 +#, no-c-format +msgid "" +"Can be used to select tasks that are not available from the interactive task " +"list, such as the kde-desktop task. See for additional information. Short form: tasks." +msgstr "" -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "ramdisk_size" -#~ msgstr "ramdisk_size" +#. Tag: title +#: boot-installer.xml:3178 +#, no-c-format +msgid "Passing parameters to kernel modules" +msgstr "" -#~ msgid "If you are using a 2.2.x kernel, you may need to set &ramdisksize;." -#~ msgstr "" -#~ "Nếu bạn dùng hạt nhân phiên bản 2.2.x, bạn có thể cần phải đặt kích cỡ " -#~ "đĩa RAM &ramdisksize;." +#. Tag: para +#: boot-installer.xml:3179 +#, no-c-format +msgid "" +"If drivers are compiled into the kernel, you can pass parameters to them as " +"described in the kernel documentation. However, if drivers are compiled as " +"modules and because kernel modules are loaded a bit differently during an " +"installation than when booting an installed system, it is not possible to " +"pass parameters to modules as you would normally do. Instead, you need to " +"use a special syntax recognized by the installer which will then make sure " +"that the parameters are saved in the proper configuration files and will " +"thus be used when the modules are actually loaded. The parameters will also " +"be propagated automatically to the configuration for the installed system." +msgstr "" -#, fuzzy -#~ msgid "" -#~ "For the gtk frontend (graphical installer), users can switch the mouse to " -#~ "left-handed operation by setting this parameter to true." -#~ msgstr "" -#~ "Đối với lối vào gtk (bộ cài đặt kiểu đồ họa), khả năng tăng tốc độ phần " -#~ "cứng trong directfb bị tắt theo mặc định. Để bật nó, hãy đặt tham số này " -#~ "thành true khi khởi động bộ cài đặt." +#. Tag: para +#: boot-installer.xml:3192 +#, no-c-format +msgid "" +"Note that it is now quite rare that parameters need to be passed to modules. " +"In most cases the kernel will be able to probe the hardware present in a " +"system and set good defaults that way. However, in some situations it may " +"still be needed to set parameters manually." +msgstr "" -#~ msgid "directfb/hw-accel" -#~ msgstr "directfb/hw-accel" +#. Tag: para +#: boot-installer.xml:3199 +#, no-c-format +msgid "" +"The syntax to use to set parameters for modules is: " +"\n" +"module_name.parameter_name=value\n" +" If you need to pass multiple parameters to the " +"same or different modules, just repeat this. For example, to set an old 3Com " +"network interface card to use the BNC (coax) connector and IRQ 10, you would " +"pass:" +msgstr "" -#~ msgid "" -#~ "For the gtk frontend (graphical installer), hardware acceleration in " -#~ "directfb is disabled by default. To enable it, set this parameter to " -#~ "true when booting the installer." -#~ msgstr "" -#~ "Đối với lối vào gtk (bộ cài đặt kiểu đồ họa), khả năng tăng tốc độ phần " -#~ "cứng trong directfb bị tắt theo mặc định. Để bật nó, hãy đặt tham số này " -#~ "thành true khi khởi động bộ cài đặt." +#. Tag: screen +#: boot-installer.xml:3209 +#, no-c-format +msgid "3c509.xcvr=3 3c509.irq=10" +msgstr "" -# Literal: don't translate / Nghĩa chữ: đừng dịch -#~ msgid "rescue/enable" -#~ msgstr "rescue/enable" +#. Tag: title +#: boot-installer.xml:3221 +#, no-c-format +msgid "Troubleshooting the Installation Process" +msgstr "Giải đáp thắc mắc trong tiến trình cài đặt" + +#. Tag: title +#: boot-installer.xml:3226 +#, fuzzy, no-c-format +msgid "CD-ROM Reliability" +msgstr "Sự đáng tin cậy của đĩa mềm" + +#. Tag: para +#: boot-installer.xml:3227 +#, no-c-format +msgid "" +"Sometimes, especially with older CD-ROM drives, the installer may fail to " +"boot from a CD-ROM. The installer may also — even after booting " +"successfully from CD-ROM — fail to recognize the CD-ROM or return " +"errors while reading from it during the installation." +msgstr "" -#~ msgid "" -#~ "Set to true to enter rescue mode rather than " -#~ "performing a normal installation. See ." -#~ msgstr "" -#~ "(Cứu/bật) Đặt thành true (đúng) để vào chế độ cứu, " -#~ "hơn là chạy tiến trình cài đặt chuẩn. Xem ." +#. Tag: para +#: boot-installer.xml:3234 +#, no-c-format +msgid "" +"There are a many different possible causes for these problems. We can only " +"list some common issues and provide general suggestions on how to deal with " +"them. The rest is up to you." +msgstr "" -# Literal: don't translate / Nghĩa chữ: đừng dịch -#, fuzzy -#~ msgid "debian-installer/locale" -#~ msgstr "debian-installer/theme" +#. Tag: para +#: boot-installer.xml:3240 +#, no-c-format +msgid "There are two very simple things that you should try first." +msgstr "" -#~ msgid "Troubleshooting the Installation Process" -#~ msgstr "Giải đáp thắc mắc trong tiến trình cài đặt" +#. Tag: para +#: boot-installer.xml:3245 +#, no-c-format +msgid "" +"If the CD-ROM does not boot, check that it was inserted correctly and that " +"it is not dirty." +msgstr "" -#, fuzzy -#~ msgid "CD-ROM Reliability" -#~ msgstr "Sự đáng tin cậy của đĩa mềm" +#. Tag: para +#: boot-installer.xml:3251 +#, no-c-format +msgid "" +"If the installer fails to recognize a CD-ROM, try just running the option " +" Detect and mount CD-ROM a second time. Some DMA related issues with older CD-ROM drives " +"are known to be resolved in this way." +msgstr "" -#~ msgid "Floppy Disk Reliability" -#~ msgstr "Sự đáng tin cậy của đĩa mềm" +#. Tag: para +#: boot-installer.xml:3261 +#, no-c-format +msgid "" +"If this does not work, then try the suggestions in the subsections below. " +"Most, but not all, suggestions discussed there are valid for both CD-ROM and " +"DVD, but we'll use the term CD-ROM for simplicity." +msgstr "" -#~ msgid "" -#~ "The biggest problem for people using floppy disks to install Debian seems " -#~ "to be floppy disk reliability." -#~ msgstr "" -#~ "Sự khó khăn lớn nhất khi người dùng đĩa mềm để cài đặt Debian có vẻ là sự " -#~ "đáng tin cậy của đĩa mềm." +#. Tag: para +#: boot-installer.xml:3267 +#, no-c-format +msgid "" +"If you cannot get the installation working from CD-ROM, try one of the other " +"installation methods that are available." +msgstr "" -#, fuzzy -#~ 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 "" -#~ "Đĩa mềm khởi động là đĩa mềm có vấn đề nghiêm trọng nhất, vì nó do phần " -#~ "cứng đọc trực tiếp, trước khi Linux khởi động. Thường phần cứng không đọc " -#~ "đáng tin cậy như trình điều khiển đĩa mềm Linux, và có thể đơn giản dừng, " -#~ "không in ra thông điệp lỗi, nếu nó đọc dữ liệu sai. Cũng có thể gặp lỗi " -#~ "trong những đĩa mềm trình điều khiển, thường được ngụ ý bởi rất nhiều " -#~ "thông điệp về lỗi nhập/xuất trên đĩa." - -#, fuzzy -#~ msgid "" -#~ "If you are having the installation stall at a particular floppy, the " -#~ "first thing you should do is write the image to a different floppy and see if that solves the problem. 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 "" -#~ "Nếu bạn thấy tiến trình cài đặt bị ngừng chạy tại một đĩa mềm riêng, " -#~ "trước tiên bạn nên tải về lại ảnh đĩa mềm đó và ghi nó vào một đĩa mềm " -#~ "khác. Có lẽ không đủ khi đơn giản định dạng lại đĩa " -#~ "mềm, thậm chí nếu có vẻ là đĩa mềm đã được định dạng lại không có lỗi. " -#~ "Thỉnh thoảng có ích khi thử ghi đĩa mềm trên hệ điều hành hay máy khác." +#. Tag: title +#: boot-installer.xml:3275 +#, no-c-format +msgid "Common issues" +msgstr "" -#~ msgid "" -#~ "One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " -#~ "third floppy." -#~ msgstr "" -#~ "Một người dùng nào đó đã thông báo rằng họ đã cần phải ghi những ảnh vào " -#~ "đĩa mềm ba lần trước khi gặp một đĩa mềm hoạt động " -#~ "được, còn sau đó, mọi thứ thì tốt với đĩa mềm thứ ba." +#. Tag: para +#: boot-installer.xml:3278 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not support reading from discs that were burned " +"at high speeds using a modern CD writer." +msgstr "" -#~ 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 "" -#~ "Người dùng khác đã thông báo rằng tiến trình khởi động lại vài lần cùng " -#~ "một đĩa mềm trong ổ đĩa mềm có thể chỉ tới việc khởi động thành công. Các " -#~ "vấn đề này do lỗi trong trình điều khiển đĩa mềm kiểu phần vững hay phần " -#~ "cứng." +#. Tag: para +#: boot-installer.xml:3284 +#, no-c-format +msgid "" +"If your system boots correctly from the CD-ROM, it does not necessarily mean " +"that Linux also supports the CD-ROM (or, more correctly, the controller that " +"your CD-ROM drive is connected to)." +msgstr "" -#~ msgid "Boot Configuration" -#~ msgstr "Cấu hình khởi động" +#. Tag: para +#: boot-installer.xml:3291 +#, no-c-format +msgid "" +"Some older CD-ROM drives do not work correctly if direct memory " +"access (DMA) is enabled." +msgstr "" -#~ 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 ." -#~ msgstr "" -#~ "Nếu bạn gặp khó khăn, hạt nhân treo cứng trong tiến trình khởi động, " -#~ "không nhận diện ngoại vi thật, hay không nhận diện được ổ đĩa, trước tiên " -#~ "bạn cần phải xem lại các tham số khởi động, như được thảo luận trong " -#~ "." +#. Tag: title +#: boot-installer.xml:3302 +#, no-c-format +msgid "How to investigate and maybe solve issues" +msgstr "" -#~ msgid "" -#~ "If you are booting with your own kernel instead of the one supplied with " -#~ "the installer, be sure that CONFIG_DEVFS is set in " -#~ "your kernel. The installer requires CONFIG_DEVFS." -#~ msgstr "" -#~ "Nếu bạn khởi động với hạt nhân riêng thay cho điều có sẵn với trình cài " -#~ "đặt, hãy kiểm tra xem biến CONFIG_DEVFS (hệ thống " -#~ "tập tin thiết bị cấu hình) đã được đặt trong hạt nhân đó. Trình cài đặt " -#~ "cần thiết biến này." +#. Tag: para +#: boot-installer.xml:3303 +#, no-c-format +msgid "If the CD-ROM fails to boot, try the suggestions listed below." +msgstr "" -#~ msgid "" -#~ "Often, problems can be solved by removing add-ons and peripherals, and " -#~ "then trying booting again. Internal modems, sound " -#~ "cards, and Plug-n-Play devices can be especially problematic." -#~ msgstr "" -#~ "Thường, vấn đề có thể giải quyết bằng cách gỡ bỏ phần thêm và ngoại vi, " -#~ "rồi thử lại khởi động. Bộ điều giải nội bộ, thẻ âm " -#~ "thanh và thiết bị cầm-và-chơi có thể gây ra nhiều vấn đề." +#. Tag: para +#: boot-installer.xml:3308 +#, no-c-format +msgid "" +"Check that your BIOS actually supports booting from CD-ROM (older systems " +"possibly don't) and that your CD-ROM drive supports the media you are using." +msgstr "" -#~ 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 mem=512m." -#~ msgstr "" -#~ "Nếu bạn có rất nhiều bộ nhớ được cài đặt trong máy tính, hơn 512M, và " -#~ "trình cài đặt treo cứng trong khi khởi động hạt nhân, có lẽ bạn cần phải " -#~ "thêm một đối số khởi động để hạn chế số lượng bộ nhớ do hạt nhân xem, v." -#~ "d. mem=512m (bộ nhớ)." +#. Tag: para +#: boot-installer.xml:3314 +#, no-c-format +msgid "" +"If you downloaded an iso image, check that the md5sum of that image matches " +"the one listed for the image in the MD5SUMS file that " +"should be present in the same location as where you downloaded the image " +"from. \n" +"$ md5sum debian-testing-i386-netinst.iso\n" +"a20391b12f7ff22ef705cee4059c6b92 debian-testing-i386-netinst." +"iso\n" +" Next, check that the md5sum of the burned CD-ROM " +"matches as well. The following command should work. It uses the size of the " +"image to read the correct number of bytes from the CD-ROM." +msgstr "" -#~ msgid "Common &arch-title; Installation Problems" -#~ msgstr "Vấn đề cài đặt &arch-title; thường" +#. Tag: screen +#: boot-installer.xml:3327 +#, no-c-format +msgid "" +"$ dd if=/dev/cdrom | \\\n" +"> head -c `stat --format=%s debian-testing-i386-netinst.iso` | \\\n" +"> md5sum\n" +"a20391b12f7ff22ef705cee4059c6b92 -\n" +"262668+0 records in\n" +"262668+0 records out\n" +"134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" +msgstr "" -#~ msgid "" -#~ "There are some common installation problems that can be solved or avoided " -#~ "by passing certain boot parameters to the installer." -#~ msgstr "" -#~ "Có một số vấn đề cài đặt thường có thể được giải quyết hay được tránh " -#~ "bằng cách gởi đối số khởi động riêng cho trình cài đặt." +#. Tag: para +#: boot-installer.xml:3332 +#, no-c-format +msgid "" +"If, after the installer has been booted successfully, the CD-ROM is not " +"detected, sometimes simply trying again may solve the problem. If you have " +"more than one CD-ROM drive, try changing the CD-ROM to the other drive. If " +"that does not work or if the CD-ROM is recognized but there are errors when " +"reading from it, try the suggestions listed below. Some basic knowledge of " +"Linux is required for this. To execute any of the commands, you should first " +"switch to the second virtual console (VT2) and activate the shell there." +msgstr "" -#~ msgid "" -#~ "Some systems have floppies with inverted DCLs. If you " -#~ "receive errors reading from the floppy, even when you know the floppy is " -#~ "good, try the parameter floppy=thinkpad." -#~ msgstr "" -#~ "Một số hệ thống riêng có đĩa mềm với DCL bị đảo. Nếu bạn " -#~ "gặp lỗi khi đọc đĩa mềm, ngay cả khi bạn biết được đĩa mềm đó là tốt, hãy " -#~ "thử nhập tham số floppy=thinkpad (đĩa mềm=vùng " -#~ "nghĩ)." +#. Tag: para +#: boot-installer.xml:3344 +#, no-c-format +msgid "" +"Switch to VT4 or view the contents of /var/log/syslog " +"(use nano as editor) to check for any specific error " +"messages. After that, also check the output of dmesg." +msgstr "" -#~ 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 hd=cylinders,heads,sectors." -#~ msgstr "" -#~ "Trên một số hệ thống riêng, như IBM PS/1 hay ValuePoint (mà có trình điều " -#~ "khiển đĩa kiểu ST-506), có lẽ ổ đĩa IDE chưa được nhận diện cho đúng. Lần " -#~ "nữa, hãy thử đầu tiên không có tham số, xem nếu ổ đĩa IDE có được nhận " -#~ "diện cho đúng chưa. Nếu chưa, kiểm tra xem có dạng hình ổ đĩa nào (số " -#~ "hình trụ [cylinders], số đầu [heads] và số rãnh ghi [sectors]) rồi nhập " -#~ "tham số hd=trụ,đầu, rãnh ghi." +#. Tag: para +#: boot-installer.xml:3351 +#, no-c-format +msgid "" +"Check in the output of dmesg if your CD-ROM drive was " +"recognized. You should see something like (the lines do not necessarily have " +"to be consecutive): \n" +"Probing IDE interface ide1...\n" +"hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive\n" +"ide1 at 0x170-0x177,0x376 on irq 15\n" +"hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)\n" +"Uniform CD-ROM driver Revision: 3.20\n" +" If you don't see something like that, chances " +"are the controller your CD-ROM is connected to was not recognized or may be " +"not supported at all. If you know what driver is needed for the controller, " +"you can try loading it manually using modprobe." +msgstr "" -#~ msgid "" -#~ "If you have a very old machine, and the kernel hangs after saying " -#~ "Checking 'hlt' instruction..., then you " -#~ "should try the no-hlt boot argument, which " -#~ "disables this test." -#~ msgstr "" -#~ "Nếu bạn có máy rất cũ, và hạt nhân treo cứng sau khi nói " -#~ "Checking 'hlt' instruction... (đang kiểm " -#~ "tra câu lệnh « đánh »), rồi bạn nên thử nhập tham số no-hlt (không đánh), mà tất khả năng kiểm tra này." +#. Tag: para +#: boot-installer.xml:3365 +#, no-c-format +msgid "" +"Check that there is a device node for your CD-ROM drive under /dev/" +". In the example above, this would be /dev/hdc. There should also be a /dev/cdroms/cdrom0." +msgstr "" -#~ 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 fb=false " -#~ "video=vga16:off to disable the framebuffer console. Only the " -#~ "English language will be available during the installation due to limited " -#~ "console features. See for details." -#~ msgstr "" -#~ "Nếu màn hình bắt đầu hiển thị ảnh lạ khi hạt nhân khởi động, v.d. màn " -#~ "hình hoàn toàn trắng, hoàn toàn đèn hay có rác điểm ảnh màu sắc, có lẽ " -#~ "máy đó chứa thẻ ảnh động không chuyển đổi được sang chế độ bộ đệm khung. " -#~ "Trong trường hợp này, bạn có thể nhập tham số khởi động " -#~ "fb=false video=vga16:off (bộ đệm khung là sai, ảnh " -#~ "động=vga16:tắt) để tắt bàn điều khiển bộ đệm khung. Tiếc là tiến trình " -#~ "cài đặt sẽ chạy chỉ bằng tiếng Anh, do tính năng bàn điều khiển bị hạn " -#~ "chế. Xem để tìm chi tiết." - -#~ msgid "System Freeze During the PCMCIA Configuration Phase" -#~ msgstr "Hệ thống đông đặc trong giai đoạn cấu hình PCMCIA" +#. Tag: para +#: boot-installer.xml:3373 +#, no-c-format +msgid "" +"Use the mount command to check if the CD-ROM is already " +"mounted; if not, try mounting it manually: \n" +"$ mount /dev/hdc /cdrom\n" +" Check if there are any error messages after that " +"command." +msgstr "" -#~ 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 hw-detect/start_pcmcia=false boot parameter. " -#~ "You can then configure PCMCIA after the installation is completed and " -#~ "exclude the resource range causing the problems." -#~ msgstr "" -#~ "Một số mô hình máy tính xách tay kiểu Dell được biết do sụp đổ khi khả " -#~ "năng phát hiện thiết bị PCMCIA thử truy cập một số địa chỉ phần cứng " -#~ "riêng. Máy tính xách tay khác có thể gặp lỗi tương tự. Nếu bạn gặp lỗi " -#~ "như vậy còn không cần có khả năng hỗ trợ PCMCIA trong khi cài đặt, bạn có " -#~ "thể tắt khả năng PCMCIA bằng tham số khởi động hw-detect/" -#~ "start_pcmcia=false (phát hiện phần cứng/khởi chạy " -#~ "PCMCIA=sai). Sau khi cài đặt xong, bạn có thể cấu hình PCMCIA, và loại " -#~ "trừ phạm vị tài nguyên gây ra lỗi đó." +#. Tag: para +#: boot-installer.xml:3383 +#, no-c-format +msgid "" +"Check if DMA is currently enabled: \n" +"$ cd /proc/ide/hdc\n" +"$ grep using_dma settings\n" +"using_dma 1 0 1 rw\n" +" A 1 in the first column after " +"using_dma means it is enabled. If it is, try disabling " +"it: \n" +"$ echo -n \"using_dma:0\" >settings\n" +" Make sure that you are in the directory for the " +"device that corresponds to your CD-ROM drive." +msgstr "" -#~ 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 exclude port 0x800-0x8ff here. There is also " -#~ "a list of some common resource range options in the System " -#~ "resource settings section of the PCMCIA HOWTO. Note that you have " -#~ "to omit the commas, if any, when you enter this value in the installer." -#~ msgstr "" -#~ "Hoặc bạn có thể khởi động trình cài đặt trong chế độ nhà chuyên môn. Lúc " -#~ "đó, bạn sẽ được nhắc nhập các tùy chọn phạm vị tài nguyên cần thiết cho " -#~ "phần cứng đó. Chẳng hạn, nếu bạn có máy tính xách tay kiểu Dell nêu trên, " -#~ "bạn nên nhập đoạn exclude port 0x800-0x8ff (loại " -#~ "trừ cổng số 0x800-0x8ff). Cũng có danh sách một số tùy chọn phạm vị tài " -#~ "nguyên thường trong tiết đoạn thiết lập tài nguyên hệ thống của " -#~ "tài liệu PCMCIA Thế Nào. Ghi chú rằng bạn cần phải bỏ dấu phẩy, " -#~ "nếu có, khi nhập giá trị này vào trình cài đặt." - -#~ msgid "System Freeze while Loading the USB Modules" -#~ msgstr "Hệ thống đông đặc trong khi tải các mô-đun USB" +#. Tag: para +#: boot-installer.xml:3398 +#, no-c-format +msgid "" +"If there are any problems during the installation, try checking the " +"integrity of the CD-ROM using the option near the bottom of the installer's " +"main menu. This option can also be used as a general test if the CD-ROM can " +"be read reliably." +msgstr "" -#~ 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 debian-installer/" -#~ "probe/usb=false parameter at the boot prompt, which will " -#~ "prevent the modules from being loaded." -#~ msgstr "" -#~ "Hạt nhân thường thử cài đặt các mô-đun USB và trình điều khiển bàn phím " -#~ "USB, để hỗ trợ một số bàn phím USB không chuẩn. Tuy nhiên, có một số hệ " -#~ "thống USB bị hỏng trong đó trình điều khiển treo cứng trong khi tải. Sự " -#~ "chỉnh sửa có thể là việc tắt bộ điều khiển USB trong thiết lập BIOS bo " -#~ "mạch chính. Một tùy chọn khác là việc nhập tham số debian-" -#~ "installer/probe/usb=false (trình cài đặt Debian/thăm dò/" -#~ "USB=sai) tại dấu nhắc khởi động, mà sẽ ngăn cản tải mô-đun USB." +#. Tag: title +#: boot-installer.xml:3413 +#, no-c-format +msgid "Floppy Disk Reliability" +msgstr "Sự đáng tin cậy của đĩa mềm" -#~ msgid "Interpreting the Kernel Startup Messages" -#~ msgstr "Giải thích thông điệp khởi chạy hạt nhân" +#. Tag: para +#: boot-installer.xml:3415 +#, no-c-format +msgid "" +"The biggest problem for people using floppy disks to install Debian seems to " +"be floppy disk reliability." +msgstr "" +"Sự khó khăn lớn nhất khi người dùng đĩa mềm để cài đặt Debian có vẻ là sự " +"đáng tin cậy của đĩa mềm." -#~ msgid "" -#~ "During the boot sequence, you may see many messages in the form " -#~ "can't find something , or something " -#~ "not present, can't initialize " -#~ "something , or even " -#~ "this driver release depends on something . 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 )." -#~ msgstr "" -#~ "Trong tiến trình khởi động, có lẽ bạn thấy nhiều thông điệp dạng " -#~ "can't find cái gì (không tìm thấy cái đó), hay " -#~ "cái gì not present (không có " -#~ "cái đó), can't initialize cái gì (không thể sở khởi cái đó), ngay cả " -#~ "this driver release depends on cái gì (bản phát hành trình điều khiển này phụ " -#~ "thuộc vào cái đó). Phần lớn thông điệp này là vô hại. Bạn thấy chúng chỉ " -#~ "vì hạt nhân của hệ thống cài đặt được xây dựng để chạy trên máy tính có " -#~ "nhiều thiết bị ngoại vi khác nhau. Không có máy tính riêng lẻ có tất cả " -#~ "các thiết bị ngoại vi, vì vậy hệ điều hành có thể hiển thị một số thông " -#~ "điệp lỗi trong khi tìm ngoại vi không có. Có lẽ bạn cũng xem hệ thống tạm " -#~ "ngừng một chút. Có xảy ra trong khi nó đợi thiết bị đáp ứng, nhưng thiết " -#~ "bị đó không nằm trên hệ thống của bạn. Nếu tiến trình khởi động hệ thống " -#~ "chạy quá lâu, bạn có thể tạo một hạt nhân riêng vào lúc sau (xem )." +#. Tag: para +#: boot-installer.xml:3420 +#, fuzzy, 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 "" +"Đĩa mềm khởi động là đĩa mềm có vấn đề nghiêm trọng nhất, vì nó do phần cứng " +"đọc trực tiếp, trước khi Linux khởi động. Thường phần cứng không đọc đáng " +"tin cậy như trình điều khiển đĩa mềm Linux, và có thể đơn giản dừng, không " +"in ra thông điệp lỗi, nếu nó đọc dữ liệu sai. Cũng có thể gặp lỗi trong " +"những đĩa mềm trình điều khiển, thường được ngụ ý bởi rất nhiều thông điệp " +"về lỗi nhập/xuất trên đĩa." + +#. Tag: para +#: boot-installer.xml:3429 +#, fuzzy, no-c-format +msgid "" +"If you are having the installation stall at a particular floppy, the first " +"thing you should do is write the image to a different " +"floppy and see if that solves the problem. 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 "" +"Nếu bạn thấy tiến trình cài đặt bị ngừng chạy tại một đĩa mềm riêng, trước " +"tiên bạn nên tải về lại ảnh đĩa mềm đó và ghi nó vào một đĩa mềm " +"khác. Có lẽ không đủ khi đơn giản định dạng lại đĩa " +"mềm, thậm chí nếu có vẻ là đĩa mềm đã được định dạng lại không có lỗi. Thỉnh " +"thoảng có ích khi thử ghi đĩa mềm trên hệ điều hành hay máy khác." + +#. Tag: para +#: boot-installer.xml:3438 +#, no-c-format +msgid "" +"One user reports he had to write the images to floppy three times before one worked, and then everything was fine with the " +"third floppy." +msgstr "" +"Một người dùng nào đó đã thông báo rằng họ đã cần phải ghi những ảnh vào đĩa " +"mềm ba lần trước khi gặp một đĩa mềm hoạt động được, " +"còn sau đó, mọi thứ thì tốt với đĩa mềm thứ ba." -#~ msgid "Bug Reporter" -#~ msgstr "Bộ thông báo lỗi" +#. Tag: para +#: boot-installer.xml:3444 +#, no-c-format +msgid "" +"Normally you should not have to download a floppy image again, but if you " +"are experiencing problems it is always useful to verify that the images were " +"downloaded correctly by verifying their md5sums." +msgstr "" -#~ 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 "" -#~ "Nếu bạn chạy qua giai đoạn khởi động đầu tiên, nhưng không thể cài đặt " -#~ "xong, mục trình đơn thông báo lỗi có thể có ích. Nó cho bạn khả năng cất " -#~ "giữ vào đĩa mềm bản ghi lỗi hệ thống và thông tin cấu hình của trình cài " -#~ "đặt, hoặc tải về nó bằng trình duyệt Mạng. Thông tin này có thể giúp đỡ " -#~ "bạn tìm biết nguyên nhân lỗi và cách sửa nó. Khi bạn thông báo lỗi, cũng " -#~ "có thể đính kèm thông tin này." +#. Tag: para +#: boot-installer.xml:3450 +#, 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 "" +"Người dùng khác đã thông báo rằng tiến trình khởi động lại vài lần cùng một " +"đĩa mềm trong ổ đĩa mềm có thể chỉ tới việc khởi động thành công. Các vấn đề " +"này do lỗi trong trình điều khiển đĩa mềm kiểu phần vững hay phần cứng." + +#. Tag: title +#: boot-installer.xml:3459 +#, no-c-format +msgid "Boot Configuration" +msgstr "Cấu hình khởi động" + +#. Tag: para +#: boot-installer.xml:3461 +#, 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 " +"." +msgstr "" +"Nếu bạn gặp khó khăn, hạt nhân treo cứng trong tiến trình khởi động, không " +"nhận diện ngoại vi thật, hay không nhận diện được ổ đĩa, trước tiên bạn cần " +"phải xem lại các tham số khởi động, như được thảo luận trong ." + +#. Tag: para +#: boot-installer.xml:3468 +#, no-c-format +msgid "" +"If you are booting with your own kernel instead of the one supplied with the " +"installer, be sure that CONFIG_DEVFS is set in your " +"kernel. The installer requires CONFIG_DEVFS." +msgstr "" +"Nếu bạn khởi động với hạt nhân riêng thay cho điều có sẵn với trình cài đặt, " +"hãy kiểm tra xem biến CONFIG_DEVFS (hệ thống tập tin " +"thiết bị cấu hình) đã được đặt trong hạt nhân đó. Trình cài đặt cần thiết " +"biến này." + +#. Tag: para +#: boot-installer.xml:3475 +#, no-c-format +msgid "" +"Often, problems can be solved by removing add-ons and peripherals, and then " +"trying booting again. Internal modems, sound cards, and " +"Plug-n-Play devices can be especially problematic." +msgstr "" +"Thường, vấn đề có thể giải quyết bằng cách gỡ bỏ phần thêm và ngoại vi, rồi " +"thử lại khởi động. Bộ điều giải nội bộ, thẻ âm thanh và " +"thiết bị cầm-và-chơi có thể gây ra nhiều vấn đề." -#~ msgid "" -#~ "Other pertinent installation messages may be found in /var/log/" -#~ " during the installation, and /var/log/installer/ after the computer has been booted into the installed system." -#~ msgstr "" -#~ "Thông điệp cài đặt thích hợp khác nằm trong thư mục /var/log/ trong khi cài đặt, rồi trong thư mục /var/log/" -#~ "installer/ sau khi máy tính đã khởi động vào hệ thống mới được " -#~ "cài đặt." +#. Tag: para +#: boot-installer.xml:3481 +#, 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 mem=512m." +msgstr "" +"Nếu bạn có rất nhiều bộ nhớ được cài đặt trong máy tính, hơn 512M, và trình " +"cài đặt treo cứng trong khi khởi động hạt nhân, có lẽ bạn cần phải thêm một " +"đối số khởi động để hạn chế số lượng bộ nhớ do hạt nhân xem, v.d. " +"mem=512m (bộ nhớ)." + +#. Tag: title +#: boot-installer.xml:3492 +#, no-c-format +msgid "Common &arch-title; Installation Problems" +msgstr "Vấn đề cài đặt &arch-title; thường" + +#. Tag: para +#: boot-installer.xml:3493 +#, 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 "" +"Có một số vấn đề cài đặt thường có thể được giải quyết hay được tránh bằng " +"cách gởi đối số khởi động riêng cho trình cài đặt." -#~ msgid "Submitting Installation Reports" -#~ msgstr "Đệ trình báo cáo cài đặt" +#. Tag: para +#: boot-installer.xml:3498 +#, no-c-format +msgid "" +"Some systems have floppies with inverted DCLs. If you receive " +"errors reading from the floppy, even when you know the floppy is good, try " +"the parameter floppy=thinkpad." +msgstr "" +"Một số hệ thống riêng có đĩa mềm với DCL bị đảo. Nếu bạn gặp " +"lỗi khi đọc đĩa mềm, ngay cả khi bạn biết được đĩa mềm đó là tốt, hãy thử " +"nhập tham số floppy=thinkpad (đĩa mềm=vùng nghĩ)." -#~ 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 "" -#~ "Nếu bạn vẫn còn gặp khó khăn, xin hãy đệ trình báo cáo cài đặt. Chúng tôi " -#~ "khuyên bạn gởi một báo cáo cài đặt, thậm chí nếu tiến trình cài đặt là " -#~ "thành công, để tập hợp càng nhiều thông tin càng có thể về các cấu hình " -#~ "phần cứng khác nhau. [Dịch giả: nếu bạn gặp " -#~ "khó khăn viết tiếng Anh, bạn viết bằng tiếng Việt và gởi báo cáo cho Nhóm " -#~ "Việt Hoá Tự Do vi-VN@googlegroups.com nhé. Chúng tôi sẽ " -#~ "dịch cho bạn.]" +#. Tag: para +#: boot-installer.xml:3504 +#, 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 hd=cylinders," +"heads,sectors." +msgstr "" +"Trên một số hệ thống riêng, như IBM PS/1 hay ValuePoint (mà có trình điều " +"khiển đĩa kiểu ST-506), có lẽ ổ đĩa IDE chưa được nhận diện cho đúng. Lần " +"nữa, hãy thử đầu tiên không có tham số, xem nếu ổ đĩa IDE có được nhận diện " +"cho đúng chưa. Nếu chưa, kiểm tra xem có dạng hình ổ đĩa nào (số hình trụ " +"[cylinders], số đầu [heads] và số rãnh ghi [sectors]) rồi nhập tham số " +"hd=trụ,đầu, " +"rãnh ghi." + +#. Tag: para +#: boot-installer.xml:3513 +#, no-c-format +msgid "" +"If you have a very old machine, and the kernel hangs after saying " +"Checking 'hlt' instruction..., then you " +"should try the no-hlt boot argument, which disables " +"this test." +msgstr "" +"Nếu bạn có máy rất cũ, và hạt nhân treo cứng sau khi nói " +"Checking 'hlt' instruction... (đang kiểm " +"tra câu lệnh « đánh »), rồi bạn nên thử nhập tham số no-hlt (không đánh), mà tất khả năng kiểm tra này." + +#. Tag: para +#: boot-installer.xml:3520 +#, 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 fb=false " +"video=vga16:off to disable the framebuffer console. Only the " +"English language will be available during the installation due to limited " +"console features. See for details." +msgstr "" +"Nếu màn hình bắt đầu hiển thị ảnh lạ khi hạt nhân khởi động, v.d. màn hình " +"hoàn toàn trắng, hoàn toàn đèn hay có rác điểm ảnh màu sắc, có lẽ máy đó " +"chứa thẻ ảnh động không chuyển đổi được sang chế độ bộ đệm khung. Trong " +"trường hợp này, bạn có thể nhập tham số khởi động fb=false " +"video=vga16:off (bộ đệm khung là sai, ảnh động=vga16:tắt) để tắt " +"bàn điều khiển bộ đệm khung. Tiếc là tiến trình cài đặt sẽ chạy chỉ bằng " +"tiếng Anh, do tính năng bàn điều khiển bị hạn chế. Xem để tìm chi tiết." + +#. Tag: title +#: boot-installer.xml:3534 +#, no-c-format +msgid "System Freeze During the PCMCIA Configuration Phase" +msgstr "Hệ thống đông đặc trong giai đoạn cấu hình PCMCIA" + +#. Tag: para +#: boot-installer.xml:3535 +#, 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 " +"hw-detect/start_pcmcia=false boot parameter. You can " +"then configure PCMCIA after the installation is completed and exclude the " +"resource range causing the problems." +msgstr "" +"Một số mô hình máy tính xách tay kiểu Dell được biết do sụp đổ khi khả năng " +"phát hiện thiết bị PCMCIA thử truy cập một số địa chỉ phần cứng riêng. Máy " +"tính xách tay khác có thể gặp lỗi tương tự. Nếu bạn gặp lỗi như vậy còn " +"không cần có khả năng hỗ trợ PCMCIA trong khi cài đặt, bạn có thể tắt khả " +"năng PCMCIA bằng tham số khởi động hw-detect/start_pcmcia=false (phát hiện phần cứng/khởi chạy PCMCIA=sai). Sau khi cài đặt xong, " +"bạn có thể cấu hình PCMCIA, và loại trừ phạm vị tài nguyên gây ra lỗi đó." + +#. Tag: para +#: boot-installer.xml:3545 +#, 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 " +"exclude port 0x800-0x8ff here. There is also a list " +"of some common resource range options in the System resource " +"settings section of the PCMCIA HOWTO. Note that you have to omit the " +"commas, if any, when you enter this value in the installer." +msgstr "" +"Hoặc bạn có thể khởi động trình cài đặt trong chế độ nhà chuyên môn. Lúc đó, " +"bạn sẽ được nhắc nhập các tùy chọn phạm vị tài nguyên cần thiết cho phần " +"cứng đó. Chẳng hạn, nếu bạn có máy tính xách tay kiểu Dell nêu trên, bạn nên " +"nhập đoạn exclude port 0x800-0x8ff (loại trừ cổng số " +"0x800-0x8ff). Cũng có danh sách một số tùy chọn phạm vị tài nguyên thường " +"trong tiết đoạn thiết lập tài nguyên hệ thống của tài liệu PCMCIA " +"Thế Nào. Ghi chú rằng bạn cần phải bỏ dấu phẩy, nếu có, khi nhập giá " +"trị này vào trình cài đặt." + +#. Tag: title +#: boot-installer.xml:3562 +#, no-c-format +msgid "System Freeze while Loading the USB Modules" +msgstr "Hệ thống đông đặc trong khi tải các mô-đun USB" + +#. Tag: para +#: boot-installer.xml:3563 +#, 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 debian-installer/probe/usb=false parameter at the boot prompt, which will prevent the modules from " +"being loaded." +msgstr "" +"Hạt nhân thường thử cài đặt các mô-đun USB và trình điều khiển bàn phím USB, " +"để hỗ trợ một số bàn phím USB không chuẩn. Tuy nhiên, có một số hệ thống USB " +"bị hỏng trong đó trình điều khiển treo cứng trong khi tải. Sự chỉnh sửa có " +"thể là việc tắt bộ điều khiển USB trong thiết lập BIOS bo mạch chính. Một " +"tùy chọn khác là việc nhập tham số debian-installer/probe/" +"usb=false (trình cài đặt Debian/thăm dò/USB=sai) tại dấu nhắc " +"khởi động, mà sẽ ngăn cản tải mô-đun USB." + +#. Tag: title +#: boot-installer.xml:3577 +#, no-c-format +msgid "Interpreting the Kernel Startup Messages" +msgstr "Giải thích thông điệp khởi chạy hạt nhân" + +#. Tag: para +#: boot-installer.xml:3579 +#, no-c-format +msgid "" +"During the boot sequence, you may see many messages in the form " +"can't find something , or something " +"not present, can't initialize " +"something , or even " +"this driver release depends on something . 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 )." +msgstr "" +"Trong tiến trình khởi động, có lẽ bạn thấy nhiều thông điệp dạng " +"can't find cái gì (không tìm thấy cái đó), hay " +"cái gì not present (không có cái " +"đó), can't initialize cái gì (không thể sở khởi cái đó), ngay cả this " +"driver release depends on cái gì (bản phát hành trình điều khiển này phụ thuộc vào cái đó). " +"Phần lớn thông điệp này là vô hại. Bạn thấy chúng chỉ vì hạt nhân của hệ " +"thống cài đặt được xây dựng để chạy trên máy tính có nhiều thiết bị ngoại vi " +"khác nhau. Không có máy tính riêng lẻ có tất cả các thiết bị ngoại vi, vì " +"vậy hệ điều hành có thể hiển thị một số thông điệp lỗi trong khi tìm ngoại " +"vi không có. Có lẽ bạn cũng xem hệ thống tạm ngừng một chút. Có xảy ra trong " +"khi nó đợi thiết bị đáp ứng, nhưng thiết bị đó không nằm trên hệ thống của " +"bạn. Nếu tiến trình khởi động hệ thống chạy quá lâu, bạn có thể tạo một hạt " +"nhân riêng vào lúc sau (xem )." + +#. Tag: title +#: boot-installer.xml:3604 +#, fuzzy, no-c-format +msgid "Reporting Installation Problems" +msgstr "Vấn đề cài đặt &arch-title; thường" + +#. Tag: para +#: boot-installer.xml:3605 +#, fuzzy, no-c-format +msgid "" +"If you get through the initial boot phase but cannot complete the install, " +"the menu option Save debug logs may be helpful. " +"It lets you store system error logs and configuration information from the " +"installer to a floppy, or download them using 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 "" +"Nếu bạn chạy qua giai đoạn khởi động đầu tiên, nhưng không thể cài đặt xong, " +"mục trình đơn thông báo lỗi có thể có ích. Nó cho bạn khả năng cất giữ vào " +"đĩa mềm bản ghi lỗi hệ thống và thông tin cấu hình của trình cài đặt, hoặc " +"tải về nó bằng trình duyệt Mạng. Thông tin này có thể giúp đỡ bạn tìm biết " +"nguyên nhân lỗi và cách sửa nó. Khi bạn thông báo lỗi, cũng có thể đính kèm " +"thông tin này." + +#. Tag: para +#: boot-installer.xml:3616 +#, no-c-format +msgid "" +"Other pertinent installation messages may be found in /var/log/ during the installation, and /var/log/installer/ after the computer has been booted into the installed system." +msgstr "" +"Thông điệp cài đặt thích hợp khác nằm trong thư mục /var/log/ trong khi cài đặt, rồi trong thư mục /var/log/installer/" +" sau khi máy tính đã khởi động vào hệ thống mới được cài đặt." + +#. Tag: title +#: boot-installer.xml:3627 +#, no-c-format +msgid "Submitting Installation Reports" +msgstr "Đệ trình báo cáo cài đặt" + +#. Tag: para +#: boot-installer.xml:3628 +#, 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 "" +"Nếu bạn vẫn còn gặp khó khăn, xin hãy đệ trình báo cáo cài đặt. Chúng tôi " +"khuyên bạn gởi một báo cáo cài đặt, thậm chí nếu tiến trình cài đặt là thành " +"công, để tập hợp càng nhiều thông tin càng có thể về các cấu hình phần cứng " +"khác nhau. [Dịch giả: nếu bạn gặp khó khăn viết " +"tiếng Anh, bạn viết bằng tiếng Việt và gởi báo cáo cho Nhóm Việt Hoá Tự Do " +"vi-VN@googlegroups.com nhé. Chúng tôi sẽ dịch cho bạn.]" + +#. Tag: para +#: boot-installer.xml:3635 +#, no-c-format +msgid "" +"Note that your installation report will be published in the Debian Bug " +"Tracking System (BTS) and forwarded to a public mailing list. Make sure that " +"you use an E-Mail address that you do not mind being made public." +msgstr "" -#~ 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 (apt-get install installation-report reportbug) and run the command reportbug installation-report." -#~ msgstr "" -#~ "Nếu bạn có hệ thống Debian hoạt động, phương pháp dễ nhất để gởi báo cáo " -#~ "cài đặt là cài đặt gói installation-report (báo cáo " -#~ "cài đặt) và reportbug (thông báo lỗi) bằng lệnh " -#~ "apt-get install installation-report reportbug, rồi " -#~ "chạy lệnh thông báo lỗi reportbug installation-report." +#. Tag: para +#: boot-installer.xml:3641 +#, 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 " +"(apt-get install installation-report reportbug) and run " +"the command reportbug installation-report." +msgstr "" +"Nếu bạn có hệ thống Debian hoạt động, phương pháp dễ nhất để gởi báo cáo cài " +"đặt là cài đặt gói installation-report (báo cáo cài " +"đặt) và reportbug (thông báo lỗi) bằng lệnh " +"apt-get install installation-report reportbug, rồi chạy " +"lệnh thông báo lỗi reportbug installation-report." + +#. Tag: para +#: boot-installer.xml:3648 +#, fuzzy, no-c-format +msgid "" +"Alternatively you can use this template when filling out installation " +"reports, and file the report as a bug report against the " +"installation-reports pseudo package, by sending it to " +"submit@bugs.debian.org. \n" +"Package: installation-reports\n" +"\n" +"Boot method: <How did you boot the installer? CD? floppy? network?>\n" +"Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" +"\n" +"Base System Installation Checklist:\n" +"[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" +"\n" +"Initial boot: [ ]\n" +"Detect network card: [ ]\n" +"Configure network: [ ]\n" +"Detect CD: [ ]\n" +"Load installer modules: [ ]\n" +"Detect hard drives: [ ]\n" +"Partition hard drives: [ ]\n" +"Install base system: [ ]\n" +"Clock/timezone setup: [ ]\n" +"User/password setup: [ ]\n" +"Install tasks: [ ]\n" +"Install boot loader: [ ]\n" +"Overall install: [ ]\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" +" 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 "" +"Xin hãy dùng biểu mẫu này khi điền báo cáo cài đặt, và đệ trình báo cáo như " +"là báo cáo lỗi đối với gói ảo installation-reports " +"(các báo cáo cài đặt), bằng cách gởi nó cho địa chỉ submit@bugs." +"debian.org. \n" +"Package [Gói]: installation-reports\n" +"\n" +"Boot method [Phương pháp khởi động]: <Bạn đã khởi động trình cài đặt như " +"thế nào? Từ đĩa CD (ghi « CD »)? Từ đĩa mềm (floppy)? Qua mạng (network)?" +">\n" +"Image version [Phiên bản ảnh]: <Ngày tháng và nơi bạn đã lấy ảnh cài " +"đặt>\n" +"Date [Ngày]: <Ngày tháng và giờ cài đặt>\n" +"\n" +"Machine [Máy]: <Mô tả máy tính (v.d. IBM Thinkpad R32)>\n" +"Processor [Bộ xử lý]:\n" +"Memory [Bộ nhớ]:\n" +"Partitions [Phân vùng]: <df -Tl là đủ; bảng phân vùng thô là tốt hơn>\n" +"\n" +"Output of lspci and lspci -n [Dữ liệu xuất khi nhập mỗi lệnh {lspci} và " +"{lspci -n}]:\n" +"\n" +"Base System Installation Checklist [Danh sách kiểm tra việc cài đặt hệ thống " +"cơ sở):\n" +"[O] = Được, [E] = Lỗi (xin hãy giải thích bên dưới), [ ] = chưa thử\n" +"\n" +"Initial boot worked [Việc khởi động đầu tiên là thành công]: [ ]\n" +"Configure network HW [Cấu hình phần cứng mạng]: [ ]\n" +"Config network [Cấu hình mạng]: [ ]\n" +"Detect CD [Phát hiện đĩa CD]: [ ]\n" +"Load installer modules [Tải các mô-đun cài đặt]: [ ]\n" +"Detect hard drives [Phát hiện các đĩa cứng]: [ ]\n" +"Partition hard drives [Phân vùng các đĩa cứng]: [ ]\n" +"Create file systems [Tạo các hệ thống tập tin]: [ ]\n" +"Mount partitions [Gắn kết các phân vùng]: [ ]\n" +"Install base system [Cài đặt hệ thống cơ sở]: [ ]\n" +"Install boot loader [Cài đặt bộ tải khởi động]: [ ]\n" +"Reboot [Khởi động lại]: [ ]\n" +"\n" +"Comments/Problems [Chú thích/Vấn đề]:\n" +"\n" +"<Mô tả của việc cài đặt, và các chú thích, chi tiết, ý nghĩ nào trong " +"tiến trình cài đặt đầu tiên.>\n" +" Trong báo cáo lỗi, xin hãy diễn tả vấn đề, gồm " +"những thông điệp hạt nhân cuối cùng đã hiển thị nếu hạt nhân đã treo cứng. " +"Diễn tả những bước đến tình trạng vấn đề này." -#, fuzzy -#~ msgid "" -#~ "Please use this template when filling out installation reports, and file " -#~ "the report as a bug report against the installation-reports pseudo package, by sending it to submit@bugs.debian." -#~ "org. \n" -#~ "Package: installation-reports\n" -#~ "\n" -#~ "Boot method: <How did you boot the installer? CD? floppy? network?" -#~ ">\n" -#~ "Image version: <Full URL to image you downloaded is best>\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 -nn and lspci -vnn:\n" -#~ "\n" -#~ "Base System Installation Checklist:\n" -#~ "[O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it\n" -#~ "\n" -#~ "Initial boot: [ ]\n" -#~ "Detect network card: [ ]\n" -#~ "Configure network: [ ]\n" -#~ "Detect CD: [ ]\n" -#~ "Load installer modules: [ ]\n" -#~ "Detect hard drives: [ ]\n" -#~ "Partition hard drives: [ ]\n" -#~ "Install base system: [ ]\n" -#~ "Clock/timezone setup: [ ]\n" -#~ "User/password setup: [ ]\n" -#~ "Install tasks: [ ]\n" -#~ "Install boot loader: [ ]\n" -#~ "Overall install: [ ]\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" -#~ " 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 "" -#~ "Xin hãy dùng biểu mẫu này khi điền báo cáo cài đặt, và đệ trình báo cáo " -#~ "như là báo cáo lỗi đối với gói ảo installation-reports (các báo cáo cài đặt), bằng cách gởi nó cho địa chỉ " -#~ "submit@bugs.debian.org. \n" -#~ "Package [Gói]: installation-reports\n" -#~ "\n" -#~ "Boot method [Phương pháp khởi động]: <Bạn đã khởi động trình cài đặt " -#~ "như thế nào? Từ đĩa CD (ghi « CD »)? Từ đĩa mềm (floppy)? Qua mạng " -#~ "(network)?>\n" -#~ "Image version [Phiên bản ảnh]: <Ngày tháng và nơi bạn đã lấy ảnh cài " -#~ "đặt>\n" -#~ "Date [Ngày]: <Ngày tháng và giờ cài đặt>\n" -#~ "\n" -#~ "Machine [Máy]: <Mô tả máy tính (v.d. IBM Thinkpad R32)>\n" -#~ "Processor [Bộ xử lý]:\n" -#~ "Memory [Bộ nhớ]:\n" -#~ "Partitions [Phân vùng]: <df -Tl là đủ; bảng phân vùng thô là tốt " -#~ "hơn>\n" -#~ "\n" -#~ "Output of lspci and lspci -n [Dữ liệu xuất khi nhập mỗi lệnh {lspci} và " -#~ "{lspci -n}]:\n" -#~ "\n" -#~ "Base System Installation Checklist [Danh sách kiểm tra việc cài đặt hệ " -#~ "thống cơ sở):\n" -#~ "[O] = Được, [E] = Lỗi (xin hãy giải thích bên dưới), [ ] = chưa thử\n" -#~ "\n" -#~ "Initial boot worked [Việc khởi động đầu tiên là thành công]: [ ]\n" -#~ "Configure network HW [Cấu hình phần cứng mạng]: [ ]\n" -#~ "Config network [Cấu hình mạng]: [ ]\n" -#~ "Detect CD [Phát hiện đĩa CD]: [ ]\n" -#~ "Load installer modules [Tải các mô-đun cài đặt]: [ ]\n" -#~ "Detect hard drives [Phát hiện các đĩa cứng]: [ ]\n" -#~ "Partition hard drives [Phân vùng các đĩa cứng]: [ ]\n" -#~ "Create file systems [Tạo các hệ thống tập tin]: [ ]\n" -#~ "Mount partitions [Gắn kết các phân vùng]: [ ]\n" -#~ "Install base system [Cài đặt hệ thống cơ sở]: [ ]\n" -#~ "Install boot loader [Cài đặt bộ tải khởi động]: [ ]\n" -#~ "Reboot [Khởi động lại]: [ ]\n" -#~ "\n" -#~ "Comments/Problems [Chú thích/Vấn đề]:\n" -#~ "\n" -#~ "<Mô tả của việc cài đặt, và các chú thích, chi tiết, ý nghĩ nào trong " -#~ "tiến trình cài đặt đầu tiên.>\n" -#~ " Trong báo cáo lỗi, xin hãy diễn tả vấn đề, " -#~ "gồm những thông điệp hạt nhân cuối cùng đã hiển thị nếu hạt nhân đã treo " -#~ "cứng. Diễn tả những bước đến tình trạng vấn đề này." +#~ msgid "Bug Reporter" +#~ msgstr "Bộ thông báo lỗi" #~ msgid "" #~ "Proceed to the next chapter to continue the installation where you will " diff --git a/po/vi/preparing.po b/po/vi/preparing.po index 70cc1487b..0e5cf1998 100644 --- a/po/vi/preparing.po +++ b/po/vi/preparing.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: preparing\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-10-26 16:20+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-08-10 21:46+0930\n" "Last-Translator: Clytie Siddall \n" "Language-Team: Vietnamese \n" @@ -3303,26 +3303,6 @@ msgstr "" #: preparing.xml:2079 #, 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 " -"." -msgstr "" -"Các bo mạch chủ tốt nhất hỗ trợ RAM tính chẵn lẻ (parity RAM), sẽ thật báo " -"bạn biết nếu hệ thống có lỗi kiểu bit đơn trong bộ nhớ RAM. Tiếc là chúng " -"không cung cấp cách sửa lỗi như vậy: chúng thường sụp đổi đúng sau khi báo " -"bạn biết về RAM sai. Tuy nhiên, sự biết về bộ nhớ sai vẫn còn là tốt hơn " -"trường hợp mà nó chèn lỗi trong dữ liệu một cách im lặng. Vì vậy các hệ " -"thống tốt nhất có bo mạch chủ hỗ trợ mô-đun bộ nhớ cả tính chẵn lẻ lẫn tính " -"chẵn lẻ thật; xem ." - -#. Tag: para -#: preparing.xml:2090 -#, 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." @@ -3332,13 +3312,13 @@ msgstr "" "ra bo mạch chủ ngắt tiến trình khi gặp lỗi tính chẵn lẻ bộ nhớ." #. Tag: title -#: preparing.xml:2098 +#: preparing.xml:2087 #, no-c-format msgid "The Turbo Switch" msgstr "Cái chuyển tốc độ" #. Tag: para -#: preparing.xml:2099 +#: preparing.xml:2088 #, no-c-format msgid "" "Many systems have a turbo switch that controls the " @@ -3358,13 +3338,13 @@ msgstr "" "mềm điều khiển cái chuyển turbo." #. Tag: title -#: preparing.xml:2112 +#: preparing.xml:2101 #, no-c-format msgid "Cyrix CPUs and Floppy Disk Errors" msgstr "CPU Cyrix và lỗi đĩa mềm" #. Tag: para -#: preparing.xml:2113 +#: preparing.xml:2102 #, no-c-format msgid "" "Many users of Cyrix CPUs have had to disable the cache in their systems " @@ -3380,7 +3360,7 @@ msgstr "" "tắt." #. Tag: para -#: preparing.xml:2121 +#: preparing.xml:2110 #, no-c-format msgid "" "We don't think this is necessarily the fault of the Cyrix CPU. It may be " @@ -3394,13 +3374,13 @@ msgstr "" "còn hợp lệ lại sau khi chuyển đổi từ mã 16-bit sang 32-bit." #. Tag: title -#: preparing.xml:2131 +#: preparing.xml:2120 #, no-c-format msgid "Peripheral Hardware Settings" msgstr "Thiết lập phần cứng ngoại vi" #. Tag: para -#: preparing.xml:2132 +#: preparing.xml:2121 #, no-c-format msgid "" "You may have to change some settings or jumpers on your computer's " @@ -3414,7 +3394,7 @@ msgstr "" "phần cứng: nó chỉ cố gắng cung cấp mẹo hữu ích." #. Tag: para -#: preparing.xml:2139 +#: preparing.xml:2128 #, no-c-format msgid "" "If any cards provide mapped memory, the memory should be " @@ -3427,13 +3407,13 @@ msgstr "" "tại một địa chỉ ít nhất 1 MB lớn hơn tổng số RAM nằm trong hệ thống đó." #. Tag: title -#: preparing.xml:2150 +#: preparing.xml:2139 #, no-c-format msgid "USB BIOS support and keyboards" msgstr "Hỗ trợ BIOS và bàn phím kiểu USB" #. Tag: para -#: preparing.xml:2151 +#: preparing.xml:2140 #, no-c-format msgid "" "If you have no AT-style keyboard and only a USB model, you may need to " @@ -3454,13 +3434,13 @@ msgstr "" "hay USB keyboard support (khả năng hỗ trợ bàn phím USB)." #. Tag: title -#: preparing.xml:2164 +#: preparing.xml:2153 #, no-c-format msgid "More than 64 MB RAM" msgstr "Hơn 64 MB RAM" #. Tag: para -#: preparing.xml:2165 +#: preparing.xml:2154 #, no-c-format msgid "" "The Linux Kernel cannot always detect what amount of RAM you have. If this " @@ -3470,13 +3450,13 @@ msgstr "" "máy tính. Trong trường hợp này, xem ." #. Tag: title -#: preparing.xml:2174 +#: preparing.xml:2163 #, no-c-format msgid "Display visibility on OldWorld Powermacs" msgstr "Tầm nhìn bộ trình bày của PowerMac kiểu cũ" #. Tag: para -#: preparing.xml:2175 +#: preparing.xml:2164 #, no-c-format msgid "" "Some OldWorld Powermacs, most notably those with the control " @@ -3499,3 +3479,20 @@ msgstr "" "thay đổi thiết lập trình bày dưới hệ điều hành MacOS thành 256 màu sắc thay " "cho thousands (mấy nghìn) hay millions (mấy " "tỷ) màu sắc." + +#~ 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 ." +#~ msgstr "" +#~ "Các bo mạch chủ tốt nhất hỗ trợ RAM tính chẵn lẻ (parity RAM), sẽ thật " +#~ "báo bạn biết nếu hệ thống có lỗi kiểu bit đơn trong bộ nhớ RAM. Tiếc là " +#~ "chúng không cung cấp cách sửa lỗi như vậy: chúng thường sụp đổi đúng sau " +#~ "khi báo bạn biết về RAM sai. Tuy nhiên, sự biết về bộ nhớ sai vẫn còn là " +#~ "tốt hơn trường hợp mà nó chèn lỗi trong dữ liệu một cách im lặng. Vì vậy " +#~ "các hệ thống tốt nhất có bo mạch chủ hỗ trợ mô-đun bộ nhớ cả tính chẵn lẻ " +#~ "lẫn tính chẵn lẻ thật; xem ." diff --git a/po/vi/using-d-i.po b/po/vi/using-d-i.po index e42e00339..cd8fa27a0 100644 --- a/po/vi/using-d-i.po +++ b/po/vi/using-d-i.po @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: using-d-i\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-10-21 22:26+0930\n" "Last-Translator: Clytie Siddall \n" "Language-Team: Vietnamese \n" @@ -3692,14 +3692,13 @@ msgstr "" #. Tag: para #: using-d-i.xml:2302 -#, no-c-format +#, fuzzy, 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 fdisk /" "mbr 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 ." +"Debian!" msgstr "" "Nếu bạn không còn có thể khởi động lại vào Windows 9x (hay DOS) sau bước " "này, bạn sẽ cần phải sử dụng đĩa khởi động Windows 9x (MS-DOS), và dùng lệnh " @@ -3709,13 +3708,13 @@ msgstr "" "\"reactivating-win\"/>." #. Tag: title -#: using-d-i.xml:2319 +#: using-d-i.xml:2318 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "Cài đặt bộ tải khởi động ELILO vào đĩa cứng" #. Tag: para -#: using-d-i.xml:2321 +#: using-d-i.xml:2320 #, no-c-format msgid "" "The &architecture; boot loader is called elilo. It is modeled " @@ -3743,7 +3742,7 @@ msgstr "" "quote> thật để làm việc tải và khởi chạy hạt nhân Linux." #. Tag: para -#: using-d-i.xml:2337 +#: using-d-i.xml:2336 #, no-c-format msgid "" "The elilo configuration and installation is done as the last " @@ -3761,13 +3760,13 @@ msgstr "" "gốc của máy tính." #. Tag: title -#: using-d-i.xml:2349 +#: using-d-i.xml:2348 #, no-c-format msgid "Choose the correct partition!" msgstr "Chọn phân vùng đúng đi." #. Tag: para -#: using-d-i.xml:2351 +#: using-d-i.xml:2350 #, no-c-format msgid "" "The criteria for selecting a partition is that it is FAT format filesystem " @@ -3785,13 +3784,13 @@ msgstr "" "trong khi cài đặt, thì xoá bỏ hoàn toàn nội dung đã có !" #. Tag: title -#: using-d-i.xml:2366 +#: using-d-i.xml:2365 #, no-c-format msgid "EFI Partition Contents" msgstr "Nội dung phân vùng EFI" #. Tag: para -#: using-d-i.xml:2368 +#: using-d-i.xml:2367 #, no-c-format msgid "" "The EFI partition is a FAT filesystem format partition on one of the hard " @@ -3822,13 +3821,13 @@ msgstr "" # Name: don't translate / Tên: đừng dịch #. Tag: filename -#: using-d-i.xml:2390 +#: using-d-i.xml:2389 #, no-c-format msgid "elilo.conf" msgstr "elilo.conf" #. Tag: para -#: using-d-i.xml:2391 +#: using-d-i.xml:2390 #, no-c-format msgid "" "This is the configuration file read by the boot loader when it starts. It is " @@ -3841,13 +3840,13 @@ msgstr "" # Name: don't translate / Tên: đừng dịch #. Tag: filename -#: using-d-i.xml:2400 +#: using-d-i.xml:2399 #, no-c-format msgid "elilo.efi" msgstr "elilo.efi" #. Tag: para -#: using-d-i.xml:2401 +#: using-d-i.xml:2400 #, no-c-format msgid "" "This is the boot loader program that the EFI Boot Manager " @@ -3862,13 +3861,13 @@ msgstr "" # Name: don't translate / Tên: đừng dịch #. Tag: filename -#: using-d-i.xml:2411 +#: using-d-i.xml:2410 #, no-c-format msgid "initrd.img" msgstr "initrd.img" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2411 #, no-c-format msgid "" "This is the initial root filesystem used to boot the kernel. It is a copy of " @@ -3884,13 +3883,13 @@ msgstr "" # Name: don't translate / Tên: đừng dịch #. Tag: filename -#: using-d-i.xml:2424 +#: using-d-i.xml:2423 #, no-c-format msgid "readme.txt" msgstr "readme.txt" #. Tag: para -#: using-d-i.xml:2425 +#: using-d-i.xml:2424 #, no-c-format msgid "" "This is a small text file warning you that the contents of the directory are " @@ -3903,13 +3902,13 @@ msgstr "" # Name: don't translate / Tên: đừng dịch #. Tag: filename -#: using-d-i.xml:2435 +#: using-d-i.xml:2434 #, no-c-format msgid "vmlinuz" msgstr "vmlinuz" #. Tag: para -#: using-d-i.xml:2436 +#: using-d-i.xml:2435 #, no-c-format msgid "" "This is the compressed kernel itself. It is a copy of the file referenced in " @@ -3923,13 +3922,13 @@ msgstr "" "bởi liên kết tượng trưng /vmlinuz." #. Tag: title -#: using-d-i.xml:2456 +#: using-d-i.xml:2455 #, no-c-format msgid "arcboot-installer" msgstr "Bộ cài đặt arcboot" #. Tag: para -#: using-d-i.xml:2457 +#: using-d-i.xml:2456 #, no-c-format msgid "" "The boot loader on SGI machines is arcboot. It has to be " @@ -3973,13 +3972,13 @@ msgstr "" # Name: don't translate / Tên: đừng dịch #. Tag: replaceable -#: using-d-i.xml:2476 +#: using-d-i.xml:2475 #, no-c-format msgid "scsi" msgstr "scsi" #. Tag: para -#: using-d-i.xml:2477 +#: using-d-i.xml:2476 #, no-c-format msgid "" "is the SCSI bus to be booted from, this is 0 for the " @@ -3989,13 +3988,13 @@ msgstr "" "điều khiển có sẵn" #. Tag: replaceable -#: using-d-i.xml:2485 +#: using-d-i.xml:2484 #, no-c-format msgid "disk" msgstr "đĩa" #. Tag: para -#: using-d-i.xml:2486 +#: using-d-i.xml:2485 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which arcboot is " @@ -4005,13 +4004,13 @@ msgstr "" "được cài đặt" #. Tag: replaceable -#: using-d-i.xml:2494 using-d-i.xml:2563 +#: using-d-i.xml:2493 using-d-i.xml:2562 #, no-c-format msgid "partnr" msgstr "số_phân" #. Tag: para -#: using-d-i.xml:2495 +#: using-d-i.xml:2494 #, no-c-format msgid "" "is the number of the partition on which /etc/arcboot.conf" #. Tag: replaceable -#: using-d-i.xml:2503 +#: using-d-i.xml:2502 #, no-c-format msgid "config" msgstr "cấu_hình" #. Tag: para -#: using-d-i.xml:2504 +#: using-d-i.xml:2503 #, no-c-format msgid "" "is the name of the configuration entry in /etc/arcboot.conf, mà là linux theo mặc định." #. Tag: title -#: using-d-i.xml:2525 +#: using-d-i.xml:2524 #, no-c-format msgid "delo-installer" msgstr "Bộ cài đặt delo" #. Tag: para -#: using-d-i.xml:2526 +#: using-d-i.xml:2525 #, no-c-format msgid "" "The boot loader on DECstations is DELO. It has to be " @@ -4072,13 +4071,13 @@ msgstr "" # Literal: don't translate / Nghĩa chữ: đừng dịch #. Tag: replaceable -#: using-d-i.xml:2545 +#: using-d-i.xml:2544 #, no-c-format msgid "#" msgstr "#" #. Tag: para -#: using-d-i.xml:2546 +#: using-d-i.xml:2545 #, no-c-format msgid "" "is the TurboChannel device to be booted from, on most DECstations this is " @@ -4088,13 +4087,13 @@ msgstr "" "nó là 3 cho bộ điều khiển có sẵn" #. Tag: replaceable -#: using-d-i.xml:2554 +#: using-d-i.xml:2553 #, no-c-format msgid "id" msgstr "mã" #. Tag: para -#: using-d-i.xml:2555 +#: using-d-i.xml:2554 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which DELO is installed" @@ -4103,7 +4102,7 @@ msgstr "" "được cài đặt" #. Tag: para -#: using-d-i.xml:2564 +#: using-d-i.xml:2563 #, no-c-format msgid "" "is the number of the partition on which /etc/delo.conf " @@ -4113,13 +4112,13 @@ msgstr "" "conf" #. Tag: replaceable -#: using-d-i.xml:2572 +#: using-d-i.xml:2571 #, no-c-format msgid "name" msgstr "tên" #. Tag: para -#: using-d-i.xml:2573 +#: using-d-i.xml:2572 #, no-c-format msgid "" "is the name of the configuration entry in /etc/delo.conflinux theo mặc định." #. Tag: para -#: using-d-i.xml:2583 +#: using-d-i.xml:2582 #, no-c-format msgid "" "In case /etc/delo.conf is on the first partition on the " @@ -4140,19 +4139,19 @@ msgstr "" "là dùng" #. Tag: screen -#: using-d-i.xml:2589 +#: using-d-i.xml:2588 #, no-c-format msgid "boot #/rzid" msgstr "boot #/rzmã" #. Tag: title -#: using-d-i.xml:2599 +#: using-d-i.xml:2598 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "Cài đặt Yaboot vào đĩa cứng" #. Tag: para -#: using-d-i.xml:2600 +#: using-d-i.xml:2599 #, no-c-format msgid "" "Newer (mid 1998 and on) PowerMacs use yaboot as their " @@ -4172,13 +4171,13 @@ msgstr "" "&debian;." #. Tag: title -#: using-d-i.xml:2618 +#: using-d-i.xml:2617 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "Cài đặt Quik vào đĩa cứng" #. Tag: para -#: using-d-i.xml:2619 +#: using-d-i.xml:2618 #, no-c-format msgid "" "The boot loader for OldWorld Power Macintosh machines is quikzipl-installer" msgstr "Bộ cài đặt zipl" #. Tag: para -#: using-d-i.xml:2636 +#: using-d-i.xml:2635 #, no-c-format msgid "" "The boot loader on &arch-title; is zipl. ZIPL." #. Tag: title -#: using-d-i.xml:2653 +#: using-d-i.xml:2652 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "Cài đặt bộ tải khởi động SILO vào đĩa cứng" #. Tag: para -#: using-d-i.xml:2655 +#: using-d-i.xml:2654 #, no-c-format msgid "" "The standard &architecture; boot loader is called silo. It is " @@ -4252,13 +4251,13 @@ msgstr "" "Linux kế bên bản cài đặt SunOS/Solaris đã có." #. Tag: title -#: using-d-i.xml:2680 +#: using-d-i.xml:2679 #, no-c-format msgid "Continue Without Boot Loader" msgstr "Tiếp tục không có bộ tải khởi động" #. Tag: para -#: using-d-i.xml:2682 +#: using-d-i.xml:2681 #, no-c-format msgid "" "This option can be used to complete the installation even when no boot " @@ -4276,7 +4275,7 @@ msgstr "" "đó và được dùng để khởi động hệ điều hành GNU/Linux." #. Tag: para -#: using-d-i.xml:2691 +#: using-d-i.xml:2690 #, no-c-format msgid "" "If you plan to manually configure your bootloader, you should check the name " @@ -4297,13 +4296,13 @@ msgstr "" "vùng riêng, tên hệ thống tập tin /boot." #. Tag: title -#: using-d-i.xml:2708 +#: using-d-i.xml:2707 #, no-c-format msgid "Finishing the Installation" msgstr "Cài đặt xong" #. Tag: para -#: using-d-i.xml:2709 +#: using-d-i.xml:2708 #, no-c-format msgid "" "These are the last bits to do before rebooting to your new system. It mostly " @@ -4313,13 +4312,13 @@ msgstr "" "chính là làm sạch theo sau &d-i;." #. Tag: title -#: using-d-i.xml:2721 +#: using-d-i.xml:2720 #, no-c-format msgid "Finish the Installation and Reboot" msgstr "Cài đặt xong và khởi động lại" #. Tag: para -#: using-d-i.xml:2723 +#: using-d-i.xml:2722 #, no-c-format msgid "" "This is the last step in the initial Debian installation process. You will " @@ -4333,7 +4332,7 @@ msgstr "" "lại vào hệ thống Debian mới." #. Tag: para -#: using-d-i.xml:2730 +#: using-d-i.xml:2729 #, no-c-format msgid "" "Select the Finish the installation menu item " @@ -4348,13 +4347,13 @@ msgstr "" "tập tin gốc trong những bước đầu tiên của tiến trình cài đặt." #. Tag: title -#: using-d-i.xml:2744 +#: using-d-i.xml:2743 #, no-c-format msgid "Miscellaneous" msgstr "Lặt vặt" #. Tag: para -#: using-d-i.xml:2745 +#: using-d-i.xml:2744 #, no-c-format msgid "" "The components listed in this section are usually not involved in the " @@ -4366,13 +4365,13 @@ msgstr "" "khó khăn." #. Tag: title -#: using-d-i.xml:2758 +#: using-d-i.xml:2757 #, no-c-format msgid "Saving the installation logs" msgstr "Lưu bản ghi cài đặt" #. Tag: para -#: using-d-i.xml:2760 +#: using-d-i.xml:2759 #, no-c-format msgid "" "If the installation is successful, the logfiles created during the " @@ -4384,7 +4383,7 @@ msgstr "" "filename> trong hệ thống Debian mới." #. Tag: para -#: using-d-i.xml:2767 +#: using-d-i.xml:2766 #, no-c-format msgid "" "Choosing Save debug logs from the main menu " @@ -4400,13 +4399,13 @@ msgstr "" "kèm báo cáo cài đặt." #. Tag: title -#: using-d-i.xml:2787 +#: using-d-i.xml:2786 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "Sử dụng hệ vỏ và xem bản ghi" #. Tag: para -#: using-d-i.xml:2790 +#: using-d-i.xml:2789 #, no-c-format msgid "" "There is an Execute a Shell item on the menu. If " @@ -4429,7 +4428,7 @@ msgstr "" "chạy một sự mô phỏng hệ vỏ Bourne có tên ash." #. Tag: para -#: using-d-i.xml:2802 +#: using-d-i.xml:2801 #, no-c-format msgid "" "At this point you are booted from the RAM disk, and there is a limited set " @@ -4447,7 +4446,7 @@ msgstr "" "như khả năng gõ xong tự động và lược sử." #. Tag: para -#: using-d-i.xml:2811 +#: using-d-i.xml:2810 #, no-c-format msgid "" "Use the menus to perform any task that they are able to do — the shell " @@ -4467,13 +4466,13 @@ msgstr "" "(thoát) nếu bạn đã sử dụng trình đơn để mở hệ vỏ." #. Tag: title -#: using-d-i.xml:2830 +#: using-d-i.xml:2829 #, no-c-format msgid "Installation Over the Network" msgstr "Cài đặt qua mạng" #. Tag: para -#: using-d-i.xml:2832 +#: using-d-i.xml:2831 #, no-c-format msgid "" "One of the more interesting components is network-console.)" #. Tag: para -#: using-d-i.xml:2842 +#: using-d-i.xml:2841 #, no-c-format msgid "" "This component is not loaded into the main installation menu by default, so " @@ -4512,7 +4511,7 @@ msgstr "" "tục lại cài đặt từ xa bằng SSH." #. Tag: para -#: using-d-i.xml:2855 +#: using-d-i.xml:2854 #, no-c-format msgid "" "For installations on &arch-title;, this is the default method after setting " @@ -4522,7 +4521,7 @@ msgstr "" "mặc định sau khi thiết lập mạng." #. Tag: para -#: using-d-i.xml:2860 +#: using-d-i.xml:2859 #, no-c-format msgid "" "After selecting this new entry, you " @@ -4544,7 +4543,7 @@ msgstr "" "sẽ tiếp tục cài đặt từ xa." #. Tag: para -#: using-d-i.xml:2872 +#: using-d-i.xml:2871 #, no-c-format msgid "" "Should you decide to continue with the installation locally, you can always " @@ -4556,7 +4555,7 @@ msgstr "" "khác." #. Tag: para -#: using-d-i.xml:2878 +#: using-d-i.xml:2877 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need " @@ -4586,7 +4585,7 @@ msgstr "" "nếu nó là đúng không." #. Tag: para -#: using-d-i.xml:2895 +#: using-d-i.xml:2894 #, no-c-format msgid "" "If you install several computers in turn and they happen to have the same IP " @@ -4604,7 +4603,7 @@ msgstr "" "filename> rồi thử lại." #. Tag: para -#: using-d-i.xml:2904 +#: using-d-i.xml:2903 #, no-c-format msgid "" "After the login you will be presented with an initial screen where you have " @@ -4624,7 +4623,7 @@ msgstr "" "cho các hệ vỏ." #. Tag: para -#: using-d-i.xml:2914 +#: using-d-i.xml:2913 #, no-c-format msgid "" "After you have started the installation remotely over SSH, you should not go " @@ -4640,7 +4639,7 @@ msgstr "" "cài đặt." #. Tag: para -#: using-d-i.xml:2922 +#: using-d-i.xml:2921 #, no-c-format msgid "" "Also, if you are running the SSH session from an X terminal, you should not " diff --git a/po/zh_CN/boot-installer.po b/po/zh_CN/boot-installer.po index c94fad46d..593784fac 100644 --- a/po/zh_CN/boot-installer.po +++ b/po/zh_CN/boot-installer.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: d-i-manual\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2006-12-25 19:53+0000\n" +"POT-Creation-Date: 2006-12-25 20:11+0000\n" "PO-Revision-Date: 2006-11-27 09:30+0800\n" "Last-Translator: Ji YongGang\n" "Language-Team: debian-chinese-gb \n" @@ -11,3637 +11,4806 @@ msgstr "" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" -#~ msgid "Booting the Installation System" -#~ msgstr "用安装系统启动" +#. 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 "在 &arch-title; 上引导安装程序" + +#. Tag: title +#: boot-installer.xml:20 +#, no-c-format +msgid "Alpha Console Firmware" +msgstr "Alpha 控制台固件" + +#. 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 "" +"控制台固件是保存在一个闪存 ROM 中并且每次在 Alpha 系统加电或者重启的时候启" +"动。在 Alpha 系统上有两种规格的控制台，并且因此有两类控制台固件供使用。" -#~ msgid "Booting the Installer on &arch-title;" -#~ msgstr "在 &arch-title; 上引导安装程序" +#. Tag: para +#: boot-installer.xml:31 +#, no-c-format +msgid "" +"SRM console, based on the Alpha Console Subsystem " +"specification, which provides an operating environment for OpenVMS, Tru64 " +"UNIX, and Linux operating systems." +msgstr "" +"SRM console 基于 Alpha 控制台子系统规范。它为 OpenVMS，" +"Tru64 Unix，以及 Linux 操作系统提供了一个操作环境。" -#~ msgid "Alpha Console Firmware" -#~ msgstr "Alpha 控制台固件" +#. Tag: para +#: boot-installer.xml:38 +#, no-c-format +msgid "" +"ARC, AlphaBIOS, or ARCSBIOS console, based on the " +"Advanced RISC Computing (ARC) specification, which provides an operating " +"environment for Windows NT." +msgstr "" +"ARC, AlphaBIOS 或 ARCSBIOS console 基于 Advanced RISC " +"Computing (ARC) 规范。它为 Windows NT 提供了一个操作环境。" -#~ 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 "" -#~ "控制台固件是保存在一个闪存 ROM 中并且每次在 Alpha 系统加电或者重启的时候启" -#~ "动。在 Alpha 系统上有两种规格的控制台，并且因此有两类控制台固件供使用。" +#. 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 "" +"按照用户的角度看，SRM 和 ARC 最重要的区别，是控制台的选择，可能会影响到您需要" +"引导的磁盘分区方法。" -#~ msgid "" -#~ "SRM console, based on the Alpha Console Subsystem " -#~ "specification, which provides an operating environment for OpenVMS, Tru64 " -#~ "UNIX, and Linux operating systems." -#~ msgstr "" -#~ "SRM console 基于 Alpha 控制台子系统规范。它为 " -#~ "OpenVMS，Tru64 Unix，以及 Linux 操作系统提供了一个操作环境。" +#. Tag: para +#: boot-installer.xml:54 +#, no-c-format +msgid "" +"ARC requires that you use an MS-DOS partition table (as created by " +"cfdisk) for the boot disk. Therefore MS-DOS partition " +"tables are the native 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 "" +"ARC 需要您为引导磁盘使用一个 MS-DOS 分区表(用 cfdisk 创" +"建)。因此从 ARC 引导则 MS-DOS 分区表是作为原始的分区格式 ARC。" +"事实上，由于 AlphaBIOS 包含了一个磁盘分区工具，您也许可以在安装 Linux 时，通" +"过固件菜单对磁盘进行分区。" + +#. Tag: para +#: boot-installer.xml:63 +#, no-c-format +msgid "" +"Conversely, SRM is incompatible " +"Specifically, the bootsector format required by the Console Subsystem " +"Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " +"BSD disklabel format, this is the native partition format for " +"SRM installations." +msgstr "" +"保守地说，SRM 是 不兼容 MS-DOS 分区表。 " +"具体来说，控制台子系统规范与需要的引导扇区格式和 DOS 分区表有冲突。由于 Tru64 Unix 使用的是 BSD 磁盘标记格式，对于SRM 安装来说，这是一" +"个原始的分区格式。" + +#. 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 "" +"由于 GNU/Linux 是唯一能够通过两种控制台格式引导的系统，这个问题就取决于您想在" +"机器上面运行什么样的其他操作系统。所有的其他 Unix 型的操作系统 (Tru64 Unix，" +"FreeBSD，OpenBSD，以及 NetBSD) 和 OpenVMS 只能从 SRM 上面引导，而 Windows NT " +"只能从 ARC 上面引导。" + +#. Tag: para +#: boot-installer.xml:87 +#, no-c-format +msgid "" +"Because MILO 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 "" +"由于 MILO 在当前生产型 Alpha 系统上并没有实现(从 2000 年二" +"月份开始)。并且也不需要购买一个 OpenVMS 和 Tru64 Unix 授权，来在老 Alpha 上装" +"上 SRM 固件。我们推荐在新的机器上使用 SRM。" -#~ msgid "" -#~ "ARC, AlphaBIOS, or ARCSBIOS console, based on the " -#~ "Advanced RISC Computing (ARC) specification, which provides an operating " -#~ "environment for Windows NT." -#~ msgstr "" -#~ "ARC, AlphaBIOS 或 ARCSBIOS console 基于 Advanced " -#~ "RISC Computing (ARC) 规范。它为 Windows NT 提供了一个操作环境。" +#. Tag: para +#: boot-installer.xml:95 +#, no-c-format +msgid "" +"The following table summarizes available and supported system type/console " +"combinations (see for the system type names). " +"The word ARC below denotes any of the ARC-compliant consoles." +msgstr "" +"下面表格总结了可用以及支持的系统类型/控制台组合(系统类型名称参见 )。单词 ARC 注明任何和 ARC 兼容的控制" +"台。" + +#. 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 "alcor" -#~ 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 "" -#~ "按照用户的角度看，SRM 和 ARC 最重要的区别，是控制台的选择，可能会影响到您" -#~ "需要引导的磁盘分区方法。" +# index.docbook:110, index.docbook:113, index.docbook:119, index.docbook:125, index.docbook:128, index.docbook:131, index.docbook:134, index.docbook:140, index.docbook:143, index.docbook:146, index.docbook:155, index.docbook:164, index.docbook:179, index.docbook:182, index.docbook:188 +#. 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 "ARC or SRM" + +#. Tag: entry +#: boot-installer.xml:117 +#, no-c-format +msgid "avanti" +msgstr "avanti" + +#. Tag: entry +#: boot-installer.xml:120 +#, no-c-format +msgid "book1" +msgstr "book1" -#~ msgid "" -#~ "ARC requires that you use an MS-DOS partition table (as created by " -#~ "cfdisk) for the boot disk. Therefore MS-DOS partition " -#~ "tables are the native 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 "" -#~ "ARC 需要您为引导磁盘使用一个 MS-DOS 分区表(用 cfdisk 创" -#~ "建)。因此从 ARC 引导则 MS-DOS 分区表是作为原始的分区格式 " -#~ "ARC。事实上，由于 AlphaBIOS 包含了一个磁盘分区工具，您也许可以在安装 " -#~ "Linux 时，通过固件菜单对磁盘进行分区。" +# index.docbook:116, index.docbook:122, index.docbook:137, index.docbook:149, index.docbook:158, index.docbook:161, index.docbook:167, index.docbook:173, index.docbook:176 +#. 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 "SRM only" + +#. Tag: entry +#: boot-installer.xml:123 +#, no-c-format +msgid "cabriolet" +msgstr "cabriolet" + +#. Tag: entry +#: boot-installer.xml:126 +#, no-c-format +msgid "dp264" +msgstr "dp264" + +#. Tag: entry +#: boot-installer.xml:129 +#, no-c-format +msgid "eb164" +msgstr "eb164" + +#. Tag: entry +#: boot-installer.xml:132 +#, no-c-format +msgid "eb64p" +msgstr "eb64p" + +#. Tag: entry +#: boot-installer.xml:135 +#, no-c-format +msgid "eb66" +msgstr "eb66" + +#. Tag: entry +#: boot-installer.xml:138 +#, no-c-format +msgid "eb66p" +msgstr "eb66p" + +#. Tag: entry +#: boot-installer.xml:141 +#, no-c-format +msgid "jensen" +msgstr "jensen" + +#. Tag: entry +#: boot-installer.xml:144 +#, no-c-format +msgid "lx164" +msgstr "lx164" + +#. Tag: entry +#: boot-installer.xml:147 +#, no-c-format +msgid "miata" +msgstr "miata" + +#. Tag: entry +#: boot-installer.xml:150 +#, no-c-format +msgid "mikasa" +msgstr "mikasa" + +#. Tag: entry +#: boot-installer.xml:153 +#, no-c-format +msgid "mikasa-p" +msgstr "mikasa-p" + +#. Tag: entry +#: boot-installer.xml:156 +#, no-c-format +msgid "nautilus" +msgstr "nautilus" + +#. Tag: entry +#: boot-installer.xml:157 +#, no-c-format +msgid "ARC (see motherboard manual) or SRM" +msgstr "ARC (see motherboard manual) or SRM" + +#. Tag: entry +#: boot-installer.xml:159 +#, no-c-format +msgid "noname" +msgstr "noname" + +#. Tag: entry +#: boot-installer.xml:162 +#, no-c-format +msgid "noritake" +msgstr "noritake" + +#. Tag: entry +#: boot-installer.xml:165 +#, no-c-format +msgid "noritake-p" +msgstr "noritake-p" + +#. Tag: entry +#: boot-installer.xml:168 +#, no-c-format +msgid "pc164" +msgstr "pc164" + +#. Tag: entry +#: boot-installer.xml:171 +#, no-c-format +msgid "rawhide" +msgstr "rawhide" + +#. Tag: entry +#: boot-installer.xml:174 +#, no-c-format +msgid "ruffian" +msgstr "ruffian" -#~ msgid "" -#~ "Conversely, SRM is incompatible " -#~ "Specifically, the bootsector format required by the Console Subsystem " -#~ "Specification conflicts with the placement of the DOS partition table. with MS-DOS partition tables. Since Tru64 Unix uses the " -#~ "BSD disklabel format, this is the native partition format " -#~ "for SRM installations." -#~ msgstr "" -#~ "保守地说，SRM 是 不兼容 MS-DOS 分区表。" -#~ " 具体来说，控制台子系统规范与需要的引导扇区格式和 DOS 分区" -#~ "表有冲突。由于 Tru64 Unix 使用的是 BSD 磁盘标记格式，对" -#~ "于SRM 安装来说，这是一个原始的分区格式。" +# index.docbook:170, index.docbook:185 +#. Tag: entry +#: boot-installer.xml:175 boot-installer.xml:190 boot-installer.xml:193 +#, no-c-format +msgid "ARC only" +msgstr "ARC only" + +#. Tag: entry +#: boot-installer.xml:177 +#, no-c-format +msgid "sable" +msgstr "sable" + +#. Tag: entry +#: boot-installer.xml:180 +#, no-c-format +msgid "sable-g" +msgstr "sable-g" + +#. Tag: entry +#: boot-installer.xml:183 +#, no-c-format +msgid "sx164" +msgstr "sx164" + +#. Tag: entry +#: boot-installer.xml:186 +#, no-c-format +msgid "takara" +msgstr "takara" + +#. Tag: entry +#: boot-installer.xml:189 +#, no-c-format +msgid "xl" +msgstr "xl" + +#. Tag: entry +#: boot-installer.xml:192 +#, no-c-format +msgid "xlt" +msgstr "xlt" + +#. 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, " +"aboot, a small, platform-independent bootloader, is used. " +"See the (unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"一般来说，这些控制台都不能直接引导 Linux ，因此需要一个中间引导装载程序。对" +"于 SRM 控制台，aboot，小型的，平台独立的引导装载器。参见" +"(抱歉的是它也有点过时了)SRM HOWTO 来获" +"得更多有关信息 aboot。" + +#. 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 "" +"以下章节来自 woody 安装手册，放在这里作为参考；如果以后 Debian 再支持基于 " +"MILO 的安装，它们对某些人或许有用。" -#~ 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 "" -#~ "由于 GNU/Linux 是唯一能够通过两种控制台格式引导的系统，这个问题就取决于您" -#~ "想在机器上面运行什么样的其他操作系统。所有的其他 Unix 型的操作系统 (Tru64 " -#~ "Unix，FreeBSD，OpenBSD，以及 NetBSD) 和 OpenVMS 只能从 SRM 上面引导，而 " -#~ "Windows NT 只能从 ARC 上面引导。" +#. 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: MILO and aboot." +msgstr "" +"一般来说，这些控制台都不能直接引导 Linux，因此需要一个中间引导装载程序。这里" +"有两个主要的 Linux 装载程序： MILO 和 aboot。" -#~ msgid "" -#~ "Because MILO 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 "" -#~ "由于 MILO 在当前生产型 Alpha 系统上并没有实现(从 2000 " -#~ "年二月份开始)。并且也不需要购买一个 OpenVMS 和 Tru64 Unix 授权，来在老 " -#~ "Alpha 上装上 SRM 固件。我们推荐在新的机器上使用 SRM。" +#. Tag: para +#: boot-installer.xml:221 +#, no-c-format +msgid "" +"MILO is itself a console, which replaces ARC or SRM in " +"memory. MILO can be booted from both ARC and SRM and is " +"the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) " +"MILO HOWTO." +msgstr "" +"MILO 自己本身是一个用来替换载入内存中的 ARC 和 SRM 的控制" +"台。MILO 能够同时从 ARC 和 SRM 引导并且是唯一一种方法从 " +"ARC 控制台引导 Linux。MILO 取决与具体的平台。(对于每种不同" +"的系统类型需要不同的 MILO 并且只适合这些系统。参见(很遗憾" +"有点过时)MILO HOWTO。" + +#. Tag: para +#: boot-installer.xml:231 +#, no-c-format +msgid "" +"aboot is a small, platform-independent bootloader, which " +"runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on aboot." +msgstr "" +"aboot 是一个小型的，平台独立的引导装载器，不过只运行与 " +"SRM 上。参见 (抱歉的是它也有点过时了 ) SRM " +"HOWTO来获得更多有关信息 aboot。" -#~ msgid "" -#~ "The following table summarizes available and supported system type/" -#~ "console combinations (see for the system " -#~ "type names). The word ARC below denotes any of the ARC-" -#~ "compliant consoles." -#~ msgstr "" -#~ "下面表格总结了可用以及支持的系统类型/控制台组合(系统类型名称参见 )。单词 ARC 注明任何和 ARC 兼容的控" -#~ "制台。" +#. 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 MILO is available: " +"\n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" Because MILO 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 aboot on new installations of GNU/Linux, " +"unless you wish to dual-boot with Windows NT." +msgstr "" +"因此，三种方案都是可行的，取决与系统控制台固件以及是否有相应的 " +"MILO ： \n" +"SRM -> aboot\n" +"SRM -> MILO\n" +"ARC -> MILO\n" +" 由于 MILO 在当前生产型 Alpha " +"系统上并没有实现(从 2000 年二月份开始)。并且也不需要购买一个 OpenVMS 和 " +"Tru64 Unix 授权，来在老 Alpha 上装上 SRM 固件。除非您想采用 Windows NT 并且进" +"行双引导，我们推荐在新的机器上使用 SRM 和 aboot 安装 " +"Linux。" + +#. 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 half-flash 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 arc command). For the reasons mentioned above, " +"we recommend switching to SRM before installing &debian;." +msgstr "" +"大部分 AlphaServers 以及目前所有的服务器以及工作站产品固件中都同时含有 SRM " +"和 AlphaBIOS。对于具有不同开发板的 half-flash 机器来说。可以通" +"过重刷固件 来从一个版本切换到另外一个版本。并且一旦 SRM 安装完毕，从软盘上运" +"行 ARC/AlphaBIOS 也是可能的(使用 arc)。基于上述的理由，我" +"们推荐在安装 &debian; 之前切换至 SRM。" + +#. Tag: para +#: boot-installer.xml:264 +#, no-c-format +msgid "" +"As on other architectures, you should install the newest available revision " +"of the firmware Except on Jensen, where Linux is not " +"supported on firmware versions newer than 1.7 — see for more information. before " +"installing &debian;. For Alpha, firmware updates can be obtained from Alpha Firmware Updates." +msgstr "" +"和另外的体系结构一样，您也应该在安装 &debian; 之前安装最新版本的固件" +"不包括 Jensen，1.7 以上版本的固件不支持 Linux — 查看 " +" 以获得更多的信息。。对于 Alpha 来说，固件升级可以通过 Alpha Firmware Updates取得。" -#~ msgid "System Type" -#~ msgstr "系统类型" +# index.docbook:274, index.docbook:780, index.docbook:1320, index.docbook:1813, index.docbook:1896, index.docbook:2236, index.docbook:2332 +#. Tag: title +#: boot-installer.xml:283 boot-installer.xml:999 boot-installer.xml:1490 +#: boot-installer.xml:1985 boot-installer.xml:2067 boot-installer.xml:2156 +#: boot-installer.xml:2500 boot-installer.xml:2596 +#, no-c-format +msgid "Booting with TFTP" +msgstr "用 TFTP 引导" + +#. Tag: para +#: boot-installer.xml:284 +#, no-c-format +msgid "" +"In SRM, Ethernet interfaces are named with the ewa " +"prefix, and will be listed in the output of the show dev command, like this (edited slightly): \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" +" You first need to set the boot protocol: " +"\n" +">>> set ewa0_protocols bootp\n" +" Then check the medium type is correct: " +"\n" +">>> set ewa0_mode mode\n" +" You can get a listing of valid modes with " +">>>set ewa0_mode." +msgstr "" +"在 SRM 上，以太网界面名字带有 ewa 前缀，并可以用 " +"show dev 命令列出，类似如下显示(可能有一点不同)： " +"\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" +" 您首先需要设置引导协议： " +"\n" +">>> set ewa0_protocol bootp\n" +" 然后检查媒介类型是否正确： " +"\n" +">>> set ewa0_mode mode\n" +" 获得一个有效模式的列表 >>>" +"set ewa0_mode。" + +#. Tag: para +#: boot-installer.xml:302 +#, no-c-format +msgid "" +"Then, to boot from the first Ethernet interface, you would type: " +"\n" +">>> boot ewa0 -flags \"\"\n" +" This will boot using the default kernel " +"parameters as included in the netboot image." +msgstr "" +"接下来，如果从第一个以太网界面引导，您需要输入： \n" +">>> boot ewa0 -flags \"\"\n" +" 这将 netboot 映象启动，并使用默认的内核参数。" -#~ msgid "Console Type Supported" -#~ msgstr "支持的控制台类型" +#. Tag: para +#: boot-installer.xml:311 +#, no-c-format +msgid "" +"If you wish to use a serial console, you must pass the " +"console= parameter to the kernel. This can be done " +"using the -flags argument to the SRM boot command. The serial ports are named the same as their " +"corresponding files in /dev. 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 ewa0 and use a console on the first serial port, you would type:" +msgstr "" +"如果希望使用一个串行控制台，您 必须 给内核传递 " +"console= 参数。这个工作可以使用附带 -" +"flags 参数的 SRM boot 命令来完成。串口号的" +"命名和它们在目录 /dev 中相同。另外，如有指定额外的内核" +"参数，也必须给 &d-i; 映象重复指定。比如，如果需要从 ewa0 引导，并且在第一个串口使用控制台，您需要输入：" + +#. Tag: screen +#: boot-installer.xml:323 +#, no-c-format +msgid "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" +msgstr "" +">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " +"console=ttyS0"" + +#. Tag: title +#: boot-installer.xml:328 +#, no-c-format +msgid "Booting from CD-ROM with the SRM Console" +msgstr "采用 SRM 控制台来从 CD 光盘上引导" + +#. Tag: para +#: boot-installer.xml:329 +#, no-c-format +msgid "" +"Type \n" +">>> boot xxxx -flags 0\n" +" where xxxx is your CD-" +"ROM drive in SRM notation." +msgstr "" +"输入 \n" +">>> boot xxxx -flags 0\n" +" 这里 xxxx 是您的光盘驱" +"动器在 SRM 的符号。" + +#. Tag: title +#: boot-installer.xml:341 +#, no-c-format +msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" +msgstr "通过 ARC 或者 AlphaBIOS 控制台来从 CD 光盘上启动" + +#. 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 ), then enter \\milo\\linload." +"exe as the boot loader and \\milo" +"\\subarch (where subarch is the proper subarchitecture name) as the OS Path in the `OS " +"Selection Setup' menu. Ruffians make an exception: You need to use " +"\\milo\\ldmilo.exe as boot loader." +msgstr "" +"为了从 ARC 控制台引导 CD 光盘，找出您的子体系结构代码名称(参见 )，然后输入 \\milo\\linload.exe 作为引导" +"装载器并且在 `OS Selection Setup' 菜单下选择 \\milo" +"\\subarch (这里 subarch 是相应的子体系结构名称)作为操作系统路径。Ruffians 则是一个例外：" +"您需要使用 \\milo\\ldmilo.exe 作为引导装载器。" + +#. Tag: title +#: boot-installer.xml:358 +#, no-c-format +msgid "Booting from Floppies with the SRM Console" +msgstr "通过 SRM 控制台从软盘引导" + +#. Tag: para +#: boot-installer.xml:359 +#, no-c-format +msgid "" +"At the SRM prompt (>>>), issue the following " +"command: \n" +">>> boot dva0 -flags 0\n" +" possibly replacing dva0 " +"with the actual device name. Usually, dva0 is the " +"floppy; type \n" +">>> show dev\n" +" to see the list of devices (e.g., if you want to " +"boot from a CD). Note that if you are booting via MILO, -flags argument is ignored, so you can just type boot dva0. If everything works OK, you will eventually see the Linux kernel " +"boot." +msgstr "" +"在 SRM 提示符下 (>>>)，使用如下命令： " +"\n" +">>> boot dva0 -flags 0\n" +" 可以用实际的设备名称来替换 dva0。通常情况下，dva0 是软盘；输入 " +"\n" +">>> show dev\n" +" 来查看设备列表(比如，如果您想从一张 CD 上面引" +"导)。注意如果您想通过 MILO 引导 -flags 参数将被忽略，因此" +"您可以只需输入 boot dva0。如果上面步骤工作正常，您将最终看" +"到 Linux 内核引导。" + +#. Tag: para +#: boot-installer.xml:376 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via aboot, use the following command: \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (typed on one line), substituting, if necessary, " +"the actual SRM boot device name for dva0, the Linux " +"boot device name for fd0, and the desired kernel " +"parameters for arguments." +msgstr "" +"如果您想在通过 aboot 引导的时候指定特定的内核参数，请使用" +"如下命令： \n" +">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " +"load_ramdisk=1 arguments\"\n" +" (输入到一行)，如果需要，替换 dva0 的真实 SRM 引导设备名 dva0，fd0 的 Linux 引导设备名，arguments 需要的内核参" +"数。" + +#. Tag: para +#: boot-installer.xml:388 +#, no-c-format +msgid "" +"If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. See " +"." +msgstr "" +"如果您想在通过 MILO 启动时指定内核参数，您必须在进入 MILO " +"时中断引导。参阅 。" + +#. Tag: title +#: boot-installer.xml:398 +#, no-c-format +msgid "Booting from Floppies with the ARC or AlphaBIOS Console" +msgstr "在 ARC 或者 AlphaBISO 控制台下从软盘引导" + +#. Tag: para +#: boot-installer.xml:400 +#, no-c-format +msgid "" +"In the OS Selection menu, set linload.exe as the boot " +"loader, and milo as the OS Path. Bootstrap using the " +"newly created entry." +msgstr "" +"在操作系统选择菜单内，设置 linload.exe 作为引导装载器，并" +"且 milo 作为操作系统参数。然后使用这个最近建立的选项启动。" + +#. Tag: title +#: boot-installer.xml:409 +#, no-c-format +msgid "Booting with MILO" +msgstr "采用 MILO 引导" + +#. 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 "" +"自我启动介质上的 MILO 会自动直接进入 Linux 引导过程。如果您要对此有所控制，只" +"需要在 MILO 倒计时时按下空格键。" -#~ msgid "alcor" -#~ msgstr "alcor" +#. 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: " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"如果您想显式指定所有的位(比如，支持附加的参数)，您可以使用像下面形式的命令： " +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" 如果通过软盘之外别的方法引导，在 Linux 标记下把上" +"面例子中的 fd0 替换成合适的设备名称。help 命令将给出一个简单的 MILO 命令参考。" + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "从 TFTP 引导" -# index.docbook:110, index.docbook:113, index.docbook:119, index.docbook:125, index.docbook:128, index.docbook:131, index.docbook:134, index.docbook:140, index.docbook:143, index.docbook:146, index.docbook:155, index.docbook:164, index.docbook:179, index.docbook:182, index.docbook:188 -#~ msgid "ARC or SRM" -#~ msgstr "ARC or SRM" +# index.docbook:432, index.docbook:786, index.docbook:1338, index.docbook:1819, index.docbook:2242, index.docbook:2338 +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"从网络引导需要您已经具备网络的连接和一台 TFTP 网络引导服务器(DHCP, RARP 以及 " +"BOOTP)。" -#~ msgid "avanti" -#~ msgstr "avanti" +# index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343 +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "较早的系统比如 715 也许需要使用一台 RBOOT 服务器来取代 BOOTP 服务器。" -#~ msgid "book1" -#~ msgstr "book1" +# index.docbook:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348 +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "支持的网络引导安装方法在 。" + +#. Tag: title +#: boot-installer.xml:459 +#, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "从 Netwinder 上的 TFTP 上引导" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" +"Netwinder 有两个网络接口：一个 10Mbps NE2000 兼容卡 (通常作为 eth0) 和一个 100Mbps Tulip 卡。使用 100Mbps 卡通过 TFTP 加载映像可能会出" +"现问题，所以建议使用 10Mbps 的接口 (标记为 10 Base-T)。" -# index.docbook:116, index.docbook:122, index.docbook:137, index.docbook:149, index.docbook:158, index.docbook:161, index.docbook:167, index.docbook:173, index.docbook:176 -#~ msgid "SRM only" -#~ msgstr "SRM only" +#. 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 ." +msgstr "" +"您需要 NeTTrom 2.2.1 或者较高的版本来引导安装系统，推荐使用 NeTTrom 2.3.3。不" +"幸的是，由于许可证的原因，固件的文件现在无法下载。如果情况有所改变，您可以从 " +"找到新映像。" -#~ msgid "cabriolet" -#~ msgstr "cabriolet" +#. 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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" +"启动 Netwinder 时，您必须在倒数时中断引导过程。这让您可以进行一些固件的设置用" +"于启动安装程序。首先，加载默认设置：\n" +" NeTTrom command-> load-defaults\n" +" 接着，您必须配置网络，可以是一个静态地址：" +"\n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" 其中 24 是网络掩码位数，或者是一个动态地址：" +"\n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" 如果 TFTP 服务器不在子网内，您还必须配置 " +"route1 设置。下面的设置，要指定 TFTP 服务器和映像的位" +"置。您可以将设置保存到 U 盘里。\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" 现在您要告诉固件将要引导的 TFTP 映像：" +"\n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" 如果您通过串口控制台安装 Netwinder，需要加入下面" +"设置：\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" 另外，对于安装时使用的键盘和监视器需要设置：" +"\n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" 您可以使用 printenv 命令回顾环" +"境设置。在确认设置正确之后，您可以加载映像：\n" +" NeTTrom command-> boot\n" +" 万一您遇到问题，有一个 detailed HOWTO 可以參考。" + +#. Tag: title +#: boot-installer.xml:529 +#, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "在 CATS 上的 TFTP 引导" + +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"在 CATS 机器上，可以使用命令 boot de0: 或者在 Cyclone 引导" +"符下类似的命令。" -#~ msgid "dp264" -#~ msgstr "dp264" +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "从 CD 光盘上引导" -#~ msgid "eb164" -#~ msgstr "eb164" +# index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378 +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"对于大多数人来说，最快的途径是使用一套 Debian CD 光盘套件。如果您有此套件，并" +"且如果您的机器支持直接 CD 引导，太棒了！只需要配置您的系" +"统可以用 CD 启动，参见 , 插入您" +"的 CD，重启，然后继续下一章。" -#~ msgid "eb64p" -#~ msgstr "eb64p" +# index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389 +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"注意某些特定的 CD 驱动器需要一些特殊的驱动程序，由此他们可能在安装的早期不能" +"被访问。如果标准的从 CD 引导的方法不能用于您的硬件，阅读本章中关于其他种类的" +"内核以及安装方法，它们有可能能解决问题。" -#~ msgid "eb66" -#~ msgstr "eb66" +# index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397 +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"即便您不能从 CD 光盘引导，依然可以安装 CD 光盘上面的 Debian 系统组件和所有软" +"件包。只需要使用不同的媒介，比如软盘引导系统。当安装操作系统，基础系统和任意" +"附加的软件包时只需指向安装系统至光盘驱动器即可。" -#~ msgid "eb66p" -#~ msgstr "eb66p" +# index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405 +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"如果您遇到引导方面的问题，请参见 。" -#~ msgid "jensen" -#~ msgstr "jensen" +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"如果需要在 Cyclone 控制台提示符下从 CD 光盘下引导，请使用命令 boot " +"cd0:cats.bin" + +#. 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 "" +"有越来越多的消费设备可以直接从设备上的闪存启动。安装程序可以被写入闪存，这样" +"当您重启机器的时候就能自动运行。" -#~ msgid "lx164" -#~ msgstr "lx164" +#. 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 "引导 NSLU2" + +#. 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 "使用 NSLU2 的 web 界面" + +#. Tag: para +#: boot-installer.xml:620 +#, no-c-format +msgid "" +"Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." +msgstr "" +"进入管理部分然后选择菜单项 Upgrade。接着从您的磁盘上找到前" +"面下载安装程序映像。然后按下 Start Upgrade 按钮，确认，等" +"几分钟再次确认。系统将直接启动进入安装程序。" + +#. Tag: title +#: boot-installer.xml:631 +#, no-c-format +msgid "Via the network using Linux/Unix" +msgstr "通过网络使用 Linux/Unix" + +#. Tag: para +#: boot-installer.xml:632 +#, no-c-format +msgid "" +"You can use upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 "" +"您可以从任一 Linux 或 Unix 机器上使用 upslug2 通过网络来升" +"级机器。Debian 下有该软件包。首先，您必须将 NSLU2 置于升级模式： " +" 去除所有连接在 USB 口上的磁盘和/或设备。 关闭 NSLU2 电源 " +" 按住复位按钮 (位于后面电源输入上方的小孔)。 按下和松开开关键打开 NSLU2。 " +" 等待 10 秒监视就绪/状态 LED。 10 秒钟后它会从琥珀色变成红" +"色。立即松开复位按钮。 NSLU2 就绪/状态 " +"LED 将会红/绿交替闪烁 (在首次出现绿色时会有 1 秒钟的延迟)。NSLU2 现在处于升级" +"模式。 如果您遇到问题，请参考 NSLU2-Linux " +"pages。一旦 NSLU2 处于升级模式，您就可以刷人新的映像：" +"\n" +"sudo upslug2 -i di-nslu2.bin\n" +" 注意，该工具还会显示 NSLU2 的 MAC 地址，它可以用" +"来配置 DHCP 服务器。整个映像写入和检验后，系统将自动重启。确保 USB 磁盘再次连" +"接，否则将无法找到安装程序。" + +#. Tag: title +#: boot-installer.xml:693 +#, no-c-format +msgid "Via the network using Windows" +msgstr "通过网络使用 Windows" + +#. Tag: para +#: boot-installer.xml:694 +#, no-c-format +msgid "" +"There is a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" +"有一个 工具 用于 Windows 通过网络升级固件。" -#~ msgid "miata" -#~ msgstr "miata" +# index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372 +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "从 CD-ROM 启动" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "引导 Linux 使用 LILO 或 GRUB" -#~ msgid "mikasa" -#~ msgstr "mikasa" +#. 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 ." +msgstr "" +"为了从硬盘引导安装程序，您首先必须按照要求下载并且放置所需的文件，请参见 " +"。" -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p" +#. Tag: para +#: boot-installer.xml:856 +#, fuzzy, 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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"如果您愿意只使用硬盘引导，然后从网络下载其他文件，需要下载 netboot/" +"debian-installer/i386/initrd.gz 及其对应的内核。这将允许您重新分区" +"您用于引导的硬盘。这里需要小心操作。" -#~ msgid "nautilus" -#~ msgstr "nautilus" +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"或者，如果您愿意保持安装时硬盘原有分区不变，可以下载 hd-media/" +"initrd.gz 文件及其内核，以及复制一个 CD 光盘 iso 文件到硬盘上(确保" +"文件名结尾是.iso)。安装程序就可以无网络从硬盘引导，并且从 " +"CD 映像文件上安装。" + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"如果采用 LILO,您需要在 /etc/lilo.conf 中配置两件最基本的事情: 在引导时装" +"入 initrd.gz 安装程序； " +" 让 vmlinuz 内核使用一个内存虚拟磁盘作为" +"它的根分区。 这里是一个 /etc/" +"lilo.conf 的例子：" + +#. Tag: screen +#: boot-installer.xml:896 +#, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"欲获知更多细节，请参阅 initrd " +"4 和 lilo." +"conf 5 man 手册。现在运" +"行 lilo 并且重新启动。" + +#. Tag: para +#: boot-installer.xml:905 +#, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"使用 GRUB 的过程也类似。在 /boot/grub/ 目录下找到 menu.lst (有时位于 /boot/" +"boot/grub/)，加入下面几行：\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" +" 然后重启。" + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"注意 ramdisk_size 的值也许需要调整至 initrd 映像的大" +"小。从这里开始，没什么区别，即采用 GRUB 或 LILO。" -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (see motherboard manual) or SRM" +# index.docbook:700, index.docbook:2176 +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "从 USB 闪盘引导" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +"假设您已经准备好了从 到 的所有步骤。现在只需要插入您的 USB 盘到一个空闲的 USB 插" +"槽并且重启计算机。系统应该重新引导，并且您将得到一个 boot: " +"提示符。这里您可以输入一些引导选项，或者只是敲击 &enterkey;。" -#~ msgid "noname" -#~ msgstr "noname" +# index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426 +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "从软盘引导" -#~ msgid "noritake" -#~ msgstr "noritake" +# index.docbook:724, index.docbook:2286 +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"您可能已经下载了所需要的软盘映像，并且根据这些映像创建了软盘 。" -#~ msgid "noritake-p" -#~ msgstr "noritake-p" +#. Tag: para +#: boot-installer.xml:949 +#, 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 "" +"从软盘引导安装程序需要放置软盘至主软驱。按照您平时的习惯关闭系统，然后重新打" +"开。" -#~ msgid "pc164" -#~ msgstr "pc164" +#. Tag: para +#: boot-installer.xml:955 +#, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"要想在 LS-120 驱动器(ATAPI 版本)使用这些软盘，您需指定这些软盘设备的虚拟地" +"址。这可以通过 root= 引导参数来指定映射的 ide-floppy 驱" +"动器设备名来完成。比如，您的 LS-120 驱动器连接到第二根线第一个 IDE 设备" +"(master)，那么在提示符下输入 linux root=/dev/hdc。" + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"注意有些机器上，Control Alt " +"Delete 不能正常地重启系统，所以推荐使用硬" +"启动。如果您正从已有的操作系统上安装(比如在 DOS 系统上)您将没有这样的" +"选择。在其它情况下，请在引导时使用硬重启。" + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"读完软盘后，您将看到屏幕上有一个有关引导软盘的介绍，并且结尾是 boot:" +" 提示符。" -#~ msgid "rawhide" -#~ msgstr "rawhide" +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"一旦您敲入 &enterkey;，您应该能够看到 Loading... 消息，并且接下来是 Uncompressing Linux...，然后是一些有关您系统的硬件信息。想知道更多有关这段引导过程的" +"信息，可以在下面 。" + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"软盘引导后需要根软盘。请插入根软盘并且输入 &enterkey;，然后其中的内容会被装入" +"内存。安装程序 debian-installer 会自动启动。" + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "在 i386 体系上有很多方法用 TFTP 进行引导。" + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "支持 PXE 的网卡或者主板" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"您的网卡或者主板可能已经提供了 PXE 引导功能。这是一个 IntelTFTP 引导的实现。如果是这样，也许可以能够配置您的 " +"BIOS 来用网络进行引导。" + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "网络 BootROM 的网卡" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "很有可能是您的网卡提供了 TFTP 引导功能。" -#~ msgid "ruffian" -#~ msgstr "ruffian" +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"请让我们知道 (&email-debian-boot-list;) 您如何来操作它，并参阅" +"此文档。" + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"etherboot project 提供了为 " +"TFTP 引导所需要的引导软盘甚至是引导 ROMS 。" -# index.docbook:170, index.docbook:185 -#~ msgid "ARC only" -#~ msgstr "ARC only" +# index.docbook:1943, index.docbook:2477 +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "引导提示" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"安装系统引导时，您应该看到友好的图形画面，显示着 Debian 标志和引导提示: " +"Press F1 for help, or ENTER to boot: 您可以按 &enterkey; 键使用默认的选项引导，或者输入一个可选的" +"引导参数来指定引导的方式。" + +#. Tag: para +#: boot-installer.xml:1078 +#, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"使用 F2 至 F8 键，可以查看可用的引导方法和" +"引导参数的信息。如果您在引导命令行上添加任何参数，确保引导方法(默认是 " +"linux)和第一个参数之间有一个空格(例如，" +"linux fb=false)。" + +#. Tag: para +#: boot-installer.xml:1087 +#, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"如果您通过远程设备安装系统，而该设备在 VGA 控制台提供文本界面，您可能不会看到" +"安装程序开始的图形启动画面; 甚至不会看到引导提示。像 Compaq 的 " +"integrated Lights Out (iLO) 和 HP 的 Integrated Remote " +"Assistant (IRA) 就是这类设备。您可以什么都看不见地按下 F1 " +"有些情况下这些设备特别的转义次序按键，例如 IRA 使用 " +"Ctrl F , 1。 跳过该画面切换到帮助文档。一旦通过启动画面，在帮" +"助文档按下的键会回显在提示符上。为了阻止安装程序在后续安装中使用 " +"framebuffer，如帮助文档所述，您也可在引导提示后面加上 fb=false。" + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "CD 的内容" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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 "" +"有三种基本的 Debian 安装光盘 CD 衍生品：名片式(Business Card) CD 有一个微型的安装程序，并且可以储存在一小张 CD 介质上。它需要借助" +"网络连接来安装基本系统的其他部分，才能建立起一个可用的系统。网络安" +"装(Network Install) CD 光盘具有基本系统需的所有包，但是它还是需要" +"网络连接到 Debian 的镜像，安装其他的软件包建立一个完整的系统。Debian CD 光盘" +"套件，则可以不使用网络就能安装大量软件包，建立完整的系统。" + +#. Tag: para +#: boot-installer.xml:1180 +#, 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 "" +"IA-64 使用 Intel 最新的可拓展固件界面(Extensible Firmware Interface (EFI))。" +"与传统的 x86 BIOS 只了解分区表和主引导记录(MBR)而不知道其他引导设备的特点不" +"同，EFI 可以对 FAT16 和 FAT32 格式的硬盘分区进行读写操作。这个特点简化了通常" +"很难以理解的系统启动过程。系统引导装载器以及 EFI 固件支持一个完全的文件系统，" +"来保存引导一个机器所需要得所有文件。这意味着在一个 IA-64 系统上的系统磁盘，具" +"有一个附加的专门为 EFI 服务的磁盘分区，而不是像传统系统上只是简单的 MBR 或者" +"引导块记录。" + +#. Tag: para +#: boot-installer.xml:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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 "" +"Debian CD 包含了一个小型版本的 EFI 分区来放置 ELILO，它的" +"配置文件，安装程序内核以及初始的文件系统(initrd)。运行的系统同时也包含了一个 " +"EFI 分区用于放置引导系统所需要的必要文件。这些文件可以从 EFI Shell 读出，说明" +"如下。" + +#. Tag: para +#: boot-installer.xml:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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 "" +"大部分有关如何 ELILO 实际装入和开始一个系统的细节是对系统" +"安装程序透明的。但是，安装程序必须设置 EFI 分区优先级来安装基本系统。否则 " +"ELILO 的安装将会失败并且导致系统不可引导。EFI 分区是分配并" +"且格式 化与分区步骤以装入系统磁盘的所有软件包。分区任务也需要为接下来的安装检" +"查一个 EFI 分区是否合适。" + +#. Tag: para +#: boot-installer.xml:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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 "" +"EFI Boot Manager 在固件初始化的最后一步会被启动。它显示一个菜单列表供用户选" +"择。取决于系统的型号并且是否有其他的软件已经被装入系统，这个菜单可能在不同系" +"统上有不同表现。在每一个系统上，至少有两个菜单项显示，Boot Option " +"Maintenance Menu 与 EFI Shell (Built-in)。推荐使" +"用第一个，当然，该选项不可用或者 CD 由于某种原因没法启动，使用第二个。" + +#. Tag: title +#: boot-installer.xml:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "重要" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" +"EFI Boot Manager 会在预设的几秒钟之后选择默认的启动方式，一般是第一菜单项。在" +"屏幕底部会有倒计时显示。时间一到，系统按默认方式启动，这样您也许需要重新启动" +"才能继续安装。如果默认是 EFI Shell，您可在提示符下执行 exit返回 Boot Manager。" + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "选项 1: 从 Boot Option Maintenance Menu 启动" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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 "" +"插入 CD 到 DVD/CD 驱动器，然后重启机器。固件在完成系统初始化后会显示 EFI " +"Boot Manager 页面和菜单。" -#~ msgid "sable" -#~ msgstr "sable" +#. Tag: para +#: boot-installer.xml:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"选择 Boot Maintenance Menu 通过方向键然后按下 " +"ENTER。会显示一个新菜单。" -#~ msgid "sable-g" -#~ msgstr "sable-g" +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" +"选择 Boot From a File 通过方向键，然后按下 " +"ENTER。将显示固件检测到的设备列表。您会看到两个菜单行，它" +"们包括 Debian Inst [Acpi ... 或 Removable Media " +"Boot标签。如果您检查菜单行其他部分，会看到对应的设备和控制器信息。" + +#. Tag: para +#: boot-installer.xml:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" +"您可选择指向 CD/DVD 驱动的入口。通过方向键选择并按下 ENTER。如果您选择 Removable Media Boot 机器将进入启动步" +"骤。如果您选择 Debian Inst [Acpi ...，它会显示一个可启动" +"的 CD 目录列表，要求您进行(额外的)下一步。" + +#. Tag: para +#: boot-installer.xml:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" +"您只在选择 Debian Inst [Acpi ... 时需要。目录列表还会显示 " +"[Treat like Removable Media Boot] 至最后一行。用方向键选" +"择，并按下 ENTER。这将进入启动步骤。" -#~ msgid "sx164" -#~ msgstr "sx164" +#. Tag: para +#: boot-installer.xml:1302 +#, 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 "" +"这些步骤启动的 Debian 引导器会显示一个菜单页用于选择启动内核和选项。进入选择" +"启动内核和选项。" + +#. Tag: title +#: boot-installer.xml:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "选项 2: 从 EFI Shell 启动" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" +"某些情况下，选项 1 无法成功，重新启动机器然后在 EFI Boot Manager 画面出现的时" +"候会有一个选项称为 EFI Shell [Built-in]。可以通过如下步骤" +"来引导 Debian 安装程序 CD :" -#~ msgid "takara" -#~ msgstr "takara" +#. Tag: para +#: boot-installer.xml:1324 +#, 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 "把 CD 放入 DVD/CD 驱动器。" + +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" +"选择 EFI Shell 然后按下 ENTER。EFI " +"Shell 将扫描所有的可引导设备，并且在显示其命令提示符前在控制台列出它们。在设" +"备上被辨认出的可引导分区，将显示成 fsn:" +"。所有其他辨认出的分区，将被命名为 blkn:。如果您在进入 Shell 之前就插入 CD，这将花费一些时间" +"用于初始化 CD 驱动器。" + +#. Tag: para +#: boot-installer.xml:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" +"在检查 CD 驱动器期间请查看 Shell 的输出显示。一般来说是 fs0: 并且其他具有可引导分区的设备上也会显示成 " +"fsn。" -#~ msgid "xl" -#~ msgstr "xl" +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"进入 fsn: 然后按下 " +"ENTER 来选择设备。这里 n 是 CD " +"光盘的分区号。Shell 现在将在提示符下显示分区号。" -#~ msgid "xlt" -#~ msgstr "xlt" +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"进入 elilo 并按下 ENTER。这将进入启动步" +"骤。" -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, aboot, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." -#~ msgstr "" -#~ "一般来说，这些控制台都不能直接引导 Linux ，因此需要一个中间引导装载程序。" -#~ "对于 SRM 控制台，aboot，小型的，平台独立的引导装载器。" -#~ "参见(抱歉的是它也有点过时了)SRM HOWTO 来获得更多有关信息 aboot。" +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"与选项 1 相同，这些步骤也会启动 Debian 引导器，显示一个菜单页供选择启动内核和" +"参数。您可在 shell 提示符下输入 fsn:" +"elilo简短命令。进入选择启动内核和选项。" + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "使用串口控制台安装" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"您可选择使用显示器与键盘或者串口连接来进行安装。要使用显示器/键盘配置，选择包" +"含 [VGA console] 的选项。要通过串口连接，选择包含 [BAUD baud serial console] 的选项，其中 BAUD 是串行连接速度。对于大多数常见的波特率的 ttyS0 设备菜单项已经预" +"置。" + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"大多时候，您会让安装程序使用与连接 EFI 控制台相同的波特率。如果您不知如何设" +"置，可以通过命令 baud 在 EFI shell 获得。" -#~ 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 "" -#~ "以下章节来自 woody 安装手册，放在这里作为参考；如果以后 Debian 再支持基于 " -#~ "MILO 的安装，它们对某些人或许有用。" +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"如果没有串行配置的选项或者您要使用的波特率，可以覆盖某个已有菜单项里面的波特" +"率。例如，使用 57600 波特率覆盖 ttyS1 设备，输入 " +"console=ttyS1,57600n8 到 Boot: 文本" +"窗口。" + +#. Tag: para +#: boot-installer.xml:1410 +#, 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 Params help menu for " +"instructions on starting the installer in Text Mode." +msgstr "" +"大多数 IA-64 机器配备默认 9600 波特率的控制台。这样设太慢，普通安装过程将花费" +"明显的时间刷新每个屏幕。您要么通过提高波特率提升安装效率，要么使用文本模式安" +"装。参考 Params 帮助菜单，获得启动文本模式安装的指导。" -#~ 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: MILO and aboot." -#~ msgstr "" -#~ "一般来说，这些控制台都不能直接引导 Linux，因此需要一个中间引导装载程序。这" -#~ "里有两个主要的 Linux 装载程序： MILO 和 " -#~ "aboot。" +#. Tag: para +#: boot-installer.xml:1419 +#, 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:1428 +#, no-c-format +msgid "Selecting the Boot Kernel and Options" +msgstr "选择启动内核与选项" + +#. Tag: para +#: boot-installer.xml:1430 +#, no-c-format +msgid "" +"The boot loader will display a form with a menu list and a text window with " +"a Boot: 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 General help screen " +"explains the menu choices and the Params screen " +"explains the common command line options." +msgstr "" +"引导程序会显示一个表单，具有菜单列与包含 Boot: 提示符" +"的文本窗口。用方向键选择菜单项并且键盘输入的字符将显示在文本窗口。输入适当的" +"功能键会显示帮助窗口。普通的帮助窗口解释菜单选项，" +"Params窗口解释命令行参数。" + +#. Tag: para +#: boot-installer.xml:1442 +#, no-c-format +msgid "" +"Consult the General help screen for the description " +"of the kernels and install modes most appropriate for your installation. You " +"should also consult below for any additional " +"parameters that you may want to set in the Boot: 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 "" +"查询 General 帮助页面，了解内核的说明和安装对应的模" +"式。您还应该查询 ，了解在文本窗口中需要设置的额" +"外参数 Boot:，您选择的内核版本将会用在安装过程和安装好" +"的系统中。如果安装时碰到内核问题，在安装好的系统中也会出现。以下两步选择和开" +"始安装：" + +#. Tag: para +#: boot-installer.xml:1460 +#, no-c-format +msgid "" +"Select the kernel version and installation mode most appropriate to your " +"needs with the arrow keys." +msgstr "使用方向键选择您需要的内核版本和适合的安装模式。" -#~ msgid "" -#~ "MILO is itself a console, which replaces ARC or SRM in " -#~ "memory. MILO can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." -#~ msgstr "" -#~ "MILO 自己本身是一个用来替换载入内存中的 ARC 和 SRM 的控" -#~ "制台。MILO 能够同时从 ARC 和 SRM 引导并且是唯一一种方法" -#~ "从 ARC 控制台引导 Linux。MILO 取决与具体的平台。(对于每" -#~ "种不同的系统类型需要不同的 MILO 并且只适合这些系统。参" -#~ "见(很遗憾有点过时)MILO HOWTO。" +#. Tag: para +#: boot-installer.xml:1465 +#, 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 "" +"在键盘上输入任何启动参数。这些文字将直接显示在文本窗口。这是内核参数(如同串口" +"控制台)指定的。" -#~ msgid "" -#~ "aboot is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " -#~ "aboot." -#~ msgstr "" -#~ "aboot 是一个小型的，平台独立的引导装载器，不过只运行与 " -#~ "SRM 上。参见 (抱歉的是它也有点过时了 ) SRM " -#~ "HOWTO来获得更多有关信息 aboot。" +#. Tag: para +#: boot-installer.xml:1472 +#, no-c-format +msgid "" +"Press ENTER. 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 "" +"按下 ENTER。会加载并启动内核。内核在 Debian 安装程序的第一" +"个屏幕显示常规的初始化信息。" -#~ msgid "" -#~ "Thus, three scenarios are generally possible, depending on the system's " -#~ "console firmware and whether or not MILO is available: " -#~ "\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Because MILO 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 aboot on new " -#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -#~ msgstr "" -#~ "因此，三种方案都是可行的，取决与系统控制台固件以及是否有相应的 " -#~ "MILO ： \n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " 由于 MILO 在当前生产型 " -#~ "Alpha 系统上并没有实现(从 2000 年二月份开始)。并且也不需要购买一个 " -#~ "OpenVMS 和 Tru64 Unix 授权，来在老 Alpha 上装上 SRM 固件。除非您想采用 " -#~ "Windows NT 并且进行双引导，我们推荐在新的机器上使用 SRM 和 " -#~ "aboot 安装 Linux。" +#. Tag: para +#: boot-installer.xml:1481 boot-installer.xml:1617 +#, 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 "进入到下一章继续安装本地语言，网络和磁盘分区。" -#~ msgid "" -#~ "The majority of AlphaServers and all current server and workstation " -#~ "products contain both SRM and AlphaBIOS in their firmware. For " -#~ "half-flash 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 arc command). " -#~ "For the reasons mentioned above, we recommend switching to SRM before " -#~ "installing &debian;." -#~ msgstr "" -#~ "大部分 AlphaServers 以及目前所有的服务器以及工作站产品固件中都同时含有 " -#~ "SRM 和 AlphaBIOS。对于具有不同开发板的 half-flash 机器来" -#~ "说。可以通过重刷固件 来从一个版本切换到另外一个版本。并且一旦 SRM 安装完" -#~ "毕，从软盘上运行 ARC/AlphaBIOS 也是可能的(使用 arc)。基" -#~ "于上述的理由，我们推荐在安装 &debian; 之前切换至 SRM。" +#. Tag: para +#: boot-installer.xml:1492 +#, fuzzy, no-c-format +msgid "" +"Booting an IA-64 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 "" +"在 IA64 系统上面从网络引导很像从 CD 上引导。唯一的区别是如何装入内核。EFI " +"Boot Manager 可以装入并且从网络服务器开始程序。一旦安装内核被装入并且启动，系" +"统 的安装将和 CD 安装步骤相同，只是基本软件包将从网络装入而不是 CD 光盘驱动" +"器。" + +#. Tag: para +#: boot-installer.xml:1526 +#, fuzzy, no-c-format +msgid "" +"Network booting an IA-64 system requires two architecture-specific actions. " +"On the boot server, DHCP and TFTP must be configured to deliver " +"elilo. On the client a new boot option must be defined in " +"the EFI boot manager to enable loading over a network." +msgstr "" +"网络引导一台 IA64 系统需要两个体系相关的操作。在引导服务器上，DHCP 和 TFTP 必" +"须配置成可以传送 elilo。在客户端，一个新的引导选项必须在 " +"EFI Boot Manager 下定义来打开网络的装入。" + +#. Tag: title +#: boot-installer.xml:1537 +#, no-c-format +msgid "Configuring the Server" +msgstr "配置网络服务器" + +#. Tag: para +#: boot-installer.xml:1538 +#, fuzzy, no-c-format +msgid "" +"A suitable TFTP entry for network booting an IA-64 system looks something " +"like this: \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" +" Note that the goal is to get elilo.efi running on the client." +msgstr "" +"一个合适的用于 ia64 系统网络引导的 TFTP 选项应该看起来像这样： " +"\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" +" 注明的是，目标是让 elilo.efi " +"在客户端运行。" + +#. Tag: para +#: boot-installer.xml:1548 +#, no-c-format +msgid "" +"Extract the netboot.tar.gz file into the directory used " +"as the root for your tftp server. Typical tftp root directories include " +"/var/lib/tftp and /tftpboot. This " +"will create a debian-installer directory tree " +"containing the boot files for an IA-64 system." +msgstr "" +"使用 root 解压 netboot.tar.gz 文件到您的 tftp 服务器。典" +"型的 tftp 根目录包括 /var/lib/tftp 和 /" +"tftpboot。这将创建 debian-installer 目录树，" +"它包括 IA-64 系统需要的启动文件。" + +#. Tag: screen +#: boot-installer.xml:1558 +#, 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 "" +"# cd /var/lib/tftp\n" +"# tar xvfz /home/user/netboot.tar.gz\n" +"./\n" +"./debian-installer/\n" +"./debian-installer/ia64/\n" +"[...]" + +#. Tag: para +#: boot-installer.xml:1558 +#, no-c-format +msgid "" +"The netboot.tar.gz contains an elilo.conf file that should work for most configurations. However, should you " +"need to make changes to this file, you can find it in the debian-" +"installer/ia64/ 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 .conf instead of " +"elilo.conf. See documentation provided in the " +"elilo package for details." +msgstr "" +"netboot.tar.gz 包含 elilo.conf 可以" +"工作在大多数的配置下。另外，要修改这个文件，您可以在 debian-" +"installer/ia64/ 目录中找到。这只需要按照客户机 IP 地址的16进制命名" +"这些文件并且给出 .conf 后缀取代 elilo.conf。请查看 elilo 软件包附带的文档以获得细节。" + +#. Tag: title +#: boot-installer.xml:1575 +#, no-c-format +msgid "Configuring the Client" +msgstr "配置客户机" + +#. Tag: para +#: boot-installer.xml:1576 +#, no-c-format +msgid "" +"To configure the client to support TFTP booting, start by booting to EFI and " +"entering the Boot Option Maintenance Menu. " +" Add a boot option. You " +"should see one or more lines with the text Load File [Acpi" +"()/.../Mac()]. 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. Name the entry Netboot or something similar, save, and exit back to the boot options " +"menu. You should see the new boot option " +"you just created, and selecting it should initiate a DHCP query, leading to " +"a TFTP load of elilo.efi from the server." +msgstr "" +"如果要配置支持 TFTP 引导的客户机，只需要引导至 EFI，然后进入 Boot " +"Option Maintenance Menu。 加入一个引" +"导选项。 您会看到一行或多行带有 " +"Load File [Acpi()/.../Mac()] 文字。如果多于一个入" +"口存在，选择您需要启动的包含 MAC 地址的网卡。使用方向键高亮选择，然后按回车。" +" 给此选项起名，如 Netboot 或者相似的，保存然后退回至引导选项菜单。 您现在应该能够看到刚刚创建的新引导选项，选择后应该会初始化一个 " +"DHCP 查询，然后会从服务器装入 elilo.efi。" + +#. Tag: para +#: boot-installer.xml:1608 +#, 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 "" +"在下载并且处理配置文件后，引导装载程序将显示它的提示符。从这里开始，安装过程" +"将和 CD 安装是 同样的过程。在内核已经完成从网络的自我安装后选择一个像上面提到" +"的引导选项，它将开始 Debian 安装程序。" + +#. Tag: title +#: boot-installer.xml:1630 +#, no-c-format +msgid "Choosing an Installation Method" +msgstr "选择安装方法" + +#. Tag: para +#: boot-installer.xml:1632 +#, 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 "" +"一些 &arch-title; 子体系可以选择使用从 2.4.x 或 2.2.x linux 内核启动。如果可" +"以这样选取，请使用 2.4.x linux 内核。使用 2.4.x linux 内核的安装程序要求较少" +"的内存，因为 2.2.x 支持需要固定尺寸的 ramdisk 而 2.4.x 使用 tmpfs。" -#~ msgid "" -#~ "As on other architectures, you should install the newest available " -#~ "revision of the firmware Except on Jensen, where Linux " -#~ "is not supported on firmware versions newer than 1.7 — see for more information. before installing &debian;. For Alpha, firmware updates can be " -#~ "obtained from Alpha Firmware Updates." -#~ msgstr "" -#~ "和另外的体系结构一样，您也应该在安装 &debian; 之前安装最新版本的固件" -#~ "不包括 Jensen，1.7 以上版本的固件不支持 Linux — 查" -#~ "看 以获得更多的信息。。对于 Alpha 来说，固件升级可以通过 Alpha Firmware Updates取得。" +#. Tag: para +#: boot-installer.xml:1640 +#, no-c-format +msgid "" +"If you are using a 2.2.x linux kernel, then you need to use the " +"&ramdisksize; kernel parameter." +msgstr "如果您在使用 2.2.x 内核，那么需要设置 &ramdisksize; 内核参数。" -# index.docbook:274, index.docbook:780, index.docbook:1320, index.docbook:1813, index.docbook:1896, index.docbook:2236, index.docbook:2332 -#~ msgid "Booting with TFTP" -#~ msgstr "用 TFTP 引导" +#. Tag: para +#: boot-installer.xml:1645 +#, no-c-format +msgid "" +"Make sure root=/dev/ram is one of your kernel " +"parameters." +msgstr "确保 root=/dev/ram 在内核参数中。" -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the ewa " -#~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " -#~ "\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" -#~ " You first need to set the boot protocol: " -#~ "\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Then check the medium type is correct: " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " You can get a listing of valid modes with " -#~ ">>>set ewa0_mode." -#~ msgstr "" -#~ "在 SRM 上，以太网界面名字带有 ewa 前缀，并可以用 " -#~ "show dev 命令列出，类似如下显示(可能有一点不同)： " -#~ "\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" -#~ " 您首先需要设置引导协议： " -#~ "\n" -#~ ">>> set ewa0_protocol bootp\n" -#~ " 然后检查媒介类型是否正确： " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " 获得一个有效模式的列表 >>>" -#~ "set ewa0_mode。" +#. Tag: para +#: boot-installer.xml:1650 +#, no-c-format +msgid "" +"If you're having trouble, check cts's " +"&arch-title; debian-installer FAQ." +msgstr "" +"如果碰到麻烦，检查 cts's &arch-title; " +"debian-installer FAQ。" + +#. Tag: title +#: boot-installer.xml:1667 +#, no-c-format +msgid "Amiga" +msgstr "Amiga" + +#. Tag: para +#: boot-installer.xml:1668 +#, no-c-format +msgid "" +"The only method of installation available to amiga is the hard drive (see " +"). In other words the cdrom is not " +"bootable." +msgstr "" +"amiga 仅支持从硬盘安装方式(参阅 )。" +"也就是说 cdrom 无法启动。" -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "接下来，如果从第一个以太网界面引导，您需要输入： " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " 这将 netboot 映象启动，并使用默认的内核参数。" +#. Tag: para +#: boot-installer.xml:1674 +#, no-c-format +msgid "" +"Amiga does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"当前 Amiga 不能与 bogl 一起工作，如果您看到 bogl 错误，您应该包含下面内核参" +"数 fb=false。" + +#. Tag: title +#: boot-installer.xml:1683 +#, no-c-format +msgid "Atari" +msgstr "Atari" + +#. Tag: para +#: boot-installer.xml:1684 +#, no-c-format +msgid "" +"The installer for atari may be started from either the hard drive (see ) or from floppies (see ). In other words the cdrom is not bootable." +msgstr "" +"atari 安装程序可以从硬盘(参阅 ) 或软盘 (参阅 " +")。也就是说 cdrom 无法启动。" +"" -#~ msgid "" -#~ "If you wish to use a serial console, you must pass " -#~ "the console= parameter to the kernel. This can be " -#~ "done using the -flags argument to the SRM " -#~ "boot command. The serial ports are named the same " -#~ "as their corresponding files in /dev. 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 " -#~ "ewa0 and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "如果希望使用一个串行控制台，您 必须 给内核传递 " -#~ "console= 参数。这个工作可以使用附带 -" -#~ "flags 参数的 SRM boot 命令来完成。串口" -#~ "号的命名和它们在目录 /dev 中相同。另外，如有指定额" -#~ "外的内核参数，也必须给 &d-i; 映象重复指定。比如，如果需要从 " -#~ "ewa0 引导，并且在第一个串口使用控制台，您需要输入：" +#. Tag: para +#: boot-installer.xml:1691 +#, no-c-format +msgid "" +"Atari does not currently work with bogl, so if you are seeing bogl errors, " +"you need to include the boot parameter fb=false." +msgstr "" +"当前 Atari 不能与 bogl 一起工作，如果您看到 bogl 错误，应该包含下面内核参数 " +"fb=false。" + +#. Tag: title +#: boot-installer.xml:1700 +#, no-c-format +msgid "BVME6000" +msgstr "BVME6000" + +#. Tag: para +#: boot-installer.xml:1701 +#, no-c-format +msgid "" +"The installer for BVME6000 may be started from a cdrom (see ), floppies (see ), or the net (see )." +msgstr "" +"BVME6000 上安装程序可以从 cdrom (参阅 ), " +"软盘(参阅 )，或网络(参阅 )。" + +#. Tag: title +#: boot-installer.xml:1711 +#, no-c-format +msgid "Macintosh" +msgstr "Macintosh" + +#. Tag: para +#: boot-installer.xml:1712 +#, no-c-format +msgid "" +"The only method of installation available to mac is from the hard drive (see " +"). In other words the cdrom is not " +"bootable. Macs do not have a working 2.4.x kernel." +msgstr "" +"mac 上启动的唯一方法是硬盘(参阅 )。" +"也就是说 cdrom 无法启动。 Macs 不能工作在 2.4 内核上。" -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" +#. Tag: para +#: boot-installer.xml:1719 +#, no-c-format +msgid "" +"If your hardware uses a 53c9x-based scsi bus, then you may need to include " +"the kernel parameter mac53c9x=1,0. Hardware with two " +"such scsi buses, such as the Quadra 950, will need mac53c9x=2,0 instead. Alternatively, the parameter can be specified as " +"mac53c9x=-1,0 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 "" +"如果您的硬件中包括基于 53c9x 的 scsi 总线，那么您需要包括下面的内核参数 " +"mac53c9x=1,0。带有两个这种 scsi 总线的硬件，如 Quadra " +"950，您需要 mac53c9x=2,0 参数。另外，参数指定为 " +"mac53c9x=-1,0 可打开自动侦测，但却禁止了 SCSI 断开。注" +"意，使用这种参数仅用于不止一个硬盘的情况下; 如果不指定，您的系统将运行得更" +"快。" + +#. Tag: title +#: boot-installer.xml:1734 +#, no-c-format +msgid "MVME147 and MVME16x" +msgstr "MVME147 and MVME16x" + +#. Tag: para +#: boot-installer.xml:1735 +#, no-c-format +msgid "" +"The installer for MVME147 and MVME16x may be started from either floppies " +"(see ) or the net (see ). In other words the cdrom is not bootable." +msgstr "" +"MVEM147 和 MVEM16x 可以从软盘(参阅 )或" +"网络(参阅 )。也就是说 cdrom 无法启动。" +"" + +#. Tag: title +#: boot-installer.xml:1745 +#, no-c-format +msgid "Q40/Q60" +msgstr "Q40/Q60" + +#. Tag: para +#: boot-installer.xml:1746 +#, no-c-format +msgid "" +"The only method of installation available to Q40/Q60 is from the hard drive " +"(see ). In other words the cdrom " +"is not bootable." +msgstr "" +"Q40/Q60 只支持从硬盘安装(参阅 )。也" +"就是说 cdrom 无法启动。" -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "采用 SRM 控制台来从 CD 光盘上引导" +#. Tag: title +#: boot-installer.xml:1757 +#, no-c-format +msgid "Booting from a Hard Disk" +msgstr "从硬盘引导" -#~ msgid "" -#~ "Type \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " where xxxx is your " -#~ "CD-ROM drive in SRM notation." -#~ msgstr "" -#~ "输入 \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " 这里 xxxx 是您的光" -#~ "盘驱动器在 SRM 的符号。" - -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "通过 ARC 或者 AlphaBIOS 控制台来从 CD 光盘上启动" +# index.docbook:1591, index.docbook:2097 +#. Tag: para +#: boot-installer.xml:1763 boot-installer.xml:2361 +#, 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 "" +"从一个以存在的操作系统上引导通常是一个方便的选择；对于一些系统来说，这则是唯" +"一支持的 安装方法。" -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see ), then enter \\milo" -#~ "\\linload.exe as the boot loader and \\milo" -#~ "\\subarch (where " -#~ "subarch is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use \\milo\\ldmilo.exe as boot loader." -#~ msgstr "" -#~ "为了从 ARC 控制台引导 CD 光盘，找出您的子体系结构代码名称(参见 )，然后输入 \\milo\\linload.exe 作为引导装载器并且在 `OS Selection Setup' 菜单下选择 " -#~ "\\milo\\subarch (这里 " -#~ "subarch 是相应的子体系结构名称)作为操作系统路" -#~ "径。Ruffians 则是一个例外：您需要使用 \\milo\\ldmilo.exe 作为引导装载器。" - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "通过 SRM 控制台从软盘引导" +# index.docbook:1597, index.docbook:2103 +#. Tag: para +#: boot-installer.xml:1769 boot-installer.xml:2367 +#, no-c-format +msgid "" +"To boot the installer from hard disk, you will have already completed " +"downloading and placing the needed files in ." +msgstr "" +"如果要从硬盘上引导安装程序，您也许已经在 处下载并且在 安置了所需文件。" -#~ msgid "" -#~ "At the SRM prompt (>>>), issue the following " -#~ "command: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possibly replacing dva0 " -#~ "with the actual device name. Usually, dva0 is the " -#~ "floppy; type \n" -#~ ">>> show dev\n" -#~ " to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, -" -#~ "flags argument is ignored, so you can just type boot " -#~ "dva0. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "在 SRM 提示符下 (>>>)，使用如下命令： " -#~ "\n" -#~ ">>> boot dva0 -flags 0\n" -#~ " 可以用实际的设备名称来替换 dva0。通常情况下，dva0 是软盘；输入 " -#~ "\n" -#~ ">>> show dev\n" -#~ " 来查看设备列表(比如，如果您想从一张 CD 上面引" -#~ "导)。注意如果您想通过 MILO 引导 -flags 参数将被忽略，因" -#~ "此您可以只需输入 boot dva0。如果上面步骤工作正常，您将" -#~ "最终看到 Linux 内核引导。" +#. Tag: para +#: boot-installer.xml:1778 +#, 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 MANIFEST for details)." +msgstr "" +"至少有六中不同的 ramdisk 可以从硬盘启动，三个不同的类型分别用于支持或不支持 " +"2.2.x linux 内核(参阅 MANIFEST 了解更多细节)。" -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for dva0, " -#~ "the Linux boot device name for fd0, and the desired " -#~ "kernel parameters for arguments." -#~ msgstr "" -#~ "如果您想在通过 aboot 引导的时候指定特定的内核参数，请使" -#~ "用如下命令： \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (输入到一行)，如果需要，替换 dva0 的真实 SRM 引导设备名 dva0，fd0 的 Linux 引导设备名，arguments 需要的内核参" -#~ "数。" +#. Tag: para +#: boot-installer.xml:1786 +#, no-c-format +msgid "" +"The three different types of ramdisks are cdrom, " +"hd-media, and nativehd. These " +"ramdisks differ only in their source for installation packages. The " +"cdrom ramdisk uses a cdrom to get debian-installer " +"packages. The hd-media ramdisk uses an iso image file " +"of a cdrom currently residing on a hard disk. Finally, the " +"nativehd ramdisk uses the net to install packages." +msgstr "" +"这三种 ramdisk 类型为 cdrom, hd-media，和 nativehd。它们的区别仅在于安装软件包的源不" +"同。cdrom ramdisk 使用 cdrom 获取 debian-installer 软件" +"包。hd-media ramdisk 使用硬盘上的 iso 映象文件。最后，" +"nativehd ramdisk 使用网络安装软件包。" + +#. Tag: title +#: boot-installer.xml:1807 +#, no-c-format +msgid "Booting from AmigaOS" +msgstr "从 AmigaOS 上引导" + +#. Tag: para +#: boot-installer.xml:1808 +#, no-c-format +msgid "" +"In the Workbench, start the Linux installation process by " +"double-clicking on the StartInstall icon in the " +"debian directory." +msgstr "" +"在 Workbench 下，双击 StartInstall 图标" +"来启动 Linux 安装过程，它位于 debian 目录中。" -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " -#~ "See ." -#~ msgstr "" -#~ "如果您想在通过 MILO 启动时指定内核参数，您必须在进入 " -#~ "MILO 时中断引导。参阅 。" +#. Tag: para +#: boot-installer.xml:1814 +#, 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 ." +msgstr "" +"在 Amiga 安装程序在一个窗口已经输出一些调试信息，您也可以按下 &enterkey; 两" +"次。之后屏幕将变灰，这里有一些很短的延迟。接下来，一个黑屏白字将显示更多的调" +"试信息。这些 信息可能上翻的非常快无法看到，但这没有问题。在一些时间过后，安装" +"程序应该自动安装，因此您可以继续参阅 。" + +#. Tag: title +#: boot-installer.xml:1829 +#, no-c-format +msgid "Booting from Atari TOS" +msgstr "从 Atari TOS 引导" + +#. Tag: para +#: boot-installer.xml:1830 +#, no-c-format +msgid "" +"At the GEM desktop, start the Linux installation process by double-clicking " +"on the bootstra.prg icon in the debian directory and clicking Ok at the program " +"options dialog box." +msgstr "" +"在 GEM 桌面上，可以通过双击 bootstra.prg 图标，它位于 " +"debian 目录下，并且在程序选项对话框内点击 " +"Ok 来开始启动安装过程。" -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "在 ARC 或者 AlphaBISO 控制台下从软盘引导" +#. Tag: para +#: boot-installer.xml:1837 +#, 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 ." +msgstr "" +"当 Atari 安装程序在一个窗口输出一些调试信息以后，您可能必须按下 &enterkey;。" +"之后屏幕将变灰，这里有一些很短的延迟。接下来，一个黑屏白字将显示更多的调试信" +"息。这些信息可能上翻的非常快没法看，但这没有问题。在一些时间过后，安装程序应" +"该自动安装，因此您可以继续参阅 。" + +#. Tag: title +#: boot-installer.xml:1852 +#, no-c-format +msgid "Booting from MacOS" +msgstr "从 MacOS 引导" + +#. Tag: para +#: boot-installer.xml:1853 +#, no-c-format +msgid "" +"You must retain the original Mac system and boot from it. It is " +"essential that, when booting MacOS in preparation for " +"booting the Penguin linux loader, you hold the shift 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 "" +"您必须有原来的 Mac 系统，并从它启动。它是 必要的，当启" +"动 MacOS 准备启动 Penguin linux 加载器时，按住 shift 键阻止" +"加载扩展。如果除了加载 linux 不使用 MacOS，您可以从 Mac 的系统文件夹下清除所" +"有的扩展和控制面板达到同样的目的。否则扩展会运行使运行的 linux 内核参数随机错" +"误。" + +#. Tag: para +#: boot-installer.xml:1864 +#, no-c-format +msgid "" +"Macs require the Penguin bootloader. If you do not have " +"the tools to handle a Stuffit archive, &penguin19.hfs; is " +"an hfs disk image with Penguin unpacked. describes how to copy this image to a floppy." +msgstr "" +"Mac 要求 Penguin 加载器。如果您没有这个工具，要把 " +"Stuffit 归档，&penguin19.hfs; 是一个 hfs 磁盘映象，带有 " +"Penguin 解压包。 说明如何" +"将该映象复制到软盘。" + +#. Tag: para +#: boot-installer.xml:1873 +#, no-c-format +msgid "" +"At the MacOS desktop, start the Linux installation process by double-" +"clicking on the Penguin Prefs icon in the " +"Penguin directory. The Penguin " +"booter will start up. Go to the Settings item in " +"the File menu, click the Kernel tab. " +"Select the kernel (vmlinuz) and ramdisk " +"(initrd.gz) images in the install " +"directory by clicking on the corresponding buttons in the upper right " +"corner, and navigating the file select dialogs to locate the files." +msgstr "" +"在 MacOS 桌面，启动 Linux 安装进行需要双击 Penguin Prefs " +"图标，它位于 Penguin 目录。Penguin 引" +"导将开始。进入到 Settings 项，它位于 " +"File菜单，点击 Kernel 选项卡。选择内" +"核(vmlinuz)和 ramdisk (initrd.gz) " +"映象，它位于 install 目录，点击右上角对应的按钮，引导文" +"件选择对话框至文件。" + +#. Tag: para +#: boot-installer.xml:1888 +#, no-c-format +msgid "" +"To set the boot parameters in Penguin, choose File -> " +"Settings..., then switch to the " +"Options tab. Boot parameters may be typed in to the " +"text entry area. If you will always want to use these settings, select " +"File -> Save Settings as Default." +msgstr "" +"为 Penguin 设置启动参数，选择 File -> " +"Settings...，然后切换到 Options 选项卡。启动参数可以写到文本区域。如果您要一直采用这些设置，选择 " +"File -> 保存设置为默认。" + +#. Tag: para +#: boot-installer.xml:1897 +#, no-c-format +msgid "" +"Close the Settings dialog, save the settings and start " +"the bootstrap using the Boot Now item in the " +"File menu." +msgstr "" +"关闭 Settings 对话框，保存设置然后开始引导用 " +"Boot Now 项，它位于 File 菜单。" -#~ msgid "" -#~ "In the OS Selection menu, set linload.exe as the boot " -#~ "loader, and milo as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "在操作系统选择菜单内，设置 linload.exe 作为引导装载器，" -#~ "并且 milo 作为操作系统参数。然后使用这个最近建立的选项" -#~ "启动。" +#. Tag: para +#: boot-installer.xml:1904 +#, no-c-format +msgid "" +"The Penguin 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 ." +msgstr "" +"Penguin 启动将输出一些调试信息到窗口。然后，屏幕变灰，会有" +"数秒延迟。接着，带有文本的黑屏出现，显示各种内核调试信息。这些信息可能滚动很" +"快无法阅读，这是正常的。再过一段时间，安装程序就会自动运行，您可以按下面步骤" +"继续 。" + +#. Tag: title +#: boot-installer.xml:1919 +#, no-c-format +msgid "Booting from Q40/Q60" +msgstr "从 Q40/Q60 启动" + +#. Tag: para +#: boot-installer.xml:1921 +#, no-c-format +msgid "FIXME" +msgstr "FIXME" + +#. Tag: para +#: boot-installer.xml:1925 +#, no-c-format +msgid "" +"The installation program should start automatically, so you can continue " +"below at ." +msgstr "" +"安装程序就会自动运行，您可以按下面步骤继续 。" -#~ msgid "Booting with MILO" -#~ msgstr "采用 MILO 引导" +#. Tag: para +#: boot-installer.xml:1937 +#, no-c-format +msgid "" +"Currently, the only &arch-title; subarchitecture that supports CD-ROM " +"booting is the BVME6000." +msgstr "目前唯一 &arch-title; 子体系结构支持 CD 光盘引导的是 BVME6000。" -#~ 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 "" -#~ "自我启动介质上的 MILO 会自动直接进入 Linux 引导过程。如果您要对此有所控" -#~ "制，只需要在 MILO 倒计时时按下空格键。" +#. Tag: para +#: boot-installer.xml:2009 +#, no-c-format +msgid "" +"After booting the VMEbus systems you will be presented with the LILO " +"Boot: 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 "" +"在引导 VMEbus 系统后您应该看到 LILO Boot: 提示符。在提示符下" +"输入以下一种方法来引导 Linux，并开始在一个 vt102 仿真终端下面安装普通的 " +"Debian 软件。" + +#. Tag: para +#: boot-installer.xml:2020 +#, no-c-format +msgid "type i6000 &enterkey; to install a BVME4000/6000" +msgstr "输入 i6000 &enterkey; 来安装 BVME4000/6000" + +#. Tag: para +#: boot-installer.xml:2025 +#, no-c-format +msgid "type i162 &enterkey; to install an MVME162" +msgstr "输入 i162 &enterkey; 来安装 MVME162" + +#. Tag: para +#: boot-installer.xml:2030 +#, no-c-format +msgid "type i167 &enterkey; to install an MVME166/167" +msgstr "输入 i167 &enterkey; 来安装 MVME166/167" + +#. Tag: para +#: boot-installer.xml:2037 +#, no-c-format +msgid "" +"You may additionally append the string TERM=vt100 to use " +"vt100 terminal emulation, e.g., i6000 TERM=vt100 &enterkey;." +msgstr "" +"您也可以附加一个字符串 TERM=vt100 来使用 vt100 终端模拟。比" +"如,i6000 TERM=vt100 &enterkey;。" -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" If you are booting from something other than a " +"floppy, substitute fd0 in the above example with the " +"appropriate device name in Linux notation. The help " +"command would give you a brief MILO command reference." +msgstr "" +"如果您確切想指定所有的位元 (例如，支援附加的參數)，您可以使用像下面的指令：" +"\n" +"MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1 \n" +" 如果透過軟碟之外的方法開機，在 Linux 提示號下把上" +"面例子中的 fd0 替換成合適的設備名稱。help 指令將列出簡單的 MILO 指令參考。" + +#. Tag: title +#: boot-installer.xml:435 +#, no-c-format +msgid "Booting from TFTP" +msgstr "從 TFTP 開機" -# index.docbook:110, index.docbook:113, index.docbook:119, index.docbook:125, index.docbook:128, index.docbook:131, index.docbook:134, index.docbook:140, index.docbook:143, index.docbook:146, index.docbook:155, index.docbook:164, index.docbook:179, index.docbook:182, index.docbook:188 -#~ msgid "ARC or SRM" -#~ msgstr "ARC or SRM" +# index.docbook:432, index.docbook:786, index.docbook:1338, index.docbook:1819, index.docbook:2242, index.docbook:2338 +#. Tag: para +#: boot-installer.xml:441 boot-installer.xml:1005 boot-installer.xml:1508 +#: boot-installer.xml:1991 boot-installer.xml:2506 boot-installer.xml:2602 +#, 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 "" +"要從網路開機，您的機器必須連接上網路和一台 TFTP 網路開機伺服器 (DHCP, RARP 以" +"及 BOOTP)。" -#~ msgid "avanti" -#~ msgstr "avanti" +# index.docbook:437, index.docbook:791, index.docbook:1343, index.docbook:1824, index.docbook:2247, index.docbook:2343 +#. Tag: para +#: boot-installer.xml:446 boot-installer.xml:1010 boot-installer.xml:1513 +#: boot-installer.xml:1996 boot-installer.xml:2511 boot-installer.xml:2607 +#, no-c-format +msgid "" +"Older systems such as the 715 might require the use of an RBOOT server " +"instead of a BOOTP server." +msgstr "較早的系統如 715 也許需要使用一台 RBOOT 伺服器來取代 BOOTP 伺服器。" -#~ msgid "book1" -#~ msgstr "book1" +# index.docbook:442, index.docbook:796, index.docbook:1348, index.docbook:1829, index.docbook:2252, index.docbook:2348 +#. Tag: para +#: boot-installer.xml:451 boot-installer.xml:1015 boot-installer.xml:1518 +#: boot-installer.xml:2001 boot-installer.xml:2516 boot-installer.xml:2612 +#, no-c-format +msgid "" +"The installation method to support network booting is described in ." +msgstr "支援的網路開機安裝方法在 。" + +#. Tag: title +#: boot-installer.xml:459 +#, fuzzy, no-c-format +msgid "Booting from TFTP on Netwinder" +msgstr "從 NetWinder 上的 TFTP 開機" + +#. 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 eth0) 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 interface (the one " +"labeled with 10 Base-T)." +msgstr "" -# index.docbook:116, index.docbook:122, index.docbook:137, index.docbook:149, index.docbook:158, index.docbook:161, index.docbook:167, index.docbook:173, index.docbook:176 -#~ msgid "SRM only" -#~ msgstr "SRM only" +#. Tag: para +#: boot-installer.xml:469 +#, fuzzy, 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 ." +msgstr "" +"您需要 NeTTrom 2.2.1 或者較高的版本來啟動安裝系統。建議使用 NeTTrom 2.3.3：請" +"從下面網址取得 :" -#~ msgid "cabriolet" -#~ msgstr "cabriolet" +#. 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: \n" +" NeTTrom command-> load-defaults\n" +" Furthermore, you must configure the network, " +"either with a static address: \n" +" NeTTrom command-> setenv netconfig_eth0 flash\n" +" NeTTrom command-> setenv eth0_ip 192.168.0.10/24\n" +" where 24 is the number of set bits in the " +"netmask, or a dynamic address: \n" +" NeTTrom command-> setenv netconfig_eth0 dhcp\n" +" You may also need to configure the " +"route1 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. " +"\n" +" NeTTrom command-> setenv kerntftpserver 192.168.0.1\n" +" NeTTrom command-> setenv kerntftpfile boot.img\n" +" NeTTrom command-> save-all\n" +" Now you have to tell the firmware that the TFTP " +"image should be booted: \n" +" NeTTrom command-> setenv kernconfig tftp\n" +" NeTTrom command-> setenv rootdev /dev/ram\n" +" If you use a serial console to install your " +"Netwinder, you need to add the following setting: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram " +"console=ttyS0,115200\n" +" Alternatively, for installations using a " +"keyboard and monitor you have to set: \n" +" NeTTrom command-> setenv cmdappend root=/dev/ram\n" +" You can use the printenv " +"command to review your environment settings. After you have verified that " +"the settings are correct, you can load the image: \n" +" NeTTrom command-> boot\n" +" In case you run into any problems, a detailed HOWTO is available." +msgstr "" -#~ msgid "dp264" -#~ msgstr "dp264" +#. Tag: title +#: boot-installer.xml:529 +#, no-c-format +msgid "Booting from TFTP on CATS" +msgstr "透過 CATS 上的 TFTP 開機" -#~ msgid "eb164" -#~ msgstr "eb164" +#. Tag: para +#: boot-installer.xml:530 +#, no-c-format +msgid "" +"On CATS machines, use boot de0: or similar at the Cyclone " +"prompt." +msgstr "" +"在 CATS 機器上，可以使用指令 boot de0: 或者在 Cyclone 開機" +"提示號輸入類似的指令。" -#~ msgid "eb64p" -#~ msgstr "eb64p" +#. Tag: title +#: boot-installer.xml:540 +#, no-c-format +msgid "Booting from CD-ROM" +msgstr "從光碟開機" -#~ msgid "eb66" -#~ msgstr "eb66" +# index.docbook:531, index.docbook:584, index.docbook:957, index.docbook:1776, index.docbook:2024, index.docbook:2378 +#. Tag: para +#: boot-installer.xml:546 boot-installer.xml:716 boot-installer.xml:1127 +#: boot-installer.xml:1948 boot-installer.xml:2288 boot-installer.xml:2642 +#, fuzzy, 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 configure your system for booting off a " +"CD as described in , insert " +"your CD, reboot, and proceed to the next chapter." +msgstr "" +"對於大多數人來說，最快的途徑是使用一套 Debian CD 光碟套件。如果您有此套件，並" +"且如果您的機器支援直接光碟開機，太棒了！只需要 設定您" +"的系統以光碟開機，請參閱 , 插入" +"您的光碟，重開機，然後繼續下一章。" -#~ msgid "eb66p" -#~ msgstr "eb66p" +# index.docbook:542, index.docbook:595, index.docbook:968, index.docbook:1787, index.docbook:2035, index.docbook:2389 +#. Tag: para +#: boot-installer.xml:557 boot-installer.xml:727 boot-installer.xml:1138 +#: boot-installer.xml:1959 boot-installer.xml:2299 boot-installer.xml:2653 +#, 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 "" +"注意某些特定的光碟機需要一些特殊的驅動程式，因為他們可能在安裝的早期步驟中無" +"法被存取。如果標準的光碟開機的方法不能用於您的硬體，閱讀本章中關於其他種類的" +"核心以及安裝方法，它們有可能能解決問題。" -#~ msgid "jensen" -#~ msgstr "jensen" +# index.docbook:550, index.docbook:603, index.docbook:976, index.docbook:1795, index.docbook:2043, index.docbook:2397 +#. Tag: para +#: boot-installer.xml:565 boot-installer.xml:735 boot-installer.xml:1146 +#: boot-installer.xml:1967 boot-installer.xml:2307 boot-installer.xml:2661 +#, 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 "" +"即便您不能從光碟開機，依然可以安裝光碟上面的 Debian 系統組件和所有軟體套件。" +"只需要使用不同的媒介，例如軟碟來開機即可。當安裝作業系統、基礎系統和任意附加" +"的軟體套件時只需指向安裝系統至光碟機即可。" -#~ msgid "lx164" -#~ msgstr "lx164" +# index.docbook:558, index.docbook:611, index.docbook:984, index.docbook:1803, index.docbook:2051, index.docbook:2405 +#. Tag: para +#: boot-installer.xml:573 boot-installer.xml:743 boot-installer.xml:1154 +#: boot-installer.xml:1975 boot-installer.xml:2315 boot-installer.xml:2669 +#, no-c-format +msgid "" +"If you have problems booting, see ." +msgstr "" +"如果您遇到開機方面的問題，請參閱 。" -#~ msgid "miata" -#~ msgstr "miata" +#. Tag: para +#: boot-installer.xml:580 +#, no-c-format +msgid "" +"To boot a CD-ROM from the Cyclone console prompt, use the command " +"boot cd0:cats.bin" +msgstr "" +"如果需要在 Cyclone 控制台提示符號下從光碟下開機，請使用指令 boot " +"cd0:cats.bin" + +#. Tag: title +#: boot-installer.xml:589 +#, fuzzy, no-c-format +msgid "Booting from Firmware" +msgstr "從 OpenFirmware 開機 CHRP" + +#. 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 "" -#~ msgid "mikasa" -#~ msgstr "mikasa" +#. 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 "" -#~ msgid "mikasa-p" -#~ msgstr "mikasa-p" +#. Tag: title +#: boot-installer.xml:612 +#, fuzzy, no-c-format +msgid "Booting the NSLU2" +msgstr "採用 MILO 開機" -#~ msgid "nautilus" -#~ msgstr "nautilus" +#. Tag: para +#: boot-installer.xml:613 +#, no-c-format +msgid "There are three ways how to put the installer firmware into flash:" +msgstr "" -#~ msgid "ARC (see motherboard manual) or SRM" -#~ msgstr "ARC (see motherboard manual) or SRM" +#. Tag: title +#: boot-installer.xml:619 +#, no-c-format +msgid "Using the NSLU2 web interface" +msgstr "" -#~ msgid "noname" -#~ msgstr "noname" +#. Tag: para +#: boot-installer.xml:620 +#, no-c-format +msgid "" +"Go to the administration section and choose the menu item Upgrade. You can then browse your disk for the installer image you have " +"previously downloaded. Then press the Start Upgrade " +"button, confirm, wait for a few minutes and confirm again. The system will " +"then boot straight into the installer." +msgstr "" -#~ msgid "noritake" -#~ msgstr "noritake" +#. Tag: title +#: boot-installer.xml:631 +#, no-c-format +msgid "Via the network using Linux/Unix" +msgstr "" -#~ msgid "noritake-p" -#~ msgstr "noritake-p" +#. Tag: para +#: boot-installer.xml:632 +#, no-c-format +msgid "" +"You can use upslug2 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: " +" Disconnect any disks and/or devices from the USB ports. Power off the NSLU2 " +" Press and hold the reset button (accessible through the " +"small hole on the back just above the power input). " +" Press and release the power button to power on the NSLU2. Wait for 10 seconds watching the ready/" +"status LED. After 10 seconds it will change from amber to red. Immediately " +"release the reset button. 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. See the NSLU2-Linux pages if you have " +"problems with this. Once your NSLU2 is in upgrade mode, you can flash the " +"new image: \n" +"sudo upslug2 -i di-nslu2.bin\n" +" 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 "" -#~ msgid "pc164" -#~ msgstr "pc164" +#. Tag: title +#: boot-installer.xml:693 +#, no-c-format +msgid "Via the network using Windows" +msgstr "" -#~ msgid "rawhide" -#~ msgstr "rawhide" +#. Tag: para +#: boot-installer.xml:694 +#, no-c-format +msgid "" +"There is a tool for Windows to upgrade the firmware " +"via the network." +msgstr "" -#~ msgid "ruffian" -#~ msgstr "ruffian" +# index.docbook:578, index.docbook:951, index.docbook:1764, index.docbook:2018, index.docbook:2372 +#. Tag: title +#: boot-installer.xml:710 boot-installer.xml:1121 boot-installer.xml:1936 +#: boot-installer.xml:2282 boot-installer.xml:2636 +#, no-c-format +msgid "Booting from a CD-ROM" +msgstr "從光碟開機" + +#. Tag: title +#: boot-installer.xml:848 +#, no-c-format +msgid "" +"Booting from Linux Using LILO or GRUB" +msgstr "使用 LILO 或 GRUB 啟動 Linux" -# index.docbook:170, index.docbook:185 -#~ msgid "ARC only" -#~ msgstr "ARC only" +#. 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 ." +msgstr "" +"為了從硬碟開機安裝程式，您首先必須按照要求下載並且放置所需的文件，請參閱 " +"。" -#~ msgid "sable" -#~ msgstr "sable" +#. Tag: para +#: boot-installer.xml:856 +#, fuzzy, 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 netboot/" +"debian-installer/i386/initrd.gz file and its corresponding kernel " +"netboot/debian-installer/i386/linux. This will allow " +"you to repartition the hard disk from which you boot the installer, although " +"you should do so with care." +msgstr "" +"如果您只想用硬碟開機，然後從網路下載其他檔案，您需要下載 netboot/" +"debian-installer/i386/initrd.gz 及其對應的核心。這將允許您重新分割" +"您用於開機的硬碟。這裡需要小心操作。" -#~ msgid "sable-g" -#~ msgstr "sable-g" +#. Tag: para +#: boot-installer.xml:866 +#, 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 hd-media/initrd." +"gz file and its kernel, as well as copy a CD iso to the drive " +"(make sure the file is named ending in .iso). The " +"installer can then boot from the drive and install from the CD image, " +"without needing the network." +msgstr "" +"或者，如果您想要保持安裝硬碟原有分割區，可以下載 hd-media/initrd." +"gz 檔案及其核心，複製一個光碟 iso 檔到硬碟上 (確保文件名結尾是 " +".iso)。安裝程式就可以不使用網路而從硬碟開機，並且從光碟映" +"像檔上安裝。" + +#. Tag: para +#: boot-installer.xml:875 +#, no-c-format +msgid "" +"For LILO, you will need to configure two essential things " +"in /etc/lilo.conf: to " +"load the initrd.gz installer at boot time; have the vmlinuz kernel use " +"a RAM disk as its root partition. Here is " +"a /etc/lilo.conf example:" +msgstr "" +"如果採用 LILO，您需要在 /etc/lilo.conf 中設定兩件最基本的事情: 在開機時載" +"入 initrd.gz 安裝程式﹔ " +" 讓 vmlinuz 核心使用一個記憶體虛擬磁碟作" +"為它的根分割區。 這裡是一個 /etc/" +"lilo.conf 的例子：" + +#. Tag: screen +#: boot-installer.xml:896 +#, fuzzy, 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 "" +"image=/boot/newinstall/vmlinuz\n" +" label=newinstall\n" +" initrd=/boot/newinstall/initrd.gz\n" +" root=/dev/ram0\n" +" append=\"devfs=mount,dall ramdisk_size=12000\"" + +#. Tag: para +#: boot-installer.xml:896 +#, no-c-format +msgid "" +"For more details, refer to the initrd 4 and " +"lilo.conf 5 man pages. Now run lilo and " +"reboot." +msgstr "" +"欲獲知更多細節，請參閱 initrd " +"4 和 lilo." +"conf 5 man 手冊。現在執" +"行 lilo 並且重新啟動。" + +#. Tag: para +#: boot-installer.xml:905 +#, fuzzy, no-c-format +msgid "" +"The procedure for GRUB is quite similar. Locate your " +"menu.lst in the /boot/grub/ " +"directory (sometimes in the /boot/boot/grub/), add the " +"following lines: \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" +" and reboot." +msgstr "" +"採用 GRUB 的設定過程也很相似。在 /boot/grub/ 目錄下 (有時會是 /boot/boot/grub/) 找出您的 " +"menu.lst，加入幾行：\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" +" 並重開機。如果開機失" +"敗，您可以嘗試在 kernel 行添加 devfs=mount,dall。" + +#. Tag: para +#: boot-installer.xml:916 +#, no-c-format +msgid "" +"Note that the value of the ramdisk_size may need to " +"be adjusted for the size of the initrd image. From here on, there should be " +"no difference between GRUB or LILO." +msgstr "" +"注意 ramdisk_size 的值也許需要調整至 initrd 映像的大" +"小。從此之後，採用 GRUB 或 LILO 都沒區" +"別。" -#~ msgid "sx164" -#~ msgstr "sx164" +# index.docbook:700, index.docbook:2176 +#. Tag: title +#: boot-installer.xml:927 +#, no-c-format +msgid "Booting from USB Memory Stick" +msgstr "從 USB 隨身碟開機" + +#. Tag: para +#: boot-installer.xml:928 +#, no-c-format +msgid "" +"Let's assume you have prepared everything from and . 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 boot: " +"prompt. Here you can enter optional boot arguments, or just hit &enterkey;." +msgstr "" +"假設您已經準備好了從 到 的所有步驟。現在只需要插入您的 USB 隨身碟到一個空的 USB " +"插槽並且重新啟動電腦。系統應該能夠開機，並且您會看到 boot: " +"提示符號。您可以輸入一些開機選項，或者只是按下 &enterkey;。" -#~ msgid "takara" -#~ msgstr "takara" +# index.docbook:723, index.docbook:1876, index.docbook:2278, index.docbook:2426 +#. Tag: title +#: boot-installer.xml:941 boot-installer.xml:2048 boot-installer.xml:2542 +#: boot-installer.xml:2690 +#, no-c-format +msgid "Booting from Floppies" +msgstr "從軟碟開機" -#~ msgid "xl" -#~ msgstr "xl" +# index.docbook:724, index.docbook:2286 +#. Tag: para +#: boot-installer.xml:942 boot-installer.xml:2550 +#, no-c-format +msgid "" +"You will have already downloaded the floppy images you needed and created " +"floppies from the images in ." +msgstr "" +"您可能已經下載了所需要得軟碟映像，並且根據這些映像建立了軟碟 。" -#~ msgid "xlt" -#~ msgstr "xlt" +#. Tag: para +#: boot-installer.xml:949 +#, 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 "" +"從軟碟開機安裝程式需要放置軟碟至主軟碟機。按照您平時的習慣關閉系統，然後重新" +"啟動。" -#~ msgid "" -#~ "Generally, none of these consoles can boot Linux directly, so the " -#~ "assistance of an intermediary bootloader is required. For the SRM " -#~ "console, aboot, a small, platform-independent " -#~ "bootloader, is used. See the (unfortunately outdated) SRM HOWTO for more information on aboot." -#~ msgstr "" -#~ "一般來說，這些控制台都不能直接以 Linux 開機，因此需要一個中繼的 boot-" -#~ "loader。SRM 控制台使用一個小型的、平台獨立的 boot-loader，aboot。請參閱 (抱歉的是它也有點過時了) SRM HOWTO來獲得更多有關資訊 aboot。" +#. Tag: para +#: boot-installer.xml:955 +#, fuzzy, 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 root= 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 " +"linux root=/dev/hdc at the boot prompt." +msgstr "" +"如果想在 LS-120 磁碟機 (ATAPI 版本) 使用這些軟碟，您需要指定這些軟碟設備的虛" +"擬位址。這個可以透過 root= 開機參數來指定映射的 ide-" +"floppy 磁碟機名稱來完成。例如，如果您的 LS-120 磁碟機連接到第二條排線上的第一" +"個 IDE 設備 (master)，那麼在提示符號下輸入 linux root=/dev/hdc。從 LS-120 上安裝只為 2.4 及其以後版本的核心支援。" + +#. Tag: para +#: boot-installer.xml:965 +#, no-c-format +msgid "" +"Note that on some machines, Control Alt Delete does not properly reset the " +"machine, so a hard 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 "" +"注意有些機器使用，Control Alt " +"Delete 不能重新啟動系統，所以建議使用硬重開機。如果您從一個既有的作業系統上安裝 (例如從 DOS 上) 您不需要這樣。" +"否則，請用硬重開機的方法來開機。" + +#. Tag: para +#: boot-installer.xml:974 +#, 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 boot: prompt." +msgstr "" +"讀完軟碟後，您將看到螢幕上有一段有關開機軟碟的介紹，並且結尾是 boot:" +" 提示符號。" -#~ 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 "" -#~ "以下章節來自 woody 安裝手冊，放在這裡作為參考﹔如果以後 Debian 再支援基於 " -#~ "MILO 的安裝，它們或許對某些人有用。" +#. Tag: para +#: boot-installer.xml:980 +#, no-c-format +msgid "" +"Once you press &enterkey;, you should see the message " +"Loading..., followed by " +"Uncompressing Linux..., 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 ." +msgstr "" +"一旦您按下 &enterkey;，您應該能夠看到 Loading... 消息，並且接下來是 Uncompressing Linux...，然後是一些有關您系統的硬體資訊。想知道更多有關這段開機過程的" +"資訊，請參考 。" + +#. Tag: para +#: boot-installer.xml:989 +#, 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 debian-installer is automatically " +"launched." +msgstr "" +"軟碟開機後需要根軟碟。請插入根軟碟並且輸入 &enterkey;，然後其中的內容會被載入" +"記憶體。安裝程式 debian-installer 會自動啟動。" + +#. Tag: para +#: boot-installer.xml:1023 +#, no-c-format +msgid "There are various ways to do a TFTP boot on i386." +msgstr "在 i386 架構上有很多方法用 TFTP 進行開機。" + +#. Tag: title +#: boot-installer.xml:1029 +#, no-c-format +msgid "NIC or Motherboard that support PXE" +msgstr "支援 PXE 的網卡或者主機板" + +#. Tag: para +#: boot-installer.xml:1030 +#, no-c-format +msgid "" +"It could be that your Network Interface Card or Motherboard provides PXE " +"boot functionality. This is a Intel " +"re-implementation of TFTP boot. If so you may be able to configure your BIOS " +"to boot from the network." +msgstr "" +"您的網卡或者主機板可能已經提供了 PXE 開機功能。這 Intel TFTP 開機的再實作。如果是這樣，也許可以能夠設定您的 " +"BIOS 來用網路進行開機。" + +#. Tag: title +#: boot-installer.xml:1041 +#, no-c-format +msgid "NIC with Network BootROM" +msgstr "採用 Network BootROM 的網卡" + +#. Tag: para +#: boot-installer.xml:1042 +#, no-c-format +msgid "" +"It could be that your Network Interface Card provides TFTP boot " +"functionality." +msgstr "您的網卡很有可能提供了 TFTP 開機功能。" -#~ 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: MILO and aboot." -#~ msgstr "" -#~ "一般來說，這些控制台都不能直接以 Linux 開機，因此需要一個中繼的 boot-" -#~ "loader。這裡有兩個主要的 Linux loader：MILO 和 " -#~ "aboot。" +#. Tag: para +#: boot-installer.xml:1047 +#, no-c-format +msgid "" +"Let us (&email-debian-boot-list;) know how did you manage it. " +"Please refer to this document." +msgstr "" +"請讓我們知道 (&email-debian-boot-list;) 您如何操作，並參考此文" +"件。" + +#. Tag: title +#: boot-installer.xml:1055 +#, no-c-format +msgid "Etherboot" +msgstr "Etherboot" + +#. Tag: para +#: boot-installer.xml:1056 +#, no-c-format +msgid "" +"The etherboot project " +"provides bootdiskettes and even bootroms that do a TFTPboot." +msgstr "" +"etherboot project 提供了為 " +"TFTP 開機所需要的開機軟碟甚至是開機 ROMS 。" -#~ msgid "" -#~ "MILO is itself a console, which replaces ARC or SRM in " -#~ "memory. MILO can be booted from both ARC and SRM and " -#~ "is the only way to bootstrap Linux from the ARC console. MILO is platform-specific (a different MILO 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) MILO HOWTO." -#~ msgstr "" -#~ "MILO 自己本身就是一個控制台，可以替換載入記憶體中的 " -#~ "ARC 和 SRM。MILO 能夠同時從 ARC 和 SRM 開機並且是唯一一" -#~ "種從 ARC 控制台啟動 Linux 的方法。MILO 是與平台相依的 " -#~ "(對於每種不同的系統需要不同的 MILO) 並且只適合這些平" -#~ "台。請參閱 (很遺憾有點過時) MILO HOWTO。" +# index.docbook:1943, index.docbook:2477 +#. Tag: title +#: boot-installer.xml:1065 +#, no-c-format +msgid "The Boot Prompt" +msgstr "開機提示" + +#. Tag: para +#: boot-installer.xml:1066 +#, 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: " +"\n" +"Press F1 for help, or ENTER to boot:\n" +" 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 "" +"安裝程式啟動後，您應該會看到一個友善的畫面，顯示著 Debian 的標誌，以及啟動提" +"示：\n" +"Press F1 for help, or ENTER to boot:\n" +" 在提示號下您可以直接按下 &enterkey; 來使用預設選" +"項啟動安裝程式，或者輸入參數以指定您要使用的啟動方式。" + +#. Tag: para +#: boot-installer.xml:1078 +#, fuzzy, no-c-format +msgid "" +"Information on available boot methods and on boot parameters which might be " +"useful can be found by pressing F2 through F8. If you add any parameters to the boot command line, be sure to type " +"the boot method (the default is linux) and a space " +"before the first parameter (e.g., linux fb=false)." +msgstr "" +"有關開機參數的資訊可能會很有用。它可以透過 F3 到 F7F8 來得知。如果您加入任何參數至開機命令列，請確" +"保在開機方法 (預設是 linux) 和第一個參數之間有一個空" +"格 (例如 linux floppy=thinkpad)。如果您只鍵入 " +"&enterkey;，這等同於輸入 linux 不附帶任何參數。" + +#. Tag: para +#: boot-installer.xml:1087 +#, fuzzy, 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 integrated Lights Out (iLO) and HP's " +"Integrated Remote Assistant (IRA). You can blindly press " +"F1 In some cases these devices will require special escape " +"sequences to enact this keypress, for example the IRA uses " +"Ctrl F , 1. 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 fb=false to the boot prompt, as described in " +"the help text." +msgstr "" +"如果您透過提供 VGA 文字介面的遠端遙控設備來安裝系統，您可能無法看到安裝程式一" +"開始顯示的版權圖形；您甚至可能看不到啟動提示號。這些設備例如康柏的 " +"integrated Lights Out (iLO) 和 Integrated Remote " +"Assistant (IRA) 的文字控制台。您可以直接按下 F1 在某" +"些狀況下，這些設備需要特殊的跳脫字串來啟用這個按鍵，例如 IRA 使用 " +"Ctrl F , 1. 來跳過這個畫面，並且顯示說明畫面。只要您離開了圖" +"標畫面並進入了說明文字畫面，您的按下的按鍵就會顯示在螢幕上。為了防止安裝程式" +"在之後的安裝步驟中使用 framebuffer，您可能會加入 debian-installer/" +"framebuffer=false 到啟動參數中，如同說明文字中描述的。" + +#. Tag: title +#: boot-installer.xml:1162 +#, no-c-format +msgid "CD Contents" +msgstr "光碟的內容" + +#. Tag: para +#: boot-installer.xml:1164 +#, no-c-format +msgid "" +"There are three basic variations of Debian Install CDs. The " +"Business Card 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 Network Install 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 "" +"有三種基本的 Debian 安裝光碟衍生品：名片式光碟具有最少量" +"的安裝程式並且可以裝在一小張光碟上。它的安裝需要網路連接來安裝其他部分的基本" +"安裝程式以建立一個可用的系統。網路安裝光碟具有所有基礎安" +"裝所需要的套件但是它還是需要一個能連接到 Debian 鏡像網站的網路連接來安裝其他" +"的軟體套件來建立一個完全的系統。Debian 光碟套件則可以不透過網路就可以安裝一個" +"具有各種範圍軟體套件的完全系統。" + +#. Tag: para +#: boot-installer.xml:1180 +#, 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 "" +"IA-64 使用 Intel 最新的可拓展韌體界面 (Extensible Firmware Interface, EFI)。" +"與傳統的 x86 BIOS 只瞭解分割區表和主開機記錄 (MBR) 而不知道其他開機設備的特點" +"不同，EFI 可以 對 FAT16 和 FAT32 格式的硬碟分割區進行讀寫操作。這個特點簡化了" +"通常很難以理解的系統啟動過程。系統的 boot-loader 以及 EFI 韌體支援一個完全的" +"檔案系統來保存啟動機器所需要的所有檔案。這意味著在一個 IA-64 系統上的系統磁碟" +"具有一個附加的專門為 EFI 服務的磁碟分割區而不是像傳統系統上只是簡單的 MBR 或" +"者開機塊記錄。" + +#. Tag: para +#: boot-installer.xml:1196 +#, no-c-format +msgid "" +"The Debian Installer CD contains a small EFI partition where the " +"ELILO 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 "" +"Debian CD 包含了一個小型版本的 EFI 分割區來放置其設定檔ELILO、安裝程式核心以及初始的檔案系統 (initrd)。運行的系統同時也包含了一" +"個 EFI 分割區用於放置開機系統所需要的必要檔案。這些檔案可以從 EFI Shell 讀" +"出，描述如下。" + +#. Tag: para +#: boot-installer.xml:1205 +#, no-c-format +msgid "" +"Most of the details of how ELILO 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 ELILO 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 "" +"大部分有關 ELILO 如何實際裝入和啟動系統的細節對系統安裝程" +"式是透明的。但是，安裝程式必須設置 EFI 分割區優先級來安裝基本系統。否則 " +"ELILO 的安裝將會失敗並且導致系統不可開機。EFI 分割區是是在" +"分割步驟中被分割出來且格式化的，之後安裝程式就會宰入系統磁碟的所有軟體套件。" +"分割步驟也會在繼續安裝步驟前檢查 EFI 分割區是否合適。" + +#. Tag: para +#: boot-installer.xml:1217 +#, 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, Boot Option " +"Maintenance Menu and EFI Shell (Built-in). " +"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 "" +"EFI Boot Manager 在韌體初始化的最後一步會被啟動。它顯示一個選單列表供使用者選" +"擇。取決於系統的型號並且是否有其他的軟體已經被裝入系統，這個選單在不同系統上" +"可能會不同。在每一個系統上，至少會有兩個選單項，Boot Option " +"Maintenance Menu 與 EFI Shell (Built-in)。建議使" +"用第一個，當然，若該選項不可用或者 CD 由於某種原因沒法啟動，使用第二個。" + +#. Tag: title +#: boot-installer.xml:1236 +#, no-c-format +msgid "IMPORTANT" +msgstr "重要" + +#. Tag: para +#: boot-installer.xml:1237 +#, 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 exit at the " +"shell prompt." +msgstr "" +"EFI Boot Manager 會在預設的幾秒鐘之後選擇預設的啟動方式，一般是第一選單項。在" +"螢幕底部會有倒計時顯示。時間一到，系統按預設方式啟動，這樣您也許需要重新啟動" +"才能繼續安裝。如果預設是 EFI Shell，您可在提示符號下執行 exit 以返回 Boot Manager。" + +#. Tag: title +#: boot-installer.xml:1249 +#, no-c-format +msgid "Option 1: Booting from the Boot Option Maintenance Menu" +msgstr "選項 1: 從 Boot Option Maintenance Menu 啟動" + +#. Tag: para +#: boot-installer.xml:1256 +#, 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 "" +"插入光碟到 DVD/CD 光碟機，然後重啟機器。韌體在完成系統初始化後會顯示 EFI " +"Boot Manager 頁面和選單。" -#~ msgid "" -#~ "aboot is a small, platform-independent bootloader, " -#~ "which runs from SRM only. See the (also unfortunately outdated) SRM HOWTO for more information on " -#~ "aboot." -#~ msgstr "" -#~ "aboot 是一個小型的，平台獨立的 boot-loader，不過只運作" -#~ "於 SRM 上。請參閱 (遺憾的是它也有點過時了 ) SRM HOWTO來取得更多有關資訊 aboot。" +#. Tag: para +#: boot-installer.xml:1262 +#, no-c-format +msgid "" +"Select Boot Maintenance Menu from the menu with the arrow " +"keys and press ENTER. This will display a new menu." +msgstr "" +"透過方向鍵選擇 Boot Maintenance Menu 然後按下 " +"ENTER。會顯示一個新選單。" -#~ msgid "" -#~ "Thus, three scenarios are generally possible, depending on the system's " -#~ "console firmware and whether or not MILO is available: " -#~ "\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " Because MILO 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 aboot on new " -#~ "installations of GNU/Linux, unless you wish to dual-boot with Windows NT." -#~ msgstr "" -#~ "因此，三種方案都是可行的，但取決與系統控制台韌體以及是否有可用的 " -#~ "MILO：\n" -#~ "SRM -> aboot\n" -#~ "SRM -> MILO\n" -#~ "ARC -> MILO\n" -#~ " 由於 MILO 並沒有實作於目前" -#~ "生產的 Alpha 系統上(從 2000 年二月份開始)。而且也不需要購買 OpenVMS 和 " -#~ "Tru64 Unix 授權，來在老 Alpha 上裝上 SRM 韌體。除非您想採用 Windows NT 並" -#~ "且進行雙開機，我們建議在新的機器上使用 SRM 和 aboot 安" -#~ "裝 Linux。" +#. Tag: para +#: boot-installer.xml:1268 +#, no-c-format +msgid "" +"Select Boot From a File from the menu with the arrow keys " +"and press ENTER. This will display a list of devices " +"probed by the firmware. You should see two menu lines containing either the " +"label Debian Inst [Acpi ... or Removable Media " +"Boot. If you examine the rest of the menu line, you will notice " +"that the device and controller information should be the same." +msgstr "" +"透過方向鍵選擇 Boot From a File，然後按下 ENTER。將顯示韌體檢測到的設備列表。您會看到兩個選單行，它們包括 " +"Debian Inst [Acpi ... 或 Removable Media Boot標籤。如果您檢查選單行其他部分，會看到對應的設備和控制器資訊。" + +#. Tag: para +#: boot-installer.xml:1279 +#, 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 ENTER. If you " +"choose Removable Media Boot the machine will immediately " +"start the boot load sequence. If you choose Debian Inst [Acpi ... instead, it will display a directory listing of the bootable " +"portion of the CD, requiring you to proceed to the next (additional) step." +msgstr "" +"您可選擇指向 CD/DVD 光碟機的項目。透過方向鍵選擇並按下 ENTER。如果您選擇 Removable Media Boot 機器將進入啟動步" +"驟。如果您選擇 Debian Inst [Acpi ...，它會顯示一個可啟動的" +"光碟目錄列表，要求您進行 (額外的) 下一步。" + +#. Tag: para +#: boot-installer.xml:1290 +#, no-c-format +msgid "" +"You will only need this step if you chose Debian Inst [Acpi .... The directory listing will also show [Treat like " +"Removable Media Boot] on the next to the last line. Select this " +"line with the arrow keys and press ENTER. This will start " +"the boot load sequence." +msgstr "" +"您只在選擇 Debian Inst [Acpi ... 時需要這個。目錄列表還會" +"顯示 [Treat like Removable Media Boot] 至最後一行。用方向" +"鍵選擇，並按下 ENTER。這將進入啟動步驟。" -#~ msgid "" -#~ "The majority of AlphaServers and all current server and workstation " -#~ "products contain both SRM and AlphaBIOS in their firmware. For " -#~ "half-flash 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 arc command). " -#~ "For the reasons mentioned above, we recommend switching to SRM before " -#~ "installing &debian;." -#~ msgstr "" -#~ "大部分 AlphaServers 以及目前所有的伺服器以及工作站產品韌體中都同時含有 " -#~ "SRM 和 AlphaBIOS 。對於具有不同試用主機板的 half-flash 機器" -#~ "來說。可以透過重寫韌體切換到另外一個版本。一旦 SRM 安裝完畢，從軟碟上運行 " -#~ "ARC/AlphaBIOS 也是可能的 (使用 arc)。基於上述理由，我們" -#~ "建議在安裝 &debian; 之前切換至 SRM。" +#. Tag: para +#: boot-installer.xml:1302 +#, 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 "" +"這些步驟啟動的 Debian boot-loader 會顯示一個選單頁以選擇啟動核心和選項。進入" +"選擇啟動核心和選項。" + +#. Tag: title +#: boot-installer.xml:1312 +#, no-c-format +msgid "Option 2: Booting from the EFI Shell" +msgstr "選項 2: 從 EFI Shell 啟動" + +#. Tag: para +#: boot-installer.xml:1313 +#, 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 " +"EFI Shell [Built-in]. Boot the Debian Installer CD with " +"the following steps:" +msgstr "" +"某些情況下，選項 1 無法成功，重新啟動機器然後在 EFI Boot Manager 畫面出現的時" +"候會有一個選項稱為 EFI Shell [Built-in]。 可以透過如下步驟" +"來啟動 Debian 安裝程式：" -#~ msgid "" -#~ "As on other architectures, you should install the newest available " -#~ "revision of the firmware Except on Jensen, where Linux " -#~ "is not supported on firmware versions newer than 1.7 — see for more information. before installing &debian;. For Alpha, firmware updates can be " -#~ "obtained from Alpha Firmware Updates." -#~ msgstr "" -#~ "和其他的架構一樣，您也應該在安裝 &debian; 之前安裝最新的韌體版本。但 " -#~ " 不包括 Jensen 1.7 以上的韌體版本，其不支援 Linux — " -#~ "請參閱 以取得更多的資訊。 。對於 Alpha 來說，韌體升級可以從 Alpha Firmware Updates 取得。" +#. Tag: para +#: boot-installer.xml:1324 +#, 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 "" +"把光碟放入光碟機並重新開機。系統初始化之後韌體將會顯示 EFI Boot Manager 的主" +"頁和選單。" -# index.docbook:274, index.docbook:780, index.docbook:1320, index.docbook:1813, index.docbook:1896, index.docbook:2236, index.docbook:2332 -#~ msgid "Booting with TFTP" -#~ msgstr "用 TFTP 開機" +#. Tag: para +#: boot-installer.xml:1330 +#, no-c-format +msgid "" +"Select EFI Shell from the menu with the arrow keys and " +"press ENTER. 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 fsn:. All other " +"recognized partitions will be named blkn:. If you inserted the CD just before entering the " +"shell, this may take a few extra seconds as it initializes the CD drive." +msgstr "" +"選擇 EFI Shell 然後按下 ENTER。EFI " +"Shell 將掃瞄所有的可開機設備，並且在顯示其指令提示符號前在控制台列出它們。被" +"辨認出去有可開機分割區的設備將以 fsn: 格式顯示。所有其他辨認出的分割區，將被命名為 " +"blkn:。如果您在進入介殼之前就" +"插入光碟，這將花費一些時間以初始化光碟機。" + +#. Tag: para +#: boot-installer.xml:1344 +#, no-c-format +msgid "" +"Examine the output from the shell looking for the CDROM drive. It is most " +"likely the fs0: device although other devices with " +"bootable partitions will also show up as fsn." +msgstr "" +"在檢查光碟機期間請查看介殼的輸出顯示。一般來說是 fs0: 其" +"他具有可開機分割區的設備上也會顯示成 fsn。" -#, fuzzy -#~ msgid "" -#~ "In SRM, Ethernet interfaces are named with the ewa " -#~ "prefix, and will be listed in the output of the show dev command, like this (edited slightly): " -#~ "\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" -#~ " You first need to set the boot protocol: " -#~ "\n" -#~ ">>> set ewa0_protocols bootp\n" -#~ " Then check the medium type is correct: " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " You can get a listing of valid modes with " -#~ ">>>set ewa0_mode." -#~ msgstr "" -#~ "在 SRM 上，以太網路介面名稱帶有 ewa 前綴，並可以用 " -#~ "show dev 命令列出，類似如下 (可能有一點不同)：" -#~ "\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" -#~ " 您首先需要設定開機協定： " -#~ "\n" -#~ ">>> set ewa0_protocol bootp\n" -#~ " 然後檢查媒介類型是否正確： " -#~ "\n" -#~ ">>> set ewa0_mode mode\n" -#~ " 您檢閱有效模式的列表 >>>" -#~ "set ewa0_mode。" +#. Tag: para +#: boot-installer.xml:1351 +#, no-c-format +msgid "" +"Enter fsn: and press " +"ENTER to select that device where n is the partition number for the CDROM. The shell will now " +"display the partition number as its prompt." +msgstr "" +"進入 fsn: 然後按下 " +"ENTER 來選擇設備。這裡 n 是光碟" +"的分割區號。介殼將在提示符號下顯示分割區號。" -#~ msgid "" -#~ "Then, to boot from the first Ethernet interface, you would type: " -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " This will boot using the default kernel " -#~ "parameters as included in the netboot image." -#~ msgstr "" -#~ "接下來，如果從第一個以太網路介面開機，您需要輸入：" -#~ "\n" -#~ ">>> boot ewa0 -flags \"\"\n" -#~ " 這會把 netboot 映像啟動，並使用預設的核心參" -#~ "數。" +#. Tag: para +#: boot-installer.xml:1358 +#, no-c-format +msgid "" +"Enter elilo and press ENTER. This will " +"start the boot load sequence." +msgstr "" +"進入 elilo 並按下 ENTER。這將進入啟動步" +"驟。" -#~ msgid "" -#~ "If you wish to use a serial console, you must pass " -#~ "the console= parameter to the kernel. This can be " -#~ "done using the -flags argument to the SRM " -#~ "boot command. The serial ports are named the same " -#~ "as their corresponding files in /dev. 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 " -#~ "ewa0 and use a console on the first serial port, " -#~ "you would type:" -#~ msgstr "" -#~ "如果希望使用一個序列控制台，您必須傳遞 " -#~ "console= 參數給核心。這個工作可以使用SRM " -#~ "boot 指令加上 -flags 參數來" -#~ "完成。序列埠編號的命名和它們在目錄 /dev 中相同。另" -#~ "外，如有指定額外的核心參數，那麼連預設值也必須指定給 &d-i; 映像。例如，若" -#~ "需要從 ewa0 開機，並且在第一個序列埠使用控制台，您" -#~ "得輸入：" +#. Tag: para +#: boot-installer.xml:1365 +#, 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 fsn:elilo command at the shell prompt. Proceed to selecting the boot kernel " +"and options." +msgstr "" +"與選項 1 相同，這些步驟也會啟動 Debian boot-loader，顯示一個選單頁供選擇啟動" +"核心和參數。您可在介殼提示符號下輸入 fsn:" +"elilo簡短指令。進入選擇啟動核心和選項。" + +#. Tag: title +#: boot-installer.xml:1379 +#, no-c-format +msgid "Installing using a Serial Console" +msgstr "使用序列埠控制台安裝" + +#. Tag: para +#: boot-installer.xml:1381 +#, 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 [BAUD baud " +"serial console], where BAUD is the speed of your " +"serial console. Menu items for the most typical baud rate settings on the " +"ttyS0 device are preconfigured." +msgstr "" +"您可選擇使用顯示器與鍵盤或者序列埠連接來進行安裝。要使用顯示器/鍵盤配置，選擇" +"包含 [VGA console] 的選項。要透過序列埠連接，選擇包含 [BAUD baud serial console] 的選項，其中 BAUD 是序列連接速度。選單項裡有大多數常見鮑率的 ttyS0 設備都有預設。" + +#. Tag: para +#: boot-installer.xml:1392 +#, 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 baud at the EFI " +"shell." +msgstr "" +"大多時候，您會讓安裝程式使用與連接 EFI 控制台相同的鮑率。如果您不知如何設定，" +"可以在 EFI shell 透過 baud 指令取得。" -#~ msgid "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" -#~ msgstr "" -#~ ">>> boot ewa0 -flags "root=/dev/ram ramdisk_size=16384 " -#~ "console=ttyS0"" +#. Tag: para +#: boot-installer.xml:1399 +#, 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 console=ttyS1,57600n8 into " +"the Boot: text window." +msgstr "" +"如果沒有序列配置的選項或者您要使用的鮑率，可以覆蓋某個選單項裡面的既有鮑率。" +"例如，使用 57600 鮑率覆蓋 ttyS1 設備，輸入 console=ttyS1,57600n8 到 Boot: 文字視窗。" -#~ msgid "Booting from CD-ROM with the SRM Console" -#~ msgstr "透過 SRM 控制台來從光碟開機" - -#~ msgid "" -#~ "Type \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " where xxxx is your " -#~ "CD-ROM drive in SRM notation." -#~ msgstr "" -#~ "輸入 \n" -#~ ">>> boot xxxx -flags 0\n" -#~ " 上一行 xxxx 是光碟" -#~ "機在 SRM 裡的提示號。" - -#~ msgid "Booting from CD-ROM with the ARC or AlphaBIOS Console" -#~ msgstr "透過 ARC 或者 AlphaBIOS 控制台來從光碟啟動" - -#~ msgid "" -#~ "To boot a CD-ROM from the ARC console, find your sub-architecture code " -#~ "name (see ), then enter \\milo" -#~ "\\linload.exe as the boot loader and \\milo" -#~ "\\subarch (where " -#~ "subarch is the proper subarchitecture name) as " -#~ "the OS Path in the `OS Selection Setup' menu. Ruffians make an exception: " -#~ "You need to use \\milo\\ldmilo.exe as boot loader." -#~ msgstr "" -#~ "為了透過 ARC 控制台以光碟開機，找出您的子架構結構代碼名稱 (請參閱 )，然後輸入 \\milo\\linload.exe 作為 boot-loader 並且在 `OS Selection Setup' 選單下選擇 " -#~ "\\milo\\subarch " -#~ "(subarch 是相應的子架構結構名稱) 作為作業系統路" -#~ "徑。Ruffians 則是一個例外：您需要使用 \\milo\\ldmilo.exe 作為 boot-loader 。" - -#~ msgid "Booting from Floppies with the SRM Console" -#~ msgstr "透過 SRM 控制台從軟碟開機" - -#~ msgid "" -#~ "At the SRM prompt (>>>), issue the following " -#~ "command: \n" -#~ ">>> boot dva0 -flags 0\n" -#~ " possibly replacing dva0 " -#~ "with the actual device name. Usually, dva0 is the " -#~ "floppy; type \n" -#~ ">>> show dev\n" -#~ " to see the list of devices (e.g., if you want " -#~ "to boot from a CD). Note that if you are booting via MILO, -" -#~ "flags argument is ignored, so you can just type boot " -#~ "dva0. If everything works OK, you will eventually see the Linux " -#~ "kernel boot." -#~ msgstr "" -#~ "在 SRM 提示符號下 (>>>)，使用如下指令：" -#~ "\n" -#~ ">>> boot dva0 -flags 0\n" -#~ " 可能要以實際的設備名稱來替換 dva0。一般狀況下，dva0 是軟碟﹔輸入 " -#~ "\n" -#~ ">>> show dev\n" -#~ " 來查看設備列表 (例如，如果您想從光碟開機)。注" -#~ "意如果您想透過 MILO 開機，-flags 參數將被忽略，因此您可" -#~ "以只輸入 boot dva0。如果上面步驟正常執行，您最終將看到 " -#~ "Linux 核心啟動。" - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via aboot, use the following command: \n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (typed on one line), substituting, if " -#~ "necessary, the actual SRM boot device name for dva0, " -#~ "the Linux boot device name for fd0, and the desired " -#~ "kernel parameters for arguments." -#~ msgstr "" -#~ "如果您想在透過 aboot 開機的時候指定特定的核心參數，請使" -#~ "用如下指令：\n" -#~ ">>> boot dva0 -file linux.bin.gz -flags \"root=/dev/fd0 " -#~ "load_ramdisk=1 arguments\"\n" -#~ " (以一行輸入)，如果有需要，替換 " -#~ "dva0 的真實 SRM 開機設備名稱，fd0 是 Linux 的開機設備名稱，而 arguments 是需" -#~ "要指定的核心參數。" - -#~ msgid "" -#~ "If you want to specify kernel parameters when booting via MILO, you will have to interrupt bootstrap once you get into MILO. " -#~ "See ." -#~ msgstr "" -#~ "如果您想在透過 MILO 開機時指定核心參數，您必須在進入 " -#~ "MILO 時中斷開機。請參閱 。" - -#~ msgid "Booting from Floppies with the ARC or AlphaBIOS Console" -#~ msgstr "透過 ARC 或者 AlphaBISO 控制台從軟碟開機" - -#~ msgid "" -#~ "In the OS Selection menu, set linload.exe as the boot " -#~ "loader, and milo as the OS Path. Bootstrap using the " -#~ "newly created entry." -#~ msgstr "" -#~ "在作業系統選擇選單內，設定 linload.exe 作為 boot-" -#~ "loader，並且將 milo 作為作業系統參數。然後使用這個最近" -#~ "建立的選項啟動。" - -#~ msgid "Booting with MILO" -#~ msgstr "採用 MILO 開機" - -#~ 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 "" -#~ "開機媒介上的 MILO 會自動進入 Linux 開機過程。如果您要對此有所控制，只需要" -#~ "在 MILO 倒計時時按下空格鍵。" - -#~ msgid "" -#~ "If you want to specify all the bits explicitly (for example, to supply " -#~ "additional parameters), you can use a command like this: " -#~ "\n" -#~ "MILO> boot fd0:linux.bin.gz root=/dev/fd0 load_ramdisk=1