386BSD 0.0 - Revision history

Jnc: rm nonexist template

2021-03-09T15:48:02Z

rm nonexist template

2019-07-15T03:44:23Z

‎The 0.0 announcement and release notes

2019-07-15T03:40:36Z

‎The 0.0 announcement

2018-12-16T14:12:04Z

+cat

2012-04-15T00:24:20Z

fix shbang patch url

2012-04-14T13:54:31Z

add some footnotes (wikip-style)

2012-04-14T13:34:38Z

add one more patch

2011-09-05T21:24:51Z

2010-12-25T17:08:57Z

2010-12-25T17:05:21Z

@@ Line 77: / Line 77: @@
 * [http://www.dnull.com/bsd/oldnews/bsdnew1761.html shbang support and proper handling long arg list]
-==Notes==
+<!-- ==Notes== -->
 [[Category: Unix-based OS's]]

@@ Line 17: / Line 17: @@
 That is right, no login, you are just running as root!!!!
-== The 0.0 announcement ==
+== The 0.0 announcement and release notes ==
 [[386BSD 0.0 announcement]]
 == releases ==

@@ Line 73: / Line 73: @@
 *[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/1c6397039f10e76b?hl=en close-on-exec was broken]
 *[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/cb899f7ccb81550b?hl=en more cooked/raw mode issues]
-* [http://www.dnull.com/bsd/oldnews/bsdnew1671.html shbang support and proper handling long arg list]
+* [http://www.dnull.com/bsd/oldnews/bsdnew1761.html shbang support and proper handling long arg list]
 ==Notes==
 {{Reflist}}

@@ Line 59: / Line 59: @@
 And all the 'errors' about stray interrupts and 'format error in
 bad-sector file' are normal (it's in usenet) as 0.0 was a very touchy
-animal.  So, ignoring the floppy I ran it under Qemu and it's
+animal.<ref>actually it is still present in later version but controlled by wdquiet variable. --[[User:Roytam|Roytam]] 06:54, 14 April 2012 (PDT)</ref>  So, ignoring the floppy I ran it under Qemu and it's
 'fast!...' but it works better when the clock is in the 1990's
 otherwise it'll reset back to 1970 and things act weird.
@@ Line 74: / Line 74: @@
 *[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/cb899f7ccb81550b?hl=en more cooked/raw mode issues]
 * [http://www.dnull.com/bsd/oldnews/bsdnew1671.html shbang support and proper handling long arg list]

← Older revision		Revision as of 13:34, 14 April 2012
Line 73:		Line 73:
	*[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/1c6397039f10e76b?hl=en close-on-exec was broken]		*[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/1c6397039f10e76b?hl=en close-on-exec was broken]
	*[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/cb899f7ccb81550b?hl=en more cooked/raw mode issues]		*[http://groups.google.com/group/comp.unix.bsd/browse_thread/thread/cb899f7ccb81550b?hl=en more cooked/raw mode issues]
		+	* [http://www.dnull.com/bsd/oldnews/bsdnew1671.html shbang support and proper handling long arg list]

@@ Line 4: / Line 4: @@
 As they state:
 <pre>
 fsck -p
 mount -a
 update
 /etc/netstart
-that is right, no login, you are just running as root!!!!
+That is right, no login, you are just running as root!!!!
 == The 0.0 announcement ==

@@ Line 1: / Line 1: @@
 [[Image:386BSD 0.0.jpg|thumb|200px|right|386BSD 0.0 floppy]]
-BSD 0.0 ... is bare.  It is not what you would expect, being spoiled in multiuser systems!
+[[386 BSD]] 0.0 ... is bare.  It is not what you would expect, being spoiled in multiuser systems!
 As they state:

@@ Line 5: / Line 5: @@
 As they state:
 <pre>
-      At  the  moment,  386BSD  comes up single user, and re-
+      At  the  moment,  386BSD  comes up single user, and
-quires manual starting of the system  daemons,  as  well  as
+requires manual starting of the system  daemons,  as  well  as
 filesystem  checks. In use, one would minimally wish to type
 after booting: