summaryrefslogtreecommitdiff
path: root/sbin/bioctl
diff options
context:
space:
mode:
authorJason McIntyre <jmc@cvs.openbsd.org>2009-03-19 15:12:00 +0000
committerJason McIntyre <jmc@cvs.openbsd.org>2009-03-19 15:12:00 +0000
commit79742db4f6bdb3e669736ffe18a23c5c0676bb61 (patch)
tree5221d12f15ce659e5ab1d9e031c184a146731012 /sbin/bioctl
parent7d4821e7e192a4b22d3301228c51563d7f8441b5 (diff)
minor tweaks (sorry grunk!);
Diffstat (limited to 'sbin/bioctl')
-rw-r--r--sbin/bioctl/bioctl.86
1 files changed, 3 insertions, 3 deletions
diff --git a/sbin/bioctl/bioctl.8 b/sbin/bioctl/bioctl.8
index 55a3ea5742c..cb3e37592b1 100644
--- a/sbin/bioctl/bioctl.8
+++ b/sbin/bioctl/bioctl.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: bioctl.8,v 1.65 2009/03/19 13:44:46 grunk Exp $
+.\" $OpenBSD: bioctl.8,v 1.66 2009/03/19 15:11:59 jmc Exp $
.\"
.\" Copyright (c) 2004, 2005 Marco Peereboom
.\"
@@ -224,12 +224,12 @@ volume:
.Nm
will ask for a passphrase, that will be needed to unlock the encrypted
disk.
-After creating a new encrypted disk, the first megabyte of it should be
+After creating a newly encrypted disk, the first megabyte of it should be
zeroed, so tools like
.Xr fdisk 8
or
.Xr disklabel 8
-don't get confused by the random data that now appears on the new disk.
+don't get confused by the random data that appears on the new disk.
This can be done with the following command (assuming the new disk is sd3):
.Bd -literal -offset 3n
# dd if=/dev/zero of=/dev/rsd3c bs=1M count=1