README-User.m4.2
ÏÂÐÇÆÚÒ»¿¼ÊÔ£¬ËùÒÔ·ÒëµÄ´Ò棬ÇëУ¶Ô¡£
MILO/
º¬ÓÐMILOÆô¶¯Òýµ¼Æ÷¡£ÕâЩÆô¶¯Òýµ¼Æ÷ÊÇΪÁËÔÚARCºÍAlphasBIOSϵͳÉÏ
Æô¶¯Óõġ£
Èç¹ûÄúÊÇ´ÓCDÉÏÔËÐеĻ°£¬Çë´ÓÎĵµµÄ±íÖÐÕÒµ½ÄãÏàÓ¦µÄ¼ÆËã»úϵͳ£¬
È»ºóÔÚ¡®²Ù×÷ϵͳѡÔñÉèÖá¯(OS Selection Setup)²Ëµ¥ÖУ¬ÔÚÆô¶¯Òýµ¼
Æ÷Ñ¡Ïî(boot loader)ÖÐÊäÈë¡®\milo\linload.exe¡¯;ÔÚ²Ù×÷ϵͳ·¾¶Ñ¡
Ïî(OS Path)ÖÐÊäÈë¡®\milo\<subarch>¡¯(ÕâÀï<subarch>ÊÇÏàÓ¦¼ÆËã»úϵ
ͳÔËÐÐÎļþµÄÃû³Æ)¡£
Èç¹ûÄãÏë´ÓÈíÅÌÉÏÆô¶¯µÄ»°£¬Ç뿽±´ÏàͬµÄÎļþ(linload.exeºÍ
ÏàÓ¦ÔËÐÐÎļþ)µ½ÄãµÄÈíÅÌ£¨×¢Ò⽫ÄãµÄÈíÅÌÔÚDOSϽøÐиñʽ»¯£©¡£
È»ºóÆô¶¯ÄãµÄAlpha»úÆ÷£¬²åÈëÈíÅÌ£¬½øÈëARC»òAlphaBIOSµÄ¡®²Ù×÷ϵͳ
Ñ¡ÔñÉèÖ᯲˵¥£¬ÉèÖÃÆô¶¯É豸(Boot Device)Ϊ´ÓÈíÅÌÆô¶¯£¬ÏµÍ³Òýµ¼
Æ÷Ϊ¡®\linload.exe¡¯£¬ÏµÍ³Â·¾¶Îª¡®<subarch>¡¯(ÏàӦϵͳµÄÔËÐÐÎļþ
Ãû)¡£×îºó£¬µ±³öÏÖMILOÌáʾ·ûʱ£¬²åÈë¼±¾È(rescue)Å̲¢´òÈëÃüÁî
¡®boot fd0:¡¯¡£
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/
º¬ÓÐΪUP1000Ö÷°åµÄAPBÆô¶¯Òýµ¼Æ÷ºÍÏà¹ØµÄÎļþ¡£ÕâÊÇΪÁËÔÚUP1000ÉÏ
´ÓCDÉÏÆô¶¯Óõġ£ÄãÐèÒª´Ó`Utility/Run Maintenance Program'²Ëµ¥ÖÐ
ÔËÐÐ'\apb\apb.exe'£¬È»ºóÔÚAPBÌáʾ·ûÏÂÊäÈë¡®boot debian_install¡¯
ÃüÁî¡£
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>/
ÕâÀïÓм¸ÖÖ²»Í¬¡®·ç¸ñ¡¯µÄ°²×°ÅÌ¡£ÓÐЩӳÏóº¬ÓÐÓÃÌض¨µÄ±àÒëÑ¡Ïî±àÒë
µÄLinuxÄںˣ¬ÕâЩӳÏó»áÔÚijЩӲ¼þÉÏÔËÐеĸüºÃ£¬ÏÂÃæµÄÄÚÈݸæËßÄã
ΪʲôÄãÐèҪijÖÖÌض¨µÄ°²×°·ç¸ñ¡£
ÔÚÕâ¸öĿ¼Ï»¹ÓÐһЩ²»ÊÇ´ÅÅÌÓ³ÏóµÄÎļþ£¬ÕâЩÎļþÊÇΪijÌض¨°²×°
·ç¸ñËùʹÓá£ÔÚʹÓÃÍøÂç°²×°»ò´ÓÁíÍâÒ»¸ö²Ù×÷ϵͳ°²×°Ê±ÕâЩÎļþ
¿ÉÄÜ»áÓÐÓá£
ÔÚ´ÓÍøÂç(network)£¬ÍøÂçÎļþϵͳ(NFS)£¬ºÍCDÇý¶¯Æ÷(CD-ROM)°²×°Ê±£¬
Ö»ÒªÄãÉ趨ÁË<debian>Ŀ¼£¬°²×°Èí¼þÖªµÀÈçºÎÕÒµ½ÕâЩÎļþ¡£Èç¹ûÄã
×¼±¸Ñ¡Ôñ"´Ó¹ÒÔØ·ÖÇø"(from a mounted partition)°²×°²¢¿½±´ÕâЩÎÄ
¼þµ½ÄãµÄÓ²ÅÌ£¬Äã²»ÐèÒªÍêÈ«¸´ÖÆÕû¸ö<debian>Ŀ¼½á¹¹£¬µ«ÊÇÄãÒª±£
Ö¤ÄãÓÐÏàÅäµÄÓ³ÏóÎļþ¼¯£¬ËùÓÐÎļþ±ØÐëÊÇÏàͬ·ç¸ñ£¬·ñÔò°²×°²¢²»ÄÜ
ÕýÈ·µÄ½øÐС£
Õâ¸ö¼ÆËã»úÌåϵÉÏ¿ÉÑ¡µÄ°²×°·ç¸ñÊÇ FLAVORS.
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
½ô´Õ .... º¬ÓеÄLinuxÄÚºËÈ¥³ýÁËһЩ²»ÖØÒªµÄÉ豸Çý¶¯Ö§³Ö£¬²¢¼Ó
ÈëÁ˸ü¶àµÄһЩͨÓÃPCIÉ豸֧³Ö¡£
Çë²ÎÔÄimages-1.44/compact/README.txt
idepci .... Óë¡®½ô´Õ¡¯ÏàËÆ£¬µ«ÊǸü¶àµÄPCIÉ豸Çý¶¯Ö§³Ö±»¼ÓÈëÁËÄÚ
ºËÖУ¬²¢ÔÚÄÚºËÖÐÈ¥³ýÁËSCSIµÄÉ豸Çý¶¯Ö§³Ö¡£
Çë²ÎÔÄimages-1.44/idepci/README.txt
udma66 .... ÕâÄÚºËÊÇΪÄÇЩÐèÒªUDMA66²¹¶¡µÄÈË×¼±¸µÄ¡£Èç¹ûÄã°²×°ÓÐ
Ultra66 IDE ¿ØÖÆÆ÷£¯Ó²Å̵Ļ°¿ÉÄÜÐèÒªÕâÄںˡ£
Çë²ÎÔÄimages-1.44/udma66/README.txt
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>/])
´ÅÅÌÓ³Ïó´óС<size>¡£Ñ¡ÔñÓëÄãÆô¶¯Å̵ÄÈÝÁ¿(´óС)ÏàͬµÄÓ³Ï󣬲¢°´ÕÕ
"дӳÏóÎļþµ½ÈíÅÌ"(Writing Image Files to Floppies)ÖеÄָʾ½øÐÐ
²Ù×÷¡£
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
** һЩÓÐÓõÄÌØÊâÎļþ
¸ù¾ÝÉÏÃæµÄÃèÊö£¬ÄãÐèҪѡÔñº¬ÓÐÓëÄã°²×°ÏàÅäµÄÎļþĿ¼¡£³ý·ÇÁíÓÐ˵Ã÷Äã
ÐèÒªÈçÏÂËùÓеġ®.bin¡¯Ó³ÏóÎļþ¡£
.../rescue.bin
¼±¾ÈÅÌÓ³Ï󣬺¬ÓÐϵͳÄں˺ÍÆô¶¯Òýµ¼Æ÷¡£
.../root.bin
¸ùĿ¼ÅÌÓ³Ï󣬺¬ÓиùĿ¼ϵͳ¡£
.../driver-#.bin
É豸Çý¶¯ÅÌÓ³Ï󣬺¬ÓÐÖ§³ÖÄÇЩûÓб»ÄÚºËÖ±½ÓÖ§³ÖµÄÉ豸Çý¶¯ÄÚºËÄ£¿é¡£
ÀýÈ磬Äã¿ÉÒÔÀûÓÃÕâÀ´°²×°ÄãÍø¿¨µÄÉ豸Çý¶¯³ÌÐò£»È»ºóÄã¿ÉÒÔͨ¹ýÍøÂçÀ´
°²×°Ê£ÏµÄϵͳ¡£ÆäËüÖ§³ÖµÄÉ豸Çý¶¯°üÀ¨µ÷Öƽâµ÷Æ÷(ppp)£¬²¢ÐпÚ
(parallel)µÈ¡£
.../base-#.bin
»ù±¾µÄDebianϵͳ(BASE_TGZ)£¬·Ö³É¼¸¸ö´ÅÅÌÓ³Ïó¡£Èç¹ûÄã×¼±¸´ÓÍøÂ磬
ÍøÂçÎļþϵͳ£¬Ó²ÅÌ(¹ÒÔØ·ÖÇø)»òCD-ROM°²×°µÄ»°£¬Äã²»ÐèÒªÕâЩ
`base-#.bin'Îļþ¡£ÕâЩÎļþÊÇΪ´ÓÈíÅÌ°²×°×¼±¸µÄ£¬Äã¿ÉÒÔÓÃÀ´
ÔÚ¼Ò°²×°»ù±¾ÏµÍ³£¬ÉèÖúõ÷Öƽâµ÷Æ÷(ppp)ºóÔÚͨ¹ýpppÀ´°²×°Ê£
ϵÄϵͳ¡£
** 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
Reply to: