Update to PicoBSD 0.44 from RELENG_3

author: roger <roger@FreeBSD.org> 1999-06-14 15:45:56 +0000
committer: roger <roger@FreeBSD.org> 1999-06-14 15:45:56 +0000
commit: 8aaed59fddf4ff59075dea6d01940fa70e4bced6 (patch)
tree: b3a6c24072584914248d48be0fc6f01aa408638c /release/picobsd/doc
parent: 896f01d1d7fd2609215a230b842c4a03b7fe3930 (diff)
download: FreeBSD-src-8aaed59fddf4ff59075dea6d01940fa70e4bced6.zip
FreeBSD-src-8aaed59fddf4ff59075dea6d01940fa70e4bced6.tar.gz
5 files changed, 51 insertions, 45 deletions
diff --git a/release/picobsd/doc/src/TODO.html b/release/picobsd/doc/src/TODO.html
index 8192f02..514dd02 100644
--- a/release/picobsd/doc/src/TODO.html
+++ b/release/picobsd/doc/src/TODO.html
@@ -1,5 +1,5 @@
 <html>
-<! $Id: TODO.html,v 1.2 1998/12/22 21:40:56 abial Exp $ >
+<! $Id: TODO.html,v 1.3.2.1 1999/05/07 10:02:45 abial Exp $ >
 <body>
 <h1><center>		Small FreeBSD ToDo List.
 </center></h1>
@@ -21,7 +21,7 @@ part of the work, please contact the coordinator of PicoBSD project
 <li>
 Eliminate need for patching FreeBSD source tree - either by
 keeping our own version of Makefiles, or by adding (many) knobs to
-the standard ones. (NOTE: this will be resolved in v. 0.44).
+the standard ones. (NOTE: this will be resolved in v. 0.45).
 </li>
 <li>
 Provide options for building separate kernel and FS images of
@@ -33,7 +33,7 @@ and "net" for most common tasks.
 </li>
 <li>
 Replace most of currently used scripts with Makefiles.
-(NOTE: this will be resolved in v. 0.44).
+(NOTE: this will be resolved in v. 0.45).
 </li>
 <li>
 Add simple authentication module to oinit.
@@ -57,6 +57,11 @@ etc, and write a short practical guide to embedding FreeBSD.
 
 <ul>
 <li>
+Change currently used crunched binaries to something more flexible
+- as it is now, even small change in set of programs requires
+rebuilding of the whole image.
+</li>
+<li>
 Change the building process so that it allows to easily choose
 (with finer granularity) needed components of the target system.
 </li>
@@ -67,12 +72,7 @@ removing drivers when running stripped kernels.
 <li>
 Investigate pros and cons of using the new boot/loader together
 with ELF kernels.
-(NOTE for v.0.43: it was simply mandatory to use it :-)
-</li>
-<li>
-Change currently used crunched binaries to something more flexible
-- as it is now, even small change in set of programs requires
-rebuilding of the whole image.
+(NOTE for v.0.43: it was simply mandatory to start to use it :-)
 </li>
 <li>
 Provide options for building systems which operate from
diff --git a/release/picobsd/doc/src/bugs.html b/release/picobsd/doc/src/bugs.html
index 2eb29ce..0ba3c5a 100644
--- a/release/picobsd/doc/src/bugs.html
+++ b/release/picobsd/doc/src/bugs.html
@@ -1,5 +1,5 @@
 <HTML>
-<! $Id: bugs.html,v 1.6 1998/11/01 20:01:40 abial Exp $ >
+<! $Id: bugs.html,v 1.7.2.1 1999/05/07 10:02:46 abial Exp $ >
 <HEAD>
    <TITLE>History and Bug fixes</TITLE>
 </HEAD>
@@ -14,6 +14,13 @@ the list before reporting a new one.</p>
 <p>We tried to make this software bug-free, but life is life... Sorry for the
  inconvenience.</p>
 
