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
Reply to: