Standardize capitalization of titles:
* First and last word uppercase * Prepositions, articles, and short conjunctions lowercase * The word 'to' lowercase * Preserved capitalization for program/command names Reviewed by: murray
This commit is contained in:
parent
8a69086f5f
commit
205cf1b49a
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=10298
22 changed files with 301 additions and 302 deletions
en_US.ISO8859-1
articles/contributing
books/handbook
advanced-networking
backups
basics
boot
config
contrib
cutting-edge
disks
install
introduction
kernelopts
l10n
linuxemu
mail
mirrors
ports
ppp-and-slip
security
serialcomms
users
x11
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.465 2001/08/08 17:29:39 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.466 2001/08/09 23:42:30 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="contrib">
|
||||
|
@ -50,7 +50,7 @@
|
|||
to at least give it a second look.</para>
|
||||
|
||||
<sect1 id="contrib-what">
|
||||
<title>What is Needed</title>
|
||||
<title>What Is Needed</title>
|
||||
|
||||
<para>The following list of tasks and sub-projects represents something of
|
||||
an amalgam of the various core team <filename>TODO</filename> lists and
|
||||
|
@ -61,7 +61,7 @@
|
|||
been appointed, maybe you would like to volunteer?</para>
|
||||
|
||||
<sect2>
|
||||
<title>Ongoing tasks</title>
|
||||
<title>Ongoing Tasks</title>
|
||||
|
||||
<para>Most of the tasks listed in the previous sections require either a
|
||||
considerable investment of time or an in-depth knowledge of the
|
||||
|
@ -150,7 +150,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Work through the PR database</title>
|
||||
<title>Work through the PR Database</title>
|
||||
|
||||
<indexterm><primary>problem reports database</primary></indexterm>
|
||||
<para>The <ulink
|
||||
|
@ -177,7 +177,7 @@
|
|||
following 6 categories:</para>
|
||||
|
||||
<sect2 id="contrib-general">
|
||||
<title>Bug reports and general commentary</title>
|
||||
<title>Bug Reports and General Commentary</title>
|
||||
|
||||
<para>An idea or suggestion of <emphasis>general</emphasis> technical
|
||||
interest should be mailed to the &a.hackers;. Likewise, people with
|
||||
|
@ -212,7 +212,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes to the documentation</title>
|
||||
<title>Changes to the Documentation</title>
|
||||
|
||||
<indexterm><primary>documentation submissions</primary></indexterm>
|
||||
<para>Changes to the documentation are overseen by the &a.doc;. Send
|
||||
|
@ -223,7 +223,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes to existing source code</title>
|
||||
<title>Changes to Existing Source Code</title>
|
||||
|
||||
<indexterm><primary>FreeBSD-current</primary></indexterm>
|
||||
<para>An addition or change to the existing source code is a somewhat
|
||||
|
@ -295,7 +295,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>New code or major value-added packages</title>
|
||||
<title>New Code or Major Value-Added Packages</title>
|
||||
|
||||
<para>In the case of a significant contribution of a large body
|
||||
work, or the addition of an important new feature to FreeBSD, it
|
||||
|
@ -381,7 +381,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Money, Hardware or Internet access</title>
|
||||
<title>Money, Hardware or Internet Access</title>
|
||||
|
||||
<para>We are always very happy to accept donations to further the cause
|
||||
of the FreeBSD Project and, in a volunteer effort like ours, a little
|
||||
|
@ -390,7 +390,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
the funds to buy such items ourselves.</para>
|
||||
|
||||
<sect3>
|
||||
<title><anchor id="donations">Donating funds</title>
|
||||
<title><anchor id="donations">Donating Funds</title>
|
||||
|
||||
<para>The FreeBSD Foundation is a non-profit, tax-exempt
|
||||
foundation established to further the goals of the FreeBSD
|
||||
|
@ -418,7 +418,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Donating hardware</title>
|
||||
<title>Donating Hardware</title>
|
||||
<indexterm><primary>donations</primary></indexterm>
|
||||
|
||||
<para>Donations of hardware in any of the 3 following categories are
|
||||
|
@ -453,7 +453,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Donating Internet access</title>
|
||||
<title>Donating Internet Access</title>
|
||||
|
||||
<para>We can always use new mirror sites for FTP, WWW or
|
||||
<command>cvsup</command>. If you would like to be such a mirror,
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.76 2001/08/10 00:14:55 logo Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.77 2001/08/10 01:06:45 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="advanced-networking">
|
||||
|
@ -44,7 +44,7 @@
|
|||
<quote>links</quote>), and Ethernet hardware addresses.</para>
|
||||
|
||||
<sect2>
|
||||
<title>An example</title>
|
||||
<title>An Example</title>
|
||||
|
||||
<para>To illustrate different aspects of routing, we will use the
|
||||
following example which is the output of the command <command>netstat
|
||||
|
@ -178,7 +178,7 @@ host2.foobar.com link#1 UC 0 0
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Default routes</title>
|
||||
<title>Default Routes</title>
|
||||
|
||||
<indexterm><primary>default route</primary></indexterm>
|
||||
<para>When the local system needs to make a connection to remote host,
|
||||
|
@ -266,7 +266,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Dual homed hosts</title>
|
||||
<title>Dual Homed Hosts</title>
|
||||
<indexterm><primary>dual homed hosts</primary></indexterm>
|
||||
<para>There is one other type of configuration that we should cover, and
|
||||
that is a host that sits on two different networks. Technically, any
|
||||
|
@ -291,7 +291,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Routing propagation</title>
|
||||
<title>Routing Propagation</title>
|
||||
<indexterm><primary>routing propogation</primary></indexterm>
|
||||
<para>We have already talked about how we define our routes to the
|
||||
outside world, but not about how the outside world finds us.</para>
|
||||
|
@ -376,13 +376,13 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Situations where bridging is appropriate</title>
|
||||
<title>Situations Where Bridging Is Appropriate</title>
|
||||
|
||||
<para>There are two common situations in which a bridge is used
|
||||
today.</para>
|
||||
|
||||
<sect3>
|
||||
<title>High traffic on a segment</title>
|
||||
<title>High Traffic on a Segment</title>
|
||||
|
||||
<para>Situation one is where your physical network segment is
|
||||
overloaded with traffic, but you don't want for whatever reason to
|
||||
|
@ -404,7 +404,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Filtering/traffic shaping firewall</title>
|
||||
<title>Filtering/Traffic Shaping Firewall</title>
|
||||
<indexterm><primary>firewall</primary></indexterm>
|
||||
<indexterm><primary>IP Masquerading</primary></indexterm>
|
||||
|
||||
|
@ -427,10 +427,10 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Configuring a bridge</title>
|
||||
<title>Configuring a Bridge</title>
|
||||
|
||||
<sect3>
|
||||
<title>Network interface card selection</title>
|
||||
<title>Network Interface Card Selection</title>
|
||||
|
||||
<para>A bridge requires at least two network cards to function.
|
||||
Unfortunately, not all network interface cards as of FreeBSD 4.0
|
||||
|
@ -441,7 +441,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Kernel configuration changes</title>
|
||||
<title>Kernel Configuration Changes</title>
|
||||
<indexterm><primary>kernel configuration</primary></indexterm>
|
||||
<indexterm>
|
||||
<primary>kernel configuration</primary>
|
||||
|
@ -457,7 +457,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Firewall support</title>
|
||||
<title>Firewall Support</title>
|
||||
<indexterm><primary>firewall</primary></indexterm>
|
||||
<para>If you are planning to use the bridge as a firewall, you will
|
||||
need to add the <varname>IPFIREWALL</varname> option as well. Read <xref
|
||||
|
@ -474,7 +474,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Traffic shaping support</title>
|
||||
<title>Traffic Shaping Support</title>
|
||||
|
||||
<para>If you want to use the bridge as a traffic shaper, you will need
|
||||
to add the <literal>DUMMYNET</literal> option to your kernel
|
||||
|
@ -484,7 +484,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Enabling the bridge</title>
|
||||
<title>Enabling the Bridge</title>
|
||||
|
||||
<para>Add the line</para>
|
||||
|
||||
|
@ -511,7 +511,7 @@ Local1 (10.20.30.1, 10.9.9.30) --> T1-GW (10.9.9.1)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Other information</title>
|
||||
<title>Other Information</title>
|
||||
|
||||
<para>If you want to be able to telnet into the bridge from the network,
|
||||
it is OK to assign one of the network cards an IP address. The
|
||||
|
@ -868,7 +868,7 @@ nfs_client_flags="-n 4"</programlisting>
|
|||
</author>
|
||||
</authorgroup>
|
||||
</sect2info>
|
||||
<title>Problems integrating with other systems</title>
|
||||
<title>Problems Integrating with Other Systems</title>
|
||||
|
||||
<para>Certain Ethernet adapters for ISA PC systems have limitations
|
||||
which can lead to serious network problems, particularly with NFS.
|
||||
|
@ -1212,7 +1212,7 @@ hostname myclient.mydomain</programlisting>
|
|||
|
||||
<sect2>
|
||||
<title>Using Shared <filename>/</filename> and <filename>/usr</filename>
|
||||
filesystems</title>
|
||||
Filesystems</title>
|
||||
|
||||
<para>Although this is not an officially sanctioned or supported way
|
||||
of doing this, some people report that it works quite well. If
|
||||
|
@ -1221,7 +1221,7 @@ hostname myclient.mydomain</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Compiling netboot for specific setups</title>
|
||||
<title>Compiling Netboot for Specific Setups</title>
|
||||
|
||||
<para>Netboot can be compiled to support NE1000/2000 cards by changing
|
||||
the configuration in
|
||||
|
@ -1440,7 +1440,7 @@ hostname myclient.mydomain</programlisting>
|
|||
used.</para>
|
||||
|
||||
<example>
|
||||
<title>Branch office or Home network</title>
|
||||
<title>Branch Office or Home Network</title>
|
||||
|
||||
<indexterm><primary>10 base 2</primary></indexterm>
|
||||
<para>Network uses a bus based topology with 10 base 2
|
||||
|
@ -1475,7 +1475,7 @@ ISDN BRI line</literallayout>
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Head office or other LAN</title>
|
||||
<title>Head Office or Other LAN</title>
|
||||
|
||||
<indexterm><primary>10 base T</primary></indexterm>
|
||||
<para>Network uses a star topology with 10 base T Ethernet
|
||||
|
@ -1553,7 +1553,7 @@ ISDN BRI line</literallayout>
|
|||
<title>NIS/YP</title>
|
||||
|
||||
<sect2>
|
||||
<title>What is it?</title>
|
||||
<title>What Is It?</title>
|
||||
<indexterm><primary>NIS</primary></indexterm>
|
||||
<indexterm><primary>Solaris</primary></indexterm>
|
||||
<indexterm><primary>HP-UX</primary></indexterm>
|
||||
|
@ -1590,7 +1590,7 @@ ISDN BRI line</literallayout>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Terms/processes you should know</title>
|
||||
<title>Terms/Processes You Should Know</title>
|
||||
|
||||
<para>There are several terms and several important user processes
|
||||
that you will come across when
|
||||
|
@ -1652,7 +1652,7 @@ ISDN BRI line</literallayout>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How does it work?</title>
|
||||
<title>How Does It Work?</title>
|
||||
|
||||
<para>There are three types of hosts in an NIS environment; master
|
||||
servers, slave servers, and clients. Servers act as a central
|
||||
|
@ -1669,7 +1669,7 @@ ISDN BRI line</literallayout>
|
|||
server it is bound to, to get this information.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Machine types</title>
|
||||
<title>Machine Types</title>
|
||||
|
||||
<itemizedlist>
|
||||
<indexterm>
|
||||
|
@ -1866,7 +1866,7 @@ ISDN BRI line</literallayout>
|
|||
database back to the client.</para>
|
||||
|
||||
<sect4>
|
||||
<title>Setting up a NIS master server</title>
|
||||
<title>Setting Up a NIS Master Server</title>
|
||||
<indexterm>
|
||||
<primary>NIS</primary>
|
||||
<secondary>server configuration</secondary>
|
||||
|
@ -1904,7 +1904,7 @@ ISDN BRI line</literallayout>
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Initializing the NIS maps</title>
|
||||
<title>Initializing the NIS Maps</title>
|
||||
<indexterm>
|
||||
<primary>NIS</primary>
|
||||
<secondary>maps</secondary>
|
||||
|
@ -1987,7 +1987,7 @@ ellington has been setup as an YP master server without any errors.</screen>
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Setting up a NIS slave server</title>
|
||||
<title>Setting up a NIS Slave Server</title>
|
||||
<indexterm>
|
||||
<primary>NIS</primary>
|
||||
<secondary>configuring a slave server</secondary>
|
||||
|
@ -2110,7 +2110,7 @@ Don't forget to update map ypservers on ellington.</screen>
|
|||
server.</para>
|
||||
|
||||
<sect4>
|
||||
<title>Setting up an NIS client</title>
|
||||
<title>Setting Up an NIS Client</title>
|
||||
<indexterm>
|
||||
<primary>NIS</primary>
|
||||
<secondary>client configuration</secondary>
|
||||
|
@ -2241,7 +2241,7 @@ nis_client_enable="YES"</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Barring some users from logging on</title>
|
||||
<title>Barring Some Users from Logging On</title>
|
||||
|
||||
<para>In our lab, there is a machine <hostid>basie</hostid> that is
|
||||
supposed to be a faculty only workstation. We don't want to take this
|
||||
|
@ -2303,7 +2303,7 @@ basie&prompt.root;</screen>
|
|||
</authorgroup>
|
||||
</sect2info>
|
||||
|
||||
<title>Using netgroups</title>
|
||||
<title>Using Netgroups</title>
|
||||
<indexterm><primary>netgroups</primary></indexterm>
|
||||
|
||||
<para>The method shown in the previous chapter works reasonably
|
||||
|
@ -2692,7 +2692,7 @@ TWO (,hotel,test-domain)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Important things to remember</title>
|
||||
<title>Important Things to Remember</title>
|
||||
|
||||
<para>There are still a couple of things that you will need to do
|
||||
differently now that you are in an NIS environment.</para>
|
||||
|
@ -2736,7 +2736,7 @@ TWO (,hotel,test-domain)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>NIS v1 compatibility</title>
|
||||
<title>NIS v1 Compatibility</title>
|
||||
|
||||
<para> FreeBSD's <application>ypserv</application> has some support
|
||||
for serving NIS v1 clients. FreeBSD's NIS implementation only
|
||||
|
@ -2755,7 +2755,7 @@ TWO (,hotel,test-domain)
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>NIS servers that are also NIS clients</title>
|
||||
<title>NIS Servers that are also NIS Clients</title>
|
||||
|
||||
<para> Care must be taken when running ypserv in a multi-server
|
||||
domain where the server machines are also NIS clients. It is
|
||||
|
@ -2831,7 +2831,7 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
|
|||
<title>DHCP</title>
|
||||
|
||||
<sect2>
|
||||
<title>What is DHCP?</title>
|
||||
<title>What Is DHCP?</title>
|
||||
<indexterm>
|
||||
<primary>Dynamic Host Configuration Protocol</primary>
|
||||
<see>DHCP</see>
|
||||
|
@ -2849,7 +2849,7 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>What This Section Covers</title>
|
||||
<title>What this Section Covers</title>
|
||||
|
||||
<para>This handbook section attempts to describe only the parts
|
||||
of the DHCP system that are integrated with FreeBSD;
|
||||
|
@ -2859,7 +2859,7 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 libscrypt.so@ -> libscrypt.so.2
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How it Works</title>
|
||||
<title>How It Works</title>
|
||||
<indexterm><primary>UDP</primary></indexterm>
|
||||
<para>When dhclient, the DHCP client, is executed on the client
|
||||
machine, it begins broadcasting requests for configuration
|
||||
|
@ -3169,7 +3169,7 @@ dhcp_flags=""</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Reasons to run a name server</title>
|
||||
<title>Reasons to Run a Name Server</title>
|
||||
|
||||
<para>Name servers usually come in two forms: an authoritative
|
||||
name server, and a caching nameserver.</para>
|
||||
|
@ -3220,7 +3220,7 @@ dhcp_flags=""</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How it works</title>
|
||||
<title>How It Works</title>
|
||||
<para>In FreeBSD, the BIND daemon is called
|
||||
<application>named</application> for obvious reasons.</para>
|
||||
|
||||
|
@ -3285,7 +3285,7 @@ dhcp_flags=""</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Configuration files</title>
|
||||
<title>Configuration Files</title>
|
||||
<indexterm>
|
||||
<primary>BIND</primary>
|
||||
<secondary>configuration files</secondary>
|
||||
|
@ -3474,7 +3474,7 @@ zone "0.168.192.in-addr.arpa" {
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Zone files</title>
|
||||
<title>Zone Files</title>
|
||||
<para>
|
||||
An example master zone file for <hostid>foobardomain.org</hostid>
|
||||
(existing within <filename>/etc/namedb/foobardomain.org</filename>)
|
||||
|
@ -3826,7 +3826,7 @@ www IN CNAME @</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How to use the nameserver</title>
|
||||
<title>How to Use the Name Server</title>
|
||||
|
||||
<para>If setup properly, the nameserver should be accessible through
|
||||
the network and locally. <filename>/etc/resolv.conf</filename> must
|
||||
|
@ -3910,7 +3910,7 @@ www IN CNAME @</programlisting>
|
|||
</author>
|
||||
</authorgroup>
|
||||
</sect1info>
|
||||
<title>Network Address Translation daemon (natd)</title>
|
||||
<title>Network Address Translation</title>
|
||||
|
||||
<sect2 id="overview">
|
||||
<title>Overview</title>
|
||||
|
@ -4344,7 +4344,7 @@ natd_flags=""</programlisting>
|
|||
<application>inetd</application> process as shown:</para>
|
||||
|
||||
<example id="inetd-hangup">
|
||||
<title>Sending <application>inetd</application> a HangUP signal</title>
|
||||
<title>Sending <application>inetd</application> a HangUP Signal</title>
|
||||
|
||||
<screen>&prompt.root kill -HUP `cat /var/run/inetd.pid`</screen>
|
||||
</example>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.38 2001/07/28 04:06:29 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/backups/chapter.sgml,v 1.39 2001/08/06 22:59:23 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="backups">
|
||||
|
@ -412,7 +412,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Do nothing</title>
|
||||
<title>Do Nothing</title>
|
||||
|
||||
<para><quote>Do nothing</quote> is not a computer program, but it is the
|
||||
most widely used backup strategy. There are no initial costs. There
|
||||
|
@ -435,7 +435,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Which Backup Program is Best?</title>
|
||||
<title>Which Backup Program Is Best?</title>
|
||||
<indexterm>
|
||||
<primary>LISA</primary>
|
||||
</indexterm>
|
||||
|
@ -513,7 +513,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
your computers and disk drives by a significant distance.</para>
|
||||
|
||||
<example>
|
||||
<title>A script for creating a bootable floppy</title>
|
||||
<title>A Script for Creating a Bootable Floppy</title>
|
||||
|
||||
<programlisting><![ CDATA [#!/bin/sh
|
||||
#
|
||||
|
@ -739,10 +739,10 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
|
|||
</sect1>
|
||||
|
||||
<sect1 id="backups-floppybackups">
|
||||
<title>What about Backups to Floppies?</title>
|
||||
<title>What About Backups to Floppies?</title>
|
||||
|
||||
<sect2 id="floppies-using">
|
||||
<title>Can I use floppies for backing up my data?</title>
|
||||
<title>Can I Use floppies for Backing Up My Data?</title>
|
||||
<indexterm><primary>backup floppies</primary></indexterm>
|
||||
<indexterm><primary>floppy disks</primary></indexterm>
|
||||
|
||||
|
@ -776,7 +776,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="floppies-creating">
|
||||
<title>So how do I backup my data to floppies?</title>
|
||||
<title>So How Do I Backup My Data to Floppies?</title>
|
||||
|
||||
<para>The best way to backup to floppy disk is to use
|
||||
&man.tar.1; with the <option>-M</option> (multi volume) option, which
|
||||
|
@ -798,7 +798,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="floppies-compress">
|
||||
<title>Can I compress my backups?</title>
|
||||
<title>Can I Compress My Backups?</title>
|
||||
<indexterm>
|
||||
<primary><command>tar</command></primary>
|
||||
</indexterm>
|
||||
|
@ -814,7 +814,7 @@ echo "The floppy has been unmounted and is now ready."]]></programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="floppies-restoring">
|
||||
<title>How do I restore my backups?</title>
|
||||
<title>How Do I Restore My Backups?</title>
|
||||
|
||||
<para>To restore the entire archive use:</para>
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.36 2001/08/06 21:25:27 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/basics/chapter.sgml,v 1.37 2001/08/09 23:42:29 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="basics">
|
||||
|
@ -313,7 +313,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
|
|||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Daemons, signals, and killing processes</title>
|
||||
<title>Daemons, Signals, and Killing Processes</title>
|
||||
|
||||
<para>When you run an editor it is easy to control the editor, tell it to
|
||||
load files, and so on. You can do this because the editor provides
|
||||
|
@ -408,7 +408,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
|
|||
shows.</para>
|
||||
|
||||
<procedure>
|
||||
<title>Sending a signal to a process</title>
|
||||
<title>Sending a Signal to a Process</title>
|
||||
|
||||
<para>This example shows how to send a signal to &man.inetd.8;. The
|
||||
&man.inetd.8; configuration file is
|
||||
|
@ -453,7 +453,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
|
|||
<replaceable>PID</replaceable>: No such process</errorname>.</para>
|
||||
|
||||
<note>
|
||||
<title>Why use <command>/bin/kill</command>?</title>
|
||||
<title>Why Use <command>/bin/kill</command>?</title>
|
||||
|
||||
<para>Many shells provide the <command>kill</command> command as a
|
||||
built in command; that is, the shell will send the signal
|
||||
|
@ -652,7 +652,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
|
|||
is.</para>
|
||||
|
||||
<sect2 id="changing-shells">
|
||||
<title>Changing your shell</title>
|
||||
<title>Changing Your Shell</title>
|
||||
|
||||
<para>The easiest way to change your shell is to use the
|
||||
<command>chsh</command> command. Running <command>chsh</command> will
|
||||
|
@ -750,7 +750,7 @@ Swap: 256M Total, 38M Used, 217M Free, 15% Inuse
|
|||
<title>For More Information...</title>
|
||||
|
||||
<sect2 id="basics-man">
|
||||
<title>Manual pages</title>
|
||||
<title>Manual Pages</title>
|
||||
<indexterm><primary>man pages</primary></indexterm>
|
||||
|
||||
<para>The most comprehensive documentation on FreeBSD is in the form
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.20 2001/08/04 19:00:04 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/boot/chapter.sgml,v 1.21 2001/08/06 21:25:27 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="boot">
|
||||
|
@ -132,7 +132,7 @@
|
|||
display similar to this one at boot time.</para>
|
||||
|
||||
<example id="boot-boot0-example">
|
||||
<title><filename>boot0</filename> screenshot</title>
|
||||
<title><filename>boot0</filename> Screenshot</title>
|
||||
|
||||
<screen>F1 DOS
|
||||
F2 FreeBSD
|
||||
|
@ -192,7 +192,7 @@ Default: F2</screen>
|
|||
was tasked to run the kernel directly.</para>
|
||||
|
||||
<example id="boot-boot2-example">
|
||||
<title><filename>boot2</filename> screenshot</title>
|
||||
<title><filename>boot2</filename> Screenshot</title>
|
||||
|
||||
<screen>>> FreeBSD/i386 BOOT
|
||||
Default: 0:ad(0,a)/kernel
|
||||
|
@ -584,7 +584,7 @@ boot:</screen>
|
|||
the root password before initiating single-user mode.</para>
|
||||
|
||||
<example id="boot-insecure-console">
|
||||
<title>An insecure console in /etc/ttys</title>
|
||||
<title>An Insecure Console in /etc/ttys</title>
|
||||
|
||||
<programlisting># name getty type status comments
|
||||
#
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.12 2001/07/30 17:18:50 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/config/chapter.sgml,v 1.13 2001/08/09 23:42:29 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="config-tuning">
|
||||
|
@ -51,7 +51,7 @@
|
|||
<title>Initial Configuration</title>
|
||||
|
||||
<sect2>
|
||||
<title>Partition layout</title>
|
||||
<title>Partition Layout</title>
|
||||
|
||||
<indexterm><primary>Partition layout</primary></indexterm>
|
||||
<indexterm>
|
||||
|
@ -748,7 +748,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
</sect1>
|
||||
|
||||
<sect1 id="configtuning-disk">
|
||||
<title>Tuning disks</title>
|
||||
<title>Tuning Disks</title>
|
||||
|
||||
<sect2>
|
||||
<title>Sysctl Variables</title>
|
||||
|
@ -846,12 +846,12 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
</sect1>
|
||||
|
||||
<sect1 id="configtuning-kernel-limits">
|
||||
<title>Tuning kernel limits</title>
|
||||
<title>Tuning Kernel Limits</title>
|
||||
|
||||
<indexterm><primary>Tuning kernel limits</primary></indexterm>
|
||||
|
||||
<sect2>
|
||||
<title>File/process limits</title>
|
||||
<title>File/Process Limits</title>
|
||||
|
||||
<sect3>
|
||||
<title><varname>kern.maxfiles</varname></title>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.465 2001/08/08 17:29:39 dd Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/contrib/chapter.sgml,v 1.466 2001/08/09 23:42:30 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="contrib">
|
||||
|
@ -50,7 +50,7 @@
|
|||
to at least give it a second look.</para>
|
||||
|
||||
<sect1 id="contrib-what">
|
||||
<title>What is Needed</title>
|
||||
<title>What Is Needed</title>
|
||||
|
||||
<para>The following list of tasks and sub-projects represents something of
|
||||
an amalgam of the various core team <filename>TODO</filename> lists and
|
||||
|
@ -61,7 +61,7 @@
|
|||
been appointed, maybe you would like to volunteer?</para>
|
||||
|
||||
<sect2>
|
||||
<title>Ongoing tasks</title>
|
||||
<title>Ongoing Tasks</title>
|
||||
|
||||
<para>Most of the tasks listed in the previous sections require either a
|
||||
considerable investment of time or an in-depth knowledge of the
|
||||
|
@ -150,7 +150,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Work through the PR database</title>
|
||||
<title>Work through the PR Database</title>
|
||||
|
||||
<indexterm><primary>problem reports database</primary></indexterm>
|
||||
<para>The <ulink
|
||||
|
@ -177,7 +177,7 @@
|
|||
following 6 categories:</para>
|
||||
|
||||
<sect2 id="contrib-general">
|
||||
<title>Bug reports and general commentary</title>
|
||||
<title>Bug Reports and General Commentary</title>
|
||||
|
||||
<para>An idea or suggestion of <emphasis>general</emphasis> technical
|
||||
interest should be mailed to the &a.hackers;. Likewise, people with
|
||||
|
@ -212,7 +212,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes to the documentation</title>
|
||||
<title>Changes to the Documentation</title>
|
||||
|
||||
<indexterm><primary>documentation submissions</primary></indexterm>
|
||||
<para>Changes to the documentation are overseen by the &a.doc;. Send
|
||||
|
@ -223,7 +223,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Changes to existing source code</title>
|
||||
<title>Changes to Existing Source Code</title>
|
||||
|
||||
<indexterm><primary>FreeBSD-current</primary></indexterm>
|
||||
<para>An addition or change to the existing source code is a somewhat
|
||||
|
@ -295,7 +295,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>New code or major value-added packages</title>
|
||||
<title>New Code or Major Value-Added Packages</title>
|
||||
|
||||
<para>In the case of a significant contribution of a large body
|
||||
work, or the addition of an important new feature to FreeBSD, it
|
||||
|
@ -381,7 +381,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Money, Hardware or Internet access</title>
|
||||
<title>Money, Hardware or Internet Access</title>
|
||||
|
||||
<para>We are always very happy to accept donations to further the cause
|
||||
of the FreeBSD Project and, in a volunteer effort like ours, a little
|
||||
|
@ -390,7 +390,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
the funds to buy such items ourselves.</para>
|
||||
|
||||
<sect3>
|
||||
<title><anchor id="donations">Donating funds</title>
|
||||
<title><anchor id="donations">Donating Funds</title>
|
||||
|
||||
<para>The FreeBSD Foundation is a non-profit, tax-exempt
|
||||
foundation established to further the goals of the FreeBSD
|
||||
|
@ -418,7 +418,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Donating hardware</title>
|
||||
<title>Donating Hardware</title>
|
||||
<indexterm><primary>donations</primary></indexterm>
|
||||
|
||||
<para>Donations of hardware in any of the 3 following categories are
|
||||
|
@ -453,7 +453,7 @@ THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Donating Internet access</title>
|
||||
<title>Donating Internet Access</title>
|
||||
|
||||
<para>We can always use new mirror sites for FTP, WWW or
|
||||
<command>cvsup</command>. If you would like to be such a mirror,
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.79 2001/07/30 17:18:51 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/cutting-edge/chapter.sgml,v 1.80 2001/08/04 20:06:21 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="cutting-edge">
|
||||
|
@ -42,7 +42,7 @@
|
|||
twice about running it.</para>
|
||||
|
||||
<sect3>
|
||||
<title>What is &os.current;?</title>
|
||||
<title>What Is &os.current;?</title>
|
||||
<indexterm><primary>snapshot</primary></indexterm>
|
||||
|
||||
<para>&os.current; is, quite literally, nothing more than a
|
||||
|
@ -59,7 +59,7 @@
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Who needs &os.current;?</title>
|
||||
<title>Who Needs &os.current;?</title>
|
||||
|
||||
<para>&os.current; is made generally available for 3 primary
|
||||
interest groups:</para>
|
||||
|
@ -90,7 +90,7 @@
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>What is &os.current; <emphasis>not</emphasis>?</title>
|
||||
<title>What Is &os.current; <emphasis>Not</emphasis>?</title>
|
||||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
|
@ -261,7 +261,7 @@ subscribe cvs-all</programlisting>
|
|||
<title>Staying Stable with &os;</title>
|
||||
|
||||
<sect3>
|
||||
<title>What is &os.stable;?</title>
|
||||
<title>What Is &os.stable;?</title>
|
||||
<indexterm><primary>-STABLE</primary></indexterm>
|
||||
|
||||
<para>&os.stable; is our development branch from which major releases
|
||||
|
@ -275,7 +275,7 @@ subscribe cvs-all</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Who needs &os.stable;?</title>
|
||||
<title>Who Needs &os.stable;?</title>
|
||||
|
||||
<para>If you are interested in tracking or contributing to the
|
||||
FreeBSD development process, especially as it relates to the
|
||||
|
@ -529,7 +529,7 @@ subscribe cvs-all</programlisting>
|
|||
tree to rebuild the system.</para>
|
||||
|
||||
<warning>
|
||||
<title>Take a backup</title>
|
||||
<title>Take a Backup</title>
|
||||
|
||||
<para>It cannot be stressed enough how important it is to take a
|
||||
backup of your system <emphasis>before</emphasis> you do this.
|
||||
|
@ -544,7 +544,7 @@ subscribe cvs-all</programlisting>
|
|||
</warning>
|
||||
|
||||
<warning>
|
||||
<title>Subscribe to the right mailing list</title>
|
||||
<title>Subscribe to the Right Mailing List</title>
|
||||
|
||||
<indexterm><primary>mailing list</primary></indexterm>
|
||||
<para>The &os.stable; and &os.current; branches are, by their
|
||||
|
@ -660,7 +660,7 @@ subscribe cvs-all</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="makeworld-singleuser">
|
||||
<title>Drop to single user mode</title>
|
||||
<title>Drop to Single User Mode</title>
|
||||
<indexterm><primary>single-user mode</primary></indexterm>
|
||||
|
||||
<para>You may want to compile the system in single user mode. Apart
|
||||
|
@ -720,10 +720,10 @@ subscribe cvs-all</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Recompile the source</title>
|
||||
<title>Recompile the Source</title>
|
||||
|
||||
<sect3>
|
||||
<title>Saving the output</title>
|
||||
<title>Saving the Output</title>
|
||||
|
||||
<para>It is a good idea to save the output you get from running
|
||||
&man.make.1; to another file. If something goes wrong you will
|
||||
|
@ -752,7 +752,7 @@ Script done, …</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Compile and install the base system</title>
|
||||
<title>Compile and Install the Base System</title>
|
||||
|
||||
<para>You must be in the <filename>/usr/src</filename>
|
||||
directory...</para>
|
||||
|
@ -889,7 +889,7 @@ Script done, …</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Compile and install a new kernel</title>
|
||||
<title>Compile and Install a New Kernel</title>
|
||||
<indexterm>
|
||||
<primary>kernel</primary>
|
||||
<secondary>compiling</secondary>
|
||||
|
@ -928,7 +928,7 @@ Script done, …</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Reboot in to single user mode</title>
|
||||
<title>Reboot into Single User Mode</title>
|
||||
<indexterm><primary>single-user mode</primary></indexterm>
|
||||
|
||||
<para>You should reboot in to single user mode to test the new kernel
|
||||
|
@ -937,7 +937,7 @@ Script done, …</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Install the new system binaries</title>
|
||||
<title>Install the New System Binaries</title>
|
||||
|
||||
<para>If you were building a version of &os; recent enough to have
|
||||
used <command>make buildworld</command> then you should now use the
|
||||
|
@ -971,7 +971,7 @@ Script done, …</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Update files not updated by <command>make world</command></title>
|
||||
<title>Update Files Not Updated by <command>make world</command></title>
|
||||
|
||||
<para>Remaking the world will not update certain directories (in
|
||||
particular, <filename>/etc</filename>, <filename>/var</filename> and
|
||||
|
@ -1002,7 +1002,7 @@ Script done, …</screen>
|
|||
for differences.</para>
|
||||
|
||||
<warning>
|
||||
<title>Backup your existing <filename>/etc</filename></title>
|
||||
<title>Backup Your Existing <filename>/etc</filename></title>
|
||||
|
||||
<para>Although, in theory, nothing is going to touch this directory
|
||||
automatically, it is always better to be sure. So copy your
|
||||
|
@ -1062,9 +1062,9 @@ Script done, …</screen>
|
|||
file.</para>
|
||||
|
||||
<tip>
|
||||
<title>Name the new root directory
|
||||
(<filename>/var/tmp/root</filename>) with a time stamp, so you can
|
||||
easily compare differences between versions</title>
|
||||
<title>Name the New Root Directory
|
||||
(<filename>/var/tmp/root</filename>) with a Time Stamp, So You Can
|
||||
Easily Compare Differences Between Versions</title>
|
||||
|
||||
<para>Frequently rebuilding the world means that you have to update
|
||||
<filename>/etc</filename> frequently as well, which can be a bit of
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.45 2001/08/09 23:42:30 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/disks/chapter.sgml,v 1.46 2001/08/10 01:18:34 murray Exp $
|
||||
-->
|
||||
|
||||
<chapter id="disks">
|
||||
|
@ -57,7 +57,7 @@
|
|||
open the case and move the jumpers and cables.</para>
|
||||
|
||||
<sidebar>
|
||||
<title>An illustration from the files of Bill and Fred's Exceptional
|
||||
<title>An Illustration from the Files of Bill and Fred's Exceptional
|
||||
Adventures:</title>
|
||||
|
||||
<para>Bill breaks-down an older Wintel box to make another FreeBSD box
|
||||
|
@ -729,8 +729,8 @@
|
|||
<para>To mount an existing filesystem image:</para>
|
||||
|
||||
<example>
|
||||
<title>Using vnconfig to mount an existing filesystem
|
||||
image</title>
|
||||
<title>Using vnconfig to mount an Existing Filesystem
|
||||
Image</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>vnconfig vn<replaceable>0</replaceable> <replaceable>diskimage</replaceable></userinput>
|
||||
&prompt.root; <userinput>mount /dev/vn<replaceable>0</replaceable>c <replaceable>/mnt</replaceable></userinput></screen>
|
||||
|
@ -773,7 +773,7 @@ Filesystem 1K-blocks Used Avail Capacity Mounted on
|
|||
example, &man.vnconfig.8;, and:</para>
|
||||
|
||||
<example>
|
||||
<title>md memory disk</title>
|
||||
<title>md Memory Disk</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>dd if=<replaceable>newimage</replaceable> of=/dev/md<replaceable>0</replaceable></userinput>
|
||||
5120+0 records in
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.83 2001/08/09 23:42:30 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/install/chapter.sgml,v 1.84 2001/08/10 16:01:35 bmah Exp $
|
||||
-->
|
||||
|
||||
<chapter id="install">
|
||||
|
@ -119,7 +119,7 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>Acquire the boot floppy images</title>
|
||||
<title>Acquire the Boot Floppy Images</title>
|
||||
|
||||
<para>These are files with a <filename>.flp</filename>
|
||||
extension. If you have a CDROM release of FreeBSD then you
|
||||
|
@ -138,7 +138,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Prepare the floppy disks</title>
|
||||
<title>Prepare the Floppy Disks</title>
|
||||
|
||||
<para>You must prepare one floppy disk per image file you had to
|
||||
download. It is imperative that these disks are free from
|
||||
|
@ -155,7 +155,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Write the image files to the floppy disks.</title>
|
||||
<title>Write the Image Files to the Floppy Disks.</title>
|
||||
|
||||
<para>The image files, such as <filename>kern.flp</filename>,
|
||||
are <emphasis>not</emphasis> regular files you copy to the
|
||||
|
@ -296,7 +296,7 @@
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Before installing from Floppies</title>
|
||||
<title>Before Installing from Floppies</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>installation</primary>
|
||||
|
@ -659,7 +659,7 @@
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Check your BIOS drive numbering</title>
|
||||
<title>Check Your BIOS Drive Numbering</title>
|
||||
|
||||
<para>If you have used features in your BIOS to renumber your disk
|
||||
drives without re-cabling them then you should read <xref
|
||||
|
@ -782,7 +782,6 @@
|
|||
a CDROM or FTP distribution or in sysinstall's documentation
|
||||
menu. It lists, for a given architecture, what hardware devices
|
||||
are known to be supported by each release of FreeBSD.</para>
|
||||
|
||||
</sect1>
|
||||
|
||||
<sect1 id="install-trouble">
|
||||
|
@ -798,7 +797,7 @@
|
|||
MS-DOS.</para>
|
||||
|
||||
<sect2>
|
||||
<title>What to do if something goes wrong...</title>
|
||||
<title>What to Do If Something Goes Wrong...</title>
|
||||
|
||||
<para>Due to various limitations of the PC architecture, it is
|
||||
impossible for probing to be 100% reliable, however, there are a
|
||||
|
@ -982,8 +981,8 @@
|
|||
cases.</para>
|
||||
|
||||
<sect2 id="headless-install">
|
||||
<title>Installing FreeBSD on a system without a monitor or
|
||||
keyboard</title>
|
||||
<title>Installing FreeBSD on a System without a Monitor or
|
||||
Keyboard</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>installation</primary>
|
||||
|
@ -1000,7 +999,7 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<title>Fetch the right boot floppy images</title>
|
||||
<title>Fetch the Right Boot Floppy Images</title>
|
||||
|
||||
<para>First you will need to get the right disk images so
|
||||
that you can boot into the install program. The secret
|
||||
|
@ -1018,7 +1017,7 @@
|
|||
|
||||
</step>
|
||||
<step>
|
||||
<title>Write the image files to the floppy disks.</title>
|
||||
<title>Write the Image Files to the Floppy Disks.</title>
|
||||
|
||||
<para>The image files, such as
|
||||
<filename>kern.flp</filename>, are
|
||||
|
@ -1071,8 +1070,8 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Enabling the boot floppies to boot into a serial
|
||||
console</title>
|
||||
<title>Enabling the Boot Floppies to Boot into a Serial
|
||||
Console</title>
|
||||
|
||||
<warning>
|
||||
<para>Do not try to mount the floppy if it is write-protected</para>
|
||||
|
@ -1115,7 +1114,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Connecting your null modem cable</title>
|
||||
<title>Connecting Your Null Modem Cable</title>
|
||||
|
||||
<indexterm><primary>null-modem cable</primary></indexterm>
|
||||
<para>You now need to connect a null modem cable between
|
||||
|
@ -1127,7 +1126,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Booting up for the install</title>
|
||||
<title>Booting Up for the Install</title>
|
||||
|
||||
<para>It's now time to go ahead and start the install. Put
|
||||
the <filename>kern.flp</filename> floppy in the floppy
|
||||
|
@ -1136,7 +1135,7 @@
|
|||
</step>
|
||||
|
||||
<step>
|
||||
<title>Connecting to your headless machine</title>
|
||||
<title>Connecting to Your Headless Machine</title>
|
||||
<indexterm>
|
||||
<primary><command>cu</command></primary>
|
||||
</indexterm>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v 1.55 2001/08/05 18:51:11 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/introduction/chapter.sgml,v 1.56 2001/08/09 23:42:31 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="introduction">
|
||||
|
@ -114,7 +114,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>What can FreeBSD do?</title>
|
||||
<title>What Can FreeBSD Do?</title>
|
||||
|
||||
<para>FreeBSD has many noteworthy features. Some of these
|
||||
are:</para>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml,v 1.19 2001/07/23 22:51:31 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/kernelopts/chapter.sgml,v 1.20 2001/08/09 23:42:31 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="kernelopts">
|
||||
|
@ -102,7 +102,7 @@
|
|||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Now What Do I Have to Do for it?</title>
|
||||
<title>Now What Do I Have to Do for It?</title>
|
||||
|
||||
<para>First, edit <filename>sys/conf/options</filename> (or
|
||||
<filename>sys/<replaceable><arch></replaceable>/conf/options.<replaceable><arch></replaceable></filename>,
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.64 2001/08/08 18:49:15 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/l10n/chapter.sgml,v 1.65 2001/08/09 23:42:32 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="l10n">
|
||||
|
@ -68,14 +68,14 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Why should I use I18N/L10N?</title>
|
||||
<title>Why Should I Use I18N/L10N?</title>
|
||||
|
||||
<para>I18N/L10N is used whenever you wish to either view, input, or
|
||||
process data in non-English languages.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>What languages are supported in the I18N effort?</title>
|
||||
<title>What Languages Are Supported in the I18N Effort?</title>
|
||||
|
||||
<para>I18N and L10N are not FreeBSD specific. Currently, one can
|
||||
choose from most of the major languages of the World, including
|
||||
|
@ -188,7 +188,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>I18N applications</title>
|
||||
<title>I18N Applications</title>
|
||||
|
||||
<para>In the FreeBSD Ports and Package system, I18N applications
|
||||
have been named with <literal>I18N</literal> in their names for
|
||||
|
@ -696,7 +696,7 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
|
|||
allow for wide or multibyte characters support.</para>
|
||||
|
||||
<sect3>
|
||||
<title>A Call to Unify the I18N effort</title>
|
||||
<title>A Call to Unify the I18N Effort</title>
|
||||
|
||||
<para>It has come to our attention that the individual I18N/L10N
|
||||
efforts for each country has been repeating each others'
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.47 2001/07/23 22:51:32 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/linuxemu/chapter.sgml,v 1.48 2001/08/09 23:42:32 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="linuxemu">
|
||||
|
@ -137,7 +137,7 @@ Id Refs Address Size Name
|
|||
linkend="linuxemu-libs-manually">manually</link>.</para>
|
||||
|
||||
<sect3 id="linuxemu-libs-port">
|
||||
<title>Installing using the linux_base port</title>
|
||||
<title>Installing Using the linux_base Port</title>
|
||||
<indexterm><primary>ports collection</primary></indexterm>
|
||||
|
||||
<para>This is by far the easiest method to use when installing the
|
||||
|
@ -155,7 +155,7 @@ Id Refs Address Size Name
|
|||
</sect3>
|
||||
|
||||
<sect3 id="linuxemu-libs-manually">
|
||||
<title>Installing libraries manually</title>
|
||||
<title>Installing Libraries Manually</title>
|
||||
|
||||
<para>If you do not have the <quote>ports</quote> collection
|
||||
installed, you can install the libraries by hand instead. You
|
||||
|
@ -182,7 +182,7 @@ Id Refs Address Size Name
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>How to install additional shared libraries</title>
|
||||
<title>How to Install Additional Shared Libraries</title>
|
||||
<indexterm><primary>shared libraries</primary></indexterm>
|
||||
|
||||
<para>What if you install the <filename>linux_base</filename> port
|
||||
|
@ -268,7 +268,7 @@ libc.so.4 (DLL Jump 4.5pl26) => /lib/libc.so.4.6.29</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Installing Linux ELF binaries</title>
|
||||
<title>Installing Linux ELF Binaries</title>
|
||||
<indexterm>
|
||||
<primary>Linux</primary>
|
||||
<secondary>ELF binaries</secondary>
|
||||
|
@ -295,7 +295,7 @@ Abort</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Configuring the host name resolver</title>
|
||||
<title>Configuring the Hostname Resolver</title>
|
||||
|
||||
<para>If DNS does not work or you get this message:</para>
|
||||
|
||||
|
@ -347,7 +347,7 @@ multi on</programlisting>
|
|||
url="http://www.wolfram.com/">http://www.wolfram.com/</ulink>.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Branding the Linux binaries</title>
|
||||
<title>Branding the Linux Binaries</title>
|
||||
|
||||
<para>The Linux binaries are located in the <filename>Unix</filename>
|
||||
directory of the <application>Mathematica</application> CDROM
|
||||
|
@ -376,7 +376,7 @@ multi on</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Obtaining your Mathematica Password</title>
|
||||
<title>Obtaining Your Mathematica Password</title>
|
||||
|
||||
<para>Before you can run <application>Mathematica</application>
|
||||
you will have to obtain a
|
||||
|
@ -409,7 +409,7 @@ disco.example.com 7115-70839-20412</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Running the Mathematica front end over a network</title>
|
||||
<title>Running the Mathematica Frontend over a Network</title>
|
||||
|
||||
<para><application>Mathematica</application> uses some special
|
||||
fonts to display characters not
|
||||
|
@ -493,7 +493,7 @@ disco.example.com 7115-70839-20412</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Installing the Linux environment</title>
|
||||
<title>Installing the Linux Environment</title>
|
||||
|
||||
<para>Make sure you have both <filename>linux_base</filename> and
|
||||
<filename>linux_devtools</filename> from the ports collection
|
||||
|
@ -516,7 +516,7 @@ disco.example.com 7115-70839-20412</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Creating the Oracle environment</title>
|
||||
<title>Creating the Oracle Environment</title>
|
||||
|
||||
<para>Before you can install Oracle, you need to set up a proper
|
||||
environment. This document only describes what to do
|
||||
|
@ -554,7 +554,7 @@ options SYSVMSG #SysV interprocess communication</programlisting>
|
|||
|
||||
<sect3 id="linuxemu-oracle-account">
|
||||
|
||||
<title>Oracle account</title>
|
||||
<title>Oracle Account</title>
|
||||
|
||||
<para>Create an Oracle account just as you would create any other
|
||||
account. The Oracle account is special only that you need to give
|
||||
|
@ -934,7 +934,7 @@ export PATH</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="installation">
|
||||
<title>Installation of FreeBSD 4.3 stable</title>
|
||||
<title>Installation of FreeBSD 4.3-STABLE</title>
|
||||
|
||||
<para>First I installed FreeBSD 4.3 stable. I did the
|
||||
default-installation via FTP.</para>
|
||||
|
@ -1024,7 +1024,7 @@ export PATH</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="getlatestsources">
|
||||
<title>Get the latest stable-sources</title>
|
||||
<title>Get the Latest STABLE Sources</title>
|
||||
|
||||
<para>For FreeBSD 4.3 stable onwards, it is quite easy to get
|
||||
the latest stable sources. With the older versions of
|
||||
|
@ -1062,7 +1062,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
|
||||
|
||||
<sect3 id="makeworldandnewkernel">
|
||||
<title>Make world and a new kernel</title>
|
||||
<title><command>make world</command> and a New Kernel</title>
|
||||
|
||||
<para>The first thing to do is to install the sources.
|
||||
As user root, do the following:</para>
|
||||
|
@ -1104,7 +1104,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="installingthelinuxenviornment">
|
||||
<title>Installing the Linux environment</title>
|
||||
<title>Installing the Linux Environment</title>
|
||||
|
||||
<para>I had some trouble downloading the required RPM-files (for
|
||||
4.3 stable, 2nd May 2001), so you might try one of the
|
||||
|
@ -1117,7 +1117,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
</itemizedlist>
|
||||
|
||||
<sect3 id="installinglinuxbase-system">
|
||||
<title>Installing Linux base-system</title>
|
||||
<title>Installing Linux Base-system</title>
|
||||
<para>First the Linux base-system needs to be installed (as root):
|
||||
<screen>&prompt.root; <userinput>cd /usr/ports/emulators/linux_base</userinput>
|
||||
&prompt.root; <userinput>make package</userinput> </screen></para>
|
||||
|
@ -1125,7 +1125,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
|
||||
|
||||
<sect3 id="installinglinuxdevelopment">
|
||||
<title>Installing Linux development</title>
|
||||
<title>Installing Linux Development</title>
|
||||
|
||||
<para>Next, the Linux development is needed:</para>
|
||||
|
||||
|
@ -1136,7 +1136,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
|
||||
|
||||
<sect3 id="installingnecessaryrpms">
|
||||
<title>Installing necessary RPMs</title>
|
||||
<title>Installing Necessary RPMs</title>
|
||||
<indexterm><primary>RPMs</primary></indexterm>
|
||||
|
||||
<para>To start the R3SETUP-Program, pam support is needed. As
|
||||
|
@ -1179,10 +1179,10 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="creatingsapr3env">
|
||||
<title>Creating the SAP/R3 environment</title>
|
||||
<title>Creating the SAP/R3 Environment</title>
|
||||
|
||||
<sect3 id="filesystemsandmountpoints">
|
||||
<title>Creating the necessary filesystems and mountpoints</title>
|
||||
<title>Creating the Necessary Filesystems and Mountpoints</title>
|
||||
|
||||
<para>For a simple installation, it is sufficient to create the
|
||||
following filesystems:</para>
|
||||
|
@ -1221,7 +1221,7 @@ DOCSUPFILE= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="creatingusersanddirectories">
|
||||
<title>Creating users and directories</title>
|
||||
<title>Creating Users and Directories</title>
|
||||
|
||||
<para><application>SAP R/3</application> needs two users and
|
||||
three groups. The usernames depend on the
|
||||
|
@ -1338,7 +1338,7 @@ Shell: /bin/sh</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="creatingdirectories">
|
||||
<title>Creating directories</title>
|
||||
<title>Creating Directories</title>
|
||||
|
||||
<para>These directories are usually created as separate
|
||||
filesystems. This depends entirely on your requirements. I
|
||||
|
@ -1395,7 +1395,7 @@ sapmsIDS 3600/tcp # SAP Message Server. 3600 + Instance-Number</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="necessarylocales">
|
||||
<title>Necessary locales</title>
|
||||
<title>Necessary Locales</title>
|
||||
<indexterm><primary>locale</primary></indexterm>
|
||||
|
||||
<para>SAP requires at least two locales that aren't part of
|
||||
|
@ -1783,7 +1783,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="continuewithsapr4installation">
|
||||
<title>Continue with SAP R/3 installation</title>
|
||||
<title>Continue with SAP R/3 Installation</title>
|
||||
|
||||
<para>First check the environment settings of users
|
||||
<username>idsamd</username>
|
||||
|
@ -1797,7 +1797,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
|
|||
-s</command> within all three files.</para>
|
||||
|
||||
<sect3 id="databaseload">
|
||||
<title>Database load</title>
|
||||
<title>Database Load</title>
|
||||
|
||||
<para>Afterwards, R3SETUP can either be restarted or continued
|
||||
(depending on whether exit was chosen or not). R3SETUP then
|
||||
|
@ -1866,10 +1866,10 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="postinstallationsteps">
|
||||
<title>Post-installation steps</title>
|
||||
<title>Post-installation Steps</title>
|
||||
|
||||
<sect3 id="requestsapr3licensekey">
|
||||
<title>Request SAP R/3 license key</title>
|
||||
<title>Request SAP R/3 License Key</title>
|
||||
|
||||
<para>This is needed, as the temporary license is only valid for
|
||||
four weeks. Don't forget to enter the correct Operating System:
|
||||
|
@ -1912,7 +1912,7 @@ LICENSE KEY = <license key, 24 chars></programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="configtranssysprofileopermodesetc">
|
||||
<title>Configure Transport System, Profile, Operation Modes, etc.</title>
|
||||
<title>Configure Transport System, Profile, Operation Modes, Etc.</title>
|
||||
|
||||
<para>Within client 000, user different from <username>ddic</username>
|
||||
and sap*, do at least the following:</para>
|
||||
|
@ -2007,10 +2007,10 @@ tape_address_rew = /dev/sa0</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="problemsduringinstallation">
|
||||
<title>Problems during installation</title>
|
||||
<title>Problems During Installation</title>
|
||||
|
||||
<sect3 id="indoraduringduringr3setup">
|
||||
<title>OSUSERSIDADM_IND_ORA during R3SETUP</title>
|
||||
<title>OSUSERSIDADM_IND_ORA During R3SETUP</title>
|
||||
|
||||
<para>If R3SETUP complains at this stage, edit file
|
||||
CENTRDB.R3S. Locate [OSUSERSIDADM_IND_ORA] and edit the
|
||||
|
@ -2026,7 +2026,7 @@ STATUS=OK (had status ERROR)
|
|||
</sect3>
|
||||
|
||||
<sect3 id="indoraduringr3setup">
|
||||
<title>OSUSERDBSID_IND_ORA during R3SETUP</title>
|
||||
<title>OSUSERDBSID_IND_ORA During R3SETUP</title>
|
||||
|
||||
<para>Possibly R3SETUP also complains at this stage. Just edit
|
||||
CENTRDB.R3S. Locate [OSUSERDBSID_IND_ORA] and edit the
|
||||
|
@ -2040,7 +2040,7 @@ STATUS=OK (had status ERROR)
|
|||
</sect3>
|
||||
|
||||
<sect3 id="oraviewvrffilenotfound">
|
||||
<title>oraview.vrf FILE NOT FOUND during Oracle installation</title>
|
||||
<title>oraview.vrf FILE NOT FOUND During Oracle Installation</title>
|
||||
|
||||
<para>You haven't deselected <emphasis>Oracle On-Line Text Viewer</emphasis>
|
||||
before starting the installation. This is marked for installation even
|
||||
|
@ -2049,7 +2049,7 @@ STATUS=OK (had status ERROR)
|
|||
</sect3>
|
||||
|
||||
<sect3 id="textenvincalid">
|
||||
<title>TEXTENV_INVALID during R3SETUP, RFC or SAPGUI start</title>
|
||||
<title>TEXTENV_INVALID During R3SETUP, RFC or SAPGUI Start</title>
|
||||
|
||||
<para>If this error is encountered, the correct locale is
|
||||
missing. SAP note 0171356 lists the necessary RPMs that need
|
||||
|
@ -2095,7 +2095,7 @@ rscp/TCP0B =TCP0B
|
|||
</sect3>
|
||||
|
||||
<sect3 id="ora-12546">
|
||||
<title>ORA-12546. Start Listener with correct permissions</title>
|
||||
<title>ORA-12546. Start Listener with Correct Permissions</title>
|
||||
|
||||
<para>Start the Oracle Listener as user
|
||||
<username>oraids</username> with the following commands:</para>
|
||||
|
@ -2107,7 +2107,7 @@ rscp/TCP0B =TCP0B
|
|||
</sect3>
|
||||
|
||||
<sect3 id="dipgntabindind">
|
||||
<title>[DIPGNTAB_IND_IND] during R3SETUP</title>
|
||||
<title>[DIPGNTAB_IND_IND] During R3SETUP</title>
|
||||
|
||||
<para>In general, see SAP note 0130581 (R3SETUP step
|
||||
<literal>DIPGNTAB</literal>
|
||||
|
@ -2144,7 +2144,7 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans </screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="rfcrswboiniindind">
|
||||
<title>[RFCRSWBOINI_IND_IND] during R3SETUP</title>
|
||||
<title>[RFCRSWBOINI_IND_IND] During R3SETUP</title>
|
||||
|
||||
<para>Set STATUS of the offending step from ERROR to OK (file
|
||||
<filename>CENTRDB.R3S</filename>) and restart R3SETUP. After
|
||||
|
@ -2156,7 +2156,7 @@ drwxrwxr-x 11 idsadm sapsys 512 May 4 14:20 trans </screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="rfcraddbdifindind">
|
||||
<title>[RFCRADDBDIF_IND_IND] during R3SETUP</title>
|
||||
<title>[RFCRADDBDIF_IND_IND] During R3SETUP</title>
|
||||
|
||||
<para>Set STATUS of the offending step from ERROR to OK (file
|
||||
<filename>CENTRDB.R3S</filename>) and restart R3SETUP. After
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.26 2001/07/30 17:18:53 murray Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mail/chapter.sgml,v 1.27 2001/08/09 23:42:32 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="mail">
|
||||
|
@ -455,7 +455,7 @@ freefall MX 20 who.cdrom.com</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="mail-domain">
|
||||
<title>Mail for your Domain</title>
|
||||
<title>Mail for Your Domain</title>
|
||||
|
||||
<para>In order to set up a <quote>mailhost</quote> (a.k.a., mail
|
||||
server) you need to have any mail sent to various workstations
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.140 2001/08/08 18:49:15 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/mirrors/chapter.sgml,v 1.141 2001/08/09 18:50:33 murray Exp $
|
||||
-->
|
||||
|
||||
<appendix id="mirrors">
|
||||
|
@ -1309,8 +1309,8 @@
|
|||
CVS:</para>
|
||||
|
||||
<example>
|
||||
<title>Checking out something from -CURRENT (&man.ls.1;) and
|
||||
deleting it again:</title>
|
||||
<title>Checking Out Something from -CURRENT (&man.ls.1;) and
|
||||
Deleting It Again:</title>
|
||||
|
||||
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
|
||||
&prompt.user; <userinput>cvs login</userinput>
|
||||
|
@ -1322,8 +1322,8 @@
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Checking out the version of &man.ls.1; in the 3.X-STABLE
|
||||
branch:</title>
|
||||
<title>Checking Out the Version of &man.ls.1; in the 3.X-STABLE
|
||||
Branch:</title>
|
||||
|
||||
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
|
||||
&prompt.user; <userinput>cvs login</userinput>
|
||||
|
@ -1335,7 +1335,7 @@
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Creating a list of changes (as unified diffs) to &man.ls.1;</title>
|
||||
<title>Creating a List of Changes (as unified diffs) to &man.ls.1;</title>
|
||||
|
||||
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
|
||||
&prompt.user; <userinput>cvs login</userinput>
|
||||
|
@ -1346,7 +1346,7 @@
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Finding out what other module names can be used:</title>
|
||||
<title>Finding Out What Other Module Names Can Be Used:</title>
|
||||
|
||||
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.FreeBSD.org:/home/ncvs</userinput>
|
||||
&prompt.user; <userinput>cvs login</userinput>
|
||||
|
@ -1399,7 +1399,7 @@
|
|||
for other things.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Why should I use <application>CTM</application>?</title>
|
||||
<title>Why Should I Use <application>CTM</application>?</title>
|
||||
|
||||
<para><application>CTM</application> will give you a local copy of
|
||||
the FreeBSD source trees. There are a number of
|
||||
|
@ -1426,7 +1426,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>What do I need to use
|
||||
<title>What Do I Need to Use
|
||||
<application>CTM</application>?</title>
|
||||
|
||||
<para>You will need two things: The <application>CTM</application>
|
||||
|
@ -1495,8 +1495,8 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Using <application>CTM</application> for the first
|
||||
time</title>
|
||||
<title>Using <application>CTM</application> for the First
|
||||
Time</title>
|
||||
|
||||
<para>Before you can start using <application>CTM</application>
|
||||
deltas, you will need to get to a starting point for the deltas
|
||||
|
@ -1531,8 +1531,8 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Using <application>CTM</application> in your daily
|
||||
life</title>
|
||||
<title>Using <application>CTM</application> in Your Daily
|
||||
Life</title>
|
||||
|
||||
<para>To apply the deltas, simply say:</para>
|
||||
|
||||
|
@ -1565,7 +1565,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Keeping your local changes</title>
|
||||
<title>Keeping Your Local Changes</title>
|
||||
|
||||
<para>As a developer one would like to experiment with and change
|
||||
files in the source tree. <application>CTM</application>
|
||||
|
@ -1583,11 +1583,11 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Other interesting <application>CTM</application> options</title>
|
||||
<title>Other Interesting <application>CTM</application> Options</title>
|
||||
|
||||
<sect3>
|
||||
<title>Finding out exactly what would be touched by an
|
||||
update</title>
|
||||
<title>Finding Out Exactly What Would Be Touched by an
|
||||
Update</title>
|
||||
|
||||
<para>You can determine the list of changes that
|
||||
<application>CTM</application> will make on your source
|
||||
|
@ -1600,7 +1600,7 @@
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Making backups before updating</title>
|
||||
<title>Making Backups Before Updating</title>
|
||||
|
||||
<para>Sometimes you may want to backup all the files that would
|
||||
be changed by a <application>CTM</application> update.</para>
|
||||
|
@ -1612,7 +1612,7 @@
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Restricting the files touched by an update</title>
|
||||
<title>Restricting the Files Touched by an Update</title>
|
||||
|
||||
<para>Sometimes you would be interested in restricting the scope
|
||||
of a given <application>CTM</application> update, or may be
|
||||
|
@ -1642,7 +1642,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Future plans for <application>CTM</application></title>
|
||||
<title>Future Plans for <application>CTM</application></title>
|
||||
|
||||
<para>Tons of them:</para>
|
||||
|
||||
|
@ -1660,7 +1660,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Miscellaneous stuff</title>
|
||||
<title>Miscellaneous Stuff</title>
|
||||
|
||||
<para>There is a sequence of deltas for the
|
||||
<literal>ports</literal> collection too, but interest has not
|
||||
|
@ -1669,7 +1669,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2 id="mirrors-ctm">
|
||||
<title>CTM mirrors</title>
|
||||
<title>CTM Mirrors</title>
|
||||
|
||||
<para><link linkend="ctm">CTM</link>/FreeBSD is available via anonymous
|
||||
FTP from the following mirror sites. If you choose to obtain CTM via
|
||||
|
@ -2292,7 +2292,7 @@ src-all</programlisting>
|
|||
</listitem>
|
||||
</itemizedlist>
|
||||
<sect3>
|
||||
<title>The refuse file</title>
|
||||
<title>The refuse File</title>
|
||||
|
||||
<para>As mentioned above, <application>CVSup</application> uses
|
||||
a <emphasis>pull method</emphasis>. Basically, this means that
|
||||
|
@ -3188,7 +3188,7 @@ src-all</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>For more information</title>
|
||||
<title>For More Information</title>
|
||||
|
||||
<para>For the <application>CVSup</application> FAQ and other
|
||||
information about <application>CVSup</application>, see
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.133 2001/08/04 20:06:22 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ports/chapter.sgml,v 1.134 2001/08/09 23:42:33 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ports">
|
||||
|
@ -104,7 +104,7 @@
|
|||
preference.</para>
|
||||
|
||||
<itemizedlist>
|
||||
<title>Package benefits</title>
|
||||
<title>Package Benefits</title>
|
||||
|
||||
<listitem>
|
||||
<para>A compressed package tarball is typically smaller than the
|
||||
|
@ -125,7 +125,7 @@
|
|||
</itemizedlist>
|
||||
|
||||
<itemizedlist>
|
||||
<title>Ports benefits</title>
|
||||
<title>Ports Benefits</title>
|
||||
|
||||
<listitem>
|
||||
<para>Packages are normally compiled with conservative options,
|
||||
|
@ -184,7 +184,7 @@
|
|||
</sect1>
|
||||
|
||||
<sect1>
|
||||
<title>Finding your application</title>
|
||||
<title>Finding Your Application</title>
|
||||
|
||||
<para>Before you can install any applications you need to know what you
|
||||
want, and what the application is called.</para>
|
||||
|
@ -257,7 +257,7 @@
|
|||
the network.</para>
|
||||
|
||||
<example>
|
||||
<title>Downloading a package and then installing it locally</title>
|
||||
<title>Downloading a Package and then Installing It Locally</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>ftp -a <replaceable>ftp2.freebsd.org</replaceable></userinput>
|
||||
Connected to ftp2.freebsd.org.
|
||||
|
@ -335,7 +335,7 @@ local: lsof-4.56.4.tgz remote: lsof-4.56.4.tgz
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Managing packages</title>
|
||||
<title>Managing Packages</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>packages</primary>
|
||||
|
@ -538,7 +538,7 @@ R-deps: </screen>
|
|||
are ready to do the actual installation.</para>
|
||||
|
||||
<sect3 id="ports-cd">
|
||||
<title>Installing ports from a CDROM</title>
|
||||
<title>Installing Ports from a CDROM</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>ports</primary>
|
||||
|
@ -630,7 +630,7 @@ R-deps: </screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="ports-inet">
|
||||
<title>Installing ports from the Internet</title>
|
||||
<title>Installing Ports from the Internet</title>
|
||||
|
||||
<para>As with the last section, this section makes an assumption
|
||||
that you have a working Internet connection. If you do not,
|
||||
|
@ -1252,7 +1252,7 @@ arcade game.</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="ports-broken">
|
||||
<title>Help! This port is broken!</title>
|
||||
<title>Help! This Port Is Broken!</title>
|
||||
|
||||
<para>If you come across a port that doesn't work for you, there are
|
||||
a few things you can do, including:</para>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.44 2001/08/09 23:42:33 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.45 2001/08/10 21:28:59 jim Exp $
|
||||
-->
|
||||
|
||||
<chapter id="ppp-and-slip">
|
||||
|
@ -259,7 +259,7 @@ tun3: flags=8010<POINTOPOINT,MULTICAST> mtu 1500</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Check the <devicename>tun</devicename> device</title>
|
||||
<title>Check the <devicename>tun</devicename> Device</title>
|
||||
|
||||
<para>Under normal circumstances, most users will only require one
|
||||
<devicename>tun</devicename> device
|
||||
|
@ -847,7 +847,7 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
|
|||
</sect5>
|
||||
|
||||
<sect5>
|
||||
<title>PPP shells for Static-IP Users</title>
|
||||
<title>PPP Shells for Static-IP Users</title>
|
||||
<indexterm><primary>PPP shells</primary></indexterm>
|
||||
|
||||
<para>Create the <filename>ppp-shell</filename> file as above
|
||||
|
@ -870,7 +870,7 @@ exec /usr/sbin/ppp -direct $IDENT</programlisting>
|
|||
</sect5>
|
||||
|
||||
<sect5>
|
||||
<title>Setting up ppp.conf for dynamic-IP users</title>
|
||||
<title>Setting up ppp.conf for Dynamic-IP Users</title>
|
||||
|
||||
<para>The <filename>/etc/ppp/ppp.conf</filename> file should
|
||||
contain something along the lines of:</para>
|
||||
|
@ -900,8 +900,8 @@ ttyd1:
|
|||
</sect5>
|
||||
|
||||
<sect5>
|
||||
<title>Setting up <filename>ppp.conf</filename> for static-IP
|
||||
users</title>
|
||||
<title>Setting up <filename>ppp.conf</filename> for Static-IP
|
||||
Users</title>
|
||||
|
||||
<para>Along with the contents of the sample
|
||||
<filename>/usr/share/examples/ppp/ppp.conf</filename> above you should add
|
||||
|
@ -938,7 +938,7 @@ mary:
|
|||
|
||||
<sect4>
|
||||
<title>More on <command>mgetty</command>, AutoPPP, and MS
|
||||
extensions</title>
|
||||
Extensions</title>
|
||||
|
||||
<sect5 id="userppp-mgetty">
|
||||
<title><command>mgetty</command> and AutoPPP</title>
|
||||
|
@ -1006,7 +1006,7 @@ exec /usr/sbin/ppp -direct pap$IDENT</programlisting>
|
|||
</sect5>
|
||||
|
||||
<sect5>
|
||||
<title>MS extensions</title>
|
||||
<title>MS Extensions</title>
|
||||
<indexterm><primary>DNS</primary></indexterm>
|
||||
<indexterm><primary>NetBIOS</primary></indexterm>
|
||||
<indexterm><primary>PPP</primary><secondary>Microsoft extensions</secondary></indexterm>
|
||||
|
@ -1037,7 +1037,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
</sect4>
|
||||
|
||||
<sect4 id="userppp-PAPnCHAP">
|
||||
<title>PAP and CHAP authentication</title>
|
||||
<title>PAP and CHAP Authentication</title>
|
||||
<indexterm><primary>PAP</primary></indexterm>
|
||||
<indexterm><primary>CHAP</primary></indexterm>
|
||||
<para>Some ISPs set their system up so that the authentication
|
||||
|
@ -1111,8 +1111,8 @@ set nbns 203.14.100.5</programlisting>
|
|||
</sect4>
|
||||
|
||||
<sect4>
|
||||
<title>Changing your <command>ppp</command> configuration on the
|
||||
fly</title>
|
||||
<title>Changing Your <command>ppp</command> Configuration on the
|
||||
Fly</title>
|
||||
|
||||
<para>It is possible to talk to the <command>ppp</command>
|
||||
program while it is running in the background, but only if a
|
||||
|
@ -1134,7 +1134,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="userppp-final">
|
||||
<title>Final system configuration</title>
|
||||
<title>Final System Configuration</title>
|
||||
<indexterm><primary>PPP</primary><secondary>configuration</secondary></indexterm>
|
||||
|
||||
<para>You now have <command>ppp</command> configured, but there
|
||||
|
@ -1379,7 +1379,7 @@ set nbns 203.14.100.5</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Using <command>pppd</command> as a client</title>
|
||||
<title>Using <command>pppd</command> as a Client</title>
|
||||
<indexterm><primary>PPP</primary><secondary>client</secondary></indexterm>
|
||||
<indexterm><primary>Cisco</primary></indexterm>
|
||||
<para>The following <filename>/etc/ppp/options</filename> might be
|
||||
|
@ -1567,7 +1567,7 @@ defaultroute # put this if you want that PPP server will be
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Using <command>pppd</command> as a server</title>
|
||||
<title>Using <command>pppd</command> as a Server</title>
|
||||
|
||||
<para><filename>/etc/ppp/options</filename> should contain something
|
||||
similar to the following:</para>
|
||||
|
@ -2186,7 +2186,7 @@ ppp_profile="default" # or your provider</programlisting>
|
|||
this should not be a problem unless you have deleted it.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Things you have to do only once</title>
|
||||
<title>Things You Have to Do Only Once</title>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
|
@ -2286,7 +2286,7 @@ nameserver 128.32.136.12</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Making a SLIP connection</title>
|
||||
<title>Making a SLIP Connection</title>
|
||||
<indexterm><primary>SLIP</primary><secondary>connecting with</secondary></indexterm>
|
||||
<procedure>
|
||||
<step>
|
||||
|
@ -2337,7 +2337,7 @@ output ***\x0d, echo \x0aCONNECTED\x0a</programlisting>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>How to shutdown the connection</title>
|
||||
<title>How to Shutdown the Connection</title>
|
||||
|
||||
<para>Do the following:</para>
|
||||
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.65 2001/08/06 22:59:24 chern Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/security/chapter.sgml,v 1.66 2001/08/09 23:42:34 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="security">
|
||||
|
@ -215,7 +215,7 @@
|
|||
linkend="security-intro">last section</link> of this chapter.</para>
|
||||
|
||||
<sect2 id="securing-root-and-staff">
|
||||
<title>Securing the root account and staff accounts</title>
|
||||
<title>Securing the <username>root</username> Account and Staff Accounts</title>
|
||||
<indexterm>
|
||||
<primary><command>su</command></primary>
|
||||
</indexterm>
|
||||
|
@ -887,7 +887,7 @@
|
|||
for compatibility reasons.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Recognizing your crypt mechanism</title>
|
||||
<title>Recognizing Your Crypt Mechanism</title>
|
||||
|
||||
<para>It is pretty easy to identify which encryption method
|
||||
FreeBSD is set up to use. Examining the encrypted passwords in
|
||||
|
@ -1020,7 +1020,7 @@ lrwxr-xr-x 1 root wheel 15 Mar 19 06:56 libcrypt_p.a -> libdescrypt_p.a</s
|
|||
connections to anywhere.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Secure connection initialization</title>
|
||||
<title>Secure Connection Initialization</title>
|
||||
|
||||
<para>To initialize S/Key for the first time, change your password,
|
||||
or change your seed while logged in over a secure connection
|
||||
|
@ -1052,7 +1052,7 @@ DEFY CLUB PRO NASH LACE SOFT</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Insecure connection initialization</title>
|
||||
<title>Insecure Connection Initialization</title>
|
||||
|
||||
<para>To initialize S/Key or change your secret password over an
|
||||
insecure connection, you will need to already have a secure
|
||||
|
@ -1098,7 +1098,7 @@ CURE MIKE BANE HIM RACY GORE</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Generating a single one-time password</title>
|
||||
<title>Generating a Single one-time Password</title>
|
||||
|
||||
<para>Once you've initialized S/Key, when you login you will be
|
||||
presented with a prompt like this:</para>
|
||||
|
@ -1163,7 +1163,7 @@ Last login: Tue Mar 21 11:56:41 from 10.0.0.2 ... </screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Generating multiple one-time passwords</title>
|
||||
<title>Generating Multiple one-time Passwords</title>
|
||||
|
||||
<para>Sometimes you have to go places where you do not have
|
||||
access to a trusted machine or secure connection. In this case,
|
||||
|
@ -1192,7 +1192,7 @@ Enter secret password: <userinput><secret password></userinput>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Restricting use of Unix passwords</title>
|
||||
<title>Restricting Use of Unix Passwords</title>
|
||||
|
||||
<para>Restrictions can be placed on the use of Unix passwords based
|
||||
on the host name, user name, terminal port, or IP address of a
|
||||
|
@ -1276,7 +1276,7 @@ permit port ttyd0</programlisting>
|
|||
of restrictive export controls on cryptographic code from the USA.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Creating the initial database</title>
|
||||
<title>Creating the Initial Database</title>
|
||||
|
||||
<para>This is done on the Kerberos server only. First make sure that
|
||||
you do not have any old Kerberos databases around. You should change
|
||||
|
@ -1373,7 +1373,7 @@ Master key entered. BEWARE!</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Making it all run</title>
|
||||
<title>Making It All Run</title>
|
||||
|
||||
<para>Two principals need to be added to the database for
|
||||
<emphasis>each</emphasis> system that will be secured with Kerberos.
|
||||
|
@ -1439,7 +1439,7 @@ Edit O.K.
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Creating the server file</title>
|
||||
<title>Creating the Server File</title>
|
||||
|
||||
<para>We now have to extract all the instances which define the services
|
||||
on each machine. For this we use the <command>ext_srvtab</command>
|
||||
|
@ -1477,7 +1477,7 @@ Generating 'grunt-new-srvtab'....</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Populating the database</title>
|
||||
<title>Populating the Database</title>
|
||||
|
||||
<para>We now have to add some user entries into the database. First
|
||||
let's create an entry for the user <username>jane</username>. Use the
|
||||
|
@ -1513,7 +1513,7 @@ Edit O.K.
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Testing it all out</title>
|
||||
<title>Testing It All Out</title>
|
||||
|
||||
<para>First we have to start the Kerberos daemons. NOTE that if you
|
||||
have correctly edited your <filename>/etc/rc.conf</filename> then this
|
||||
|
@ -1574,7 +1574,7 @@ Password changed.</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Adding <command>su</command> privileges</title>
|
||||
<title>Adding <command>su</command> Privileges</title>
|
||||
|
||||
<para>Kerberos allows us to give <emphasis>each</emphasis> user who
|
||||
needs root privileges their own <emphasis>separate</emphasis>
|
||||
|
@ -1643,7 +1643,7 @@ May 2 20:43:12 May 3 04:43:12 krbtgt.GRONDAR.ZA@GRONDAR.ZA</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Using other commands</title>
|
||||
<title>Using Other Commands</title>
|
||||
|
||||
<para>In an earlier example, we created a principal called
|
||||
<literal>jane</literal> with an instance <literal>root</literal>.
|
||||
|
@ -1743,7 +1743,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</note>
|
||||
|
||||
<sect2>
|
||||
<title>What is a firewall?</title>
|
||||
<title>What Is a Firewall?</title>
|
||||
|
||||
<para>There are currently two distinct types of firewalls in common use
|
||||
on the Internet today. The first type is more properly called a
|
||||
|
@ -1769,7 +1769,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
document.</para>
|
||||
|
||||
<sect3 id="firewalls-packet-filters">
|
||||
<title>Packet filtering routers</title>
|
||||
<title>Packet Filtering Routers</title>
|
||||
|
||||
<para>A router is a machine which forwards packets between two or more
|
||||
networks. A packet filtering router has an extra piece of code in
|
||||
|
@ -1798,7 +1798,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="firewalls-proxy-servers">
|
||||
<title>Proxy servers</title>
|
||||
<title>Proxy Servers</title>
|
||||
|
||||
<para>Proxy servers are machines which have had the normal system
|
||||
daemons (telnetd, ftpd, etc) replaced with special servers. These
|
||||
|
@ -1828,7 +1828,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>What does IPFW allow me to do?</title>
|
||||
<title>What Does IPFW Allow Me to Do?</title>
|
||||
<indexterm><primary><command>ipfw</command></primary></indexterm>
|
||||
|
||||
<para><command>IPFW</command>, the software supplied with
|
||||
|
@ -1941,7 +1941,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
entries.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Altering the IPFW rules</title>
|
||||
<title>Altering the IPFW Rules</title>
|
||||
|
||||
<para>The syntax for this form of the command is:
|
||||
<cmdsynopsis>
|
||||
|
@ -2248,7 +2248,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Listing the IPFW rules</title>
|
||||
<title>Listing the IPFW Rules</title>
|
||||
|
||||
<para>The syntax for this form of the command is:
|
||||
<cmdsynopsis>
|
||||
|
@ -2294,7 +2294,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Flushing the IPFW rules</title>
|
||||
<title>Flushing the IPFW Rules</title>
|
||||
|
||||
<para>The syntax for flushing the chain is:
|
||||
<cmdsynopsis>
|
||||
|
@ -2310,7 +2310,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Clearing the IPFW packet counters</title>
|
||||
<title>Clearing the IPFW Packet Counters</title>
|
||||
|
||||
<para>The syntax for clearing one or more packet counters is:
|
||||
<cmdsynopsis>
|
||||
|
@ -2327,7 +2327,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Example commands for ipfw</title>
|
||||
<title>Example Commands for ipfw</title>
|
||||
|
||||
<para>This command will deny all packets from the host <hostid
|
||||
role="fqdn">evil.crackers.org</hostid> to the telnet port of the
|
||||
|
@ -2364,7 +2364,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Building a packet filtering firewall</title>
|
||||
<title>Building a Packet Filtering Firewall</title>
|
||||
|
||||
<note>
|
||||
<para>The following suggestions are just that: suggestions. The
|
||||
|
@ -2543,7 +2543,7 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
options IPSEC_ESP #IP security (crypto; define w/IPSEC)</programlisting>
|
||||
|
||||
<sect2>
|
||||
<title>Transport mode example with IPv4</title>
|
||||
<title>Transport Mode Example with IPv4</title>
|
||||
|
||||
<para>Let's setup security association to deploy a secure channel
|
||||
between HOST A (10.2.3.4) and HOST B (10.6.7.8). Here we show a little
|
||||
|
@ -2638,7 +2638,7 @@ spdadd 10.6.7.8 10.2.3.4 any -P out ipsec
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Transport mode example with IPv6</title>
|
||||
<title>Transport Mode Example with IPv6</title>
|
||||
|
||||
<para>Another example using IPv6.</para>
|
||||
|
||||
|
@ -2693,7 +2693,7 @@ spdadd 10.6.7.8 10.2.3.4 any -P out ipsec
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Tunnel mode example with IPv4</title>
|
||||
<title>Tunnel Mode Example with IPv4</title>
|
||||
|
||||
<para>Tunnel mode between two security gateways</para>
|
||||
|
||||
|
@ -2761,7 +2761,7 @@ spdadd 10.6.7.8 10.2.3.4 any -P out ipsec
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Tunnel mode example with IPv6</title>
|
||||
<title>Tunnel Mode Example with IPv6</title>
|
||||
|
||||
<para>Encryption algorithm is 3des-cbc, and authentication algorithm
|
||||
for ESP is hmac-sha1. Authentication algorithm for AH is hmac-md5.
|
||||
|
@ -2869,7 +2869,7 @@ spdadd 10.6.7.8 10.2.3.4 any -P out ipsec
|
|||
in the base system since FreeBSD 4.0.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Advantages of using OpenSSH</title>
|
||||
<title>Advantages of Using OpenSSH</title>
|
||||
|
||||
<para>Normally, when using &man.telnet.1; or &man.rlogin.1;,
|
||||
data is sent over the network in an clear, un-encrypted form.
|
||||
|
@ -2896,7 +2896,7 @@ spdadd 10.6.7.8 10.2.3.4 any -P out ipsec
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>SSH client</title>
|
||||
<title>SSH Client</title>
|
||||
<indexterm>
|
||||
<primary>OpenSSH</primary>
|
||||
<secondary>client</secondary>
|
||||
|
@ -2925,7 +2925,7 @@ user@foobardomain.com's password: <userinput>*******</userinput></screen>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Secure copy</title>
|
||||
<title>Secure Copy</title>
|
||||
<indexterm>
|
||||
<primary>OpenSSH</primary>
|
||||
<secondary>secure copy</secondary>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.39 2001/08/09 22:50:09 logo Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/serialcomms/chapter.sgml,v 1.40 2001/08/09 23:42:34 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="serialcomms">
|
||||
|
@ -112,7 +112,7 @@
|
|||
required.</para>
|
||||
|
||||
<sect4 id="term-cables-null">
|
||||
<title>Null-modem cables</title>
|
||||
<title>Null-modem Cables</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>null-modem cable</primary>
|
||||
|
@ -819,7 +819,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
</sect2>
|
||||
|
||||
<sect2 id="term-debug">
|
||||
<title>Troubleshooting your connection</title>
|
||||
<title>Troubleshooting Your Connection</title>
|
||||
|
||||
<para>Even with the most meticulous attention to detail, something could
|
||||
still go wrong while setting up a terminal. Here is a list of
|
||||
|
@ -1455,7 +1455,7 @@ AT&B2&W</programlisting>
|
|||
on your system.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Checking out the FreeBSD system</title>
|
||||
<title>Checking out the FreeBSD System</title>
|
||||
|
||||
<para>Hook up your modem to your FreeBSD system, boot the system, and,
|
||||
if your modem has status indication lights, watch to see whether the
|
||||
|
@ -1568,7 +1568,7 @@ AT&B2&W</programlisting>
|
|||
use zmodem to transfer it to your machine.</para>
|
||||
|
||||
<sect2>
|
||||
<title>My stock Hayes modem is not supported, what can I do?</title>
|
||||
<title>My Stock Hayes Modem Is Not Supported, What Can I Do?</title>
|
||||
|
||||
<para>Actually, the man page for <command>tip</command> is out of date.
|
||||
There is a generic Hayes dialer already built in. Just use
|
||||
|
@ -1599,7 +1599,7 @@ AT&B2&W</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="direct-at">
|
||||
<title>How am I expected to enter these AT commands?</title>
|
||||
<title>How Am I Expected to Enter These AT Commands?</title>
|
||||
|
||||
<indexterm>
|
||||
<primary><filename>/etc/remote</filename></primary>
|
||||
|
@ -1633,8 +1633,8 @@ AT&B2&W</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>The <literal>@</literal> sign for the pn capability does not
|
||||
work!</title>
|
||||
<title>The <literal>@</literal> Sign for the pn Capability Does Not
|
||||
Work!</title>
|
||||
|
||||
<para>The <literal>@</literal> sign in the phone number capability tells
|
||||
tip to look in <filename>/etc/phones</filename> for a phone number.
|
||||
|
@ -1646,7 +1646,7 @@ AT&B2&W</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How can I dial a phone number on the command line?</title>
|
||||
<title>How Can I Dial a Phone Number on the Command Line?</title>
|
||||
|
||||
<para>Put what is called a <quote>generic</quote> entry in your
|
||||
<filename>/etc/remote</filename> file. For example:</para>
|
||||
|
@ -1672,7 +1672,7 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Do I have to type in the bps rate every time I do that?</title>
|
||||
<title>Do I Have to Type in the bps Rate Every Time I Do That?</title>
|
||||
|
||||
<para>Put in an entry for <literal>tip1200</literal> or
|
||||
<literal>cu1200</literal>, but go ahead and use whatever bps rate is
|
||||
|
@ -1683,7 +1683,7 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>I access a number of hosts through a terminal server.</title>
|
||||
<title>I Access a Number of Hosts through a Terminal Server.</title>
|
||||
|
||||
<para>Rather than waiting until you are connected and typing
|
||||
<command>CONNECT <host></command> each time, use tip's
|
||||
|
@ -1703,7 +1703,7 @@ deep13:Gizmonics Institute terminal server:\
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Can tip try more than one line for each site?</title>
|
||||
<title>Can Tip Try More Than one Line for each Site?</title>
|
||||
|
||||
<para>This is often a problem where a university has several modem lines
|
||||
and several thousand students trying to use them...</para>
|
||||
|
@ -1731,15 +1731,15 @@ big-university 5551114</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Why do I have to hit
|
||||
<title>Why Do I Have to Hit
|
||||
<keycombo action="simul">
|
||||
<keycap>Ctrl</keycap><keycap>P</keycap>
|
||||
</keycombo>
|
||||
twice to send
|
||||
Twice to Send
|
||||
<keycombo action="simul">
|
||||
<keycap>Ctrl</keycap><keycap>P</keycap>
|
||||
</keycombo>
|
||||
once?</title>
|
||||
Once?</title>
|
||||
|
||||
<para><keycombo action="simul"><keycap>Ctrl</keycap><keycap>P</keycap></keycombo> is the default <quote>force</quote> character, used to tell
|
||||
<command>tip</command> that the next character is literal data. You
|
||||
|
@ -1776,7 +1776,7 @@ big-university 5551114</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Suddenly everything I type is in UPPER CASE??</title>
|
||||
<title>Suddenly Everything I Type Is in UPPER CASE??</title>
|
||||
|
||||
<para>You must have pressed
|
||||
<keycombo action="simul">
|
||||
|
@ -1811,7 +1811,7 @@ raisechar=^^</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How can I do file transfers with <command>tip</command>?</title>
|
||||
<title>How Can I Do File Transfers with <command>tip</command>?</title>
|
||||
|
||||
<para>If you are talking to another Unix system, you can send and
|
||||
receive files with <command>~p</command> (put) and
|
||||
|
@ -1836,7 +1836,7 @@ raisechar=^^</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>How can I run zmodem with <command>tip</command>?</title>
|
||||
<title>How Can I Run zmodem with <command>tip</command>?</title>
|
||||
|
||||
<para>To receive files, start the sending program on the remote end.
|
||||
Then, type <command>~C rz</command> to begin receiving them
|
||||
|
@ -2221,7 +2221,7 @@ boot:</screen>
|
|||
and the console eventually selected.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Case 1: You set the flags to 0x10 for sio0</title>
|
||||
<title>Case 1: You Set the flags to 0x10 for sio0</title>
|
||||
|
||||
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x10 irq 4</programlisting>
|
||||
|
||||
|
@ -2284,7 +2284,7 @@ boot:</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>Case 2: You set the flags to 0x30 for sio0</title>
|
||||
<title>Case 2: You Set the flags to 0x30 for sio0</title>
|
||||
|
||||
<programlisting>device sio0 at isa? port "IO_COM1" tty flags 0x30 irq 4</programlisting>
|
||||
|
||||
|
@ -2351,7 +2351,7 @@ boot:</screen>
|
|||
<title>Tips for the Serial Console</title>
|
||||
|
||||
<sect3>
|
||||
<title>Setting A Faster Serial Port Speed</title>
|
||||
<title>Setting a Faster Serial Port Speed</title>
|
||||
|
||||
<para>By default the serial port settings are set to 9600 baud, 8
|
||||
bits, no parity, 1 stop bit. If you wish to change the speed, you
|
||||
|
@ -2371,8 +2371,8 @@ boot:</screen>
|
|||
</sect3>
|
||||
|
||||
<sect3 id="serialconsole-com2">
|
||||
<title>Using Serial Port Other Than <devicename>sio0</devicename> For
|
||||
The Console</title>
|
||||
<title>Using Serial Port Other Than <devicename>sio0</devicename> for
|
||||
the Console</title>
|
||||
|
||||
<para>Using a port other than <devicename>sio0</devicename> as the
|
||||
console requires some recompiling. If you want to use another
|
||||
|
@ -2494,7 +2494,7 @@ ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
|||
will override the settings in the boot block.</para>
|
||||
|
||||
<sect3>
|
||||
<title>Setting Up the Serial Console</title>
|
||||
<title>Setting up the Serial Console</title>
|
||||
|
||||
<para>You can easily specify the boot loader and the kernel to use the
|
||||
serial console by writing just one line in
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.23 2001/08/04 19:05:48 jim Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/users/chapter.sgml,v 1.24 2001/08/09 23:42:35 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="users">
|
||||
|
@ -497,7 +497,7 @@ Goodbye!
|
|||
make sure you know what you're doing.</para>
|
||||
|
||||
<example>
|
||||
<title>rmuser interactive account removal</title>
|
||||
<title>rmuser Interactive Account Removal</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>rmuser jru</userinput>
|
||||
Matching password entry:
|
||||
|
@ -614,7 +614,7 @@ Other information:</screen>
|
|||
</note>
|
||||
|
||||
<example>
|
||||
<title>Changing your password</title>
|
||||
<title>Changing Your Password</title>
|
||||
|
||||
<screen>&prompt.user; <userinput>passwd</userinput>
|
||||
Changing local password for jru.
|
||||
|
@ -626,7 +626,7 @@ passwd: done</screen>
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Changing another user's password as the superuser</title>
|
||||
<title>Changing Another User's Password as the Superuser</title>
|
||||
|
||||
<screen>&prompt.root; <userinput>passwd jru</userinput>
|
||||
Changing local password for jru.
|
||||
|
@ -965,7 +965,7 @@ passwd: done</screen>
|
|||
then confirm that it exists you can use:</para>
|
||||
|
||||
<example>
|
||||
<title>Adding a group using &man.pw.8;</title>
|
||||
<title>Adding a Group Using &man.pw.8;</title>
|
||||
|
||||
<screen>&prompt.root; <userinput><command>pw</command> groupadd <groupname>teamtwo</groupname></userinput>
|
||||
&prompt.root; <userinput><command>pw</command> groupshow <groupname>teamtwo</groupname></userinput>
|
||||
|
@ -979,7 +979,7 @@ teamtwo:*:1100:</screen>
|
|||
the <groupname>teamtwo</groupname> group.</para>
|
||||
|
||||
<example>
|
||||
<title>Adding somebody to a group using &man.pw.8;</title>
|
||||
<title>Adding Somebody to a Group Using &man.pw.8;</title>
|
||||
|
||||
<screen>&prompt.root; <userinput><command>pw</command> groupmod <groupname>teamtwo</groupname> <option>-M</option> <username>jru</username></userinput>
|
||||
&prompt.root; <userinput><command>pw</command> groupshow <groupname>teamtwo</groupname></userinput>
|
||||
|
@ -998,7 +998,7 @@ teamtwo:*:1100:jru</screen>
|
|||
additionally data from <filename>/etc/passwd</filename>.</para>
|
||||
|
||||
<example>
|
||||
<title>Using &man.id.1; to determine group membership</title>
|
||||
<title>Using &man.id.1; to Determine Group Membership</title>
|
||||
|
||||
<screen>&prompt.user; <userinput><command>id</command> <username>jru</username></userinput>
|
||||
uid=1001(jru) gid=1001(jru) groups=1001(jru), 1100(teamtwo)</screen>
|
||||
|
|
|
@ -1,7 +1,7 @@
|
|||
<!--
|
||||
The FreeBSD Documentation Project
|
||||
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v 1.38 2001/08/09 22:50:10 logo Exp $
|
||||
$FreeBSD: doc/en_US.ISO8859-1/books/handbook/x11/chapter.sgml,v 1.39 2001/08/09 23:42:35 chern Exp $
|
||||
-->
|
||||
|
||||
<chapter id="x11">
|
||||
|
@ -129,7 +129,7 @@
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Installing XFree86 4.X software</title>
|
||||
<title>Installing XFree86 4.X Software</title>
|
||||
|
||||
<para><application>XFree86 4</application> can be installed
|
||||
using the FreeBSD ports system or using &man.pkg.add.1;. If the
|
||||
|
@ -268,7 +268,7 @@ 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>
|
||||
|
||||
|
@ -420,7 +420,7 @@ EndSection</programlisting>
|
|||
</sect2>
|
||||
|
||||
<sect2 id="antialias">
|
||||
<title>Anti-Aliasing your fonts</title>
|
||||
<title>Anti-Aliasing Your Fonts</title>
|
||||
|
||||
<para>Starting with version 4.0.2, <application>XFree86</application>
|
||||
supports anti-aliased
|
||||
|
@ -725,7 +725,7 @@ match any family == "LuciduxMono" edit family =+ "Lucidux Mono";</programl
|
|||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Running A Network Display Server</title>
|
||||
<title>Running a Network Display Server</title>
|
||||
<para>In order for other clients to connect to your display
|
||||
server, you will need to edit the access control rules, and
|
||||
enable the connection listener. By default these are set to
|
||||
|
@ -926,7 +926,7 @@ DisplayManager.requestPort: 0</screen>
|
|||
</sect3>
|
||||
</sect2>
|
||||
<sect2 id="x11-wm-kde2-details">
|
||||
<title>More details on KDE2</title>
|
||||
<title>More Details on KDE2</title>
|
||||
|
||||
<para>Now that <application>KDE2</application> is installed on
|
||||
your system, you'll find that you can learn a lot from its
|
||||
|
@ -1040,7 +1040,7 @@ esac</screen>
|
|||
|
||||
</sect3>
|
||||
<sect3 id="x11-wm-kde2-antialias">
|
||||
<title>Anti-aliased fonts</title>
|
||||
<title>Anti-aliased Fonts</title>
|
||||
|
||||
<para>Tired of blocky staircase edges to your fonts under X11?
|
||||
Tired of unreadable text in web browsers? Well, no
|
||||
|
|
Loading…
Reference in a new issue