summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNozomu KURASAWA <nabetaro@caldron.jp>2006-10-17 16:09:46 +0000
committerNozomu KURASAWA <nabetaro@caldron.jp>2006-10-17 16:09:46 +0000
commitbb8fcf3d5f08c19ff1cda2cb823187e394e300d9 (patch)
treec57b3013c532a7aa02f379c935415ce61009f27f
parent83784bea69b990596f8a368007f981d4f35cfcc4 (diff)
downloadinstallation-guide-bb8fcf3d5f08c19ff1cda2cb823187e394e300d9.zip
Update translation for Japanese.
-rw-r--r--ja/boot-installer/x86.xml3
-rw-r--r--ja/hardware/supported/hppa.xml4
-rw-r--r--ja/using-d-i/modules/partman-crypto.xml8
3 files changed, 7 insertions, 8 deletions
diff --git a/ja/boot-installer/x86.xml b/ja/boot-installer/x86.xml
index 00185e83b..e8079b061 100644
--- a/ja/boot-installer/x86.xml
+++ b/ja/boot-installer/x86.xml
@@ -336,7 +336,6 @@ argument, giving the device that the ide-floppy driver maps the device
to. For example, if your LS-120 drive is connected as the first IDE
device (master) on the second cable, you enter
<userinput>linux root=/dev/hdc</userinput> at the boot prompt.
-Installation from LS-120 is only supported by 2.4 and later kernels.
-->
フロッピーのセットで LS-120 ドライブ (ATAPI 版) からインストールするには、
フロッピーデバイスの仮想位置を指定する必要があります。
@@ -345,8 +344,6 @@ ide-floppy ドライバが割り当てたデバイスを指定する事で行います。
例えば LS-120 ドライブ を 2 番目のケーブルに、
最初の IDE デバイス (マスター) として接続していれば、
ブートプロンプトに <userinput>linux.bin root=/dev/hdc</userinput> と入力します。
-LS120 からのインストールは 2.4 以降のカーネルでのみサポートされています。
-
</para><para>
diff --git a/ja/hardware/supported/hppa.xml b/ja/hardware/supported/hppa.xml
index 70af6b07e..61c9cc3c5 100644
--- a/ja/hardware/supported/hppa.xml
+++ b/ja/hardware/supported/hppa.xml
@@ -1,13 +1,13 @@
<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 11648 -->
+<!-- original version: 41452 -->
<sect2 arch="hppa"><title>CPU・マザーボード・ビデオのサポート</title>
<para>
<!--
-The are two major support <emphasis>&architecture;</emphasis> flavors:
+There are two major support <emphasis>&architecture;</emphasis> flavors:
PA-RISC 1.1 and PA-RISC 2.0. The PA-RISC 1.1 architecture is targeted
at 32-bit processors whereas the 2.0 architecture is targeted to
the 64-bit processors. Some systems are able to run either kernel.
diff --git a/ja/using-d-i/modules/partman-crypto.xml b/ja/using-d-i/modules/partman-crypto.xml
index 73e2ae63a..c890ee632 100644
--- a/ja/using-d-i/modules/partman-crypto.xml
+++ b/ja/using-d-i/modules/partman-crypto.xml
@@ -1,6 +1,6 @@
<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
-<!-- original version: 39460 -->
+<!-- original version: 41817 -->
<sect3 id="partman-crypto">
<!--
@@ -550,7 +550,7 @@ one via loop-AES.
1 番目は dm-crypt で暗号化し、2 番目は loop-AES で暗号化しています。
<informalexample><screen>
-Encrypted volume (<replaceable>crypt0</replaceable>) - 115.1 GB Linux device-mapper
+Encrypted volume (<replaceable>sda2_crypt</replaceable>) - 115.1 GB Linux device-mapper
#1 115.1 GB F ext3
Loopback (<replaceable>loop0</replaceable>) - 515.2 MB AES256 keyfile
@@ -569,13 +569,15 @@ change the file system types if the defaults do not suit you.
<!--
One thing to note here are the identifiers in parentheses
(<replaceable>crypt0</replaceable>
+(<replaceable>sda2_crypt</replaceable>
and <replaceable>loop0</replaceable> 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
ordinary boot process and boot process with encryption involved will
be covered later in <xref linkend="mount-encrypted-volumes"/>.
-->
-ここで注意するのは、括弧内の識別子 (ここでは <replaceable>crypt0</replaceable>
+ここで注意するのは、括弧内の識別子 (ここでは
+<replaceable>sda2_crypt</replaceable>
と <replaceable>loop0</replaceable>) と、
暗号化ボリュームを割り当てるマウントポイントです。
後で新しいシステムを起動するときに、この情報が必要になります。