mirror of
https://git.FreeBSD.org/src.git
synced 2024-12-03 09:00:21 +00:00
Fix some more spelling errors.
This commit is contained in:
parent
58b5a92dd6
commit
d45d3fa224
Notes:
svn2git
2020-12-20 02:59:44 +00:00
svn path=/head/; revision=13794
@ -18,7 +18,7 @@ Fuchsia:Fast.
|
||||
Gardenia:Secret, untold love.
|
||||
Honeysuckle:Bonds of love.
|
||||
Ivy:Friendship, fidelity, marriage.
|
||||
Jasmine:Amiablity, transports of joy, sensuality.
|
||||
Jasmine:Amiability, transports of joy, sensuality.
|
||||
Leaves (dead):Melancholy.
|
||||
Lilac:Youthful innocence.
|
||||
Lilly of the valley:Return of happiness.
|
||||
@ -39,7 +39,7 @@ Rose, thornless, any color:Early attachment.
|
||||
Rose, white:I am worthy of you.
|
||||
Rose, yellow:Decrease of love, rise of jealousy.
|
||||
Rosebud, white:Girlhood, and a heart ignorant of love.
|
||||
Rosemary:Rememberance.
|
||||
Rosemary:Remembrance.
|
||||
Sunflower:Haughtiness.
|
||||
Tulip, red:Declaration of love.
|
||||
Tulip, yellow:Hopeless love.
|
||||
|
@ -1,58 +1,58 @@
|
||||
# A bit of background is needed here.
|
||||
#
|
||||
# - nahanni is the name of my machine on my local ethernet. My local
|
||||
# - nahanni is the name of my machine on my local Ethernet. My local
|
||||
# network is a subnet of a class C network. This subnet has 29 bits for
|
||||
# for the network address and 3 bits for the host address. Consequently,
|
||||
# "nahanni/29" matches anything on my local network.
|
||||
#
|
||||
# - avalon is a (pseudonym) for a machine out on the internet that I trust
|
||||
# - avalon is a (pseudonym) for a machine out on the interned that I trust
|
||||
# completely.
|
||||
#
|
||||
# - zona is the name of my end of the ppp link to my old place of work.
|
||||
# - zona is the name of my end of the PPP link to my old place of work.
|
||||
# This name corresponds to an IP address on their class C network.
|
||||
# Consequently, "zona/24" matches any IP address on their network.
|
||||
#
|
||||
# - xnahanni is my end of my ppp link to the university (i.e. the Internet).
|
||||
# - xnahanni is my end of my PPP link to the university (i.e. the Internet).
|
||||
#
|
||||
# - dab-nahanni is my end of the ppp link to my new place of work. They
|
||||
# - dab-nahanni is my end of the PPP link to my new place of work. They
|
||||
# have a class B network so "dab-nahanni/16" matches any IP address on
|
||||
# their network.
|
||||
|
||||
# Start from scratch.
|
||||
|
||||
ipfirewall flush
|
||||
ipfw flush
|
||||
|
||||
# Basic accept filters to provide local sanity.
|
||||
# These are the IP addresses of the interfaces on my local machine.
|
||||
# The first is an ethernet interface. The rest are ppp interfaces.
|
||||
# The first is an Ethernet interface. The rest are PPP interfaces.
|
||||
|
||||
ipfirewall addb accept all from nahanni to 0/0
|
||||
ipfirewall addb accept all from xnahanni to 0/0
|
||||
# handled below: ipfirewall addb accept all from zona to 0/0
|
||||
# handled below: ipfirewall addb accept all from dab-nahanni to 0/0
|
||||
ipfw addf accept all from nahanni to 0/0
|
||||
ipfw addf accept all from xnahanni to 0/0
|
||||
# handled below: ipfw addf accept all from zona to 0/0
|
||||
# handled below: ipfw addf accept all from dab-nahanni to 0/0
|
||||
|
||||
# Trust my local network.
|
||||
|
||||
ipfirewall addb accept all from nahanni/29 to 0/0
|
||||
ipfw addf accept all from nahanni/29 to 0/0
|
||||
|
||||
# Allow anything from avalon.
|
||||
|
||||
ipfirewall addb accept all from avalon to 0/0
|
||||
ipfw addf accept all from avalon to 0/0
|
||||
|
||||
# Allow anything from our old work (they have a class C network so /24 is appropriate).
|
||||
# This also allows anything from zona (our end of the work ppp link).
|
||||
# This also allows anything from zona (our end of the work PPP link).
|
||||
|
||||
ipfirewall addb accept all from zona/24 to 0/0
|
||||
ipfw addf accept all from zona/24 to 0/0
|
||||
|
||||
# Allow anything from the new work (and from our end of the ppp link to the
|
||||
# Allow anything from the new work (and from our end of the PPP link to the
|
||||
# new place of work).
|
||||
|
||||
ipfirewall addb accept all from dab-nahanni/16 to 0/0
|
||||
ipfw addf accept all from dab-nahanni/16 to 0/0
|
||||
|
||||
# Allow me to contact any external UDP service and others to contact a few
|
||||
# of my special udp services.
|
||||
|
||||
ipfirewall addb accept udp from 0/0 to 0/0 900:5000 domain bootp talk ntalk route
|
||||
ipfw addf accept udp from 0/0 to 0/0 900:5000 domain bootp talk ntalk route
|
||||
|
||||
# Allow me to contact other services available on untrusted hosts.
|
||||
# This one is a bit tricky. We allow packets from any foreign port number
|
||||
@ -70,12 +70,12 @@ ipfirewall addb accept udp from 0/0 to 0/0 900:5000 domain bootp talk ntalk rout
|
||||
# allowing outsiders to connect to services in this range doesn't constitute
|
||||
# a security hole.
|
||||
|
||||
ipfirewall addb accept tcp from 0/0 to 0/0 900:5000
|
||||
ipfw addf accept tcp from 0/0 to 0/0 900:5000
|
||||
|
||||
# Allow others to contact X-servers on my local network.
|
||||
# Depend on xhosts to protect things.
|
||||
|
||||
ipfirewall addb accept tcp from 0/0 to nahanni/29 6000
|
||||
ipfw addf accept tcp from 0/0 to nahanni/29 6000
|
||||
|
||||
# Allow others to connect to a few basic services.
|
||||
# We don't actually run the auth service. Allowing it means that others
|
||||
@ -87,8 +87,8 @@ ipfirewall addb accept tcp from 0/0 to nahanni/29 6000
|
||||
# via the Internet but I receive my e-mail via uucp. If you get your e-mail
|
||||
# via the Internet then you'll have to add smtp to the list of ports to allow.
|
||||
|
||||
ipfirewall addb accept tcp from 0/0 to 0/0 daytime time nameserver auth
|
||||
ipfw addf accept tcp from 0/0 to 0/0 daytime time nameserver auth
|
||||
|
||||
# Allow icmp stuff from anywhere (this isn't described in the README - sorry).
|
||||
|
||||
ipfirewall addb accept icmp from 0/0 to 0/0
|
||||
ipfw addf accept icmp from 0/0 to 0/0
|
||||
|
@ -3,16 +3,16 @@
|
||||
# Default settings...They deny anybody , which connected to our
|
||||
# PPP lines,to access any host on our development network:
|
||||
# 192.114.207.*
|
||||
ipfirewall addf deny all from 192.114.201.231 to 192.114.208.0/24
|
||||
ipfirewall addf deny all from 192.114.201.232 to 192.114.208.0/24
|
||||
ipfw addf deny all from 192.114.201.231 to 192.114.208.0/24
|
||||
ipfw addf deny all from 192.114.201.232 to 192.114.208.0/24
|
||||
.....
|
||||
ipfirewall addf deny all from 192.114.201.238 to 192.114.208.0/24
|
||||
ipfw addf deny all from 192.114.201.238 to 192.114.208.0/24
|
||||
# VIP Login: this option executes when user VIP enters the system.
|
||||
# His IP is $VIPIP,which is one of our dial-up lines,for example
|
||||
# 192.114.201.233
|
||||
ipfirewall delf deny all from $VIPIP to 192.114.208.0/24
|
||||
ipfw delf deny all from $VIPIP to 192.114.208.0/24
|
||||
|
||||
# VIP Logout: the guy leaves the system...
|
||||
ipfirewall addf deny all from $VIPIP to 192.114.208.0/24
|
||||
ipfw addf deny all from $VIPIP to 192.114.208.0/24
|
||||
|
||||
#Thats all folks...
|
||||
|
@ -47,7 +47,7 @@ quite simple.
|
||||
|
||||
<p>
|
||||
Here are examples of things that you'll be using in the source. First,
|
||||
let's decend into a subsection:
|
||||
let's descend into a subsection:
|
||||
|
||||
<sect1>This is a subsection
|
||||
|
||||
|
@ -35,7 +35,7 @@ replacement files for use by Linux documentation.
|
||||
|
||||
<tt/linuxdoc-sgml/ is not meant to be a general document-processing system.
|
||||
Although it can be used for documents of many types, I have tailored it for
|
||||
use by the Linux documentors in producing HOWTOs, FAQs, and (later) the
|
||||
use by the Linux documenters in producing HOWTOs, FAQs, and (later) the
|
||||
Linux Documentation Project manuals. Therefore, I have tweaked features
|
||||
into and out of the system for this purpose. If you see a lack of generality
|
||||
in the system, that is the reason. There's nothing binding <tt/linuxdoc-sgml/
|
||||
@ -75,7 +75,7 @@ types.
|
||||
|
||||
The DTD specifies the names of ``elements'' within the document. An element
|
||||
is just a bit of structure---like a section, a subsection, a paragraph,
|
||||
or even something smaller like <em/emphasised text/. Unlike LaTeX, however,
|
||||
or even something smaller like <em/emphasized text/. Unlike LaTeX, however,
|
||||
these elements are not in any way intrinsic to SGML itself. The
|
||||
<tt/linuxdoc-sgml/ DTD happens to define elements that look a lot like
|
||||
their LaTeX counterparts---you have sections, subsections, verbatim
|
||||
@ -453,7 +453,7 @@ as so:
|
||||
Here is some example text.
|
||||
&etago;verb>&etago;tscreen>
|
||||
</verb></tscreen>
|
||||
<tt/tscreen/ is an envionment that simply indents the text and sets the
|
||||
<tt/tscreen/ is an environment that simply indents the text and sets the
|
||||
sets the default font to <tt/tt/. This makes examples look much nicer, both
|
||||
in the LaTeX and plain ASCII versions. You can use <tt/tscreen/
|
||||
without <tt/verb/, however, if you use any special characters in your
|
||||
@ -590,7 +590,7 @@ expression:
|
||||
<tscreen><verb>
|
||||
See section <ref id="sec-intro" name="Introduction"> for an introduction.
|
||||
</verb></tscreen>
|
||||
This will replace the <tt/ref/ tag with the section number labelled
|
||||
This will replace the <tt/ref/ tag with the section number labeled
|
||||
as <tt/sec-intro/. The <tt/name/ argument to <tt/ref/ is necessary for
|
||||
<tt/nroff/ and HTML translations (at the moment). The <tt/nroff/
|
||||
macro set used by Linuxdoc-SGML does not currently support cross-references,
|
||||
@ -729,6 +729,6 @@ modify your version of the DTD or replacement files to get other features
|
||||
in the system. We all must use the same DTD and replacement files or
|
||||
this whole system will break down. If you find bugs in it, or have suggestions
|
||||
for how we can change thing or add/modify features, let me know. I'll be
|
||||
more than happy to accomodate you.
|
||||
more than happy to accommodate you.
|
||||
|
||||
</article>
|
||||
|
Loading…
Reference in New Issue
Block a user