mirror of
https://github.com/openbsd/src.git
synced 2025-01-10 06:47:55 -08:00
fix some spacing issues;
This commit is contained in:
parent
e7bba6235f
commit
1daccde927
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: atactl.8,v 1.37 2007/05/31 19:19:43 jmc Exp $
|
||||
.\" $OpenBSD: atactl.8,v 1.38 2008/06/03 19:51:02 jmc Exp $
|
||||
.\" $NetBSD: atactl.8,v 1.5 1999/02/24 18:49:14 jwise Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1998 The NetBSD Foundation, Inc.
|
||||
@ -35,7 +35,7 @@
|
||||
.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
|
||||
.\" POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: May 31 2007 $
|
||||
.Dd $Mdocdate: June 3 2008 $
|
||||
.Dt ATACTL 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -462,7 +462,7 @@ SMART support) as reported by
|
||||
.Pp
|
||||
.Dl # atactl /dev/wd0c identify
|
||||
.Pp
|
||||
Enable SMART support on
|
||||
Enable SMART support on
|
||||
.Pa /dev/wd0
|
||||
for detection of early warning signs of device failure:
|
||||
.Pp
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: raidctl.8,v 1.39 2008/03/23 23:28:46 krw Exp $
|
||||
.\" $OpenBSD: raidctl.8,v 1.40 2008/06/03 19:51:02 jmc Exp $
|
||||
.\" $NetBSD: raidctl.8,v 1.24 2001/07/10 01:30:52 lukem Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1998 The NetBSD Foundation, Inc.
|
||||
@ -61,7 +61,7 @@
|
||||
.\" any improvements or extensions that they make and grant Carnegie the
|
||||
.\" rights to redistribute these changes.
|
||||
.\"
|
||||
.Dd $Mdocdate: March 23 2008 $
|
||||
.Dd $Mdocdate: June 3 2008 $
|
||||
.Dt RAIDCTL 8
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -1160,7 +1160,8 @@ up of RAID 1 sets) are
|
||||
supported as root devices or auto-configurable devices at this point.
|
||||
(Multi-layered RAID devices
|
||||
.Em are
|
||||
supported in general, however, as mentioned earlier.) Note that in
|
||||
supported in general, however, as mentioned earlier.)
|
||||
Note that in
|
||||
order to enable component auto-detection and auto-configuration of
|
||||
RAID devices, the line:
|
||||
.Bd -unfilled -offset indent
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: tsec.4,v 1.2 2008/05/20 11:39:12 jmc Exp $
|
||||
.\" $OpenBSD: tsec.4,v 1.3 2008/06/03 19:51:02 jmc Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2008 Mark Kettenis <kettenis@openbsd.org>
|
||||
.\"
|
||||
@ -14,7 +14,7 @@
|
||||
.\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
|
||||
.\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
|
||||
.\"
|
||||
.Dd $Mdocdate: May 20 2008 $
|
||||
.Dd $Mdocdate: June 3 2008 $
|
||||
.Dt TSEC 4 socppc
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -45,11 +45,11 @@ Attempt to autoselect the media type (default)
|
||||
Use 1000baseT on copper, full duplex
|
||||
.It media 1000baseT Op mediaopt half-duplex
|
||||
Use 1000baseT on copper, half duplex
|
||||
.It media 1000baseSX mediaopt full-duplex
|
||||
.It media 1000baseSX mediaopt full-duplex
|
||||
Use 1000baseSX on fiber, full duplex
|
||||
.It media 1000baseSX Op mediaopt half-duplex
|
||||
Use 1000baseSX on fiber, half duplex
|
||||
.It media 100baseTX mediaopt full-duplex
|
||||
.It media 100baseTX mediaopt full-duplex
|
||||
Use 100baseTX, full duplex
|
||||
.It media 100baseTX Op mediaopt half-duplex
|
||||
Use 100baseTX, half duplex
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: pfsync.4,v 1.26 2007/09/20 20:50:07 mpf Exp $
|
||||
.\" $OpenBSD: pfsync.4,v 1.27 2008/06/03 19:51:02 jmc Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 2002 Michael Shalayeff
|
||||
.\" Copyright (c) 2003-2004 Ryan McBride
|
||||
@ -24,7 +24,7 @@
|
||||
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
|
||||
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
|
||||
.\"
|
||||
.Dd $Mdocdate: September 20 2007 $
|
||||
.Dd $Mdocdate: June 3 2008 $
|
||||
.Dt PFSYNC 4
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -121,7 +121,7 @@ e.g.:
|
||||
It is important that the pfsync traffic be well secured
|
||||
as there is no authentication on the protocol and it would
|
||||
be trivial to spoof packets which create states, bypassing the pf ruleset.
|
||||
Either run the pfsync protocol on a trusted network \- ideally a network
|
||||
Either run the pfsync protocol on a trusted network \- ideally a network
|
||||
dedicated to pfsync messages such as a crossover cable between two firewalls,
|
||||
or specify a peer address and protect the traffic with
|
||||
.Xr ipsec 4 .
|
||||
|
@ -1,4 +1,4 @@
|
||||
.\" $OpenBSD: shar.1,v 1.10 2007/08/06 19:16:06 sobrado Exp $
|
||||
.\" $OpenBSD: shar.1,v 1.11 2008/06/03 19:51:02 jmc Exp $
|
||||
.\" $NetBSD: shar.1,v 1.4 1995/08/18 14:55:40 pk Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1990, 1993
|
||||
@ -30,7 +30,7 @@
|
||||
.\"
|
||||
.\" @(#)shar.1 8.1 (Berkeley) 6/6/93
|
||||
.\"
|
||||
.Dd $Mdocdate: August 6 2007 $
|
||||
.Dd $Mdocdate: June 3 2008 $
|
||||
.Dt SHAR 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -61,7 +61,7 @@ To create a shell archive of the program
|
||||
and mail it to Rick:
|
||||
.Bd -literal -offset indent
|
||||
$ cd ls
|
||||
$ shar `find . -print` \&| mail -s "ls source" rick
|
||||
$ shar `find . -print` \&| mail -s "ls source" rick
|
||||
.Ed
|
||||
.Pp
|
||||
To recreate the program directory:
|
||||
|
Loading…
Reference in New Issue
Block a user