hardenedbsd/HardenedBSD
1
0
Fork 0
mirror of https://git.hardenedbsd.org/hardenedbsd/HardenedBSD.git synced 2025-01-01 00:18:15 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fix more typos to be a good example.

Browse Source 
Found by:	codespell
This commit is contained in:
Ulrich Spörlein 2011-05-22 14:23:48 +00:00
parent bf2fe08eea
commit 5665fe6b21
8 changed files with 139 additions and 143 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
share/examples/diskless/README.TEMPLATING
View File

@ -136,7 +136,7 @@ be useful to set up clients and server for diskless boot.
should never be overwritten by the templating copy.
TYPICAL CUSTOMIZED CONFIGRATION SOFTLINKS
TYPICAL CUSTOMIZED CONFIGURATION SOFTLINKS
The following files typically need to be turned into softlinks
to /conf/ME/<filename>:
@ -261,9 +261,9 @@ be useful to set up clients and server for diskless boot.
identity.pub
WHEN INITIALLY CONVERTING A TARGET MACHINE TO USE TEMPLATING, ALWAYS
MAKE A FULL BACKUP OF THE TARGET MACHINE FIRST! You may accidently delete
files on the target during the conversion due to forgetting to enter
items into appropriate .cpignore files on the source.
MAKE A FULL BACKUP OF THE TARGET MACHINE FIRST! You may accidentally
delete files on the target during the conversion due to forgetting to
enter items into appropriate .cpignore files on the source.
SECURITY CONSIDERATIONS WITH NFS ROOT EXPORT FROM TEMPLATE MACHINE
SECURITY CONSIDERATIONS WITH NFS USR EXPORT FROM TEMPLATE MACHINE

2
share/examples/drivers/make_device_driver.sh
View File

