[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[d-i doc] 翻訳更新

鍋太郎です。

インストールマニュアルが更新されてましたので、訳を追随しました。
チェックしていただけると助かります。

ja/administrivia/administrivia.xml
ja/appendix/preseed.xml
ja/using-d-i/modules/partman.xml
ja/using-d-i/modules/netcfg.xml
ja/hardware/hardware-supported.xml
ja/boot-installer/parameters.xml
ja/boot-installer/trouble.xml

ja/administrivia/administrivia.xmlのみ文字コードが違いますので、
diffファイルを分けています。

よろしくお願いします。

-- 
+--------------------------------------------------------+
 倉澤 望(鍋太郎) 
 KURASAWA Nozomu (nabetaro)  <nabetaro @ caldron.jp>
 GnuPG FingerPrint:
    C4E5 7063 FD75 02EB E71D  559B ECF6 B9D2 8147 ADFB
+--------------------------------------------------------+

Attachment: d-i-update1214.tar.gz
Description: Binary data

Index: ja/administrivia/administrivia.xml
===================================================================
--- ja/administrivia/administrivia.xml	(ӥ 43350)
+++ ja/administrivia/administrivia.xml	(ȥԡ)
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 39614 -->
+<!-- original version: 43043 -->
 
 <appendix id="administrivia">
  <title>付記</title>
@@ -86,12 +86,12 @@
 <!--
 If you have problems or suggestions regarding this document, you
 should probably submit them as a bug report against the package
-<classname>debian-installer-manual</classname>.  See the
+<classname>installation-guide</classname>.  See the
 <classname>reportbug</classname> package or read the online
 documentation of the <ulink url="&url-bts;">Debian Bug
 Tracking System</ulink>.  It would be nice if you could check the
-<ulink url="&url-bts;debian-installer-manual">open bugs against
-debian-installer-manual</ulink> to see whether your problem has
+<ulink url="&url-bts;installation-guide">open bugs against
+installation-guide</ulink> to see whether your problem has
 already been reported. If so, you can supply additional corroboration
 or helpful information to
 <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>,
@@ -99,14 +99,14 @@
 already-reported bug.
 -->
 この文書に関する問題や提案がある場合には、それらを
-<classname>debian-installer-manual</classname> パッケージに対するバグ報告として
+<classname>installation-guide</classname> パッケージに対するバグ報告として
 提出してください。
 その方法については <classname>reportbug</classname> パッケージや
 <ulink url="&url-bts;">Debian バグ追跡システム</ulink>
 のオンラインドキュメントをご覧ください。
 なお同じ問題が報告済みかどうかを調べるためには、
-<ulink url="&url-bts;debian-installer-manual">
-debian-installer-manual パッケージに関するバグ報告</ulink>
+<ulink url="&url-bts;installation-guide">
+installation-guide パッケージに関するバグ報告</ulink>
 を確認するとよいでしょう。もし同じ問題が報告済みならば、
 <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>
 宛に、確証のための追加情報や有益な情報を提供することができます。
Index: ja/appendix/preseed.xml
===================================================================
--- ja/appendix/preseed.xml	(ӥ 43350)
+++ ja/appendix/preseed.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 42036 -->
+<!-- original version: 42982 -->
 
 <!--
 Be carefull with the format of this file as it is parsed to generate
@@ -30,10 +30,10 @@
 <para>
 
 <!--
-This appendix explains the intricacies of preseeding answers to questions in
-&d-i; to automate your installation.
+This appendix explains how to preseed answers to questions in &d-i; to
+automate your installation.
 -->
-Ͽ preseed Ԥޤ
+Ͽ preseed ˡޤ
  &d-i; μ˲Ƥ󥹥ȡưΤǤ
 
 </para><para>
@@ -81,9 +81,7 @@
 <firstterm>network</firstterm>. Initrd preseeding will work with any
 installation method and supports preseeding of more things, but it requires
 the most preparation. File and network preseeding each can be used with
-different installation methods. With file and network preseeding the first
-few installer questions cannot be preseeded because the preconfiguration
-file is only loaded after they have been asked.
+different installation methods.
 -->
 preseed Ѥˤϡ
 <firstterm>initrd</firstterm>, <firstterm>ե</firstterm>,
@@ -92,9 +90,6 @@
 ¿ preseed 򥵥ݡȤޤ̤νɬפǤ
 ե preseed ͥåȥ preseed ϡ
 줾쥤󥹥ȡˡۤʤ˻Ѥޤ
-ե preseed ͥåȥ preseed Ǥϡ
-ե뤬ɤ߹ޤˤĤ䤵Ƥޤᡢ
-μ preseed ˴ޤ뤳ȤǤޤ
 
 </para><para>
 
@@ -122,7 +117,18 @@
   <entry>CD/DVD</entry>
   <entry>yes</entry>
   <entry>yes</entry>
-  <entry>no</entry>
+  <entry>yes<footnote id='apx-ps-net'>
+
+  <para>
+<!--
+  but only if you have network access, and set <literal>preseed/url</literal>
+  appropriately
+-->
+  ͥåȥԤǤʤ
+  Ŭڤ <literal>preseed/url</literal> ꤹ硣
+  </para>
+
+  </footnote></entry>
 </row><row>
   <entry>netboot</entry>
   <entry>yes</entry>
@@ -135,7 +141,7 @@
   <entry>hd-media <phrase condition="bootable-usb">(USB ƥåޤ)</phrase></entry>
   <entry>yes</entry>
   <entry>yes</entry>
-  <entry>no</entry>
+  <entry>yes<footnoteref linkend='apx-ps-net'/></entry>
 </row><row condition="supports-floppy-boot">
 <!--
   <entry>floppy based (cd-drivers)</entry>
@@ -143,7 +149,7 @@
   <entry>եåԡ١ (CD ɥ饤)</entry>
   <entry>yes</entry>
   <entry>yes</entry>
-  <entry>no</entry>
+  <entry>yes<footnoteref linkend='apx-ps-net'/></entry>
 </row><row condition="supports-floppy-boot">
 <!--
   <entry>floppy based (net-drivers)</entry>
@@ -183,32 +189,38 @@
 </para><para>
 
 <!--
-In practical terms this means for file and network preseeding that the
-questions about language, country and keyboard selection will already have
-been asked. For network preseeding add to that any questions related to
-network configuration. Some other questions that are only displayed
-at medium or low priority (like the first hardware detection run) will
-also already have been processed.
--->
-ºݤä򤹤ȡե preseed ͥåȥ preseed Ǥϡ
-졢񡢥ܡɤˤĤƼϡˤƤޤäƤޤ
-ͥåȥ preseed Ǥϡ˥ͥåȥˤĤƤäƤ
-¾ͥ٤פפǤɽʤ
-(ϤΥϡɥФʤ) ϡ˽ƤޤäƤޤ
-
-</para><para>
-
-<!--
 Obviously, any questions that have been processed before the
-preconfiguration file is loaded cannot be preseeded.
-<xref linkend="preseed-bootparms"/> offers a way to avoid these
-questions being asked.
+preconfiguration file is loaded cannot be preseeded (this will include
+questions that are only displayed at medium or low priority, like the
+first hardware detection run). <xref linkend="preseed-bootparms"/>
+offers a way to avoid these questions being asked.
 -->
 ޤǤʤե뤬ɤ߹ޤ˽ϡ
 preseed Ǥޤ
+(ǽΥϡɥФΤ褦ˡ
+ͥ٤ǤɽʤޤǤޤ)
 <xref linkend="preseed-bootparms"/> Ǥϡ
 ä䤬Фʤ褦ˤˡ󶡤Ƥޤ
 
+</para><para>
+
+<!--
+In order to avoid the questions that would normally appear before the
+preseeding occurs, you can start the installer in <quote>auto</quote>
+mode. This delays questions that would normally be asked too early for
+preseeding (i.e. language, country and keyboard selection) until after
+the network comes up, thus allowing them to be preseeded. It also runs
+the installation in crtitical priority, which avoids many unimportant
+questions. See <xref linkend="preseed-auto"/> for details.
+-->
+preseed ưˡ̾︽򤹤Τˡ
+<quote>ư</quote> ⡼ɤǥ󥹥ȡưǤޤ
+ˤͥåȥ꤬ޤǡpreseed ˹Ԥ 
+(졢񡢥ܡʤ) ٤餻preseed ˤμޤޤ
+ޤ󥹥ȡͥ٤ǽפǹԤᡢ
+̤ˤפǤʤǤޤ
+ܺ٤ <xref linkend="preseed-auto"/> 
+
 </para>
   </sect2>
 
@@ -223,14 +235,13 @@
 Although most questions used by &d-i; can be preseeded using this method,
 there are some notable exceptions. You must (re)partition an entire disk
 or use available free space on a disk; it is not possible to use existing
-partitions. You currently cannot use preseeding to set up RAID.
+partitions. 
 -->
 &d-i; ǹԤΤۤȤɤϤˡ preseed Ǥޤ
 Ĥܤ٤㳰ޤ
 ǥΤ () ѡƥʬ䤹뤫
 ǥζΰѤʤФʤޤ
 Ĥޤ¸ΥѡƥѤǤʤȸȤǤ
-ޤߡRAID Υåȥåפ preseed ѤǤޤ
 
 </para>
   </sect2>
@@ -257,7 +268,7 @@
 
 </para>
 
-<itemizedlist>
+<itemizedlist spacing="compact">
 <listitem><para>
   string: allows the user to type any value
 </para></listitem>
@@ -297,76 +308,9 @@
 </para>
   </sect2>
 -->
+ </sect1>
 
-  <sect2 id="preseed-hooks">
-<!--
-  <title>Running custom commands during the installation</title>
--->
-  <title>󥹥ȡǤΥॳޥɤμ¹</title>
-<para>
 
-<!--
-A very powerful and flexible option offered by the preconfiguration tools
-is the ability to run commands or scripts at certain points in the
-installation. See <xref linkend="preseed-shell"/> for details.
--->
-ġ󶡤롢ȤƤ⶯Ϥǽʥץˡ
-󥹥ȡηޤäǥޥɤ䥹ץȤ¹Ԥ뵡ǽޤ
-ܺ٤ <xref linkend="preseed-shell"/> 
-
-</para>
-
-<itemizedlist>
-<listitem><para>
-<!--
-  <userinput>preseed/early_command</userinput>: is run as soon as the
-  preconfiguration file has been loaded
--->
-  <userinput>preseed/early_command</userinput>: ϡ
-  ե뤬ɤ߹ޤȤ˼¹Ԥޤ
-</para></listitem>
-<listitem><para>
-<!--
-  <userinput>preseed/late_command</userinput>: is run just before the reboot
-  at the end of the install, but before the <filename>/target</filename>
-  filesystem has been unmounted
--->
-  <userinput>preseed/late_command</userinput>: ϡ
-  󥹥ȡ뤬äƺƵưľ
-  <filename>/target</filename> ե륷ƥ򥢥ޥȤ˼¹Ԥޤ
-</para></listitem>
-</itemizedlist>
-
-  </sect2>
-
-  <sect2 id="preseed-seenflag">
-<!--
-  <title>Using preseeding to change default values</title>
--->
-  <title>ǥեͤѹ˴ؤ preseed </title>
-<para>
-
-<!--
-It is possible to use preseeding to change the default answer for a
-question, but still have the question asked. To do this the
-<firstterm>seen</firstterm> flag must be reset to <quote>false</quote> after
-setting the value for a question.
--->
-֤ФǥեȤβѹΤ preseed ѤǤޤ
-ˤϡͤꤷǡ
-<firstterm>seen</firstterm> ե饰 <quote>false</quote>
-ꤷʤФʤޤ
-
-</para>
-
-<informalexample><screen>
-d-i foo/bar string value
-d-i foo/bar seen false
-</screen></informalexample>
-
-  </sect2>
- </sect1>
-
  <sect1 id="preseed-using">
 <!--
  <title>Using preseeding</title>
@@ -375,16 +319,16 @@
 <para>
 
 <!--
-Of course you will first need to create a preconfiguration file and place it in
+You will first need to create a preconfiguration file and place it in
 the location from where you want to use it. Creating the preconfiguration file
 is covered later in this appendix. Putting it in the correct location is fairly
 straightforward for network preseeding or if you want to read the file off
 a floppy or usb-stick. If you want to include the file on a CD or DVD, you
 will have to remaster the ISO image. How to get the preconfiguration file
 included in the initrd is outside the scope of this document; please consult
-the developers documentation for &d-i;.
+the developers' documentation for &d-i;.
 -->
-եǽ˺Ѥ֤ɬפޤ
+եǽ˺Ѥ֤ɬפޤ
 եκϿǸۤɰޤ
 ͥåȥ preseed ξ䡢
 եեåԡ USB ƥåɤ߹硢
@@ -514,20 +458,382 @@
 <filename>preseed/file</filename>  <filename>file</filename> 
 ṳ̂Ǥ뤳ȤդƤ
 
+</para>
+  </sect2>
+
+  <sect2 id="preseed-bootparms">
+<!--
+  <title>Using boot parameters to preseed questions</title>
+-->
+  <title>preseed 䤹֡ȥѥ᡼</title>
+<para>
+
+<!--
+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. 
+-->
+ե preseed γʳǻѤǤʤǤ⡢
+preseed ͤ򥤥󥹥ȡ鵯ưΥޥɥ饤Ϳ뤳Ȥǡ
+󥹥ȡưǹԤޤ
+
 </para><para>
 
 <!--
-While you're at it, you may want to add a boot parameter
-<userinput>debconf/priority=critical</userinput>. This will avoid most
-questions even if the preseeding below misses some.
+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.
 -->
-¹Ԥˤꡢ֡ȥѥ᡼
-<userinput>debconf/priority=critical</userinput> ɲä⤷ޤ
-preseed ǤĤʲϳ餷Ƥ⡢
-ۤȤɤμ䤬ɽʤʤޤ
+preseed Ѥꤷؤꤷˤ⡢
+֡ȥѥ᡼Ѥޤ
+ͭѤʻˡΥץ뤬Υޥ˥奢̤ξˤޤ
 
+</para><para>
+
+<!--
+To set a value to be used inside &d-i;, just pass
+<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>
+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 <firstterm>owner</firstterm> of the variable as in
+<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>.
+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.
+-->
+&d-i; ǻѤͤ򥻥åȤˤϡ
+<userinput><replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>
+Τ褦Ͽˤ preseed ѿϤǤ
+ͤåȥƥΥѥåꤹ뤳Ȥ硢
+<userinput><replaceable>owner</replaceable>:<replaceable>path/to/variable</replaceable>=<replaceable>value</replaceable></userinput>
+ǻѤ褦ѿ <firstterm>owner</firstterm> 
+餫Ѱդɬפޤ
+owner ꤷʤ硢
+ѿͤϥåȥƥ debconf ǡ١˥ԡ줺
+ϢѥåѤޤ
+
+</para><para>
+
+<!--
+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.  In
+particular, the <literal>preseed/url</literal> variable has been
+aliased as <literal>url</literal> and has some extra magic to allow
+shortened urls to be used. Another example is the <literal>tasks</literal>
+alias, which translates to <literal>tasksel:tasksel/first</literal>.
+-->
+֡ȥץץȤˤ褯Ѥѿˤϡ
+ûꥢ뤳ȤդƤ
+ͭʥꥢϡܥץǴѿ̾˻ѤƤޤ
+äˡ<literal>preseed/url</literal> ѿˤ <literal>url</literal> 
+Ȥꥢꡢû URL Ȥ뤳ȤΤ뵻Ĥޤ
+⤦ġ<literal>tasks</literal> Ȥꥢꡢ
+ <literal>tasksel:tasksel/first</literal> Ѵޤ
+
+</para><para>
+
+<!--
+A <quote>-\-</quote> in the boot options has special meaning. Kernel
+parameters that appear after the last <quote>-\-</quote> 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.
+-->
+֡ȥץ <quote>--</quote> ̤ʰ̣ޤ
+Ǹ <quote>--</quote> ³ͥѥ᡼ȡ
+(󥹥ȡ餬ݡȤ֡ȥξ) 
+󥹥ȡѤߤΥ֡ȥ˥ԡޤ
+󥹥ȡϡ(ꥪץΤ褦) ץǧȡ
+ưŪ˥ե륿ݤޤ
+
 </para>
+<note><para>
+
+<!--
+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.)
+-->
+ߤ Linux ͥ (2.6.9 ʹ) Ǥϡ
+ (󥹥ȡ餬ǥեȤǻꤹ륪ץޤ) 
+ޥɥ饤󥪥ץ 32 ġĶץ 32 ļޤ
+οĶȡͥϥѥ˥å (å) Ƥޤޤ
+(ΥͥǤϤοäȾʤǤ)
+
+</para></note>
+<para>
+
+<!--
+For most installations some of the default options in your bootloader
+configuration file, like <literal>vga=normal</literal>, may be safely
+removed which may allow you to add more options for preseeding.
+-->
+ۤȤɤΥ󥹥ȡǤϡ֡ȥեˤ
+(<literal>vga=normal</literal> Τ褦) 
+ǥեȥץ˺Ǥ뤫⤷ޤ
+ˤ preseed ѤˤäȥץɲäǤޤ
+
+</para>
+<note><para>
+
+<!--
+It may not always be possible to specify values with spaces for boot
+parameters, even if you delimit them with quotes.
+-->
+֡ȥѥ᡼˶ޤͤꤹΤϡ
+ǶڤäȤƤ⤤Ĥ⤦ޤȤϸ¤ޤ
+
+</para></note>
   </sect2>
