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

[d-i doc] 翻訳更新

鍋太郎です。

インストールマニュアルの訳を追随しました。

本文と差分を添付しますので査読をお願いいたします。

アーカイブの内容は以下になります。
$ tar ztf d-i-update0724.tar.gz 
ja/boot-new/boot-new.xml

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

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

Index: ja/boot-new/boot-new.xml
===================================================================
--- ja/boot-new/boot-new.xml	(ӥ 39257)
+++ ja/boot-new/boot-new.xml	(ȥԡ)
@@ -1,6 +1,6 @@
 <?xml version="1.0" encoding="EUC-JP"?>
 <!-- retain these comments for translator revision tracking -->
-<!-- original version: 33725 -->
+<!-- original version: 38703 -->
 
 <chapter id="boot-new">
 <!--
@@ -344,6 +344,245 @@
    </sect2>
  </sect1>
 
+ <sect1 id="mount-encrypted-volumes">
+<!--
+ <title>Mounting encrypted volumes</title>
+-->
+ <title>Ź沽ܥ塼Υޥ</title>
+
+<para>
+
+<!--
+If you created encrypted volumes during the installation and assigned
+them mount points, you will be asked to enter the passphrase for each
+of these volumes during the boot. The actual procedure differs
+slightly between dm-crypt and loop-AES.
+-->
+󥹥ȡ˰Ź沽ܥ塼ޥȥݥȤ˳Ƥȡ
+Υܥ塼Фơư˥ѥե졼Ϥ褦˿֤Ƥޤ
+ºݤμϡdm-crypt  loop-AES Ǥϼ㴳ۤʤޤ
+
+</para>
+
+  <sect2 id="mount-loop-aes">
+  <title>loop-AES</title>
+
+<para>
+
+<!--
+For partitions encrypted via loop-AES you will be shown the following
+prompt during the boot:
+-->
+loop-AES ǰŹ沽ѡƥǤϡ
+ư˰ʲΤ褦ʥץץȤɽޤ
+
+<informalexample><screen>
+mount: going to use loop device /dev/loop<replaceable>X</replaceable>
+Password:
+</screen></informalexample>
+
+<!--
+In the first line of the prompt, <replaceable>X</replaceable> is the
+number of the loop device. You are now probably wondering
+<emphasis>for which volume</emphasis> you are actually entering the
+passphrase. Does is relate to your <filename>/home</filename>? Or to
+<filename>/var</filename>? Of course, if you have just one encrypted
+volume, this is easy and you can just enter the passphrase you used
+when setting up this volume. If you set up more than one encrypted
+volume during the installation, the notes you wrote down as the last
+step in <xref linkend="partman-crypto"/> come in handy. If you did not
+make a note of the mapping between
+<filename>loop<replaceable>X</replaceable></filename> and the mount
+points before, you can still find it
+in <filename>/etc/fstab</filename> of your new system.
+-->
+ץץȤκǽιԤ <replaceable>X</replaceable> ϡ
+롼ץǥХֹǤ
+餯<emphasis>ܥ塼ऴȤ</emphasis> ѥե졼Ϥ뤳Ȥˡ
+´򴶤ΤǤϤʤǤ礦
+<filename>/home</filename> ˤĤ? 
+⤷ <filename>/var</filename> ˤĤ?
+Ź沽ܥ塼ǤС
+åȥåפȤϤѥե졼ϤΤñǤ
+󥹥ȡˡŹ沽ܥ塼򾯤ʤȤĤꤷƤʤ顢
+<xref linkend="partman-crypto"/> 
+κǸΥƥåפνα᤿⤬ΩĤǤ礦
+ <filename>loop<replaceable>X</replaceable></filename> 
+ȥޥȥݥȤδ֤Υޥåԥ󥰤Ͽʤ硢
+ƥ <filename>/etc/fstab</filename> ˤޤ
+
+</para><para>
+
+<!--
+No characters (even asterisks) will be shown while entering the
+passphrase. Be careful, you have only <emphasis>one try</emphasis>. If
+you enter wrong passphrase, an error message will appear and the boot
+process will skip that volume and continue to mount the next
+filesystem. Please see <xref linkend="crypto-troubleshooting"/> for
+further information.
+-->
+ѥե졼ϻˤʸ (ꥹ) ɽޤ
+<emphasis>Ԥ 1 </emphasis>ʤȤդƤ
+ѥե졼ְ㤨ȡΥܥ塼򥹥åפơ
+Υե륷ƥޥȤ褦Ȥޤ
+ܺ٤ϡ<xref linkend="crypto-troubleshooting"/> 
+
+</para><para>
+
+<!--
+After entering all passphrases the boot should continue as usual.
+-->
+ѥե졼򤹤٤Ϥȡ̾Ʊͤ˵ư³ޤ
+
+</para>
+  </sect2>
+
+  <sect2 id="mount-dm-crypt">
+  <title>dm-crypt</title>
+
+<para condition="FIXME">
+
+<!--
+TODO: write something once it works.
+-->
+TODO: ɤΤ褦ư뤫񤤤Ƥ
+
+</para>
+  </sect2>
+
+  <sect2 id="crypto-troubleshooting">
+<!--
+  <title>Troubleshooting</title>
+-->
+  <title>ȥ֥륷塼</title>
+
+<para>
+
+<!--
+If some of the encrypted volumes could not be mounted because a wrong
+passphrase was entered, you will have to mount them manually after the
+boot. There are several cases.
+-->
+ѥե졼ְ㤨ơŹ沽ܥ塼ޥȤǤʤä硢
+֡ȸ˼ưǥޥȤɬפޤʲξͤޤ
+
+</para>
+
+<itemizedlist>
+<listitem><para>
+
+<!--
+The first case concerns the root partition. When it is not mounted
+correctly, the boot process will halt and you will have to reboot the
+computer to try again.
+-->
+ޤϤξϡ롼ȥѡƥ˴ؤ뤳ȤǤ
+ޥȤǤʤȥ֡ȥץߤ
+ƵưƤ⤦ٹԤʤФʤޤ
+
+</para></listitem>
+<listitem><para>
+
+<!--
+The easiest case is for encrypted volumes holding data like
+<filename>/home</filename> or <filename>/srv</filename>. You can
+simply mount them manually after the boot. For loop-AES this is
+one-step operation:
+-->
+Ǥñʾϡ<filename>/home</filename>  <filename>/srv</filename> 
+ȤäǡݻƤŹ沽ܥ塼ξǤ
+ξϡ֡ȸ˼ưǥޥȤƤǤ
+loop-AES ǤϡʲΤ褦 1 ƥåפǤ
+
+<informalexample><screen>
+<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>
+<prompt>Password:</prompt>
+</screen></informalexample>
+
+<!--
+where <replaceable>/mount_point</replaceable> should be replaced by
+the particular directory (e.g. <filename>/home</filename>). The only
+difference from an ordinary mount is that you will be asked to enter
+the passphrase for this volume.
+-->
+<replaceable>/mount_point</replaceable> ϡ
+Υǥ쥯ȥ֤Ƥ( <filename>/home</filename>)
+̾ΥޥȤȰ㤦Τϡ
+Υܥ塼Ѥ˥ѥե졼Ϥ褦¥롢ȤȤǤ
+
+
+</para><para>
+
+<!--
+For dm-crypt this is a bit trickier. First you need to register the
+volumes with <application>device mapper</application> by running:
+-->
+dm-crypt ξϾȥåǤ
+ޤ <application>device mapper</application> ¹Ԥơ
+ܥ塼Ͽɬפޤ
+
+<informalexample><screen>
+<prompt>#</prompt> <userinput>/etc/init.d/cryptdisks start</userinput>
+</screen></informalexample>
+
+<!--
+This will scan all volumes mentioned
+in <filename>/etc/crypttab</filename> and will create appropriate
+devices under the <filename>/dev</filename> directory after entering
+the correct passphrases. (Already registered volumes will be skipped,
+so you can repeat this command several times without worrying.) After
+successful registration you can simply mount the volumes the usual
+way:
+-->
+<filename>/etc/crypttab</filename> ˵Ҥ줿ܥ塼ह٤Ƥ򸡺
+ѥե졼Ϥȡ
+<filename>/dev</filename> ǥ쥯ȥʲˡŬڤʥǥХޤ
+(Ͽ줿ܥ塼ϥåפΤǡټ¹ԤƤٹ𤬤Ǥޤ)
+ϿȡʲΤ褦̾ˡǥޥȤǤޤ
+
+<informalexample><screen>
+<prompt>#</prompt> <userinput>mount <replaceable>/mount_point</replaceable></userinput>
+</screen></informalexample>
+
+</para></listitem>
+<listitem><para>
+
+<!--
+If the volumes holding noncritical system files could not be mounted
+(<filename>/usr</filename> or <filename>/var</filename>), the system
+should still boot and you should be able to mount the volumes manually
+like in the previous case. However, you will also need to (re)start
+any services usually running in your default runlevel because it is
+very likely that they were not started. The easiest way to achieve
+this is by switching to the first runlevel and back by entering
+-->
+ƥǤʤƥե򰷤ܥ塼 
+(<filename>/usr</filename>  <filename>/var</filename>) 
+ޥȤǤʤä硢Ǥ⥷ƥबư
+ҤξΤ褦˼ưǥܥ塼ޥȤǤǤ礦
+ǥեȤΥ٥̾ưƤ륵ӥ
+ưƤʤǽΤǡ() ưɬפޤ
+ǤñʤΤϡǽΥ٥˰ʲΤ褦ڤؤ뤳ȤǤ
+
+<informalexample><screen>
+<prompt>#</prompt> <userinput>init 1</userinput>
+</screen></informalexample>
+
+<!--
+at the shell prompt and pressing <keycombo> <keycap>Control</keycap>
+<keycap>D</keycap> </keycombo> when asked for the root password.
+-->
+rootΥѥɤ֤줿 <keycombo> <keycap>Control</keycap>
+<keycap>D</keycap> </keycombo> 򲡤
+ΥץץȤǾ嵭ϤƤ
+
+</para></listitem>
+</itemizedlist>
+
+  </sect2>
+ </sect1>
+
+
  <sect1 id="login">
 <!--
  <title>Log In</title>