@ -485,7 +485,7 @@ ${1}_isa_probe (device_t device)
/*rid*/0, membase, memsize);
/*
* We found one, return non-positive numbers..
* Return -N if we cant handle it, but not well.
* Return -N if we can't handle it, but not well.
* Return -2 if we would LIKE the device.
* Return -1 if we want it a lot.
* Return 0 if we MUST get the device.

2
share/examples/netgraph/ether.bridge
View File

@ -40,7 +40,7 @@ BRIDGE_NAME="bnet0"
# machine as well then set ${LOCAL_IFACES} as well (they may also be
# listed in ${BRIDGE_IFACES}). Of course, any ${LOCAL_IFACE} must
# be ifconfig(8)ured separately. If you don't want a ${LOCAL_IFACE}
# then assign it the emtpy string.
# then assign it the empty string.
BRIDGE_IFACES="de0 fxp0 fxp1"
LOCAL_IFACES="fxp0 fxp1"

8
share/examples/netgraph/frame_relay
View File

@ -13,13 +13,13 @@ ngctl mkpeer ${CARD}: frame_relay rawdata downstream
# Link management protocol node.
ngctl mkpeer ${CARD}:rawdata lmi dlci0 auto0
# Also attach dlci 1023, as it needs both to try autoconfiguring.
# Also attach dlci 1023, as it needs both to try auto-configuring.
# The Link management protocol is now alive and probing..
ngctl connect ${CARD}:rawdata ${CARD}:rawdata.dlci0 dlci1023 auto1023
# Attach the DLCI(channel) the Telco has assigned you to
# a node to hadle whatever protocol encapsulation your peer
# is using. In this case rfc1490 encapsulation.
# a node to handle whatever protocol encapsulation your peer
# is using. In this case RFC1490 encapsulation.
ngctl mkpeer ${CARD}:rawdata rfc1490 dlci${DLCI} downstream
@ -34,7 +34,7 @@ ngctl mkpeer ${CARD}:rawdata.dlci${DLCI} iface inet inet
# Then use ifconfig on interface ng0 as usual
# A variant on this whole set might use the 'name' command to make it more
# readable. but it doesn't work if you have multiple lines or dlcis
# readable. But it doesn't work if you have multiple lines or dlcis
# e.g.
# ngctl mkpeer ${CARD}: frame_relay rawdata downstream
# ngctl name ${CARD}:rawdata mux

4
share/examples/netgraph/ngctl
View File

@ -46,7 +46,7 @@
# Note that we used ngctl's ``name'' command to do this. However,
# the following manually constructed netgraph message would have
# acomplished the exact same thing:
# accomplished the exact same thing:
+ msg foo name { name="fred" }
@ -85,7 +85,7 @@
# As soon as we sent the message, we got back a response. Here
# ngctl is telling us that it received a control message with the
# NGF_RESP (response) flag set, the reponse was to a prior ``getname''
# NGF_RESP (response) flag set, the response was to a prior ``getname''
# control message, that the originator was the node addressable
# as ``fred:''. The message arguments field is then displayed to
# us in its ASCII form. In this case, what we get back is a struct

2
share/examples/netgraph/raw
View File

@ -6,7 +6,7 @@
CARD=sr0
# create an interface "ng0" and attach it to the sync port.
# The packets had jolly well better be ip because we are not discriminating.
# The packets had jolly well better be IP because we are not discriminating.
ngctl mkpeer ${CARD}: iface rawdata inet
# if ng0 already exists, use a CONNECT command instead of a mkpeer. e.g.

21
share/examples/netgraph/virtual.chain
View File

@ -14,7 +14,6 @@
#
# $FreeBSD$
#
#
# This script creates and connects n router like nodes. Complex wide
# area topologies can be created with the help of script.
#
@ -27,7 +26,7 @@
#
# 1. Edit the definition of ${TARGET_TOPOLOGY} to define your virtual
# nodes. Virtual topology definition includes node names and their
# IP address. Target top. sytax: ( name|ip<->name|ip ... )
# IP address. Target top. syntax: ( name|ip<->name|ip ... )
# Example 1: ( n1|10.0.2.1/30<->n2|10.0.2.2/30 ...)
# Example 2: ( n1|2001:b90::14a/125<->n1|2001:b90::14b/125 ...)
#
@ -35,8 +34,8 @@
#
# 3. Add necessary static route commands for each virtual node. For
# example assume you have three virtual nodes connected each other
# llike a chain ( n1 is connected to n2, n2 is connecte to n3 ).
# In order to estabklish connectivity among these virtual nodes,
# like a chain (n1 is connected to n2, n2 is connected to n3).
# In order to establish connectivity among these virtual nodes,
# you have to add default routes to node n1 and node n3. Example
# static route command is:
# STATIC_ROUTE0="jexec n1 route add -inet default 10.0.2.2"
@ -48,7 +47,7 @@
# 4. Stop bridging by running this script with "stop" as the
# command line argument.
#
# 5. This cript uses a template file in order to carry information
# 5. This script uses a template file in order to carry information
# between start and stop calls.
# In the start call, the netgraph interfaces and jails are created.
# At the stop phase, all created objects should be removed.
@ -85,7 +84,7 @@
#
# List the names of virtual nodes and their IP addresses. Use ':'
# character to seperate node name from node IP address and netmask.
# character to separate node name from node IP address and netmask.
TARGET_TOPOLOGY="n1|10.0.2.1/30<->n2|10.0.2.2/30 n2|10.0.2.5/30<->n3|10.0.2.6/30 n2|10.0.2.9/30<->n4|10.0.2.10/30"
STATIC_ROUTE0="jexec n1 route add -inet default 10.0.2.2"
@ -93,7 +92,7 @@ STATIC_ROUTE1="jexec n3 route add -inet default 10.0.2.5"
STATIC_ROUTE2="jexec n4 route add -inet default 10.0.2.9"
STATIC_ROUTE_CNT=3
# MAC manifacturer prefix. This can be modified according to needs.
# MAC manufacturer prefix. This can be modified according to needs.
MAC_PREFIX="00:1d:92"
# Temporary file is important for proper execution of script.
@ -135,7 +134,7 @@ virtual_chain_start() {
# Create temporary file for usage. This file includes generated
# interface names and jail names. All bridges, interfaces and jails
# are written to file while created. In clean-up process written
# objects are cleaned (i.e removed) from system.
# objects are cleaned (i.e. removed) from system.
if [ -e ${TEMP_FILE} ]; then
touch ${TEMP_FILE}
@ -193,7 +192,7 @@ virtual_chain_start() {
i=`expr $i + 1`
done
echo "Virtual WAN established succesfully!"
echo "Virtual WAN established successfully!"
}
virtual_chain_create_interface_with_ip() {
@ -280,7 +279,6 @@ virtual_chain_create_peer_if_necessary() {
}
# Stop routine.
virtual_chain_stop() {
@ -312,7 +310,7 @@ virtual_chain_stop() {
echo "Removing tempfile ${TEMP_FILE}"
rm ${TEMP_FILE}
fi
echo "Virtual LAN objects removed succesfully!"
echo "Virtual LAN objects removed successfully!"
}
@ -324,7 +322,6 @@ virtual_chain_usage() {
# Main entry point.
case $# in
1)
case $1 in

15
share/examples/netgraph/virtual.lan
View File

@ -13,7 +13,6 @@
# its use.
#
# $FreeBSD$
#
# This script adds virtual nodes to one of the physical interfaces
# visible on your local area network (LAN). Virtual nodes seems real
@ -33,7 +32,7 @@
#
# 2. Edit the definition of ${TARGET_TOPOLOGY} to define your virtual
# nodes. Virtual topology definition includes node names and their
# IP address. Target top. sytax: ( node1|ip1/24 node2|ip2/24 ... )
# IP address. Target top. syntax: ( node1|ip1/24 node2|ip2/24 ... )
# Example 1: ( n1|122.122.122.12/24, n2|122.122.122.13/24 ...)
# Example 2: ( n1|2001:b90::14a/125, n1|2001:b90::14b/125 ...)
#
@ -42,7 +41,7 @@
# 4. Stop bridging by running this script with "stop" as the
# command line argument.
#
# 5. This cript uses a template file in order to carry information
# 5. This script uses a template file in order to carry information
# between start and stop calls.
# In the start call, the netgraph interfaces and jails are created.
# At the stop phase, all created objects should be removed.
@ -85,11 +84,11 @@
ETHER_INTF="em0"
# List the names of virtual nodes and their IP addresses. Use ':'
# character to seperate node name from node IP address and netmask.
# character to separate node name from node IP address and netmask.
TARGET_TOPOLOGY="c1|10.0.2.20/24 c2|10.0.2.21/24 c3|10.0.2.22/24"
# MAC manifacturer prefix. This can be modified according to needs.
# MAC manufacturer prefix. This can be modified according to needs.
MAC_PREFIX="00:1d:92"
# Temporary file is important for proper execution of script.
@ -131,7 +130,7 @@ virtual_lan_start() {
# Create temporary file for usage. This file includes generated
# interface names and jail names. All bridges, interfaces and jails
# are written to file while created. In clean-up process written
# objects are cleaned (i.e removed) from system.
# objects are cleaned (i.e. removed) from system.
if [ -e ${TEMP_FILE} ]; then
touch ${TEMP_FILE}
@ -265,7 +264,7 @@ virtual_lan_start() {
# incremented.
LINKNUM=`expr ${LINKNUM} + 1`
done
echo "Virtual LAN established succesfully!"
echo "Virtual LAN established successfully!"
}
@ -300,7 +299,7 @@ virtual_lan_stop() {
echo "Removing tempfile ${TEMP_FILE}"
rm ${TEMP_FILE}
fi
echo "Virtual LAN objects removed succesfully!"
echo "Virtual LAN objects removed successfully!"
}