Fix/Standardize:
internet -> Internet can not -> cannot CD-ROM -> CDROM cdrom -> CDROM UNIX -> Unix To be standardized with the rest of the doc tree. Approved by: murray
This commit is contained in:
Chern Lee
parent
005639d0fb
commit
6dbf07d805
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=9952
22 changed files with 94 additions and 94 deletions
|
|
@ -2,7 +2,7 @@
|
|||
<!ENTITY % man PUBLIC "-//FreeBSD//ENTITIES DocBook Manual Page Entities//EN">
|
||||
%man;
|
||||
]>
|
||||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/formatting-media/article.sgml,v 1.17 2001/07/11 13:05:44 nik Exp $ -->
|
||||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/formatting-media/article.sgml,v 1.18 2001/07/11 13:07:38 nik Exp $ -->
|
||||
<article>
|
||||
<articleinfo>
|
||||
<title>Formatting Media For Use With FreeBSD</title>
|
||||
|
|
@ -91,7 +91,7 @@
|
|||
<sect2>
|
||||
<title>Definitions</title>
|
||||
|
||||
<para>UNIX disk management over the centuries has invented many
|
||||
<para>Unix disk management over the centuries has invented many
|
||||
new definitions for old words. The following glossary covers
|
||||
the definitions used in this document and (hopefully) for
|
||||
FreeBSD in general.</para>
|
||||
|
|
@ -118,7 +118,7 @@ now. -->
|
|||
similarly manipulable material, spun by a motor under a
|
||||
head. Data is stored on the disk by changing the pattern
|
||||
of magnetism on the disc, which can be later read. Hard
|
||||
disks, CD-ROMs, Magneto-optical,and Zip/Jaz removables are
|
||||
disks, CDROMs, Magneto-optical,and Zip/Jaz removables are
|
||||
examples of disks.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
</affiliation>
|
||||
</author>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/freebsd-questions/article.sgml,v 1.3 2001/07/10 14:00:14 dd Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/articles/freebsd-questions/article.sgml,v 1.4 2001/07/13 16:34:19 nik Exp $</pubdate>
|
||||
|
||||
<abstract>
|
||||
<para>This document provides useful information for people looking to
|
||||
|
|
@ -401,10 +401,10 @@ so why don't y9ou guys tell me what I doing wrong.</literallayout>
|
|||
|
||||
<literallayout class="monospaced">Subject: Problems installing FreeBSD
|
||||
|
||||
I've just got the FreeBSD 2.1.5 CD-ROM from Walnut Creek, and I'm having a lot
|
||||
I've just got the FreeBSD 2.1.5 CDROM from Walnut Creek, and I'm having a lot
|
||||
of difficulty installing it. I have a 66 MHz 486 with 16 MB of
|
||||
memory and an Adaptec 1540A SCSI board, a 1.2GB Quantum Fireball
|
||||
disk and a Toshiba 3501XA CD-ROM drive. The installation works just
|
||||
disk and a Toshiba 3501XA CDROM drive. The installation works just
|
||||
fine, but when I try to reboot the system, I get the message
|
||||
``Missing Operating System''.</literallayout>
|
||||
</example>
|
||||
|
|
@ -489,7 +489,7 @@ fine, but when I try to reboot the system, I get the message
|
|||
If not, wait a day or so. If nobody else comes up with a
|
||||
better answer, you can still reply and say, for example, <quote>I
|
||||
don't know if this is correct, but since nobody else has
|
||||
replied, why don't you try replacing your ATAPI CD-ROM with
|
||||
replied, why don't you try replacing your ATAPI CDROM with
|
||||
a frog?</quote>.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
|||
|
|
@ -103,7 +103,7 @@ Expected value for L=8 is 7.1836656
|
|||
|
||||
<p>This experiment shows that IPsec <i>does</i> seem to be distributing the
|
||||
payload data <i>uniformly</i>, as encryption should. However, the
|
||||
experiment described here <i>can not </i>detect many possible flaws in a
|
||||
experiment described here <i>cannot </i>detect many possible flaws in a
|
||||
system (none of which do I have any evidence for). These include poor
|
||||
key generation or exchange, data or keys being visible to others, use of
|
||||
weak algorithms, kernel subversion, etc. Study the source; know the
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/mh/article.sgml,v 1.11 2001/07/08 19:15:05 dannyboy Exp $ -->
|
||||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/mh/article.sgml,v 1.12 2001/07/11 13:13:41 nik Exp $ -->
|
||||
<!-- FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN">
|
||||
|
|
@ -344,7 +344,7 @@ which I am probably the guilty party).</screen>
|
|||
into your <filename>inbox</filename> directory with a file name that is
|
||||
equivalent to the message number. So even if you didn't have
|
||||
any of the MH tools to read your email you could still use
|
||||
standard UNIX commands to munge around in those directories and
|
||||
standard Unix commands to munge around in those directories and
|
||||
just more your files. It's this simplicity that really gives you
|
||||
a lot of power with what you can do with your email.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/multi-os/article.sgml,v 1.16 2001/07/10 14:00:14 dd Exp $ -->
|
||||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/multi-os/article.sgml,v 1.17 2001/07/11 13:24:45 nik Exp $ -->
|
||||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN">
|
||||
<article>
|
||||
<articleinfo>
|
||||
|
|
@ -46,7 +46,7 @@
|
|||
repartition your hard drive, you run the risk of destroying the
|
||||
data on the original partitions. However, if your hard drive is
|
||||
completely occupied by DOS, you might find the FIPS utility
|
||||
(included on the FreeBSD CD-ROM in the
|
||||
(included on the FreeBSD CDROM in the
|
||||
<filename>\TOOLS</filename> directory or via <ulink
|
||||
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools">ftp</ulink>)
|
||||
useful. It lets you repartition your hard disk without
|
||||
|
|
@ -276,7 +276,7 @@ Press Esc to continue
|
|||
<quote>destroy</quote> the MBR, and you will have to reinstall your
|
||||
previous boot manager. Boot Easy can be reinstalled by using
|
||||
the BOOTINST.EXE utility included in the \TOOLS directory on the
|
||||
CD-ROM, and via <ulink
|
||||
CDROM, and via <ulink
|
||||
URL="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools">ftp</ulink>.
|
||||
You can also re-start the installation process and go to the
|
||||
partition editor. From there, mark the FreeBSD partition as
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/new-users/article.sgml,v 1.19 2001/06/23 06:56:59 dd Exp $ -->
|
||||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/new-users/article.sgml,v 1.20 2001/07/06 13:02:50 dd Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN">
|
||||
|
|
@ -787,7 +787,7 @@
|
|||
them (get the package if it exists, with <command>pkg_add
|
||||
/cdrom/packages/All/<replaceable>packagename</replaceable></command>, where
|
||||
<replaceable>packagename</replaceable> is the filename of the
|
||||
package). The cdrom has lists of the packages and ports with
|
||||
package). The CDROM has lists of the packages and ports with
|
||||
brief descriptions in <filename>cdrom/packages/index</filename>,
|
||||
<filename>cdrom/packages/index.txt</filename>, and
|
||||
<filename>cdrom/ports/index</filename>, with fuller descriptions
|
||||
|
|
@ -796,11 +796,11 @@
|
|||
programs and program names respectively.</para>
|
||||
|
||||
<para>If you find the handbook too sophisticated (what with
|
||||
<command>lndir</command> and all) on installing ports from the cdrom,
|
||||
<command>lndir</command> and all) on installing ports from the CDROM,
|
||||
here's what usually works:</para>
|
||||
|
||||
<para>Find the port you want, say <command>kermit</command>. There will
|
||||
be a directory for it on the cdrom. Copy the subdirectory to
|
||||
be a directory for it on the CDROM. Copy the subdirectory to
|
||||
<filename>/usr/local</filename> (a good place for software you
|
||||
add that should be available to all users) with:</para>
|
||||
|
||||
|
|
@ -831,7 +831,7 @@
|
|||
</informalexample>
|
||||
|
||||
<para>During this process the port will ftp to get any compressed
|
||||
files it needs that it didn't find on the cdrom or in
|
||||
files it needs that it didn't find on the CDROM or in
|
||||
<filename>/usr/ports/distfiles</filename>. If you don't have
|
||||
your network running yet and there was no file for the port in
|
||||
<filename>/cdrom/ports/distfiles</filename>, you will have to
|
||||
|
|
@ -1004,13 +1004,13 @@ setenv XNLSPATH /usr/X11R6/lib/X11/nls</programlisting>
|
|||
insert another one, and mount it with
|
||||
<command>/sbin/mount_cd9660 /dev/cd0a /cdrom</command> assuming
|
||||
<hardware>cd0a</hardware> is the device name for your CDROM drive. The
|
||||
most recent versions of FreeBSD let you mount the cdrom with
|
||||
most recent versions of FreeBSD let you mount the CDROM with
|
||||
just <command>/sbin/mount /cdrom</command>.</para>
|
||||
|
||||
<para>Using the live file system—the second of FreeBSD's
|
||||
CDROM disks—is useful if you've got limited space. What
|
||||
is on the live file system varies from release to release. You
|
||||
might try playing games from the cdrom. This involves using
|
||||
might try playing games from the CDROM. This involves using
|
||||
<command>lndir</command>, which gets installed with the X Window
|
||||
System, to tell the program(s) where to find the necessary
|
||||
files, because they're in the <filename>/cdrom</filename> file
|
||||
|
|
|
|||
|
|
@ -1,4 +1,4 @@
|
|||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/vm-design/article.sgml,v 1.4 2001/02/20 19:49:32 nik Exp $ -->
|
||||
<!-- $FreeBSD: doc/en_US.ISO8859-1/articles/vm-design/article.sgml,v 1.5 2001/07/10 13:24:13 dd Exp $ -->
|
||||
<!-- FreeBSD Documentation Project -->
|
||||
|
||||
<!DOCTYPE ARTICLE PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
|
|
@ -75,7 +75,7 @@
|
|||
problem that is easily and rapidly being addressed by the Linux
|
||||
community in the same way it has been addressed in the BSD
|
||||
community—by continuous code development. The NT folk, on the
|
||||
other hand, repeatedly make the same mistakes solved by UNIX decades ago
|
||||
other hand, repeatedly make the same mistakes solved by Unix decades ago
|
||||
and then spend years fixing them. Over and over again. They have a
|
||||
severe case of ‘not designed here’ and ‘we are always
|
||||
right because our marketing department says so’. I have little
|
||||
|
|
@ -793,7 +793,7 @@
|
|||
This allows the cache to be left alone across a process context
|
||||
switch, which is very important.</para>
|
||||
|
||||
<para>But in the UNIX world you are dealing with virtual address
|
||||
<para>But in the Unix world you are dealing with virtual address
|
||||
spaces, not physical address spaces. Any program you write will
|
||||
see the virtual address space given to it. The actual
|
||||
<emphasis>physical</emphasis> pages underlying that virtual
|
||||
|
|
|
|||
|
|
@ -112,7 +112,7 @@
|
|||
|
||||
<para>IDE devices in FreeBSD are prefixed with a <literal>w</literal>.
|
||||
For example, an IDE hard disk might be
|
||||
<filename>/dev/wd0</filename>, an IDE (ATAPI) cdrom might be
|
||||
<filename>/dev/wd0</filename>, an IDE (ATAPI) CDROM might be
|
||||
<filename>/dev/wcd1</filename>, and so on.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD$
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/isa/chapter.sgml,v 1.1 2001/05/02 01:56:01 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="isa-driver">
|
||||
|
|
@ -1711,7 +1711,7 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
As for any other bus, if the device can not be detected or
|
||||
As for any other bus, if the device cannot be detected or
|
||||
is detected but failed the self-test or some other problem
|
||||
happened then it returns a positive value of error. The
|
||||
value ENXIO must be returned if the device is not
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/scsi/chapter.sgml,v 1.3 2001/04/13 08:09:03 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/scsi/chapter.sgml,v 1.4 2001/06/13 11:35:56 tom Exp $
|
||||
-->
|
||||
|
||||
<chapter id="scsi">
|
||||
|
|
@ -1865,7 +1865,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
|
|||
<itemizedlist>
|
||||
|
||||
<listitem><para><emphasis>CAM_RESRC_UNAVAIL</emphasis> - some
|
||||
resource is temporarily unavailable and the SIM driver can not
|
||||
resource is temporarily unavailable and the SIM driver cannot
|
||||
generate an event when it will become available. An example of
|
||||
this resource would be some intra-controller hardware resource
|
||||
for which the controller does not generate an interrupt when
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml,v 1.1 2001/05/14 02:52:43 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/ipv6/chapter.sgml,v 1.2 2001/07/06 13:02:53 dd Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ipv6">
|
||||
|
|
@ -788,7 +788,7 @@ fe80:2::%ep0/64 link#2 UC ep0</screen>
|
|||
<title>Applications</title>
|
||||
|
||||
<para>For userland programming, we support IPv6 socket API as
|
||||
specified in RFC2553, RFC2292 and upcoming internet drafts.</para>
|
||||
specified in RFC2553, RFC2292 and upcoming Internet drafts.</para>
|
||||
|
||||
<para>TCP/UDP over IPv6 is available and quite stable. You can
|
||||
enjoy &man.telnet.1;, &man.ftp.1;, &man.rlogin.1;, &man.rsh.1;,
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD$
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/isa/chapter.sgml,v 1.1 2001/05/02 01:56:01 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="isa-driver">
|
||||
|
|
@ -1711,7 +1711,7 @@
|
|||
</para>
|
||||
|
||||
<para>
|
||||
As for any other bus, if the device can not be detected or
|
||||
As for any other bus, if the device cannot be detected or
|
||||
is detected but failed the self-test or some other problem
|
||||
happened then it returns a positive value of error. The
|
||||
value ENXIO must be returned if the device is not
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/scsi/chapter.sgml,v 1.3 2001/04/13 08:09:03 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/scsi/chapter.sgml,v 1.4 2001/06/13 11:35:56 tom Exp $
|
||||
-->
|
||||
|
||||
<chapter id="scsi">
|
||||
|
|
@ -1865,7 +1865,7 @@ ahc_async(void *callback_arg, u_int32_t code, struct cam_path *path, void *arg)<
|
|||
<itemizedlist>
|
||||
|
||||
<listitem><para><emphasis>CAM_RESRC_UNAVAIL</emphasis> - some
|
||||
resource is temporarily unavailable and the SIM driver can not
|
||||
resource is temporarily unavailable and the SIM driver cannot
|
||||
generate an event when it will become available. An example of
|
||||
this resource would be some intra-controller hardware resource
|
||||
for which the controller does not generate an interrupt when
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml,v 1.8 2001/06/13 11:36:07 tom Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/developers-handbook/secure/chapter.sgml,v 1.9 2001/06/13 18:18:58 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="secure">
|
||||
|
|
@ -426,7 +426,7 @@ int main() {
|
|||
running applications in a secure environment but it does have
|
||||
some shortcomings. Currently, the IPC mechanisms have not been
|
||||
converted to the <function>suser_xxx</function> so applications
|
||||
such as MySQL can not be run within a jail. Superuser access
|
||||
such as MySQL cannot be run within a jail. Superuser access
|
||||
may have a very limited meaning within a jail, but there is
|
||||
no way to specify exactly what "very limited" means.</para>
|
||||
</sect2>
|
||||
|
|
|
|||
|
|
@ -17,7 +17,7 @@
|
|||
|
||||
<corpauthor>The FreeBSD Documentation Project</corpauthor>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.243 2001/07/06 13:02:56 dd Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/faq/book.sgml,v 1.244 2001/07/10 14:39:25 nik Exp $</pubdate>
|
||||
|
||||
<copyright>
|
||||
<year>1995</year>
|
||||
|
|
@ -1122,7 +1122,7 @@ File: +DESC (ignored)</screen>
|
|||
2.2, need at least 5MB to install on a new system.</para>
|
||||
|
||||
<para>All versions of FreeBSD, including 3.0, will
|
||||
<emphasis>run</emphasis> in 4MB of RAM, they just can not run the
|
||||
<emphasis>run</emphasis> in 4MB of RAM, they just cannot run the
|
||||
installation program in 4MB. You can add extra memory for the
|
||||
install process, if you like, and then after the system is up
|
||||
and running, go back to 4MB. Or you could always just swap your
|
||||
|
|
@ -1232,9 +1232,9 @@ File: +DESC (ignored)</screen>
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Boot the FreeBSD boot floppy (or CD-ROM) and choose the
|
||||
<para>Boot the FreeBSD boot floppy (or CDROM) and choose the
|
||||
<quote>Fixit</quote> menu item. Select either the Fixit
|
||||
floppy or CD-ROM #2 (the <quote>live</quote> file system
|
||||
floppy or CDROM #2 (the <quote>live</quote> file system
|
||||
option) as appropriate and enter the fixit shell. Then
|
||||
execute the following command:</para>
|
||||
|
||||
|
|
@ -1468,21 +1468,21 @@ File: +DESC (ignored)</screen>
|
|||
|
||||
<qandaentry>
|
||||
<question id="no-install-cdrom">
|
||||
<para>I booted from my ATAPI CD-ROM, but the install program says no
|
||||
CD-ROM is found. Where did it go?</para>
|
||||
<para>I booted from my ATAPI CDROM, but the install program says no
|
||||
CDROM is found. Where did it go?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>The usual cause of this problem is a mis-configured CD-ROM
|
||||
drive. Many PCs now ship with the CD-ROM as the slave device on
|
||||
<para>The usual cause of this problem is a mis-configured CDROM
|
||||
drive. Many PCs now ship with the CDROM as the slave device on
|
||||
the secondary IDE controller, with no master device on that
|
||||
controller. This is illegal according to the ATAPI specification,
|
||||
but Windows plays fast and loose with the specification, and the
|
||||
BIOS ignores it when booting. This is why the BIOS was able to
|
||||
see the CD-ROM to boot from it, but why FreeBSD can not see it to
|
||||
see the CDROM to boot from it, but why FreeBSD cannot see it to
|
||||
complete the install.</para>
|
||||
|
||||
<para>Reconfigure your system so that the CD-ROM is either the
|
||||
<para>Reconfigure your system so that the CDROM is either the
|
||||
master device on the IDE controller it is attached to, or make
|
||||
sure that it is the slave on an IDE controller that also has a
|
||||
master device.</para>
|
||||
|
|
@ -1839,7 +1839,7 @@ BUSY</literallayout></entry>
|
|||
<answer>
|
||||
<para>The default password format on FreeBSD is to use
|
||||
<emphasis>MD5</emphasis>-based passwords. These are believed to
|
||||
be more secure than the traditional UNIX password format, which
|
||||
be more secure than the traditional Unix password format, which
|
||||
used a scheme based on the <emphasis>DES</emphasis> algorithm.
|
||||
DES passwords are still available if you need to share your
|
||||
password file with legacy operating systems which still use the
|
||||
|
|
@ -2387,14 +2387,14 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
|
|||
|
||||
<qandaentry>
|
||||
<question id="supported-cdrom-drives">
|
||||
<para>Which CD-ROM drives are supported by FreeBSD?</para>
|
||||
<para>Which CDROM drives are supported by FreeBSD?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>Any SCSI drive connected to a supported controller is
|
||||
supported.</para>
|
||||
|
||||
<para>The following proprietary CD-ROM interfaces are also
|
||||
<para>The following proprietary CDROM interfaces are also
|
||||
supported:</para>
|
||||
|
||||
<itemizedlist>
|
||||
|
|
@ -2408,15 +2408,15 @@ Filesystem 1024-blocks Used Avail Capacity Mounted on
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Sound Blaster Non-SCSI CD-ROM</para>
|
||||
<para>Sound Blaster Non-SCSI CDROM</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Matsushita/Panasonic CD-ROM</para>
|
||||
<para>Matsushita/Panasonic CDROM</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>ATAPI compatible IDE CD-ROMs</para>
|
||||
<para>ATAPI compatible IDE CDROMs</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
|
|
@ -3008,7 +3008,7 @@ diff -u -r1.60.2.1 -r1.60.2.2
|
|||
|
||||
<note>
|
||||
<para>This is only for sound! This driver does not support
|
||||
CD-ROMs, SCSI or joysticks on these cards, except for the
|
||||
CDROMs, SCSI or joysticks on these cards, except for the
|
||||
SoundBlaster. The SoundBlaster SCSI interface and some
|
||||
non-SCSI CDROMS are supported, but you cannot boot off this
|
||||
device.</para>
|
||||
|
|
@ -3434,7 +3434,7 @@ quit</programlisting>
|
|||
this problem.</para>
|
||||
|
||||
<note>
|
||||
<para>You can not use a
|
||||
<para>You cannot use a
|
||||
<literal>dangerously dedicated</literal> disk
|
||||
with an HP Netserver. See <link linkend="dedicate">this
|
||||
note</link> for more info.</para>
|
||||
|
|
@ -3536,8 +3536,8 @@ quit</programlisting>
|
|||
(ATAPI). It can take a couple of seconds for a CDROM drive to
|
||||
notice that it has been fed, so be patient.</para>
|
||||
|
||||
<para>Sometimes a SCSI CD-ROM may be missed because it had not
|
||||
enough time to answer the bus reset. If you have a SCSI CD-ROM
|
||||
<para>Sometimes a SCSI CDROM may be missed because it had not
|
||||
enough time to answer the bus reset. If you have a SCSI CDROM
|
||||
please try to add the following symbol into your kernel
|
||||
configuration file and recompile.</para>
|
||||
|
||||
|
|
@ -6220,7 +6220,7 @@ options SYSVMSG # enable for messaging</programlisting>
|
|||
<para>If you did not install your system with full sources,
|
||||
the sendmail config stuff has been broken out into a separate
|
||||
source distribution tarball just for you. Assuming you have got
|
||||
your CD-ROM mounted, do:</para>
|
||||
your CDROM mounted, do:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /cdrom/src</userinput>
|
||||
&prompt.root; <userinput>cat scontrib.?? | tar xzf - -C /usr/src contrib/sendmail</userinput></screen>
|
||||
|
|
@ -6348,12 +6348,12 @@ rewrite: ruleset 0 returns: $# uucp-dom $@ if-bus $: foo \
|
|||
<answer>
|
||||
<para>If you have got a statically assigned IP number, you should
|
||||
not need to adjust anything from the default. Set your host
|
||||
name up as your assigned internet name and sendmail will do
|
||||
name up as your assigned Internet name and sendmail will do
|
||||
the rest.</para>
|
||||
|
||||
<para>If you have got a dynamically assigned IP number and use a
|
||||
dialup <application>ppp</application> connection to the
|
||||
internet, you will probably be given a mailbox on your ISPs
|
||||
Internet, you will probably be given a mailbox on your ISPs
|
||||
mail server. Lets assume your ISPs domain is
|
||||
<hostid role="domainname">myISP.com</hostid>, and that your user name is
|
||||
<username>user</username>. Lets also assume you have
|
||||
|
|
@ -6516,7 +6516,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
|
|||
|
||||
<qandaentry>
|
||||
<question id="dos-to-unix-txt">
|
||||
<para>How do I reformat DOS text files to UNIX ones?</para>
|
||||
<para>How do I reformat DOS text files to Unix ones?</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
|
|
@ -6742,16 +6742,16 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
|
||||
<para>UNIX implements two core sandboxes. One is at the
|
||||
<para>Unix implements two core sandboxes. One is at the
|
||||
process level, and one is at the userid level.</para>
|
||||
|
||||
<para>Every UNIX process is completely firewalled off from every
|
||||
other UNIX process. One process can not modify the address
|
||||
<para>Every Unix process is completely firewalled off from every
|
||||
other Unix process. One process cannot modify the address
|
||||
space of another. This is unlike Windows where a process
|
||||
can easily overwrite the address space of any other, leading
|
||||
to a crash.</para>
|
||||
|
||||
<para>A UNIX process is owned by a particular userid. If the
|
||||
<para>A Unix process is owned by a particular userid. If the
|
||||
userid is not the <username>root</username> user, it serves to firewall the process
|
||||
off from processes owned by other users. The userid is also
|
||||
used to firewall off on-disk data.</para>
|
||||
|
|
@ -6880,7 +6880,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
|
|||
<screen>&prompt.root; <userinput>chmod 666 /dev/fd0</userinput></screen>
|
||||
|
||||
<para>To allow users in the group
|
||||
<groupname>operator</groupname> to mount the cdrom drive,
|
||||
<groupname>operator</groupname> to mount the CDROM drive,
|
||||
use:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>chgrp operator /dev/cd0c</userinput>
|
||||
|
|
@ -6903,7 +6903,7 @@ define(`confDELIVERY_MODE',`deferred')dnl</programlisting>
|
|||
&prompt.user; <userinput>mount -t msdos /dev/fd0 ~/my-mount-point</userinput></screen>
|
||||
|
||||
<para>Users in group <groupname>operator</groupname> can now
|
||||
mount the cdrom <devicename>/dev/cd0c</devicename> onto a
|
||||
mount the CDROM <devicename>/dev/cd0c</devicename> onto a
|
||||
directory that they own:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>mkdir ~/my-mount-point</userinput>
|
||||
|
|
@ -8233,7 +8233,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
|
|||
Internet provider (or even if you receive a dynamic IP number),
|
||||
you may want to look at the &man.natd.8;
|
||||
program. &man.natd.8; allows you to connect an
|
||||
entire subnet to the internet using only a single IP
|
||||
entire subnet to the Internet using only a single IP
|
||||
number.</para>
|
||||
|
||||
<para>The &man.ppp.8;
|
||||
|
|
@ -10673,7 +10673,7 @@ raisechar=^^</programlisting>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>If you are talking to another UNIX system, you can send
|
||||
<para>If you are talking to another Unix system, you can send
|
||||
and receive files with <literal>~p</literal> (put) and
|
||||
<literal>~t</literal> (take). These commands run
|
||||
&man.cat.1; and
|
||||
|
|
@ -10789,7 +10789,7 @@ raisechar=^^</programlisting>
|
|||
<para>To understand why FreeBSD uses the
|
||||
<filename>ELF</filename> format, you must first know a little
|
||||
about the 3 currently <quote>dominant</quote> executable
|
||||
formats for UNIX:</para>
|
||||
formats for Unix:</para>
|
||||
|
||||
<note>
|
||||
<para>Prior to FreeBSD 3.x, FreeBSD used the a.out
|
||||
|
|
@ -11026,7 +11026,7 @@ raisechar=^^</programlisting>
|
|||
which are trashed (due to variable-length records getting
|
||||
written when fixed records were expected), but it can break
|
||||
Suns NIS clients and potentially cause other problems in
|
||||
interacting with other UNIX systems.</para>
|
||||
interacting with other Unix systems.</para>
|
||||
|
||||
<para>In FreeBSD 3.0 and later, the maximum name length has
|
||||
been increased to 16 characters and those various utilities
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@
|
|||
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml,v 1.25 2001/07/13 20:49:09 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-markup/chapter.sgml,v 1.26 2001/07/15 11:17:05 nik Exp $
|
||||
-->
|
||||
|
||||
<chapter id="sgml-markup">
|
||||
|
|
@ -2115,7 +2115,7 @@ This is the file called 'foo2'</screen>
|
|||
|
||||
<para>There will often be times when you want to show the user what to
|
||||
do, or refer to a file, or command line, or similar, where the user
|
||||
can not simply copy the examples that you provide, but must instead
|
||||
cannot simply copy the examples that you provide, but must instead
|
||||
include some information themselves.</para>
|
||||
|
||||
<para><sgmltag>replaceable</sgmltag> is designed for this eventuality.
|
||||
|
|
@ -2503,11 +2503,11 @@ IMAGES= chapter1/fig1.png
|
|||
title or the chapter number.</para>
|
||||
|
||||
<note>
|
||||
<para>This means that you <emphasis>can not</emphasis> use
|
||||
<para>This means that you <emphasis>cannot</emphasis> use
|
||||
<sgmltag>xref</sgmltag> to link to an <literal>id</literal>
|
||||
attribute on an <sgmltag>anchor</sgmltag> element. The
|
||||
<sgmltag>anchor</sgmltag> has no content, so the
|
||||
<sgmltag>xref</sgmltag> can not generate the text for the
|
||||
<sgmltag>xref</sgmltag> cannot generate the text for the
|
||||
link.</para>
|
||||
</note>
|
||||
|
||||
|
|
|
|||
|
|
@ -27,7 +27,7 @@
|
|||
ANY WAY OUT OF THE USE OF THIS DOCUMENTATION, EVEN IF ADVISED OF THE
|
||||
POSSIBILITY OF SUCH DAMAGE.
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml,v 1.17 2001/04/17 16:16:19 nik Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/fdp-primer/sgml-primer/chapter.sgml,v 1.18 2001/07/13 20:49:35 nik Exp $
|
||||
-->
|
||||
|
||||
<chapter id="sgml-primer">
|
||||
|
|
@ -76,7 +76,7 @@
|
|||
|
||||
and easily see which parts are filenames, which are commands to be typed
|
||||
in, which parts are references to manual pages, and so on. But the
|
||||
computer processing the document can not. For this we need
|
||||
computer processing the document cannot. For this we need
|
||||
markup.</para>
|
||||
|
||||
<para>“Markup” is commonly used to describe “adding
|
||||
|
|
@ -909,7 +909,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
|
|||
<sect2 id="sgml-primer-general-entities">
|
||||
<title>General Entities</title>
|
||||
|
||||
<para>You can not use general entities in an SGML context (although you
|
||||
<para>You cannot use general entities in an SGML context (although you
|
||||
define them in one). They can only be used in your document.
|
||||
Contrast this with <link
|
||||
linkend="sgml-primer-parameter-entities">parameter
|
||||
|
|
@ -932,7 +932,7 @@ nsgmls:example.sgml:6:8:E: end tag for "HEAD" which is not finished</screen>
|
|||
|
||||
<para>You can also use general entities to enter characters that you
|
||||
could not otherwise include in an SGML document. For example, <
|
||||
and & can not normally appear in an SGML document. When the SGML
|
||||
and & cannot normally appear in an SGML document. When the SGML
|
||||
parser sees the < symbol it assumes that a tag (either a start tag
|
||||
or an end tag) is about to appear, and when it sees the & symbol
|
||||
it assumes the next text will be the name of an entity.</para>
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.56 2001/07/14 23:40:27 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.57 2001/07/17 00:11:17 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="advanced-networking">
|
||||
|
|
@ -11,7 +11,7 @@
|
|||
<title>Synopsis</title>
|
||||
|
||||
<para>The following chapter will cover some of the more frequently
|
||||
used network services on UNIX systems. This, of course, will
|
||||
used network services on Unix systems. This, of course, will
|
||||
pertain to configuring said services on your FreeBSD system.</para>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -3095,7 +3095,7 @@ dhcp_flags=""</programlisting>
|
|||
<sect3>
|
||||
<title><filename>/etc/namedb/named.conf</filename></title>
|
||||
|
||||
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.56 2001/07/14 23:40:27 murray Exp $
|
||||
<programlisting>// $FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.57 2001/07/17 00:11:17 chern Exp $
|
||||
//
|
||||
// Refer to the named(8) man page for details. If you are ever going
|
||||
// to setup a primary server, make sure you've understood the hairy
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.12 2001/06/29 18:31:16 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.13 2001/07/06 13:03:00 dd Exp $
|
||||
-->
|
||||
|
||||
<chapter id="boot">
|
||||
|
|
@ -467,7 +467,7 @@ boot:</screen>
|
|||
|
||||
<para>The automatic reboot sequence makes sure that the
|
||||
filesystems available on the system are consistent. If they
|
||||
are not, and <command>fsck</command> can not fix the
|
||||
are not, and <command>fsck</command> cannot fix the
|
||||
inconsistencies, <command>init</command> drops the system
|
||||
into <link linkend="boot-singleuser">single-user mode</link>
|
||||
for the system administrator to take care of the problems
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v 1.30 2001/07/17 00:11:24 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v 1.31 2001/07/17 01:22:35 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="x11">
|
||||
|
|
@ -1615,7 +1615,7 @@ EndSection</programlisting>
|
|||
<para>You should now make a directory for your TrueType fonts
|
||||
(e.g. <filename>/usr/X11R6/lib/X11/fonts/TrueType</filename>)
|
||||
and copy all of your TrueType fonts into this directory. Keep in
|
||||
mind that you can not take TrueType fonts directly from a
|
||||
mind that you cannot take TrueType fonts directly from a
|
||||
Macintosh; they must be in Unix/DOS/Windows format for use by
|
||||
<application>XFree86</application>. Once you have copied the
|
||||
files into this directory you need to use
|
||||
|
|
|
|||
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.156 2001/07/13 07:33:25 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/porters-handbook/book.sgml,v 1.157 2001/07/14 20:56:36 tobez Exp $
|
||||
-->
|
||||
|
||||
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
|
||||
|
|
@ -628,7 +628,7 @@ lib/X11/oneko/mouse.xpm
|
|||
answers to the questions, you check the
|
||||
<makevar>PACKAGE_BUILDING</makevar> variable and turn off the
|
||||
interactive script when it is set. This will allow us to build the
|
||||
packages for CD-ROMs and ftp.</para>
|
||||
packages for CDROMs and ftp.</para>
|
||||
</sect1>
|
||||
</chapter>
|
||||
|
||||
|
|
@ -953,7 +953,7 @@ PORTEPOCH= 1</programlisting>
|
|||
subdirectories are specified by the variable
|
||||
<makevar>CATEGORIES</makevar>. It is intended to make life easier
|
||||
for the user when he is wading through the pile of packages on the
|
||||
ftp site or the CD-ROM. Please take a look at the existing <link
|
||||
ftp site or the CDROM. Please take a look at the existing <link
|
||||
linkend="porting-categories">categories</link> and pick the ones
|
||||
that are suitable for your port.</para>
|
||||
|
||||
|
|
@ -2267,7 +2267,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
|
|||
<para>It is your responsibility as a porter to read the licensing
|
||||
terms of the software and make sure that the FreeBSD project will
|
||||
not be held accountable for violating them by redistributing the
|
||||
source or compiled binaries either via ftp or CD-ROM. If in doubt,
|
||||
source or compiled binaries either via ftp or CDROM. If in doubt,
|
||||
please contact the &a.ports;.</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -2279,7 +2279,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
|
|||
<para>If the port has a “do not sell for profit” type of
|
||||
license, set the variable <makevar>NO_CDROM</makevar> to a string
|
||||
describing the reason why. We will make sure such ports will not go
|
||||
into the CD-ROM come release time. The distfile and package will
|
||||
into the CDROM come release time. The distfile and package will
|
||||
still be available via ftp.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -2288,7 +2288,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
|
|||
site, or the resulting binary package cannot be distributed due to
|
||||
licensing; set the variable <makevar>NO_PACKAGE</makevar> to a
|
||||
string describing the reason why. We will make sure such packages
|
||||
will not go on the ftp site, nor into the CD-ROM come release time.
|
||||
will not go on the ftp site, nor into the CDROM come release time.
|
||||
The distfile will still be included on both however.</para>
|
||||
</listitem>
|
||||
|
||||
|
|
@ -2445,7 +2445,7 @@ PLIST_SUB= OCTAVE_VERSION=${OCTAVE_VERSION}</programlisting>
|
|||
<title>Differentiating operating systems and OS versions</title>
|
||||
|
||||
<para>You may come across code that needs modifications or conditional
|
||||
compilation based upon what version of UNIX it is running under. If
|
||||
compilation based upon what version of Unix it is running under. If
|
||||
you need to make such changes to the code for conditional
|
||||
compilation, make sure you make the changes as general as possible
|
||||
so that we can back-port code to FreeBSD 1.x systems and cross-port
|
||||
|
|
|
|||
|
|
@ -18,7 +18,7 @@
|
|||
</author>
|
||||
</authorgroup>
|
||||
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/ppp-primer/book.sgml,v 1.9 2001/04/17 01:39:30 dd Exp $</pubdate>
|
||||
<pubdate>$FreeBSD: doc/en_US.ISO8859-1/books/ppp-primer/book.sgml,v 1.10 2001/04/17 15:58:38 nik Exp $</pubdate>
|
||||
|
||||
<abstract><para>This is a step-by-step guide for configuring FreeBSD systems to act as
|
||||
a dial-up router/gateway in a Local Area Environment. All entries may
|
||||
|
|
@ -578,7 +578,7 @@ changes" when prompted.</para>
|
|||
<title>Testing the FreeBSD system</title>
|
||||
|
||||
<para>Congratulations! Once you've made it to this point, the FreeBSD
|
||||
system is configured as a network-connected UNIX system! If you made
|
||||
system is configured as a network-connected Unix system! If you made
|
||||
any changes to the <filename>/etc/rc.conf</filename> file you should probably
|
||||
re-boot your FreeBSD system. This will accomplish two important
|
||||
objectives:
|
||||
|
|
|
|||
Loading…
Reference in a new issue