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

Add trademark symbols:

Browse source 
- Add trademark tags for all trademarks now that the stylesheet
   handles it right.
 - Always use correct case for trademarks.
 - Don't join trademarks with other words, e.g. using hyphens.
This commit is contained in:
Simon L. B. Nielsen 2003-08-20 22:38:04 +00:00
parent be40faddd2
commit d122695827
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=17942
5 changed files with 51 additions and 51 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

32
en_US.ISO8859-1/books/handbook/basics/chapter.sgml
View file

@ -16,7 +16,7 @@
<!-- 10 Mar 2000 -->
</chapterinfo>
<title>Unix Basics</title>
<title>UNIX Basics</title>
<sect1 id="basics-synopsis">
<title>Synopsis</title>
@ -25,7 +25,7 @@
<para>The following chapter will cover the basic commands and
functionality of the FreeBSD operating system. Much of this
material is relevant for any Unix-like operating system. Feel
material is relevant for any &unix; like operating system. Feel
free to skim over this chapter if you are familiar with the
material. If you are new to FreeBSD, then you will definitely
want to read through this chapter carefully.</para>
@ -34,7 +34,7 @@
<itemizedlist>
<listitem>
<para>How Unix file permissions work.</para>
<para>How &unix; file permissions work.</para>
</listitem>
<listitem>
<para>What processes, daemons, and signals are.</para>
@ -59,10 +59,10 @@
<sect1 id="permissions">
<title>Permissions</title>
<indexterm><primary>Unix</primary></indexterm>
<indexterm><primary>UNIX</primary></indexterm>
<para>FreeBSD, being a direct descendant of BSD Unix, is based on
several key Unix concepts. The first, and
<para>FreeBSD, being a direct descendant of BSD &unix;, is based on
several key &unix; concepts. The first, and
most pronounced, is that FreeBSD is a multi-user operating system.
The system can handle several users all working simultaneously on
completely unrelated tasks. The system is responsible for properly
@ -974,7 +974,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
taken by the process. This is split into two columns, one for total
size, and one for resident size&mdash;total size is how much memory the
application has needed, and the resident size is how much it is actually
using at the moment. In this example you can see that <application>Netscape</application> has
using at the moment. In this example you can see that <application>&netscape;</application> has
required almost 30&nbsp;MB of RAM, but is currently only using 9&nbsp;MB.</para>
<para>&man.top.1; automatically updates this display every two seconds;
@ -1112,7 +1112,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
<prompt>Password:</prompt>
&prompt.root; <userinput>/bin/kill -s HUP 198</userinput></screen>
<para>In common with most Unix commands, &man.kill.1; will not print any
<para>In common with most &unix; commands, &man.kill.1; will not print any
output if it is successful. If you send a signal to a
process that you do not own then you will see <errorname>kill:
<replaceable>PID</replaceable>: Operation not
@ -1170,7 +1170,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
<para>Which shell do you use? It is really a matter of taste. If you
are a C programmer you might feel more comfortable with a C-like shell
such as <command>tcsh</command>. If you have come from Linux or are new
to a Unix command line interface you might try <command>bash</command>.
to a &unix; command line interface you might try <command>bash</command>.
The point is that each
shell has unique properties that may or may not work with your
preferred working environment, and that you have a choice of what
@ -1430,7 +1430,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
first IDE CDROM drive, while <devicename>kbd0</devicename>
represents the keyboard.</para>
<para>Most of these devices in a Unix operating system must be
<para>Most of these devices in a &unix; operating system must be
accessed through special files called device nodes, which are
located in the <filename>/dev</filename> directory.</para>
@ -1538,7 +1538,7 @@ login:</screen>
<para>Every multiuser system needs some way to distinguish one
<quote>user</quote> from the rest. In FreeBSD (and all the
&unix;-like operating systems), this is accomplished by requiring that
&unix; like operating systems), this is accomplished by requiring that
every user must <quote>log into</quote> the system before being able
to run programs. Every user has a unique name (the
<quote>username</quote>) and a personal, secret key (the
@ -1690,13 +1690,13 @@ console none unknown off secure</programlisting>
<para>To understand why FreeBSD uses the <acronym>ELF</acronym>
format, you must first know a little about the 3 currently
<quote>dominant</quote> executable formats for Unix:</para>
<quote>dominant</quote> executable formats for &unix;:</para>
<itemizedlist>
<listitem>
<para>&man.a.out.5;</para>
<para>The oldest and <quote>classic</quote> Unix object
<para>The oldest and <quote>classic</quote> &unix; object
format. It uses a short and compact header with a magic
number at the beginning that is often used to characterize
the format (see &man.a.out.5; for more details). It
@ -1750,7 +1750,7 @@ console none unknown off secure</programlisting>
forward</quote> anyway, the migration cost was accepted as
necessary and the transition made. FreeBSD's shared library
mechanism is based more closely on Sun's
SunOS-style shared library mechanism
&sunos; style shared library mechanism
and, as such, is very easy to use.</para>
<para>So, why are there so many different formats?</para>
@ -1758,9 +1758,9 @@ console none unknown off secure</programlisting>
<para>Back in the dim, dark past, there was simple hardware. This
simple hardware supported a simple, small system. <filename>a.out</filename> was
completely adequate for the job of representing binaries on this
simple system (a PDP-11). As people ported Unix from this simple
simple system (a PDP-11). As people ported &unix; from this simple
system, they retained the <filename>a.out</filename> format because it was sufficient
for the early ports of Unix to architectures like the Motorola
for the early ports of &unix; to architectures like the Motorola
68k, VAXen, etc.</para>
<para>Then some bright hardware engineer decided that if he could

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

@ -161,7 +161,7 @@
</listitem>
<listitem>
<para>Introduce you to X, the UNIX windowing system, and
<para>Introduce you to X, the &unix; windowing system, and
detail how to configure a desktop environment that makes you
more productive.</para>
</listitem>

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

@ -237,7 +237,7 @@
<para>In general, each operating system that you use will identify
partitions in a particular way. For example, DOS, and its
descendants, like Windows, assign each primary and logical partition a
descendants, like &windows;, assign each primary and logical partition a
<firstterm>drive letter</firstterm>, starting with
<devicename>C:</devicename>.</para>
@ -252,7 +252,7 @@
<para>If you are already using all the partitions on all your disks, then
you will have to free one of them for FreeBSD using the tools
provided by the other operating systems you use (e.g.,
<command>fdisk</command> on DOS or Windows).</para>
<command>fdisk</command> on DOS or &windows;).</para>
<para>If you have a spare partition then you can use that. However, you
may need to shrink one or more of your existing partitions
@ -283,7 +283,7 @@
<title>Using an Existing Partition Unchanged</title>
<para>Suppose that you have a computer with a single 4&nbsp;GB disk that
already has a version of Windows installed, and you have split the
already has a version of &windows; installed, and you have split the
disk into two drive letters, <devicename>C:</devicename> and
<devicename>D:</devicename>, each of which is 2&nbsp;GB in size. You have
1&nbsp;GB of data on <devicename>C:</devicename>, and 0.5&nbsp;GB of data on
@ -299,8 +299,8 @@
<title>Shrinking an Existing Partition</title>
<para>Suppose that you have a computer with a single 4&nbsp;GB disk that
already has a version of Windows installed. When you installed
Windows you created one large partition, giving you a
already has a version of &windows; installed. When you installed
&windows; you created one large partition, giving you a
<devicename>C:</devicename> drive that is 4&nbsp;GB in size. You are
currently using 1.5&nbsp;GB of space, and want FreeBSD to have 2&nbsp;GB of
space.</para>
@ -309,13 +309,13 @@
<orderedlist>
<listitem>
<para>Backup your Windows data, and then reinstall Windows,
<para>Backup your &windows; data, and then reinstall &windows;,
asking for a 2&nbsp;GB partition at install time.</para>
</listitem>
<listitem>
<para>Use one of the tools such as <application>PartitionMagic</application>,
described above, to shrink your Windows
<para>Use one of the tools such as <application>&partitionmagic;</application>,
described above, to shrink your &windows;
partition.</para>
</listitem>
</orderedlist>
@ -545,7 +545,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
in the <filename>floppies/</filename> directory, and
can also be downloaded from the <ulink
url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">
floppies directory</ulink> for the i386 architecture and from this <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/&rel.current;-RELEASE/floppies/">floppies directory</ulink> for the Alpha architecture.</para>
floppies directory</ulink> for the &i386; architecture and from this <ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/alpha/&rel.current;-RELEASE/floppies/">floppies directory</ulink> for the Alpha architecture.</para>
<para>The floppy images have a <filename>.flp</filename> extension.
The <filename>floppies/</filename> directory contains a number of
@ -598,7 +598,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<indexterm><primary>DOS</primary></indexterm>
<para>If you are creating the floppies on a computer running
DOS/Windows, then we provide a tool to do
DOS/&windows;, then we provide a tool to do
this called <command>fdimage</command>.</para>
<para>If you are using the floppies from the CDROM, and your
@ -627,7 +627,7 @@ pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
<para>On FreeBSD, <filename>/dev/fd0</filename> refers to the
first floppy disk (the <devicename>A:</devicename> drive).
<filename>/dev/fd1</filename> would be the
<devicename>B:</devicename> drive, and so on. Other UNIX
<devicename>B:</devicename> drive, and so on. Other &unix;
variants might have different names for the floppy disk
devices, and you will need to check the documentation for the
system as necessary.</para>
@ -1865,7 +1865,7 @@ Mounting root from ufs:/dev/md0c
<para>Each partition-that-contains-a-filesystem is stored in what
FreeBSD calls a <firstterm>slice</firstterm>. Slice is FreeBSD's term
for what were earlier called partitions, and again, this is because of
FreeBSD's UNIX background. Slices are numbered, starting at 1,
FreeBSD's &unix; background. Slices are numbered, starting at 1,
through to 4.</para>
<indexterm><primary>slices</primary></indexterm>
@ -2147,8 +2147,8 @@ Mounting root from ufs:/dev/md0c
gives them, and their description and sub-type. This example shows two
small unused slices, which are artifacts of disk layout schemes on the
PC. It also shows one large FAT slice, which almost certainly appears
as <devicename>C:</devicename> in DOS / Windows, and an extended
slice, which may contain other drive letters for DOS / Windows.</para>
as <devicename>C:</devicename> in DOS / &windows;, and an extended
slice, which may contain other drive letters for DOS / &windows;.</para>
<para>The third section shows the commands that are available in
<application>FDisk</application>.</para>
@ -4714,7 +4714,7 @@ failed. Would you like to try again?
<title>FreeBSD Bootup</title>
<sect3 id="freebsdboot-i386">
<title>FreeBSD Bootup on the i386</title>
<title>FreeBSD Bootup on the &i386;</title>
<para>If everything went well, you will see messages scroll
off the screen and you will arrive at a login prompt. You can view
@ -4891,7 +4891,7 @@ Password:</screen>
<prompt>&gt;&gt;&gt;</prompt> <userinput>SET AUTO_ACTION BOOT</userinput></screen>
<para>The boot messages will be similar (but not identical) to
those produced by FreeBSD booting on the i386.</para>
those produced by FreeBSD booting on the &i386;.</para>
</sect3>
</sect2>
@ -5041,7 +5041,7 @@ Please press any key to reboot.</screen>
</sect2>
<sect2>
<title>Dealing with Existing MS-DOS Partitions</title>
<title>Dealing with Existing &ms-dos; Partitions</title>
<indexterm><primary>DOS</primary></indexterm>
<para>Many users wish to install &os; on <acronym>PC</acronym>s inhabited by
@ -5053,7 +5053,7 @@ Please press any key to reboot.</screen>
<para>The <application>FIPS</application> utility allows you to split an
existing &ms-dos; partition into two pieces, preserving the original
partition and allowing you to install onto the second free piece.
You first need to defragment your MS-DOS partition using the &windows;;
You first need to defragment your &ms-dos; partition using the &windows;;
<application>Disk Defragmenter</application> utility (go into Explorer, right-click on
the hard drive, and choose to defrag your hard drive), or use
<application>Norton Disk Tools</application>. Now you can run the
@ -5073,7 +5073,7 @@ Please press any key to reboot.</screen>
</sect2>
<sect2>
<title>Using MS-DOS File Systems</title>
<title>Using &ms-dos; File Systems</title>
<para>At this time, &os; does not support file systems compressed with the
<application>Double Space&trade;</application> application. Therefore the file
@ -5082,22 +5082,22 @@ Please press any key to reboot.</screen>
located in the <guimenuitem>Start</guimenuitem>&gt; <guimenuitem>Programs</guimenuitem> &gt;
<guimenuitem>System Tools</guimenuitem> menu.</para>
<para>&os; can support MS-DOS based file systems. This requires you use
<para>&os; can support &ms-dos; based file systems. This requires you use
the &man.mount.msdos.8; command (in &os; 5.X, the command is &man.mount.msdosfs.8;)
with the required parameters. The utilities most common usage is:</para>
<screen>&prompt.root; <userinput>mount_msdos /dev/ad0s1 /mnt</userinput></screen>
<para>In this example, the MS-DOS file system is located on the first partition of
<para>In this example, the &ms-dos; file system is located on the first partition of
the primary hard disk. Your situation may be different, check the output from
the <command>dmesg</command>, and <command>mount</command> commands. They should
produce enough information too give an idea of the partition layout.</para>
<note><para>Extended MS-DOS file systems are usually mapped after the &os;
<note><para>Extended &ms-dos; file systems are usually mapped after the &os;
partitions. In other words, the slice number may be higher than the ones
&os; is using. For instance, the first MS-DOS partition may be
&os; is using. For instance, the first &ms-dos; partition may be
<filename>/dev/ad0s1</filename>, the &os; partition may be
<filename>/dev/ad0s2</filename>, with the extended MS-DOS partition being
<filename>/dev/ad0s2</filename>, with the extended &ms-dos; partition being
located on <filename>/dev/ad0s3</filename>. To some, this can be confusing
at first.</para></note>
</sect2>
@ -5250,7 +5250,7 @@ Please press any key to reboot.</screen>
<para>On FreeBSD <filename>/dev/fd0</filename> refers to
the first floppy disk (the <devicename>A:</devicename>
drive). <filename>/dev/fd1</filename> would be the
<devicename>B:</devicename> drive, and so on. Other UNIX
<devicename>B:</devicename> drive, and so on. Other &unix;
variants might have different names for the floppy disk
devices, and you will need to check the documentation for
the system as necessary.</para>
@ -5570,8 +5570,8 @@ Please press any key to reboot.</screen>
as it takes to hold all the files in the
<filename>bin</filename> (binary distribution) directory. If
you are preparing the floppies from DOS, then they
<emphasis>MUST</emphasis> be formatted using the MS-DOS
<command>FORMAT</command> command. If you are using Windows,
<emphasis>MUST</emphasis> be formatted using the &ms-dos;
<command>FORMAT</command> command. If you are using &windows;,
use Explorer to format the disks (right-click on the
<devicename>A:</devicename> drive, and select <quote>Format</quote>.</para>
@ -5617,13 +5617,13 @@ Please press any key to reboot.</screen>
</sect2>
<sect2 id="install-msdos">
<title>Installing from an MS-DOS Partition</title>
<title>Installing from an &ms-dos; Partition</title>
<indexterm>
<primary>installation</primary>
<secondary>from MS-DOS</secondary>
</indexterm>
<para>To prepare for an installation from an MS-DOS partition,
<para>To prepare for an installation from an &ms-dos; partition,
copy the files from the distribution into a directory
called <filename>freebsd</filename> in the root directory of the
partition. For example, <filename>c:\freebsd</filename>. The
@ -5656,7 +5656,7 @@ Please press any key to reboot.</screen>
versions.</para>
</note>
<para>For as many distributions you wish to install from an MS-DOS
<para>For as many distributions you wish to install from an &ms-dos;
partition (and you have the free space for), install each one
under <filename>c:\freebsd</filename> &mdash; the
<literal>BIN</literal> distribution is the only one required for
@ -5733,7 +5733,7 @@ Please press any key to reboot.</screen>
early in the installation process.</para>
<para>If you use PAP or CHAP to connect your ISP (in other words, if
you can connect to the ISP in Windows without using a script), then
you can connect to the ISP in &windows; without using a script), then
all you will need to do is type in <command>dial</command> at the
<application>ppp</application> prompt. Otherwise, you will need to
know how to dial your ISP using the <quote>AT commands</quote>

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

@ -109,7 +109,7 @@
<listitem>
<para>FreeBSD is a <emphasis>32-bit</emphasis> operating
system (<emphasis>64-bit</emphasis> on the Alpha and UltraSparc) and was
system (<emphasis>64-bit</emphasis> on the Alpha and &ultrasparc;) and was
designed as such from the ground up.</para>
</listitem>
@ -242,7 +242,7 @@
limited only by your own imagination. From software development
to factory automation, inventory control to azimuth correction of
remote satellite antennae; if it can be done with a commercial
UNIX product then it is more than likely that you can do it with
&unix; product then it is more than likely that you can do it with
FreeBSD too! FreeBSD also benefits significantly from
literally thousands of high quality applications developed by
research centers and universities around the world, often

2
en_US.ISO8859-1/books/handbook/ports/chapter.sgml
View file

@ -48,7 +48,7 @@
<sect1 id="ports-overview">
<title>Overview of Software Installation</title>
<para>If you have used a Unix system before you will know that the typical
<para>If you have used a &unix; system before you will know that the typical
procedure for installing third party software goes something like
this:</para>