+  <sect2 id="preseed-auto">
+<!--
+  <title>Auto mode</title>
+-->
+  <title>ư⡼</title>
+<para>
+
+<!--
+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:
+-->
+ޤץʥޥɥ饤֡ȥץץȤͿ
+Ǥդʣʥޥư󥹥ȡФƹԤ 
+Debian Installer εǽޤ
+ΤˡʲΥץ֡ȥץץȤ˻Ѥޤ
+
+<informalexample><screen>
+auto url=autoserver
+</screen></informalexample>
+
+<!--
+This relies on there being a DHCP server that will get the machine to
+the point where <literal>autoserver</literal> can be resolved by DNS,
+perhaps after adding the local domain if that was provided by DHCP.
+If this was done at a site where the domain is
+<literal>example.com</literal>, and they have a reasonably sane DHCP
+setup, it would result in the preseed file being retrieved from
+<literal>http://autoserver.example.com/d-i/etch/./preseed.cfg</literal>.
+-->
+ϡDNS  <literal>autoserver</literal> ̾Ǥ 
+(餯 DHCP ǥɥᥤɲø)
+Υޥ DHCP ФǤ뤳ȤˤƤޤ
+<literal>example.com</literal> ȤɥᥤΥȤ
+̤ΤޤȤ DHCP ꤷƤС
+<literal>http://autoserver.example.com/d-i/etch/./preseed.cfg</literal>
+顢preseed ե褦ˤʤޤ
+
+</para><para>
+
+<!--
+The path segment of that comes from
+<literal>auto-install/defaultroot</literal>, which includes the
+directory <literal>etch</literal> by default to allow future versions
+to specify their own codename to let people migrate forwards in a
+controlled manner.  The <literal>/./</literal> 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 <literal>preseed/run</literal> to
+<literal>/scripts/late_command.sh</literal> then the file will be
+fetched from
+<literal>http://autoserver.example.com/d-i/etch/./scripts/late_command.sh</literal>.
+-->
+ΥѥȤ <literal>auto-install/defaultroot</literal> ͳ褷ޤ
+ˤϡΥСǥɥ͡ꤷưܹԤƤ褦ˡ
+ǥեȤ <literal>etch</literal> ǥ쥯ȥ꤬ޤޤƤޤ
+<literal>/./</literal> ϡθ³ѥꤹ褦ˡ
+롼ȤХѥ򼨤ޤ (preseed/include  preseed/run ǻ)
+ˤꡢե URL/ ǻϤޤѥ
+ preseed Ĥä꤫ХѥǥեǤޤ
+ץȤγع¤˿˰ưǤ 
+(㤨 ֥ФdzϤUSB ƥå˥ԡ)
+ݡ֥ʥץȤΤǤ
+ΥץǤϡpreseed ե <literal>preseed/run</literal>  
+<literal>/scripts/late_command.sh</literal> ꤵƤ硢
+<literal>http://autoserver.example.com/d-i/etch/./scripts/late_command.sh</literal>
+եޤ
+
+</para><para>
+
+<!--
+If there is no local DHCP or DNS infrastructure, or if you
+do not want to use the default path to the preseed.cfg, you can still
+use an explicit url, and if you don't use the <literal>/./</literal>
+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:
+-->
+긵 DHCP  DNS Υե餬ʤ䡢
+preseed.cfg ΥǥեȥѥѤʤǤ⡢
+Ȥ URL ѤǤ<literal>/./</literal> ǤѤʤϡ
+ѥγǤޤ (㤨 URL  3 ܤ /)
+ʲϡ긵Υͥåȥե餫ɬפʪΥץǤ
+
+<informalexample><screen>
+auto url=<replaceable>http://192.168.1.2/path/to/mypreseed.file</replaceable>
+</screen></informalexample>
+
+<!--
+The way this works is that:
+-->
+ˡϼΤ褦ưޤ
+<itemizedlist spacing="compact">
+<listitem><para>
+<!--
+if the URL is missing a protocol, http is assumed,
+-->
+URL Ĥʤ硢http Ȳꤷޤ
+</para></listitem>
+<listitem><para>
+<!--
+if the hostname section contains no periods, it has the domain derived
+from DHCP appended to it, and
+-->
+ۥ̾˥ԥꥪɤʤСDHCP Фɲäޤ
+</para></listitem>
+<listitem><para>
+<!--
+if there's no <literal>/</literal>'s after the hostname, then the default
+path is added.
+-->
+ۥ̾θ <literal>/</literal> ʤСǥեȥѥɲäޤ
+</para></listitem>
+</itemizedlist>
+
+</para><para>
+
+<!--
+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 any scripts that might be specified <literal>preseed/run</literal>
+settings in the loaded preseed file.  At present, the only example of
+this is <literal>auto-install/classes</literal>, which has an alias
+<literal>classes</literal>.  This can be used thus:
+-->
+URL ꤹΤ˲äơ
+&d-i; Ȥο񤤤ˤľܱƶʤɲäǤޤ
+ɤ߹ preseed ե <literal>preseed/run</literal> ǻꤷ
+ΥץȤˤϤȤǤޤ
+ߤΤȤ<literal>classes</literal> Ȥꥢġ
+<literal>auto-install/classes</literal> ΥץΤߤǤ
+ʲΤ褦˻Ѥޤ
+
+<informalexample><screen>
+auto url=<replaceable>example.com</replaceable> classes=<replaceable>class_A;class_B</replaceable>
+</screen></informalexample>
+
+<!--
+The classes could for example denote the type of system to be installed,
+or the localization to be used.
+-->
+classes ˤϤΥץǤϡ󥹥ȡ뤹륷ƥΥפ䡢
+ϰ貽ꤹΤ˻ѤǤޤ
+
+</para><para>
+
+<!--
+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 <literal>auto-install/style</literal> which is then used
+in your scripts.  If you feel the need to do this, please mention it on
+the <email>debian-boot@lists.debian.org</email> mailing list so that we
+can avoid namespace conflicts, and perhaps add an alias for the parameter
+for you.
+-->
+γǰϤĥǤ⤷硢
+auto-install ֤̾ѤΤǤ
+Ǥ顢ˤʤΥץȤǻѤ 
+<literal>auto-install/style</literal> Τ褦ʪ⤷ޤ
+줬ɬפȻפΤʤ顢֤̾ξͤ򤱤뤿
+<email>debian-boot@lists.debian.org</email> ᡼󥰥ꥹȤƤƤ
+餯ѥ᡼Υꥢɲäޤ
+
+</para><para>
+
+<!--
+The <literal>auto</literal> boot label is not yet defined on all
+architectures. The same effect may be achieved by simply adding the two
+parameters <literal>auto=true priority=critical</literal> to the kernel
+command line.  The <literal>auto</literal> parameter is an alias for
+<literal>auto-install/enabled</literal> and controls the delay of the
+locale and keyboard questions until after there has been a chance to
+preseed them, while <literal>priority</literal> is an alias for
+<literal>preseed/priority</literal> and setting it to
+<literal>critical</literal> stops any questions with a lower priority
+from being asked.
+-->
+<literal>auto</literal> ֡ȥ٥ϡ
+ɤΥƥǤޤƤޤ
+ͥΥޥɥ饤ˡñ˥ѥ᡼ 2  
+<literal>auto=true priority=critical</literal> ɲäȡ
+Ʊ̤ޤ
+<literal>auto</literal> ѥ᡼ <literal>auto-install/enabled</literal> 
+Υꥢǡ䥭ܡɤμ preseed ǹԤ褦٤餻ޤ
+ޤ<literal>priority</literal>  <literal>preseed/priority</literal> 
+Υꥢǡ<literal>critical</literal> ꤹȡ
+ͥ٤㤤롣
+
+
+</para><para>
+
+<!--
+Additional options that may be of interest while attempting to
+automate an install while using DHCP are: <literal>interface=auto
+netcfg/dhcp_timeout=60</literal> which makes the machine choose the
+first viable NIC and be more patient about getting a reply to its
+DHCP query.
+-->
+DHCP Ѥƥ󥹥ȡμưԤݤˡ
+Ϣɲåץϰʲ̤Ǥ<literal>interface=auto
+netcfg/dhcp_timeout=60</literal> ϥޥ󤬺ǽλѲǽ NIC 򤷡
+DHCP 䤤碌ФäȲԤĤ褦ˤʤޤ
+
+</para>
+  </sect2>
+
+  <sect2 id="preseed-aliases">
+<!--
+  <title>Aliases useful with preseeding</title>
+-->
+  <title>preseed ѤǤ륨ꥢ</title>
+<para>
+
+<!--
+The following aliases can be useful when using (auto mode) preseeding.
+-->
+ʲΥꥢ (ư⡼) preseed ѤݤѤǤޤ
+
+</para>
+
+<!-- Setting column width does not seem to work; use non-breaking spaces
+     to separate columns a bit -->
+<informaltable frame="none">
+<tgroup cols="2"><tbody>
+<row><entry>auto</entry><entry>auto-install/enabled</entry></row>
+<row><entry>classes</entry><entry>auto-install/classes</entry></row>
+<row><entry>fb</entry><entry>debian-installer/framebuffer</entry></row>
+<row><entry>locale</entry><entry>debian-installer/locale</entry></row>
+<row><entry>priority</entry><entry>debconf/priority</entry></row>
+<row><entry>file</entry><entry>preseed/file</entry></row>
+<row><entry>url</entry><entry>preseed/url</entry></row>
+<row><entry>hostname&nbsp;&nbsp;&nbsp;</entry><entry>netcfg/get_hostname</entry></row>
+<row><entry>domain</entry><entry>netcfg/get_domain</entry></row>
+<row><entry>interface</entry><entry>netcfg/choose_interface</entry></row>
+<row><entry>suite</entry><entry>mirror/suite</entry></row>
+</tbody></tgroup>
+</informaltable>
+
+  </sect2>
+
   
   <sect2 id="preseed-dhcp">
 <!--
@@ -593,112 +899,6 @@
 
 </para>
   </sect2>
-
-  <sect2 id="preseed-bootparms">
-<!--
-  <title>Using boot parameters to supplement preseeding</title>
--->
-  <title>preseed ­֡ȥѥ᡼</title>
-<para>
-
-<!--
-Some parts of the installation process cannot be automated using some forms
-of preseeding because the questions are asked before the preconfiguration
-file is loaded. For example, if the preconfiguration file is downloaded over
-the network, the network setup must be done first. One reason to use initrd
-preseeding is that it allows preseeding of even these early steps of the
-installation process.
--->
-󥹥ȡץΤΤʬμϡ
-ե뤬ɤ߹ޤˤʤ뤿ἫưǤޤ
-㤨Сեͥåȥɤ硢
-ޤͥåȥ꤬λƤʤФʤޤ
-󥹥ȡץᤤʳ preseed ǤȤΤ
-initrd preseed ѤͳΤҤȤĤǤ
-
-</para><para>
-
-<!--
-If a preconfiguration file cannot be used to preseed some steps, the install
-can still be fully automated, since you can pass preseed values to the kernel
-on the command line. Just pass <userinput>path/to/var=value</userinput>
-for any of the preseed variables listed in the examples.
--->
-ե preseed ˻ѤǤʤƥåפäƤ⡢
-ޥɥ饤󤫤 preseed ͤ򥫡ͥϤΤǡ
-ޤ˼ưǤޤ
-<userinput>path/to/var=value</userinput> Ȥ褦ˡ
-ץˤ preseed ѿϤƤ
-
-</para><para>
-
-<!--
-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.
--->
-֡ȥץץȤˤ褯Ѥѿˤϡ
-ûꥢ뤳ȤդƤ
-ͭʥꥢϡܥץǴѿ̾˻ѤƤޤ
-
-</para><para>
-
-<!--
-A <quote>-\-</quote> in the boot options has special meaning.
-Kernel parameters that appear after it will be copied into the installed
-bootloader configuration (if supported by the installer for the
-bootloader). Note that the <quote>-\-</quote> may already be
-present in the default boot parameters.
--->
-֡ȥץ <quote>--</quote> ̤ʰ̣ޤ
-³ͥѥ᡼ȡ
-󥹥ȡѤߤΥ֡ȥ˥ԡޤ 
-(󥹥ȡ餬ݡȤ֡ȥξ)
-<quote>--</quote> ϡǥեȥ֡ȥѥ᡼ǡ
-Ǥ˻ѤƤ뤳ȤդƤ
-
-</para>
-<note><para>
-
-<!--
-The 2.4 kernel accepts a maximum of 8 command line options and
-8 environment options (including any options added by default for the
-installer). If these numbers are exceeded, 2.4 kernels will drop any
-excess options and 2.6 kernels will panic. For kernel 2.6.9 and later,
-you can use 32 command line options and 32 environment options.
--->
-ͥ 2.4 ǤϺ (󥹥ȡ餬ǥեȤǻꤹ륪ץޤ) 
-ޥɥ饤󥪥ץ 8 ġĶץ 8 ļޤ
-οĶȡͥ 2.4 ǤĶᤷץꤳܤƤޤ
-ͥ 2.6 Ǥϥѥ˥åƤޤޤ
-ͥ 2.6.9 ʹߤǤϡޥɥ饤󥪥ץ 32 ġ
-Ķץ 32 ļޤ
-
-</para></note>
-<para>
-
-<!--
-For most installations some of the default options in your bootloader
-configuration file, like <literal>vga=normal</literal>, may be safely
-removed which may allow you to add more options for preseeding.
--->
-ۤȤɤΥ󥹥ȡǤϡ֡ȥեˤ
-(<literal>vga=normal</literal> Τ褦) 
-ǥեȥץ˺Ǥ뤫⤷ޤ
-ˤ preseed ѤˤäȥץɲäǤޤ
-
-</para>
-<note><para>
-
-<!--
-It may not always be possible to specify values with spaces for boot
-parameters, even if you delimit them with quotes.
--->
-֡ȥѥ᡼˶ޤͤꤹΤϡ
-ǶڤäȤƤ⤤Ĥ⤦ޤȤϸ¤ޤ
-
-</para></note>
-  </sect2>
  </sect1>
 
  <sect1 id="preseed-creating">
