[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [d-i doc] install-methods 翻訳
鍋太郎です。
チェックありがとうございます。
On Thu, 15 Apr 2004 22:35:36 +0900
TAKEI Nobumitsu <takei@xxxxxxxxxxxxxxxx> wrote:
> downloading-files.xml
>
> OldWorld ……インストールするときには、
> インストーラの起動には BootX しか使えないという制約があります。
>
> ではいかがでしょう.
OldWorld マシンに new-powermac バージョンをインストールするときには、
インストーラの起動に BootX しか使えないという制約があります。
とさせていただきます。
> ja/install-methods/floppy/i386.xml
> 訳文1行が原文側のコメントアウトに含まれてしまっています.
> ja/install-methods/floppy/powerpc.xml
> 原文がコメントアウトされていません.
すみません。またやってしまいました……
申し訳ないです。
修正したものを添付します。
--
+--------------------------+
倉澤 望(鍋太郎)
KURASAWA Nozomu (nabetaro)
nabetaro@xxxxxxxxxxxxx
+--------------------------+
<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
<!-- $Id: downloading-files.xml 11648 2004-03-22 00:37:46Z joeyh $ -->
<!-- original version: 11648 -->
<sect1 id="downloading-files">
<title>Debian ߥ顼ȤΥեΥ</title>
<para>
<!--
To find the nearest (and thus probably the fastest) mirror, see the
<ulink url="&url-debian-mirrors;">list of Debian mirrors</ulink>.
-->
äȤᤤ (Ƥ餯äȤ®) ߥ顼Ȥõˤϡ
<ulink url="&url-debian-mirrors;">Debian ߥ顼Ȱ</ulink>
ȤƤ
</para><para>
<!--
When downloading files from a Debian mirror, be sure to download the
files in <emphasis>binary</emphasis> mode, not text or automatic
mode. It's important to replicate the directory structure you find on
the mirror to create a local `sub-mirror'.
-->
Debian ߥ顼ȤեɤȤ
<emphasis>Хʥ(binary)</emphasis>
⡼ɤǥեɤ褦ǧƤ
ƥ (text) ⡼ɤ伫ư⡼ɤǤϤǤ
Ρ֥֥ߥ顼פˤϡ
ߥ顼Ȥˤ褦ʥǥ쥯ȥ깽¤ʣ뤳ȤڤǤ
<phrase arch="not-s390">
<!--
It isn't really necessary to do this
if you place all the installation files on floppies; but it still
makes it easier to find the files when you need them.
-->
ºݤˤϡ٤ƤΥȡѥե
եåԡǽɬפϤޤ
ǤեåԡǽƤС
ե뤬ɬפˤʤäȤ˸ĤΤϴñˤʤޤ
</phrase>
<!--
You should start your local directory structure at the level under
<filename>installer-&architecture;</filename>, for example:
-->
Υǥ쥯ȥ깽¤ϡ
<filename>installer-&architecture;</filename> βϤȤǤ礦
㤨:
<informalexample><screen arch="i386">
current/images/floppy/boot.img
</screen><screen arch="not-i386">
current/images/<replaceable>subarchitecture</replaceable>/netboot/initrd.gz
</screen></informalexample>
<!--
You don't need to download every file under that level, just those
that apply to you (you'll find out which ones apply as you read on).
Just name the directories the same as the mirror's, and keep the files
in their proper directories.
-->
γزեɤɬפϤޤ
ʤɬפʥեǤΤǤ
(ɤ줬ɬפɤ߿ʤФ狼ޤ)
ǥ쥯ȥ̾ϥߥ顼ȤΤΤƱˤ
եơŬڤʥǥ쥯ȥƤޤ礦
</para><para>
<!--
If your machine is set up to automatically decompress/decode files you
download, you must turn that feature off when downloading the
installation system files. They will be decompressed just-in-time by
the installer. Decompressing in your current system will waste space
and time, and if the original compressed archives are deleted by the
decompression program, they won't be there later when the installer
needs them.
-->
ʤΥޥɤեưŪ
Ĺ椹褦ꤵƤϡ
ɻˤϤεǽ̵ˤɬפޤ
Ĺϥȡ餬ɬפʤȤ˹Ԥޤ
ޤΥƥǿĹΤϡǥ̤Ȼ̵֤̤Ǥ
ˡΰ̤줿ե뤬ĹץˤäƺƤޤȡ
ȡ餬ɬפȤȤˤΥե뤬ʤȤȤˤʤޤ
</para><para arch="powerpc;m68k">
<!--
This is particularly true on the Macintosh, where <filename>.bin</filename>
files are interpreted to be MacBinary, and the decoder's attempts to
convert them will fail noisily.
-->
äϡä Macintosh ˳ޤ
<filename>.bin</filename> ե MacBinary Ȳᤵޤ
ץबѴǤʤȸäȤˤʤǤ礦
</para><para arch="powerpc">
<!--
Also, many of the binary files such as <filename>yaboot</filename>
will be automatically interpreted as text since they have no file
extensions unless you specifically select binary transfer mode. These
files will be <emphasis>unusable</emphasis> if they are transferred in
text mode.
-->
ޤŪ˥Хʥž⡼ɤꤷʤȡ
<filename>yaboot</filename> ʤɤγĥҤΤʤ¿ΥХʥեϡ
ưŪ˥ƥȤǤȲᤵޤ
ƥȥ⡼ɤž줿ե <emphasis>Ȥޤ</emphasis>
</para>
<sect2 arch="m68k">
<title>ȡ륪ץ</title>
<para>
<!--
For m68k (except VME), the installation system files
(<filename>rescue.bin, linux.bin, root.bin, and
drivers.tgz</filename>) have been compiled into one tarball. You may
also need the base system installation file
<filename>basedebs.tar</filename>.
-->
m68k (VME ʳ) Υȡѥƥե
(<filename>rescue.bin, linux.bin, root.bin, drivers.tgz</filename>) ϡ
ޤȤ 1 Ĥ tarball ˤʤäƤޤ
ܥƥΥȡѥե <filename>basedebs.tar</filename>
ɬפǤ
</para><para>
<!--
If you have a working Ethernet connection on the computer, and your
Ethernet card is of one of the types compiled into the installation
kernel, you may only need the install system tarball.
-->
ͥå³ư륳ԥ塼ꡢ
ͥåȥɤȡ륫ͥȤ߹ޤƤΤΤʤ顢
ɬפʤΤϥȡ륷ƥ tarball Ǥ
</para><para>
<!--
If you are installing on a system without a working network
connection, or if your network connection is via PPP (using a modem)
rather than Ethernet, you will also need to download
<filename>basedebs.tar</filename> before starting the installation.
-->
ưͥåȥ³Τʤƥ˥ȡ뤹䡢
ͥåȤǤϤʤ (ǥȤä)
PPP ǥͥåȥ³ϡ
ȡϤ <filename>basedebs.tar</filename>
ɤɬפޤ
</para>
</sect2>
<sect2 arch="not-m68k">
<title>ȡ륪ץ</title>
<para>
<!--
Files you may need fall into three categories:
-->
ɬפȤʤեϼ 3 Ĥμʬޤ
</para>
<orderedlist>
<listitem><para>
<!--
Files needed to boot into the installation system (for example,
<phrase arch="not-s390">
<filename>boot.img</filename> and <filename>root.img</filename>, or
<filename>vmlinuz</filename> and <filename>initrd.gz</filename>)
</phrase>
<phrase arch="s390">
<filename>kernel.debian</filename>,
<filename>parmfile.debian</filename>, and
<filename>initrd.debian</filename>)
</phrase>
-->
ȡ륷ƥư뤿ɬפʥե (㤨
<phrase arch="not-s390">
<filename>boot.img</filename> <filename>root.img</filename>⤷
<filename>vmlinuz</filename> <filename>initrd.gz</filename>)
</phrase>
<phrase arch="s390">
<filename>kernel.debian</filename>,
<filename>parmfile.debian</filename>,
<filename>initrd.debian</filename>)
</phrase>
</para></listitem>
<listitem><para>
<!--
Files the installation system will need access to
after it has been booted in order to install the operating system
kernel and peripheral drivers (for example,
<filename>net-drivers.img</filename> and
<filename>cd-drivers.img</filename>)
-->
ȡ륷ƥबưȤˡ
OS Υͥȼյɥ饤ФȤȡ뤹뤿
ɬפΤե
(㤨 <filename>net-drivers.img</filename>
<filename>cd-drivers.img</filename>)
</para></listitem>
<listitem><para>
<!--
Base system installation files
-->
ܥƥ।ȡѤΥե
</para></listitem>
</orderedlist>
<para>
<!--
If you have a working Ethernet connection on the computer, and your
Ethernet card is of one of the types compiled into the installation
kernel, you may only need the install system boot files. The installer
is capable of installing drivers and the rest of the system over the
network for many common Ethernet cards.
-->
ȡоݤΥԥ塼ư륤ͥå³ꡢ
Υͥåȥɤȡ륫ͥȤ߹ޤƤʤС
ɬפȤʤΤϥȡ륷ƥεưեǤ
ȡϡ¿ΥͥåȥɤФơ
ͥåȥͳǤΥͥȥɥ饤ФμݡȤƤޤ
</para><para>
<!--
If you have an Ethernet connection for which the installer doesn't
have built-in support, you may need both the install system boot files
and the peripheral driver installation files.
-->
ͥå³ΥݡȤȡȤ߹ޤƤʤ硢
ɬפȤʤΤϡȡ륷ƥ൯ưե롢ͥ롢
֥ɥ饤ФΥȡѥեǤ
</para><para>
<!--
If you are installing on a system without a working network
connection, or if your network connection is via PPP (using a modem)
rather than Ethernet, you will need to obtain all three types of files
before starting the installation. The base system installation files
are available on the first Debian CD (or on its smaller variant called
<firstterm>netinst</firstterm>, which is under 120MB). You can use
this ISO image even if you don't have a CD-ROM drive.
-->
ưͥåȥ³Τʤƥ˥ȡ뤹뤫
ͥåȤǤϤʤ (ǥȤä) PPP ͳǥͥåȥ³ϡ
3 Υե뤹٤Ƥȡ˼ɬפޤ
ܥƥ।ȡեϡDebian CD 1
(ޤ 120MB ʲ <firstterm>netinst</firstterm> ȸƤФ뾮Ѽ)
ˤޤ
Ȥ CD-ROM ɥ饤֤ʤƤ ISO ѤǤޤ
</para><para>
<!--
If you're not sure which files you need, just start with the install
system boot files. If your first attempt to configure the network
within the installer fails, you can just quit, get the extra files you
need, and re-start the installation.
-->
ɤΥե뤬ɬפʤΤ狼ʤϡ
ȡ륷ƥεưեϤޤ
ͥåȥκǽλߤԤ顢
ȡǤɬפɲåեꤷơ
ȡľФ褤ΤǤ
</para>
</sect2>
<sect2 arch="i386" id="kernel-choice">
<title>ȡ륻åȤ</title>
<para>
<!--
Installation files include kernel images, which are available in
various <firstterm>flavors</firstterm>. Each flavor supports a
different set of hardware. The flavors available for &arch-title; are:
-->
ȡѥեˤϥͥ륤äƤꡢ
Υͥ륤ˤϤޤޤ <firstterm>flavors</firstterm> ޤ
ƥե졼Сϡ줾ۤʤäϡɥݡȤޤ
&arch-title; ǻȤե졼Сϰʲ̤Ǥ
<variablelist>
<varlistentry>
<term>vanilla</term>
<listitem><para>
<!--
The standard kernel package available in Debian. This includes almost
all drivers supported by Linux built as modules, which includes
drivers for network devices, SCSI devices, sound cards, Video4Linux
devices, etc. The <quote>vanilla</quote> flavor includes one boot
floppy, one root and two driver floppies.
-->
Debian ɸ५ͥѥåäƤΤǤ
Linux ǥݡȤƤۤȤɤ٤ƤΥɥ饤Ф
⥸塼ȤȤ߹ޤƤޤ
ˤϥͥåȥǥХSCSI ǥХ
ɥɡVideo4Linux ǥХʤɤޤޤޤ
<quote>vanilla</quote> ե졼Сϡ1 ֡ȥեåԡ
1 root եåԡ2 driver եåԡʤޤ
</para></listitem>
</varlistentry>
<varlistentry>
<term>speakup</term>
<listitem><para>
<!--
Almost like <quote>vanilla</quote>, but it contains support for
braille display. A complete list of supported models may be found in
brltty documentation. This flavor includes one boot floppy, one root
floppy and one driver floppy.
-->
ۤȤ <quote>vanilla</quote> ƱǤ
ǥץ쥤ݡȤƤޤ
ݡȤǥδʥꥹȤ brltty ʸǸĤǤ礦
Υե졼Сϡ1 ֡ȥեåԡ
1 root եåԡ1 driver եåԡʤޤ
</para></listitem>
</varlistentry>
</variablelist>
</para><para>
<!--
Although we have described above how many 1.44MB diskettes the
different sets occupy, you may still choose different methods of
installation.
-->
ƥե졼Сιܤ 1.44MB Υǥɬפˤʤ뤫ޤ
¾ΥȡˡȤޤ
</para><para>
<!--
The kernel config files for these flavors can be found in their
respective directories in a file named <filename>kernel-config</filename>.
-->
ƥե졼Сѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
</para>
</sect2>
<sect2 arch="not-i386">
<title>ȡ륻åȤ</title>
<para>
<!--
Installation files include kernel images, which are available for
various <firstterm>subarchitectures</firstterm>. Each subarchitecture
supports a different set of hardware. The kernel config files for
these subarchitectures can be found in their respective directories in
a file named <filename>kernel-config</filename>. The subarchitectures
available for &arch-title; are:
-->
ȡѥեˤϥͥ륤ޤޤޤ
ͥ륤ˤϡޤޤ <firstterm>֥ƥ</firstterm>
ΤΤޤ
줾Υ֥ƥϡۤʤϡɥݡȤޤ
ƥ֥ƥѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
&arch-title; ˤϰʲΥ֥ƥ㤬ѰդƤޤ
</para>
<variablelist arch="sparc">
<varlistentry>
<term>`sun4cmd'</term>
<listitem><para>
<!--
This is the kernel required for older SPARC hardware. For specific
models supported, see <xref linkend="sparc-cpus"/>.
-->
Ť SPARC ϡɥΥͥǤ
ɤΥǥ뤬ݡȤƤ뤫
<xref linkend="sparc-cpus"/>
</para></listitem>
</varlistentry>
<varlistentry>
<term>`sun4u'</term>
<listitem><para>
<!--
UltraSPARC machines.
-->
UltraSPARC ޥǤ
</para></listitem>
</varlistentry>
</variablelist>
<para arch="sparc">
<!--
The kernel config files for these subarchitectures can be found in their
respective directories in a file named <filename>kernel-config</filename>.
-->
ƥ֥ƥѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
</para>
<variablelist arch="mipsel">
<varlistentry>
<term>`r4k-kn04'</term>
<listitem><para>
<!--
This is the kernel required for the R4000 based DECstation 5000/150 and
similar machines, such as the R4400 based DECstation 5000/260.
-->
R4000 ١ DECstation 5000/150 䡢˻ޥ
(㤨 R4400 ١ DECstation 5000/260 ʤ) ΥͥǤ
</para></listitem>
</varlistentry>
<varlistentry>
<term>`r3k-kn02'</term>
<listitem><para>
<!--
This is the kernel required for R3000 based DECstations with KN02 (or
compatible) main board, such as the DECstation 5000/1xx series with
xx=20,25,33 and the DECstation 5000/240.
-->
KN02 (뤤ϸߴ)ᥤܡɤѤ R3000 ١ DECstation
(㤨 DECstation 5000/1xx (xx=20,25,33)
DECstation 5000/240) ΥͥǤ
</para></listitem>
</varlistentry>
</variablelist>
<para arch="mipsel">
<!--
The kernel config files for these subarchitectures can be found in their
respective directories in a file named <filename>kernel-config</filename>.
-->
ƥ֥ƥѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
</para>
<variablelist arch="mips">
<varlistentry>
<term>`r4k-ip22'</term>
<listitem><para>
<!--
This is the kernel required for SGI Indy, Indigo 2 and Challenge S machines.
The kernel includes almost all drivers supported by Linux built as modules,
which includes drivers for network devices, SCSI devices, etc. There are no
other flavors for &arch-title; available currently.
-->
SGI Indy, Indigo 2, Challenge S ޥѤΥͥǤ
ΥͥˤϡLinux ǥݡȤƤɥ饤ФΤۤܤ٤
(ͥåȥǥХSCSI ǥХʤ) ⥸塼ȤƴޤޤƤޤ
&arch-title; ˤϡۤΥե졼СϤޤ
</para></listitem>
</varlistentry>
</variablelist>
<para arch="mips">
<!--
The kernel config files for these subarchitectures can be found in their
respective directories in a file named <filename>kernel-config</filename>.
-->
ƥ֥ƥѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
</para>
<variablelist arch="hppa">
<varlistentry>
<term>`32'</term>
<listitem><para>
<!--
This is the kernel to use on all 32 bit processors. On processors
that support 32 and 64 bit modes, this is probably also the best
kernel to use for installation.
-->
٤Ƥ 32 ӥåȥץåΥͥǤ
ץå 32 ӥåȥ⡼ɤ 64 ӥåȥ⡼ɤξݡȤƤ硢
¿ʬȡˤϤΥͥ뤬Ǥ礦
</para></listitem>
</varlistentry>
<varlistentry>
<term>`64'</term>
<listitem><para>
<!--
This is the kernel to use on all 64 bit processors. On processors
that support 32 and 64 bit modes, the 32 bit kernel is probably the
best kernel to use for installation.
-->
٤Ƥ 64 ӥåȥץåѤΥͥǤ
ץå 32 ӥåȥ⡼ɤ 64 ӥåȥ⡼ɤξݡȤƤ硢
¿ʬȡˤ 32 ӥåѥͥ뤬Ǥ礦
</para></listitem>
</varlistentry>
</variablelist>
<para arch="hppa">
<!--
These kernels include almost all drivers supported by Linux built as
modules, which includes drivers for network devices, SCSI devices,
etc. Support for standard hardware is compiled in to the kernel,
so it is unlikely that you will need to configure any modules during
installation.
-->
ΥͥˤϡLinux ǥݡȤƤɥ饤ФΤۤܤ٤
(ͥåȥǥХSCSI ǥХʤ) ⥸塼ȤƴޤޤƤޤ
ɸŪʥϡɥϥͥȤ߹ߤޤƤޤΤǡ
ȡ˥⥸塼ɬפϤۤȤɤʤϤǤ
</para><para arch="hppa">
<!--
The kernel config files for these subarchitectures can be found in their
respective directories in a file named <filename>kernel-config</filename>.
-->
ƥ֥ƥѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
</para>
<variablelist arch="s390">
<varlistentry>
<term>`tape'</term>
<listitem><para>
<!--
Includes a kernel image which supports booting (IPL) from a tape
(emulated or real) and a DASD (Direct Access Storage Device). You need
these files if you want to install &debian; native or in an
LPAR (logical partition) but they can also be used to install under VM
with a tape (real or emulated).
-->
(ߥ졼Ȥޤʪ) ơפ DASD (Direct Access Storage Device)
εư (IPL) ݡȤ륫ͥ륤Ǥ
&debian; ͥƥ֤˥ȡ뤹
뤤 LPAR (logical partition) ˥ȡ뤹ɬפȤʤޤ
VM (ʪޤϥߥ졼Ȥ) ơפ饤ȡ뤹ݤˤ
ѤǤޤ
</para><para arch="s390"><phrase condition="FIXME">
<emphasis>FIXME: nolabel ͥϤɤǤ礦?</emphasis>
</phrase></para>
</listitem>
</varlistentry>
<varlistentry>
<term>`vmrdr'</term>
<listitem><para>
<!--
Includes a kernel image which supports booting (IPL) from the VM
reader and a DASD, These files can only be used if you want to install
&debian; in a VM guest.
-->
VM DASD εư (IPL) ݡȤ륫ͥ륤Ǥ
Υե &debian; VM Ȥ˥ȡ뤹ȤˤΤȤޤ
</para></listitem>
</varlistentry>
</variablelist>
<para arch="s390">
<!--
Both of these kernels include almost all drivers supported by Linux
built as modules. Support for standard hardware is compiled into the
kernel, so it is unlikely that you will need to configure any modules
during installation.
-->
ΥͥǤ⡢Linux ǥݡȤƤɥ饤ФΤۤܤ٤Ƥ
⥸塼ȤƴޤޤƤޤ
ɸŪʥϡɥϥͥȤ߹ߤޤƤޤΤǡ
ȡ˥⥸塼ɬפϤۤȤɤʤϤǤ
</para><para arch="s390">
<!--
Both kernels were also built to directly support IBM's OCO modules. You
can simply download then from IBM's
<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml">
developerWorks web site</ulink> and load them into the running kernel.
Please make sure that you pick the modules for the standard kernel,
i.e. not the ones for a kernel with the ``on-demand'' timer patch.
-->
Υͥ⡢
IBM OCO ⥸塼ľܥݡȤ褦ӥɤƤޤIBM
<ulink url="http://oss.software.ibm.com/developerworks/opensource/linux390/index.shtml">
developerWorks web site</ulink> ɤơ
¹Υͥɤ߹ޤǤ
ɸ५ͥѤΥ⥸塼֤褦դƤĤޤꡢ
``on-demand'' timer ѥåդͥѤΥ⥸塼ǤϤʤȤȤǤ
</para><para arch="s390">
<!--
The kernel config files for these subarchitectures can be found in their
respective directories in a file named <filename>kernel-config</filename>.
-->
ƥ֥ƥѥͥեϡ줾Υǥ쥯ȥ
<filename>kernel-config</filename> Ȥ֤̾Ƥޤ
</para>
<variablelist arch="powerpc">
<varlistentry>
<term>`powermac'</term>
<listitem><para>
<!--
This is the kernel to use for most Power Macintosh computers; it uses
version 2.2 of the Linux kernel.
-->
ۤȤɤ Power Macintosh ԥ塼ǻȤͥǤ
Linux ͥΥС 2.2 ѤƤޤ
</para></listitem>
</varlistentry>
<varlistentry>
<term>`new-powermac'</term>
<listitem><para>
<!--
Use this kernel for very new Power Macintosh computers; it is based on
version 2.4 of the Linux kernel. If you want to install the
new-powermac version on an OldWorld machine, you are limited to using
BootX to boot the installer; the kernel doesn't fit on a floppy and
Debian CDs are not bootable on OldWorlds. You could also switch to the
&kernelversion; kernel after you finish the powermac flavor install.
-->
Ƕ Power Macintosh ԥ塼ǻȤͥǤ
Linux ͥΥС 2.4 ˤƤޤ
OldWorld ޥ new-powermac Сȡ뤹Ȥˤϡ
ȡεư BootX ȤʤȤޤ
Τᡢͥ뤬եåԡ꤭餺
ޤ OldWorld Debian CD ưǤޤ
powermac ե졼Сǥȡ뤬λ塢
&kernelversion; ڤؤ뤳ȤǤޤ
</para></listitem>
</varlistentry>
<varlistentry>
<term>`apus'</term>
<listitem><para>
<!--
Use this kernel for Amiga Power-UP Systems (APUS); it is based on
version 2.2 of the Linux kernel.
-->
Amiga Power-UP Systems (APUS) ѤΥͥǤ
Linux ͥΥС 2.2 ˤƤޤ
</para></listitem>
</varlistentry>
<varlistentry>
<term>`chrp'</term>
<listitem><para>
<!--
Use this kernel for embedded CHRP computers; it is based on
version 2.2 of the Linux kernel.
-->
ȹ CHRP ԥ塼ѤΥͥǤ
Linux ͥΥС 2.2 ˤƤޤ
</para></listitem>
</varlistentry>
<varlistentry>
<term>`prep'</term>
<listitem><para>
<!--
Use this kernel for Motorola and IBM RS/6000 PReP computers; it is based on
version 2.2 of the Linux kernel.
-->
Motorola IBM RS/6000 PReP ԥ塼ѤΥͥǤ
Linux ͥΥС 2.2 ˤƤޤ
</para></listitem>
</varlistentry>
</variablelist>
<para arch="powerpc">
<!--
The kernel config files for these subarchitectures can be found in their
respective directories in a file named <filename>config.gz</filename>.
-->
ƥե졼СѤΥͥեϡ줾Υǥ쥯ȥ
<filename>config.gz</filename> Ȥ֤̾Ƥޤ
</para><para arch="arm">
<!--
There is only one installation kernel available for each supported ARM
machine family.
-->
ARM ޥեߥݡȤƤ륤ȡѥͥ 1 ĤǤ
</para><para arch="m68k;ia64">
<!--
There is only one install kernel available for &arch-title;, which
should include sufficient functionality to install on all systems. It
is unlikely to be optimised for your particular hardware, and you
might consider replacing it once installation is complete. In
particular, this kernel does not support SMP.
-->
&arch-title; ѤΥȡ륫ͥ 1 Ĥޤ
ΥͥϤ٤ƤΥƥ˥ȡ뤹뤿
ʬʵǽޤޤƤޤ
ΥϡɥѤ˥ޥƤ櫓ǤϤޤΤǡ
ȡ뤬λȤǤ礦
äˡΥͥǤ SMP ݡȤƤޤ
</para><para arch="m68k;ia64">
<!--
The kernel config files for these kernels can be found in their
respective directories in a file named <filename>config.gz</filename>.
-->
ƥե졼СѤΥͥեϡ줾Υǥ쥯ȥ
<filename>config.gz</filename> Ȥ֤̾Ƥޤ
</para>
</sect2>
<sect2 id="where-files">
<title>ȡѥեΤ꤫</title>
<para arch="m68k">
<!--
For Amiga, Atari, and 68k Mac, the install system files have been
compiled into one tarball. You will download the appropriate tarball
listed in
<xref linkend="amiga-install-files"/>,
<xref linkend="atari-install-files"/>, or
<xref linkend="mac-install-files"/>. Only
VME machines will need the separate boot, root, kernel and drivers
files.
-->
Amiga, Atari, 68k Mac Υȡѥƥեϡ
1 Ĥ tarball ˤޤȤƤޤ
<xref linkend="amiga-install-files"/>,
<xref linkend="atari-install-files"/>,
<xref linkend="mac-install-files"/> Τ줫
Ŭڤ tarball ɤƤ
VME ޥϡ̡ rescue, root, kernel, driver ƥե뤬ɬפǤ
</para>
<variablelist>
<varlistentry>
<term>֡ȥ</term>
<listitem>
<itemizedlist>
&list-rescue-images;
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry condition="rescue-needs-root-disk">
<term>root ޤ tarball</term>
<listitem>
<itemizedlist>
&list-root-images;
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>ͥХʥ</term>
<listitem>
<itemizedlist>
&list-kernel-files;
</itemizedlist>
</listitem>
</varlistentry>
<varlistentry>
<term>ɥ饤Хޤ tarball</term>
<listitem>
<itemizedlist>
&list-driver-images;
&list-driver-disk-tarball;
</itemizedlist>
</listitem>
</varlistentry>
</variablelist>
<para arch="not-powerpc">
<!--
The boot image contains a compressed Linux boot
kernel. It is used for
<phrase arch="not-s390">both floppy disk booting (when transferred to a
floppy) and as the source for
</phrase>
the Linux kernel when the kernel is
being installed on your machine. The kernel binary
<filename>vmlinuz</filename>
is an uncompressed binary kernel. It is used when booting the
installer from
<phrase arch="not-s390">
the hard disk, usb stick, network or CD-ROM, and is not needed for
floppy installer booting.
</phrase><phrase arch="s390">
tape, emulated tape or the VM reader.
</phrase>
-->
֡ȥˤϡ̤줿 Linux ֡ȥͥ뤬äƤޤ
֡ȥ
<phrase arch="not-s390">
(եåԡ˥ǡ줿) եåԡǥεư
</phrase>
Linux ͥΥޥؤΥȡ˻Ȥޤ
ͥХʥ <filename>vmlinuz</filename>
̤ΥХʥꥫͥǤ
ϥȡ
<phrase arch="not-s390">
ϡɥǥusb ƥåͥåȥCD-ROM鵯ưȤ˻Ȥޤ
եåԡ饤ȡưȤɬפޤ
</phrase><phrase arch="s390">
ơסơץߥ졼VM 鵯ưȤ˻Ȥޤ
</phrase>
</para>
<para arch="mipsel">
<!--
Besides the file <filename>linux.bin</filename>, which is a kernel image in
ELF format, the file <filename>linux.ecoff</filename> contains the same
kernel in ECOFF format, which is required for net booting DECstations.
-->
ELF եޥåȤΥͥ륤Ǥ
<filename>linux.bin</filename> եΤۤ
DECstations ͥåȥ֡ȤȤɬפ
ECOFF եޥåȤ <filename>linux.ecoff</filename> ޤߤޤ
</para><para arch="powerpc">
<!--
Both the <filename>boot-floppy-hfs</filename> floppy image and the
<filename>boot.img</filename> image contain a compressed Linux boot
kernel. The <filename>boot-floppy-hfs</filename> floppy is used to
boot the installation system, while <filename>boot.img</filename>
serves as the source for the Linux kernel when the kernel is being
installed on your machine. A <filename>boot.img</filename> floppy
cannot be booted on &arch-title;. A third uncompressed kernel image,
simply named <filename>linux.bin</filename>, is used when booting the
installer from the hard disk or CD-ROM. It is not needed for floppy
installer booting.
-->
<filename>boot-floppy-hfs</filename> եåԡ
<filename>boot.img</filename> ξˡ
̤줿 Linux ֡ȥͥ뤬ޤޤƤޤ
<filename>boot-floppy-hfs</filename> եåԡϥȡ륷ƥεưѤ졢
<filename>boot.img</filename> Linux ͥޥ˥ȡ뤹ݤ
ԡˤʤޤ
&arch-title; <filename>boot.img</filename> եåԡϵưǤޤ
3 ܤΥ̤ͥǡ<filename>linux.bin</filename> Ȥ̾Ǥ
ϥϡɥǥ CD-ROM 饤ȡưȤ˻Ȥޤ
եåԡ饤ȡưȤˤϻȤޤ
</para><para arch="powerpc">
<!--
There are two versions of the hfs boot floppy image. The standard one,
<filename>boot-floppy-hfs.img</filename>, may work best on older
machines such as the 7200 and 8500 with no added video cards. If the
standard image gives a black screen when booting, try the image with
video=ofonly added to the boot arguments:
<filename>boot-video-ofonly.img</filename>.
-->
hfs Υ֡ȥեåԡΥС 2 Ĥޤ
ɸŪ <filename>boot-floppy-hfs.img</filename> ϡ
7200 ӥǥɤɲäƤʤ 8500 Τ褦ʸŤޥǤ褯ưǤ礦
ɸ।ȵư˲̤ðŤˤʤäƤޤ硢
ư video=ofonly ɲäơ
<filename>boot-video-ofonly.img</filename> Ƥ
</para><para condition="supports-floppy-boot">
<!--
Refer to <xref linkend="create-floppy"/>
for important information on properly
creating floppy disks from floppy images.
-->
եåԡեåԡǥŬڤ˺ˤä
פʾ <xref linkend="create-floppy"/> ˤޤΤǡȤƤ
</para><para condition="rescue-needs-root-disk">
<!--
The root floppy image <filename>root.img</filename> contains a
compressed RAMdisk filesystem which gets loaded into memory after you
boot the installer.
-->
root եåԡΥ (<filename>root.img</filename>) ˤϡ
ȡưȤ˥ɤ߹ޤ
RAM ǥե륷ƥब̤ƴޤޤƤޤ
</para><para>
<!--
The peripheral drivers may be downloaded as a series of floppy images
or as a tarball (<filename>drivers.tgz</filename>). The installer
system will need access to the drivers file during installation. If
you have a hard drive partition or connected computer which will be
accessible to the installer (see below), the tarball will be more
convenient to handle. The floppy image files are needed only if you
must install the drivers from floppies.
-->
յΥɥ饤ФϡʣΥեåԡȤơ
뤤 1 Ĥ tarball (<filename>drivers.tgz</filename>)
ȤƥɤǤޤ
ȡ饷ƥϡ
ȡ˥ɥ饤Хե˥ɬפޤ
ϡɥǥΥѡƥ䡢
³Ƥ̤Υԥ塼Ф
ȡ餬Ǥʤ ()
tarball Τۤ䤹Ǥ礦
եåԡեϡեåԡɥ饤Фȡ
ʤФʤȤˤɬפˤʤޤ
</para><para>
<!--
When downloading files, you should also pay attention to the type of
file system you are downloading them <emphasis>to</emphasis>, unless
you will use floppies for the kernel and drivers. The installer can
read files from many kinds of file systems, including FAT, HFS,
ext2fs, and Minix. When downloading files to a *nix file system,
choose the largest possible files from the archive.
-->
ͥɥ饤Ф˥եåԡȤʤϡ
եΥɤκݤˡ
ɤե <emphasis>֤</emphasis>
ե륷ƥμˤդɬפޤ
ȡϤĤΥե륷ƥ (FAT, HFS, ext2fs, Minix)
ɤळȤǤޤ*nix Υե륷ƥ˥ɤˤϡ
֤Ǥ礭ʥեǤ
</para><para>
<!--
During the installation, you will erase the partition(s) on which you
are installing Debian before beginning the installation. All
downloaded files must be placed on partitions
<emphasis>other</emphasis> than those on which you are planning to
install the system.
-->
ȡǡ
Debian ȡ뤷褦ȤƤѡƥƤϾõޤ
ɤեϡƥȡ뤹ͽ
ѡƥȤ<emphasis>̤ΤȤ</emphasis>֤ɬפޤ
</para>
&download-alpha.xml;
&download-arm.xml;
&download-powerpc.xml;
&download-m68k.xml;
</sect2>
</sect1>
<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
<!-- $Id: i386.xml 11648 2004-03-22 00:37:46Z joeyh $ -->
<!-- original version: 11648 -->
<!-- This is not set off for i386 only, because many people will have -->
<!-- access to a PC in order to make a floppy for other arches. -->
<sect2><title>DOS, Windows, OS/2 ǤΥǥν</title>
<para condition="workaround-bug-99926">
<!--
If you have access to an i386 machine, you can use one of the
following programs to copy images to floppies.
-->
i386 ޥѤǤȤϡ
եåԡؤΥΥԡˤϰʲΥץΤɤ줫Ȥޤ
<!-- links from 99926 info -->
</para><para condition="workaround-bug-99926">
<!--
The FDVOL, WrtDsk or RaWrite3 programs can be used under MS-DOS.
-->
FDVOL, WrtDsk, RaWrite3 Ȥäץब MS-DOS ǻȤޤ
</para><para condition="workaround-bug-99926">
<ulink url="http://www.minix-vmd.org/pub/Minix-vmd/dosutil/">
</ulink>
</para><para condition="workaround-bug-99926">
<!--
To use these programs, first make sure that you are booted into
DOS. Trying to use these programs from within a DOS box in Windows, or
double-clicking on these programs from the Windows Explorer is
<emphasis>not</emphasis> expected to work. If you don't know how to
boot into DOS, just hit <keycap>F8</keycap> while booting.
-->
ΥץȤˤϡޤ DOS ưȤǧޤ礦
Windows DOS ץץȤ餳ΥץȤäꡢ
Windows ΥץǤΥץ֥륯åΤǤϡ
<emphasis>̤ˤưޤ</emphasis>
DOS ưˤϡưƤ
<keycap>F8</keycap> OK Ǥ
</para><para>
<!--
<command>NTRawrite</command> is a freeware contemporary version of
<command>Rawrite/Rawrite3</command> that is compatible with WinNT and
Win2K. It is a self-explanatory GUI application; you select the disk
drive to write to, browse to the disk image you want to place there
and hit the Write button.
-->
<command>NTRawrite</command> ϥեǡWinNT Win2K ȸߴΤ
<command>Rawrite/Rawrite3</command> θǤǤ
狼䤹 GUI ץꥱʤΤǡ
ʤϽǥɥ饤֤
ǥξ֥饦ƽܥǤ
</para><para>
<ulink url="http://sourceforge.net/projects/ntrawrite/"></ulink>
</para>
</sect2>
<!-- FIXME: Questionable whether or how this will be supported in d-i -->
<sect2 id="set-lang">
<title>
ƹ쥵ݡѤ rescue եåԡѹ
</title>
<para>
<!--
The messages shown by the rescue floppy (before loading the Linux
kernel) can be shown in your mother tongue. To achieve this if you are
not an English speaker, after writing the image file, you must copy
the provided message files and a font to the floppy. For MS-DOS and
Windows users there is a batch file <filename>setlang.bat</filename> in the
<filename>dosutils</filename> directory, which copies the correct
files. Simply enter this directory (e.g.
<userinput>cd c:\debian\dosutils</userinput>) within a command prompt
window, and run
<userinput>setlang <replaceable>lang</replaceable></userinput>,
where <replaceable>lang</replaceable> is a
two-letter code of your language in lower case, for example
<userinput>setlang pl</userinput> to set the language to Polish.
Currently these language codes are available:
-->
rescue եåԡɽå (Linux ͥɤΤ) ϡ
ʤˤǤޤ
ѸʳξˤԤˤϡ
ΤΥåեȥեȤ
եΥեåԡ˥ԡޤ
MS-DOS Windows Υ桼ϡ
<filename>dosutils</filename> ǥ쥯ȥ
<filename>setlang.bat</filename> ȤХåե뤬ޤ
ȤŬڤʥեԡǤޤ
ޥɥץץȤǡΥǥ쥯ȥ˰ܤ
(: <userinput>cd c:\debian\dosutils</userinput>)
<userinput>setlang <replaceable>lang</replaceable></userinput> ¹Ԥޤ
<replaceable>lang</replaceable> ˤ 2 ʸθ쥳ɤʸޤ
㤨иݡɸˤˤ
<userinput>setlang pl</userinput> Ȥޤ
ѤǤ쥳ɤϼ̤Ǥ
<informalexample><screen>
&setlang-language-code-list;
</screen></informalexample>
</para><para>
<!-- TRANSLATORS: Please replace "non localized (English)" -->
<!-- in the following paragraph with "localized (your-language)" -->
<!--
Note that the descriptions in this manual assume that you use
non localized (English) installation; otherwise the names of
menus and buttons will differ from what you will see on your screen.
-->
ʤΥޥ˥奢ˤϡ
饤 (ܸ첽) Ƥʤȡ륷ƥꤷƤޤ
㤦ƥȤäƤϡ
˥塼ܥ̾˸ΤȤϰۤʤǽޤ
</para>
</sect2>
<?xml version="1.0" encoding="EUC-JP"?>
<!-- retain these comments for translator revision tracking -->
<!-- $Id: powerpc.xml 11648 2004-03-22 00:37:46Z joeyh $ -->
<!-- original version: 11648 -->
<sect2 arch="powerpc"><title>MacOS Υǥν</title>
<para>
<!--
An AppleScript, <application>Make Debian Floppy</application>, is
available for burning floppies from the provided disk image files. It
can be downloaded from
<ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/debian-imac/MakeDebianFloppy.sit"></ulink>. To
use it, just unstuff it on your desktop, and then drag any floppy
image file to it. You must have Applescript installed and enabled in
your extensions manager. Disk Copy will ask you to confirm that you
wish to erase the floppy and proceed to write the file image to it.
-->
<application>Make Debian Floppy</application> Ȥ AppleScript ȤС
Ƥǥեեåԡ˽ळȤޤ
AppleScript
<ulink url="ftp://ftp2.sourceforge.net/pub/sourceforge/debian-imac/MakeDebianFloppy.sit"></ulink>
ɤǤޤǥȥåפ unstuff ơ
եåԡեξ˥ɥåǤ
AppleScript ȡ뤷
extensions manager ͭˤƤɬפޤ
եåԡƤõƥե륤νߤʤɤ
Disk Copy Ҥͤޤ
</para><para>
<!--
You can also use the MacOS utility <command>Disk Copy</command>
directly, or the freeware utility <command>suntar</command>. The
<filename>root.bin</filename> file is an example of a floppy
image. Use one of the following methods to create a floppy from the
floppy image with these utilities.
-->
MacOS Υ桼ƥƥ <command>Disk Copy</command> ľܻȤäꡢ
եΥ桼ƥƥ <command>suntar</command> ȤȤǤޤ
<filename>root.bin</filename> եեåԡȤơ
Υ桼ƥƥǥեåԡ
եåԡǥˡʲˤĤҲ𤷤ޤ
</para>
<sect3>
<title><command>Disk Copy</command> Ѥǥν</title>
<para>
<!--
If you are creating the floppy image from files which were originally
on the official &debian; CD, then the Type and Creator are already set
correctly. The following <command>Creator-Changer</command> steps are
only necessary if you downloaded the image files from a Debian mirror.
-->
&debian; CD ˤäե뤫եåԡϡ
Type Creator ϴŬڤͤˤʤäƤޤ
˼ <command>Creator-Changer</command> κȤϡե
Debian ߥ顼ɤǤΤɬפȤʤޤ
</para>
<orderedlist>
<listitem><para>
<!--
Obtain
<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink>
and use it to open the <filename>root.bin</filename> file.
-->
<ulink url="&url-powerpc-creator-changer;">Creator-Changer</ulink>
Ѥ <filename>root.bin</filename> եץޤ
</para></listitem>
<listitem><para>
<!--
Change the Creator to <userinput>ddsk</userinput> (Disk Copy), and the
Type to <userinput>DDim</userinput> (binary floppy image). The case is
sensitive for these fields.
-->
Creator <userinput>ddsk</userinput> (Disk Copy) ѹ
Type <userinput>DDim</userinput> (Хʥեåԡ) ѹޤ
ΥեɤǤʸʸ̤ޤΤդƤ
</para></listitem>
<listitem><para>
<!--
<emphasis>Important:</emphasis> In the Finder, use <userinput>Get
Info</userinput> to display the Finder information about the floppy
image, and `X' the <userinput>File Locked</userinput> check box so
that MacOS will be unable to remove the boot blocks if the image is
accidentally mounted.
-->
<emphasis>:</emphasis>
Finder <userinput>Get Info</userinput> Ѥơ
եåԡ Finder ɽƤ
<userinput>File Locked</userinput> åܥå `X' 졢
ְäƥޥȤƤޤäǤ
MacOS ֡ȥ֥åäƤޤʤ褦ˤƤ
</para></listitem>
<listitem><para>
<!--
Obtain <command>Disk Copy</command>; if you have a MacOS system or CD it
will very likely be there already, otherwise try
<ulink url="&url-powerpc-diskcopy;"></ulink>.
-->
<command>Disk Copy</command> ꤷޤ
MacOS ƥ CD ʤ顢ˤˤǤ礦
äƤʤ
<ulink url="&url-powerpc-diskcopy;"></ulink> ƤߤƤ
</para></listitem>
<listitem><para>
<!--
Run <command>Disk Copy</command>, and select `Make a Floppy' from the
<userinput>Utilities</userinput> menu, then select the
<emphasis>locked</emphasis> image file from the resulting dialog. It
will ask you to insert a floppy, then ask if you really want to erase
it. When done it should eject the floppy.
-->
<command>Disk Copy</command> ¹Ԥޤ
<userinput>Utilities</userinput> ˥塼 `Make a Floppy' ӡ
줿 <emphasis>locked</emphasis> եǤ
եåԡ褦졢
³ƤƤ˾äƤɤ֤ޤ
ߤäեåԡϥȤޤ
</para></listitem>
</orderedlist>
</sect3>
<sect3>
<title><command>suntar</command> Ѥǥν</title>
<para>
<orderedlist>
<listitem><para>
<!--
Obtain <command>suntar</command> from <ulink url="&url-powerpc-suntar;">
</ulink>. Start the <command>suntar</command> program and select
`Overwrite Sectors...' from the <userinput>Special</userinput> menu.
-->
<command>suntar</command> <ulink url="&url-powerpc-suntar;"></ulink>
ꤷޤ<command>suntar</command> ץư
<userinput>Special</userinput> ˥塼 `Overwrite Sectors...' Ӥޤ
</para></listitem>
<listitem><para>
<!--
Insert the floppy disk as requested, then hit &enterkey; (start at
sector 0).
-->
줿Ȥǥեåԡǥ
&enterkey; ޤ ( 0 Ϥޤ)
</para></listitem>
<listitem><para>
<!--
Select the <filename>root.bin</filename> file in the file-opening dialog.
-->
file-opening <filename>root.bin</filename> եӤޤ
</para></listitem>
<listitem><para>
<!--
After the floppy has been created successfully, select `Eject' from
the <userinput>File</userinput> menu. If there are any errors writing
the floppy, simply toss that floppy and try another.
-->
եåԡޤ줿顢<userinput>File</userinput> ˥塼
`Eject' Ӥޤեåԡνߤǥ顼ä顢
ΥեåԡϼΤƤ̤ΥեåԡƤ
</para></listitem>
</orderedlist>
<!--
Before using the floppy you created, <emphasis>set the write protect
tab</emphasis>! Otherwise if you accidentally mount it in MacOS,
MacOS will helpfully ruin it.
-->
եåԡȤˡ
<emphasis>ĥưƽɻߤˤƤ</emphasis>
Ƥʤȡְä MacOS ˥ޥȤƤޤä硢
MacOS եåԡƤޤޤ
</para>
</sect3>
</sect2>