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

accross -> across.

Browse source 
& -> &.
Remove references to imaginary freebsd-policy mailing list.
Submitted by:	John Mulhollen <JMULHOLLEN@gcwf.com>
		Thomas Graichen <graichen@axp5.physik.fu-berlin.de>
This commit is contained in:
John Fieber 1996-07-12 16:18:50 +00:00
parent 9c304646ae
commit a8de64f2ae
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=422
2 changed files with 8 additions and 17 deletions
Download patch file Download diff file Expand all files Collapse all files

11
handbook/eresources.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: eresources.sgml,v 1.24 1996-05-22 19:48:59 jkh Exp $ -->
<!-- $Id: eresources.sgml,v 1.25 1996-07-12 16:18:49 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt>
@ -53,7 +53,6 @@ freebsd-chat Non-technical items related to the FreeBSD community
freebsd-current Discussion concerning the use of FreeBSD-current
freebsd-stable Discussion concerning the use of FreeBSD-stable
freebsd-isp Issues for Internet Service Providers using FreeBSD
freebsd-policy General policy issues and suggestions
freebsd-questions User questions
</verb>
@ -252,14 +251,6 @@ development and their support within FreeBSD
platforms</em><newline> Cross-platform freebsd issues, general
discussion and proposals for non-Intel FreeBSD ports.
<tag/FREEBSD-POLICY/ <em>Policy issues and
suggestions</em><newline> This is a forum for policy discussions
related to FreeBSD. This includes where FreeBSD is going, how to
set up a consortium, whether or not and how to make FreeBSD pay
for itself, how to attract more users, and so on. When a topic
relates directly to FreeBSD but has little or no technical
content then it should be sent to this list.
<tag/FREEBSD-PORTS/ <em>Discussion of "ports"</em><newline>
Discussions concerning FreeBSD's "ports collection" (/usr/ports), proposed
ports, modifications to ports collection infrastructure and general

14
handbook/hw.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: hw.sgml,v 1.30 1996-07-03 21:22:16 jfieber Exp $ -->
<!-- $Id: hw.sgml,v 1.31 1996-07-12 16:18:50 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -840,7 +840,7 @@ an exabyte 2 GB 8mm tape drive. 8mm drives are reliable,
convienent and quiet. Cartidges are inexpensive and small (4.8 x
3.3 x 0.6 inches; 122 x 84 x 15 mm). One downside of 8mm tape is
relatively short head and tape life due to the high rate of
relative motion of the tape accross the heads.
relative motion of the tape across the heads.
<!--spec-->
<p>Data thruput ranges from ~250kB/s to ~500kB/s. Data
@ -857,7 +857,7 @@ heads are positioned at an angle to the media (approximately 6
degrees). The tape wraps around 270 degrees of the spool that
holds the heads. The spool spins while the tape slides over the
spool. The result is a high density of data and closely packed
tracks that angle accross the tape from one edge to the other.
tracks that angle across the tape from one edge to the other.
<sect3><heading><label id="hw:storage:tapebackups:qic">
@ -975,7 +975,7 @@ overridden on the command line to utilize the capacity of current
tape drives.
<p><tt>rdump(8)</tt> and <tt>rrestore(8)</tt> backup data
accross the network to a tape drive attached to another computer.
aross the network to a tape drive attached to another computer.
Both programs rely upon <tt>rcmd(3)</tt> and <tt>ruserok(3)</tt>
to access the remote tape drive. Therefore, the user performing
the backup must have <tt>rhosts</tt> access to the remote
@ -983,7 +983,7 @@ computer. The arguments to <tt>rdump(8)</tt> and
<tt>rrestore(8)</tt> must suitable to use on the remote computer.
(e.g. When <tt>rdump</tt>'ing from a FreeBSD computer to an
Exabyte tape drive connected to a Sun called komodo, use: <tt>/sbin/rdump
0dsbfu 54000 13000 126 komodo:/dev/nrst8 /dev/rsd0a 2>&1</tt>)
0dsbfu 54000 13000 126 komodo:/dev/nrst8 /dev/rsd0a 2>&amp;1</tt>)
Beware: there are security implications to allowing
<tt>rhosts</tt> commands. Evaluate your situation carefully.
@ -999,7 +999,7 @@ that are available from <tt>cpio(1)</tt>, but <tt>tar(1)</tt>
does not require the unusual command pipeline that
<tt>cpio(1)</tt> uses.
<p><tt>tar(1)</tt> does not support backups accross the
<p><tt>tar(1)</tt> does not support backups across the
network. You can use a pipeline and <tt>rsh(1)</tt> to send the
data to a remote tape drive. (XXX add an example command)
@ -1013,7 +1013,7 @@ This last feature makes <tt>cpio(1)</tt> and excellent choice for
installation media. <tt>cpio(1)</tt> does not know how to walk
the directory tree and a list of files must be provided thru <tt>STDIN</tt>.
<p><tt>cpio(1)</tt> does not support backups accross the
<p><tt>cpio(1)</tt> does not support backups across the
network. You can use a pipeline and <tt>rsh(1)</tt> to send the
data to a remote tape drive. (XXX add an example command)