@@ -1170,8 +1370,7 @@
 partition existing free space on a disk or a whole disk. The layout of the
 disk can be determined by using a predefined recipe, a custom recipe from
 a recipe file or a recipe included in the preconfiguration file. It is
-currently not possible to partition multiple disks using preseeding nor to
-set up RAID.
+currently not possible to partition multiple disks using preseeding.
 -->
 ϡɥǥΥѡƥʬ preseed ѤΤϡ
 <classname>partman-auto</classname> ǥݡȤƤ뵡ǽ˸ꤵƤޤ
@@ -1179,8 +1378,8 @@
 ǥ쥤Ȥϡ餫쥷ԡ
 쥷ԥեˤ륫쥷ԡ
 ե˽񤤤쥷ԤǤޤ
-ߤΤȤѡƥ preseed ѤʣΥǥ뤳Ȥ䡢
-RAID ꤹ뤳ȤϤǤޤ
+ߤΤȤѡƥ preseed 
+ѤʣΥǥ뤳ȤϤǤޤ
 
 </para>
 
@@ -1415,7 +1614,9 @@
 #d-i apt-setup/local0/comment string local server
 # Enable deb-src lines
 #d-i apt-setup/local0/source boolean true
-# URL to the public key of the local repository
+# URL to the public key of the local repository; you must provide a key or
+# apt will complain about the unauthenticated repository and so the
+# sources.list line will be left commented out
 #d-i apt-setup/local0/key string http://local.server/key
 </screen></informalexample>
 
Index: ja/using-d-i/modules/partman.xml
===================================================================
--- ja/using-d-i/modules/partman.xml	(ӥ 43350)
+++ ja/using-d-i/modules/partman.xml	(ȥԡ)
@@ -221,13 +221,13 @@
 </para><para arch="ia64">
 
 <!--
-If you choose guided partitioning for your IA64 system, there
+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.
 -->
-IA64 ƥФƥɥѡƥʬԤȷ᤿硢
+IA-64 ƥФƥɥѡƥʬԤȷ᤿硢
 EFI ֡ȥѤˡ FAT16 εưǽե륷ƥǥեޥåȤ줿
 ɲåѡƥ󤬤ϤǤ
 ư EFI ֡ȥѡƥȤƥѡƥ򥻥åȥåפ褦
Index: ja/using-d-i/modules/netcfg.xml
===================================================================
--- ja/using-d-i/modules/netcfg.xml	(ӥ 43350)
+++ ja/using-d-i/modules/netcfg.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 23058 -->
+<!-- original version: 43043 -->
 
    <sect3 id="netcfg">
    <title>ͥåȥ</title>
@@ -88,9 +88,7 @@
 negation of the netmask. It will also guess your gateway.  If you
 can't find any of these answers, use the system's guesses &mdash; you
 can change them once the system has been installed, if necessary, by
-editing <filename>/etc/network/interfaces</filename>.  Alternatively,
-you can install <classname>etherconf</classname>, which will step you
-through your network setup.
+editing <filename>/etc/network/interfaces</filename>.
 -->
 Ĥ뤫ĤʤϤȤ⤫Ūܺ٤ϼڤ˸Ĥޤ
 ץǤϡͥåȥ IP ɥ쥹
@@ -102,8 +100,6 @@
 ١ƥ򥤥󥹥ȡ뤷ǡ
 ɬפʤ <filename>/etc/network/interfaces</filename> Խơ
 ѹ뤳ȤǤޤ
-¾ˤϡͥåȥɤäƹԤ <classname>etherconf</classname> 
-򥤥󥹥ȡ뤹뤳ȤǤޤ
 
 </para></note>
    </sect3>
Index: ja/hardware/hardware-supported.xml
===================================================================
--- ja/hardware/hardware-supported.xml	(ӥ 43350)
+++ ja/hardware/hardware-supported.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 40543 -->
+<!-- original version: 43032 -->
 
  <sect1 id="hardware-supported">
 <!--
@@ -92,25 +92,24 @@
 
 <row>
 <!--
-  <entry morerows="2">ARM and StrongARM</entry>
-  <entry morerows="2">arm</entry>
+  <entry morerows="3">ARM and StrongARM</entry>
+  <entry morerows="3">arm</entry>
   <entry>Netwinder and CATS</entry>
   <entry>netwinder</entry>
 -->
-  <entry morerows="2">ARMStrongARM</entry>
-  <entry morerows="2">arm</entry>
+  <entry morerows="3">ARMStrongARM</entry>
+  <entry morerows="3">arm</entry>
   <entry>NetwinderCATS</entry>
   <entry>netwinder</entry>
 </row><row>
-  <entry>Linksys NSLU2</entry>
-  <entry>nslu2</entry>
+  <entry>Intel IOP32x</entry>
+  <entry>iop32x</entry>
 </row><row>
-<!--
+  <entry>Intel IXP4xx</entry>
+  <entry>ixp4xx</entry>
+</row><row>
   <entry>RiscPC</entry>
   <entry>rpc</entry>
--->
-  <entry>RiscPC</entry>
-  <entry>rpc</entry>
 </row>
 
 <row>
Index: ja/boot-installer/parameters.xml
===================================================================
--- ja/boot-installer/parameters.xml	(ӥ 43350)
+++ ja/boot-installer/parameters.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 42485 -->
+<!-- original version: 42824 -->
 
  <sect1 id="boot-parms"><title>֡ȥѥ᡼</title>
 <para>
@@ -584,7 +584,22 @@
 </para></listitem>
 </varlistentry>
 
-<varlistentry>
+<varlistentry condition="g-i">
+<term>mouse/left</term>
+<listitem><para>
+
+<!--
+For the gtk frontend (graphical installer), users can switch the mouse to
+left-handed operation by setting this parameter to <userinput>true</userinput>.
+-->
+gtk եȥ (ե륤󥹥ȡ) Ѥˡ
+Υѥ᡼ <userinput>true</userinput> Ȥȡ
+ޥ򺸼褦ڤؤޤ
+
+</para></listitem>
+</varlistentry>
+
+<varlistentry condition="g-i">
 <term>directfb/hw-accel</term>
 <listitem><para>
 
@@ -593,7 +608,7 @@
 is disabled by default. To enable it, set this parameter to
 <userinput>true</userinput> when booting the installer.
 -->
-gtk եȥ (ե륤󥹥ȡ) Τˡ
+gtk եȥ (ե륤󥹥ȡ) Ѥˡ
 directfb Υϡɥ졼ϡǥեȤ̵ȤʤäƤޤ
 ͭˤˤϡ󥹥ȡεưκݡ
 Υѥ᡼ <userinput>true</userinput> ꤷƤ
Index: ja/boot-installer/trouble.xml
===================================================================
--- ja/boot-installer/trouble.xml	(ӥ 43350)
+++ ja/boot-installer/trouble.xml	(ȥԡ)
@@ -1,12 +1,351 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 39614 -->
+<!-- original version: 42532 -->
 
  <sect1 id="boot-troubleshooting">
  <title>󥹥ȡץΥȥ֥륷塼ƥ</title>
 <para>
 </para>
 
