From fe6fbeaa7bb30e6a352b0b3dd8e0c77453ee9ab1 Mon Sep 17 00:00:00 2001 From: Nozomu KURASAWA Date: Sun, 15 May 2011 01:18:36 +0000 Subject: Update POT and Update Japanese translations --- po/ja/boot-installer.po | 864 ++++++++++++++++++++++++------------------ po/ja/hardware.po | 505 ++++++++++++------------ po/ja/install-methods.po | 455 ++++++++++++---------- po/ja/installation-howto.po | 71 ++-- po/ja/preseed.po | 447 ++++++++++++---------- po/ja/using-d-i.po | 698 +++++++++++++++++----------------- po/pot/boot-installer.pot | 687 +++++++++++++++++---------------- po/pot/hardware.pot | 442 ++++++++++----------- po/pot/install-methods.pot | 276 +++++++------- po/pot/installation-howto.pot | 66 ++-- po/pot/preseed.pot | 353 +++++++++-------- po/pot/using-d-i.pot | 692 ++++++++++++++++----------------- 12 files changed, 2939 insertions(+), 2617 deletions(-) (limited to 'po') diff --git a/po/ja/boot-installer.po b/po/ja/boot-installer.po index ce5246b07..bb4120eb0 100644 --- a/po/ja/boot-installer.po +++ b/po/ja/boot-installer.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: 2010-12-29 21:09+0900\n" "Last-Translator: KURASAWA Nozomu \n" "Language-Team: Japanese \n" @@ -61,8 +61,8 @@ msgid "Booting from TFTP" msgstr "TFTP からの起動" #. Tag: para -#: boot-installer.xml:43 boot-installer.xml:653 boot-installer.xml:1192 -#: boot-installer.xml:1683 boot-installer.xml:1792 +#: boot-installer.xml:43 boot-installer.xml:675 boot-installer.xml:1215 +#: boot-installer.xml:1706 boot-installer.xml:1815 #, no-c-format msgid "" "Booting from the network requires that you have a network connection and a " @@ -72,8 +72,8 @@ msgstr "" "(DHCP, RARP, BOOTP) が必要です。" #. Tag: para -#: boot-installer.xml:48 boot-installer.xml:658 boot-installer.xml:1197 -#: boot-installer.xml:1688 boot-installer.xml:1797 +#: boot-installer.xml:48 boot-installer.xml:680 boot-installer.xml:1220 +#: boot-installer.xml:1711 boot-installer.xml:1820 #, no-c-format msgid "" "Older systems such as the 715 might require the use of an RBOOT server " @@ -82,8 +82,8 @@ msgstr "" "715 のような古いシステムは、BOOTP サーバではなく RBOOT サーバが必要です。" #. Tag: para -#: boot-installer.xml:53 boot-installer.xml:663 boot-installer.xml:1202 -#: boot-installer.xml:1693 boot-installer.xml:1802 +#: boot-installer.xml:53 boot-installer.xml:685 boot-installer.xml:1225 +#: boot-installer.xml:1716 boot-installer.xml:1825 #, no-c-format msgid "" "The installation method to support network booting is described in CD-ROM をドライブに入れて再起動し、次の章に進んでください。" #. Tag: para -#: boot-installer.xml:81 boot-installer.xml:351 boot-installer.xml:822 -#: boot-installer.xml:1480 boot-installer.xml:1842 +#: boot-installer.xml:81 boot-installer.xml:351 boot-installer.xml:845 +#: boot-installer.xml:1503 boot-installer.xml:1865 #, no-c-format msgid "" "Note that certain CD drives may require special drivers, and thus be " @@ -132,8 +132,8 @@ msgstr "" "ついて読んでください。" #. Tag: para -#: boot-installer.xml:89 boot-installer.xml:359 boot-installer.xml:830 -#: boot-installer.xml:1488 boot-installer.xml:1850 +#: boot-installer.xml:89 boot-installer.xml:359 boot-installer.xml:853 +#: boot-installer.xml:1511 boot-installer.xml:1873 #, no-c-format msgid "" "Even if you cannot boot from CD-ROM, you can probably install the &debian; " @@ -149,8 +149,8 @@ msgstr "" "ください。" #. Tag: para -#: boot-installer.xml:97 boot-installer.xml:367 boot-installer.xml:838 -#: boot-installer.xml:1496 boot-installer.xml:1858 +#: boot-installer.xml:97 boot-installer.xml:367 boot-installer.xml:861 +#: boot-installer.xml:1519 boot-installer.xml:1881 #, no-c-format msgid "" "If you have problems booting, see ." @@ -500,8 +500,8 @@ msgid "The installer will now start as usual." msgstr "今度は通常のように、インストーラが起動します。" #. Tag: title -#: boot-installer.xml:334 boot-installer.xml:805 boot-installer.xml:1463 -#: boot-installer.xml:1825 +#: boot-installer.xml:334 boot-installer.xml:828 boot-installer.xml:1486 +#: boot-installer.xml:1848 #, no-c-format msgid "Booting from a CD-ROM" msgstr "CD-ROM からの起動" @@ -515,17 +515,34 @@ msgstr "Windows からの起動" #. Tag: para #: boot-installer.xml:442 #, no-c-format +msgid "To start the installer from Windows, you can either" +msgstr "" + +#. Tag: para +#: boot-installer.xml:447 +#, fuzzy, no-c-format +#| msgid "" +#| "To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM " +#| "or USB memory stick installation media as described in and ." msgid "" -"To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or " -"USB memory stick installation media as described in and ." +"obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in " +" and , or" msgstr "" "Windows からインストーラを起動するには、 " "や で説明しているように、まず CD-ROM/DVD-" "ROM や USB メモリの、インストールメディアを入手しなければなりません。" #. Tag: para -#: boot-installer.xml:448 +#: boot-installer.xml:453 +#, no-c-format +msgid "" +"download a standalone Windows executable, which is available as tools/win32-" +"loader/stable/win32-loader.exe on the &debian; mirrors," +msgstr "" + +#. Tag: para +#: boot-installer.xml:461 #, no-c-format msgid "" "If you use an installation CD or DVD, a pre-installation program should be " @@ -540,23 +557,27 @@ msgstr "" "きます。" #. Tag: para -#: boot-installer.xml:456 -#, no-c-format +#: boot-installer.xml:469 +#, fuzzy, no-c-format +#| msgid "" +#| "After the program has been started, a few preliminary questions will be " +#| "asked and the system will be prepared to start the &debian-gnu; installer." msgid "" "After the program has been started, a few preliminary questions will be " -"asked and the system will be prepared to start the &debian-gnu; installer." +"asked and the system will be prepared to reboot into the &debian-gnu; " +"installer." msgstr "" "プログラム起動後は、いくつか予備的な質問がなされた後、&debian-gnu; インストー" "ラを起動する準備が整います。" #. Tag: title -#: boot-installer.xml:465 +#: boot-installer.xml:479 #, no-c-format msgid "Booting from DOS" msgstr "DOS からの起動" #. Tag: para -#: boot-installer.xml:466 +#: boot-installer.xml:480 #, no-c-format msgid "" "Boot into DOS (not Windows). To do this, you can for instance boot from a " @@ -566,7 +587,7 @@ msgstr "" "スクから起動します。" #. Tag: para -#: boot-installer.xml:471 +#: boot-installer.xml:485 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-" @@ -584,7 +605,7 @@ msgstr "" "ブを変更します。" #. Tag: para -#: boot-installer.xml:481 +#: boot-installer.xml:495 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., " @@ -606,7 +627,7 @@ msgstr "" "ください。カーネルが読み込まれインストーラシステムが起動します。" #. Tag: title -#: boot-installer.xml:499 +#: boot-installer.xml:513 #, no-c-format msgid "" "Booting from Linux Using LILO or GRUB" @@ -614,7 +635,7 @@ msgstr "" "LILO や GRUB を用いた Linux からの起動" #. Tag: para -#: boot-installer.xml:502 +#: boot-installer.xml:516 #, no-c-format msgid "" "To boot the installer from hard disk, you must first download and place the " @@ -625,7 +646,7 @@ msgstr "" "なりません。" #. Tag: para -#: boot-installer.xml:507 +#: boot-installer.xml:521 #, no-c-format msgid "" "If you intend to use the hard drive only for booting and then download " @@ -643,7 +664,7 @@ msgstr "" "できます。(注意して行ってください)" #. Tag: para -#: boot-installer.xml:517 +#: boot-installer.xml:531 #, no-c-format msgid "" "Alternatively, if you intend to keep an existing partition on the hard drive " @@ -661,7 +682,7 @@ msgstr "" "ンストールできます。" #. Tag: para -#: boot-installer.xml:526 +#: boot-installer.xml:540 #, no-c-format msgid "" "For LILO, you will need to configure two essential things " @@ -679,7 +700,7 @@ msgstr "" "itemizedlist> /etc/lilo.conf の例を示します。" #. Tag: screen -#: boot-installer.xml:547 +#: boot-installer.xml:561 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -691,7 +712,7 @@ msgstr "" " initrd=/boot/newinstall/initrd.gz" #. Tag: para -#: boot-installer.xml:547 +#: boot-installer.xml:561 #, no-c-format msgid "" "For more details, refer to the initrdGRUB is quite similar. Locate your " +#| "menu.lst in the /boot/grub/ " +#| "directory (or sometimes /boot/boot/grub/) and add an " +#| "entry for the installer, for example (assuming /boot " +#| "is on the first partition of the first disk in the system):" msgid "" -"The procedure for GRUB is quite similar. Locate your " +"The procedure for GRUB1 is quite similar. Locate your " "menu.lst in the /boot/grub/ " "directory (or sometimes /boot/boot/grub/) and add an " "entry for the installer, for example (assuming /boot is " @@ -723,7 +750,7 @@ msgstr "" "ティションにあると仮定します)。" #. Tag: screen -#: boot-installer.xml:564 +#: boot-installer.xml:578 #, no-c-format msgid "" "title New Install\n" @@ -737,7 +764,49 @@ msgstr "" "initrd /boot/newinstall/initrd.gz" #. Tag: para -#: boot-installer.xml:566 +#: boot-installer.xml:580 +#, fuzzy, no-c-format +#| msgid "" +#| "The procedure for GRUB is quite similar. Locate your " +#| "menu.lst in the /boot/grub/ " +#| "directory (or sometimes /boot/boot/grub/) and add an " +#| "entry for the installer, for example (assuming /boot " +#| "is on the first partition of the first disk in the system):" +msgid "" +"The procedure for GRUB2 is very similar. The file is " +"named grub.cfg instead of menu.lst. An entry for the installer would be for instance for example:" +msgstr "" +"GRUB での手順もよく似ています。/boot/grub/ ディレクトリ (時には /boot/boot/grub/ ディレク" +"トリ) に、menu.lst を配置して、例えばインストーラ用に以" +"下の行を追加してください (/boot が第一ディスクの第一パー" +"ティションにあると仮定します)。" + +#. Tag: screen +#: boot-installer.xml:586 +#, fuzzy, no-c-format +#| msgid "" +#| "title New Install\n" +#| "root (hd0,0)\n" +#| "kernel /boot/newinstall/vmlinuz\n" +#| "initrd /boot/newinstall/initrd.gz" +msgid "" +"menuentry 'New Install' {\n" +"insmod part_msdos\n" +"insmod ext2\n" +"set root='(hd0,msdos1)'\n" +"linux /boot/newinstall/vmlinuz\n" +"initrd /boot/newinstall/initrd.gz\n" +"}" +msgstr "" +"title New Install\n" +"root (hd0,0)\n" +"kernel /boot/newinstall/vmlinuz\n" +"initrd /boot/newinstall/initrd.gz" + +#. Tag: para +#: boot-installer.xml:588 #, no-c-format msgid "" "From here on, there should be no difference between GRUB " @@ -747,13 +816,13 @@ msgstr "" "ん。" #. Tag: title -#: boot-installer.xml:575 +#: boot-installer.xml:597 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "USB メモリからの起動" #. Tag: para -#: boot-installer.xml:576 +#: boot-installer.xml:598 #, no-c-format msgid "" "Let's assume you have prepared everything from と入力します。" #. Tag: para -#: boot-installer.xml:613 +#: boot-installer.xml:635 #, no-c-format msgid "" "Note that on some machines, Control Altboot: というプロンプトが表示されます。" #. Tag: para -#: boot-installer.xml:628 +#: boot-installer.xml:650 #, no-c-format msgid "" "Once you press &enterkey;, you should see the message " @@ -857,7 +926,7 @@ msgstr "" "\"kernel-msgs\"/> で説明します。" #. Tag: para -#: boot-installer.xml:637 +#: boot-installer.xml:659 #, no-c-format msgid "" "After booting from the boot floppy, the root floppy is requested. Insert the " @@ -871,26 +940,26 @@ msgstr "" "起動します。" #. Tag: title -#: boot-installer.xml:647 boot-installer.xml:1174 boot-installer.xml:1315 -#: boot-installer.xml:1369 boot-installer.xml:1677 boot-installer.xml:1786 +#: boot-installer.xml:669 boot-installer.xml:1197 boot-installer.xml:1338 +#: boot-installer.xml:1392 boot-installer.xml:1700 boot-installer.xml:1809 #, no-c-format msgid "Booting with TFTP" msgstr "TFTP での起動" #. Tag: para -#: boot-installer.xml:671 +#: boot-installer.xml:693 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "i386 での TFTP ブートはいろいろな方法があります。" #. Tag: title -#: boot-installer.xml:677 +#: boot-installer.xml:699 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "PXE をサポートする NIC・マザーボード" #. Tag: para -#: boot-installer.xml:678 +#: boot-installer.xml:700 #, no-c-format msgid "" "It could be that your Network Interface Card or Motherboard provides PXE " @@ -904,13 +973,13 @@ msgstr "" "BIOS を設定することができます。" #. Tag: title -#: boot-installer.xml:689 +#: boot-installer.xml:711 #, no-c-format msgid "NIC with Network BootROM" msgstr "ネットワーク BootROM がある NIC" #. Tag: para -#: boot-installer.xml:690 +#: boot-installer.xml:712 #, no-c-format msgid "" "It could be that your Network Interface Card provides TFTP boot " @@ -920,7 +989,7 @@ msgstr "" "せん。" #. Tag: para -#: boot-installer.xml:695 +#: boot-installer.xml:717 #, no-c-format msgid "" "Let us (&email-debian-boot-list;) know how did you manage it. " @@ -930,13 +999,13 @@ msgstr "" "ださい。この文書に参加をお願いします。" #. Tag: title -#: boot-installer.xml:703 +#: boot-installer.xml:725 #, no-c-format msgid "Etherboot" msgstr "Etherboot" #. Tag: para -#: boot-installer.xml:704 +#: boot-installer.xml:726 #, no-c-format msgid "" "The etherboot project " @@ -946,13 +1015,13 @@ msgstr "" "TFTP ブートを行うブートディスケットとブート ROM を提供しています。" #. Tag: title -#: boot-installer.xml:714 +#: boot-installer.xml:736 #, no-c-format msgid "The Boot Screen" msgstr "ブート画面" #. Tag: para -#: boot-installer.xml:715 +#: boot-installer.xml:737 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical " @@ -982,12 +1051,18 @@ msgstr "" "Graphical install が有効でない場合があります。" #. Tag: para -#: boot-installer.xml:725 -#, no-c-format +#: boot-installer.xml:747 +#, fuzzy, no-c-format +#| msgid "" +#| "For a normal installation, select either the Install or " +#| "the Graphical install entry — using either the arrow " +#| "keys on your keyboard or by typing the first (highlighted) letter — " +#| "and press &enterkey; to boot the installer." msgid "" "For a normal installation, select either the Install or the " "Graphical install entry — using either the arrow keys " -"on your keyboard or by typing the first (highlighted) letter — and " +"on your keyboard or by typing the first (highlighted) letter, the " +"Install entry is already selected by default — and " "press &enterkey; to boot the installer." msgstr "" "通常のインストールでは、Install か Graphical installAdvanced options entry gives access to a second menu that " @@ -1008,7 +1083,7 @@ msgstr "" "セスできます。" #. Tag: para -#: boot-installer.xml:738 +#: boot-installer.xml:761 #, no-c-format msgid "" "If you wish or need to add any boot parameters for either the installer or " @@ -1026,7 +1101,7 @@ msgstr "" "ニューに戻り、行った変更を取り消します。" #. Tag: para -#: boot-installer.xml:747 +#: boot-installer.xml:770 #, no-c-format msgid "" "Choosing the Help entry will result in the first help screen " @@ -1061,7 +1136,7 @@ msgstr "" "install fb=false)。" #. Tag: para -#: boot-installer.xml:766 +#: boot-installer.xml:789 #, no-c-format msgid "" "The keyboard is assumed to have a default American English layout at this " @@ -1079,7 +1154,7 @@ msgstr "" "す。" #. Tag: para -#: boot-installer.xml:776 +#: boot-installer.xml:799 #, no-c-format msgid "" "If you are using a system that has the BIOS configured to use serial " @@ -1099,7 +1174,7 @@ msgstr "" "Remote Assistant (IRA) のテキストコンソールを含みます。" #. Tag: para -#: boot-installer.xml:786 +#: boot-installer.xml:809 #, no-c-format msgid "" "To bypass the graphical boot screen you can either blindly press &escapekey; " @@ -1119,13 +1194,13 @@ msgstr "" "fb=false を追加したくなるでしょう。" #. Tag: title -#: boot-installer.xml:846 +#: boot-installer.xml:869 #, no-c-format msgid "CD Contents" msgstr "CD の内容" #. Tag: para -#: boot-installer.xml:848 +#: boot-installer.xml:871 #, no-c-format msgid "" "There are three basic variations of &debian; Install CDs. The " @@ -1149,7 +1224,7 @@ msgstr "" "をインストールできます。" #. Tag: para -#: boot-installer.xml:864 +#: boot-installer.xml:887 #, no-c-format msgid "" "The IA-64 architecture uses the next generation Extensible Firmware " @@ -1175,7 +1250,7 @@ msgstr "" "を意味します。" #. Tag: para -#: boot-installer.xml:880 +#: boot-installer.xml:903 #, no-c-format msgid "" "The &debian; Installer CD contains a small EFI partition where the " @@ -1191,7 +1266,7 @@ msgstr "" "のファイルは下に記述したように EFI シェルから読むことができます。" #. Tag: para -#: boot-installer.xml:889 +#: boot-installer.xml:912 #, no-c-format msgid "" "Most of the details of how ELILO actually loads and " @@ -1214,7 +1289,7 @@ msgstr "" "確認します。" #. Tag: para -#: boot-installer.xml:901 +#: boot-installer.xml:924 #, no-c-format msgid "" "The EFI Boot Manager is presented as the last step of the firmware " @@ -1237,13 +1312,13 @@ msgstr "" "ださい。" #. Tag: title -#: boot-installer.xml:920 +#: boot-installer.xml:943 #, no-c-format msgid "IMPORTANT" msgstr "重要" #. Tag: para -#: boot-installer.xml:921 +#: boot-installer.xml:944 #, no-c-format msgid "" "The EFI Boot Manager will select a default boot action, typically the first " @@ -1262,13 +1337,13 @@ msgstr "" "ジャに戻ることができます。" #. Tag: title -#: boot-installer.xml:933 +#: boot-installer.xml:956 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "オプション 1: 起動オプションメンテナンスメニューからの起動" #. Tag: para -#: boot-installer.xml:940 +#: boot-installer.xml:963 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " @@ -1279,7 +1354,7 @@ msgstr "" "と、ファームウェアが EFI ブートマネージャの画面やメニューを表示する。" #. Tag: para -#: boot-installer.xml:946 +#: boot-installer.xml:969 #, no-c-format msgid "" "Select Boot Maintenance Menu from the menu with the arrow " @@ -1289,7 +1364,7 @@ msgstr "" "ENTER を押す。ここで新しいメニューを表示する。" #. Tag: para -#: boot-installer.xml:952 +#: boot-installer.xml:975 #, no-c-format msgid "" "Select Boot From a File from the menu with the arrow keys " @@ -1307,7 +1382,7 @@ msgstr "" "に気がつくだろう。" #. Tag: para -#: boot-installer.xml:963 +#: boot-installer.xml:986 #, no-c-format msgid "" "You can choose either of the entries that refer to the CD/DVD drive. Select " @@ -1324,7 +1399,7 @@ msgstr "" "移ることを要求し、CD の起動可能部分のディレクトリ一覧を表示するだろう。" #. Tag: para -#: boot-installer.xml:974 +#: boot-installer.xml:997 #, no-c-format msgid "" "You will only need this step if you chose Debian Inst [Acpi ...ENTER を押すと、ブートロードシーケンスを開始する。" #. Tag: para -#: boot-installer.xml:986 +#: boot-installer.xml:1009 #, no-c-format msgid "" "These steps start the &debian; boot loader which will display a menu page " @@ -1350,13 +1425,13 @@ msgstr "" "ブートローダを起動します。起動カーネルやオプションの選択に移行してください。" #. Tag: title -#: boot-installer.xml:996 +#: boot-installer.xml:1019 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "オプション 2: EFI シェルからの起動" #. Tag: para -#: boot-installer.xml:997 +#: boot-installer.xml:1020 #, no-c-format msgid "" "If, for some reason, option 1 is not successful, reboot the machine and when " @@ -1370,7 +1445,7 @@ msgstr "" "ください。" #. Tag: para -#: boot-installer.xml:1008 +#: boot-installer.xml:1031 #, no-c-format msgid "" "Insert the CD in the DVD/CD drive and reboot the machine. The firmware will " @@ -1381,7 +1456,7 @@ msgstr "" "と、ファームウェアが EFI ブートマネージャの画面やメニューを表示する。" #. Tag: para -#: boot-installer.xml:1014 +#: boot-installer.xml:1037 #, no-c-format msgid "" "Select EFI Shell from the menu with the arrow keys and " @@ -1403,7 +1478,7 @@ msgstr "" "化するのに数秒よけいにかかる可能性がある。" #. Tag: para -#: boot-installer.xml:1028 +#: boot-installer.xml:1051 #, no-c-format msgid "" "Examine the output from the shell looking for the CDROM drive. It is most " @@ -1416,7 +1491,7 @@ msgstr "" "filename> という、起動可能パーティションを持つ他のデバイスとして表される。" #. Tag: para -#: boot-installer.xml:1035 +#: boot-installer.xml:1058 #, no-c-format msgid "" "Enter fsn: and press " @@ -1430,7 +1505,7 @@ msgstr "" "される。" #. Tag: para -#: boot-installer.xml:1042 +#: boot-installer.xml:1065 #, no-c-format msgid "" "Enter elilo and press ENTER. This will " @@ -1440,7 +1515,7 @@ msgstr "" "ブートローダが起動される。" #. Tag: para -#: boot-installer.xml:1049 +#: boot-installer.xml:1072 #, no-c-format msgid "" "As with option 1, these steps start the &debian; boot loader which will " @@ -1455,13 +1530,13 @@ msgstr "" "ます。起動カーネルやオプションの選択に進んでください。" #. Tag: title -#: boot-installer.xml:1063 +#: boot-installer.xml:1086 #, no-c-format msgid "Installing using a Serial Console" msgstr "シリアルコンソールを用いたインストール" #. Tag: para -#: boot-installer.xml:1065 +#: boot-installer.xml:1088 #, no-c-format msgid "" "You may choose to perform an install using a monitor and keyboard or using a " @@ -1482,7 +1557,7 @@ msgstr "" "定されています。" #. Tag: para -#: boot-installer.xml:1076 +#: boot-installer.xml:1099 #, no-c-format msgid "" "In most circumstances, you will want the installer to use the same baud rate " @@ -1495,7 +1570,7 @@ msgstr "" "baud コマンドを使って取得できます。" #. Tag: para -#: boot-installer.xml:1083 +#: boot-installer.xml:1106 #, no-c-format msgid "" "If there is not an option available that is configured for the serial device " @@ -1511,7 +1586,7 @@ msgstr "" "力してください。" #. Tag: para -#: boot-installer.xml:1094 +#: boot-installer.xml:1117 #, no-c-format msgid "" "Most IA-64 boxes ship with a default console setting of 9600 baud. This " @@ -1529,7 +1604,7 @@ msgstr "" "ニューの説明をご覧ください。" #. Tag: para -#: boot-installer.xml:1103 +#: boot-installer.xml:1126 #, no-c-format msgid "" "If you select the wrong console type, you will be able to select the kernel " @@ -1542,13 +1617,13 @@ msgstr "" "める前に、再起動する必要があるでしょう。" #. Tag: title -#: boot-installer.xml:1112 +#: boot-installer.xml:1135 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "起動カーネルやオプションの選択" #. Tag: para -#: boot-installer.xml:1114 +#: boot-installer.xml:1137 #, no-c-format msgid "" "The boot loader will display a form with a menu list and a text window with " @@ -1568,7 +1643,7 @@ msgstr "" "明します。" #. Tag: para -#: boot-installer.xml:1126 +#: boot-installer.xml:1149 #, no-c-format msgid "" "Consult the General help screen for the description " @@ -1590,7 +1665,7 @@ msgstr "" "可能性があります。以下の手順で選択しインストールを開始してください。" #. Tag: para -#: boot-installer.xml:1144 +#: boot-installer.xml:1167 #, no-c-format msgid "" "Select the kernel version and installation mode most appropriate to your " @@ -1599,7 +1674,7 @@ msgstr "" "カーネルのバージョンと目的に対して最も適切なモードを、矢印キーで選択する。" #. Tag: para -#: boot-installer.xml:1149 +#: boot-installer.xml:1172 #, no-c-format msgid "" "Enter any boot parameters by typing at the keyboard. The text will be " @@ -1611,7 +1686,7 @@ msgstr "" "定を行う。" #. Tag: para -#: boot-installer.xml:1156 +#: boot-installer.xml:1179 #, no-c-format msgid "" "Press ENTER. This will load and start the kernel. The " @@ -1622,7 +1697,7 @@ msgstr "" "は &debian; インストーラの第 1 画面に通常の初期化メッセージを表示する。" #. Tag: para -#: boot-installer.xml:1165 boot-installer.xml:1301 +#: boot-installer.xml:1188 boot-installer.xml:1324 #, no-c-format msgid "" "Proceed to the next chapter to continue the installation where you will set " @@ -1632,7 +1707,7 @@ msgstr "" "ンストールを続けるのには、次章に進んでください。" #. Tag: para -#: boot-installer.xml:1176 +#: boot-installer.xml:1199 #, no-c-format msgid "" "Booting an IA-64 system from the network is similar to a CD boot. The only " @@ -1651,7 +1726,7 @@ msgstr "" "トールと同じ手順で、システムのインストールを行うことになります。" #. Tag: para -#: boot-installer.xml:1210 +#: boot-installer.xml:1233 #, no-c-format msgid "" "Network booting an IA-64 system requires two architecture-specific actions. " @@ -1665,13 +1740,13 @@ msgstr "" "ロードができるよう EFI ブートマネージャに定義しなければなりません。" #. Tag: title -#: boot-installer.xml:1221 +#: boot-installer.xml:1244 #, no-c-format msgid "Configuring the Server" msgstr "サーバの設定" #. Tag: para -#: boot-installer.xml:1222 +#: boot-installer.xml:1245 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something " @@ -1695,7 +1770,7 @@ msgstr "" "することが目的であることに注意してください。" #. Tag: para -#: boot-installer.xml:1232 +#: boot-installer.xml:1255 #, no-c-format msgid "" "Extract the netboot.tar.gz file into the directory used " @@ -1711,7 +1786,7 @@ msgstr "" "installer ディレクトリを作成します。" #. Tag: screen -#: boot-installer.xml:1242 +#: boot-installer.xml:1265 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -1729,7 +1804,7 @@ msgstr "" "[...]" #. Tag: para -#: boot-installer.xml:1242 +#: boot-installer.xml:1265 #, no-c-format msgid "" "The netboot.tar.gz contains an elilo.conf パッケージで提供されるドキュメントを参照してください。" #. Tag: title -#: boot-installer.xml:1259 +#: boot-installer.xml:1282 #, no-c-format msgid "Configuring the Client" msgstr "クライアントの設定" #. Tag: para -#: boot-installer.xml:1260 +#: boot-installer.xml:1283 #, no-c-format msgid "" "To configure the client to support TFTP booting, start by booting to EFI and " @@ -1786,7 +1861,7 @@ msgstr "" "いるか、確認した方がいいでしょう。" #. Tag: para -#: boot-installer.xml:1292 +#: boot-installer.xml:1315 #, no-c-format msgid "" "The boot loader will display its prompt after it has downloaded and " @@ -1801,13 +1876,13 @@ msgstr "" "らカーネルの読み込みが完了すれば、&debian; インストーラを起動します。" #. Tag: title -#: boot-installer.xml:1318 boot-installer.xml:1342 +#: boot-installer.xml:1341 boot-installer.xml:1365 #, no-c-format msgid "SGI TFTP Booting" msgstr "SGI の TFTP での起動" #. Tag: para -#: boot-installer.xml:1319 +#: boot-installer.xml:1342 #, no-c-format msgid "" "After entering the command monitor use \n" @@ -1829,13 +1904,13 @@ msgstr "" " とします。" #. Tag: title -#: boot-installer.xml:1339 boot-installer.xml:1406 boot-installer.xml:2007 +#: boot-installer.xml:1362 boot-installer.xml:1429 boot-installer.xml:2041 #, no-c-format msgid "Boot Parameters" msgstr "ブートパラメータ" #. Tag: para -#: boot-installer.xml:1343 +#: boot-installer.xml:1366 #, no-c-format msgid "" "On SGI machines you can append boot parameters to the bootp():bootp(): command you can give the path and " @@ -1863,19 +1938,19 @@ msgstr "" "command> を通して渡せます:" #. Tag: screen -#: boot-installer.xml:1358 +#: boot-installer.xml:1381 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "bootp(): append=\"root=/dev/sda1\"" #. Tag: title -#: boot-installer.xml:1372 boot-installer.xml:1409 +#: boot-installer.xml:1395 boot-installer.xml:1432 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "Cobalt の TFTP での起動" #. Tag: para -#: boot-installer.xml:1373 +#: boot-installer.xml:1396 #, no-c-format msgid "" "Strictly speaking, Cobalt does not use TFTP but NFS to boot. You need to " @@ -1893,7 +1968,7 @@ msgstr "" "す。" #. Tag: para -#: boot-installer.xml:1383 +#: boot-installer.xml:1406 #, no-c-format msgid "" "Via SSH (default): In this case, the installer will configure the network " @@ -1908,7 +1983,7 @@ msgstr "" "トでマシンに接続すると、インストールが始まります。" #. Tag: para -#: boot-installer.xml:1392 +#: boot-installer.xml:1415 #, no-c-format msgid "" "Via serial console: Using a null modem cable, you can connect to the serial " @@ -1919,7 +1994,7 @@ msgstr "" "リアルポートに接続 (115200 bps) し、インストールを実行できます。" #. Tag: para -#: boot-installer.xml:1410 +#: boot-installer.xml:1433 #, no-c-format msgid "" "You cannot pass any boot parameters directly. Instead, you have to edit the " @@ -1931,13 +2006,13 @@ msgstr "" "args に追加する必要があります。" #. Tag: title -#: boot-installer.xml:1425 +#: boot-installer.xml:1448 #, no-c-format msgid "s390 Limitations" msgstr "s390 の制限" #. Tag: para -#: boot-installer.xml:1426 +#: boot-installer.xml:1449 #, no-c-format msgid "" "In order to run the installation system a working network setup and ssh " @@ -1947,7 +2022,7 @@ msgstr "" "ssh セッションが使えることが必要となります。" #. Tag: para -#: boot-installer.xml:1431 +#: boot-installer.xml:1454 #, no-c-format msgid "" "The booting process starts with a network setup that prompts you for several " @@ -1960,13 +2035,13 @@ msgstr "" "にログインします。すると標準のインストールシステムが起動されます。" #. Tag: title -#: boot-installer.xml:1442 +#: boot-installer.xml:1465 #, no-c-format msgid "s390 Boot Parameters" msgstr "s390 ブートパラメータ" #. Tag: para -#: boot-installer.xml:1443 +#: boot-installer.xml:1466 #, no-c-format msgid "" "On S/390 you can append boot parameters in the parm file. This file can " @@ -1978,7 +2053,7 @@ msgstr "" "メージの parmfile.debian で提供しています。" #. Tag: para -#: boot-installer.xml:1503 +#: boot-installer.xml:1526 #, no-c-format msgid "" "Currently, the only &arch-title; subarchitectures that support CD-ROM " @@ -1995,7 +2070,7 @@ msgstr "" "Delete キーを起動時に同時に押せば、CD-ROM から起動できます。" #. Tag: para -#: boot-installer.xml:1512 +#: boot-installer.xml:1535 #, no-c-format msgid "" "OldWorld PowerMacs will not boot a &debian; CD, because OldWorld computers " @@ -2011,7 +2086,7 @@ msgstr "" "ピードライブを使い、必要とされたファイルのために CD を指定してください。" #. Tag: para -#: boot-installer.xml:1521 +#: boot-installer.xml:1544 #, no-c-format msgid "" "If your system doesn't boot directly from CD-ROM, you can still use the CD-" @@ -2028,19 +2103,19 @@ msgstr "" "い。" #. Tag: screen -#: boot-installer.xml:1530 +#: boot-installer.xml:1553 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "0 > boot cd:,\\install\\yaboot" #. Tag: title -#: boot-installer.xml:1536 +#: boot-installer.xml:1559 #, no-c-format msgid "Booting from Hard Disk" msgstr "ハードディスクからの起動" #. Tag: para -#: boot-installer.xml:1542 +#: boot-installer.xml:1565 #, no-c-format msgid "" "Booting from an existing operating system is often a convenient option; for " @@ -2050,7 +2125,7 @@ msgstr "" "のシステムについては、インストールをサポートする唯一の方法です。" #. Tag: para -#: boot-installer.xml:1548 +#: boot-installer.xml:1571 #, no-c-format msgid "" "To boot the installer from hard disk, you will have already completed " @@ -2062,13 +2137,13 @@ msgstr "" "があります。" #. Tag: title -#: boot-installer.xml:1568 +#: boot-installer.xml:1591 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "MacOS からの OldWorld PowerMac の起動" #. Tag: para -#: boot-installer.xml:1569 +#: boot-installer.xml:1592 #, no-c-format msgid "" "If you set up BootX in , you can use it to " @@ -2090,13 +2165,13 @@ msgstr "" "タンをクリックすると、MacOS がシャットダウンして、インストーラが起動します。" #. Tag: title -#: boot-installer.xml:1587 +#: boot-installer.xml:1610 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "OpenFirmware からの NewWorld Mac の起動" #. Tag: para -#: boot-installer.xml:1588 +#: boot-installer.xml:1611 #, no-c-format msgid "" "You will have already placed the vmlinux, " @@ -2142,19 +2217,19 @@ msgstr "" "が開始されるはずです。" #. Tag: title -#: boot-installer.xml:1620 +#: boot-installer.xml:1643 #, no-c-format msgid "Booting from USB memory stick" msgstr "USB メモリからの起動" #. Tag: para -#: boot-installer.xml:1621 +#: boot-installer.xml:1644 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "現在、NewWorld PowerMac は USB からの起動をサポートしています。" #. Tag: para -#: boot-installer.xml:1627 +#: boot-installer.xml:1650 #, no-c-format msgid "" "Make sure you have prepared everything from boot-floppy-hfs.img floppy, place it " @@ -2310,7 +2385,7 @@ msgstr "" "てください。" #. Tag: para -#: boot-installer.xml:1751 +#: boot-installer.xml:1774 #, no-c-format msgid "" "For those not familiar with Macintosh floppy operations: a floppy placed in " @@ -2324,7 +2399,7 @@ msgstr "" "ションをチェックします。" #. Tag: para -#: boot-installer.xml:1758 +#: boot-installer.xml:1781 #, no-c-format msgid "" "After booting, the root.bin floppy is requested. Insert " @@ -2336,13 +2411,13 @@ msgstr "" "れると、インストーラプログラムが自動的に起動します。" #. Tag: title -#: boot-installer.xml:1769 +#: boot-installer.xml:1792 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "PowerPC ブートパラメータ" #. Tag: para -#: boot-installer.xml:1770 +#: boot-installer.xml:1793 #, no-c-format msgid "" "Many older Apple monitors used a 640x480 67Hz mode. If your video appears " @@ -2358,7 +2433,7 @@ msgstr "" "userinput> に変えてください。" #. Tag: para -#: boot-installer.xml:1810 +#: boot-installer.xml:1833 #, no-c-format msgid "" "On machines with OpenBoot, simply enter the boot monitor on the machine " @@ -2378,7 +2453,7 @@ msgstr "" "パラメータを渡せます。" #. Tag: para -#: boot-installer.xml:1865 +#: boot-installer.xml:1888 #, no-c-format msgid "" "Most OpenBoot versions support the boot cdrom command " @@ -2390,13 +2465,13 @@ msgstr "" "システムならセカンダリのマスター) から起動せよ、という命令の別名です。" #. Tag: title -#: boot-installer.xml:1874 +#: boot-installer.xml:1897 #, no-c-format msgid "IDPROM Messages" msgstr "IDPROM メッセージ" #. Tag: para -#: boot-installer.xml:1875 +#: boot-installer.xml:1898 #, no-c-format msgid "" "If you cannot boot because you get messages about a problem with " @@ -2411,25 +2486,37 @@ msgstr "" "\">Sun NVRAM FAQ を見てください。" #. Tag: title -#: boot-installer.xml:1894 +#: boot-installer.xml:1917 #, no-c-format msgid "Accessibility" msgstr "アクセシビリティ" #. Tag: para -#: boot-installer.xml:1895 -#, no-c-format +#: boot-installer.xml:1918 +#, fuzzy, no-c-format +#| msgid "" +#| "Some users may need specific support because of e.g. some visual " +#| "impairment. USB braille displays are " +#| "detected automatically, but most other Most accessibility features have to be " +#| "enabled manually. On machines that support it, the " +#| "boot menu emits a beep when it is ready to receive keystrokes. " +#| "Some boot parameters can then be appended " +#| "to enable accessibility features (see also ). Note that on most architectures the " +#| "boot loader interprets your keyboard as a QWERTY keyboard." msgid "" "Some users may need specific support because of e.g. some visual impairment. " "USB braille displays are detected " -"automatically, but most other Most accessibility features have to be enabled manually. " -"On machines that support it, the boot menu emits a beep " -"when it is ready to receive keystrokes. Some boot parameters can " -"then be appended to enable accessibility " -"features (see also ). Note that on most architectures the boot loader interprets your " -"keyboard as a QWERTY keyboard." +"automatically (not serial displays connected via a serial-to-USB converter), " +"but most other Most accessibility features have to be enabled manually. On machines that support it, the boot menu emits a beep when it is " +"ready to receive keystrokes. Some boot parameters can then be appended to enable accessibility features (see also ). Note that " +"on most architectures the boot loader interprets your keyboard as a QWERTY " +"keyboard." msgstr "" "あるユーザにとっては、目が不自由であるといった理由により、それぞれに見合った" "支援が必要なことがあります。USB 点字ディス" @@ -2443,13 +2530,13 @@ msgstr "" "キーボードとして認識することに注意してください。" #. Tag: title -#: boot-installer.xml:1914 +#: boot-installer.xml:1938 #, no-c-format msgid "USB Braille Displays" msgstr "USB 点字ディスプレイ" #. Tag: para -#: boot-installer.xml:1915 +#: boot-installer.xml:1939 #, no-c-format msgid "" "USB braille displays should be automatically detected. A textual version of " @@ -2470,14 +2557,31 @@ msgstr "" "す。" #. Tag: title -#: boot-installer.xml:1930 +#: boot-installer.xml:1954 #, no-c-format msgid "Serial Braille Displays" msgstr "シリアル接続点字ディスプレイ" #. Tag: para -#: boot-installer.xml:1931 -#, no-c-format +#: boot-installer.xml:1955 +#, fuzzy, no-c-format +#| msgid "" +#| "Serial braille displays cannot safely be automatically detected (since " +#| "that may damage some of them). You thus need to append the " +#| "brltty=driver,port,table boot parameter " +#| "to tell brltty which driver it should use. " +#| "driver should be replaced by the two-letter " +#| "driver code for your terminal (see the driver code list). port should be " +#| "replaced by the name of the serial port the display is connected to, " +#| "ttyS0 is the default. table is the name of the braille table to be used (see the table code list); the English table " +#| "is the default. Note that the table can be changed later by entering the " +#| "preference menu. Documentation on key bindings for braille devices is " +#| "available on the brltty website." msgid "" "Serial braille displays cannot safely be automatically detected (since that " "may damage some of them). You thus need to append the " @@ -2486,15 +2590,16 @@ msgid "" "tell brltty which driver it should use. " "driver should be replaced by the two-letter " "driver code for your terminal (see the driver code list). port should be " +"\">BRLTTY manual). port should be " "replaced by the name of the serial port the display is connected to, " -"ttyS0 is the default. table is the name of the braille table to be used (see the table code list); the English table is " -"the default. Note that the table can be changed later by entering the " -"preference menu. Documentation on key bindings for braille devices is " -"available on the brltty website." +"ttyS0 is the default, ttyUSB0 " +"can be typically used when using a serial-to-USB converter. " +"table is the name of the braille table to be used " +"(see the BRLTTY manual); the " +"English table is the default. Note that the table can be changed later by " +"entering the preference menu. Documentation on key bindings for braille " +"devices is available on the brltty website." msgstr "" "シリアル接続点字ディスプレイは、(ある種のものを破損する可能性があるため) 安全" "に自動検出できません。そのため、ブートパラメータに " @@ -2502,24 +2607,24 @@ msgstr "" "replaceable>,table と追加し、" "brltty にどのドライバを使用するべきか教える必要があり" "ます。driver を、あなたの端末用の 2 文字のドライバ" -"コードに置き換えてください (ドライバ" -"コードリスト 参照)。port は、ディスプレイ" -"を接続するシリアルポート名に置き換えてください。デフォルトは " -"ttyS0 です。table は、使用" -"する点字テーブルの名前に置き換えてください (テーブルコードリスト 参照)。デフォルトは英語になっています。" -"テーブルは、後で設定メニューに入って変更できることに注意してください。点字デ" -"バイスのキーバインドは、brltty のウェブサイト に文書があります。" +"コードに置き換えてください (ドライバコード" +"リスト 参照)。port は、ディスプレイを接続" +"するシリアルポート名に置き換えてください。デフォルトは ttyS0 です。table は、使用する点字テーブルの" +"名前に置き換えてください (テーブル" +"コードリスト 参照)。デフォルトは英語になっています。テーブルは、後で" +"設定メニューに入って変更できることに注意してください。点字デバイスのキーバイ" +"ンドは、brltty のウェブサイト に文書があります。" #. Tag: title -#: boot-installer.xml:1953 +#: boot-installer.xml:1977 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "ハードウェア音声合成" #. Tag: para -#: boot-installer.xml:1954 +#: boot-installer.xml:1978 #, no-c-format msgid "" "Support for hardware speech synthesis devices is available only alongside " @@ -2531,7 +2636,7 @@ msgstr "" "ントリを選択する必要があります。" #. Tag: para -#: boot-installer.xml:1960 +#: boot-installer.xml:1984 #, no-c-format msgid "" "Hardware speech synthesis devices cannot be automatically detected. You thus " @@ -2552,13 +2657,13 @@ msgstr "" "スのサポートをターゲットシステムに自動でインストールします。" #. Tag: title -#: boot-installer.xml:1975 +#: boot-installer.xml:1999 #, no-c-format msgid "Board Devices" msgstr "基板デバイス" #. Tag: para -#: boot-installer.xml:1976 +#: boot-installer.xml:2000 #, no-c-format msgid "" "Some accessibility devices are actual boards that are plugged inside the " @@ -2574,7 +2679,7 @@ msgstr "" "これにより使用できる言語が減ってしまいます。" #. Tag: para -#: boot-installer.xml:1984 +#: boot-installer.xml:2008 #, no-c-format msgid "" "If desired a textual version of the bootloader can be activated before " @@ -2584,13 +2689,13 @@ msgstr "" "h &enterkey; をタイプしてください。" #. Tag: title -#: boot-installer.xml:1992 +#: boot-installer.xml:2016 #, no-c-format msgid "High-Contrast Theme" msgstr "高コントラストテーマ" #. Tag: para -#: boot-installer.xml:1993 +#: boot-installer.xml:2017 #, no-c-format msgid "" "For users with low vision, the installer can use a high-contrast theme that " @@ -2601,8 +2706,22 @@ msgstr "" "を使用できます。これを有効にするには、ブートパラメータに " "theme=dark を追加してください。" +#. Tag: title +#: boot-installer.xml:2026 +#, no-c-format +msgid "Preseeding" +msgstr "" + #. Tag: para -#: boot-installer.xml:2008 +#: boot-installer.xml:2027 +#, no-c-format +msgid "" +"Alternatively, &debian; can be installed completely automatically by using " +"preseeding. This is documented in ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2042 #, no-c-format msgid "" "Boot parameters are Linux kernel parameters which are generally used to make " @@ -2616,7 +2735,7 @@ msgstr "" "あるのです。" #. Tag: para -#: boot-installer.xml:2015 +#: boot-installer.xml:2049 #, no-c-format msgid "" "If this is the first time you're booting the system, try the default boot " @@ -2630,7 +2749,7 @@ msgstr "" "ステムに伝えるためのパラメータを調べ、あとで再起動します。" #. Tag: para -#: boot-installer.xml:2022 +#: boot-installer.xml:2056 #, no-c-format msgid "" "Information on many boot parameters can be found in the \n" @@ -2675,7 +2794,7 @@ msgstr "" "userinput> も mem=64m も 64MB の RAM を意味します。" #. Tag: para -#: boot-installer.xml:2047 +#: boot-installer.xml:2081 #, no-c-format msgid "" "If you are booting with a serial console, generally the kernel will " @@ -2707,7 +2826,7 @@ msgstr "" "vt102 です。 。" #. Tag: para -#: boot-installer.xml:2071 +#: boot-installer.xml:2105 #, no-c-format msgid "" "For &arch-title; the serial devices are ttya or " @@ -2721,13 +2840,13 @@ msgstr "" "を設定しても結構です。" #. Tag: title -#: boot-installer.xml:2082 +#: boot-installer.xml:2116 #, no-c-format msgid "&debian; Installer Parameters" msgstr "&debian; Installer パラメータ" #. Tag: para -#: boot-installer.xml:2083 +#: boot-installer.xml:2117 #, no-c-format msgid "" "The installation system recognizes a few additional boot " @@ -2741,7 +2860,7 @@ msgstr "" "ニックしてしまいます。 をいくつか認識します。" #. Tag: para -#: boot-installer.xml:2096 +#: boot-installer.xml:2130 #, no-c-format msgid "" "A number of parameters have a short form that helps avoid the " @@ -2756,20 +2875,20 @@ msgstr "" "ルの例は、通常、短縮形も使用しています。" #. Tag: term -#: boot-installer.xml:2108 +#: boot-installer.xml:2142 #, no-c-format msgid "debconf/priority (priority)" msgstr "debconf/priority (priority)" #. Tag: para -#: boot-installer.xml:2109 +#: boot-installer.xml:2143 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" "このパラメータには、表示するメッセージのもっとも低い優先度を設定します。" #. Tag: para -#: boot-installer.xml:2113 +#: boot-installer.xml:2147 #, no-c-format msgid "" "The default installation uses priority=high. This " @@ -2783,7 +2902,7 @@ msgstr "" "な優先度に調整します。" #. Tag: para -#: boot-installer.xml:2120 +#: boot-installer.xml:2154 #, no-c-format msgid "" "If you add priority=medium as boot parameter, you " @@ -2802,14 +2921,29 @@ msgstr "" "なメッセージだけを表示し、大騒ぎせずに正しい設定をしようとします。" #. Tag: term -#: boot-installer.xml:2134 +#: boot-installer.xml:2168 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "DEBIAN_FRONTEND" #. Tag: para -#: boot-installer.xml:2135 -#, no-c-format +#: boot-installer.xml:2169 +#, 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 that " +#| "support it, the graphical installer uses the gtk " +#| "frontend." msgid "" "This boot parameter controls the type of user interface used for the " "installer. The current possible parameter settings are: " @@ -2821,9 +2955,11 @@ msgid "" " 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 that support it, the " -"graphical installer uses the gtk frontend." +"console installs. Some specialized types of install media may only offer a " +"limited selection of frontends, but the newt and " +"text frontends are available on most default install " +"media. On architectures that support it, the graphical installer uses the " +"gtk frontend." msgstr "" "このブートパラメータはインストーラで使うユーザインターフェースを制御します。" "現在有効な設定は以下の通りです。 " @@ -2840,13 +2976,13 @@ msgstr "" "用します。" #. Tag: term -#: boot-installer.xml:2164 +#: boot-installer.xml:2200 #, no-c-format msgid "BOOT_DEBUG" msgstr "BOOT_DEBUG" #. Tag: para -#: boot-installer.xml:2165 +#: boot-installer.xml:2201 #, no-c-format msgid "" "Setting this boot parameter to 2 will cause the installer's boot process to " @@ -2859,49 +2995,49 @@ msgstr "" "できます。(シェルを終了すると起動プロセスを継続します)" #. Tag: userinput -#: boot-installer.xml:2174 +#: boot-installer.xml:2210 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "BOOT_DEBUG=0" #. Tag: para -#: boot-installer.xml:2175 +#: boot-installer.xml:2211 #, no-c-format msgid "This is the default." msgstr "デフォルトです。" #. Tag: userinput -#: boot-installer.xml:2179 +#: boot-installer.xml:2215 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "BOOT_DEBUG=1" #. Tag: para -#: boot-installer.xml:2180 +#: boot-installer.xml:2216 #, no-c-format msgid "More verbose than usual." msgstr "通常よりも詳細です。" #. Tag: userinput -#: boot-installer.xml:2184 +#: boot-installer.xml:2220 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "BOOT_DEBUG=2" #. Tag: para -#: boot-installer.xml:2185 +#: boot-installer.xml:2221 #, no-c-format msgid "Lots of debugging information." msgstr "デバッグ情報を大量に表示します。" #. Tag: userinput -#: boot-installer.xml:2189 +#: boot-installer.xml:2225 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "BOOT_DEBUG=3" #. Tag: para -#: boot-installer.xml:2190 +#: boot-installer.xml:2226 #, no-c-format msgid "" "Shells are run at various points in the boot process to allow detailed " @@ -2911,13 +3047,13 @@ msgstr "" "起動を続けるにはシェルから抜けてください。" #. Tag: term -#: boot-installer.xml:2204 +#: boot-installer.xml:2240 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "INSTALL_MEDIA_DEV" #. Tag: para -#: boot-installer.xml:2205 +#: boot-installer.xml:2241 #, no-c-format msgid "" "The value of the parameter is the path to the device to load the &debian; " @@ -2929,7 +3065,7 @@ msgstr "" "す。" #. Tag: para -#: boot-installer.xml:2211 +#: boot-installer.xml:2247 #, no-c-format msgid "" "The boot floppy, which normally scans all floppies it can to find the root " @@ -2939,13 +3075,13 @@ msgstr "" "が、このパラメータで 1 つのデバイスを探すように上書きできます。" #. Tag: term -#: boot-installer.xml:2221 +#: boot-installer.xml:2257 #, no-c-format msgid "lowmem" msgstr "lowmem" #. Tag: para -#: boot-installer.xml:2222 +#: boot-installer.xml:2258 #, no-c-format msgid "" "Can be used to force the installer to a lowmem level higher than the one the " @@ -2957,13 +3093,13 @@ msgstr "" "す。 もご覧ください。" #. Tag: term -#: boot-installer.xml:2232 +#: boot-installer.xml:2268 #, no-c-format msgid "noshell" msgstr "noshell" #. Tag: para -#: boot-installer.xml:2233 +#: boot-installer.xml:2269 #, no-c-format msgid "" "Prevents the installer from offering interactive shells on tty2 and tty3. " @@ -2973,13 +3109,13 @@ msgstr "" "リティが限られている、無人インストールの際に便利です。" #. Tag: term -#: boot-installer.xml:2242 +#: boot-installer.xml:2278 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "debian-installer/framebuffer (fb)" #. Tag: para -#: boot-installer.xml:2243 +#: boot-installer.xml:2279 #, no-c-format msgid "" "Some architectures use the kernel framebuffer to offer installation in a " @@ -2997,13 +3133,13 @@ msgstr "" "の兆候です。" #. Tag: para -#: boot-installer.xml:2252 +#: boot-installer.xml:2288 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "そのような問題が、hppa について報告されています。" #. Tag: para -#: boot-installer.xml:2256 +#: boot-installer.xml:2292 #, no-c-format msgid "" "Because of display problems on some systems, framebuffer support is " @@ -3021,13 +3157,13 @@ msgstr "" "fb=true というパラメータを試してください。" #. Tag: term -#: boot-installer.xml:2270 +#: boot-installer.xml:2306 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "debian-installer/theme (theme)" #. Tag: para -#: boot-installer.xml:2271 +#: boot-installer.xml:2307 #, no-c-format msgid "" "A theme determines how the user interface of the installer looks (colors, " @@ -3043,13 +3179,13 @@ msgstr "" "と指定してテーマを設定してください。" #. Tag: term -#: boot-installer.xml:2283 boot-installer.xml:2516 +#: boot-installer.xml:2319 boot-installer.xml:2552 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "netcfg/disable_dhcp" #. Tag: para -#: boot-installer.xml:2284 +#: boot-installer.xml:2320 #, no-c-format msgid "" "By default, the &d-i; automatically probes for network configuration via " @@ -3062,7 +3198,7 @@ msgstr "" "敗する場合のみ、手動ネットワーク設定を行えます。" #. Tag: para -#: boot-installer.xml:2291 +#: boot-installer.xml:2327 #, no-c-format msgid "" "If you have a DHCP server on your local network, but want to avoid it " @@ -3075,13 +3211,13 @@ msgstr "" "netcfg/disable_dhcp=true パラメータを使用できます。" #. Tag: term -#: boot-installer.xml:2302 +#: boot-installer.xml:2338 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "hw-detect/start_pcmcia" #. Tag: para -#: boot-installer.xml:2303 +#: boot-installer.xml:2339 #, no-c-format msgid "" "Set to false to prevent starting PCMCIA services, if " @@ -3092,13 +3228,13 @@ msgstr "" "ピュータには、そういう行儀悪さがあることが知られています。" #. Tag: term -#: boot-installer.xml:2313 +#: boot-installer.xml:2349 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "disk-detect/dmraid/enable (dmraid)" #. Tag: para -#: boot-installer.xml:2314 +#: boot-installer.xml:2350 #, no-c-format msgid "" "Set to true to enable support for Serial ATA RAID " @@ -3112,13 +3248,13 @@ msgstr "" "\"&url-d-i-wiki;\">&debian; Installer Wiki にあります。" #. Tag: term -#: boot-installer.xml:2325 +#: boot-installer.xml:2361 #, no-c-format msgid "preseed/url (url)" msgstr "preseed/url (url)" #. Tag: para -#: boot-installer.xml:2326 +#: boot-installer.xml:2362 #, no-c-format msgid "" "Specify the url to a preconfiguration file to download and use for " @@ -3129,13 +3265,13 @@ msgstr "" "い。" #. Tag: term -#: boot-installer.xml:2335 +#: boot-installer.xml:2371 #, no-c-format msgid "preseed/file (file)" msgstr "preseed/file (file)" #. Tag: para -#: boot-installer.xml:2336 +#: boot-installer.xml:2372 #, no-c-format msgid "" "Specify the path to a preconfiguration file to load for automating the " @@ -3145,13 +3281,13 @@ msgstr "" " を参照してください。" #. Tag: term -#: boot-installer.xml:2345 +#: boot-installer.xml:2381 #, no-c-format msgid "preseed/interactive" msgstr "preseed/interactive" #. Tag: para -#: boot-installer.xml:2346 +#: boot-installer.xml:2382 #, no-c-format msgid "" "Set to true to display questions even if they have " @@ -3166,13 +3302,13 @@ msgstr "" "す。詳細は、 をご覧ください。" #. Tag: term -#: boot-installer.xml:2358 +#: boot-installer.xml:2394 #, no-c-format msgid "auto-install/enable (auto)" msgstr "auto-install/enable (auto)" #. Tag: para -#: boot-installer.xml:2359 +#: boot-installer.xml:2395 #, no-c-format msgid "" "Delay questions that are normally asked before preseeding is possible until " @@ -3184,13 +3320,13 @@ msgstr "" "auto\"/> をご覧ください。" #. Tag: term -#: boot-installer.xml:2370 +#: boot-installer.xml:2406 #, no-c-format msgid "finish-install/keep-consoles" msgstr "finish-install/keep-consoles" #. Tag: para -#: boot-installer.xml:2371 +#: boot-installer.xml:2407 #, no-c-format msgid "" "During installations from serial or management console, the regular virtual " @@ -3202,13 +3338,13 @@ msgstr "" "れを回避するには true をセットしてください。" #. Tag: term -#: boot-installer.xml:2382 +#: boot-installer.xml:2418 #, no-c-format msgid "cdrom-detect/eject" msgstr "cdrom-detect/eject" #. Tag: para -#: boot-installer.xml:2383 +#: boot-installer.xml:2419 #, no-c-format msgid "" "By default, before rebooting, &d-i; automatically ejects the optical media " @@ -3226,7 +3362,7 @@ msgstr "" "ムライン、キャディタイプのドライブは、自動的にメディアをリロードできません。" #. Tag: para -#: boot-installer.xml:2392 +#: boot-installer.xml:2428 #, no-c-format msgid "" "Set to false to disable automatic ejection, and be " @@ -3238,13 +3374,13 @@ msgstr "" "要があります。" #. Tag: term -#: boot-installer.xml:2403 +#: boot-installer.xml:2439 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "base-installer/install-recommends (recommends)" #. Tag: para -#: boot-installer.xml:2404 +#: boot-installer.xml:2440 #, no-c-format msgid "" "By setting this option to false, the package " @@ -3258,7 +3394,7 @@ msgstr "" "base\"/> をご覧ください。" #. Tag: para -#: boot-installer.xml:2411 +#: boot-installer.xml:2447 #, no-c-format msgid "" "Note that this option allows to have a leaner system, but can also result in " @@ -3273,13 +3409,13 @@ msgstr "" "ンは、経験豊富なユーザにしか有用ではないでしょう。" #. Tag: term -#: boot-installer.xml:2423 +#: boot-installer.xml:2459 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "debian-installer/allow_unauthenticated" #. Tag: para -#: boot-installer.xml:2424 +#: boot-installer.xml:2460 #, no-c-format msgid "" "By default the installer requires that repositories be authenticated using a " @@ -3292,13 +3428,13 @@ msgstr "" "い。警告: 危険です。お勧めしません。" #. Tag: term -#: boot-installer.xml:2435 +#: boot-installer.xml:2471 #, no-c-format msgid "ramdisk_size" msgstr "ramdisk_size" #. Tag: para -#: boot-installer.xml:2436 +#: boot-installer.xml:2472 #, no-c-format msgid "" "This parameter should already be set to a correct value where needed; set it " @@ -3310,13 +3446,13 @@ msgstr "" "い。値は kB で指定してください。" #. Tag: term -#: boot-installer.xml:2446 +#: boot-installer.xml:2482 #, no-c-format msgid "rescue/enable" msgstr "rescue/enable" #. Tag: para -#: boot-installer.xml:2447 +#: boot-installer.xml:2483 #, no-c-format msgid "" "Set to true to enter rescue mode rather than " @@ -3326,13 +3462,13 @@ msgstr "" "userinput> にセットしてください。 をご覧ください。" #. Tag: title -#: boot-installer.xml:2460 +#: boot-installer.xml:2496 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "ブートパラメータで質問に答える" #. Tag: para -#: boot-installer.xml:2461 +#: boot-installer.xml:2497 #, no-c-format msgid "" "With some exceptions, a value can be set at the boot prompt for any question " @@ -3345,25 +3481,25 @@ msgstr "" "bootparms\"/> にあります。特殊な例を以下に示します。" #. Tag: term -#: boot-installer.xml:2473 +#: boot-installer.xml:2509 #, no-c-format msgid "debian-installer/language (language)" msgstr "debian-installer/language (language)" #. Tag: term -#: boot-installer.xml:2474 +#: boot-installer.xml:2510 #, no-c-format msgid "debian-installer/country (country)" msgstr "debian-installer/country (country)" #. Tag: term -#: boot-installer.xml:2475 +#: boot-installer.xml:2511 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "debian-installer/locale (locale)" #. Tag: para -#: boot-installer.xml:2476 +#: boot-installer.xml:2512 #, no-c-format msgid "" "There are two ways to specify the language, country and locale to use for " @@ -3373,7 +3509,7 @@ msgstr "" "ふたつあります。" #. Tag: para -#: boot-installer.xml:2481 +#: boot-installer.xml:2517 #, no-c-format msgid "" "The first and easiest is to pass only the parameter localelanguage " @@ -3408,13 +3544,13 @@ msgstr "" "UTF-8" #. Tag: term -#: boot-installer.xml:2502 +#: boot-installer.xml:2538 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "anna/choose_modules (modules)" #. Tag: para -#: boot-installer.xml:2503 +#: boot-installer.xml:2539 #, no-c-format msgid "" "Can be used to automatically load installer components that are not loaded " @@ -3430,7 +3566,7 @@ msgstr "" "\"pppoe\"/> をご覧ください) が便利です。" #. Tag: para -#: boot-installer.xml:2517 +#: boot-installer.xml:2553 #, no-c-format msgid "" "Set to true if you want to disable DHCP and instead " @@ -3440,13 +3576,13 @@ msgstr "" "userinput> と設定します。" #. Tag: term -#: boot-installer.xml:2526 +#: boot-installer.xml:2562 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "mirror/protocol (protocol)" #. Tag: para -#: boot-installer.xml:2527 +#: boot-installer.xml:2563 #, no-c-format msgid "" "By default the installer will use the http protocol to download files from " @@ -3463,13 +3599,13 @@ msgstr "" "ホスト名を手入力しなければならないことに注意してください。" #. Tag: term -#: boot-installer.xml:2540 +#: boot-installer.xml:2576 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "tasksel:tasksel/first (tasks)" #. Tag: para -#: boot-installer.xml:2541 +#: boot-installer.xml:2577 #, no-c-format msgid "" "Can be used to select tasks that are not available from the interactive task " @@ -3481,13 +3617,13 @@ msgstr "" "ださい。" #. Tag: title -#: boot-installer.xml:2555 +#: boot-installer.xml:2591 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "カーネルモジュールへパラメータを渡す" #. Tag: para -#: boot-installer.xml:2556 +#: boot-installer.xml:2592 #, no-c-format msgid "" "If drivers are compiled into the kernel, you can pass parameters to them as " @@ -3510,7 +3646,7 @@ msgstr "" "ステムに伝播します。" #. Tag: para -#: boot-installer.xml:2569 +#: boot-installer.xml:2605 #, no-c-format msgid "" "Note that it is now quite rare that parameters need to be passed to modules. " @@ -3524,7 +3660,7 @@ msgstr "" "は、未だにパラメータを手で設定しなければなりません。" #. Tag: para -#: boot-installer.xml:2576 +#: boot-installer.xml:2612 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: " @@ -3545,19 +3681,19 @@ msgstr "" "スカードで BNC (coax) を使用し、IRQ 10 を設定する場合は、以下のようにします。" #. Tag: screen -#: boot-installer.xml:2586 +#: boot-installer.xml:2622 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "3c509.xcvr=3 3c509.irq=10" #. Tag: title -#: boot-installer.xml:2592 +#: boot-installer.xml:2628 #, no-c-format msgid "Blacklisting kernel modules" msgstr "カーネルモジュールのブラックリスト化" #. Tag: para -#: boot-installer.xml:2593 +#: boot-installer.xml:2629 #, no-c-format msgid "" "Sometimes it may be necessary to blacklist a module to prevent it from being " @@ -3575,7 +3711,7 @@ msgstr "" "因となります。" #. Tag: para -#: boot-installer.xml:2602 +#: boot-installer.xml:2638 #, no-c-format msgid "" "You can blacklist a module using the following syntax: " @@ -3591,7 +3727,7 @@ msgstr "" "が有効になります。" #. Tag: para -#: boot-installer.xml:2610 +#: boot-installer.xml:2646 #, no-c-format msgid "" "Note that a module may still be loaded by the installation system itself. " @@ -3605,19 +3741,19 @@ msgstr "" "げます。" #. Tag: title -#: boot-installer.xml:2626 +#: boot-installer.xml:2662 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "インストールプロセスのトラブルシューティング" #. Tag: title -#: boot-installer.xml:2631 +#: boot-installer.xml:2667 #, no-c-format msgid "CD-ROM Reliability" msgstr "CD-ROM の信頼性" #. Tag: para -#: boot-installer.xml:2632 +#: boot-installer.xml:2668 #, no-c-format msgid "" "Sometimes, especially with older CD-ROM drives, the installer may fail to " @@ -3631,7 +3767,7 @@ msgstr "" "す。" #. Tag: para -#: boot-installer.xml:2639 +#: boot-installer.xml:2675 #, no-c-format msgid "" "There are many different possible causes for these problems. We can only " @@ -3642,13 +3778,13 @@ msgstr "" "法を提供することしかできません。後はあなた次第です。" #. Tag: para -#: boot-installer.xml:2645 +#: boot-installer.xml:2681 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "まずはじめに試すのは、以下の 2 点です。" #. Tag: para -#: boot-installer.xml:2650 +#: boot-installer.xml:2686 #, no-c-format msgid "" "If the CD-ROM does not boot, check that it was inserted correctly and that " @@ -3658,7 +3794,7 @@ msgstr "" "さい。" #. Tag: para -#: boot-installer.xml:2656 +#: boot-installer.xml:2692 #, no-c-format msgid "" "If the installer fails to recognize a CD-ROM, try just running the option " @@ -3671,7 +3807,7 @@ msgstr "" "ROM ドライブの DMA に関連する問題は、この方法で解決することが知られています。" #. Tag: para -#: boot-installer.xml:2666 +#: boot-installer.xml:2702 #, no-c-format msgid "" "If this does not work, then try the suggestions in the subsections below. " @@ -3683,7 +3819,7 @@ msgstr "" "という用語を用いています。" #. Tag: para -#: boot-installer.xml:2672 +#: boot-installer.xml:2708 #, no-c-format msgid "" "If you cannot get the installation working from CD-ROM, try one of the other " @@ -3693,13 +3829,13 @@ msgstr "" "さい。" #. Tag: title -#: boot-installer.xml:2680 +#: boot-installer.xml:2716 #, no-c-format msgid "Common issues" msgstr "共通の問題" #. Tag: para -#: boot-installer.xml:2683 +#: boot-installer.xml:2719 #, no-c-format msgid "" "Some older CD-ROM drives do not support reading from discs that were burned " @@ -3709,7 +3845,7 @@ msgstr "" "ディスクからの読み込みをサポートしていない物があります。" #. Tag: para -#: boot-installer.xml:2689 +#: boot-installer.xml:2725 #, no-c-format msgid "" "If your system boots correctly from the CD-ROM, it does not necessarily mean " @@ -3721,7 +3857,7 @@ msgstr "" "ポートしているとは限りません。" #. Tag: para -#: boot-installer.xml:2696 +#: boot-installer.xml:2732 #, no-c-format msgid "" "Some older CD-ROM drives do not work correctly if direct memory " @@ -3731,19 +3867,19 @@ msgstr "" "が有効だと、正しく動作しない物もあります。" #. Tag: title -#: boot-installer.xml:2707 +#: boot-installer.xml:2743 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "調査および問題解決の方法" #. Tag: para -#: boot-installer.xml:2708 +#: boot-installer.xml:2744 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "CD-ROM が起動に失敗したら、以下のことを試してください。" #. Tag: para -#: boot-installer.xml:2713 +#: boot-installer.xml:2749 #, no-c-format msgid "" "Check that your BIOS actually supports booting from CD-ROM (older systems " @@ -3754,7 +3890,7 @@ msgstr "" "ください。" #. Tag: para -#: boot-installer.xml:2719 +#: boot-installer.xml:2755 #, no-c-format msgid "" "If you downloaded an iso image, check that the md5sum of that image matches " @@ -3779,7 +3915,7 @@ msgstr "" "み込むのにイメージのサイズを利用します。" #. Tag: screen -#: boot-installer.xml:2732 +#: boot-installer.xml:2768 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -3801,7 +3937,7 @@ msgstr "" "134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s" #. Tag: para -#: boot-installer.xml:2737 +#: boot-installer.xml:2773 #, no-c-format msgid "" "If, after the installer has been booted successfully, the CD-ROM is not " @@ -3821,7 +3957,7 @@ msgstr "" "に切り替えて、シェルを有効にしてください。" #. Tag: para -#: boot-installer.xml:2749 +#: boot-installer.xml:2785 #, no-c-format msgid "" "Switch to VT4 or view the contents of /var/log/syslog " @@ -3833,7 +3969,7 @@ msgstr "" "示してください。その後、dmesg の出力でもチェックできます。" #. Tag: para -#: boot-installer.xml:2756 +#: boot-installer.xml:2792 #, no-c-format msgid "" "Check in the output of dmesg if your CD-ROM drive was " @@ -3863,7 +3999,7 @@ msgstr "" "むのを試せます。" #. Tag: para -#: boot-installer.xml:2770 +#: boot-installer.xml:2806 #, no-c-format msgid "" "Check that there is a device node for your CD-ROM drive under /dev/" @@ -3875,7 +4011,7 @@ msgstr "" "/dev/cdrom にもあるかもしれません。" #. Tag: para -#: boot-installer.xml:2778 +#: boot-installer.xml:2814 #, no-c-format msgid "" "Use the mount command to check if the CD-ROM is already " @@ -3892,7 +4028,7 @@ msgstr "" "チェックしてください。" #. Tag: para -#: boot-installer.xml:2788 +#: boot-installer.xml:2824 #, no-c-format msgid "" "Check if DMA is currently enabled: \n" @@ -3918,7 +4054,7 @@ msgstr "" "クトリで操作してください。" #. Tag: para -#: boot-installer.xml:2803 +#: boot-installer.xml:2839 #, no-c-format msgid "" "If there are any problems during the installation, try checking the " @@ -3931,13 +4067,13 @@ msgstr "" "ションを一般的なテストとして使用できます。" #. Tag: title -#: boot-installer.xml:2818 +#: boot-installer.xml:2854 #, no-c-format msgid "Floppy Disk Reliability" msgstr "フロッピーディスクの信頼性" #. Tag: para -#: boot-installer.xml:2820 +#: boot-installer.xml:2856 #, no-c-format msgid "" "The biggest problem for people using floppy disks to install &debian; seems " @@ -3947,7 +4083,7 @@ msgstr "" "は、フロッピーディスクの信頼性だと思います。" #. Tag: para -#: boot-installer.xml:2825 +#: boot-installer.xml:2861 #, no-c-format msgid "" "The boot floppy is the floppy with the worst problems, because it is read by " @@ -3965,7 +4101,7 @@ msgstr "" "ディスク I/O エラーに関するメッセージが大量に表示されます。" #. Tag: para -#: boot-installer.xml:2834 +#: boot-installer.xml:2870 #, no-c-format msgid "" "If you are having the installation stall at a particular floppy, the first " @@ -3982,7 +4118,7 @@ msgstr "" "ムで書き込んでみると、うまくいくこともあるようです。" #. Tag: para -#: boot-installer.xml:2843 +#: boot-installer.xml:2879 #, no-c-format msgid "" "One user reports he had to write the images to floppy three の説明に従ってブートパラメータを確認してください。" #. Tag: para -#: boot-installer.xml:2873 +#: boot-installer.xml:2909 #, no-c-format msgid "" "Often, problems can be solved by removing add-ons and peripherals, and then " @@ -4049,7 +4185,7 @@ msgstr "" "ド、 Plug&Play デバイスなどは特に問題となりがちです。" #. Tag: para -#: boot-installer.xml:2879 +#: boot-installer.xml:2915 #, no-c-format msgid "" "If you have a large amount of memory installed in your machine, more than " @@ -4062,13 +4198,13 @@ msgstr "" "を使って、カーネルが扱うメモリの量を制限する必要があるかもしれません。" #. Tag: title -#: boot-installer.xml:2890 boot-installer.xml:2992 +#: boot-installer.xml:2926 boot-installer.xml:3028 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "&arch-title; へのインストールに共通の問題" #. Tag: para -#: boot-installer.xml:2891 +#: boot-installer.xml:2927 #, no-c-format msgid "" "There are some common installation problems that can be solved or avoided by " @@ -4078,7 +4214,7 @@ msgstr "" "ラメータで解決したり、確実にバイパスして回避したりできます。" #. Tag: para -#: boot-installer.xml:2896 +#: boot-installer.xml:2932 #, no-c-format msgid "" "Some systems have floppies with inverted DCLs. If you receive " @@ -4091,7 +4227,7 @@ msgstr "" "てください。" #. Tag: para -#: boot-installer.xml:2902 +#: boot-installer.xml:2938 #, no-c-format msgid "" "On some systems, such as the IBM PS/1 or ValuePoint (which have ST-506 disk " @@ -4111,7 +4247,7 @@ msgstr "" "userinput> というパラメータを使ってください。" #. Tag: para -#: boot-installer.xml:2911 +#: boot-installer.xml:2947 #, no-c-format msgid "" "If you have a very old machine, and the kernel hangs after saying " @@ -4125,7 +4261,7 @@ msgstr "" "でしょう。" #. Tag: para -#: boot-installer.xml:2918 +#: boot-installer.xml:2954 #, no-c-format msgid "" "Some systems (especially laptops) that have a native resolution that is not " @@ -4151,7 +4287,7 @@ msgstr "" "パラメータに fb=false を追加してみてください。" #. Tag: para -#: boot-installer.xml:2936 +#: boot-installer.xml:2972 #, no-c-format msgid "" "If your screen begins to show a weird picture while the kernel boots, eg. " @@ -4171,13 +4307,13 @@ msgstr "" "ください。" #. Tag: title -#: boot-installer.xml:2950 +#: boot-installer.xml:2986 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "PCMCIA 設定中のシステムフリーズ" #. Tag: para -#: boot-installer.xml:2951 +#: boot-installer.xml:2987 #, no-c-format msgid "" "Some laptop models produced by Dell are known to crash when PCMCIA device " @@ -4197,7 +4333,7 @@ msgstr "" "外することができます。" #. Tag: para -#: boot-installer.xml:2961 +#: boot-installer.xml:2997 #, no-c-format msgid "" "Alternatively, you can boot the installer in expert mode. You will then be " @@ -4219,13 +4355,13 @@ msgstr "" "あればカンマを省略しなければならないことに注意してください。" #. Tag: title -#: boot-installer.xml:2978 +#: boot-installer.xml:3014 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "USB モジュールロード中のシステムフリーズ" #. Tag: para -#: boot-installer.xml:2979 +#: boot-installer.xml:3015 #, no-c-format msgid "" "The kernel normally tries to install USB modules and the USB keyboard driver " @@ -4243,19 +4379,19 @@ msgstr "" "す。" #. Tag: para -#: boot-installer.xml:2993 +#: boot-installer.xml:3029 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "以下、言及しておくべき、インストール時の一般的な問題があります。" #. Tag: title -#: boot-installer.xml:2999 +#: boot-installer.xml:3035 #, no-c-format msgid "Misdirected video output" msgstr "ビデオ出力先の間違い" #. Tag: para -#: boot-installer.xml:3000 +#: boot-installer.xml:3036 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, " @@ -4281,7 +4417,7 @@ msgstr "" "userinput> をインストーラに与えて起動してください。" #. Tag: para -#: boot-installer.xml:3014 +#: boot-installer.xml:3050 #, no-c-format msgid "" "Note that you may also have to manually add this parameter to the silo " @@ -4295,13 +4431,13 @@ msgstr "" "filename> のビデオドライバを修正してください。" #. Tag: title -#: boot-installer.xml:3025 +#: boot-installer.xml:3061 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "起動に失敗ないし CD-ROM からインストール" #. Tag: para -#: boot-installer.xml:3026 +#: boot-installer.xml:3062 #, no-c-format msgid "" "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if " @@ -4313,20 +4449,20 @@ msgstr "" "システムで報告されています。" #. Tag: para -#: boot-installer.xml:3032 +#: boot-installer.xml:3068 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" "そのようなシステムでは、インストーラをネットから起動するのをお勧めします。" #. Tag: title -#: boot-installer.xml:3041 +#: boot-installer.xml:3077 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "カーネルの起動時メッセージの意味" #. Tag: para -#: boot-installer.xml:3043 +#: boot-installer.xml:3079 #, no-c-format msgid "" "During the boot sequence, you may see many messages in the form " @@ -4364,13 +4500,13 @@ msgstr "" "baking\"/> 参照)。" #. Tag: title -#: boot-installer.xml:3068 +#: boot-installer.xml:3104 #, no-c-format msgid "Reporting Installation Problems" msgstr "インストールで発生した問題の報告" #. Tag: para -#: boot-installer.xml:3069 +#: boot-installer.xml:3105 #, no-c-format msgid "" "If you get through the initial boot phase but cannot complete the install, " @@ -4389,7 +4525,7 @@ msgstr "" "バグ報告を送る際に、バグ報告にこの情報を付けることができます。" #. Tag: para -#: boot-installer.xml:3080 +#: boot-installer.xml:3116 #, no-c-format msgid "" "Other pertinent installation messages may be found in /var/log/ にあるはずです。" #. Tag: title -#: boot-installer.xml:3091 +#: boot-installer.xml:3127 #, no-c-format msgid "Submitting Installation Reports" msgstr "インストールレポートの送信" #. Tag: para -#: boot-installer.xml:3092 +#: boot-installer.xml:3128 #, no-c-format msgid "" "If you still have problems, please submit an installation report. We also " @@ -4420,7 +4556,7 @@ msgstr "" "さんのハードウェア設定情報を手に入れることができます。" #. Tag: para -#: boot-installer.xml:3099 +#: boot-installer.xml:3135 #, no-c-format msgid "" "Note that your installation report will be published in the Debian Bug " @@ -4432,7 +4568,7 @@ msgstr "" "ない e-mail アドレスを使用してください。" #. Tag: para -#: boot-installer.xml:3105 +#: boot-installer.xml:3141 #, no-c-format msgid "" "If you have a working &debian; system, the easiest way to send an " @@ -4451,7 +4587,7 @@ msgstr "" "て、reportbug installation-reports を実行してください。" #. Tag: para -#: boot-installer.xml:3115 +#: boot-installer.xml:3151 #, no-c-format msgid "" "Alternatively you can use this template when filling out installation " diff --git a/po/ja/hardware.po b/po/ja/hardware.po index ce35be624..5bbd45f10 100644 --- a/po/ja/hardware.po +++ b/po/ja/hardware.po @@ -3,8 +3,8 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-10-29 05:56+0000\n" -"PO-Revision-Date: 2011-01-27 07:49+0900\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" +"PO-Revision-Date: 2011-05-15 10:05+0900\n" "Last-Translator: KURASAWA Nozomu \n" "Language-Team: Japanese \n" "Language: ja\n" @@ -517,14 +517,14 @@ msgstr "" "ト の購読も必要かもしれません。" #. Tag: title -#: hardware.xml:239 hardware.xml:275 hardware.xml:381 hardware.xml:400 -#: hardware.xml:483 hardware.xml:541 hardware.xml:594 +#: hardware.xml:239 hardware.xml:275 hardware.xml:382 hardware.xml:401 +#: hardware.xml:484 hardware.xml:542 hardware.xml:595 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "CPU・マザーボード・ビデオのサポート" #. Tag: para -#: hardware.xml:240 hardware.xml:401 +#: hardware.xml:240 hardware.xml:402 #, no-c-format msgid "" "Complete information concerning supported peripherals can be found at CPU" msgstr "CPU" @@ -639,22 +639,30 @@ msgstr "Kirkwood" #. Tag: para #: hardware.xml:331 #, no-c-format +#| msgid "" +#| "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM " +#| "CPU, Ethernet, SATA, USB, and other functionality in one chip. We " +#| "currently support the following Kirkwood based devices: OpenRD (OpenRD-" +#| "Base and OpenRD-Client), SheevaPlug and QNAP Turbo Station (TS-110, TS-119, TS-210, TS-219 and " +#| "TS-219P; the TS-410 and TS-419P are not yet supported)." msgid "" "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM " "CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently " -"support the following Kirkwood based devices: OpenRD (OpenRD-Base and OpenRD-" -"Client), SheevaPlug and " -"QNAP Turbo Station " -"(TS-110, TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not " -"yet supported)." +"support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-" +"Client and OpenRD-Ultimate), SheevaPlug and QNAP " +"Turbo Station (TS-110, TS-112, TS-119, TS-119P+, TS-210, TS-212, " +"TS-219, TS-219P, TS-219P+, TS-410, TS-410U, TS-419P, TS-419P+ and TS-419U)." msgstr "" "Kirkwood は、Marvell 製の System on a Chip (SoC) で、ARM CPU、イーサネット、" "SATA、USB、その他の機能が 1 チップに統合されています。現在以下の Kirkwood " -"ベースデバイスをサポートしています。OpenRD (OpenRD-Base and OpenRD-Client) " -"や SheevaPlug 、QNAP Turbo Station です " -"(TS-110, TS-119, TS-210, TS-219, TS-219P; TS-410 と TS-419P は、まだサポート" -"していません)。" +"ベースデバイスをサポートしています。OpenRD (OpenRD-Base, OpenRD-Client, " +"OpenRD-Ultimate) や SheevaPlug、 QNAP Turbo Station (TS-110, TS-112, TS-119, TS-119P+, TS-210, TS-212, TS-219, TS-219P, " +"TS-219P+, TS-410, TS-410U, TS-419P, TS-419P+, TS-419U) です。" #. Tag: term #: hardware.xml:346 @@ -665,31 +673,42 @@ msgstr "Orion5x" #. Tag: para #: hardware.xml:347 #, no-c-format +#| msgid "" +#| "Orion is a system on a chip (SoC) from Marvell that integrates an ARM " +#| "CPU, Ethernet, SATA, USB, and other functionality in one chip. There are " +#| "many Network Attached Storage (NAS) devices on the market that are based " +#| "on an Orion chip. We currently support the following Orion based devices: " +#| "Buffalo Kurobox, " +#| "HP mv2120, QNAP Turbo Station (TS-109, TS-209 and " +#| "TS-409)." msgid "" "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, " "Ethernet, SATA, USB, and other functionality in one chip. There are many " "Network Attached Storage (NAS) devices on the market that are based on an " "Orion chip. We currently support the following Orion based devices: Buffalo Kurobox, HP mv2120, QNAP Turbo Station (TS-109, TS-209 and TS-409)." +"\"&url-arm-cyrius-dns323;\">D-Link DNS-323, HP mv2120, QNAP Turbo Station (TS-109, TS-209 and TS-409)." msgstr "" "Orion は、Marvell 製の System on a Chip (SoC) で、ARM CPU、イーサネット、" "SATA、USB、その他の機能が 1 チップに統合されています。市場に出回っているたく" "さんのネットワークストレージ (NAS) で Orion チップが採用されています。現在以" "下の Orion ベースデバイスをサポートしています。Buffalo 玄箱, HP mv2120, QNAP Turbo " -"Station (TS-109, TS-209 and TS-409) です。" +"kuroboxpro;\">Buffalo 玄箱, D-" +"Link DNS-323, HP mv2120, QNAP Turbo Station " +"(TS-109, TS-209, TS-409) です。" #. Tag: term -#: hardware.xml:362 +#: hardware.xml:363 #, no-c-format msgid "Versatile" msgstr "Versatile" #. Tag: para -#: hardware.xml:363 +#: hardware.xml:364 #, no-c-format msgid "" "The Versatile platform is emulated by QEMU and is therefore a nice way to " @@ -699,7 +718,7 @@ msgstr "" "ウェアがなくても ARM での &debian; のテストや実行を行う良い方法です。" #. Tag: para -#: hardware.xml:382 +#: hardware.xml:383 #, no-c-format msgid "" "There are two major support &architecture; flavors: PA-" @@ -717,7 +736,7 @@ msgstr "" "ランドも使用できるようになるでしょう。" #. Tag: para -#: hardware.xml:410 +#: hardware.xml:411 #, no-c-format msgid "" "Nearly all x86-based (IA-32) processors still in use in personal computers " @@ -731,7 +750,7 @@ msgstr "" "Intel P4 Xeon といったプロセッサもサポートしています。" #. Tag: para -#: hardware.xml:417 +#: hardware.xml:418 #, no-c-format msgid "" "However, &debian; GNU/Linux &releasename; will not run " @@ -770,7 +789,7 @@ msgstr "" "para> 。" #. Tag: para -#: hardware.xml:450 +#: hardware.xml:451 #, no-c-format msgid "" "If your system has a 64-bit processor from the AMD64 or Intel EM64T " @@ -782,13 +801,13 @@ msgstr "" "amd64 アーキテクチャ用インストーラを使用した方がいいでしょう。" #. Tag: title -#: hardware.xml:459 +#: hardware.xml:460 #, no-c-format msgid "I/O Bus" msgstr "I/O バス" #. Tag: para -#: hardware.xml:460 +#: hardware.xml:461 #, no-c-format msgid "" "The system bus is the part of the motherboard which allows the CPU to " @@ -804,7 +823,7 @@ msgstr "" "のどれかが使われています。" #. Tag: para -#: hardware.xml:484 +#: hardware.xml:485 #, no-c-format msgid "" "&debian; on &arch-title; supports the following platforms: " @@ -838,7 +857,7 @@ msgstr "" "グリストに連絡してください。" #. Tag: para -#: hardware.xml:519 +#: hardware.xml:520 #, no-c-format msgid "" "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and " @@ -852,7 +871,7 @@ msgstr "" "います。" #. Tag: para -#: hardware.xml:525 +#: hardware.xml:526 #, no-c-format msgid "" "Some MIPS machines can be operated in both big and little endian mode. For " @@ -864,7 +883,7 @@ msgstr "" "チャの文書をご覧ください。" #. Tag: para -#: hardware.xml:542 +#: hardware.xml:543 #, no-c-format msgid "" "&debian; on &arch-title; supports the following platforms: " @@ -894,13 +913,13 @@ msgstr "" "ください。" #. Tag: title -#: hardware.xml:570 +#: hardware.xml:571 #, no-c-format msgid "CPU/Machine types" msgstr "CPU/マシンタイプ" #. Tag: para -#: hardware.xml:572 +#: hardware.xml:573 #, no-c-format msgid "" "All MIPS based Cobalt machines are supported with the exception of the Qube " @@ -910,19 +929,19 @@ msgstr "" "す。" #. Tag: title -#: hardware.xml:580 +#: hardware.xml:581 #, no-c-format msgid "Supported console options" msgstr "サポートするコンソールオプション" #. Tag: para -#: hardware.xml:581 +#: hardware.xml:582 #, no-c-format msgid "Cobalt machines use 115200 bps." msgstr "Cobalt マシンは 115200 bps を使用します。" #. Tag: para -#: hardware.xml:595 +#: hardware.xml:596 #, no-c-format msgid "" "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and " @@ -932,13 +951,13 @@ msgstr "" "キテクチャと PreP サブアーキテクチャのみサポートしています。" #. Tag: title -#: hardware.xml:616 +#: hardware.xml:617 #, no-c-format msgid "Kernel Flavours" msgstr "カーネルフレーバー" #. Tag: para -#: hardware.xml:618 +#: hardware.xml:619 #, no-c-format msgid "" "There are two flavours of the powerpc kernel in &debian;, based on the CPU " @@ -948,13 +967,13 @@ msgstr "" "種類あります。" #. Tag: term -#: hardware.xml:625 +#: hardware.xml:626 #, no-c-format msgid "powerpc" msgstr "powerpc" #. Tag: para -#: hardware.xml:626 +#: hardware.xml:627 #, no-c-format msgid "" "Most systems use this kernel flavour, which supports the PowerPC 601, 603, " @@ -967,19 +986,19 @@ msgstr "" "す。" #. Tag: term -#: hardware.xml:636 +#: hardware.xml:637 #, no-c-format msgid "power64" msgstr "power64" #. Tag: para -#: hardware.xml:637 +#: hardware.xml:638 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "power64 カーネルフレーバーは以下の CPU をサポートしています。" #. Tag: para -#: hardware.xml:641 +#: hardware.xml:642 #, no-c-format msgid "" "The POWER3 processor is used in older IBM 64-bit server systems: known " @@ -991,7 +1010,7 @@ msgstr "" "7044-170, 7043-260, 7044-270 です。" #. Tag: para -#: hardware.xml:647 +#: hardware.xml:648 #, no-c-format msgid "" "The POWER4 processor is used in more recent IBM 64-bit server systems: known " @@ -1001,7 +1020,7 @@ msgstr "" "す。よく知られたモデルは、pSeries 615, 630, 650, 655, 670, 690 です。" #. Tag: para -#: hardware.xml:652 +#: hardware.xml:653 #, no-c-format msgid "" "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 " @@ -1011,13 +1030,13 @@ msgstr "" "ベースにしており、このカーネルフレーバーを使用します。" #. Tag: title -#: hardware.xml:686 +#: hardware.xml:687 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "Power Macintosh (pmac) サブアーキテクチャ" #. Tag: para -#: hardware.xml:688 +#: hardware.xml:689 #, no-c-format msgid "" "Apple (and briefly a few other manufacturers — Power Computing, for " @@ -1031,7 +1050,7 @@ msgstr "" "に分類されています。" #. Tag: para -#: hardware.xml:695 +#: hardware.xml:696 #, no-c-format msgid "" "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI " @@ -1045,7 +1064,7 @@ msgstr "" "規則を持つ iMac 以前の PowerPC モデルも OldWorld です。" #. Tag: para -#: hardware.xml:703 +#: hardware.xml:704 #, no-c-format msgid "" "The so called NewWorld PowerMacs are any PowerMacs in translucent colored " @@ -1060,7 +1079,7 @@ msgstr "" "れ、MacOS 用に ROM in RAM システムを使用しています。" #. Tag: para -#: hardware.xml:711 +#: hardware.xml:712 #, no-c-format msgid "" "Specifications for Apple hardware are available at AppleSpec Legacy から入手できます。" #. Tag: entry -#: hardware.xml:727 hardware.xml:862 hardware.xml:906 hardware.xml:935 +#: hardware.xml:728 hardware.xml:863 hardware.xml:907 hardware.xml:936 #, no-c-format msgid "Model Name/Number" msgstr "モデル名/型番" #. Tag: entry -#: hardware.xml:728 +#: hardware.xml:729 #, no-c-format msgid "Generation" msgstr "世代" #. Tag: entry -#: hardware.xml:734 +#: hardware.xml:735 #, no-c-format msgid "Apple" msgstr "Apple" #. Tag: entry -#: hardware.xml:735 +#: hardware.xml:736 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "iMac ボンダイブルー、5 色、スロットローディング" #. Tag: entry -#: hardware.xml:736 hardware.xml:739 hardware.xml:742 hardware.xml:745 -#: hardware.xml:748 hardware.xml:751 hardware.xml:754 hardware.xml:757 -#: hardware.xml:760 hardware.xml:763 hardware.xml:766 hardware.xml:769 -#: hardware.xml:772 hardware.xml:775 hardware.xml:778 hardware.xml:781 +#: hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 +#: hardware.xml:749 hardware.xml:752 hardware.xml:755 hardware.xml:758 +#: hardware.xml:761 hardware.xml:764 hardware.xml:767 hardware.xml:770 +#: hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 #, no-c-format msgid "NewWorld" msgstr "NewWorld" #. Tag: entry -#: hardware.xml:738 +#: hardware.xml:739 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "iMac 2000 年夏モデル、2001 年年初モデル" #. Tag: entry -#: hardware.xml:741 +#: hardware.xml:742 #, no-c-format msgid "iMac G5" msgstr "iMac G5" #. Tag: entry -#: hardware.xml:744 +#: hardware.xml:745 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "iBook, iBook SE, iBook Dual USB" #. Tag: entry -#: hardware.xml:747 +#: hardware.xml:748 #, no-c-format msgid "iBook2" msgstr "iBook2" #. Tag: entry -#: hardware.xml:750 +#: hardware.xml:751 #, no-c-format msgid "iBook G4" msgstr "iBook G4" #. Tag: entry -#: hardware.xml:753 +#: hardware.xml:754 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "Power Macintosh Blue and White (B&W) G3" #. Tag: entry -#: hardware.xml:756 +#: hardware.xml:757 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "Power Macintosh G4 PCI, AGP, Cube" #. Tag: entry -#: hardware.xml:759 +#: hardware.xml:760 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "Power Macintosh G4 Gigabit Ethernet" #. Tag: entry -#: hardware.xml:762 +#: hardware.xml:763 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "Power Macintosh G4 Digital Audio, Quicksilver" #. Tag: entry -#: hardware.xml:765 +#: hardware.xml:766 #, no-c-format msgid "Power Macintosh G5" msgstr "Power Macintosh G5" #. Tag: entry -#: hardware.xml:768 +#: hardware.xml:769 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "PowerBook G3 FireWire Pismo (2000)" #. Tag: entry -#: hardware.xml:771 +#: hardware.xml:772 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "PowerBook G3 Lombard (1999)" #. Tag: entry -#: hardware.xml:774 +#: hardware.xml:775 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "PowerBook G4 Titanium" #. Tag: entry -#: hardware.xml:777 +#: hardware.xml:778 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "PowerBook G4 Aluminum" #. Tag: entry -#: hardware.xml:780 +#: hardware.xml:781 #, no-c-format msgid "Xserve G5" msgstr "Xserve G5" #. Tag: entry -#: hardware.xml:783 +#: hardware.xml:784 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "Performa 4400, 54xx, 5500" #. Tag: entry -#: hardware.xml:784 hardware.xml:787 hardware.xml:790 hardware.xml:793 -#: hardware.xml:796 hardware.xml:799 hardware.xml:802 hardware.xml:805 -#: hardware.xml:808 hardware.xml:811 hardware.xml:814 hardware.xml:817 -#: hardware.xml:823 hardware.xml:826 hardware.xml:832 hardware.xml:838 -#: hardware.xml:844 +#: hardware.xml:785 hardware.xml:788 hardware.xml:791 hardware.xml:794 +#: hardware.xml:797 hardware.xml:800 hardware.xml:803 hardware.xml:806 +#: hardware.xml:809 hardware.xml:812 hardware.xml:815 hardware.xml:818 +#: hardware.xml:824 hardware.xml:827 hardware.xml:833 hardware.xml:839 +#: hardware.xml:845 #, no-c-format msgid "OldWorld" msgstr "OldWorld" #. Tag: entry -#: hardware.xml:786 +#: hardware.xml:787 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "Performa 6360, 6400, 6500" #. Tag: entry -#: hardware.xml:789 +#: hardware.xml:790 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "Power Macintosh 4400, 5400" #. Tag: entry -#: hardware.xml:792 +#: hardware.xml:793 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "Power Macintosh 7200, 7300, 7500, 7600" #. Tag: entry -#: hardware.xml:795 +#: hardware.xml:796 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "Power Macintosh 8200, 8500, 8600" #. Tag: entry -#: hardware.xml:798 +#: hardware.xml:799 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "Power Macintosh 9500, 9600" #. Tag: entry -#: hardware.xml:801 +#: hardware.xml:802 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "Power Macintosh (ベージュ) G3 ミニタワー" #. Tag: entry -#: hardware.xml:804 +#: hardware.xml:805 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "Power Macintosh (ベージュ) デスクトップ, オールインワン" #. Tag: entry -#: hardware.xml:807 +#: hardware.xml:808 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "PowerBook 2400, 3400, 3500" #. Tag: entry -#: hardware.xml:810 +#: hardware.xml:811 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "PowerBook G3 Wallstreet (1998)" #. Tag: entry -#: hardware.xml:813 +#: hardware.xml:814 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "Twentieth Anniversary Macintosh" #. Tag: entry -#: hardware.xml:816 +#: hardware.xml:817 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "Workgroup Server 7250, 7350, 8550, 9650, G3" #. Tag: entry -#: hardware.xml:821 +#: hardware.xml:822 #, no-c-format msgid "Power Computing" msgstr "Power Computing" #. Tag: entry -#: hardware.xml:822 +#: hardware.xml:823 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "PowerBase, PowerTower / Pro, PowerWave" #. Tag: entry -#: hardware.xml:825 +#: hardware.xml:826 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "PowerCenter / Pro, PowerCurve" #. Tag: entry -#: hardware.xml:830 +#: hardware.xml:831 #, no-c-format msgid "UMAX" msgstr "UMAX" #. Tag: entry -#: hardware.xml:831 +#: hardware.xml:832 #, no-c-format msgid "C500, C600, J700, S900" msgstr "C500, C600, J700, S900" #. Tag: entry -#: hardware.xml:836 +#: hardware.xml:837 #, no-c-format msgid "APS" msgstr "APS" #. Tag: entry -#: hardware.xml:837 +#: hardware.xml:838 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "APS Tech M*Power 604e/2000" #. Tag: entry -#: hardware.xml:842 hardware.xml:868 +#: hardware.xml:843 hardware.xml:869 #, no-c-format msgid "Motorola" msgstr "Motorola" #. Tag: entry -#: hardware.xml:843 +#: hardware.xml:844 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "Starmax 3000, 4000, 5000, 5500" #. Tag: title -#: hardware.xml:852 +#: hardware.xml:853 #, no-c-format msgid "PReP subarchitecture" msgstr "PReP サブアーキテクチャ" #. Tag: entry -#: hardware.xml:869 +#: hardware.xml:870 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "Firepower, PowerStack Series E, PowerStack II" #. Tag: entry -#: hardware.xml:871 +#: hardware.xml:872 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "MPC 7xx, 8xx" #. Tag: entry -#: hardware.xml:873 +#: hardware.xml:874 #, no-c-format msgid "MTX, MTX+" msgstr "MTX, MTX+" #. Tag: entry -#: hardware.xml:875 +#: hardware.xml:876 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" #. Tag: entry -#: hardware.xml:877 +#: hardware.xml:878 #, no-c-format msgid "MCP(N)750" msgstr "MCP(N)750" #. Tag: entry -#: hardware.xml:881 hardware.xml:912 +#: hardware.xml:882 hardware.xml:913 #, no-c-format msgid "IBM RS/6000" msgstr "IBM RS/6000" #. Tag: entry -#: hardware.xml:882 +#: hardware.xml:883 #, no-c-format msgid "40P, 43P" msgstr "40P, 43P" #. Tag: entry -#: hardware.xml:884 +#: hardware.xml:885 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "Power 830/850/860 (6070, 6050)" #. Tag: entry -#: hardware.xml:886 +#: hardware.xml:887 #, no-c-format msgid "6030, 7025, 7043" msgstr "6030, 7025, 7043" #. Tag: entry -#: hardware.xml:888 +#: hardware.xml:889 #, no-c-format msgid "p640" msgstr "p640" #. Tag: title -#: hardware.xml:896 +#: hardware.xml:897 #, no-c-format msgid "CHRP subarchitecture (unsupported)" msgstr "CHRP サブアーキテクチャ (未サポート)" #. Tag: entry -#: hardware.xml:913 +#: hardware.xml:914 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "B50, 43P-150, 44P" #. Tag: entry -#: hardware.xml:916 +#: hardware.xml:917 #, no-c-format msgid "Genesi" msgstr "Genesi" #. Tag: entry -#: hardware.xml:917 +#: hardware.xml:918 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "Pegasos I, Pegasos II" #. Tag: title -#: hardware.xml:925 +#: hardware.xml:926 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "APUS サブアーキテクチャ (未サポート)" #. Tag: entry -#: hardware.xml:941 +#: hardware.xml:942 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "Amiga Power-UP Systems (APUS)" #. Tag: entry -#: hardware.xml:942 +#: hardware.xml:943 #, no-c-format msgid "A1200, A3000, A4000" msgstr "A1200, A3000, A4000" #. Tag: title -#: hardware.xml:950 +#: hardware.xml:951 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "Nubus PowerMac サブアーキテクチャ (未サポート)" #. Tag: para -#: hardware.xml:952 +#: hardware.xml:953 #, no-c-format msgid "" "NuBus systems are not currently supported by &debian;/powerpc. The " @@ -1473,13 +1492,13 @@ msgstr "" "サポートされています。" #. Tag: title -#: hardware.xml:989 +#: hardware.xml:990 #, no-c-format msgid "Non-PowerPC Macs" msgstr "非 PowerPC Mac" #. Tag: para -#: hardware.xml:991 +#: hardware.xml:992 #, no-c-format msgid "" "Macintosh computers using the 680x0 series of processors are not にあります。" #. Tag: title -#: hardware.xml:1048 +#: hardware.xml:1049 #, no-c-format msgid "CPU and Main Boards Support" msgstr "CPU・マザーボードのサポート" #. Tag: para -#: hardware.xml:1049 +#: hardware.xml:1050 #, no-c-format msgid "" "Sparc-based hardware is divided into a number of different subarchitectures, " @@ -1574,13 +1593,13 @@ msgstr "" "ろうか、といったことを一覧します。" #. Tag: term -#: hardware.xml:1060 +#: hardware.xml:1061 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "sun4, sun4c, sun4d, sun4m" #. Tag: para -#: hardware.xml:1062 +#: hardware.xml:1063 #, no-c-format msgid "" "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a " @@ -1594,7 +1613,7 @@ msgstr "" "ページ をご覧ください。" #. Tag: para -#: hardware.xml:1069 +#: hardware.xml:1070 #, no-c-format msgid "" "The last &debian; release to support sparc32 was Etch, but even then only " @@ -1606,13 +1625,13 @@ msgstr "" "ポートは、以前のリリースから終了しています。" #. Tag: term -#: hardware.xml:1079 +#: hardware.xml:1080 #, no-c-format msgid "sun4u" msgstr "sun4u" #. Tag: para -#: hardware.xml:1081 +#: hardware.xml:1082 #, no-c-format msgid "" "This subarchitecture includes all 64-bit machines (sparc64) based on the " @@ -1629,13 +1648,13 @@ msgstr "" "にあわせて、sparc64 か sparc64-smp のカーネルを使用してください。" #. Tag: term -#: hardware.xml:1094 +#: hardware.xml:1095 #, no-c-format msgid "sun4v" msgstr "sun4v" #. Tag: para -#: hardware.xml:1096 +#: hardware.xml:1097 #, no-c-format msgid "" "This is the newest addition to the Sparc family, which includes machines " @@ -1649,7 +1668,7 @@ msgstr "" "い。" #. Tag: para -#: hardware.xml:1107 +#: hardware.xml:1108 #, no-c-format msgid "" "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are " @@ -1660,13 +1679,13 @@ msgstr "" "ください。" #. Tag: title -#: hardware.xml:1116 +#: hardware.xml:1117 #, no-c-format msgid "Laptops" msgstr "ラップトップコンピュータ" #. Tag: para -#: hardware.xml:1117 +#: hardware.xml:1118 #, no-c-format msgid "" "Laptops are also supported and nowadays most laptops work out of the box. In " @@ -1683,13 +1702,13 @@ msgstr "" "ださい。" #. Tag: title -#: hardware.xml:1129 hardware.xml:1152 hardware.xml:1172 hardware.xml:1195 +#: hardware.xml:1130 hardware.xml:1153 hardware.xml:1173 hardware.xml:1196 #, no-c-format msgid "Multiple Processors" msgstr "マルチプロセッサ" #. Tag: para -#: hardware.xml:1130 +#: hardware.xml:1131 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing の選択を解除してください。" #. Tag: para -#: hardware.xml:1154 +#: hardware.xml:1155 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessingsymmetric multiprocessing" #. Tag: para -#: hardware.xml:1196 +#: hardware.xml:1197 #, no-c-format msgid "" "Multiprocessor support — also called symmetric multiprocessing&smp-config-option; を選択してください。" #. Tag: title -#: hardware.xml:1223 +#: hardware.xml:1224 #, no-c-format msgid "Graphics Card Support" msgstr "グラフィックカードのサポート" #. Tag: para -#: hardware.xml:1224 +#: hardware.xml:1225 #, no-c-format msgid "" "You should be using a VGA-compatible display interface for the console " @@ -1854,7 +1873,7 @@ msgstr "" "で明示する場合を除いて X11 を用いません。" #. Tag: para -#: hardware.xml:1233 +#: hardware.xml:1234 #, no-c-format msgid "" "&debian;'s support for graphical interfaces is determined by the underlying " @@ -1871,13 +1890,13 @@ msgstr "" "&x11ver; を採用しています。" #. Tag: para -#: hardware.xml:1242 +#: hardware.xml:1243 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2." msgstr "X.Org X ウィンドウシステムは SGI Indy と O2 でのみサポートしています。" #. Tag: para -#: hardware.xml:1247 +#: hardware.xml:1248 #, no-c-format msgid "" "Most graphics options commonly found on Sparc-based machines are supported. " @@ -1898,7 +1917,7 @@ msgstr "" "るドキュメントをお読みください。" #. Tag: para -#: hardware.xml:1257 +#: hardware.xml:1258 #, no-c-format msgid "" "It is not uncommon for a Sparc machine to have two graphics cards in a " @@ -1925,13 +1944,13 @@ msgstr "" "動的にシリアルコンソールを使用する物があります。" #. Tag: title -#: hardware.xml:1279 +#: hardware.xml:1280 #, no-c-format msgid "Network Connectivity Hardware" msgstr "ネットワーク接続機器" #. Tag: para -#: hardware.xml:1280 +#: hardware.xml:1281 #, no-c-format msgid "" "Almost any network interface card (NIC) supported by the &arch-kernel; " @@ -1947,7 +1966,7 @@ msgstr "" "\"i386\">多くの古い ISA カードも同様にサポートされています。" #. Tag: para -#: hardware.xml:1289 +#: hardware.xml:1290 #, no-c-format msgid "" "This includes a lot of generic PCI cards (for systems that have PCI) and the " @@ -1957,62 +1976,62 @@ msgstr "" "の NIC が含まれます。" #. Tag: para -#: hardware.xml:1295 +#: hardware.xml:1296 #, no-c-format msgid "Sun LANCE" msgstr "Sun LANCE" #. Tag: para -#: hardware.xml:1300 +#: hardware.xml:1301 #, no-c-format msgid "Sun Happy Meal" msgstr "Sun Happy Meal" #. Tag: para -#: hardware.xml:1305 +#: hardware.xml:1306 #, no-c-format msgid "Sun BigMAC" msgstr "Sun BigMAC" #. Tag: para -#: hardware.xml:1310 +#: hardware.xml:1311 #, no-c-format msgid "Sun QuadEthernet" msgstr "Sun QuadEthernet" #. Tag: para -#: hardware.xml:1315 +#: hardware.xml:1316 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "MyriCOM Gigabit Ethernet" #. Tag: para -#: hardware.xml:1322 +#: hardware.xml:1323 #, no-c-format msgid "The list of supported network devices is:" msgstr "以下にサポートしているネットワークデバイスを挙げます。" #. Tag: para -#: hardware.xml:1327 +#: hardware.xml:1328 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" "Channel to Channel (CTC) や ESCON 接続 (リアルもしくはエミュレーション)" #. Tag: para -#: hardware.xml:1332 +#: hardware.xml:1333 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "OSA-2 Token Ring/Ethernet や OSA-Express Fast Ethernet (非 QDIO)" #. Tag: para -#: hardware.xml:1337 +#: hardware.xml:1338 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "QDIO モードの OSA-Express, HiperSockets, Guest-LAN" #. Tag: para -#: hardware.xml:1346 +#: hardware.xml:1347 #, no-c-format msgid "" "On &arch-title;, most built-in Ethernet devices are supported and modules " @@ -2031,19 +2050,19 @@ msgstr "" "\"&url-slug-firmware;\">Slug-Firmware site で手に入れられます。" #. Tag: para -#: hardware.xml:1356 +#: hardware.xml:1357 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "ISDN はサポートしていますが、インストール中には使用できません。" #. Tag: title -#: hardware.xml:1363 +#: hardware.xml:1364 #, no-c-format msgid "Wireless Network Cards" msgstr "ワイヤレスネットワークカード" #. Tag: para -#: hardware.xml:1364 +#: hardware.xml:1365 #, no-c-format msgid "" "Wireless networking is in general supported as well and a growing number of " @@ -2060,7 +2079,7 @@ msgstr "" "ついての詳細は、 をご覧ください。" #. Tag: para -#: hardware.xml:1372 +#: hardware.xml:1373 #, no-c-format msgid "" "Wireless NICs that are not supported by the official &arch-kernel; kernel " @@ -2071,7 +2090,7 @@ msgstr "" "gnu; で動作しますが、インストールの間はサポートされません。" #. Tag: para -#: hardware.xml:1377 +#: hardware.xml:1378 #, no-c-format msgid "" "Support for encrypted wireless during installation is currently limited to " @@ -2083,7 +2102,7 @@ msgstr "" "せん。" #. Tag: para -#: hardware.xml:1383 +#: hardware.xml:1384 #, no-c-format msgid "" "If there is a problem with wireless and there is no other NIC you can use " @@ -2101,7 +2120,7 @@ msgstr "" "い。" #. Tag: para -#: hardware.xml:1393 +#: hardware.xml:1394 #, no-c-format msgid "" "In some cases the driver you need may not be available as a &debian; " @@ -2119,13 +2138,13 @@ msgstr "" "パッケージが最後の楽園になります。" #. Tag: title -#: hardware.xml:1407 +#: hardware.xml:1408 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "&arch-title; に対する既知の問題" #. Tag: para -#: hardware.xml:1408 +#: hardware.xml:1409 #, no-c-format msgid "" "There are a couple of issues with specific network cards that are worth " @@ -2134,13 +2153,13 @@ msgstr "" "以下にあえて言及する特定のネットワークカードには、2, 3 の問題があります。" #. Tag: title -#: hardware.xml:1415 +#: hardware.xml:1416 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "tulip ドライバと dfme ドライバの競合" #. Tag: para -#: hardware.xml:1417 +#: hardware.xml:1418 #, no-c-format msgid "" "There are various PCI network cards that have the same PCI identification, " @@ -2158,7 +2177,7 @@ msgstr "" "場合、NIC は動作しないか誤動作します。" #. Tag: para -#: hardware.xml:1427 +#: hardware.xml:1428 #, no-c-format msgid "" "This is a common problem on Netra systems with a Davicom (DEC-Tulip " @@ -2172,7 +2191,7 @@ msgstr "" "ジュールをブラックリストに入れることで防げます。" #. Tag: para -#: hardware.xml:1435 +#: hardware.xml:1436 #, no-c-format msgid "" "An alternative solution during the installation is to switch to a shell and " @@ -2190,13 +2209,13 @@ msgstr "" "込まれたままになる可能性があることに注意してください。" #. Tag: title -#: hardware.xml:1448 +#: hardware.xml:1449 #, no-c-format msgid "Sun B100 blade" msgstr "Sun B100 blade" #. Tag: para -#: hardware.xml:1450 +#: hardware.xml:1451 #, no-c-format msgid "" "The cassini network driver does not work with Sun B100 " @@ -2206,13 +2225,13 @@ msgstr "" "動作しません。" #. Tag: title -#: hardware.xml:1465 +#: hardware.xml:1466 #, no-c-format msgid "Braille Displays" msgstr "点字ディスプレイ" #. Tag: para -#: hardware.xml:1466 +#: hardware.xml:1467 #, no-c-format msgid "" "Support for braille displays is determined by the underlying support found " @@ -2230,13 +2249,13 @@ msgstr "" "brltty のバージョン &brlttyver; を提供しています。" #. Tag: title -#: hardware.xml:1480 +#: hardware.xml:1481 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "ハードウェア音声合成" #. Tag: para -#: hardware.xml:1481 +#: hardware.xml:1482 #, no-c-format msgid "" "Support for hardware speech synthesis devices is determined by the " @@ -2257,13 +2276,13 @@ msgstr "" "classname> のバージョン &speakupver; を提供しています。" #. Tag: title -#: hardware.xml:1501 +#: hardware.xml:1502 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "周辺機器やその他のハードウェア" #. Tag: para -#: hardware.xml:1502 +#: hardware.xml:1503 #, no-c-format msgid "" "&arch-kernel; supports a large variety of hardware devices such as mice, " @@ -2275,7 +2294,7 @@ msgstr "" "らのデバイスが必要なわけではありません。" #. Tag: para -#: hardware.xml:1508 +#: hardware.xml:1509 #, no-c-format msgid "" "USB hardware generally works fine, only some USB keyboards may require " @@ -2285,7 +2304,7 @@ msgstr "" "かもしれません ( をご覧ください)。" #. Tag: para -#: hardware.xml:1514 +#: hardware.xml:1515 #, no-c-format msgid "" "Again, see the Linux Hardware " @@ -2297,7 +2316,7 @@ msgstr "" "ulink> をご覧ください。" #. Tag: para -#: hardware.xml:1520 +#: hardware.xml:1521 #, no-c-format msgid "" "Package installations from XPRAM and tape are not supported by this system. " @@ -2309,7 +2328,7 @@ msgstr "" "トワークからインストールする必要があります。" #. Tag: para -#: hardware.xml:1526 +#: hardware.xml:1527 #, no-c-format msgid "" "The Cobalt RaQ has no support for additional devices but the Qube has one " @@ -2319,13 +2338,13 @@ msgstr "" "ひとつあります。" #. Tag: title -#: hardware.xml:1538 +#: hardware.xml:1539 #, no-c-format msgid "Devices Requiring Firmware" msgstr "ファームウェアが必要なデバイス" #. Tag: para -#: hardware.xml:1539 +#: hardware.xml:1540 #, no-c-format msgid "" "Besides the availability of a device driver, some hardware also requires so-" @@ -2343,7 +2362,7 @@ msgstr "" "クコントローラでも、ファームウェアが必要なものがあります。" #. Tag: para -#: hardware.xml:1547 +#: hardware.xml:1548 #, no-c-format msgid "" "In most cases firmware is non-free according to the criteria used by the " @@ -2360,7 +2379,7 @@ msgstr "" "free セクションに独立したパッケージとして、利用できることがしばしばあります。" #. Tag: para -#: hardware.xml:1556 +#: hardware.xml:1557 #, no-c-format msgid "" "However, this does not mean that such hardware cannot be used during an " @@ -2378,13 +2397,13 @@ msgstr "" "た詳細情報は、 をご覧ください。" #. Tag: title -#: hardware.xml:1572 +#: hardware.xml:1573 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "GNU/&arch-kernel; に適したハードウェアの購入" #. Tag: para -#: hardware.xml:1574 +#: hardware.xml:1575 #, no-c-format msgid "" "There are several vendors, who ship systems with &debian; or other " @@ -2400,7 +2419,7 @@ msgstr "" "信できるわけですから。" #. Tag: para -#: hardware.xml:1582 +#: hardware.xml:1583 #, no-c-format msgid "" "If you do have to buy a machine with Windows bundled, carefully read the " @@ -2416,7 +2435,7 @@ msgstr "" "にはいるかも知れません。" #. Tag: para -#: hardware.xml:1590 +#: hardware.xml:1591 #, no-c-format msgid "" "Whether or not you are purchasing a system with &arch-kernel; bundled, or " @@ -2434,13 +2453,13 @@ msgstr "" "ハードウェアベンダを支援しましょう。" #. Tag: title -#: hardware.xml:1601 +#: hardware.xml:1602 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "独占的・閉鎖的なハードウェアを避ける" #. Tag: para -#: hardware.xml:1602 +#: hardware.xml:1603 #, no-c-format msgid "" "Some hardware manufacturers simply won't tell us how to write drivers for " @@ -2453,7 +2472,7 @@ msgstr "" "意) をしない限り、文書を見せてくれないメーカーもあります。" #. Tag: para -#: hardware.xml:1609 +#: hardware.xml:1610 #, no-c-format msgid "" "Since we haven't been granted access to the documentation on these devices, " @@ -2468,13 +2487,13 @@ msgstr "" "れば、彼らも &arch-kernel; が重要な市場であると認識するでしょう。" #. Tag: title -#: hardware.xml:1621 +#: hardware.xml:1622 #, no-c-format msgid "Windows-specific Hardware" msgstr "Windows に特化したハードウェア" #. Tag: para -#: hardware.xml:1622 +#: hardware.xml:1623 #, no-c-format msgid "" "A disturbing trend is the proliferation of Windows-specific modems and " @@ -2498,7 +2517,7 @@ msgstr "" "等の機能を持つハードウェア内蔵のものよりも高価になることもあります。" #. Tag: para -#: hardware.xml:1635 +#: hardware.xml:1636 #, no-c-format msgid "" "You should avoid Windows-specific hardware for two reasons. The first is " @@ -2537,7 +2556,7 @@ msgstr "" "くなります。" #. Tag: para -#: hardware.xml:1656 +#: hardware.xml:1657 #, no-c-format msgid "" "You can help improve this situation by encouraging these manufacturers to " @@ -2554,13 +2573,13 @@ msgstr "" "この種のハードウェアを避けることです。" #. Tag: title -#: hardware.xml:1674 +#: hardware.xml:1675 #, no-c-format msgid "Installation Media" msgstr "インストールに利用できるメディア" #. Tag: para -#: hardware.xml:1676 +#: hardware.xml:1677 #, no-c-format msgid "" "This section will help you determine which different media types you can use " @@ -2577,13 +2596,13 @@ msgstr "" "あります。その章から、このページをもう一度参照するかもしれません。" #. Tag: title -#: hardware.xml:1687 +#: hardware.xml:1688 #, no-c-format msgid "Floppies" msgstr "フロッピーディスク" #. Tag: para -#: hardware.xml:1688 +#: hardware.xml:1689 #, no-c-format msgid "" "In some cases, you'll have to do your first boot from floppy disks. " @@ -2594,19 +2613,19 @@ msgstr "" "う。通常 3.5 インチ高密度 (1440 kB) フロッピードライブがあれば充分です。" #. Tag: para -#: hardware.xml:1694 +#: hardware.xml:1695 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "CHRP では、フロッピーのサポートは、現在中断しています。" #. Tag: title -#: hardware.xml:1701 +#: hardware.xml:1702 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "CD-ROM/DVD-ROM" #. Tag: para -#: hardware.xml:1703 +#: hardware.xml:1704 #, no-c-format msgid "" "Whenever you see CD-ROM in this manual, it applies to both CD-" @@ -2619,7 +2638,7 @@ msgstr "" "でも IDE/ATAPI でもないような、非常に古く非標準な CD-ROM ドライブを除く)" #. Tag: para -#: hardware.xml:1710 +#: hardware.xml:1711 #, no-c-format msgid "" "CD-ROM based installation is supported for some architectures. On machines " @@ -2638,7 +2657,7 @@ msgstr "" " を参照して一度他の方法で起動してください。" #. Tag: para -#: hardware.xml:1722 +#: hardware.xml:1723 #, no-c-format msgid "" "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The boot the installation system over the " @@ -2774,7 +2793,7 @@ msgstr "" "でしょう。" #. Tag: para -#: hardware.xml:1799 +#: hardware.xml:1800 #, no-c-format msgid "" "Diskless installation, using network booting from a local area network and " @@ -2784,13 +2803,13 @@ msgstr "" "トして、ディスクレスインストールをすることも一つの選択です。" #. Tag: title -#: hardware.xml:1807 +#: hardware.xml:1808 #, no-c-format msgid "Un*x or GNU system" msgstr "Un*x・GNU システム" #. Tag: para -#: hardware.xml:1809 +#: hardware.xml:1810 #, no-c-format msgid "" "If you are running another Unix-like system, you could use it to install " @@ -2806,13 +2825,13 @@ msgstr "" "> へスキップしてください。" #. Tag: title -#: hardware.xml:1821 +#: hardware.xml:1822 #, no-c-format msgid "Supported Storage Systems" msgstr "サポートする記憶装置" #. Tag: para -#: hardware.xml:1823 +#: hardware.xml:1824 #, no-c-format msgid "" "The &debian; boot disks contain a kernel which is built to maximize the " @@ -2831,7 +2850,7 @@ msgstr "" "をサポートするのが望ましいでしょう。" #. Tag: para -#: hardware.xml:1833 +#: hardware.xml:1834 #, no-c-format msgid "" "Generally, the &debian; installation system includes support for floppies, " @@ -2845,7 +2864,7 @@ msgstr "" "ルシステムは、FAT、Win-32 拡張 FAT (VFAT)、NTFS です。" #. Tag: para -#: hardware.xml:1840 +#: hardware.xml:1841 #, no-c-format msgid "" "Disk interfaces that emulate the AT hard disk interface " @@ -2861,7 +2880,7 @@ msgstr "" "ご覧ください。" #. Tag: para -#: hardware.xml:1848 +#: hardware.xml:1849 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " @@ -2885,7 +2904,7 @@ msgstr "" "ulink> をご覧ください。" #. Tag: para -#: hardware.xml:1881 +#: hardware.xml:1882 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " @@ -2897,7 +2916,7 @@ msgstr "" "をまったくサポートしていないことにご注意ください。" #. Tag: para -#: hardware.xml:1887 +#: hardware.xml:1888 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " @@ -2909,7 +2928,7 @@ msgstr "" "ポートしていないことにご注意ください。" #. Tag: para -#: hardware.xml:1893 +#: hardware.xml:1894 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " @@ -2919,7 +2938,7 @@ msgstr "" "ポートされています。" #. Tag: para -#: hardware.xml:1898 +#: hardware.xml:1899 #, no-c-format msgid "" "Any storage system supported by the Linux kernel is also supported by the " @@ -2932,13 +2951,13 @@ msgstr "" "です。" #. Tag: title -#: hardware.xml:1915 +#: hardware.xml:1916 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "必要なメモリとディスクスペース" #. Tag: para -#: hardware.xml:1917 +#: hardware.xml:1918 #, no-c-format msgid "" "You must have at least &minimum-memory; of memory and &minimum-fs-size; of " @@ -2952,7 +2971,7 @@ msgstr "" "をご覧ください。" #. Tag: para -#: hardware.xml:1924 +#: hardware.xml:1925 #, no-c-format msgid "" "Installation on systems with less memory " diff --git a/po/ja/install-methods.po b/po/ja/install-methods.po index 3897dd8b7..f54510be1 100644 --- a/po/ja/install-methods.po +++ b/po/ja/install-methods.po @@ -3,8 +3,8 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" -"PO-Revision-Date: 2010-12-30 09:42+0900\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" +"PO-Revision-Date: 2011-05-15 10:10+0900\n" "Last-Translator: KURASAWA Nozomu \n" "Language-Team: Japanese \n" "Language: ja\n" @@ -761,21 +761,6 @@ msgstr "USB メモリでの起動用ファイルの準備" #: install-methods.xml:532 #, no-c-format msgid "" -"There are two installation methods possible when booting from USB stick. The " -"first is to only use the USB stick to boot the installer, and then install " -"completely from the network. The second is to also copy a CD image onto the " -"USB stick and use that as a source for packages, possibly in combination " -"with a mirror." -msgstr "" -"USB メモリから起動した際に、利用できるインストール法が 2 つあります。ひとつ" -"は、USB メモリをインストーラの起動にのみ使用し、完全にネットワークからインス" -"トールする方法、2 つめは、CD イメージを USB メモリにコピーし、パッケージをそ" -"こから (可能であればミラーサイトも組み合わせて) インストールする方法です。" - -#. Tag: para -#: install-methods.xml:540 -#, no-c-format -msgid "" "To prepare the USB stick, you will need a system where GNU/Linux is already " "running and where USB is supported. With current GNU/Linux systems the USB " "stick should be automatically recognized when you insert it. If it is not " @@ -796,7 +781,7 @@ msgstr "" "イッチを切る必要があります。" #. Tag: para -#: install-methods.xml:553 +#: install-methods.xml:545 #, no-c-format msgid "" "The procedures described in this section will destroy anything already on " @@ -808,38 +793,53 @@ msgstr "" "いデバイス名を必ず確認して使用してください。間違ったデバイス名を使用すると、" "例えばハードディスク内のすべてのデータを失うといったことが起こります。" +#. Tag: title +#: install-methods.xml:555 +#, no-c-format +msgid "Preparing a USB stick using a hybrid CD or DVD image" +msgstr "" + #. Tag: para -#: install-methods.xml:560 +#: install-methods.xml:556 #, no-c-format msgid "" -"To prepare a USB stick that only boots the installer, which then proceeds to " -"install entirely from the network, you'll need to download the " -"mini.iso image from the netboot " -"directory (at the location mentioned in ), " -"and write this file directly to the USB stick, overwriting its current " -"contents. This method will work with very small USB sticks, only a few " -"megabytes in size." +"Debian CD and DVD images can now be written directly a USB stick, which is a " +"very easy way to make a bootable USB stick. Simply choose a CD or DVD image " +"that will fit on your USB stick. See to " +"get a CD or DVD image." msgstr "" -"インストーラの起動のみを行い、ネットワークからインストール全体を行う USB メモ" -"リを用意するには、netboot ディレクトリ (場所は で言及)から mini.iso イメージ" -"をダウンロードし、USB メモリの既存の内容を上書きしてください。この方法では数 " -"MB しか使用しませんので、非常に小さな USB メモリでも動作します。" #. Tag: para -#: install-methods.xml:570 +#: install-methods.xml:563 #, no-c-format msgid "" -"For example, when using an existing GNU/Linux system, the mini." -"iso file can be written to a USB stick as follows: " -"\n" -"# cat mini.iso > /dev/sdX\n" -"# sync\n" -" To add firmware to a USB stick prepared in this " -"way, obtain the necessary firmware files. See for more information. Now unplug and replug the USB stick, and " -"two partitions should now be visible on it. You should mount the second of " -"the two partitions, and unpack the firmware onto it." +"Alternatively, for very small USB sticks, only a few megabytes in size, you " +"can download the mini.iso image from the " +"netboot directory (at the location mentioned in )." +msgstr "" + +#. Tag: para +#: install-methods.xml:571 +#, fuzzy, no-c-format +#| msgid "" +#| "For example, when using an existing GNU/Linux system, the mini." +#| "iso file can be written to a USB stick as follows: " +#| "\n" +#| "# cat mini.iso > /dev/sdX\n" +#| "# sync\n" +#| " To add firmware to a USB stick prepared in " +#| "this way, obtain the necessary firmware files. See for more information. Now unplug and replug the " +#| "USB stick, and two partitions should now be visible on it. You should " +#| "mount the second of the two partitions, and unpack the firmware onto it." +msgid "" +"A special method can be used to add firmware to the mini.iso. First, write the mini.iso to the USB stick. " +"Next obtain the necessary firmware files. See for more information about firmware. Now unplug and replug the " +"USB stick, and two partitions should now be visible on it. You should mount " +"the second of the two partitions, and unpack the firmware onto it." msgstr "" "例えば、既存の GNU/Linux システムを用いる場合、mini.iso " "ファイルを以下のようにして USB メモリに書き込めます。" @@ -852,7 +852,7 @@ msgstr "" "ティションをマウントし、ファームウェアをそこに展開してください。" #. Tag: screen -#: install-methods.xml:582 +#: install-methods.xml:581 #, no-c-format msgid "" "# mount /dev/sdX2 /mnt\n" @@ -868,50 +868,53 @@ msgstr "" "# umount" #. Tag: para -#: install-methods.xml:584 +#: install-methods.xml:587 #, no-c-format msgid "" -"To prepare a USB stick that installs packages from a CD image included on " -"the stick, use the installer images found in the hd-media directory. Either the easy way or the " -"flexible way can be used to copy the image to the USB stick. " -"For this installation method you will also need to download a CD image. The " -"installation image and the CD image must be based on the same release of &d-" -"i;. If they do not match you are likely to get errors The " -"error message that is most likely to be displayed is that no kernel modules " -"can be found. This means that the version of the kernel module udebs " -"included on the CD image is different from the version of the running " -"kernel. during the installation." +"The CD or DVD image you choose should be written directly to the USB stick, " +"overwriting its current contents. For example, when using an existing GNU/" +"Linux system, the CD or DVD image file can be written to a USB stick as " +"follows:" msgstr "" -"内部にある CD イメージからパッケージをインストールする USB メモリを用意するに" -"は、hd-media ディレクトリにあるインストーライメージを使" -"用してください。このイメージを USB メモリにコピーするには、簡単な方法" -" でも 柔軟な方法 でもかまいません。このインストール法" -"では、CD イメージもダウンロードする必要があるでしょう。インストールイメージ" -"と CD イメージは &d-i; の同じリリースのものでなければなりません。同じものを使" -"用しないと、おそらくインストール中にエラーになるでしょう " -"もっとも起こりそうなエラーは、カーネルモジュールが見つからないというもので" -"す。これは、CD イメージにあるカーネルモジュール udeb のバージョンが、実行中の" -"カーネルのバージョンと異なることを表しています。 。" -#. Tag: para -#: install-methods.xml:604 +#. Tag: screen +#: install-methods.xml:594 #, no-c-format +#| msgid "# zcat boot.img.gz > /dev/sdX" msgid "" -"Note that the USB stick should be at least 256 MB in size (smaller setups " -"are possible if you follow )." +"# cat debian.iso > /dev/sdX\n" +"# sync" msgstr "" -"USB メモリは少なくとも 128 MB のサイズがなければなりません ( のようにすれば、 より小さなセットアップが可能です)。" +"# cat debian.iso > /dev/sdX\n" +"# sync" #. Tag: title -#: install-methods.xml:612 +#: install-methods.xml:601 #, no-c-format -msgid "Copying the files — the easy way" -msgstr "ファイルのコピー — 簡単な方法" +#| msgid "Booting the USB stick" +msgid "Manually copying files to the USB stick" +msgstr "USB メモリへのファイルの手動コピー" + +#. Tag: para +#: install-methods.xml:602 +#, fuzzy, no-c-format +#| msgid "" +#| "Note that the USB stick should be at least 256 MB in size (smaller setups " +#| "are possible if you follow )." +msgid "" +"An alternative way to set up your USB stick is to manually copy the " +"installer files, and also a CD image to it. Note that the USB stick should " +"be at least 256 MB in size (smaller setups are possible if you follow )." +msgstr "" +"USB メモリは少なくとも 256 MB のサイズがなければなりません ( のようにすれば、もっと少ないサイズでもセットアップが" +"可能です)。" #. Tag: para -#: install-methods.xml:613 +#: install-methods.xml:609 #, no-c-format msgid "" "There is an all-in-one file hd-media/boot.img.gz which " @@ -927,7 +930,7 @@ msgstr "" "あります。" #. Tag: para -#: install-methods.xml:622 +#: install-methods.xml:618 #, no-c-format msgid "" "Note that, although convenient, this method does have one major " @@ -946,19 +949,19 @@ msgstr "" "さい businesscard や netinst の CD イメージしか使えないことです。" #. Tag: para -#: install-methods.xml:632 +#: install-methods.xml:628 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "このイメージを使用するには、単にUSB メモリに直接展開してください。" #. Tag: screen -#: install-methods.xml:636 +#: install-methods.xml:632 #, no-c-format msgid "# zcat boot.img.gz > /dev/sdX" msgstr "# zcat boot.img.gz > /dev/sdX" #. Tag: para -#: install-methods.xml:638 +#: install-methods.xml:634 #, no-c-format msgid "" "Create a partition of type \"Apple_Bootstrap\" on your USB stick using " @@ -970,13 +973,13 @@ msgstr "" "モリに直接展開してください。" #. Tag: screen -#: install-methods.xml:644 +#: install-methods.xml:640 #, no-c-format msgid "# zcat boot.img.gz > /dev/sdX2" msgstr "# zcat boot.img.gz > /dev/sdX2" #. Tag: para -#: install-methods.xml:646 +#: install-methods.xml:642 #, no-c-format msgid "" "After that, mount the USB memory stick " @@ -997,13 +1000,14 @@ msgstr "" "アンマウント (umount /mnt) すると完了です。" #. Tag: title -#: install-methods.xml:663 +#: install-methods.xml:659 #, no-c-format -msgid "Copying the files — the flexible way" -msgstr "ファイルのコピー — 柔軟な方法" +#| msgid "Copying the files — the flexible way" +msgid "Manually copying files to the USB stick — the flexible way" +msgstr "USB メモリへのファイルの手動コピー — 柔軟な方法" #. Tag: para -#: install-methods.xml:664 +#: install-methods.xml:660 #, no-c-format msgid "" "If you like more flexibility or just want to know what's going on, you " @@ -1018,13 +1022,13 @@ msgstr "" "ということです。" #. Tag: title -#: install-methods.xml:679 install-methods.xml:791 +#: install-methods.xml:675 install-methods.xml:787 #, no-c-format msgid "Partitioning the USB stick" msgstr "USB メモリのパーティション分割" #. Tag: para -#: install-methods.xml:680 +#: install-methods.xml:676 #, no-c-format msgid "" "We will show how to set up the memory stick to use the first partition, " @@ -1034,7 +1038,7 @@ msgstr "" "を示します。" #. Tag: para -#: install-methods.xml:685 +#: install-methods.xml:681 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you " @@ -1061,7 +1065,7 @@ msgstr "" "&debian; パッケージに含まれています。" #. Tag: para -#: install-methods.xml:704 +#: install-methods.xml:700 #, no-c-format msgid "" "In order to start the kernel after booting from the USB stick, we will put a " @@ -1079,7 +1083,7 @@ msgstr "" "のに利用できます。" #. Tag: para -#: install-methods.xml:714 +#: install-methods.xml:710 #, no-c-format msgid "" "To put syslinux on the FAT16 partition on your USB " @@ -1104,13 +1108,13 @@ msgstr "" "を作成します。" #. Tag: title -#: install-methods.xml:731 install-methods.xml:838 +#: install-methods.xml:727 install-methods.xml:834 #, no-c-format msgid "Adding the installer image" msgstr "インストーライメージの追加" #. Tag: para -#: install-methods.xml:732 +#: install-methods.xml:728 #, no-c-format msgid "" "Mount the partition (mount /dev/sdX1 /" @@ -1135,7 +1139,7 @@ msgstr "" "DOS (8.3) のファイル名しか処理できないことに注意してください。" #. Tag: para -#: install-methods.xml:756 +#: install-methods.xml:752 #, no-c-format msgid "" "Next you should create a syslinux.cfg configuration " @@ -1158,7 +1162,7 @@ msgstr "" "vga=788 を追加すると良いでしょう。" #. Tag: para -#: install-methods.xml:768 +#: install-methods.xml:764 #, no-c-format msgid "" "If you used an hd-media image, you should now copy a " @@ -1178,7 +1182,7 @@ msgstr "" "(umount /mnt)。" #. Tag: para -#: install-methods.xml:792 +#: install-methods.xml:788 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware " @@ -1207,7 +1211,7 @@ msgstr "" "classname> &debian; パッケージに含まれています。" #. Tag: para -#: install-methods.xml:809 +#: install-methods.xml:805 #, no-c-format msgid "" "In order to start the kernel after booting from the USB stick, we will put a " @@ -1223,7 +1227,7 @@ msgstr "" "す。" #. Tag: para -#: install-methods.xml:818 +#: install-methods.xml:814 #, no-c-format msgid "" "The normal ybin tool that comes with yabootmount /dev/sdX2 /" @@ -1269,31 +1273,31 @@ msgstr "" "リへコピーしてください。" #. Tag: para -#: install-methods.xml:846 +#: install-methods.xml:842 #, no-c-format msgid "vmlinux (kernel binary)" msgstr "vmlinux (カーネルバイナリ)" #. Tag: para -#: install-methods.xml:851 +#: install-methods.xml:847 #, no-c-format msgid "initrd.gz (initial ramdisk image)" msgstr "initrd.gz (初期 RAM ディスクイメージ)" #. Tag: para -#: install-methods.xml:856 +#: install-methods.xml:852 #, no-c-format msgid "yaboot.conf (yaboot configuration file)" msgstr "yaboot.conf (yaboot 設定ファイル)" #. Tag: para -#: install-methods.xml:861 +#: install-methods.xml:857 #, no-c-format msgid "boot.msg (optional boot message)" msgstr "boot.msg (追加起動メッセージ)" #. Tag: para -#: install-methods.xml:868 +#: install-methods.xml:864 #, no-c-format msgid "" "The yaboot.conf configuration file should contain the " @@ -1328,7 +1332,7 @@ msgstr "" "size パラメータを、 増やす必要があることに注意してください。" #. Tag: para -#: install-methods.xml:878 +#: install-methods.xml:874 #, no-c-format msgid "" "If you used an hd-media image, you should now copy a " @@ -1342,38 +1346,13 @@ msgstr "" "ウントしてください (umount /mnt)。" #. Tag: title -#: install-methods.xml:893 -#, no-c-format -msgid "Booting the USB stick" -msgstr "USB メモリからの起動" - -#. Tag: para #: install-methods.xml:894 #, no-c-format -msgid "" -"If your system refuses to boot from the memory stick, the stick may contain " -"an invalid master boot record (MBR). To fix this, use the install-" -"mbr command from the package mbr:" -msgstr "" -"システムが USB メモリから起動できなければ、 この USB メモリには無効なマスター" -"ブートレコード (MBR) があります。 これを修正するために、mbr パッケージの install-mbr コマンドを次のように実" -"行してください。" - -#. Tag: screen -#: install-methods.xml:901 -#, no-c-format -msgid "# install-mbr /dev/sdX" -msgstr "# install-mbr /dev/sdX" - -#. Tag: title -#: install-methods.xml:912 -#, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "ハードディスク起動ファイルの準備" #. Tag: para -#: install-methods.xml:913 +#: install-methods.xml:895 #, no-c-format msgid "" "The installer may be booted using boot files placed on an existing hard " @@ -1385,7 +1364,7 @@ msgstr "" "ることもできます。" #. Tag: para -#: install-methods.xml:919 +#: install-methods.xml:901 #, no-c-format msgid "" "A full, pure network installation can be achieved using this " @@ -1399,7 +1378,7 @@ msgstr "" "事全てを避けることができます。" #. Tag: para -#: install-methods.xml:926 +#: install-methods.xml:908 #, no-c-format msgid "" "The installer cannot boot from files on an HFS+ file system. MacOS System " @@ -1421,7 +1400,7 @@ msgstr "" "たファイル) をやりとりするためには、HFS パーティションが必要です。" #. Tag: para -#: install-methods.xml:937 +#: install-methods.xml:919 #, no-c-format msgid "" "Different programs are used for hard disk installation system booting, " @@ -1433,7 +1412,7 @@ msgstr "" "別々のプログラムを使います。" #. Tag: title -#: install-methods.xml:946 +#: install-methods.xml:928 #, no-c-format msgid "" "Hard disk installer booting using LILO or GRUB/boot/newinstall/ などです。" #. Tag: para -#: install-methods.xml:968 +#: install-methods.xml:950 #, no-c-format msgid "vmlinuz (kernel binary)" msgstr "vmlinuz (カーネルバイナリ)" #. Tag: para -#: install-methods.xml:973 +#: install-methods.xml:955 #, no-c-format msgid "initrd.gz (ramdisk image)" msgstr "initrd.gz (RAM ディスクイメージ)" #. Tag: para -#: install-methods.xml:980 +#: install-methods.xml:962 #, no-c-format msgid "" "Finally, to configure the bootloader proceed to loadlin" msgstr "" "loadlin を使用したハードディスクからのインストーラの起動" #. Tag: para -#: install-methods.xml:991 +#: install-methods.xml:973 #, no-c-format msgid "" "This section explains how to prepare your hard drive for booting the " @@ -1516,7 +1495,7 @@ msgstr "" "するようハードディスクを準備する方法を説明します。" #. Tag: para -#: install-methods.xml:996 +#: install-methods.xml:978 #, no-c-format msgid "" "Copy the following directories from a &debian; CD image to c:\\/&x86-install-dir; (kernel binary and ramdisk image)" @@ -1535,19 +1514,19 @@ msgstr "" "メージ)" #. Tag: para -#: install-methods.xml:1006 +#: install-methods.xml:988 #, no-c-format msgid "/tools (loadlin tool)" msgstr "/tools (loadlin ツール)" #. Tag: title -#: install-methods.xml:1019 +#: install-methods.xml:1001 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "OldWorld Mac におけるハードディスクからのインストーラの起動" #. Tag: para -#: install-methods.xml:1020 +#: install-methods.xml:1002 #, no-c-format msgid "" "The boot-floppy-hfs floppy uses miBootBootX が必要です。" #. Tag: para -#: install-methods.xml:1033 +#: install-methods.xml:1015 #, no-c-format msgid "" "Download and unstuff the BootX distribution, " @@ -1599,13 +1578,13 @@ msgstr "" "System Folder に置いてください。" #. Tag: title -#: install-methods.xml:1053 +#: install-methods.xml:1035 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "NewWorld Mac におけるハードディスクからのインストーラの起動" #. Tag: para -#: install-methods.xml:1054 +#: install-methods.xml:1036 #, no-c-format msgid "" "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as " @@ -1626,7 +1605,7 @@ msgstr "" "PowerMac をサポートしておらず、 使うべきではありません。" #. Tag: para -#: install-methods.xml:1065 +#: install-methods.xml:1047 #, no-c-format msgid "" "Copy (not move) the following four files which you " @@ -1640,31 +1619,31 @@ msgstr "" "ラッグします)。" #. Tag: filename -#: install-methods.xml:1075 install-methods.xml:1401 +#: install-methods.xml:1057 install-methods.xml:1383 #, no-c-format msgid "vmlinux" msgstr "vmlinux" #. Tag: filename -#: install-methods.xml:1080 install-methods.xml:1406 +#: install-methods.xml:1062 install-methods.xml:1388 #, no-c-format msgid "initrd.gz" msgstr "initrd.gz" #. Tag: filename -#: install-methods.xml:1085 install-methods.xml:1411 +#: install-methods.xml:1067 install-methods.xml:1393 #, no-c-format msgid "yaboot" msgstr "yaboot" #. Tag: filename -#: install-methods.xml:1090 install-methods.xml:1416 +#: install-methods.xml:1072 install-methods.xml:1398 #, no-c-format msgid "yaboot.conf" msgstr "yaboot.conf" #. Tag: para -#: install-methods.xml:1095 +#: install-methods.xml:1077 #, no-c-format msgid "" "Make a note of the partition number of the MacOS partition where you place " @@ -1680,7 +1659,7 @@ msgstr "" "入力するコマンドで必要となります。" #. Tag: para -#: install-methods.xml:1103 +#: install-methods.xml:1085 #, no-c-format msgid "To boot the installer, proceed to ." msgstr "" @@ -1688,13 +1667,13 @@ msgstr "" "トーラを起動させるには、 に進んでください。" #. Tag: title -#: install-methods.xml:1116 +#: install-methods.xml:1098 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "TFTP ネットブート用ファイルの準備" #. Tag: para -#: install-methods.xml:1117 +#: install-methods.xml:1099 #, no-c-format msgid "" "If your machine is connected to a local area network, you may be able to " @@ -1710,7 +1689,7 @@ msgstr "" "せん。" #. Tag: para -#: install-methods.xml:1125 +#: install-methods.xml:1107 #, no-c-format msgid "" "You need to set up a TFTP server, and for many machines a DHCP serverThe Reverse Address Resolution Protocol " @@ -1744,7 +1723,7 @@ msgstr "" "DHCP でしか設定できないこともあります。" #. Tag: para -#: install-methods.xml:1146 +#: install-methods.xml:1128 #, no-c-format msgid "" "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good " @@ -1756,7 +1735,7 @@ msgstr "" "あります。" #. Tag: para -#: install-methods.xml:1152 +#: install-methods.xml:1134 #, no-c-format msgid "" "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There " @@ -1767,7 +1746,7 @@ msgstr "" "す。" #. Tag: para -#: install-methods.xml:1157 +#: install-methods.xml:1139 #, no-c-format msgid "" "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to " @@ -1781,7 +1760,7 @@ msgstr "" "4.x, SunOS 5.x (Solaris), GNU/Linux での例を示します。" #. Tag: para -#: install-methods.xml:1165 +#: install-methods.xml:1147 #, no-c-format msgid "" "For a &debian-gnu; server we recommend tftpd-hpa. " @@ -1795,13 +1774,13 @@ msgstr "" "です。" #. Tag: title -#: install-methods.xml:1181 +#: install-methods.xml:1163 #, no-c-format msgid "Setting up RARP server" msgstr "RARP サーバの設定" #. Tag: para -#: install-methods.xml:1182 +#: install-methods.xml:1164 #, no-c-format msgid "" "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC " @@ -1820,7 +1799,7 @@ msgstr "" "て ip addr show dev eth0 コマンドを使ってください。" #. Tag: para -#: install-methods.xml:1194 +#: install-methods.xml:1176 #, no-c-format msgid "" "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, " @@ -1845,13 +1824,13 @@ msgstr "" "で) 実行してください。" #. Tag: title -#: install-methods.xml:1215 +#: install-methods.xml:1197 #, no-c-format msgid "Setting up a DHCP server" msgstr "DHCP サーバの設定" #. Tag: para -#: install-methods.xml:1216 +#: install-methods.xml:1198 #, no-c-format msgid "" "One free software DHCP server is ISC dhcpd. For &debian-" @@ -1865,7 +1844,7 @@ msgstr "" "dhcpd.conf を参照)" #. Tag: screen -#: install-methods.xml:1223 +#: install-methods.xml:1205 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -1909,7 +1888,7 @@ msgstr "" "}" #. Tag: para -#: install-methods.xml:1225 +#: install-methods.xml:1207 #, no-c-format msgid "" "In this example, there is one server servername " @@ -1926,7 +1905,7 @@ msgstr "" "ションは TFTP 経由で取得するファイルの名前です。" #. Tag: para -#: install-methods.xml:1235 +#: install-methods.xml:1217 #, no-c-format msgid "" "After you have edited the dhcpd configuration file, " @@ -1937,13 +1916,13 @@ msgstr "" "してください。" #. Tag: title -#: install-methods.xml:1243 +#: install-methods.xml:1225 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "DHCP 設定での PXE 起動の有効化" #. Tag: para -#: install-methods.xml:1244 +#: install-methods.xml:1226 #, no-c-format msgid "" "Here is another example for a dhcp.conf using the Pre-" @@ -2014,13 +1993,13 @@ msgstr "" "い)。" #. Tag: title -#: install-methods.xml:1264 +#: install-methods.xml:1246 #, no-c-format msgid "Setting up a BOOTP server" msgstr "BOOTP サーバの設定" #. Tag: para -#: install-methods.xml:1265 +#: install-methods.xml:1247 #, no-c-format msgid "" "There are two BOOTP servers available for GNU/Linux. The first is CMU " @@ -2036,7 +2015,7 @@ msgstr "" "ぞれ入っています。" #. Tag: para -#: install-methods.xml:1273 +#: install-methods.xml:1255 #, no-c-format msgid "" "To use CMU bootpd, you must first uncomment (or add) the " @@ -2100,7 +2079,7 @@ msgstr "" "userinput> 変数がマシンの MAC アドレスです。 " #. Tag: para -#: install-methods.xml:1306 +#: install-methods.xml:1288 #, no-c-format msgid "" "By contrast, setting up BOOTP with ISC dhcpd is really " @@ -2124,13 +2103,13 @@ msgstr "" "dhcpd を再起動するだけです。" #. Tag: title -#: install-methods.xml:1325 +#: install-methods.xml:1307 #, no-c-format msgid "Enabling the TFTP Server" msgstr "TFTP サーバの立ち上げ" #. Tag: para -#: install-methods.xml:1326 +#: install-methods.xml:1308 #, no-c-format msgid "" "To get the TFTP server ready to go, you should first make sure that " @@ -2140,7 +2119,7 @@ msgstr "" "を確認してください。" #. Tag: para -#: install-methods.xml:1331 +#: install-methods.xml:1313 #, no-c-format msgid "" "In the case of tftpd-hpa there are two ways the " @@ -2155,7 +2134,7 @@ msgstr "" "は、パッケージのインストール時や再設定時に選択できます。" #. Tag: para -#: install-methods.xml:1340 +#: install-methods.xml:1322 #, no-c-format msgid "" "Historically, TFTP servers used /tftpboot as directory " @@ -2173,7 +2152,7 @@ msgstr "" "要に応じて、本節の設定例を調整してください。" #. Tag: para -#: install-methods.xml:1350 +#: install-methods.xml:1332 #, no-c-format msgid "" "All in.tftpd alternatives available in &debian; should " @@ -2189,7 +2168,7 @@ msgstr "" "勧めします。" #. Tag: para -#: install-methods.xml:1358 +#: install-methods.xml:1340 #, no-c-format msgid "" "If you intend to install &debian; on an SGI machine and your TFTP server is " @@ -2219,13 +2198,13 @@ msgstr "" "調整してください。" #. Tag: title -#: install-methods.xml:1380 +#: install-methods.xml:1362 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "TFTP イメージを適切な場所に配置する" #. Tag: para -#: install-methods.xml:1381 +#: install-methods.xml:1363 #, no-c-format msgid "" "Next, place the TFTP boot image you need, as found in boot netbootpd to supply the " @@ -2381,13 +2360,13 @@ msgstr "" "filename> の filename= オプションに指定します。" #. Tag: title -#: install-methods.xml:1590 +#: install-methods.xml:1572 #, no-c-format msgid "Automatic Installation" msgstr "自動インストール" #. Tag: para -#: install-methods.xml:1591 +#: install-methods.xml:1573 #, no-c-format msgid "" "For installing on multiple computers it's possible to do fully automatic " @@ -2402,13 +2381,13 @@ msgstr "" "FAI home page をご覧ください。" #. Tag: title -#: install-methods.xml:1603 +#: install-methods.xml:1585 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "&debian; インストーラを用いた自動インストール" #. Tag: para -#: install-methods.xml:1604 +#: install-methods.xml:1586 #, no-c-format msgid "" "The &debian; Installer supports automating installs via preconfiguration " @@ -2422,7 +2401,7 @@ msgstr "" "れます。" #. Tag: para -#: install-methods.xml:1611 +#: install-methods.xml:1593 #, no-c-format msgid "" "Full documentation on preseeding including a working example that you can " @@ -2431,6 +2410,78 @@ msgstr "" "編集できる動作サンプルを含む preseed の完全なドキュメントは、 にあります。" +#~ msgid "" +#~ "There are two installation methods possible when booting from USB stick. " +#~ "The first is to only use the USB stick to boot the installer, and then " +#~ "install completely from the network. The second is to also copy a CD " +#~ "image onto the USB stick and use that as a source for packages, possibly " +#~ "in combination with a mirror." +#~ msgstr "" +#~ "USB メモリから起動した際に、利用できるインストール法が 2 つあります。ひと" +#~ "つは、USB メモリをインストーラの起動にのみ使用し、完全にネットワークからイ" +#~ "ンストールする方法、2 つめは、CD イメージを USB メモリにコピーし、パッケー" +#~ "ジをそこから (可能であればミラーサイトも組み合わせて) インストールする方法" +#~ "です。" + +#~ msgid "" +#~ "To prepare a USB stick that only boots the installer, which then proceeds " +#~ "to install entirely from the network, you'll need to download the " +#~ "mini.iso image from the netboot " +#~ "directory (at the location mentioned in ), " +#~ "and write this file directly to the USB stick, overwriting its current " +#~ "contents. This method will work with very small USB sticks, only a few " +#~ "megabytes in size." +#~ msgstr "" +#~ "インストーラの起動のみを行い、ネットワークからインストール全体を行う USB " +#~ "メモリを用意するには、netboot ディレクトリ (場所は " +#~ " で言及)から mini.iso " +#~ "イメージをダウンロードし、USB メモリの既存の内容を上書きしてください。この" +#~ "方法では数 MB しか使用しませんので、非常に小さな USB メモリでも動作しま" +#~ "す。" + +#~ msgid "" +#~ "To prepare a USB stick that installs packages from a CD image included on " +#~ "the stick, use the installer images found in the hd-media directory. Either the easy way or the " +#~ "flexible way can be used to copy the image to the USB " +#~ "stick. For this installation method you will also need to download a CD " +#~ "image. The installation image and the CD image must be based on the same " +#~ "release of &d-i;. If they do not match you are likely to get " +#~ "errors The error message that is most likely to be " +#~ "displayed is that no kernel modules can be found. This means that the " +#~ "version of the kernel module udebs included on the CD image is different " +#~ "from the version of the running kernel. during the " +#~ "installation." +#~ msgstr "" +#~ "内部にある CD イメージからパッケージをインストールする USB メモリを用意す" +#~ "るには、hd-media ディレクトリにあるインストーライメー" +#~ "ジを使用してください。このイメージを USB メモリにコピーするには、簡" +#~ "単な方法 でも 柔軟な方法 でもかまいません。このイン" +#~ "ストール法では、CD イメージもダウンロードする必要があるでしょう。インス" +#~ "トールイメージと CD イメージは &d-i; の同じリリースのものでなければなりま" +#~ "せん。同じものを使用しないと、おそらくインストール中にエラーになるでしょう" +#~ " もっとも起こりそうなエラーは、カーネルモジュールが見つか" +#~ "らないというものです。これは、CD イメージにあるカーネルモジュール udeb の" +#~ "バージョンが、実行中のカーネルのバージョンと異なることを表しています。 。" + +#~ msgid "Copying the files — the easy way" +#~ msgstr "ファイルのコピー — 簡単な方法" + +#~ msgid "" +#~ "If your system refuses to boot from the memory stick, the stick may " +#~ "contain an invalid master boot record (MBR). To fix this, use the " +#~ "install-mbr command from the package mbr:" +#~ msgstr "" +#~ "システムが USB メモリから起動できなければ、 この USB メモリには無効なマス" +#~ "ターブートレコード (MBR) があります。 これを修正するために、" +#~ "mbr パッケージの install-mbr コ" +#~ "マンドを次のように実行してください。" + +#~ msgid "# install-mbr /dev/sdX" +#~ msgstr "# install-mbr /dev/sdX" + #~ msgid "The installer cannot boot from files on an NTFS file system." #~ msgstr "インストーラは NTFS ファイルシステムからは起動できません。" diff --git a/po/ja/installation-howto.po b/po/ja/installation-howto.po index 1ebf8bb73..d9d7f62b7 100644 --- a/po/ja/installation-howto.po +++ b/po/ja/installation-howto.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: 2010-12-30 23:50+0900\n" "Last-Translator: KURASAWA Nozomu \n" "Language-Team: Japanese \n" @@ -252,6 +252,17 @@ msgstr "" #: installation-howto.xml:138 #, no-c-format msgid "" +"The easiest way to prepare your USB memory stick is to download any Debian " +"CD or DVD image that will fit on it, and write the CD image directly to the " +"memory stick. Of course this will destroy anything already on the memory " +"stick. This works because Debian CD images are \"isohybrid\" images that can " +"boot both from CD and from USB drives." +msgstr "" + +#. Tag: para +#: installation-howto.xml:146 +#, no-c-format +msgid "" "The easiest way to prepare your USB memory stick is to download hd-" "media/boot.img.gz, and use gunzip to extract the 256 MB image " "from that file. Write this image directly to your memory stick, which must " @@ -271,7 +282,7 @@ msgstr "" ".iso で終わりさえすれば、どんなファイル名でも大丈夫です。" #. Tag: para -#: installation-howto.xml:149 +#: installation-howto.xml:157 #, no-c-format msgid "" "There are other, more flexible ways to set up a memory stick to use the " @@ -283,7 +294,7 @@ msgstr "" "をご覧ください。" #. Tag: para -#: installation-howto.xml:155 +#: installation-howto.xml:163 #, no-c-format msgid "" "Some BIOSes can boot USB storage directly, and some cannot. You may need to " @@ -298,7 +309,7 @@ msgstr "" "\"/>をご覧ください。" #. Tag: para -#: installation-howto.xml:162 +#: installation-howto.xml:170 #, no-c-format msgid "" "Booting Macintosh systems from USB storage devices involves manual use of " @@ -308,13 +319,13 @@ msgstr "" "を必要とします。方法は、をご覧ください。" #. Tag: title -#: installation-howto.xml:171 +#: installation-howto.xml:179 #, no-c-format msgid "Booting from network" msgstr "ネットワークからの起動" #. Tag: para -#: installation-howto.xml:172 +#: installation-howto.xml:180 #, no-c-format msgid "" "It's also possible to boot &d-i; completely from the net. The various " @@ -326,7 +337,7 @@ msgstr "" "filename> 以下のファイルは、&d-i; を netboot するために使用できます。" #. Tag: para -#: installation-howto.xml:178 +#: installation-howto.xml:186 #, no-c-format msgid "" "The easiest thing to set up is probably PXE netbooting. Untar the file " @@ -344,13 +355,13 @@ msgstr "" "linkend=\"install-tftp\"/>をご覧ください。" #. Tag: title -#: installation-howto.xml:192 +#: installation-howto.xml:200 #, no-c-format msgid "Booting from hard disk" msgstr "ハードディスクからの起動" #. Tag: para -#: installation-howto.xml:193 +#: installation-howto.xml:201 #, no-c-format msgid "" "It's possible to boot the installer using no removable media, but just an " @@ -372,13 +383,13 @@ msgstr "" "を説明しています。" #. Tag: title -#: installation-howto.xml:210 +#: installation-howto.xml:218 #, no-c-format msgid "Installation" msgstr "インストール" #. Tag: para -#: installation-howto.xml:211 +#: installation-howto.xml:219 #, no-c-format msgid "" "Once the installer starts, you will be greeted with an initial screen. Press " @@ -390,7 +401,7 @@ msgstr "" "(をご覧ください)。" #. Tag: para -#: installation-howto.xml:217 +#: installation-howto.xml:225 #, no-c-format msgid "" "After a while you will be asked to select your language. Use the arrow keys " @@ -405,7 +416,7 @@ msgstr "" "合は、世界中のすべての国のリストから選択できます。" #. Tag: para -#: installation-howto.xml:225 +#: installation-howto.xml:233 #, no-c-format msgid "" "You may be asked to confirm your keyboard layout. Choose the default unless " @@ -415,7 +426,7 @@ msgstr "" "ければ、デフォルトを選択してください。" #. Tag: para -#: installation-howto.xml:230 +#: installation-howto.xml:238 #, no-c-format msgid "" "Now sit back while debian-installer detects some of your hardware, and loads " @@ -425,7 +436,7 @@ msgstr "" "などからインストーラの残りの部分をロードする間、くつろいでいてください。" #. Tag: para -#: installation-howto.xml:235 +#: installation-howto.xml:243 #, no-c-format msgid "" "Next the installer will try to detect your network hardware and set up " @@ -437,7 +448,7 @@ msgstr "" "ワークを手動で設定する機会が与えられます。" #. Tag: para -#: installation-howto.xml:241 +#: installation-howto.xml:249 #, no-c-format msgid "" "The next step is setting up your clock and time zone. The installer will try " @@ -451,7 +462,7 @@ msgstr "" "のみ問い合わせてきます。" #. Tag: para -#: installation-howto.xml:248 +#: installation-howto.xml:256 #, no-c-format msgid "" "Now it is time to partition your disks. First you will be given the " @@ -467,7 +478,7 @@ msgstr "" "手動 を選んでください。" #. Tag: para -#: installation-howto.xml:256 +#: installation-howto.xml:264 #, no-c-format msgid "" "If you have an existing DOS or Windows partition that you want to preserve, " @@ -483,7 +494,7 @@ msgstr "" "を指定してください。" #. Tag: para -#: installation-howto.xml:263 +#: installation-howto.xml:271 #, no-c-format msgid "" "On the next screen you will see your partition table, how the partitions " @@ -508,7 +519,7 @@ msgstr "" "割に関するもっと多くの情報があります。" #. Tag: para -#: installation-howto.xml:276 +#: installation-howto.xml:284 #, no-c-format msgid "" "Now &d-i; formats your partitions and starts to install the base system, " @@ -519,7 +530,7 @@ msgstr "" "す。" #. Tag: para -#: installation-howto.xml:281 +#: installation-howto.xml:289 #, no-c-format msgid "" "The base system that was installed earlier is a working, but very minimal " @@ -543,7 +554,7 @@ msgstr "" " をご覧ください。" #. Tag: para -#: installation-howto.xml:293 +#: installation-howto.xml:301 #, no-c-format msgid "" "Installation of the base system is followed by setting up user accounts. By " @@ -556,7 +567,7 @@ msgstr "" "ザのアカウントを 1 つ作成することになります。" #. Tag: para -#: installation-howto.xml:300 +#: installation-howto.xml:308 #, no-c-format msgid "" "The last step is to install a boot loader. If the installer detects other " @@ -573,7 +584,7 @@ msgstr "" "その選択を無効にして他の場所にインストールする機会が与えられます。" #. Tag: para -#: installation-howto.xml:310 +#: installation-howto.xml:318 #, no-c-format msgid "" "&d-i; will now tell you that the installation has finished. Remove the cdrom " @@ -587,7 +598,7 @@ msgstr "" "linkend=\"boot-new\"/> で説明しています。" #. Tag: para -#: installation-howto.xml:317 +#: installation-howto.xml:325 #, no-c-format msgid "" "If you need more information on the install process, see をご覧ください。" #. Tag: title -#: installation-howto.xml:326 +#: installation-howto.xml:334 #, no-c-format msgid "Send us an installation report" msgstr "インストールレポートを送ってください" #. Tag: para -#: installation-howto.xml:327 +#: installation-howto.xml:335 #, no-c-format msgid "" "If you successfully managed an installation with &d-i;, please take time to " @@ -620,7 +631,7 @@ msgstr "" "法です。" #. Tag: para -#: installation-howto.xml:337 +#: installation-howto.xml:345 #, no-c-format msgid "" "If you did not complete the install, you probably found a bug in debian-" @@ -636,13 +647,13 @@ msgstr "" "は、をご覧ください。" #. Tag: title -#: installation-howto.xml:349 +#: installation-howto.xml:357 #, no-c-format msgid "And finally…" msgstr "そして最後に…" #. Tag: para -#: installation-howto.xml:350 +#: installation-howto.xml:358 #, no-c-format msgid "" "We hope that your &debian; installation is pleasant and that you find " diff --git a/po/ja/preseed.po b/po/ja/preseed.po index 7d53297b5..ade460c3d 100644 --- a/po/ja/preseed.po +++ b/po/ja/preseed.po @@ -3,8 +3,8 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" -"PO-Revision-Date: 2010-12-30 23:45+0900\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" +"PO-Revision-Date: 2011-05-15 10:06+0900\n" "Last-Translator: KURASAWA Nozomu \n" "Language-Team: Japanese \n" "Language: ja\n" @@ -31,7 +31,7 @@ msgstr "" "トールを自動化するものです。" #. Tag: para -#: preseed.xml:23 preseed.xml:676 +#: preseed.xml:23 preseed.xml:677 #, no-c-format msgid "" "The configuration fragments used in this appendix are also available as an " @@ -116,7 +116,7 @@ msgid "initrd" msgstr "initrd" #. Tag: entry -#: preseed.xml:70 preseed.xml:523 +#: preseed.xml:70 preseed.xml:524 #, no-c-format msgid "file" msgstr "ファイル" @@ -409,23 +409,30 @@ msgstr "" #. Tag: para #: preseed.xml:285 #, no-c-format +#| msgid "" +#| "Note that preseed/url can be shortened to just " +#| "url and preseed/file to just " +#| "file when they are passed as boot parameters." msgid "" "Note that preseed/url can be shortened to just " -"url and preseed/file to just " -"file when they are passed as boot parameters." +"url, preseed/file to just " +"file and preseed/file/checksum to " +"just preseed-md5 when they are passed as boot " +"parameters." msgstr "" "ブートパラメータに渡す際に、preseed/url は " "url に、preseed/file は " -"file に短縮できることに注意してください。" +"file に、preseed/file/checksum は " +"preseed-md5 に短縮できることに注意してください。" #. Tag: title -#: preseed.xml:295 +#: preseed.xml:296 #, no-c-format msgid "Using boot parameters to preseed questions" msgstr "preseed が質問するブートパラメータの利用" #. Tag: para -#: preseed.xml:296 +#: preseed.xml:297 #, no-c-format msgid "" "If a preconfiguration file cannot be used to preseed some steps, the install " @@ -436,7 +443,7 @@ msgstr "" "ストーラ起動時のコマンドラインに与えることで、インストールを自動で行えます。" #. Tag: para -#: preseed.xml:302 +#: preseed.xml:303 #, no-c-format msgid "" "Boot parameters can also be used if you do not really want to use " @@ -447,7 +454,7 @@ msgstr "" "使用します。有用な使用法のサンプルが、このマニュアルの別の場所にあります。" #. Tag: para -#: preseed.xml:308 +#: preseed.xml:309 #, no-c-format msgid "" "To set a value to be used inside &d-i;, just pass " @@ -482,7 +489,7 @@ msgstr "" "ベースにコピーされず、関連パッケージの設定中使用されません。" #. Tag: para -#: preseed.xml:331 +#: preseed.xml:332 #, no-c-format msgid "" "Normally, preseeding a question in this way will mean that the question will " @@ -496,7 +503,7 @@ msgstr "" "seenflag\"/> もご覧ください。" #. Tag: para -#: preseed.xml:338 +#: preseed.xml:339 #, no-c-format msgid "" "Note that some variables that are frequently set at the boot prompt have a " @@ -513,7 +520,7 @@ msgstr "" "スがあり、これは tasksel:tasksel/first に変換されます。" #. Tag: para -#: preseed.xml:347 +#: preseed.xml:348 #, no-c-format msgid "" "A -- in the boot options has special meaning. Kernel " @@ -529,7 +536,7 @@ msgstr "" "タをかけます。" #. Tag: para -#: preseed.xml:356 +#: preseed.xml:357 #, no-c-format msgid "" "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line " @@ -543,7 +550,7 @@ msgstr "" "ます (以前のカーネルではこの数字がもっと少ないです)。" #. Tag: para -#: preseed.xml:364 +#: preseed.xml:365 #, no-c-format msgid "" "For most installations some of the default options in your bootloader " @@ -555,7 +562,7 @@ msgstr "" "るかもしれません。これにより preseed 用にもっとオプションを追加できます。" #. Tag: para -#: preseed.xml:371 +#: preseed.xml:372 #, no-c-format msgid "" "It may not always be possible to specify values with spaces for boot " @@ -565,13 +572,13 @@ msgstr "" "うまくいくとは限りません。" #. Tag: title -#: preseed.xml:380 +#: preseed.xml:381 #, no-c-format msgid "Auto mode" msgstr "自動モード" #. Tag: para -#: preseed.xml:381 +#: preseed.xml:382 #, no-c-format msgid "" "There are several features of &debian; Installer that combine to allow " @@ -600,7 +607,7 @@ msgstr "" "を取得するようになります。" #. Tag: para -#: preseed.xml:398 +#: preseed.xml:399 #, no-c-format msgid "" "The last part of that url (d-i/&releasename;/./preseed.cfg からファイルを取得します。" #. Tag: para -#: preseed.xml:418 +#: preseed.xml:419 #, no-c-format msgid "" "If there is no local DHCP or DNS infrastructure, or if you do not want to " @@ -658,13 +665,13 @@ msgstr "" " この方法は次のように動作します。" #. Tag: para -#: preseed.xml:431 +#: preseed.xml:432 #, no-c-format msgid "if the URL is missing a protocol, http is assumed," msgstr "URL が見つからない場合、http だと仮定します。" #. Tag: para -#: preseed.xml:434 +#: preseed.xml:435 #, no-c-format msgid "" "if the hostname section contains no periods, it has the domain derived from " @@ -673,7 +680,7 @@ msgstr "" "ホスト名セクションにピリオドがなければ、DHCP から引き出して追加します。" #. Tag: para -#: preseed.xml:438 +#: preseed.xml:439 #, no-c-format msgid "" "if there's no /'s after the hostname, then the default " @@ -682,7 +689,7 @@ msgstr "" "ホスト名の後に / がなければ、デフォルトパスを追加します。" #. Tag: para -#: preseed.xml:444 +#: preseed.xml:445 #, no-c-format msgid "" "In addition to specifying the url, you can also specify settings that do not " @@ -707,7 +714,7 @@ msgstr "" "ステムのタイプや、地域化を指定するのに使用できます。" #. Tag: para -#: preseed.xml:458 +#: preseed.xml:459 #, no-c-format msgid "" "It is of course possible to extend this concept, and if you do, it is " @@ -726,7 +733,7 @@ msgstr "" "す。" #. Tag: para -#: preseed.xml:468 +#: preseed.xml:469 #, no-c-format msgid "" "The auto boot label is not yet defined everywhere. The " @@ -749,7 +756,7 @@ msgstr "" "literal> に設定すると、優先度の低い質問を抑制するようになります。" #. Tag: para -#: preseed.xml:482 +#: preseed.xml:483 #, no-c-format msgid "" "Additional options that may be of interest while attempting to automate an " @@ -763,7 +770,7 @@ msgstr "" "待つようになります。" #. Tag: para -#: preseed.xml:491 +#: preseed.xml:492 #, no-c-format msgid "" "An extensive example of how to use this framework, including example scripts " @@ -778,13 +785,13 @@ msgstr "" "たくさんのすばらしい効果があります。" #. Tag: title -#: preseed.xml:502 +#: preseed.xml:503 #, no-c-format msgid "Aliases useful with preseeding" msgstr "preseed で利用できるエイリアス" #. Tag: para -#: preseed.xml:503 +#: preseed.xml:504 #, no-c-format msgid "" "The following aliases can be useful when using (auto mode) preseeding. Note " @@ -798,175 +805,175 @@ msgstr "" "interface=eth0 のようにです。" #. Tag: entry -#: preseed.xml:516 +#: preseed.xml:517 #, no-c-format msgid "auto" msgstr "auto" #. Tag: entry -#: preseed.xml:516 +#: preseed.xml:517 #, no-c-format msgid "auto-install/enable" msgstr "auto-install/enable" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:518 #, no-c-format msgid "classes" msgstr "classes" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:518 #, no-c-format msgid "auto-install/classes" msgstr "auto-install/classes" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:519 #, no-c-format msgid "fb" msgstr "fb" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:519 #, no-c-format msgid "debian-installer/framebuffer" msgstr "debian-installer/framebuffer" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:520 #, no-c-format msgid "language" msgstr "language" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:520 #, no-c-format msgid "debian-installer/language" msgstr "debian-installer/language" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:521 #, no-c-format msgid "country" msgstr "country" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:521 #, no-c-format msgid "debian-installer/country" msgstr "debian-installer/country" #. Tag: entry -#: preseed.xml:521 +#: preseed.xml:522 #, no-c-format msgid "locale" msgstr "locale" #. Tag: entry -#: preseed.xml:521 +#: preseed.xml:522 #, no-c-format msgid "debian-installer/locale" msgstr "debian-installer/locale" #. Tag: entry -#: preseed.xml:522 +#: preseed.xml:523 #, no-c-format msgid "priority" msgstr "priority" #. Tag: entry -#: preseed.xml:522 +#: preseed.xml:523 #, no-c-format msgid "debconf/priority" msgstr "debconf/priority" #. Tag: entry -#: preseed.xml:523 +#: preseed.xml:524 #, no-c-format msgid "preseed/file" msgstr "preseed/file" #. Tag: entry -#: preseed.xml:524 +#: preseed.xml:525 #, no-c-format msgid "url" msgstr "url" #. Tag: entry -#: preseed.xml:524 +#: preseed.xml:525 #, no-c-format msgid "preseed/url" msgstr "preseed/url" #. Tag: entry -#: preseed.xml:525 +#: preseed.xml:526 #, no-c-format msgid "interface" msgstr "interface" #. Tag: entry -#: preseed.xml:525 +#: preseed.xml:526 #, no-c-format msgid "netcfg/choose_interface" msgstr "netcfg/choose_interface" #. Tag: entry -#: preseed.xml:526 +#: preseed.xml:527 #, no-c-format msgid "hostname   " msgstr "hostname   " #. Tag: entry -#: preseed.xml:526 +#: preseed.xml:527 #, no-c-format msgid "netcfg/get_hostname" msgstr "netcfg/get_hostname" #. Tag: entry -#: preseed.xml:527 +#: preseed.xml:528 #, no-c-format msgid "domain" msgstr "domain" #. Tag: entry -#: preseed.xml:527 +#: preseed.xml:528 #, no-c-format msgid "netcfg/get_domain" msgstr "netcfg/get_domain" #. Tag: entry -#: preseed.xml:528 +#: preseed.xml:529 #, no-c-format msgid "protocol" msgstr "protocol" #. Tag: entry -#: preseed.xml:528 +#: preseed.xml:529 #, no-c-format msgid "mirror/protocol" msgstr "mirror/protocol" #. Tag: entry -#: preseed.xml:529 +#: preseed.xml:530 #, no-c-format msgid "suite" msgstr "suite" #. Tag: entry -#: preseed.xml:529 +#: preseed.xml:530 #, no-c-format msgid "mirror/suite" msgstr "mirror/suite" #. Tag: title -#: preseed.xml:536 +#: preseed.xml:537 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "事前設定ファイルを指定するための DHCP の利用方法" #. Tag: para -#: preseed.xml:537 +#: preseed.xml:538 #, no-c-format msgid "" "It's also possible to use DHCP to specify a preconfiguration file to " @@ -985,7 +992,7 @@ msgstr "" "です。" #. Tag: screen -#: preseed.xml:548 +#: preseed.xml:549 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -997,7 +1004,7 @@ msgstr "" "}" #. Tag: para -#: preseed.xml:550 +#: preseed.xml:551 #, no-c-format msgid "" "Note that the above example limits this filename to DHCP clients that " @@ -1011,7 +1018,7 @@ msgstr "" "ンストールするのではなく、特定のホストに対して行うようにもできます。" #. Tag: para -#: preseed.xml:557 +#: preseed.xml:558 #, no-c-format msgid "" "A good way to use the DHCP preseeding is to only preseed values specific to " @@ -1027,13 +1034,13 @@ msgstr "" "&debian; の完全自動インストールは、充分注意しなければ行うべきではありません。" #. Tag: title -#: preseed.xml:571 +#: preseed.xml:572 #, no-c-format msgid "Creating a preconfiguration file" msgstr "事前設定ファイルの作成" #. Tag: para -#: preseed.xml:572 +#: preseed.xml:573 #, no-c-format msgid "" "The preconfiguration file is in the format used by the debconf-set-" @@ -1045,13 +1052,13 @@ msgstr "" "トは以下のようになります。" #. Tag: screen -#: preseed.xml:578 +#: preseed.xml:579 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "<所有者> <質問名> <質問タイプ> <値>" #. Tag: para -#: preseed.xml:580 +#: preseed.xml:581 #, no-c-format msgid "" "There are a few rules to keep in mind when writing a preconfiguration file." @@ -1060,7 +1067,7 @@ msgstr "" "ださい" #. Tag: para -#: preseed.xml:587 +#: preseed.xml:588 #, no-c-format msgid "" "Put only a single space or tab between type and value: any additional " @@ -1071,7 +1078,7 @@ msgstr "" "したままにしてください。" #. Tag: para -#: preseed.xml:591 +#: preseed.xml:592 #, no-c-format msgid "" "A line can be split into multiple lines by appending a backslash " @@ -1086,7 +1093,7 @@ msgstr "" "て、サポートしていません。" #. Tag: para -#: preseed.xml:598 +#: preseed.xml:599 #, no-c-format msgid "" "For debconf variables (templates) used in the installer itself, the owner " @@ -1103,7 +1110,7 @@ msgstr "" "トールしたシステムの debconf データベースに伝播させます。" #. Tag: para -#: preseed.xml:606 +#: preseed.xml:607 #, no-c-format msgid "" "Most questions need to be preseeded using the values valid in English and " @@ -1114,7 +1121,7 @@ msgstr "" "(partman など) 訳した値を使用できる質問もあります。" #. Tag: para -#: preseed.xml:612 +#: preseed.xml:613 #, no-c-format msgid "" "Some questions take a code as value instead of the English text that is " @@ -1124,7 +1131,7 @@ msgstr "" "るものがあります。" #. Tag: para -#: preseed.xml:618 +#: preseed.xml:619 #, no-c-format msgid "" "The easiest way to create a preconfiguration file is to use the example file " @@ -1134,7 +1141,7 @@ msgstr "" "にあるサンプルファイルを元にして作業することです。" #. Tag: para -#: preseed.xml:623 +#: preseed.xml:624 #, no-c-format msgid "" "An alternative method is to do a manual installation and then, after " @@ -1148,7 +1155,7 @@ msgstr "" "を 1 ファイルに出力してください。" #. Tag: screen -#: preseed.xml:630 +#: preseed.xml:631 #, no-c-format msgid "" "$ debconf-get-selections --installer > file\n" @@ -1158,7 +1165,7 @@ msgstr "" "$ debconf-get-selections >> file" #. Tag: para -#: preseed.xml:632 +#: preseed.xml:633 #, no-c-format msgid "" "However, a file generated in this manner will have some items that should " @@ -1169,7 +1176,7 @@ msgstr "" "どのユーザはサンプルファイルから始めるのがよいでしょう。" #. Tag: para -#: preseed.xml:640 +#: preseed.xml:641 #, no-c-format msgid "" "This method relies on the fact that, at the end of the installation, the " @@ -1184,7 +1191,7 @@ msgstr "" "デフォルトでは root にのみ読み込みが許可されています。" #. Tag: para -#: preseed.xml:648 +#: preseed.xml:649 #, no-c-format msgid "" "The directory /var/log/installer and all files in it " @@ -1196,7 +1203,7 @@ msgstr "" "除されます。" #. Tag: para -#: preseed.xml:656 +#: preseed.xml:657 #, no-c-format msgid "" "To check possible values for questions, you can use nano " @@ -1212,7 +1219,7 @@ msgstr "" "い。" #. Tag: para -#: preseed.xml:664 +#: preseed.xml:665 #, no-c-format msgid "" "To check if the format of your preconfiguration file is valid before " @@ -1224,13 +1231,13 @@ msgstr "" "replaceable> が使えます。" #. Tag: title -#: preseed.xml:675 +#: preseed.xml:676 #, no-c-format msgid "Contents of the preconfiguration file (for &releasename;)" msgstr "事前設定ファイルの内容 (&releasename; 用)" #. Tag: para -#: preseed.xml:681 +#: preseed.xml:682 #, no-c-format msgid "" "Note that this example is based on an installation for the Intel x86 " @@ -1245,7 +1252,7 @@ msgstr "" "のアーキテクチャ用に適切な debconf 設定で置き換える必要があるでしょう。" #. Tag: para -#: preseed.xml:689 +#: preseed.xml:690 #, no-c-format msgid "" "Details on how the different Debian Installer components actually work can " @@ -1255,13 +1262,13 @@ msgstr "" "詳細は、 にあります。" #. Tag: title -#: preseed.xml:697 +#: preseed.xml:698 #, no-c-format msgid "Localization" msgstr "地域化" #. Tag: para -#: preseed.xml:698 +#: preseed.xml:699 #, no-c-format msgid "" "Setting localization values will only work if you are using initrd " @@ -1272,7 +1279,7 @@ msgstr "" "の方法では、この質問をされた後にしか事前設定ファイルを読み込めません。" #. Tag: para -#: preseed.xml:704 +#: preseed.xml:705 #, no-c-format msgid "" "The locale can be used to specify both language and country and can be any " @@ -1289,7 +1296,7 @@ msgstr "" "replaceable> としてください。" #. Tag: para -#: preseed.xml:713 +#: preseed.xml:714 #, no-c-format msgid "" "Although this method is very easy to use, it does not allow preseeding of " @@ -1310,8 +1317,18 @@ msgstr "" "ブートパラメータで指定できます。" #. Tag: screen -#: preseed.xml:728 -#, no-c-format +#: preseed.xml:729 +#, no-c-format +#| msgid "" +#| "# Preseeding only locale sets language, country and locale.\n" +#| "d-i debian-installer/locale string en_US\n" +#| "\n" +#| "# The values can also be preseeded individually for greater flexibility.\n" +#| "#d-i debian-installer/language string en\n" +#| "#d-i debian-installer/country string NL\n" +#| "#d-i debian-installer/locale string en_GB.UTF-8\n" +#| "# Optionally specify additional locales to be generated.\n" +#| "#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" msgid "" "# Preseeding only locale sets language, country and locale.\n" "d-i debian-installer/locale string en_US\n" @@ -1321,7 +1338,7 @@ msgid "" "#d-i debian-installer/country string NL\n" "#d-i debian-installer/locale string en_GB.UTF-8\n" "# Optionally specify additional locales to be generated.\n" -"#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" +"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8" msgstr "" "# Preseeding only locale sets language, country and locale.\n" "d-i debian-installer/locale string en_US\n" @@ -1331,10 +1348,10 @@ msgstr "" "#d-i debian-installer/country string NL\n" "#d-i debian-installer/locale string en_GB.UTF-8\n" "# Optionally specify additional locales to be generated.\n" -"#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" +"#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8" #. Tag: para -#: preseed.xml:730 +#: preseed.xml:731 #, no-c-format msgid "" "Keyboard configuration consists of selecting a keyboard architecture and a " @@ -1348,23 +1365,33 @@ msgstr "" "キーボードアーキテクチャ向けに、&d-i; で有効でなくてはなりません。" #. Tag: screen -#: preseed.xml:737 +#: preseed.xml:738 #, no-c-format +#| msgid "" +#| "# Keyboard selection.\n" +#| "#d-i console-tools/archs select at\n" +#| "d-i console-keymaps-at/keymap select us\n" +#| "# Example for a different keyboard architecture\n" +#| "#d-i console-keymaps-usb/keymap select mac-usb-us" msgid "" "# Keyboard selection.\n" "#d-i console-tools/archs select at\n" -"d-i console-keymaps-at/keymap select us\n" +"# keymap is an alias for console-keymaps-at\n" +"d-i keymap select us\n" +"d-i keyboard-configuration/xkb-keymap select us\n" "# Example for a different keyboard architecture\n" "#d-i console-keymaps-usb/keymap select mac-usb-us" msgstr "" "# Keyboard selection.\n" "#d-i console-tools/archs select at\n" -"d-i console-keymaps-at/keymap select us\n" +"# keymap is an alias for console-keymaps-at\n" +"d-i keymap select us\n" +"d-i keyboard-configuration/xkb-keymap select us\n" "# Example for a different keyboard architecture\n" "#d-i console-keymaps-usb/keymap select mac-usb-us" #. Tag: para -#: preseed.xml:739 +#: preseed.xml:740 #, no-c-format msgid "" "To skip keyboard configuration, preseed console-tools/archs のようにブートパラメータを使用してください。" #. Tag: para -#: preseed.xml:773 +#: preseed.xml:774 #, no-c-format msgid "" "Although preseeding the network configuration is normally not possible when " @@ -1440,19 +1467,19 @@ msgstr "" "というものです。" #. Tag: screen -#: preseed.xml:783 +#: preseed.xml:784 #, no-c-format msgid "killall.sh; netcfg" msgstr "killall.sh; netcfg" #. Tag: para -#: preseed.xml:785 +#: preseed.xml:786 #, no-c-format msgid "The following debconf variables are relevant for network configuration." msgstr "以下の debconf 変数は、ネットワークの設定と関係があります。" #. Tag: screen -#: preseed.xml:791 +#: preseed.xml:792 #, no-c-format msgid "" "# Disable network configuration entirely. This is useful for cdrom\n" @@ -1554,7 +1581,7 @@ msgstr "" "#d-i hw-detect/load_firmware boolean true" #. Tag: para -#: preseed.xml:793 +#: preseed.xml:794 #, no-c-format msgid "" "Please note that netcfg will automatically determine the " @@ -1575,13 +1602,13 @@ msgstr "" "できます。" #. Tag: title -#: preseed.xml:809 +#: preseed.xml:810 #, no-c-format msgid "Network console" msgstr "ネットワークコンソール" #. Tag: screen -#: preseed.xml:811 +#: preseed.xml:812 #, no-c-format msgid "" "# Use the following settings if you wish to make use of the network-console\n" @@ -1599,13 +1626,13 @@ msgstr "" "#d-i network-console/password-again password r00tme" #. Tag: title -#: preseed.xml:816 +#: preseed.xml:817 #, no-c-format msgid "Mirror settings" msgstr "ミラーサイト設定" #. Tag: para -#: preseed.xml:817 +#: preseed.xml:818 #, no-c-format msgid "" "Depending on the installation method you use, a mirror may be used to " @@ -1619,7 +1646,7 @@ msgstr "" "できます。" #. Tag: para -#: preseed.xml:824 +#: preseed.xml:825 #, no-c-format msgid "" "The parameter mirror/suite determines the suite for " @@ -1629,7 +1656,7 @@ msgstr "" "用の組を設定します。" #. Tag: para -#: preseed.xml:829 +#: preseed.xml:830 #, no-c-format msgid "" "The parameter mirror/udeb/suite determines the suite " @@ -1646,7 +1673,7 @@ msgstr "" "トーラは、自動的に正しい値を設定しますので、設定する必要はありません。" #. Tag: screen -#: preseed.xml:840 +#: preseed.xml:841 #, no-c-format msgid "" "# If you select ftp, the mirror/country string does not need to be set.\n" @@ -1674,13 +1701,13 @@ msgstr "" "#d-i mirror/udeb/suite string testing" #. Tag: title -#: preseed.xml:845 +#: preseed.xml:846 #, no-c-format msgid "Account setup" msgstr "アカウント設定" #. Tag: para -#: preseed.xml:846 +#: preseed.xml:847 #, no-c-format msgid "" "The password for the root account and name and password for a first regular " @@ -1692,7 +1719,7 @@ msgstr "" "どちらかを使用できます。" #. Tag: para -#: preseed.xml:853 +#: preseed.xml:854 #, no-c-format msgid "" "Be aware that preseeding passwords is not completely secure as everyone with " @@ -1708,7 +1735,7 @@ msgstr "" "ん。" #. Tag: screen -#: preseed.xml:863 +#: preseed.xml:864 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -1766,7 +1793,7 @@ msgstr "" "#d-i passwd/user-default-groups string audio cdrom video" #. Tag: para -#: preseed.xml:865 +#: preseed.xml:866 #, no-c-format msgid "" "The passwd/root-password-crypted and " @@ -1785,7 +1812,7 @@ msgstr "" "利です。" #. Tag: para -#: preseed.xml:875 +#: preseed.xml:876 #, no-c-format msgid "" "The following command can be used to generate an MD5 hash for a password:" @@ -1793,19 +1820,19 @@ msgstr "" "以下のコマンドを、パスワードの MD5 ハッシュを生成するのに利用できます。" #. Tag: screen -#: preseed.xml:879 +#: preseed.xml:880 #, no-c-format msgid "$ printf \"r00tme\" | mkpasswd -s -m md5" msgstr "$ printf \"r00tme\" | mkpasswd -s -m md5" #. Tag: title -#: preseed.xml:885 +#: preseed.xml:886 #, no-c-format msgid "Clock and time zone setup" msgstr "時計と時間帯の設定" #. Tag: screen -#: preseed.xml:887 +#: preseed.xml:888 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -1833,13 +1860,13 @@ msgstr "" "#d-i clock-setup/ntp-server string ntp.example.com" #. Tag: title -#: preseed.xml:892 +#: preseed.xml:893 #, no-c-format msgid "Partitioning" msgstr "パーティション分割" #. Tag: para -#: preseed.xml:893 +#: preseed.xml:894 #, no-c-format msgid "" "Using preseeding to partition the harddisk is limited to what is supported " @@ -1855,7 +1882,7 @@ msgstr "" "スタムレシピ、事前設定ファイルに書いたレシピから選択できます。" #. Tag: para -#: preseed.xml:901 +#: preseed.xml:902 #, no-c-format msgid "" "Preseeding of advanced partition setups using RAID, LVM and encryption is " @@ -1867,7 +1894,7 @@ msgstr "" "な、完全な柔軟性があるわけではありません。" #. Tag: para -#: preseed.xml:907 +#: preseed.xml:908 #, no-c-format msgid "" "The examples below only provide basic information on the use of recipes. For " @@ -1887,7 +1914,7 @@ msgstr "" "してください。" #. Tag: para -#: preseed.xml:921 +#: preseed.xml:922 #, no-c-format msgid "" "The identification of disks is dependent on the order in which their drivers " @@ -1899,13 +1926,13 @@ msgstr "" "なければなりません。" #. Tag: title -#: preseed.xml:930 +#: preseed.xml:931 #, no-c-format msgid "Partitioning example" msgstr "パーティション分割の例" #. Tag: screen -#: preseed.xml:932 +#: preseed.xml:933 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -2055,13 +2082,13 @@ msgstr "" "d-i partman/confirm_nooverwrite boolean true" #. Tag: title -#: preseed.xml:936 +#: preseed.xml:937 #, no-c-format msgid "Partitioning using RAID" msgstr "RAID を用いたパーティション分割" #. Tag: para -#: preseed.xml:937 +#: preseed.xml:938 #, no-c-format msgid "" "You can also use preseeding to set up partitions on software RAID arrays. " @@ -2073,7 +2100,7 @@ msgstr "" "成、スペアデバイスの指定です。" #. Tag: para -#: preseed.xml:943 +#: preseed.xml:944 #, no-c-format msgid "" "If you are using RAID 1, you can preseed grub to install to all devices used " @@ -2083,7 +2110,7 @@ msgstr "" "preseed で探せます。 をご覧ください。" #. Tag: para -#: preseed.xml:950 +#: preseed.xml:951 #, no-c-format msgid "" "This type of automated partitioning is easy to get wrong. It is also " @@ -2099,7 +2126,7 @@ msgstr "" "い。" #. Tag: screen -#: preseed.xml:960 +#: preseed.xml:961 #, no-c-format msgid "" "# The method should be set to \"raid\".\n" @@ -2203,13 +2230,13 @@ msgstr "" "d-i partman/confirm_nooverwrite boolean true" #. Tag: title -#: preseed.xml:965 +#: preseed.xml:966 #, no-c-format msgid "Controlling how partitions are mounted" msgstr "パーティションマウント法の制御" #. Tag: para -#: preseed.xml:966 +#: preseed.xml:967 #, no-c-format msgid "" "Normally, filesystems are mounted using a universally unique identifier " @@ -2227,7 +2254,7 @@ msgstr "" "マウントされます。" #. Tag: para -#: preseed.xml:975 +#: preseed.xml:976 #, no-c-format msgid "" "Devices with stable names, such as LVM logical volumes, will continue to use " @@ -2237,7 +2264,7 @@ msgstr "" "され続けます。" #. Tag: para -#: preseed.xml:982 +#: preseed.xml:983 #, no-c-format msgid "" "Traditional device names may change based on the order in which the kernel " @@ -2252,7 +2279,7 @@ msgstr "" "す。こうなってしまうと、起動時の挙動が不定になってしまいます。" #. Tag: screen -#: preseed.xml:992 +#: preseed.xml:993 #, no-c-format msgid "" "# The default is to mount by UUID, but you can also choose \"traditional\" " @@ -2270,13 +2297,13 @@ msgstr "" "#d-i partman/mount_style select uuid" #. Tag: title -#: preseed.xml:998 +#: preseed.xml:999 #, no-c-format msgid "Base system installation" msgstr "基本システムのインストール" #. Tag: para -#: preseed.xml:999 +#: preseed.xml:1000 #, no-c-format msgid "" "There is actually not very much that can be preseeded for this stage of the " @@ -2287,7 +2314,7 @@ msgstr "" "カーネルのインストールに関するものだけです。" #. Tag: screen -#: preseed.xml:1006 +#: preseed.xml:1007 #, no-c-format msgid "" "# Configure APT to not install recommended packages by default. Use of this\n" @@ -2321,13 +2348,13 @@ msgstr "" "#d-i base-installer/kernel/image string &kernelpackage;-2.6-486" #. Tag: title -#: preseed.xml:1011 +#: preseed.xml:1012 #, no-c-format msgid "Apt setup" msgstr "apt 設定" #. Tag: para -#: preseed.xml:1012 +#: preseed.xml:1013 #, no-c-format msgid "" "Setup of the /etc/apt/sources.list and basic " @@ -2340,7 +2367,7 @@ msgstr "" "に、他の (ローカルな) リポジトリを追加できます。" #. Tag: screen -#: preseed.xml:1020 +#: preseed.xml:1021 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -2398,13 +2425,13 @@ msgstr "" "#d-i debian-installer/allow_unauthenticated boolean true" #. Tag: title -#: preseed.xml:1025 +#: preseed.xml:1026 #, no-c-format msgid "Package selection" msgstr "パッケージ選択" #. Tag: para -#: preseed.xml:1026 +#: preseed.xml:1027 #, no-c-format msgid "" "You can choose to install any combination of tasks that are available. " @@ -2414,73 +2441,73 @@ msgstr "" "スクを以下に書き出します。" #. Tag: userinput -#: preseed.xml:1035 +#: preseed.xml:1036 #, no-c-format msgid "standard" msgstr "standard" #. Tag: userinput -#: preseed.xml:1038 +#: preseed.xml:1039 #, no-c-format msgid "desktop" msgstr "desktop" #. Tag: userinput -#: preseed.xml:1041 +#: preseed.xml:1042 #, no-c-format msgid "gnome-desktop" msgstr "gnome-desktop" #. Tag: userinput -#: preseed.xml:1044 +#: preseed.xml:1045 #, no-c-format msgid "kde-desktop" msgstr "kde-desktop" #. Tag: userinput -#: preseed.xml:1047 +#: preseed.xml:1048 #, no-c-format msgid "web-server" msgstr "web-server" #. Tag: userinput -#: preseed.xml:1050 +#: preseed.xml:1051 #, no-c-format msgid "print-server" msgstr "print-server" #. Tag: userinput -#: preseed.xml:1053 +#: preseed.xml:1054 #, no-c-format msgid "dns-server" msgstr "dns-server" #. Tag: userinput -#: preseed.xml:1056 +#: preseed.xml:1057 #, no-c-format msgid "file-server" msgstr "file-server" #. Tag: userinput -#: preseed.xml:1059 +#: preseed.xml:1060 #, no-c-format msgid "mail-server" msgstr "mail-server" #. Tag: userinput -#: preseed.xml:1062 +#: preseed.xml:1063 #, no-c-format msgid "sql-database" msgstr "sql-database" #. Tag: userinput -#: preseed.xml:1065 +#: preseed.xml:1066 #, no-c-format msgid "laptop" msgstr "laptop" #. Tag: para -#: preseed.xml:1069 +#: preseed.xml:1070 #, no-c-format msgid "" "You can also choose to install no tasks, and force the installation of a set " @@ -2492,7 +2519,7 @@ msgstr "" "クは常に含めるのをお勧めします。" #. Tag: para -#: preseed.xml:1075 +#: preseed.xml:1076 #, no-c-format msgid "" "If you want to install some individual packages in addition to packages " @@ -2507,7 +2534,7 @@ msgstr "" "で区切ったパッケージのリストを取れます。" #. Tag: screen -#: preseed.xml:1085 +#: preseed.xml:1086 #, no-c-format msgid "" "#tasksel tasksel/first multiselect standard, web-server\n" @@ -2545,14 +2572,64 @@ msgstr "" "#popularity-contest popularity-contest/participate boolean false" #. Tag: title -#: preseed.xml:1090 +#: preseed.xml:1091 #, no-c-format msgid "Boot loader installation" msgstr "ブートローダのインストール" #. Tag: screen -#: preseed.xml:1092 -#, no-c-format +#: preseed.xml:1093 +#, no-c-format +#| msgid "" +#| "# Grub is the default boot loader (for x86). " +#| "If you want lilo installed\n" +#| "# instead, uncomment this:\n" +#| "#d-i grub-installer/skip boolean true\n" +#| "# To also skip installing lilo, and install no bootloader, uncomment " +#| "this\n" +#| "# too:\n" +#| "#d-i lilo-installer/skip boolean true\n" +#| "# To install no bootloader, " +#| "uncomment this\n" +#| "#d-i grub-installer/skip boolean true\n" +#| "\n" +#| "# With a few exceptions for unusual partitioning setups, GRUB 2 is now " +#| "the\n" +#| "# default. If you need GRUB Legacy for some particular reason, then\n" +#| "# uncomment this:\n" +#| "#d-i grub-installer/grub2_instead_of_grub_legacy boolean false\n" +#| "\n" +#| "# This is fairly safe to set, it makes grub install automatically to the " +#| "MBR\n" +#| "# if no other operating system is detected on the machine.\n" +#| "d-i grub-installer/only_debian boolean true\n" +#| "\n" +#| "# This one makes grub-installer install to the MBR if it also finds some " +#| "other\n" +#| "# OS, which is less safe as it might not be able to boot that other OS.\n" +#| "d-i grub-installer/with_other_os boolean true\n" +#| "\n" +#| "# Alternatively, if you want to install to a location other than the " +#| "mbr,\n" +#| "# uncomment and edit these lines:\n" +#| "#d-i grub-installer/only_debian boolean false\n" +#| "#d-i grub-installer/with_other_os boolean false\n" +#| "#d-i grub-installer/bootdev string (hd0,0)\n" +#| "# To install grub to multiple disks:\n" +#| "#d-i grub-installer/bootdev string (hd0,0) (hd1,0) (hd2,0)\n" +#| "# To install to a particular device:\n" +#| "#d-i grub-installer/bootdev string /dev/sda\n" +#| "\n" +#| "# Optional password for grub, either in clear text\n" +#| "#d-i grub-installer/password password r00tme\n" +#| "#d-i grub-installer/password-again password r00tme\n" +#| "# or encrypted using an MD5 hash, see grub-md5-crypt(8).\n" +#| "#d-i grub-installer/password-crypted password [MD5 hash]\n" +#| "\n" +#| "# Use the following option to add additional boot parameters for the\n" +#| "# installed system (if supported by the bootloader installer).\n" +#| "# Note: options passed to the installer will be added automatically.\n" +#| "#d-i debian-installer/add-kernel-opts string nousb" msgid "" "# Grub is the default boot loader (for x86). If " "you want lilo installed\n" @@ -2565,11 +2642,6 @@ msgid "" "this\n" "#d-i grub-installer/skip boolean true\n" "\n" -"# With a few exceptions for unusual partitioning setups, GRUB 2 is now the\n" -"# default. If you need GRUB Legacy for some particular reason, then\n" -"# uncomment this:\n" -"#d-i grub-installer/grub2_instead_of_grub_legacy boolean false\n" -"\n" "# This is fairly safe to set, it makes grub install automatically to the " "MBR\n" "# if no other operating system is detected on the machine.\n" @@ -2612,11 +2684,6 @@ msgstr "" "this\n" "#d-i grub-installer/skip boolean true\n" "\n" -"# With a few exceptions for unusual partitioning setups, GRUB 2 is now the\n" -"# default. If you need GRUB Legacy for some particular reason, then\n" -"# uncomment this:\n" -"#d-i grub-installer/grub2_instead_of_grub_legacy boolean false\n" -"\n" "# This is fairly safe to set, it makes grub install automatically to the " "MBR\n" "# if no other operating system is detected on the machine.\n" @@ -2649,7 +2716,7 @@ msgstr "" "#d-i debian-installer/add-kernel-opts string nousb" #. Tag: para -#: preseed.xml:1094 +#: preseed.xml:1095 #, no-c-format msgid "" "An MD5 hash for a password for grub can be generated " @@ -2661,13 +2728,13 @@ msgstr "" "\"preseed-account\"/> にあるコマンドを使用して生成します。" #. Tag: title -#: preseed.xml:1104 +#: preseed.xml:1105 #, no-c-format msgid "Finishing up the installation" msgstr "インストールの仕上げ" #. Tag: screen -#: preseed.xml:1106 +#: preseed.xml:1107 #, no-c-format msgid "" "# During installations from serial console, the regular virtual consoles\n" @@ -2707,13 +2774,13 @@ msgstr "" "#d-i debian-installer/exit/poweroff boolean true" #. Tag: title -#: preseed.xml:1111 +#: preseed.xml:1112 #, no-c-format msgid "Preseeding other packages" msgstr "他パッケージの preseed" #. Tag: screen -#: preseed.xml:1113 +#: preseed.xml:1114 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -2733,19 +2800,19 @@ msgstr "" "# debconf-get-selections >> file" #. Tag: title -#: preseed.xml:1120 +#: preseed.xml:1121 #, no-c-format msgid "Advanced options" msgstr "高度なオプション" #. Tag: title -#: preseed.xml:1123 +#: preseed.xml:1124 #, no-c-format msgid "Running custom commands during the installation" msgstr "インストール中のカスタムコマンド実行" #. Tag: para -#: preseed.xml:1124 +#: preseed.xml:1125 #, no-c-format msgid "" "A very powerful and flexible option offered by the preconfiguration tools is " @@ -2755,7 +2822,7 @@ msgstr "" "るといった、とても強力で柔軟なオプションが存在します。" #. Tag: screen -#: preseed.xml:1132 +#: preseed.xml:1133 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -2803,13 +2870,13 @@ msgstr "" "#d-i preseed/late_command string apt-install zsh; in-target chsh -s /bin/zsh" #. Tag: title -#: preseed.xml:1137 +#: preseed.xml:1138 #, no-c-format msgid "Using preseeding to change default values" msgstr "preseed を用いたデフォルト値変更" #. Tag: para -#: preseed.xml:1138 +#: preseed.xml:1139 #, no-c-format msgid "" "It is possible to use preseeding to change the default answer for a " @@ -2835,7 +2902,7 @@ msgstr "" "やデバッグにも便利です。" #. Tag: para -#: preseed.xml:1152 +#: preseed.xml:1153 #, no-c-format msgid "" "Note that the d-i owner should only be used for variables " @@ -2849,7 +2916,7 @@ msgstr "" "linkend=\"preseed-bootparms\"/> の脚注をご覧ください。" #. Tag: para -#: preseed.xml:1159 +#: preseed.xml:1160 #, no-c-format msgid "" "If you are preseeding using boot parameters, you can make the installer ask " @@ -2872,13 +2939,13 @@ msgstr "" "果を及ぼしません。" #. Tag: title -#: preseed.xml:1173 +#: preseed.xml:1174 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "事前設定ファイルのチェーンロード" #. Tag: para -#: preseed.xml:1174 +#: preseed.xml:1175 #, no-c-format msgid "" "It is possible to include other preconfiguration files from a " @@ -2893,7 +2960,7 @@ msgstr "" "確かな設定を指定するという使い方ができます。" #. Tag: screen -#: preseed.xml:1184 +#: preseed.xml:1185 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -2943,7 +3010,7 @@ msgstr "" "#d-i preseed/run string foo.sh" #. Tag: para -#: preseed.xml:1186 +#: preseed.xml:1187 #, no-c-format msgid "" "It is also possible to chainload from the initrd or file preseeding phase, " diff --git a/po/ja/using-d-i.po b/po/ja/using-d-i.po index 53114b832..d3c9e3013 100644 --- a/po/ja/using-d-i.po +++ b/po/ja/using-d-i.po @@ -3,7 +3,7 @@ msgid "" msgstr "" "Project-Id-Version: \n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: 2011-01-28 08:22+0900\n" "Last-Translator: KURASAWA Nozomu \n" "Language-Team: Japanese \n" @@ -1277,13 +1277,13 @@ msgstr "" "etc/network/interfaces を編集して変更できます。" #. Tag: title -#: using-d-i.xml:812 +#: using-d-i.xml:813 #, no-c-format msgid "Configuring the Clock and Time Zone" msgstr "時計とタイムゾーンの設定" #. Tag: para -#: using-d-i.xml:814 +#: using-d-i.xml:815 #, no-c-format msgid "" "The installer will first attempt to connect to a time server on the Internet " @@ -1300,14 +1300,14 @@ msgstr "" "とはできません。" #. Tag: para -#: using-d-i.xml:823 +#: using-d-i.xml:824 #, no-c-format msgid "The installer does not modify the system clock on the s390 platform." msgstr "" "インストーラは、s390 プラットフォームのシステムクロックを修正しません。" #. Tag: para -#: using-d-i.xml:836 +#: using-d-i.xml:837 #, no-c-format msgid "" "Depending on the location selected earlier in the installation process, you " @@ -1321,7 +1321,7 @@ msgstr "" "ゾーンであると仮定します。" #. Tag: para -#: using-d-i.xml:844 +#: using-d-i.xml:845 #, no-c-format msgid "" "In expert mode or when installing at medium priority, you will have the " @@ -1332,7 +1332,7 @@ msgstr "" "協定世界時 (UTC) を使用する、という選択肢が追加されます。" #. Tag: para -#: using-d-i.xml:850 +#: using-d-i.xml:851 #, no-c-format msgid "" "If for some reason you wish to set a time zone for the installed system that " @@ -1343,7 +1343,7 @@ msgstr "" "異なるものにしたい場合は、2 つの選択肢があります。" #. Tag: para -#: using-d-i.xml:861 +#: using-d-i.xml:862 #, no-c-format msgid "" "The simplest option is to just select a different time zone after the " @@ -1354,13 +1354,13 @@ msgstr "" "タイムゾーンを選択することです。以下のようなコマンドになります。" #. Tag: screen -#: using-d-i.xml:867 +#: using-d-i.xml:868 #, no-c-format msgid "# dpkg-reconfigure tzdata" msgstr "# dpkg-reconfigure tzdata" #. Tag: para -#: using-d-i.xml:873 +#: using-d-i.xml:874 #, no-c-format msgid "" "Alternatively, the time zone can be set at the very start of the " @@ -1376,7 +1376,7 @@ msgstr "" "きです。" #. Tag: para -#: using-d-i.xml:887 +#: using-d-i.xml:888 #, no-c-format msgid "" "For automated installations the time zone can be set to any desired value " @@ -1386,13 +1386,13 @@ msgstr "" "す。" #. Tag: title -#: using-d-i.xml:901 +#: using-d-i.xml:902 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "ユーザとパスワードのセットアップ" #. Tag: para -#: using-d-i.xml:902 +#: using-d-i.xml:903 #, no-c-format msgid "" "Just before configuring the clock, the installer will allow you to set up " @@ -1404,13 +1404,13 @@ msgstr "" "トール完了後に作成してください。" #. Tag: title -#: using-d-i.xml:916 +#: using-d-i.xml:917 #, no-c-format msgid "Set the Root Password" msgstr "root パスワードの設定" #. Tag: para -#: using-d-i.xml:920 +#: using-d-i.xml:921 #, no-c-format msgid "" "The root account is also called the super-" @@ -1424,7 +1424,7 @@ msgstr "" "使用するのみにすべきです。" #. Tag: para -#: using-d-i.xml:928 +#: using-d-i.xml:929 #, no-c-format msgid "" "Any password you create should contain at least 6 characters, and should " @@ -1439,7 +1439,7 @@ msgstr "" "ください。" #. Tag: para -#: using-d-i.xml:936 +#: using-d-i.xml:937 #, no-c-format msgid "" "If anyone ever tells you they need your root password, be extremely wary. " @@ -1451,13 +1451,13 @@ msgstr "" "ワードを教える必要は、通常決してありません。" #. Tag: title -#: using-d-i.xml:946 +#: using-d-i.xml:947 #, no-c-format msgid "Create an Ordinary User" msgstr "一般ユーザの作成" #. Tag: para -#: using-d-i.xml:948 +#: using-d-i.xml:949 #, no-c-format msgid "" "The system will ask you whether you wish to create an ordinary user account " @@ -1471,7 +1471,7 @@ msgstr "" "ありません。" #. Tag: para -#: using-d-i.xml:957 +#: using-d-i.xml:958 #, no-c-format msgid "" "Why not? Well, one reason to avoid using root's privileges is that it is " @@ -1490,7 +1490,7 @@ msgstr "" "今までご存じなければ、ご一読ください。" #. Tag: para -#: using-d-i.xml:967 +#: using-d-i.xml:968 #, no-c-format msgid "" "You will first be prompted for the user's full name. Then you'll be asked " @@ -1503,7 +1503,7 @@ msgstr "" "フォルトになります。最後にこのアカウントのパスワードを求められます。" #. Tag: para -#: using-d-i.xml:974 +#: using-d-i.xml:975 #, no-c-format msgid "" "If at any point after installation you would like to create another account, " @@ -1513,13 +1513,13 @@ msgstr "" "command> コマンドを使用してください。" #. Tag: title -#: using-d-i.xml:985 +#: using-d-i.xml:986 #, no-c-format msgid "Partitioning and Mount Point Selection" msgstr "パーティションの分割とマウントポイントの選択" #. Tag: para -#: using-d-i.xml:986 +#: using-d-i.xml:987 #, no-c-format msgid "" "At this time, after hardware detection has been executed a final time, &d-i; " @@ -1537,7 +1537,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:1007 +#: using-d-i.xml:1008 #, no-c-format msgid "" "If you are uncomfortable with partitioning, or just want to know more " @@ -1547,7 +1547,7 @@ msgstr "" "\"partitioning\"/> をご覧ください。" #. Tag: para -#: using-d-i.xml:1013 +#: using-d-i.xml:1014 #, no-c-format msgid "" "If a hard disk has previously used under Solaris, the partitioner may not " @@ -1569,7 +1569,7 @@ msgstr "" "できなくなることに注意してください。" #. Tag: para -#: using-d-i.xml:1026 +#: using-d-i.xml:1027 #, no-c-format msgid "" "First you will be given the opportunity to automatically partition either an " @@ -1583,13 +1583,13 @@ msgstr "" "guimenuitem> を選んでください。" #. Tag: title -#: using-d-i.xml:1036 +#: using-d-i.xml:1037 #, no-c-format msgid "Supported partitioning options" msgstr "サポートするパーティション分割オプション" #. Tag: para -#: using-d-i.xml:1037 +#: using-d-i.xml:1038 #, no-c-format msgid "" "The partitioner used in &d-i; is fairly versatile. It allows to create many " @@ -1601,7 +1601,7 @@ msgstr "" "て、たくさんの異なるパーティション構成を作成できます。" #. Tag: para -#: using-d-i.xml:1043 +#: using-d-i.xml:1044 #, no-c-format msgid "" "Exactly which options are available depends mainly on the architecture, but " @@ -1621,7 +1621,7 @@ msgstr "" "きます。もっと高い優先度の場合は、実用的な値がデフォルトで使用されます。" #. Tag: para -#: using-d-i.xml:1054 +#: using-d-i.xml:1055 #, no-c-format msgid "" "The installer supports various forms of advanced partitioning and use of " @@ -1631,31 +1631,31 @@ msgstr "" "とんどの場合組み合わせて)、サポートします。" #. Tag: emphasis -#: using-d-i.xml:1061 +#: using-d-i.xml:1062 #, no-c-format msgid "Logical Volume Management (LVM)" msgstr "論理ボリュームマネージメント" #. Tag: emphasis -#: using-d-i.xml:1064 +#: using-d-i.xml:1065 #, no-c-format msgid "Software RAID" msgstr "ソフトウェア RAID" #. Tag: para -#: using-d-i.xml:1065 +#: using-d-i.xml:1066 #, no-c-format msgid "Supported are RAID levels 0, 1, 4, 5, 6 and 10." msgstr "サポートしている RAID レベルは 0, 1, 4, 5, 6, 10 です。" #. Tag: emphasis -#: using-d-i.xml:1069 +#: using-d-i.xml:1070 #, no-c-format msgid "Encryption" msgstr "暗号化" #. Tag: para -#: using-d-i.xml:1071 +#: using-d-i.xml:1072 #, no-c-format msgid "" "Serial ATA RAID (using dmraid)" @@ -1663,7 +1663,7 @@ msgstr "" "シリアル ATA RAID (dmraid を利用)" #. Tag: para -#: using-d-i.xml:1073 +#: using-d-i.xml:1074 #, no-c-format msgid "" "Also called fake RAID or BIOS RAID. Support " @@ -1677,13 +1677,13 @@ msgstr "" "ます。" #. Tag: para -#: using-d-i.xml:1079 +#: using-d-i.xml:1080 #, no-c-format msgid "Multipath (experimental)" msgstr "マルチパス (実験的)" #. Tag: para -#: using-d-i.xml:1081 +#: using-d-i.xml:1082 #, no-c-format msgid "" "See our Wiki for information. " @@ -1695,13 +1695,13 @@ msgstr "" "きます。" #. Tag: para -#: using-d-i.xml:1088 +#: using-d-i.xml:1089 #, no-c-format msgid "The following file systems are supported." msgstr "以下のファイルシステムをサポートしています。" #. Tag: para -#: using-d-i.xml:1093 +#: using-d-i.xml:1094 #, no-c-format msgid "" "ext2r0, " @@ -1715,7 +1715,7 @@ msgstr "" "phrase>" #. Tag: para -#: using-d-i.xml:1098 +#: using-d-i.xml:1099 #, no-c-format msgid "" "The default file system selected in most cases is ext3; for /bootjfs (not available on all architectures)" msgstr "" "jfs (全アーキテクチャで使用できるわけではありません)" #. Tag: emphasis -#: using-d-i.xml:1107 +#: using-d-i.xml:1108 #, no-c-format msgid "ufs" msgstr "ufs" #. Tag: para -#: using-d-i.xml:1108 +#: using-d-i.xml:1109 #, no-c-format msgid "The default file system is UFS." msgstr "デフォルトファイルシステムは UFS です。" #. Tag: para -#: using-d-i.xml:1111 +#: using-d-i.xml:1112 #, no-c-format msgid "xfs (not available on all architectures)" msgstr "" "xfs (全アーキテクチャで使用できるわけではありません)" #. Tag: emphasis -#: using-d-i.xml:1115 +#: using-d-i.xml:1116 #, no-c-format msgid "zfs" msgstr "zfs" #. Tag: para -#: using-d-i.xml:1116 +#: using-d-i.xml:1117 #, no-c-format msgid "" "As ZFS support in the installer is still in development, only a basic subset " @@ -1770,8 +1770,8 @@ msgstr "" "ブセットはサポートしています。いくつかは初期インストールの後に、手動で有効に" "できますが、以下のようにいくつか警告があります。" -#. Tag: listitem -#: using-d-i.xml:1121 +#. Tag: para +#: using-d-i.xml:1122 #, no-c-format msgid "" "Each ZFS pool will host only one filesystem. After install is finished, more " @@ -1782,8 +1782,8 @@ msgstr "" "zfs create コマンドを使用して、プールにたくさんのファイルシス" "テムを作成できます。" -#. Tag: listitem -#: using-d-i.xml:1126 +#. Tag: para +#: using-d-i.xml:1127 #, no-c-format msgid "" "Each ZFS pool will be composed of exactly one partition. After install is " @@ -1799,8 +1799,8 @@ msgstr "" "換したりできます。しかし、システム起動時に GRUB の動作を妨げるため、ルート" "ファイルシステムをホストするプールでは行うべきではありません。" -#. Tag: listitem -#: using-d-i.xml:1134 +#. Tag: para +#: using-d-i.xml:1135 #, no-c-format msgid "" "Compression is not currently supported. After the install is finished, " @@ -1815,7 +1815,7 @@ msgstr "" "動時に GRUB の動作を妨げる可能性があります。" #. Tag: para -#: using-d-i.xml:1143 +#: using-d-i.xml:1144 #, no-c-format msgid "" "reiserfs (optional; not available on all architectures)" @@ -1824,7 +1824,7 @@ msgstr "" "はありません)" #. Tag: para -#: using-d-i.xml:1145 +#: using-d-i.xml:1146 #, no-c-format msgid "" "Support for the Reiser file system is no longer available by default. When " @@ -1838,13 +1838,13 @@ msgstr "" "します。" #. Tag: emphasis -#: using-d-i.xml:1152 +#: using-d-i.xml:1153 #, no-c-format msgid "jffs2" msgstr "jffs2" #. Tag: para -#: using-d-i.xml:1153 +#: using-d-i.xml:1154 #, no-c-format msgid "" "Used on some systems to read flash memory. It is not possible to create new " @@ -1854,13 +1854,13 @@ msgstr "" "ティションは作成できません。" #. Tag: emphasis -#: using-d-i.xml:1158 +#: using-d-i.xml:1159 #, no-c-format msgid "qnx4" msgstr "qnx4" #. Tag: para -#: using-d-i.xml:1159 +#: using-d-i.xml:1160 #, no-c-format msgid "" "Existing partitions will be recognized and it is possible to assign mount " @@ -1870,19 +1870,19 @@ msgstr "" "qnx4 パーティションは作成できません。" #. Tag: para -#: using-d-i.xml:1163 +#: using-d-i.xml:1164 #, no-c-format msgid "FAT16, FAT32" msgstr "FAT16, FAT32" #. Tag: para -#: using-d-i.xml:1166 +#: using-d-i.xml:1167 #, no-c-format msgid "NTFS (read-only)" msgstr "NTFS (読み込み専用)" #. Tag: para -#: using-d-i.xml:1168 +#: using-d-i.xml:1169 #, no-c-format msgid "" "Existing NTFS partitions can be resized and it is possible to assign mount " @@ -1892,13 +1892,13 @@ msgstr "" "す。新しい NTFS パーティションは作成できません。" #. Tag: title -#: using-d-i.xml:1178 +#: using-d-i.xml:1179 #, no-c-format msgid "Guided Partitioning" msgstr "ガイドパーティション分割" #. Tag: para -#: using-d-i.xml:1179 +#: using-d-i.xml:1180 #, no-c-format msgid "" "If you choose guided partitioning, you may have three options: to create " @@ -1915,7 +1915,7 @@ msgstr "" "サポートを利用します。 を利用する方法です。" #. Tag: para -#: using-d-i.xml:1194 +#: using-d-i.xml:1195 #, no-c-format msgid "" "The option to use (encrypted) LVM may not be available on all architectures." @@ -1924,7 +1924,7 @@ msgstr "" "わけではありません。" #. Tag: para -#: using-d-i.xml:1199 +#: using-d-i.xml:1200 #, no-c-format msgid "" "When using LVM or encrypted LVM, the installer will create most partitions " @@ -1941,7 +1941,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:1208 +#: using-d-i.xml:1209 #, no-c-format msgid "" "When using encrypted LVM, the installer will also automatically erase the " @@ -1956,7 +1956,7 @@ msgstr "" "スクのサイズにより、時間がかかることがあります。" #. Tag: para -#: using-d-i.xml:1217 +#: using-d-i.xml:1218 #, no-c-format msgid "" "If you choose guided partitioning using LVM or encrypted LVM, some changes " @@ -1973,7 +1973,7 @@ msgstr "" "に、インストーラは変更してよいか確認してきます。" #. Tag: para -#: using-d-i.xml:1227 +#: using-d-i.xml:1228 #, no-c-format msgid "" "If you choose guided partitioning (either classic " @@ -1991,7 +1991,7 @@ msgstr "" "にしてください。" #. Tag: para -#: using-d-i.xml:1236 +#: using-d-i.xml:1237 #, no-c-format msgid "" "Any data on the disk you select will eventually be lost, but you will always " @@ -2006,7 +2006,7 @@ msgstr "" "を使用する場合は元に戻せません。" #. Tag: para -#: using-d-i.xml:1246 +#: using-d-i.xml:1247 #, no-c-format msgid "" "Next, you will be able to choose from the schemes listed in the table below. " @@ -2023,73 +2023,73 @@ msgstr "" "依存します) がなければ、ガイドパーティション分割は失敗してしまいます。" #. Tag: entry -#: using-d-i.xml:1262 +#: using-d-i.xml:1263 #, no-c-format msgid "Partitioning scheme" msgstr "パーティション分割方法" #. Tag: entry -#: using-d-i.xml:1263 +#: using-d-i.xml:1264 #, no-c-format msgid "Minimum space" msgstr "最低容量" #. Tag: entry -#: using-d-i.xml:1264 +#: using-d-i.xml:1265 #, no-c-format msgid "Created partitions" msgstr "作成するパーティション" #. Tag: entry -#: using-d-i.xml:1270 +#: using-d-i.xml:1271 #, no-c-format msgid "All files in one partition" msgstr "All files in one partition" #. Tag: entry -#: using-d-i.xml:1271 +#: using-d-i.xml:1272 #, no-c-format msgid "600MB" msgstr "600MB" #. Tag: entry -#: using-d-i.xml:1272 +#: using-d-i.xml:1273 #, no-c-format msgid "/, swap" msgstr "/, swap" #. Tag: entry -#: using-d-i.xml:1274 +#: using-d-i.xml:1275 #, no-c-format msgid "Separate /home partition" msgstr "Separate /home partition" #. Tag: entry -#: using-d-i.xml:1275 +#: using-d-i.xml:1276 #, no-c-format msgid "500MB" msgstr "500MB" #. Tag: entry -#: using-d-i.xml:1276 +#: using-d-i.xml:1277 #, no-c-format msgid "/, /home, swap" msgstr "/, /home, swap" #. Tag: entry -#: using-d-i.xml:1280 +#: using-d-i.xml:1281 #, no-c-format msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "Separate /home, /usr, /var and /tmp partitions" #. Tag: entry -#: using-d-i.xml:1281 +#: using-d-i.xml:1282 #, no-c-format msgid "1GB" msgstr "1GB" #. Tag: entry -#: using-d-i.xml:1282 +#: using-d-i.xml:1283 #, no-c-format msgid "" "/, /home, /usr, /var, /tmp, swap" #. Tag: para -#: using-d-i.xml:1291 +#: using-d-i.xml:1292 #, no-c-format msgid "" "If you choose guided partitioning using (encrypted) LVM, the installer will " @@ -2113,7 +2113,7 @@ msgstr "" "します。" #. Tag: para -#: using-d-i.xml:1297 +#: using-d-i.xml:1298 #, no-c-format msgid "" "If you choose guided partitioning for your IA-64 system, there will be an " @@ -2127,7 +2127,7 @@ msgstr "" "セットアップするよう、フォーマットメニューに追加メニュー項目があります。" #. Tag: para -#: using-d-i.xml:1305 +#: using-d-i.xml:1306 #, no-c-format msgid "" "After selecting a scheme, the next screen will show your new partition " @@ -2139,7 +2139,7 @@ msgstr "" "いった情報が含まれています。" #. Tag: para -#: using-d-i.xml:1311 +#: using-d-i.xml:1312 #, no-c-format msgid "" "The list of partitions might look like this: \n" @@ -2189,7 +2189,7 @@ msgstr "" "んが、手動パーティション分割で使用できる変化を示します。" #. Tag: para -#: using-d-i.xml:1324 +#: using-d-i.xml:1325 #, no-c-format msgid "" "This concludes the guided partitioning. If you are satisfied with the " @@ -2210,13 +2210,13 @@ msgstr "" "ティション分割で修正してください。" #. Tag: title -#: using-d-i.xml:1338 +#: using-d-i.xml:1339 #, no-c-format msgid "Manual Partitioning" msgstr "手動パーティション分割" #. Tag: para -#: using-d-i.xml:1339 +#: using-d-i.xml:1340 #, no-c-format msgid "" "A similar screen to the one shown just above will be displayed if you choose " @@ -2231,7 +2231,7 @@ msgstr "" "ションの使用法については、本節の残りで扱います。" #. Tag: para -#: using-d-i.xml:1347 +#: using-d-i.xml:1348 #, no-c-format msgid "" "If you select a pristine disk which has neither partitions nor free space on " @@ -2245,7 +2245,7 @@ msgstr "" "SPACE (空き領域) という新しい行が現れます。" #. Tag: para -#: using-d-i.xml:1355 +#: using-d-i.xml:1356 #, no-c-format msgid "" "If you select some free space, you will have the opportunity to create a new " @@ -2285,7 +2285,7 @@ msgstr "" "イン画面に戻ってください。" #. Tag: para -#: using-d-i.xml:1377 +#: using-d-i.xml:1378 #, no-c-format msgid "" "If you decide you want to change something about your partition, simply " @@ -2306,7 +2306,7 @@ msgstr "" "できます。" #. Tag: para -#: using-d-i.xml:1388 +#: using-d-i.xml:1389 #, no-c-format msgid "" "Be sure to create at least two partitions: one for the rootpartman がそれを検出し、行うまで先に進むことができません。" #. Tag: para -#: using-d-i.xml:1402 +#: using-d-i.xml:1403 #, no-c-format msgid "" "Capabilities of partman can be extended with installer " @@ -2349,7 +2349,7 @@ msgstr "" "partman-lvm)" #. Tag: para -#: using-d-i.xml:1410 +#: using-d-i.xml:1411 #, no-c-format msgid "" "After you are satisfied with partitioning, select Finish " @@ -2363,13 +2363,13 @@ msgstr "" "成するかどうか確認することになります。" #. Tag: title -#: using-d-i.xml:1438 +#: using-d-i.xml:1439 #, no-c-format msgid "Configuring Multidisk Devices (Software RAID)" msgstr "マルチディスクデバイス (ソフトウェア RAID) の設定" #. Tag: para -#: using-d-i.xml:1439 +#: using-d-i.xml:1440 #, no-c-format msgid "" "If you have more than one harddrive To be honest, you can " @@ -2388,7 +2388,7 @@ msgstr "" "firstterm> の方が有名) と呼びます。" #. Tag: para -#: using-d-i.xml:1452 +#: using-d-i.xml:1453 #, no-c-format msgid "" "MD is basically a bunch of partitions located on different disks and " @@ -2402,7 +2402,7 @@ msgstr "" "てられる等) と同様に使用できます。" #. Tag: para -#: using-d-i.xml:1460 +#: using-d-i.xml:1461 #, no-c-format msgid "" "What benefits this brings depends on the type of MD device you are creating. " @@ -2508,97 +2508,97 @@ msgstr "" "varlistentry> まとめると以下のようになります。" #. Tag: entry -#: using-d-i.xml:1574 +#: using-d-i.xml:1575 #, no-c-format msgid "Type" msgstr "タイプ" #. Tag: entry -#: using-d-i.xml:1575 +#: using-d-i.xml:1576 #, no-c-format msgid "Minimum Devices" msgstr "デバイス最小構成数" #. Tag: entry -#: using-d-i.xml:1576 +#: using-d-i.xml:1577 #, no-c-format msgid "Spare Device" msgstr "予備デバイス" #. Tag: entry -#: using-d-i.xml:1577 +#: using-d-i.xml:1578 #, no-c-format msgid "Survives disk failure?" msgstr "ディスク破損に耐えるか?" #. Tag: entry -#: using-d-i.xml:1578 +#: using-d-i.xml:1579 #, no-c-format msgid "Available Space" msgstr "利用可能領域" #. Tag: entry -#: using-d-i.xml:1584 +#: using-d-i.xml:1585 #, no-c-format msgid "RAID0" msgstr "RAID0" #. Tag: entry -#: using-d-i.xml:1585 using-d-i.xml:1593 using-d-i.xml:1623 +#: using-d-i.xml:1586 using-d-i.xml:1594 using-d-i.xml:1624 #, no-c-format msgid "2" msgstr "2" #. Tag: entry -#: using-d-i.xml:1586 using-d-i.xml:1587 +#: using-d-i.xml:1587 using-d-i.xml:1588 #, no-c-format msgid "no" msgstr "no" #. Tag: entry -#: using-d-i.xml:1588 +#: using-d-i.xml:1589 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "RAID にある最小パーティションのサイズ×デバイス数" #. Tag: entry -#: using-d-i.xml:1592 +#: using-d-i.xml:1593 #, no-c-format msgid "RAID1" msgstr "RAID1" #. Tag: entry -#: using-d-i.xml:1594 using-d-i.xml:1602 using-d-i.xml:1613 using-d-i.xml:1624 +#: using-d-i.xml:1595 using-d-i.xml:1603 using-d-i.xml:1614 using-d-i.xml:1625 #, no-c-format msgid "optional" msgstr "任意" #. Tag: entry -#: using-d-i.xml:1595 using-d-i.xml:1603 using-d-i.xml:1614 using-d-i.xml:1625 +#: using-d-i.xml:1596 using-d-i.xml:1604 using-d-i.xml:1615 using-d-i.xml:1626 #, no-c-format msgid "yes" msgstr "yes" #. Tag: entry -#: using-d-i.xml:1596 +#: using-d-i.xml:1597 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "RAID にある最小パーティションのサイズ" #. Tag: entry -#: using-d-i.xml:1600 +#: using-d-i.xml:1601 #, no-c-format msgid "RAID5" msgstr "RAID5" #. Tag: entry -#: using-d-i.xml:1601 +#: using-d-i.xml:1602 #, no-c-format msgid "3" msgstr "3" #. Tag: entry -#: using-d-i.xml:1604 +#: using-d-i.xml:1605 #, no-c-format msgid "" "Size of the smallest partition multiplied by (number of devices in RAID " @@ -2606,19 +2606,19 @@ msgid "" msgstr "RAID にある最小パーティションのサイズ×(デバイス数 - 1)" #. Tag: entry -#: using-d-i.xml:1611 +#: using-d-i.xml:1612 #, no-c-format msgid "RAID6" msgstr "RAID6" #. Tag: entry -#: using-d-i.xml:1612 +#: using-d-i.xml:1613 #, no-c-format msgid "4" msgstr "4" #. Tag: entry -#: using-d-i.xml:1615 +#: using-d-i.xml:1616 #, no-c-format msgid "" "Size of the smallest partition multiplied by (number of devices in RAID " @@ -2626,13 +2626,13 @@ msgid "" msgstr "最小パーティションのサイズ×(RAID にあるデバイス数 - 2)" #. Tag: entry -#: using-d-i.xml:1622 +#: using-d-i.xml:1623 #, no-c-format msgid "RAID10" msgstr "RAID10" #. Tag: entry -#: using-d-i.xml:1626 +#: using-d-i.xml:1627 #, no-c-format msgid "" "Total of all partitions divided by the number of chunk copies (defaults to " @@ -2640,7 +2640,7 @@ msgid "" msgstr "全パーティションサイズ÷チャンクのコピー数 (デフォルトは 2)" #. Tag: para -#: using-d-i.xml:1633 +#: using-d-i.xml:1634 #, no-c-format msgid "" "If you want to know more about Software RAID, have a look at Software RAID HOWTO をご覧ください。" #. Tag: para -#: using-d-i.xml:1638 +#: using-d-i.xml:1639 #, no-c-format msgid "" "To create an MD device, you need to have the desired partitions it should " @@ -2665,7 +2665,7 @@ msgstr "" "ニューの partman で行えます)" #. Tag: para -#: using-d-i.xml:1647 +#: using-d-i.xml:1648 #, no-c-format msgid "" "Make sure that the system can be booted with the partitioning scheme you are " @@ -2685,7 +2685,7 @@ msgstr "" "filename> に RAID1 を用いる例が選択したり得ます。" #. Tag: para -#: using-d-i.xml:1659 +#: using-d-i.xml:1660 #, no-c-format msgid "" "Support for MD is a relatively new addition to the installer. You may " @@ -2702,7 +2702,7 @@ msgstr "" "して動作させることができるかも知れません。" #. Tag: para -#: using-d-i.xml:1668 +#: using-d-i.xml:1669 #, no-c-format msgid "" "Next, you should choose Configure software RAID " @@ -2723,7 +2723,7 @@ msgstr "" "さい。その後は選択した MD デバイスに依存します。" #. Tag: para -#: using-d-i.xml:1681 +#: using-d-i.xml:1682 #, no-c-format msgid "" "RAID0 is simple — you will be issued with the list of available RAID " @@ -2734,7 +2734,7 @@ msgstr "" "に MD にするパーティションを選択してください。" #. Tag: para -#: using-d-i.xml:1688 +#: using-d-i.xml:1689 #, no-c-format msgid "" "RAID1 is a bit more tricky. First, you will be asked to enter the number of " @@ -2753,7 +2753,7 @@ msgstr "" "せん。" #. Tag: para -#: using-d-i.xml:1700 +#: using-d-i.xml:1701 #, no-c-format msgid "" "RAID5 has a setup procedure similar to RAID1 with the exception that you " @@ -2764,7 +2764,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:1706 +#: using-d-i.xml:1707 #, no-c-format msgid "" "RAID6 also has a setup procedure similar to RAID1 except that at least " @@ -2775,7 +2775,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:1712 +#: using-d-i.xml:1713 #, no-c-format msgid "" "RAID10 again has a setup procedure similar to RAID1 except in expert mode. " @@ -2795,7 +2795,7 @@ msgstr "" "は、たくさんのアクティブデバイスがなければなりません。" #. Tag: para -#: using-d-i.xml:1726 +#: using-d-i.xml:1727 #, no-c-format msgid "" "It is perfectly possible to have several types of MD at once. For example, " @@ -2813,7 +2813,7 @@ msgstr "" "ション) で結合できます。" #. Tag: para -#: using-d-i.xml:1735 +#: using-d-i.xml:1736 #, no-c-format msgid "" "After you set up MD devices to your liking, you can Finish/home を選ぶことで行います。" #. Tag: para -#: using-d-i.xml:1789 +#: using-d-i.xml:1790 #, no-c-format msgid "" "When you return to the main partman screen, you will see " @@ -2925,7 +2925,7 @@ msgstr "" "作は以下の通りです。" #. Tag: para -#: using-d-i.xml:1800 +#: using-d-i.xml:1801 #, no-c-format msgid "" "Display configuration details: shows LVM device " @@ -2935,43 +2935,43 @@ msgstr "" "の名称やサイズなどを表示します" #. Tag: guimenuitem -#: using-d-i.xml:1805 +#: using-d-i.xml:1806 #, no-c-format msgid "Create volume group" msgstr "ボリュームグループの作成" #. Tag: guimenuitem -#: using-d-i.xml:1808 +#: using-d-i.xml:1809 #, no-c-format msgid "Create logical volume" msgstr "論理ボリュームの作成" #. Tag: guimenuitem -#: using-d-i.xml:1811 +#: using-d-i.xml:1812 #, no-c-format msgid "Delete volume group" msgstr "ボリュームグループの削除" #. Tag: guimenuitem -#: using-d-i.xml:1814 +#: using-d-i.xml:1815 #, no-c-format msgid "Delete logical volume" msgstr "論理ボリュームの削除" #. Tag: guimenuitem -#: using-d-i.xml:1817 +#: using-d-i.xml:1818 #, no-c-format msgid "Extend volume group" msgstr "ボリュームグループの拡張" #. Tag: guimenuitem -#: using-d-i.xml:1820 +#: using-d-i.xml:1821 #, no-c-format msgid "Reduce volume group" msgstr "ボリュームグループの縮小" #. Tag: para -#: using-d-i.xml:1822 +#: using-d-i.xml:1823 #, no-c-format msgid "" "Finish: return to the main partmanpartman screen, any created " @@ -3002,13 +3002,13 @@ msgstr "" "常のボリュームと同じように表示されています (そして同じように扱えます)。" #. Tag: title -#: using-d-i.xml:1847 +#: using-d-i.xml:1848 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "暗号化ボリュームの設定" #. Tag: para -#: using-d-i.xml:1848 +#: using-d-i.xml:1849 #, no-c-format msgid "" "&d-i; allows you to set up encrypted partitions. Every file you write to " @@ -3029,7 +3029,7 @@ msgstr "" "ないと、ハードディスクのデータはランダムな文字列にしか見えません。" #. Tag: para -#: using-d-i.xml:1860 +#: using-d-i.xml:1861 #, no-c-format msgid "" "The two most important partitions to encrypt are: the home partition, where " @@ -3055,7 +3055,7 @@ msgstr "" "ションからカーネルを起動する方法がないからです。" #. Tag: para -#: using-d-i.xml:1875 +#: using-d-i.xml:1876 #, no-c-format msgid "" "Please note that the performance of encrypted partitions will be less than " @@ -3069,7 +3069,7 @@ msgstr "" "けます。" #. Tag: para -#: using-d-i.xml:1882 +#: using-d-i.xml:1883 #, no-c-format msgid "" "To use encryption, you have to create a new partition by selecting some free " @@ -3089,7 +3089,7 @@ msgstr "" "ティションを暗号化するオプションが追加されます。" #. Tag: para -#: using-d-i.xml:1893 +#: using-d-i.xml:1894 #, no-c-format msgid "" "&d-i; supports several encryption methods. The default method is " @@ -3106,7 +3106,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:1905 +#: using-d-i.xml:1906 #, no-c-format msgid "" "First, let's have a look at the options available when you select " @@ -3119,13 +3119,13 @@ msgstr "" "デフォルト値を指定してください。セキュリティを念頭に置いて選択されています。" #. Tag: term -#: using-d-i.xml:1915 +#: using-d-i.xml:1916 #, no-c-format msgid "Encryption: aes" msgstr "Encryption: aes" #. Tag: para -#: using-d-i.xml:1917 +#: using-d-i.xml:1918 #, no-c-format msgid "" "This option lets you select the encryption algorithm (cipher256" msgstr "Key size: 256" #. Tag: para -#: using-d-i.xml:1937 +#: using-d-i.xml:1938 #, no-c-format msgid "" "Here you can specify the length of the encryption key. With a larger key " @@ -3168,13 +3168,13 @@ msgstr "" "影響を与えます。利用できる暗号化キーのサイズは暗号方式に依存します。" #. Tag: term -#: using-d-i.xml:1949 +#: using-d-i.xml:1950 #, no-c-format msgid "IV algorithm: cbc-essiv:sha256" msgstr "IV algorithm: cbc-essiv:sha256" #. Tag: para -#: using-d-i.xml:1951 +#: using-d-i.xml:1952 #, no-c-format msgid "" "The Initialization Vector or IVcbc-essiv:sha256Passphrase" msgstr "Encryption key: Passphrase" #. Tag: para -#: using-d-i.xml:1975 +#: using-d-i.xml:1976 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "ここでは、このパーティションの暗号化キーのタイプを選択できます。" #. Tag: term -#: using-d-i.xml:1981 +#: using-d-i.xml:1982 #, no-c-format msgid "Passphrase" msgstr "Passphrase" #. Tag: para -#: using-d-i.xml:1982 +#: using-d-i.xml:1983 #, no-c-format msgid "" "The encryption key will be computed Using a passphrase as " @@ -3235,13 +3235,13 @@ msgstr "" "\">LUKS を使用して設定するという意味です。します。" #. Tag: term -#: using-d-i.xml:1997 using-d-i.xml:2090 +#: using-d-i.xml:1998 using-d-i.xml:2091 #, no-c-format msgid "Random key" msgstr "Random key" #. Tag: para -#: using-d-i.xml:1998 +#: using-d-i.xml:1999 #, no-c-format msgid "" "A new encryption key will be generated from random data each time you try to " @@ -3258,7 +3258,7 @@ msgstr "" "解読されないでしょう)" #. Tag: para -#: using-d-i.xml:2007 +#: using-d-i.xml:2008 #, no-c-format msgid "" "Random keys are useful for swap partitions because you do not need to bother " @@ -3277,13 +3277,13 @@ msgstr "" "なってしまうのです。" #. Tag: term -#: using-d-i.xml:2026 using-d-i.xml:2103 +#: using-d-i.xml:2027 using-d-i.xml:2104 #, no-c-format msgid "Erase data: yes" msgstr "Erase data: yes" #. Tag: para -#: using-d-i.xml:2028 +#: using-d-i.xml:2029 #, no-c-format msgid "" "Determines whether the content of this partition should be overwritten with " @@ -3303,7 +3303,7 @@ msgstr "" "データを復元できると信じられています。。" #. Tag: para -#: using-d-i.xml:2048 +#: using-d-i.xml:2049 #, no-c-format msgid "" "If you select Encryption method: " @@ -3315,13 +3315,13 @@ msgstr "" "ンを提供するように変わります。" #. Tag: term -#: using-d-i.xml:2057 +#: using-d-i.xml:2058 #, no-c-format msgid "Encryption: AES256" msgstr "Encryption: AES256" #. Tag: para -#: using-d-i.xml:2059 +#: using-d-i.xml:2060 #, no-c-format msgid "" "For loop-AES, unlike dm-crypt, the options for cipher and key size are " @@ -3333,25 +3333,25 @@ msgstr "" "ださい。" #. Tag: term -#: using-d-i.xml:2069 +#: using-d-i.xml:2070 #, no-c-format msgid "Encryption key: Keyfile (GnuPG)" msgstr "Encryption key: Keyfile (GnuPG)" #. Tag: para -#: using-d-i.xml:2071 +#: using-d-i.xml:2072 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "ここでは、このパーティションの暗号化キーのタイプを選択できます。" #. Tag: term -#: using-d-i.xml:2077 +#: using-d-i.xml:2078 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "Keyfile (GnuPG)" #. Tag: para -#: using-d-i.xml:2078 +#: using-d-i.xml:2079 #, no-c-format msgid "" "The encryption key will be generated from random data during the " @@ -3364,19 +3364,19 @@ msgstr "" "は、適切なパスフレーズを入力する必要があります (後のプロセスで要求されます)。" #. Tag: para -#: using-d-i.xml:2091 +#: using-d-i.xml:2092 #, no-c-format msgid "Please see the section on random keys above." msgstr "前述の Random key の節をご覧ください。" #. Tag: para -#: using-d-i.xml:2105 +#: using-d-i.xml:2106 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "前節の Erase data の節をご覧ください。" #. Tag: para -#: using-d-i.xml:2114 +#: using-d-i.xml:2115 #, no-c-format msgid "" "After you have selected the desired parameters for your encrypted " @@ -3394,7 +3394,7 @@ msgstr "" "かかるでしょう。" #. Tag: para -#: using-d-i.xml:2124 +#: using-d-i.xml:2125 #, no-c-format msgid "" "Next you will be asked to enter a passphrase for partitions configured to " @@ -3409,7 +3409,7 @@ msgstr "" "前など) でないものです。" #. Tag: para -#: using-d-i.xml:2133 +#: using-d-i.xml:2134 #, no-c-format msgid "" "Before you input any passphrases, you should have made sure that your " @@ -3432,7 +3432,7 @@ msgstr "" "トが有効でなかったのかもしれません。" #. Tag: para -#: using-d-i.xml:2146 +#: using-d-i.xml:2147 #, no-c-format msgid "" "If you selected to use methods other than a passphrase to create encryption " @@ -3453,7 +3453,7 @@ msgstr "" "ます。暗号化するパーティションの数だけ繰り返します。" #. Tag: para -#: using-d-i.xml:2162 +#: using-d-i.xml:2163 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted " @@ -3486,7 +3486,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:2175 +#: using-d-i.xml:2176 #, no-c-format msgid "" "Pay attention to the identifiers in parentheses (sda2_crypt で扱います。" #. Tag: para -#: using-d-i.xml:2185 +#: using-d-i.xml:2186 #, no-c-format msgid "" "Once you are satisfied with the partitioning scheme, continue with the " @@ -3511,13 +3511,13 @@ msgid "" msgstr "パーティション分割の内容に納得いったら、インストールに進んでください。" #. Tag: title -#: using-d-i.xml:2196 +#: using-d-i.xml:2197 #, no-c-format msgid "Installing the Base System" msgstr "基本システムのインストール" #. Tag: para -#: using-d-i.xml:2197 +#: using-d-i.xml:2198 #, no-c-format msgid "" "Although this stage is the least problematic, it consumes a significant " @@ -3530,7 +3530,7 @@ msgstr "" "接続しかなければ、ある程度時間がかかるかもしれません。" #. Tag: para -#: using-d-i.xml:2210 +#: using-d-i.xml:2211 #, no-c-format msgid "" "During installation of the base system, package unpacking and setup messages " @@ -3546,7 +3546,7 @@ msgstr "" "keycap>F1 を押してください。" #. Tag: para -#: using-d-i.xml:2219 +#: using-d-i.xml:2220 #, no-c-format msgid "" "The unpack/setup messages generated during this phase are also saved in " @@ -3558,7 +3558,7 @@ msgstr "" "ます。" #. Tag: para -#: using-d-i.xml:2225 +#: using-d-i.xml:2226 #, no-c-format msgid "" "As part of the installation, a &arch-kernel; kernel will be installed. At " @@ -3571,7 +3571,7 @@ msgstr "" "り低い優先度モードでは、利用可能なカーネルのリストから選ぶことができます。" #. Tag: para -#: using-d-i.xml:2232 +#: using-d-i.xml:2233 #, no-c-format msgid "" "When packages are installed using the package management system, it will by " @@ -3588,7 +3588,7 @@ msgstr "" "同時に入っているべきパッケージです。" #. Tag: para -#: using-d-i.xml:2242 +#: using-d-i.xml:2243 #, no-c-format msgid "" "For technical reasons packages installed during the installation of the base " @@ -3601,13 +3601,13 @@ msgstr "" "中のこの時点以降でのみ効力を発揮します。" #. Tag: title -#: using-d-i.xml:2254 +#: using-d-i.xml:2255 #, no-c-format msgid "Installing Additional Software" msgstr "追加ソフトウェアのインストール" #. Tag: para -#: using-d-i.xml:2255 +#: using-d-i.xml:2256 #, no-c-format msgid "" "At this point you have a usable but limited system. Most users will want to " @@ -3622,13 +3622,13 @@ msgstr "" "す。" #. Tag: title -#: using-d-i.xml:2270 +#: using-d-i.xml:2271 #, no-c-format msgid "Configuring apt" msgstr "apt の設定" #. Tag: para -#: using-d-i.xml:2272 +#: using-d-i.xml:2273 #, no-c-format msgid "" "One of the tools used to install packages on a &debian-gnu; system is a " @@ -3663,7 +3663,7 @@ msgstr "" "理の推奨ユーティリティです。" #. Tag: para -#: using-d-i.xml:2296 +#: using-d-i.xml:2297 #, no-c-format msgid "" "apt must be configured so that it knows from where to " @@ -3677,7 +3677,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:2303 +#: using-d-i.xml:2304 #, no-c-format msgid "" "If you are installing at default priority, the installer will largely take " @@ -3694,7 +3694,7 @@ msgstr "" "ミラーを追加します。" #. Tag: para -#: using-d-i.xml:2312 +#: using-d-i.xml:2313 #, no-c-format msgid "" "If you are installing at a lower priority (e.g. in expert mode), you will be " @@ -3709,13 +3709,13 @@ msgstr "" "の有無を選べます。" #. Tag: title -#: using-d-i.xml:2323 +#: using-d-i.xml:2324 #, no-c-format msgid "Installing from more than one CD or DVD" msgstr "2 枚以上の CD/DVD でのインストール" #. Tag: para -#: using-d-i.xml:2325 +#: using-d-i.xml:2326 #, no-c-format msgid "" "If you are installing from a CD or a DVD that is part of a larger set, the " @@ -3728,7 +3728,7 @@ msgstr "" "ケージをインストールするため、スキャンしたくなると思います。" #. Tag: para -#: using-d-i.xml:2332 +#: using-d-i.xml:2333 #, no-c-format msgid "" "If you do not have any additional CDs or DVDs, that is no problem: using " @@ -3742,7 +3742,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:2340 +#: using-d-i.xml:2341 #, no-c-format msgid "" "Packages are included on CDs (and DVDs) in the order of their popularity. " @@ -3755,7 +3755,7 @@ msgstr "" "後の CD に入っているパッケージを使用することになります。" #. Tag: para -#: using-d-i.xml:2347 +#: using-d-i.xml:2348 #, no-c-format msgid "" "It also means that buying or downloading and burning a full CD set is just a " @@ -3772,7 +3772,7 @@ msgstr "" "のをカバーできるでしょう。" #. Tag: para -#: using-d-i.xml:2356 +#: using-d-i.xml:2357 #, no-c-format msgid "" "A good rule of thumb is that for a regular desktop installation (using the " @@ -3786,7 +3786,7 @@ msgstr "" "環境をすべてカバーしています。" #. Tag: para -#: using-d-i.xml:2364 +#: using-d-i.xml:2365 #, no-c-format msgid "" "If you do scan multiple CDs or DVDs, the installer will prompt you to " @@ -3803,13 +3803,13 @@ msgstr "" "低くなります。" #. Tag: title -#: using-d-i.xml:2377 +#: using-d-i.xml:2378 #, no-c-format msgid "Using a network mirror" msgstr "ネットワークミラーの利用" #. Tag: para -#: using-d-i.xml:2379 +#: using-d-i.xml:2380 #, no-c-format msgid "" "One question that will be asked during most installs is whether or not to " @@ -3821,7 +3821,7 @@ msgstr "" "が、中には例外もあります。" #. Tag: para -#: using-d-i.xml:2385 +#: using-d-i.xml:2386 #, no-c-format msgid "" "If you are not installing from a full CD or DVD or " @@ -3838,7 +3838,7 @@ msgstr "" "literal> タスクを選択しないのが最善でしょう" #. Tag: para -#: using-d-i.xml:2394 +#: using-d-i.xml:2395 #, no-c-format msgid "" "If you are installing from a single full CD or using a full CD image, using " @@ -3857,7 +3857,7 @@ msgstr "" "インストールは、(新しいシステムで起動した後など) 後で行うのがよいでしょう。" #. Tag: para -#: using-d-i.xml:2405 +#: using-d-i.xml:2406 #, no-c-format msgid "" "If you are installing from a DVD or using a DVD image, any packages needed " @@ -3871,7 +3871,7 @@ msgstr "" "ションとなります。" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2413 #, no-c-format msgid "" "One advantage of adding a network mirror is that updates that have occurred " @@ -3886,7 +3886,7 @@ msgstr "" "延ばすことができます。" #. Tag: para -#: using-d-i.xml:2419 +#: using-d-i.xml:2420 #, no-c-format msgid "" "In summary: selecting a network mirror is generally a good idea, except if " @@ -3901,26 +3901,26 @@ msgstr "" "のダウンロードするデータ量は、以下に依存します。" #. Tag: para -#: using-d-i.xml:2428 +#: using-d-i.xml:2429 #, no-c-format msgid "the tasks you select in the next step of the installation," msgstr "インストールの次のステップで選択するタスク。" #. Tag: para -#: using-d-i.xml:2433 +#: using-d-i.xml:2434 #, no-c-format msgid "which packages are needed for those tasks," msgstr "どのパッケージがそのタスクに必要か。" #. Tag: para -#: using-d-i.xml:2438 +#: using-d-i.xml:2439 #, no-c-format msgid "" "which of those packages are present on the CDs or DVDs you have scanned, and" msgstr "そのパッケージがスキャンした CD や DVD に収録されているかどうか。" #. Tag: para -#: using-d-i.xml:2443 +#: using-d-i.xml:2444 #, no-c-format msgid "" "whether any updated versions of packages included on the CDs or DVDs are " @@ -3932,7 +3932,7 @@ msgstr "" "意されているかどうか。" #. Tag: para -#: using-d-i.xml:2452 +#: using-d-i.xml:2453 #, no-c-format msgid "" "Note that the last point means that, even if you choose not to use a network " @@ -3946,13 +3946,13 @@ msgstr "" "ください。" #. Tag: title -#: using-d-i.xml:2468 +#: using-d-i.xml:2469 #, no-c-format msgid "Selecting and Installing Software" msgstr "ソフトウェアの選択・インストール" #. Tag: para -#: using-d-i.xml:2470 +#: using-d-i.xml:2471 #, no-c-format msgid "" "During the installation process, you are given the opportunity to select " @@ -3969,7 +3969,7 @@ msgstr "" "集中します。" #. Tag: para -#: using-d-i.xml:2479 +#: using-d-i.xml:2480 #, no-c-format msgid "" "So, you have the ability to choose tasks first, and " @@ -4002,7 +4002,7 @@ msgstr "" "必要容量一覧があります。" #. Tag: para -#: using-d-i.xml:2506 +#: using-d-i.xml:2507 #, no-c-format msgid "" "Some tasks may be pre-selected based on the characteristics of the computer " @@ -4014,7 +4014,7 @@ msgstr "" "選択をはずせます。全くタスクを選ばないようにもできます。" #. Tag: para -#: using-d-i.xml:2513 +#: using-d-i.xml:2514 #, no-c-format msgid "" "In the standard user interface of the installer, you can use the space bar " @@ -4024,7 +4024,7 @@ msgstr "" "グルできます。" #. Tag: para -#: using-d-i.xml:2519 +#: using-d-i.xml:2520 #, no-c-format msgid "" "Unless you are using the special KDE or Xfce/LXDE CDs, the Desktop " @@ -4034,7 +4034,7 @@ msgstr "" "環境 タスクは、GNOME デスクトップ環境をインストールします。" #. Tag: para -#: using-d-i.xml:2524 +#: using-d-i.xml:2525 #, no-c-format msgid "" "It is not possible to interactively select a different desktop during the " @@ -4055,7 +4055,7 @@ msgstr "" "もっと軽量な Xfce デスクトップ環境や LXDE デスクトップ環境を選択できます。" #. Tag: para -#: using-d-i.xml:2535 +#: using-d-i.xml:2536 #, no-c-format msgid "" "Some CD images (businesscard, netinst and DVD) also allow selection of the " @@ -4069,7 +4069,7 @@ msgstr "" "environments を探してください。" #. Tag: para -#: using-d-i.xml:2542 +#: using-d-i.xml:2543 #, no-c-format msgid "" "Note that this will only work if the packages needed for the desired desktop " @@ -4086,7 +4086,7 @@ msgstr "" "ストールがうまくいくでしょう。" #. Tag: para -#: using-d-i.xml:2552 +#: using-d-i.xml:2553 #, no-c-format msgid "" "The various server tasks will install software roughly as follows. DNS " @@ -4106,7 +4106,7 @@ msgstr "" "classname>。" #. Tag: para -#: using-d-i.xml:2563 +#: using-d-i.xml:2564 #, no-c-format msgid "" "The Standard system task will install any package that has a " @@ -4122,7 +4122,7 @@ msgstr "" "にしてください。" #. Tag: para -#: using-d-i.xml:2571 +#: using-d-i.xml:2572 #, no-c-format msgid "" "If during language selection a default locale other than the C" #. Tag: title -#: using-d-i.xml:2629 +#: using-d-i.xml:2630 #, no-c-format msgid "Detecting other operating systems" msgstr "他 OS の検出" #. Tag: para -#: using-d-i.xml:2631 +#: using-d-i.xml:2632 #, no-c-format msgid "" "Before a boot loader is installed, the installer will attempt to probe for " @@ -4231,7 +4231,7 @@ msgstr "" "できるように、このコンピュータを設定します。" #. Tag: para -#: using-d-i.xml:2639 +#: using-d-i.xml:2640 #, no-c-format msgid "" "Note that multiple operating systems booting on a single machine is still " @@ -4246,13 +4246,13 @@ msgstr "" "す。作動しない場合は、詳細についてブートマネージャの文書を調べるべきです。" #. Tag: title -#: using-d-i.xml:2657 +#: using-d-i.xml:2658 #, no-c-format msgid "palo-installer" msgstr "palo インストーラ" #. Tag: para -#: using-d-i.xml:2658 +#: using-d-i.xml:2659 #, no-c-format msgid "" "The bootloader on PA-RISC is palo. PALO is " @@ -4268,19 +4268,19 @@ msgstr "" "Linux パーティションを読むことができるからです。" #. Tag: para -#: using-d-i.xml:2667 +#: using-d-i.xml:2668 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "hppa FIXME ( もっと情報が必要 )" #. Tag: title -#: using-d-i.xml:2679 +#: using-d-i.xml:2680 #, no-c-format msgid "Install the Grub Boot Loader on a Hard Disk" msgstr "ハードディスクへの Grub ブートローダのインストール" #. Tag: para -#: using-d-i.xml:2681 +#: using-d-i.xml:2682 #, no-c-format msgid "" "The main &architecture; boot loader is called grub. Grub is a " @@ -4292,7 +4292,7 @@ msgstr "" "選んでおけばよいでしょう。" #. Tag: para -#: using-d-i.xml:2687 +#: using-d-i.xml:2688 #, no-c-format msgid "" "By default, grub will be installed into the Master Boot Record (MBR), where " @@ -4305,7 +4305,7 @@ msgstr "" "さい。" #. Tag: para -#: using-d-i.xml:2693 +#: using-d-i.xml:2694 #, no-c-format msgid "" "If you do not want to install grub, use the &BTN-GOBACK; button to get to " @@ -4316,13 +4316,13 @@ msgstr "" "てください。そしてそこから、使用したいブートローダを選択してください。" #. Tag: title -#: using-d-i.xml:2706 +#: using-d-i.xml:2707 #, no-c-format msgid "Install the LILO Boot Loader on a Hard Disk" msgstr "ハードディスクへの LILO ブートローダのインストール" #. Tag: para -#: using-d-i.xml:2708 +#: using-d-i.xml:2709 #, no-c-format msgid "" "The second &architecture; boot loader is called LILO. It is " @@ -4338,7 +4338,7 @@ msgstr "" "\">LILO mini-HOWTO もご覧ください。" #. Tag: para -#: using-d-i.xml:2718 +#: using-d-i.xml:2719 #, no-c-format msgid "" "Currently the LILO installation will only create menu entries for other " @@ -4352,7 +4352,7 @@ msgstr "" "ません。" #. Tag: para -#: using-d-i.xml:2726 +#: using-d-i.xml:2727 #, no-c-format msgid "" "&d-i; offers you three choices on where to install the LILOLILO will take complete control of the boot " @@ -4378,13 +4378,13 @@ msgstr "" "す。" #. Tag: term -#: using-d-i.xml:2740 +#: using-d-i.xml:2741 #, no-c-format msgid "new &debian; partition" msgstr "new &debian; partition" #. Tag: para -#: using-d-i.xml:2740 +#: using-d-i.xml:2741 #, no-c-format msgid "" "Choose this if you want to use another boot manager. LILO " @@ -4396,13 +4396,13 @@ msgstr "" "インストールし、第 2 のブートローダとして動作します。" #. Tag: term -#: using-d-i.xml:2749 +#: using-d-i.xml:2750 #, no-c-format msgid "Other choice" msgstr "Other choice" #. Tag: para -#: using-d-i.xml:2749 +#: using-d-i.xml:2750 #, no-c-format msgid "" "Useful for advanced users who want to install LILO " @@ -4418,7 +4418,7 @@ msgstr "" "従来の名前を使用できます。" #. Tag: para -#: using-d-i.xml:2759 +#: using-d-i.xml:2760 #, no-c-format msgid "" "If you can no longer boot into Windows 9x (or DOS) after this step, you'll " @@ -4434,13 +4434,13 @@ msgstr "" "る、ということを意味します!" #. Tag: title -#: using-d-i.xml:2775 +#: using-d-i.xml:2776 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "ハードディスクへの ELILO ブートローダのインストール" #. Tag: para -#: using-d-i.xml:2777 +#: using-d-i.xml:2778 #, no-c-format msgid "" "The &architecture; boot loader is called elilo. It is modeled " @@ -4468,7 +4468,7 @@ msgstr "" "Boot Manager により実際に実行されます。" #. Tag: para -#: using-d-i.xml:2793 +#: using-d-i.xml:2794 #, no-c-format msgid "" "The elilo configuration and installation is done as the last " @@ -4485,13 +4485,13 @@ msgstr "" "システムがあるディスクのパーティションを選択します。" #. Tag: title -#: using-d-i.xml:2805 +#: using-d-i.xml:2806 #, no-c-format msgid "Choose the correct partition!" msgstr "正しいパーティションを選択してください!" #. Tag: para -#: using-d-i.xml:2807 +#: using-d-i.xml:2808 #, no-c-format msgid "" "The criterion for selecting a partition is that it must be a FAT format " @@ -4510,13 +4510,13 @@ msgstr "" "ください!" #. Tag: title -#: using-d-i.xml:2822 +#: using-d-i.xml:2823 #, no-c-format msgid "EFI Partition Contents" msgstr "EFI パーティションの内容" #. Tag: para -#: using-d-i.xml:2824 +#: using-d-i.xml:2825 #, no-c-format msgid "" "The EFI partition is a FAT filesystem format partition on one of the hard " @@ -4546,13 +4546,13 @@ msgstr "" "のファイルシステムにその他のファイルがあるかもしれません。" #. Tag: filename -#: using-d-i.xml:2846 +#: using-d-i.xml:2847 #, no-c-format msgid "elilo.conf" msgstr "elilo.conf" #. Tag: para -#: using-d-i.xml:2847 +#: using-d-i.xml:2848 #, no-c-format msgid "" "This is the configuration file read by the boot loader when it starts. It is " @@ -4564,13 +4564,13 @@ msgstr "" "ピーです。" #. Tag: filename -#: using-d-i.xml:2856 +#: using-d-i.xml:2857 #, no-c-format msgid "elilo.efi" msgstr "elilo.efi" #. Tag: para -#: using-d-i.xml:2857 +#: using-d-i.xml:2858 #, no-c-format msgid "" "This is the boot loader program that the EFI Boot Manager " @@ -4583,13 +4583,13 @@ msgstr "" "&debian; GNU/Linux を選択するとこれが起動します。" #. Tag: filename -#: using-d-i.xml:2867 +#: using-d-i.xml:2868 #, no-c-format msgid "initrd.img" msgstr "initrd.img" #. Tag: para -#: using-d-i.xml:2868 +#: using-d-i.xml:2869 #, no-c-format msgid "" "This is the initial root filesystem used to boot the kernel. It is a copy of " @@ -4603,13 +4603,13 @@ msgstr "" "filename> で指し示す /boot にあるファイルです。" #. Tag: filename -#: using-d-i.xml:2880 +#: using-d-i.xml:2881 #, no-c-format msgid "readme.txt" msgstr "readme.txt" #. Tag: para -#: using-d-i.xml:2881 +#: using-d-i.xml:2882 #, no-c-format msgid "" "This is a small text file warning you that the contents of the directory are " @@ -4621,13 +4621,13 @@ msgstr "" "する小さなテキストファイルです。" #. Tag: filename -#: using-d-i.xml:2891 +#: using-d-i.xml:2892 #, no-c-format msgid "vmlinuz" msgstr "vmlinuz" #. Tag: para -#: using-d-i.xml:2892 +#: using-d-i.xml:2893 #, no-c-format msgid "" "This is the compressed kernel itself. It is a copy of the file referenced in " @@ -4641,13 +4641,13 @@ msgstr "" "るファイルです。" #. Tag: title -#: using-d-i.xml:2912 +#: using-d-i.xml:2913 #, no-c-format msgid "arcboot-installer" msgstr "arcboot-installer" #. Tag: para -#: using-d-i.xml:2913 +#: using-d-i.xml:2914 #, no-c-format msgid "" "The boot loader on SGI machines is arcboot. It has to be " @@ -4691,13 +4691,13 @@ msgstr "" "い。" #. Tag: replaceable -#: using-d-i.xml:2932 +#: using-d-i.xml:2933 #, no-c-format msgid "scsi" msgstr "scsi" #. Tag: para -#: using-d-i.xml:2933 +#: using-d-i.xml:2934 #, no-c-format msgid "" "is the SCSI bus to be booted from, this is 0 for the " @@ -4707,13 +4707,13 @@ msgstr "" "となる。" #. Tag: replaceable -#: using-d-i.xml:2941 +#: using-d-i.xml:2942 #, no-c-format msgid "disk" msgstr "disk" #. Tag: para -#: using-d-i.xml:2942 +#: using-d-i.xml:2943 #, no-c-format msgid "" "is the SCSI ID of the hard disk on which arcboot is " @@ -4723,13 +4723,13 @@ msgstr "" "す。" #. Tag: replaceable -#: using-d-i.xml:2950 +#: using-d-i.xml:2951 #, no-c-format msgid "partnr" msgstr "partnr" #. Tag: para -#: using-d-i.xml:2951 +#: using-d-i.xml:2952 #, no-c-format msgid "" "is the number of the partition on which /etc/arcboot.conf/etc/arcboot.conf があるパーティションの番号を表す。" #. Tag: replaceable -#: using-d-i.xml:2959 +#: using-d-i.xml:2960 #, no-c-format msgid "config" msgstr "config" #. Tag: para -#: using-d-i.xml:2960 +#: using-d-i.xml:2961 #, no-c-format msgid "" "is the name of the configuration entry in /etc/arcboot.conflinux である。" #. Tag: title -#: using-d-i.xml:2981 +#: using-d-i.xml:2982 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "ハードディスクへの Yaboot のインストール" #. Tag: para -#: using-d-i.xml:2982 +#: using-d-i.xml:2983 #, no-c-format msgid "" "Newer (mid 1998 and on) PowerMacs use yaboot as their " @@ -4780,13 +4780,13 @@ msgstr "" "が &debian-gnu; を起動できるように設定されています。" #. Tag: title -#: using-d-i.xml:3000 +#: using-d-i.xml:3001 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "ハードディスクへの Quik のインストール" #. Tag: para -#: using-d-i.xml:3001 +#: using-d-i.xml:3002 #, no-c-format msgid "" "The boot loader for OldWorld Power Macintosh machines is quikzipl-installer" msgstr "zipl インストーラ" #. Tag: para -#: using-d-i.xml:3018 +#: using-d-i.xml:3019 #, no-c-format msgid "" "The boot loader on &arch-title; is zipl. ZIPL を見てください。" #. Tag: title -#: using-d-i.xml:3035 +#: using-d-i.xml:3036 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "ハードディスクへの SILO ブートローダのインストール" #. Tag: para -#: using-d-i.xml:3037 +#: using-d-i.xml:3038 #, no-c-format msgid "" "The standard &architecture; boot loader is called silo. It is " @@ -4858,13 +4858,13 @@ msgstr "" "Solaris と一緒に GNU/Linux をインストールするのなら、これが便利です。" #. Tag: title -#: using-d-i.xml:3062 +#: using-d-i.xml:3063 #, no-c-format msgid "Continue Without Boot Loader" msgstr "ブートローダなしで継続" #. Tag: para -#: using-d-i.xml:3064 +#: using-d-i.xml:3065 #, no-c-format msgid "" "This option can be used to complete the installation even when no boot " @@ -4877,7 +4877,7 @@ msgstr "" "るのに利用できます。" #. Tag: para -#: using-d-i.xml:3071 +#: using-d-i.xml:3072 #, no-c-format msgid "" "If you plan to manually configure your bootloader, you should check the name " @@ -4899,13 +4899,13 @@ msgstr "" "す。" #. Tag: title -#: using-d-i.xml:3088 +#: using-d-i.xml:3089 #, no-c-format msgid "Finishing the Installation" msgstr "インストールの完了" #. Tag: para -#: using-d-i.xml:3089 +#: using-d-i.xml:3090 #, no-c-format msgid "" "This is the last step in the &debian; installation process during which the " @@ -4916,13 +4916,13 @@ msgstr "" "最終段階です。ほとんどが &d-i; の後片付けです。" #. Tag: title -#: using-d-i.xml:3102 +#: using-d-i.xml:3103 #, no-c-format msgid "Setting the System Clock" msgstr "システム時計の設定" #. Tag: para -#: using-d-i.xml:3104 +#: using-d-i.xml:3105 #, no-c-format msgid "" "The installer may ask you if the computer's clock is set to UTC. Normally " @@ -4935,7 +4935,7 @@ msgstr "" "れているかどうか、といったことから UTC を基準にするかどうかを判断します。" #. Tag: para -#: using-d-i.xml:3111 +#: using-d-i.xml:3112 #, no-c-format msgid "" "In expert mode you will always be able to choose whether or not the clock is " @@ -4953,7 +4953,7 @@ msgstr "" "地時間を選択してください。" #. Tag: para -#: using-d-i.xml:3122 +#: using-d-i.xml:3123 #, no-c-format msgid "" "At this point &d-i; will also attempt to save the current time to the " @@ -4964,13 +4964,13 @@ msgstr "" "す。先ほどの選択により、UTC か現地時間のどちらかで保存します。" #. Tag: title -#: using-d-i.xml:3137 +#: using-d-i.xml:3138 #, no-c-format msgid "Reboot the System" msgstr "システムの再起動" #. Tag: para -#: using-d-i.xml:3139 +#: using-d-i.xml:3140 #, no-c-format msgid "" "You will be prompted to remove the boot media (CD, floppy, etc) that you " @@ -4981,7 +4981,7 @@ msgstr "" "促されます。システムはこの後、新しい &debian; システムで再起動します。" #. Tag: para -#: using-d-i.xml:3145 +#: using-d-i.xml:3146 #, no-c-format msgid "" "After a final prompt the system will be halted because rebooting is not " @@ -4994,13 +4994,13 @@ msgstr "" "イルシステムとして選択した DASD から GNU/Linux を IPL してください。" #. Tag: title -#: using-d-i.xml:3158 +#: using-d-i.xml:3159 #, no-c-format msgid "Troubleshooting" msgstr "トラブルシューティング" #. Tag: para -#: using-d-i.xml:3159 +#: using-d-i.xml:3160 #, no-c-format msgid "" "The components listed in this section are usually not involved in the " @@ -5011,13 +5011,13 @@ msgstr "" "うまく行かない時に、ユーザの助けになるようバックグラウンドで待っています。" #. Tag: title -#: using-d-i.xml:3172 +#: using-d-i.xml:3173 #, no-c-format msgid "Saving the installation logs" msgstr "インストールログの保存" #. Tag: para -#: using-d-i.xml:3174 +#: using-d-i.xml:3175 #, no-c-format msgid "" "If the installation is successful, the logfiles created during the " @@ -5029,7 +5029,7 @@ msgstr "" "れています。" #. Tag: para -#: using-d-i.xml:3181 +#: using-d-i.xml:3182 #, no-c-format msgid "" "Choosing Save debug logs from the main menu " @@ -5045,13 +5045,13 @@ msgstr "" "したいときに便利です。" #. Tag: title -#: using-d-i.xml:3201 +#: using-d-i.xml:3202 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "シェルの使用とログの参照" #. Tag: para -#: using-d-i.xml:3203 +#: using-d-i.xml:3204 #, no-c-format msgid "" "There are several methods you can use to get a shell while running an " @@ -5076,14 +5076,14 @@ msgstr "" "keycombo> でインストーラ自体に戻ってください。" #. Tag: para -#: using-d-i.xml:3221 +#: using-d-i.xml:3222 #, no-c-format msgid "For the graphical installer see also ." msgstr "" "グラフィカルインストーラでは、 もご覧ください。" #. Tag: para -#: using-d-i.xml:3225 +#: using-d-i.xml:3226 #, no-c-format msgid "" "If you cannot switch consoles, there is also an Execute a " @@ -5098,7 +5098,7 @@ msgstr "" "userinput> と入力すると、シェルを終了してインストーラに戻ります。" #. Tag: para -#: using-d-i.xml:3233 +#: using-d-i.xml:3234 #, no-c-format msgid "" "At this point you are booted from the RAM disk, and there is a limited set " @@ -5116,7 +5116,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:3242 +#: using-d-i.xml:3243 #, no-c-format msgid "" "To edit and view files, use the text editor nano. Log " @@ -5128,7 +5128,7 @@ msgstr "" "log ディレクトリにあります。" #. Tag: para -#: using-d-i.xml:3249 +#: using-d-i.xml:3250 #, no-c-format msgid "" "Although you can do basically anything in a shell that the available " @@ -5140,7 +5140,7 @@ msgstr "" "しかありません。" #. Tag: para -#: using-d-i.xml:3255 +#: using-d-i.xml:3256 #, no-c-format msgid "" "Doing things manually from the shell may interfere with the installation " @@ -5153,13 +5153,13 @@ msgstr "" "swap を有効にするようにし、シェルから手動で行わないようにしましょう。" #. Tag: title -#: using-d-i.xml:3271 +#: using-d-i.xml:3272 #, no-c-format msgid "Installation Over the Network" msgstr "ネットワーク越しのインストール" #. Tag: para -#: using-d-i.xml:3273 +#: using-d-i.xml:3274 #, no-c-format msgid "" "One of the more interesting components is network-console で自動化できます)" #. Tag: para -#: using-d-i.xml:3283 +#: using-d-i.xml:3284 #, no-c-format msgid "" "This component is not loaded into the main installation menu by default, so " @@ -5198,7 +5198,7 @@ msgstr "" "ばれる新しいメニュー項目が表示されます。" #. Tag: para -#: using-d-i.xml:3296 +#: using-d-i.xml:3297 #, no-c-format msgid "" "For installations on &arch-title;, this is the default method after setting " @@ -5208,7 +5208,7 @@ msgstr "" "法です。" #. Tag: para -#: using-d-i.xml:3301 +#: using-d-i.xml:3302 #, no-c-format msgid "" "After selecting this new entry, you " @@ -5229,7 +5229,7 @@ msgstr "" "全に転送する必要があります。" #. Tag: para -#: using-d-i.xml:3313 +#: using-d-i.xml:3314 #, no-c-format msgid "" "Should you decide to continue with the installation locally, you can always " @@ -5240,7 +5240,7 @@ msgstr "" "メニューに戻ります。そこで別のコンポーネントを選択してください。" #. Tag: para -#: using-d-i.xml:3319 +#: using-d-i.xml:3320 #, no-c-format msgid "" "Now let's switch to the other side of the wire. As a prerequisite, you need " @@ -5271,7 +5271,7 @@ msgstr "" "認してください。" #. Tag: para -#: using-d-i.xml:3336 +#: using-d-i.xml:3337 #, no-c-format msgid "" "The ssh server in the installer uses a default " @@ -5294,7 +5294,7 @@ msgstr "" "により、再接続後にインストールを再開できるかどうかが決まるでしょう。" #. Tag: para -#: using-d-i.xml:3349 +#: using-d-i.xml:3350 #, no-c-format msgid "" "You may be able to avoid the connection being dropped by adding the option " @@ -5316,7 +5316,7 @@ msgstr "" "用は必要最小限にするべきです。" #. Tag: para -#: using-d-i.xml:3362 +#: using-d-i.xml:3363 #, no-c-format msgid "" "If you install several computers in turn and they happen to have the same IP " @@ -5339,7 +5339,7 @@ msgstr "" "もう一度行う必要があります。" #. Tag: para -#: using-d-i.xml:3378 +#: using-d-i.xml:3379 #, no-c-format msgid "" "After the login you will be presented with an initial screen where you have " @@ -5358,7 +5358,7 @@ msgstr "" "べきですが、シェル用には複数のセッションを起動できます。" #. Tag: para -#: using-d-i.xml:3388 +#: using-d-i.xml:3389 #, no-c-format msgid "" "After you have started the installation remotely over SSH, you should not go " @@ -5373,13 +5373,13 @@ msgstr "" "インストールしたシステムに何か問題が発生するかもしれません。" #. Tag: title -#: using-d-i.xml:3407 +#: using-d-i.xml:3408 #, no-c-format msgid "Loading Missing Firmware" msgstr "見つからないファームウェアの読み込み" #. Tag: para -#: using-d-i.xml:3408 +#: using-d-i.xml:3409 #, no-c-format msgid "" "As described in , some devices require " @@ -5394,7 +5394,7 @@ msgstr "" "が必要になります。" #. Tag: para -#: using-d-i.xml:3416 +#: using-d-i.xml:3417 #, no-c-format msgid "" "If a device driver requests firmware that is not available, &d-i; will " @@ -5412,7 +5412,7 @@ msgstr "" "ジュールを再読込します。" #. Tag: para -#: using-d-i.xml:3426 +#: using-d-i.xml:3427 #, no-c-format msgid "" "Which devices are scanned and which file systems are supported depends on " @@ -5430,7 +5430,7 @@ msgstr "" "す。" #. Tag: para -#: using-d-i.xml:3436 +#: using-d-i.xml:3437 #, no-c-format msgid "" "Note that it is possible to skip loading the firmware if you know the device " @@ -5442,7 +5442,7 @@ msgstr "" "にご注意ください。" #. Tag: para -#: using-d-i.xml:3443 +#: using-d-i.xml:3444 #, no-c-format msgid "" "Support for loading firmware is still relatively basic and is likely to be " @@ -5458,13 +5458,13 @@ msgstr "" "( 参照) としてご報告ください。" #. Tag: title -#: using-d-i.xml:3454 +#: using-d-i.xml:3455 #, no-c-format msgid "Preparing a medium" msgstr "メディアの準備" #. Tag: para -#: using-d-i.xml:3455 +#: using-d-i.xml:3456 #, no-c-format msgid "" "Although in some cases the firmware can also be loaded from a partition on a " @@ -5484,7 +5484,7 @@ msgstr "" "されている、FAT を使用するのをお勧めします。" #. Tag: para -#: using-d-i.xml:3465 +#: using-d-i.xml:3466 #, no-c-format msgid "" "Tarballs and zip files containing current packages for the most common " @@ -5500,7 +5500,7 @@ msgstr "" "テムに展開するだけです。" #. Tag: para -#: using-d-i.xml:3479 +#: using-d-i.xml:3480 #, no-c-format msgid "" "If the firmware you need is not included in the tarball, you can also " @@ -5516,7 +5516,7 @@ msgstr "" "ケージを含むかもしれません。" #. Tag: para -#: using-d-i.xml:3493 +#: using-d-i.xml:3494 #, no-c-format msgid "" "It is also possible to copy individual firmware files to the medium. Loose " @@ -5528,13 +5528,13 @@ msgstr "" "から入手できます。" #. Tag: title -#: using-d-i.xml:3502 +#: using-d-i.xml:3503 #, no-c-format msgid "Firmware and the Installed System" msgstr "ファームウェアとインストールしたシステム" #. Tag: para -#: using-d-i.xml:3503 +#: using-d-i.xml:3504 #, no-c-format msgid "" "Any firmware loaded during the installation will be copied automatically to " @@ -5552,7 +5552,7 @@ msgstr "" "がわずかにあります。" #. Tag: para -#: using-d-i.xml:3512 +#: using-d-i.xml:3513 #, no-c-format msgid "" "If the firmware was loaded from a firmware package, &d-i; will also install " @@ -5568,7 +5568,7 @@ msgstr "" "できるようになると、自動的に更新するという利点があります。" #. Tag: para -#: using-d-i.xml:3520 +#: using-d-i.xml:3521 #, no-c-format msgid "" "If loading the firmware was skipped during the installation, the relevant " @@ -5580,7 +5580,7 @@ msgstr "" "トールしたシステムで動作しないでしょう。" #. Tag: para -#: using-d-i.xml:3527 +#: using-d-i.xml:3528 #, no-c-format msgid "" "If the firmware was loaded from loose firmware files, the firmware copied to " diff --git a/po/pot/boot-installer.pot b/po/pot/boot-installer.pot index f733e1824..9d6d54644 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: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -45,19 +45,19 @@ msgid "Booting from TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:43 boot-installer.xml:653 boot-installer.xml:1192 boot-installer.xml:1683 boot-installer.xml:1792 +#: boot-installer.xml:43 boot-installer.xml:675 boot-installer.xml:1215 boot-installer.xml:1706 boot-installer.xml:1815 #, 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:48 boot-installer.xml:658 boot-installer.xml:1197 boot-installer.xml:1688 boot-installer.xml:1797 +#: boot-installer.xml:48 boot-installer.xml:680 boot-installer.xml:1220 boot-installer.xml:1711 boot-installer.xml:1820 #, 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:53 boot-installer.xml:663 boot-installer.xml:1202 boot-installer.xml:1693 boot-installer.xml:1802 +#: boot-installer.xml:53 boot-installer.xml:685 boot-installer.xml:1225 boot-installer.xml:1716 boot-installer.xml:1825 #, no-c-format msgid "The installation method to support network booting is described in ." msgstr "" @@ -69,25 +69,25 @@ msgid "Booting from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:70 boot-installer.xml:340 boot-installer.xml:811 boot-installer.xml:1469 boot-installer.xml:1831 +#: boot-installer.xml:70 boot-installer.xml:340 boot-installer.xml:834 boot-installer.xml:1492 boot-installer.xml:1854 #, 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:81 boot-installer.xml:351 boot-installer.xml:822 boot-installer.xml:1480 boot-installer.xml:1842 +#: boot-installer.xml:81 boot-installer.xml:351 boot-installer.xml:845 boot-installer.xml:1503 boot-installer.xml:1865 #, 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:89 boot-installer.xml:359 boot-installer.xml:830 boot-installer.xml:1488 boot-installer.xml:1850 +#: boot-installer.xml:89 boot-installer.xml:359 boot-installer.xml:853 boot-installer.xml:1511 boot-installer.xml:1873 #, 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:97 boot-installer.xml:367 boot-installer.xml:838 boot-installer.xml:1496 boot-installer.xml:1858 +#: boot-installer.xml:97 boot-installer.xml:367 boot-installer.xml:861 boot-installer.xml:1519 boot-installer.xml:1881 #, no-c-format msgid "If you have problems booting, see ." msgstr "" @@ -267,7 +267,7 @@ msgid "The installer will now start as usual." msgstr "" #. Tag: title -#: boot-installer.xml:334 boot-installer.xml:805 boot-installer.xml:1463 boot-installer.xml:1825 +#: boot-installer.xml:334 boot-installer.xml:828 boot-installer.xml:1486 boot-installer.xml:1848 #, no-c-format msgid "Booting from a CD-ROM" msgstr "" @@ -281,35 +281,47 @@ msgstr "" #. Tag: para #: boot-installer.xml:442 #, no-c-format -msgid "To start the installer from Windows, you must first obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in and ." +msgid "To start the installer from Windows, you can either" msgstr "" #. Tag: para -#: boot-installer.xml:448 +#: boot-installer.xml:447 +#, no-c-format +msgid "obtain CD-ROM/DVD-ROM or USB memory stick installation media as described in and , or" +msgstr "" + +#. Tag: para +#: boot-installer.xml:453 +#, no-c-format +msgid "download a standalone Windows executable, which is available as tools/win32-loader/stable/win32-loader.exe on the &debian; mirrors," +msgstr "" + +#. Tag: para +#: boot-installer.xml:461 #, no-c-format msgid "If you use an installation CD or DVD, a pre-installation program should be launched automatically when you insert the disc. In case Windows does not start it automatically, or if you are using a USB memory stick, you can run it manually by accessing the device and executing setup.exe." msgstr "" #. Tag: para -#: boot-installer.xml:456 +#: boot-installer.xml:469 #, no-c-format -msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to start the &debian-gnu; installer." +msgid "After the program has been started, a few preliminary questions will be asked and the system will be prepared to reboot into the &debian-gnu; installer." msgstr "" #. Tag: title -#: boot-installer.xml:465 +#: boot-installer.xml:479 #, no-c-format msgid "Booting from DOS" msgstr "" #. Tag: para -#: boot-installer.xml:466 +#: boot-installer.xml:480 #, no-c-format msgid "Boot into DOS (not Windows). To do this, you can for instance boot from a recovery or diagnostic disk." msgstr "" #. Tag: para -#: boot-installer.xml:471 +#: boot-installer.xml:485 #, no-c-format msgid "" "If you can access the installation CD, change the current drive to the CD-ROM drive, e.g. \n" @@ -318,7 +330,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:481 +#: boot-installer.xml:495 #, no-c-format msgid "" "Enter the subdirectory for the flavor you chose, e.g., \n" @@ -329,37 +341,37 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:499 +#: boot-installer.xml:513 #, no-c-format msgid "Booting from Linux Using LILO or GRUB" msgstr "" #. Tag: para -#: boot-installer.xml:502 +#: boot-installer.xml:516 #, 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:507 +#: boot-installer.xml:521 #, 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/&architecture;/initrd.gz file and its corresponding kernel netboot/debian-installer/&architecture;/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:517 +#: boot-installer.xml:531 #, 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 (or DVD) 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/DVD image, without needing the network." msgstr "" #. Tag: para -#: boot-installer.xml:526 +#: boot-installer.xml:540 #, 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:547 +#: boot-installer.xml:561 #, no-c-format msgid "" "image=/boot/newinstall/vmlinuz\n" @@ -368,19 +380,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:547 +#: boot-installer.xml:561 #, 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:556 +#: boot-installer.xml:570 #, no-c-format -msgid "The procedure for GRUB is quite similar. Locate your menu.lst in the /boot/grub/ directory (or sometimes /boot/boot/grub/) and add an entry for the installer, for example (assuming /boot is on the first partition of the first disk in the system):" +msgid "The procedure for GRUB1 is quite similar. Locate your menu.lst in the /boot/grub/ directory (or sometimes /boot/boot/grub/) and add an entry for the installer, for example (assuming /boot is on the first partition of the first disk in the system):" msgstr "" #. Tag: screen -#: boot-installer.xml:564 +#: boot-installer.xml:578 #, no-c-format msgid "" "title New Install\n" @@ -390,133 +402,152 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:566 +#: boot-installer.xml:580 +#, no-c-format +msgid "The procedure for GRUB2 is very similar. The file is named grub.cfg instead of menu.lst. An entry for the installer would be for instance for example:" +msgstr "" + +#. Tag: screen +#: boot-installer.xml:586 +#, no-c-format +msgid "" + "menuentry 'New Install' {\n" + "insmod part_msdos\n" + "insmod ext2\n" + "set root='(hd0,msdos1)'\n" + "linux /boot/newinstall/vmlinuz\n" + "initrd /boot/newinstall/initrd.gz\n" + "}" +msgstr "" + +#. Tag: para +#: boot-installer.xml:588 #, no-c-format msgid "From here on, there should be no difference between GRUB or LILO." msgstr "" #. Tag: title -#: boot-installer.xml:575 +#: boot-installer.xml:597 #, no-c-format msgid "Booting from USB Memory Stick" msgstr "" #. Tag: para -#: boot-installer.xml:576 +#: boot-installer.xml:598 #, 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:589 boot-installer.xml:1732 +#: boot-installer.xml:611 boot-installer.xml:1755 #, no-c-format msgid "Booting from Floppies" msgstr "" #. Tag: para -#: boot-installer.xml:590 boot-installer.xml:1740 +#: boot-installer.xml:612 boot-installer.xml:1763 #, 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:597 +#: boot-installer.xml:619 #, 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:603 +#: boot-installer.xml:625 #, 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 install root=/dev/hdc at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:613 +#: boot-installer.xml:635 #, 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:622 +#: boot-installer.xml:644 #, 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:628 +#: boot-installer.xml:650 #, 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:637 +#: boot-installer.xml:659 #, 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: title -#: boot-installer.xml:647 boot-installer.xml:1174 boot-installer.xml:1315 boot-installer.xml:1369 boot-installer.xml:1677 boot-installer.xml:1786 +#: boot-installer.xml:669 boot-installer.xml:1197 boot-installer.xml:1338 boot-installer.xml:1392 boot-installer.xml:1700 boot-installer.xml:1809 #, no-c-format msgid "Booting with TFTP" msgstr "" #. Tag: para -#: boot-installer.xml:671 +#: boot-installer.xml:693 #, no-c-format msgid "There are various ways to do a TFTP boot on i386." msgstr "" #. Tag: title -#: boot-installer.xml:677 +#: boot-installer.xml:699 #, no-c-format msgid "NIC or Motherboard that support PXE" msgstr "" #. Tag: para -#: boot-installer.xml:678 +#: boot-installer.xml:700 #, 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:689 +#: boot-installer.xml:711 #, no-c-format msgid "NIC with Network BootROM" msgstr "" #. Tag: para -#: boot-installer.xml:690 +#: boot-installer.xml:712 #, no-c-format msgid "It could be that your Network Interface Card provides TFTP boot functionality." msgstr "" #. Tag: para -#: boot-installer.xml:695 +#: boot-installer.xml:717 #, 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:703 +#: boot-installer.xml:725 #, no-c-format msgid "Etherboot" msgstr "" #. Tag: para -#: boot-installer.xml:704 +#: boot-installer.xml:726 #, no-c-format msgid "The etherboot project provides bootdiskettes and even bootroms that do a TFTPboot." msgstr "" #. Tag: title -#: boot-installer.xml:714 +#: boot-installer.xml:736 #, no-c-format msgid "The Boot Screen" msgstr "" #. Tag: para -#: boot-installer.xml:715 +#: boot-installer.xml:737 #, no-c-format msgid "" "When the installer boots, you should be presented with a friendly graphical screen showing the &debian; logo and a menu: \n" @@ -532,25 +563,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:725 +#: boot-installer.xml:747 #, no-c-format -msgid "For a normal installation, select either the Install or the Graphical install entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter — and press &enterkey; to boot the installer." +msgid "For a normal installation, select either the Install or the Graphical install entry — using either the arrow keys on your keyboard or by typing the first (highlighted) letter, the Install entry is already selected by default — and press &enterkey; to boot the installer." msgstr "" #. Tag: para -#: boot-installer.xml:732 +#: boot-installer.xml:755 #, no-c-format msgid "The Advanced options entry gives access to a second menu that allows to boot the installer in expert mode, in rescue mode and for automated installs." msgstr "" #. Tag: para -#: boot-installer.xml:738 +#: boot-installer.xml:761 #, no-c-format msgid "If you wish or need to add any boot parameters for either the installer or the kernel, press &tabkey;. This will display the default boot command for the selected menu entry and allow to add additional options. The help screens (see below) list some common possible options. Press &enterkey; to boot the installer with your options; pressing &escapekey; will return you to the boot menu and undo any changes you made." msgstr "" #. Tag: para -#: boot-installer.xml:747 +#: boot-installer.xml:770 #, no-c-format msgid "" "Choosing the Help entry will result in the first help screen being displayed which gives an overview of all available help screens. Note that it is not possible to return to the boot menu after the help screens have been displayed. However, the F3 and F4 help screens list commands that are equivalent to the boot methods listed in the menu. All help screens have a boot prompt at which the boot command can be typed: \n" @@ -559,259 +590,259 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:766 +#: boot-installer.xml:789 #, no-c-format msgid "The keyboard is assumed to have a default American English layout at this point. This means that if your keyboard has a different (language-specific) layout, the characters that appear on the screen may be different from what you'd expect when you type parameters. Wikipedia has a schema of the US keyboard layout which can be used as a reference to find the correct keys to use." msgstr "" #. Tag: para -#: boot-installer.xml:776 +#: boot-installer.xml:799 #, no-c-format msgid "If you are using a system that has the BIOS configured to use serial console, you may not be able to see the initial graphical splash screen upon booting the installer; you may even not see the boot menu. The same can happen if you are installing the system via a remote management device that provides a text interface to the VGA console. Examples of these devices include the text console of Compaq's integrated Lights Out (iLO) and HP's Integrated Remote Assistant (IRA)." msgstr "" #. Tag: para -#: boot-installer.xml:786 +#: boot-installer.xml:809 #, no-c-format msgid "To bypass the graphical boot screen you can either blindly press &escapekey; to get a text boot prompt, or (equally blindly) press H followed by &enterkey; to select the Help option described above. After that your keystrokes should be echoed at the prompt. To prevent the installer from using the framebuffer for the rest of the installation, you will also want to add vga=normal fb=false to the boot prompt, as described in the help text." msgstr "" #. Tag: title -#: boot-installer.xml:846 +#: boot-installer.xml:869 #, no-c-format msgid "CD Contents" msgstr "" #. Tag: para -#: boot-installer.xml:848 +#: boot-installer.xml:871 #, 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:864 +#: boot-installer.xml:887 #, 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:880 +#: boot-installer.xml:903 #, 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:889 +#: boot-installer.xml:912 #, 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:901 +#: boot-installer.xml:924 #, 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:920 +#: boot-installer.xml:943 #, no-c-format msgid "IMPORTANT" msgstr "" #. Tag: para -#: boot-installer.xml:921 +#: boot-installer.xml:944 #, 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:933 +#: boot-installer.xml:956 #, no-c-format msgid "Option 1: Booting from the Boot Option Maintenance Menu" msgstr "" #. Tag: para -#: boot-installer.xml:940 +#: boot-installer.xml:963 #, 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:946 +#: boot-installer.xml:969 #, 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:952 +#: boot-installer.xml:975 #, 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:963 +#: boot-installer.xml:986 #, 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:974 +#: boot-installer.xml:997 #, 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:986 +#: boot-installer.xml:1009 #, 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:996 +#: boot-installer.xml:1019 #, no-c-format msgid "Option 2: Booting from the EFI Shell" msgstr "" #. Tag: para -#: boot-installer.xml:997 +#: boot-installer.xml:1020 #, 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:1008 +#: boot-installer.xml:1031 #, 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:1014 +#: boot-installer.xml:1037 #, 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:1028 +#: boot-installer.xml:1051 #, 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:1035 +#: boot-installer.xml:1058 #, 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:1042 +#: boot-installer.xml:1065 #, no-c-format msgid "Enter elilo and press ENTER. This will start the boot load sequence." msgstr "" #. Tag: para -#: boot-installer.xml:1049 +#: boot-installer.xml:1072 #, 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:1063 +#: boot-installer.xml:1086 #, no-c-format msgid "Installing using a Serial Console" msgstr "" #. Tag: para -#: boot-installer.xml:1065 +#: boot-installer.xml:1088 #, 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:1076 +#: boot-installer.xml:1099 #, 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:1083 +#: boot-installer.xml:1106 #, 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:1094 +#: boot-installer.xml:1117 #, 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:1103 +#: boot-installer.xml:1126 #, 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:1112 +#: boot-installer.xml:1135 #, no-c-format msgid "Selecting the Boot Kernel and Options" msgstr "" #. Tag: para -#: boot-installer.xml:1114 +#: boot-installer.xml:1137 #, 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:1126 +#: boot-installer.xml:1149 #, 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:1144 +#: boot-installer.xml:1167 #, 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:1149 +#: boot-installer.xml:1172 #, 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:1156 +#: boot-installer.xml:1179 #, 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:1165 boot-installer.xml:1301 +#: boot-installer.xml:1188 boot-installer.xml:1324 #, 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:1176 +#: boot-installer.xml:1199 #, 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 through 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:1210 +#: boot-installer.xml:1233 #, 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:1221 +#: boot-installer.xml:1244 #, no-c-format msgid "Configuring the Server" msgstr "" #. Tag: para -#: boot-installer.xml:1222 +#: boot-installer.xml:1245 #, no-c-format msgid "" "A suitable TFTP entry for network booting an IA-64 system looks something like this: \n" @@ -824,13 +855,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1232 +#: boot-installer.xml:1255 #, 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:1242 +#: boot-installer.xml:1265 #, no-c-format msgid "" "# cd /var/lib/tftp\n" @@ -842,37 +873,37 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1242 +#: boot-installer.xml:1265 #, 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:1259 +#: boot-installer.xml:1282 #, no-c-format msgid "Configuring the Client" msgstr "" #. Tag: para -#: boot-installer.xml:1260 +#: boot-installer.xml:1283 #, 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:1292 +#: boot-installer.xml:1315 #, 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:1318 boot-installer.xml:1342 +#: boot-installer.xml:1341 boot-installer.xml:1365 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1319 +#: boot-installer.xml:1342 #, no-c-format msgid "" "After entering the command monitor use \n" @@ -883,19 +914,19 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1339 boot-installer.xml:1406 boot-installer.xml:2007 +#: boot-installer.xml:1362 boot-installer.xml:1429 boot-installer.xml:2041 #, no-c-format msgid "Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1343 +#: boot-installer.xml:1366 #, 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:1348 +#: boot-installer.xml:1371 #, 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" @@ -904,133 +935,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:1358 +#: boot-installer.xml:1381 #, no-c-format msgid "bootp(): append=\"root=/dev/sda1\"" msgstr "" #. Tag: title -#: boot-installer.xml:1372 boot-installer.xml:1409 +#: boot-installer.xml:1395 boot-installer.xml:1432 #, no-c-format msgid "Cobalt TFTP Booting" msgstr "" #. Tag: para -#: boot-installer.xml:1373 +#: boot-installer.xml:1396 #, 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:1383 +#: boot-installer.xml:1406 #, 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:1392 +#: boot-installer.xml:1415 #, 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." msgstr "" #. Tag: para -#: boot-installer.xml:1410 +#: boot-installer.xml:1433 #, 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:1425 +#: boot-installer.xml:1448 #, no-c-format msgid "s390 Limitations" msgstr "" #. Tag: para -#: boot-installer.xml:1426 +#: boot-installer.xml:1449 #, 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:1431 +#: boot-installer.xml:1454 #, 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:1442 +#: boot-installer.xml:1465 #, no-c-format msgid "s390 Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1443 +#: boot-installer.xml:1466 #, 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. A sample parm file parmfile.debian is provided with the installation images." msgstr "" #. Tag: para -#: boot-installer.xml:1503 +#: boot-installer.xml:1526 #, no-c-format msgid "Currently, the only &arch-title; subarchitectures that support CD-ROM booting are PReP (though not all systems) 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:1512 +#: boot-installer.xml:1535 #, 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:1521 +#: boot-installer.xml:1544 #, 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:1530 +#: boot-installer.xml:1553 #, no-c-format msgid "0 > boot cd:,\\install\\yaboot" msgstr "" #. Tag: title -#: boot-installer.xml:1536 +#: boot-installer.xml:1559 #, no-c-format msgid "Booting from Hard Disk" msgstr "" #. Tag: para -#: boot-installer.xml:1542 +#: boot-installer.xml:1565 #, 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:1548 +#: boot-installer.xml:1571 #, no-c-format msgid "To boot the installer from hard disk, you will have already completed downloading and placing the needed files as described in ." msgstr "" #. Tag: title -#: boot-installer.xml:1568 +#: boot-installer.xml:1591 #, no-c-format msgid "Booting OldWorld PowerMacs from MacOS" msgstr "" #. Tag: para -#: boot-installer.xml:1569 +#: boot-installer.xml:1592 #, 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:1587 +#: boot-installer.xml:1610 #, no-c-format msgid "Booting NewWorld Macs from OpenFirmware" msgstr "" #. Tag: para -#: boot-installer.xml:1588 +#: boot-installer.xml:1611 #, 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 . You will now have to boot into OpenFirmware (see ). At the prompt, type \n" @@ -1041,31 +1072,31 @@ msgid "" msgstr "" #. Tag: title -#: boot-installer.xml:1620 +#: boot-installer.xml:1643 #, no-c-format msgid "Booting from USB memory stick" msgstr "" #. Tag: para -#: boot-installer.xml:1621 +#: boot-installer.xml:1644 #, no-c-format msgid "Currently, NewWorld PowerMac systems are known to support USB booting." msgstr "" #. Tag: para -#: boot-installer.xml:1627 +#: boot-installer.xml:1650 #, 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. See ." msgstr "" #. Tag: para -#: boot-installer.xml:1636 +#: boot-installer.xml:1659 #, 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:1648 +#: boot-installer.xml:1671 #, no-c-format msgid "" "Having worked out the device path, use a command like this to boot the installer: \n" @@ -1074,25 +1105,25 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1662 +#: boot-installer.xml:1685 #, 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:1668 +#: boot-installer.xml:1691 #, 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:1701 +#: boot-installer.xml:1724 #, no-c-format msgid "Currently, PReP and New World PowerMac systems support netbooting." msgstr "" #. Tag: para -#: boot-installer.xml:1705 +#: boot-installer.xml:1728 #, no-c-format msgid "" "On machines with Open Firmware, such as NewWorld Power Macs, enter the boot monitor (see ) and use the command \n" @@ -1105,169 +1136,181 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:1733 +#: boot-installer.xml:1756 #, 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:1745 +#: boot-installer.xml:1768 #, 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:1751 +#: boot-installer.xml:1774 #, 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:1758 +#: boot-installer.xml:1781 #, 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:1769 +#: boot-installer.xml:1792 #, no-c-format msgid "PowerPC Boot Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:1770 +#: boot-installer.xml:1793 #, 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:1810 +#: boot-installer.xml:1833 #, 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. You can pass extra boot parameters to &d-i; at the end of the boot command." msgstr "" #. Tag: para -#: boot-installer.xml:1865 +#: boot-installer.xml:1888 #, 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)." msgstr "" #. Tag: title -#: boot-installer.xml:1874 +#: boot-installer.xml:1897 #, no-c-format msgid "IDPROM Messages" msgstr "" #. Tag: para -#: boot-installer.xml:1875 +#: boot-installer.xml:1898 #, 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: title -#: boot-installer.xml:1894 +#: boot-installer.xml:1917 #, no-c-format msgid "Accessibility" msgstr "" #. Tag: para -#: boot-installer.xml:1895 +#: boot-installer.xml:1918 #, no-c-format -msgid "Some users may need specific support because of e.g. some visual impairment. USB braille displays are detected automatically, but most other Most accessibility features have to be enabled manually. On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes. Some boot parameters can then be appended to enable accessibility features (see also ). Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." +msgid "Some users may need specific support because of e.g. some visual impairment. USB braille displays are detected automatically (not serial displays connected via a serial-to-USB converter), but most other Most accessibility features have to be enabled manually. On machines that support it, the boot menu emits a beep when it is ready to receive keystrokes. Some boot parameters can then be appended to enable accessibility features (see also ). Note that on most architectures the boot loader interprets your keyboard as a QWERTY keyboard." msgstr "" #. Tag: title -#: boot-installer.xml:1914 +#: boot-installer.xml:1938 #, no-c-format msgid "USB Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1915 +#: boot-installer.xml:1939 #, no-c-format msgid "USB braille displays should be automatically detected. A textual version of the installer will then be automatically selected, and support for the braille display will be automatically installed on the target system. You can thus just press &enterkey; at the boot menu. Once brltty is started, you can choose a braille table by entering the preference menu. Documentation on key bindings for braille devices is available on the brltty website." msgstr "" #. Tag: title -#: boot-installer.xml:1930 +#: boot-installer.xml:1954 #, no-c-format msgid "Serial Braille Displays" msgstr "" #. Tag: para -#: boot-installer.xml:1931 +#: boot-installer.xml:1955 #, no-c-format -msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the brltty=driver,port,table boot parameter to tell brltty which driver it should use. driver should be replaced by the two-letter driver code for your terminal (see the driver code list). port should be replaced by the name of the serial port the display is connected to, ttyS0 is the default. table is the name of the braille table to be used (see the table code list); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the brltty website." +msgid "Serial braille displays cannot safely be automatically detected (since that may damage some of them). You thus need to append the brltty=driver,port,table boot parameter to tell brltty which driver it should use. driver should be replaced by the two-letter driver code for your terminal (see the BRLTTY manual). port should be replaced by the name of the serial port the display is connected to, ttyS0 is the default, ttyUSB0 can be typically used when using a serial-to-USB converter. table is the name of the braille table to be used (see the BRLTTY manual); the English table is the default. Note that the table can be changed later by entering the preference menu. Documentation on key bindings for braille devices is available on the brltty website." msgstr "" #. Tag: title -#: boot-installer.xml:1953 +#: boot-installer.xml:1977 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: boot-installer.xml:1954 +#: boot-installer.xml:1978 #, no-c-format msgid "Support for hardware speech synthesis devices is available only alongside support for graphical installer. You thus need to select the Graphical install entry in the boot menu." msgstr "" #. Tag: para -#: boot-installer.xml:1960 +#: boot-installer.xml:1984 #, no-c-format msgid "Hardware speech synthesis devices cannot be automatically detected. You thus need to append the speakup.synth=driver boot parameter to tell speakup which driver it should use. driver should be replaced by the driver code for your device (see driver code list). The textual version of the installer will then be automatically selected, and support for the speech synthesis device will be automatically installed on the target system." msgstr "" #. Tag: title -#: boot-installer.xml:1975 +#: boot-installer.xml:1999 #, no-c-format msgid "Board Devices" msgstr "" #. Tag: para -#: boot-installer.xml:1976 +#: boot-installer.xml:2000 #, no-c-format msgid "Some accessibility devices are actual boards that are plugged inside the machine and that read text directly from the video memory. To get them to work framebuffer support must be disabled by using the vga=normal fb=false boot parameter. This will however reduce the number of available languages." msgstr "" #. Tag: para -#: boot-installer.xml:1984 +#: boot-installer.xml:2008 #, no-c-format msgid "If desired a textual version of the bootloader can be activated before adding the boot parameter by typing h &enterkey;." msgstr "" #. Tag: title -#: boot-installer.xml:1992 +#: boot-installer.xml:2016 #, no-c-format msgid "High-Contrast Theme" msgstr "" #. Tag: para -#: boot-installer.xml:1993 +#: boot-installer.xml:2017 #, no-c-format msgid "For users with low vision, the installer can use a high-contrast theme that makes it more readable. To enable it, append the theme=dark boot parameter." msgstr "" +#. Tag: title +#: boot-installer.xml:2026 +#, no-c-format +msgid "Preseeding" +msgstr "" + #. Tag: para -#: boot-installer.xml:2008 +#: boot-installer.xml:2027 +#, no-c-format +msgid "Alternatively, &debian; can be installed completely automatically by using preseeding. This is documented in ." +msgstr "" + +#. Tag: para +#: boot-installer.xml:2042 #, 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:2015 +#: boot-installer.xml:2049 #, 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:2022 +#: boot-installer.xml:2056 #, 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:2031 +#: boot-installer.xml:2065 #, no-c-format msgid "" "When the kernel boots, a message \n" @@ -1276,493 +1319,493 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2047 +#: boot-installer.xml:2081 #, no-c-format msgid "If you are booting with a serial console, generally the kernel will autodetect this. 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 In order to ensure the terminal type used by the installer matches your terminal emulator, the parameter TERM=type can be added. Note that the installer only supports the following terminal types: linux, bterm, ansi, vt102 and dumb. The default for serial console in &d-i; is vt102. ." msgstr "" #. Tag: para -#: boot-installer.xml:2071 +#: boot-installer.xml:2105 #, 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:2082 +#: boot-installer.xml:2116 #, no-c-format msgid "&debian; Installer Parameters" msgstr "" #. Tag: para -#: boot-installer.xml:2083 +#: boot-installer.xml:2117 #, 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: para -#: boot-installer.xml:2096 +#: boot-installer.xml:2130 #, no-c-format msgid "A number of parameters have a short form that helps avoid the limitations of the kernel command line options and makes entering the parameters easier. If a parameter has a short form, it will be listed in brackets behind the (normal) long form. Examples in this manual will normally use the short form too." msgstr "" #. Tag: term -#: boot-installer.xml:2108 +#: boot-installer.xml:2142 #, no-c-format msgid "debconf/priority (priority)" msgstr "" #. Tag: para -#: boot-installer.xml:2109 +#: boot-installer.xml:2143 #, no-c-format msgid "This parameter sets the lowest priority of messages to be displayed." msgstr "" #. Tag: para -#: boot-installer.xml:2113 +#: boot-installer.xml:2147 #, 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:2120 +#: boot-installer.xml:2154 #, 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:2134 +#: boot-installer.xml:2168 #, no-c-format msgid "DEBIAN_FRONTEND" msgstr "" #. Tag: para -#: boot-installer.xml:2135 +#: boot-installer.xml:2169 #, 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 that support it, the graphical installer uses the gtk 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. Some specialized types of install media may only offer a limited selection of frontends, but the newt and text frontends are available on most default install media. On architectures that support it, the graphical installer uses the gtk frontend." msgstr "" #. Tag: term -#: boot-installer.xml:2164 +#: boot-installer.xml:2200 #, no-c-format msgid "BOOT_DEBUG" msgstr "" #. Tag: para -#: boot-installer.xml:2165 +#: boot-installer.xml:2201 #, 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:2174 +#: boot-installer.xml:2210 #, no-c-format msgid "BOOT_DEBUG=0" msgstr "" #. Tag: para -#: boot-installer.xml:2175 +#: boot-installer.xml:2211 #, no-c-format msgid "This is the default." msgstr "" #. Tag: userinput -#: boot-installer.xml:2179 +#: boot-installer.xml:2215 #, no-c-format msgid "BOOT_DEBUG=1" msgstr "" #. Tag: para -#: boot-installer.xml:2180 +#: boot-installer.xml:2216 #, no-c-format msgid "More verbose than usual." msgstr "" #. Tag: userinput -#: boot-installer.xml:2184 +#: boot-installer.xml:2220 #, no-c-format msgid "BOOT_DEBUG=2" msgstr "" #. Tag: para -#: boot-installer.xml:2185 +#: boot-installer.xml:2221 #, no-c-format msgid "Lots of debugging information." msgstr "" #. Tag: userinput -#: boot-installer.xml:2189 +#: boot-installer.xml:2225 #, no-c-format msgid "BOOT_DEBUG=3" msgstr "" #. Tag: para -#: boot-installer.xml:2190 +#: boot-installer.xml:2226 #, 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:2204 +#: boot-installer.xml:2240 #, no-c-format msgid "INSTALL_MEDIA_DEV" msgstr "" #. Tag: para -#: boot-installer.xml:2205 +#: boot-installer.xml:2241 #, 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:2211 +#: boot-installer.xml:2247 #, 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:2221 +#: boot-installer.xml:2257 #, no-c-format msgid "lowmem" msgstr "" #. Tag: para -#: boot-installer.xml:2222 +#: boot-installer.xml:2258 #, no-c-format msgid "Can be used to force the installer to a lowmem level higher than the one the installer sets by default based on available memory. Possible values are 1 and 2. See also ." msgstr "" #. Tag: term -#: boot-installer.xml:2232 +#: boot-installer.xml:2268 #, no-c-format msgid "noshell" msgstr "" #. Tag: para -#: boot-installer.xml:2233 +#: boot-installer.xml:2269 #, no-c-format msgid "Prevents the installer from offering interactive shells on tty2 and tty3. Useful for unattended installations where physical security is limited." msgstr "" #. Tag: term -#: boot-installer.xml:2242 +#: boot-installer.xml:2278 #, no-c-format msgid "debian-installer/framebuffer (fb)" msgstr "" #. Tag: para -#: boot-installer.xml:2243 +#: boot-installer.xml:2279 #, 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 using the parameter vga=normal fb=false. 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:2252 +#: boot-installer.xml:2288 #, no-c-format msgid "Such problems have been reported on hppa." msgstr "" #. Tag: para -#: boot-installer.xml:2256 +#: boot-installer.xml:2292 #, 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:2270 +#: boot-installer.xml:2306 #, no-c-format msgid "debian-installer/theme (theme)" msgstr "" #. Tag: para -#: boot-installer.xml:2271 +#: boot-installer.xml:2307 #, 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 theme=dark." msgstr "" #. Tag: term -#: boot-installer.xml:2283 boot-installer.xml:2516 +#: boot-installer.xml:2319 boot-installer.xml:2552 #, no-c-format msgid "netcfg/disable_dhcp" msgstr "" #. Tag: para -#: boot-installer.xml:2284 +#: boot-installer.xml:2320 #, 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:2291 +#: boot-installer.xml:2327 #, 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:2302 +#: boot-installer.xml:2338 #, no-c-format msgid "hw-detect/start_pcmcia" msgstr "" #. Tag: para -#: boot-installer.xml:2303 +#: boot-installer.xml:2339 #, 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:2313 +#: boot-installer.xml:2349 #, no-c-format msgid "disk-detect/dmraid/enable (dmraid)" msgstr "" #. Tag: para -#: boot-installer.xml:2314 +#: boot-installer.xml:2350 #, no-c-format msgid "Set to true to enable support for Serial ATA RAID (also called ATA RAID, BIOS RAID or fake RAID) disks in the installer. Note that this support is currently experimental. Additional information can be found on the &debian; Installer Wiki." msgstr "" #. Tag: term -#: boot-installer.xml:2325 +#: boot-installer.xml:2361 #, no-c-format msgid "preseed/url (url)" msgstr "" #. Tag: para -#: boot-installer.xml:2326 +#: boot-installer.xml:2362 #, no-c-format msgid "Specify the url to a preconfiguration file to download and use for automating the install. See ." msgstr "" #. Tag: term -#: boot-installer.xml:2335 +#: boot-installer.xml:2371 #, no-c-format msgid "preseed/file (file)" msgstr "" #. Tag: para -#: boot-installer.xml:2336 +#: boot-installer.xml:2372 #, no-c-format msgid "Specify the path to a preconfiguration file to load for automating the install. See ." msgstr "" #. Tag: term -#: boot-installer.xml:2345 +#: boot-installer.xml:2381 #, no-c-format msgid "preseed/interactive" msgstr "" #. Tag: para -#: boot-installer.xml:2346 +#: boot-installer.xml:2382 #, no-c-format msgid "Set to true to display questions even if they have been preseeded. Can be useful for testing or debugging a preconfiguration file. Note that this will have no effect on parameters that are passed as boot parameters, but for those a special syntax can be used. See for details." msgstr "" #. Tag: term -#: boot-installer.xml:2358 +#: boot-installer.xml:2394 #, no-c-format msgid "auto-install/enable (auto)" msgstr "" #. Tag: para -#: boot-installer.xml:2359 +#: boot-installer.xml:2395 #, no-c-format msgid "Delay questions that are normally asked before preseeding is possible until after the network is configured. See for details about using this to automate installs." msgstr "" #. Tag: term -#: boot-installer.xml:2370 +#: boot-installer.xml:2406 #, no-c-format msgid "finish-install/keep-consoles" msgstr "" #. Tag: para -#: boot-installer.xml:2371 +#: boot-installer.xml:2407 #, no-c-format msgid "During installations from serial or management console, the regular virtual consoles (VT1 to VT6) are normally disabled in /etc/inittab. Set to true to prevent this." msgstr "" #. Tag: term -#: boot-installer.xml:2382 +#: boot-installer.xml:2418 #, no-c-format msgid "cdrom-detect/eject" msgstr "" #. Tag: para -#: boot-installer.xml:2383 +#: boot-installer.xml:2419 #, 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:2392 +#: boot-installer.xml:2428 #, 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:2403 +#: boot-installer.xml:2439 #, no-c-format msgid "base-installer/install-recommends (recommends)" msgstr "" #. Tag: para -#: boot-installer.xml:2404 +#: boot-installer.xml:2440 #, no-c-format msgid "By setting this option to false, the package management system will be configured to not automatically install Recommends, both during the installation and for the installed system. See also ." msgstr "" #. Tag: para -#: boot-installer.xml:2411 +#: boot-installer.xml:2447 #, no-c-format msgid "Note that this option allows to have a leaner system, but can also result in features being missing that you might normally expect to be available. You may have to manually install some of the recommended packages to obtain the full functionality you want. This option should therefore only be used by very experienced users." msgstr "" #. Tag: term -#: boot-installer.xml:2423 +#: boot-installer.xml:2459 #, no-c-format msgid "debian-installer/allow_unauthenticated" msgstr "" #. Tag: para -#: boot-installer.xml:2424 +#: boot-installer.xml:2460 #, no-c-format msgid "By default the installer requires that repositories be authenticated using a known gpg key. Set to true to disable that authentication. Warning: insecure, not recommended." msgstr "" #. Tag: term -#: boot-installer.xml:2435 +#: boot-installer.xml:2471 #, no-c-format msgid "ramdisk_size" msgstr "" #. Tag: para -#: boot-installer.xml:2436 +#: boot-installer.xml:2472 #, no-c-format msgid "This parameter should already be set to a correct value where needed; set it only it you see errors during the boot that indicate the ramdisk could not be loaded completely. The value is in kB." msgstr "" #. Tag: term -#: boot-installer.xml:2446 +#: boot-installer.xml:2482 #, no-c-format msgid "rescue/enable" msgstr "" #. Tag: para -#: boot-installer.xml:2447 +#: boot-installer.xml:2483 #, no-c-format msgid "Set to true to enter rescue mode rather than performing a normal installation. See ." msgstr "" #. Tag: title -#: boot-installer.xml:2460 +#: boot-installer.xml:2496 #, no-c-format msgid "Using boot parameters to answer questions" msgstr "" #. Tag: para -#: boot-installer.xml:2461 +#: boot-installer.xml:2497 #, 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:2473 +#: boot-installer.xml:2509 #, no-c-format msgid "debian-installer/language (language)" msgstr "" #. Tag: term -#: boot-installer.xml:2474 +#: boot-installer.xml:2510 #, no-c-format msgid "debian-installer/country (country)" msgstr "" #. Tag: term -#: boot-installer.xml:2475 +#: boot-installer.xml:2511 #, no-c-format msgid "debian-installer/locale (locale)" msgstr "" #. Tag: para -#: boot-installer.xml:2476 +#: boot-installer.xml:2512 #, no-c-format msgid "There are two ways to specify the language, country and locale to use for the installation and the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2481 +#: boot-installer.xml:2517 #, no-c-format msgid "The first and easiest is to pass only the parameter locale. Language and country will then be derived from its value. You can for example use locale=de_CH to select German as language and Switzerland as country (de_CH.UTF-8 will be set as default locale for the installed system). Limitation is that not all possible combinations of language, country and locale can be achieved this way." msgstr "" #. Tag: para -#: boot-installer.xml:2490 +#: boot-installer.xml:2526 #, no-c-format msgid "The second, more flexible option is to specify language and country separately. In this case locale can optionally be added to specify a specific default locale for the installed system. Example: language=en country=DE locale=en_GB.UTF-8." msgstr "" #. Tag: term -#: boot-installer.xml:2502 +#: boot-installer.xml:2538 #, no-c-format msgid "anna/choose_modules (modules)" msgstr "" #. Tag: para -#: boot-installer.xml:2503 +#: boot-installer.xml:2539 #, no-c-format msgid "Can be used to automatically load installer components that are not loaded by default. Examples of optional components that may be useful are openssh-client-udeb (so you can use scp during the installation) and ppp-udeb (see )." msgstr "" #. Tag: para -#: boot-installer.xml:2517 +#: boot-installer.xml:2553 #, 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:2526 +#: boot-installer.xml:2562 #, no-c-format msgid "mirror/protocol (protocol)" msgstr "" #. Tag: para -#: boot-installer.xml:2527 +#: boot-installer.xml:2563 #, no-c-format msgid "By default the installer will use the http protocol to download files from &debian; mirrors and changing that to ftp is not possible during installations at normal priority. By setting this parameter to ftp, you can force the installer to use that protocol instead. Note that you cannot select an ftp mirror from a list, you have to enter the hostname manually." msgstr "" #. Tag: term -#: boot-installer.xml:2540 +#: boot-installer.xml:2576 #, no-c-format msgid "tasksel:tasksel/first (tasks)" msgstr "" #. Tag: para -#: boot-installer.xml:2541 +#: boot-installer.xml:2577 #, 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." msgstr "" #. Tag: title -#: boot-installer.xml:2555 +#: boot-installer.xml:2591 #, no-c-format msgid "Passing parameters to kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2556 +#: boot-installer.xml:2592 #, 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:2569 +#: boot-installer.xml:2605 #, 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:2576 +#: boot-installer.xml:2612 #, no-c-format msgid "" "The syntax to use to set parameters for modules is: \n" @@ -1771,133 +1814,133 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2586 +#: boot-installer.xml:2622 #, no-c-format msgid "3c509.xcvr=3 3c509.irq=10" msgstr "" #. Tag: title -#: boot-installer.xml:2592 +#: boot-installer.xml:2628 #, no-c-format msgid "Blacklisting kernel modules" msgstr "" #. Tag: para -#: boot-installer.xml:2593 +#: boot-installer.xml:2629 #, no-c-format msgid "Sometimes it may be necessary to blacklist a module to prevent it from being loaded automatically by the kernel and udev. One reason could be that a particular module causes problems with your hardware. The kernel also sometimes lists two different drivers for the same device. This can cause the device to not work correctly if the drivers conflict or if the wrong driver is loaded first." msgstr "" #. Tag: para -#: boot-installer.xml:2602 +#: boot-installer.xml:2638 #, no-c-format msgid "You can blacklist a module using the following syntax: module_name.blacklist=yes. This will cause the module to be blacklisted in /etc/modprobe.d/blacklist.local both during the installation and for the installed system." msgstr "" #. Tag: para -#: boot-installer.xml:2610 +#: boot-installer.xml:2646 #, no-c-format msgid "Note that a module may still be loaded by the installation system itself. You can prevent that from happening by running the installation in expert mode and unselecting the module from the list of modules displayed during the hardware detection phases." msgstr "" #. Tag: title -#: boot-installer.xml:2626 +#: boot-installer.xml:2662 #, no-c-format msgid "Troubleshooting the Installation Process" msgstr "" #. Tag: title -#: boot-installer.xml:2631 +#: boot-installer.xml:2667 #, no-c-format msgid "CD-ROM Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2632 +#: boot-installer.xml:2668 #, 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:2639 +#: boot-installer.xml:2675 #, no-c-format msgid "There are 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:2645 +#: boot-installer.xml:2681 #, no-c-format msgid "There are two very simple things that you should try first." msgstr "" #. Tag: para -#: boot-installer.xml:2650 +#: boot-installer.xml:2686 #, 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:2656 +#: boot-installer.xml:2692 #, 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:2666 +#: boot-installer.xml:2702 #, 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:2672 +#: boot-installer.xml:2708 #, 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:2680 +#: boot-installer.xml:2716 #, no-c-format msgid "Common issues" msgstr "" #. Tag: para -#: boot-installer.xml:2683 +#: boot-installer.xml:2719 #, 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:2689 +#: boot-installer.xml:2725 #, no-c-format msgid "If your system boots correctly from the CD-ROM, it does not necessarily mean that &arch-kernel; also supports the CD-ROM (or, more correctly, the controller that your CD-ROM drive is connected to)." msgstr "" #. Tag: para -#: boot-installer.xml:2696 +#: boot-installer.xml:2732 #, 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:2707 +#: boot-installer.xml:2743 #, no-c-format msgid "How to investigate and maybe solve issues" msgstr "" #. Tag: para -#: boot-installer.xml:2708 +#: boot-installer.xml:2744 #, no-c-format msgid "If the CD-ROM fails to boot, try the suggestions listed below." msgstr "" #. Tag: para -#: boot-installer.xml:2713 +#: boot-installer.xml:2749 #, 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:2719 +#: boot-installer.xml:2755 #, 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" @@ -1907,7 +1950,7 @@ msgid "" msgstr "" #. Tag: screen -#: boot-installer.xml:2732 +#: boot-installer.xml:2768 #, no-c-format msgid "" "$ dd if=/dev/cdrom | \\\n" @@ -1920,19 +1963,19 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2737 +#: boot-installer.xml:2773 #, 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 &arch-kernel; 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:2749 +#: boot-installer.xml:2785 #, 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:2756 +#: boot-installer.xml:2792 #, 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" @@ -1945,13 +1988,13 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2770 +#: boot-installer.xml:2806 #, 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/cdrom." msgstr "" #. Tag: para -#: boot-installer.xml:2778 +#: boot-installer.xml:2814 #, no-c-format msgid "" "Use the mount command to check if the CD-ROM is already mounted; if not, try mounting it manually: \n" @@ -1960,7 +2003,7 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2788 +#: boot-installer.xml:2824 #, no-c-format msgid "" "Check if DMA is currently enabled: \n" @@ -1973,163 +2016,163 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:2803 +#: boot-installer.xml:2839 #, 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:2818 +#: boot-installer.xml:2854 #, no-c-format msgid "Floppy Disk Reliability" msgstr "" #. Tag: para -#: boot-installer.xml:2820 +#: boot-installer.xml:2856 #, 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:2825 +#: boot-installer.xml:2861 #, 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:2834 +#: boot-installer.xml:2870 #, 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:2843 +#: boot-installer.xml:2879 #, 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:2849 +#: boot-installer.xml:2885 #, 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:2855 +#: boot-installer.xml:2891 #, 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:2864 +#: boot-installer.xml:2900 #, no-c-format msgid "Boot Configuration" msgstr "" #. Tag: para -#: boot-installer.xml:2866 +#: boot-installer.xml:2902 #, 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:2873 +#: boot-installer.xml:2909 #, 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:2879 +#: boot-installer.xml:2915 #, 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:2890 boot-installer.xml:2992 +#: boot-installer.xml:2926 boot-installer.xml:3028 #, no-c-format msgid "Common &arch-title; Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:2891 +#: boot-installer.xml:2927 #, 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:2896 +#: boot-installer.xml:2932 #, 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:2902 +#: boot-installer.xml:2938 #, 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:2911 +#: boot-installer.xml:2947 #, 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:2918 +#: boot-installer.xml:2954 #, no-c-format msgid "Some systems (especially laptops) that have a native resolution that is not a 4:3 ratio (i.e. not for example 800x600 or 1024x768) may have a blank display after the installer has been booted. In that case adding the boot parameter vga=788 The parameter vga=788 will activate the VESA framebuffer with a resolution of 800x600. This will probably work, but may not be the optimal resolution for your system. A list of supported resolutions can be obtained by using vga=ask, but you should be aware that list may not be complete. may help. If that does not work, try adding the boot parameter fb=false." msgstr "" #. Tag: para -#: boot-installer.xml:2936 +#: boot-installer.xml:2972 #, 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 to disable the framebuffer console. Only a reduced set of languages will be available during the installation due to limited console features. See for details." msgstr "" #. Tag: title -#: boot-installer.xml:2950 +#: boot-installer.xml:2986 #, no-c-format msgid "System Freeze During the PCMCIA Configuration Phase" msgstr "" #. Tag: para -#: boot-installer.xml:2951 +#: boot-installer.xml:2987 #, 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:2961 +#: boot-installer.xml:2997 #, 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:2978 +#: boot-installer.xml:3014 #, no-c-format msgid "System Freeze while Loading USB Modules" msgstr "" #. Tag: para -#: boot-installer.xml:2979 +#: boot-installer.xml:3015 #, 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 nousb parameter at the boot prompt." msgstr "" #. Tag: para -#: boot-installer.xml:2993 +#: boot-installer.xml:3029 #, no-c-format msgid "There are some common installation problems that are worth mentioning." msgstr "" #. Tag: title -#: boot-installer.xml:2999 +#: boot-installer.xml:3035 #, no-c-format msgid "Misdirected video output" msgstr "" #. Tag: para -#: boot-installer.xml:3000 +#: boot-installer.xml:3036 #, no-c-format msgid "" "It is fairly common for &arch-title; to have two video cards in one machine, for example an ATI card and a Sun Creator 3D. In some cases, this may result in the video output getting misdirected soon after the system boots. In typical cases, the display will only show: \n" @@ -2139,85 +2182,85 @@ msgid "" msgstr "" #. Tag: para -#: boot-installer.xml:3014 +#: boot-installer.xml:3050 #, no-c-format msgid "Note that you may also have to manually add this parameter to the silo configuration (edit /target/etc/silo.conf before rebooting) and, if you installed X11, modify the video driver in /etc/X11/xorg.conf." msgstr "" #. Tag: title -#: boot-installer.xml:3025 +#: boot-installer.xml:3061 #, no-c-format msgid "Failure to Boot or Install from CD-ROM" msgstr "" #. Tag: para -#: boot-installer.xml:3026 +#: boot-installer.xml:3062 #, no-c-format msgid "Some Sparc systems are notoriously difficult to boot from CD-ROM and even if they do boot, there may be inexplicable failures during the installation. Most problems have been reported with SunBlade systems." msgstr "" #. Tag: para -#: boot-installer.xml:3032 +#: boot-installer.xml:3068 #, no-c-format msgid "We recommend to install such systems by netbooting the installer." msgstr "" #. Tag: title -#: boot-installer.xml:3041 +#: boot-installer.xml:3077 #, no-c-format msgid "Interpreting the Kernel Startup Messages" msgstr "" #. Tag: para -#: boot-installer.xml:3043 +#: boot-installer.xml:3079 #, 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:3068 +#: boot-installer.xml:3104 #, no-c-format msgid "Reporting Installation Problems" msgstr "" #. Tag: para -#: boot-installer.xml:3069 +#: boot-installer.xml:3105 #, 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:3080 +#: boot-installer.xml:3116 #, 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:3091 +#: boot-installer.xml:3127 #, no-c-format msgid "Submitting Installation Reports" msgstr "" #. Tag: para -#: boot-installer.xml:3092 +#: boot-installer.xml:3128 #, 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:3099 +#: boot-installer.xml:3135 #, 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:3105 +#: boot-installer.xml:3141 #, 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 (aptitude install installation-report reportbug), configure reportbug as explained in , and run the command reportbug installation-reports." msgstr "" #. Tag: para -#: boot-installer.xml:3115 +#: boot-installer.xml:3151 #, 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" diff --git a/po/pot/hardware.pot b/po/pot/hardware.pot index f4c5dd767..f25ca29ac 100644 --- a/po/pot/hardware.pot +++ b/po/pot/hardware.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: 2010-10-29 05:56+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -447,19 +447,19 @@ msgid "This is the first official release of &debian-gnu; for the &arch-title; a msgstr "" #. Tag: title -#: hardware.xml:239 hardware.xml:275 hardware.xml:381 hardware.xml:400 hardware.xml:483 hardware.xml:541 hardware.xml:594 +#: hardware.xml:239 hardware.xml:275 hardware.xml:382 hardware.xml:401 hardware.xml:484 hardware.xml:542 hardware.xml:595 #, no-c-format msgid "CPU, Main Boards, and Video Support" msgstr "" #. Tag: para -#: hardware.xml:240 hardware.xml:401 +#: hardware.xml:240 hardware.xml:402 #, no-c-format msgid "Complete information concerning supported peripherals can be found at Linux Hardware Compatibility HOWTO. This section merely outlines the basics." msgstr "" #. Tag: title -#: hardware.xml:248 hardware.xml:409 hardware.xml:518 +#: hardware.xml:248 hardware.xml:410 hardware.xml:519 #, no-c-format msgid "CPU" msgstr "" @@ -521,7 +521,7 @@ msgstr "" #. Tag: para #: hardware.xml:331 #, no-c-format -msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base and OpenRD-Client), SheevaPlug and QNAP Turbo Station (TS-110, TS-119, TS-210, TS-219 and TS-219P; the TS-410 and TS-419P are not yet supported)." +msgid "Kirkwood is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. We currently support the following Kirkwood based devices: OpenRD (OpenRD-Base, OpenRD-Client and OpenRD-Ultimate), SheevaPlug and QNAP Turbo Station (TS-110, TS-112, TS-119, TS-119P+, TS-210, TS-212, TS-219, TS-219P, TS-219P+, TS-410, TS-410U, TS-419P, TS-419P+ and TS-419U)." msgstr "" #. Tag: term @@ -533,1295 +533,1295 @@ msgstr "" #. Tag: para #: hardware.xml:347 #, no-c-format -msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: Buffalo Kurobox, HP mv2120, QNAP Turbo Station (TS-109, TS-209 and TS-409)." +msgid "Orion is a system on a chip (SoC) from Marvell that integrates an ARM CPU, Ethernet, SATA, USB, and other functionality in one chip. There are many Network Attached Storage (NAS) devices on the market that are based on an Orion chip. We currently support the following Orion based devices: Buffalo Kurobox, D-Link DNS-323, HP mv2120, QNAP Turbo Station (TS-109, TS-209 and TS-409)." msgstr "" #. Tag: term -#: hardware.xml:362 +#: hardware.xml:363 #, no-c-format msgid "Versatile" msgstr "" #. Tag: para -#: hardware.xml:363 +#: hardware.xml:364 #, no-c-format msgid "The Versatile platform is emulated by QEMU and is therefore a nice way to test and run &debian; on ARM if you don't have the hardware." msgstr "" #. Tag: para -#: hardware.xml:382 +#: hardware.xml:383 #, no-c-format msgid "There are two major support &architecture; flavors: PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted at 32-bit processors whereas the 2.0 architecture is targeted to the 64-bit processors. Some systems are able to run either kernel. In both cases, the userland is 32-bit. There is the possibility of a 64-bit userland in the future." msgstr "" #. Tag: para -#: hardware.xml:410 +#: hardware.xml:411 #, no-c-format msgid "Nearly all x86-based (IA-32) processors still in use in personal computers are supported, including all varieties of Intel's \"Pentium\" series. This also includes 32-bit AMD and VIA (former Cyrix) processors, and processors like the Athlon XP and Intel P4 Xeon." msgstr "" #. Tag: para -#: hardware.xml:417 +#: hardware.xml:418 #, no-c-format msgid "However, &debian; GNU/Linux &releasename; will not run on 386 or earlier processors. Despite the architecture name \"i386\", support for actual 80386 processors (and their clones) was dropped with the Sarge (r3.1) release of &debian; We have long tried to avoid this, but in the end it was necessary due a unfortunate series of issues with the compiler and the kernel, starting with an bug in the C++ ABI provided by GCC. You should still be able to run &debian; GNU/Linux on actual 80386 processors if you compile your own kernel and compile all packages from source, but that is beyond the scope of this manual. . (No version of Linux has ever supported the 286 or earlier chips in the series.) All i486 and later processors are still supported Many &debian; packages will actually run slightly faster on modern computers as a positive side effect of dropping support for these old chips. The i486, introduced in 1989, has three opcodes (bswap, cmpxchg, and xadd) which the i386, introduced in 1986, did not have. Previously, these could not be easily used by most &debian; packages; now they can. ." msgstr "" #. Tag: para -#: hardware.xml:450 +#: hardware.xml:451 #, no-c-format msgid "If your system has a 64-bit processor from the AMD64 or Intel EM64T families, you will probably want to use the installer for the amd64 architecture instead of the installer for the (32-bit) i386 architecture." msgstr "" #. Tag: title -#: hardware.xml:459 +#: hardware.xml:460 #, no-c-format msgid "I/O Bus" msgstr "" #. Tag: para -#: hardware.xml:460 +#: hardware.xml:461 #, no-c-format msgid "The system bus is the part of the motherboard which allows the CPU to communicate with peripherals such as storage devices. Your computer must use the ISA, EISA, PCI, PCIe, PCI-X, or VESA Local Bus (VLB, sometimes called the VL bus). Essentially all personal computers sold in recent years use one of these." msgstr "" #. Tag: para -#: hardware.xml:484 +#: hardware.xml:485 #, no-c-format msgid "&debian; on &arch-title; supports the following platforms: SGI IP22: this platform includes the SGI machines Indy, Indigo 2 and Challenge S. Since these machines are very similar, whenever this document refers to the SGI Indy, the Indigo 2 and Challenge S are meant as well. SGI IP32: this platform is generally known as SGI O2. MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. Complete information regarding supported mips/mipsel machines can be found at the Linux-MIPS homepage. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the debian-&arch-listname; mailing list." msgstr "" #. Tag: para -#: hardware.xml:519 +#: hardware.xml:520 #, no-c-format msgid "On SGI IP22, SGI Indy, Indigo 2 and Challenge S with R4000, R4400, R4600 and R5000 processors are supported by the &debian; installation system on big endian MIPS. On SGI IP32, currently only systems based on the R5000 are supported." msgstr "" #. Tag: para -#: hardware.xml:525 +#: hardware.xml:526 #, no-c-format msgid "Some MIPS machines can be operated in both big and little endian mode. For little endian MIPS, please read the documentation for the mipsel architecture." msgstr "" #. Tag: para -#: hardware.xml:542 +#: hardware.xml:543 #, no-c-format msgid "&debian; on &arch-title; supports the following platforms: Cobalt Microserver: only MIPS based Cobalt machines are covered here. This includes the Cobalt RaQ, Qube2 and RaQ2, and the Gateway Microserver. MIPS Malta: this platform is emulated by QEMU and is therefore a nice way to test and run &debian; on MIPS if you don't have the hardware. Complete information regarding supported mips/mipsel machines can be found at the Linux-MIPS homepage. In the following, only the systems supported by the &debian; installer will be covered. If you are looking for support for other subarchitectures, please contact the debian-&arch-listname; mailing list." msgstr "" #. Tag: title -#: hardware.xml:570 +#: hardware.xml:571 #, no-c-format msgid "CPU/Machine types" msgstr "" #. Tag: para -#: hardware.xml:572 +#: hardware.xml:573 #, no-c-format msgid "All MIPS based Cobalt machines are supported with the exception of the Qube 2700 (Qube 1)." msgstr "" #. Tag: title -#: hardware.xml:580 +#: hardware.xml:581 #, no-c-format msgid "Supported console options" msgstr "" #. Tag: para -#: hardware.xml:581 +#: hardware.xml:582 #, no-c-format msgid "Cobalt machines use 115200 bps." msgstr "" #. Tag: para -#: hardware.xml:595 +#: hardware.xml:596 #, no-c-format msgid "For &debian-gnu; &release; only the PMac (Power-Macintosh or PowerMac) and PreP subarchitectures are supported." msgstr "" #. Tag: title -#: hardware.xml:616 +#: hardware.xml:617 #, no-c-format msgid "Kernel Flavours" msgstr "" #. Tag: para -#: hardware.xml:618 +#: hardware.xml:619 #, no-c-format msgid "There are two flavours of the powerpc kernel in &debian;, based on the CPU type:" msgstr "" #. Tag: term -#: hardware.xml:625 +#: hardware.xml:626 #, no-c-format msgid "powerpc" msgstr "" #. Tag: para -#: hardware.xml:626 +#: hardware.xml:627 #, no-c-format msgid "Most systems use this kernel flavour, which supports the PowerPC 601, 603, 604, 740, 750, and 7400 processors. All Apple PowerMac machines up to and including the one marketed as G4 use one of these processors." msgstr "" #. Tag: term -#: hardware.xml:636 +#: hardware.xml:637 #, no-c-format msgid "power64" msgstr "" #. Tag: para -#: hardware.xml:637 +#: hardware.xml:638 #, no-c-format msgid "The power64 kernel flavour supports the following CPUs:" msgstr "" #. Tag: para -#: hardware.xml:641 +#: hardware.xml:642 #, no-c-format msgid "The POWER3 processor is used in older IBM 64-bit server systems: known models include the IntelliStation POWER Model 265, the pSeries 610 and 640, and the RS/6000 7044-170, 7043-260, and 7044-270." msgstr "" #. Tag: para -#: hardware.xml:647 +#: hardware.xml:648 #, no-c-format msgid "The POWER4 processor is used in more recent IBM 64-bit server systems: known models include the pSeries 615, 630, 650, 655, 670, and 690." msgstr "" #. Tag: para -#: hardware.xml:652 +#: hardware.xml:653 #, no-c-format msgid "Systems using the Apple G5 (PPC970FX processor) are also based on the POWER4 architecture, and use this kernel flavour." msgstr "" #. Tag: title -#: hardware.xml:686 +#: hardware.xml:687 #, no-c-format msgid "Power Macintosh (pmac) subarchitecture" msgstr "" #. Tag: para -#: hardware.xml:688 +#: hardware.xml:689 #, no-c-format msgid "Apple (and briefly a few other manufacturers — Power Computing, for example) made a series of Macintosh computers based on the PowerPC processor. For purposes of architecture support, they are categorized as NuBus (not supported by &debian;), OldWorld, and NewWorld." msgstr "" #. Tag: para -#: hardware.xml:695 +#: hardware.xml:696 #, no-c-format msgid "OldWorld systems are most Power Macintoshes with a floppy drive and a PCI bus. Most 603, 603e, 604, and 604e based Power Macintoshes are OldWorld machines. Those pre-iMac PowerPC models from Apple use a four digit naming scheme, except for the beige colored G3 systems, which are also OldWorld." msgstr "" #. Tag: para -#: hardware.xml:703 +#: hardware.xml:704 #, no-c-format msgid "The so called NewWorld PowerMacs are any PowerMacs in translucent colored plastic cases and later models. That includes all iMacs, iBooks, G4 systems, blue colored G3 systems, and most PowerBooks manufactured in and after 1999. The NewWorld PowerMacs are also known for using the ROM in RAM system for MacOS, and were manufactured from mid-1998 onwards." msgstr "" #. Tag: para -#: hardware.xml:711 +#: hardware.xml:712 #, no-c-format msgid "Specifications for Apple hardware are available at AppleSpec, and, for older hardware, AppleSpec Legacy." msgstr "" #. Tag: entry -#: hardware.xml:727 hardware.xml:862 hardware.xml:906 hardware.xml:935 +#: hardware.xml:728 hardware.xml:863 hardware.xml:907 hardware.xml:936 #, no-c-format msgid "Model Name/Number" msgstr "" #. Tag: entry -#: hardware.xml:728 +#: hardware.xml:729 #, no-c-format msgid "Generation" msgstr "" #. Tag: entry -#: hardware.xml:734 +#: hardware.xml:735 #, no-c-format msgid "Apple" msgstr "" #. Tag: entry -#: hardware.xml:735 +#: hardware.xml:736 #, no-c-format msgid "iMac Bondi Blue, 5 Flavors, Slot Loading" msgstr "" #. Tag: entry -#: hardware.xml:736 hardware.xml:739 hardware.xml:742 hardware.xml:745 hardware.xml:748 hardware.xml:751 hardware.xml:754 hardware.xml:757 hardware.xml:760 hardware.xml:763 hardware.xml:766 hardware.xml:769 hardware.xml:772 hardware.xml:775 hardware.xml:778 hardware.xml:781 +#: hardware.xml:737 hardware.xml:740 hardware.xml:743 hardware.xml:746 hardware.xml:749 hardware.xml:752 hardware.xml:755 hardware.xml:758 hardware.xml:761 hardware.xml:764 hardware.xml:767 hardware.xml:770 hardware.xml:773 hardware.xml:776 hardware.xml:779 hardware.xml:782 #, no-c-format msgid "NewWorld" msgstr "" #. Tag: entry -#: hardware.xml:738 +#: hardware.xml:739 #, no-c-format msgid "iMac Summer 2000, Early 2001" msgstr "" #. Tag: entry -#: hardware.xml:741 +#: hardware.xml:742 #, no-c-format msgid "iMac G5" msgstr "" #. Tag: entry -#: hardware.xml:744 +#: hardware.xml:745 #, no-c-format msgid "iBook, iBook SE, iBook Dual USB" msgstr "" #. Tag: entry -#: hardware.xml:747 +#: hardware.xml:748 #, no-c-format msgid "iBook2" msgstr "" #. Tag: entry -#: hardware.xml:750 +#: hardware.xml:751 #, no-c-format msgid "iBook G4" msgstr "" #. Tag: entry -#: hardware.xml:753 +#: hardware.xml:754 #, no-c-format msgid "Power Macintosh Blue and White (B&W) G3" msgstr "" #. Tag: entry -#: hardware.xml:756 +#: hardware.xml:757 #, no-c-format msgid "Power Macintosh G4 PCI, AGP, Cube" msgstr "" #. Tag: entry -#: hardware.xml:759 +#: hardware.xml:760 #, no-c-format msgid "Power Macintosh G4 Gigabit Ethernet" msgstr "" #. Tag: entry -#: hardware.xml:762 +#: hardware.xml:763 #, no-c-format msgid "Power Macintosh G4 Digital Audio, Quicksilver" msgstr "" #. Tag: entry -#: hardware.xml:765 +#: hardware.xml:766 #, no-c-format msgid "Power Macintosh G5" msgstr "" #. Tag: entry -#: hardware.xml:768 +#: hardware.xml:769 #, no-c-format msgid "PowerBook G3 FireWire Pismo (2000)" msgstr "" #. Tag: entry -#: hardware.xml:771 +#: hardware.xml:772 #, no-c-format msgid "PowerBook G3 Lombard (1999)" msgstr "" #. Tag: entry -#: hardware.xml:774 +#: hardware.xml:775 #, no-c-format msgid "PowerBook G4 Titanium" msgstr "" #. Tag: entry -#: hardware.xml:777 +#: hardware.xml:778 #, no-c-format msgid "PowerBook G4 Aluminum" msgstr "" #. Tag: entry -#: hardware.xml:780 +#: hardware.xml:781 #, no-c-format msgid "Xserve G5" msgstr "" #. Tag: entry -#: hardware.xml:783 +#: hardware.xml:784 #, no-c-format msgid "Performa 4400, 54xx, 5500" msgstr "" #. Tag: entry -#: hardware.xml:784 hardware.xml:787 hardware.xml:790 hardware.xml:793 hardware.xml:796 hardware.xml:799 hardware.xml:802 hardware.xml:805 hardware.xml:808 hardware.xml:811 hardware.xml:814 hardware.xml:817 hardware.xml:823 hardware.xml:826 hardware.xml:832 hardware.xml:838 hardware.xml:844 +#: hardware.xml:785 hardware.xml:788 hardware.xml:791 hardware.xml:794 hardware.xml:797 hardware.xml:800 hardware.xml:803 hardware.xml:806 hardware.xml:809 hardware.xml:812 hardware.xml:815 hardware.xml:818 hardware.xml:824 hardware.xml:827 hardware.xml:833 hardware.xml:839 hardware.xml:845 #, no-c-format msgid "OldWorld" msgstr "" #. Tag: entry -#: hardware.xml:786 +#: hardware.xml:787 #, no-c-format msgid "Performa 6360, 6400, 6500" msgstr "" #. Tag: entry -#: hardware.xml:789 +#: hardware.xml:790 #, no-c-format msgid "Power Macintosh 4400, 5400" msgstr "" #. Tag: entry -#: hardware.xml:792 +#: hardware.xml:793 #, no-c-format msgid "Power Macintosh 7200, 7300, 7500, 7600" msgstr "" #. Tag: entry -#: hardware.xml:795 +#: hardware.xml:796 #, no-c-format msgid "Power Macintosh 8200, 8500, 8600" msgstr "" #. Tag: entry -#: hardware.xml:798 +#: hardware.xml:799 #, no-c-format msgid "Power Macintosh 9500, 9600" msgstr "" #. Tag: entry -#: hardware.xml:801 +#: hardware.xml:802 #, no-c-format msgid "Power Macintosh (Beige) G3 Minitower" msgstr "" #. Tag: entry -#: hardware.xml:804 +#: hardware.xml:805 #, no-c-format msgid "Power Macintosh (Beige) Desktop, All-in-One" msgstr "" #. Tag: entry -#: hardware.xml:807 +#: hardware.xml:808 #, no-c-format msgid "PowerBook 2400, 3400, 3500" msgstr "" #. Tag: entry -#: hardware.xml:810 +#: hardware.xml:811 #, no-c-format msgid "PowerBook G3 Wallstreet (1998)" msgstr "" #. Tag: entry -#: hardware.xml:813 +#: hardware.xml:814 #, no-c-format msgid "Twentieth Anniversary Macintosh" msgstr "" #. Tag: entry -#: hardware.xml:816 +#: hardware.xml:817 #, no-c-format msgid "Workgroup Server 7250, 7350, 8550, 9650, G3" msgstr "" #. Tag: entry -#: hardware.xml:821 +#: hardware.xml:822 #, no-c-format msgid "Power Computing" msgstr "" #. Tag: entry -#: hardware.xml:822 +#: hardware.xml:823 #, no-c-format msgid "PowerBase, PowerTower / Pro, PowerWave" msgstr "" #. Tag: entry -#: hardware.xml:825 +#: hardware.xml:826 #, no-c-format msgid "PowerCenter / Pro, PowerCurve" msgstr "" #. Tag: entry -#: hardware.xml:830 +#: hardware.xml:831 #, no-c-format msgid "UMAX" msgstr "" #. Tag: entry -#: hardware.xml:831 +#: hardware.xml:832 #, no-c-format msgid "C500, C600, J700, S900" msgstr "" #. Tag: entry -#: hardware.xml:836 +#: hardware.xml:837 #, no-c-format msgid "APS" msgstr "" #. Tag: entry -#: hardware.xml:837 +#: hardware.xml:838 #, no-c-format msgid "APS Tech M*Power 604e/2000" msgstr "" #. Tag: entry -#: hardware.xml:842 hardware.xml:868 +#: hardware.xml:843 hardware.xml:869 #, no-c-format msgid "Motorola" msgstr "" #. Tag: entry -#: hardware.xml:843 +#: hardware.xml:844 #, no-c-format msgid "Starmax 3000, 4000, 5000, 5500" msgstr "" #. Tag: title -#: hardware.xml:852 +#: hardware.xml:853 #, no-c-format msgid "PReP subarchitecture" msgstr "" #. Tag: entry -#: hardware.xml:869 +#: hardware.xml:870 #, no-c-format msgid "Firepower, PowerStack Series E, PowerStack II" msgstr "" #. Tag: entry -#: hardware.xml:871 +#: hardware.xml:872 #, no-c-format msgid "MPC 7xx, 8xx" msgstr "" #. Tag: entry -#: hardware.xml:873 +#: hardware.xml:874 #, no-c-format msgid "MTX, MTX+" msgstr "" #. Tag: entry -#: hardware.xml:875 +#: hardware.xml:876 #, no-c-format msgid "MVME2300(SC)/24xx/26xx/27xx/36xx/46xx" msgstr "" #. Tag: entry -#: hardware.xml:877 +#: hardware.xml:878 #, no-c-format msgid "MCP(N)750" msgstr "" #. Tag: entry -#: hardware.xml:881 hardware.xml:912 +#: hardware.xml:882 hardware.xml:913 #, no-c-format msgid "IBM RS/6000" msgstr "" #. Tag: entry -#: hardware.xml:882 +#: hardware.xml:883 #, no-c-format msgid "40P, 43P" msgstr "" #. Tag: entry -#: hardware.xml:884 +#: hardware.xml:885 #, no-c-format msgid "Power 830/850/860 (6070, 6050)" msgstr "" #. Tag: entry -#: hardware.xml:886 +#: hardware.xml:887 #, no-c-format msgid "6030, 7025, 7043" msgstr "" #. Tag: entry -#: hardware.xml:888 +#: hardware.xml:889 #, no-c-format msgid "p640" msgstr "" #. Tag: title -#: hardware.xml:896 +#: hardware.xml:897 #, no-c-format msgid "CHRP subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:913 +#: hardware.xml:914 #, no-c-format msgid "B50, 43P-150, 44P" msgstr "" #. Tag: entry -#: hardware.xml:916 +#: hardware.xml:917 #, no-c-format msgid "Genesi" msgstr "" #. Tag: entry -#: hardware.xml:917 +#: hardware.xml:918 #, no-c-format msgid "Pegasos I, Pegasos II" msgstr "" #. Tag: title -#: hardware.xml:925 +#: hardware.xml:926 #, no-c-format msgid "APUS subarchitecture (unsupported)" msgstr "" #. Tag: entry -#: hardware.xml:941 +#: hardware.xml:942 #, no-c-format msgid "Amiga Power-UP Systems (APUS)" msgstr "" #. Tag: entry -#: hardware.xml:942 +#: hardware.xml:943 #, no-c-format msgid "A1200, A3000, A4000" msgstr "" #. Tag: title -#: hardware.xml:950 +#: hardware.xml:951 #, no-c-format msgid "Nubus PowerMac subarchitecture (unsupported)" msgstr "" #. Tag: para -#: hardware.xml:952 +#: hardware.xml:953 #, no-c-format msgid "NuBus systems are not currently supported by &debian;/powerpc. The monolithic Linux/PPC kernel architecture does not have support for these machines; instead, one must use the MkLinux Mach microkernel, which &debian; does not yet support. These include the following: Power Macintosh 6100, 7100, 8100 Performa 5200, 6200, 6300 Powerbook 1400, 2300, and 5300 Workgroup Server 6150, 8150, 9150 A linux kernel for these machines and limited support is available at ." msgstr "" #. Tag: title -#: hardware.xml:989 +#: hardware.xml:990 #, no-c-format msgid "Non-PowerPC Macs" msgstr "" #. Tag: para -#: hardware.xml:991 +#: hardware.xml:992 #, no-c-format msgid "Macintosh computers using the 680x0 series of processors are not in the PowerPC family but are instead m68k machines. Those models start with Mac II series, go on to the LC family, then the Centris series, and culminate in the Quadras and Performas. These models usually have a Roman numeral or 3-digit model number such as Mac IIcx, LCIII or Quadra 950." msgstr "" #. Tag: para -#: hardware.xml:1000 +#: hardware.xml:1001 #, no-c-format msgid "This model range started with the Mac II (Mac II, IIx, IIcx, IIci, IIsi, IIvi, IIvx, IIfx), then the LC (LC, LCII, III, III+, 475, 520, 550, 575, 580, 630), then the Mac TV, then the Centris (610, 650, 660AV), the Quadra (605, 610, 630, 650, 660AV, 700, 800, 840AV, 900, 950), and finally the Performa 200-640CD." msgstr "" #. Tag: para -#: hardware.xml:1008 +#: hardware.xml:1009 #, no-c-format msgid "In laptops, it started with the Mac Portable, then the PowerBook 100-190cs and the PowerBook Duo 210-550c (excluding PowerBook 500 which is Nubus, please see the section above)." msgstr "" #. Tag: title -#: hardware.xml:1024 +#: hardware.xml:1025 #, no-c-format msgid "S/390 and zSeries machine types" msgstr "" #. Tag: para -#: hardware.xml:1025 +#: hardware.xml:1026 #, no-c-format msgid "Since &debian; Squeeze, support for booting in ESA/390 mode was dropped. Your machine needs to support for at least the z/Architecture, Architecture Level Set 2. The userland is still compiled for ESA/390, though. All zSeries hardware is fully supported. &arch-title; support software is included from the kernel 2.6.32 development stream. The most current information about IBM's Linux support can be found at the Linux on System z page on developerWorks." msgstr "" #. Tag: title -#: hardware.xml:1048 +#: hardware.xml:1049 #, no-c-format msgid "CPU and Main Boards Support" msgstr "" #. Tag: para -#: hardware.xml:1049 +#: hardware.xml:1050 #, no-c-format msgid "Sparc-based hardware is divided into a number of different subarchitectures, identified by one of the following names: sun4, sun4c, sun4d, sun4m, sun4u or sun4v. The following list describes what machines they include and what level of support may be expected for each of them." msgstr "" #. Tag: term -#: hardware.xml:1060 +#: hardware.xml:1061 #, no-c-format msgid "sun4, sun4c, sun4d, sun4m" msgstr "" #. Tag: para -#: hardware.xml:1062 +#: hardware.xml:1063 #, no-c-format msgid "None of these 32-bit sparc subarchitectures (sparc32) is supported. For a complete list of machines belonging to these subarchitectures, please consult the Wikipedia SPARCstation page." msgstr "" #. Tag: para -#: hardware.xml:1069 +#: hardware.xml:1070 #, no-c-format msgid "The last &debian; release to support sparc32 was Etch, but even then only for sun4m systems. Support for the other 32-bits subarchitectures had already been discontinued after earlier releases." msgstr "" #. Tag: term -#: hardware.xml:1079 +#: hardware.xml:1080 #, no-c-format msgid "sun4u" msgstr "" #. Tag: para -#: hardware.xml:1081 +#: hardware.xml:1082 #, no-c-format msgid "This subarchitecture includes all 64-bit machines (sparc64) based on the UltraSparc processor and its clones. Most of the machines are well supported, even though for some you may experience problems booting from CD due to firmware or bootloader bugs (this problem may be worked around by using netbooting). Use the sparc64 or sparc64-smp kernel in UP and SMP configurations respectively." msgstr "" #. Tag: term -#: hardware.xml:1094 +#: hardware.xml:1095 #, no-c-format msgid "sun4v" msgstr "" #. Tag: para -#: hardware.xml:1096 +#: hardware.xml:1097 #, no-c-format msgid "This is the newest addition to the Sparc family, which includes machines based on the Niagara multi-core CPUs. At the moment such CPUs are only available in T1000 and T2000 servers by Sun, and are well supported. Use the sparc64-smp kernel." msgstr "" #. Tag: para -#: hardware.xml:1107 +#: hardware.xml:1108 #, no-c-format msgid "Note that Fujitsu's SPARC64 CPUs used in PRIMEPOWER family of servers are not supported due to lack of support in the Linux kernel." msgstr "" #. Tag: title -#: hardware.xml:1116 +#: hardware.xml:1117 #, no-c-format msgid "Laptops" msgstr "" #. Tag: para -#: hardware.xml:1117 +#: hardware.xml:1118 #, no-c-format msgid "Laptops are also supported and nowadays most laptops work out of the box. In case a laptop contains specialized or proprietary hardware, some specific functions may not be supported. To see if your particular laptop works well with GNU/Linux, see for example the Linux Laptop pages." msgstr "" #. Tag: title -#: hardware.xml:1129 hardware.xml:1152 hardware.xml:1172 hardware.xml:1195 +#: hardware.xml:1130 hardware.xml:1153 hardware.xml:1173 hardware.xml:1196 #, no-c-format msgid "Multiple Processors" msgstr "" #. Tag: para -#: hardware.xml:1130 +#: hardware.xml:1131 #, no-c-format msgid "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. The standard &debian; &release; kernel image has been compiled with SMP support. The standard kernel is also usable on non-SMP systems, but has a slight overhead which will cause a small reduction in performance. For normal system use this will hardly be noticable." msgstr "" #. Tag: para -#: hardware.xml:1139 +#: hardware.xml:1140 #, no-c-format msgid "In order to optimize the kernel for single CPU systems, you'll have to replace the standard &debian; kernel. You can find a discussion of how to do this in . At this time (kernel version &kernelversion;) the way you disable SMP is to deselect &smp-config-option; in the &smp-config-section; section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1154 +#: hardware.xml:1155 #, no-c-format msgid "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. The standard &debian; &release; kernel image has been compiled with SMP-alternatives support. This means that the kernel will detect the number of processors (or processor cores) and will automatically deactivate SMP on uniprocessor systems." msgstr "" #. Tag: para -#: hardware.xml:1163 +#: hardware.xml:1164 #, no-c-format msgid "The 486 flavour of the &debian; kernel image packages for &arch-title; is not compiled with SMP support." msgstr "" #. Tag: para -#: hardware.xml:1173 +#: hardware.xml:1174 #, no-c-format msgid "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture. However, the standard &debian; &release; kernel image does not support SMP. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1182 +#: hardware.xml:1183 #, no-c-format msgid "In order to take advantage of multiple processors, you'll have to replace the standard &debian; kernel. You can find a discussion of how to do this in . At this time (kernel version &kernelversion;) the way you enable SMP is to select &smp-config-option; in the &smp-config-section; section of the kernel config." msgstr "" #. Tag: para -#: hardware.xml:1196 +#: hardware.xml:1197 #, no-c-format msgid "Multiprocessor support — also called symmetric multiprocessing or SMP — is available for this architecture, and is supported by a precompiled &debian; kernel image. Depending on your install media, this SMP-capable kernel may or may not be installed by default. This should not prevent installation, since the standard, non-SMP kernel should boot on SMP systems; the kernel will simply use the first CPU." msgstr "" #. Tag: para -#: hardware.xml:1206 +#: hardware.xml:1207 #, no-c-format msgid "In order to take advantage of multiple processors, you should check to see if a kernel package that supports SMP is installed, and if not, choose an appropriate kernel package." msgstr "" #. Tag: para -#: hardware.xml:1212 +#: hardware.xml:1213 #, no-c-format msgid "You can also build your own customized kernel to support SMP. You can find a discussion of how to do this in . At this time (kernel version &kernelversion;) the way you enable SMP is to select &smp-config-option; in the &smp-config-section; section of the kernel config." msgstr "" #. Tag: title -#: hardware.xml:1223 +#: hardware.xml:1224 #, no-c-format msgid "Graphics Card Support" msgstr "" #. Tag: para -#: hardware.xml:1224 +#: hardware.xml:1225 #, no-c-format msgid "You should be using a VGA-compatible display interface for the console terminal. Nearly every modern display card is compatible with VGA. Ancient standards such CGA, MDA, or HGA should also work, assuming you do not require X11 support. Note that X11 is not used during the installation process described in this document unless the graphical installer was explicitly selected." msgstr "" #. Tag: para -#: hardware.xml:1233 +#: hardware.xml:1234 #, no-c-format msgid "&debian;'s support for graphical interfaces is determined by the underlying support found in X.Org's X11 system. Most AGP, PCI, PCIe, and PCI-X video cards work under X.Org. Details on supported graphics buses, cards, monitors, and pointing devices can be found at . &debian; &release; ships with X.Org version &x11ver;." msgstr "" #. Tag: para -#: hardware.xml:1242 +#: hardware.xml:1243 #, no-c-format msgid "The X.Org X Window System is only supported on the SGI Indy and the O2." msgstr "" #. Tag: para -#: hardware.xml:1247 +#: hardware.xml:1248 #, no-c-format msgid "Most graphics options commonly found on Sparc-based machines are supported. X.org graphics drivers are available for sunbw2, suncg14, suncg3, suncg6, sunleo and suntcx framebuffers, Creator3D and Elite3D cards (sunffb driver), PGX24/PGX64 ATI-based video cards (ati driver), and PermediaII-based cards (glint driver). To use an Elite3D card with X.org you additionally need to install the afbinit package, and read the documentation included with it on how to activate the card." msgstr "" #. Tag: para -#: hardware.xml:1257 +#: hardware.xml:1258 #, no-c-format msgid "It is not uncommon for a Sparc machine to have two graphics cards in a default configuration. In such a case there is a possibility that the Linux kernel will not direct its output to the card initially used by the firmware. The lack of output on the graphical console may then be mistaken for a hang (usually the last message seen on console is 'Booting Linux...'). One possible solution is to physically remove one of the video cards; another option is to disable one of the cards using a kernel boot parameter. Also, if graphical output is not required or desired, serial console may be used as an alternative. On some systems use of serial console can be activated automatically by disconnecting the keyboard before booting the system." msgstr "" #. Tag: title -#: hardware.xml:1279 +#: hardware.xml:1280 #, no-c-format msgid "Network Connectivity Hardware" msgstr "" #. Tag: para -#: hardware.xml:1280 +#: hardware.xml:1281 #, no-c-format msgid "Almost any network interface card (NIC) supported by the &arch-kernel; kernel should also be supported by the installation system; modular drivers should normally be loaded automatically. This includes most PCI and PCMCIA cards. Many older ISA cards are supported as well." msgstr "" #. Tag: para -#: hardware.xml:1289 +#: hardware.xml:1290 #, no-c-format msgid "This includes a lot of generic PCI cards (for systems that have PCI) and the following NICs from Sun:" msgstr "" #. Tag: para -#: hardware.xml:1295 +#: hardware.xml:1296 #, no-c-format msgid "Sun LANCE" msgstr "" #. Tag: para -#: hardware.xml:1300 +#: hardware.xml:1301 #, no-c-format msgid "Sun Happy Meal" msgstr "" #. Tag: para -#: hardware.xml:1305 +#: hardware.xml:1306 #, no-c-format msgid "Sun BigMAC" msgstr "" #. Tag: para -#: hardware.xml:1310 +#: hardware.xml:1311 #, no-c-format msgid "Sun QuadEthernet" msgstr "" #. Tag: para -#: hardware.xml:1315 +#: hardware.xml:1316 #, no-c-format msgid "MyriCOM Gigabit Ethernet" msgstr "" #. Tag: para -#: hardware.xml:1322 +#: hardware.xml:1323 #, no-c-format msgid "The list of supported network devices is:" msgstr "" #. Tag: para -#: hardware.xml:1327 +#: hardware.xml:1328 #, no-c-format msgid "Channel to Channel (CTC) and ESCON connection (real or emulated)" msgstr "" #. Tag: para -#: hardware.xml:1332 +#: hardware.xml:1333 #, no-c-format msgid "OSA-2 Token Ring/Ethernet and OSA-Express Fast Ethernet (non-QDIO)" msgstr "" #. Tag: para -#: hardware.xml:1337 +#: hardware.xml:1338 #, no-c-format msgid "OSA-Express in QDIO mode, HiperSockets and Guest-LANs" msgstr "" #. Tag: para -#: hardware.xml:1346 +#: hardware.xml:1347 #, no-c-format msgid "On &arch-title;, most built-in Ethernet devices are supported and modules for additional PCI and USB devices are provided. The major exception is the IXP4xx platform (featuring devices such as the Linksys NSLU2) which needs a proprietary microcode for the operation of its built-in Ethernet device. Unofficial images for Linksys NSLU2 with this proprietary microcode can be obtained from the Slug-Firmware site." msgstr "" #. Tag: para -#: hardware.xml:1356 +#: hardware.xml:1357 #, no-c-format msgid "ISDN is supported, but not during the installation." msgstr "" #. Tag: title -#: hardware.xml:1363 +#: hardware.xml:1364 #, no-c-format msgid "Wireless Network Cards" msgstr "" #. Tag: para -#: hardware.xml:1364 +#: hardware.xml:1365 #, no-c-format msgid "Wireless networking is in general supported as well and a growing number of wireless adapters are supported by the official &arch-kernel; kernel, although many of them do require firmware to be loaded. If firmware is needed, the installer will prompt you to load firmware. See for detailed information on how to load firmware during the installation." msgstr "" #. Tag: para -#: hardware.xml:1372 +#: hardware.xml:1373 #, no-c-format msgid "Wireless NICs that are not supported by the official &arch-kernel; kernel can generally be made to work under &debian-gnu;, but are not supported during the installation." msgstr "" #. Tag: para -#: hardware.xml:1377 +#: hardware.xml:1378 #, no-c-format msgid "Support for encrypted wireless during installation is currently limited to WEP. If your access point uses stronger encryption, it cannot be used during the installation process." msgstr "" #. Tag: para -#: hardware.xml:1383 +#: hardware.xml:1384 #, no-c-format msgid "If there is a problem with wireless and there is no other NIC you can use during the installation, it is still possible to install &debian-gnu; using a full CD-ROM or DVD image. Select the option to not configure a network and install using only the packages available from the CD/DVD. You can then install the driver and firmware you need after the installation is completed (after the reboot) and configure your network manually." msgstr "" #. Tag: para -#: hardware.xml:1393 +#: hardware.xml:1394 #, no-c-format msgid "In some cases the driver you need may not be available as a &debian; package. You will then have to look if there is source code available in the internet and compile the driver yourself. How to do this is outside the scope of this manual. If no Linux driver is available, your last resort is to use the ndiswrapper package, which allows you to use a Windows driver." msgstr "" #. Tag: title -#: hardware.xml:1407 +#: hardware.xml:1408 #, no-c-format msgid "Known Issues for &arch-title;" msgstr "" #. Tag: para -#: hardware.xml:1408 +#: hardware.xml:1409 #, no-c-format msgid "There are a couple of issues with specific network cards that are worth mentioning here." msgstr "" #. Tag: title -#: hardware.xml:1415 +#: hardware.xml:1416 #, no-c-format msgid "Conflict between tulip and dfme drivers" msgstr "" #. Tag: para -#: hardware.xml:1417 +#: hardware.xml:1418 #, no-c-format msgid "There are various PCI network cards that have the same PCI identification, but are supported by related, but different drivers. Some cards work with the tulip driver, others with the dfme driver. Because they have the same identification, the kernel cannot distinguish between them and it is not certain which driver will be loaded. If this happens to be the wrong one, the NIC may not work, or work badly." msgstr "" #. Tag: para -#: hardware.xml:1427 +#: hardware.xml:1428 #, no-c-format msgid "This is a common problem on Netra systems with a Davicom (DEC-Tulip compatible) NIC. In that case the tulip driver is probably the correct one. You can prevent this issue by blacklisting the wrong driver module as described in ." msgstr "" #. Tag: para -#: hardware.xml:1435 +#: hardware.xml:1436 #, no-c-format msgid "An alternative solution during the installation is to switch to a shell and unload the wrong driver module using modprobe -r module (or both, if they are both loaded). After that you can load the correct module using modprobe module. Note that the wrong module may then still be loaded when the system is rebooted." msgstr "" #. Tag: title -#: hardware.xml:1448 +#: hardware.xml:1449 #, no-c-format msgid "Sun B100 blade" msgstr "" #. Tag: para -#: hardware.xml:1450 +#: hardware.xml:1451 #, no-c-format msgid "The cassini network driver does not work with Sun B100 blade systems." msgstr "" #. Tag: title -#: hardware.xml:1465 +#: hardware.xml:1466 #, no-c-format msgid "Braille Displays" msgstr "" #. Tag: para -#: hardware.xml:1466 +#: hardware.xml:1467 #, no-c-format msgid "Support for braille displays is determined by the underlying support found in brltty. Most displays work under brltty, connected via either a serial port, USB or bluetooth. Details on supported braille devices can be found on the brltty website. &debian-gnu; &release; ships with brltty version &brlttyver;." msgstr "" #. Tag: title -#: hardware.xml:1480 +#: hardware.xml:1481 #, no-c-format msgid "Hardware Speech Synthesis" msgstr "" #. Tag: para -#: hardware.xml:1481 +#: hardware.xml:1482 #, no-c-format msgid "Support for hardware speech synthesis devices is determined by the underlying support found in speakup. speakup only supports integrated boards and external devices connected to a serial port (no USB or serial-to-USB adapters are supported). Details on supported hardware speech synthesis devices can be found on the speakup website. &debian-gnu; &release; ships with speakup version &speakupver;." msgstr "" #. Tag: title -#: hardware.xml:1501 +#: hardware.xml:1502 #, no-c-format msgid "Peripherals and Other Hardware" msgstr "" #. Tag: para -#: hardware.xml:1502 +#: hardware.xml:1503 #, no-c-format msgid "&arch-kernel; supports a large variety of hardware devices such as mice, printers, scanners, PCMCIA and USB devices. However, most of these devices are not required while installing the system." msgstr "" #. Tag: para -#: hardware.xml:1508 +#: hardware.xml:1509 #, no-c-format msgid "USB hardware generally works fine, only some USB keyboards may require additional configuration (see )." msgstr "" #. Tag: para -#: hardware.xml:1514 +#: hardware.xml:1515 #, no-c-format msgid "Again, see the Linux Hardware Compatibility HOWTO to determine whether your specific hardware is supported by Linux." msgstr "" #. Tag: para -#: hardware.xml:1520 +#: hardware.xml:1521 #, no-c-format msgid "Package installations from XPRAM and tape are not supported by this system. All packages that you want to install need to be available on a DASD or over the network using NFS, HTTP or FTP." msgstr "" #. Tag: para -#: hardware.xml:1526 +#: hardware.xml:1527 #, no-c-format msgid "The Cobalt RaQ has no support for additional devices but the Qube has one PCI slot." msgstr "" #. Tag: title -#: hardware.xml:1538 +#: hardware.xml:1539 #, no-c-format msgid "Devices Requiring Firmware" msgstr "" #. Tag: para -#: hardware.xml:1539 +#: hardware.xml:1540 #, no-c-format msgid "Besides the availability of a device driver, some hardware also requires so-called firmware or microcode to be loaded into the device before it can become operational. This is most common for network interface cards (especially wireless NICs), but for example some USB devices and even some hard disk controllers also require firmware." msgstr "" #. Tag: para -#: hardware.xml:1547 +#: hardware.xml:1548 #, no-c-format msgid "In most cases firmware is non-free according to the criteria used by the &debian-gnu; project and thus cannot be included in the main distribution or in the installation system. If the device driver itself is included in the distribution and if &debian-gnu; legally can distribute the firmware, it will often be available as a separate package from the non-free section of the archive." msgstr "" #. Tag: para -#: hardware.xml:1556 +#: hardware.xml:1557 #, no-c-format msgid "However, this does not mean that such hardware cannot be used during an installation. Starting with &debian-gnu; 5.0, &d-i; supports loading firmware files or packages containing firmware from a removable medium, such as a floppy disk or USB stick. See for detailed information on how to load firmware files or packages during the installation." msgstr "" #. Tag: title -#: hardware.xml:1572 +#: hardware.xml:1573 #, no-c-format msgid "Purchasing Hardware Specifically for GNU/&arch-kernel;" msgstr "" #. Tag: para -#: hardware.xml:1574 +#: hardware.xml:1575 #, no-c-format msgid "There are several vendors, who ship systems with &debian; or other distributions of GNU/Linux pre-installed. You might pay more for the privilege, but it does buy a level of peace of mind, since you can be sure that the hardware is well-supported by GNU/Linux." msgstr "" #. Tag: para -#: hardware.xml:1582 +#: hardware.xml:1583 #, no-c-format msgid "If you do have to buy a machine with Windows bundled, carefully read the software license that comes with Windows; you may be able to reject the license and obtain a rebate from your vendor. Searching the Internet for windows refund may get you some useful information to help with that." msgstr "" #. Tag: para -#: hardware.xml:1590 +#: hardware.xml:1591 #, no-c-format msgid "Whether or not you are purchasing a system with &arch-kernel; bundled, or even a used system, it is still important to check that your hardware is supported by the &arch-kernel; kernel. Check if your hardware is listed in the references found above. Let your salesperson (if any) know that you're shopping for a &arch-kernel; system. Support &arch-kernel;-friendly hardware vendors." msgstr "" #. Tag: title -#: hardware.xml:1601 +#: hardware.xml:1602 #, no-c-format msgid "Avoid Proprietary or Closed Hardware" msgstr "" #. Tag: para -#: hardware.xml:1602 +#: hardware.xml:1603 #, no-c-format msgid "Some hardware manufacturers simply won't tell us how to write drivers for their hardware. Others won't allow us access to the documentation without a non-disclosure agreement that would prevent us from releasing the &arch-kernel; source code." msgstr "" #. Tag: para -#: hardware.xml:1609 +#: hardware.xml:1610 #, no-c-format msgid "Since we haven't been granted access to the documentation on these devices, they simply won't work under &arch-kernel;. You can help by asking the manufacturers of such hardware to release the documentation. If enough people ask, they will realize that the free software community is an important market." msgstr "" #. Tag: title -#: hardware.xml:1621 +#: hardware.xml:1622 #, no-c-format msgid "Windows-specific Hardware" msgstr "" #. Tag: para -#: hardware.xml:1622 +#: hardware.xml:1623 #, no-c-format msgid "A disturbing trend is the proliferation of Windows-specific modems and printers. In some cases these are specially designed to be operated by the Microsoft Windows operating system and bear the legend WinModem or Made especially for Windows-based computers. This is generally done by removing the embedded processors of the hardware and shifting the work they do over to a Windows driver that is run by your computer's main CPU. This strategy makes the hardware less expensive, but the savings are often not passed on to the user and this hardware may even be more expensive than equivalent devices that retain their embedded intelligence." msgstr "" #. Tag: para -#: hardware.xml:1635 +#: hardware.xml:1636 #, no-c-format msgid "You should avoid Windows-specific hardware for two reasons. The first is that the manufacturers do not generally make the resources available to write a &arch-kernel; driver. Generally, the hardware and software interface to the device is proprietary, and documentation is not available without a non-disclosure agreement, if it is available at all. This precludes it being used for free software, since free software writers disclose the source code of their programs. The second reason is that when devices like these have had their embedded processors removed, the operating system must perform the work of the embedded processors, often at real-time priority, and thus the CPU is not available to run your programs while it is driving these devices. Since the typical Windows user does not multi-process as intensively as a &arch-kernel; user, the manufacturers hope that the Windows user simply won't notice the burden this hardware places on their CPU. However, any multi-processing operating system, even Windows 2000 or XP, suffers from degraded performance when peripheral manufacturers skimp on the embedded processing power of their hardware." msgstr "" #. Tag: para -#: hardware.xml:1656 +#: hardware.xml:1657 #, no-c-format msgid "You can help improve this situation by encouraging these manufacturers to release the documentation and other resources necessary for us to program their hardware, but the best strategy is simply to avoid this sort of hardware until it is listed as working in the Linux Hardware Compatibility HOWTO." msgstr "" #. Tag: title -#: hardware.xml:1674 +#: hardware.xml:1675 #, no-c-format msgid "Installation Media" msgstr "" #. Tag: para -#: hardware.xml:1676 +#: hardware.xml:1677 #, no-c-format msgid "This section will help you determine which different media types you can use to install &debian;. For example, if you have a floppy disk drive on your machine, it can be used to install &debian;. There is a whole chapter devoted to media, , which lists the advantages and disadvantages of each media type. You may want to refer back to this page once you reach that section." msgstr "" #. Tag: title -#: hardware.xml:1687 +#: hardware.xml:1688 #, no-c-format msgid "Floppies" msgstr "" #. Tag: para -#: hardware.xml:1688 +#: hardware.xml:1689 #, no-c-format msgid "In some cases, you'll have to do your first boot from floppy disks. Generally, all you will need is a high-density (1440 kilobytes) 3.5 inch floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1694 +#: hardware.xml:1695 #, no-c-format msgid "For CHRP, floppy support is currently broken." msgstr "" #. Tag: title -#: hardware.xml:1701 +#: hardware.xml:1702 #, no-c-format msgid "CD-ROM/DVD-ROM" msgstr "" #. Tag: para -#: hardware.xml:1703 +#: hardware.xml:1704 #, no-c-format msgid "Whenever you see CD-ROM in this manual, it applies to both CD-ROMs and DVD-ROMs, because both technologies are really the same from the operating system's point of view, except for some very old nonstandard CD-ROM drives which are neither SCSI nor IDE/ATAPI." msgstr "" #. Tag: para -#: hardware.xml:1710 +#: hardware.xml:1711 #, no-c-format msgid "CD-ROM based installation is supported for some architectures. On machines which support bootable CD-ROMs, you should be able to do a completely floppy-less tape-less installation. Even if your system doesn't support booting from a CD-ROM, you can use the CD-ROM in conjunction with the other techniques to install your system, once you've booted up by other means; see ." msgstr "" #. Tag: para -#: hardware.xml:1722 +#: hardware.xml:1723 #, no-c-format msgid "SCSI, SATA and IDE/ATAPI CD-ROMs are supported. The Linux CD-ROM HOWTO contains in-depth information on using CD-ROMs with Linux." msgstr "" #. Tag: para -#: hardware.xml:1728 +#: hardware.xml:1729 #, no-c-format msgid "USB CD-ROM drives are also supported, as are FireWire devices that are supported by the ohci1394 and sbp2 drivers." msgstr "" #. Tag: para -#: hardware.xml:1733 +#: hardware.xml:1734 #, no-c-format msgid "IDE/ATAPI CD-ROMs are supported on all ARM machines." msgstr "" #. Tag: para -#: hardware.xml:1737 +#: hardware.xml:1738 #, no-c-format msgid "On SGI machines, booting from CD-ROM requires a SCSI CD-ROM drive capable of working with a logical blocksize of 512 bytes. Many of the SCSI CD-ROM drives sold on the PC market do not have this capability. If your CD-ROM drive has a jumper labeled Unix/PC or 512/2048, place it in the Unix or 512 position. To start the install, simply choose the System installation entry in the firmware." msgstr "" #. Tag: title -#: hardware.xml:1751 +#: hardware.xml:1752 #, no-c-format msgid "Hard Disk" msgstr "" #. Tag: para -#: hardware.xml:1753 +#: hardware.xml:1754 #, no-c-format msgid "Booting the installation system directly from a hard disk is another option for many architectures. This will require some other operating system to load the installer onto the hard disk." msgstr "" #. Tag: para -#: hardware.xml:1759 +#: hardware.xml:1760 #, no-c-format msgid "Although the &arch-title; does not allow booting from SunOS (Solaris), you can install from a SunOS partition (UFS slices)." msgstr "" #. Tag: title -#: hardware.xml:1767 +#: hardware.xml:1768 #, no-c-format msgid "USB Memory Stick" msgstr "" #. Tag: para -#: hardware.xml:1769 +#: hardware.xml:1770 #, no-c-format msgid "Many &debian; boxes need their floppy and/or CD-ROM drives only for setting up the system and for rescue purposes. If you operate some servers, you will probably already have thought about omitting those drives and using an USB memory stick for installing and (when necessary) for recovering the system. This is also useful for small systems which have no room for unnecessary drives." msgstr "" #. Tag: title -#: hardware.xml:1781 +#: hardware.xml:1782 #, no-c-format msgid "Network" msgstr "" #. Tag: para -#: hardware.xml:1783 +#: hardware.xml:1784 #, no-c-format msgid "The network can be used during the installation to retrieve files needed for the installation. Whether the network is used or not depends on the installation method you choose and your answers to certain questions that will be asked during the installation. The installation system supports most types of network connections (including PPPoE, but not ISDN or PPP), via either HTTP or FTP. After the installation is completed, you can also configure your system to use ISDN and PPP." msgstr "" #. Tag: para -#: hardware.xml:1793 +#: hardware.xml:1794 #, no-c-format msgid "You can also boot the installation system over the network. This is the preferred installation technique for &arch-title;." msgstr "" #. Tag: para -#: hardware.xml:1799 +#: hardware.xml:1800 #, no-c-format msgid "Diskless installation, using network booting from a local area network and NFS-mounting of all local filesystems, is another option." msgstr "" #. Tag: title -#: hardware.xml:1807 +#: hardware.xml:1808 #, no-c-format msgid "Un*x or GNU system" msgstr "" #. Tag: para -#: hardware.xml:1809 +#: hardware.xml:1810 #, no-c-format msgid "If you are running another Unix-like system, you could use it to install &debian-gnu; without using the &d-i; described in the rest of this manual. This kind of install may be useful for users with otherwise unsupported hardware or on hosts which can't afford downtime. If you are interested in this technique, skip to the ." msgstr "" #. Tag: title -#: hardware.xml:1821 +#: hardware.xml:1822 #, no-c-format msgid "Supported Storage Systems" msgstr "" #. Tag: para -#: hardware.xml:1823 +#: hardware.xml:1824 #, no-c-format msgid "The &debian; boot disks contain a kernel which is built to maximize the number of systems it runs on. Unfortunately, this makes for a larger kernel, which includes many drivers that won't be used for your machine (see to learn how to build your own kernel). Support for the widest possible range of devices is desirable in general, to ensure that &debian; can be installed on the widest array of hardware." msgstr "" #. Tag: para -#: hardware.xml:1833 +#: hardware.xml:1834 #, no-c-format msgid "Generally, the &debian; installation system includes support for floppies, IDE (also known as PATA) drives, IDE floppies, parallel port IDE devices, SATA and SCSI controllers and drives, USB, and FireWire. The supported file systems include FAT, Win-32 FAT extensions (VFAT) and NTFS." msgstr "" #. Tag: para -#: hardware.xml:1840 +#: hardware.xml:1841 #, no-c-format msgid "Disk interfaces that emulate the AT hard disk interface — often called MFM, RLL, IDE, or PATA — are supported. SATA and SCSI disk controllers from many different manufacturers are supported. See the Linux Hardware Compatibility HOWTO for more details." msgstr "" #. Tag: para -#: hardware.xml:1848 +#: hardware.xml:1849 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. The following SCSI drivers are supported in the default kernel: Sparc ESP PTI Qlogic,ISP Adaptec AIC7xxx NCR and Symbios 53C8XX IDE systems (such as the UltraSPARC 5) are also supported. See Linux for SPARC Processors FAQ for more information on SPARC hardware supported by the Linux kernel." msgstr "" #. Tag: para -#: hardware.xml:1881 +#: hardware.xml:1882 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support floppies on CHRP systems at all." msgstr "" #. Tag: para -#: hardware.xml:1887 +#: hardware.xml:1888 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. Note that the current Linux kernel does not support the floppy drive." msgstr "" #. Tag: para -#: hardware.xml:1893 +#: hardware.xml:1894 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system." msgstr "" #. Tag: para -#: hardware.xml:1898 +#: hardware.xml:1899 #, no-c-format msgid "Any storage system supported by the Linux kernel is also supported by the boot system. This means that FBA and ECKD DASDs are supported with the old Linux disk layout (ldl) and the new common S/390 disk layout (cdl)." msgstr "" #. Tag: title -#: hardware.xml:1915 +#: hardware.xml:1916 #, no-c-format msgid "Memory and Disk Space Requirements" msgstr "" #. Tag: para -#: hardware.xml:1917 +#: hardware.xml:1918 #, no-c-format msgid "You must have at least &minimum-memory; of memory and &minimum-fs-size; of hard disk space to perform a normal installation. Note that these are fairly minimal numbers. For more realistic figures, see ." msgstr "" #. Tag: para -#: hardware.xml:1924 +#: hardware.xml:1925 #, no-c-format msgid "Installation on systems with less memory Installation images that support the graphical installer require more memory than images that support only the textual installer and should not be used on systems with less than &minimum-memory; of memory. If there is a choice between booting the regular and the graphical installer, the former should be selected. or disk space available may be possible but is only advised for experienced users." msgstr "" diff --git a/po/pot/install-methods.pot b/po/pot/install-methods.pot index 80c6dc7e6..622b38e8b 100644 --- a/po/pot/install-methods.pot +++ b/po/pot/install-methods.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -380,39 +380,41 @@ msgstr "" #. Tag: para #: install-methods.xml:532 #, no-c-format -msgid "There are two installation methods possible when booting from USB stick. The first is to only use the USB stick to boot the installer, and then install completely from the network. The second is to also copy a CD image onto the USB stick and use that as a source for packages, possibly in combination with a mirror." +msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named /dev/sdX, where the X is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command dmesg after inserting it. To write to your stick, you may have to turn off its write protection switch." msgstr "" #. Tag: para -#: install-methods.xml:540 +#: install-methods.xml:545 #, no-c-format -msgid "To prepare the USB stick, you will need a system where GNU/Linux is already running and where USB is supported. With current GNU/Linux systems the USB stick should be automatically recognized when you insert it. If it is not you should check that the usb-storage kernel module is loaded. When the USB stick is inserted, it will be mapped to a device named /dev/sdX, where the X is a letter in the range a-z. You should be able to see to which device the USB stick was mapped by running the command dmesg after inserting it. To write to your stick, you may have to turn off its write protection switch." +msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." +msgstr "" + +#. Tag: title +#: install-methods.xml:555 +#, no-c-format +msgid "Preparing a USB stick using a hybrid CD or DVD image" msgstr "" #. Tag: para -#: install-methods.xml:553 +#: install-methods.xml:556 #, no-c-format -msgid "The procedures described in this section will destroy anything already on the device! Make very sure that you use the correct device name for your USB stick. If you use the wrong device the result could be that all information on for example a hard disk could be lost." +msgid "Debian CD and DVD images can now be written directly a USB stick, which is a very easy way to make a bootable USB stick. Simply choose a CD or DVD image that will fit on your USB stick. See to get a CD or DVD image." msgstr "" #. Tag: para -#: install-methods.xml:560 +#: install-methods.xml:563 #, no-c-format -msgid "To prepare a USB stick that only boots the installer, which then proceeds to install entirely from the network, you'll need to download the mini.iso image from the netboot directory (at the location mentioned in ), and write this file directly to the USB stick, overwriting its current contents. This method will work with very small USB sticks, only a few megabytes in size." +msgid "Alternatively, for very small USB sticks, only a few megabytes in size, you can download the mini.iso image from the netboot directory (at the location mentioned in )." msgstr "" #. Tag: para -#: install-methods.xml:570 +#: install-methods.xml:571 #, no-c-format -msgid "" - "For example, when using an existing GNU/Linux system, the mini.iso file can be written to a USB stick as follows: \n" - "# cat mini.iso > /dev/sdX\n" - "# sync\n" - " To add firmware to a USB stick prepared in this way, obtain the necessary firmware files. See for more information. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it." +msgid "A special method can be used to add firmware to the mini.iso. First, write the mini.iso to the USB stick. Next obtain the necessary firmware files. See for more information about firmware. Now unplug and replug the USB stick, and two partitions should now be visible on it. You should mount the second of the two partitions, and unpack the firmware onto it." msgstr "" #. Tag: screen -#: install-methods.xml:582 +#: install-methods.xml:581 #, no-c-format msgid "" "# mount /dev/sdX2 /mnt\n" @@ -423,91 +425,99 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:584 +#: install-methods.xml:587 #, no-c-format -msgid "To prepare a USB stick that installs packages from a CD image included on the stick, use the installer images found in the hd-media directory. Either the easy way or the flexible way can be used to copy the image to the USB stick. For this installation method you will also need to download a CD image. The installation image and the CD image must be based on the same release of &d-i;. If they do not match you are likely to get errors The error message that is most likely to be displayed is that no kernel modules can be found. This means that the version of the kernel module udebs included on the CD image is different from the version of the running kernel. during the installation." +msgid "The CD or DVD image you choose should be written directly to the USB stick, overwriting its current contents. For example, when using an existing GNU/Linux system, the CD or DVD image file can be written to a USB stick as follows:" msgstr "" -#. Tag: para -#: install-methods.xml:604 +#. Tag: screen +#: install-methods.xml:594 #, no-c-format -msgid "Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow )." +msgid "" + "# cat debian.iso > /dev/sdX\n" + "# sync" msgstr "" #. Tag: title -#: install-methods.xml:612 +#: install-methods.xml:601 +#, no-c-format +msgid "Manually copying files to the USB stick" +msgstr "" + +#. Tag: para +#: install-methods.xml:602 #, no-c-format -msgid "Copying the files — the easy way" +msgid "An alternative way to set up your USB stick is to manually copy the installer files, and also a CD image to it. Note that the USB stick should be at least 256 MB in size (smaller setups are possible if you follow )." msgstr "" #. Tag: para -#: install-methods.xml:613 +#: install-methods.xml:609 #, no-c-format msgid "There is an all-in-one file hd-media/boot.img.gz which contains all the installer files (including the kernel) as well as syslinux and its configuration file as well as yaboot and its configuration file." msgstr "" #. Tag: para -#: install-methods.xml:622 +#: install-methods.xml:618 #, no-c-format msgid "Note that, although convenient, this method does have one major disadvantage: the logical size of the device will be limited to 256 MB, even if the capacity of the USB stick is larger. You will need to repartition the USB stick and create new file systems to get its full capacity back if you ever want to use it for some different purpose. A second disadvantage is that you cannot copy a full CD image onto the USB stick, but only the smaller businesscard or netinst CD images." msgstr "" #. Tag: para -#: install-methods.xml:632 +#: install-methods.xml:628 #, no-c-format msgid "To use this image simply extract it directly to your USB stick:" msgstr "" #. Tag: screen -#: install-methods.xml:636 +#: install-methods.xml:632 #, no-c-format msgid "# zcat boot.img.gz > /dev/sdX" msgstr "" #. Tag: para -#: install-methods.xml:638 +#: install-methods.xml:634 #, no-c-format msgid "Create a partition of type \"Apple_Bootstrap\" on your USB stick using mac-fdisk's C command and extract the image directly to that:" msgstr "" #. Tag: screen -#: install-methods.xml:644 +#: install-methods.xml:640 #, no-c-format msgid "# zcat boot.img.gz > /dev/sdX2" msgstr "" #. Tag: para -#: install-methods.xml:646 +#: install-methods.xml:642 #, no-c-format msgid "After that, mount the USB memory stick (mount /dev/sdX /mnt), (mount /dev/sdX2 /mnt), which will now have a FAT filesystem an HFS filesystem on it, and copy a &debian; netinst or businesscard ISO image to it. Unmount the stick (umount /mnt) and you are done." msgstr "" #. Tag: title -#: install-methods.xml:663 +#: install-methods.xml:659 #, no-c-format -msgid "Copying the files — the flexible way" +msgid "Manually copying files to the USB stick — the flexible way" msgstr "" #. Tag: para -#: install-methods.xml:664 +#: install-methods.xml:660 #, no-c-format msgid "If you like more flexibility or just want to know what's going on, you should use the following method to put the files on your stick. One advantage of using this method is that — if the capacity of your USB stick is large enough — you have the option of copying a full CD ISO image to it." msgstr "" #. Tag: title -#: install-methods.xml:679 install-methods.xml:791 +#: install-methods.xml:675 install-methods.xml:787 #, no-c-format msgid "Partitioning the USB stick" msgstr "" #. Tag: para -#: install-methods.xml:680 +#: install-methods.xml:676 #, no-c-format msgid "We will show how to set up the memory stick to use the first partition, instead of the entire device." msgstr "" #. Tag: para -#: install-methods.xml:685 +#: install-methods.xml:681 #, no-c-format msgid "" "Since most USB sticks come pre-configured with a single FAT16 partition, you probably won't have to repartition or reformat the stick. If you have to do that anyway, use cfdisk or any other partitioning tool to create a FAT16 partition Don't forget to set the bootable bootable flag. , and then create the filesystem using: \n" @@ -516,13 +526,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:704 +#: install-methods.xml:700 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. Although any boot loader (e.g. lilo) should work, it's convenient to use syslinux, since it uses a FAT16 partition and can be reconfigured by just editing a text file. Any operating system which supports the FAT file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:714 +#: install-methods.xml:710 #, no-c-format msgid "" "To put syslinux on the FAT16 partition on your USB stick, install the syslinux and mtools packages on your system, and do: \n" @@ -531,19 +541,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:731 install-methods.xml:838 +#: install-methods.xml:727 install-methods.xml:834 #, no-c-format msgid "Adding the installer image" msgstr "" #. Tag: para -#: install-methods.xml:732 +#: install-methods.xml:728 #, no-c-format msgid "Mount the partition (mount /dev/sdX1 /mnt) and copy the following installer image files to the stick: vmlinuz or linux (kernel binary) initrd.gz (initial ramdisk image) You can choose between either the regular version or the graphical version of the installer. The latter can be found in the gtk subdirectory. If you want to rename the files, please note that syslinux can only process DOS (8.3) file names." msgstr "" #. Tag: para -#: install-methods.xml:756 +#: install-methods.xml:752 #, no-c-format msgid "" "Next you should create a syslinux.cfg configuration file, which at a bare minimum should contain the following two lines (change the name of the kernel binary to linux if you used a netboot image): \n" @@ -553,13 +563,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:768 +#: install-methods.xml:764 #, no-c-format msgid "If you used an hd-media image, you should now copy a &debian; ISO image You can use either a businesscard, a netinst or a full CD image (see ). Be sure to select one that fits. Note that the netboot mini.iso image is not usable for this purpose. onto the stick. When you are done, unmount the USB memory stick (umount /mnt)." msgstr "" #. Tag: para -#: install-methods.xml:792 +#: install-methods.xml:788 #, no-c-format msgid "" "Most USB sticks do not come pre-configured in such a way that Open Firmware can boot from them, so you will need to repartition the stick. On Mac systems, run mac-fdisk /dev/sdX, initialise a new partition map using the i command, and create a new partition of type Apple_Bootstrap using the C command. (Note that the first \"partition\" will always be the partition map itself.) Then type \n" @@ -568,13 +578,13 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:809 +#: install-methods.xml:805 #, no-c-format msgid "In order to start the kernel after booting from the USB stick, we will put a boot loader on the stick. The yaboot boot loader can be installed on an HFS filesystem and can be reconfigured by just editing a text file. Any operating system which supports the HFS file system can be used to make changes to the configuration of the boot loader." msgstr "" #. Tag: para -#: install-methods.xml:818 +#: install-methods.xml:814 #, no-c-format msgid "" "The normal ybin tool that comes with yaboot does not yet understand USB storage devices, so you will have to install yaboot by hand using the hfsutils tools. Type \n" @@ -587,37 +597,37 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:839 +#: install-methods.xml:835 #, no-c-format msgid "Mount the partition (mount /dev/sdX2 /mnt) and copy the following installer image files to the stick:" msgstr "" #. Tag: para -#: install-methods.xml:846 +#: install-methods.xml:842 #, no-c-format msgid "vmlinux (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:851 +#: install-methods.xml:847 #, no-c-format msgid "initrd.gz (initial ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:856 +#: install-methods.xml:852 #, no-c-format msgid "yaboot.conf (yaboot configuration file)" msgstr "" #. Tag: para -#: install-methods.xml:861 +#: install-methods.xml:857 #, no-c-format msgid "boot.msg (optional boot message)" msgstr "" #. Tag: para -#: install-methods.xml:868 +#: install-methods.xml:864 #, no-c-format msgid "" "The yaboot.conf configuration file should contain the following lines: \n" @@ -635,283 +645,265 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:878 +#: install-methods.xml:874 #, no-c-format msgid "If you used an hd-media image, you should now copy a &debian; ISO image (businesscard, netinst or full CD image; be sure to select one that fits) onto the stick. When you are done, unmount the USB memory stick (umount /mnt)." msgstr "" #. Tag: title -#: install-methods.xml:893 -#, no-c-format -msgid "Booting the USB stick" -msgstr "" - -#. Tag: para #: install-methods.xml:894 #, no-c-format -msgid "If your system refuses to boot from the memory stick, the stick may contain an invalid master boot record (MBR). To fix this, use the install-mbr command from the package mbr:" -msgstr "" - -#. Tag: screen -#: install-methods.xml:901 -#, no-c-format -msgid "# install-mbr /dev/sdX" -msgstr "" - -#. Tag: title -#: install-methods.xml:912 -#, no-c-format msgid "Preparing Files for Hard Disk Booting" msgstr "" #. Tag: para -#: install-methods.xml:913 +#: install-methods.xml:895 #, no-c-format msgid "The installer may be booted using boot files placed on an existing hard drive partition, either launched from another operating system or by invoking a boot loader directly from the BIOS." msgstr "" #. Tag: para -#: install-methods.xml:919 +#: install-methods.xml:901 #, no-c-format msgid "A full, pure network installation can be achieved using this technique. This avoids all hassles of removable media, like finding and burning CD images or struggling with too numerous and unreliable floppy disks." msgstr "" #. Tag: para -#: install-methods.xml:926 +#: install-methods.xml:908 #, no-c-format msgid "The installer cannot boot from files on an HFS+ file system. MacOS System 8.1 and above may use HFS+ file systems; NewWorld PowerMacs all use HFS+. To determine whether your existing file system is HFS+, select Get Info for the volume in question. HFS file systems appear as Mac OS Standard, while HFS+ file systems say Mac OS Extended. You must have an HFS partition in order to exchange files between MacOS and Linux, in particular the installation files you download." msgstr "" #. Tag: para -#: install-methods.xml:937 +#: install-methods.xml:919 #, no-c-format msgid "Different programs are used for hard disk installation system booting, depending on whether the system is a NewWorld or an OldWorld model." msgstr "" #. Tag: title -#: install-methods.xml:946 +#: install-methods.xml:928 #, no-c-format msgid "Hard disk installer booting using LILO or GRUB" msgstr "" #. Tag: para -#: install-methods.xml:948 +#: install-methods.xml:930 #, no-c-format msgid "This section explains how to add to or even replace an existing linux installation using either LILO or GRUB." msgstr "" #. Tag: para -#: install-methods.xml:954 +#: install-methods.xml:936 #, no-c-format msgid "At boot time, both bootloaders support loading in memory not only the kernel, but also a disk image. This RAM disk can be used as the root file-system by the kernel." msgstr "" #. Tag: para -#: install-methods.xml:960 +#: install-methods.xml:942 #, no-c-format msgid "Copy the following files from the &debian; archives to a convenient location on your hard drive (note that LILO can not boot from files on an NTFS file system), for instance to /boot/newinstall/." msgstr "" #. Tag: para -#: install-methods.xml:968 +#: install-methods.xml:950 #, no-c-format msgid "vmlinuz (kernel binary)" msgstr "" #. Tag: para -#: install-methods.xml:973 +#: install-methods.xml:955 #, no-c-format msgid "initrd.gz (ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:980 +#: install-methods.xml:962 #, no-c-format msgid "Finally, to configure the bootloader proceed to ." msgstr "" #. Tag: title -#: install-methods.xml:990 +#: install-methods.xml:972 #, no-c-format msgid "Hard disk installer booting using loadlin" msgstr "" #. Tag: para -#: install-methods.xml:991 +#: install-methods.xml:973 #, no-c-format msgid "This section explains how to prepare your hard drive for booting the installer from DOS using loadlin." msgstr "" #. Tag: para -#: install-methods.xml:996 +#: install-methods.xml:978 #, no-c-format msgid "Copy the following directories from a &debian; CD image to c:\\." msgstr "" #. Tag: para -#: install-methods.xml:1001 +#: install-methods.xml:983 #, no-c-format msgid "/&x86-install-dir; (kernel binary and ramdisk image)" msgstr "" #. Tag: para -#: install-methods.xml:1006 +#: install-methods.xml:988 #, no-c-format msgid "/tools (loadlin tool)" msgstr "" #. Tag: title -#: install-methods.xml:1019 +#: install-methods.xml:1001 #, no-c-format msgid "Hard Disk Installer Booting for OldWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1020 +#: install-methods.xml:1002 #, no-c-format msgid "The boot-floppy-hfs floppy uses miBoot to launch Linux installation, but miBoot cannot easily be used for hard disk booting. BootX, launched from MacOS, supports booting from files placed on the hard disk. BootX can also be used to dual-boot MacOS and Linux after your &debian; installation is complete. For the Performa 6360, it appears that quik cannot make the hard disk bootable. So BootX is required on that model." msgstr "" #. Tag: para -#: install-methods.xml:1033 +#: install-methods.xml:1015 #, no-c-format msgid "Download and unstuff the BootX distribution, available from , or in the dists/woody/main/disks-powerpc/current/powermac directory on &debian; http/ftp mirrors and official &debian; CDs. Use Stuffit Expander to extract it from its archive. Within the package, there is an empty folder called Linux Kernels. Download linux.bin and ramdisk.image.gz from the disks-powerpc/current/powermac folder, and place them in the Linux Kernels folder. Then place the Linux Kernels folder in the active System Folder." msgstr "" #. Tag: title -#: install-methods.xml:1053 +#: install-methods.xml:1035 #, no-c-format msgid "Hard Disk Installer Booting for NewWorld Macs" msgstr "" #. Tag: para -#: install-methods.xml:1054 +#: install-methods.xml:1036 #, no-c-format msgid "NewWorld PowerMacs support booting from a network or an ISO9660 CD-ROM, as well as loading ELF binaries directly from the hard disk. These machines will boot Linux directly via yaboot, which supports loading a kernel and RAMdisk directly from an ext2 partition, as well as dual-booting with MacOS. Hard disk booting of the installer is particularly appropriate for newer machines without floppy drives. BootX is not supported and must not be used on NewWorld PowerMacs." msgstr "" #. Tag: para -#: install-methods.xml:1065 +#: install-methods.xml:1047 #, no-c-format msgid "Copy (not move) the following four files which you downloaded earlier from the &debian; archives, onto the root level of your hard drive (this can be accomplished by option-dragging each file to the hard drive icon)." msgstr "" #. Tag: filename -#: install-methods.xml:1075 install-methods.xml:1401 +#: install-methods.xml:1057 install-methods.xml:1383 #, no-c-format msgid "vmlinux" msgstr "" #. Tag: filename -#: install-methods.xml:1080 install-methods.xml:1406 +#: install-methods.xml:1062 install-methods.xml:1388 #, no-c-format msgid "initrd.gz" msgstr "" #. Tag: filename -#: install-methods.xml:1085 install-methods.xml:1411 +#: install-methods.xml:1067 install-methods.xml:1393 #, no-c-format msgid "yaboot" msgstr "" #. Tag: filename -#: install-methods.xml:1090 install-methods.xml:1416 +#: install-methods.xml:1072 install-methods.xml:1398 #, no-c-format msgid "yaboot.conf" msgstr "" #. Tag: para -#: install-methods.xml:1095 +#: install-methods.xml:1077 #, no-c-format msgid "Make a note of the partition number of the MacOS partition where you place these files. If you have the MacOS pdisk program, you can use the L command to check for the partition number. You will need this partition number for the command you type at the Open Firmware prompt when you boot the installer." msgstr "" #. Tag: para -#: install-methods.xml:1103 +#: install-methods.xml:1085 #, no-c-format msgid "To boot the installer, proceed to ." msgstr "" #. Tag: title -#: install-methods.xml:1116 +#: install-methods.xml:1098 #, no-c-format msgid "Preparing Files for TFTP Net Booting" msgstr "" #. Tag: para -#: install-methods.xml:1117 +#: install-methods.xml:1099 #, no-c-format msgid "If your machine is connected to a local area network, you may be able to boot it over the network from another machine, using TFTP. If you intend to boot the installation system from another machine, the boot files will need to be placed in specific locations on that machine, and the machine configured to support booting of your specific machine." msgstr "" #. Tag: para -#: install-methods.xml:1125 +#: install-methods.xml:1107 #, no-c-format msgid "You need to set up a TFTP server, and for many machines a DHCP server, or RARP server, or BOOTP server." msgstr "" #. Tag: para -#: install-methods.xml:1132 +#: install-methods.xml:1114 #, no-c-format msgid "The Reverse Address Resolution Protocol (RARP) is one way to tell your client what IP address to use for itself. Another way is to use the BOOTP protocol. BOOTP is an IP protocol that informs a computer of its IP address and where on the network to obtain a boot image. The DHCP (Dynamic Host Configuration Protocol) is a more flexible, backwards-compatible extension of BOOTP. Some systems can only be configured via DHCP." msgstr "" #. Tag: para -#: install-methods.xml:1146 +#: install-methods.xml:1128 #, no-c-format msgid "For PowerPC, if you have a NewWorld Power Macintosh machine, it is a good idea to use DHCP instead of BOOTP. Some of the latest machines are unable to boot using BOOTP." msgstr "" #. Tag: para -#: install-methods.xml:1152 +#: install-methods.xml:1134 #, no-c-format msgid "Some older HPPA machines (e.g. 715/75) use RBOOTD rather than BOOTP. There is an rbootd package available in &debian;." msgstr "" #. Tag: para -#: install-methods.xml:1157 +#: install-methods.xml:1139 #, no-c-format msgid "The Trivial File Transfer Protocol (TFTP) is used to serve the boot image to the client. Theoretically, any server, on any platform, which implements these protocols, may be used. In the examples in this section, we shall provide commands for SunOS 4.x, SunOS 5.x (a.k.a. Solaris), and GNU/Linux." msgstr "" #. Tag: para -#: install-methods.xml:1165 +#: install-methods.xml:1147 #, no-c-format msgid "For a &debian-gnu; server we recommend tftpd-hpa. It's written by the same author as the syslinux bootloader and is therefore least likely to cause issues. A good alternative is atftpd." msgstr "" #. Tag: title -#: install-methods.xml:1181 +#: install-methods.xml:1163 #, no-c-format msgid "Setting up RARP server" msgstr "" #. Tag: para -#: install-methods.xml:1182 +#: install-methods.xml:1164 #, no-c-format msgid "To set up RARP, you need to know the Ethernet address (a.k.a. the MAC address) of the client computers to be installed. If you don't know this information, you can pick it off the initial OpenPROM boot messages, use the OpenBoot .enet-addr command, or boot into Rescue mode (e.g., from the rescue floppy) and use the command ip addr show dev eth0." msgstr "" #. Tag: para -#: install-methods.xml:1194 +#: install-methods.xml:1176 #, no-c-format msgid "On a RARP server system using a Linux 2.4 or 2.6 kernel, or Solaris/SunOS, you use the rarpd program. You need to ensure that the Ethernet hardware address for the client is listed in the ethers database (either in the /etc/ethers file, or via NIS/NIS+) and in the hosts database. Then you need to start the RARP daemon. Issue the command (as root): /usr/sbin/rarpd -a on most Linux systems and SunOS 5 (Solaris 2), /usr/sbin/in.rarpd -a on some other Linux systems, or /usr/etc/rarpd -a in SunOS 4 (Solaris 1)." msgstr "" #. Tag: title -#: install-methods.xml:1215 +#: install-methods.xml:1197 #, no-c-format msgid "Setting up a DHCP server" msgstr "" #. Tag: para -#: install-methods.xml:1216 +#: install-methods.xml:1198 #, no-c-format msgid "One free software DHCP server is ISC dhcpd. For &debian-gnu;, the dhcp3-server package is recommended. Here is a sample configuration file for it (see /etc/dhcp3/dhcpd.conf):" msgstr "" #. Tag: screen -#: install-methods.xml:1223 +#: install-methods.xml:1205 #, no-c-format msgid "" "option domain-name \"example.com\";\n" @@ -936,25 +928,25 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1225 +#: install-methods.xml:1207 #, no-c-format msgid "In this example, there is one server servername which performs all of the work of DHCP server, TFTP server, and network gateway. You will almost certainly need to change the domain-name options, as well as the server name and client hardware address. The filename option should be the name of the file which will be retrieved via TFTP." msgstr "" #. Tag: para -#: install-methods.xml:1235 +#: install-methods.xml:1217 #, no-c-format msgid "After you have edited the dhcpd configuration file, restart it with /etc/init.d/dhcp3-server restart." msgstr "" #. Tag: title -#: install-methods.xml:1243 +#: install-methods.xml:1225 #, no-c-format msgid "Enabling PXE Booting in the DHCP configuration" msgstr "" #. Tag: para -#: install-methods.xml:1244 +#: install-methods.xml:1226 #, no-c-format msgid "" "Here is another example for a dhcp.conf using the Pre-boot Execution Environment (PXE) method of TFTP. \n" @@ -989,19 +981,19 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1264 +#: install-methods.xml:1246 #, no-c-format msgid "Setting up a BOOTP server" msgstr "" #. Tag: para -#: install-methods.xml:1265 +#: install-methods.xml:1247 #, no-c-format msgid "There are two BOOTP servers available for GNU/Linux. The first is CMU bootpd. The other is actually a DHCP server: ISC dhcpd. In &debian-gnu; these are contained in the bootp and dhcp3-server packages respectively." msgstr "" #. Tag: para -#: install-methods.xml:1273 +#: install-methods.xml:1255 #, no-c-format msgid "" "To use CMU bootpd, you must first uncomment (or add) the relevant line in /etc/inetd.conf. On &debian-gnu;, you can run update-inetd --enable bootps, then /etc/init.d/inetd reload to do so. Just in case your BOOTP server does not run &debian;, the line in question should look like: \n" @@ -1018,43 +1010,43 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1306 +#: install-methods.xml:1288 #, no-c-format msgid "By contrast, setting up BOOTP with ISC dhcpd is really easy, because it treats BOOTP clients as a moderately special case of DHCP clients. Some architectures require a complex configuration for booting clients via BOOTP. If yours is one of those, read the section . Otherwise you will probably be able to get away with simply adding the allow bootp directive to the configuration block for the subnet containing the client in /etc/dhcp3/dhcpd.conf, and restart dhcpd with /etc/init.d/dhcp3-server restart." msgstr "" #. Tag: title -#: install-methods.xml:1325 +#: install-methods.xml:1307 #, no-c-format msgid "Enabling the TFTP Server" msgstr "" #. Tag: para -#: install-methods.xml:1326 +#: install-methods.xml:1308 #, no-c-format msgid "To get the TFTP server ready to go, you should first make sure that tftpd is enabled." msgstr "" #. Tag: para -#: install-methods.xml:1331 +#: install-methods.xml:1313 #, no-c-format msgid "In the case of tftpd-hpa there are two ways the service can be run. It can be started on demand by the system's inetd daemon, or it can be set up to run as an independent daemon. Which of these methods is used is selected when the package is installed and can be changed by reconfiguring the package." msgstr "" #. Tag: para -#: install-methods.xml:1340 +#: install-methods.xml:1322 #, no-c-format msgid "Historically, TFTP servers used /tftpboot as directory to serve images from. However, &debian-gnu; packages may use other directories to comply with the Filesystem Hierarchy Standard. For example, tftpd-hpa by default uses /srv/tftp. You may have to adjust the configuration examples in this section accordingly." msgstr "" #. Tag: para -#: install-methods.xml:1350 +#: install-methods.xml:1332 #, no-c-format msgid "All in.tftpd alternatives available in &debian; should log TFTP requests to the system logs by default. Some of them support a -v argument to increase verbosity. It is recommended to check these log messages in case of boot problems as they are a good starting point for diagnosing the cause of errors." msgstr "" #. Tag: para -#: install-methods.xml:1358 +#: install-methods.xml:1340 #, no-c-format msgid "" "If you intend to install &debian; on an SGI machine and your TFTP server is a GNU/Linux box running Linux 2.4, you'll need to set the following on your server: \n" @@ -1065,49 +1057,49 @@ msgid "" msgstr "" #. Tag: title -#: install-methods.xml:1380 +#: install-methods.xml:1362 #, no-c-format msgid "Move TFTP Images Into Place" msgstr "" #. Tag: para -#: install-methods.xml:1381 +#: install-methods.xml:1363 #, no-c-format msgid "Next, place the TFTP boot image you need, as found in , in the tftpd boot image directory. You may have to make a link from that file to the file which tftpd will use for booting a particular client. Unfortunately, the file name is determined by the TFTP client, and there are no strong standards." msgstr "" #. Tag: para -#: install-methods.xml:1390 +#: install-methods.xml:1372 #, no-c-format msgid "On NewWorld Power Macintosh machines, you will need to set up the yaboot boot loader as the TFTP boot image. Yaboot will then retrieve the kernel and RAMdisk images via TFTP itself. You will need to download the following files from the netboot/ directory:" msgstr "" #. Tag: filename -#: install-methods.xml:1421 +#: install-methods.xml:1403 #, no-c-format msgid "boot.msg" msgstr "" #. Tag: para -#: install-methods.xml:1426 +#: install-methods.xml:1408 #, no-c-format msgid "For PXE booting, everything you should need is set up in the netboot/netboot.tar.gz tarball. Simply extract this tarball into the tftpd boot image directory. Make sure your dhcp server is configured to pass pxelinux.0 to tftpd as the filename to boot." msgstr "" #. Tag: para -#: install-methods.xml:1434 +#: install-methods.xml:1416 #, no-c-format msgid "For PXE booting, everything you should need is set up in the netboot/netboot.tar.gz tarball. Simply extract this tarball into the tftpd boot image directory. Make sure your dhcp server is configured to pass /debian-installer/ia64/elilo.efi to tftpd as the filename to boot." msgstr "" #. Tag: title -#: install-methods.xml:1446 +#: install-methods.xml:1428 #, no-c-format msgid "SPARC TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1447 +#: install-methods.xml:1429 #, no-c-format msgid "" "Some SPARC architectures add the subarchitecture names, such as SUN4M or SUN4C, to the filename. Thus, if your system's subarchitecture is a SUN4C, and its IP is 192.168.1.3, the filename would be C0A80103.SUN4C. However, there are also subarchitectures where the file the client looks for is just client-ip-in-hex. An easy way to determine the hexadecimal code for the IP address is to enter the following command in a shell (assuming the machine's intended IP is 10.0.0.4). \n" @@ -1116,55 +1108,55 @@ msgid "" msgstr "" #. Tag: para -#: install-methods.xml:1463 +#: install-methods.xml:1445 #, no-c-format msgid "If you've done all this correctly, giving the command boot net from the OpenPROM should load the image. If the image cannot be found, try checking the logs on your tftp server to see which image name is being requested." msgstr "" #. Tag: para -#: install-methods.xml:1470 +#: install-methods.xml:1452 #, no-c-format msgid "You can also force some sparc systems to look for a specific file name by adding it to the end of the OpenPROM boot command, such as boot net my-sparc.image. This must still reside in the directory that the TFTP server looks in." msgstr "" #. Tag: title -#: install-methods.xml:1481 +#: install-methods.xml:1463 #, no-c-format msgid "SGI TFTP Booting" msgstr "" #. Tag: para -#: install-methods.xml:1482 +#: install-methods.xml:1464 #, no-c-format msgid "On SGI machines you can rely on the bootpd to supply the name of the TFTP file. It is given either as the bf= in /etc/bootptab or as the filename= option in /etc/dhcpd.conf." msgstr "" #. Tag: title -#: install-methods.xml:1590 +#: install-methods.xml:1572 #, no-c-format msgid "Automatic Installation" msgstr "" #. Tag: para -#: install-methods.xml:1591 +#: install-methods.xml:1573 #, no-c-format msgid "For installing on multiple computers it's possible to do fully automatic installations. &debian; packages intended for this include fai-quickstart (which can use an install server) and the &debian; Installer itself. Have a look at the FAI home page for detailed information." msgstr "" #. Tag: title -#: install-methods.xml:1603 +#: install-methods.xml:1585 #, no-c-format msgid "Automatic Installation Using the &debian; Installer" msgstr "" #. Tag: para -#: install-methods.xml:1604 +#: install-methods.xml:1586 #, no-c-format msgid "The &debian; Installer supports automating installs via preconfiguration files. A preconfiguration file can be loaded from the network or from removable media, and used to fill in answers to questions asked during the installation process." msgstr "" #. Tag: para -#: install-methods.xml:1611 +#: install-methods.xml:1593 #, no-c-format msgid "Full documentation on preseeding including a working example that you can edit is in ." msgstr "" diff --git a/po/pot/installation-howto.pot b/po/pot/installation-howto.pot index f20ddeeed..ece17af28 100644 --- a/po/pot/installation-howto.pot +++ b/po/pot/installation-howto.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: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -131,179 +131,185 @@ msgstr "" #. Tag: para #: installation-howto.xml:138 #, no-c-format +msgid "The easiest way to prepare your USB memory stick is to download any Debian CD or DVD image that will fit on it, and write the CD image directly to the memory stick. Of course this will destroy anything already on the memory stick. This works because Debian CD images are \"isohybrid\" images that can boot both from CD and from USB drives." +msgstr "" + +#. Tag: para +#: installation-howto.xml:146 +#, no-c-format msgid "The easiest way to prepare your USB memory stick is to download hd-media/boot.img.gz, and use gunzip to extract the 256 MB image from that file. Write this image directly to your memory stick, which must be at least 256 mb in size. Of course this will destroy anything already on the memory stick. Then mount the memory stick, which will now have a FAT filesystem on it. Next, download a &debian; netinst CD image, and copy that file to the memory stick; any filename is ok as long as it ends in .iso." msgstr "" #. Tag: para -#: installation-howto.xml:149 +#: installation-howto.xml:157 #, no-c-format msgid "There are other, more flexible ways to set up a memory stick to use the debian-installer, and it's possible to get it to work with smaller memory sticks. For details, see ." msgstr "" #. Tag: para -#: installation-howto.xml:155 +#: installation-howto.xml:163 #, no-c-format msgid "Some BIOSes can boot USB storage directly, and some cannot. You may need to configure your BIOS to boot from a removable drive or even a USB-ZIP to get it to boot from the USB device. For helpful hints and details, see ." msgstr "" #. Tag: para -#: installation-howto.xml:162 +#: installation-howto.xml:170 #, no-c-format msgid "Booting Macintosh systems from USB storage devices involves manual use of Open Firmware. For directions, see ." msgstr "" #. Tag: title -#: installation-howto.xml:171 +#: installation-howto.xml:179 #, no-c-format msgid "Booting from network" msgstr "" #. Tag: para -#: installation-howto.xml:172 +#: installation-howto.xml:180 #, no-c-format msgid "It's also possible to boot &d-i; completely from the net. The various methods to netboot depend on your architecture and netboot setup. The files in netboot/ can be used to netboot &d-i;." msgstr "" #. Tag: para -#: installation-howto.xml:178 +#: installation-howto.xml:186 #, no-c-format msgid "The easiest thing to set up is probably PXE netbooting. Untar the file netboot/pxeboot.tar.gz into /srv/tftp or wherever is appropriate for your tftp server. Set up your DHCP server to pass filename /pxelinux.0 to clients, and with luck everything will just work. For detailed instructions, see ." msgstr "" #. Tag: title -#: installation-howto.xml:192 +#: installation-howto.xml:200 #, no-c-format msgid "Booting from hard disk" msgstr "" #. Tag: para -#: installation-howto.xml:193 +#: installation-howto.xml:201 #, no-c-format msgid "It's possible to boot the installer using no removable media, but just an existing hard disk, which can have a different OS on it. Download hd-media/initrd.gz, hd-media/vmlinuz, and a &debian; CD image to the top-level directory of the hard disk. Make sure that the CD image has a filename ending in .iso. Now it's just a matter of booting linux with the initrd. explains one way to do it. " msgstr "" #. Tag: title -#: installation-howto.xml:210 +#: installation-howto.xml:218 #, no-c-format msgid "Installation" msgstr "" #. Tag: para -#: installation-howto.xml:211 +#: installation-howto.xml:219 #, no-c-format msgid "Once the installer starts, you will be greeted with an initial screen. Press &enterkey; to boot, or read the instructions for other boot methods and parameters (see )." msgstr "" #. Tag: para -#: installation-howto.xml:217 +#: installation-howto.xml:225 #, no-c-format msgid "After a while you will be asked to select your language. Use the arrow keys to pick a language and press &enterkey; to continue. Next you'll be asked to select your country, with the choices including countries where your language is spoken. If it's not on the short list, a list of all the countries in the world is available." msgstr "" #. Tag: para -#: installation-howto.xml:225 +#: installation-howto.xml:233 #, no-c-format msgid "You may be asked to confirm your keyboard layout. Choose the default unless you know better." msgstr "" #. Tag: para -#: installation-howto.xml:230 +#: installation-howto.xml:238 #, no-c-format msgid "Now sit back while debian-installer detects some of your hardware, and loads the rest of itself from CD, floppy, USB, etc." msgstr "" #. Tag: para -#: installation-howto.xml:235 +#: installation-howto.xml:243 #, no-c-format msgid "Next the installer will try to detect your network hardware and set up networking by DHCP. If you are not on a network or do not have DHCP, you will be given the opportunity to configure the network manually." msgstr "" #. Tag: para -#: installation-howto.xml:241 +#: installation-howto.xml:249 #, no-c-format msgid "The next step is setting up your clock and time zone. The installer will try to contact a time server on the Internet to ensure the clock is set correctly. The time zone is based on the country selected earlier and the installer will only ask to select one if a country has multiple zones." msgstr "" #. Tag: para -#: installation-howto.xml:248 +#: installation-howto.xml:256 #, no-c-format msgid "Now it is time to partition your disks. First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive (see ). This is recommended for new users or anyone in a hurry. If you do not want to autopartition, choose Manual from the menu." msgstr "" #. Tag: para -#: installation-howto.xml:256 +#: installation-howto.xml:264 #, no-c-format msgid "If you have an existing DOS or Windows partition that you want to preserve, be very careful with automatic partitioning. If you choose manual partitioning, you can use the installer to resize existing FAT or NTFS partitions to create room for the &debian; install: simply select the partition and specify its new size." msgstr "" #. Tag: para -#: installation-howto.xml:263 +#: installation-howto.xml:271 #, no-c-format msgid "On the next screen you will see your partition table, how the partitions will be formatted, and where they will be mounted. Select a partition to modify or delete it. If you did automatic partitioning, you should just be able to choose Finish partitioning and write changes to disk from the menu to use what it set up. Remember to assign at least one partition for swap space and to mount a partition on /. For more detailed information on how to use the partitioner, please refer to ; the appendix has more general information about partitioning." msgstr "" #. Tag: para -#: installation-howto.xml:276 +#: installation-howto.xml:284 #, no-c-format msgid "Now &d-i; formats your partitions and starts to install the base system, which can take a while. That is followed by installing a kernel." msgstr "" #. Tag: para -#: installation-howto.xml:281 +#: installation-howto.xml:289 #, no-c-format msgid "The base system that was installed earlier is a working, but very minimal installation. To make the system more functional the next step allows you to install additional packages by selecting tasks. Before packages can be installed apt needs to be configured as that defines from where the packages will be retrieved. The Standard system task will be selected by default and should normally be installed. Select the Desktop environment task if you would like to have a graphical desktop after the installation. See for additional information about this step." msgstr "" #. Tag: para -#: installation-howto.xml:293 +#: installation-howto.xml:301 #, no-c-format msgid "Installation of the base system is followed by setting up user accounts. By default you will need to provide a password for the root (administrator) account and information necessary to create one regular user account." msgstr "" #. Tag: para -#: installation-howto.xml:300 +#: installation-howto.xml:308 #, no-c-format msgid "The last step is to install a boot loader. If the installer detects other operating systems on your computer, it will add them to the boot menu and let you know. By default GRUB will be installed to the master boot record of the first harddrive, which is generally a good choice. You'll be given the opportunity to override that choice and install it elsewhere. " msgstr "" #. Tag: para -#: installation-howto.xml:310 +#: installation-howto.xml:318 #, no-c-format msgid "&d-i; will now tell you that the installation has finished. Remove the cdrom or other boot media and hit &enterkey; to reboot your machine. It should boot up into the newly installed system and allow you to log in. This is explained in ." msgstr "" #. Tag: para -#: installation-howto.xml:317 +#: installation-howto.xml:325 #, no-c-format msgid "If you need more information on the install process, see ." msgstr "" #. Tag: title -#: installation-howto.xml:326 +#: installation-howto.xml:334 #, no-c-format msgid "Send us an installation report" msgstr "" #. Tag: para -#: installation-howto.xml:327 +#: installation-howto.xml:335 #, no-c-format msgid "If you successfully managed an installation with &d-i;, please take time to provide us with a report. The simplest way to do so is to install the reportbug package (aptitude install reportbug), configure reportbug as explained in , and run reportbug installation-reports." msgstr "" #. Tag: para -#: installation-howto.xml:337 +#: installation-howto.xml:345 #, no-c-format msgid "If you did not complete the install, you probably found a bug in debian-installer. To improve the installer it is necessary that we know about them, so please take the time to report them. You can use an installation report to report problems; if the install completely fails, see ." msgstr "" #. Tag: title -#: installation-howto.xml:349 +#: installation-howto.xml:357 #, no-c-format msgid "And finally…" msgstr "" #. Tag: para -#: installation-howto.xml:350 +#: installation-howto.xml:358 #, no-c-format msgid "We hope that your &debian; installation is pleasant and that you find &debian; useful. You might want to read ." msgstr "" diff --git a/po/pot/preseed.pot b/po/pot/preseed.pot index f61071809..09ab589ec 100644 --- a/po/pot/preseed.pot +++ b/po/pot/preseed.pot @@ -6,7 +6,7 @@ msgid "" msgstr "" "Project-Id-Version: PACKAGE VERSION\n" "Report-Msgid-Bugs-To: debian-boot@lists.debian.org\n" -"POT-Creation-Date: 2010-12-29 12:07+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -27,7 +27,7 @@ msgid "This appendix explains how to preseed answers to questions in &d-i; to au msgstr "" #. Tag: para -#: preseed.xml:23 preseed.xml:676 +#: preseed.xml:23 preseed.xml:677 #, no-c-format msgid "The configuration fragments used in this appendix are also available as an example preconfiguration file from &urlset-example-preseed;." msgstr "" @@ -81,7 +81,7 @@ msgid "initrd" msgstr "" #. Tag: entry -#: preseed.xml:70 preseed.xml:523 +#: preseed.xml:70 preseed.xml:524 #, no-c-format msgid "file" msgstr "" @@ -246,77 +246,77 @@ msgstr "" #. Tag: para #: preseed.xml:285 #, no-c-format -msgid "Note that preseed/url can be shortened to just url and preseed/file to just file when they are passed as boot parameters." +msgid "Note that preseed/url can be shortened to just url, preseed/file to just file and preseed/file/checksum to just preseed-md5 when they are passed as boot parameters." msgstr "" #. Tag: title -#: preseed.xml:295 +#: preseed.xml:296 #, no-c-format msgid "Using boot parameters to preseed questions" msgstr "" #. Tag: para -#: preseed.xml:296 +#: preseed.xml:297 #, no-c-format msgid "If a preconfiguration file cannot be used to preseed some steps, the install can still be fully automated, since you can pass preseed values on the command line when booting the installer." msgstr "" #. Tag: para -#: preseed.xml:302 +#: preseed.xml:303 #, no-c-format msgid "Boot parameters can also be used if you do not really want to use preseeding, but just want to provide an answer for a specific question. Some examples where this can be useful are documented elsewhere in this manual." msgstr "" #. Tag: para -#: preseed.xml:308 +#: preseed.xml:309 #, no-c-format msgid "To set a value to be used inside &d-i;, just pass path/to/variable=value for any of the preseed variables listed in the examples in this appendix. If a value is to be used to configure packages for the target system, you will need to prepend the owner The owner of a debconf variable (or template) is normally the name of the package that contains the corresponding debconf template. For variables used in the installer itself the owner is d-i. Templates and variables can have more than one owner which helps to determine whether they can be removed from the debconf database if the package is purged. of the variable as in owner:path/to/variable=value. If you don't specify the owner, the value for the variable will not be copied to the debconf database in the target system and thus remain unused during the configuration of the relevant package." msgstr "" #. Tag: para -#: preseed.xml:331 +#: preseed.xml:332 #, no-c-format msgid "Normally, preseeding a question in this way will mean that the question will not be asked. To set a specific default value for a question, but still have the question asked, use ?= instead of = as operator. See also ." msgstr "" #. Tag: para -#: preseed.xml:338 +#: preseed.xml:339 #, no-c-format msgid "Note that some variables that are frequently set at the boot prompt have a shorter alias. If an alias is available, it is used in the examples in this appendix instead of the full variable. The preseed/url variable for example has been aliased as url. Another example is the tasks alias, which translates to tasksel:tasksel/first." msgstr "" #. Tag: para -#: preseed.xml:347 +#: preseed.xml:348 #, no-c-format msgid "A -- in the boot options has special meaning. Kernel parameters that appear after the last -- may be copied into the bootloader configuration for the installed system (if supported by the installer for the bootloader). The installer will automatically filter out any options (like preconfiguration options) that it recognizes." msgstr "" #. Tag: para -#: preseed.xml:356 +#: preseed.xml:357 #, no-c-format msgid "Current linux kernels (2.6.9 and later) accept a maximum of 32 command line options and 32 environment options, including any options added by default for the installer. If these numbers are exceeded, the kernel will panic (crash). (For earlier kernels, these numbers were lower.)" msgstr "" #. Tag: para -#: preseed.xml:364 +#: preseed.xml:365 #, no-c-format msgid "For most installations some of the default options in your bootloader configuration file, like vga=normal, may be safely removed which may allow you to add more options for preseeding." msgstr "" #. Tag: para -#: preseed.xml:371 +#: preseed.xml:372 #, no-c-format msgid "It may not always be possible to specify values with spaces for boot parameters, even if you delimit them with quotes." msgstr "" #. Tag: title -#: preseed.xml:380 +#: preseed.xml:381 #, no-c-format msgid "Auto mode" msgstr "" #. Tag: para -#: preseed.xml:381 +#: preseed.xml:382 #, no-c-format msgid "" "There are several features of &debian; Installer that combine to allow fairly simple command lines at the boot prompt to result in arbitrarily complex customized automatic installs. To illustrate this, here are some examples that can be used at the boot prompt: \n" @@ -325,13 +325,13 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:398 +#: preseed.xml:399 #, no-c-format msgid "The last part of that url (d-i/&releasename;/./preseed.cfg) is taken from auto-install/defaultroot. By default this includes the directory &releasename; to allow future versions to specify their own codename and let people migrate forwards in a controlled manner. The /./ bit is used to indicate a root, relative to which subsequent paths can be anchored (for use in preseed/include and preseed/run). This allows files to be specified either as full URLs, paths starting with / that are thus anchored, or even paths relative to the location where the last preseed file was found. This can be used to construct more portable scripts where an entire hierarchy of scripts can be moved to a new location without breaking it, for example copying the files onto a USB stick when they started out on a web server. In this example, if the preseed file sets preseed/run to /scripts/late_command.sh then the file will be fetched from http://autoserver.example.com/d-i/&releasename;/./scripts/late_command.sh." msgstr "" #. Tag: para -#: preseed.xml:418 +#: preseed.xml:419 #, no-c-format msgid "" "If there is no local DHCP or DNS infrastructure, or if you do not want to use the default path to preseed.cfg, you can still use an explicit url, and if you don't use the /./ element it will be anchored to the start of the path (i.e. the third / in the URL). Here is an example that requires minimal support from the local network infrastructure: \n" @@ -340,25 +340,25 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:431 +#: preseed.xml:432 #, no-c-format msgid "if the URL is missing a protocol, http is assumed," msgstr "" #. Tag: para -#: preseed.xml:434 +#: preseed.xml:435 #, no-c-format msgid "if the hostname section contains no periods, it has the domain derived from DHCP appended to it, and" msgstr "" #. Tag: para -#: preseed.xml:438 +#: preseed.xml:439 #, no-c-format msgid "if there's no /'s after the hostname, then the default path is added." msgstr "" #. Tag: para -#: preseed.xml:444 +#: preseed.xml:445 #, no-c-format msgid "" "In addition to specifying the url, you can also specify settings that do not directly affect the behavior of &d-i; itself, but can be passed through to scripts specified using preseed/run in the loaded preseed file. At present, the only example of this is auto-install/classes, which has an alias classes. This can be used thus: \n" @@ -367,217 +367,217 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:458 +#: preseed.xml:459 #, no-c-format msgid "It is of course possible to extend this concept, and if you do, it is reasonable to use the auto-install namespace for this. So one might have something like auto-install/style which is then used in your scripts. If you feel the need to do this, please mention it on the debian-boot@lists.debian.org mailing list so that we can avoid namespace conflicts, and perhaps add an alias for the parameter for you." msgstr "" #. Tag: para -#: preseed.xml:468 +#: preseed.xml:469 #, no-c-format msgid "The auto boot label is not yet defined everywhere. The same effect may be achieved by simply adding the two parameters auto=true priority=critical to the kernel command line. The auto parameter is an alias for auto-install/enable and setting it to true delays the locale and keyboard questions until after there has been a chance to preseed them, while priority is an alias for debconf/priority and setting it to critical stops any questions with a lower priority from being asked." msgstr "" #. Tag: para -#: preseed.xml:482 +#: preseed.xml:483 #, no-c-format msgid "Additional options that may be of interest while attempting to automate an install while using DHCP are: interface=auto netcfg/dhcp_timeout=60 which makes the machine choose the first viable NIC and be more patient about getting a reply to its DHCP query." msgstr "" #. Tag: para -#: preseed.xml:491 +#: preseed.xml:492 #, no-c-format msgid "An extensive example of how to use this framework, including example scripts and classes, can be found on the website of its developer. The examples available there also show many other nice effects that can be achieved by creative use of preconfiguration." msgstr "" #. Tag: title -#: preseed.xml:502 +#: preseed.xml:503 #, no-c-format msgid "Aliases useful with preseeding" msgstr "" #. Tag: para -#: preseed.xml:503 +#: preseed.xml:504 #, no-c-format msgid "The following aliases can be useful when using (auto mode) preseeding. Note that these are simply short aliases for question names, and you always need to specify a value as well: for example, auto=true or interface=eth0." msgstr "" #. Tag: entry -#: preseed.xml:516 +#: preseed.xml:517 #, no-c-format msgid "auto" msgstr "" #. Tag: entry -#: preseed.xml:516 +#: preseed.xml:517 #, no-c-format msgid "auto-install/enable" msgstr "" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:518 #, no-c-format msgid "classes" msgstr "" #. Tag: entry -#: preseed.xml:517 +#: preseed.xml:518 #, no-c-format msgid "auto-install/classes" msgstr "" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:519 #, no-c-format msgid "fb" msgstr "" #. Tag: entry -#: preseed.xml:518 +#: preseed.xml:519 #, no-c-format msgid "debian-installer/framebuffer" msgstr "" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:520 #, no-c-format msgid "language" msgstr "" #. Tag: entry -#: preseed.xml:519 +#: preseed.xml:520 #, no-c-format msgid "debian-installer/language" msgstr "" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:521 #, no-c-format msgid "country" msgstr "" #. Tag: entry -#: preseed.xml:520 +#: preseed.xml:521 #, no-c-format msgid "debian-installer/country" msgstr "" #. Tag: entry -#: preseed.xml:521 +#: preseed.xml:522 #, no-c-format msgid "locale" msgstr "" #. Tag: entry -#: preseed.xml:521 +#: preseed.xml:522 #, no-c-format msgid "debian-installer/locale" msgstr "" #. Tag: entry -#: preseed.xml:522 +#: preseed.xml:523 #, no-c-format msgid "priority" msgstr "" #. Tag: entry -#: preseed.xml:522 +#: preseed.xml:523 #, no-c-format msgid "debconf/priority" msgstr "" #. Tag: entry -#: preseed.xml:523 +#: preseed.xml:524 #, no-c-format msgid "preseed/file" msgstr "" #. Tag: entry -#: preseed.xml:524 +#: preseed.xml:525 #, no-c-format msgid "url" msgstr "" #. Tag: entry -#: preseed.xml:524 +#: preseed.xml:525 #, no-c-format msgid "preseed/url" msgstr "" #. Tag: entry -#: preseed.xml:525 +#: preseed.xml:526 #, no-c-format msgid "interface" msgstr "" #. Tag: entry -#: preseed.xml:525 +#: preseed.xml:526 #, no-c-format msgid "netcfg/choose_interface" msgstr "" #. Tag: entry -#: preseed.xml:526 +#: preseed.xml:527 #, no-c-format msgid "hostname   " msgstr "" #. Tag: entry -#: preseed.xml:526 +#: preseed.xml:527 #, no-c-format msgid "netcfg/get_hostname" msgstr "" #. Tag: entry -#: preseed.xml:527 +#: preseed.xml:528 #, no-c-format msgid "domain" msgstr "" #. Tag: entry -#: preseed.xml:527 +#: preseed.xml:528 #, no-c-format msgid "netcfg/get_domain" msgstr "" #. Tag: entry -#: preseed.xml:528 +#: preseed.xml:529 #, no-c-format msgid "protocol" msgstr "" #. Tag: entry -#: preseed.xml:528 +#: preseed.xml:529 #, no-c-format msgid "mirror/protocol" msgstr "" #. Tag: entry -#: preseed.xml:529 +#: preseed.xml:530 #, no-c-format msgid "suite" msgstr "" #. Tag: entry -#: preseed.xml:529 +#: preseed.xml:530 #, no-c-format msgid "mirror/suite" msgstr "" #. Tag: title -#: preseed.xml:536 +#: preseed.xml:537 #, no-c-format msgid "Using a DHCP server to specify preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:537 +#: preseed.xml:538 #, no-c-format msgid "It's also possible to use DHCP to specify a preconfiguration file to download from the network. DHCP allows specifying a filename. Normally this is a file to netboot, but if it appears to be an URL then installation media that support network preseeding will download the file from the URL and use it as a preconfiguration file. Here is an example of how to set it up in the dhcpd.conf for version 3 of the ISC DHCP server (the dhcp3-server &debian; package)." msgstr "" #. Tag: screen -#: preseed.xml:548 +#: preseed.xml:549 #, no-c-format msgid "" "if substring (option vendor-class-identifier, 0, 3) = \"d-i\" {\n" @@ -586,85 +586,85 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:550 +#: preseed.xml:551 #, no-c-format msgid "Note that the above example limits this filename to DHCP clients that identify themselves as \"d-i\", so it will not affect regular DHCP clients, but only the installer. You can also put the text in a stanza for only one particular host to avoid preseeding all installs on your network." msgstr "" #. Tag: para -#: preseed.xml:557 +#: preseed.xml:558 #, no-c-format msgid "A good way to use the DHCP preseeding is to only preseed values specific to your network, such as the &debian; mirror to use. This way installs on your network will automatically get a good mirror selected, but the rest of the installation can be performed interactively. Using DHCP preseeding to fully automate &debian; installs should only be done with care." msgstr "" #. Tag: title -#: preseed.xml:571 +#: preseed.xml:572 #, no-c-format msgid "Creating a preconfiguration file" msgstr "" #. Tag: para -#: preseed.xml:572 +#: preseed.xml:573 #, no-c-format msgid "The preconfiguration file is in the format used by the debconf-set-selections command. The general format of a line in a preconfiguration file is:" msgstr "" #. Tag: screen -#: preseed.xml:578 +#: preseed.xml:579 #, no-c-format msgid "<owner> <question name> <question type> <value>" msgstr "" #. Tag: para -#: preseed.xml:580 +#: preseed.xml:581 #, no-c-format msgid "There are a few rules to keep in mind when writing a preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:587 +#: preseed.xml:588 #, no-c-format msgid "Put only a single space or tab between type and value: any additional whitespace will be interpreted as belonging to the value." msgstr "" #. Tag: para -#: preseed.xml:591 +#: preseed.xml:592 #, no-c-format msgid "A line can be split into multiple lines by appending a backslash (\\) as the line continuation character. A good place to split a line is after the question name; a bad place is between type and value. Split lines will be joined into a single line with all leading/trailing whitespace condensed to a single space." msgstr "" #. Tag: para -#: preseed.xml:598 +#: preseed.xml:599 #, no-c-format msgid "For debconf variables (templates) used in the installer itself, the owner should be set to d-i; to preseed variables used in the installed system, the name of the package that contains the corresponding debconf template should be used. Only variables that have their owner set to something other than d-i will be propagated to the debconf database for the installed system." msgstr "" #. Tag: para -#: preseed.xml:606 +#: preseed.xml:607 #, no-c-format msgid "Most questions need to be preseeded using the values valid in English and not the translated values. However, there are some questions (for example in partman) where the translated values need to be used." msgstr "" #. Tag: para -#: preseed.xml:612 +#: preseed.xml:613 #, no-c-format msgid "Some questions take a code as value instead of the English text that is shown during installation." msgstr "" #. Tag: para -#: preseed.xml:618 +#: preseed.xml:619 #, no-c-format msgid "The easiest way to create a preconfiguration file is to use the example file linked in as basis and work from there." msgstr "" #. Tag: para -#: preseed.xml:623 +#: preseed.xml:624 #, no-c-format msgid "An alternative method is to do a manual installation and then, after rebooting, use the debconf-get-selections from the debconf-utils package to dump both the debconf database and the installer's cdebconf database to a single file:" msgstr "" #. Tag: screen -#: preseed.xml:630 +#: preseed.xml:631 #, no-c-format msgid "" "$ debconf-get-selections --installer > file\n" @@ -672,79 +672,79 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:632 +#: preseed.xml:633 #, no-c-format msgid "However, a file generated in this manner will have some items that should not be preseeded, and the example file is a better starting place for most users." msgstr "" #. Tag: para -#: preseed.xml:640 +#: preseed.xml:641 #, no-c-format msgid "This method relies on the fact that, at the end of the installation, the installer's cdebconf database is saved to the installed system in /var/log/installer/cdebconf. However, because the database may contain sensitive information, by default the files are only readable by root." msgstr "" #. Tag: para -#: preseed.xml:648 +#: preseed.xml:649 #, no-c-format msgid "The directory /var/log/installer and all files in it will be deleted from your system if you purge the package installation-report." msgstr "" #. Tag: para -#: preseed.xml:656 +#: preseed.xml:657 #, no-c-format msgid "To check possible values for questions, you can use nano to examine the files in /var/lib/cdebconf while an installation is in progress. View templates.dat for the raw templates and questions.dat for the current values and for the values assigned to variables." msgstr "" #. Tag: para -#: preseed.xml:664 +#: preseed.xml:665 #, no-c-format msgid "To check if the format of your preconfiguration file is valid before performing an install, you can use the command debconf-set-selections -c preseed.cfg." msgstr "" #. Tag: title -#: preseed.xml:675 +#: preseed.xml:676 #, no-c-format msgid "Contents of the preconfiguration file (for &releasename;)" msgstr "" #. Tag: para -#: preseed.xml:681 +#: preseed.xml:682 #, no-c-format msgid "Note that this example is based on an installation for the Intel x86 architecture. If you are installing a different architecture, some of the examples (like keyboard selection and bootloader installation) may not be relevant and will need to be replaced by debconf settings appropriate for your architecture." msgstr "" #. Tag: para -#: preseed.xml:689 +#: preseed.xml:690 #, no-c-format msgid "Details on how the different Debian Installer components actually work can be found in ." msgstr "" #. Tag: title -#: preseed.xml:697 +#: preseed.xml:698 #, no-c-format msgid "Localization" msgstr "" #. Tag: para -#: preseed.xml:698 +#: preseed.xml:699 #, no-c-format msgid "Setting localization values will only work if you are using initrd preseeding. With all other methods the preconfiguration file will only be loaded after these questions have been asked." msgstr "" #. Tag: para -#: preseed.xml:704 +#: preseed.xml:705 #, no-c-format msgid "The locale can be used to specify both language and country and can be any combination of a language supported by &d-i; and a recognized country. If the combination does not form a valid locale, the installer will automatically select a locale that is valid for the selected language. To specify the locale as a boot parameter, use locale=en_US." msgstr "" #. Tag: para -#: preseed.xml:713 +#: preseed.xml:714 #, no-c-format msgid "Although this method is very easy to use, it does not allow preseeding of all possible combinations of language, country and locale Preseeding locale to en_NL would for example result in en_US.UTF-8 as default locale for the installed system. If e.g. en_GB.UTF-8 is preferred instead, the values will need to be preseeded individually. . So alternatively the values can be preseeded individually. Language and country can also be specified as boot parameters." msgstr "" #. Tag: screen -#: preseed.xml:728 +#: preseed.xml:729 #, no-c-format msgid "" "# Preseeding only locale sets language, country and locale.\n" @@ -755,76 +755,78 @@ msgid "" "#d-i debian-installer/country string NL\n" "#d-i debian-installer/locale string en_GB.UTF-8\n" "# Optionally specify additional locales to be generated.\n" - "#d-i localechooser/supported-locales en_US.UTF-8, nl_NL.UTF-8" + "#d-i localechooser/supported-locales multiselect en_US.UTF-8, nl_NL.UTF-8" msgstr "" #. Tag: para -#: preseed.xml:730 +#: preseed.xml:731 #, no-c-format msgid "Keyboard configuration consists of selecting a keyboard architecture and a keymap. In most cases the correct keyboard architecture is selected by default, so there's normally no need to preseed it. The keymap must be known to the &d-i; for the selected keyboard architecture." msgstr "" #. Tag: screen -#: preseed.xml:737 +#: preseed.xml:738 #, no-c-format msgid "" "# Keyboard selection.\n" "#d-i console-tools/archs select at\n" - "d-i console-keymaps-at/keymap select us\n" + "# keymap is an alias for console-keymaps-at\n" + "d-i keymap select us\n" + "d-i keyboard-configuration/xkb-keymap select us\n" "# Example for a different keyboard architecture\n" "#d-i console-keymaps-usb/keymap select mac-usb-us" msgstr "" #. Tag: para -#: preseed.xml:739 +#: preseed.xml:740 #, no-c-format msgid "To skip keyboard configuration, preseed console-tools/archs with skip-config. This will result in the kernel keymap remaining active." msgstr "" #. Tag: para -#: preseed.xml:748 +#: preseed.xml:749 #, no-c-format msgid "The changes in the input layer for 2.6 kernels have made the keyboard architecture virtually obsolete. For 2.6 kernels normally a PC (at) keymap should be selected." msgstr "" #. Tag: title -#: preseed.xml:758 +#: preseed.xml:759 #, no-c-format msgid "Network configuration" msgstr "" #. Tag: para -#: preseed.xml:759 +#: preseed.xml:760 #, no-c-format msgid "Of course, preseeding the network configuration won't work if you're loading your preconfiguration file from the network. But it's great when you're booting from CD or USB stick. If you are loading preconfiguration files from the network, you can pass network config parameters by using kernel boot parameters." msgstr "" #. Tag: para -#: preseed.xml:767 +#: preseed.xml:768 #, no-c-format msgid "If you need to pick a particular interface when netbooting before loading a preconfiguration file from the network, use a boot parameter such as interface=eth1." msgstr "" #. Tag: para -#: preseed.xml:773 +#: preseed.xml:774 #, no-c-format msgid "Although preseeding the network configuration is normally not possible when using network preseeding (using preseed/url), you can use the following hack to work around that, for example if you'd like to set a static address for the network interface. The hack is to force the network configuration to run again after the preconfiguration file has been loaded by creating a preseed/run script containing the following commands:" msgstr "" #. Tag: screen -#: preseed.xml:783 +#: preseed.xml:784 #, no-c-format msgid "killall.sh; netcfg" msgstr "" #. Tag: para -#: preseed.xml:785 +#: preseed.xml:786 #, no-c-format msgid "The following debconf variables are relevant for network configuration." msgstr "" #. Tag: screen -#: preseed.xml:791 +#: preseed.xml:792 #, no-c-format msgid "" "# Disable network configuration entirely. This is useful for cdrom\n" @@ -878,19 +880,19 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:793 +#: preseed.xml:794 #, no-c-format msgid "Please note that netcfg will automatically determine the netmask if netcfg/get_netmask is not preseeded. In this case, the variable has to be marked as seen for automatic installations. Similarly, netcfg will choose an appropriate address if netcfg/get_gateway is not set. As a special case, you can set netcfg/get_gateway to none to specify that no gateway should be used." msgstr "" #. Tag: title -#: preseed.xml:809 +#: preseed.xml:810 #, no-c-format msgid "Network console" msgstr "" #. Tag: screen -#: preseed.xml:811 +#: preseed.xml:812 #, no-c-format msgid "" "# Use the following settings if you wish to make use of the network-console\n" @@ -902,31 +904,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:816 +#: preseed.xml:817 #, no-c-format msgid "Mirror settings" msgstr "" #. Tag: para -#: preseed.xml:817 +#: preseed.xml:818 #, no-c-format msgid "Depending on the installation method you use, a mirror may be used to download additional components of the installer, to install the base system, and to set up the /etc/apt/sources.list for the installed system." msgstr "" #. Tag: para -#: preseed.xml:824 +#: preseed.xml:825 #, no-c-format msgid "The parameter mirror/suite determines the suite for the installed system." msgstr "" #. Tag: para -#: preseed.xml:829 +#: preseed.xml:830 #, no-c-format msgid "The parameter mirror/udeb/suite determines the suite for additional components for the installer. It is only useful to set this if components are actually downloaded over the network and should match the suite that was used to build the initrd for the installation method used for the installation. Normally the installer will automatically use the correct value and there should be no need to set this." msgstr "" #. Tag: screen -#: preseed.xml:840 +#: preseed.xml:841 #, no-c-format msgid "" "# If you select ftp, the mirror/country string does not need to be set.\n" @@ -943,25 +945,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:845 +#: preseed.xml:846 #, no-c-format msgid "Account setup" msgstr "" #. Tag: para -#: preseed.xml:846 +#: preseed.xml:847 #, no-c-format msgid "The password for the root account and name and password for a first regular user's account can be preseeded. For the passwords you can use either clear text values or MD5 hashes." msgstr "" #. Tag: para -#: preseed.xml:853 +#: preseed.xml:854 #, no-c-format msgid "Be aware that preseeding passwords is not completely secure as everyone with access to the preconfiguration file will have the knowledge of these passwords. Using MD5 hashes is considered slightly better in terms of security but it might also give a false sense of security as access to a MD5 hash allows for brute force attacks." msgstr "" #. Tag: screen -#: preseed.xml:863 +#: preseed.xml:864 #, no-c-format msgid "" "# Skip creation of a root account (normal user account will be able to\n" @@ -993,31 +995,31 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:865 +#: preseed.xml:866 #, no-c-format msgid "The passwd/root-password-crypted and passwd/user-password-crypted variables can also be preseeded with ! as their value. In that case, the corresponding account is disabled. This may be convenient for the root account, provided of course that an alternative method is set up to allow administrative activities or root login (for instance by using SSH key authentication or sudo)." msgstr "" #. Tag: para -#: preseed.xml:875 +#: preseed.xml:876 #, no-c-format msgid "The following command can be used to generate an MD5 hash for a password:" msgstr "" #. Tag: screen -#: preseed.xml:879 +#: preseed.xml:880 #, no-c-format msgid "$ printf \"r00tme\" | mkpasswd -s -m md5" msgstr "" #. Tag: title -#: preseed.xml:885 +#: preseed.xml:886 #, no-c-format msgid "Clock and time zone setup" msgstr "" #. Tag: screen -#: preseed.xml:887 +#: preseed.xml:888 #, no-c-format msgid "" "# Controls whether or not the hardware clock is set to UTC.\n" @@ -1034,43 +1036,43 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:892 +#: preseed.xml:893 #, no-c-format msgid "Partitioning" msgstr "" #. Tag: para -#: preseed.xml:893 +#: preseed.xml:894 #, no-c-format msgid "Using preseeding to partition the harddisk is limited to what is supported by partman-auto. You can choose to partition either existing free space on a disk or a whole disk. The layout of the disk can be determined by using a predefined recipe, a custom recipe from a recipe file or a recipe included in the preconfiguration file." msgstr "" #. Tag: para -#: preseed.xml:901 +#: preseed.xml:902 #, no-c-format msgid "Preseeding of advanced partition setups using RAID, LVM and encryption is supported, but not with the full flexibility possible when partitioning during a non-preseeded install." msgstr "" #. Tag: para -#: preseed.xml:907 +#: preseed.xml:908 #, no-c-format msgid "The examples below only provide basic information on the use of recipes. For detailed information see the files partman-auto-recipe.txt and partman-auto-raid-recipe.txt included in the debian-installer package. Both files are also available from the &d-i; source repository. Note that the supported functionality may change between releases." msgstr "" #. Tag: para -#: preseed.xml:921 +#: preseed.xml:922 #, no-c-format msgid "The identification of disks is dependent on the order in which their drivers are loaded. If there are multiple disks in the system, make very sure the correct one will be selected before using preseeding." msgstr "" #. Tag: title -#: preseed.xml:930 +#: preseed.xml:931 #, no-c-format msgid "Partitioning example" msgstr "" #. Tag: screen -#: preseed.xml:932 +#: preseed.xml:933 #, no-c-format msgid "" "# If the system has free space you can choose to only partition that space.\n" @@ -1145,31 +1147,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:936 +#: preseed.xml:937 #, no-c-format msgid "Partitioning using RAID" msgstr "" #. Tag: para -#: preseed.xml:937 +#: preseed.xml:938 #, no-c-format msgid "You can also use preseeding to set up partitions on software RAID arrays. Supported are RAID levels 0, 1, 5, 6 and 10, creating degraded arrays and specifying spare devices." msgstr "" #. Tag: para -#: preseed.xml:943 +#: preseed.xml:944 #, no-c-format msgid "If you are using RAID 1, you can preseed grub to install to all devices used in the array; see ." msgstr "" #. Tag: para -#: preseed.xml:950 +#: preseed.xml:951 #, no-c-format msgid "This type of automated partitioning is easy to get wrong. It is also functionality that receives relatively little testing from the developers of &d-i;. The responsibility to get the various recipes right (so they make sense and don't conflict) lies with the user. Check /var/log/syslog if you run into problems." msgstr "" #. Tag: screen -#: preseed.xml:960 +#: preseed.xml:961 #, no-c-format msgid "" "# The method should be set to \"raid\".\n" @@ -1223,31 +1225,31 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:965 +#: preseed.xml:966 #, no-c-format msgid "Controlling how partitions are mounted" msgstr "" #. Tag: para -#: preseed.xml:966 +#: preseed.xml:967 #, no-c-format msgid "Normally, filesystems are mounted using a universally unique identifier (UUID) as a key; this allows them to be mounted properly even if their device name changes. UUIDs are long and difficult to read, so, if you prefer, the installer can mount filesystems based on the traditional device names, or based on a label you assign. If you ask the installer to mount by label, any filesystems without a label will be mounted using a UUID instead." msgstr "" #. Tag: para -#: preseed.xml:975 +#: preseed.xml:976 #, no-c-format msgid "Devices with stable names, such as LVM logical volumes, will continue to use their traditional names rather than UUIDs." msgstr "" #. Tag: para -#: preseed.xml:982 +#: preseed.xml:983 #, no-c-format msgid "Traditional device names may change based on the order in which the kernel discovers devices at boot, which may cause the wrong filesystem to be mounted. Similarly, labels are likely to clash if you plug in a new disk or a USB drive, and if that happens your system's behaviour when started will be random." msgstr "" #. Tag: screen -#: preseed.xml:992 +#: preseed.xml:993 #, no-c-format msgid "" "# The default is to mount by UUID, but you can also choose \"traditional\" to\n" @@ -1257,19 +1259,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:998 +#: preseed.xml:999 #, no-c-format msgid "Base system installation" msgstr "" #. Tag: para -#: preseed.xml:999 +#: preseed.xml:1000 #, no-c-format msgid "There is actually not very much that can be preseeded for this stage of the installation. The only questions asked concern the installation of the kernel." msgstr "" #. Tag: screen -#: preseed.xml:1006 +#: preseed.xml:1007 #, no-c-format msgid "" "# Configure APT to not install recommended packages by default. Use of this\n" @@ -1286,19 +1288,19 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1011 +#: preseed.xml:1012 #, no-c-format msgid "Apt setup" msgstr "" #. Tag: para -#: preseed.xml:1012 +#: preseed.xml:1013 #, no-c-format msgid "Setup of the /etc/apt/sources.list and basic configuration options is fully automated based on your installation method and answers to earlier questions. You can optionally add other (local) repositories." msgstr "" #. Tag: screen -#: preseed.xml:1020 +#: preseed.xml:1021 #, no-c-format msgid "" "# You can choose to install non-free and contrib software.\n" @@ -1330,97 +1332,97 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1025 +#: preseed.xml:1026 #, no-c-format msgid "Package selection" msgstr "" #. Tag: para -#: preseed.xml:1026 +#: preseed.xml:1027 #, no-c-format msgid "You can choose to install any combination of tasks that are available. Available tasks as of this writing include:" msgstr "" #. Tag: userinput -#: preseed.xml:1035 +#: preseed.xml:1036 #, no-c-format msgid "standard" msgstr "" #. Tag: userinput -#: preseed.xml:1038 +#: preseed.xml:1039 #, no-c-format msgid "desktop" msgstr "" #. Tag: userinput -#: preseed.xml:1041 +#: preseed.xml:1042 #, no-c-format msgid "gnome-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:1044 +#: preseed.xml:1045 #, no-c-format msgid "kde-desktop" msgstr "" #. Tag: userinput -#: preseed.xml:1047 +#: preseed.xml:1048 #, no-c-format msgid "web-server" msgstr "" #. Tag: userinput -#: preseed.xml:1050 +#: preseed.xml:1051 #, no-c-format msgid "print-server" msgstr "" #. Tag: userinput -#: preseed.xml:1053 +#: preseed.xml:1054 #, no-c-format msgid "dns-server" msgstr "" #. Tag: userinput -#: preseed.xml:1056 +#: preseed.xml:1057 #, no-c-format msgid "file-server" msgstr "" #. Tag: userinput -#: preseed.xml:1059 +#: preseed.xml:1060 #, no-c-format msgid "mail-server" msgstr "" #. Tag: userinput -#: preseed.xml:1062 +#: preseed.xml:1063 #, no-c-format msgid "sql-database" msgstr "" #. Tag: userinput -#: preseed.xml:1065 +#: preseed.xml:1066 #, no-c-format msgid "laptop" msgstr "" #. Tag: para -#: preseed.xml:1069 +#: preseed.xml:1070 #, no-c-format msgid "You can also choose to install no tasks, and force the installation of a set of packages in some other way. We recommend always including the standard task." msgstr "" #. Tag: para -#: preseed.xml:1075 +#: preseed.xml:1076 #, no-c-format msgid "If you want to install some individual packages in addition to packages installed by tasks, you can use the parameter pkgsel/include. The value of this parameter can be a list of packages separated by either commas or spaces, which allows it to be used easily on the kernel command line as well." msgstr "" #. Tag: screen -#: preseed.xml:1085 +#: preseed.xml:1086 #, no-c-format msgid "" "#tasksel tasksel/first multiselect standard, web-server\n" @@ -1442,13 +1444,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1090 +#: preseed.xml:1091 #, no-c-format msgid "Boot loader installation" msgstr "" #. Tag: screen -#: preseed.xml:1092 +#: preseed.xml:1093 #, no-c-format msgid "" "# Grub is the default boot loader (for x86). If you want lilo installed\n" @@ -1460,11 +1462,6 @@ msgid "" "# To install no bootloader, uncomment this\n" "#d-i grub-installer/skip boolean true\n" "\n" - "# With a few exceptions for unusual partitioning setups, GRUB 2 is now the\n" - "# default. If you need GRUB Legacy for some particular reason, then\n" - "# uncomment this:\n" - "#d-i grub-installer/grub2_instead_of_grub_legacy boolean false\n" - "\n" "# This is fairly safe to set, it makes grub install automatically to the MBR\n" "# if no other operating system is detected on the machine.\n" "d-i grub-installer/only_debian boolean true\n" @@ -1496,19 +1493,19 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1094 +#: preseed.xml:1095 #, no-c-format msgid "An MD5 hash for a password for grub can be generated using grub-md5-crypt, or using the command from the example in ." msgstr "" #. Tag: title -#: preseed.xml:1104 +#: preseed.xml:1105 #, no-c-format msgid "Finishing up the installation" msgstr "" #. Tag: screen -#: preseed.xml:1106 +#: preseed.xml:1107 #, no-c-format msgid "" "# During installations from serial console, the regular virtual consoles\n" @@ -1531,13 +1528,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1111 +#: preseed.xml:1112 #, no-c-format msgid "Preseeding other packages" msgstr "" #. Tag: screen -#: preseed.xml:1113 +#: preseed.xml:1114 #, no-c-format msgid "" "# Depending on what software you choose to install, or if things go wrong\n" @@ -1550,25 +1547,25 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1120 +#: preseed.xml:1121 #, no-c-format msgid "Advanced options" msgstr "" #. Tag: title -#: preseed.xml:1123 +#: preseed.xml:1124 #, no-c-format msgid "Running custom commands during the installation" msgstr "" #. Tag: para -#: preseed.xml:1124 +#: preseed.xml:1125 #, no-c-format msgid "A very powerful and flexible option offered by the preconfiguration tools is the ability to run commands or scripts at certain points in the installation." msgstr "" #. Tag: screen -#: preseed.xml:1132 +#: preseed.xml:1133 #, no-c-format msgid "" "# d-i preseeding is inherently not secure. Nothing in the installer checks\n" @@ -1594,13 +1591,13 @@ msgid "" msgstr "" #. Tag: title -#: preseed.xml:1137 +#: preseed.xml:1138 #, no-c-format msgid "Using preseeding to change default values" msgstr "" #. Tag: para -#: preseed.xml:1138 +#: preseed.xml:1139 #, no-c-format msgid "" "It is possible to use preseeding to change the default answer for a question, but still have the question asked. To do this the seen flag must be reset to false after setting the value for a question. \n" @@ -1610,31 +1607,31 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1152 +#: preseed.xml:1153 #, no-c-format msgid "Note that the d-i owner should only be used for variables used in the installer itself. For variables belonging to packages installed on the target system, you should use the name of that package instead. See the footnote to ." msgstr "" #. Tag: para -#: preseed.xml:1159 +#: preseed.xml:1160 #, no-c-format msgid "If you are preseeding using boot parameters, you can make the installer ask the corresponding question by using the ?= operator, i.e. foo/bar?=value (or owner:foo/bar?=value). This will of course only have effect for parameters that correspond to questions that are actually displayed during an installation and not for internal parameters." msgstr "" #. Tag: title -#: preseed.xml:1173 +#: preseed.xml:1174 #, no-c-format msgid "Chainloading preconfiguration files" msgstr "" #. Tag: para -#: preseed.xml:1174 +#: preseed.xml:1175 #, no-c-format msgid "It is possible to include other preconfiguration files from a preconfiguration file. Any settings in those files will override pre-existing settings from files loaded earlier. This makes it possible to put, for example, general networking settings for your location in one file and more specific settings for certain configurations in other files." msgstr "" #. Tag: screen -#: preseed.xml:1184 +#: preseed.xml:1185 #, no-c-format msgid "" "# More than one file can be listed, separated by spaces; all will be\n" @@ -1662,7 +1659,7 @@ msgid "" msgstr "" #. Tag: para -#: preseed.xml:1186 +#: preseed.xml:1187 #, no-c-format msgid "It is also possible to chainload from the initrd or file preseeding phase, into network preseeding by setting preseed/url in the earlier files. This will cause network preseeding to be performed when the network comes up. You need to be careful when doing this, since there will be two distinct runs at preseeding, meaning for example that you get another chance to run the preseed/early command, the second one happening after the network comes up." msgstr "" diff --git a/po/pot/using-d-i.pot b/po/pot/using-d-i.pot index ee9062a1b..05ca6da97 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: 2011-01-08 16:52+0000\n" +"POT-Creation-Date: 2011-05-15 00:54+0000\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" @@ -669,151 +669,151 @@ msgid "Some technical details you might, or might not, find handy: the program a msgstr "" #. Tag: title -#: using-d-i.xml:812 +#: using-d-i.xml:813 #, no-c-format msgid "Configuring the Clock and Time Zone" msgstr "" #. Tag: para -#: using-d-i.xml:814 +#: using-d-i.xml:815 #, no-c-format msgid "The installer will first attempt to connect to a time server on the Internet (using the NTP protocol) in order to correctly set the system time. If this does not succeed, the installer will assume the time and date obtained from the system clock when the installation system was booted are correct. It is not possible to manually set the system time during the installation process." msgstr "" #. Tag: para -#: using-d-i.xml:823 +#: using-d-i.xml:824 #, no-c-format msgid "The installer does not modify the system clock on the s390 platform." msgstr "" #. Tag: para -#: using-d-i.xml:836 +#: using-d-i.xml:837 #, no-c-format msgid "Depending on the location selected earlier in the installation process, you may be shown a list of time zones relevant for that location. If your location has only one time zone and you are doing a default installation, you will not be asked anything and the system will assume that time zone." msgstr "" #. Tag: para -#: using-d-i.xml:844 +#: using-d-i.xml:845 #, no-c-format msgid "In expert mode or when installing at medium priority, you will have the additional option to select Coordinated Universal Time (UTC) as time zone." msgstr "" #. Tag: para -#: using-d-i.xml:850 +#: using-d-i.xml:851 #, no-c-format msgid "If for some reason you wish to set a time zone for the installed system that does not match the selected location, there are two options." msgstr "" #. Tag: para -#: using-d-i.xml:861 +#: using-d-i.xml:862 #, no-c-format msgid "The simplest option is to just select a different time zone after the installation has been completed and you've booted into the new system. The command to do this is:" msgstr "" #. Tag: screen -#: using-d-i.xml:867 +#: using-d-i.xml:868 #, no-c-format msgid "# dpkg-reconfigure tzdata" msgstr "" #. Tag: para -#: using-d-i.xml:873 +#: using-d-i.xml:874 #, no-c-format msgid "Alternatively, the time zone can be set at the very start of the installation by passing the parameter time/zone=value when you boot the installation system. The value should of course be a valid time zone, for example Europe/London or UTC." msgstr "" #. Tag: para -#: using-d-i.xml:887 +#: using-d-i.xml:888 #, no-c-format msgid "For automated installations the time zone can be set to any desired value using preseeding." msgstr "" #. Tag: title -#: using-d-i.xml:901 +#: using-d-i.xml:902 #, no-c-format msgid "Setting Up Users And Passwords" msgstr "" #. Tag: para -#: using-d-i.xml:902 +#: using-d-i.xml:903 #, no-c-format msgid "Just before configuring the clock, the installer will allow you to set up the root account and/or an account for the first user. Other user accounts can be created after the installation has been completed." msgstr "" #. Tag: title -#: using-d-i.xml:916 +#: using-d-i.xml:917 #, no-c-format msgid "Set the Root Password" msgstr "" #. Tag: para -#: using-d-i.xml:920 +#: using-d-i.xml:921 #, no-c-format msgid "The root account is also called the super-user; it is a login that bypasses all security protection on your system. The root account should only be used to perform system administration, and only used for as short a time as possible." msgstr "" #. Tag: para -#: using-d-i.xml:928 +#: using-d-i.xml:929 #, no-c-format msgid "Any password you create should contain at least 6 characters, and should contain both upper- and lower-case characters, as well as punctuation characters. Take extra care when setting your root password, since it is such a powerful account. Avoid dictionary words or use of any personal information which could be guessed." msgstr "" #. Tag: para -#: using-d-i.xml:936 +#: using-d-i.xml:937 #, no-c-format msgid "If anyone ever tells you they need your root password, be extremely wary. You should normally never give your root password out, unless you are administering a machine with more than one system administrator." msgstr "" #. Tag: title -#: using-d-i.xml:946 +#: using-d-i.xml:947 #, no-c-format msgid "Create an Ordinary User" msgstr "" #. Tag: para -#: using-d-i.xml:948 +#: using-d-i.xml:949 #, no-c-format msgid "The system will ask you whether you wish to create an ordinary user account at this point. This account should be your main personal log-in. You should not use the root account for daily use or as your personal login." msgstr "" #. Tag: para -#: using-d-i.xml:957 +#: using-d-i.xml:958 #, no-c-format msgid "Why not? Well, one reason to avoid using root's privileges is that it is very easy to do irreparable damage as root. Another reason is that you might be tricked into running a Trojan-horse program — that is a program that takes advantage of your super-user powers to compromise the security of your system behind your back. Any good book on Unix system administration will cover this topic in more detail — consider reading one if it is new to you." msgstr "" #. Tag: para -#: using-d-i.xml:967 +#: using-d-i.xml:968 #, no-c-format msgid "You will first be prompted for the user's full name. Then you'll be asked for a name for the user account; generally your first name or something similar will suffice and indeed will be the default. Finally, you will be prompted for a password for this account." msgstr "" #. Tag: para -#: using-d-i.xml:974 +#: using-d-i.xml:975 #, no-c-format msgid "If at any point after installation you would like to create another account, use the adduser command." msgstr "" #. Tag: title -#: using-d-i.xml:985 +#: using-d-i.xml:986 #, no-c-format msgid "Partitioning and Mount Point Selection" msgstr "" #. Tag: para -#: using-d-i.xml:986 +#: using-d-i.xml:987 #, no-c-format msgid "At this time, after hardware detection has been executed a final time, &d-i; should be at its full strength, customized for the user's needs and ready to do some real work. As the title of this section indicates, the main task of the next few components lies in partitioning your disks, creating filesystems, assigning mountpoints and optionally configuring closely related options like RAID, LVM or encrypted devices." msgstr "" #. Tag: para -#: using-d-i.xml:1007 +#: using-d-i.xml:1008 #, no-c-format msgid "If you are uncomfortable with partitioning, or just want to know more details, see ." msgstr "" #. Tag: para -#: using-d-i.xml:1013 +#: using-d-i.xml:1014 #, no-c-format msgid "" "If a hard disk has previously used under Solaris, the partitioner may not detect the size of the drive correctly. Creating a new partition table does not fix this issue. What does help, is to zero the first few sectors of the drive: \n" @@ -822,355 +822,355 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1026 +#: using-d-i.xml:1027 #, no-c-format msgid "First you will be given the opportunity to automatically partition either an entire drive, or available free space on a drive. This is also called guided partitioning. If you do not want to autopartition, choose Manual from the menu." msgstr "" #. Tag: title -#: using-d-i.xml:1036 +#: using-d-i.xml:1037 #, no-c-format msgid "Supported partitioning options" msgstr "" #. Tag: para -#: using-d-i.xml:1037 +#: using-d-i.xml:1038 #, no-c-format msgid "The partitioner used in &d-i; is fairly versatile. It allows to create many different partitioning schemes, using various partition tables, file systems and advanced block devices." msgstr "" #. Tag: para -#: using-d-i.xml:1043 +#: using-d-i.xml:1044 #, no-c-format msgid "Exactly which options are available depends mainly on the architecture, but also on other factors. For example, on systems with limited internal memory some options may not be available. Defaults may vary as well. The type of partition table used by default can for example be different for large capacity hard disks than for smaller hard disks. Some options can only be changed when installing at medium or low debconf priority; at higher priorities sensible defaults will be used." msgstr "" #. Tag: para -#: using-d-i.xml:1054 +#: using-d-i.xml:1055 #, no-c-format msgid "The installer supports various forms of advanced partitioning and use of storage devices, which in many cases can be used in combination." msgstr "" #. Tag: emphasis -#: using-d-i.xml:1061 +#: using-d-i.xml:1062 #, no-c-format msgid "Logical Volume Management (LVM)" msgstr "" #. Tag: emphasis -#: using-d-i.xml:1064 +#: using-d-i.xml:1065 #, no-c-format msgid "Software RAID" msgstr "" #. Tag: para -#: using-d-i.xml:1065 +#: using-d-i.xml:1066 #, no-c-format msgid "Supported are RAID levels 0, 1, 4, 5, 6 and 10." msgstr "" #. Tag: emphasis -#: using-d-i.xml:1069 +#: using-d-i.xml:1070 #, no-c-format msgid "Encryption" msgstr "" #. Tag: para -#: using-d-i.xml:1071 +#: using-d-i.xml:1072 #, no-c-format msgid "Serial ATA RAID (using dmraid)" msgstr "" #. Tag: para -#: using-d-i.xml:1073 +#: using-d-i.xml:1074 #, no-c-format msgid "Also called fake RAID or BIOS RAID. Support for Serial ATA RAID is currently only available if enabled when the installer is booted. Further information is available on our Wiki." msgstr "" #. Tag: para -#: using-d-i.xml:1079 +#: using-d-i.xml:1080 #, no-c-format msgid "Multipath (experimental)" msgstr "" #. Tag: para -#: using-d-i.xml:1081 +#: using-d-i.xml:1082 #, no-c-format msgid "See our Wiki for information. Support for multipath is currently only available if enabled when the installer is booted." msgstr "" #. Tag: para -#: using-d-i.xml:1088 +#: using-d-i.xml:1089 #, no-c-format msgid "The following file systems are supported." msgstr "" #. Tag: para -#: using-d-i.xml:1093 +#: using-d-i.xml:1094 #, no-c-format msgid "ext2r0, ext2, ext3, ext4" msgstr "" #. Tag: para -#: using-d-i.xml:1098 +#: using-d-i.xml:1099 #, no-c-format msgid "The default file system selected in most cases is ext3; for /boot partitions ext2 will be selected by default when guided partitioning is used." msgstr "" #. Tag: para -#: using-d-i.xml:1103 +#: using-d-i.xml:1104 #, no-c-format msgid "jfs (not available on all architectures)" msgstr "" #. Tag: emphasis -#: using-d-i.xml:1107 +#: using-d-i.xml:1108 #, no-c-format msgid "ufs" msgstr "" #. Tag: para -#: using-d-i.xml:1108 +#: using-d-i.xml:1109 #, no-c-format msgid "The default file system is UFS." msgstr "" #. Tag: para -#: using-d-i.xml:1111 +#: using-d-i.xml:1112 #, no-c-format msgid "xfs (not available on all architectures)" msgstr "" #. Tag: emphasis -#: using-d-i.xml:1115 +#: using-d-i.xml:1116 #, no-c-format msgid "zfs" msgstr "" #. Tag: para -#: using-d-i.xml:1116 +#: using-d-i.xml:1117 #, no-c-format msgid "As ZFS support in the installer is still in development, only a basic subset of ZFS features are supported. Some of them can be enabled manually after the initial install, but there are some caveats:" msgstr "" #. Tag: para -#: using-d-i.xml:1121 +#: using-d-i.xml:1122 #, no-c-format msgid "Each ZFS pool will host only one filesystem. After install is finished, more filesystems can be created on this pool by using the zfs create command." msgstr "" #. Tag: para -#: using-d-i.xml:1126 +#: using-d-i.xml:1127 #, no-c-format msgid "Each ZFS pool will be composed of exactly one partition. After install is finished, a single-device ZFS pool can be converted into a multi-device pool by using the zpool add command, or into a mirrored pool by using the zpool attach command. However, you shouldn't do this on the pool that hosts root filesystem, as it would prevent GRUB from booting your system." msgstr "" #. Tag: para -#: using-d-i.xml:1134 +#: using-d-i.xml:1135 #, no-c-format msgid "Compression is not currently supported. After the install is finished, compression can be enabled by setting the compression property via the zfs set command. However, if a compression algorithm other than the default (lzjb) is used on the pool that hosts your root filesystem, this may prevent GRUB from booting your system." msgstr "" #. Tag: para -#: using-d-i.xml:1143 +#: using-d-i.xml:1144 #, no-c-format msgid "reiserfs (optional; not available on all architectures)" msgstr "" #. Tag: para -#: using-d-i.xml:1145 +#: using-d-i.xml:1146 #, no-c-format msgid "Support for the Reiser file system is no longer available by default. When the installer is running at medium or low debconf priority it can be enabled by selecting the partman-reiserfs component. Only version 3 of the file system is supported." msgstr "" #. Tag: emphasis -#: using-d-i.xml:1152 +#: using-d-i.xml:1153 #, no-c-format msgid "jffs2" msgstr "" #. Tag: para -#: using-d-i.xml:1153 +#: using-d-i.xml:1154 #, no-c-format msgid "Used on some systems to read flash memory. It is not possible to create new jffs2 partitions." msgstr "" #. Tag: emphasis -#: using-d-i.xml:1158 +#: using-d-i.xml:1159 #, no-c-format msgid "qnx4" msgstr "" #. Tag: para -#: using-d-i.xml:1159 +#: using-d-i.xml:1160 #, no-c-format msgid "Existing partitions will be recognized and it is possible to assign mount points for them. It is not possible to create new qnx4 partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1163 +#: using-d-i.xml:1164 #, no-c-format msgid "FAT16, FAT32" msgstr "" #. Tag: para -#: using-d-i.xml:1166 +#: using-d-i.xml:1167 #, no-c-format msgid "NTFS (read-only)" msgstr "" #. Tag: para -#: using-d-i.xml:1168 +#: using-d-i.xml:1169 #, no-c-format msgid "Existing NTFS partitions can be resized and it is possible to assign mount points for them. It is not possible to create new NTFS partitions." msgstr "" #. Tag: title -#: using-d-i.xml:1178 +#: using-d-i.xml:1179 #, no-c-format msgid "Guided Partitioning" msgstr "" #. Tag: para -#: using-d-i.xml:1179 +#: using-d-i.xml:1180 #, no-c-format msgid "If you choose guided partitioning, you may have three options: to create partitions directly on the hard disk (classic method), or to create them using Logical Volume Management (LVM), or to create them using encrypted LVM The installer will encrypt the LVM volume group using a 256 bit AES key and makes use of the kernel's dm-crypt support. ." msgstr "" #. Tag: para -#: using-d-i.xml:1194 +#: using-d-i.xml:1195 #, no-c-format msgid "The option to use (encrypted) LVM may not be available on all architectures." msgstr "" #. Tag: para -#: using-d-i.xml:1199 +#: using-d-i.xml:1200 #, no-c-format msgid "When using LVM or encrypted LVM, the installer will create most partitions inside one big partition; the advantage of this method is that partitions inside this big partition can be resized relatively easily later. In the case of encrypted LVM the big partition will not be readable without knowing a special key phrase, thus providing extra security of your (personal) data." msgstr "" #. Tag: para -#: using-d-i.xml:1208 +#: using-d-i.xml:1209 #, no-c-format msgid "When using encrypted LVM, the installer will also automatically erase the disk by writing random data to it. This further improves security (as it makes it impossible to tell which parts of the disk are in use and also makes sure that any traces of previous installations are erased), but may take some time depending on the size of your disk." msgstr "" #. Tag: para -#: using-d-i.xml:1217 +#: using-d-i.xml:1218 #, no-c-format msgid "If you choose guided partitioning using LVM or encrypted LVM, some changes in the partition table will need to be written to the selected disk while LVM is being set up. These changes effectively erase all data that is currently on the selected hard disk and you will not be able to undo them later. However, the installer will ask you to confirm these changes before they are written to disk." msgstr "" #. Tag: para -#: using-d-i.xml:1227 +#: using-d-i.xml:1228 #, no-c-format msgid "If you choose guided partitioning (either classic or using (encrypted) LVM) for a whole disk, you will first be asked to select the disk you want to use. Check that all your disks are listed and, if you have several disks, make sure you select the correct one. The order they are listed in may differ from what you are used to. The size of the disks may help to identify them." msgstr "" #. Tag: para -#: using-d-i.xml:1236 +#: using-d-i.xml:1237 #, no-c-format msgid "Any data on the disk you select will eventually be lost, but you will always be asked to confirm any changes before they are written to the disk. If you have selected the classic method of partitioning, you will be able to undo any changes right until the end; when using (encrypted) LVM this is not possible. " msgstr "" #. Tag: para -#: using-d-i.xml:1246 +#: using-d-i.xml:1247 #, no-c-format msgid "Next, you will be able to choose from the schemes listed in the table below. All schemes have their pros and cons, some of which are discussed in . If you are unsure, choose the first one. Bear in mind that guided partitioning needs a certain minimal amount of free space to operate with. If you don't give it at least about 1GB of space (depends on chosen scheme), guided partitioning will fail." msgstr "" #. Tag: entry -#: using-d-i.xml:1262 +#: using-d-i.xml:1263 #, no-c-format msgid "Partitioning scheme" msgstr "" #. Tag: entry -#: using-d-i.xml:1263 +#: using-d-i.xml:1264 #, no-c-format msgid "Minimum space" msgstr "" #. Tag: entry -#: using-d-i.xml:1264 +#: using-d-i.xml:1265 #, no-c-format msgid "Created partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:1270 +#: using-d-i.xml:1271 #, no-c-format msgid "All files in one partition" msgstr "" #. Tag: entry -#: using-d-i.xml:1271 +#: using-d-i.xml:1272 #, no-c-format msgid "600MB" msgstr "" #. Tag: entry -#: using-d-i.xml:1272 +#: using-d-i.xml:1273 #, no-c-format msgid "/, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:1274 +#: using-d-i.xml:1275 #, no-c-format msgid "Separate /home partition" msgstr "" #. Tag: entry -#: using-d-i.xml:1275 +#: using-d-i.xml:1276 #, no-c-format msgid "500MB" msgstr "" #. Tag: entry -#: using-d-i.xml:1276 +#: using-d-i.xml:1277 #, no-c-format msgid "/, /home, swap" msgstr "" #. Tag: entry -#: using-d-i.xml:1280 +#: using-d-i.xml:1281 #, no-c-format msgid "Separate /home, /usr, /var and /tmp partitions" msgstr "" #. Tag: entry -#: using-d-i.xml:1281 +#: using-d-i.xml:1282 #, no-c-format msgid "1GB" msgstr "" #. Tag: entry -#: using-d-i.xml:1282 +#: using-d-i.xml:1283 #, no-c-format msgid "/, /home, /usr, /var, /tmp, swap" msgstr "" #. Tag: para -#: using-d-i.xml:1291 +#: using-d-i.xml:1292 #, no-c-format msgid "If you choose guided partitioning using (encrypted) LVM, the installer will also create a separate /boot partition. The other partitions, including the swap partition, will be created inside the LVM partition." msgstr "" #. Tag: para -#: using-d-i.xml:1297 +#: using-d-i.xml:1298 #, no-c-format msgid "If you choose guided partitioning for your IA-64 system, there will be an additional partition, formatted as a FAT16 bootable filesystem, for the EFI boot loader. There is also an additional menu item in the formatting menu to manually set up a partition as an EFI boot partition." msgstr "" #. Tag: para -#: using-d-i.xml:1305 +#: using-d-i.xml:1306 #, no-c-format msgid "After selecting a scheme, the next screen will show your new partition table, including information on whether and how partitions will be formatted and where they will be mounted." msgstr "" #. Tag: para -#: using-d-i.xml:1311 +#: using-d-i.xml:1312 #, no-c-format msgid "" "The list of partitions might look like this: \n" @@ -1193,601 +1193,601 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:1324 +#: using-d-i.xml:1325 #, no-c-format msgid "This concludes the guided partitioning. If you are satisfied with the generated partition table, you can choose Finish partitioning and write changes to disk from the menu to implement the new partition table (as described at the end of this section). If you are not happy, you can choose to Undo changes to partitions and run guided partitioning again, or modify the proposed changes as described below for manual partitioning." msgstr "" #. Tag: title -#: using-d-i.xml:1338 +#: using-d-i.xml:1339 #, no-c-format msgid "Manual Partitioning" msgstr "" #. Tag: para -#: using-d-i.xml:1339 +#: using-d-i.xml:1340 #, no-c-format msgid "A similar screen to the one shown just above will be displayed if you choose manual partitioning except that your existing partition table will be shown and without the mount points. How to manually set up your partition table and the usage of partitions by your new &debian; system will be covered in the remainder of this section." msgstr "" #. Tag: para -#: using-d-i.xml:1347 +#: using-d-i.xml:1348 #, no-c-format msgid "If you select a pristine disk which has neither partitions nor free space on it, you will be asked if a new partition table should be created (this is needed so you can create new partitions). After this, a new line entitled FREE SPACE should appear in the table under the selected disk." msgstr "" #. Tag: para -#: using-d-i.xml:1355 +#: using-d-i.xml:1356 #, no-c-format msgid "If you select some free space, you will have the opportunity to create a new partition. You will have to answer a quick series of questions about its size, type (primary or logical), and location (beginning or end of the free space). After this, you will be presented with a detailed overview of your new partition. The main setting is Use as:, which determines if the partition will have a file system on it, or be used for swap, software RAID, LVM, an encrypted file system, or not be used at all. Other settings include mountpoint, mount options, and bootable flag; which settings are shown depends on how the partition is to be used. If you don't like the preselected defaults, feel free to change them to your liking. E.g. by selecting the option Use as:, you can choose a different filesystem for this partition, including options to use the partition for swap, software RAID, LVM, or not use it at all. Another nice feature is the ability to copy data from an existing partition onto this one. When you are satisfied with your new partition, select Done setting up the partition and you will return to partman's main screen." msgstr "" #. Tag: para -#: using-d-i.xml:1377 +#: using-d-i.xml:1378 #, no-c-format msgid "If you decide you want to change something about your partition, simply select the partition, which will bring you to the partition configuration menu. This is the same screen as is used when creating a new partition, so you can change the same settings. One thing that may not be very obvious at a first glance is that you can resize the partition by selecting the item displaying the size of the partition. Filesystems known to work are at least fat16, fat32, ext2, ext3 and swap. This menu also allows you to delete a partition." msgstr "" #. Tag: para -#: using-d-i.xml:1388 +#: using-d-i.xml:1389 #, no-c-format msgid "Be sure to create at least two partitions: one for the root filesystem (which must be mounted as /) and one for swap. If you forget to mount the root filesystem, partman won't let you continue until you correct this issue." msgstr "" #. Tag: para -#: using-d-i.xml:1396 +#: using-d-i.xml:1397 #, no-c-format msgid "If you forget to select and format an EFI boot partition, partman will detect this and will not let you continue until you allocate one." msgstr "" #. Tag: para -#: using-d-i.xml:1402 +#: using-d-i.xml:1403 #, no-c-format msgid "Capabilities of partman can be extended with installer modules, but are dependent on your system's architecture. So if you can't see all promised goodies, check if you have loaded all required modules (e.g. partman-ext3, partman-xfs, or partman-lvm)." msgstr "" #. Tag: para -#: using-d-i.xml:1410 +#: using-d-i.xml:1411 #, no-c-format msgid "After you are satisfied with partitioning, select Finish partitioning and write changes to disk from the partitioning menu. You will be presented with a summary of changes made to the disks and asked to confirm that the filesystems should be created as requested." msgstr "" #. Tag: title -#: using-d-i.xml:1438 +#: using-d-i.xml:1439 #, no-c-format msgid "Configuring Multidisk Devices (Software RAID)" msgstr "" #. Tag: para -#: using-d-i.xml:1439 +#: using-d-i.xml:1440 #, no-c-format msgid "If you have more than one harddrive To be honest, you can construct an MD device even from partitions residing on single physical drive, but that won't give any benefits. in your computer, you can use mdcfg to set up your drives for increased performance and/or better reliability of your data. The result is called Multidisk Device (or after its most famous variant software RAID)." msgstr "" #. Tag: para -#: using-d-i.xml:1452 +#: using-d-i.xml:1453 #, no-c-format msgid "MD is basically a bunch of partitions located on different disks and combined together to form a logical device. This device can then be used like an ordinary partition (i.e. in partman you can format it, assign a mountpoint, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:1460 +#: using-d-i.xml:1461 #, no-c-format msgid "What benefits this brings depends on the type of MD device you are creating. Currently supported are: RAID0 Is mainly aimed at performance. RAID0 splits all incoming data into stripes and distributes them equally over each disk in the array. This can increase the speed of read/write operations, but when one of the disks fails, you will lose everything (part of the information is still on the healthy disk(s), the other part was on the failed disk). The typical use for RAID0 is a partition for video editing. RAID1 Is suitable for setups where reliability is the first concern. It consists of several (usually two) equally-sized partitions where every partition contains exactly the same data. This essentially means three things. First, if one of your disks fails, you still have the data mirrored on the remaining disks. Second, you can use only a fraction of the available capacity (more precisely, it is the size of the smallest partition in the RAID). Third, file-reads are load-balanced among the disks, which can improve performance on a server, such as a file server, that tends to be loaded with more disk reads than writes. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. RAID5 Is a good compromise between speed, reliability and data redundancy. RAID5 splits all incoming data into stripes and distributes them equally on all but one disk (similar to RAID0). Unlike RAID0, RAID5 also computes parity information, which gets written on the remaining disk. The parity disk is not static (that would be called RAID4), but is changing periodically, so the parity information is distributed equally on all disks. When one of the disks fails, the missing part of information can be computed from remaining data and its parity. RAID5 must consist of at least three active partitions. Optionally you can have a spare disk in the array which will take the place of the failed disk in the case of failure. As you can see, RAID5 has a similar degree of reliability to RAID1 while achieving less redundancy. On the other hand, it might be a bit slower on write operations than RAID0 due to computation of parity information. RAID6 Is similar to RAID5 except that it uses two parity devices instead of one. A RAID6 array can survive up to two disk failures. RAID10 RAID10 combines striping (as in RAID0) and mirroring (as in RAID1). It creates n copies of incoming data and distributes them across the partitions so that none of the copies of the same data are on the same device. The default value of n is 2, but it can be set to something else in expert mode. The number of partitions used must be at least n. RAID10 has different layouts for distributing the copies. The default is near copies. Near copies have all of the copies at about the same offset on all of the disks. Far copies have the copies at different offsets on the disks. Offset copies copy the stripe, not the individual copies. RAID10 can be used to achieve reliability and redundancy without the drawback of having to calculate parity. To sum it up:" msgstr "" #. Tag: entry -#: using-d-i.xml:1574 +#: using-d-i.xml:1575 #, no-c-format msgid "Type" msgstr "" #. Tag: entry -#: using-d-i.xml:1575 +#: using-d-i.xml:1576 #, no-c-format msgid "Minimum Devices" msgstr "" #. Tag: entry -#: using-d-i.xml:1576 +#: using-d-i.xml:1577 #, no-c-format msgid "Spare Device" msgstr "" #. Tag: entry -#: using-d-i.xml:1577 +#: using-d-i.xml:1578 #, no-c-format msgid "Survives disk failure?" msgstr "" #. Tag: entry -#: using-d-i.xml:1578 +#: using-d-i.xml:1579 #, no-c-format msgid "Available Space" msgstr "" #. Tag: entry -#: using-d-i.xml:1584 +#: using-d-i.xml:1585 #, no-c-format msgid "RAID0" msgstr "" #. Tag: entry -#: using-d-i.xml:1585 using-d-i.xml:1593 using-d-i.xml:1623 +#: using-d-i.xml:1586 using-d-i.xml:1594 using-d-i.xml:1624 #, no-c-format msgid "2" msgstr "" #. Tag: entry -#: using-d-i.xml:1586 using-d-i.xml:1587 +#: using-d-i.xml:1587 using-d-i.xml:1588 #, no-c-format msgid "no" msgstr "" #. Tag: entry -#: using-d-i.xml:1588 +#: using-d-i.xml:1589 #, no-c-format msgid "Size of the smallest partition multiplied by number of devices in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1592 +#: using-d-i.xml:1593 #, no-c-format msgid "RAID1" msgstr "" #. Tag: entry -#: using-d-i.xml:1594 using-d-i.xml:1602 using-d-i.xml:1613 using-d-i.xml:1624 +#: using-d-i.xml:1595 using-d-i.xml:1603 using-d-i.xml:1614 using-d-i.xml:1625 #, no-c-format msgid "optional" msgstr "" #. Tag: entry -#: using-d-i.xml:1595 using-d-i.xml:1603 using-d-i.xml:1614 using-d-i.xml:1625 +#: using-d-i.xml:1596 using-d-i.xml:1604 using-d-i.xml:1615 using-d-i.xml:1626 #, no-c-format msgid "yes" msgstr "" #. Tag: entry -#: using-d-i.xml:1596 +#: using-d-i.xml:1597 #, no-c-format msgid "Size of the smallest partition in RAID" msgstr "" #. Tag: entry -#: using-d-i.xml:1600 +#: using-d-i.xml:1601 #, no-c-format msgid "RAID5" msgstr "" #. Tag: entry -#: using-d-i.xml:1601 +#: using-d-i.xml:1602 #, no-c-format msgid "3" msgstr "" #. Tag: entry -#: using-d-i.xml:1604 +#: using-d-i.xml:1605 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus one)" msgstr "" #. Tag: entry -#: using-d-i.xml:1611 +#: using-d-i.xml:1612 #, no-c-format msgid "RAID6" msgstr "" #. Tag: entry -#: using-d-i.xml:1612 +#: using-d-i.xml:1613 #, no-c-format msgid "4" msgstr "" #. Tag: entry -#: using-d-i.xml:1615 +#: using-d-i.xml:1616 #, no-c-format msgid "Size of the smallest partition multiplied by (number of devices in RAID minus two)" msgstr "" #. Tag: entry -#: using-d-i.xml:1622 +#: using-d-i.xml:1623 #, no-c-format msgid "RAID10" msgstr "" #. Tag: entry -#: using-d-i.xml:1626 +#: using-d-i.xml:1627 #, no-c-format msgid "Total of all partitions divided by the number of chunk copies (defaults to two)" msgstr "" #. Tag: para -#: using-d-i.xml:1633 +#: using-d-i.xml:1634 #, no-c-format msgid "If you want to know more about Software RAID, have a look at Software RAID HOWTO." msgstr "" #. Tag: para -#: using-d-i.xml:1638 +#: using-d-i.xml:1639 #, no-c-format msgid "To create an MD device, you need to have the desired partitions it should consist of marked for use in a RAID. (This is done in partman in the Partition settings menu where you should select Use as: physical volume for RAID .)" msgstr "" #. Tag: para -#: using-d-i.xml:1647 +#: using-d-i.xml:1648 #, no-c-format msgid "Make sure that the system can be booted with the partitioning scheme you are planning. In general it will be necessary to create a separate file system for /boot when using RAID for the root (/) file system. Most boot loaders (including lilo and grub) do support mirrored (not striped!) RAID1, so using for example RAID5 for / and RAID1 for /boot can be an option." msgstr "" #. Tag: para -#: using-d-i.xml:1659 +#: using-d-i.xml:1660 #, no-c-format msgid "Support for MD is a relatively new addition to the installer. You may experience problems for some RAID levels and in combination with some bootloaders if you try to use MD for the root (/) file system. For experienced users, it may be possible to work around some of these problems by executing some configuration or installation steps manually from a shell." msgstr "" #. Tag: para -#: using-d-i.xml:1668 +#: using-d-i.xml:1669 #, no-c-format msgid "Next, you should choose Configure software RAID from the main partman menu. (The menu will only appear after you mark at least one partition for use as physical volume for RAID.) On the first screen of mdcfg simply select Create MD device. You will be presented with a list of supported types of MD devices, from which you should choose one (e.g. RAID1). What follows depends on the type of MD you selected." msgstr "" #. Tag: para -#: using-d-i.xml:1681 +#: using-d-i.xml:1682 #, no-c-format msgid "RAID0 is simple — you will be issued with the list of available RAID partitions and your only task is to select the partitions which will form the MD." msgstr "" #. Tag: para -#: using-d-i.xml:1688 +#: using-d-i.xml:1689 #, no-c-format msgid "RAID1 is a bit more tricky. First, you will be asked to enter the number of active devices and the number of spare devices which will form the MD. Next, you need to select from the list of available RAID partitions those that will be active and then those that will be spare. The count of selected partitions must be equal to the number provided earlier. Don't worry. If you make a mistake and select a different number of partitions, &d-i; won't let you continue until you correct the issue." msgstr "" #. Tag: para -#: using-d-i.xml:1700 +#: using-d-i.xml:1701 #, no-c-format msgid "RAID5 has a setup procedure similar to RAID1 with the exception that you need to use at least three active partitions." msgstr "" #. Tag: para -#: using-d-i.xml:1706 +#: using-d-i.xml:1707 #, no-c-format msgid "RAID6 also has a setup procedure similar to RAID1 except that at least four active partitions are required." msgstr "" #. Tag: para -#: using-d-i.xml:1712 +#: using-d-i.xml:1713 #, no-c-format msgid "RAID10 again has a setup procedure similar to RAID1 except in expert mode. In expert mode, &d-i; will ask you for the layout. The layout has two parts. The first part is the layout type. It is either n (for near copies), f (for far copies), or o (for offset copies). The second part is the number of copies to make of the data. There must be at least that many active devices so that all of the copies can be distributed onto different disks." msgstr "" #. Tag: para -#: using-d-i.xml:1726 +#: using-d-i.xml:1727 #, no-c-format msgid "It is perfectly possible to have several types of MD at once. For example, if you have three 200 GB hard drives dedicated to MD, each containing two 100 GB partitions, you can combine the first partitions on all three disks into the RAID0 (fast 300 GB video editing partition) and use the other three partitions (2 active and 1 spare) for RAID1 (quite reliable 100 GB partition for /home)." msgstr "" #. Tag: para -#: using-d-i.xml:1735 +#: using-d-i.xml:1736 #, no-c-format msgid "After you set up MD devices to your liking, you can Finish mdcfg to return back to the partman to create filesystems on your new MD devices and assign them the usual attributes like mountpoints." msgstr "" #. Tag: title -#: using-d-i.xml:1750 +#: using-d-i.xml:1751 #, no-c-format msgid "Configuring the Logical Volume Manager (LVM)" msgstr "" #. Tag: para -#: using-d-i.xml:1751 +#: using-d-i.xml:1752 #, no-c-format msgid "If you are working with computers at the level of system administrator or advanced user, you have surely seen the situation where some disk partition (usually the most important one) was short on space, while some other partition was grossly underused and you had to manage this situation by moving stuff around, symlinking, etc." msgstr "" #. Tag: para -#: using-d-i.xml:1759 +#: using-d-i.xml:1760 #, no-c-format msgid "To avoid the described situation you can use Logical Volume Manager (LVM). Simply said, with LVM you can combine your partitions (physical volumes in LVM lingo) to form a virtual disk (so called volume group), which can then be divided into virtual partitions (logical volumes). The point is that logical volumes (and of course underlying volume groups) can span across several physical disks." msgstr "" #. Tag: para -#: using-d-i.xml:1769 +#: using-d-i.xml:1770 #, no-c-format msgid "Now when you realize you need more space for your old 160GB /home partition, you can simply add a new 300GB disk to the computer, join it with your existing volume group and then resize the logical volume which holds your /home filesystem and voila — your users have some room again on their renewed 460GB partition. This example is of course a bit oversimplified. If you haven't read it yet, you should consult the LVM HOWTO." msgstr "" #. Tag: para -#: using-d-i.xml:1780 +#: using-d-i.xml:1781 #, no-c-format msgid "LVM setup in &d-i; is quite simple and completely supported inside partman. First, you have to mark the partition(s) to be used as physical volumes for LVM. This is done in the Partition settings menu where you should select Use as: physical volume for LVM ." msgstr "" #. Tag: para -#: using-d-i.xml:1789 +#: using-d-i.xml:1790 #, no-c-format msgid "When you return to the main partman screen, you will see a new option Configure the Logical Volume Manager. When you select that, you will first be asked to confirm pending changes to the partition table (if any) and after that the LVM configuration menu will be shown. Above the menu a summary of the LVM configuration is shown. The menu itself is context sensitive and only shows valid actions. The possible actions are:" msgstr "" #. Tag: para -#: using-d-i.xml:1800 +#: using-d-i.xml:1801 #, no-c-format msgid "Display configuration details: shows LVM device structure, names and sizes of logical volumes and more" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1805 +#: using-d-i.xml:1806 #, no-c-format msgid "Create volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1808 +#: using-d-i.xml:1809 #, no-c-format msgid "Create logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1811 +#: using-d-i.xml:1812 #, no-c-format msgid "Delete volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1814 +#: using-d-i.xml:1815 #, no-c-format msgid "Delete logical volume" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1817 +#: using-d-i.xml:1818 #, no-c-format msgid "Extend volume group" msgstr "" #. Tag: guimenuitem -#: using-d-i.xml:1820 +#: using-d-i.xml:1821 #, no-c-format msgid "Reduce volume group" msgstr "" #. Tag: para -#: using-d-i.xml:1822 +#: using-d-i.xml:1823 #, no-c-format msgid "Finish: return to the main partman screen" msgstr "" #. Tag: para -#: using-d-i.xml:1828 +#: using-d-i.xml:1829 #, no-c-format msgid "Use the options in that menu to first create a volume group and then create your logical volumes inside it." msgstr "" #. Tag: para -#: using-d-i.xml:1833 +#: using-d-i.xml:1834 #, no-c-format msgid "After you return to the main partman screen, any created logical volumes will be displayed in the same way as ordinary partitions (and you should treat them as such)." msgstr "" #. Tag: title -#: using-d-i.xml:1847 +#: using-d-i.xml:1848 #, no-c-format msgid "Configuring Encrypted Volumes" msgstr "" #. Tag: para -#: using-d-i.xml:1848 +#: using-d-i.xml:1849 #, no-c-format msgid "&d-i; allows you to set up encrypted partitions. Every file you write to such a partition is immediately saved to the device in encrypted form. Access to the encrypted data is granted only after entering the passphrase used when the encrypted partition was originally created. This feature is useful to protect sensitive data in case your laptop or hard drive gets stolen. The thief might get physical access to the hard drive, but without knowing the right passphrase, the data on the hard drive will look like random characters." msgstr "" #. Tag: para -#: using-d-i.xml:1860 +#: using-d-i.xml:1861 #, no-c-format msgid "The two most important partitions to encrypt are: the home partition, where your private data resides, and the swap partition, where sensitive data might be stored temporarily during operation. Of course, nothing prevents you from encrypting any other partitions that might be of interest. For example /var where database servers, mail servers or print servers store their data, or /tmp which is used by various programs to store potentially interesting temporary files. Some people may even want to encrypt their whole system. The only exception is the /boot partition which must remain unencrypted, because currently there is no way to load the kernel from an encrypted partition." msgstr "" #. Tag: para -#: using-d-i.xml:1875 +#: using-d-i.xml:1876 #, no-c-format msgid "Please note that the performance of encrypted partitions will be less than that of unencrypted ones because the data needs to be decrypted or encrypted for every read or write. The performance impact depends on your CPU speed, chosen cipher and a key length." msgstr "" #. Tag: para -#: using-d-i.xml:1882 +#: using-d-i.xml:1883 #, no-c-format msgid "To use encryption, you have to create a new partition by selecting some free space in the main partitioning menu. Another option is to choose an existing partition (e.g. a regular partition, an LVM logical volume or a RAID volume). In the Partition settings menu, you need to select physical volume for encryption at the Use as: option. The menu will then change to include several cryptographic options for the partition." msgstr "" #. Tag: para -#: using-d-i.xml:1893 +#: using-d-i.xml:1894 #, no-c-format msgid "&d-i; supports several encryption methods. The default method is dm-crypt (included in newer Linux kernels, able to host LVM physical volumes), the other is loop-AES (older, maintained separately from the Linux kernel tree). Unless you have compelling reasons to do otherwise, it is recommended to use the default." msgstr "" #. Tag: para -#: using-d-i.xml:1905 +#: using-d-i.xml:1906 #, no-c-format msgid "First, let's have a look at the options available when you select Device-mapper (dm-crypt) as the encryption method. As always: when in doubt, use the defaults, because they have been carefully chosen with security in mind." msgstr "" #. Tag: term -#: using-d-i.xml:1915 +#: using-d-i.xml:1916 #, no-c-format msgid "Encryption: aes" msgstr "" #. Tag: para -#: using-d-i.xml:1917 +#: using-d-i.xml:1918 #, no-c-format msgid "This option lets you select the encryption algorithm (cipher) which will be used to encrypt the data on the partition. &d-i; currently supports the following block ciphers: aes, blowfish, serpent, and twofish. It is beyond the scope of this document to discuss the qualities of these different algorithms, however, it might help your decision to know that in 2000, AES was chosen by the American National Institute of Standards and Technology as the standard encryption algorithm for protecting sensitive information in the 21st century." msgstr "" #. Tag: term -#: using-d-i.xml:1935 +#: using-d-i.xml:1936 #, no-c-format msgid "Key size: 256" msgstr "" #. Tag: para -#: using-d-i.xml:1937 +#: using-d-i.xml:1938 #, no-c-format msgid "Here you can specify the length of the encryption key. With a larger key size, the strength of the encryption is generally improved. On the other hand, increasing the length of the key usually has a negative impact on performance. Available key sizes vary depending on the cipher." msgstr "" #. Tag: term -#: using-d-i.xml:1949 +#: using-d-i.xml:1950 #, no-c-format msgid "IV algorithm: cbc-essiv:sha256" msgstr "" #. Tag: para -#: using-d-i.xml:1951 +#: using-d-i.xml:1952 #, no-c-format msgid "The Initialization Vector or IV algorithm is used in cryptography to ensure that applying the cipher on the same clear text data with the same key always produces a unique cipher text. The idea is to prevent the attacker from deducing information from repeated patterns in the encrypted data." msgstr "" #. Tag: para -#: using-d-i.xml:1961 +#: using-d-i.xml:1962 #, no-c-format msgid "From the provided alternatives, the default cbc-essiv:sha256 is currently the least vulnerable to known attacks. Use the other alternatives only when you need to ensure compatibility with some previously installed system that is not able to use newer algorithms." msgstr "" #. Tag: term -#: using-d-i.xml:1973 +#: using-d-i.xml:1974 #, no-c-format msgid "Encryption key: Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1975 +#: using-d-i.xml:1976 #, no-c-format msgid "Here you can choose the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:1981 +#: using-d-i.xml:1982 #, no-c-format msgid "Passphrase" msgstr "" #. Tag: para -#: using-d-i.xml:1982 +#: using-d-i.xml:1983 #, no-c-format msgid "The encryption key will be computed Using a passphrase as the key currently means that the partition will be set up using LUKS. on the basis of a passphrase which you will be able to enter later in the process." msgstr "" #. Tag: term -#: using-d-i.xml:1997 using-d-i.xml:2090 +#: using-d-i.xml:1998 using-d-i.xml:2091 #, no-c-format msgid "Random key" msgstr "" #. Tag: para -#: using-d-i.xml:1998 +#: using-d-i.xml:1999 #, no-c-format msgid "A new encryption key will be generated from random data each time you try to bring up the encrypted partition. In other words: on every shutdown the content of the partition will be lost as the key is deleted from memory. (Of course, you could try to guess the key with a brute force attack, but unless there is an unknown weakness in the cipher algorithm, it is not achievable in our lifetime.)" msgstr "" #. Tag: para -#: using-d-i.xml:2007 +#: using-d-i.xml:2008 #, no-c-format msgid "Random keys are useful for swap partitions because you do not need to bother yourself with remembering the passphrase or wiping sensitive information from the swap partition before shutting down your computer. However, it also means that you will not be able to use the suspend-to-disk functionality offered by newer Linux kernels as it will be impossible (during a subsequent boot) to recover the suspended data written to the swap partition." msgstr "" #. Tag: term -#: using-d-i.xml:2026 using-d-i.xml:2103 +#: using-d-i.xml:2027 using-d-i.xml:2104 #, no-c-format msgid "Erase data: yes" msgstr "" #. Tag: para -#: using-d-i.xml:2028 +#: using-d-i.xml:2029 #, no-c-format msgid "Determines whether the content of this partition should be overwritten with random data before setting up the encryption. This is recommended because it might otherwise be possible for an attacker to discern which parts of the partition are in use and which are not. In addition, this will make it harder to recover any leftover data from previous installations It is believed that the guys from three-letter agencies can restore the data even after several rewrites of the magnetooptical media, though. ." msgstr "" #. Tag: para -#: using-d-i.xml:2048 +#: using-d-i.xml:2049 #, no-c-format msgid "If you select Encryption method: Loopback (loop-AES) , the menu changes to provide the following options:" msgstr "" #. Tag: term -#: using-d-i.xml:2057 +#: using-d-i.xml:2058 #, no-c-format msgid "Encryption: AES256" msgstr "" #. Tag: para -#: using-d-i.xml:2059 +#: using-d-i.xml:2060 #, no-c-format msgid "For loop-AES, unlike dm-crypt, the options for cipher and key size are combined, so you can select both at the same time. Please see the above sections on ciphers and key sizes for further information." msgstr "" #. Tag: term -#: using-d-i.xml:2069 +#: using-d-i.xml:2070 #, no-c-format msgid "Encryption key: Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:2071 +#: using-d-i.xml:2072 #, no-c-format msgid "Here you can select the type of the encryption key for this partition." msgstr "" #. Tag: term -#: using-d-i.xml:2077 +#: using-d-i.xml:2078 #, no-c-format msgid "Keyfile (GnuPG)" msgstr "" #. Tag: para -#: using-d-i.xml:2078 +#: using-d-i.xml:2079 #, no-c-format msgid "The encryption key will be generated from random data during the installation. Moreover this key will be encrypted with GnuPG, so to use it, you will need to enter the proper passphrase (you will be asked to provide one later in the process)." msgstr "" #. Tag: para -#: using-d-i.xml:2091 +#: using-d-i.xml:2092 #, no-c-format msgid "Please see the section on random keys above." msgstr "" #. Tag: para -#: using-d-i.xml:2105 +#: using-d-i.xml:2106 #, no-c-format msgid "Please see the the section on erasing data above." msgstr "" #. Tag: para -#: using-d-i.xml:2114 +#: using-d-i.xml:2115 #, no-c-format msgid "After you have selected the desired parameters for your encrypted partitions, return back to the main partitioning menu. There should now be a new menu item called Configure encrypted volumes. After you select it, you will be asked to confirm the deletion of data on partitions marked to be erased and possibly other actions such as writing a new partition table. For large partitions this might take some time." msgstr "" #. Tag: para -#: using-d-i.xml:2124 +#: using-d-i.xml:2125 #, no-c-format msgid "Next you will be asked to enter a passphrase for partitions configured to use one. Good passphrases should be longer than 8 characters, should be a mixture of letters, numbers and other characters and should not contain common dictionary words or information easily associable with you (such as birthdates, hobbies, pet names, names of family members or relatives, etc.)." msgstr "" #. Tag: para -#: using-d-i.xml:2133 +#: using-d-i.xml:2134 #, no-c-format msgid "Before you input any passphrases, you should have made sure that your keyboard is configured correctly and generates the expected characters. If you are unsure, you can switch to the second virtual console and type some text at the prompt. This ensures that you won't be surprised later, e.g. by trying to input a passphrase using a qwerty keyboard layout when you used an azerty layout during the installation. This situation can have several causes. Maybe you switched to another keyboard layout during the installation, or the selected keyboard layout might not have been set up yet when entering the passphrase for the root file system." msgstr "" #. Tag: para -#: using-d-i.xml:2146 +#: using-d-i.xml:2147 #, no-c-format msgid "If you selected to use methods other than a passphrase to create encryption keys, they will be generated now. Because the kernel may not have gathered a sufficient amount of entropy at this early stage of the installation, the process may take a long time. You can help speed up the process by generating entropy: e.g. by pressing random keys, or by switching to the shell on the second virtual console and generating some network and disk traffic (downloading some files, feeding big files into /dev/null, etc.). This will be repeated for each partition to be encrypted." msgstr "" #. Tag: para -#: using-d-i.xml:2162 +#: using-d-i.xml:2163 #, no-c-format msgid "" "After returning to the main partitioning menu, you will see all encrypted volumes as additional partitions which can be configured in the same way as ordinary partitions. The following example shows two different volumes. The first one is encrypted via dm-crypt, the second one via loop-AES. \n" @@ -1800,553 +1800,553 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:2175 +#: using-d-i.xml:2176 #, no-c-format msgid "Pay attention to the identifiers in parentheses (sda2_crypt and loop0 in this case) and the mount points you assigned to each encrypted volume. You will need this information later when booting the new system. The differences between the ordinary boot process and the boot process with encryption involved will be covered later in ." msgstr "" #. Tag: para -#: using-d-i.xml:2185 +#: using-d-i.xml:2186 #, no-c-format msgid "Once you are satisfied with the partitioning scheme, continue with the installation." msgstr "" #. Tag: title -#: using-d-i.xml:2196 +#: using-d-i.xml:2197 #, no-c-format msgid "Installing the Base System" msgstr "" #. Tag: para -#: using-d-i.xml:2197 +#: using-d-i.xml:2198 #, no-c-format msgid "Although this stage is the least problematic, it consumes a significant fraction of the install because it downloads, verifies and unpacks the whole base system. If you have a slow computer or network connection, this could take some time." msgstr "" #. Tag: para -#: using-d-i.xml:2210 +#: using-d-i.xml:2211 #, no-c-format msgid "During installation of the base system, package unpacking and setup messages are redirected to tty4. You can access this terminal by pressing Left AltF4; get back to the main installer process with Left AltF1." msgstr "" #. Tag: para -#: using-d-i.xml:2219 +#: using-d-i.xml:2220 #, no-c-format msgid "The unpack/setup messages generated during this phase are also saved in /var/log/syslog. You can check them there if the installation is performed over a serial console." msgstr "" #. Tag: para -#: using-d-i.xml:2225 +#: using-d-i.xml:2226 #, no-c-format msgid "As part of the installation, a &arch-kernel; kernel will be installed. At the default priority, the installer will choose one for you that best matches your hardware. In lower priority modes, you will be able to choose from a list of available kernels." msgstr "" #. Tag: para -#: using-d-i.xml:2232 +#: using-d-i.xml:2233 #, no-c-format msgid "When packages are installed using the package management system, it will by default also install packages that are recommended by those packages. Recommended packages are not strictly required for the core functionality of the selected software, but they do enhance that software and should, in the view of the package maintainers, normally be installed together with that software." msgstr "" #. Tag: para -#: using-d-i.xml:2242 +#: using-d-i.xml:2243 #, no-c-format msgid "For technical reasons packages installed during the installation of the base system are installed without their Recommends. The rule described above only takes effect after this point in the installation process." msgstr "" #. Tag: title -#: using-d-i.xml:2254 +#: using-d-i.xml:2255 #, no-c-format msgid "Installing Additional Software" msgstr "" #. Tag: para -#: using-d-i.xml:2255 +#: using-d-i.xml:2256 #, no-c-format msgid "At this point you have a usable but limited system. Most users will want to install additional software on the system to tune it to their needs, and the installer allows you do so. This step can take even longer than installing the base system if you have a slow computer or network connection." msgstr "" #. Tag: title -#: using-d-i.xml:2270 +#: using-d-i.xml:2271 #, no-c-format msgid "Configuring apt" msgstr "" #. Tag: para -#: using-d-i.xml:2272 +#: using-d-i.xml:2273 #, no-c-format msgid "One of the tools used to install packages on a &debian-gnu; system is a program called apt-get, from the apt package Note that the program which actually installs the packages is called dpkg. However, this program is more of a low-level tool. apt-get is a higher-level tool, which will invoke dpkg as appropriate. It knows how to retrieve packages from your CD, the network, or wherever. It is also able to automatically install other packages which are required to make the package you're trying to install work correctly. . Other front-ends for package management, like aptitude and synaptic, are also in use. These front-ends are recommended for new users, since they integrate some additional features (package searching and status checks) in a nice user interface. In fact, aptitude is now the recommended utility for package management." msgstr "" #. Tag: para -#: using-d-i.xml:2296 +#: using-d-i.xml:2297 #, no-c-format msgid "apt must be configured so that it knows from where to retrieve packages. The results of this configuration are written to the file /etc/apt/sources.list. You can examine and edit this file to your liking after the installation is complete." msgstr "" #. Tag: para -#: using-d-i.xml:2303 +#: using-d-i.xml:2304 #, no-c-format msgid "If you are installing at default priority, the installer will largely take care of the configuration automatically, based on the installation method you are using and possibly using choices made earlier in the installation. In most cases the installer will automatically add a security mirror and, if you are installing the stable distribution, a mirror for the volatile update service." msgstr "" #. Tag: para -#: using-d-i.xml:2312 +#: using-d-i.xml:2313 #, no-c-format msgid "If you are installing at a lower priority (e.g. in expert mode), you will be able to make more decisions yourself. You can choose whether or not to use the security and/or volatile update services, and you can choose to add packages from the contrib and non-free sections of the archive." msgstr "" #. Tag: title -#: using-d-i.xml:2323 +#: using-d-i.xml:2324 #, no-c-format msgid "Installing from more than one CD or DVD" msgstr "" #. Tag: para -#: using-d-i.xml:2325 +#: using-d-i.xml:2326 #, no-c-format msgid "If you are installing from a CD or a DVD that is part of a larger set, the installer will ask if you want to scan additional CDs or DVDs. If you have additional CDs or DVDs available, you probably want to do this so the installer can use the packages included on them." msgstr "" #. Tag: para -#: using-d-i.xml:2332 +#: using-d-i.xml:2333 #, no-c-format msgid "If you do not have any additional CDs or DVDs, that is no problem: using them is not required. If you also do not use a network mirror (as explained in the next section), it can mean that not all packages belonging to the tasks you select in the next step of the installation can be installed." msgstr "" #. Tag: para -#: using-d-i.xml:2340 +#: using-d-i.xml:2341 #, no-c-format msgid "Packages are included on CDs (and DVDs) in the order of their popularity. This means that for most uses only the first CDs in a set are needed and that only very few people actually use any of the packages included on the last CDs in a set." msgstr "" #. Tag: para -#: using-d-i.xml:2347 +#: using-d-i.xml:2348 #, no-c-format msgid "It also means that buying or downloading and burning a full CD set is just a waste of money as you'll never use most of them. In most cases you are better off getting only the first 3 to 8 CDs and installing any additional packages you may need from the Internet by using a mirror. The same goes for DVD sets: the first DVD, or maybe the first two DVDs will cover most needs." msgstr "" #. Tag: para -#: using-d-i.xml:2356 +#: using-d-i.xml:2357 #, no-c-format msgid "A good rule of thumb is that for a regular desktop installation (using the GNOME desktop environment) only the first three CDs are needed. For the alternative desktop environments (KDE or Xfce), additional CDs are needed. The first DVD easily covers all three desktop environments." msgstr "" #. Tag: para -#: using-d-i.xml:2364 +#: using-d-i.xml:2365 #, no-c-format msgid "If you do scan multiple CDs or DVDs, the installer will prompt you to exchange them when it needs packages from another CD/DVD than the one currently in the drive. Note that only CDs or DVDs that belong to the same set should be scanned. The order in which they are scanned does not really matter, but scanning them in ascending order will reduce the chance of mistakes." msgstr "" #. Tag: title -#: using-d-i.xml:2377 +#: using-d-i.xml:2378 #, no-c-format msgid "Using a network mirror" msgstr "" #. Tag: para -#: using-d-i.xml:2379 +#: using-d-i.xml:2380 #, no-c-format msgid "One question that will be asked during most installs is whether or not to use a network mirror as a source for packages. In most cases the default answer should be fine, but there are some exceptions." msgstr "" #. Tag: para -#: using-d-i.xml:2385 +#: using-d-i.xml:2386 #, no-c-format msgid "If you are not installing from a full CD or DVD or using a full CD/DVD image, you really should use a network mirror as otherwise you will end up with only a very minimal system. However, if you have a limited Internet connection it is best not to select the desktop task in the next step of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2394 +#: using-d-i.xml:2395 #, no-c-format msgid "If you are installing from a single full CD or using a full CD image, using a network mirror is not required, but is still strongly recommended because a single CD contains only a fairly limited number of packages. If you have a limited Internet connection it may still be best to not select a network mirror here, but to finish the installation using only what's available on the CD and selectively install additional packages after the installation (i.e. after you have rebooted into the new system)." msgstr "" #. Tag: para -#: using-d-i.xml:2405 +#: using-d-i.xml:2406 #, no-c-format msgid "If you are installing from a DVD or using a DVD image, any packages needed during the installation should be present on the first DVD. The same is true if you have scanned multiple CDs as explained in the previous section. Use of a network mirror is optional." msgstr "" #. Tag: para -#: using-d-i.xml:2412 +#: using-d-i.xml:2413 #, no-c-format msgid "One advantage of adding a network mirror is that updates that have occurred since the CD/DVD set was created and have been included in a point release, will become available for installation, thus extending the life of your CD/DVD set without compromising the security or stability of the installed system." msgstr "" #. Tag: para -#: using-d-i.xml:2419 +#: using-d-i.xml:2420 #, no-c-format msgid "In summary: selecting a network mirror is generally a good idea, except if you do not have a good Internet connection. If the current version of a package is available from CD/DVD, the installer will always use that. The amount of data that will be downloaded if you do select a mirror thus depends on" msgstr "" #. Tag: para -#: using-d-i.xml:2428 +#: using-d-i.xml:2429 #, no-c-format msgid "the tasks you select in the next step of the installation," msgstr "" #. Tag: para -#: using-d-i.xml:2433 +#: using-d-i.xml:2434 #, no-c-format msgid "which packages are needed for those tasks," msgstr "" #. Tag: para -#: using-d-i.xml:2438 +#: using-d-i.xml:2439 #, no-c-format msgid "which of those packages are present on the CDs or DVDs you have scanned, and" msgstr "" #. Tag: para -#: using-d-i.xml:2443 +#: using-d-i.xml:2444 #, no-c-format msgid "whether any updated versions of packages included on the CDs or DVDs are available from a mirror (either a regular package mirror, or a mirror for security or volatile updates)." msgstr "" #. Tag: para -#: using-d-i.xml:2452 +#: using-d-i.xml:2453 #, no-c-format msgid "Note that the last point means that, even if you choose not to use a network mirror, some packages may still be downloaded from the Internet if there is a security or volatile update available for them and those services have been configured." msgstr "" #. Tag: title -#: using-d-i.xml:2468 +#: using-d-i.xml:2469 #, no-c-format msgid "Selecting and Installing Software" msgstr "" #. Tag: para -#: using-d-i.xml:2470 +#: using-d-i.xml:2471 #, no-c-format msgid "During the installation process, you are given the opportunity to select additional software to install. Rather than picking individual software packages from the &num-of-distrib-pkgs; available packages, this stage of the installation process focuses on selecting and installing predefined collections of software to quickly set up your computer to perform various tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2479 +#: using-d-i.xml:2480 #, no-c-format msgid "So, you have the ability to choose tasks first, and then add on more individual packages later. These tasks loosely represent a number of different jobs or things you want to do with your computer, such as Desktop environment, Web server, or Print server You should know that to present this list, the installer is merely invoking the tasksel program. It can be run at any time after installation to install more packages (or remove them), or you can use a more fine-grained tool such as aptitude. If you are looking for a specific single package, after installation is complete, simply run aptitude install package, where package is the name of the package you are looking for. . lists the space requirements for the available tasks." msgstr "" #. Tag: para -#: using-d-i.xml:2506 +#: using-d-i.xml:2507 #, no-c-format msgid "Some tasks may be pre-selected based on the characteristics of the computer you are installing. If you disagree with these selections you can deselect them. You can even opt to install no tasks at all at this point." msgstr "" #. Tag: para -#: using-d-i.xml:2513 +#: using-d-i.xml:2514 #, no-c-format msgid "In the standard user interface of the installer, you can use the space bar to toggle selection of a task." msgstr "" #. Tag: para -#: using-d-i.xml:2519 +#: using-d-i.xml:2520 #, no-c-format msgid "Unless you are using the special KDE or Xfce/LXDE CDs, the Desktop environment task will install the GNOME desktop environment." msgstr "" #. Tag: para -#: using-d-i.xml:2524 +#: using-d-i.xml:2525 #, no-c-format msgid "It is not possible to interactively select a different desktop during the installation. However, it is possible to get &d-i; to install a KDE desktop environment instead of GNOME by using preseeding (see ) or by adding the parameter desktop=kde at the boot prompt when starting the installer. Alternatively the more lightweight Xfce and LXDE desktop environments can be selected by using desktop=xfce or desktop=lxde." msgstr "" #. Tag: para -#: using-d-i.xml:2535 +#: using-d-i.xml:2536 #, no-c-format msgid "Some CD images (businesscard, netinst and DVD) also allow selection of the desired desktop environment from the graphical boot menu. Select the Advanced options option in the main menu and look for Alternative desktop environments." msgstr "" #. Tag: para -#: using-d-i.xml:2542 +#: using-d-i.xml:2543 #, no-c-format msgid "Note that this will only work if the packages needed for the desired desktop environment are actually available. If you are installing using a single full CD image, they will need to be downloaded from a mirror as most needed packages are only included on later CDs; installing KDE, Xfce or LXDE this way should work fine if you are using a DVD image or any other installation method." msgstr "" #. Tag: para -#: using-d-i.xml:2552 +#: using-d-i.xml:2553 #, no-c-format msgid "The various server tasks will install software roughly as follows. DNS server: bind9; File server: samba, nfs; Mail server: exim4, spamassassin, uw-imap; Print server: cups; SQL database: postgresql; Web server: apache2." msgstr "" #. Tag: para -#: using-d-i.xml:2563 +#: using-d-i.xml:2564 #, no-c-format msgid "The Standard system task will install any package that has a priority standard. This includes a lot of common utilities that are normally available on any Linux or Unix system. You should leave this task selected unless you know what you are doing and want a really minimal system." msgstr "" #. Tag: para -#: using-d-i.xml:2571 +#: using-d-i.xml:2572 #, no-c-format msgid "If during language selection a default locale other than the C locale was selected, tasksel will check if any localization tasks are defined for that locale and will automatically try to install relevant localization packages. This includes for example packages containing word lists or special fonts for your language. If a desktop environment was selected, it will also install appropriate localization packages for that (if available)." msgstr "" #. Tag: para -#: using-d-i.xml:2581 +#: using-d-i.xml:2582 #, no-c-format msgid "Once you've selected your tasks, select &BTN-CONT;. At this point, aptitude will install the packages that are part of the selected tasks. If a particular program needs more information from the user, it will prompt you during this process." msgstr "" #. Tag: para -#: using-d-i.xml:2588 +#: using-d-i.xml:2589 #, no-c-format msgid "You should be aware that especially the Desktop task is very large. Especially when installing from a normal CD-ROM in combination with a mirror for packages not on the CD-ROM, the installer may want to retrieve a lot of packages over the network. If you have a relatively slow Internet connection, this can take a long time. There is no option to cancel the installation of packages once it has started." msgstr "" #. Tag: para -#: using-d-i.xml:2597 +#: using-d-i.xml:2598 #, no-c-format msgid "Even when packages are included on the CD-ROM, the installer may still retrieve them from the mirror if the version available on the mirror is more recent than the one included on the CD-ROM. If you are installing the stable distribution, this can happen after a point release (an update of the original stable release); if you are installing the testing distribution this will happen if you are using an older image." msgstr "" #. Tag: title -#: using-d-i.xml:2612 +#: using-d-i.xml:2613 #, no-c-format msgid "Making Your System Bootable" msgstr "" #. Tag: para -#: using-d-i.xml:2614 +#: using-d-i.xml:2615 #, no-c-format msgid "If you are installing a diskless workstation, obviously, booting off the local disk isn't a meaningful option, and this step will be skipped. You may wish to set OpenBoot to boot from the network by default; see ." msgstr "" #. Tag: title -#: using-d-i.xml:2629 +#: using-d-i.xml:2630 #, no-c-format msgid "Detecting other operating systems" msgstr "" #. Tag: para -#: using-d-i.xml:2631 +#: using-d-i.xml:2632 #, no-c-format msgid "Before a boot loader is installed, the installer will attempt to probe for other operating systems which are installed on the machine. If it finds a supported operating system, you will be informed of this during the boot loader installation step, and the computer will be configured to boot this other operating system in addition to &debian;." msgstr "" #. Tag: para -#: using-d-i.xml:2639 +#: using-d-i.xml:2640 #, no-c-format msgid "Note that multiple operating systems booting on a single machine is still something of a black art. The automatic support for detecting and setting up boot loaders to boot other operating systems varies by architecture and even by subarchitecture. If it does not work you should consult your boot manager's documentation for more information." msgstr "" #. Tag: title -#: using-d-i.xml:2657 +#: using-d-i.xml:2658 #, no-c-format msgid "palo-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2658 +#: using-d-i.xml:2659 #, no-c-format msgid "The bootloader on PA-RISC is palo. PALO is similar in configuration and usage to LILO, with a few exceptions. First of all, PALO allows you to boot any kernel image on your boot partition. This is because PALO can actually read Linux partitions." msgstr "" #. Tag: para -#: using-d-i.xml:2667 +#: using-d-i.xml:2668 #, no-c-format msgid "hppa FIXME ( need more info )" msgstr "" #. Tag: title -#: using-d-i.xml:2679 +#: using-d-i.xml:2680 #, no-c-format msgid "Install the Grub Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2681 +#: using-d-i.xml:2682 #, no-c-format msgid "The main &architecture; boot loader is called grub. Grub is a flexible and robust boot loader and a good default choice for new users and old hands alike." msgstr "" #. Tag: para -#: using-d-i.xml:2687 +#: using-d-i.xml:2688 #, no-c-format msgid "By default, grub will be installed into the Master Boot Record (MBR), where it will take over complete control of the boot process. If you prefer, you can install it elsewhere. See the grub manual for complete information." msgstr "" #. Tag: para -#: using-d-i.xml:2693 +#: using-d-i.xml:2694 #, no-c-format msgid "If you do not want to install grub, use the &BTN-GOBACK; button to get to the main menu, and from there select whatever bootloader you would like to use." msgstr "" #. Tag: title -#: using-d-i.xml:2706 +#: using-d-i.xml:2707 #, no-c-format msgid "Install the LILO Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2708 +#: using-d-i.xml:2709 #, no-c-format msgid "The second &architecture; boot loader is called LILO. It is an old complex program which offers lots of functionality, including DOS, Windows, and OS/2 boot management. Please carefully read the instructions in the directory /usr/share/doc/lilo/ if you have special needs; also see the LILO mini-HOWTO." msgstr "" #. Tag: para -#: using-d-i.xml:2718 +#: using-d-i.xml:2719 #, no-c-format msgid "Currently the LILO installation will only create menu entries for other operating systems if these can be chainloaded. This means you may have to manually add a menu entry for operating systems like GNU/Linux and GNU/Hurd after the installation." msgstr "" #. Tag: para -#: using-d-i.xml:2726 +#: using-d-i.xml:2727 #, no-c-format msgid "&d-i; offers you three choices on where to install the LILO boot loader:" msgstr "" #. Tag: term -#: using-d-i.xml:2733 +#: using-d-i.xml:2734 #, no-c-format msgid "Master Boot Record (MBR)" msgstr "" #. Tag: para -#: using-d-i.xml:2733 +#: using-d-i.xml:2734 #, no-c-format msgid "This way the LILO will take complete control of the boot process." msgstr "" #. Tag: term -#: using-d-i.xml:2740 +#: using-d-i.xml:2741 #, no-c-format msgid "new &debian; partition" msgstr "" #. Tag: para -#: using-d-i.xml:2740 +#: using-d-i.xml:2741 #, no-c-format msgid "Choose this if you want to use another boot manager. LILO will install itself at the beginning of the new &debian; partition and it will serve as a secondary boot loader." msgstr "" #. Tag: term -#: using-d-i.xml:2749 +#: using-d-i.xml:2750 #, no-c-format msgid "Other choice" msgstr "" #. Tag: para -#: using-d-i.xml:2749 +#: using-d-i.xml:2750 #, no-c-format msgid "Useful for advanced users who want to install LILO somewhere else. In this case you will be asked for desired location. You can use traditional device names such as /dev/hda or /dev/sda." msgstr "" #. Tag: para -#: using-d-i.xml:2759 +#: using-d-i.xml:2760 #, 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;!" msgstr "" #. Tag: title -#: using-d-i.xml:2775 +#: using-d-i.xml:2776 #, no-c-format msgid "Install the ELILO Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2777 +#: using-d-i.xml:2778 #, 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 files into it. The elilo.efi program is copied into the EFI partition and then run by the EFI Boot Manager to do the actual work of loading and starting the Linux kernel." msgstr "" #. Tag: para -#: using-d-i.xml:2793 +#: using-d-i.xml:2794 #, 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:2805 +#: using-d-i.xml:2806 #, no-c-format msgid "Choose the correct partition!" msgstr "" #. Tag: para -#: using-d-i.xml:2807 +#: using-d-i.xml:2808 #, no-c-format msgid "The criterion for selecting a partition is that it must be a 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, elilo may format the partition during the installation, erasing any previous contents!" msgstr "" #. Tag: title -#: using-d-i.xml:2822 +#: using-d-i.xml:2823 #, no-c-format msgid "EFI Partition Contents" msgstr "" #. Tag: para -#: using-d-i.xml:2824 +#: using-d-i.xml:2825 #, 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:2846 +#: using-d-i.xml:2847 #, no-c-format msgid "elilo.conf" msgstr "" #. Tag: para -#: using-d-i.xml:2847 +#: using-d-i.xml:2848 #, 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:2856 +#: using-d-i.xml:2857 #, no-c-format msgid "elilo.efi" msgstr "" #. Tag: para -#: using-d-i.xml:2857 +#: using-d-i.xml:2858 #, 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:2867 +#: using-d-i.xml:2868 #, no-c-format msgid "initrd.img" msgstr "" #. Tag: para -#: using-d-i.xml:2868 +#: using-d-i.xml:2869 #, 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:2880 +#: using-d-i.xml:2881 #, no-c-format msgid "readme.txt" msgstr "" #. Tag: para -#: using-d-i.xml:2881 +#: using-d-i.xml:2882 #, 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:2891 +#: using-d-i.xml:2892 #, no-c-format msgid "vmlinuz" msgstr "" #. Tag: para -#: using-d-i.xml:2892 +#: using-d-i.xml:2893 #, 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:2912 +#: using-d-i.xml:2913 #, no-c-format msgid "arcboot-installer" msgstr "" #. Tag: para -#: using-d-i.xml:2913 +#: using-d-i.xml:2914 #, 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" @@ -2359,289 +2359,289 @@ msgid "" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2932 +#: using-d-i.xml:2933 #, no-c-format msgid "scsi" msgstr "" #. Tag: para -#: using-d-i.xml:2933 +#: using-d-i.xml:2934 #, 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:2941 +#: using-d-i.xml:2942 #, no-c-format msgid "disk" msgstr "" #. Tag: para -#: using-d-i.xml:2942 +#: using-d-i.xml:2943 #, no-c-format msgid "is the SCSI ID of the hard disk on which arcboot is installed" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2950 +#: using-d-i.xml:2951 #, no-c-format msgid "partnr" msgstr "" #. Tag: para -#: using-d-i.xml:2951 +#: using-d-i.xml:2952 #, no-c-format msgid "is the number of the partition on which /etc/arcboot.conf resides" msgstr "" #. Tag: replaceable -#: using-d-i.xml:2959 +#: using-d-i.xml:2960 #, no-c-format msgid "config" msgstr "" #. Tag: para -#: using-d-i.xml:2960 +#: using-d-i.xml:2961 #, 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:2981 +#: using-d-i.xml:2982 #, no-c-format msgid "Install Yaboot on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:2982 +#: using-d-i.xml:2983 #, 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-gnu;." msgstr "" #. Tag: title -#: using-d-i.xml:3000 +#: using-d-i.xml:3001 #, no-c-format msgid "Install Quik on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:3001 +#: using-d-i.xml:3002 #, 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:3017 +#: using-d-i.xml:3018 #, no-c-format msgid "zipl-installer" msgstr "" #. Tag: para -#: using-d-i.xml:3018 +#: using-d-i.xml:3019 #, 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:3035 +#: using-d-i.xml:3036 #, no-c-format msgid "Install the SILO Boot Loader on a Hard Disk" msgstr "" #. Tag: para -#: using-d-i.xml:3037 +#: using-d-i.xml:3038 #, 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:3062 +#: using-d-i.xml:3063 #, no-c-format msgid "Continue Without Boot Loader" msgstr "" #. Tag: para -#: using-d-i.xml:3064 +#: using-d-i.xml:3065 #, 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)." msgstr "" #. Tag: para -#: using-d-i.xml:3071 +#: using-d-i.xml:3072 #, 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:3088 +#: using-d-i.xml:3089 #, no-c-format msgid "Finishing the Installation" msgstr "" #. Tag: para -#: using-d-i.xml:3089 +#: using-d-i.xml:3090 #, no-c-format msgid "This is the last step in the &debian; installation process during which the installer will do any last minute tasks. It mostly consists of tidying up after the &d-i;." msgstr "" #. Tag: title -#: using-d-i.xml:3102 +#: using-d-i.xml:3103 #, no-c-format msgid "Setting the System Clock" msgstr "" #. Tag: para -#: using-d-i.xml:3104 +#: using-d-i.xml:3105 #, no-c-format msgid "The installer may ask you if the computer's clock is set to UTC. Normally this question is avoided if possible and the installer tries to work out whether the clock is set to UTC based on things like what other operating systems are installed." msgstr "" #. Tag: para -#: using-d-i.xml:3111 +#: using-d-i.xml:3112 #, no-c-format msgid "In expert mode you will always be able to choose whether or not the clock is set to UTC. Macintosh hardware clocks are normally set to local time. If you want to dual-boot, select local time instead of UTC. Systems that (also) run Dos or Windows are normally set to local time. If you want to dual-boot, select local time instead of UTC." msgstr "" #. Tag: para -#: using-d-i.xml:3122 +#: using-d-i.xml:3123 #, no-c-format msgid "At this point &d-i; will also attempt to save the current time to the system's hardware clock. This will be done either in UTC or local time, depending on the selection that was just made." msgstr "" #. Tag: title -#: using-d-i.xml:3137 +#: using-d-i.xml:3138 #, no-c-format msgid "Reboot the System" msgstr "" #. Tag: para -#: using-d-i.xml:3139 +#: using-d-i.xml:3140 #, no-c-format msgid "You will be prompted to remove the boot media (CD, floppy, etc) that you used to boot the installer. After that the system will be rebooted into your new &debian; system." msgstr "" #. Tag: para -#: using-d-i.xml:3145 +#: using-d-i.xml:3146 #, no-c-format msgid "After a final prompt the system will be halted because rebooting is not supported on &arch-title;. You then need to IPL &debian-gnu; from the DASD which you selected for the root filesystem during the first steps of the installation." msgstr "" #. Tag: title -#: using-d-i.xml:3158 +#: using-d-i.xml:3159 #, no-c-format msgid "Troubleshooting" msgstr "" #. Tag: para -#: using-d-i.xml:3159 +#: using-d-i.xml:3160 #, 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:3172 +#: using-d-i.xml:3173 #, no-c-format msgid "Saving the installation logs" msgstr "" #. Tag: para -#: using-d-i.xml:3174 +#: using-d-i.xml:3175 #, 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:3181 +#: using-d-i.xml:3182 #, 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:3201 +#: using-d-i.xml:3202 #, no-c-format msgid "Using the Shell and Viewing the Logs" msgstr "" #. Tag: para -#: using-d-i.xml:3203 +#: using-d-i.xml:3204 #, no-c-format msgid "There are several methods you can use to get a shell while running an installation. On most systems, and if you are not installing over serial console, the easiest method is to switch to the second virtual console by pressing Left Alt F2 That is: press the Alt key on the left-hand side of the space bar and the F2 function key at the same time. (on a Mac keyboard, Option F2). Use Left Alt F1 to switch back to the installer itself." msgstr "" #. Tag: para -#: using-d-i.xml:3221 +#: using-d-i.xml:3222 #, no-c-format msgid "For the graphical installer see also ." msgstr "" #. Tag: para -#: using-d-i.xml:3225 +#: using-d-i.xml:3226 #, no-c-format msgid "If you cannot switch consoles, there is also an Execute a Shell item on the main menu that can be used to start a shell. You can get to the main menu from most dialogs by using the &BTN-GOBACK; button one or more times. Type exit to close the shell and return to the installer." msgstr "" #. Tag: para -#: using-d-i.xml:3233 +#: using-d-i.xml:3234 #, 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 shell is a Bourne shell clone called ash and has some nice features like autocompletion and history." msgstr "" #. Tag: para -#: using-d-i.xml:3242 +#: using-d-i.xml:3243 #, no-c-format msgid "To edit and view files, use the text editor nano. Log files for the installation system can be found in the /var/log directory." msgstr "" #. Tag: para -#: using-d-i.xml:3249 +#: using-d-i.xml:3250 #, no-c-format msgid "Although you can do basically anything in a shell that the available commands allow you to do, the option to use a shell is really only there in case something goes wrong and for debugging." msgstr "" #. Tag: para -#: using-d-i.xml:3255 +#: using-d-i.xml:3256 #, no-c-format msgid "Doing things manually from the shell may interfere with the installation process and result in errors or an incomplete installation. In particular, you should always use let the installer activate your swap partition and not do this yourself from a shell." msgstr "" #. Tag: title -#: using-d-i.xml:3271 +#: using-d-i.xml:3272 #, no-c-format msgid "Installation Over the Network" msgstr "" #. Tag: para -#: using-d-i.xml:3273 +#: using-d-i.xml:3274 #, 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:3283 +#: using-d-i.xml:3284 #, 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:3296 +#: using-d-i.xml:3297 #, 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:3301 +#: using-d-i.xml:3302 #, 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:3313 +#: using-d-i.xml:3314 #, 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:3319 +#: using-d-i.xml:3320 #, 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" @@ -2650,127 +2650,127 @@ msgid "" msgstr "" #. Tag: para -#: using-d-i.xml:3336 +#: using-d-i.xml:3337 #, no-c-format msgid "The ssh server in the installer uses a default configuration that does not send keep-alive packets. In principle, a connection to the system being installed should be kept open indefinitely. However, in some situations — depending on your local network setup — the connection may be lost after some period of inactivity. One common case where this can happen is when there is some form of Network Address Translation (NAT) somewhere between the client and the system being installed. Depending on at which point of the installation the connection was lost, you may or may not be able to resume the installation after reconnecting." msgstr "" #. Tag: para -#: using-d-i.xml:3349 +#: using-d-i.xml:3350 #, no-c-format msgid "You may be able to avoid the connection being dropped by adding the option -o ServerAliveInterval=value when starting the ssh connection, or by adding that option in your ssh configuration file. Note however that in some cases adding this option may also cause a connection to be dropped (for example if keep-alive packets are sent during a brief network outage, from which ssh would otherwise have recovered), so it should only be used when needed." msgstr "" #. Tag: para -#: using-d-i.xml:3362 +#: using-d-i.xml:3363 #, 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 The following command will remove an existing entry for a host: ssh-keygen -R <hostname|IP address>. and try again." msgstr "" #. Tag: para -#: using-d-i.xml:3378 +#: using-d-i.xml:3379 #, 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:3388 +#: using-d-i.xml:3389 #, 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: title -#: using-d-i.xml:3407 +#: using-d-i.xml:3408 #, no-c-format msgid "Loading Missing Firmware" msgstr "" #. Tag: para -#: using-d-i.xml:3408 +#: using-d-i.xml:3409 #, no-c-format msgid "As described in , some devices require firmware to be loaded. In most cases the device will not work at all if the firmware is not available; sometimes basic functionality is not impaired if it is missing and the firmware is only needed to enable additional features." msgstr "" #. Tag: para -#: using-d-i.xml:3416 +#: using-d-i.xml:3417 #, no-c-format msgid "If a device driver requests firmware that is not available, &d-i; will display a dialog offering to load the missing firmware. If this option is selected, &d-i; will scan available devices for either loose firmware files or packages containing firmware. If found, the firmware will be copied to the correct location (/lib/firmware) and the driver module will be reloaded." msgstr "" #. Tag: para -#: using-d-i.xml:3426 +#: using-d-i.xml:3427 #, no-c-format msgid "Which devices are scanned and which file systems are supported depends on the architecture, the installation method and the stage of the installation. Especially during the early stages of the installation, loading the firmware is most likely to succeed from a FAT-formatted floppy disk or USB stick. On i386 and amd64 firmware can also be loaded from an MMC or SD card." msgstr "" #. Tag: para -#: using-d-i.xml:3436 +#: using-d-i.xml:3437 #, no-c-format msgid "Note that it is possible to skip loading the firmware if you know the device will also function without it, or if the device is not needed during the installation." msgstr "" #. Tag: para -#: using-d-i.xml:3443 +#: using-d-i.xml:3444 #, no-c-format msgid "Support for loading firmware is still relatively basic and is likely to be improved in future releases of the installer. Currently &d-i; will for example not display any warning if you choose to load missing firmware, but the requested firmware is not found. Please report any issues you encounter by filing an installation report (see )." msgstr "" #. Tag: title -#: using-d-i.xml:3454 +#: using-d-i.xml:3455 #, no-c-format msgid "Preparing a medium" msgstr "" #. Tag: para -#: using-d-i.xml:3455 +#: using-d-i.xml:3456 #, no-c-format msgid "Although in some cases the firmware can also be loaded from a partition on a hard disk, the most common method to load firmware will be from some removable medium such as a floppy disk or a USB stick. The firmware files or packages must be placed in either the root directory or a directory named /firmware of the file system on the medium. The recommended file system to use is FAT as that is most certain to be supported during the early stages of the installation." msgstr "" #. Tag: para -#: using-d-i.xml:3465 +#: using-d-i.xml:3466 #, no-c-format msgid "Tarballs and zip files containing current packages for the most common firmware are available from: Just download the tarball or zip file for the correct release and unpack it to the file system on the medium." msgstr "" #. Tag: para -#: using-d-i.xml:3479 +#: using-d-i.xml:3480 #, no-c-format msgid "If the firmware you need is not included in the tarball, you can also download specific firmware packages from the (non-free section of the) archive. The following overview should list most available firmware packages but is not guaranteed to be complete and may also contain non-firmware packages:" msgstr "" #. Tag: para -#: using-d-i.xml:3493 +#: using-d-i.xml:3494 #, no-c-format msgid "It is also possible to copy individual firmware files to the medium. Loose firmware could be obtained for example from an already installed system or from a hardware vendor." msgstr "" #. Tag: title -#: using-d-i.xml:3502 +#: using-d-i.xml:3503 #, no-c-format msgid "Firmware and the Installed System" msgstr "" #. Tag: para -#: using-d-i.xml:3503 +#: using-d-i.xml:3504 #, no-c-format msgid "Any firmware loaded during the installation will be copied automatically to the installed system. In most cases this will ensure that the device that requires the firmware will also work correctly after the system is rebooted into the installed system. However, if the installed system runs a different kernel version from the installer there is a slight chance that the firmware cannot be loaded due to version skew." msgstr "" #. Tag: para -#: using-d-i.xml:3512 +#: using-d-i.xml:3513 #, no-c-format msgid "If the firmware was loaded from a firmware package, &d-i; will also install this package for the installed system and will automatically add the non-free section of the package archive in APT's sources.list. This has the advantage that the firmware should be updated automatically if a new version becomes available." msgstr "" #. Tag: para -#: using-d-i.xml:3520 +#: using-d-i.xml:3521 #, no-c-format msgid "If loading the firmware was skipped during the installation, the relevant device will probably not work with the installed system until the firmware (package) is installed manually." msgstr "" #. Tag: para -#: using-d-i.xml:3527 +#: using-d-i.xml:3528 #, no-c-format msgid "If the firmware was loaded from loose firmware files, the firmware copied to the installed system will not be automatically updated unless the corresponding firmware package (if available) is installed after the installation is completed." msgstr "" -- cgit v1.2.3