+<h3>PicoBSD 0.44</h3>
+<ul>
+<li>
+	1999.05.10: Slightly refreshed version to match 3.2-RELEASE.
+	No significant changes (yet)... :-(
+</li>
+</ul>
 <h3>PicoBSD 0.43</h3>
 <ul>
 <li>
diff --git a/release/picobsd/doc/src/faq.html b/release/picobsd/doc/src/faq.html
index 1a86d58..462739b 100644
--- a/release/picobsd/doc/src/faq.html
+++ b/release/picobsd/doc/src/faq.html
@@ -1,5 +1,5 @@
 <HTML>
-<! $Id: faq.html,v 1.3 1998/10/28 16:16:31 abial Exp $ >
+<! $Id: faq.html,v 1.4.2.1 1999/05/07 10:02:48 abial Exp $ >
 <HEAD>
    <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
    <META NAME="Author" CONTENT="Dinesh Nair">
@@ -37,26 +37,22 @@ fully grown daemons, and PicoBSD as a system infested with
 
 <P><B>What version of FreeBSD is PicoBSD based on ?</B></p>
 
-<P>PicoBSD has versions based on FreeBSD 3.0-RELEASE, 3.0-current and
+<P>PicoBSD has versions based on FreeBSD 3.2-RELEASE, 4.0-current and
 FreeBSD 2.2.5-RELEASE.
 <A HREF="mailto:abial@freebsd.org">Andrzej Bialecki</A> maintains the <A HREF="http://www.freebsd.org/~picobsd/picobsd.html">FreeBSD
-3.0-RELEASE and -current versions</A> and 
+3.x-RELEASE and -current versions</A> and 
 <A HREF="mailto:dinesh@alphaque.com">Dinesh Nair</A>
 maintains the <A HREF="http://info.net-gw.com/picoBSD/">FreeBSD
-2.2.5-RELEASE</A> version. Both the versions don't differ by much except
-for the following:
+2.2.5-RELEASE</A> version. Both the versions are different:
 <UL TYPE=CIRCLE>
 <LI>
-the 3.0-current version is, well, more current so it has support for the
-latest whiz-bang devices; on the other hand, it sometimes mean it can
-provide functionality not yet present in 2.2.5-RELEASE</LI>
+the 3.x-RELEASE version is the one actively maintained, and provides support
+for many new devices</li>
 
 <LI>
-the 2.2.5-RELEASE version is more stable and since binary sizes are smaller,
-it sometimes has a little more functionality than the 3.0-current version</LI>
+the 2.2.5-RELEASE version is not maintained anymore - the only difference is
+that it has lynx on board.</li>
 </UL>
-As far as possible, both versions will be kept functionally similar, but
-occasionaly divergence may occur.
 
 <p><b>What is current version of PicoBSD?</b></p>
 
@@ -84,7 +80,7 @@ external or internal.
 For LAN access, an Ethernet NIC (support for 3Com, NE2000 etc available)
 would also be required.
 <p>In case of "router" flavor, its requirements are even smaller: it can
-run in only 4MB of RAM, on a 386SX CPU.</p>
+run in as low as 4MB of RAM, on a 386SX CPU.</p>
 
 <P><B>Where do I get PicoBSD?</B></p>
  PicoBSD is available at the following
@@ -96,7 +92,7 @@ FreeBSD 3.0-RELEASE and -current</A> maintained by Andrzej Bialecki</LI>
 
 <LI>
 <A HREF="http://info.net-gw.com/picoBSD/">PicoBSD based on FreeBSD 2.2.5-RELEASE</A>
-maintained by Dinesh Nair</LI>
+prepared by Dinesh Nair</LI>
 </UL>
 Additional mirror sites will be brought online as demand increases. If
 you're interested in mirroring the PicoBSD distribution, please get in
@@ -133,13 +129,13 @@ Replace the <U>domain</U> with your domain and change the <U>nameserver</U>
 IP address to your nameserver or your ISP's nameserver. You may have as
 many <U>nameserver</U> lines as you want. Don't forget to run <I>/stand/update</I>
 to commit your changes to the floppy.
-<p>NOTE: starting with version 0.4, the <i>dialup</i> scripts asks you to
+<p>NOTE: starting with version 0.4, the <i>dialup</i> script asks you to
 set your nameserver as well as default domain name.</p>
 
 <p><b>I can't execute the <i>/stand/update</i> on the "router" floppy.</b></p>
 <p>The "router" floppy doesn't contain any real shell, so some commands work
 differently (and some don't work at all). In order to use this script you
-have to source it in, i.e.:
+have to 'source it in', i.e.:
 <pre>
 	(48)/# pwd
 	/
diff --git a/release/picobsd/doc/src/hardware.html b/release/picobsd/doc/src/hardware.html
index 2954695..f6f3e4e 100644
--- a/release/picobsd/doc/src/hardware.html
+++ b/release/picobsd/doc/src/hardware.html
@@ -1,5 +1,5 @@
 <html>
-<! $Id: hardware.html,v 1.1 1998/09/26 17:23:01 abial Exp $ >
+<! $Id: hardware.html,v 1.2.2.1 1999/02/21 22:04:54 abial Exp $ >
 <body>
 <h1><center>Lists of supported hardware configurations.</center></h1>
 
@@ -68,7 +68,7 @@ traceroute
 <li>support for several types of Ethernet cards (two of each kind) - see above
 for descriptions: ed, ie, ep, de, fxp, lnc
 </li>
-<li>network daemons: routing daemon (routed), inetd, telnetd, snmpd.
+<li>network daemons: routing daemon (routed), inetd, telnetd.
 </li>
 <li>IP Firewall and NAT daemon (natd).
 </li>
diff --git a/release/picobsd/doc/src/how2build.html b/release/picobsd/doc/src/how2build.html
index 7225603..5d08037 100644
--- a/release/picobsd/doc/src/how2build.html
+++ b/release/picobsd/doc/src/how2build.html
@@ -1,5 +1,5 @@
 <html>
-<! $Id: how2build.html,v 1.3 1998/10/28 16:16:31 abial Exp $ >
+<! $Id: how2build.html,v 1.4.2.1 1999/05/07 10:02:49 abial Exp $ >
 <head>
 <title><center>PicoBSD Development Kit</center></title>
 </head>
@@ -10,21 +10,18 @@
 
 <ol>
 <li>
-	Get the file <code>picobsd.tgz</code>. It contains the scripts
-	you'll need.  Also, I assume you run quite -current system with
-	full sources installed.
-
-<p>	NOTE1: beginning with version 0.4, PicoBSD sources are maintained as
-	part of official FreeBSD CVS repository, so if you have recent
-	source tree you can find them in /src/release/picobsd.</p>
-
-<p>	NOTE2: there were some mysterious interactions between vn(4) driver and
-	'disklabel auto' in versions earlier than 3.0. There is another set
-	of scripts prepared by <A HREF="mailto:dinesh@alphaque.com">Dinesh Nair
-	</a> which allows to build PicoBSD floppies on a earlier systems.</p>
-
-<p>	Unpack the archive into your <code>src/release/picobsd</code>.
-	You'll need at least 5MB of free space.</p>
+<p>	Beginning with version 0.4, PicoBSD sources are maintained as
+	part of official FreeBSD CVS repository, so 
+	you can find them in src/release/picobsd.</p>
+</li>
+<li>
+	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.
+	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
@@ -113,7 +110,7 @@
 <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 'pseudo-device vn').
+	line in your kernel config file stating 'pseudo-device vn xxx').
 </li>
 <li>	You'll need at least 9MB of free disk space, and free /mnt directory.
 </li>
@@ -163,6 +160,12 @@
 		after <code>stage1</code> script ends).
 </li>
 </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)
+		devices. Also, you can add 'set -x' at hte beginning
+		of the scripts to see exactly where they stop.
+</li>
 </ul>
 
 	You can also remove <code>2>&amp;1</code> redirections from Makefiles
author	roger <roger@FreeBSD.org>	1999-06-14 15:45:56 +0000
committer	roger <roger@FreeBSD.org>	1999-06-14 15:45:56 +0000
commit	8aaed59fddf4ff59075dea6d01940fa70e4bced6 (patch)
tree	b3a6c24072584914248d48be0fc6f01aa408638c /release/picobsd/doc
parent	896f01d1d7fd2609215a230b842c4a03b7fe3930 (diff)
download	FreeBSD-src-8aaed59fddf4ff59075dea6d01940fa70e4bced6.zip FreeBSD-src-8aaed59fddf4ff59075dea6d01940fa70e4bced6.tar.gz