+  <sect2 arch="not-s390" id="unreliable-cd">
+<!--
+  <title>CD-ROM Reliability</title>
+-->
+  <title>CD-ROM ο</title>
+<para>
+
+<!--
+Sometimes, especially with older CD-ROM drives, the installer may fail
+to boot from a CD-ROM. The installer may also &mdash; even after booting
+successfully from CD-ROM &mdash; fail to recognize the CD-ROM or return
+errors while reading from it during the installation.
+-->
+ä˸Ť CD-ROM ɥ饤֤ξ硢
+CD-ROM Υ󥹥ȡεư˼Ԥ뤫⤷ޤ
+ޤ󥹥ȡ ( CD-ROM 鵯ưƤ) CD-ROM ǧʤäꡢ
+󥹥ȡ桢 CD ɤ߹ߤǥ顼֤ǽ⤢ޤ
+
+</para><para>
+
+<!--
+There are a many different possible causes for these problems. We can
+only list some common issues and provide general suggestions on how to
+deal with them. The rest is up to you.
+-->
+θ͡ʤȤͤޤ
+Ū󤲤ơŪнˡ󶡤뤳ȤǤޤ
+ϤʤǤ
+
+</para><para>
+
+<!--
+There are two very simple things that you should try first.
+-->
+ޤϤ˻Τϡʲ 2 Ǥ
+
+<itemizedlist>
+<listitem><para>
+
+<!--
+If the CD-ROM does not boot, check that it was inserted correctly and that
+it is not dirty.
+-->
+CD-ROM ưʤ硢Ƥ뤫
+ƤʤǧƤ
+
+</para></listitem>
+<listitem><para>
+
+<!--
+If the installer fails to recognize a CD-ROM, try just running the option
+<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice>
+a second time. Some DMA related isses with older CD-ROM drives are known to
+be resolved in this way.
+-->
+󥹥ȡ餬CD-ROMǧʤ硢 
+<menuchoice> <guimenuitem>Detect and mount CD-ROM</guimenuitem> </menuchoice>
+¹ԤƤ
+Ť CD-ROM ɥ饤֤ DMA ˴Ϣϡ
+ˡDz褹뤳ȤΤƤޤ
+
+</para></listitem>
+</itemizedlist>
+
+</para><para>
+
+<!--
+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.
+-->
+Ǥưʤ硢ʲˤ뤳ȤƤߤƤ
+ۤȤɤ (Ǥ⤹٤ƤǤϤʤ) Ƥ CD-ROM  DVD ξͭǤ
+ñ CD-ROM ȤѸѤƤޤ
+
+</para><para>
+
+<!--
+If you cannot get the installation working from CD-ROM, try one of the
+other installation methods that are available.
+-->
+CD-ROM 饤󥹥ȡ뤬ǤʤС
+¾Υ󥹥ȡˡƤߤƤ
+
+</para>
+
+  <sect3>
+<!--
+  <title>Common issues</title>
+-->
+  <title>̤</title>
+
+<itemizedlist>
+  <listitem><para>
+
+<!--
+Some older CD-ROM drives do not support reading from discs that were burned
+at high speeds using a modern CD writer.
+-->
+Ť CD-ROM ɥ饤֤ˤϡǶ CD 饤ǻѤ褦ʡ
+®ǾƤ ǥɤ߹ߤ򥵥ݡȤƤʤʪޤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+If your system boots correctly from the CD-ROM, it does not necessarily
+mean that Linux also supports the CD-ROM (or, more correctly, the controller
+that your CD-ROM drive is connected to).
+-->
+ƥब CD-ROM ưȤäơ
+Linux  CD-ROM ɥ饤
+(äΤ˸ȡCD-ROM ɥ饤֤ĤʤäƤ륳ȥ) 
+򥵥ݡȤƤȤϸ¤ޤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+Some older CD-ROM drives do not work correctly if <quote>direct memory
+access</quote> (DMA) is enabled.
+-->
+Ť CD-ROM ɥ饤֤ˤϡ
+<quote>쥯ȥꥢ</quote> (DMA) ͭȡ
+ưʤʪ⤢ޤ
+
+  </para></listitem>
+</itemizedlist>
+
+  </sect3>
+
+  <sect3>
+<!--
+  <title>How to investigate and maybe solve issues</title>
+-->
+  <title>Ĵˡ</title>
+<para>
+
+<!--
+If the CD-ROM fails to boot, try the suggestions listed below.
+-->
+CD-ROM ư˼Ԥ顢ʲΤȤƤ
+
+<itemizedlist>
+  <listitem><para>
+
+<!--
+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.
+-->
+BIOS  CD-ROM εư򤭤ȥݡȤƤ뤫 (ŤƥԲ)
+CD-ROM ɥ饤֤ȤͽΥǥ򥵥ݡȤƤ뤫åƤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+If you downloaded an iso image, check that the md5sum of that image matches
+the one listed for the image in the <filename>MD5SUMS</filename> file that
+should be present in the same location as where you downloaded the image
+from.
+-->
+ISO ᡼ɤ硢
+᡼ɤΤƱˤ <filename>MD5SUMS</filename> 
+˵ܤƤ md5sum ƱɤåƤ
+
+<informalexample><screen>
+$ md5sum <replaceable>debian-testing-i386-netinst.iso</replaceable>
+a20391b12f7ff22ef705cee4059c6b92  <replaceable>debian-testing-i386-netinst.iso</replaceable>
+</screen></informalexample>
+
+<!--
+Next, check that the md5sum of the burned CD-ROM matches as well. The
+following command should work. It uses the size of the image to read the
+correct number of bytes from the CD-ROM.
+-->
+ˡƤ CD-ROM  md5sum Ȱפ뤫ɤåƤ
+ʲΥޥɤǹԤޤ
+CD-ROM Хȿɤ߹Τ˥᡼ΥѤޤ
+
+<informalexample><screen>
+$ dd if=/dev/cdrom | \
+> head -c `stat --format=%s <replaceable>debian-testing-i386-netinst.iso</replaceable>` | \
+> md5sum
+a20391b12f7ff22ef705cee4059c6b92  -
+262668+0 records in
+262668+0 records out
+134486016 bytes (134 MB) copied, 97.474 seconds, 1.4 MB/s
+</screen></informalexample>
+
+  </para></listitem>
+</itemizedlist>
+
+</para><para>
+
+<!--
+If, after the installer has been booted successfully, the CD-ROM is not
+detected, sometimes simply trying again may solve the problem. If you have
+more than one CD-ROM drive, try changing the CD-ROM to the other drive.
+If that does not work or if the CD-ROM is recognized but there are errors
+when reading from it, try the suggestions listed below. Some basic knowledge
+of Linux is required for this.
+To execute any of the commands, you should first switch to the second
+virtual console (VT2) and activate the shell there.
+-->
+󥹥ȡεưǡCD-ROM 򸡽Фʤ硢
+ñ˥ȥ饤Dz褹뤳Ȥ⤢ޤ
+CD-ROM ɥ饤֤ʣ硢¾ CD-ROM ɥ饤֤ѤƤߤƤ
+ǤưʤäꡢCD-ROM ǧƤɤ߹ߥ顼ȯϡ
+ʲΤȤƤߤƤLinux δμɬפǤ
+ޥɤ¹Ԥˤϡޤ 2 ۥ󥽡 (VT2) ڤؤơ
+ͭˤƤ
+
+<itemizedlist>
+  <listitem><para>
+
+<!--
+Switch to VT4 or view the contents of <filename>/var/log/syslog</filename>
+(use <command>nano</command> as editor) to check for any specific error
+messages. After that, also check the output of <command>dmesg</command>.
+-->
+顼ååΤ VT4 ڤؤꡢ
+<filename>/var/log/syslog</filename> Ƥ 
+(ǥ <command>nano</command> Ѥ) ɽƤ
+θ塢<command>dmesg</command> νϤǤåǤޤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+Check in the output of <command>dmesg</command> if your CD-ROM drive was
+recognized. You should see something like (the lines do not necessarily
+have to be consecutive):
+-->
+CD-ROM ɥ饤֤ǧ <command>dmesg</command> 
+νϤǥåƤʲΤ褦˸ޤ
+(ԤϢ³ƤɬפϤޤ)
+
+<informalexample><screen>
+Probing IDE interface ide1...
+hdc: TOSHIBA DVD-ROM SD-R6112, ATAPI CD/DVD-ROM drive
+ide1 at 0x170-0x177,0x376 on irq 15
+hdc: ATAPI 24X DVD-ROM DVD-R CD-R/RW drive, 2048kB Cache, UDMA(33)
+Uniform CD-ROM driver Revision: 3.20
+</screen></informalexample>
+
+<!--
+If you don't see something like that, chances are the controller your CD-ROM
+is connected to was not recognized or may be not supported at all. If you
+know what driver is needed for the drive, you can try loading it manually
+using <command>modprobe</command>.
+-->
+ʾΤ褦˸ʤСCD-ROM ³ȥǧǤʤ
+餯ݡȤƤޤ󡣥ɥ饤֤ɬפʥɥ饤ФʬäƤС
+<command>modprobe</command> Ѥɤ߹Τޤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+Check that there is a device node for your CD-ROM drive under
+<filename>/dev/</filename>. In the example above, this would be
+<filename>/dev/hdc</filename>.
+There should also be a <filename>/dev/cdroms/cdrom0</filename>.
+-->
+<filename>/dev/</filename> ˤ 
+CD-ROM ɥ饤֤ΥǥХΡɤåƤ
+Ǥϡ<filename>/dev/hdc</filename> ˤʤäƤޤ
+<filename>/dev/cdroms/cdrom0</filename> ˤ⤢뤫⤷ޤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+Use the <command>mount</command> command to check if the CD-ROM is already
+mounted; if not, try mounting it manually:
+-->
+CD-ROM Ǥ˥ޥȤƤʤ
+<command>mount</command> ޥɤǥåƤ
+ޥȤƤʤСǥޥȤƤ
+
+<informalexample><screen>
+$ mount /dev/<replaceable>hdc</replaceable> /cdrom
+</screen></informalexample>
+
+<!--
+Check if there are any error messages after that command.
+-->
+嵭Υޥɸˡ顼åǤ뤫åƤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+Check if DMA is currently enabled:
+-->
+DMA ͭʲΤ褦˥åƤ
+
+<informalexample><screen>
+$ cd /proc/<replaceable>ide</replaceable>/<replaceable>hdc</replaceable>
+$ grep dma settings
+using_dma      1       0       1       rw
+</screen></informalexample>
+
+<!--
+A <quote>1</quote> means it is enabled. If it is, try disabling it:
+-->
+<quote>1</quote> ͭȤ̣ǤξʲΤ褦̵ˤƤ
+
+<informalexample><screen>
+$ echo -n "using_dma:0" >settings
+</screen></informalexample>
+
+<!--
+Make sure that you are in the directory for the device that corresponds
+to your CD-ROM drive.
+-->
+μ¤ˡCD-ROM ɥ饤֤˰פǥХΥǥ쥯ȥƤ
+
+  </para></listitem>
+  <listitem><para>
+
+<!--
+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.
+-->
+󥹥ȡ˲꤬С󥹥ȡᥤ˥塼βˤ롢
+CD-ROM åԤäƤ
+CD-ROM μ¤ɤ硢ΥץŪʥƥȤȤƻѤǤޤ
+
+  </para></listitem>
+</itemizedlist>
+
+</para>
+  </sect3>
+  </sect2>
+
   <sect2 condition="supports-floppy-boot" id="unreliable-floppies">
   <title>եåԡǥο</title>
 
