Fix some bitrotted documentation.

3 files changed, 18 insertions, 24 deletions

diff --git a/release/picobsd/doc/src/how2build.html b/release/picobsd/doc/src/how2build.html
index 8549c5b..12303be 100644
--- a/release/picobsd/doc/src/how2build.html
+++ b/release/picobsd/doc/src/how2build.html
@@ -18,13 +18,13 @@
 	Become root. You'll need to mount and unmount various volumes.
 </li>
 <li>
-	Make sure you are running kernel with support for vn(4) devices.
+	Make sure you are running kernel with support for md(4) devices.
 	If you run plain GENERIC (just as it was installed on your system),
 	you'll need to recompile you kernel and reinstall it. See the
 	appropriate entries in The Handbook (/usr/share/doc/handbook).
 </li>
 <li>	Change working directory (<code>cd build</code>) and run the
-	<code>./build</code> script. Select target language, size of MFS and
+	<code>./picobsd</code> script. Select target language, size of MFS and
 	one of pre-canned setups (personal dialup, dialin server or
 	router-like). Details of each setup are contained in dial/,
 	router/, isp/ and net/ directories respectively. You should at least
@@ -107,14 +107,15 @@
 </li>
 </ul>
 </li>
-<li>	Make sure that the system you're running has /dev/[r]vn0* entries in
-	/dev directory (if not, you can make them with 'MAKEDEV vn0'), AND
-	that your running kernel has built-in vnode driver (there should be a
-	line in your kernel config file stating 'device vn xxx').
+<li>	Make sure that the system you're running has /dev/md0* entries in
+	/dev directory (if not, and you dont have DEVFS running, you can
+	make them with 'MAKEDEV md0'), AND
+	that your running kernel has built-in memory file device (there
+	should be a line in your kernel config file stating 'device md').
 </li>
 <li>	You'll need at least 9MB of free disk space, and free /mnt directory.
 </li>
-<li>	Do a <code>cd build/</code> and fire off the <code>./build</code>
+<li>	Do a <code>cd build/</code> and fire off the <code>./picobsd</code>
 	script. Select the build parameters or 'n' for 'no change'. If all
 	is well, after some time (like 10-30m) you end up with a
 	'picobsd.bin' file in this directory.
@@ -162,7 +163,7 @@
 </ul>
 <li>		the build process displays "Preparing MFS" and then
 		silently stops. In this case check if you're running it as
-		root, and that you run kernel with support for vn(4)
+		root, and that you run kernel with support for md(4)
 		devices. Also, you can add 'set -x' at hte beginning
 		of the scripts to see exactly where they stop.
 </li>
diff --git a/release/picobsd/doc/src/intrinsics.html b/release/picobsd/doc/src/intrinsics.html
index c69d022..f8ff478 100644
--- a/release/picobsd/doc/src/intrinsics.html
+++ b/release/picobsd/doc/src/intrinsics.html
@@ -49,13 +49,9 @@ the build process:</p>
 </li>
 <li>
 	'stage1' prepares the file called fs.PICOBSD with given size - it's a
-	placeholder for the future MFS. Next, it turns it into device (using
-	vnconfig), and then performs some tricks :-) which allow for
-	doing 'disklabel'. I use the 'auto' option to disklabel(8), which
-	behaves strangely in 2.2.x - what it's supposed to do is to
-	automagically determine the disk parameters from the  underlying
-	device (in this case, /dev/rvn0). This works ok in 3.0-current, and
-	allows for using arbitrary (>1024kB) MFS sizes.
+	placeholder for the future MFS. Next, it turns it into device,
+	and then performs some tricks which allow for doing 'disklabel'.
+	I use the 'auto' option to disklabel(8).
 
 <p>	One notable exception here is with the "router" floppy - I use one
 	of extended floppy formats (820kB).</p>
diff --git a/release/picobsd/doc/src/intro.html b/release/picobsd/doc/src/intro.html
index 035cd0c..f115697 100644
--- a/release/picobsd/doc/src/intro.html
+++ b/release/picobsd/doc/src/intro.html
@@ -54,7 +54,7 @@ would offer you benefits of Unix, while still fitting in reasonable space -
 here it is!</p>
 
 <p>PicoBSD is a one floppy version of 
-<A HREF="http://www.freebsd.org/">FreeBSD</a> 3.0-current, which in its
+<A HREF="http://www.freebsd.org/">FreeBSD</a>, which in its
 different variations allows you to have secure dialup access, small diskless
 router or even a dial-in server. And all this on only one standard 1.44MB
 floppy - no need to sacrifice over 100MB of your precious HDD space.</p>
@@ -103,17 +103,14 @@ the set of fonts included, C locale, and the language of messages.</p>
 <p><i>(See the <A HREF="hardware.html">feature list</a> for more
 details)</i></p>
 
-<p>The above floppies were built from 3.0-current sources. Though they
-provide more features, they tend to be less stable than the latest
-RELEASE of FreeBSD. Dinesh Nair back-ported these scripts to the
-latest release (2.2.5), and continues development of PicoBSD using sources
-from that branch. You can find floppies built from 2.2.5 sources 
-<A HREF="http://www.freebsd.org/~picobsd/picobsd225/">here</a> or at 
-<A HREF="http://info.net-gw.com/picoBSD/">his server</a>.</p>
+<p>The above floppies were built from FreeBSD sources.
+You can find floppies built from 2.2.5 sources 
+<A HREF="http://www.freebsd.org/~picobsd/picobsd225/">here</a> or 
+<A HREF="http://info.net-gw.com/picoBSD/">here</a>.</p>
 
 <HR shade align="center">
 <A NAME="how"><h3>How can I use it?</h3>
-<p>Previous versions were packed with PKZIP(tm) compatible program - now they
+<p>Previous versions were packed with a PKZIP(tm) compatible program - now they
 are simply the raw binary floppy images, so you just need to grab the
 appropriate version of the file.</p>