Remove support for FreeBSD prior to 7.0 from the Handbook.
More specifically: - mentions of old versions of FreeBSD in historical context are left in tact - remove section about KerberosIV - remove section about SAP R/3 - remove mentions of XFree86 - only support gvinum - update examples to 7.X or 8.X - remove Alpha support - add COMPAT_FREEBSD[67] kernel options - csup(1) now only in the base system - update (tty) device names, add warnings for 7.X - remove MD5 from the port checksum algorithms - update port versions (probably not all) - add definitions for ctm-src[5-8] to mailing-lists.ent Reviewed by: bcr, joel, remko, simon
This commit is contained in:
Rene Ladan
parent
6c5f66f13e
commit
fffad858e3
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=36653
25 changed files with 315 additions and 2920 deletions
en_US.ISO8859-1
books/handbook
advanced-networking
audit
basics
boot
config
cutting-edge
disks
firewalls
install
introduction
kernelconfig
l10n
linuxemu
mail
mirrors
multimedia
network-servers
ports
ppp-and-slip
printing
security
serialcomms
vinum
x11
share/sgml
|
|
@ -659,13 +659,13 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
|
|||
&man.mrouted.8;.</para>
|
||||
|
||||
<note>
|
||||
<para>As of &os; 7.0 the &man.mrouted.8; multicast routing daemon
|
||||
has been removed from the base system. It implements the
|
||||
<para>The &man.mrouted.8; multicast routing daemon
|
||||
implements the
|
||||
<acronym>DVMRP</acronym> multicast routing protocol, which has
|
||||
largely been replaced by &man.pim.4; in many multicast
|
||||
installations. The related &man.map-mbone.8; and
|
||||
&man.mrinfo.8; utilities have also been removed. These programs
|
||||
are now available in the &os; Ports Collection as
|
||||
installations. &man.mrouted.8; and the related &man.map-mbone.8; and
|
||||
&man.mrinfo.8; utilities
|
||||
are available in the &os; Ports Collection as
|
||||
<filename role="package">net/mrouted</filename>.</para>
|
||||
</note>
|
||||
</sect2>
|
||||
|
|
@ -774,7 +774,7 @@ route_net2="-net 192.168.1.0/24 192.168.1.1"</programlisting>
|
|||
implementation of these protocols enable high speed bursting
|
||||
of data and prioritized traffic flow.</para>
|
||||
|
||||
<para>Since the 6.0 version, &os; supports networks that operate
|
||||
<para>&os; supports networks that operate
|
||||
using 802.11a, 802.11b, and 802.11g. The WPA and 802.11i
|
||||
security protocols are likewise supported (in conjunction with
|
||||
any of 11a, 11b, and 11g) and QoS and traffic prioritization
|
||||
|
|
@ -2528,7 +2528,7 @@ c2e8bc80 0 250 00:02:72:00:d4:1a 00:07:e0:00:0b:ca 3 6 OPEN</scree
|
|||
device are paired. Alternatively, you can initiate pairing on the remote
|
||||
device.</para>
|
||||
|
||||
<para>On &os; 5.5, 6.1 and newer, the following line can be added to the
|
||||
<para>The following line can be added to the
|
||||
<filename>/etc/rc.conf</filename> file to have
|
||||
<application>hcsecd</application> started automatically on system
|
||||
start:</para>
|
||||
|
|
@ -2612,7 +2612,7 @@ Bluetooth Profile Descriptor List:
|
|||
<screen>&prompt.user; <userinput>sdpcontrol -a 00:01:03:fc:6e:ec search OPUSH</userinput></screen>
|
||||
|
||||
<para>Offering services on &os; to Bluetooth clients is done with the
|
||||
&man.sdpd.8; server. On &os; 5.5, 6.1 and newer, the following line can
|
||||
&man.sdpd.8; server. The following line can
|
||||
be added to the <filename>/etc/rc.conf</filename> file:</para>
|
||||
|
||||
<programlisting>sdpd_enable="YES"</programlisting>
|
||||
|
|
@ -3001,42 +3001,9 @@ ifconfig_fxp1="up"</programlisting>
|
|||
provides faster Spanning Tree convergence than legacy STP, the
|
||||
protocol will exchange information with neighbouring switches
|
||||
to quickly transition to forwarding without creating
|
||||
loops.</para>
|
||||
|
||||
<para>The following table shows the supported operating
|
||||
modes:</para>
|
||||
|
||||
<informaltable frame="none" pgwide="1">
|
||||
<tgroup cols="3">
|
||||
<thead>
|
||||
<row>
|
||||
<entry>OS Version</entry>
|
||||
<entry>STP Modes</entry>
|
||||
<entry>Default Mode</entry>
|
||||
</row>
|
||||
</thead>
|
||||
|
||||
<tbody>
|
||||
<row>
|
||||
<entry>&os; 5.4—&os; 6.2</entry>
|
||||
<entry>STP</entry>
|
||||
<entry>STP</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>&os; 6.3+</entry>
|
||||
<entry>RSTP or STP</entry>
|
||||
<entry>STP</entry>
|
||||
</row>
|
||||
|
||||
<row>
|
||||
<entry>&os; 7.0+</entry>
|
||||
<entry>RSTP or STP</entry>
|
||||
<entry>RSTP</entry>
|
||||
</row>
|
||||
</tbody>
|
||||
</tgroup>
|
||||
</informaltable>
|
||||
loops.
|
||||
&os; supports RTSP and STP as operating modes, with RTSP
|
||||
being the default mode.</para>
|
||||
|
||||
<para>Spanning Tree can be enabled on member interfaces using
|
||||
the <literal>stp</literal> command. For a bridge with
|
||||
|
|
@ -3782,9 +3749,9 @@ ifconfig_lagg0="laggproto failover laggport bge0 laggport wlan0 DHCP"
|
|||
both BOOTP and <acronym>DHCP</acronym> requests.</para>
|
||||
|
||||
<para><application>ISC DHCP
|
||||
3.0</application> is not part of the base
|
||||
3.1</application> is not part of the base
|
||||
system. You will first need to install the
|
||||
<filename role="package">net/isc-dhcp30-server</filename> port or the
|
||||
<filename role="package">net/isc-dhcp31-server</filename> port or the
|
||||
corresponding package.</para>
|
||||
|
||||
<para>Once <application>ISC DHCP</application> is installed, it
|
||||
|
|
@ -4290,8 +4257,8 @@ cd /usr/src/etc; make distribution</programlisting>
|
|||
(ISA and PCI) BRI cards and the AVM T1 PCI PRI cards.</para>
|
||||
|
||||
<para>For documentation on <application>isdn4bsd</application>,
|
||||
have a look at <filename>/usr/share/examples/isdn/</filename>
|
||||
directory on your FreeBSD system or at the <ulink
|
||||
have a look at
|
||||
the <ulink
|
||||
url="http://www.freebsd-support.de/i4b/">homepage of
|
||||
isdn4bsd</ulink> which also has pointers to hints, erratas and
|
||||
much more documentation such as the <ulink
|
||||
|
|
|
|||
|
|
@ -581,7 +581,7 @@ trailer,133</programlisting>
|
|||
<literal>return</literal> token indicates the successful execution, and the <literal>trailer</literal>
|
||||
concludes the record.</para>
|
||||
|
||||
<para>In &os; 6.3 and later, <command>praudit</command> also supports
|
||||
<para><command>praudit</command> also supports
|
||||
an XML output format, which can be selected using the
|
||||
<option>-x</option> argument.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -1750,8 +1750,8 @@ root 5211 0.0 0.2 3620 1724 2 I+ 2:09AM 0:00.01 passwd</screen>
|
|||
|
||||
<listitem>
|
||||
<para>Mount the file system read-only. This is identical
|
||||
to using the <option>ro</option> (<option>rdonly</option>
|
||||
for &os; versions older than 5.2) argument to the
|
||||
to using the <option>ro</option>
|
||||
argument to the
|
||||
<option>-o</option> option.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
|
|
|
|||
|
|
@ -788,9 +788,6 @@ bitmap_name="<replaceable>/boot/splash.pcx</replaceable>"</programlisting>
|
|||
</indexterm>
|
||||
<title>Device Hints</title>
|
||||
|
||||
<note><para>This is a FreeBSD 5.0 and later feature which does not
|
||||
exist in earlier versions.</para></note>
|
||||
|
||||
<para>During initial system startup, the boot &man.loader.8; will read the
|
||||
&man.device.hints.5; file. This file stores kernel boot information
|
||||
known as variables, sometimes referred to as <quote>device hints</quote>.
|
||||
|
|
|
|||
|
|
@ -897,8 +897,8 @@ linuxemu/chapter.sgml -->
|
|||
those involved with &os;, have taken the latter
|
||||
approach.</para>
|
||||
|
||||
<para>Thanks to the contributions of Bill Paul (wpaul), as of
|
||||
&os; 5.3-RELEASE there is <quote>native</quote> support
|
||||
<para>Thanks to the contributions of Bill Paul (wpaul)
|
||||
there is <quote>native</quote> support
|
||||
for the Network Driver Interface Specification (NDIS). The
|
||||
&os; NDISulator (otherwise known as Project Evil) takes a
|
||||
&windows; driver binary and basically tricks it into
|
||||
|
|
@ -1901,9 +1901,9 @@ device_probe_and_attach: cbb0 attach returned 12</screen>
|
|||
reduce system boot times. The defaults are fairly high and can be
|
||||
responsible for <literal>15</literal> seconds of delay in the
|
||||
boot process. Reducing it to <literal>5</literal> seconds usually
|
||||
works (especially with modern drives). Newer versions of &os;
|
||||
(5.0 and higher) should use the <varname>kern.cam.scsi_delay</varname>
|
||||
boot time tunable. The tunable, and kernel config option accept
|
||||
works (especially with modern drives).
|
||||
The <varname>kern.cam.scsi_delay</varname> boot time tunable should
|
||||
be used. The tunable, and kernel config option accept
|
||||
values in terms of <emphasis>milliseconds</emphasis> and
|
||||
<emphasis>not</emphasis> <emphasis>seconds</emphasis>.</para>
|
||||
</sect3>
|
||||
|
|
|
|||
|
|
@ -116,9 +116,8 @@
|
|||
role="package">net/cvsup</filename> (if you do not want to install
|
||||
the graphical <command>cvsup</command> client, you can just install
|
||||
the port <filename>net/cvsup-without-gui</filename>).
|
||||
If you are using
|
||||
&os; 6.2-RELEASE or later, you may wish to substitute this
|
||||
with &man.csup.1;, which is now part of the base system.</para>
|
||||
You may wish to substitute this
|
||||
with &man.csup.1;, which is part of the base system.</para>
|
||||
</note>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -162,10 +161,8 @@
|
|||
|
||||
<note>
|
||||
<para>Binary updates are available for all architectures and
|
||||
releases currently supported by the security team; however,
|
||||
some features, such as the &os; operating system upgrades,
|
||||
require the latest release of &man.freebsd-update.8; and &os; 6.3
|
||||
or greater. Before updating to a new release, the current
|
||||
releases currently supported by the security team.
|
||||
Before updating to a new release, the current
|
||||
release announcements should be reviewed as they may contain
|
||||
important information pertinent to the desired release. These
|
||||
announcements may be viewed at the following link:
|
||||
|
|
@ -425,9 +422,9 @@ MergeChanges /etc/ /var/named/etc/</programlisting>
|
|||
<para>Major and minor version updates may be performed by
|
||||
providing <command>freebsd-update</command> with a release
|
||||
version target, for example, the following command will
|
||||
update to &os; 6.4:</para>
|
||||
update to &os; 8.1:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>freebsd-update -r 6.4-RELEASE upgrade</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>freebsd-update -r 8.1-RELEASE upgrade</userinput></screen>
|
||||
|
||||
<para>After the command has been received,
|
||||
<command>freebsd-update</command> will evaluate the
|
||||
|
|
@ -437,7 +434,7 @@ MergeChanges /etc/ /var/named/etc/</programlisting>
|
|||
what components have not been detected. For example:</para>
|
||||
|
||||
<screen>Looking up update.FreeBSD.org mirrors... 1 mirrors found.
|
||||
Fetching metadata signature for 6.3-RELEASE from update1.FreeBSD.org... done.
|
||||
Fetching metadata signature for 8.0-RELEASE from update1.FreeBSD.org... done.
|
||||
Fetching metadata index... done.
|
||||
Inspecting system... done.
|
||||
|
||||
|
|
@ -462,7 +459,7 @@ Does this look reasonable (y/n)? y</screen>
|
|||
similar to the following:</para>
|
||||
|
||||
<screen>WARNING: This system is running a "<replaceable>MYKERNEL</replaceable>" kernel, which is not a
|
||||
kernel configuration distributed as part of FreeBSD 6.3-RELEASE.
|
||||
kernel configuration distributed as part of FreeBSD 8.0-RELEASE.
|
||||
This kernel will not be updated: you MUST update the kernel manually
|
||||
before running "/usr/sbin/freebsd-update install"</screen>
|
||||
|
||||
|
|
@ -2009,12 +2006,6 @@ DOCSUPFILE?= /usr/share/examples/cvsup/doc-supfile</programlisting>
|
|||
problems. Hopefully, the current procedure will remain stable for a
|
||||
long time.</para>
|
||||
|
||||
<note>
|
||||
<para>Upgrading from &os; 3.<replaceable>X</replaceable> or earlier
|
||||
releases is a bit trickier; read <filename>UPDATING</filename>
|
||||
carefully if you have to perform this sort of upgrade.</para>
|
||||
</note>
|
||||
|
||||
<para>To summarize, the currently recommended way of upgrading &os;
|
||||
from sources is:</para>
|
||||
|
||||
|
|
@ -2448,8 +2439,8 @@ Script done, …</screen>
|
|||
<sect2 id="make-installworld">
|
||||
<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
|
||||
<para>
|
||||
You should now use
|
||||
<maketarget>installworld</maketarget> to install the new system
|
||||
binaries.</para>
|
||||
|
||||
|
|
@ -2837,7 +2828,7 @@ Script done, …</screen>
|
|||
process is to remove this directory and start afresh. In this
|
||||
case, keeping <filename>/usr/obj</filename> around after you
|
||||
have finished makes little sense, and will free up a large
|
||||
chunk of disk space (currently about 340 MB).</para>
|
||||
chunk of disk space (currently about 2 GB).</para>
|
||||
|
||||
<para>However, if you know what you are doing you can have
|
||||
<command>make buildworld</command> skip this step. This will
|
||||
|
|
|
|||
|
|
@ -2513,7 +2513,7 @@ sa0(ncr1:4:0): Logical unit is in process of becoming ready</screen>
|
|||
|
||||
<indexterm><primary><command>tar</command></primary></indexterm>
|
||||
|
||||
<para>On FreeBSD 5.3 and later, both GNU <command>tar</command>
|
||||
<para>Both GNU <command>tar</command>
|
||||
and the default <command>bsdtar</command> are available. The
|
||||
GNU version can be invoked with <command>gtar</command>. It
|
||||
supports remote devices using the same syntax as
|
||||
|
|
@ -3688,7 +3688,7 @@ gbde_lockdir="/etc/gbde"</programlisting>
|
|||
|
||||
<title>Disk Encryption with <command>geli</command></title>
|
||||
|
||||
<para>A new cryptographic GEOM class is available as of &os; 6.0 -
|
||||
<para>An alternative cryptographic GEOM class is available -
|
||||
<command>geli</command>. It is currently being developed by
|
||||
&a.pjd;. The <command>geli</command> utility is different to
|
||||
<command>gbde</command>; it offers different features and uses
|
||||
|
|
@ -3738,8 +3738,8 @@ gbde_lockdir="/etc/gbde"</programlisting>
|
|||
<command>geli</command> in the &os; kernel and will explain how
|
||||
to create and use a <command>geli</command> encryption provider.</para>
|
||||
|
||||
<para>In order to use <command>geli</command>, you must be running
|
||||
&os; 6.0-RELEASE or later. Super-user privileges will be
|
||||
<para>
|
||||
Super-user privileges will be
|
||||
required since modifications to the kernel are necessary.</para>
|
||||
|
||||
<procedure>
|
||||
|
|
@ -3900,13 +3900,13 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting>
|
|||
<secondary>encrypting</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>Swap encryption in &os; is easy to configure and has been
|
||||
available since &os; 5.3-RELEASE. Depending on which version
|
||||
<para>Swap encryption in &os; is easy to configure
|
||||
. Depending on which version
|
||||
of &os; is being used, different options are available
|
||||
and configuration can vary slightly. From &os; 6.0-RELEASE onwards,
|
||||
the &man.gbde.8; or &man.geli.8; encryption systems can be used
|
||||
for swap encryption. With earlier versions, only &man.gbde.8; is
|
||||
available. Both systems use the <filename>encswap</filename>
|
||||
and configuration can vary slightly.
|
||||
The &man.gbde.8; or &man.geli.8; encryption systems can be used
|
||||
for swap encryption.
|
||||
Both systems use the <filename>encswap</filename>
|
||||
<link linkend="configtuning-rcd">rc.d</link> script.</para>
|
||||
|
||||
<para>The previous section, <link linkend="disks-encrypting">Encrypting
|
||||
|
|
@ -3945,7 +3945,7 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting>
|
|||
<sect2>
|
||||
<title>Swap Encryption with &man.gbde.8;</title>
|
||||
|
||||
<para>If &os; 6.0-RELEASE or newer is being used, the
|
||||
<para>The
|
||||
<literal>.bde</literal> suffix should be added to the device in the
|
||||
respective <filename>/etc/fstab</filename> swap line:</para>
|
||||
|
||||
|
|
@ -3953,11 +3953,6 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting>
|
|||
# Device Mountpoint FStype Options Dump Pass#
|
||||
/dev/ad0s1b.bde none swap sw 0 0
|
||||
</programlisting>
|
||||
|
||||
<para>For systems prior to &os; 6.0-RELEASE, the following line
|
||||
in <filename>/etc/rc.conf</filename> is also needed:</para>
|
||||
|
||||
<programlisting>gbde_swap_enable="YES"</programlisting>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
|
|
@ -3986,10 +3981,6 @@ geli_da2_flags="-p -k /root/da2.key"</programlisting>
|
|||
|
||||
<programlisting>geli_swap_flags="-e blowfish -l 128 -s 4096 -d"</programlisting>
|
||||
|
||||
<para>For systems prior to &os; 6.2-RELEASE, use the following line:</para>
|
||||
|
||||
<programlisting>geli_swap_flags="-a blowfish -l 128 -s 4096 -d"</programlisting>
|
||||
|
||||
<para>Please refer to the description of the <command>onetime</command> command
|
||||
in the &man.geli.8; manual page for a list of possible options.</para>
|
||||
</sect2>
|
||||
|
|
|
|||
|
|
@ -256,14 +256,10 @@
|
|||
|
||||
<programlisting>pf_rules="<replaceable>/path/to/pf.conf</replaceable>"</programlisting>
|
||||
|
||||
<note>
|
||||
<para>As of &os; 7.0 the sample <filename>pf.conf</filename>
|
||||
that was in <filename class="directory">/etc/</filename> has been
|
||||
moved to <filename
|
||||
class="directory">/usr/share/examples/pf/</filename>. For &os;
|
||||
versions prior to 7.0 there is an <filename>/etc/pf.conf</filename>
|
||||
by default.</para>
|
||||
</note>
|
||||
<para>The sample <filename>pf.conf</filename>
|
||||
can be found in <filename
|
||||
class="directory">/usr/share/examples/pf/</filename>.
|
||||
</para>
|
||||
|
||||
<para>The <acronym>PF</acronym> module can also be loaded manually
|
||||
from the command line:</para>
|
||||
|
|
@ -374,7 +370,7 @@ pflog_flags="" # additional flags for pflogd startup</programli
|
|||
url="http://www.openbsd.org/faq/pf/">PF FAQ</ulink>,
|
||||
please keep in mind that different versions of &os; can
|
||||
contain different versions of PF. Currently,
|
||||
&os; 7.<replaceable>X</replaceable> and later are
|
||||
&os; is
|
||||
using the same version of <acronym>PF</acronym> as
|
||||
OpenBSD 4.1.</para>
|
||||
</warning>
|
||||
|
|
|
|||
|
|
@ -118,21 +118,6 @@
|
|||
</note>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>&os;/&arch.alpha;</title>
|
||||
|
||||
<indexterm><primary>Alpha</primary></indexterm>
|
||||
|
||||
<para>Support for the Alpha was removed beginning with
|
||||
&os; 7.0. The
|
||||
&os; 6.<replaceable>X</replaceable> series of
|
||||
releases is the last containing support for this
|
||||
architecture. Please check the <ulink
|
||||
url="http://www.FreeBSD.org/releases/index.html">Release
|
||||
Information</ulink> page of the &os; web site for more
|
||||
information.</para>
|
||||
</sect3>
|
||||
|
||||
<sect3>
|
||||
<title>&os;/&arch.amd64;</title>
|
||||
|
||||
|
|
@ -4924,8 +4909,8 @@ Please press any key to reboot.</screen>
|
|||
If you have problems, logging can be directed to the screen using
|
||||
the command <command>set log local ...</command>.</para>
|
||||
|
||||
<para>If a hard-wired connection to another FreeBSD (2.0-R or
|
||||
later) machine is available, you might also consider installing
|
||||
<para>If a hard-wired connection to another FreeBSD
|
||||
machine is available, you might also consider installing
|
||||
over a <quote>laplink</quote> parallel port cable. The data rate
|
||||
over the parallel port is much higher than what is typically
|
||||
possible over a serial line (up to 50 kbytes/sec), thus resulting
|
||||
|
|
|
|||
|
|
@ -56,7 +56,7 @@
|
|||
<indexterm><primary>4.4BSD-Lite</primary></indexterm>
|
||||
|
||||
<para>&os; is a 4.4BSD-Lite based operating system for
|
||||
Intel (x86 and &itanium;), AMD64, <trademark>Alpha</trademark>, Sun
|
||||
Intel (x86 and &itanium;), AMD64, Sun
|
||||
&ultrasparc; computers. Ports to other
|
||||
architectures are also underway. You can also
|
||||
read about <link linkend="history">the history of &os;</link>,
|
||||
|
|
@ -112,14 +112,13 @@
|
|||
|
||||
<listitem>
|
||||
<para>&os; is a <emphasis>32-bit</emphasis> operating
|
||||
system (<emphasis>64-bit</emphasis> on the Alpha, &itanium;,
|
||||
system (<emphasis>64-bit</emphasis> on the &itanium;,
|
||||
AMD64, and &ultrasparc;) and was designed as such from the ground
|
||||
up.</para>
|
||||
</listitem>
|
||||
|
||||
<indexterm>
|
||||
<primary>X Window System</primary>
|
||||
<seealso>XFree86</seealso>
|
||||
</indexterm>
|
||||
|
||||
<listitem>
|
||||
|
|
@ -351,7 +350,6 @@
|
|||
|
||||
<indexterm>
|
||||
<primary>X Window System</primary>
|
||||
<secondary>XFree86</secondary>
|
||||
</indexterm>
|
||||
<indexterm>
|
||||
<primary>X Window System</primary>
|
||||
|
|
@ -650,7 +648,8 @@
|
|||
6.0-RELEASE, the first release of the 6.X branch, was released in
|
||||
November 2005. The most recent 6.4-RELEASE came out in
|
||||
November 2008. There will be no additional releases from the
|
||||
RELENG_6 branch.</para>
|
||||
RELENG_6 branch. This branch is the last branch to support the
|
||||
Alpha architecture.</para>
|
||||
|
||||
<para>The RELENG_7 branch was created in October 2007. The first
|
||||
release of this branch was 7.0-RELEASE, which came
|
||||
|
|
@ -931,7 +930,7 @@
|
|||
&pentium; II,
|
||||
&pentium; III,
|
||||
&pentium; 4 (or compatible),
|
||||
&xeon;, DEC <trademark>Alpha</trademark>
|
||||
&xeon;,
|
||||
and Sun &ultrasparc; based computer
|
||||
systems. It is based primarily on software from U.C. Berkeley's
|
||||
CSRG group, with some enhancements from NetBSD, OpenBSD, 386BSD, and
|
||||
|
|
|
|||
|
|
@ -276,7 +276,7 @@ following line in &man.loader.conf.5:
|
|||
will edit your custom kernel configuration, and
|
||||
<filename>compile</filename>, which is the staging area where your
|
||||
kernel will be built. <replaceable>arch</replaceable> represents
|
||||
one of <filename>i386</filename>, <filename>alpha</filename>,
|
||||
one of <filename>i386</filename>,
|
||||
<filename>amd64</filename>, <filename>ia64</filename>,
|
||||
<filename>powerpc</filename>, <filename>sparc64</filename>, or
|
||||
<filename>pc98</filename> (an alternative development branch of PC
|
||||
|
|
@ -469,7 +469,7 @@ following line in &man.loader.conf.5:
|
|||
<author>
|
||||
<firstname>Joel</firstname>
|
||||
<surname>Dahl</surname>
|
||||
<contrib>Updated for &os; 6.X by </contrib>
|
||||
<contrib>Updated by </contrib>
|
||||
</author>
|
||||
</authorgroup>
|
||||
</sect1info>
|
||||
|
|
@ -497,7 +497,7 @@ following line in &man.loader.conf.5:
|
|||
architecture independent options, see
|
||||
<filename>/usr/src/sys/conf/NOTES</filename>.</para>
|
||||
|
||||
<para>As of &os; 5.0, a new <literal>include</literal> directive is
|
||||
<para>An <literal>include</literal> directive is
|
||||
available for use in configuration files. This allows another
|
||||
configuration file to be logically included in the current one, making
|
||||
it easy to maintain small changes relative to an existing file. For
|
||||
|
|
@ -552,7 +552,7 @@ options IPDIVERT
|
|||
<programlisting>machine i386</programlisting>
|
||||
|
||||
<para>This is the machine architecture. It must be either
|
||||
<literal>alpha</literal>, <literal>amd64</literal>,
|
||||
<literal>amd64</literal>,
|
||||
<literal>i386</literal>, <literal>ia64</literal>,
|
||||
<literal>pc98</literal>, <literal>powerpc</literal>, or
|
||||
<literal>sparc64</literal>.</para>
|
||||
|
|
@ -726,7 +726,7 @@ options NFS_ROOT # NFS usable as /, requires NFSCLIENT</progra
|
|||
|
||||
<programlisting>options PSEUDOFS # Pseudo-filesystem framework</programlisting>
|
||||
|
||||
<para>6.X kernels making use of <literal>PROCFS</literal> must also
|
||||
<para>Kernels making use of <literal>PROCFS</literal> must also
|
||||
include support for <literal>PSEUDOFS</literal>.</para>
|
||||
|
||||
<programlisting>options GEOM_GPT # GUID Partition Tables.</programlisting>
|
||||
|
|
@ -741,19 +741,31 @@ options NFS_ROOT # NFS usable as /, requires NFSCLIENT</progra
|
|||
|
||||
<programlisting>options COMPAT_FREEBSD4 # Compatible with &os;4</programlisting>
|
||||
|
||||
<para>This option is required on &os; 5.X &i386; and Alpha systems
|
||||
<para>This option is required
|
||||
to support applications compiled on older versions of &os;
|
||||
that use older system call interfaces. It is recommended that
|
||||
this option be used on all &i386; and Alpha systems that may
|
||||
this option be used on all &i386; systems that may
|
||||
run older applications; platforms that gained support only in
|
||||
5.X, such as ia64 and &sparc64;, do not require this option.</para>
|
||||
|
||||
<programlisting>options COMPAT_FREEBSD5 # Compatible with &os;5</programlisting>
|
||||
|
||||
<para>This option is required on &os; 6.X and above to
|
||||
<para>This option is required to
|
||||
support applications compiled on &os; 5.X versions that use
|
||||
&os; 5.X system call interfaces.</para>
|
||||
|
||||
<programlisting>options COMPAT_FREEBSD6 # Compatible with &os;6</programlisting>
|
||||
|
||||
<para>This option is required to
|
||||
support applications compiled on &os; 6.X versions that use
|
||||
&os; 6.X system call interfaces.</para>
|
||||
|
||||
<programlisting>options COMPAT_FREEBSD7 # Compatible with &os;7</programlisting>
|
||||
|
||||
<para>This option is required on &os; 8 and above to
|
||||
support applications compiled on &os; 7.X versions that use
|
||||
&os; 7.X system call interfaces.</para>
|
||||
|
||||
<programlisting>options SCSI_DELAY=5000 # Delay (in ms) before probing SCSI</programlisting>
|
||||
|
||||
<para>This causes the kernel to pause for 5 seconds before probing
|
||||
|
|
@ -817,7 +829,7 @@ options NFS_ROOT # NFS usable as /, requires NFSCLIENT</progra
|
|||
leave this in.</para>
|
||||
|
||||
<note>
|
||||
<para>Note that on &os; 8.0-CURRENT and later versions, all mutexes are
|
||||
<para>Note that on &os; 8.0-RELEASE and later versions, all mutexes are
|
||||
adaptive by default, unless explicitly set to non-adaptive by
|
||||
compiling with the <literal>NO_ADAPTIVE_MUTEXES</literal> option. As
|
||||
a result, Giant is adaptive by default now, and the
|
||||
|
|
|
|||
|
|
@ -614,9 +614,7 @@ keychange="<replaceable>fkey_number sequence</replaceable>"</programlisting>
|
|||
<title>Displaying Fonts</title>
|
||||
<indexterm><primary>X11 True Type font server</primary></indexterm>
|
||||
<para>Install <application>&xorg;</application> server
|
||||
(<filename role="package">x11-servers/xorg-server</filename>)
|
||||
or <application>&xfree86;</application> server
|
||||
(<filename role="package">x11-servers/XFree86-4-Server</filename>),
|
||||
(<filename role="package">x11-servers/xorg-server</filename>),
|
||||
then install the language &truetype; fonts. Setting the correct
|
||||
locale should allow you to view your selected language in menus
|
||||
and such.</para>
|
||||
|
|
|
|||
File diff suppressed because it is too large
Load diff
|
|
@ -140,7 +140,7 @@
|
|||
|
||||
<para>This includes command line programs such as
|
||||
<application>mutt</application>,
|
||||
<application>pine</application>, <application>elm</application>,
|
||||
<application>alpine</application>, <application>elm</application>,
|
||||
and <command>mail</command>, and <acronym>GUI</acronym> programs such as
|
||||
<application>balsa</application>,
|
||||
<application>xfmail</application> to name a few, and something
|
||||
|
|
@ -1700,7 +1700,7 @@ define(`confAUTH_MECHANISMS', `GSSAPI DIGEST-MD5 CRAM-MD5 LOGIN')dnl</programlis
|
|||
Users may choose between graphical email clients such as
|
||||
<application>evolution</application> or
|
||||
<application>balsa</application>, console based clients such as
|
||||
<application>mutt</application>, <application>pine</application>
|
||||
<application>mutt</application>, <application>alpine</application>
|
||||
or <command>mail</command>, or the web interfaces used by some
|
||||
large organizations.</para>
|
||||
|
||||
|
|
@ -1933,35 +1933,35 @@ EOT</screen>
|
|||
|
||||
</sect2>
|
||||
|
||||
<sect2 id="pine-command">
|
||||
<title>pine</title>
|
||||
<sect2 id="alpine-command">
|
||||
<title>alpine</title>
|
||||
|
||||
<para><application>pine</application> is aimed at a beginner
|
||||
<para><application>alpine</application> is aimed at a beginner
|
||||
user, but also includes some advanced features.</para>
|
||||
|
||||
<warning>
|
||||
<para>The <application>pine</application> software has had several remote vulnerabilities
|
||||
<para>The <application>alpine</application> software has had several remote vulnerabilities
|
||||
discovered in the past, which allowed remote attackers to
|
||||
execute arbitrary code as users on the local system, by the
|
||||
action of sending a specially-prepared email. All such
|
||||
<emphasis>known</emphasis> problems have been fixed, but the
|
||||
<application>pine</application> code is written in a very insecure style and the &os;
|
||||
<application>alpine</application> code is written in a very insecure style and the &os;
|
||||
Security Officer believes there are likely to be other
|
||||
undiscovered vulnerabilities. You install
|
||||
<application>pine</application> at your own risk.</para>
|
||||
<application>alpine</application> at your own risk.</para>
|
||||
</warning>
|
||||
|
||||
<para>The current version of <application>pine</application> may
|
||||
be installed using the <filename
|
||||
role="package">mail/pine4</filename> port. Once the port has
|
||||
installed, <application>pine</application> can be started by
|
||||
role="package">mail/alpine</filename> port. Once the port has
|
||||
installed, <application>alpine</application> can be started by
|
||||
issuing the following command:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>pine</userinput></screen>
|
||||
<screen>&prompt.user; <userinput>alpine</userinput></screen>
|
||||
|
||||
<para>The first time that <application>pine</application> is run
|
||||
<para>The first time that <application>alpine</application> is run
|
||||
it displays a greeting page with a brief introduction, as well
|
||||
as a request from the <application>pine</application>
|
||||
as a request from the <application>alpine</application>
|
||||
development team to send an anonymous email message allowing
|
||||
them to judge how many users are using their client. To send
|
||||
this anonymous message, press <keycap>Enter</keycap>, or
|
||||
|
|
@ -1982,7 +1982,7 @@ EOT</screen>
|
|||
main menu, relevant keyboard shortcuts to perform functions
|
||||
specific to the task at hand are shown.</para>
|
||||
|
||||
<para>The default directory opened by <application>pine</application>
|
||||
<para>The default directory opened by <application>alpine</application>
|
||||
is the <filename class="directory">inbox</filename>. To view the message index, press
|
||||
<keycap>I</keycap>, or select the <guimenuitem>MESSAGE INDEX</guimenuitem>
|
||||
option as seen below:</para>
|
||||
|
|
@ -2005,7 +2005,7 @@ EOT</screen>
|
|||
</mediaobject>
|
||||
|
||||
<para>In the screenshot below, a sample message is displayed by
|
||||
<application>pine</application>. Keyboard shortcuts are
|
||||
<application>alpine</application>. Keyboard shortcuts are
|
||||
displayed as a reference at the bottom of the screen. An
|
||||
example of one of these shortcuts is the <keycap>r</keycap> key,
|
||||
which tells the <acronym>MUA</acronym> to reply to the current
|
||||
|
|
@ -2017,15 +2017,15 @@ EOT</screen>
|
|||
</imageobject>
|
||||
</mediaobject>
|
||||
|
||||
<para>Replying to an email in <application>pine</application> is
|
||||
<para>Replying to an email in <application>alpine</application> is
|
||||
done using the <application>pico</application> editor, which is
|
||||
installed by default with <application>pine</application>.
|
||||
installed by default with <application>alpine</application>.
|
||||
The <application>pico</application> utility makes it easy to
|
||||
navigate around the message and is slightly more forgiving on
|
||||
novice users than &man.vi.1; or &man.mail.1;. Once the reply
|
||||
is complete, the message can be sent by pressing
|
||||
<keycombo action="simul"><keycap>Ctrl</keycap><keycap>X</keycap>
|
||||
</keycombo>. The <application>pine</application> application
|
||||
</keycombo>. The <application>alpine</application> application
|
||||
will ask for confirmation.</para>
|
||||
|
||||
<mediaobject>
|
||||
|
|
@ -2034,9 +2034,9 @@ EOT</screen>
|
|||
</imageobject>
|
||||
</mediaobject>
|
||||
|
||||
<para>The <application>pine</application> application can be
|
||||
<para>The <application>alpine</application> application can be
|
||||
customized using the <guimenuitem>SETUP</guimenuitem> option from the main
|
||||
menu. Consult <ulink url="http://www.washington.edu/pine/"></ulink>
|
||||
menu. Consult <ulink url="http://www.washington.edu/alpine/"></ulink>
|
||||
for more information.</para>
|
||||
|
||||
</sect2>
|
||||
|
|
|
|||
|
|
@ -438,13 +438,13 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
|
|||
</example>
|
||||
|
||||
<example>
|
||||
<title>Checking Out the Version of &man.ls.1; in the 6-STABLE
|
||||
<title>Checking Out the Version of &man.ls.1; in the 8-STABLE
|
||||
Branch:</title>
|
||||
|
||||
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput>
|
||||
&prompt.user; <userinput>cvs login</userinput>
|
||||
<emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>.
|
||||
&prompt.user; <userinput>cvs co -rRELENG_6 ls</userinput>
|
||||
&prompt.user; <userinput>cvs co -rRELENG_8 ls</userinput>
|
||||
</screen>
|
||||
</example>
|
||||
|
||||
|
|
@ -454,7 +454,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
|
|||
<screen>&prompt.user; <userinput>setenv CVSROOT :pserver:anoncvs@anoncvs.tw.FreeBSD.org:/home/ncvs</userinput>
|
||||
&prompt.user; <userinput>cvs login</userinput>
|
||||
<emphasis>At the prompt, enter any word for</emphasis> <quote>password</quote>.
|
||||
&prompt.user; <userinput>cvs rdiff -u -rRELENG_5_3_0_RELEASE -rRELENG_5_4_0_RELEASE ls</userinput>
|
||||
&prompt.user; <userinput>cvs rdiff -u -rRELENG_8_0_0_RELEASE -rRELENG_8_1_0_RELEASE ls</userinput>
|
||||
</screen>
|
||||
</example>
|
||||
|
||||
|
|
@ -574,7 +574,7 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
|
|||
<application>CTM</application> distribution lists.
|
||||
&a.ctm-cvs-cur.name; supports the entire CVS tree.
|
||||
&a.ctm-src-cur.name; supports the head of the development
|
||||
branch. &a.ctm-src-4.name; supports the 4.X release
|
||||
branch. &a.ctm-src-7.name; supports the 7.X release
|
||||
branch, etc.. (If you do not know how to subscribe yourself
|
||||
to a list, click on the list name above or go to
|
||||
&a.mailman.lists.link; and click on the list that you
|
||||
|
|
@ -882,12 +882,10 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
|
|||
<application>CVSup</application> software in C. Its biggest
|
||||
advantage is, that it is faster and does not depend on the
|
||||
Modula-3 language, thus you do not need to install it as a
|
||||
requirement. Moreover, if you are using &os; 6.2 or later,
|
||||
requirement. Moreover
|
||||
you can use it out-of-the-box, since it is included in the base
|
||||
system. Older &os; versions do not have &man.csup.1; in their
|
||||
base system but you can easily install the
|
||||
<filename role="package">net/csup</filename> port, or a precompiled
|
||||
package. If you decided to use
|
||||
system.
|
||||
If you decided to use
|
||||
<application>csup</application>, just skip the steps on the
|
||||
installation of <application>CVSup</application> and
|
||||
substitute the references of <application>CVSup</application> with
|
||||
|
|
@ -912,19 +910,11 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
|
|||
<note>
|
||||
<para>If you are going to be using
|
||||
<application>CVSup</application> on a machine which will not have
|
||||
<application>&xfree86;</application> or <application>&xorg;</application> installed, such as a server, be
|
||||
<application>&xorg;</application> installed, such as a server, be
|
||||
sure to use the port which does not include the
|
||||
<application>CVSup</application> <acronym>GUI</acronym>,
|
||||
<filename role="package">net/cvsup-without-gui</filename>.</para>
|
||||
</note>
|
||||
|
||||
<para>If you want to install <application>csup</application> on
|
||||
&os; 6.1 or earlier, you can use the precompiled
|
||||
<filename role="package">net/csup</filename> package
|
||||
from the &os; <link linkend="ports">packages collection</link>.
|
||||
If you prefer to build <application>csup</application> from source,
|
||||
you can use the <filename role="package">net/csup</filename>
|
||||
port instead.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2 id="cvsup-config">
|
||||
|
|
@ -1072,8 +1062,8 @@ Warning: Permanently added 'anoncvs1.freebsd.org' (DSA) to the list of known hos
|
|||
users might be interested in. When specifying a tag in
|
||||
<application>CVSup</application>'s configuration file, it
|
||||
must be preceded with <literal>tag=</literal>
|
||||
(<literal>RELENG_4</literal> will become
|
||||
<literal>tag=RELENG_4</literal>).
|
||||
(<literal>RELENG_8</literal> will become
|
||||
<literal>tag=RELENG_8</literal>).
|
||||
Keep in mind that only the <literal>tag=.</literal> is
|
||||
relevant for the Ports Collection.</para>
|
||||
|
||||
|
|
|
|||
|
|
@ -120,7 +120,7 @@
|
|||
<author>
|
||||
<firstname>Marc</firstname>
|
||||
<surname>Fonvieille</surname>
|
||||
<contrib>Enhanced for &os; 5.X by </contrib>
|
||||
<contrib>Enhanced by </contrib>
|
||||
<!-- 13 September 2004 -->
|
||||
</author>
|
||||
</authorgroup>
|
||||
|
|
@ -399,12 +399,8 @@ kld snd_ich (1p/2r/0v channels duplex default)</screen>
|
|||
device, such as music players or sound daemons.</para>
|
||||
</note>
|
||||
|
||||
<para>If you are not using &man.devfs.5;, you will have to point
|
||||
your applications at
|
||||
<filename>/dev/dsp0</filename>.<replaceable>x</replaceable>,
|
||||
where <replaceable>x</replaceable> is 0 to 3 if
|
||||
<varname>dev.pcm.0.rec.vchans</varname> is set to 4 as in the
|
||||
above example. On a system using &man.devfs.5;, the above will
|
||||
<para>
|
||||
The above will
|
||||
automatically be allocated transparently to a program
|
||||
that requests <filename>/dev/dsp0</filename>.</para>
|
||||
</sect2>
|
||||
|
|
@ -687,7 +683,7 @@ MPEG 1.0 layer III, 128 kbit/s, 44100 Hz joint-stereo
|
|||
it did with sound.</para>
|
||||
|
||||
<para>Before you begin, you should know the model of the video
|
||||
card you have and the chip it uses. While <application>&xorg;</application> and <application>&xfree86;</application> support a
|
||||
card you have and the chip it uses. While <application>&xorg;</application> supports a
|
||||
wide variety of video cards, fewer give good playback
|
||||
performance. To obtain a list of extensions supported by the
|
||||
X server using your card use the command &man.xdpyinfo.1; while
|
||||
|
|
@ -735,7 +731,7 @@ kern.ipc.shmall=32768</programlisting>
|
|||
method described below will have varying quality across
|
||||
different hardware. Secondly, the rendering of video in X11 is
|
||||
a topic receiving a lot of attention lately, and with each
|
||||
version of <application>&xorg;</application>, or of <application>&xfree86;</application>, there may be significant improvement.</para>
|
||||
version of <application>&xorg;</application>, there may be significant improvement.</para>
|
||||
|
||||
<para>A list of common video interfaces:</para>
|
||||
|
||||
|
|
@ -761,7 +757,7 @@ kern.ipc.shmall=32768</programlisting>
|
|||
<sect3 id="video-interface-xvideo">
|
||||
<title>XVideo</title>
|
||||
|
||||
<para><application>&xorg;</application> and <application>&xfree86; 4.X</application> have an extension called
|
||||
<para><application>&xorg;</application> has an extension called
|
||||
<emphasis>XVideo</emphasis> (aka Xvideo, aka Xv, aka xv) which
|
||||
allows video to be directly displayed in drawable objects
|
||||
through a special acceleration. This extension provides very
|
||||
|
|
|
|||
|
|
@ -110,7 +110,7 @@
|
|||
</authorgroup>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<contrib>Updated for &os; 6.1-RELEASE by </contrib>
|
||||
<contrib>Updated by </contrib>
|
||||
<othername>The &os; Documentation Project</othername>
|
||||
</author>
|
||||
</authorgroup>
|
||||
|
|
@ -2549,9 +2549,7 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
|
|||
<para>DHCP, the Dynamic Host Configuration Protocol, describes
|
||||
the means by which a system can connect to a network and obtain the
|
||||
necessary information for communication upon that network. FreeBSD
|
||||
versions prior to 6.0 use the ISC (Internet Systems
|
||||
Consortium) DHCP client (&man.dhclient.8;) implementation.
|
||||
Later versions use the OpenBSD <command>dhclient</command>
|
||||
uses the OpenBSD <command>dhclient</command>
|
||||
taken from OpenBSD 3.7. All
|
||||
information here regarding <command>dhclient</command> is for
|
||||
use with either of the ISC or OpenBSD DHCP clients. The DHCP
|
||||
|
|
@ -2595,12 +2593,11 @@ nis_client_flags="-S <replaceable>NIS domain</replaceable>,<replaceable>server</
|
|||
<sect2>
|
||||
<title>FreeBSD Integration</title>
|
||||
|
||||
<para>&os; fully integrates the ISC or OpenBSD DHCP client,
|
||||
<command>dhclient</command> (according to the &os; version you run). DHCP client support is provided
|
||||
<para>&os; fully integrates the OpenBSD DHCP client,
|
||||
<command>dhclient</command>. DHCP client support is provided
|
||||
within both the installer and the base system, obviating the need
|
||||
for detailed knowledge of network configurations on any network
|
||||
that runs a DHCP server. <command>dhclient</command> has been
|
||||
included in all FreeBSD distributions since 3.2.</para>
|
||||
that runs a DHCP server.</para>
|
||||
<indexterm>
|
||||
<primary><application>sysinstall</application></primary>
|
||||
</indexterm>
|
||||
|
|
@ -4601,7 +4598,7 @@ DocumentRoot /www/someotherdomain.tld
|
|||
be included on your FreeBSD installation media. If you did
|
||||
not install <application>Samba</application> when you first
|
||||
installed FreeBSD, then you can install it from the <filename
|
||||
role="package">net/samba3</filename> port or package.</para>
|
||||
role="package">net/samba34</filename> port or package.</para>
|
||||
|
||||
<!-- mention LDAP, Active Directory, WinBIND, ACL, Quotas, PAM, .. -->
|
||||
|
||||
|
|
@ -4612,7 +4609,7 @@ DocumentRoot /www/someotherdomain.tld
|
|||
|
||||
<para>A default <application>Samba</application> configuration
|
||||
file is installed as
|
||||
<filename>/usr/local/share/examples/samba/smb.conf.default</filename>. This
|
||||
<filename>/usr/local/share/examples/samba34/smb.conf.default</filename>. This
|
||||
file must be copied to
|
||||
<filename>/usr/local/etc/smb.conf</filename> and customized
|
||||
before <application>Samba</application> can be used.</para>
|
||||
|
|
@ -4744,27 +4741,23 @@ DocumentRoot /www/someotherdomain.tld
|
|||
authenticate clients with LDAP, NIS+, a SQL database,
|
||||
or a modified password file. The default
|
||||
authentication method is <literal>smbpasswd</literal>,
|
||||
and that is all that will be covered here.</para>
|
||||
and that is all that will be covered here.</para>
|
||||
</listitem>
|
||||
</varlistentry>
|
||||
</variablelist>
|
||||
|
||||
<para>Assuming that the default <literal>smbpasswd</literal>
|
||||
backend is used, the
|
||||
<filename>/usr/local/private/smbpasswd</filename> file must
|
||||
<filename>/usr/local/etc/samba/smbpasswd</filename> file must
|
||||
be created to allow <application>Samba</application> to
|
||||
authenticate clients. If you would like to give
|
||||
your &unix; user accounts access from &windows; clients, use the
|
||||
following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>smbpasswd -a username</userinput></screen>
|
||||
|
||||
<note>
|
||||
<para>Since <application>Samba</application> 3.0.23c, the actual
|
||||
directory for authentication files is
|
||||
<filename class="directory">/usr/local/etc/samba</filename>. The
|
||||
recommended backend is now <literal>tdbsam</literal>, and the
|
||||
following command should be used to add user accounts:</para>
|
||||
<para>The recommended backend is now <literal>tdbsam</literal>, and
|
||||
the following command should be used to add user accounts:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput><command>pdbedit <option>-a</option> <option>-u</option> <replaceable>username</replaceable></command></userinput></screen>
|
||||
</note>
|
||||
|
|
@ -4782,7 +4775,7 @@ DocumentRoot /www/someotherdomain.tld
|
|||
<sect2>
|
||||
<title>Starting <application>Samba</application></title>
|
||||
|
||||
<para>The <filename role="package">net/samba3</filename> port adds
|
||||
<para>The <filename role="package">net/samba34</filename> port adds
|
||||
a new startup script, which can be used to control
|
||||
<application>Samba</application>. To enable this script, so
|
||||
that it can be used for example to start, stop or restart
|
||||
|
|
|
|||
|
|
@ -462,14 +462,14 @@ local: lsof-4.56.4.tgz remote: lsof-4.56.4.tgz
|
|||
the version of the package that was built with your
|
||||
release. It is possible to change this behavior by
|
||||
overriding <envar>PACKAGESITE</envar>.
|
||||
For example, if you run a &os; 5.4-RELEASE
|
||||
For example, if you run a &os; 8.1-RELEASE
|
||||
system, by default &man.pkg.add.1; will try to fetch
|
||||
packages from
|
||||
<literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5.4-release/Latest/</literal>.
|
||||
<literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8.1-release/Latest/</literal>.
|
||||
If you want to force &man.pkg.add.1; to download
|
||||
&os; 5-STABLE packages, set <envar>PACKAGESITE</envar>
|
||||
&os; 8-STABLE packages, set <envar>PACKAGESITE</envar>
|
||||
to
|
||||
<literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-5-stable/Latest/</literal>.
|
||||
<literal>ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-8-stable/Latest/</literal>.
|
||||
</para>
|
||||
</note>
|
||||
|
||||
|
|
@ -642,9 +642,7 @@ docbook =
|
|||
<note>
|
||||
<para>The implementation of <application>CVSup</application> protocol
|
||||
included with the &os; system is called
|
||||
<application>csup</application>. It first appeared in &os; 6.2.
|
||||
Users of older &os; releases can install it via the <filename
|
||||
role="package">net/csup</filename> port/package.</para>
|
||||
<application>csup</application>.</para>
|
||||
</note>
|
||||
|
||||
<para>Make sure <filename class="directory">/usr/ports</filename>
|
||||
|
|
@ -824,7 +822,7 @@ docbook =
|
|||
<para>A <filename>distinfo</filename> file. This file
|
||||
contains information about the files that must be
|
||||
downloaded to build the port, and their checksums
|
||||
(using &man.md5.1; and &man.sha256.1;), to
|
||||
(using &man.sha256.1;), to
|
||||
verify that files have not been corrupted during the
|
||||
download.</para>
|
||||
</listitem>
|
||||
|
|
|
|||
|
|
@ -94,7 +94,7 @@
|
|||
<para>Throughout in this chapter, user PPP will simply be
|
||||
referred to as <application>ppp</application> unless a distinction
|
||||
needs to be made between it and any other PPP software such as
|
||||
<application>pppd</application>. Unless otherwise stated, all of
|
||||
<application>pppd</application> (&os; 7.X only). Unless otherwise stated, all of
|
||||
the commands explained in this chapter should be executed as
|
||||
<username>root</username>.</para>
|
||||
</note>
|
||||
|
|
@ -268,7 +268,7 @@
|
|||
</indexterm>
|
||||
|
||||
<para>Both <command>ppp</command> and <command>pppd</command>
|
||||
(the kernel level implementation of PPP) use the configuration
|
||||
(the kernel level implementation of PPP, &os; 7.X only) use the configuration
|
||||
files located in the <filename class="directory">/etc/ppp</filename> directory.
|
||||
Examples for user ppp can be found in
|
||||
<filename class="directory">/usr/share/examples/ppp/</filename>.</para>
|
||||
|
|
|
|||
|
|
@ -204,6 +204,15 @@
|
|||
<sect1 id="printing-intro-setup">
|
||||
<title>Basic Setup</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
|
||||
<para>To use printers with the <application>LPD</application> spooling
|
||||
system, you will need to set up both your printer hardware and the
|
||||
<application>LPD</application> software. This document describes two
|
||||
|
|
@ -778,8 +787,8 @@ showpage</programlisting>
|
|||
<indexterm><primary>serial port</primary></indexterm>
|
||||
<indexterm><primary>parity</primary></indexterm>
|
||||
<para>Where <replaceable>port</replaceable> is the device
|
||||
entry for the serial port (<literal>ttyd0</literal>,
|
||||
<literal>ttyd1</literal>, etc.),
|
||||
entry for the serial port (<literal>ttyu0</literal>,
|
||||
<literal>ttyu1</literal>, etc.),
|
||||
<replaceable>bps-rate</replaceable> is the
|
||||
bits-per-second rate at which the printer communicates,
|
||||
and <replaceable>parity</replaceable> is the parity
|
||||
|
|
@ -791,7 +800,7 @@ showpage</programlisting>
|
|||
a serial line to the third serial port at 19200 bps
|
||||
with no parity:</para>
|
||||
|
||||
<programlisting>printer:dv=<filename class="devicefile">/dev/ttyd2</filename>:br#19200:pa=none</programlisting>
|
||||
<programlisting>printer:dv=<filename class="devicefile">/dev/ttyu2</filename>:br#19200:pa=none</programlisting>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
|
@ -803,7 +812,7 @@ showpage</programlisting>
|
|||
<para>If this step does not work, edit the file
|
||||
<filename>/etc/remote</filename> again and try using
|
||||
<filename class="devicefile">/dev/cuaa<replaceable>N</replaceable></filename> instead of
|
||||
<filename class="devicefile">/dev/ttyd<replaceable>N</replaceable></filename>.</para>
|
||||
<filename class="devicefile">/dev/ttyu<replaceable>N</replaceable></filename>.</para>
|
||||
</step>
|
||||
|
||||
<step>
|
||||
|
|
@ -1145,7 +1154,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
|
|||
|
||||
bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:</programlisting>
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:</programlisting>
|
||||
|
||||
<para>If you do not specify the <literal>lp</literal> capability
|
||||
for a printer in your <filename>/etc/printcap</filename> file,
|
||||
|
|
@ -1237,7 +1246,7 @@ bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
|||
|
||||
<programlisting>bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:</programlisting>
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:</programlisting>
|
||||
</sect4>
|
||||
|
||||
<sect4 id="printing-textfilter">
|
||||
|
|
@ -1309,7 +1318,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
|
|||
|
||||
bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:\
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:\
|
||||
:if=<filename>/usr/local/libexec/if-simple</filename>:</programlisting>
|
||||
|
||||
<note>
|
||||
|
|
@ -1397,6 +1406,15 @@ $%&'()*+,-./01234567
|
|||
<sect1 id="printing-advanced">
|
||||
<title>Advanced Printer Setup</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
|
||||
<para>This section describes filters for printing specially formatted
|
||||
files, header pages, printing across networks, and restricting and
|
||||
accounting for printer usage.</para>
|
||||
|
|
@ -2093,7 +2111,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
|
|||
|
||||
bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:if=<filename>/usr/local/libexec/psif</filename>:\
|
||||
:df=<filename>/usr/local/libexec/psdf</filename>:</programlisting>
|
||||
|
||||
|
|
@ -3210,7 +3228,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
|
|||
|
||||
bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:sc:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:if=<filename>/usr/local/libexec/psif</filename>:\
|
||||
:df=<filename>/usr/local/libexec/psdf</filename>:</programlisting>
|
||||
|
||||
|
|
@ -3285,7 +3303,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
|
|||
|
||||
bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:sc:rg=artists:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:if=<filename>/usr/local/libexec/psif</filename>:\
|
||||
:df=<filename>/usr/local/libexec/psdf</filename>:</programlisting>
|
||||
|
||||
|
|
@ -3358,7 +3376,7 @@ rattan|line|diablo|lp|Diablo 630 Line Printer:\
|
|||
#
|
||||
bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:sc:rg=artists:mx#5000:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:rw:\
|
||||
:if=<filename>/usr/local/libexec/psif</filename>:\
|
||||
:df=<filename>/usr/local/libexec/psdf</filename>:</programlisting>
|
||||
|
||||
|
|
@ -3446,7 +3464,7 @@ madrigal.fishbaum.de</programlisting>
|
|||
|
||||
<programlisting>bamboo|ps|PS|S|panasonic|Panasonic KX-P4455 PostScript v51.4:\
|
||||
:sh:sd=<filename class="directory">/var/spool/lpd/bamboo</filename>:sc:rg=artists:mx#5000:\
|
||||
:lp=<filename class="devicefile">/dev/ttyd5</filename>:ms#-parenb cs8 clocal crtscts:rw:mx#5000:\
|
||||
:lp=<filename class="devicefile">/dev/ttyu5</filename>:ms#-parenb cs8 clocal crtscts:rw:mx#5000:\
|
||||
:if=<filename>/usr/local/libexec/psif</filename>:\
|
||||
:df=<filename>/usr/local/libexec/psdf</filename>:</programlisting>
|
||||
|
||||
|
|
|
|||
|
|
@ -55,11 +55,6 @@
|
|||
with <application>inetd</application>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>How to set up <application>KerberosIV</application> on &os;
|
||||
releases prior to 5.0.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>How to set up <application>Kerberos5</application> on
|
||||
&os;.</para>
|
||||
|
|
@ -407,7 +402,6 @@
|
|||
vast majority of break-ins occur remotely, over a network, from
|
||||
people who do not have physical access to your workstation or
|
||||
servers.</para>
|
||||
<indexterm><primary>KerberosIV</primary></indexterm>
|
||||
|
||||
<para>Using something like Kerberos also gives you the ability to
|
||||
disable or change the password for a staff account in one place,
|
||||
|
|
@ -944,7 +938,6 @@
|
|||
<sect2>
|
||||
<title>Access Issues with Kerberos and SSH</title>
|
||||
<indexterm><primary><command>ssh</command></primary></indexterm>
|
||||
<indexterm><primary>KerberosIV</primary></indexterm>
|
||||
|
||||
<para>There are a few issues with both Kerberos and
|
||||
ssh that need to be addressed if
|
||||
|
|
@ -1565,496 +1558,6 @@ sendmail : PARANOID : deny</programlisting>
|
|||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="kerberosIV">
|
||||
<sect1info>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Mark</firstname>
|
||||
<surname>Murray</surname>
|
||||
<contrib>Contributed by </contrib>
|
||||
</author>
|
||||
</authorgroup>
|
||||
<authorgroup>
|
||||
<author>
|
||||
<firstname>Mark</firstname>
|
||||
<surname>Dapoz</surname>
|
||||
<contrib>Based on a contribution by </contrib>
|
||||
</author>
|
||||
</authorgroup>
|
||||
</sect1info>
|
||||
|
||||
<title><application>KerberosIV</application></title>
|
||||
|
||||
<para>Kerberos is a network add-on system/protocol that allows users to
|
||||
authenticate themselves through the services of a secure server.
|
||||
Services such as remote login, remote copy, secure inter-system file
|
||||
copying and other high-risk tasks are made considerably safer and more
|
||||
controllable.</para>
|
||||
|
||||
<para>The following instructions can be used as a guide on how to set up
|
||||
Kerberos as distributed for &os;. However, you should refer to the
|
||||
relevant manual pages for a complete description.</para>
|
||||
|
||||
<sect2>
|
||||
<title>Installing <application>KerberosIV</application></title>
|
||||
|
||||
<indexterm><primary>MIT</primary></indexterm>
|
||||
<indexterm>
|
||||
<primary>KerberosIV</primary>
|
||||
<secondary>installing</secondary>
|
||||
</indexterm>
|
||||
<para>Kerberos is an optional component of &os;. The easiest
|
||||
way to install this software is by selecting the <literal>krb4</literal> or
|
||||
<literal>krb5</literal> distribution in <application>sysinstall</application>
|
||||
during the initial installation of &os;. This will install
|
||||
the <quote>eBones</quote> (KerberosIV) or <quote>Heimdal</quote> (Kerberos5)
|
||||
implementation of Kerberos. These implementations are
|
||||
included because they are developed outside the USA/Canada and
|
||||
were thus available to system owners outside those countries
|
||||
during the era of restrictive export controls on cryptographic
|
||||
code from the USA.</para>
|
||||
|
||||
<para>Alternatively, the MIT implementation of Kerberos is
|
||||
available from the Ports Collection as
|
||||
<filename role="package">security/krb5</filename>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<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
|
||||
to the directory <filename class="directory">/etc/kerberosIV</filename>
|
||||
and check that only the following files are present:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cd /etc/kerberosIV</userinput>
|
||||
&prompt.root; <userinput>ls</userinput>
|
||||
README krb.conf krb.realms</screen>
|
||||
|
||||
<para>If any additional files (such as <filename>principal.*</filename>
|
||||
or <filename>master_key</filename>) exist, then use the
|
||||
<command>kdb_destroy</command> command to destroy the old Kerberos
|
||||
database, or if Kerberos is not running, simply delete the extra
|
||||
files.</para>
|
||||
|
||||
<para>You should now edit the <filename>krb.conf</filename> and
|
||||
<filename>krb.realms</filename> files to define your Kerberos realm.
|
||||
In this case the realm will be <literal>EXAMPLE.COM</literal> and the
|
||||
server is <hostid role="fqdn">grunt.example.com</hostid>. We edit
|
||||
or create the <filename>krb.conf</filename> file:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cat krb.conf</userinput>
|
||||
EXAMPLE.COM
|
||||
EXAMPLE.COM grunt.example.com admin server
|
||||
CS.BERKELEY.EDU okeeffe.berkeley.edu
|
||||
ATHENA.MIT.EDU kerberos.mit.edu
|
||||
ATHENA.MIT.EDU kerberos-1.mit.edu
|
||||
ATHENA.MIT.EDU kerberos-2.mit.edu
|
||||
ATHENA.MIT.EDU kerberos-3.mit.edu
|
||||
LCS.MIT.EDU kerberos.lcs.mit.edu
|
||||
TELECOM.MIT.EDU bitsy.mit.edu
|
||||
ARC.NASA.GOV trident.arc.nasa.gov</screen>
|
||||
|
||||
<para>In this case, the other realms do not need to be there. They are
|
||||
here as an example of how a machine may be made aware of multiple
|
||||
realms. You may wish to not include them for simplicity.</para>
|
||||
|
||||
<para>The first line names the realm in which this system works. The
|
||||
other lines contain realm/host entries. The first item on a line is a
|
||||
realm, and the second is a host in that realm that is acting as a
|
||||
<quote>key distribution center</quote>. The words <literal>admin
|
||||
server</literal> following a host's name means that host also
|
||||
provides an administrative database server. For further explanation
|
||||
of these terms, please consult the Kerberos manual pages.</para>
|
||||
|
||||
<para>Now we have to add <hostid role="fqdn">grunt.example.com</hostid>
|
||||
to the <literal>EXAMPLE.COM</literal> realm and also add an entry to
|
||||
put all hosts in the <hostid role="domainname">.example.com</hostid>
|
||||
domain in the <literal>EXAMPLE.COM</literal> realm. The
|
||||
<filename>krb.realms</filename> file would be updated as
|
||||
follows:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cat krb.realms</userinput>
|
||||
grunt.example.com EXAMPLE.COM
|
||||
.example.com EXAMPLE.COM
|
||||
.berkeley.edu CS.BERKELEY.EDU
|
||||
.MIT.EDU ATHENA.MIT.EDU
|
||||
.mit.edu ATHENA.MIT.EDU</screen>
|
||||
|
||||
<para>Again, the other realms do not need to be there. They are here as
|
||||
an example of how a machine may be made aware of multiple realms. You
|
||||
may wish to remove them to simplify things.</para>
|
||||
|
||||
<para>The first line puts the <emphasis>specific</emphasis> system into
|
||||
the named realm. The rest of the lines show how to default systems of
|
||||
a particular subdomain to a named realm.</para>
|
||||
|
||||
<para>Now we are ready to create the database. This only needs to run
|
||||
on the Kerberos server (or Key Distribution Center). Issue the
|
||||
<command>kdb_init</command> command to do this:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kdb_init</userinput>
|
||||
<prompt>Realm name [default ATHENA.MIT.EDU ]:</prompt> <userinput>EXAMPLE.COM</userinput>
|
||||
You will be prompted for the database Master Password.
|
||||
It is important that you NOT FORGET this password.
|
||||
|
||||
<prompt>Enter Kerberos master key:</prompt> </screen>
|
||||
|
||||
<para>Now we have to save the key so that servers on the local machine
|
||||
can pick it up. Use the <command>kstash</command> command to do
|
||||
this:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kstash</userinput>
|
||||
|
||||
<prompt>Enter Kerberos master key:</prompt>
|
||||
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!</screen>
|
||||
|
||||
<para>This saves the encrypted master password in
|
||||
<filename>/etc/kerberosIV/master_key</filename>.</para>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Making It All Run</title>
|
||||
|
||||
<indexterm>
|
||||
<primary>KerberosIV</primary>
|
||||
<secondary>initial startup</secondary>
|
||||
</indexterm>
|
||||
|
||||
<para>Two principals need to be added to the database for
|
||||
<emphasis>each</emphasis> system that will be secured with Kerberos.
|
||||
Their names are <literal>kpasswd</literal> and <literal>rcmd</literal>.
|
||||
These two principals are made for each system, with the instance being
|
||||
the name of the individual system.</para>
|
||||
|
||||
<para>These daemons, <application>kpasswd</application> and
|
||||
<application>rcmd</application> allow other systems to change Kerberos
|
||||
passwords and run commands like &man.rcp.1;,
|
||||
&man.rlogin.1; and &man.rsh.1;.</para>
|
||||
|
||||
<para>Now let us add these entries:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kdb_edit</userinput>
|
||||
Opening database...
|
||||
|
||||
<prompt>Enter Kerberos master key:</prompt>
|
||||
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!
|
||||
Previous or default values are in [brackets] ,
|
||||
enter return to leave the same, or new value.
|
||||
|
||||
<prompt>Principal name:</prompt> <userinput>passwd</userinput>
|
||||
<prompt>Instance:</prompt> <userinput>grunt</userinput>
|
||||
|
||||
<Not found>, <prompt>Create [y] ?</prompt> <userinput>y</userinput>
|
||||
|
||||
Principal: passwd, Instance: grunt, kdc_key_ver: 1
|
||||
<prompt>New Password:</prompt> <---- enter RANDOM here
|
||||
Verifying password
|
||||
|
||||
<prompt>New Password:</prompt> <---- enter RANDOM here
|
||||
|
||||
<prompt>Random password [y] ?</prompt> <userinput>y</userinput>
|
||||
|
||||
Principal's new key version = 1
|
||||
<prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
|
||||
<prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt>
|
||||
<prompt>Attributes [ 0 ] ?</prompt>
|
||||
Edit O.K.
|
||||
<prompt>Principal name:</prompt> <userinput>rcmd</userinput>
|
||||
<prompt>Instance:</prompt> <userinput>grunt</userinput>
|
||||
|
||||
<Not found>, <prompt>Create [y] ?</prompt>
|
||||
|
||||
Principal: rcmd, Instance: grunt, kdc_key_ver: 1
|
||||
<prompt>New Password:</prompt> <---- enter RANDOM here
|
||||
Verifying password
|
||||
|
||||
<prompt>New Password:</prompt> <---- enter RANDOM here
|
||||
|
||||
<prompt>Random password [y] ?</prompt>
|
||||
|
||||
Principal's new key version = 1
|
||||
<prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
|
||||
<prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt>
|
||||
<prompt>Attributes [ 0 ] ?</prompt>
|
||||
Edit O.K.
|
||||
<prompt>Principal name:</prompt> <---- null entry here will cause an exit</screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<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> command. This will create a file
|
||||
which must be copied or moved <emphasis>by secure means</emphasis> to
|
||||
each Kerberos client's <filename class="directory">/etc</filename>
|
||||
directory. This file must be present on each server and client, and is
|
||||
crucial to the operation of Kerberos.</para>
|
||||
|
||||
|
||||
<screen>&prompt.root; <userinput>ext_srvtab grunt</userinput>
|
||||
<prompt>Enter Kerberos master key:</prompt>
|
||||
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!
|
||||
Generating 'grunt-new-srvtab'....</screen>
|
||||
|
||||
<para>Now, this command only generates a temporary file which must be
|
||||
renamed to <filename>srvtab</filename> so that all the servers can pick
|
||||
it up. Use the &man.mv.1; command to move it into place on
|
||||
the original system:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mv grunt-new-srvtab srvtab</userinput></screen>
|
||||
|
||||
<para>If the file is for a client system, and the network is not deemed
|
||||
safe, then copy the
|
||||
<filename><replaceable>client</replaceable>-new-srvtab</filename> to
|
||||
removable media and transport it by secure physical means. Be sure to
|
||||
rename it to <filename>srvtab</filename> in the client's <filename
|
||||
class="directory">/etc</filename> directory, and make sure it is
|
||||
mode 600:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mv grumble-new-srvtab srvtab</userinput>
|
||||
&prompt.root; <userinput>chmod 600 srvtab</userinput></screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Populating the Database</title>
|
||||
|
||||
<para>We now have to add some user entries into the database. First
|
||||
let us create an entry for the user <username>jane</username>. Use the
|
||||
<command>kdb_edit</command> command to do this:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kdb_edit</userinput>
|
||||
Opening database...
|
||||
|
||||
<prompt>Enter Kerberos master key:</prompt>
|
||||
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!
|
||||
Previous or default values are in [brackets] ,
|
||||
enter return to leave the same, or new value.
|
||||
|
||||
<prompt>Principal name:</prompt> <userinput>jane</userinput>
|
||||
<prompt>Instance:</prompt>
|
||||
|
||||
<Not found>, <prompt>Create [y] ?</prompt> <userinput>y</userinput>
|
||||
|
||||
Principal: jane, Instance: , kdc_key_ver: 1
|
||||
<prompt>New Password:</prompt> <---- enter a secure password here
|
||||
Verifying password
|
||||
|
||||
<prompt>New Password:</prompt> <---- re-enter the password here
|
||||
Principal's new key version = 1
|
||||
<prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
|
||||
<prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt>
|
||||
<prompt>Attributes [ 0 ] ?</prompt>
|
||||
Edit O.K.
|
||||
<prompt>Principal name:</prompt> <---- null entry here will cause an exit</screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<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
|
||||
will happen automatically when you reboot. This is only necessary on
|
||||
the Kerberos server. Kerberos clients will automatically get what
|
||||
they need from the <filename
|
||||
class="directory">/etc/kerberosIV</filename> directory.</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kerberos &</userinput>
|
||||
Kerberos server starting
|
||||
Sleep forever on error
|
||||
Log file is /var/log/kerberos.log
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!
|
||||
|
||||
Current Kerberos master key version is 1
|
||||
Local realm: EXAMPLE.COM
|
||||
&prompt.root; <userinput>kadmind -n &</userinput>
|
||||
KADM Server KADM0.0A initializing
|
||||
Please do not use 'kill -9' to kill this job, use a
|
||||
regular kill instead
|
||||
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!</screen>
|
||||
|
||||
<para>Now we can try using the <command>kinit</command> command to get a
|
||||
ticket for the ID <username>jane</username> that we created
|
||||
above:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>kinit jane</userinput>
|
||||
MIT Project Athena (grunt.example.com)
|
||||
Kerberos Initialization for "jane"
|
||||
<prompt>Password:</prompt> </screen>
|
||||
|
||||
<para>Try listing the tokens using <command>klist</command> to see if we
|
||||
really have them:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>klist</userinput>
|
||||
Ticket file: /tmp/tkt245
|
||||
Principal: jane@EXAMPLE.COM
|
||||
|
||||
Issued Expires Principal
|
||||
Apr 30 11:23:22 Apr 30 19:23:22 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
|
||||
|
||||
<para>Now try changing the password using &man.passwd.1; to
|
||||
check if the <application>kpasswd</application> daemon can get
|
||||
authorization to the Kerberos database:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>passwd</userinput>
|
||||
realm EXAMPLE.COM
|
||||
<prompt>Old password for jane:</prompt>
|
||||
<prompt>New Password for jane:</prompt>
|
||||
Verifying password
|
||||
<prompt>New Password for jane:</prompt>
|
||||
Password changed.</screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Adding <command>su</command> Privileges</title>
|
||||
|
||||
<para>Kerberos allows us to give <emphasis>each</emphasis> user
|
||||
who needs <username>root</username> privileges their own
|
||||
<emphasis>separate</emphasis> &man.su.1; password.
|
||||
We could now add an ID which is authorized to
|
||||
&man.su.1; to <username>root</username>. This is
|
||||
controlled by having an instance of <username>root</username>
|
||||
associated with a principal. Using <command>kdb_edit</command>
|
||||
we can create the entry <literal>jane.root</literal> in the
|
||||
Kerberos database:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kdb_edit</userinput>
|
||||
Opening database...
|
||||
|
||||
<prompt>Enter Kerberos master key:</prompt>
|
||||
|
||||
Current Kerberos master key version is 1.
|
||||
|
||||
Master key entered. BEWARE!
|
||||
Previous or default values are in [brackets] ,
|
||||
enter return to leave the same, or new value.
|
||||
|
||||
<prompt>Principal name:</prompt> <userinput>jane</userinput>
|
||||
<prompt>Instance:</prompt> <userinput>root</userinput>
|
||||
|
||||
<Not found>, Create [y] ? y
|
||||
|
||||
Principal: jane, Instance: root, kdc_key_ver: 1
|
||||
<prompt>New Password:</prompt> <---- enter a SECURE password here
|
||||
Verifying password
|
||||
|
||||
<prompt>New Password:</prompt> <---- re-enter the password here
|
||||
|
||||
Principal's new key version = 1
|
||||
<prompt>Expiration date (enter yyyy-mm-dd) [ 2000-01-01 ] ?</prompt>
|
||||
<prompt>Max ticket lifetime (*5 minutes) [ 255 ] ?</prompt> <userinput>12</userinput> <--- Keep this short!
|
||||
<prompt>Attributes [ 0 ] ?</prompt>
|
||||
Edit O.K.
|
||||
<prompt>Principal name:</prompt> <---- null entry here will cause an exit</screen>
|
||||
|
||||
<para>Now try getting tokens for it to make sure it works:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kinit jane.root</userinput>
|
||||
MIT Project Athena (grunt.example.com)
|
||||
Kerberos Initialization for "jane.root"
|
||||
<prompt>Password:</prompt></screen>
|
||||
|
||||
<para>Now we need to add the user to <username>root</username>'s
|
||||
<filename>.klogin</filename> file:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
|
||||
jane.root@EXAMPLE.COM</screen>
|
||||
|
||||
<para>Now try doing the &man.su.1;:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>su</userinput>
|
||||
<prompt>Password:</prompt></screen>
|
||||
|
||||
<para>and take a look at what tokens we have:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>klist</userinput>
|
||||
Ticket file: /tmp/tkt_root_245
|
||||
Principal: jane.root@EXAMPLE.COM
|
||||
|
||||
Issued Expires Principal
|
||||
May 2 20:43:12 May 3 04:43:12 krbtgt.EXAMPLE.COM@EXAMPLE.COM</screen>
|
||||
</sect2>
|
||||
|
||||
<sect2>
|
||||
<title>Using Other Commands</title>
|
||||
|
||||
<para>In an earlier example, we created a principal called
|
||||
<literal>jane</literal> with an instance <literal>root</literal>.
|
||||
This was based on a user with the same name as the principal, and this
|
||||
is a Kerberos default; that a
|
||||
<literal><principal>.<instance></literal> of the form
|
||||
<literal><username>.</literal><username>root</username> will allow
|
||||
that <literal><username></literal> to &man.su.1; to
|
||||
<username>root</username> if the necessary entries are in the
|
||||
<filename>.klogin</filename> file in <username>root</username>'s
|
||||
home directory:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>cat /root/.klogin</userinput>
|
||||
jane.root@EXAMPLE.COM</screen>
|
||||
|
||||
<para>Likewise, if a user has in their own home directory lines of the
|
||||
form:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>cat ~/.klogin</userinput>
|
||||
jane@EXAMPLE.COM
|
||||
jack@EXAMPLE.COM</screen>
|
||||
|
||||
<para>This allows anyone in the <literal>EXAMPLE.COM</literal> realm
|
||||
who has authenticated themselves as <username>jane</username> or
|
||||
<username>jack</username> (via <command>kinit</command>, see above)
|
||||
to access to <username>jane</username>'s
|
||||
account or files on this system (<hostid>grunt</hostid>) via
|
||||
&man.rlogin.1;, &man.rsh.1; or
|
||||
&man.rcp.1;.</para>
|
||||
|
||||
<para>For example, <username>jane</username> now logs into another system using
|
||||
Kerberos:</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>kinit</userinput>
|
||||
MIT Project Athena (grunt.example.com)
|
||||
<prompt>Password:</prompt>
|
||||
&prompt.user; <userinput>rlogin grunt</userinput>
|
||||
Last login: Mon May 1 21:14:47 from grumble
|
||||
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
|
||||
The Regents of the University of California. All rights reserved.
|
||||
|
||||
FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
||||
|
||||
<para>Or <username>jack</username> logs into <username>jane</username>'s account on the same machine
|
||||
(<username>jane</username> having
|
||||
set up the <filename>.klogin</filename> file as above, and the person
|
||||
in charge of Kerberos having set up principal
|
||||
<emphasis>jack</emphasis> with a null instance):</para>
|
||||
|
||||
<screen>&prompt.user; <userinput>kinit</userinput>
|
||||
&prompt.user; <userinput>rlogin grunt -l jane</userinput>
|
||||
MIT Project Athena (grunt.example.com)
|
||||
<prompt>Password:</prompt>
|
||||
Last login: Mon May 1 21:16:55 from grumble
|
||||
Copyright (c) 1980, 1983, 1986, 1988, 1990, 1991, 1993, 1994
|
||||
The Regents of the University of California. All rights reserved.
|
||||
FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
<sect1 id="kerberos5">
|
||||
<sect1info>
|
||||
<authorgroup>
|
||||
|
|
@ -2075,17 +1578,6 @@ FreeBSD BUILT-19950429 (GR386) #0: Sat Apr 29 17:50:09 SAT 1995</screen>
|
|||
|
||||
<title><application>Kerberos5</application></title>
|
||||
|
||||
<para>Every &os; release beyond &os;-5.1 includes support
|
||||
only for <application>Kerberos5</application>. Hence
|
||||
<application>Kerberos5</application> is the only version
|
||||
included, and its configuration is similar in many aspects
|
||||
to that of <application>KerberosIV</application>. The following
|
||||
information only applies to
|
||||
<application>Kerberos5</application> in post &os;-5.0
|
||||
releases. Users who wish to use the
|
||||
<application>KerberosIV</application> package may install the
|
||||
<filename role="package">security/krb4</filename> port.</para>
|
||||
|
||||
<para><application>Kerberos</application> is a network add-on
|
||||
system/protocol that allows users to authenticate themselves
|
||||
through the services of a secure server. Services such as remote
|
||||
|
|
@ -2860,7 +2352,7 @@ kadmind5_server_enable="YES"</programlisting>
|
|||
encrypted authentication of mail clients, web based transactions
|
||||
such as credit card payments and more. Many ports such as
|
||||
<filename role="package">www/apache13-ssl</filename>, and
|
||||
<filename role="package">mail/sylpheed-claws</filename>
|
||||
<filename role="package">mail/claws-mail</filename>
|
||||
will offer compilation support for building with
|
||||
<application>OpenSSL</application>.</para>
|
||||
|
||||
|
|
@ -3981,8 +3473,8 @@ user@unfirewalled-system.example.org's password: <userinput>*******</userinput><
|
|||
</indexterm>
|
||||
<title>File System Access Control Lists</title>
|
||||
|
||||
<para>In conjunction with file system enhancements like snapshots, FreeBSD 5.0
|
||||
and later offers the security of File System Access Control Lists
|
||||
<para>In conjunction with file system enhancements like snapshots, FreeBSD
|
||||
offers the security of File System Access Control Lists
|
||||
(<acronym>ACL</acronym>s).</para>
|
||||
|
||||
<para>Access Control Lists extend the standard &unix;
|
||||
|
|
|
|||
|
|
@ -61,6 +61,17 @@
|
|||
<sect1 id="serial">
|
||||
<title>Introduction</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/cuad<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/cuau<replaceable>N</replaceable></filename> and
|
||||
from
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
<!-- XXX Write me! -->
|
||||
|
||||
<sect2 id="serial-terminology">
|
||||
|
|
@ -484,7 +495,7 @@
|
|||
<itemizedlist>
|
||||
<listitem>
|
||||
<para>Call-in ports are named
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename>
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>
|
||||
where <replaceable>N</replaceable> is the port number,
|
||||
starting from zero. Generally, you use the call-in port for
|
||||
terminals. Call-in ports require that the serial line assert
|
||||
|
|
@ -493,7 +504,7 @@
|
|||
|
||||
<listitem>
|
||||
<para>Call-out ports are named
|
||||
<filename>/dev/cuad<replaceable>N</replaceable></filename>.
|
||||
<filename>/dev/cuau<replaceable>N</replaceable></filename>.
|
||||
You usually do not use the call-out port for terminals, just
|
||||
for modems. You may use the call-out port if the serial cable
|
||||
or the terminal does not support the carrier detect
|
||||
|
|
@ -503,10 +514,10 @@
|
|||
|
||||
<para>If you have connected a terminal to the first serial port
|
||||
(<devicename>COM1</devicename> in &ms-dos;), then you will
|
||||
use <filename>/dev/ttyd0</filename> to refer to the terminal. If
|
||||
use <filename>/dev/ttyu0</filename> to refer to the terminal. If
|
||||
the terminal is on the second serial port (also known as
|
||||
<devicename>COM2</devicename>), use
|
||||
<filename>/dev/ttyd1</filename>, and so forth.</para>
|
||||
<filename>/dev/ttyu1</filename>, and so forth.</para>
|
||||
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
|
@ -562,7 +573,7 @@ sio3: type 16550A</screen>
|
|||
Be careful if you are using a configuration
|
||||
file that was previously used for a different version of
|
||||
FreeBSD because the device flags and the syntax have changed between
|
||||
versions.</para>
|
||||
versions.
|
||||
|
||||
<note>
|
||||
<para><literal>port IO_COM1</literal> is a substitution for
|
||||
|
|
@ -587,15 +598,15 @@ sio3: type 16550A</screen>
|
|||
special files</quote>, which are located in the
|
||||
<filename>/dev</filename> directory. The <devicename>sio</devicename>
|
||||
devices are accessed through the
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> (dial-in)
|
||||
and <filename>/dev/cuad<replaceable>N</replaceable></filename>
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename> (dial-in)
|
||||
and <filename>/dev/cuau<replaceable>N</replaceable></filename>
|
||||
(call-out) devices. FreeBSD also provides initialization devices
|
||||
(<filename>/dev/ttyd<replaceable>N</replaceable>.init</filename> and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.init</filename>)
|
||||
(<filename>/dev/ttyu<replaceable>N</replaceable>.init</filename> and
|
||||
<filename>/dev/cuau<replaceable>N</replaceable>.init</filename>)
|
||||
and
|
||||
locking devices
|
||||
(<filename>/dev/ttyd<replaceable>N</replaceable>.lock</filename> and
|
||||
<filename>/dev/cuad<replaceable>N</replaceable>.lock</filename>).
|
||||
(<filename>/dev/ttyu<replaceable>N</replaceable>.lock</filename> and
|
||||
<filename>/dev/cuau<replaceable>N</replaceable>.lock</filename>).
|
||||
The
|
||||
initialization devices are used to initialize communications port
|
||||
parameters each time a port is opened, such as
|
||||
|
|
@ -612,16 +623,16 @@ sio3: type 16550A</screen>
|
|||
<sect2 id="serial-hw-config">
|
||||
<title>Serial Port Configuration</title>
|
||||
|
||||
<indexterm><primary><devicename>ttyd</devicename></primary></indexterm>
|
||||
<indexterm><primary><devicename>cuad</devicename></primary></indexterm>
|
||||
<indexterm><primary><devicename>ttyu</devicename></primary></indexterm>
|
||||
<indexterm><primary><devicename>cuau</devicename></primary></indexterm>
|
||||
|
||||
<para>The <devicename>ttyd<replaceable>N</replaceable></devicename> (or
|
||||
<devicename>cuad<replaceable>N</replaceable></devicename>) device is the
|
||||
<para>The <devicename>ttyu<replaceable>N</replaceable></devicename> (or
|
||||
<devicename>cuau<replaceable>N</replaceable></devicename>) device is the
|
||||
regular device you will want to open for your applications. When a
|
||||
process opens the device, it will have a default set of terminal I/O
|
||||
settings. You can see these settings with the command</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -a -f /dev/ttyd1</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>stty -a -f /dev/ttyu1</userinput></screen>
|
||||
|
||||
<para>When you change the settings to this device, the settings are in
|
||||
effect until the device is closed. When it is reopened, it goes back to
|
||||
|
|
@ -629,9 +640,9 @@ sio3: type 16550A</screen>
|
|||
adjust the settings of the <quote>initial state</quote> device. For
|
||||
example, to turn on <option>CLOCAL</option> mode, 8 bit communication,
|
||||
and <option>XON/XOFF</option> flow control by default for
|
||||
<devicename>ttyd5</devicename>, type:</para>
|
||||
<devicename>ttyu5</devicename>, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyd5.init clocal cs8 ixon ixoff</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyu5.init clocal cs8 ixon ixoff</userinput></screen>
|
||||
|
||||
<indexterm>
|
||||
<primary>rc files</primary>
|
||||
|
|
@ -645,12 +656,12 @@ sio3: type 16550A</screen>
|
|||
<para>To prevent certain settings from being changed by an
|
||||
application, make adjustments to the <quote>lock state</quote>
|
||||
device. For example, to lock the speed of
|
||||
<devicename>ttyd5</devicename> to 57600 bps, type:</para>
|
||||
<devicename>ttyu5</devicename> to 57600 bps, type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyd5.lock 57600</userinput></screen>
|
||||
<screen>&prompt.root; <userinput>stty -f /dev/ttyu5.lock 57600</userinput></screen>
|
||||
|
||||
<para>Now, an application that opens
|
||||
<devicename>ttyd5</devicename> and tries to change the speed of
|
||||
<devicename>ttyu5</devicename> and tries to change the speed of
|
||||
the port will be stuck with 57600 bps.</para>
|
||||
|
||||
<para>Naturally, you should make the initial state and lock state devices
|
||||
|
|
@ -671,6 +682,18 @@ sio3: type 16550A</screen>
|
|||
</sect1info>
|
||||
<title>Terminals</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/cuad<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/cuau<replaceable>N</replaceable></filename> and
|
||||
from
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
|
||||
<indexterm><primary>terminals</primary></indexterm>
|
||||
|
||||
<para>Terminals provide a convenient and low-cost way to access
|
||||
|
|
@ -769,7 +792,7 @@ sio3: type 16550A</screen>
|
|||
<para>Where <quote>serial-port-device</quote> is the name of a
|
||||
special device file denoting a serial port of your system.
|
||||
These device files are called
|
||||
<devicename>/dev/cuad<replaceable>N</replaceable></devicename>.</para>
|
||||
<devicename>/dev/cuau<replaceable>N</replaceable></devicename>.</para>
|
||||
|
||||
<para>The <quote>N</quote>-part of a device name is the serial
|
||||
port number.</para>
|
||||
|
|
@ -779,7 +802,7 @@ sio3: type 16550A</screen>
|
|||
one (like they do, for instance in &ms-dos;-derived systems).
|
||||
This means that what &ms-dos;-based systems call
|
||||
<devicename>COM1</devicename> is usually
|
||||
<filename>/dev/cuad0</filename> in &os;.</para>
|
||||
<filename>/dev/cuau0</filename> in &os;.</para>
|
||||
</note>
|
||||
|
||||
<note>
|
||||
|
|
@ -882,8 +905,8 @@ sio3: type 16550A</screen>
|
|||
|
||||
<para>A default FreeBSD install includes an
|
||||
<filename>/etc/ttys</filename> file with support for the first
|
||||
four serial ports: <devicename>ttyd0</devicename> through
|
||||
<devicename>ttyd3</devicename>. If you are attaching a terminal
|
||||
four serial ports: <devicename>ttyu0</devicename> through
|
||||
<devicename>ttyu3</devicename>. If you are attaching a terminal
|
||||
to one of those ports, you do not need to add another entry.</para>
|
||||
|
||||
<example id="ex-etc-ttys">
|
||||
|
|
@ -899,13 +922,13 @@ sio3: type 16550A</screen>
|
|||
entries in the <filename>/etc/ttys</filename> file would
|
||||
look like this:</para>
|
||||
|
||||
<programlisting>ttyd1<co
|
||||
<programlisting>ttyu1<co
|
||||
id="co-ttys-line1col1"> "/usr/libexec/getty std.38400"<co
|
||||
id="co-ttys-line1col2"> wy50<co
|
||||
id="co-ttys-line1col3"> on<co
|
||||
id="co-ttys-line1col4"> insecure<co
|
||||
id="co-ttys-line1col5">
|
||||
ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
||||
ttyu5 "/usr/libexec/getty std.19200" vt100 on insecure
|
||||
</programlisting>
|
||||
|
||||
<calloutlist>
|
||||
|
|
@ -1058,11 +1081,11 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<para>You should see an entry for the terminal. For
|
||||
example, the following display shows that a
|
||||
<command>getty</command> is running on the second serial
|
||||
port <devicename>ttyd1</devicename> and is using the
|
||||
port <devicename>ttyu1</devicename> and is using the
|
||||
<literal>std.38400</literal> entry in
|
||||
<filename>/etc/gettytab</filename>:</para>
|
||||
|
||||
<screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyd1</screen>
|
||||
<screen>22189 d1 Is+ 0:00.03 /usr/libexec/getty std.38400 ttyu1</screen>
|
||||
|
||||
<para>If no <command>getty</command> process is running, make sure
|
||||
you have enabled the port in <filename>/etc/ttys</filename>.
|
||||
|
|
@ -1130,6 +1153,19 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
</authorgroup>
|
||||
</sect1info>
|
||||
<title>Dial-in Service</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/cuad<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/cuau<replaceable>N</replaceable></filename> and
|
||||
from
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
|
||||
<indexterm><primary>dial-in service</primary></indexterm>
|
||||
|
||||
<para>Configuring your FreeBSD system for dial-in service is very
|
||||
|
|
@ -1259,10 +1295,10 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<para>As with terminals, <command>init</command> spawns a
|
||||
<command>getty</command> process for each configured serial
|
||||
port for dial-in connections. For example, if a modem is
|
||||
attached to <filename>/dev/ttyd0</filename>, the command
|
||||
attached to <filename>/dev/ttyu0</filename>, the command
|
||||
<command>ps ax</command> might show this:</para>
|
||||
|
||||
<screen> 4850 ?? I 0:00.09 /usr/libexec/getty V19200 ttyd0</screen>
|
||||
<screen> 4850 ?? I 0:00.09 /usr/libexec/getty V19200 ttyu0</screen>
|
||||
|
||||
<para>When a user dials the modem's line and the modems connect, the
|
||||
<acronym>CD</acronym> (Carrier Detect) line is reported by the modem.
|
||||
|
|
@ -1447,11 +1483,11 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
different terminal type. The general format for both
|
||||
locked-speed and matching-speed configurations is:</para>
|
||||
|
||||
<programlisting>ttyd0 "/usr/libexec/getty <replaceable>xxx</replaceable>" dialup on</programlisting>
|
||||
<programlisting>ttyu0 "/usr/libexec/getty <replaceable>xxx</replaceable>" dialup on</programlisting>
|
||||
|
||||
<para>The first item in the above line is the device special file for
|
||||
this entry — <devicename>ttyd0</devicename> means
|
||||
<filename>/dev/ttyd0</filename> is the file that this
|
||||
this entry — <devicename>ttyu0</devicename> means
|
||||
<filename>/dev/ttyu0</filename> is the file that this
|
||||
<command>getty</command> will be watching. The second item,
|
||||
<literal>"/usr/libexec/getty
|
||||
<replaceable>xxx</replaceable>"</literal>
|
||||
|
|
@ -1496,7 +1532,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
speed is locked at 19.2 Kbps, the <filename>ttys</filename>
|
||||
entry might look like this:</para>
|
||||
|
||||
<programlisting>ttyd0 "/usr/libexec/getty std.19200" dialup on</programlisting>
|
||||
<programlisting>ttyu0 "/usr/libexec/getty std.19200" dialup on</programlisting>
|
||||
|
||||
<para>If your modem is locked at a different data rate,
|
||||
substitute the appropriate value for
|
||||
|
|
@ -1518,7 +1554,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
the <literal>V19200</literal> starting point), your
|
||||
<filename>ttys</filename> entry might look like this:</para>
|
||||
|
||||
<programlisting>ttyd0 "/usr/libexec/getty V19200" dialup on</programlisting>
|
||||
<programlisting>ttyu0 "/usr/libexec/getty V19200" dialup on</programlisting>
|
||||
</sect4>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -1542,8 +1578,8 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
devices, the following lines could be added to
|
||||
<filename>/etc/rc.d/serial</filename>:</para>
|
||||
<programlisting># Serial port initial configuration
|
||||
stty -f /dev/ttyd1.init crtscts
|
||||
stty -f /dev/cuad1.init crtscts</programlisting>
|
||||
stty -f /dev/ttyu1.init crtscts
|
||||
stty -f /dev/cuau1.init crtscts</programlisting>
|
||||
|
||||
</sect3>
|
||||
</sect2>
|
||||
|
|
@ -1717,12 +1753,12 @@ AT&B2&W</programlisting>
|
|||
<command>getty</command> process on the correct port. You should see
|
||||
lines like these among the processes displayed:</para>
|
||||
|
||||
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd0
|
||||
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyd1</screen>
|
||||
<screen> 114 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu0
|
||||
115 ?? I 0:00.10 /usr/libexec/getty V19200 ttyu1</screen>
|
||||
|
||||
<para>If you see something different, like this:</para>
|
||||
|
||||
<screen> 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyd0</screen>
|
||||
<screen> 114 d0 I 0:00.10 /usr/libexec/getty V19200 ttyu0</screen>
|
||||
|
||||
<para>and the modem has not accepted a call yet, this means that
|
||||
<command>getty</command> has completed its open on the
|
||||
|
|
@ -1734,7 +1770,7 @@ AT&B2&W</programlisting>
|
|||
|
||||
<para>If you do not see any <command>getty</command> processes waiting
|
||||
to open the desired
|
||||
<devicename>ttyd<replaceable>N</replaceable></devicename> port,
|
||||
<devicename>ttyu<replaceable>N</replaceable></devicename> port,
|
||||
double-check your entries in <filename>/etc/ttys</filename> to see
|
||||
if there are any mistakes there. Also, check the log file
|
||||
<filename>/var/log/messages</filename> to see if there are any log
|
||||
|
|
@ -1742,7 +1778,7 @@ AT&B2&W</programlisting>
|
|||
regarding any problems. If there are any messages, triple-check the
|
||||
configuration files <filename>/etc/ttys</filename> and
|
||||
<filename>/etc/gettytab</filename>, as well as the appropriate
|
||||
device special files <filename>/dev/ttydN</filename>, for any
|
||||
device special files <filename>/dev/ttyuN</filename>, for any
|
||||
mistakes, missing entries, or missing device special files.</para>
|
||||
</sect3>
|
||||
|
||||
|
|
@ -1801,6 +1837,16 @@ AT&B2&W</programlisting>
|
|||
|
||||
<sect1 id="dialout">
|
||||
<title>Dial-out Service</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/cuad<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/cuau<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
|
||||
<indexterm><primary>dial-out service</primary></indexterm>
|
||||
|
||||
<para>The following are tips for getting your host to be able to connect
|
||||
|
|
@ -1842,13 +1888,13 @@ AT&B2&W</programlisting>
|
|||
</indexterm>
|
||||
<para>Make what is called a <quote>direct</quote> entry in your
|
||||
<filename>/etc/remote</filename> file. For example, if your modem is
|
||||
hooked up to the first serial port, <filename>/dev/cuad0</filename>,
|
||||
hooked up to the first serial port, <filename>/dev/cuau0</filename>,
|
||||
then put in the following line:</para>
|
||||
|
||||
<programlisting>cuad0:dv=/dev/cuad0:br#19200:pa=none</programlisting>
|
||||
<programlisting>cuau0:dv=/dev/cuau0:br#19200:pa=none</programlisting>
|
||||
|
||||
<para>Use the highest bps rate your modem supports in the br capability.
|
||||
Then, type <command>tip cuad0</command> and you will be connected to
|
||||
Then, type <command>tip cuau0</command> and you will be connected to
|
||||
your modem.</para>
|
||||
|
||||
<para>Or use <command>cu</command> as <username>root</username> with the
|
||||
|
|
@ -1857,7 +1903,7 @@ AT&B2&W</programlisting>
|
|||
<screen>&prompt.root; <userinput>cu -l<replaceable>line</replaceable> -s<replaceable>speed</replaceable></userinput></screen>
|
||||
|
||||
<para><replaceable>line</replaceable> is the serial port
|
||||
(e.g.<filename>/dev/cuad0</filename>) and
|
||||
(e.g.<filename>/dev/cuau0</filename>) and
|
||||
<replaceable>speed</replaceable> is the speed
|
||||
(e.g.<literal>57600</literal>). When you are done entering the AT
|
||||
commands type <command>~.</command> to exit.</para>
|
||||
|
|
@ -1883,9 +1929,9 @@ AT&B2&W</programlisting>
|
|||
<filename>/etc/remote</filename> file. For example:</para>
|
||||
|
||||
<programlisting>tip115200|Dial any phone number at 115200 bps:\
|
||||
:dv=/dev/cuad0:br#115200:at=hayes:pa=none:du:
|
||||
:dv=/dev/cuau0:br#115200:at=hayes:pa=none:du:
|
||||
tip57600|Dial any phone number at 57600 bps:\
|
||||
:dv=/dev/cuad0:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
:dv=/dev/cuau0:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
|
||||
<para>Then you can do things like:</para>
|
||||
|
||||
|
|
@ -1895,7 +1941,7 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
use a generic <literal>cu</literal> entry:</para>
|
||||
|
||||
<programlisting>cu115200|Use cu to dial any number at 115200bps:\
|
||||
:dv=/dev/cuad1:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
:dv=/dev/cuau1:br#57600:at=hayes:pa=none:du:</programlisting>
|
||||
|
||||
<para>and type:</para>
|
||||
|
||||
|
|
@ -1926,7 +1972,7 @@ tip57600|Dial any phone number at 57600 bps:\
|
|||
muffin|muffin.deep13.com|Frank's machine:\
|
||||
:cm=CONNECT muffin\n:tc=deep13:
|
||||
deep13:Gizmonics Institute terminal server:\
|
||||
:dv=/dev/cuad2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
|
||||
:dv=/dev/cuau2:br#38400:at=hayes:du:pa=none:pn=5551234:</programlisting>
|
||||
|
||||
<para>will let you type <command>tip pain</command> or <command>tip
|
||||
muffin</command> to connect to the hosts <hostid>pain</hostid> or
|
||||
|
|
@ -1947,7 +1993,7 @@ deep13:Gizmonics Institute terminal server:\
|
|||
<programlisting>big-university:\
|
||||
:pn=\@:tc=dialout
|
||||
dialout:\
|
||||
:dv=/dev/cuad3:br#9600:at=courier:du:pa=none:</programlisting>
|
||||
:dv=/dev/cuau3:br#9600:at=courier:du:pa=none:</programlisting>
|
||||
|
||||
<para>Then, list the phone numbers for the university in
|
||||
<filename>/etc/phones</filename>:</para>
|
||||
|
|
@ -2101,6 +2147,16 @@ raisechar=^^</programlisting>
|
|||
</authorgroup>
|
||||
</sect1info>
|
||||
<title>Setting Up the Serial Console</title>
|
||||
|
||||
<warning>
|
||||
<para>As of &os; 8.0, device nodes for serial ports have been
|
||||
renamed from
|
||||
<filename>/dev/ttyd<replaceable>N</replaceable></filename> to
|
||||
<filename>/dev/ttyu<replaceable>N</replaceable></filename>.
|
||||
&os; 7.X users will have to adapt the following
|
||||
documentation according to these changes.</para>
|
||||
</warning>
|
||||
|
||||
<indexterm><primary>serial console</primary></indexterm>
|
||||
|
||||
<sect2 id="serialconsole-intro">
|
||||
|
|
@ -2148,7 +2204,7 @@ raisechar=^^</programlisting>
|
|||
<para>Edit <filename>/etc/ttys</filename> and change
|
||||
<literal>off</literal> to <literal>on</literal> and
|
||||
<literal>dialup</literal> to <literal>vt100</literal> for the
|
||||
<devicename>ttyd0</devicename> entry. Otherwise a password will
|
||||
<devicename>ttyu0</devicename> entry. Otherwise a password will
|
||||
not be required to connect via the serial console, resulting in a
|
||||
potential security hole.</para>
|
||||
</step>
|
||||
|
|
@ -2298,7 +2354,7 @@ raisechar=^^</programlisting>
|
|||
|
||||
<para>Example:</para>
|
||||
|
||||
<programlisting>device sio0 at isa? port IO_COM1 flags 0x10 irq 4</programlisting>
|
||||
<programlisting>device sio0 flags 0x10</programlisting>
|
||||
|
||||
<para>See the &man.sio.4; manual page for more details.</para>
|
||||
|
||||
|
|
@ -2496,7 +2552,7 @@ boot:</screen>
|
|||
<title>Case 1: You Set the Flags to 0x10 for
|
||||
<devicename>sio0</devicename></title>
|
||||
|
||||
<programlisting>device sio0 at isa? port IO_COM1 flags 0x10 irq 4</programlisting>
|
||||
<programlisting>device sio0 flags 0x10</programlisting>
|
||||
|
||||
<informaltable frame="none" pgwide="1">
|
||||
<tgroup cols="4">
|
||||
|
|
@ -2559,7 +2615,7 @@ boot:</screen>
|
|||
<sect3>
|
||||
<title>Case 2: You Set the Flags to 0x30 for <devicename>sio0</devicename></title>
|
||||
|
||||
<programlisting>device sio0 at isa? port IO_COM1 flags 0x30 irq 4</programlisting>
|
||||
<programlisting>device sio0 flags 0x30</programlisting>
|
||||
|
||||
<informaltable frame="none" pgwide="1">
|
||||
<tgroup cols="4">
|
||||
|
|
@ -2708,11 +2764,11 @@ console="comconsole,vidconsole"</programlisting>
|
|||
example, if you want to make <devicename>sio1</devicename>
|
||||
(<devicename>COM2</devicename>) the console:</para>
|
||||
|
||||
<programlisting>device sio1 at isa? port IO_COM2 flags 0x10 irq 3</programlisting>
|
||||
<programlisting>device sio1 flags 0x10</programlisting>
|
||||
|
||||
<para>or</para>
|
||||
|
||||
<programlisting>device sio1 at isa? port IO_COM2 flags 0x30 irq 3</programlisting>
|
||||
<programlisting>device sio1 flags 0x30</programlisting>
|
||||
|
||||
<para>The console flags for the other serial ports should not be
|
||||
set.</para>
|
||||
|
|
@ -2762,13 +2818,13 @@ options DDB</programlisting>
|
|||
<para>Open the file <filename>/etc/ttys</filename> with an editor
|
||||
and locate the lines:</para>
|
||||
|
||||
<programlisting>ttyd0 "/usr/libexec/getty std.9600" unknown off secure
|
||||
ttyd1 "/usr/libexec/getty std.9600" unknown off secure
|
||||
ttyd2 "/usr/libexec/getty std.9600" unknown off secure
|
||||
ttyd3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
||||
<programlisting>ttyu0 "/usr/libexec/getty std.9600" unknown off secure
|
||||
ttyu1 "/usr/libexec/getty std.9600" unknown off secure
|
||||
ttyu2 "/usr/libexec/getty std.9600" unknown off secure
|
||||
ttyu3 "/usr/libexec/getty std.9600" unknown off secure</programlisting>
|
||||
|
||||
<para><devicename>ttyd0</devicename> through
|
||||
<devicename>ttyd3</devicename> corresponds to
|
||||
<para><devicename>ttyu0</devicename> through
|
||||
<devicename>ttyu3</devicename> corresponds to
|
||||
<devicename>COM1</devicename> through <devicename>COM4</devicename>.
|
||||
Change <literal>off</literal> to <literal>on</literal> for the
|
||||
desired port. If you have changed the speed of the serial port,
|
||||
|
|
|
|||
|
|
@ -765,16 +765,6 @@
|
|||
would cause Vinum to create the following device nodes:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
<note><para>This only applies to the historic Vinum
|
||||
implemenation.</para></note>
|
||||
|
||||
<para>The control devices
|
||||
<filename class="devicefile">/dev/vinum/control</filename> and
|
||||
<filename class="devicefile">/dev/vinum/controld</filename>, which are used
|
||||
by &man.gvinum.8; and the Vinum daemon respectively.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>Device entries for each volume.
|
||||
These are the main devices used by Vinum. Thus the configuration
|
||||
|
|
@ -786,15 +776,6 @@
|
|||
<filename class="devicefile">/dev/gvinum/raid10</filename>.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<note><para>This only applies to the historic Vinum
|
||||
implemenation.</para></note>
|
||||
|
||||
<para>A directory <filename class="directory">/dev/vinum/drive</filename>
|
||||
with entries for each drive. These entries are in fact
|
||||
symbolic links to the corresponding disk nodes.</para>
|
||||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<para>All volumes get direct entries under
|
||||
<filename class="directory">/dev/gvinum/</filename>.</para>
|
||||
|
|
@ -877,13 +858,6 @@ newfs: /dev/gvinum/concat: can't figure out file system partition</screen>
|
|||
&man.newfs.8;:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>newfs /dev/gvinum/concat</userinput></screen>
|
||||
|
||||
<note><para>On &os; versions prior to 5.0 &man.newfs.8; requires
|
||||
an additional <option>-v</option> flag and the old device naming
|
||||
scheme:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>newfs -v /dev/vinum/concat</userinput></screen></note>
|
||||
|
||||
</sect2>
|
||||
</sect1>
|
||||
|
||||
|
|
@ -943,29 +917,15 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
|
|||
<sect3 id="vinum-rc-startup">
|
||||
<title>Automatic Startup</title>
|
||||
|
||||
<note><para>This information only relates to the historic
|
||||
Vinum implementation. <emphasis>Gvinum</emphasis> always
|
||||
<para>
|
||||
<emphasis>Gvinum</emphasis> always
|
||||
features an automatic startup once the kernel module is
|
||||
loaded, via &man.loader.conf.5;. To load the
|
||||
<emphasis>Gvinum</emphasis> module at boot time, add
|
||||
<literal>geom_vinum_load="YES"</literal> to
|
||||
<filename>/boot/loader.conf</filename>.</para></note>
|
||||
<filename>/boot/loader.conf</filename>.</para>
|
||||
|
||||
<para>In order to start Vinum automatically when you boot the
|
||||
system, ensure that you have the following line in your
|
||||
<filename>/etc/rc.conf</filename>:</para>
|
||||
|
||||
<programlisting>start_vinum="YES" # set to YES to start vinum</programlisting>
|
||||
|
||||
<para>If you do not have a file
|
||||
<filename>/etc/rc.conf</filename>, create one with this
|
||||
content. This will cause the system to load the Vinum
|
||||
<acronym>kld</acronym> at startup, and to start any objects
|
||||
mentioned in the configuration. This is done before
|
||||
mounting file systems, so it is possible to automatically
|
||||
&man.fsck.8; and mount file systems on Vinum volumes.</para>
|
||||
|
||||
<para>When you start Vinum with the <command>vinum
|
||||
<para>When you start Vinum with the <command>gvinum
|
||||
start</command> command, Vinum reads the configuration
|
||||
database from one of the Vinum drives. Under normal
|
||||
circumstances, each drive contains an identical copy of the
|
||||
|
|
@ -1040,39 +1000,10 @@ sd name bigraid.p0.s4 drive e plex bigraid.p0 state initializing len 4194304b dr
|
|||
</listitem>
|
||||
|
||||
<listitem>
|
||||
<note><para>For <emphasis>Gvinum</emphasis>, all startup
|
||||
<para>For <emphasis>Gvinum</emphasis>, all startup
|
||||
is done automatically once the kernel module has been
|
||||
loaded, so the procedure described above is all that is
|
||||
needed. The following text documents the behaviour of
|
||||
the historic Vinum system, for the sake of older
|
||||
setups.</para></note>
|
||||
|
||||
<para>Vinum must be initialized early since it needs to
|
||||
supply the volume for the root filesystem. By default,
|
||||
the Vinum kernel part is not looking for drives that might
|
||||
contain Vinum volume information until the administrator
|
||||
(or one of the startup scripts) issues a <command>vinum
|
||||
start</command> command.</para>
|
||||
|
||||
<note><para>The following paragraphs are outlining the steps
|
||||
needed for &os;.</para></note>
|
||||
|
||||
<para>By placing the line:</para>
|
||||
|
||||
<programlisting>vinum.autostart="YES"</programlisting>
|
||||
|
||||
<para>into <filename>/boot/loader.conf</filename>, Vinum is
|
||||
instructed to automatically scan all drives for Vinum
|
||||
information as part of the kernel startup.</para>
|
||||
|
||||
<para>Note that it is not necessary to instruct the kernel
|
||||
where to look for the root filesystem.
|
||||
<filename>/boot/loader</filename> looks up the name of the
|
||||
root device in <filename>/etc/fstab</filename>, and passes
|
||||
this information on to the kernel. When it comes to mount
|
||||
the root filesystem, the kernel figures out from the
|
||||
device name provided which driver to ask to translate this
|
||||
into the internal device ID (major/minor number).</para>
|
||||
needed.</para>
|
||||
</listitem>
|
||||
</itemizedlist>
|
||||
</sect2>
|
||||
|
|
|
|||
|
|
@ -27,27 +27,15 @@
|
|||
<para>FreeBSD uses X11 to provide users with
|
||||
a powerful graphical user interface. X11
|
||||
is a freely available version of the X Window System that
|
||||
is implemented in both <application>&xorg;</application> and
|
||||
<application>&xfree86;</application> (and other software
|
||||
packages not discussed here). &os; versions up to and
|
||||
including &os; 5.2.1-RELEASE
|
||||
will find the default installation to be
|
||||
<application>&xfree86;</application>, the X11 server released by
|
||||
The &xfree86; Project, Inc. As of &os; 5.3-RELEASE, the
|
||||
default and official flavor of X11 was changed to
|
||||
is implemented in <application>&xorg;</application>
|
||||
(and other software
|
||||
packages not discussed here).
|
||||
The
|
||||
default and official flavor of X11 in &os; is
|
||||
<application>&xorg;</application>, the X11 server developed by
|
||||
the X.Org Foundation under a license very similar to the one used
|
||||
by &os;. Commercial X servers for &os; are also available.</para>
|
||||
|
||||
<para>This chapter will cover the installation and configuration
|
||||
of X11 with emphasis on <application>&xorg;</application> &xorg.version; release. For
|
||||
information about configuring <application>&xfree86;</application>
|
||||
(i.e. on older releases of &os; where
|
||||
<application>&xfree86;</application> was the default X11
|
||||
distribution) or previous releases of <application>&xorg;</application>, it is always possible to refer to archived versions
|
||||
of the &os; Handbook at <ulink
|
||||
url="http://docs.FreeBSD.org/doc/"></ulink>.</para>
|
||||
|
||||
<para>For more information on the video hardware that X11
|
||||
supports, check the <ulink
|
||||
url="http://www.x.org/">&xorg;</ulink> web site.</para>
|
||||
|
|
|
|||
|
|
@ -102,6 +102,22 @@
|
|||
<!ENTITY a.ctm-src-4 "<ulink url='&a.ctm-src-4.url;'>CTM 4-STABLE src branch distribution mailing list</ulink>">
|
||||
<!ENTITY a.ctm-src-4.name "<ulink url='&a.ctm-src-4.url;'>ctm-src-4</ulink>">
|
||||
|
||||
<!ENTITY a.ctm-src-5.url "&a.mailman.listinfo;/ctm-src-5">
|
||||
<!ENTITY a.ctm-src-5 "<ulink url='&a.ctm-src-5.url;'>CTM 5-STABLE src branch distribution mailing list</ulink>">
|
||||
<!ENTITY a.ctm-src-5.name "<ulink url='&a.ctm-src-5.url;'>ctm-src-5</ulink>">
|
||||
|
||||
<!ENTITY a.ctm-src-6.url "&a.mailman.listinfo;/ctm-src-6">
|
||||
<!ENTITY a.ctm-src-6 "<ulink url='&a.ctm-src-6.url;'>CTM 6-STABLE src branch distribution mailing list</ulink>">
|
||||
<!ENTITY a.ctm-src-6.name "<ulink url='&a.ctm-src-6.url;'>ctm-src-6</ulink>">
|
||||
|
||||
<!ENTITY a.ctm-src-7.url "&a.mailman.listinfo;/ctm-src-7">
|
||||
<!ENTITY a.ctm-src-7 "<ulink url='&a.ctm-src-7.url;'>CTM 7-STABLE src branch distribution mailing list</ulink>">
|
||||
<!ENTITY a.ctm-src-7.name "<ulink url='&a.ctm-src-7.url;'>ctm-src-7</ulink>">
|
||||
|
||||
<!ENTITY a.ctm-src-8.url "&a.mailman.listinfo;/ctm-src-8">
|
||||
<!ENTITY a.ctm-src-8 "<ulink url='&a.ctm-src-8.url;'>CTM 8-STABLE src branch distribution mailing list</ulink>">
|
||||
<!ENTITY a.ctm-src-8.name "<ulink url='&a.ctm-src-8.url;'>ctm-src-8</ulink>">
|
||||
|
||||
<!ENTITY a.ctm-src-cur.url "&a.mailman.listinfo;/ctm-src-cur">
|
||||
<!ENTITY a.ctm-src-cur "<ulink url='&a.ctm-src-cur.url;'>CTM -CURRENT src branch distribution mailing list</ulink>">
|
||||
<!ENTITY a.ctm-src-cur.name "<ulink url='&a.ctm-src-cur.url;'>ctm-src-cur</ulink>">
|
||||
|
|
|
|||
Loading…
Reference in a new issue