@@ -26,7 +365,7 @@
 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
+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.
 -->
 ä˥֡ȥեåԡǤˤʤ褦Ǥ
@@ -41,25 +380,35 @@
 </para><para>
 
 <!--
-If you are having the installation stall at a particular floppy, the
-first thing you should do is re-download the floppy disk image and
-write it to a <emphasis>different</emphasis> floppy. Simply
-reformatting the old
+If you are having the installation stall at a particular floppy, the first
+thing you should do is write the image to a <emphasis>different</emphasis>
+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.
 -->
 󥹥ȡ뤬ΥեåԡߤƤޤϡ
-ޤեåԡǥΥ᡼ɤľơ
- <emphasis>̤</emphasis> եåԡ˽ľƤߤ뤳ȤǤ
+ޤ <emphasis>̤</emphasis> եåԡ˽ľơ
+꤬褹뤫Ƥ
 ŤեåԡեޥåȤľǤϽʬǤϤޤ
-(ΥեåԡΥեޥåȤȽ񤭹߻˥顼ФʤäȤƤ⡢Ǥ)
+(ΥեåԡΥեޥåȤ񤭹߻˥顼ФʤäȤƤ⡢Ǥ)
 եåԡ̤Υƥǽ񤭹Ǥߤȡ
 ޤȤ⤢褦Ǥ
 
 </para><para>
 
 <!--
+Normally you should not have 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.
+-->
+̾եåԡ᡼٥ɤɬפϤޤ󤬡
+꤬ȯϡ᡼ΥɤԤƤ뤫
+md5sum 򸡾ڤƳǧȤǤ礦
+
+</para><para>
+
+<!--
 One user reports he had to write the images to floppy
 <emphasis>three</emphasis> times before one worked, and then
 everything was fine with the third floppy.
@@ -444,7 +793,7 @@
 
 
 Boot method: &lt;󥹥ȡεưˡ? CD? եåԡ? ͥåȥ?&gt;
-Image version: &lt;᡼&gt;
+Image version: &lt;᡼ɤ URL ٥&gt;
 Date: &lt;󥹥ȡ뤷&gt;
 
 Machine: &lt;ޥ ( IBM Thinkpad R32)&gt;
@@ -453,23 +802,24 @@
 Root Device: &lt;IDE?  SCSI?  ǥХ̾?&gt;
 Partitions: &lt;df -Tl η; ͥ褵Υѡƥơ֥&gt;
 
-Output of lspci and lspci -n:
+Output of lspci -nn and lspci -vnn:
 
 Base System Installation Checklist:
 [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it
 
-Initial boot worked:    [ ]
-Configure network HW:   [ ]
-Config network:         [ ]
+Initial boot:           [ ]
+Detect network card:    [ ]
+Configure network:      [ ]
 Detect CD:              [ ]
 Load installer modules: [ ]
 Detect hard drives:     [ ]
 Partition hard drives:  [ ]
-Create file systems:    [ ]
-Mount partitions:       [ ]
 Install base system:    [ ]
+Clock/timezone setup:   [ ]
+User/password setup:    [ ]
+Install tasks:          [ ]
 Install boot loader:    [ ]
-Reboot:                 [ ]
+Overall install:        [ ]
 
 Comments/Problems:
 

Index: ja/administrivia/administrivia.xml
===================================================================
--- ja/administrivia/administrivia.xml	(リビジョン 43350)
+++ ja/administrivia/administrivia.xml	(作業コピー)
@@ -1,5 +1,5 @@
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 39614 -->
+<!-- original version: 43043 -->
 
 <appendix id="administrivia">
  <title>付記</title>
@@ -86,12 +86,12 @@
 <!--
 If you have problems or suggestions regarding this document, you
 should probably submit them as a bug report against the package
-<classname>debian-installer-manual</classname>.  See the
+<classname>installation-guide</classname>.  See the
 <classname>reportbug</classname> package or read the online
 documentation of the <ulink url="&url-bts;">Debian Bug
 Tracking System</ulink>.  It would be nice if you could check the
-<ulink url="&url-bts;debian-installer-manual">open bugs against
-debian-installer-manual</ulink> to see whether your problem has
+<ulink url="&url-bts;installation-guide">open bugs against
+installation-guide</ulink> to see whether your problem has
 already been reported. If so, you can supply additional corroboration
 or helpful information to
 <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>,
@@ -99,14 +99,14 @@
 already-reported bug.
 -->
 この文書に関する問題や提案がある場合には、それらを
-<classname>debian-installer-manual</classname> パッケージに対するバグ報告として
+<classname>installation-guide</classname> パッケージに対するバグ報告として
 提出してください。
 その方法については <classname>reportbug</classname> パッケージや
 <ulink url="&url-bts;">Debian バグ追跡システム</ulink>
 のオンラインドキュメントをご覧ください。
 なお同じ問題が報告済みかどうかを調べるためには、
-<ulink url="&url-bts;debian-installer-manual">
-debian-installer-manual パッケージに関するバグ報告</ulink>
+<ulink url="&url-bts;installation-guide">
+installation-guide パッケージに関するバグ報告</ulink>
 を確認するとよいでしょう。もし同じ問題が報告済みならば、
 <email><replaceable>XXXX</replaceable>@bugs.debian.org</email>
 宛に、確証のための追加情報や有益な情報を提供することができます。