This fortune brought to you by:
$FreeBSD: src/games/fortune/datfiles/fortunes2,v 1.17.2.8 2002/10/19 05:10:15 fanf Exp $
-$DragonFly: src/games/fortune/datfiles/fortunes2,v 1.4 2005/08/09 22:55:04 corecode Exp $
+$DragonFly: src/games/fortune/datfiles/fortunes2,v 1.5 2007/02/19 11:10:11 swildner Exp $
%
=======================================================================
A firefly is not a fly, but a beetle.
A giant panda bear is really a member of the racoon family.
A black panther is really a leopard that has a solid black coat
- rather then a spotted one.
+ rather than a spotted one.
Peanuts are not really nuts. The majority of nuts grow on trees
while peanuts grow underground. They are classified as a
legume-part of the pea family.
.\"
.\" @(#)mmap.2 8.4 (Berkeley) 5/11/95
.\" $FreeBSD: src/lib/libc/sys/mmap.2,v 1.22.2.12 2002/02/27 03:40:13 dd Exp $
-.\" $DragonFly: src/lib/libc/sys/mmap.2,v 1.7 2007/01/08 03:33:34 dillon Exp $
+.\" $DragonFly: src/lib/libc/sys/mmap.2,v 1.8 2007/02/19 11:10:12 swildner Exp $
.\"
.Dd December 11, 2006
.Dt MMAP 2
Region is not included in a core file.
.It Dv MAP_NOSYNC
Causes data dirtied via this VM map to be flushed to physical media
-only when necessary (usually by the pager) rather then gratuitously.
+only when necessary (usually by the pager) rather than gratuitously.
Typically this prevents the update daemons from flushing pages dirtied
through such maps and thus allows efficient sharing of memory across
unassociated processes using a file-backed shared memory map. Without
to implement a file-based shared memory store.
It is recommended that you create the backing store by
.Fn write Ns ing
-zero's to the backing file rather then
+zero's to the backing file rather than
.Fn ftruncate Ns ing
it.
You can test file fragmentation by observing the KB/t (kilobytes per
.Bx
implements a coherent filesystem buffer cache. However, it may be
used to associate dirty VM pages with filesystem buffers and thus cause
-them to be flushed to physical media sooner rather then later.
+them to be flushed to physical media sooner rather than later.
.It Dv MAP_PRIVATE
Modifications are private.
.It Dv MAP_SHARED
.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.\" $DragonFly: src/sbin/jscan/jscan.8,v 1.11 2006/03/27 16:45:44 swildner Exp $
+.\" $DragonFly: src/sbin/jscan/jscan.8,v 1.12 2007/02/19 11:10:12 swildner Exp $
.\"
.Dd March 6, 2005
.Dt JSCAN 8
.It Fl f
.Nm
will sleep for 5 seconds and loop when it hits EOF on file or prefix
-set input rather then exit. This option is typically used when running
+set input rather than exit. This option is typically used when running
on an input file or prefix set which is live (being written to by
another
.Nm
NOTE: If
you are generating a mirror with the same command via
.Fl m ,
-and the journaling data input is a stream rather then a file or prefix
+and the journaling data input is a stream rather than a file or prefix
set, you must use
.Fl w/W
if you want the mirror to be restartable. This is because while we can
If
.Fl w/W
is not specified then neither the mirroring or output modes will fork. Under
-these conditions, if the input is a stream rather then a file
+these conditions, if the input is a stream rather than a file
.Nm
will be forced to buffer meta-transactions (for mirroring) entirely in
memory, which could present a serious problem since a single meta-transaction
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD: src/share/man/man4/ccd.4,v 1.11.2.8 2001/12/17 11:30:11 ru Exp $
-.\" $DragonFly: src/share/man/man4/ccd.4,v 1.4 2006/07/22 23:52:23 swildner Exp $
+.\" $DragonFly: src/share/man/man4/ccd.4,v 1.5 2007/02/19 11:10:11 swildner Exp $
.\"
.Dd August 9, 1995
.Dt CCD 4
the driver will automatically attempt to read the same sector from the
other side of the mirror. Currently
.Nm
-uses a duel seek zone model to optimize reads for a multi-tasking load
-rather then a sequential load.
+uses a dual seek zone model to optimize reads for a multi-tasking load
+rather than a sequential load.
.Pp
In an event of a disk
failure, you can use
.\" the source tree.
.\"
.\" $FreeBSD: src/share/man/man7/firewall.7,v 1.1.2.8 2003/04/29 07:57:22 brueffer Exp $
-.\" $DragonFly: src/share/man/man7/firewall.7,v 1.8 2006/05/21 14:15:05 swildner Exp $
+.\" $DragonFly: src/share/man/man7/firewall.7,v 1.9 2007/02/19 11:10:11 swildner Exp $
.\"
.Dd May 26, 2001
.Dt FIREWALL 7
.Pp
Constructing a firewall may appear to be trivial, but most people
get them wrong. The most common mistake is to create an exclusive
-firewall rather then an inclusive firewall. An exclusive firewall
+firewall rather than an inclusive firewall. An exclusive firewall
allows all packets through except for those matching a set of rules.
An inclusive firewall allows only packets matching the rulset
through. Inclusive firewalls are much, much safer then exclusive
.Sy auth
service in an attempt to authenticate the user making a connection.
Auth is rather dangerous but the proper implementation is to return
-a TCP reset for the connection attempt rather then simply blackholing
+a TCP reset for the connection attempt rather than simply blackholing
the packet. We cover these and other quirks involved with constructing
a firewall in the sample firewall section below.
.Sh IPFW KERNEL CONFIGURATION
We've mentioned multi-homing hosts and binding services to internal or
external addresses but we haven't really explained it. When you have a
host with multiple IP addresses assigned to it, you can bind services run
-on that host to specific IPs or interfaces rather then all IPs. Take
+on that host to specific IPs or interfaces rather than all IPs. Take
the firewall machine for example: With three interfaces
and two exposed IP addresses
on one of those interfaces, the firewall machine is known by 5 different
.\" the source tree.
.\"
.\" $FreeBSD: src/share/man/man7/security.7,v 1.13.2.11 2002/04/13 02:04:44 keramida Exp $
-.\" $DragonFly: src/share/man/man7/security.7,v 1.7 2006/11/17 23:23:05 swildner Exp $
+.\" $DragonFly: src/share/man/man7/security.7,v 1.8 2007/02/19 11:10:11 swildner Exp $
.\"
.Dd September 18, 1999
.Dt SECURITY 7
last layer of your security onion is perhaps the most important - detection.
The rest of your security is pretty much useless (or, worse, presents you with
a false sense of safety) if you cannot detect potential incursions. Half
-the job of the onion is to slow down the attacker rather then stop him
+the job of the onion is to slow down the attacker rather than stop him
in order to give the detection side of the equation a chance to catch him in
the act.
.Pp
and
.Pa /usr
.Pp
-When using ssh rather then NFS, writing the security script is much more
+When using ssh rather than NFS, writing the security script is much more
difficult. You essentially have to
.Pa scp
the scripts to the client box in order to run them, making them visible, and
.\" the source tree.
.\"
.\" $FreeBSD: src/share/man/man7/tuning.7,v 1.1.2.30 2002/12/17 19:32:08 dillon Exp $
-.\" $DragonFly: src/share/man/man7/tuning.7,v 1.9 2006/10/15 00:04:45 swildner Exp $
+.\" $DragonFly: src/share/man/man7/tuning.7,v 1.10 2007/02/19 11:10:11 swildner Exp $
.\"
.Dd May 11, 2006
.Dt TUNING 7
to the pageout daemon.
Do not turn this option on unless you need it,
because the tradeoff you are making is to essentially pre-page memory sooner
-rather then later, eating more swap and disk bandwidth.
+rather than later, eating more swap and disk bandwidth.
In a small system
this option will have a detrimental effect but in a large system that is
already doing moderate paging this option allows the VM system to stage
we describe a firewall protecting internal hosts with a topology where
the externally visible hosts are not routed through it.
Use 100BaseT rather
-than 10BaseT, or use 1000BaseT rather then 100BaseT, depending on your needs.
+than 10BaseT, or use 1000BaseT rather than 100BaseT, depending on your needs.
Most bottlenecks occur at the WAN link (e.g.\&
modem, T1, DSL, whatever).
If expanding the link is not an option it may be possible to use the
.\" SUCH DAMAGE.
.\"
.\" $FreeBSD: src/usr.bin/ktrdump/ktrdump.8,v 1.7 2005/03/08 06:58:56 hmp Exp $
-.\" $DragonFly: src/usr.bin/ktrdump/ktrdump.8,v 1.7 2006/03/27 16:45:44 swildner Exp $
+.\" $DragonFly: src/usr.bin/ktrdump/ktrdump.8,v 1.8 2007/02/19 11:10:12 swildner Exp $
.\"
.Dd May 5, 2004
.Dt KTRDUMP 8
normally tries to translate the caller fields and (when easily parsed)
trace arguments into symbols. This option forces hex values to be
displayed instead. This option will also cause relative timestamps to
-be displayed as TSC timestamps rather then converted to microseconds.
+be displayed as TSC timestamps rather than converted to microseconds.
.It Fl p
Print the trace data.
.It Fl q
.\"
.\" From: @(#)install.1 8.1 (Berkeley) 6/6/93
.\" $FreeBSD: src/usr.bin/xinstall/install.1,v 1.16.2.9 2002/07/01 21:01:23 des Exp $
-.\" $DragonFly: src/usr.bin/xinstall/install.1,v 1.4 2006/02/17 19:39:17 swildner Exp $
+.\" $DragonFly: src/usr.bin/xinstall/install.1,v 1.5 2007/02/19 11:10:12 swildner Exp $
.\"
.Dd May 7, 2001
.Dt INSTALL 1
Specify the location of the /etc directory containing the group and password
files. The default is "/etc". If an alternative directory is specified
group and username lookups will be made from the alternative group and
-password files rather then the system group and password files.
+password files rather than the system group and password files.
.It Fl B Ar suffix
Use
.Ar suffix
.\"
.\" @(#)vnconfig.8 8.1 (Berkeley) 6/5/93
.\" $FreeBSD: src/usr.sbin/vnconfig/vnconfig.8,v 1.14.2.8 2003/01/04 22:35:53 keramida Exp $
-.\" $DragonFly: src/usr.sbin/vnconfig/vnconfig.8,v 1.3 2006/02/10 19:01:10 swildner Exp $
+.\" $DragonFly: src/usr.sbin/vnconfig/vnconfig.8,v 1.4 2007/02/19 11:10:12 swildner Exp $
.\"
.Dd July 8, 1993
.Dt VNCONFIG 8
the underlying backing store (for example, when you remove a large file).
Use this option if you wish to avoid long-term fragmentation of the backing
store. Also note that when this option is used, the initial contents of the
-backing store may contain garbage rather then zeros. It may even be possible to
+backing store may contain garbage rather than zeros. It may even be possible to
recover the prior contents of a swap-backed VN across a reboot if the VN device
is configured before any swap is allocated by the system.
.It Ar follow
can partition your VN disk and, for example, create a filesystem on one of
the partitions. If you are using a file as backing store, it may be possible
to recover your VN disk after a crash by vnconfig'ing the same file again
-and using the VN configuration already stored in the file rather then
+and using the VN configuration already stored in the file rather than
relabeling and recreating the filesystem. It is even possible to fsck the
VN partitions that previously contained filesystems.
.Pp
uqs's projects / games.git / commitdiff