Re: README-User.m4.2 (校對)
On Sun, Dec 17, 2000 at 02:29:37AM -0500, zxd@bu.edu wrote:
> 下星期一考試，所以翻譯的匆忙，請校對。
>
謝謝，我們現在不是很急，悠著來。
%%%%%%%% 初校稿，請繼續
MILO/
含有MILO啟動引導程序。這些啟動引導程序是為了在ARC和AlphasBIOS系統
上啟動用的。
如果您是從CD上運行的話，請從文檔的表中找到你相應的計算機結構體系，
然後在‘操作系統選擇設置’(OS Selection Setup)菜單中，在啟動引導
程序選項(boot loader)中輸入‘\milo\linload.exe’;在操作系統路徑選
項(OS Path)中輸入‘\milo\<subarch>’(這裡<subarch>是相應計算機結構
體系的名稱)。
如果你想從軟盤上啟動的話，請拷貝本目錄下和你的計算機系統結構同名
的文件(這個文件本身是 MILO 二進制引導程序) 和linload.exe到你的軟
盤上（注意先將你的軟盤格式化成DOS格式）。
然後啟動你的Alpha機器，插入軟盤，進入ARC或AlphaBIOS的‘操作系統
選擇設置’菜單，把啟動設備(Boot Device)設置為這個軟盤，系統引導
程序為‘\linload.exe’，系統路徑為相應的計算機結構體系名(既MILO
的文件名)。最後，當出現MILO提示符時，插入救急(rescue)盤並打入命令
‘boot fd0:’。
APB/
含有為UP1000主板使用的APB啟動引導程序和相關的文件。這是為了在
UP1000上從CD上啟動用的。你需要從`Utility/Run Maintenance Program'
菜單中運行'\apb\apb.exe'，然後在APB提示符下輸入‘boot debian_install’
命令。
]dnl,
dnl ARCHITECTURE, XXX, [
dnl This probably ought to be filled in more by the maintainers who know
dnl what to say here for their architecture's subarch's.
dnl]
)[]dnl ifelse(ARCHITECTURE, ...)
])[]dnl ifdef([SUBARCHES], ...)
dnl
ifdef([FLAVORS], [dnl
ifdef([SUBARCHES],[<subarch>/])<flavor>/
這裡有幾種不同‘風格’的安裝盤。有些映象含有用特定的編譯選項編譯
的Linux內核，這些映象會在某些硬件上運行的更好，下面的內容將告訴你
為什麼你需要某種特定的安裝風格。
在這個目錄下還有一些不是磁盤映象的文件，這些文件是為某特定安裝
風格所使用。在使用網絡安裝或從另外一個操作系統安裝時這些文件
可能會有用。
在從網絡，網絡文件系統(NFS)，和CD驅動器安裝時，只要你設定了
<debian>目錄，安裝軟件就知道如何找到這些文件。如果你準備選擇"從掛
載分區"安裝而要拷貝這些文件到你的硬盤，你不需要完全復制整個
<debian>目錄結構，但是你要保証你有相配的映象文件集，所有文件必須
是相同風格，否則安裝將不能正確的進行。
這個計算機結構體系上可選的安裝風格是 FLAVORS.
dnl
ifelse(ARCHITECTURE, i386, [dnl
compact.... 所含的Linux內核去除了對一些不重要的設備驅動的支持，並
加入了對更多的常用PCI設備的支持。
請參閱images-1.44/compact/README.txt
idepci .... 與 compact 相似，但是更多的PCI設備驅動的支持被加入了
內核中，並在內核中去除了對SCSI的設備驅動的支持。
請參閱images-1.44/idepci/README.txt
udma66 .... 這內核是為那些需要UDMA66補丁的人準備的。如果你的系統安
裝了Ultra66 IDE 控制器／硬盤的話可能需要這內核。
請參閱images-1.44/udma66/README.txt
]dnl,
dnl ARCHITECTURE, XXX, [dnl
dnl Other arch with flavor info goes here.
dnl]
)dnl
])[]dnl
dnl
ifdef([SIZES], [dnl
ifdef([SUBARCHES],[<subarch>/])images-<size>/ifdef([FLAVORS],[<flavor>/])
磁盤映象大小<size>。選擇與你啟動盤的容量相同的映象，並按照下面
“向軟盤裡寫入映象文件”中的指示進行操作。
])[]dnl
** 一些有用的特殊文件
根據上面的描述，你需要選擇含有與你安裝相配的文件目錄。除非另有說明你
需要如下所有的‘.bin’映象文件。
.../rescue.bin
救急盤映象，含有系統內核和啟動引導程序。
.../root.bin
根系統盤映象，含有根文件系統。
.../driver-#.bin
設備驅動盤映象，含有支持那些沒有被內核直接支持的設備驅動內核模塊。
例如，你可以利用它來安裝你的網卡的設備驅動程序；然後你可以通過網絡
來安裝剩下的系統。其它支持的設備驅動模塊包括調制解調器(ppp)，並行口
(parallel)等。
.../base-#.bin
基本的Debian系統(BASE_TGZ)，分成幾個磁盤映象。如果你準備從網絡，
網絡文件系統，硬盤(掛載分區)或CD-ROM安裝的話，你不需要這些
`base-#.bin'文件。這些文件是為從軟盤安裝準備的，你可以先用
它安裝基本系統，設置好調制解調器(ppp)後再通過ppp來安裝剩
下的系統。
dnl
%%%%%%%% 參考原文
MILO/
Contains MILO boot loaders for certain platforms. These are used
for booting on ARC and AlphaBIOS systems.
To boot on one of these from CD, find your subarchitecture from
the table in the documentation, then enter `\milo\linload.exe'
as the boot loader and `\milo\<subarch>' (where <subarch> is the
proper subarchitecture name) as the OS Path in the `OS Selection
Setup' menu.
To boot one of these from floppy, copy the file with the same
name as your subarchitecture (this is the MILO binary) and
`linload.exe' from this directory to a DOS-formatted floppy
disk. Power on your Alpha, insert this disk, then enter the `OS
Selection Setup' menu in ARC or AlphaBIOS. Set the boot device
to the floppy drive, the OS Loader to `\linload.exe', and the OS
Path to your subarchitecture name (i.e. the name of the MILO
binary). Then, at the MILO prompt, insert the rescue disk and
enter the command `boot fd0:'.
APB/
Contains the APB boot loader and associated files for the UP1000
motherboard. These are used when booting from CD on the UP1000.
To boot on this platform, run '\apb\apb.exe' from the
`Utility/Run Maintenance Program' menu, and type `boot
debian_install' at the APB prompt.
]dnl,
dnl ARCHITECTURE, XXX, [
dnl This probably ought to be filled in more by the maintainers who know
dnl what to say here for their architecture's subarch's.
dnl]
)[]dnl ifelse(ARCHITECTURE, ...)
])[]dnl ifdef([SUBARCHES], ...)
dnl
ifdef([FLAVORS], [dnl
ifdef([SUBARCHES],[<subarch>/])<flavor>/
There are several `flavors' of installation disk available. In
some cases the images contain a Linux kernel compiled with
certain options that make it work better on some hardware. See
below for information about why you might need to use a flavor.
Also in this directory are files for a particular flavor which
are not disk images, but may be helpful for network
installations or installations from another operating system.
During a network, NFS, or CD-ROM install, the install software
knows how to find these files, once you have indicated the
<debian> directory. If you plan to copy these files to a spot
on your hard drive in anticipation of using the installer's
"from a mounted partition" option, you do not need to duplicate
the directory structure of the <debian> archive, but you do need
to make sure you get a matched set of images, all of the same
<flavor>, or things probably won't work correctly.
The flavors available for this architecture are FLAVORS.
dnl
ifelse(ARCHITECTURE, i386, [dnl
compact .... A Linux kernel with some non-critical device
drivers removed, and a few of the more common PCI
device drivers compiled into the kernel itself.
See images-1.44/compact/README.txt
idepci .... Similar to compact, but even more PCI device drivers
are compiled into the kernel, and SCSI is removed.
See images-1.44/idepci/README.txt
udma66 ..... Specialized kernel for those who require the UDMA66
IDE patch. This may be needed if you have a
Promise Ultra66 IDE controller, among others.
See images-1.44/udma66/README.txt
]dnl,
dnl ARCHITECTURE, XXX, [dnl
dnl Other arch with flavor info goes here.
dnl]
)dnl
])[]dnl
dnl
ifdef([SIZES], [dnl
ifdef([SUBARCHES],[<subarch>/])images-<size>/ifdef([FLAVORS],[<flavor>/])
Disk images of size <size>. Choose the size that will fit on the
media you intend to bootstrap the installation software from, and
follow the instructions below under "Writing Image Files to
Floppies".
])[]dnl
** Specific Files of Interest
Using the descriptions above, you need to select the directory
containing the set of files which is appropriate to the installation
you are doing. You will need all of the following `.bin' images,
unless marked otherwise.
.../rescue.bin
Rescue disk image, containing the kernel and a boot loader.
.../root.bin
Root disk image, containing the root file system.
.../driver-#.bin
Device driver disk images, containing kernel modules you can
load for hardware for which there is not a driver built into the
kernel. For instance, you can use this to install a driver for
your network adapter; once you have installed that driver, you
can install the rest of the system over the network. Other
modules include PPP, parallel support, etc.
.../base-#.bin
The base Debian distribution (BASE_TGZ), split into disk images.
If you intend to install from the network, NFS, a mounted
partition, or a CD-ROM, you will not need the `base-#.bin'
images. (This is good news for the majority of us.) These are
for floppy-only installs, or people installing the base system
so that they can get PPP started and the rest of their system
installed via modem.
dnl
%%%%%%%%%%%%%%%%%
--
Best regard
hashao
--
| This message was re-posted from debian-chinese-gb@lists.debian.org
| and converted from gb2312 to big5 by an automatic gateway.
Reply to: