Reduce diff against RELENG_7.
Obtained from: The FreeBSD Simplified Chinese Project
This commit is contained in:
Xin LI
parent
d5718812ea
commit
226004be05
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=174502
@ -1,6 +1,6 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
#
|
||||
# Original Revision: 1.7
|
||||
# Original Revision: 1.8
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/..
|
||||
@ -9,7 +9,6 @@ SUBDIR = relnotes
|
||||
SUBDIR+= hardware
|
||||
SUBDIR+= readme
|
||||
SUBDIR+= errata
|
||||
SUBDIR+= installation
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
|
||||
@ -1,3 +1,4 @@
|
||||
# Original Revision: 1.5
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../..
|
||||
|
||||
@ -1,12 +1,33 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
#
|
||||
# Original Revision: 1.6
|
||||
# Original Revision: 1.10
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../..
|
||||
|
||||
SUBDIR= amd64
|
||||
SUBDIR+= i386
|
||||
.ifdef NO_LANGCODE_IN_DESTDIR
|
||||
DESTDIR?= ${DOCDIR}/hardware
|
||||
.else
|
||||
DESTDIR?= ${DOCDIR}/zh_CN.GB2312/hardware
|
||||
.endif
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ${DEV-AUTODIR}/catalog-auto
|
||||
SRCS+= ${DEV-AUTODIR}/dev-auto.sgml
|
||||
|
||||
CATALOGS+= -c ${DEV-AUTODIR}/catalog-auto
|
||||
|
||||
URL_RELPREFIX?= ../../../..
|
||||
|
||||
HWNOTES_MI= 1
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
|
||||
@ -1,18 +0,0 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
#
|
||||
# Original Revision: 1.3
|
||||
# $FreeBSD$
|
||||
|
||||
.ifdef NO_LANGCODE_IN_DESTDIR
|
||||
DESTDIR?= ${DOCDIR}/hardware/${.CURDIR:T}
|
||||
.else
|
||||
DESTDIR?= ${DOCDIR}/zh_CN.GB2312/hardware/${.CURDIR:T}
|
||||
.endif
|
||||
|
||||
# Force include of the autogenerated catalog. It has to be set
|
||||
# directly in the CATALOG variable since doc.docbook.mk check if each
|
||||
# catalog file exist for the other *CATALOG variables, and
|
||||
# catalog-auto does not exist yet when that check is performed,
|
||||
# causing catalog-auto not to be added to CATALOGS which breaks the
|
||||
# build.
|
||||
CATALOGS+= -c ${DEV-AUTODIR}/catalog-auto
|
||||
@ -1,25 +0,0 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
#
|
||||
# Original Revision: 1.2
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= proc-amd64.sgml
|
||||
SRCS+= ../common/hw.ent
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/dev.sgml
|
||||
SRCS+= ${DEV-AUTODIR}/catalog-auto
|
||||
SRCS+= ${DEV-AUTODIR}/dev-auto.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,30 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.3
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % devauto PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN">
|
||||
%devauto;
|
||||
<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "amd64">
|
||||
<!ENTITY arch.print "AMD64">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
§.intro;
|
||||
§.proc.amd64;
|
||||
§.dev;
|
||||
</article>
|
||||
@ -1,66 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.6
|
||||
$FreeBSD$
|
||||
-->
|
||||
<sect1 id="proc">
|
||||
<title>支持的处理器和主板</title>
|
||||
|
||||
<para>从 2003 年中开始， &os;/&arch; 提供了 &arch.print;
|
||||
(<quote>Hammer</quote>) 和 Intel EM64T 架构的支持，
|
||||
现在则更成为了 Tier-1 平台 (完全支持的架构)，
|
||||
您可以预期它在 &os; 操作系统的各个方面拥有产品级的品质，
|
||||
包括安装和开发环境。</para>
|
||||
|
||||
<para>请注意这个架构有两个名字，
|
||||
AMD64 (AMD) 和 Intel EM64T (扩展内存 64-位 技术)。
|
||||
两种架构的 64-位 模式几乎是完全相互兼容的，
|
||||
而 &os;/&arch; 则应该两者都能支持。</para>
|
||||
|
||||
<para>撰写本文时， 已经确认能够支持下列处理器：</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>AMD Athlon64 (<quote>Clawhammer</quote>).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>AMD Opteron (<quote>Sledgehammer</quote>).</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Intel 64-位 至强 (<quote>Nacona</quote>).
|
||||
这款处理器采用 90nm 制程工艺制造， 运行于
|
||||
2.80 到 3.60 GHz (FSB 800MHz) 并配合 Intel E7520/E7525/E7320 芯片组。</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>支持 Intel EM64T 的 Intel 奔腾 4 处理器
|
||||
(<quote>Prescott</quote>).
|
||||
这些处理器采用 90nm 制程工艺制造，
|
||||
使用 FC-LGA775 封装， 运行于 3.20F/3.40F/3.60F GHz
|
||||
并配合 Intel 925X Express 芯片组。
|
||||
相关的 S-Spec 编号为 SL7L9, SL7L8, SL7LA, SL7NZ, SL7PZ,
|
||||
和 SL7PX。 请注意标记为 5xx 号的处理器并不支持
|
||||
EM64T。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>Intel EM64T 是 IA-32 (x86) 的一个扩展版本， 并不同于
|
||||
Intel IA-64 (安腾) 架构， 后者为 &os;/ia64 所支持。
|
||||
一些 Intel 的较早的文档将 Intel EM64T 称为
|
||||
<quote>64-位扩展技术</quote> 或 <quote>IA-32e</quote>。</para>
|
||||
|
||||
<para>目前为止测试过的最大内存配置是 8GB。 SMP 支持已经于近日完工，
|
||||
并相当稳定了。</para>
|
||||
|
||||
<para>在许多方面， &os;/&arch; 和 &os;/i386 非常相像， 特别是所支持的设备方面。
|
||||
在 64-位 代码清理以及一些 (特别是旧的) 驱动方面还存在一些问题。
|
||||
一般来说， 在其他 64-位 平台上运行正常的驱动应该可以使用。</para>
|
||||
|
||||
<para>&os;/&arch; 是 &os; 一个非常年轻的平台。 尽管核心的
|
||||
&os; 内核和基本系统组件是相当健壮的，
|
||||
但可能还存在一些不太完善的地方， 特别是对第三方软件包的支持方面。</para>
|
||||
|
||||
</sect1>
|
||||
1373
release/doc/zh_CN.GB2312/hardware/article.sgml
Normal file
1373
release/doc/zh_CN.GB2312/hardware/article.sgml
Normal file
File diff suppressed because it is too large
Load Diff
@ -1,23 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.8
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<articleinfo>
|
||||
<title>&os;/&arch; &release.current; 兼容硬件说明</title>
|
||||
|
||||
<corpauthor>The &os; Documentation Project</corpauthor>
|
||||
|
||||
<copyright>
|
||||
<year>2000</year>
|
||||
<year>2001</year>
|
||||
<year>2002</year>
|
||||
<year>2003</year>
|
||||
<year>2004</year>
|
||||
<year>2005</year>
|
||||
<year>2006</year>
|
||||
<holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
|
||||
</copyright>
|
||||
</articleinfo>
|
||||
@ -1,967 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.306
|
||||
-->
|
||||
|
||||
<!--
|
||||
|
||||
The "Supported Devices" section of the release notes.
|
||||
Generally processor-independent, with conditional text
|
||||
inclusion handling any architecture-dependent text.
|
||||
|
||||
Within each subsection describing a class of hardware
|
||||
(i.e. Ethernet interfaces), list broad groups of devices
|
||||
alphabetically as paragraphs sorted alphabetically (frequently
|
||||
these groups will be arranged by manufacturer, i.e. 3Com
|
||||
Ethernet interfaces).
|
||||
|
||||
Where applicable, a "Miscellaneous" section may follow all
|
||||
other named sections.
|
||||
|
||||
These guidelines are not hard-and-fast rules, and exceptions
|
||||
will occur. Following these guidelines (vague as they may be)
|
||||
is highly recommended to try to keep the formatting of
|
||||
this section consistent.
|
||||
|
||||
We give manpage references using the &man entities where
|
||||
possible. If a driver has no manpage (and consequently no
|
||||
&man entity, we simply give the name of the driver).
|
||||
Please avoid doing &man entity conversions unless you
|
||||
know for sure that an entity and manpage exist; sweeps through
|
||||
this file to fix "missed" conversions are likely to break the
|
||||
build.
|
||||
-->
|
||||
|
||||
<sect1 id="support">
|
||||
<sect1info>
|
||||
<pubdate>$FreeBSD$</pubdate>
|
||||
</sect1info>
|
||||
|
||||
<title>支持的硬件</title>
|
||||
|
||||
<para>这一节描述了目前已知的被 &os 在
|
||||
&arch.print; 平台上支持的硬件。 其他配置可能也能用， 只是尚未测试过。
|
||||
我们鼓励您对这份列表的内容进行反馈、 更新和修正。</para>
|
||||
|
||||
<para>这份列表尽可能包含了驱动程序能够适用的一类设备。
|
||||
如果驱动程序在 &os; 基本安装包中有联机手册 (绝大多数应该有)
|
||||
则会在这里引用。 支持的具体设备或控制器型号等等，
|
||||
可以在联机手册中找到。</para>
|
||||
|
||||
<note>
|
||||
<para>设备列表是直接从 &os; 联机手册中生成的。 这意味着一些设备，
|
||||
如果它们被多种不同的驱动程序支持的话， 可能会相应地出现多次。</para>
|
||||
</note>
|
||||
|
||||
<sect2 id="disk">
|
||||
<title>磁盘控制器</title>
|
||||
|
||||
<para arch="i386,alpha,sparc64,ia64,pc98,amd64">IDE/ATA 控制器 (&man.ata.4; 驱动程序)</para>
|
||||
<para arch="pc98">IDE/ATA 控制器 (wdc 驱动程序)
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>板载 IDE 控制器</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
&hwlist.aac;
|
||||
|
||||
&hwlist.adv;
|
||||
|
||||
&hwlist.adw;
|
||||
|
||||
&hwlist.aha;
|
||||
|
||||
&hwlist.ahb;
|
||||
|
||||
&hwlist.ahc;
|
||||
|
||||
&hwlist.ahd;
|
||||
|
||||
&hwlist.aic;
|
||||
|
||||
&hwlist.amd;
|
||||
|
||||
&hwlist.amr;
|
||||
|
||||
&hwlist.arcmsr;
|
||||
|
||||
&hwlist.asr;
|
||||
|
||||
&hwlist.bt;
|
||||
|
||||
&hwlist.ciss;
|
||||
|
||||
&hwlist.ct;
|
||||
|
||||
&hwlist.dpt;
|
||||
<note>
|
||||
<para arch="i386,amd64">支持从这种控制器启动。 但 EISA
|
||||
卡目前并不支持。</para>
|
||||
|
||||
<para arch="alpha">由于 SRM 的限制， 不支持从这种控制器启动。</para>
|
||||
</note>
|
||||
|
||||
&hwlist.esp;
|
||||
|
||||
&hwlist.hptmv;
|
||||
|
||||
&hwlist.ida;
|
||||
|
||||
&hwlist.iir;
|
||||
|
||||
&hwlist.ips;
|
||||
|
||||
&hwlist.isp;
|
||||
|
||||
&hwlist.mfi;
|
||||
|
||||
&hwlist.mlx;
|
||||
|
||||
<note>
|
||||
<para arch="i386,amd64">能够支持从这些控制器启动。 不支持 EISA
|
||||
适配器。</para>
|
||||
|
||||
<para arch="alpha">由于 SRM 的限制， 不支持从这些控制器启动。
|
||||
Digital/Compaq 为 Alpha 系统作为 StorageWorks 系列一部分出售的 DAC960
|
||||
控制器， 例如 KZPSC 或 KZPAC 可以从 SRM 启动。 注意这些卡使用
|
||||
2.x 的固件。 目前尚不知道新版固件是否能配合 SRM 启动。</para>
|
||||
</note>
|
||||
|
||||
&hwlist.mly;
|
||||
|
||||
&hwlist.mpt;
|
||||
|
||||
&hwlist.ncr;
|
||||
|
||||
&hwlist.ncv;
|
||||
|
||||
&hwlist.nsp;
|
||||
|
||||
&hwlist.pst;
|
||||
|
||||
&hwlist.rr232x;
|
||||
|
||||
&hwlist.stg;
|
||||
|
||||
&hwlist.sym;
|
||||
|
||||
&hwlist.trm;
|
||||
|
||||
&hwlist.twa;
|
||||
|
||||
&hwlist.twe;
|
||||
|
||||
&hwlist.vpo;
|
||||
|
||||
<para arch="i386">wds(4) 驱动程序支持 WD7000 SCSI 控制器</para>
|
||||
|
||||
<para>所有支持的 SCSI 控制器都提供了完整的
|
||||
SCSI-I, SCSI-II, 和 SCSI-III 设备支持， 包括硬盘， 光盘，
|
||||
磁带机 (包括 DAT, 8mm Exabyte, Mammoth, 以及 DLT), 盘柜,
|
||||
处理器目标设备 以及 CD-ROM 驱动器。 支持 CD-ROM 命令的
|
||||
WORM 设备则提供了只读的支持
|
||||
(例如 &man.cd.4;)。 WORM/CD-R/CD-RW 写操作的支持由
|
||||
&man.cdrecord.1; 提供， 它是 Ports Collection 中
|
||||
<filename role="package">sysutils/cdrtools</filename> port
|
||||
的一部分。</para>
|
||||
|
||||
<para>目前， 对以下 CD-ROM 文件系统类型提供支持：
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>SCSI 接口 (也包括 ProAudio Spectrum 和
|
||||
SoundBlaster SCSI) (&man.cd.4;)</para>
|
||||
</listitem>
|
||||
|
||||
<listitem arch="i386">
|
||||
<para>Sony 专有接口 (所有型号) (&man.scd.4;)</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>ATAPI IDE 接口 (&man.acd.4;)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386">以下设备不再维护了：
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Mitsumi 专有的 CD-ROM 接口 (所有型号) (&man.mcd.4;)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
</sect2>
|
||||
<sect2 id="ethernet">
|
||||
<title>以太网接口</title>
|
||||
|
||||
&hwlist.aue;
|
||||
|
||||
&hwlist.axe;
|
||||
|
||||
&hwlist.bce;
|
||||
|
||||
<para arch="i386,amd64">基于 Broadcom BCM4401 的高速以太网适配器
|
||||
(&man.bfe.4; 驱动程序)</para>
|
||||
|
||||
&hwlist.bge;
|
||||
|
||||
&hwlist.cdce;
|
||||
|
||||
<para arch="i386,amd64">基于 Crystal Semiconductor CS89x0 的 NIC
|
||||
(&man.cs.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
&hwlist.cue;
|
||||
|
||||
&hwlist.dc;
|
||||
|
||||
&hwlist.de;
|
||||
|
||||
&hwlist.ed;
|
||||
|
||||
&hwlist.em;
|
||||
|
||||
&hwlist.ep;
|
||||
|
||||
&hwlist.ex;
|
||||
|
||||
&hwlist.fe;
|
||||
|
||||
&hwlist.fxp;
|
||||
|
||||
&hwlist.gem;
|
||||
|
||||
&hwlist.hme;
|
||||
|
||||
&hwlist.ie;
|
||||
|
||||
&hwlist.ixgb;
|
||||
|
||||
&hwlist.kue;
|
||||
|
||||
&hwlist.lge;
|
||||
|
||||
&hwlist.mxge;
|
||||
|
||||
&hwlist.my;
|
||||
|
||||
&hwlist.nge;
|
||||
|
||||
&hwlist.nve;
|
||||
|
||||
&hwlist.pcn;
|
||||
|
||||
&hwlist.re;
|
||||
|
||||
&hwlist.rl;
|
||||
|
||||
&hwlist.rue;
|
||||
|
||||
&hwlist.sf;
|
||||
|
||||
&hwlist.sis;
|
||||
|
||||
&hwlist.sk;
|
||||
|
||||
&hwlist.sn;
|
||||
|
||||
&hwlist.snc;
|
||||
|
||||
&hwlist.ste;
|
||||
|
||||
&hwlist.stge;
|
||||
|
||||
&hwlist.ti;
|
||||
|
||||
&hwlist.tl;
|
||||
|
||||
<para arch="i386,pc98,amd64">基于 SMC 83c17x (EPIC) 的以太网 NIC (&man.tx.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
&hwlist.txp;
|
||||
|
||||
&hwlist.udav;
|
||||
|
||||
&hwlist.vge;
|
||||
|
||||
&hwlist.vr;
|
||||
|
||||
&hwlist.vx;
|
||||
|
||||
&hwlist.wb;
|
||||
|
||||
&hwlist.xe;
|
||||
|
||||
&hwlist.xl;
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="tokenring">
|
||||
<title>Token Ring Interfaces</title>
|
||||
|
||||
&hwlist.oltr;
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="fddi">
|
||||
<title>FDDI 接口</title>
|
||||
<para arch="i386,pc98,alpha">DEC DEFPA PCI (&man.fpa.4; 驱动程序)</para>
|
||||
<para arch="i386">DEC DEFEA EISA (&man.fpa.4; 驱动程序)</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="atm">
|
||||
<title>ATM 接口</title>
|
||||
|
||||
<para arch="i386,pc98">基于 Midway 的 ATM 接口 (&man.en.4;
|
||||
驱动程序)</para>
|
||||
|
||||
<para arch="i386,pc98,sparc64">FORE Systems, Inc. PCA-200E ATM PCI
|
||||
适配器 (hfa 和 &man.fatm.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386,pc98">基于 IDT NICStAR 77201/211 的 ATM 适配器 (&man.idt.4;
|
||||
驱动程序)</para>
|
||||
|
||||
<para arch="i386,pc98,sparc64">FORE Systems, Inc. HE155 和 HE622
|
||||
ATM 接口 (&man.hatm.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386,pc98">基于 IDT77252 的 ATM 卡 (&man.patm.4;
|
||||
驱动程序)</para>
|
||||
|
||||
</sect2>
|
||||
<sect2 id="wlan">
|
||||
<title>无线网络接口</title>
|
||||
|
||||
<para arch="i386">NCR / AT&T / Lucent Technologies WaveLan T1-speed
|
||||
ISA/radio LAN 卡 (&man.wl.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386,pc98,amd64">Lucent Technologies WaveLAN/IEEE 802.11b
|
||||
无线网络适配器以及软件通用型的采用 Lucent Hermes, Intersil
|
||||
PRISM-II, Intersil PRISM-2.5, Intersil Prism-3, 和 Symbol
|
||||
Spectrum24 芯片组的网卡 (&man.wi.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
<para arch="i386,pc98,amd64">Cisco/Aironet 802.11b 无线网络适配器 (&man.an.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
<para arch="i386,pc98">Raytheon Raylink 2.4GHz 无线网络适配器 (&man.ray.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
&hwlist.awi;
|
||||
|
||||
&hwlist.cnw;
|
||||
|
||||
&hwlist.ath;
|
||||
</sect2>
|
||||
|
||||
<sect2 id="misc-network">
|
||||
<title>其他网络设备</title>
|
||||
|
||||
&hwlist.ce;
|
||||
|
||||
&hwlist.cx;
|
||||
|
||||
&hwlist.cp;
|
||||
|
||||
&hwlist.ctau;
|
||||
|
||||
<para arch="i386">Granch SBNI12 点对点通讯适配器
|
||||
(&man.sbni.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
<para arch="i386">Granch SBNI16 SHDSL 调制解调器 (&man.sbsh.4;
|
||||
驱动程序)</para>
|
||||
|
||||
&hwlist.cm;
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="isdn">
|
||||
<title>ISDN 接口</title>
|
||||
<para arch="i386">AcerISDN P10 ISA PnP (实验性的)</para>
|
||||
<para arch="i386">Asuscom ISDNlink 128K ISA</para>
|
||||
<para arch="i386">ASUSCOM P-IN100-ST-D (以及其他基于 Winbond W6692 的卡)</para>
|
||||
<para arch="i386">AVM
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>A1</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>B1 ISA (在 V2.0 上测试过)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>B1 PCI (在 V4.0 上测试过)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Fritz!Card classic</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Fritz!Card PnP</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Fritz!Card PCI</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Fritz!Card PCI, Version 2</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>T1</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para arch="i386">Creatix
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>ISDN-S0</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>ISDN-S0 P&P</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para arch="i386">Compaq Microcom 610 ISDN (Compaq series PSB2222I) ISA PnP</para>
|
||||
<para arch="i386">Dr. Neuhaus Niccy Go@ 及兼容</para>
|
||||
<para arch="i386">Dynalink IS64PPH 和 IS64PPH+</para>
|
||||
<para arch="i386">Eicon Diehl DIVA 2.0 和 2.02</para>
|
||||
<para arch="i386">ELSA
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>ELSA PCC-16</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>QuickStep 1000pro ISA</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>MicroLink ISDN/PCI</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>QuickStep 1000pro PCI</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para arch="i386">ITK ix1 Micro ( < V.3, 非 PnP 版本 )</para>
|
||||
<para arch="i386">Sedlbauer Win Speed</para>
|
||||
<para arch="i386">Siemens I-Surf 2.0</para>
|
||||
<para arch="i386">TELEINT ISDN SPEED No.1 (试验性支持)</para>
|
||||
<para arch="i386">Teles
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>S0/8</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>S0/16</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>S0/16.3</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>S0/16.3 PnP</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>16.3c ISA PnP (试验性支持)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Teles PCI-TJ</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
<para arch="i386">Traverse Technologies NETjet-S PCI</para>
|
||||
<para arch="i386">USRobotics Sportster ISDN TA intern</para>
|
||||
<para arch="i386">基于 Winbond W6692 的 PCI 卡</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="serial">
|
||||
<title>串口</title>
|
||||
|
||||
<para arch="i386,alpha,amd64"><quote>PC 标准</quote> 基于 8250、 16450， 以及基于 16550 的串口 (&man.sio.4; 驱动程序)</para>
|
||||
|
||||
&hwlist.uart;
|
||||
|
||||
&hwlist.scc;
|
||||
|
||||
<para arch="i386,alpha,amd64">使用共享 IRQ 的 AST 4 口串口卡</para>
|
||||
|
||||
<para arch="i386">ARNET 串口卡 (&man.ar.4; 驱动程序)
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>使用共享 IRQ 的 ARNET 8 口串口卡</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>ARNET (现在是 Digiboard) Sync 570/i 高速串口</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386">Boca 多口串口卡
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Boca BB1004 4-口串口卡
|
||||
(<emphasis>不</emphasis> 支持调制解调器)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Boca IOAT66 6-口串口卡 (支持调制解调器)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Boca BB1008 8-口串口卡
|
||||
(<emphasis>不</emphasis> 支持调制解调器)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Boca BB2016 16-口串口卡 (支持调制解调器)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386,alpha">Comtrol Rocketport 卡 (&man.rp.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386">Cyclades Cyclom-Y 串口板 (&man.cy.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386">使用共享 IRQ 的 STB 4 口串口卡</para>
|
||||
|
||||
<para arch="i386">DigiBoard 智能串口卡 (digi 驱动程序)
|
||||
</para>
|
||||
|
||||
<para arch="i386,ia64,amd64">基于 PCI 的多口串口板 (&man.puc.4;
|
||||
驱动程序)
|
||||
<itemizedlist>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Actiontech 56K PCI</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Avlab Technology, PCI IO 2S 和 PCI IO 4S</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Comtrol RocketPort 550</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Decision Computers PCCOM 4-多口串口 和 双口 RS232/422/485</para>
|
||||
</listitem>
|
||||
<listitem arch="ia64">
|
||||
<para>Diva Serial (GSP) 多口 UART</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Dolphin Peripherals 4025/4035/4036</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>IC Book Labs Dreadnought 16x Lite 和 Pro</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Lava Computers 2SP-PCI/DSerial-PCI/Quattro-PCI/Octopus-550</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Middle Digital, Weasle 串口</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Moxa Industio CP-114, Smartio C104H-PCI 和 C168H/PCI</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>NEC PK-UG-X001 和 PK-UG-X008</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Netmos NM9835 PCI-2S-550</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Oxford Semiconductor OX16PCI954 PCI UART</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Syba Tech SD-LAB PCI-4S2P-550-ECP</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>SIIG Cyber I/O PCI 16C550/16C650/16C850</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>SIIG Cyber 2P1S PCI 16C550/16C650/16C850</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>SIIG Cyber 2S1P PCI 16C550/16C650/16C850</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>SIIG Cyber 4S PCI 16C550/16C650/16C850</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>SIIG Cyber Serial (Single 和 Dual) PCI 16C550/16C650/16C850</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Syba Tech Ltd. PCI-4S2P-550-ECP</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>Titan PCI-200H 和 PCI-800H</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>US Robotics (3Com) 3CP5609 调制解调器</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,amd64">
|
||||
<para>VScom PCI-400 和 PCI-800</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
&hwlist.rc;
|
||||
|
||||
&hwlist.sr;
|
||||
|
||||
<para arch="i386,amd64">支持 Specialix SI/XIO/SX 多口串口卡, 同时包括较旧的
|
||||
SIHOST2.x 以及 <quote>增强型</quote> (基于 transputer，
|
||||
也就是 JET 的) 宿主卡 (ISA、 EISA 和 PCI 接口)
|
||||
注意， 最新的 SX+ PCI 卡目前还不支持。
|
||||
(&man.si.4; 驱动程序)</para>
|
||||
|
||||
<para arch="pc98">内置串口 (&man.sio.4; 驱动程序)
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>PC-9801 板载</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>PC-9821 第二 CCU (flags 0x12000000)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="pc98">NEC PC-9861K, PC-9801-101 和 Midori-Denshi MDC-926Rs (&man.sio.4; 驱动程序)
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>COM2 (flags 0x01000000)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>COM3 (flags 0x02000000)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="pc98">NEC PC-9801-120 (&man.sio.4; 驱动程序)</para>
|
||||
<note arch="pc98">
|
||||
<para>需要在内核配置中指定 "flags 0x11000000"。</para>
|
||||
</note>
|
||||
|
||||
<para arch="pc98">Microcore MC-16550, MC-16550II, MC-RS98 (&man.sio.4; 驱动程序)</para>
|
||||
<note arch="pc98">
|
||||
<para>需要在内核配置中指定 "flags 0x14000?01"。</para>
|
||||
</note>
|
||||
|
||||
<para arch="pc98">Media Intelligent RSB-2000, RSB-3000 and AIWA B98-02 (&man.sio.4; 驱动程序)</para>
|
||||
<note arch="pc98">
|
||||
<para>需要在内核配置中指定 "flags 0x15000?01"。</para>
|
||||
</note>
|
||||
|
||||
<para arch="pc98">Media Intelligent RSB-384 (&man.sio.4; 驱动程序)</para>
|
||||
<note arch="pc98">
|
||||
<para>需要在内核配置中指定 "flags 0x16000001"。</para>
|
||||
</note>
|
||||
|
||||
<para arch="pc98">I-O DATA RSA-98III (&man.sio.4; 驱动程序)</para>
|
||||
<note arch="pc98">
|
||||
<para>需要在内核配置中指定 "flags 0x18000?01"。</para>
|
||||
</note>
|
||||
|
||||
<para arch="pc98">Hayes ESP98 (&man.sio.4; 驱动程序)</para>
|
||||
<note arch="pc98">
|
||||
<para>需要在内核配置中指定 "options COM_ESP" 和 "flags 0x19000000"。</para>
|
||||
</note>
|
||||
|
||||
</sect2>
|
||||
<sect2 id="sound">
|
||||
<title>声音设备</title>
|
||||
|
||||
&hwlist.snd.ad1816;
|
||||
|
||||
&hwlist.snd.als4000;
|
||||
|
||||
&hwlist.snd.atiixp;
|
||||
|
||||
&hwlist.snd.audiocs;
|
||||
|
||||
&hwlist.snd.cmi;
|
||||
|
||||
&hwlist.snd.cs4281;
|
||||
|
||||
&hwlist.snd.csa;
|
||||
|
||||
&hwlist.snd.ds1;
|
||||
|
||||
&hwlist.snd.emu10k1;
|
||||
|
||||
&hwlist.snd.emu10kx;
|
||||
|
||||
&hwlist.snd.envy24;
|
||||
|
||||
&hwlist.snd.envy24ht;
|
||||
|
||||
&hwlist.snd.es137x;
|
||||
|
||||
&hwlist.snd.ess;
|
||||
|
||||
&hwlist.snd.fm801;
|
||||
|
||||
&hwlist.snd.gusc;
|
||||
|
||||
&hwlist.snd.hda;
|
||||
|
||||
&hwlist.snd.ich;
|
||||
|
||||
&hwlist.snd.maestro;
|
||||
|
||||
&hwlist.snd.maestro3;
|
||||
|
||||
&hwlist.snd.mss;
|
||||
|
||||
&hwlist.snd.neomagic;
|
||||
|
||||
&hwlist.snd.sbc;
|
||||
|
||||
&hwlist.snd.solo;
|
||||
|
||||
&hwlist.snd.spicds;
|
||||
|
||||
&hwlist.snd.t4dwave;
|
||||
|
||||
&hwlist.snd.via8233;
|
||||
|
||||
&hwlist.snd.via82c686;
|
||||
|
||||
&hwlist.snd.vibes;
|
||||
|
||||
<para arch="pc98">NEC PC-9801-73, 86 及兼容 (nss 驱动程序)
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>NEC A-MATE 内置声音</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Q-Vision WaveStar, WaveMaster</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="pc98">NEC X-MATE, CanBe, ValueStar 内置 (mss 驱动程序)</para>
|
||||
|
||||
<para arch="pc98">Creative Technologies SoundBlaster(98) (&man.sb.4;
|
||||
驱动程序)</para>
|
||||
|
||||
<para arch="pc98">I-O DATA CD-BOX (&man.sb.4; 驱动程序)</para>
|
||||
|
||||
<para arch="pc98">MPU-401 及兼容接口 (mpu 驱动)
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Q-Vision WaveStar</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="camera">
|
||||
<title>照相机和视频捕捉设备</title>
|
||||
|
||||
&hwlist.bktr;
|
||||
|
||||
<para arch="i386">Connectix QuickCam</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="usb">
|
||||
<title>USB 设备</title>
|
||||
|
||||
<para arch="alpha,i386,ia64,pc98,amd64">&os; 能够支持一系列 USB 外设；
|
||||
已知能够正确使用的设备在这节列出。 由于 USB 设备天生的通用性，
|
||||
除了少量比较有个性的设备之外， 同一类型的设备几乎都能被支持，
|
||||
即使在这里没有明确地列出。</para>
|
||||
|
||||
<note arch="alpha,i386,ia64,pc98,amd64">
|
||||
<para>USB 以太网适配器可以在 <link
|
||||
linkend="ethernet">以太网接口</link> 一节找到。</para>
|
||||
</note>
|
||||
|
||||
<note arch="alpha,i386,ia64,pc98,amd64">
|
||||
<para>USB 蓝牙适配器可以在 <link
|
||||
linkend="bluetooth">蓝牙</link> 一节找到。</para>
|
||||
</note>
|
||||
|
||||
&hwlist.ohci;
|
||||
|
||||
&hwlist.uhci;
|
||||
|
||||
<para arch="i386,ia64,pc98,amd64">采用 EHCI 接口的 USB 2.0
|
||||
控制器 (&man.ehci.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386,ia64,pc98,alpha,amd64">集线器
|
||||
</para>
|
||||
<para arch="i386,ia64,pc98,alpha,amd64">键盘 (&man.ukbd.4; 驱动程序)
|
||||
</para>
|
||||
<para arch="i386,pc98,amd64">其他
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Assist Computer Systems PC Camera C-M1</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>ActiveWire I/O 板</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Creative Technology Video Blaster WebCam Plus</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>D-Link DSB-R100 USB Radio (&man.ufm.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Mirunet AlphaCam Plus</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
&hwlist.urio;
|
||||
|
||||
&hwlist.umodem;
|
||||
|
||||
<para arch="i386,ia64,pc98,alpha,amd64">鼠标器 (&man.ums.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
&hwlist.ulpt;
|
||||
|
||||
&hwlist.ubsa;
|
||||
|
||||
&hwlist.ubser;
|
||||
|
||||
&hwlist.uftdi;
|
||||
|
||||
&hwlist.uplcom;
|
||||
|
||||
&hwlist.umct;
|
||||
|
||||
&hwlist.uscanner;
|
||||
|
||||
&hwlist.umass;
|
||||
|
||||
<para arch="i386,pc98,amd64">声音设备 (&man.uaudio.4; 驱动程序)
|
||||
</para>
|
||||
|
||||
&hwlist.uvisor;
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="firewire">
|
||||
<title>IEEE 1394 (火线) 设备</title>
|
||||
|
||||
&hwlist.fwohci;
|
||||
|
||||
<para arch="i386,sparc64,amd64">串行总线协议 2 (SBP-2)
|
||||
存储设备 (&man.sbp.4; 驱动程序)</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="bluetooth">
|
||||
<title>蓝牙设备</title>
|
||||
|
||||
&hwlist.ng.bt3c;
|
||||
|
||||
&hwlist.ng.ubt;
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="crypto-accel">
|
||||
<title>密码学加速器</title>
|
||||
|
||||
&hwlist.hifn;
|
||||
|
||||
&hwlist.safe;
|
||||
|
||||
&hwlist.ubsec;
|
||||
</sect2>
|
||||
|
||||
<sect2 id="misc">
|
||||
<title>其他</title>
|
||||
|
||||
<para arch="i386,pc98,amd64">FAX-Modem/PCCARD
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>MELCO IGM-PCM56K/IGM-PCM56KH</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Nokia Card Phone 2.0 (gsm900/dcs1800 HSCSD 终端)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386,pc98,alpha,amd64">软驱 (&man.fdc.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386,alpha,amd64">VGA-兼容 显示卡
|
||||
(&man.vga.4; 驱动程序)
|
||||
|
||||
<note>
|
||||
<para>关于特定显卡与 <application>Xorg</application> 的兼容信息，
|
||||
可以在 <ulink
|
||||
url="http://www.x.org/"></ulink> 找到。</para>
|
||||
</note>
|
||||
|
||||
</para>
|
||||
|
||||
<para arch="i386,pc98,alpha,ia64,amd64">键盘包括：
|
||||
<itemizedlist>
|
||||
<listitem arch="i386,alpha">
|
||||
<para>AT-风格的 键盘 (&man.atkbd.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,alpha,amd64">
|
||||
<para>PS/2 键盘 (&man.atkbd.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
<listitem arch="pc98">
|
||||
<para>标准键盘</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,pc98,alpha,ia64,amd64">
|
||||
<para>USB 键盘 (&man.ukbd.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386,pc98,alpha,ia64,amd64">定点设备包括：
|
||||
<itemizedlist>
|
||||
<listitem arch="i386,pc98,amd64">
|
||||
<para>总线鼠标和兼容设备 (&man.mse.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,alpha,amd64">
|
||||
<para>PS/2 鼠标和兼容设备， 也包括一系列笔记本定点设备
|
||||
(&man.psm.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>串口鼠标和兼容设备</para>
|
||||
</listitem>
|
||||
<listitem arch="i386,pc98,alpha,ia64,amd64">
|
||||
<para>USB 鼠标 (&man.ums.4; 驱动程序)</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>&man.moused.8; 提供了如何在 &os; 中使用定点设备的进一步信息。
|
||||
关于如何在 <application>Xorg</application> 中使用这类设备的信息， 可以在
|
||||
<ulink url="http://www.x.org/"></ulink> 找到。</para>
|
||||
</note>
|
||||
</para>
|
||||
|
||||
<para arch="i386,alpha,amd64"><quote>PC 标准</quote> 并口 (&man.ppc.4; 驱动程序)</para>
|
||||
<para arch="pc98"><quote>PC-9821 标准</quote> 并口 (&man.ppc.4; 驱动程序)</para>
|
||||
|
||||
<para arch="i386,amd64">PC-兼容 游戏杆 (&man.joy.4; 驱动程序)</para>
|
||||
|
||||
<para arch="pc98">SoundBlaster(98) 的游戏杆接口 (&man.joy.4;
|
||||
驱动程序)</para>
|
||||
|
||||
<para arch="i386,pc98">PHS Data Communication Card/PCCARD
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>NTT DoCoMo P-in Comp@ct</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>Panasonic KX-PH405</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>SII MC-P200</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386">基于 Xilinx XC6200 的可重配置硬件卡， 与
|
||||
<ulink url="http://www.vcc.com/">Virtual
|
||||
Computers</ulink> 的 HOT1 兼容 (xrpu 驱动程序)。</para>
|
||||
|
||||
<para arch="pc98">NEC PC-98 笔记本的电源管理控制器 (pmc
|
||||
驱动程序)</para>
|
||||
|
||||
<para arch="sparc64">OpenFirmware 控制台 (ofwcons 驱动程序)</para>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
@ -1,19 +0,0 @@
|
||||
<!-- -*- sgml -*- -->
|
||||
<!-- Original Revision: 1.6 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!-- Text constants which probably don't need to be changed.-->
|
||||
|
||||
<!-- Files to be included -->
|
||||
|
||||
<!ENTITY artheader SYSTEM "../common/artheader.sgml">
|
||||
<!ENTITY sect.intro SYSTEM "../common/intro.sgml">
|
||||
<!ENTITY sect.proc.alpha SYSTEM "../alpha/proc-alpha.sgml">
|
||||
<!ENTITY sect.proc.amd64 SYSTEM "../amd64/proc-amd64.sgml">
|
||||
<!ENTITY sect.proc.i386 SYSTEM "../i386/proc-i386.sgml">
|
||||
<!ENTITY sect.proc.ia64 SYSTEM "../ia64/proc-ia64.sgml">
|
||||
<!ENTITY sect.proc.powerpc SYSTEM "../powerpc/proc-powerpc.sgml">
|
||||
<!ENTITY sect.proc.pc98 SYSTEM "../pc98/proc-pc98.sgml">
|
||||
<!ENTITY sect.proc.sparc64 SYSTEM "../sparc64/proc-sparc64.sgml">
|
||||
<!ENTITY sect.dev SYSTEM "../common/dev.sgml">
|
||||
|
||||
@ -1,24 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.7
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<sect1 id="intro">
|
||||
<title>介绍</title>
|
||||
|
||||
<para>这份文档包含了 &os; &release.current; (也记为 &os;/&arch; &release.current;)
|
||||
在 &arch.print; 硬件平台上的兼容硬件说明。 它列出了已知能够在这一平台上使用的硬件，
|
||||
以及一些有用的启动时内核定制项， 用以支持新的设备。</para>
|
||||
|
||||
<note>
|
||||
<para>这份文档包含的信息是 &arch.print;
|
||||
硬件平台所专用的。 不同硬件架构上的硬件兼容说明可能有一些细节上的差异。</para>
|
||||
</note>
|
||||
|
||||
<para arch="ia64">关于 &os;/&arch; 的更多信息可以在
|
||||
<ulink url="&url.base;/platforms/ia64/index.html">&os;/&arch;
|
||||
Project</ulink> 上找到。</para>
|
||||
|
||||
</sect1>
|
||||
@ -1,24 +0,0 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
# Original Revision: 1.6
|
||||
#
|
||||
# $FreeBSD$
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= proc-i386.sgml
|
||||
SRCS+= ../common/hw.ent
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/dev.sgml
|
||||
SRCS+= ${DEV-AUTODIR}/catalog-auto
|
||||
SRCS+= ${DEV-AUTODIR}/dev-auto.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,30 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
Original Revision: 1.6
|
||||
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % devauto PUBLIC "-//FreeBSD//ENTITIES Auto Generated Device Lists//EN">
|
||||
%devauto;
|
||||
<!ENTITY % sections SYSTEM "../common/hw.ent"> %sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "i386">
|
||||
<!ENTITY arch.print "i386">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
§.intro;
|
||||
§.proc.i386;
|
||||
§.dev;
|
||||
</article>
|
||||
@ -1,80 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.14
|
||||
$FreeBSD$
|
||||
-->
|
||||
<sect1 id="proc">
|
||||
<title>支持的处理器和主板</title>
|
||||
|
||||
<para>&os;/i386 能够在各式各样的 <quote>IBM PC
|
||||
兼容</quote> 机器上运行。 由于这种架构的硬件非常多，
|
||||
不可能详尽地列举 &os; 所支持的所有设备组合。
|
||||
不过， 这里给出了一些一般的指导原则。</para>
|
||||
|
||||
<para>几乎所有的包含浮点运算单元的 i386-兼容 处理器都能被很好地支持。
|
||||
&os; 支持从 80486 开始的所有 Intel 处理器，
|
||||
其中包括 80486, Pentium, Pentium Pro, Pentium II, Pentium III,
|
||||
Pentium 4, 以及它们的一些变体， 例如 Xeon (至强) 和 Celeron (赛扬)
|
||||
处理器。 所有 i386-兼容 的 AMD 处理器也被支持， 这包括
|
||||
Am486, Am5x86, K5, K6
|
||||
(及其变体), Athlon (包括 Athlon-MP, Athlon-XP, Athlon-4,
|
||||
以及 Athlon Thunderbird), 还有 Duron 处理器。 AMD
|
||||
Élan SC520 嵌入式处理器也在支持之列。 Transmeta
|
||||
Crusoe 被视为支持的处理器， 此外， 还包括来自 Cyrix 和 NexGen
|
||||
的 i386-兼容 处理器。</para>
|
||||
|
||||
<para>这类架构的主板型号也非常众多。 使用
|
||||
ISA, VLB, EISA, AGP, 和 PCI 扩展总线的主板的支持非常完善。
|
||||
此外， 对 IBM PS/2 系列 PC 的 MCA (<quote>MicroChannel</quote>)
|
||||
扩展总线也提供了有限的支持。</para>
|
||||
|
||||
<para>一般而言， &os; 支持对称多处理器 (SMP) 的系统， 尽管一些时候
|
||||
BIOS 或主板的问题可能会造成麻烦。 &a.smp;
|
||||
邮件列表的存档可能能提供一些线索。</para>
|
||||
|
||||
<para>&os; 能够利用 Intel CPU 的超线程 (HTT) 支持并从中受益。 启用了
|
||||
<literal>options SMP</literal> 的内核能够自动检测到附加的逻辑处理器。
|
||||
默认的 &os; 调度器将逻辑处理器等同于一些额外的物理处理器；
|
||||
换言之， 它不会尝试根据同一 CPU 上的逻辑处理器对调度决策实施优化。
|
||||
由于这种简单的调度策略会导致性能不够理想， 某些情况下通过设置
|
||||
<varname>machdep.hlt_logical_cpus</varname> sysctl
|
||||
变量来禁止逻辑处理器可能会改善性能。 此外， 也可以使用
|
||||
<varname>machdep.hlt_cpus</varname> sysctl
|
||||
变量设置空闲循环来禁用某个特定的逻辑处理器。 请参考
|
||||
&man.smp.4; 联机手册来了解详情。</para>
|
||||
|
||||
<para>&os; 能够利用支持物理地址扩展 (PAE) 的 CPU 上的这种能力。
|
||||
启用了 <literal>PAE</literal> 特性的内核能够检测高于 4GB
|
||||
的内存并使用它们。 这一特性对设备驱动和 &os;
|
||||
能够利用的其它特性有一些约束， 请参考 &man.pae.4; 联机手册了解详情。</para>
|
||||
|
||||
<para>一般来说， &os; 能够在基于 i386 的笔记本上运行， 虽然对于特定硬件特性，
|
||||
例如声音， 图形， 电源管理， 以及 PCCARD 扩展槽的支持可能存在程度上的差异。
|
||||
这些特性在不同的机器上迥然不同， 通常需要 &os; 对它们进行各式各样的支持特例，
|
||||
以绕过硬件的问题或其他诡异的毛病。 如有怀疑， 请搜索
|
||||
&a.mobile; 邮件列表的存档以得到有用的资料。</para>
|
||||
|
||||
<para>绝大多数较新的笔记本 (以及许多桌面机) 都使用了高级配置和电源管理
|
||||
(ACPI) 标准。 &os; 通过来自 Intel 的 ACPI 组件架构参考实现来支持 ACPI，
|
||||
在 &man.acpi.4; 联机手册中提供了它的介绍。 在一些机器上使用 ACPI
|
||||
可能会造成不稳定， 此时您可能需要禁用 ACPI 驱动程序，
|
||||
它通常是通过内核模块来加载的。 您可以通过在
|
||||
<filename>/boot/device.hints</filename> 增加下面的行来达到目的：</para>
|
||||
|
||||
<programlisting>hint.acpi.0.disabled="1"</programlisting>
|
||||
|
||||
<para>调试 ACPI 相关问题的用户可能会发现禁用一部分 ACPI
|
||||
功能会很有用。 &man.acpi.4;
|
||||
联机手册提供了关于如何在引导夹在其中进行设置来完成这些工作的详细信息。</para>
|
||||
|
||||
<para>ACPI 依赖于由 BIOS 提供的 Differentiated System Descriptor Table
|
||||
(DSDT)。 一些机器上的 DSDT 无效或不完整， 这可能会导致 ACPI
|
||||
无法正常工作。 用于替代某些机器上的 DSDT 可以在 <ulink
|
||||
url="http://acpi.sourceforge.net/">ACPI4Linux</ulink> 项目的网站中的
|
||||
<ulink
|
||||
url="http://acpi.sourceforge.net/dsdt/index.php">DSDT</ulink>
|
||||
部分找到。 &os; 可以使用这些 DSDT 来代替由 BIOS 提供的
|
||||
DSDT； 参见 &man.acpi.4; 联机手册以获得更多信息。</para>
|
||||
|
||||
</sect1>
|
||||
@ -1,13 +0,0 @@
|
||||
# Original Revision: 1.8
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../..
|
||||
|
||||
SUBDIR= amd64
|
||||
SUBDIR+= ia64
|
||||
SUBDIR+= i386
|
||||
SUBDIR+= pc98
|
||||
SUBDIR+= sparc64
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,8 +0,0 @@
|
||||
# Original Revision: 1.2
|
||||
# $FreeBSD$
|
||||
|
||||
.ifdef NO_LANGCODE_IN_DESTDIR
|
||||
DESTDIR?= ${DOCDIR}/installation/${.CURDIR:T}
|
||||
.else
|
||||
DESTDIR?= ${DOCDIR}/zh_CN.GB2312/installation/${.CURDIR:T}
|
||||
.endif
|
||||
@ -1,21 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/abstract.sgml
|
||||
SRCS+= ../common/install.sgml
|
||||
SRCS+= ../common/layout.sgml
|
||||
SRCS+= ../common/trouble.sgml
|
||||
SRCS+= ../common/upgrade.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,31 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.2
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/install.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "amd64">
|
||||
<!ENTITY arch.print "AMD64">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
&abstract;
|
||||
§.install;
|
||||
§.layout;
|
||||
§.upgrade;
|
||||
§.trouble;
|
||||
</article>
|
||||
@ -1,11 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.2
|
||||
$FreeBSD$ -->
|
||||
|
||||
<abstract>
|
||||
<para>这篇文章对安装
|
||||
&os;/&arch; &release.current; 作了一些简短的说明，特别强调了如何获取
|
||||
&os; 发行版本。 也给出了发现并解决的故障和频繁被问到的问题的记录。</para>
|
||||
</abstract>
|
||||
@ -1,25 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.8
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<articleinfo>
|
||||
<title>&os;/&arch; &release.current; °²×°ËµÃ÷Êé</title>
|
||||
|
||||
<corpauthor>
|
||||
The &os; Project
|
||||
</corpauthor>
|
||||
|
||||
<copyright>
|
||||
<year>2000</year>
|
||||
<year>2001</year>
|
||||
<year>2002</year>
|
||||
<year>2003</year>
|
||||
<year>2004</year>
|
||||
<year>2005</year>
|
||||
<year>2006</year>
|
||||
<holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
|
||||
</copyright>
|
||||
</articleinfo>
|
||||
@ -1,20 +0,0 @@
|
||||
<!-- -*- sgml -*- -->
|
||||
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.2
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!-- Text constants which probably don't need to be changed.-->
|
||||
|
||||
<!-- Files to be included -->
|
||||
|
||||
<!ENTITY artheader SYSTEM "artheader.sgml">
|
||||
<!ENTITY abstract SYSTEM "abstract.sgml">
|
||||
<!ENTITY sect.install SYSTEM "install.sgml">
|
||||
<!ENTITY sect.layout SYSTEM "layout.sgml">
|
||||
<!ENTITY sect.upgrade SYSTEM "upgrade.sgml">
|
||||
<!ENTITY sect.trouble SYSTEM "trouble.sgml">
|
||||
|
||||
@ -1,928 +0,0 @@
|
||||
<!--
|
||||
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.33
|
||||
$FreeBSD$
|
||||
|
||||
install.sgml
|
||||
|
||||
This file has architecture-dependent installation instructions, culled
|
||||
from {alpha,i386}/INSTALL.TXT.
|
||||
|
||||
-->
|
||||
|
||||
<sect1 id="install">
|
||||
<title>安装 &os;</title>
|
||||
|
||||
<para>这一章节介绍了安装一个新的 &os; 发行版本的过程。
|
||||
这些说明重点强调了获取 &os; &release.current;
|
||||
发行版本并开始安装的过程。<ulink
|
||||
url="&url.books.handbook;/install.html">&os;
|
||||
使用手册</ulink>的<ulink
|
||||
url="&url.books.handbook;/"><quote>安装
|
||||
&os;</quote></ulink>一章提供了有关安装程序本身更深层次的信息，
|
||||
包括一个全程截图的指南。</para>
|
||||
|
||||
<para>如果您正在从 &os; 的前一个发行版本升级，请查看
|
||||
<xref linkend="upgrading">的升级说明。</para>
|
||||
|
||||
<sect2 id="getting-started">
|
||||
<title>开始</title>
|
||||
|
||||
<para>可能在安装前要做的最重要的步骤就是阅读 &os;
|
||||
提供的各种各样的安装文档。 与 &os; 这个发行版本相关的文档的 roadmap
|
||||
可以在 <filename>README.TXT</filename>
|
||||
中找到，这个文件通常放在和本文件相同的位置。
|
||||
大部分文档，比如发行注记和硬件兼容性列表也可以在安装程序的
|
||||
Documentation 菜单中查看。</para>
|
||||
|
||||
<para>注意如果您能接入 Internet 的话， &os; <ulink
|
||||
url="&url.books.faq;/">FAQ</ulink> 和 <ulink
|
||||
url="&url.books.handbook;/">使用手册</ulink>
|
||||
的在线版本也可以在 <ulink url="&url.base;/">&os;
|
||||
项目 Web 站点</ulink>上找到。</para>
|
||||
|
||||
<para>这份文档集合可能看起来很吓人，但是阅读它们所花费的时间很可能会节省更多的时间。
|
||||
熟悉可用的资源也有助于处理安装过程中的问题。</para>
|
||||
|
||||
<para>再好的计划有时也会出错， 所以如果您遇到麻烦请看一看
|
||||
<xref linkend="trouble">， 包含了很多有价值的出错处理的信息。
|
||||
在安装之前您也应该阅读升级过的
|
||||
<filename>ERRATA.TXT</filename> 拷贝，
|
||||
因为这会对您的特定发行版本的中间时期所报告的任何问题向您提出警告。</para>
|
||||
|
||||
<important>
|
||||
<para>尽管 &os; 会尽可能地避免偶然的数据丢失，
|
||||
但是如果在安装过程中您做错了什么还是很可能会
|
||||
<emphasis>清空您的整个硬盘</emphasis>。
|
||||
请不要进入 &os; 最后的安装菜单，
|
||||
除非您事先已经对重要数据进行了充分的备份。</para>
|
||||
</important>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>硬件需求</title>
|
||||
|
||||
<!-- i386/pc98 text starts here -->
|
||||
|
||||
<para arch="i386,pc98">&os; 在 &arch.print; 系统上需要 486
|
||||
或更高的处理器， 以及至少 24 MB 的 RAM。
|
||||
最小安装需要至少 150MB 的剩余硬盘空间。 请阅读下面的部分，
|
||||
来了解如何缩小现有的 DOS 分区以便安装 &os; 的方法。</para>
|
||||
|
||||
<!-- alpha text starts here -->
|
||||
|
||||
<para arch="alpha">&arch.print; 体系的 &os; 支持的平台在
|
||||
<filename>HARDWARE.TXT</filename> 中描述。</para>
|
||||
|
||||
<para arch="alpha">您需要一块专门的磁盘来安装
|
||||
&os;/alpha。和其他操作系统共享一块磁盘现在来说是不可行的。
|
||||
这块磁盘需要连接在 SRM 固件支持的 SCSI 控制器上，
|
||||
或者是一块 IDE 磁盘，如果您机器的 SRM 支持从 IDE 磁盘启动的话。</para>
|
||||
|
||||
<para arch="alpha">您的根文件系统必须位于可启动磁盘的第一个分区
|
||||
(partition <literal>a</literal>)。</para>
|
||||
|
||||
<para arch="alpha">您需要针对您的平台的 SRM 控制台固件。
|
||||
有时候，可以在 AlphaBIOS (或 ARC) 固件和 SRM 之间切换。
|
||||
否则的话就必须从销售商的 Web 站点下载最新的固件。</para>
|
||||
|
||||
<!-- sparc64 text starts here -->
|
||||
|
||||
<para arch="sparc64">&arch.print; 体系的 &os; 支持的平台在
|
||||
<filename>HARDWARE.TXT</filename> 中描述。</para>
|
||||
|
||||
<para arch="sparc64">您需要一块专门的磁盘来安装
|
||||
&os;/sparc64。和其他操作系统共享一块磁盘现在来说是不可行的。</para>
|
||||
|
||||
<!-- amd64 text starts here -->
|
||||
<para arch="amd64">&arch.print; 体系的 &os; 需要
|
||||
Athlon64、Athlon64-FX、Opteron 或者更好的处理器来运行。</para>
|
||||
|
||||
<para arch="amd64">如果您有一台机器基于
|
||||
nVidia nForce3 Pro-150，您必须在 BIOS 设定中禁用
|
||||
IO APIC。如果没有一个选项来调整这个，您可能必须禁用
|
||||
ACPI。在 Pro-150 芯片组中有些 bug 我们还没有找到解决方案。</para>
|
||||
|
||||
<!-- generic text starts here -->
|
||||
|
||||
<para>如果您对配置 &os; 的硬件不熟悉，您一定要阅读
|
||||
<filename>HARDWARE.TXT</filename> 文件，它包含了 &os;
|
||||
支持的硬件的重要信息。</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="floppies">
|
||||
<title>软盘映像说明</title>
|
||||
|
||||
<para arch="i386,alpha,pc98">取决于您选择如何来安装
|
||||
&os;，您可能需要创建几张软盘(通常是三张)来开启安装过程。
|
||||
这一章节简要描述了如何创建这些软盘来从 CDROM 或者从 Internet
|
||||
安装。注意一般情况下在一台支持自启动 CDROM 的机器上从 CDROM
|
||||
安装 &os; 的话，这一章节描述的步骤都是不需要的，可以跳过。</para>
|
||||
|
||||
<para arch="i386,alpha">对于大多数 CDROM 或者网络安装来说，您需要从
|
||||
<filename>floppies/</filename> 目录拷贝到真实软盘的只有
|
||||
<filename>boot.flp</filename> 和 <filename>kern<replaceable>X</replaceable>.flp</filename>
|
||||
映像(用于 1.44MB 软盘)。</para>
|
||||
|
||||
<para arch="pc98">对于通常的CDROM 或者网络安装来说，您需要从
|
||||
<filename>floppies/</filename> 目录拷贝到真实软盘的只有
|
||||
<filename>boot.flp</filename> 和 <filename>kern<replaceable>X</replaceable>.flp</filename>
|
||||
映像(用于 1.44MB 软盘) 或者 <filename>boot-small.flp</filename> 和
|
||||
<filename>kern-small.flp</filename> 映像(用于 1.2MB 软盘)。</para>
|
||||
|
||||
<para arch="i386,alpha,pc98">通过网络获取这些映像很容易。只需要从 <ulink
|
||||
url="&release.url;"></ulink>
|
||||
或者列在使用手册的 <ulink
|
||||
url="&url.books.handbook;/mirrors-ftp.html">FTP
|
||||
站点</ulink>一节或
|
||||
<ulink url="http://mirrorlist.FreeBSD.org/"></ulink> Web 页面中的众多镜像站点中下载
|
||||
<replaceable>release</replaceable><filename>/floppies/boot.flp</filename>
|
||||
和所有的
|
||||
<replaceable>release</replaceable><filename>/floppies/kern<replaceable>X</replaceable>.flp</filename>
|
||||
文件。</para>
|
||||
|
||||
<para arch="i386,alpha">拿几张空的、 新格式化过的软盘， 一张复制映像
|
||||
<filename>boot.flp</filename>，另两张复制 <filename>kern<replaceable>X</replaceable>.flp</filename> 文件。
|
||||
这些映像 <emphasis>不是</emphasis> DOS 文件。 您不能把它们当作普通文件简单地复制到一张
|
||||
DOS 或者 UFS 软盘上，您需要在 DOS 下使用 <filename>fdimage.exe</filename>
|
||||
或者在 UNIX 下使用 &man.dd.1; 命令把它们<quote>image</quote>复制到软盘上(查看您的
|
||||
CDROM 或者 &os; FTP 镜像上的 <filename>tools</filename> 目录)。</para>
|
||||
|
||||
<para arch="pc98">拿几张空的、 新格式化过的软盘， 一张复制映像
|
||||
<filename>boot.flp</filename>，另两张复制 <filename>kern<replaceable>X</replaceable>.flp</filename> 文件。
|
||||
这些映像 <emphasis>不是</emphasis> DOS 文件。您不能把它们当作普通文件简单的复制到一张
|
||||
DOS 或者 UFS 软盘上，您需要在 DOS 下使用 <filename>rawrite.exe</filename>
|
||||
或者在 UNIX 下使用 &man.dd.1; 命令把它们<quote>image</quote>复制到软盘上(查看您的
|
||||
CDROM 或者 &os; FTP 镜像上的 <filename>tools</filename> 目录)。</para>
|
||||
|
||||
<para arch="i386,alpha,pc98">例如，要从 DOS 下创建内核软盘映像，您应该这样做：</para>
|
||||
|
||||
<screen arch="i386,alpha"><prompt>C></prompt> <userinput>fdimage boot.flp a:</userinput></screen>
|
||||
<screen arch="pc98"><prompt>A></prompt> <userinput>rawrite</userinput></screen>
|
||||
|
||||
<para arch="i386,alpha">假定您已经把 <filename>fdimage.exe</filename> 和 <filename>boot.flp</filename>
|
||||
复制到了某个目录里。当然，您应该对 <filename>kern<replaceable>X</replaceable>.flp</filename> 文件也这么做。</para>
|
||||
|
||||
<para arch="pc98">假定您已经把 <filename>rawrite.exe</filename> 和 <filename>boot.flp</filename>
|
||||
复制到了某个目录里。当然，您应该对 <filename>kern<replaceable>X</replaceable>.flp</filename> 文件也这么做。</para>
|
||||
|
||||
<para arch="i386,alpha,pc98">如果您正在一台 UNIX 机器上创建启动软盘，您可能会发现：</para>
|
||||
|
||||
<screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0</userinput></screen>
|
||||
<screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0.1440</userinput></screen>
|
||||
|
||||
<para arch="i386,alpha">或</para>
|
||||
|
||||
<screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/fd0</userinput></screen>
|
||||
|
||||
<para arch="i386,alpha,pc98">或</para>
|
||||
|
||||
<screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/floppy</userinput></screen>
|
||||
<screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot-small.flp of=/dev/rfd0.1200</userinput></screen>
|
||||
|
||||
<para arch="i386,alpha,pc98">工作正常，这取决于您的硬件和操作系统环境
|
||||
(不同版本的 UNIX 对软驱有不同的命名)。</para>
|
||||
|
||||
<para arch="amd64,sparc64">&os;/&arch; 不支持软盘安装。</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="start-installation">
|
||||
<title>从 CDROM 或者 Internet 安装 &os;</title>
|
||||
|
||||
<!-- i386/pc98 text starts here -->
|
||||
|
||||
<para arch="i386,amd64">最容易的安装方法就是从 CDROM 安装。
|
||||
如果您有一个支持的 CDROM 驱动器和一张 &os;
|
||||
安装 CDROM，有两种方式来开始安装：
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>如果您的系统支持自启动 CDROM
|
||||
介质的<quote>CDBOOT</quote>标准并且已经激活了从 CD 启动，
|
||||
只要把 &os; 安装 CD 放进您的 CDROM 驱动器并启动系统开始安装。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>从每个 &os; 发行版的 <filename>floppies/</filename>
|
||||
目录创建一系列的 &os; 启动软盘。阅读
|
||||
<xref linkend="floppies"> 了解在不同的操作系统下创建启动软盘的更多信息。
|
||||
然后您只要从第一张软盘启动，很快就会进入 &os; 安装。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="pc98">最容易的安装方法就是从 CDROM 安装。
|
||||
如果您有一个支持的 CDROM 驱动器和一张 &os;
|
||||
安装 CDROM，有一种方式来开始安装：
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>从每个 &os; 发行版的 <filename>floppies/</filename>
|
||||
目录创建一系列的 &os; 启动软盘。阅读
|
||||
<xref linkend="floppies"> 了解在不同的操作系统下创建启动软盘的更多信息。
|
||||
然后您只要从第一张软盘启动，很快就会进入 &os; 安装。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</para>
|
||||
|
||||
<para arch="i386">如果您没有 CDROM (或者您的计算机不支持从
|
||||
CDROM 启动) 并且只是想要通过网络使用 PPP、SLIP 或者专用连接安装，
|
||||
您应该使用 <xref linkend="floppies"> 处的安装说明从文件
|
||||
<filename>floppies/boot.flp</filename> 和
|
||||
<filename>floppies/kern<replaceable>X</replaceable>.flp</filename> 创建一系列 &os; 启动软盘来开始安装。
|
||||
用 <filename>boot.flp</filename> 软盘重新启动您的计算机，
|
||||
出现提示符时插入需要的其他软盘。然后，请到
|
||||
<xref linkend="ftpnfs"> 寻找通过 FTP 或 NFS 安装的额外的提示。</para>
|
||||
|
||||
<para arch="pc98">如果您没有 CDROM (或者您的计算机不支持从
|
||||
CDROM 启动) 并且只是想要通过网络使用 PPP、SLIP 或者专用连接安装，
|
||||
您应该使用 <xref linkend="floppies"> 处的安装说明从文件
|
||||
<filename>floppies/boot.flp</filename> 和
|
||||
<filename>floppies/kern<replaceable>X</replaceable>.flp</filename> 创建一系列 &os; 启动软盘来开始安装。
|
||||
用 <filename>boot.flp</filename> 软盘重新启动您的计算机，
|
||||
出现提示符时插入需要的其他软盘。然后，请到
|
||||
<xref linkend="ftpnfs"> 寻找通过 FTP 或 NFS 安装的额外的提示。</para>
|
||||
|
||||
<!-- alpha text starts here -->
|
||||
|
||||
<para arch="alpha">最容易的安装方式就是从 CDROM 安装。
|
||||
如果您有一个支持的 CDROM 驱动器和一张 &os;
|
||||
安装 CDROM，您可以直接从 CDROM 启动 &os;。将 CDROM
|
||||
插入驱动器并输入下面的命令来开始安装(如果需要，用合适的
|
||||
CDROM 驱动器名称来取代)：</para>
|
||||
|
||||
<screen arch="alpha">>>><userinput>boot dka0</userinput></screen>
|
||||
|
||||
<para arch="alpha">您也可以从软盘启动安装。
|
||||
您应该使用 <xref linkend="floppies"> 处的安装说明从文件
|
||||
<filename>floppies/boot.flp</filename> 和
|
||||
<filename>floppies/kern<replaceable>X</replaceable>.flp</filename> 创建一系列 &os; 启动软盘来开始安装。
|
||||
从 SRM 控制台提示符处(<literal>>>></literal>)，插入
|
||||
<filename>boot.flp</filename> 软盘并键入下面的命令来开始安装：</para>
|
||||
|
||||
<screen arch="alpha">>>><userinput>boot dva0</userinput></screen>
|
||||
|
||||
<para arch="alpha">当提示时插入其他软盘，
|
||||
您会停在安装程序的第一个屏幕。</para>
|
||||
|
||||
<!-- sparc64 text starts here -->
|
||||
|
||||
<para arch="sparc64">大多数 &arch; 系统被设置成自动从硬盘启动。
|
||||
要安装 &os;，您需要通过网络或者 CDROM 启动，这需要您改动 PROM
|
||||
(OpenFirmware)。</para>
|
||||
|
||||
<para arch="sparc64">要做这个，重新启动系统，等到启动信息出现。
|
||||
取决于机器型号，但是应该看起来像这样：</para>
|
||||
|
||||
<screen arch="sparc64">Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
|
||||
Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved.
|
||||
OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
|
||||
Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
||||
|
||||
<para arch="sparc64">这时候如果您的系统继续从硬盘启动，
|
||||
您需要按键盘上的 <keycombo
|
||||
action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo>
|
||||
或者 <keycombo
|
||||
action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo>
|
||||
或者通过串口控制台发送一个 <command>BREAK</command> 信号
|
||||
(例子中 &man.tip.1; 或者 &man.cu.1; 使用 <command>~#</command>)
|
||||
来进入 PROM 提示符。看上去像这样：</para>
|
||||
|
||||
<screenco arch="sparc64">
|
||||
<areaspec>
|
||||
<area id="prompt-single" coords="1 5">
|
||||
<area id="prompt-smp" coords="2 5">
|
||||
</areaspec>
|
||||
|
||||
<screen><prompt>ok </prompt>
|
||||
<prompt>ok {0} </prompt></screen>
|
||||
|
||||
<calloutlist>
|
||||
<callout arearefs="prompt-single">
|
||||
<para>这是系统中只有一个 CPU 使用的提示符。</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="prompt-smp">
|
||||
<para>这是在 SMP 系统中使用的提示符，数字显示活动的 CPU 数目。</para>
|
||||
</callout>
|
||||
</calloutlist>
|
||||
</screenco>
|
||||
|
||||
<para arch="sparc64">这时候，将 CDROM 放进驱动器，并在
|
||||
PROM 提示符处键入 <command>boot
|
||||
cdrom</command>。</para>
|
||||
|
||||
</sect2>
|
||||
<sect2>
|
||||
<title>详述各种安装类型</title>
|
||||
|
||||
<para>一旦您看到了初始的安装屏幕，不管用哪种方式，
|
||||
您就可以跟随各种各样的菜单提示到处浏览了。如果您以前从未使用过 &os;
|
||||
安装程序，建议您阅读 Documentation 子菜单还有第一个菜单概括的
|
||||
<quote>Usage</quote> 说明中的文档。</para>
|
||||
|
||||
<note>
|
||||
<para>如果您感到迷惑，按 <keycap>F1</keycap>
|
||||
键查看与指定部分相关的在线文档。</para>
|
||||
</note>
|
||||
|
||||
<para>如果您以前从未安装过 &os;，或者即使您安装过，
|
||||
仍然强烈推荐使用<quote>Standard</quote>安装模式，
|
||||
因为它确保您一路安装下来访问到了所有重要的要检查的条目。
|
||||
如果您非常熟悉 &os; 安装过程并 <emphasis>精确的</emphasis>
|
||||
知道您想做什么，可以使用<quote>Express</quote>或者<quote>Custom</quote>安装选项。
|
||||
如果您在升级一个现存的系统，使用<quote>Upgrade</quote>选项。</para>
|
||||
|
||||
<para>&os; 安装程序支持直接使用软盘、DOS、磁带、CDROM、FTP、NFS
|
||||
和 UFS 分区来作为安装介质。下面是从每种类型的介质安装的更深入的提示。</para>
|
||||
|
||||
<para arch="alpha">一旦安装过程结束，您将可以在 SRM
|
||||
提示符处键入类似这样的命令来启动 &os;/&arch;：</para>
|
||||
|
||||
<screen arch="alpha">>>><userinput>boot dkc0</userinput></screen>
|
||||
|
||||
<para arch="alpha">这告知固件从指定的硬盘启动。To
|
||||
查找您机器上硬盘的 SRM 名称，使用 <literal>show
|
||||
device</literal> 命令：</para>
|
||||
|
||||
<screen arch="alpha">>>><userinput>show device</userinput>
|
||||
dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476
|
||||
dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658
|
||||
dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015
|
||||
dva0.0.0.0.1 DVA0
|
||||
ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01
|
||||
pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27
|
||||
pqa0.0.0.4.0 PQA0 PCI EIDE
|
||||
pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
|
||||
|
||||
<para arch="alpha">这个例子来自于一台 Digital Personal Workstation 433au，
|
||||
显示表明有三个磁盘设备连接在机器上。第一个是叫做
|
||||
<devicename>dka0</devicename> 的 CDROM，另外两个是分别叫做
|
||||
<devicename>dkc0</devicename> 和
|
||||
<devicename>dkc100</devicename> 的硬盘。</para>
|
||||
|
||||
<para arch="alpha">您可以用 <option>-file</option> 和 <option>-flags</option>
|
||||
选项指定加载哪个内核文件以及使用什么样的启动参数，例如：</para>
|
||||
|
||||
<screen arch="alpha"><prompt>>>></prompt> <userinput>boot -file kernel.old -flags s</userinput></screen>
|
||||
|
||||
<para arch="alpha">要让 &os;/&arch; 自动启动，使用这些命令：</para>
|
||||
|
||||
<screen arch="alpha"><prompt>>>></prompt> <userinput>set boot_osflags a</userinput>
|
||||
<prompt>>>></prompt> <userinput>set bootdef_dev dkc0</userinput>
|
||||
<prompt>>>></prompt> <userinput>set auto_action BOOT</userinput></screen>
|
||||
|
||||
<sect3>
|
||||
<title>从网络 CDROM 安装</title>
|
||||
|
||||
<para>如果您只希望从本地 CDROM 驱动器安装，可以查看
|
||||
<xref linkend="start-installation">。如果您的系统上没有 CDROM
|
||||
驱动器，又希望使用有网络连接的另一个系统上的 CDROM 驱动器中的
|
||||
&os; 发行 CD，也有几种方式可以实现：</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>如果您能够直接通过 &os; 机器上的 CDROM 驱动器 FTP
|
||||
安装，这很容易：保证有一台 FTP
|
||||
服务器正在运行，然后只要把下面的几行添加到密码文件中
|
||||
(使用 &man.vipw.8; 命令)：</para>
|
||||
|
||||
<screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
|
||||
|
||||
<para>在您要运行安装的机器上，到 Options
|
||||
菜单并设定 Release Name 为
|
||||
<literal>any</literal>。然后您可以选择一种
|
||||
<literal>FTP</literal> 媒介类型并在 ftp
|
||||
站点目录中选定<quote>URL</quote>后键入
|
||||
<filename>ftp://<replaceable>machine</replaceable></filename>。</para>
|
||||
|
||||
<warning>
|
||||
<para>这会允许本地网络(或 Internet) 上的任何人和这台机器建立
|
||||
<quote>匿名 FTP</quote> 连接，这可能不是所希望看到的。</para>
|
||||
</warning>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>如果希望通过 NFS 将 CDROM 直接导出给其他机器来进行安装，
|
||||
您需要首先在 <filename>/etc/exports</filename>
|
||||
文件中添加对应的项目 (在有 CDROM 驱动器的那台机器上)。
|
||||
下面的例子将允许
|
||||
<hostid role="hostname">ziggy.foo.com</hostid> 在安装过程中直接通过
|
||||
NFS 挂接 CDROM：</para>
|
||||
|
||||
<screen>/cdrom -ro ziggy.foo.com</screen>
|
||||
|
||||
<para>当然， 带 CDROM 的那台机器必须配置为 NFS 服务器，
|
||||
如果您不知道如何完成其配置， 则 NFS 对您来说可能并不是最佳的选择，
|
||||
除非您打算仔细阅读 &man.rc.conf.5; 并配置它。 如果顺利的话，
|
||||
将可以通过输入： <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename>
|
||||
作为在目标机器 NFS 安装过程的参数，
|
||||
例如 <filename>wiggy:/cdrom</filename>。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>从软盘安装</title>
|
||||
|
||||
<para>如果由于硬件不支持，
|
||||
或者您喜欢把简单的问题复杂化而不得不从软盘安装，
|
||||
您需要首先准备一些空白的软盘。</para>
|
||||
|
||||
<para>首先， 按照 <xref linkend="floppies"> 所介绍的过程来制作启动盘。</para>
|
||||
|
||||
<para>然后， 仔细阅读 <xref linkend="layout"> 并要特别注意
|
||||
<quote>发行版本所采用的格式</quote> 一节，
|
||||
因为它介绍了您需要复制到软盘上的文件， 以及可以放心地跳过的文件。</para>
|
||||
|
||||
<para>接下来您需要至少准备足够多的能放下 <filename>bin</filename>
|
||||
目录里文件的 1.44MB 软盘。 如果您需要在 DOS 下准备这些软盘，
|
||||
则 <emphasis>必须</emphasis> 使用 MS-DOS 的
|
||||
<filename>FORMAT</filename> 命令来格式化它们。 如果您使用 Windows，
|
||||
则可以使用 Windows 文件管理器 的格式化命令。</para>
|
||||
|
||||
<important>
|
||||
<para>通常， 软盘是 <quote>在出厂前格式化过的</quote>。
|
||||
虽然这很方便， 但过去许多用户的问题报告都与没有格式化磁盘有关。
|
||||
建议您自行格式化一下， 以确认没有问题。</para>
|
||||
</important>
|
||||
|
||||
<para>如果您正在从另一个 &os; 机器上制作需要的软盘，
|
||||
格式化仍然是一个好习惯， 只是您并不需要在每张软盘上都放一个
|
||||
DOS 文件系统。 您可以使用 &man.disklabel.8; 和 &man.newfs.8;
|
||||
这两个命令来在软盘上制作 UFS 文件系统， 使用下面介绍的命令：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>fdformat -f 1440 fd0</userinput>
|
||||
&prompt.root; <userinput>disklabel -w fd0 floppy3</userinput>
|
||||
&prompt.root; <userinput>newfs -i 65536 /dev/fd0</userinput></screen>
|
||||
|
||||
<para>在以 DOS 或 UFS 格式化过软盘之后， 还需要将文件复制到上面。
|
||||
发布文件的大小是经过精心准备的， 因此每张软盘都能够放下一个发布文件。
|
||||
每一个发布包的文件应该放到它自己的子目录中，
|
||||
例如： <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
|
||||
|
||||
<important>
|
||||
<para><filename>bin.inf</filename> 文件需要放到
|
||||
<filename>bin</filename> 发布集的第一张软盘上，
|
||||
因为安装文件需要读取它以了解在将发布包重组时还需要获取多少个文件块。
|
||||
当把发布放到软盘上时，
|
||||
<filename>distname.inf</filename> 文件 <emphasis>必须</emphasis>
|
||||
和发布集的第一块放在一起。</para>
|
||||
</important>
|
||||
|
||||
<para>一旦您进入了安装程序的 Media 提示， 选择
|
||||
<quote>Floppy</quote> 之后您将得到相应的提示。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 arch="i386,pc98,amd64">
|
||||
<title>从 DOS 分区安装</title>
|
||||
|
||||
<para arch="i386,amd64">要从 MS-DOS 分区安装您只需简单地把发布包文件复制到主
|
||||
DOS 分区 (<devicename>C:</devicename>) 上的一个名字为
|
||||
<filename>FREEBSD</filename> 的目录即可。 例如， 要从 DOS 中使用来自
|
||||
CDROM 的文件完成 &os; 的最小安装， 您需要照下面的提示做：</para>
|
||||
|
||||
<para arch="pc98">要从 MS-DOS 分区安装您只需简单地把发布包文件复制到主
|
||||
DOS 分区 (<devicename>A:</devicename>) 上的一个名字为
|
||||
<filename>FREEBSD</filename> 的目录即可。 例如， 要从 DOS 中使用来自
|
||||
CDROM 的文件完成 &os; 的最小安装， 您需要照下面的提示做：</para>
|
||||
|
||||
<screen arch="i386,amd64"><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput>
|
||||
<prompt>C:\></prompt> <userinput>XCOPY /S E:\BASE C:\FREEBSD\BASE</userinput></screen>
|
||||
<screen arch="pc98"><prompt>A:\></prompt> <userinput>MD A:\FREEBSD</userinput>
|
||||
<prompt>A:\></prompt> <userinput>XCOPY /S E:\BASE A:\FREEBSD\BASE</userinput></screen>
|
||||
|
||||
<para>这里假设 <devicename>E:</devicename> 是您的 CD 所挂接的驱动器符。</para>
|
||||
|
||||
<para arch="i386,amd64">如果需要从 DOS 安装更多的发行包 (当然您需要足够的磁盘空间)
|
||||
需要将它们都复制到
|
||||
<filename>C:\FREEBSD</filename> - 而 <filename>BIN</filename> 则是必需的。</para>
|
||||
|
||||
<para arch="pc98">如果需要从 DOS 安装更多的发行包 (当然您需要足够的磁盘空间)
|
||||
需要将它们都复制到
|
||||
<filename>A:\FREEBSD</filename> - 而 <filename>BIN</filename> 则是必需的。</para>
|
||||
|
||||
<para>一旦您复制了这些目录， 就可以简单地从软盘开始安装，
|
||||
并在指定介质类型时选择 <quote>DOS</quote>。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>从 QIC/SCSI 磁带安装</title>
|
||||
|
||||
<para>当从磁带安装时， 安装程序预期安装文件是 tar 到上面的，
|
||||
因此把您感兴趣的安装包复制出来之后， 简单地使用 &man.tar.1;
|
||||
把它们放到磁带上就可以了：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
|
||||
&prompt.root; <userinput>tar cvf /dev/sa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
|
||||
|
||||
<para>当您进行安装时， 您应该确认临时目录
|
||||
(将提示您选择它) 中有足够放下 <emphasis>完整的</emphasis>
|
||||
磁带内容的空间。 由于磁带不支持随机访问， 这种方式需要很多临时存储。
|
||||
您需要准备写到磁带上那样多的临时存储空间。</para>
|
||||
|
||||
<note>
|
||||
<para>当开始安装时， 磁带应该在从软盘启动
|
||||
<emphasis>之前</emphasis> 放进磁带机。 如果不这样做，
|
||||
安装程序的 <quote>探测</quote> 操作可能会找不到它。</para>
|
||||
</note>
|
||||
|
||||
<para>现在按照 <xref linkend="floppies">
|
||||
的描述制作安装软盘并继续安装就可以了。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="ftpnfs">
|
||||
<title>通过网络使用 FTP 或 NFS 安装</title>
|
||||
|
||||
<para>按照第一节的说明制作引导盘之后，
|
||||
您可以使用三种不同的连接方式来继续安装过程： 串口连接、
|
||||
并口连接， 或以太网。</para>
|
||||
|
||||
<sect4>
|
||||
<title>串口</title>
|
||||
|
||||
<para>SLIP 支持非常原始， 而且基本上限于硬连线的连接，
|
||||
例如在两台计算机之间的串口电缆。 这类连接必须是直接连好的，
|
||||
因为 SLIP 安装目前并不提供拨号能力。
|
||||
如果您需要使用调制解调器来拨号或需要在连接之前进行其它交互，
|
||||
则应使用 PPP 来代替它。</para>
|
||||
|
||||
<para>如果您使用 PPP， 一定要确认您手头有
|
||||
Internet 服务提供商的 IP 地址和 DNS 信息，
|
||||
因为您在安装的开始阶段需要它们。 您还需要知道自己的 IP
|
||||
地址， 尽管 PPP 支持动态地址协商，
|
||||
并能够直接从您的 ISP 获取这些信息， 如果他们支持这样做的话。</para>
|
||||
|
||||
<para>最后您还需要了解在您的 PPP 拨号服务上如何使用一些 <quote>AT
|
||||
命令</quote> 来进行拨号， 因为 PPP 拨号程序只提供了非常简单的终端仿真程序。</para>
|
||||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>并口</title>
|
||||
|
||||
<para>如果有可用的到另一台 &os; 或 Linux
|
||||
机器的连接， 您也可以考虑通过
|
||||
<quote>laplink</quote> 风格的并口电缆来安装。
|
||||
通过并口连接的速度通常要比串口电缆
|
||||
(通常最多 50k/秒) 要快的多， 因此能够让您更快地完成安装。
|
||||
当使用点对点的并口电缆连接时通常并不需要
|
||||
<quote>真实的</quote> IP 地址， 一般来说您可以在连接的两端使用
|
||||
RFC 1918 风格的地址 (例如 <hostid
|
||||
role="ipaddr">10.0.0.1</hostid>， <hostid role="ipaddr">10.0.0.2</hostid>，
|
||||
等等)。</para>
|
||||
|
||||
<important>
|
||||
<para>如果您的 PLIP 另一端使用的是 Linux，
|
||||
则还需要在 TCP/IP 设置界面的<quote>extra options for
|
||||
ifconfig</quote> 中指定
|
||||
<option>link0</option>， 以便兼容 Linux
|
||||
中略有不同的 PLIP 协议。</para>
|
||||
</important>
|
||||
|
||||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>以太网</title>
|
||||
|
||||
<para>&os; 支持绝大多数常见的以太网卡，
|
||||
它支持的网卡列表作为 &os; 硬件说明 (参见 Documentation
|
||||
菜单中的 <filename>HARDWARE.TXT</filename> 或启动盘和
|
||||
CDROM 的顶级目录)。 如果您使用的是某种被支持的
|
||||
PCMCIA 网卡， 则还应确认它在笔记本启动
|
||||
<emphasis>之前</emphasis> 就已经插好了。
|
||||
不幸的是， &os; 目前还不支持在安装过程中
|
||||
<quote>热插</quote> PCMCIA 卡。</para>
|
||||
|
||||
<para>同时还需要知道您在局域网上的 IP 地址，
|
||||
子网的 <option>netmask</option> 值和机器名。
|
||||
您的系统管理员会告诉您在您的网络上所需要的值。
|
||||
如果您想通过名字而不是 IP 地址来访问其它机器，
|
||||
则还需要一个域名服务器， 而且可能还需要网关的地址
|
||||
(如果使用 PPP， 则是您提供商的 IP 地址)
|
||||
才能够访问它。 如果您打算通过 HTTP 代理来完成
|
||||
FTP 安装， 您还需要代理服务器的地址。</para>
|
||||
|
||||
<para>如果您不知道这些问题的答案， 您可能需要
|
||||
<emphasis>首先</emphasis> 联系系统管理员， 然后才能开始安装。
|
||||
在已有网络上使用随便选择的 IP 地址和子网掩码几乎肯定无法正常工作，
|
||||
而且您的管理员可能会给您上人生一课。</para>
|
||||
|
||||
<para>一旦您的网络连接能够使用， 就可以继续通过
|
||||
NFS 或 FTP 来完成安装了。</para>
|
||||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>NFS 安装提示</title>
|
||||
|
||||
<para>NFS 安装相当的简单： 您只需将
|
||||
&os; 的安装文件复制到服务器上的某个目录，
|
||||
并在选择 NFS 介质时给出这个目录即可。</para>
|
||||
|
||||
<para>如果服务器只支持来自 <quote>特权端口</quote> 的访问
|
||||
(这是 Sun 和 Linux 工作站上通常的默认情形)，
|
||||
您可能需要在安装之前在 Options 菜单中设置这个选项。</para>
|
||||
|
||||
<para>如果您的网卡质量很差并造成数据传输迟缓，
|
||||
您可能还需要调整一些 Options 选项。</para>
|
||||
|
||||
<para>为了让 NFS 安装能够正常进行， 服务器还必须支持
|
||||
<quote>子目录挂接 (subdir mounts)</quote>， 例如如果您的 &os;
|
||||
安装包目录在
|
||||
<filename>wiggy:/usr/archive/stuff/FreeBSD</filename> 中， 则
|
||||
<hostid role="hostname">wiggy</hostid> 必须允许直接挂接
|
||||
<filename>/usr/archive/stuff/FreeBSD</filename>， 而不仅仅是
|
||||
<filename>/usr</filename> 或 <filename>/usr/archive/stuff</filename>。</para>
|
||||
|
||||
<para>在 &os; 的 <filename>/etc/exports</filename> 文件中可以通过
|
||||
<option>-alldirs</option> 选项来控制它。 在其它 NFS 服务器上可能有不同的写法。
|
||||
如果您收到了来自服务器的 <literal>Permission Denied</literal> 消息，
|
||||
通常是因为您没有启用这一特性导致的。</para>
|
||||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>FTP 安装提示</title>
|
||||
|
||||
<para>FTP 安装可以通过从任何包含足够新版的
|
||||
&os; 的镜像站点来完成。 安装过程中您可以从 FTP
|
||||
站点菜单中选择遍布全球的几乎每一个官方的镜像站点来完成安装。</para>
|
||||
|
||||
<para>如果您正从某个没有在这里列出的 FTP 站点安装，
|
||||
或您无法正确地配置域名解析服务器， 您也可以通过在菜单中选择
|
||||
<quote>URL</quote> 来指定自己的 URL。 URL 可以包括一个域名或
|
||||
IP 地址， 因此当没有域名解析服务器时， 您可以用类似下面的 URL
|
||||
来完成安装：</para>
|
||||
|
||||
<screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen>
|
||||
|
||||
<para>您可以从三种 FTP 安装方式中选择适合的：</para>
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>FTP: 这种方式使用标准的
|
||||
<quote>主动 (Active)</quote> 传输方式，
|
||||
此时服务器将主动发起到客户机的数据连接。
|
||||
在存在防火墙的环境中通常这会无法正常工作，
|
||||
但与不支持被动模式的较老的 FTP 服务器配合时它是最佳选择。
|
||||
如果您使用被动模式时连接挂起， 请尝试这个选项。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>FTP Passive: 这将设置 FTP <quote>被动 (Passive)</quote>
|
||||
模式， 它将阻止服务器打开到客户机的连接。
|
||||
这个选项对于通过不允许连入到随机端口的防火墙接入的用户来说，
|
||||
是最佳的选择。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>FTP via an HTTP proxy: 这个选项指示 &os;
|
||||
使用 HTTP 连到一个代理商完成所有的 FTP 操作。
|
||||
代理服务器将翻译所有的请求， 并把它们发给 FTP 服务器。
|
||||
这允许用户通过完全不允许 FTP， 但提供了 HTTP 代理的防火墙连接。
|
||||
除了 FTP 服务器之外， 您还必须指定代理服务器的主机名。</para>
|
||||
|
||||
<para>极端情况下您可能有不通过 HTTP 的 FTP 代理服务器，
|
||||
您可以把 URL 指定为下面的样子：</para>
|
||||
|
||||
<screen><userinput>ftp://foo.bar.com:<replaceable>端口</replaceable>/pub/FreeBSD</userinput></screen>
|
||||
|
||||
<para>上面的 URL 中， <replaceable>端口</replaceable>
|
||||
是 FTP 代理服务器的端口号。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
</sect4>
|
||||
</sect3>
|
||||
<sect3 arch="i386,alpha,amd64">
|
||||
<title>串口控制台用户提示</title>
|
||||
|
||||
<para>如果您想在只有串口的机器上安装 &os;
|
||||
(例如， 在没有或不想购买 VGA 卡时)，
|
||||
请按照下面的步骤完成安装：</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>连接某种 ANSI (vt100) 兼容的终端或终端仿真程序到您打算安装 &os;
|
||||
的计算机的 <devicename>COM1</devicename> 口。</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>拔掉键盘 (是的， 这是正确的!) 然后尝试从软盘或安装
|
||||
CDROM 启动。 启动时不要插键盘。</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>如果您在串口控制台上没有得到任何输出，
|
||||
请重新插上键盘。 如果您正从
|
||||
CDROM 启动， 在听到嘟嘟声时立即 <xref linkend="hitspace">。</para>
|
||||
</step>
|
||||
<step>
|
||||
<para>如果从软盘引导， 当软驱不再动作时， 插入第一张
|
||||
<filename>kern<replaceable>X</replaceable>.flp</filename> 盘并按
|
||||
<keycap>Enter</keycap>。 当软驱不再动作时， 插入下一张
|
||||
<filename>kern<replaceable>X</replaceable>.flp</filename> 盘并按 <keycap>Enter</keycap>，
|
||||
重复直到您已经插入了所有的 <filename>kern<replaceable>X</replaceable>.flp</filename> 盘。
|
||||
当磁盘动作结束时， 再次插入 <filename>boot.flp</filename>
|
||||
软盘并按 <keycap>Enter</keycap>。</para>
|
||||
</step>
|
||||
<step id="hitspace">
|
||||
<para>一旦听到嘟嘟声， 按数字 <keycap>6</keycap>， 并输入</para>
|
||||
|
||||
<screen><userinput>boot -h</userinput></screen>
|
||||
|
||||
<para>您现在一定可以从串口看到一切。 如果这样还无法正常工作，
|
||||
请检查您的串口电缆， 以及终端仿真程序或实际的终端设备的设置。
|
||||
应该设置为 9600 波特， 8 数据位， 无奇偶校验位。</para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>&arch.print; 体系结构用户的疑问与解答</title>
|
||||
|
||||
<qandaset arch="i386,amd64">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>救命! 我的空间不足! 我是否需要首先删除所有的东西?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>如果您的计算机已经在运行 DOS 而只有很少或没有可以用于安装
|
||||
&os; 的磁盘空间， 还有机会! 您可以从 &os; CDROM 的
|
||||
<filename>tools/</filename> 目录， 或众多 &os;
|
||||
ftp 站点上找到 <application>FIPS</application>
|
||||
工具来解决这个问题。</para>
|
||||
|
||||
<para><application>FIPS</application> 允许您将已经存在的
|
||||
DOS 分区分割为两部分， 保持原有分区中的内容，
|
||||
从而在剩余空间上安装。 在运行 FIPS 之前首先应该使用 DOS 6.xx 的
|
||||
<filename>DEFRAG</filename> 工具或
|
||||
<application>Norton Disk Tools</application>
|
||||
对您的 DOS 分区执行 <quote>碎片整理</quote>。
|
||||
它将提示您输入所需的其它信息。 此后，
|
||||
您可以重新启动并在新的分区上安装 &os;。
|
||||
还应注意 FIPS 将把第二个分区作为第一个的分区的
|
||||
<quote>克隆</quote>， 因此实际上您将在原有的一个 DOS
|
||||
主分区之外看到一个新的主分区。 不必理会警告!
|
||||
您可以简单地删除那个多余的 DOS 主分区
|
||||
(可以通过分区大小来看出是否是应该删除的那个)。</para>
|
||||
|
||||
<para><application>FIPS</application> 目前并不支持
|
||||
NTFS 格式的分区。 要分割这样的分区， 您需要类似
|
||||
<application>Partition Magic</application>
|
||||
这样的商业产品。</para>
|
||||
|
||||
<para><application>FIPS</application> 无法处理扩展
|
||||
DOS 分区。 但它支持 Windows 95/98/ME 的 FAT32 格式主分区。</para>
|
||||
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我能在 &os; 中使用压缩的 DOS 文件系统吗?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>不能。 如果您使用类似
|
||||
<application>Stacker</application>(tm) 或
|
||||
<application>DoubleSpace</application>(tm) 这样的工具，
|
||||
&os; 只能使用文件系统中尚未压缩的部分。
|
||||
余下的部分将展示为一个大文件。
|
||||
<emphasis>不要删除那个文件</emphasis> 否则您可能会后悔莫及的!</para>
|
||||
|
||||
<para>如果需要在 DOS 和 &os; 之间通讯， 最好建立一个未压缩的 DOS
|
||||
扩展分区。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>是否能挂接我的 DOS 扩展分区?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>可以。 DOS 扩展分区会被映射到 &os; 的其它
|
||||
<quote>slices</quote> 之后。 例如， 您的 <devicename>D:</devicename> 驱可能会是
|
||||
<filename>/dev/da0s5</filename>， 而 <devicename>E:</devicename> 驱则是
|
||||
<filename>/dev/da0s6</filename>， 等等。 当然， 这个例子假定您的扩展分区是在
|
||||
SCSI 驱动器 0 上。 对于 IDE 驱动器， 相应地用 <literal>ad</literal> 换掉
|
||||
<literal>da</literal>。 您可以按下面的方法来挂接其它 DOS 驱动器：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount -t msdosfs /dev/da0s5 /dos_d</userinput></screen>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>可以在 &os; 中执行 DOS 可执行文件吗?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>正在开发中的 BSDI 的 &man.doscmd.1; 工具能够适应多数情况，
|
||||
尽管还有一些较为粗糙的地方。
|
||||
<filename role="package">emulators/doscmd</filename> port/package
|
||||
可以在 &os; Ports Collection 中找到。
|
||||
如果您对这样的工作感兴趣， 请发邮件到 &a.emulation;
|
||||
并说明您对这项工作感兴趣!</para>
|
||||
|
||||
<para>&os; Ports Collection 中的 <filename role="package">emulators/pcemu</filename>
|
||||
port/package 能够模拟 8088 和足够多的 BIOS 服务来支持
|
||||
DOS 文本模式的应用程序。 运行它需要
|
||||
X Window System (XFree86)。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>可以在 &os; 中运行 µsoft.windows; 应用吗?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>在 &os; Ports Collection 中有很多能够运行众多
|
||||
&windows; 应用程序的 ports/packages。
|
||||
<filename role="package">emulators/wine</filename> 的
|
||||
port/package 提供了在 &os; 之上的一个兼容层， 使得很多
|
||||
&windows; 应用程序得以在 X Windows (XFree86) 中执行。
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>是否能够在 &os; 中运行其他操作系统?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>再次强调， &os; 的 Ports Collection 中有很多能够模拟
|
||||
"虚拟机" 并使得其他操作系统能够在 &os; 之上执行的 ports/packages。
|
||||
<filename role="package">emulators/bochs</filename> 中的 port/package
|
||||
允许 µsoft.windows;、 Linux 甚至另一份 &os; 在
|
||||
&os; 桌面的一个窗口中执行。
|
||||
<filename role="package">emulators/vmware2</filename> 和
|
||||
<filename role="package">emulators/vmware3</filename> ports/packages
|
||||
提供了商业的 VMware 虚拟机软件， 并能够在 &os; 上执行。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
|
||||
<qandaset arch="alpha">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我能从 ARC 或 Alpha BIOS 控制台启动吗?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>不能。 同 Compaq Tru64 和 VMS 类似， &os; 只能从
|
||||
SRM 控制台启动。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>救命啊！ 我没有足够的磁盘空间了！ 我需要把所有的数据都删掉吗?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>很不幸， 是的。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我能挂接 Compaq Tru64 或 VMS 扩展分区吗?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>不， 目前还不能。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>是否可以直接执行 Compaq Tru64 (OSF/1) 的可执行文件?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>&os; 能够通过 <filename role="package">emulators/osf1_base</filename>
|
||||
port/package 很好地运行 Tru64 应用程序。
|
||||
</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>那么是否可以执行 Linux 可执行文件呢?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>&os; 可以运行 AlphaLinux 可执行文件， 但需要配合
|
||||
<filename role="package">emulators/linux_base</filename>
|
||||
port/package。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>那么 NT Alpha 的可执行文件呢?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>&os; 无法直接执行 NT 应用程序， 尽管它能够挂接 NT 分区。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</sect2>
|
||||
</sect1>
|
||||
@ -1,143 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.11
|
||||
$FreeBSD$
|
||||
|
||||
This section contains the contents of the old LAYOUT.TXT file.
|
||||
-->
|
||||
<sect1 id="layout">
|
||||
<title>发行版本所采用的格式</title>
|
||||
|
||||
<para>典型的 &os; 发布目录的样子和下面列出的类似
|
||||
(具体细节可能随版本、 硬件架构和其他因素而有微小变化)：</para>
|
||||
|
||||
<screen>ERRATA.HTM README.TXT compat1x dict kernel
|
||||
ERRATA.TXT RELNOTES.HTM compat20 doc manpages
|
||||
HARDWARE.HTM RELNOTES.TXT compat21 docbook.css packages
|
||||
HARDWARE.TXT base compat22 filename.txt ports
|
||||
INSTALL.HTM boot compat3x floppies proflibs
|
||||
INSTALL.TXT catpages compat4x games src
|
||||
README.HTM cdrom.inf crypto info tools</screen>
|
||||
|
||||
<para>这些文件也可以在多碟组的第一张 CDROM 上找到，
|
||||
只是格局略有不同。 在多数平台上， 安装 CDROM 在安装包文件之外，
|
||||
也提供了一个 <quote>现场文件系统</quote>。 现场文件系统，
|
||||
对于修复或排出现有的 &os; 安装的问题非常有用 (参见 <xref
|
||||
linkend="trouble"> 以了解如何完成这项工作)。</para>
|
||||
|
||||
<para>对于无法从 CDROM 介质引导系统 (但可以通过其它手段来读取 CDROM)
|
||||
的用户来说， 应关注一下 <filename>floppies</filename> 目录。
|
||||
很容易从 <filename>floppies</filename> 提供的文件来自行制作 1.44MB 引导盘
|
||||
(参见 <xref linkend="floppies"> 以了解如何这样做)， 并用它来开始从 CDROM、
|
||||
FTP， 或者 NFS 的安装。 在安装过程中所需要的其他数据，
|
||||
将自动地根据您的选择获得。 如果您之前从未安装过 &os;，
|
||||
则应完整地阅读这份文档 (安装指引)。</para>
|
||||
|
||||
<para>如果您在尝试进行某种其他类型的安装，
|
||||
或对于发布目录是如何组织的感到好奇， 请参考下面的说明以了解进一步的内容：</para>
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para><filename>*.TXT</filename> 和
|
||||
<filename>*.HTM</filename> 文件包含了文档
|
||||
(举例来说， 这份文档可以在
|
||||
<filename>INSTALL.TXT</filename> 和
|
||||
<filename>INSTALL.HTM</filename> 中找到)，
|
||||
您应该在开始安装之前阅读它们。
|
||||
<filename>*.TXT</filename> 文件是普通的文本文件， 而
|
||||
<filename>*.HTM</filename> 文件则是 HTML 文件，
|
||||
可以使用几乎任何一种 Web 浏览器来阅读。
|
||||
某些发布可能还包其他格式的文档， 例如 PDF 或 PostScript。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename>docbook.css</filename> 是层次样式表
|
||||
(CSS) 文件， 它会被 Web 浏览器用以完成
|
||||
HTML 文档的排版。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename>base</filename>,
|
||||
<filename>catpages</filename>,
|
||||
<filename>crypto</filename>,
|
||||
<filename>dict</filename>,
|
||||
<filename>doc</filename>,
|
||||
<filename>games</filename>,
|
||||
<filename>info</filename>,
|
||||
<filename>manpages</filename>,
|
||||
<filename>proflibs</filename>, 以及
|
||||
<filename>src</filename> 这些目录中包含了 &os; 本身的发布版本组件，
|
||||
它们被分割为更小的文件， 以便放进软盘中 (如果需要的话)。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename>compat1x</filename>,
|
||||
<filename>compat20</filename>,
|
||||
<filename>compat21</filename>,
|
||||
<filename>compat22</filename>,
|
||||
<filename>compat3x</filename>, 以及
|
||||
<filename>compat4x</filename>
|
||||
目录包含了用于与先前版本兼容的文件， 它们以单个的 gzip 压缩的
|
||||
tar 文件的形式发布 - 在安装过程中或之后可以通过
|
||||
<filename>install.sh</filename> 脚本来安装它们。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename>floppies/</filename> 子目录中包含了安装用的软盘镜像；
|
||||
关于它们的更多信息可以在 <xref linkend="floppies"> 找到。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para><filename>packages</filename> 和 <filename>ports</filename> 目录提供了 &os;
|
||||
的 Packages 和 Ports Collections。 Packages 可以从其目录中通过下面的命令安装：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>sysinstall configPackages</userinput></screen>
|
||||
|
||||
<para>Packages 也可以通过将
|
||||
<filename>packages</filename>/ 下的文件名交给 &man.pkg.add.1;
|
||||
命令来完成。</para>
|
||||
|
||||
<para>Ports Collection 可以通过与其他组件相同的方法来安装，
|
||||
解压缩后它需要大约 190MB 的磁盘空间。 关于
|
||||
ports collection 的更多资料可以在
|
||||
<ulink url="&url.base;/ports/">http://www.FreeBSD.org/ports/</ulink>
|
||||
或本地的
|
||||
<filename>/usr/share/doc/handbook</filename> 找到，
|
||||
当然， 后者的前提是您安装了 <filename>doc</filename>
|
||||
发布。</para>
|
||||
</listitem>
|
||||
<listitem>
|
||||
<para>最后， <filename>tools</filename> 目录中提供了各种用以测试磁盘尺寸、
|
||||
安装引导管理器等的 DOS 工具。 这些工具纯粹是可选的，
|
||||
提供它们是为了方便用户。</para>
|
||||
</listitem>
|
||||
</orderedlist>
|
||||
|
||||
<para>典型的发布目录 (举例来说， <filename>info</filename> 发布) 在内部应该是这样：</para>
|
||||
|
||||
<screen>CHECKSUM.MD5 info.ab info.ad info.inf install.sh
|
||||
info.aa info.ac info.ae info.mtree</screen>
|
||||
|
||||
<para><filename>CHECKSUM.MD5</filename> 文件包含了每个文件的 MD5 签名。
|
||||
这主要是为了手工检测数据是否有损坏用的， 实际的安装过程并不会用到它。
|
||||
<filename>info.a*</filename> 文件是分割过的经过 gzip 压缩的 tar
|
||||
文件， 其内容可以通过下面的命令来显示：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cat info.a* | tar tvzf -</userinput></screen>
|
||||
|
||||
<para>在安装过程中， 这些文件会被自动地重组并根据需要展开。</para>
|
||||
|
||||
<para><filename>info.inf</filename> 文件也是必要的，
|
||||
因为它会被安装程序读取以了解需要为安装包复制多少片。 当把安装包放到软盘上时，
|
||||
<filename>.inf</filename> 文件 <emphasis>必须</emphasis>
|
||||
放在每一个安装包的第一张软盘上!</para>
|
||||
|
||||
<para><filename>info.mtree</filename> 文件是另一个供用户参考而非必需的文件。
|
||||
它包括了 <emphasis>未压缩的</emphasis> 安装包中的每个文件的 MD5 签名，
|
||||
并可在其后通过使用 &man.mtree.8;
|
||||
程序来验证安装权限和校验和以了解这些文件是否有过改动。
|
||||
当和 <filename>base</filename> 安装包联用时，
|
||||
这是一种检测木马攻击的很好的手段。</para>
|
||||
|
||||
<para>最后， <filename>install.sh</filename>
|
||||
文件是用来方便用户在安装之后安装某个安装包的。 要在装完系统之后从 CDROM
|
||||
安装某个安装包， 您可以按照下面的例子来完成：</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /cdrom/info</userinput>
|
||||
&prompt.root; <userinput>sh install.sh</userinput></screen>
|
||||
</sect1>
|
||||
@ -1,344 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.20
|
||||
$FreeBSD$
|
||||
|
||||
This file contains the comments of the old TROUBLE.TXT file.
|
||||
-->
|
||||
<sect1 id="trouble">
|
||||
<title>故障排除</title>
|
||||
|
||||
<sect2 id="repairing">
|
||||
<title>修复现有的 &os; 安装</title>
|
||||
|
||||
<para>&os; 在其安装程序 &man.sysinstall.8; 的顶级菜单上， 提供了一个
|
||||
<quote>fixit</quote> 选项。 它提供了一个包含 &os;
|
||||
基本系统中常用程序的 shell； 这个环境对于修复或排除现有的 &os;
|
||||
安装中的故障十分有用。 要使用 fixit 模式，
|
||||
您需要按照和其他引导盘相同的方式制作 <filename>fixit.flp</filename> 软盘，
|
||||
或者使用 <quote>现场文件系统</quote> CDROM。
|
||||
一般来说， 现场文件系统应该在 &os; 安装光盘中的第一张上。
|
||||
请注意， 使用 fixit 选项需要一些 UNIX 系统管理的经验。</para>
|
||||
|
||||
<para>一般来说， 有两种方法来启动 fixit 模式。
|
||||
能够从 &os; 安装 CDROM 启动的用户， 应该这样做并在
|
||||
&man.sysinstall.8; 的主菜单选择 <quote>fixit</quote>。
|
||||
然后， 再选择其中的
|
||||
<quote>CDROM/DVD</quote> 选项。</para>
|
||||
|
||||
<para>无法从 CDROM 启动， 但可以从软盘启动的用户，
|
||||
则需要更多的步骤。 除了安装过程所需要的
|
||||
<filename>boot.flp</filename> 和
|
||||
<filename>kern<replaceable>X</replaceable>.flp</filename> 之外，
|
||||
还需要制作一张
|
||||
<filename>fixit.flp</filename> 软盘， 方法和其他软盘无异。
|
||||
按照启动安装程序的步骤进行， 直到出现
|
||||
&man.sysinstall.8; 菜单为止。 这时， 选择其中的
|
||||
<quote>fixit</quote> 项， 随后的菜单中，
|
||||
选择 <quote>Floppy</quote>， 并依提示插入 <filename>fixit.flp</filename>
|
||||
软盘。</para>
|
||||
|
||||
<para>尽管 CDROM 和软盘上的 fixit 环境很相似， 但并非一模一样。
|
||||
它们都提供了一系列用于检查、 修复文件系统及其内容的命令。
|
||||
在 CDROM 上的 fixit 版本提供了全部 &os; 基本系统中的命令，
|
||||
因为它是一个现场文件系统。 与此相反， 由于空间限制， 软盘 fixit 环境，
|
||||
则只能提供它的一个子集。</para>
|
||||
|
||||
<para>软盘版本的 fixit 中，
|
||||
可以在 <filename>/stand</filename> 或
|
||||
<filename>/mnt2/stand</filename> 找到一些常用的独立的应用程序。
|
||||
而在 CDROM 版本的 fixit 中， 这些程序可以在
|
||||
<filename>/stand</filename> 或
|
||||
<filename>/mnt2/rescue</filename> 中找到 (余下的程序，
|
||||
可以在现场文件系统中找到， 其位置是
|
||||
<filename>/mnt</filename>)。</para>
|
||||
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>&arch.print; 架构上常见的问题</title>
|
||||
|
||||
<qandaset arch="i386">
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我的计算机在启动并检测硬件时停住了，
|
||||
或者安装时行为异常， 或者软驱没有检测到。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>&os; 5.0 以及更高版本大量地使用了 i386、 amd64
|
||||
以及 ia64 平台上的系统 ACPI
|
||||
服务以帮助检测系统在启动过程中检测到的设备。
|
||||
不幸的是， ACPI 驱动程序以及主板及其 BIOS 仍然存在一些 bug。
|
||||
ACPI 可以通过在启动加载的第三阶段通过设置
|
||||
<quote>hint.acpi.0.disabled</quote> 来禁用：</para>
|
||||
|
||||
<screen>set hint.acpi.0.disabled="1"</screen>
|
||||
|
||||
<para>在每次启动时这个选项都会被复位，
|
||||
因此有必要把 <literal>hint.acpi.0.disabled="1"</literal>
|
||||
加入到
|
||||
<filename>/boot/loader.conf</filename>中。
|
||||
要了解关于启动加载器的进一步详情， 请参考
|
||||
&os; 使用手册。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386,pc98,alpha,sparc64">
|
||||
<question>
|
||||
<para>先前版本的 &os; 能够识别我的旧式 ISA 设备，
|
||||
而新版本不能了。 发生了什么问题？</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>类似 matcd 这样的一些驱动程序， 会由于无人维护或者其他一些原因而被删除。
|
||||
其他一些仍然存在， 但由于其具有侵略性的检测方法而被默认禁用。
|
||||
下面这些 ISA 设备驱动可以在启动加载器的第三步时启用：
|
||||
aha, ahv, aic, bt, ed, cs, sn, ie, fe, le, 以及 lnc。
|
||||
要做到这一点， 在加载器进行 10 秒倒计时的时候将其中止，
|
||||
并在提示符后输入：</para>
|
||||
|
||||
<screen>unset hint.foo.0.disabled</screen>
|
||||
|
||||
<para>将 <replaceable>foo</replaceable>
|
||||
替换为驱动程序的名字就可以重新启用它们。
|
||||
通过编辑文件
|
||||
<filename>/boot/device.hints</filename>
|
||||
并删去相应的
|
||||
<quote>disabled</quote> 行可以使这一设置持久化。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>安装完 &os; 之后的首次硬盘启动， 内核已经正确加载并检测了硬件，
|
||||
但却停机并给出了类似下面的信息：</para>
|
||||
|
||||
<screen>changing root device to ad1s1a panic: cannot mount root</screen>
|
||||
<para>哪个地方出错? 应该如何解决?</para>
|
||||
|
||||
<para>在引导提示中给出的
|
||||
<literal>bios_drive:interface(unit,partition)kernel_name</literal>
|
||||
是什么意思?</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>当引导盘不是系统中的第一块盘时可能会触发一个存在了很久的问题。
|
||||
BIOS 使用和 &os; 不同的标号机制， 而改正这样的问题是非常困难的事情。</para>
|
||||
|
||||
<para>当引导盘不是系统中的第一块盘时， &os;
|
||||
可能需要一些额外的帮助才能找到它。 这里有两种比较常见的情形，
|
||||
在这两种情形中， 您都需要告诉 &os; 根文件系统的位置。
|
||||
您可以通过指定 BIOS 磁盘编号、 类型以及
|
||||
&os; 对那种类型的编号来完成这项工作。</para>
|
||||
|
||||
<para>第一种情况是您有两个 IDE 磁盘，
|
||||
每个配置成主盘在它们各自的 IDE 总线上，并且希望它们能从
|
||||
第二个盘引导 &os;
|
||||
BIOS 把它们看作磁盘 0 和磁盘 1， &os; 把它们看作
|
||||
<devicename>ad0</devicename> 和
|
||||
<devicename>ad2</devicename>。</para>
|
||||
|
||||
<para>&os; 在 BIOS 磁盘 1 上，类型为
|
||||
<literal>ad</literal> &os; 盘号为 2，
|
||||
因此您可以说：</para>
|
||||
|
||||
<screen><userinput>1:ad(2,a)kernel</userinput></screen>
|
||||
|
||||
<para>注意如果有一个从盘在主接口上， 则上面这些就不必要了
|
||||
(而且， 事实上是错的)。</para>
|
||||
|
||||
<para>第二种解决涉及到从一个 SCSI 磁盘上引导
|
||||
当您在系统上有一个或多个 IDE 磁盘。在这种情况下，
|
||||
&os; 的盘号比 BIOS 的盘号要低。
|
||||
如果您像 SCSI 磁盘一样有两个 IDE 磁盘，
|
||||
SCSI 磁盘是 BIOS 磁盘 2, 类型 <literal>da</literal>
|
||||
&os; 盘号为 0，因此您可以这样说：</para>
|
||||
|
||||
<screen><userinput>2:da(0,a)kernel</userinput></screen>
|
||||
|
||||
<para>告诉 &os; 您想从 BIOS 磁盘2上引导，它就是系统上的第
|
||||
一个 SCSI 磁盘。如果您只有一个
|
||||
IDE 磁盘，您需要使用 '1:' 来代替。</para>
|
||||
|
||||
<para>您一旦知道了需要使用的数值之后，
|
||||
就可以用您喜欢的文本编辑器把这些命令写进
|
||||
<filename>/boot.config</filename> 文件中。
|
||||
除非另有说明， &os; 会使用这个文件的内容， 作为对
|
||||
<literal>boot:</literal> 提示的回应。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>第一次安装 &os; 后，我从硬盘进行引导，但是引导管理器却提示
|
||||
<literal>F?</literal> 在每次引导时，但却不能引导进入系统。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>在安装 &os; 的编辑分区时， 硬盘尺寸设置错误。
|
||||
返回到分区编辑器并指定您的硬盘的实际尺寸。
|
||||
您必须重新安装 &os; 再次重新设置正确的尺寸。</para>
|
||||
|
||||
<para>如果在为您的机器指出正确的尺寸之后仍然失败，这里有个技巧：
|
||||
安装一个小的 DOS 分区在磁盘开始安装 &os; 后。安装程序将查看 DOS
|
||||
分区并且尝试着去推断正确的尺寸。通常这样就能正常工作。</para>
|
||||
|
||||
<para>下面的提示不再推荐，但是留在这里作为参考：</para>
|
||||
|
||||
<blockquote>
|
||||
<para>如果您正打算安装只使用 &os; 的服务器， 而不关心 (未来)
|
||||
和 DOS, Linux 或其他操作系统的兼容性， 您还可以选择使用整个磁盘
|
||||
(分区编辑器中的 ‘A’)， 选择那个不标准的选项来让
|
||||
&os; 占满磁盘的每一个扇区。 这样您就不再需要考虑尺寸问题，
|
||||
而限制则是您将无法运行 &os; 以外的其他操作系统。</para>
|
||||
</blockquote>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>&man.mcd.4; 驱动总是认为它发现了一个设备， 而这导致我的
|
||||
Intel EtherExpress 网卡无法正常工作。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>在引导加载的第三阶段， 设置 hint
|
||||
<quote>hint.mcd.0.disabled="1"</quote> 和
|
||||
<quote>hint.mcd.1.disabled="1"</quote>，
|
||||
就可以禁止探测 <devicename>mcd0</devicename> 和
|
||||
<devicename>mcd1</devicename> 设备。 一般而言，
|
||||
在内核配置文件中您应该只保留和启用那些将要用到的设备。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>系统发现了我的 my &man.ed.4; 网卡，但却出现
|
||||
设备超时错误。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>您的卡可能使用了与 <filename>/boot/device.hints</filename>
|
||||
文件中指定的不同的 IRQ。 ed 驱动默认并不使用‘软’配置 (在 DOS 下使用
|
||||
EZSETUP 进行的配置)， 但如果您在接口的 hint 上指定
|
||||
<literal>-1</literal>， 就会使用软配置。</para>
|
||||
|
||||
<para>可以通过跳线来改变硬件的设定 (并根据需要修改内核配置)
|
||||
或通过设置 hint <quote>hint.ed.0.irq="-1"</quote> 将
|
||||
IRQ 指定为 <literal>-1</literal>。 后者将让内核使用软件配置。</para>
|
||||
|
||||
<para>另一种可能是您的卡使用了 IRQ 9， 而这是和 IRQ 2 共用的，
|
||||
这也是经常造成问题的原因
|
||||
(尤其是当您的 VGA 显卡使用 IRQ 2 时!)。 只要可能，
|
||||
您就不应使用 IRQ 2 或 9。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>我从软盘引导安装我的 IBM ThinkPad (tm)膝上型电脑，
|
||||
键盘的输入一团糟。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>较早的 IBM 笔记本使用了非标准的键盘控制器，
|
||||
因此您必须告诉键盘驱动 (atkbd0) 进入与 ThinkPad
|
||||
协同工作的一个特殊模式。 设置
|
||||
hint <quote>hint.atkbd.0.flags="4"</quote> 应该能让其正常工作。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386,pc98,alpha,sparc64">
|
||||
<question>
|
||||
<para>我的系统找不到我的 Intel EtherExpress 16 卡。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>您必须设置您的 Intel EtherExpress 16 卡的内存映射到地址
|
||||
0xD0000， 并使用 Intel 提供的 <filename>softset.exe</filename>
|
||||
程序进行设置， 让使映射后的内存大小为 32K </para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>在 EISA HP Netserver 上安装时，我的
|
||||
AIC-7xxx SCSI 控制器检测不到。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>这是一个已知问题， 并用会在将来对其进行修复。
|
||||
要让系统能够正常安装，
|
||||
需要在加载器第三阶段设置 hint <quote>hw.eisa_slots="12"</quote>。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>我有一台 Panasonic AL-N1 或 Rios Chandler Pentium
|
||||
机器， 我发现每当进入安装时系统都会挂机。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>由于某些原因， 您的机器可能不喜欢新的
|
||||
<literal>i586_copyout</literal> 和
|
||||
<literal>i586_copyin</literal> 代码。
|
||||
要禁用它们， 需要设置 hint <quote>hint.npx.0.flags="1"</quote>。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我有个 CMD640 IDE 控制器， 系统它坏了。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>&os; 不支持这种控制器。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>在一台 Compaq Aero 笔记本上， 当尝试从软盘安装时， 提示 <quote>No
|
||||
floppy devices found! Please check ...</quote>。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>Compaq 系统总是与其它系统有点不同， 他们没有在笔记本的 CMOS RAM
|
||||
中说明软驱的存在。 因此， 驱动程序会认为没有配置软驱。 您需要设置 hint
|
||||
<quote>hint.fdc.0.flags="1"</quote>
|
||||
这样驱动程序将认为第一个软驱存在， 而不去查询 CMOS。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>在安装一台 Dell Poweredge XE 时， 无法识别 Dell
|
||||
自有的 RAID 控制器 DSA (Dell SCSI Array)。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>配置 DSA 来使用 AHA-1540 仿真使用 EISA
|
||||
配置程序。之后 &os; 检测到 DSA
|
||||
作为一个 Adaptec AHA-1540 SCSI 控制器，irq 11 和 port
|
||||
340。在可视化模式下系统将使用 DSA RAID disks，
|
||||
但您不能使用 DSA-specific 里的特性，例如查看 RAID 健壮性。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我有一个 IBM EtherJet PCI 卡，它被
|
||||
&man.fxp.4; 驱动程序正确的探测到， 但网卡上的灯却不亮，
|
||||
也不能连到网络。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>我们不理解为什么会发生这样情况， IBM 也不理解
|
||||
(我们问过他们)。 这块网卡是标准的 Intel EtherExpress
|
||||
Pro/100， 只是上面有 IBM 的标签， 这种卡通常工作的都很好。
|
||||
您可以在一些 IBM 的服务器上看一些这方面的征兆。
|
||||
唯一的解决办法是安装一个不同品牌的网卡。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry arch="i386">
|
||||
<question>
|
||||
<para>当我在配置网络服务期间安装了一个
|
||||
IBM Netfinity 3500， 系统停止了响应。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>在 Netfinity 3500 板上有一个问题， 目前为止我们还没有找出其根源。
|
||||
它可能与系统配置不正确的 SMP 特性有关。
|
||||
目前您只能换一块不同品牌的网卡， 而在任何时候都避免使用板载的。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
<qandaentry>
|
||||
<question>
|
||||
<para>我安装到由 Mylex PCI RAID 控制器管理的磁盘时，
|
||||
系统启动失败 (例如， 显示
|
||||
<literal>read error</literal> 错误信息)。</para>
|
||||
</question>
|
||||
<answer>
|
||||
<para>Mylex 驱动中有一个 bug，
|
||||
它会忽略 BIOS 中的 <quote>8GB</quote> 模式设置。
|
||||
请改为使用 2GB 模式。</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
</qandaset>
|
||||
</sect2>
|
||||
</sect1>
|
||||
@ -1,199 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.13
|
||||
$FreeBSD$
|
||||
|
||||
This section contains the contents of the old UPGRADE.TXT
|
||||
file.
|
||||
-->
|
||||
<sect1 id="upgrading">
|
||||
<title>升级 &os;</title>
|
||||
|
||||
<para>这些说明描述了从一个旧版本的 &os; 执行二进制升级的过程。</para>
|
||||
|
||||
<warning>
|
||||
<para>尽管 &os; 升级过程尽力防止意外的数据丢失，
|
||||
但是仍有很大可能这次安装会
|
||||
<emphasis>擦除您的整个硬盘</emphasis>！
|
||||
请不要接受最后的确认请求，除非您已经备份了所有重要的数据文件。</para>
|
||||
</warning>
|
||||
|
||||
<important>
|
||||
<para>这些说明假定您正在使用您打算升级的 &os; 版本提供的
|
||||
&man.sysinstall.8; 版本。使用一个不匹配的 &man.sysinstall.8;
|
||||
版本几乎总是会造成问题并且已知会让系统处于不可用状态。
|
||||
在这方面最容易犯的错误就是使用现存的安装的旧的
|
||||
&man.sysinstall.8; 副本来升级 &os; 到新的版本。
|
||||
这是 <emphasis>绝不</emphasis> 推荐的。</para>
|
||||
</important>
|
||||
|
||||
<warning>
|
||||
<para>现在还不支持从 &os; 4-STABLE 到 &os; &release.current;
|
||||
的二进制升级。&os; 4-STABLE 中存在的一些文件会引起混乱，
|
||||
但是却不能被二进制升级移除。一个著名的例子就是旧的
|
||||
<filename>/usr/include/g++</filename> 目录会引起 C++
|
||||
程序编译错误 (也可能没有影响)。</para>
|
||||
|
||||
<para>这些升级说明提供给那些从近来的
|
||||
&os; &release.branch; snapshot 升级的用户。</para>
|
||||
</warning>
|
||||
|
||||
<sect2>
|
||||
<title>介绍</title>
|
||||
|
||||
<para>升级过程用相应的最新的
|
||||
&os; release 取代用户选定的发行版本。
|
||||
这个过程保护标准的系统配置文件数据，
|
||||
还有用户数据、已安装的包和其它软件。</para>
|
||||
|
||||
<para>推荐正在考虑升级的管理员在着手升级之前完整阅读这一章节。
|
||||
不这样做的后果很可能就是升级失败或者数据丢失。</para>
|
||||
|
||||
<sect3>
|
||||
<title>升级概览</title>
|
||||
|
||||
<para>发行版本的升级就是执行解压缩新版本组件覆盖当前版本。
|
||||
属于旧的发行版本的文件不会被删除。</para>
|
||||
|
||||
<para>系统配置文件通过保留并恢复下列文件的当前版本来实现保护：</para>
|
||||
|
||||
<para><filename>Xaccel.ini</filename>,
|
||||
<filename>XF86Config</filename>,
|
||||
<filename>adduser.conf</filename>,
|
||||
<filename>aliases</filename>,
|
||||
<filename>aliases.db</filename>,
|
||||
<filename>amd.map</filename>,
|
||||
<filename>crontab</filename>,
|
||||
<filename>csh.cshrc</filename>,
|
||||
<filename>csh.login</filename>,
|
||||
<filename>csh.logout</filename>,
|
||||
<filename>cvsupfile</filename>,
|
||||
<filename>dhclient.conf</filename>,
|
||||
<filename>disktab</filename>,
|
||||
<filename>dm.conf</filename>,
|
||||
<filename>dumpdates</filename>,
|
||||
<filename>exports</filename>,
|
||||
<filename>fbtab</filename>,
|
||||
<filename>fstab</filename>,
|
||||
<filename>ftpusers</filename>,
|
||||
<filename>gettytab</filename>,
|
||||
<filename>gnats</filename>,
|
||||
<filename>group</filename>,
|
||||
<filename>hosts</filename>,
|
||||
<filename>hosts.allow</filename>,
|
||||
<filename>hosts.equiv</filename>,
|
||||
<filename>hosts.lpd</filename>,
|
||||
<filename>inetd.conf</filename>,
|
||||
<filename>localtime</filename>,
|
||||
<filename>login.access</filename>,
|
||||
<filename>login.conf</filename>,
|
||||
<filename>mail</filename>,
|
||||
<filename>mail.rc</filename>,
|
||||
<filename>make.conf</filename>,
|
||||
<filename>manpath.config</filename>,
|
||||
<filename>master.passwd</filename>,
|
||||
<filename>motd</filename>,
|
||||
<filename>namedb</filename>,
|
||||
<filename>networks</filename>,
|
||||
<filename>newsyslog.conf</filename>,
|
||||
<filename>nsmb.conf</filename>,
|
||||
<filename>nsswitch.conf</filename>,
|
||||
<filename>pam.conf</filename>,
|
||||
<filename>passwd</filename>,
|
||||
<filename>periodic</filename>,
|
||||
<filename>ppp</filename>,
|
||||
<filename>printcap</filename>,
|
||||
<filename>profile</filename>,
|
||||
<filename>pwd.db</filename>,
|
||||
<filename>rc.conf</filename>,
|
||||
<filename>rc.conf.local</filename>,
|
||||
<filename>rc.firewall</filename>,
|
||||
<filename>rc.local</filename>,
|
||||
<filename>remote</filename>,
|
||||
<filename>resolv.conf</filename>,
|
||||
<filename>rmt</filename>,
|
||||
<filename>sendmail.cf</filename>,
|
||||
<filename>sendmail.cw</filename>,
|
||||
<filename>services</filename>,
|
||||
<filename>shells</filename>,
|
||||
<filename>skeykeys</filename>,
|
||||
<filename>spwd.db</filename>,
|
||||
<filename>ssh</filename>,
|
||||
<filename>syslog.conf</filename>,
|
||||
<filename>ttys</filename>,
|
||||
<filename>uucp</filename>
|
||||
</para>
|
||||
|
||||
<para>这些文件相应的新版本被转移到
|
||||
<filename>/etc/upgrade/</filename>。
|
||||
系统管理员可以仔细阅读这些新版本并合并需要的部分。
|
||||
注意这里面很多文件是相互依赖的，
|
||||
最好的合并过程是将所有的站点特定数据从当前文件复制进新的文件。</para>
|
||||
|
||||
<para>在升级过程中，会提示管理员
|
||||
<filename>/etc/</filename> 中所有文件要存放的位置。
|
||||
在本地修改合并进入其它文件后，也可以从这个位置再找回它们。</para>
|
||||
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>过程</title>
|
||||
|
||||
<para>这一节详细描述了升级过程。尤其关注那些和通常的安装有明显区别的部分。</para>
|
||||
|
||||
<sect3>
|
||||
<title>备份</title>
|
||||
|
||||
<para>用户数据和系统配置文件在升级前应该备份。
|
||||
尽管升级过程尽力的去防止意外的失误，
|
||||
还是有可能全部或部分的毁坏数据和配置文件信息。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>挂载文件系统</title>
|
||||
|
||||
<para>进入 disklabel 编辑器会列出命名的磁盘文件系统设备。
|
||||
在着手升级前，管理员应该记录一下设备名和相应的挂载点。
|
||||
这些挂载点应该在这里输入。
|
||||
<emphasis>不要</emphasis> 对任何文件系统设置<quote>newfs
|
||||
flag</quote>，因为这会引起数据丢失。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>选择 Distribution</title>
|
||||
|
||||
<para>选择 distribution 的时候，没有强制的约束必须选择哪一个。
|
||||
基本规则是，<literal>base</literal>
|
||||
distribution 对于升级来说应该选择，如果已经安装了联机手册
|
||||
<literal>man</literal> distribution 也应该选择。
|
||||
如果管理员希望添加额外的功能，在最初的安装之外其它 distribution
|
||||
也可以选择。</para>
|
||||
</sect3>
|
||||
|
||||
<sect3 id="fstab">
|
||||
<title>安装之后</title>
|
||||
|
||||
<para>一旦安装过程完成，就会提示管理员检查新的配置文件。
|
||||
这时候，应该做下检查来保证系统配置文件有效。
|
||||
尤其是，应该检查 <filename>/etc/rc.conf</filename> 和
|
||||
<filename>/etc/fstab</filename> 文件。</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>从源代码升级</title>
|
||||
|
||||
<para>那些对允许更复杂、诡异的升级方法感兴趣的人应该看看
|
||||
&os; 使用手册的 <ulink
|
||||
url="&url.books.handbook;/cutting-edge.html">
|
||||
最前沿</ulink> 一章。这个过程包括了从源代码重建整个 &os;。
|
||||
这依赖于可靠的网络连接、额外的磁盘空间和时间，
|
||||
但是有网络以及其它更复杂安装的优势。
|
||||
这基本和跟踪 -STABLE 或 -CURRENT 开发分支的过程是相同的。</para>
|
||||
|
||||
<para><filename>/usr/src/UPDATING</filename> 包含了从源代码升级 &os;
|
||||
系统的重要信息。它列出了 &os; 中各种各样可能影响升级的改动。</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
@ -1,21 +0,0 @@
|
||||
# Original Revision: 1.4
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/abstract.sgml
|
||||
SRCS+= ../common/install.sgml
|
||||
SRCS+= ../common/layout.sgml
|
||||
SRCS+= ../common/trouble.sgml
|
||||
SRCS+= ../common/upgrade.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,31 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.5
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/install.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "i386">
|
||||
<!ENTITY arch.print "i386">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
&abstract;
|
||||
§.install;
|
||||
§.layout;
|
||||
§.upgrade;
|
||||
§.trouble;
|
||||
</article>
|
||||
@ -1,21 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/abstract.sgml
|
||||
SRCS+= ../common/install.sgml
|
||||
SRCS+= ../common/layout.sgml
|
||||
SRCS+= ../common/trouble.sgml
|
||||
SRCS+= ../common/upgrade.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,31 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.2
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/install.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "ia64">
|
||||
<!ENTITY arch.print "IA-64">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
&abstract;
|
||||
§.install;
|
||||
§.layout;
|
||||
§.upgrade;
|
||||
§.trouble;
|
||||
</article>
|
||||
@ -1,21 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/abstract.sgml
|
||||
SRCS+= ../common/install.sgml
|
||||
SRCS+= ../common/layout.sgml
|
||||
SRCS+= ../common/trouble.sgml
|
||||
SRCS+= ../common/upgrade.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,31 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.2
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/install.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "pc98">
|
||||
<!ENTITY arch.print "NEC PC-98x1">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
&abstract;
|
||||
§.install;
|
||||
§.layout;
|
||||
§.upgrade;
|
||||
§.trouble;
|
||||
</article>
|
||||
@ -1,19 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= install.sgml
|
||||
SRCS+= ../common/artheader.sgml
|
||||
SRCS+= ../common/install.sgml
|
||||
SRCS+= ../common/layout.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,31 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.5
|
||||
$FreeBSD$
|
||||
-->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/install.ent"> %sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "sparc64">
|
||||
<!ENTITY arch.print "UltraSPARC">
|
||||
<!ENTITY release.url "ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&artheader;
|
||||
&abstract;
|
||||
§.install;
|
||||
§.layout;
|
||||
§.upgrade;
|
||||
§.trouble;
|
||||
</article>
|
||||
@ -1,566 +0,0 @@
|
||||
<!--
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.15
|
||||
$FreeBSD$
|
||||
|
||||
This file contains sparc64-specific installation instructions.
|
||||
|
||||
-->
|
||||
|
||||
<sect1 id="install">
|
||||
<title>Installing &os;</title>
|
||||
|
||||
<para>This text describes how to install and boot the &arch; port.
|
||||
Users of this port are encouraged to subscribe to the
|
||||
&a.sparc;.</para>
|
||||
|
||||
<warning>
|
||||
<para>The kernel and userland binaries mentioned below are highly
|
||||
experimental (for example, the kernel contains some ATA changes
|
||||
and EEPROM handling code which could potentially be dangerous).
|
||||
Unless you know what you are doing and are willing to cope with
|
||||
any damage that might arise, you should probably not be trying
|
||||
this.</para>
|
||||
</warning>
|
||||
|
||||
<para>Unlike &os;/i386 or &os;/alpha, there is no version of
|
||||
&man.sysinstall.8; for &os;/&arch;. The installation procedure
|
||||
consists of loading a kernel (either from CDROM or the network)
|
||||
onto the &arch; machine, with a root filesystem on CDROM or
|
||||
exported via NFS. The utilities on the root filesystem can then
|
||||
be used to partition the local disk on the &arch; machine and
|
||||
optionally to copy the &os; distribution to the local disk to make
|
||||
a stand-alone machine.</para>
|
||||
|
||||
<para>Currently, there are two ways to install &os;/&arch; on a new
|
||||
machine. By far the easier of the two is to install from CDROM;
|
||||
this method allows you to install &os; without any dependencies on
|
||||
any other computers.</para>
|
||||
|
||||
<para>If installing from CDROM is impossible or undesirable, the
|
||||
alternative is to install over the network. This requires another
|
||||
machine, suitably configured, to serve the boot loader, kernel,
|
||||
and root filesystem to the new machine, via a combination of
|
||||
RARP, TFTP, and either BOOTP or DHCP. This netboot server can be
|
||||
another &os; machine, but is not required to be.</para>
|
||||
|
||||
<para>You will need to decide which of these methods you want to use
|
||||
for installation, as this will determine the set of files you need
|
||||
to download (if any), as well as the steps required to do the
|
||||
installation.</para>
|
||||
|
||||
<!-- this should read "in this document" after the re-structure -->
|
||||
|
||||
<important>
|
||||
<para>The URLs in this section are provisional and subject to
|
||||
change. Please see the archives of the &a.sparc; for the most
|
||||
recent locations of files. This notice will be removed when
|
||||
more permanent URLs have been determined.</para>
|
||||
</important>
|
||||
|
||||
<sect2 id="getting-to-prom-prompt">
|
||||
<title>Getting to the PROM Prompt</title>
|
||||
|
||||
<para>Most &arch; systems are set up to boot automatically from
|
||||
disk. To install &os;, you need to boot over the network or
|
||||
from a CDROM, which requires you to break into the PROM
|
||||
(OpenFirmware).</para>
|
||||
|
||||
<para>To do this, reboot the system, and wait until the boot
|
||||
message appears. It depends on the model, but should look about
|
||||
like:</para>
|
||||
|
||||
<screen>Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
|
||||
Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved.
|
||||
OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
|
||||
Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
|
||||
|
||||
<para>If your system proceeds to boot from disk at this point, you
|
||||
need to press <keycombo
|
||||
action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo>
|
||||
or <keycombo
|
||||
action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo>
|
||||
on the keyboard, or send a <command>BREAK</command> over the
|
||||
serial console (using for example <command>~#</command> in
|
||||
&man.tip.1; or &man.cu.1;) to get to the PROM prompt. It looks
|
||||
like this:</para>
|
||||
|
||||
<screenco>
|
||||
<areaspec>
|
||||
<area id="prompt-single" coords="1 5">
|
||||
<area id="prompt-smp" coords="2 5">
|
||||
</areaspec>
|
||||
|
||||
<screen><prompt>ok </prompt>
|
||||
<prompt>ok {0} </prompt></screen>
|
||||
|
||||
<calloutlist>
|
||||
<callout arearefs="prompt-single">
|
||||
<para>This is the prompt used on systems with just one
|
||||
CPU.</para>
|
||||
</callout>
|
||||
|
||||
<callout arearefs="prompt-smp">
|
||||
<para>This is the prompt used on SMP systems, the digit
|
||||
indicates the number of the active CPU.</para>
|
||||
</callout>
|
||||
</calloutlist>
|
||||
</screenco>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="prepare-cd">
|
||||
<title>Preparing for a CDROM Installation</title>
|
||||
|
||||
<para>If you want to do a CDROM installation, an ISO image with a
|
||||
snapshot of &os;/&arch; can be found at <ulink
|
||||
url="&release.url;"></ulink>. This file can be used to create a
|
||||
bootable CDROM which contains everything necessary to boot and
|
||||
load at least a minimal &os; installation.</para>
|
||||
|
||||
<!-- XXX ISO location?-->
|
||||
<para>Place the CDROM into your drive, and break into the PROM as
|
||||
described above. On the PROM prompt, type <command>boot
|
||||
cdrom</command>. The system should boot into single-user mode
|
||||
now, and you can create the disk label and install the base
|
||||
system archive as described in <xref
|
||||
linkend="creating-disk-label"> and <xref
|
||||
linkend="creating-root-filesystem">.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="prepare-network">
|
||||
<title>Preparing for a Network Installation</title>
|
||||
|
||||
<para>A &os;/&arch; kernel is booted by having the firmware
|
||||
retrieve and execute a <application>loader</application>, which
|
||||
in turn fetches and executes the actual kernel. For this boot
|
||||
process, you need to set up &man.rarpd.8; and &man.tftpd.8; (for
|
||||
the firmware) and &man.bootpd.8; (for the
|
||||
<application>loader</application>) on another networked system.
|
||||
The loader can fetch a kernel using TFTP or NFS. All of this is
|
||||
covered in detail below.</para>
|
||||
|
||||
<sect3 id="downloading">
|
||||
<title>Getting the Required Files</title>
|
||||
|
||||
<para>For a network installation, you will need several files.
|
||||
First, you will need to download a &os;/&arch; loader for
|
||||
&man.tftpd.8; to serve to your &arch; client. The loader will
|
||||
use either TFTP or NFS to retrieve the &os; kernel from the
|
||||
netboot server. There is a separate loader for each of these
|
||||
methods (i.e. a loader for TFTP and a loader for NFS). You
|
||||
should download one of the following files, as
|
||||
appropriate:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="&release.url;loader-tftp.gz"></ulink></para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><ulink
|
||||
url="&release.url;loader-nfs.gz"></ulink></para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>A network installation also requires a kernel to be served
|
||||
to the netboot client. A suitable kernel can be found at
|
||||
<ulink url="&release.url;"></ulink>.</para>
|
||||
<!-- XXX kernel filename?-->
|
||||
|
||||
<para>Finally, you will need a &man.tar.1; archive which
|
||||
contains the binaries and configuration files from the base
|
||||
system. This file is available from <ulink
|
||||
url="&release.url;distrib.tar.gz"></ulink>.</para>
|
||||
</sect3>
|
||||
|
||||
<!-- put the words "netboot server" in here -->
|
||||
<sect3>
|
||||
<title>rarpd</title>
|
||||
|
||||
<para>You need to add the Ethernet address of your &os;/&arch;
|
||||
system to <filename>/etc/ethers</filename> on the netboot
|
||||
server. An entry looks like:</para>
|
||||
|
||||
<programlisting>0:3:ba:b:92:d4 your.host.name</programlisting>
|
||||
|
||||
<para>The Ethernet address is usually displayed in the boot
|
||||
message.</para>
|
||||
|
||||
<para>Make sure <hostid>your.host.name</hostid> is in
|
||||
<filename>/etc/hosts</filename> or has a valid DNS entry (or
|
||||
use an IP address). Then, start &man.rarpd.8; on a network
|
||||
interface that is on the same subnet as the &os;/&arch;
|
||||
system.</para>
|
||||
</sect3>
|
||||
|
||||
<!-- put the words "netboot server" in here -->
|
||||
<sect3>
|
||||
<title>tftpd</title>
|
||||
|
||||
<para>Activate &man.tftpd.8; in your &man.inetd.8;
|
||||
configuration by uncommenting the following line in
|
||||
<filename>/etc/inetd.conf</filename>:</para>
|
||||
|
||||
<programlisting>tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot</programlisting>
|
||||
|
||||
<para>Copy the unpacked loader to your
|
||||
<filename>/tftpboot</filename> directory, and name it with the
|
||||
&os;/&arch; host's IP address in upper-case hexadecimal
|
||||
notation without dots (or use appropriately-named symbolic
|
||||
links). For example, your setup may look like this, for an IP
|
||||
address of <hostid>192.168.0.16</hostid>:</para>
|
||||
|
||||
<screen> lrwx------ 1 tmm users 9 Jul 24 17:05 /tftpboot/C0A80010 -> boot/loader
|
||||
-rw-r--r-- 1 tmm users 1643021 Oct 20 18:04 /tftpboot/boot/loader</screen>
|
||||
|
||||
<para>If you have trouble booting, it is very helpful to use
|
||||
&man.tcpdump.1; to monitor the TFTP requests. This will allow
|
||||
you to see the file name you need to use for the loader.
|
||||
Error replies by the TFTP server are most often due to
|
||||
incorrect file permissions.</para>
|
||||
</sect3>
|
||||
|
||||
<!-- put the words "netboot server" in here -->
|
||||
<sect3>
|
||||
<title>Setting up bootpd/dhcpd</title>
|
||||
|
||||
<para>You can use either BOOTP or DHCP (both not both) to
|
||||
provide some parameters to the boot loader, such as a
|
||||
machine's IP address. If you are using another &os; machine
|
||||
as a netboot server, the BOOTP functionality is provided by
|
||||
&man.bootpd.8;, which is a part of the &os; base system.
|
||||
Several DHCP servers are provided in the &os; Ports
|
||||
Collection.</para>
|
||||
|
||||
<para>If you are going to use &man.bootpd.8;, create entries for
|
||||
your &os;/&arch; system in the server's
|
||||
<filename>/etc/bootptab</filename> (see &man.bootptab.5; for
|
||||
more details):</para>
|
||||
|
||||
<programlisting>.default:\
|
||||
:bf="kernel":dn=local:ds=<replaceable>name-server-ip-address</replaceable>:\
|
||||
:gw=<replaceable>gateway-ip-address</replaceable>:ht=ether:hd="/tftpboot/boot/kernel":hn:\
|
||||
:sa="<replaceable>tftp-server-ip-address</replaceable>":\
|
||||
:rp="<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>":\
|
||||
:sm=<replaceable>ip-netmask</replaceable>
|
||||
|
||||
<replaceable>name-of-the-entry</replaceable>:\
|
||||
ha=<replaceable>sparc64-ethernet-address</replaceable>:ip=<replaceable>sparc64-ip-address</replaceable>:tc=.default</programlisting>
|
||||
|
||||
<para>The Ethernet address must be the same as the one in the
|
||||
TFTP example above, but it is specified hexadecimal notation
|
||||
without colons (for the example above, this would be
|
||||
<literal>0003ba0b92d4</literal>). NFS/TFTP specific entries
|
||||
can be omitted if the given method is not used. The strings
|
||||
given in the <literal>hd</literal> and <literal>bf</literal>
|
||||
properties are concatenated to give the boot file name. If
|
||||
your kernel is named differently or you use another directory,
|
||||
change these values as required. If you are booting using
|
||||
NFS, remove the <literal>bf</literal> and
|
||||
<literal>hd</literal> settings (or change them to specify the
|
||||
directory and file inside the NFS root hierarchy in which the
|
||||
kernel will reside). The name of the host entry is
|
||||
conventionally the host name without the domain
|
||||
appended.</para>
|
||||
|
||||
<para>For a DHCP server, add an entry similar to the following
|
||||
to your <filename>dhcpd.conf</filename> file. An example
|
||||
entry for <application>ISC DHCP</application> version 2
|
||||
(available in the &os; Ports Collection as <filename
|
||||
role="package">net/isc-dhcp2</filename>) is shown
|
||||
below:</para>
|
||||
|
||||
<programlisting>host <replaceable>name-of-entry</replaceable> {
|
||||
hardware ethernet <replaceable>sparc64-ethernet-address</replaceable>;
|
||||
option host-name "<replaceable>sparc64-fully-qualified-domain-name</replaceable>";
|
||||
fixed-address <replaceable>sparc64-ip-address</replaceable>;
|
||||
always-reply-rfc1048 on;
|
||||
filename "kernel";
|
||||
option root-path "<replaceable>tftp-server-ip-address</replaceable>:<replaceable>nfs-root-directory</replaceable>";
|
||||
}</programlisting>
|
||||
|
||||
<para>The <literal>filename</literal> option corresponds to the
|
||||
concatenation of <literal>hd</literal> and
|
||||
<literal>bf</literal> in <filename>/etc/bootptab</filename>.
|
||||
The Ethernet address is specified in hexadecimal with colons,
|
||||
just like in the &man.rarpd.8; example above.
|
||||
<literal>options root-path</literal> corresponds to
|
||||
<literal>rp</literal> in <filename>/etc/bootptab</filename>.
|
||||
If the name given in <literal>option host-name</literal> is
|
||||
resolvable, i.e. has a DNS entry or is associated with an
|
||||
address in <filename>/etc/hosts</filename>, the
|
||||
<literal>fixed-address</literal> specification can be
|
||||
omitted.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Loading the Kernel</title>
|
||||
|
||||
<para>With the daemons on the netboot server configured, the
|
||||
next step is to copy the kernel (obtained during the steps of
|
||||
<xref linkend="downloading">) to an appropriate directory.
|
||||
There are two ways of retrieving a kernel over the network:
|
||||
TFTP and NFS. (You specified one of these two alternatives by
|
||||
picking a loader.)</para>
|
||||
|
||||
<para>For both TFTP and NFS, the loader will use the parameters
|
||||
that it obtained via BOOTP or DHCP to find the kernel.</para>
|
||||
|
||||
<sect4>
|
||||
<title>Loading the Kernel over TFTP</title>
|
||||
|
||||
<para>Place the kernel in the directory you specified using
|
||||
<literal>bf</literal> and <literal>hd</literal> in the
|
||||
<filename>/etc/bootptab</filename> or the
|
||||
<literal>filename</literal> parameter to
|
||||
<filename>dhcpd.conf</filename>.</para>
|
||||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Loading the Kernel over NFS</title>
|
||||
|
||||
<para>Export the directory that was specified by the
|
||||
<literal>rp</literal> property in
|
||||
<filename>/etc/bootptab</filename> or the
|
||||
<literal>root-path</literal> parameter in
|
||||
<filename>dhcpd.conf</filename> (see &man.exports.5;). Copy
|
||||
the kernel to the directory you specified using
|
||||
<literal>bf</literal> and <literal>hd</literal> in the
|
||||
<filename>/etc/bootptab</filename> or the
|
||||
<literal>filename</literal> parameter to
|
||||
<filename>dhcpd.conf</filename>.</para>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Loading the Base System to the Netboot Server</title>
|
||||
|
||||
<para>You must extract the base system distribution image to the
|
||||
NFS root directory specified either by the
|
||||
<literal>rp</literal> option in
|
||||
<filename>/etc/bootptab</filename> or the
|
||||
<literal>root-path</literal> option in
|
||||
<filename>dhcpd.conf</filename>. This directory tree will
|
||||
become the &arch;'s root filesystem once the kernel is booted.
|
||||
Besides providing a normal userland environment, it also
|
||||
contains all of the necessary utilities for you to install the
|
||||
distribution on the &arch; client's local disk.</para>
|
||||
|
||||
<para>Using whatever editing tools you have on the netboot
|
||||
server, you probably will want to edit the &arch;'s
|
||||
<filename>/etc/fstab</filename> and
|
||||
<filename>/etc/rc.conf</filename> and set a
|
||||
<username>root</username> password.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Booting</title>
|
||||
|
||||
<para>If all goes well, you can now boot the &os; on your &arch;
|
||||
machine by dropping into the PROM prompt as described in <xref
|
||||
linkend="getting-to-prom-prompt">. Now, just type
|
||||
<command>boot net</command> and the system should boot.
|
||||
Specifically, the loader is retrieved via TFTP, it then does a
|
||||
BOOTP request and will proceed to load the kernel (either
|
||||
using TFTP or NFS, depending on your choice of loader). Then,
|
||||
it should wait 10 seconds for user input and proceed to
|
||||
execute the kernel.</para>
|
||||
|
||||
<para>If something does not work in between, and you suspect
|
||||
TFTP/NFS/BOOTP problems, <application>Ethereal</application>
|
||||
(available in the &os; Ports Collection as <filename
|
||||
role="package"> net/ethereal</filename>) is usually helpful.
|
||||
The most common problems are related to bad file permissions.
|
||||
Also note that &man.rarpd.8; will not answer to packets under
|
||||
some circumstances, refer to the manual page for
|
||||
details.</para>
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="creating-disk-label">
|
||||
<title>Creating a Disk Label</title>
|
||||
|
||||
<para>The kernel supports the Sun disk label format, so you can
|
||||
label the disks you want to use with &os; from Solaris.</para>
|
||||
|
||||
<para>&os; disk labels must currently be created by hand, as
|
||||
&man.sysinstall.8; is not yet available on &os;/&arch;. Please
|
||||
refer to the <ulink
|
||||
url="&url.books.handbook;/">&os;
|
||||
Handbook</ulink> for more information about labels and special
|
||||
partitions.</para>
|
||||
|
||||
<para>On &os;/&arch;, a Sun compatibility label is embedded in the
|
||||
&os; label; this is needed for the PROM to boot from disk. This
|
||||
imposes an additional restriction on the disk label format:
|
||||
partitions are required to start on a cylinder boundary.</para>
|
||||
|
||||
<para>To create a disk label, the following procedure is the
|
||||
easiest:</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Run <command>disklabel -w -r
|
||||
<replaceable>device</replaceable> auto</command> to create a
|
||||
basic disk label. The third argument you need specify here
|
||||
is just the name of the device, not the complete path to the
|
||||
device node (e.g. <devicename>ad0</devicename> for the first
|
||||
ATA disk).</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para> Use <command>disklabel -e
|
||||
<replaceable>device</replaceable></command> to open an
|
||||
editor in which you can edit the disk label. The
|
||||
information presented to you should look like:</para>
|
||||
|
||||
<screen># /dev/ad6c:
|
||||
type: unknown
|
||||
disk: amnesiac
|
||||
label:
|
||||
flags:
|
||||
bytes/sector: 512
|
||||
sectors/track: 63
|
||||
tracks/cylinder: 16
|
||||
sectors/cylinder: 1008
|
||||
cylinders: 79780
|
||||
sectors/unit: 80418240
|
||||
rpm: 3600
|
||||
interleave: 1
|
||||
trackskew: 0
|
||||
cylinderskew: 0
|
||||
headswitch: 0 # milliseconds
|
||||
track-to-track seek: 0 # milliseconds
|
||||
drivedata: 0
|
||||
|
||||
8 partitions:
|
||||
# size offset fstype [fsize bsize bps/cpg]
|
||||
c: 80418240 0 unused 0 0 # (Cyl. 0 - 79779)</screen>
|
||||
|
||||
<para>You can now add new partitions in the same format as the
|
||||
already present line. Using <literal>*</literal> in the
|
||||
offset field makes the procedure easier; please refer to the
|
||||
&man.disklabel.8; manual page for more information.</para>
|
||||
|
||||
<para>To make sure the restriction mentioned above is met, the
|
||||
size of each partition must be a multiple of the number of
|
||||
sectors per cylinder as shown in the information that is
|
||||
presented in the editor (1008 in the example above).</para>
|
||||
|
||||
<para>When you are done, save your changes and quit the
|
||||
editor.i This will cause the disk label to be
|
||||
written.</para>
|
||||
|
||||
<warning>
|
||||
<para>This procedure will overwrite any disk label that may
|
||||
be already present on the disk. Any existing filesystems
|
||||
on this disk must have their respective partition entries
|
||||
in the old and new label match
|
||||
<emphasis>exactly</emphasis>, or they will be
|
||||
lost.</para>
|
||||
</warning>
|
||||
|
||||
<para>If you want to double-check that your partitions end on
|
||||
cylinder boundaries, run <command>disklabel -e
|
||||
<replaceable>device</replaceable></command> again. The
|
||||
editor will display the cylinders used by a particular
|
||||
partition on the right hand side of the output. If any of
|
||||
the partitions you defined (i.e. anything except partition
|
||||
<literal>c</literal>) shows an <literal>*</literal> next to
|
||||
it, the partition does <emphasis>NOT</emphasis> start or end
|
||||
on a cylinder boundary. You <emphasis>MUST</emphasis> fix
|
||||
these or your system will not work.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
<para>Use <command>disklabel -B</command> if you want to make
|
||||
the disk bootable for &os;/&arch;.</para>
|
||||
|
||||
<warning>
|
||||
<para>Using <command>disklabel -B</command> on a disk will
|
||||
overwrite any preexisting boot block, so it will likely
|
||||
render any other operating system installed on the same
|
||||
disk unbootable.</para>
|
||||
</warning>
|
||||
|
||||
<para>If you do not want to overwrite the boot block, it is
|
||||
possible to load the <application>loader</application> via
|
||||
TFTP as described above, but have it boot the kernel from
|
||||
disk. This requires a special loader binary, which is
|
||||
available at <ulink
|
||||
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz"></ulink></para>
|
||||
</step>
|
||||
</procedure>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="creating-root-filesystem">
|
||||
<title>Creating the Root Fileystem</title>
|
||||
|
||||
<para>If you want to boot from a local disk, you will need to
|
||||
create a root filesystem to hold the base system binaries and
|
||||
configuration files (and optionally other filesystems mounted
|
||||
in places such as <filename>/usr</filename> and
|
||||
<filename>/var</filename>).</para>
|
||||
|
||||
<para>The kernel contains support for Sun disklabels, so you can
|
||||
use Solaris disks, which may even be prepared using
|
||||
<application>newfs</application> under Solaris. NetBSD disk
|
||||
labels and filesystems are also usable from &os;.</para>
|
||||
|
||||
<warning>
|
||||
<para>Do <emphasis>not</emphasis> run Solaris
|
||||
<application>fsck</application> on filesystems modified by
|
||||
&os;. Doing so will damage the file permissions.</para>
|
||||
</warning>
|
||||
|
||||
<para>To create filesystems and to install the base system, boot
|
||||
from CDROM or via NFS and create a disk label as described in
|
||||
<xref linkend="creating-disk-label">.</para>
|
||||
|
||||
<para>When booting the first time and you have not entered your
|
||||
root partition into <filename>/etc/fstab</filename> yet, you may
|
||||
need to specify your root partition on the mountroot prompt when
|
||||
booting (use a format like
|
||||
<command>ufs:<replaceable>disk</replaceable><replaceable>partition</replaceable></command>,
|
||||
i.e. leave the slice specification out). If the kernel does
|
||||
automatically attempt to boot from another filesystem, press a
|
||||
key other than <keycap>Enter</keycap> on the
|
||||
<application>loader</application> prompt:</para>
|
||||
|
||||
<screen>Hit [Enter] to boot immediately, or any other key for command prompt.</screen>
|
||||
|
||||
<para>Then, boot the kernel using <command>boot -a -s</command>,
|
||||
which will cause the kernel to ask you for the root partition
|
||||
and then boot into single-user mode. Once the root filesystem
|
||||
has been entered into <filename>/etc/fstab</filename>, it should
|
||||
be automatically mounted as <filename>/</filename> on the next
|
||||
boot.</para>
|
||||
|
||||
<para>If you are booting over the network (via NFS), the above
|
||||
BOOTP entries should suffice to have the kernel find and mount
|
||||
the root filesystem via NFS.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="installing-base-system">
|
||||
<title>Installing the Base System</title>
|
||||
|
||||
<para>If you booted the kernel from the network, you downloaded a
|
||||
&man.tar.1; archive with the base system and exported it from
|
||||
the netboot server via NFS. You can unpack this same archive to
|
||||
your local disk to create a stand-alone system (remember to copy
|
||||
the kernel over as well).</para>
|
||||
|
||||
<para>If you booted from CDROM, the same archive is available in
|
||||
<filename>/root/</filename> on the CDROM.</para>
|
||||
|
||||
<para>Before booting the system stand-alone, you will want to edit
|
||||
<filename>/etc/fstab</filename> and
|
||||
<filename>/etc/rc.conf</filename> and set a
|
||||
<username>root</username> password.</para>
|
||||
|
||||
<para>Note that some programs from the base system may not be
|
||||
present in the archive, or may not work properly yet.</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
@ -2,7 +2,7 @@
|
||||
The FreeBSD Documentation Project
|
||||
The FreeBSD Simplified Chinese Project
|
||||
|
||||
Original Revision: 1.37
|
||||
Original Revision: 1.40
|
||||
-->
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
@ -27,6 +27,8 @@
|
||||
<year>2003</year>
|
||||
<year>2004</year>
|
||||
<year>2005</year>
|
||||
<year>2006</year>
|
||||
<year>2007</year>
|
||||
<holder role="mailto:doc@FreeBSD.org">The &os; Documentation Project</holder>
|
||||
</copyright>
|
||||
|
||||
@ -56,13 +58,12 @@
|
||||
<title>关于 &os;</title>
|
||||
|
||||
<para>&os; 是一个基于 4.4 BSD Lite 的操作系统，支持
|
||||
DEC/Compaq/HP Alpha/AXP 计算机 (alpha)，
|
||||
基于 AMD64 和 Intel EM64T 的 PC 硬件 (amd64)，
|
||||
基于 Intel, AMD, Cyrix 或 NexGen <quote>x86</quote> 的 PC 硬件 (i386)，
|
||||
基于 Intel Itanium Processor 的计算机 (ia64)，
|
||||
NEC PC-9801/9821 系列 PC 及其兼容机 (pc98)，
|
||||
以及 &ultrasparc; 机器 (sparc64)。
|
||||
支持 &powerpc; (powerpc), and &mips; (mips)
|
||||
基于 AMD64 和 Intel EM64T 的 PC 硬件 (&arch.amd64;)，
|
||||
基于 Intel, AMD, Cyrix 或 NexGen <quote>x86</quote> 的 PC 硬件 (&arch.i386;)，
|
||||
基于 Intel Itanium Processor 的计算机 (&arch.ia64;)，
|
||||
NEC PC-9801/9821 系列 PC 及其兼容机 (&arch.pc98;)，
|
||||
以及 &ultrasparc; 机器 (&arch.sparc64;)。
|
||||
支持 &powerpc; (&arch.powerpc;) 和 &mips; (mips)
|
||||
硬件架构的的版本也正在开发中。
|
||||
&os; 支持各种各样的外围设备，
|
||||
可以胜任软件开发、游戏，以及提供 Internet
|
||||
@ -168,8 +169,8 @@
|
||||
<para>&os; -RELEASE 发行版本可以从几个发行商那里以 CDROM 或者 DVD
|
||||
的形式订购。 对于全新安装来说， 这通常是获取 &os; 最方便的方式，
|
||||
因为它提供了在必要时快速地重新安装系统的方法。
|
||||
一些发行版本包含了一些来自 &os; Ports Collection 的可选的、
|
||||
预编译的 <quote>package</quote>。</para>
|
||||
一些发行版本包含了一些来自 &os; Ports 套件的可选的、
|
||||
预编译的 <quote>package</quote> 以及其他资料。</para>
|
||||
|
||||
<para>一个已知的 CDROM 和 DVD
|
||||
发行商列表列在使用手册的 <ulink
|
||||
@ -199,10 +200,10 @@
|
||||
URL="&url.articles.hubs;/">如何为 &os; 做镜像站点</ulink>
|
||||
这篇文章中找到关于镜像站点的更多有用的信息。</para>
|
||||
|
||||
<para>镜像通常包含启动安装程序所必需的软盘镜像，
|
||||
以及安装进程本身所需要的发行版本文件。
|
||||
许多镜像也包含创建 &os; 发行 CDROM 的必要的 ISO 镜像。</para>
|
||||
|
||||
<para>镜像站点通常会提供用于刻录 &os; 发行版本的 CDROM
|
||||
的 ISO 映像文件。 它们通常包括了软盘映像 (仅限支持的平台)
|
||||
以及通过网络安装所需要的文件。 最后，
|
||||
镜像站点通常还会提供最新发行版本对应的预编译软件包。</para>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
@ -287,7 +288,7 @@
|
||||
大多数发行版本会包含
|
||||
ASCII 文本 (<filename>.TXT</filename>) 和 HTML
|
||||
(<filename>.HTM</filename>) 格式。有一些发行版本也可能包含其它的格式，
|
||||
比如 PostScript(<filename>.PS</filename>)或者可移植文档格式
|
||||
比如 Portable Document Format
|
||||
(<filename>.PDF</filename>)。
|
||||
|
||||
<itemizedlist>
|
||||
@ -308,11 +309,6 @@
|
||||
展示了 &os; 已经测试并已知可以使用的设备。</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename>INSTALL.TXT</filename>：用于从发行介质安装
|
||||
&os; 的安装说明。</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para><filename>ERRATA.TXT</filename>：发行勘误。
|
||||
提供新近发现的、 发行之后发现的问题等信息，
|
||||
@ -322,20 +318,10 @@
|
||||
创建以来发现并修正问题的最新的信息。</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<note>
|
||||
<para>这几个文档(特别是，
|
||||
<filename>RELNOTES.TXT</filename>、
|
||||
<filename>HARDWARE.TXT</filename> 和
|
||||
<filename>INSTALL.TXT</filename>) 包含了对特定硬件体系的信息。
|
||||
比如， alpha 发行说明中可能包含某些不适用于 &i386; 的信息，
|
||||
反之亦然。 每篇文档适用的体系结构会在文档的标题处列出。</para>
|
||||
</note>
|
||||
|
||||
</para>
|
||||
|
||||
<para>在支持 &man.sysinstall.8; 的平台上 (目前有
|
||||
alpha、&i386;、ia64、pc98 还有 &sparc64;)，
|
||||
&arch.amd64;、 &arch.i386;、 &arch.ia64;、 &arch.pc98; 以及 &arch.sparc64;)，
|
||||
这些文档在安装时都可以通过 Documentation 菜单访问。
|
||||
一旦系统已经安装，您可以通过重新运行
|
||||
&man.sysinstall.8; 工具来重新访问菜单。</para>
|
||||
@ -380,7 +366,8 @@
|
||||
url="&url.books.faq;/">FreeBSD
|
||||
文档页面</ulink> 或者它的镜像上得到。 如果安装了
|
||||
<filename>doc</filename> 发行集， 则可以在本地使用 Web
|
||||
浏览器来阅读使用手册和 FAQ。</para>
|
||||
浏览器来阅读使用手册和 FAQ。 值得一提的是，
|
||||
在使用手册中提供了如何安装 &os; 的详细说明。</para>
|
||||
|
||||
<para>许多在线书籍和文章也由 &os; 项目维护， 涵盖了更专业的、&os;
|
||||
相关的主题。 这些文章题材广泛，从邮件列表的有效使用到双重启动
|
||||
|
||||
@ -1,16 +1,27 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
# Original Revision: 1.8
|
||||
# Original Revision: 1.11
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../..
|
||||
|
||||
SUBDIR = amd64
|
||||
SUBDIR+= ia64
|
||||
SUBDIR+= i386
|
||||
SUBDIR+= pc98
|
||||
SUBDIR+= powerpc
|
||||
SUBDIR+= sparc64
|
||||
.ifdef NO_LANGCODE_IN_DESTDIR
|
||||
DESTDIR?= ${DOCDIR}/relnotes
|
||||
.else
|
||||
DESTDIR?= ${DOCDIR}/zh_CN.GB2312/relnotes
|
||||
.endif
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
|
||||
URL_RELPREFIX?= ../../../..
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
|
||||
@ -1,10 +0,0 @@
|
||||
# The FreeBSD Simplified Chinese Project
|
||||
# Original Revision: 1.2
|
||||
#
|
||||
# $FreeBSD$
|
||||
|
||||
.ifdef NO_LANGCODE_IN_DESTDIR
|
||||
DESTDIR?= ${DOCDIR}/relnotes/${.CURDIR:T}
|
||||
.else
|
||||
DESTDIR?= ${DOCDIR}/zh_CN.GB2312/relnotes/${.CURDIR:T}
|
||||
.endif
|
||||
@ -1,19 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/relnotes.ent
|
||||
SRCS+= ../common/new.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,22 +0,0 @@
|
||||
<!-- Original Revision: 1.4 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/relnotes.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "amd64">
|
||||
<!ENTITY arch.print "AMD64">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&art;
|
||||
</article>
|
||||
1507
release/doc/zh_CN.GB2312/relnotes/article.sgml
Normal file
1507
release/doc/zh_CN.GB2312/relnotes/article.sgml
Normal file
File diff suppressed because it is too large
Load Diff
File diff suppressed because it is too large
Load Diff
@ -1,17 +0,0 @@
|
||||
<!-- -*- sgml -*- -->
|
||||
|
||||
<!-- Original Revision: 1.3 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!-- Text constants which probably don't need to be changed.-->
|
||||
|
||||
<!-- The marker for MFCs. -->
|
||||
<!ENTITY merged "[ÒѺϲ¢]">
|
||||
|
||||
<!ENTITY % include.historic "IGNORE">
|
||||
<!ENTITY % no.include.historic "IGNORE">
|
||||
|
||||
<!-- Files to be included -->
|
||||
|
||||
<!ENTITY art SYSTEM "../common/new.sgml">
|
||||
|
||||
@ -1,21 +0,0 @@
|
||||
# Original Revision: 1.7
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/relnotes.ent
|
||||
SRCS+= ../common/new.sgml
|
||||
|
||||
URL_RELPREFIX?= ../../../..
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,22 +0,0 @@
|
||||
<!-- Original Revision: 1.7 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/relnotes.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "i386">
|
||||
<!ENTITY arch.print "i386">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&art;
|
||||
</article>
|
||||
@ -1,19 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/relnotes.ent
|
||||
SRCS+= ../common/new.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,22 +0,0 @@
|
||||
<!-- Original Revision: 1.4 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/relnotes.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "ia64">
|
||||
<!ENTITY arch.print "IA-64">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&art;
|
||||
</article>
|
||||
@ -1,19 +0,0 @@
|
||||
# Original Revision: 1.1
|
||||
# $FreeBSD$
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/relnotes.ent
|
||||
SRCS+= ../common/new.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,22 +0,0 @@
|
||||
<!-- Original Revision: 1.4 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/relnotes.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "pc98">
|
||||
<!ENTITY arch.print "NEC PC-98x1">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&art;
|
||||
</article>
|
||||
@ -1,20 +0,0 @@
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Original Revision: 1.1
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/relnotes.ent
|
||||
SRCS+= ../common/new.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,22 +0,0 @@
|
||||
<!-- Original Revision: 1.1 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/relnotes.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "powerpc">
|
||||
<!ENTITY arch.print "PowerPC">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&art;
|
||||
</article>
|
||||
@ -1,20 +0,0 @@
|
||||
# $FreeBSD$
|
||||
#
|
||||
# Original Revision: 1.1
|
||||
|
||||
RELN_ROOT?= ${.CURDIR}/../../..
|
||||
|
||||
DOC?= article
|
||||
FORMATS?= html
|
||||
INSTALL_COMPRESSED?= gz
|
||||
INSTALL_ONLY_COMPRESSED?=
|
||||
|
||||
JADEFLAGS+= -V %generate-article-toc%
|
||||
|
||||
# SGML content
|
||||
SRCS+= article.sgml
|
||||
SRCS+= ../common/relnotes.ent
|
||||
SRCS+= ../common/new.sgml
|
||||
|
||||
.include "${RELN_ROOT}/share/mk/doc.relnotes.mk"
|
||||
.include "${DOC_PREFIX}/share/mk/doc.project.mk"
|
||||
@ -1,23 +0,0 @@
|
||||
<!-- Original Revision: 1.6 -->
|
||||
<!-- $FreeBSD$ -->
|
||||
|
||||
<!DOCTYPE article PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
<!ENTITY % articles.ent PUBLIC "-//FreeBSD//ENTITIES DocBook FreeBSD Articles Entity Set//EN">
|
||||
%articles.ent;
|
||||
|
||||
<!ENTITY % release PUBLIC "-//FreeBSD//ENTITIES Release Specification//EN">
|
||||
%release;
|
||||
<!ENTITY % sections SYSTEM "../common/relnotes.ent">
|
||||
%sections;
|
||||
|
||||
<!-- Architecture-specific customization -->
|
||||
|
||||
<!ENTITY arch "sparc64">
|
||||
<!ENTITY arch.print "UltraSPARC">
|
||||
<!ENTITY release.url "ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/">
|
||||
|
||||
]>
|
||||
|
||||
<article>
|
||||
&art;
|
||||
</article>
|
||||
Loading…
Reference in New Issue
Block a user