Whitespace fixes.
Punctuation chars should not be preceded by spaces.
This commit is contained in:
parent
591fe197a8
commit
e7655d4598
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=12193
18 changed files with 49 additions and 50 deletions
en_US.ISO8859-1
articles
books
arch-handbook/jail
developers-handbook/jail
faq
handbook
config
cutting-edge
disks
install
linuxemu
mail
mirrors
ports
preface
security
serialcomms
|
@ -40,7 +40,7 @@
|
|||
accessible by any machines other than the 'Clients'.</para>
|
||||
</warning>
|
||||
|
||||
<para>Terminology : </para>
|
||||
<para>Terminology:</para>
|
||||
|
||||
<informaltable frame="none">
|
||||
<tgroup cols="2">
|
||||
|
@ -79,7 +79,7 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Install DHCP : Install isc-dhcp-2.0 you can use this config file
|
||||
<para>Install DHCP: Install isc-dhcp-2.0 you can use this config file
|
||||
<ulink url="http://people.FreeBSD.org/~alfred/pxe/dhcpd.conf">
|
||||
dhcpd.conf</ulink>, stick it in /usr/local/etc/</para>
|
||||
</step>
|
||||
|
@ -132,7 +132,7 @@
|
|||
|
||||
<procedure>
|
||||
<step>
|
||||
<para>Download bootfiles : Download the
|
||||
<para>Download bootfiles: Download the
|
||||
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386/kern.flp">
|
||||
kern.flp</ulink> and
|
||||
<ulink url="ftp://ftp.FreeBSD.org/pub/FreeBSD/snapshots/i386/mfsroot.flp">
|
||||
|
|
|
@ -223,11 +223,11 @@
|
|||
|
||||
<para>The next step is to create a branch point
|
||||
<emphasis>tag</emphasis>, so that diffs against the start of
|
||||
the branch are easier with CVS :</para>
|
||||
the branch are easier with CVS:</para>
|
||||
|
||||
<screen>/usr/src&prompt.root; <userinput>cvs rtag -rRELENG_4 RELENG_4_4_BP src</userinput></screen>
|
||||
|
||||
<para>And then a new branch tag is created with : </para>
|
||||
<para>And then a new branch tag is created with:</para>
|
||||
|
||||
<screen>/usr/src&prompt.root; <userinput>cvs rtag -b -rRELENG_4_4_BP RELENG_4_4 src</userinput></screen>
|
||||
|
||||
|
@ -267,7 +267,7 @@
|
|||
|
||||
<para>Before the final release can be tagged, built, and
|
||||
released, the following files need to be modified to reflect
|
||||
the correct version of FreeBSD : </para>
|
||||
the correct version of FreeBSD:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
@ -443,7 +443,7 @@
|
|||
release build. Most of these variables are documented at the
|
||||
top of <filename>src/release/Makefile</filename>. The exact
|
||||
command used to build the official FreeBSD 4.4 (x86) release
|
||||
was : </para>
|
||||
was:</para>
|
||||
|
||||
<screen><command>make <literal>release CHROOTDIR=/local3/release \
|
||||
BUILDNAME=4.4-RELEASE \
|
||||
|
@ -863,7 +863,7 @@
|
|||
url="mailto:phk@FreeBSD.org">Poul-Henning Kamp</ulink>, and others
|
||||
who worked on the release engineering tools in the very early days
|
||||
of FreeBSD. This article was influenced by release engineering
|
||||
documents from the CSRG[14] , the NetBSD Project[11], and John
|
||||
documents from the CSRG[14], the NetBSD Project[11], and John
|
||||
Baldwin's proposed release engineering process notes[12].</para>
|
||||
</sect1>
|
||||
|
||||
|
|
|
@ -393,7 +393,7 @@ disk wd3 at wdc1 drive 1</programlisting>
|
|||
<literal>A-8</literal> indicates a 15 Mbits/second controller
|
||||
capable of handling 52 sectors/track. A <literal>D</literal>
|
||||
means a 15 Mbits/second controller that can also handle drives
|
||||
with > 36 sectors/track (also 52 ?).</para>
|
||||
with > 36 sectors/track (also 52?).</para>
|
||||
|
||||
<para>All variations should be capable of using 1:1 interleaving.
|
||||
Use 1:1, FreeBSD is fast enough to handle it.</para>
|
||||
|
@ -986,7 +986,7 @@ sd0(bt0:0:0): Direct-Access 1350MB (2766300 512 byte sectors)</screen>
|
|||
and, last but not least, have more capacity. You can imagine that
|
||||
the value reported by the drive when inquiring about the geometry
|
||||
now becomes suspect at best, and nearly always misleading. When
|
||||
asked for a geometry , it is nearly always better to supply the
|
||||
asked for a geometry, it is nearly always better to supply the
|
||||
geometry used by the BIOS, or <emphasis>if the BIOS is never going
|
||||
to know about this disk</emphasis>, (e.g. it is not a booting
|
||||
disk) to supply a fictitious geometry that is convenient.</para>
|
||||
|
|
|
@ -811,7 +811,7 @@
|
|||
|
||||
<para>This is what Page coloring does. Instead of assigning
|
||||
<emphasis>random</emphasis> physical pages to virtual addresses,
|
||||
which may result in non-optimal cache performance , Page coloring
|
||||
which may result in non-optimal cache performance, Page coloring
|
||||
assigns <emphasis>reasonably-contiguous</emphasis> physical pages
|
||||
to virtual addresses. Thus programs can be written under the
|
||||
assumption that the characteristics of the underlying hardware
|
||||
|
|
|
@ -68,7 +68,7 @@
|
|||
<para>In <filename>jail.c</filename>, the first thing I would
|
||||
note is the declaration of an important structure
|
||||
<literal>struct jail j</literal>; which was included from
|
||||
<filename>/usr/include/sys/jail.h</filename> .
|
||||
<filename>/usr/include/sys/jail.h</filename>.
|
||||
|
||||
<para>The definition of the jail structure is:</para>
|
||||
|
||||
|
@ -486,14 +486,14 @@ static int bpfopen(dev, flags, fmt, p)
|
|||
|
||||
<para>There are certain protocols which are very common, such as
|
||||
TCP, UDP, IP and ICMP. IP and ICMP are on the same level: the
|
||||
network layer 2 . There are certain precautions which are
|
||||
network layer 2. There are certain precautions which are
|
||||
taken in order to prevent a jailed process from binding a
|
||||
protocol to a certain port only if the <literal>nam</literal>
|
||||
parameter is set. nam is a pointer to a sockaddr structure,
|
||||
which describes the address on which to bind the service. A
|
||||
more exact definition is that sockaddr "may be used as a
|
||||
template for reffering to the identifying tag and length of
|
||||
each address"[2] . In the function in
|
||||
each address"[2]. In the function in
|
||||
<literal>pcbbind</literal>, <literal>sin</literal> is a
|
||||
pointer to a sockaddr.in structure, which contains the port,
|
||||
address, length and domain family of the socket which is to be
|
||||
|
|
|
@ -68,7 +68,7 @@
|
|||
<para>In <filename>jail.c</filename>, the first thing I would
|
||||
note is the declaration of an important structure
|
||||
<literal>struct jail j</literal>; which was included from
|
||||
<filename>/usr/include/sys/jail.h</filename> .
|
||||
<filename>/usr/include/sys/jail.h</filename>.
|
||||
|
||||
<para>The definition of the jail structure is:</para>
|
||||
|
||||
|
@ -486,14 +486,14 @@ static int bpfopen(dev, flags, fmt, p)
|
|||
|
||||
<para>There are certain protocols which are very common, such as
|
||||
TCP, UDP, IP and ICMP. IP and ICMP are on the same level: the
|
||||
network layer 2 . There are certain precautions which are
|
||||
network layer 2. There are certain precautions which are
|
||||
taken in order to prevent a jailed process from binding a
|
||||
protocol to a certain port only if the <literal>nam</literal>
|
||||
parameter is set. nam is a pointer to a sockaddr structure,
|
||||
which describes the address on which to bind the service. A
|
||||
more exact definition is that sockaddr "may be used as a
|
||||
template for reffering to the identifying tag and length of
|
||||
each address"[2] . In the function in
|
||||
each address"[2]. In the function in
|
||||
<literal>pcbbind</literal>, <literal>sin</literal> is a
|
||||
pointer to a sockaddr.in structure, which contains the port,
|
||||
address, length and domain family of the socket which is to be
|
||||
|
|
|
@ -5827,7 +5827,7 @@ C:\="DOS"</programlisting>
|
|||
URL="http://www.vmunix.com/mark/FreeBSD/ZIP-FAQ.html">
|
||||
Mark Mayo's ZIP FAQ</ulink>)</para>
|
||||
|
||||
<para>If it is a ZIP drive or a floppy , you have already got a DOS
|
||||
<para>If it is a ZIP drive or a floppy, you have already got a DOS
|
||||
filesystem on it, you can use a command like this:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>mount -t msdos /dev/fd0c /floppy</userinput></screen>
|
||||
|
|
|
@ -876,7 +876,7 @@ kern.maxfiles: 2088 -> 5000</screen>
|
|||
<para>The &man.tunefs.8; program can be used to fine-tune a
|
||||
filesystem. This program has many different options, but for
|
||||
now we are only concerned with toggling Soft Updates on and
|
||||
off, which is done by :</para>
|
||||
off, which is done by:</para>
|
||||
|
||||
<screen>&prompt.root; tunefs -n enable /filesystem
|
||||
&prompt.root; tunefs -n disable /filesystem</screen>
|
||||
|
|
|
@ -179,7 +179,7 @@
|
|||
|
||||
<orderedlist>
|
||||
<listitem>
|
||||
<para>Join the &a.current; and the &a.cvsall; . This is not
|
||||
<para>Join the &a.current; and the &a.cvsall;. This is not
|
||||
just a good idea, it is <emphasis>essential</emphasis>. If
|
||||
you are not on the <emphasis>&a.current;</emphasis>,
|
||||
you will not see the comments that people are
|
||||
|
@ -238,7 +238,7 @@ subscribe cvs-all</programlisting>
|
|||
customize the sample supfile above, and configure
|
||||
<link linkend="cvsup">cvsup</link> for your environment.
|
||||
If you want help doing this configuration,
|
||||
simply type : </para>
|
||||
simply type:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>pkg_add -f ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/packages/All/cvsupit-3.0.tgz</userinput></screen>
|
||||
|
||||
|
|
|
@ -1001,7 +1001,7 @@ scsibus1:
|
|||
<screen>&prompt.root; <userinput>burncd -f /dev/acd1c -s 12 data archive.tar.gz fixate</userinput></screen>
|
||||
|
||||
<para>In order to retrieve the data burned to such a CD, you
|
||||
must read data from the raw device node :</para>
|
||||
must read data from the raw device node:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>tar xzvf /dev/acd1c</userinput></screen>
|
||||
|
||||
|
|
|
@ -2768,7 +2768,7 @@ do so by typing: /stand/sysinstall .
|
|||
<para>Selecting <guibutton>[ No ]</guibutton> and pressing
|
||||
<keycap>Enter</keycap> will abort
|
||||
the installation so no changes will be made to your system. The
|
||||
following message will appear :</para>
|
||||
following message will appear:</para>
|
||||
|
||||
<screen> Message
|
||||
Installation complete with some errors. You may wish to scroll
|
||||
|
@ -3070,7 +3070,7 @@ use the current settings.
|
|||
|
||||
<para>To allow anonymous FTP, use the arrow keys to select
|
||||
<guibutton>[ Yes ]</guibutton> and press <keycap>Enter</keycap>.
|
||||
The following screens (or similar) will display :</para>
|
||||
The following screens (or similar) will display:</para>
|
||||
|
||||
<figure id="anon-ftp2">
|
||||
<title>Default Anonymous FTP Configuration</title>
|
||||
|
@ -3082,7 +3082,7 @@ use the current settings.
|
|||
</mediaobject>
|
||||
</figure>
|
||||
|
||||
<para>Pressing <keycap>F1</keycap> will display the help :</para>
|
||||
<para>Pressing <keycap>F1</keycap> will display the help:</para>
|
||||
|
||||
<screen>This screen allows you to configure the anonymous FTP user.
|
||||
|
||||
|
@ -3431,7 +3431,7 @@ To change any of these settings later, edit /etc/rc.conf
|
|||
interval, select <guimenuitem>Saver</guimenuitem> again. At the
|
||||
Screensaver Options menu, select <guimenuitem>Timeout</guimenuitem>
|
||||
using the arrow keys and press <keycap>Enter</keycap>. A pop-up
|
||||
menu will appear :</para>
|
||||
menu will appear:</para>
|
||||
|
||||
<figure id="saver-timeout">
|
||||
<title>Screensaver Timeout</title>
|
||||
|
@ -3880,7 +3880,7 @@ To change any of these settings later, edit /etc/rc.conf
|
|||
|
||||
<para>Verify all the settings once again and select
|
||||
<guibutton>Done</guibutton> and the following message will
|
||||
display :</para>
|
||||
display:</para>
|
||||
|
||||
<screen>If you've finished configuring everything press the
|
||||
Okay button to start the X server using the configuration
|
||||
|
@ -3936,7 +3936,7 @@ when you've finished.</screen>
|
|||
</procedure>
|
||||
|
||||
<para>Once the configuration is done, the installation program will
|
||||
need to create a link to the server :</para>
|
||||
need to create a link to the server:</para>
|
||||
|
||||
<screen> Do you want to create an 'X' link to the SVGA server?
|
||||
|
||||
|
@ -4096,7 +4096,7 @@ when you've finished.</screen>
|
|||
<para>You should add at least one user during the installation so
|
||||
that you can use the system without being logged in as root. The
|
||||
root partition is generally small and running applications as
|
||||
root can quickly fill it. A bigger danger is noted below :</para>
|
||||
root can quickly fill it. A bigger danger is noted below:</para>
|
||||
|
||||
<screen> User Confirmation Requested
|
||||
Would you like to add any initial user accounts to the system? Adding
|
||||
|
@ -4295,7 +4295,7 @@ when you've finished.</screen>
|
|||
|
||||
<para>Select <guibutton>[X Exit Install]</guibutton> with the arrow
|
||||
keys and press <keycap>Enter</keycap>. You will be asked to
|
||||
confirm exiting the installation :</para>
|
||||
confirm exiting the installation:</para>
|
||||
|
||||
<screen> User Confirmation Requested
|
||||
Are you sure you wish to exit? The system will reboot (be sure to
|
||||
|
@ -4333,7 +4333,7 @@ when you've finished.</screen>
|
|||
(rpratt, in this example). Avoid logging in as root except when
|
||||
necessary.</para>
|
||||
|
||||
<para>Typical boot messages :</para>
|
||||
<para>Typical boot messages:</para>
|
||||
|
||||
<screen>Copyright (c) 1992-2002 The FreeBSD Project.
|
||||
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
|
||||
|
|
|
@ -552,7 +552,7 @@ disco.example.com 7115-70839-20412</screen>
|
|||
|
||||
<step><para>Patch the
|
||||
<filename>usr/local/maple/bin/maple.system.type</filename>
|
||||
file with the following :</para>
|
||||
file with the following:</para>
|
||||
<programlisting> ----- snip ------------------
|
||||
*** maple.system.type.orig Sun Jul 8 16:35:33 2001
|
||||
--- maple.system.type Sun Jul 8 16:35:51 2001
|
||||
|
@ -633,8 +633,7 @@ exit 0
|
|||
|
||||
<listitem><para><command>lmgrd</command> is known to be very picky
|
||||
about the license file and to core dump if there are any
|
||||
problems. A correct license file should look like this
|
||||
:</para>
|
||||
problems. A correct license file should look like this:</para>
|
||||
|
||||
<programlisting># =======================================================
|
||||
# License File for UNIX Installations ("Pointer File")
|
||||
|
@ -699,7 +698,7 @@ FEATURE Maple maplelmg 2000.0831 permanent 1 XXXXXXXXXXXX \
|
|||
<para>If you want to run the intelligent agent, you will
|
||||
also need to install the Red Hat Tcl package:
|
||||
<filename>tcl-8.0.3-20.i386.rpm</filename>. The general command
|
||||
for installing packages with the official RPM port is :</para>
|
||||
for installing packages with the official RPM port is:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>rpm -i --ignoreos --root /compat/linux --dbpath /var/lib/rpm <replaceable>package</replaceable></userinput></screen>
|
||||
|
||||
|
@ -1575,7 +1574,7 @@ Shell: /bin/sh</programlisting>
|
|||
<title>Entries in /etc/services</title>
|
||||
|
||||
<para>SAP R/3 requires some entries in file
|
||||
<filename>/etc/services</filename> , which will not be set
|
||||
<filename>/etc/services</filename>, which will not be set
|
||||
correctly during installation under FreeBSD. Please add the
|
||||
following entries (you need at least those entries
|
||||
corresponding to the instance number - in this case,
|
||||
|
@ -1950,7 +1949,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
|
|||
|
||||
<para>Confirm all Screens with Enter until the software is
|
||||
installed, except that one has to deselect the
|
||||
<emphasis>Oracle On-Line Text Viewer</emphasis> , as this is
|
||||
<emphasis>Oracle On-Line Text Viewer</emphasis>, as this is
|
||||
not currently available for Linux. Oracle then wants to
|
||||
relink with <command>i386-glibc20-linux-gcc</command>
|
||||
instead of the available <command>gcc</command>,
|
||||
|
@ -1988,7 +1987,7 @@ options SEMUME=100 #number of UNDO keys</programlisting></para>
|
|||
<username>idsamd</username>
|
||||
(<sid>adm) and
|
||||
<username>oraids</username> (ora<sid>). They should now
|
||||
both have the files <filename>.profile</filename> ,
|
||||
both have the files <filename>.profile</filename>,
|
||||
<filename>.login</filename> and <filename>.cshrc</filename>
|
||||
which are all using <command>hostname</command>. In case the
|
||||
system's hostname is the fully qualified name, you need to
|
||||
|
|
|
@ -369,7 +369,7 @@ procmail: "|/usr/local/bin/procmail"</programlisting>
|
|||
<para>The aliases update matches the mailbox name on the left of
|
||||
the colon, and will expand it to the target(s) on the right. The
|
||||
first example simply expands the mailbox <username>root</username>
|
||||
to the mailbox <username>localuser</username> , which is then
|
||||
to the mailbox <username>localuser</username>, which is then
|
||||
looked up again in the aliases database. If no match is found,
|
||||
then the message is delivered to the local user
|
||||
<username>localuser</username>. The next example shows a mail
|
||||
|
@ -668,7 +668,7 @@ the DNS for <quote>customer.com</quote>.</programlisting>
|
|||
straight forward solution is to put your ISP's address in
|
||||
a relay-domains file at
|
||||
<filename>/etc/mail/relay-domains</filename>. A quick way
|
||||
to do this would be :</para>
|
||||
to do this would be:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>echo "your.isp.example.com" > /etc/mail/relay-domains</userinput></screen>
|
||||
|
||||
|
@ -680,7 +680,7 @@ the DNS for <quote>customer.com</quote>.</programlisting>
|
|||
is also very useful if you only have one or two email
|
||||
accounts setup. If there are a large number of addresses
|
||||
to add, you can simply open this file in your favorite
|
||||
text editor and then add the domains one per line :</para>
|
||||
text editor and then add the domains one per line:</para>
|
||||
|
||||
<programlisting>your.isp.example.com
|
||||
other.isp.example.net
|
||||
|
|
|
@ -86,7 +86,7 @@
|
|||
<title>Distributors</title>
|
||||
|
||||
<para>If you are a reseller and want to carry FreeBSD CDROM products,
|
||||
please contact a distributor :</para>
|
||||
please contact a distributor:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
|
|
@ -1082,7 +1082,7 @@ Receiving lsof_4.57D.freebsd.tar.gz (439860 bytes): 100%
|
|||
to a remote file server or local read-only CDROM media.
|
||||
If this is the case, then you should specify a different
|
||||
directory to be used for storing distfiles with the
|
||||
following command :</para>
|
||||
following command:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>make DISTDIR=<replaceable>/local/dir/with/write/permission</replaceable> install</userinput></screen>
|
||||
</answer>
|
||||
|
|
|
@ -377,7 +377,7 @@
|
|||
<para>Keys are rendered in <keycap>bold</keycap> to stand out from
|
||||
other text. Key combinations that are meant to be typed
|
||||
simultaneously are rendered with `<literal>+</literal>' between
|
||||
the keys, such as :</para>
|
||||
the keys, such as:</para>
|
||||
|
||||
<para>
|
||||
<keycombo action="simul">
|
||||
|
@ -388,7 +388,7 @@
|
|||
</para>
|
||||
|
||||
<para>Keys that are meant to be typed in sequence will be separated with
|
||||
commas, for example :</para>
|
||||
commas, for example:</para>
|
||||
|
||||
<para>
|
||||
<keycombo action="simul">
|
||||
|
|
|
@ -366,7 +366,7 @@
|
|||
|
||||
<programlisting>foobar:R9DT/Fa1/LV9U:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh</programlisting>
|
||||
|
||||
<para>Should be changed to this :</para>
|
||||
<para>Should be changed to this:</para>
|
||||
|
||||
<programlisting>foobar:*:1000:1000::0:0:Foo Bar:/home/foobar:/usr/local/bin/tcsh</programlisting>
|
||||
|
||||
|
|
|
@ -624,7 +624,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cuala1</screen>
|
|||
program.</para>
|
||||
|
||||
<para>Thus, to configure terminals for your FreeBSD system the
|
||||
following steps should be taken as <username>root</username> :</para>
|
||||
following steps should be taken as <username>root</username>:</para>
|
||||
|
||||
<procedure>
|
||||
<step>
|
||||
|
@ -809,7 +809,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<para>After making the necessary changes to the
|
||||
<filename>/etc/ttys</filename> file you should send a SIGHUP
|
||||
(hangup) signal to the <command>init</command> process to
|
||||
force it to re-read its configuration file. For example :</para>
|
||||
force it to re-read its configuration file. For example:</para>
|
||||
|
||||
<screen>&prompt.root; <userinput>kill -HUP 1</userinput></screen>
|
||||
|
||||
|
@ -956,7 +956,7 @@ ttyd5 "/usr/libexec/getty std.19200" vt100 on insecure
|
|||
<para>If you are using an external modem, then you will of
|
||||
course need the proper cable. A standard RS-232C serial
|
||||
cable should suffice as long as all of the normal signals
|
||||
are wired :</para>
|
||||
are wired:</para>
|
||||
|
||||
<itemizedlist>
|
||||
<listitem>
|
||||
|
@ -1313,7 +1313,7 @@ vq|VH57600|Very High Speed Modem at 57600,8-bit:\
|
|||
<varname>crtscts</varname> on serial port #1's
|
||||
(<devicename>COM2:</devicename>) dial-in and dial-out initialization
|
||||
devices, the following lines could be added to
|
||||
<filename>/etc/rc.serial</filename> :</para>
|
||||
<filename>/etc/rc.serial</filename>:</para>
|
||||
<programlisting># Serial port initial configuration
|
||||
stty -f /dev/ttyid1 crtscts
|
||||
stty -f /dev/cuai01 crtscts</programlisting>
|
||||
|
|
Loading…
Reference in a new issue