386BSD 0.0 - Revision history

Jnc: rm nonexist template

2021-03-09T15:48:02Z

rm nonexist template

← Older revision		Revision as of 15:48, 9 March 2021
Line 77:		Line 77:
	* [http://www.dnull.com/bsd/oldnews/bsdnew1761.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==		<!-- ==Notes== -->
	~~{{Reflist}}~~

	[[Category: Unix-based OS's]]		[[Category: Unix-based OS's]]

2019-07-15T03:44:23Z

The 0.0 announcement and release notes

2019-07-15T03:40:36Z

The 0.0 announcement

← Older revision		Revision as of 03:40, 15 July 2019
Line 17:		Line 17:
	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 ==		== The 0.0 announcement and release notes ==
			These are both pretty big, so I've put them onto their own pages.

	[[386BSD 0.0 announcement]]		[[386BSD 0.0 announcement]]
			[[386BSD 0.0 release notes]]

	== releases ==		== releases ==

2018-12-16T14:12:04Z

+cat

2012-04-15T00:24:20Z

fix shbang patch url

← Older revision		Revision as of 00:24, 15 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]		* [http://www.dnull.com/bsd/oldnews/bsdnew1761.html shbang support and proper handling long arg list]

	==Notes==		==Notes==
	{{Reflist}}		{{Reflist}}

2012-04-14T13:54:31Z

add some footnotes (wikip-style)

← Older revision		Revision as of 13:54, 14 April 2012
Line 59:		Line 59:
	And all the 'errors' about stray interrupts and 'format error in		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		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		'fast!...' but it works better when the clock is in the 1990's
	otherwise it'll reset back to 1970 and things act weird.		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://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/bsdnew1671.html shbang support and proper handling long arg list]

			==Notes==
			{{Reflist}}

2012-04-14T13:34:38Z

add one more patch

← 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]

2011-09-05T21:24:51Z

← Older revision		Revision as of 21:24, 5 September 2011
Line 4:		Line 4:

	As they state:		As they state:

			At the moment, 386BSD comes up single user, and requires manual starting of the system daemons, as well as filesystem checks. In use, one would minimally wish to type after booting:
	<pre>		<pre>
	~~At the moment, 386BSD comes up single user, and~~
	~~requires manual starting of the system daemons, as well as~~
	~~filesystem checks. In use, one would minimally wish to type~~
	~~after booting:~~

	fsck -p		fsck -p
	mount -a		mount -a
	update		update
	/etc/netstart		/etc/netstart
			</pre>
			This will improve in forthcoming versions of 386BSD. Be aware that the user is running as the super-user, and care should be taken given the maximum privileges present.

	~~This will improve in forthcoming versions of 386BSD.~~
	~~Be aware that the user is running as the super-user, and~~
	~~care should be taken given the maximum privileges present.~~
	~~</pre>~~

	~~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 ==		== The 0.0 announcement ==

2010-12-25T17:08:57Z

← Older revision		Revision as of 17:08, 25 December 2010
Line 1:		Line 1:
	[[Image:386BSD 0.0.jpg\|thumb\|200px\|right\|386BSD 0.0 floppy]]		[[Image:386BSD 0.0.jpg\|thumb\|200px\|right\|386BSD 0.0 floppy]]

	~~386BSD~~ 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:		As they state:

2010-12-25T17:05:21Z

← Older revision		Revision as of 17:05, 25 December 2010
Line 5:		Line 5:
	As they state:		As they state:
	<pre>		<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		filesystem checks. In use, one would minimally wish to type
	after booting:		after booting: