os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

*.sgml:

Browse source 
- Use trademark entities.
 - Add trademark attributions.
 - Always use correct case for trademarks.
 - Don't join trademarks with other words, e.g. using hyphens.
 - Use 'UNIX like systems' instead of 'UNIX systems'.

trademark.ent:
 - Add entities for more trademarks / companies.
This commit is contained in:
Simon L. B. Nielsen 2003-08-23 23:26:44 +00:00
parent 3b26814443
commit 4cfd05d16f
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17963
10 changed files with 217 additions and 182 deletions
en_US.ISO8859-1/books/handbook
book.sgml
boot
chapter.sgml
config
chapter.sgml
disks
chapter.sgml
kernelconfig
chapter.sgml
printing
chapter.sgml
security
chapter.sgml
users
chapter.sgml
x11
chapter.sgml
share/sgml
trademarks.ent

6
en_US.ISO8859-1/books/handbook/book.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/book.sgml,v 1.137 2003/08/20 22:38:02 simon Exp $
-->
<!DOCTYPE BOOK PUBLIC "-//FreeBSD//DTD DocBook V4.1-Based Extension//EN" [
@ -84,6 +84,8 @@
<legalnotice id="trademarks" role="trademarks">
&tm-attrib.freebsd;
&tm-attrib.3com;
&tm-attrib.3ware;
&tm-attrib.adaptec;
&tm-attrib.adobe;
&tm-attrib.apple;
&tm-attrib.corel;
@ -93,6 +95,8 @@
&tm-attrib.intel;
&tm-attrib.intuit;
&tm-attrib.linux;
&tm-attrib.lsilogic;
&tm-attrib.m-systems;
&tm-attrib.macromedia;
&tm-attrib.microsoft;
&tm-attrib.netscape;

4
en_US.ISO8859-1/books/handbook/boot/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.54 2003/07/13 18:01:24 ceri Exp $
-->
<chapter id="boot">
@ -147,7 +147,7 @@ F5 Drive 1
Default: F2</screen>
</example>
<para>Other operating systems, in particular Windows&nbsp;95, have been known
<para>Other operating systems, in particular &windows;&nbsp;95, have been known
to overwrite an existing MBR with their own. If this happens to you,
or you want to replace your existing MBR with the FreeBSD MBR then use
the following command:</para>

4
en_US.ISO8859-1/books/handbook/config/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.119 2003/08/23 11:55:25 mheinen Exp $
-->
<chapter id="config-tuning">
@ -79,7 +79,7 @@
<itemizedlist>
<listitem>
<para>Understand Unix and FreeBSD basics (<xref
<para>Understand &unix; and FreeBSD basics (<xref
linkend="basics">).</para>
</listitem>
<listitem>

40
en_US.ISO8859-1/books/handbook/disks/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.183 2003/08/15 21:50:10 simon Exp $
-->
<chapter id="disks">
@ -113,16 +113,16 @@
</row>
<row>
<entry>Flash drives</entry>
<entry><literal>fla</literal> for DiskOnChip Flash device</entry>
<entry><literal>fla</literal> for &diskonchip; Flash device</entry>
</row>
<row>
<entry>RAID drives</entry>
<entry><literal>aacd</literal> for Adaptec AdvancedRAID,
<entry><literal>aacd</literal> for &adaptec; AdvancedRAID,
<literal>mlxd</literal> and <literal>mlyd</literal>
for Mylex,
<literal>amrd</literal> for AMI MegaRAID,
for &mylex;,
<literal>amrd</literal> for AMI &megaraid;,
<literal>idad</literal> for Compaq Smart RAID,
<literal>twed</literal> for 3Ware RAID.</entry>
<literal>twed</literal> for &tm.3ware; RAID.</entry>
</row>
</tbody>
</tgroup>
@ -311,7 +311,7 @@
<para>If you will not be sharing the new drive with another operating
system, you may use the <literal>dedicated</literal> mode. Remember
this mode can confuse Microsoft operating systems; however, no damage
will be done by them. IBM's OS/2 however, will
will be done by them. IBM's &os2; however, will
<quote>appropriate</quote> any partition it finds which it does not
understand.</para>
@ -815,7 +815,7 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed</screen>
<title>mkisofs</title>
<para><filename role="package">sysutils/mkisofs</filename> produces an ISO 9660 file system
that is an image of a directory tree in the Unix file system name
that is an image of a directory tree in the &unix; file system name
space. The simplest usage is:</para>
<screen>&prompt.root; <userinput>mkisofs -o <replaceable>imagefile.iso</replaceable> <replaceable>/path/to/tree</replaceable></userinput></screen>
@ -841,10 +841,10 @@ ar0: ATA RAID1 subdisks: ad4 ad6 status: REBUILDING 0% completed</screen>
</indexterm>
<para>A number of options are available to overcome those
restrictions. In particular, <option>-R</option> enables the
Rock Ridge extensions common to Unix systems, <option>-J</option>
Rock Ridge extensions common to &unix; systems, <option>-J</option>
enables Joliet extensions used by Microsoft systems, and
<option>-hfs</option> can be used to create HFS file systems used
by MacOS.</para>
by &macos;.</para>
<para>For CDs that are going to be used only on FreeBSD systems,
<option>-U</option> can be used to disable all filename
@ -1733,7 +1733,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<indexterm><primary><command>dump</command></primary></indexterm>
<indexterm><primary><command>restore</command></primary></indexterm>
<para>The traditional Unix backup programs are
<para>The traditional &unix; backup programs are
<command>dump</command> and <command>restore</command>. They
operate on the drive as a collection of disk blocks, below the
abstractions of files, links and directories that are created by
@ -1751,7 +1751,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
symbolic links into those file systems.</para></note>
<para><command>dump</command> has quirks that remain from its early days in
Version 6 of AT&amp;T Unix (circa 1975). The default
Version 6 of AT&amp;T UNIX (circa 1975). The default
parameters are suitable for 9-track tapes (6250 bpi), not the
high-density media available today (up to 62,182 ftpi). These
defaults must be overridden on the command line to utilize the
@ -1796,7 +1796,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<secondary><command>tar</command></secondary>
</indexterm>
<para>&man.tar.1; also dates back to Version 6 of AT&amp;T Unix
<para>&man.tar.1; also dates back to Version 6 of AT&amp;T UNIX
(circa 1975). <command>tar</command> operates in cooperation
with the file system; <command>tar</command> writes files and
directories to tape. <command>tar</command> does not support the
@ -1833,7 +1833,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<secondary><command>cpio</command></secondary>
</indexterm>
<para>&man.cpio.1; is the original Unix file interchange tape
<para>&man.cpio.1; is the original &unix; file interchange tape
program for magnetic media. <command>cpio</command> has options
(among many others) to perform byte-swapping, write a number of
different archive formats, and pipe the data to other programs.
@ -1870,11 +1870,11 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<indexterm><primary>POSIX</primary></indexterm>
<indexterm><primary>IEEE</primary></indexterm>
<para>&man.pax.1; is IEEE/POSIX's answer to
<para>&man.pax.1; is IEEE/&posix;'s answer to
<command>tar</command> and <command>cpio</command>. Over the
years the various versions of <command>tar</command> and
<command>cpio</command> have gotten slightly incompatible. So
rather than fight it out to fully standardize them, POSIX
rather than fight it out to fully standardize them, &posix;
created a new archive utility. <command>pax</command> attempts
to read and write many of the various <command>cpio</command>
and <command>tar</command> formats, plus new formats of its own.
@ -1924,16 +1924,16 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>If your time and your data is worth little to nothing, then
<quote>Do nothing</quote> is the most suitable backup program for your
computer. But beware, Unix is a useful tool, you may find that within
computer. But beware, &unix; is a useful tool, you may find that within
six months you have a collection of files that are valuable to
you.</para>
<para><quote>Do nothing</quote> is the correct backup method for
<filename>/usr/obj</filename> and other directory trees that can be
exactly recreated by your computer. An example is the files that
comprise the HTML or PostScript version of this Handbook.
comprise the HTML or &postscript; version of this Handbook.
These document formats have been created from SGML input
files. Creating backups of the HTML or PostScript files is
files. Creating backups of the HTML or &postscript; files is
not necessary. The SGML files are backed up regularly.</para>
</sect2>
@ -1945,7 +1945,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
<para>&man.dump.8; <emphasis>Period.</emphasis> Elizabeth D. Zwicky
torture tested all the backup programs discussed here. The clear
choice for preserving all your data and all the peculiarities of Unix
choice for preserving all your data and all the peculiarities of &unix;
file systems is <command>dump</command>. Elizabeth created file systems containing
a large variety of unusual conditions (and some not so unusual ones)
and tested each program by doing a backup and restore of those

20
en_US.ISO8859-1/books/handbook/kernelconfig/chapter.sgml
View file

@ -98,7 +98,7 @@
dynamic loadable kernel module for that functionality yet.</para>
<para>Building a custom kernel is one of the most important rites of
passage nearly every Unix user must endure. This process, while
passage nearly every &unix; user must endure. This process, while
time consuming, will provide many benefits to your &os; system.
Unlike the <filename>GENERIC</filename> kernel, which must support a
wide range of hardware, a custom kernel only contains support for
@ -232,7 +232,7 @@
<filename>GENERIC</filename>.</para>
<indexterm><primary>SunOS</primary></indexterm>
<para>If you have built a kernel under SunOS or some other BSD
<para>If you have built a kernel under &sunos; or some other BSD
operating system, much of this file will be very familiar to you.
If you are coming from some other operating system such as DOS, on
the other hand, the <filename>GENERIC</filename> configuration file
@ -652,7 +652,7 @@ pseudo-device loop # Network loopback</programlisting>
<para>This line allows the kernel to simulate a math co-processor if
your computer does not have one (386 or 486SX). If you have a
486DX, or a 386 or 486SX (with a separate 387 or 487 chip), or
higher (Pentium, Pentium&nbsp;II, etc.), you can comment this line
higher (&pentium;, &pentium;&nbsp;II, etc.), you can comment this line
out.</para>
<note>
@ -755,7 +755,7 @@ options MD_ROOT #MD is a potential root device</programlisting>
options NFS_ROOT #NFS usable as root device, NFS required</programlisting>
<para>The network Filesystem. Unless you plan to mount partitions
from a Unix file server over TCP/IP, you can comment these
from a &unix; file server over TCP/IP, you can comment these
out.</para>
<indexterm>
@ -764,7 +764,7 @@ options NFS_ROOT #NFS usable as root device, NFS required</programl
</indexterm>
<programlisting>options MSDOSFS #MSDOS Filesystem</programlisting>
<para>The MS-DOS Filesystem. Unless you plan to mount a DOS formatted
<para>The &ms-dos; Filesystem. Unless you plan to mount a DOS formatted
hard drive partition at boot time, you can safely comment this out.
It will be automatically loaded the first time you mount a DOS
partition, as described above. Also, the excellent
@ -806,12 +806,12 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 required</programli
<programlisting>options COMPAT_FREEBSD4 #Compatible with &os;4</programlisting>
<para>This option is required on &os; 5.0 i386 and alpha systems
<para>This option is required on &os; 5.0 &i386; and alpha systems
to support applications compiled on older versions of &os;
that use older system call interfaces. It is recommended that
this option be used on all i386 and alpha systems that may
this option be used on all &i386; and alpha systems that may
run older applications; platforms that gained support only in
5.0, such as ia64 and sparc64, do not require this option.</para>
5.0, such as ia64 and &sparc64;, do not require this option.</para>
<programlisting>options SCSI_DELAY=15000 #Delay (in ms) before probing SCSI</programlisting>
@ -880,7 +880,7 @@ options CD9660_ROOT #CD-ROM usable as root, CD9660 required</programli
<programlisting>options P1003_1B #Posix P1003_1B real-time extensions
options _KPOSIX_PRIORITY_SCHEDULING</programlisting>
<para>Real-time extensions added in the 1993 POSIX. Certain
<para>Real-time extensions added in the 1993 &posix;. Certain
applications in the ports collection use these
(such as <application>StarOffice</application>).</para>
@ -1109,7 +1109,7 @@ device sio2 at isa? disable port IO_COM3 irq 5
device sio3 at isa? disable port IO_COM4 irq 9</programlisting>
<para>These are the four serial ports referred to as COM1 through COM4
in the MS-DOS/Windows world.</para>
in the &ms-dos/&windows; world.</para>
<note>
<para>If you have an internal modem on COM4 and a serial port at

150
en_US.ISO8859-1/books/handbook/printing/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/printing/chapter.sgml,v 1.76 2003/08/15 02:02:50 murray Exp $
-->
<chapter id="printing">
@ -38,7 +38,7 @@
<para>FreeBSD can also be configured to act as a print server on a
network; in this capacity FreeBSD can receive print jobs from a variety
of other computers, including other FreeBSD computers, Windows and MacOS
of other computers, including other FreeBSD computers, &windows; and &macos;
hosts. FreeBSD will ensure that one job at a time is printed, and can
keep statistics on which users and machines are doing the most printing,
produce <quote>banner</quote> pages showing who's printout is who's, and
@ -330,15 +330,15 @@
<indexterm><primary>PostScript</primary></indexterm>
<para>Usually, the only time you need two-way communication with
the printer is if the printer speaks PostScript. PostScript
printers can be very verbose. In fact, PostScript jobs are
the printer is if the printer speaks &postscript;. &postscript;
printers can be very verbose. In fact, &postscript; jobs are
actually programs sent to the printer; they need not produce
paper at all and may return results directly to the computer.
PostScript also uses two-way communication to tell the
computer about problems, such as errors in the PostScript
&postscript; also uses two-way communication to tell the
computer about problems, such as errors in the &postscript;
program or paper jams. Your users may be appreciative of such
information. Furthermore, the best way to do effective
accounting with a PostScript printer requires two-way
accounting with a &postscript; printer requires two-way
communication: you ask the printer for its page count (how
many pages it has printed in its lifetime), then send the
user's job, then ask again for its page count. Subtract the
@ -710,8 +710,8 @@ ppc0: FIFO with 16/16/8 bytes threshold</screen>
printable ASCII characters in 96 lines.</para>
<indexterm><primary>PostScript</primary></indexterm>
<para>For a PostScript (or other language-based) printer, we
will need a more sophisticated test. A small PostScript
<para>For a &postscript; (or other language-based) printer, we
will need a more sophisticated test. A small &postscript;
program, such as the following, will suffice:</para>
<programlisting>%!PS
@ -720,17 +720,17 @@ ppc0: FIFO with 16/16/8 bytes threshold</screen>
(Is this thing working?) show
showpage</programlisting>
<para>The above PostScript code can be placed into a file and
<para>The above &postscript; code can be placed into a file and
used as shown in the examples appearing in the following
sections.</para>
<indexterm><primary>PCL</primary></indexterm>
<note>
<para>When this document refers to a printer language, it is
assuming a language like PostScript, and not Hewlett
assuming a language like &postscript;, and not Hewlett
Packard's PCL. Although PCL has great functionality, you
can intermingle plain text with its escape sequences.
PostScript cannot directly print plain text, and that is the
&postscript; cannot directly print plain text, and that is the
kind of printer language for which we must make special
accommodations.</para>
</note>
@ -769,7 +769,7 @@ showpage</programlisting>
</listitem>
<listitem>
<para>If the printer understands PostScript or other
<para>If the printer understands &postscript; or other
printer language, then send a small program to the
printer. Type:</para>
@ -870,14 +870,14 @@ showpage</programlisting>
</listitem>
<listitem>
<para>If the printer understands PostScript or other
<para>If the printer understands &postscript; or other
printer language, then send a small program to the
printer. Type the program, line by line,
<emphasis>very carefully</emphasis> as backspacing
or other editing keys may be significant to the
printer. You may also need to type a special
end-of-file key for the printer so it knows it
received the whole program. For PostScript
received the whole program. For &postscript;
printers, press <literal>CONTROL+D</literal>.</para>
<para>Alternatively, you can put the program in a file
@ -984,7 +984,7 @@ showpage</programlisting>
</procedure>
<note>
<para>Language-based printers, such as PostScript printers,
<para>Language-based printers, such as &postscript; printers,
cannot directly print plain text. The simple setup outlined
above and described in the following sections assumes that if
you are installing such a printer you will print only files
@ -999,10 +999,10 @@ showpage</programlisting>
print jobs in the printer language <emphasis>and</emphasis>
print plain text jobs, you are strongly urged to add an
additional step to the simple setup outlined above: install an
automatic plain-text-to-PostScript (or other printer language)
automatic plain-text-to-&postscript; (or other printer language)
conversion program. The section entitled <link
linkend="printing-advanced-if-conversion">Accommodating Plain
Text Jobs on PostScript Printers</link> tells how to do
Text Jobs on &postscript; Printers</link> tells how to do
this.</para>
<sect4 id="printing-naming">
@ -1034,7 +1034,7 @@ showpage</programlisting>
<para>In the following example, we start with a skeletal
<filename>/etc/printcap</filename> that defines two printers
(a Diablo 630 line printer and a Panasonic KX-P4455 PostScript
(a Diablo 630 line printer and a Panasonic KX-P4455 &postscript;
laser printer):</para>
<programlisting>#
@ -1411,12 +1411,12 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<filename>/etc/printcap</filename>. To test the default
printer, type &man.lpr.1; without any <option>-P</option>
argument. Again, if you are testing a printer that expects
PostScript, send a PostScript program in that language instead
&postscript;, send a &postscript; program in that language instead
of using &man.lptest.1;. You can do so by putting the program
in a file and typing <command>lpr
<replaceable>file</replaceable></command>.</para>
<para>For a PostScript printer, you should get the results of
<para>For a &postscript; printer, you should get the results of
the program. If you are using &man.lptest.1;, then your
results should look like the following:</para>
@ -1497,24 +1497,24 @@ $%&amp;'()*+,-./01234567
<listitem>
<para><application>LPD</application> expects every printer to be
able to print plain text by
default. This presents a problem for PostScript (or other
default. This presents a problem for &postscript; (or other
language-based printers) which cannot directly print plain text.
Section <link
linkend="printing-advanced-if-conversion">Accommodating
Plain Text Jobs on PostScript Printers</link> tells you what you
Plain Text Jobs on &postscript; Printers</link> tells you what you
should do to overcome this problem. You should read this
section if you have a PostScript printer.</para>
section if you have a &postscript; printer.</para>
</listitem>
<listitem>
<para>PostScript is a popular output format for many programs. Even
some people (myself included) write PostScript code directly. But
PostScript printers are expensive. Section <link
linkend="printing-advanced-ps">Simulating PostScript on
Non-PostScript Printers</link> tells how you can further modify
a printer's text filter to accept and print PostScript data on a
<emphasis>non-PostScript</emphasis> printer. You should read
this section if you do not have a PostScript printer.</para>
<para>&postscript; is a popular output format for many programs. Even
some people (myself included) write &postscript; code directly. But
&postscript; printers are expensive. Section <link
linkend="printing-advanced-ps">Simulating &postscript; on
Non &postscript; Printers</link> tells how you can further modify
a printer's text filter to accept and print &postscript; data on a
<emphasis>non &postscript;</emphasis> printer. You should read
this section if you do not have a &postscript; printer.</para>
</listitem>
<listitem>
@ -1779,24 +1779,24 @@ $%&amp;'()*+,-./01234567
</sect3>
<sect3 id="printing-advanced-if-conversion">
<title>Accommodating Plain Text Jobs on PostScript Printers</title>
<title>Accommodating Plain Text Jobs on &postscript; Printers</title>
<indexterm><primary>print jobs</primary></indexterm>
<para>If you are the only user of your computer and PostScript (or
<para>If you are the only user of your computer and &postscript; (or
other language-based) printer, and you promise to never send plain
text to your printer and to never use features of various programs
that will want to send plain text to your printer, then you do not
need to worry about this section at all.</para>
<para>But, if you would like to send both PostScript and plain text
<para>But, if you would like to send both &postscript; and plain text
jobs to the printer, then you are urged to augment your printer
setup. To do so, we have the text filter detect if the arriving job
is plain text or PostScript. All PostScript jobs must start with
is plain text or &postscript;. All &postscript; jobs must start with
<literal>%!</literal> (for other printer languages, see your printer
documentation). If those are the first two characters in the job,
we have PostScript, and can pass the rest of the job directly. If
we have &postscript;, and can pass the rest of the job directly. If
those are not the first two characters in the file, then the filter
will convert the text into PostScript and print the result.</para>
will convert the text into &postscript; and print the result.</para>
<para>How do we do this?</para>
@ -1806,7 +1806,7 @@ $%&amp;'()*+,-./01234567
</indexterm>
<para>If you have got a serial printer, a great way to do it is to
install <command>lprps</command>. <command>lprps</command> is a
PostScript printer filter which performs two-way communication with
&postscript; printer filter which performs two-way communication with
the printer. It updates the printer's status file with verbose
information from the printer, so users and administrators can see
exactly what the state of the printer is (such as <errorname>toner
@ -1814,7 +1814,7 @@ $%&amp;'()*+,-./01234567
importantly, it includes a program called <command>psif</command>
which detects whether the incoming job is plain text and calls
<command>textps</command> (another program that comes with
<command>lprps</command>) to convert it to PostScript. It then uses
<command>lprps</command>) to convert it to &postscript;. It then uses
<command>lprps</command> to send the job to the printer.</para>
<para><command>lprps</command> is part of the FreeBSD Ports Collection
@ -1824,7 +1824,7 @@ $%&amp;'()*+,-./01234567
<command>psif</command> program that is part of
<command>lprps</command>. If you installed <command>lprps</command>
from the ports collection, use the following in the serial
PostScript printer's entry in
&postscript; printer's entry in
<filename>/etc/printcap</filename>:</para>
<programlisting>:if=/usr/local/libexec/psif:</programlisting>
@ -1833,7 +1833,7 @@ $%&amp;'()*+,-./01234567
that tells <application>LPD</application> to open the printer in
read-write mode.</para>
<para>If you have a parallel PostScript printer (and therefore cannot
<para>If you have a parallel &postscript; printer (and therefore cannot
use two-way communication with the printer, which
<command>lprps</command> needs), you can use the following shell
script as the text filter:</para>
@ -1863,38 +1863,38 @@ else
fi</programlisting>
<para>In the above script, <command>textps</command> is a program we
installed separately to convert plain text to PostScript. You can
use any text-to-PostScript program you wish. The FreeBSD Ports
installed separately to convert plain text to &postscript;. You can
use any text-to-&postscript; program you wish. The FreeBSD Ports
Collection (see <link linkend="ports">The Ports Collection</link>)
includes a full featured text-to-PostScript program called
includes a full featured text-to-&postscript; program called
<literal>a2ps</literal> that you might want to investigate.</para>
</sect3>
<sect3 id="printing-advanced-ps">
<title>Simulating PostScript on Non-PostScript Printers</title>
<title>Simulating &postscript; on Non &postscript; Printers</title>
<indexterm>
<primary>PostScript</primary>
<secondary>emulating</secondary>
</indexterm>
<indexterm>
<primary>Ghostscript</primary></indexterm>
<para>PostScript is the <emphasis>de facto</emphasis> standard for
high quality typesetting and printing. PostScript is, however, an
<para>&postscript; is the <emphasis>de facto</emphasis> standard for
high quality typesetting and printing. &postscript; is, however, an
<emphasis>expensive</emphasis> standard. Thankfully, Aladdin
Enterprises has a free PostScript work-alike called
Enterprises has a free &postscript; work-alike called
<application>Ghostscript</application> that runs with FreeBSD.
Ghostscript can read most PostScript files and can render their
Ghostscript can read most &postscript; files and can render their
pages onto a variety of devices, including many brands of
non-PostScript printers. By installing Ghostscript and using a
special text filter for your printer, you can make your
non-PostScript printer act like a real PostScript printer.</para>
non &postscript; printer act like a real &postscript; printer.</para>
<para>Ghostscript is in the FreeBSD Ports Collection, if you
would like to install it from there. You can fetch, build, and
install it quite easily yourself, as well.</para>
<para>To simulate PostScript, we have the text filter detect if it is
printing a PostScript file. If it is not, then the filter will pass
<para>To simulate &postscript;, we have the text filter detect if it is
printing a &postscript; file. If it is not, then the filter will pass
the file directly to the printer; otherwise, it will use Ghostscript
to first convert the file into a format the printer will
understand.</para>
@ -1975,9 +1975,9 @@ exit 2</programlisting>
<para>Conversion filters make printing various kinds of files easy.
As an example, suppose we do a lot of work with the &tex;
typesetting system, and we have a PostScript printer. Every time
typesetting system, and we have a &postscript; printer. Every time
we generate a DVI file from &tex;, we cannot print it directly until
we convert the DVI file into PostScript. The command sequence
we convert the DVI file into &postscript;. The command sequence
goes like this:</para>
<screen>&prompt.user; <userinput>dvips seaweed-analysis.dvi</userinput>
@ -2151,10 +2151,10 @@ exec /usr/local/bin/dvips -f | /usr/local/libexec/lprps "$@"</programlisting>
<para>This script runs <command>dvips</command> in filter mode (the
<option>-f</option> argument) on standard input, which is the job
to print. It then starts the PostScript printer filter
to print. It then starts the &postscript; printer filter
<command>lprps</command> (see section <link
linkend="printing-advanced-if-conversion">Accommodating Plain
Text Jobs on PostScript Printers</link>) with the arguments
Text Jobs on &postscript; Printers</link>) with the arguments
<application>LPD</application>
passed to this script. <command>lprps</command> will use those
arguments to account for the pages printed.</para>
@ -2199,7 +2199,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
:vf=/usr/local/libexec/hpvf:</programlisting>
<para>The following script is a conversion filter for troff data
from the groff typesetting system for the PostScript printer named
from the groff typesetting system for the &postscript; printer named
<literal>bamboo</literal>:</para>
<programlisting>#!/bin/sh
@ -2383,7 +2383,7 @@ exit 0</programlisting>
</indexterm>
<para>The FreeBSD Ports Collection has a text filter that performs
automatic conversion called <command>apsfilter</command>. It can
detect plain text, PostScript, and DVI files, run the proper
detect plain text, &postscript;, and DVI files, run the proper
conversions, and print.</para>
</sect4>
</sect3>
@ -2542,10 +2542,10 @@ exit 0</programlisting>
<para>The <application>LPD</application> system can provide header
pages automatically for your
printouts <emphasis>if</emphasis> your printer can directly print
plain text. If you have a PostScript printer, you will need an
plain text. If you have a &postscript; printer, you will need an
external program to generate the header page; see <link
linkend="printing-advanced-header-pages-ps">Header Pages on
PostScript Printers</link>.</para>
&postscript; Printers</link>.</para>
<sect3 id="printing-advanced-header-pages-enabling">
<title>Enabling Header Pages</title>
@ -2760,11 +2760,11 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
</sect3>
<sect3 id="printing-advanced-header-pages-ps">
<title>Header Pages on PostScript Printers</title>
<title>Header Pages on &postscript; Printers</title>
<para>As described above, <application>LPD</application> can generate
a plain text header page
suitable for many printers. Of course, PostScript cannot directly
suitable for many printers. Of course, &postscript; cannot directly
print plain text, so the header page feature of
<application>LPD</application> is
useless&mdash;or mostly so.</para>
@ -2778,7 +2778,7 @@ teak|hp|laserjet|Hewlett Packard LaserJet 3Si:\
<para>Let us explore this method. The following script takes three
arguments (user login name, host name, and job name) and makes a
simple PostScript header page:</para>
simple &postscript; header page:</para>
<programlisting>#!/bin/sh
#
@ -2915,15 +2915,15 @@ done
will need to use the trick introduced in section <link
linkend="printing-advanced-header-pages-accounting">Accounting for
Header Pages</link>: write an output filter that parses the
LPD-generated header page and produces a PostScript version. If the
LPD-generated header page and produces a &postscript; version. If the
user submits the job with <command>lpr -h</command>, then
<application>LPD</application> will
not generate a header page, and neither will your output filter.
Otherwise, your output filter will read the text from
<application>LPD</application> and send
the appropriate header page PostScript code to the printer.</para>
the appropriate header page &postscript; code to the printer.</para>
<para>If you have a PostScript printer on a serial line, you can make
<para>If you have a &postscript; printer on a serial line, you can make
use of <command>lprps</command>, which comes with an output filter,
<command>psof</command>, which does the above. Note that
<command>psof</command> does not charge for header pages.</para>
@ -3126,7 +3126,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<application>LPDs</application> would transfer the
file to <hostid>rose</hostid>. The file would wait in <hostid>rose</hostid>'s
queue until it was finally printed. It would be converted from DVI to
PostScript (since <literal>bamboo</literal> is a PostScript printer) on
&postscript; (since <literal>bamboo</literal> is a &postscript; printer) on
<hostid>rose</hostid>.</para>
</sect3>
@ -3297,7 +3297,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<sect3 id="printing-advanced-restricting-access">
<title>Restricting Access to Printers</title>
<para>You can control who can print to what printers by using the Unix
<para>You can control who can print to what printers by using the &unix;
group mechanism and the <literal>rg</literal> capability in
<filename>/etc/printcap</filename>. Just place the users you want
to have access to a printer in a certain group, and then name that
@ -3387,7 +3387,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
<para>Let us add limits to our example printers
<literal>rattan</literal> and <literal>bamboo</literal>. Since
those artists' PostScript files tend to be large, we will limit them
those artists' &postscript; files tend to be large, we will limit them
to five megabytes. We will put no limit on the plain text line
printer:</para>
@ -3799,7 +3799,7 @@ total 337.00 154 $ 6.74</screen>
<para>How do you handle other file formats, though?</para>
<para>Well, for DVI-to-LaserJet or DVI-to-PostScript conversion, you
<para>Well, for DVI-to-LaserJet or DVI-to-&postscript; conversion, you
can have your filter parse the diagnostic output of
<command>dvilj</command> or <command>dvips</command> and look to see
how many pages were converted. You might be able to do similar
@ -3815,7 +3815,7 @@ total 337.00 154 $ 6.74</screen>
<para>There is only one <emphasis>sure</emphasis> way to do
<emphasis>accurate</emphasis> accounting. Get a printer that can
tell you how much paper it uses, and attach it via a serial line or
a network connection. Nearly all PostScript printers support this
a network connection. Nearly all &postscript; printers support this
notion. Other makes and models do as well (networked Imagen laser
printers, for example). Modify the filters for these printers to
get the page usage after they print each job and have them log
@ -4648,11 +4648,11 @@ exit 2</programlisting>
<indexterm><primary>ASCII</primary></indexterm>
<para>You have become another victim of the <emphasis>staircase
effect</emphasis>, caused by conflicting interpretations of
what characters should indicate a new line. Unix-style
what characters should indicate a new line. &unix; style
operating systems use a single character: ASCII code 10, the
line feed (LF). MS-DOS, OS/2, and others uses a pair of
line feed (LF). &ms-dos;, &os2;, and others uses a pair of
characters, ASCII code 10 <emphasis>and</emphasis> ASCII code
13 (the carriage return or CR). Many printers use the MS-DOS
13 (the carriage return or CR). Many printers use the &ms-dos;
convention for representing new-lines.</para>
<para>When you print with FreeBSD, your text used just the line

62
en_US.ISO8859-1/books/handbook/security/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.175 2003/08/15 19:12:03 blackend Exp $
-->
<chapter id="security">
@ -62,7 +62,7 @@
<listitem>
<para>How to configure IPsec and create a VPN between
FreeBSD/Windows machines.</para>
FreeBSD/&windows; machines.</para>
</listitem>
<listitem>
@ -95,12 +95,12 @@
<title>Introduction</title>
<para>Security is a function that begins and ends with the system
administrator. While all BSD Unix multi-user systems have some
administrator. While all BSD &unix; multi-user systems have some
inherent security, the job of building and maintaining additional
security mechanisms to keep those users <quote>honest</quote> is
probably one of the single largest undertakings of the sysadmin.
Machines are only as secure as you make them, and security concerns
are ever competing with the human necessity for convenience. Unix
are ever competing with the human necessity for convenience. &unix;
systems, in general, are capable of running a huge number of
simultaneous processes and many of these processes operate as
servers &ndash; meaning that external entities can connect and talk
@ -975,7 +975,7 @@
<indexterm><primary>DES</primary></indexterm>
<indexterm><primary>MD5</primary></indexterm>
<para>Every user on a Unix system has a password associated with
<para>Every user on a &unix; system has a password associated with
their account. It seems obvious that these passwords need to be
known only to the user and the actual operating system. In
order to keep these passwords secret, they are encrypted with
@ -989,11 +989,11 @@
space of possible passwords.</para>
<para>Unfortunately the only secure way to encrypt passwords when
Unix came into being was based on DES, the Data Encryption
&unix; came into being was based on DES, the Data Encryption
Standard. This was not such a problem for users resident in
the US, but since the source code for DES could not be exported
outside the US, FreeBSD had to find a way to both comply with
US law and retain compatibility with all the other Unix
US law and retain compatibility with all the other &unix;
variants that still used DES.</para>
<para>The solution was to divide up the encryption libraries
@ -1059,8 +1059,8 @@
Everything). OPIE uses the MD5 hash by default.</para>
<para>There are three different sorts of passwords which we will discuss
below. The first is your usual Unix-style or
Kerberos password; we will call this a <quote>Unix password</quote>.
below. The first is your usual &unix; style or
Kerberos password; we will call this a <quote>&unix; password</quote>.
The second sort is the one-time password which is generated by the
S/Key <command>key</command> program or the OPIE
&man.opiekey.1; program and accepted by the
@ -1075,14 +1075,14 @@
one-time passwords; we will call it a <quote>secret password</quote>
or just unqualified <quote>password</quote>.</para>
<para>The secret password does not have anything to do with your Unix
<para>The secret password does not have anything to do with your &unix;
password; they can be the same but this is not recommended. S/Key
and OPIE secret passwords are not limited to 8 characters like old
Unix passwords<footnote><para>Under &os; the standard login
&unix; passwords<footnote><para>Under &os; the standard login
password may be up to 128 characters in length.</para></footnote>,
they can be as long as you like. Passwords of six or
seven word long phrases are fairly common. For the most part, the
S/Key or OPIE system operates completely independently of the Unix
S/Key or OPIE system operates completely independently of the &unix;
password system.</para>
<para>Besides the password, there are two other pieces of data that
@ -1188,7 +1188,7 @@ MOS MALL GOAT ARM AVID COED
insecure connection, you will need to already have a secure
connection to some place where you can run <command>key</command>
or <command>opiekey</command>; this might be in the form of a
desk accessory on a Macintosh, or a shell prompt on a machine you
desk accessory on a &macintosh;, or a shell prompt on a machine you
trust. You will also need to make up an iteration count (100 is
probably a good value), and you may make up your own seed or use a
randomly-generated one. Over on the insecure connection (to the
@ -1293,7 +1293,7 @@ Password: </screen>
answer this login prompt. This must be done on a trusted system
that you can run <command>key</command> or
<command>opiekey</command> on. (There are versions of these for DOS,
Windows and MacOS as well.) They need both the iteration count and
&windows; and &macos; as well.) They need both the iteration count and
the seed as command line options. You can cut-and-paste these
right from the login prompt on the machine that you are logging
in to.</para>
@ -1368,9 +1368,9 @@ Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
</sect2>
<sect2>
<title>Restricting Use of Unix Passwords</title>
<title>Restricting Use of &unix; Passwords</title>
<para>S/Key can place restrictions on the use of Unix passwords based
<para>S/Key can place restrictions on the use of &unix; passwords based
on the host name, user name, terminal port, or IP address of a
login session. These restrictions can be found in the
configuration file <filename>/etc/skey.access</filename>. The
@ -1380,10 +1380,10 @@ Enter secret pass phrase: <userinput>&lt;secret password&gt;</userinput>
<para>If there is no <filename>/etc/skey.access</filename> file
(this is the default on FreeBSD 4.X systems), then all users will
be allowed to use Unix passwords. If the file exists, however,
be allowed to use &unix; passwords. If the file exists, however,
then all users will be required to use S/Key unless explicitly
permitted to do otherwise by configuration statements in the
<filename>skey.access</filename> file. In all cases, Unix
<filename>skey.access</filename> file. In all cases, &unix;
passwords are permitted on the console.</para>
<para>Here is a sample <filename>skey.access</filename> configuration
@ -1396,23 +1396,23 @@ permit port ttyd0</programlisting>
<para>The first line (<literal>permit internet</literal>) allows
users whose IP source address (which is vulnerable to spoofing)
matches the specified value and mask, to use Unix passwords. This
matches the specified value and mask, to use &unix; passwords. This
should not be considered a security mechanism, but rather, a means
to remind authorized users that they are using an insecure network
and need to use S/Key for authentication.</para>
<para>The second line (<literal>permit user</literal>) allows the
specified username, in this case <username>fnord</username>, to use
Unix passwords at any time. Generally speaking, this should only
&unix; passwords at any time. Generally speaking, this should only
be used for people who are either unable to use the
<command>key</command> program, like those with dumb terminals, or
those who are uneducable.</para>
<para>The third line (<literal>permit port</literal>) allows all
users logging in on the specified terminal line to use Unix
users logging in on the specified terminal line to use &unix;
passwords; this would be used for dial-ups.</para>
<para>OPIE can restrict the use of Unix passwords based on the IP
<para>OPIE can restrict the use of &unix; passwords based on the IP
address of a login session just like S/Key does. The relevant file
is <filename>/etc/opieaccess</filename>, which is present by default
on FreeBSD 5.0 and newer systems. Please check &man.opieaccess.5;
@ -1425,7 +1425,7 @@ permit port ttyd0</programlisting>
<para>This line allows users whose IP source address (which is
vulnerable to spoofing) matches the specified value and mask,
to use Unix passwords at any time.</para>
to use &unix; passwords at any time.</para>
<para>If no rules in <filename>opieaccess</filename> are matched,
the default is to deny non-OPIE logins.</para>
@ -2920,7 +2920,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
<para>This section will guide you through the process of setting
up IPsec, and to use it in an environment which consists of
FreeBSD and <application>Microsoft Windows 2000/XP</application>
FreeBSD and <application>&microsoft.windows; 2000/XP</application>
machines, to make them communicate securely. In order to set up
IPsec, it is necessary that you are familiar with the concepts
of building a custom kernel (see
@ -3070,7 +3070,7 @@ options IPSEC_DEBUG #debug for IP security
<textobject>
<literallayout class="monospaced">Network #1 [ Internal Hosts ] Private Net, 192.168.1.2-254
[ Win9x/NT/2K ]
[ Unix ]
[ UNIX ]
|
|
.---[fxp1]---. Private IP, 192.168.1.1
@ -3088,7 +3088,7 @@ options IPSEC_DEBUG #debug for IP security
|
Network #2 [ Internal Hosts ]
[ Win9x/NT/2K ] Private Net, 192.168.2.2-254
[ Unix ]</literallayout>
[ UNIX ]</literallayout>
</textobject>
</mediaobject>
@ -3114,7 +3114,7 @@ Network #2 [ Internal Hosts ]
<programlisting>ping 192.168.2.34</programlisting>
<para>and have it work, transparently. Windows machines should
<para>and have it work, transparently. &windows; machines should
be able to see the machines on the other network, browse file
shares, and so on, in exactly the same way that they can browse
machines on the local network.</para>
@ -3141,7 +3141,7 @@ Network #2 [ Internal Hosts ]
<listitem>
<para>Configure additional software on the FreeBSD gateways,
to allow Windows machines to see one another across the
to allow &windows; machines to see one another across the
VPN.</para>
</listitem>
</orderedlist>
@ -4466,8 +4466,8 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput><
and later offers the security of File System Access Control Lists
(<acronym>ACLs</acronym>).</para>
<para>Access Control Lists extend the standard UNIX
permission model in a highly compatible (POSIX.1e) way. This feature
<para>Access Control Lists extend the standard &unix;
permission model in a highly compatible (&posix;.1e) way. This feature
permits an administrator to make use of and take advantage of a
more sophisticated security model.</para>
@ -4482,7 +4482,7 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput><
This option is included in the <filename>GENERIC</filename> kernel.
<acronym>ACLs</acronym> rely on extended attributes being enabled on
the file system. Extended attributes are natively supported in the next generation
UNIX file system, <acronym>UFS2</acronym>.</para>
&unix; file system, <acronym>UFS2</acronym>.</para>
<note><para>A higher level of administrative overhead is required to
configure extended attributes on <acronym>UFS1</acronym> than on

8
en_US.ISO8859-1/books/handbook/users/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD$
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.37 2002/10/10 21:14:28 blackend Exp $
-->
<chapter id="users">
@ -67,7 +67,7 @@
<itemizedlist>
<listitem>
<para>Understand the basics of Unix and FreeBSD (<xref
<para>Understand the basics of &unix; and FreeBSD (<xref
linkend="basics">).</para>
</listitem>
</itemizedlist>
@ -321,7 +321,7 @@
</indexterm>
<para>There are a variety of different commands available in the
Unix environment to manipulate user accounts. The most common
&unix; environment to manipulate user accounts. The most common
commands are summarized below, followed by more detailed
examples of their usage.</para>
@ -982,7 +982,7 @@ passwd: done</screen>
<secondary>groups</secondary>
</indexterm>
<para>A group is simply a list of users. Groups are identified by
their group name and GID (Group ID). In FreeBSD (and most other Unix
their group name and GID (Group ID). In FreeBSD (and most other &unix; like
systems), the two factors the kernel uses to decide whether a process
is allowed to do something is its user ID and list of groups it
belongs to. Unlike a user ID, a process has a list of groups

70
en_US.ISO8859-1/books/handbook/x11/chapter.sgml
View file

@ -37,7 +37,7 @@
</listitem>
<listitem>
<para>How to use TrueType fonts in
<para>How to use &truetype; fonts in
<application>XFree86</application>.</para>
</listitem>
@ -59,8 +59,8 @@
<title>Understanding X</title>
<para>Using X for the first time can be somewhat of a shock to someone
familiar with other graphical environments, such as Microsoft Windows or
MacOS.</para>
familiar with other graphical environments, such as &microsoft.windows; or
&macos;.</para>
<para>It is not necessary to understand all of the details of various
X components and how they interact; however, some basic knowledge makes
@ -69,7 +69,7 @@
<sect2>
<title>Why X?</title>
<para>X is not the first window system written for Unix, but it is the
<para>X is not the first window system written for &unix;, but it is the
most popular. X's original development team had worked on another
window system before writing X. That system's name was
<quote>W</quote> (for <quote>Window</quote>). X is just the next
@ -90,7 +90,7 @@
monitor, and mouse attached. The server is responsible for managing
the display, handling input from the keyboard and mouse, and so on.
Each X application (such as <application>XTerm</application>, or
<application>Netscape</application>) is a <quote>client</quote>. A
<application>&netscape;</application>) is a <quote>client</quote>. A
client sends messages to the server such as <quote>Please draw a
window at these coordinates</quote>, and the server sends back
messages such as <quote>The user just clicked on the OK
@ -116,7 +116,7 @@
<para>There is nothing in the protocol that forces the client and
server machines to be running the same operating system, or even to
be running on the same type of computer. It is certainly possible to
run an X server on Microsoft Windows or Apple's MacOS, and there are
run an X server on &microsoft.windows; or Apple's &macos;, and there are
various free and commercial applications available that do exactly
that.</para>
@ -129,7 +129,7 @@
<sect2>
<title>The Window Manager</title>
<para>The X design philosophy is much like the Unix design philosophy,
<para>The X design philosophy is much like the &unix; design philosophy,
<quote>tools, not policy</quote>. This means that X does not try to
dictate how a task is to be accomplished. Instead, tools are provided
to the user, and it is the user's responsibility to decide how to use
@ -141,7 +141,7 @@
<keycombo action="simul">
<keycap>Alt</keycap>
<keycap>Tab</keycap>
</keycombo>, in the case of Microsoft Windows), what the title bars
</keycombo>, in the case of &microsoft.windows;), what the title bars
on each window should look like, whether or not they have close
buttons on them, and so on.</para>
@ -181,7 +181,7 @@
well.</para>
<para>A familiar focus policy is called <quote>click-to-focus</quote>.
This is the model utilized by Microsoft Windows, in which a window
This is the model utilized by &microsoft.windows;, in which a window
becomes active upon receiving a mouse click.</para>
<para>X does not support any particular focus policy. Instead, the
@ -245,10 +245,10 @@
<para><quote>Widget</quote> is a term for all the items in the user
interface that can be clicked or manipulated in some way; buttons,
check boxes, radio buttons, icons, lists, and so on. Microsoft
Windows calls these <quote>controls</quote>.</para>
check boxes, radio buttons, icons, lists, and so on. &microsoft.windows;
calls these <quote>controls</quote>.</para>
<para>Microsoft Windows and Apple's MacOS both have a very rigid widget
<para>&microsoft.windows; and Apple's &macos; both have a very rigid widget
policy. Application developers are supposed to ensure that their
applications share a common look and feel. With X, it was not
considered sensible to mandate a particular graphical style, or set
@ -257,8 +257,8 @@
<para>As a result, do not expect X applications to have a common
look and feel. There are several popular widget sets and
variations, including the original Athena widget set from MIT,
<application>Motif</application> (on which the widget set in
Microsoft Windows was modeled, all bevelled edges and three shades of
<application>&motif;</application> (on which the widget set in
&microsoft.windows; was modeled, all bevelled edges and three shades of
grey), <application>OpenLook</application>, and others.</para>
<para>Most newer X applications today will use a modern-looking widget
@ -266,7 +266,7 @@
<application>GTK</application>, used by the
<application>GNOME</application>
project. In this respect, there is some convergence in
look-and-feel of the Unix desktop, which certainly makes things
look-and-feel of the &unix; desktop, which certainly makes things
easier for the novice user.</para>
</sect2>
</sect1>
@ -526,11 +526,11 @@ EndSection</programlisting>
<title>Advanced Configuration Topics</title>
<sect3>
<title>Configuration with Intel i810 Graphics Chipsets</title>
<title>Configuration with &intel; i810 Graphics Chipsets</title>
<indexterm><primary>Intel i810 graphic chipset</primary></indexterm>
<para>Configuration with Intel i810 integrated chipsets
<para>Configuration with &intel; i810 integrated chipsets
requires the <devicename>agpgart</devicename>
AGP programming interface for <application>XFree86</application>
to drive the card. The &man.agp.4; driver is in the
@ -599,8 +599,8 @@ EndSection</programlisting>
<application>XFree86</application> are less than ideal for typical
desktop publishing applications. Large presentation fonts show up
jagged and unprofessional looking, and small fonts in
<application>Netscape</application> are almost completely unintelligible.
However, there are several free, high quality Type1 (PostScript) fonts
<application>&netscape;</application> are almost completely unintelligible.
However, there are several free, high quality Type1 (&postscript;) fonts
available which can be readily used
with <application>XFree86</application>, either version 3.X or
version 4.X. For instance, the URW font collection
@ -612,8 +612,8 @@ EndSection</programlisting>
graphics software such as the <application>Gimp</application>, and are not
complete enough to serve as screen fonts. In addition,
<application>XFree86</application> can be configured to use
TrueType fonts with a minimum of effort: see the
<link linkend="truetype">section on TrueType fonts</link> later.</para>
&truetype; fonts with a minimum of effort: see the
<link linkend="truetype">section on &truetype; fonts</link> later.</para>
<para>To install the above Type1 font collections from the ports
collection, run the following commands:</para>
@ -647,7 +647,7 @@ EndSection</programlisting>
</sect2>
<sect2 id="truetype">
<title>TrueType Fonts</title>
<title>&truetype; Fonts</title>
<indexterm><primary>TrueType Fonts</primary></indexterm>
<indexterm><primary>fonts</primary>
@ -655,7 +655,7 @@ EndSection</programlisting>
</indexterm>
<para><application>XFree86 4.X</application> has built in support
for rendering TrueType fonts. There are two different modules
for rendering &truetype; fonts. There are two different modules
that can enable this functionality. The freetype module is used
in this example because it is more consistent with the other font
rendering back-ends. To enable the freetype module just add the
@ -665,17 +665,17 @@ EndSection</programlisting>
<programlisting>Load "freetype"</programlisting>
<para>For <application>XFree86 3.3.X</application>, a separate
TrueType font server is needed.
&truetype; font server is needed.
<application>Xfstt</application> is commonly used for
this purpose. To install <application>Xfstt</application>,
simply install the port
<filename role="package">x11-servers/Xfstt</filename>.</para>
<para>Now make a directory for the TrueType fonts (for example,
<para>Now make a directory for the &truetype; fonts (for example,
<filename>/usr/X11R6/lib/X11/fonts/TrueType</filename>)
and copy all of the TrueType fonts into this directory. Keep in
mind that TrueType fonts cannot be directly taken from a
Macintosh; they must be in Unix/DOS/Windows format for use by
and copy all of the &truetype; fonts into this directory. Keep in
mind that &truetype; fonts cannot be directly taken from a
&macintosh;; they must be in &unix;/DOS/&windows; format for use by
<application>XFree86</application>. Once the files have been
copied into this directory, use
<application>ttmkfdir</application> to create a
@ -688,7 +688,7 @@ EndSection</programlisting>
<screen>&prompt.root; <userinput>cd /usr/X11R6/lib/X11/fonts/TrueType</userinput>
&prompt.root; <userinput>ttmkfdir > fonts.dir</userinput></screen>
<para>Now add the TrueType directory to the font
<para>Now add the &truetype; directory to the font
path. This is just the same as described above for <link
linkend="type1">Type1</link> fonts, that is, use</para>
@ -698,10 +698,10 @@ EndSection</programlisting>
<para>or add a <option>FontPath</option> line to the
<filename>XF86Config</filename> file.</para>
<para>That's it. Now <application>Netscape</application>,
<para>That's it. Now <application>&netscape;</application>,
<application>Gimp</application>,
<application>StarOffice</application>, and all of the other X
applications should now recognize the installed TrueType
<application>&staroffice;</application>, and all of the other X
applications should now recognize the installed &truetype;
fonts. Extremely small fonts (as with text in a high resolution
display on a web page) and extremely large fonts (within
<application>StarOffice</application>) will look much better
@ -1357,7 +1357,7 @@ DisplayManager.requestPort: 0</screen>
news client and more. <application>KDE</application> also
comes with a web browser called
<application>Konqueror</application>, which represents
a solid competitor to other existing web browsers on Unix
a solid competitor to other existing web browsers on &unix;
systems. More information on <application>KDE</application>
can be found on the <ulink url="http://www.kde.org/">KDE
website</ulink>. For FreeBSD specific informations and
@ -1417,7 +1417,7 @@ DisplayManager.requestPort: 0</screen>
<para>Now that <application>KDE</application> is installed on
the system, most things can be discovered through the
help pages, or just by pointing and clicking at various menus.
Windows or Mac users will feel quite at home.</para>
&windows; or &mac; users will feel quite at home.</para>
<para>The best reference for <application>KDE</application> is
the on-line documentation. <application>KDE</application>
@ -1572,7 +1572,7 @@ esac</screen>
more lightweight and meant for those who want a simple,
efficient desktop which is nevertheless easy to use and
configure. Visually, it looks very much like
<application>CDE</application>, found on commercial Unix
<application>CDE</application>, found on commercial &unix;
systems. Some of <application>XFce</application>'s features
are:</para>

35
share/sgml/trademarks.ent
View file

@ -9,7 +9,7 @@
Please keep this file sorted and in sync with
www/en/copyright/trademarks.sgml.
$FreeBSD$
$FreeBSD: doc/share/sgml/trademarks.ent,v 1.3 2003/08/19 08:16:14 blackend Exp $
-->
<!ENTITY tm-attrib.3com "<para>3Com and HomeConnect are registered
@ -17,6 +17,11 @@
<!-- An SGML entity can't start with a number... -->
<!ENTITY t3com "<trademark class='registered'>3Com</trademark>">
<!ENTITY tm-attrib.3ware "<para>3ware and Escalade are registered
trademarks of 3ware Inc.</para>">
<!ENTITY tm.3ware "<trademark class='registered'>3ware</trademark>">
<!ENTITY escalade "<trademark class='registered'>Escalade</trademark>">
<!ENTITY tm-attrib.adobe "<para>Adobe, Acrobat, Acrobat Reader, and
PostScript are either registered trademarks or trademarks of Adobe
Systems Incorporated in the United States and/or other
@ -25,10 +30,16 @@
<!ENTITY acrobat.reader "<trademark class='registered'>Acrobat&nbsp;Reader</trademark>">
<!ENTITY postscript "<trademark class='registered'>PostScript</trademark>">
<!ENTITY tm-attrib.apple "<para>Apple, FireWire, Macintosh, Mac OS,
<!-- http://www.adaptec.com/worldwide/company/compeditorial.html?prodkey=legal_copyright -->
<!ENTITY tm-attrib.adaptec "<para>Adaptec is registered trademark of
Adaptec, Inc.</para>">
<!ENTITY adaptec "<trademark class='registered'>Adaptec</trademark>">
<!ENTITY tm-attrib.apple "<para>Apple, FireWire, Mac, Macintosh, Mac OS,
Quicktime, and TrueType are trademarks of Apple Computer, Inc.,
registered in the United States and other countries.</para>">
<!ENTITY firewire "<trademark class='registered'>FireWire</trademark>">
<!ENTITY mac "<trademark class='registered'>Mac</trademark>">
<!ENTITY macintosh "<trademark class='registered'>Macintosh</trademark>">
<!ENTITY macos "<trademark class='registered'>Mac&nbsp;OS</trademark>">
<!ENTITY truetype "<trademark class='registered'>TrueType</trademark>">
@ -49,6 +60,11 @@
countries.</para>">
<!ENTITY soundblaster "<trademark class='registered'>SoundBlaster</trademark>">
<!-- http://www.dell.com/us/en/gen/misc/policy_007_policy.htm -->
<!ENTITY tm-attrib.dell "<para>Dell, Dell Precision, Latitude,
Optiplex, PowerEdge are trademarks or registered trademarks of Dell
Computer Corporation</para>">
<!ENTITY tm-attrib.freebsd "<para>FreeBSD is a registered trademark of
Wind River Systems, Inc. This is expected to change soon.</para>">
@ -92,6 +108,13 @@
<!ENTITY tm-attrib.linux "<para>Linux is a registered trademarks of
Linus Torvalds in the United States.</para>">
<!-- http://www.lsilogic.com/trademrk.html -->
<!ENTITY tm-attrib.lsilogic "<para>LSI Logic, AcceleRAID, eXtremeRAID,
MegaRAID and Mylex are trademarks or registered trademarks of LSI
Logic Corp.</para>">
<!ENTITY megaraid "<trademark class='registered'>MegaRAID</trademark>">
<!ENTITY mylex "<trademark class='registered'>Mylex</trademark>">
<!ENTITY tm-attrib.macromedia "<para>Macromedia and Flash are
trademarks or registered trademarks of Macromedia, Inc. in the
United States and/or other countries.</para>">
@ -112,6 +135,12 @@
countries.</para>">
<!ENTITY mips "<trademark class='registered'>MIPS</trademark>">
<!-- http://www.m-sys.com/content/LegalTerms.asp -->
<!ENTITY tm-attrib.m-systems "<para>M-Systems and, DiskOnChip are
trademarks or registered trademarks of M-Systems Flash Disk
Pioneers, Ltd.</para>">
<!ENTITY diskonchip "<trademark class='registered'>DiskOnChip</trademark>">
<!ENTITY tm-attrib.netscape "<para>Netscape and the Netscape Navigator
are registered trademarks of Netscape Communications Corporation in
the U.S. and other countries.</para>">
@ -156,6 +185,8 @@
<!ENTITY tm-attrib.sap "<para>SAP, R/3, and mySAP are trademarks or
registered trademarks of SAP AG in Germany and in several other
countries all over the world.</para>">
<!ENTITY sap.r3 "<trademark class='registered'>SAP</trademark>
<trademark class='registered'>R/3</trademark>">
<!ENTITY tm-attrib.sgi "<para>Silicon Graphics, SGI, and OpenGL are
registered trademarks of Silicon Graphics, Inc., in the United