add directory distributions

distributions/386BSD/0.1/386BSD/ANSS

@@ -0,0 +1,74 @@
+vi jmrtc
+[?1h="jmrtc" 1291 lines, 59319 characters From jmonroy@netcom.com Thu Jul	 1 01:08:25 1993
+Received: by netcom2.netcom.com (5.65/SMI-4.1/Netcom)
+	id AA29532; Thu, 1 Jul 93 01:09:02 -0700
+Date: Thu, 1 Jul 93 01:09:02 -0700
+From: jmonroy@netcom.com (Jesus Monroy Jr)
+Message-Id: <9307010809.AA29532@netcom2.netcom.com>
+To: sokol@reyes.stanford.edu
+Status: RO
+
+
+Reasons to fix the RTC.
+
+Released: 21:32:25 Sun	06-27-1993
+
+		At the request of Bill Jolitz and other, I have
+	written this report.  I should note that this is NOT a request
+	for a Real-Time OS (Operating System).	Also, I was a bit
+	unaware of the lack of work done in this area, RTC (Real-Time
+	Control). My assumption was that other had this knowledge, as
+	second-hand, just as John Sokol and I.	Our knowledge came
+	from work on our commercial products, the printer-port sound
+	dongle and the printer-port GPIB [communicator].  So in a
+	sense I am apologizing for any misunderstandings which may"jmrtc" 1291 lines, 59319 charactersiFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993iiFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993iiiFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993iiiiFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993iiiiiFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iiFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iikFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iikkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993	iikkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kkkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993		kkkkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kkkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993			kkkkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993				kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993				kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993				kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1993
+				
+78M8				kFrom jmonroy@netcom.com Thu Jul  1 01:08:25 199
+3				kkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1
+93				kkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 1
+993				kkkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25 
+1993				kkkkkFrom jmonroy@netcom.com Thu Jul  1 01:08:25
+ 1993					kFrom jmonroy@netcom.com Thu Jul  1 01:08:2
+5 1993					kFrom jmonroy@netcom.com Thu Jul  1 01:08:
+25 1993					kFrom jmonroy@netcom.com Thu Jul  1 01:08
+:25 1993				kFrom jmonroy@netcom.com Thu Jul  1 01:0
+8:25 1993				kkFrom jmonroy@netcom.com Thu Jul  1 01:
+08:25 1993				kkkFrom jmonroy@netcom.com Thu Jul  1 01
+:08:25 1993kFrom jmonroy@netcom.com Thu Jul  1 0
+1:08:25 1993kFrom jmonroy@netcom.com Thu Jul  1 
+01:08:25 1993kFrom jmonroy@netcom.com Thu Jul  1
+ 01:08:25 1993kFrom jmonroy@netcom.com Thu Jul  
+1 01:08:25 1993					kFrom jmonroy@netcom.com Thu Jul
+ 1 01:08:25 1993				kFrom jmonroy@netcom.com Thu Jul
+  1 01:08:25 1993				kkFrom jmonroy@netcom.com Thu Ju
+l  1 01:08:25 1993				kkkFrom jmonroy@netcom.com Thu J
+ul  1 01:08:25 1993kFrom jmonroy@netcom.com Thu 
+Jul  1 01:08:25 1993kFrom jmonroy@netcom.com Thu
+ Jul  1 01:08:25 1993kFrom jmonroy@netcom.com Th
+u Jul  1 01:08:25 1993kFrom jmonroy@netcom.com T
+hu Jul  1 01:08:25 1993					kFrom jmonroy@netcom.com 
+Thu Jul  1 01:08:25 1993				kFrom jmonroy@netcom.com
+ Thu Jul  1 01:08:25 1993				kkFrom jmonroy@netcom.co
+m Thu Jul  1 01:08:25 1993				kkkFrom jmonroy@netcom.c
+om Thu Jul  1 01:08:25 1993kFrom jmonroy@netcom.
+com Thu Jul  1 01:08:25 1993kFrom jmonroy@netcom
+.com Thu Jul  1 01:08:25 1993kFrom jmonroy@netco
+m.com Thu Jul  1 01:08:25 1993kFrom jmonroy@netc
+om.com Thu Jul  1 01:08:25 1993					kFrom jmonroy@net
+com.com Thu Jul  1 01:08:25 1993				kFrom jmonroy@ne
+tcom.com Thu Jul  1 01:08:25 1993				kkFrom jmonroy@n
+etcom.com Thu Jul  1 01:08:25 1993				kkkFrom jmonroy@
+netcom.com Thu Jul  1 01:08:25 1993kFrom jmonroy
+@netcom.com Thu Jul  1 01:08:25 1993kFrom jmonro
+y@netcom.com Thu Jul  1 01:08:25 1993kFrom jmonr
+oy@netcom.com Thu Jul  1 01:08:25 1993kFrom jmon
+roy@netcom.com Thu Jul  1 01:08:25 1993					kFrom jmo
+nroy@netcom.com Thu Jul  1 01:08:25 1993				kFrom jm
+onroy@netcom.com Thu Jul  1 01:08:25 1993				kjFrom j
+monroy@netcom.com Thu Jul  1 01:08:25 1993				kjjFrom 
+jmonroy@netcom.com Thu Jul  1 01:08:25 1993jFrom
+ jmonroy@netcom.com Thu Jul  1 01:08:25 1993jFro
+m jmonroy@netcom.com Thu Jul  1 01:08:25 1993jFr
+om jmonroy@netcom.com Thu Jul  1 01:08:25 1993jF
+rom jmonroy@netcom.com Thu Jul  1 01:08:25 1993j
+From jmonroy@netcom.com Thu Jul  1 01:08:25 1993

distributions/386BSD/0.1/386BSD/ANSS2

@@ -0,0 +1,194 @@
+
+
+	report.	 The next paragraph is an outline on the report.
+
+
+
+		This  is a breakdown of the sections below.  The
+
+	sections are broken up by a set of triple dashed lines with
+
+	the section number in the center of the line.  The first
+
+	section shows that time is an issue and planning is better
+
+	than post (or run-time) analysis.  The second section shows
+
+	that interrupts and the error recovery process are the main
+
+	contentions for efficient context switching and kernel
+
+	operations.  So, not having a failure will greatly increase
+
+	system efficiency (This should be a Given.).  Section Three
+
+	answer the popular myths about RTC. In section four are
+
+	comments  from	 Mr. David Brown of UCSD  about his
+
+	experiences with the QIC-40/80 implementation.	Lastly in
+
+	Section Five are my comments and recommendations.
+
+
+
+		    -----------o0o--------------
+
+
+
+		Before starting I will define some words:
+
+
+
+		Clock	    Time giver; this device always has the
+
+current time in a real-time format, but
+
+not necessarily a earth-time format.
+
+(I.E. hours/minutes/seconds)
+
+
+
+		Timer	    This should be like a stop/start watch.
+
+The purpose is to measure elapsed time,
+
+and signal (precision alarms).
+
+
+
+		Counter	    This will be a hardware/software counter.
+
+The purpose of which is to count the
+
+passage of time in a sliced fashion; in
+
+this way it just counts and is not
+
+referenced to anything in general.
+
+
+
+
+
+		    -----------o1o--------------
+
+		    -----------o1o--------------
+
+		    -----------o1o--------------
+
+
+
+			Why fix the RTC
+
+			---------------
+
+
+
+		Speed is our paradox as end users ask for flexibility
+
+	and better services.  Those of us involved with the technology
+
+	know that more speed is available,  such that the applicator
+
+	to this, will ask for this, volante, and more.	The disjointed
+
+	questions, listed below, arise:
+
+
+
+		How do we plan for the unknown?
+
+
+
+		What historical facts may lead us toward the right
+
+		decisions?
+
+
+
+		Is having more than one clock necessary?
+
+
+
+		If so, what functionality is needed?
+
+
+
+		How is this of benefit to the QIC-40/80?
+
+
+
+		Who will decide these issues?
+
+
+
+
+
+		Strangely enough I will say this may already be decided
+
+	for 386bsd.  Even more strange, I plan not to discuss, in
+
+	depth, the aspects of RTC (Real Time Control) of a Non-real
+
+	time OS, like 386bsd. [1]
+
+
+
+		What will follow are: reasons for a functional RTC
+
+	(Real Time Clock) and Reasons for the new temporal
+
+	(time-related) system calls.  In addition, before starting I
+
+	should say that these notes may also be released with "RTC
+
+	Notes", articles in which I plan to explain the exploit of
+
+	the RTC (clock).  A few persons have expressed interest
+
+	in writing this driver, they include:
+
+
+
+		gordon@sneaky.lonestar.org	  Gordon L. Burditt
+
+		sokol@reyes.stanford.edu	  John L. Sokol
+
+
+
+
+
+			-----------o1o--------------
+
+
+
+
+
+		To start off with it is best that I quote someone.
+
+
+
+
+
+		"Time is fundamentally different from the state
+
+		 components of a computing machine.  For all we
+
+		 know, time is continuous, monotonic and
+
+		 divergent, and program variables generally
+
+		 happen not to have any of these characteristics.
+
+		 Only if we recognize the special status of time
+
+		 will we be able to find and exploit the
+
+		 intricacies of providing time properties and
+
+		 avoid pitfalls like "Zeno" behaviors, which
+78M8	should say that these notes may also be released with "RTC78M8	(time-related) system calls.  In addition, before starting I78M8	(Real Time Clock) and Reasons for the new temporal78M8		What will follow are: reasons for a functional RTC78M878M8	time OS, like 386bsd. [1]78M8	depth, the aspects of RTC (Real Time Control) of a Non-real78M8	for 386bsd.  Even more strange, I plan not to discuss, in78M8		Strangely enough I will say this may already be decided78M878M878M8		Who will decide these issues?78M878M8		How is this of benefit to the QIC-40/80?78M878M8		If so, what functionality is needed?78M878M8		Is having more than one clock necessary?78M878M8		decisions?78M8		What historical facts may lead us toward the right78M878M8		How do we plan for the unknown?78M878M8	questions, listed below, arise:78M8	to this, will ask for this, volante, and more.	The disjointed78M8	know that more speed is available,  such that the applicator78M8	and better services.  Those of us involved with the technology78M8		Speed is our paradox as end users ask for flexibility78M878M8			---------------78M8			Why fix the RTC78M878M8		    -----------o1o--------------78M8		    -----------o1o--------------78M8		    -----------o1o--------------78M878M878M8			    referenced to anything in general.78M8			    this way it just counts and is not78M8			    passage of time in a sliced fashion; in78M8			    The purpose of which is to count the78M8		Counter	    This will be a hardware/software counter.78M878M8			    and signal (precision alarms).78M8			    The purpose is to measure elapsed time,78M8		Timer	    This should be like a stop/start watch.78M878M8			    (I.E. hours/minutes/seconds)78M8			    not necessarily a earth-time format.78M8			    current time in a real-time format, but78M8		Clock	    Time giver; this device always has the78M878M8		Before starting I will define some words:78M878M8		    -----------o0o--------------78M878M8	Section Five are my comments and recommendations.
+
+

distributions/386BSD/0.1/386BSD/BINMAN

@@ -0,0 +1,57 @@
+441875432 240640 bin01.00
+3402628943 240640 bin01.01
+3421007189 240640 bin01.02
+2824989560 240640 bin01.03
+949718622 240640 bin01.04
+493712579 240640 bin01.05
+433972301 240640 bin01.06
+2138347779 240640 bin01.07
+2476552551 240640 bin01.08
+2785667660 240640 bin01.09
+3370718171 240640 bin01.10
+1399943521 240640 bin01.11
+6298593 240640 bin01.12
+3800527281 240640 bin01.13
+67086176 240640 bin01.14
+1436432920 240640 bin01.15
+1876914985 240640 bin01.16
+2473547701 240640 bin01.17
+1605023766 240640 bin01.18
+1266505117 240640 bin01.19
+1427212099 240640 bin01.20
+1867269487 240640 bin01.21
+566731085 240640 bin01.22
+85112529 240640 bin01.23
+3111271658 240640 bin01.24
+2492439112 240640 bin01.25
+2066675106 240640 bin01.26
+2950451818 240640 bin01.27
+717218077 240640 bin01.28
+518901856 240640 bin01.29
+75851061 240640 bin01.30
+168227342 240640 bin01.31
+3762212985 240640 bin01.32
+2550888322 240640 bin01.33
+2006326207 240640 bin01.34
+3989166203 240640 bin01.35
+1489191847 240640 bin01.36
+613527858 240640 bin01.37
+2026734843 240640 bin01.38
+1676217456 240640 bin01.39
+2825123822 240640 bin01.40
+308650158 240640 bin01.41
+3405597195 240640 bin01.42
+107074193 240640 bin01.43
+1785821567 240640 bin01.44
+3329740773 240640 bin01.45
+2593897473 240640 bin01.46
+851650659 240640 bin01.47
+3782400489 240640 bin01.48
+2428661842 240640 bin01.49
+2859692637 240640 bin01.50
+414791052 240640 bin01.51
+293482156 240640 bin01.52
+1977080362 240640 bin01.53
+500884922 240640 bin01.54
+535588852 240640 bin01.55
+658514098 227717 bin01.56

distributions/386BSD/0.1/386BSD/BUGNFIX.FOR

@@ -0,0 +1,131 @@
+
+
+
+
+
+
+
+		    386BSD RELEASE 0.1
+		  BUG AND FIX REPORT FORM
+
+
+     386BSD is an experimental research system intended	for
+exploration  and  study. The inclusion of source code allows
+the creative and industrious student of operating systems to
+modify,	correct,  augment and otherwise alter the system in
+any manner desired.  Due to  the  "free"  nature  of  386BSD
+Release 0.1, we cannot provide "on-demand" support.
+
+     We do encourage feedback, however, on bug fixes,  prob-
+lems  and  solutions  which  arise during configuration, and
+improvements to 386BSD.	These changes will be	incorporated
+back  into  the system, and made available once again to the
+386BSD audience, to further encourage use of this system.
+
+     Please complete this bug and fix report and return to:
+
+    Lynne Greer Jolitz
+    386BSD Bug and Fix Report
+    447 61ST Street
+    Oakland, CA. 94609	USA
+
+    +1-510-420-0174 FAX
+    ljolitz@cardio.ucsf.edu
+    CIS 76703,4266
+
+
+_B_U_G _F_I_N_D_E_R _I_N_F_O_R_M_A_T_I_O_N
+
+NAME:
+TITLE:
+FIRM:
+ADDRESS:
+COUNTRY:
+PHONE:
+FAX:
+EMAIL:
+
+
+_P_C _I_N_F_O_R_M_A_T_I_O_N
+
+1.   What  is  your  PC	system	configuration?	Please	be
+     specific,	as  success  can  vary	with a difference in
+     manufacture date or variation.
+
+	 386/486/387:
+	 ISA/EISA/SCSI:
+	 RAM size:
+	 drive(s) type and size:
+	 tape(s) type and size:
+	 ethernet type:
+
+
+386BSD BUGNFIX.FORM	  1			July 1992
+
+
+
+
+
+
+
+
+
+
+	 graphics type:
+	 serial type:
+	 parallel type:
+	 other:
+
+
+_B_u_g_s
+
+1.   What bugs have you found in this system? Please  attach
+     any  pertinent  printouts	and  system messages. Please
+     also attach any bug fixes for others to use.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+386BSD BUGNFIX.FORM	  2			July 1992
+
+
+

distributions/386BSD/0.1/386BSD/CAREWARE.INF

@@ -0,0 +1,130 @@
+
+
+
+
+
+
+
+		       "Tiny 386BSD"
+			  and the
+		   DDJ Careware Program:
+
+		    Making A Difference
+
+		       William Jolitz
+			Lynne Jolitz
+
+
+_W_h_a_t _i_s _C_a_r_e_w_a_r_e?
+
+     For several years now, the editors of _D_r. _D_o_b_b_s _J_o_u_r_n_a_l
+have  overseen a charity program called _C_a_r_e_w_a_r_e.  Careware,
+in a nutshell, is a way to "give back"	something  to  those
+less  fortunate	in  our  community,  and, at the same time,
+obtain a copy of a popular piece of software featured in the
+magazine  --  simply  by  stuffing  a  dollar or two in your
+floppy mailer for a local charity! It's that easy.
+
+     Now, as part of the DDJ Careware Program, we are making
+available  to  the  editors of DDJ the latest version of our
+"Tiny 386BSD" installation floppy. Even though we have	made
+this  software	freely	available  --  with  no contribution
+required for the use of 386BSD -- we hope  that	the  386BSD
+User  Community	will  choose to participate in this charity
+drive and help the children aided by the _C_h_i_l_d_r_e_n'_s  _S_u_p_p_o_r_t
+_L_e_a_g_u_e _o_f _t_h_e _E_a_s_t _B_a_y.
+
+_W_h_a_t _i_s _t_h_e _C_h_i_l_d_r_e_n'_s _S_u_p_p_o_r_t _L_e_a_g_u_e?
+
+     In this age of "fiscal austerity", many small community
+organizations  --  especially those working with children --
+have been hard-hit by state and local budget cuts.  The	CSL
+is  a  volunteer  organization	which is solely dedicated to
+raising funds for small	local	agencies  which	help  needy
+children.  Some	of  the  agencies which have received funds
+from CSL in the past include those using computers  to	com-
+municate  with disabled children, providing respite weekends
+for abused children, counciling bereaved children, and	set-
+ting  up  safe after-school play areas for children in impo-
+verished neighborhoods.
+
+     Simply put, by sending a dollar or two along with	your
+software  request,  you directly benefit a child. Even if it
+is only a dollar, it does make a difference.
+
+_H_o_w _d_o _I _P_a_r_t_i_c_i_p_a_t_e _i_n _t_h_e _C_a_r_e_w_a_r_e _P_r_o_g_r_a_m?
+
+     To get a labeled copy of "Tiny 386BSD",  send  a  high-
+density	error-free  formatted	floppy	(either	3.5-inch or
+5.25-inch) and a SASE mailer to:
+
+
+386BSD CAREWARE.INFO	 1			July 1992
+
+
+
+
+
+
+
+
+
+
+    Tiny 386BSD
+    DDJ
+    411 Borel Avenue
+    San Mateo, CA.  94402  USA
+
+
+While there is no obligation to participate,  if  you  would
+like to help a disadvantaged child, just include a dollar or
+two (or more, if you so desire) in  your  mailer  and  we'll
+make sure it gets to the Children's Support League.  (If you
+send a check, please make it payable to the "Children's Sup-
+port League of the East Bay").
+
+_A _C_h_a_l_l_e_n_g_e _t_o _t_h_e _3_8_6_B_S_D _U_s_e_r	_C_o_m_m_u_n_i_t_y:  _W_e	_C_a_n  _M_a_k_e  _a
+_D_i_f_f_e_r_e_n_c_e
+
+     Thanks to the generous and enthusiastic response of the
+D-Flat	C-library  users and and X-Sharp 3-D Graphics users,
+the DDJ Careware  Project  has	helped	hundreds  of  people
+throughout the country.
+
+     While a dollar or two may seem like a  trivial  amount,
+it does add up.	The Brevard County Food Bank in Florida has
+received over $3,000 in the past year alone from  supportive
+users  of  D-Flat, and the Vermont Association for the Blind
+and Visually Disabled has received over	$100  in  the	past
+month  from  X-Sharp users. For these charities, a dollar or
+two has made a difference!
+
+     Now it's our turn. Just like the generous users  of  D-
+Flat  and X-Sharp, we believe that each person in the 386BSD
+User Community is quite willing to meet	the  challenge	and
+help  a	child.	We  know  that a dollar or two from 386BSD
+users can make a difference as well.  The  choice,  however,
+is yours.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+386BSD CAREWARE.INFO	 2			July 1992
+
+
+

distributions/386BSD/0.1/386BSD/CONTRIB.LIS

@@ -0,0 +1,196 @@
+
+
+
+
+
+
+
+		     386BSD Release 0.1
+		      Contributor List
+
+		     Lynne Greer Jolitz
+		     William F. Jolitz
+
+
+_H_a_r_d_w_a_r_e _a_n_d _M_o_n_e_t_a_r_y _C_o_n_t_r_i_b_u_t_o_r_s
+
+Many people and firms have provided hardware and/or money to
+try and keep this unfunded project going despite a recession
+and hard times -- usually by digging into their own pockets.
+Each  of  these	contributors  gave,  not  only because they
+believed that the continuation of 386BSD  is  vital  to	the
+health of the research, educational, and development commun-
+ities, but also because they realize that an individual	can
+and does make a difference!
+
+Without the help of the people	listed	here,  this  release
+would  simply  not  have  been possible. We would especially
+like to thank Thos Sumner, whose loan of a  486/50  SCSI  PC
+made  development  go  more rapidly.  The rest of the 386BSD
+user community should make special note of all these  people
+and   firms  and  commend  them	for  their  generosity	and
+foresight.
+
+We hope that their leadership and vision will serve as shin-
+ing  examples to the entire 386BSD user community, and serve
+to encourage others to actively participate in 386BSD.
+
+    Jan van den Bosch
+    Compaq Computer Corporation
+    Cyrix Corporation
+    Dixon Dick
+    Steven P. Donegan
+    Jon Erickson
+    Eric J. Haug
+    Bob McGhee
+    Jesus Monroy Jr.
+    Andrew Moore
+    Rich Murphey
+    Mark Ng
+    Kenji Okamoto
+    John Plocher
+    Mark R. Riordan
+    John B. Scalia
+    Steve Sizemore
+    Thos Sumner
+    David E. Tweten
+
+
+
+
+
+386BSD CONTRIB LIST	  1			July 1992
+
+
+
+
+
+
+
+
+
+
+_S_o_f_t_w_a_r_e _C_o_n_t_r_i_b_u_t_o_r_s
+
+The following people have contributed key software programs,
+modules and fixes, including novel work and ports of popular
+public domain user programs.   Some  of	this  software	was
+directly  contributed  to  us,	while  other items were made
+available to  all  users  via  the  network.   Occasionally,
+several	people	came  up with a variety of approaches for a
+single item. In this instance, we tried to  choose  the	one
+which  we  felt would best serve the rest of the 386BSD user
+base for this release. However, the creativity and persever-
+ance  of all the software contributors trying to make 386BSD
+better for the entire 386BSD user  community  was  consider-
+able. Each individual effort is worthy of pride.
+
+We wish to personally thank all of  these  people,  as	they
+have  helped make 386BSD Release 0.1 a reality. We hope that
+these contributors and all the rest of the 386BSD user	com-
+munity	will continue to actively participate to make future
+releases even better!
+
+    James Van Artsdalen
+    Scott Burris
+    Randall Dean
+    Chris Demetriou
+    Mark Eichin
+    Bruce Evans
+    Steve Ferguson
+    Jeffrey Goh
+    David Greenman
+    Amancio Hasty Jr
+    John W. Hatley
+    Eric J. Haug
+    Tom Ivar Helbekkmo
+    John D. Irwin
+    Peter Klingebiel
+    Paul Kranenburg
+    Daniel Lanciani
+    Karl Lehenbauer
+    Lee M. J. McLoughlin
+    Andrew J. Michael
+    Jesus Monroy Jr.
+    Daniel A. Muntz
+    Richard Murphey
+    Glen Overby
+    Brad Parker
+    Herb Pereyl
+    Ken Raeburn
+    Paul Richards
+    Guido van Rooij
+    Peng-Toh Sim
+    Wolfgang Solfrank
+    Dave Stanhope
+
+
+386BSD CONTRIB LIST	  2			July 1992
+
+
+
+
+
+
+
+
+
+
+    Mark Tinguely
+    Linus Torvalds
+    Richard Tobin
+    Rob Warnock
+    Christian Wiedmann
+    Pace Willisson
+    Joerg Wunsch
+
+    And all of the other 386BSD Software Contributors.
+
+
+_S_u_p_p_o_r_t _a_n_d _A_d_v_i_c_e _C_o_n_t_r_i_b_u_t_o_r_s
+
+Many people have continually encouraged us over	the  course
+of these releases, and provided us with technical advice and
+guidance. These people have also spent considerable time and
+energy	getting	this software out to the rest of the 386BSD
+community.  While it is impossible for us to  list  everyone
+who  has  been	supportive  of 386BSD, we wish to personally
+thank some of the people who have been of special assistance
+to  us	directly  over	the course of getting 386BSD out the
+door.
+
+    Bruce Blakely
+    Dave Campbell
+    Free Software Foundation
+    Paul Fromberg
+    Tom Genereaux
+    John Gilmore
+    Dave Harris
+    Jim Joyce
+    Dan Kionka
+    Dory Leifer
+    Per Lindqvist
+    Marshall Midden
+    Rich Morin
+    Silicon Valley Computer Society
+    John Sokol
+    Thos Sumner
+    Karen Trocki
+    Rob Warnock
+
+    and a special thanks to:
+    John Erickson, Tami Zemel, Ray Valdez, Monica Berg, Michael Floyd
+	    and everyone else at Dr. Dobbs Journal.
+    Juergen Fey, Rainer Huttenloher, Gerd Oskar Bausewein
+	    and everyone else at UNIX Magazin.
+
+    And all of the 386BSD User Community.
+
+
+
+
+
+386BSD CONTRIB LIST	  3			July 1992
+
+
+

distributions/386BSD/0.1/386BSD/COPYRIGH

@@ -0,0 +1,131 @@
+
+
+
+
+
+
+
+		    386BSD Release 0.1
+			 Copyright
+
+
+  /*
+   * Copyright (c) 1989, 1990, 1991, 1992 William F. Jolitz, TeleMuse
+   * All rights reserved.
+   *
+   * Redistribution and use in source and binary forms, with or without
+   * modification, are permitted provided that the following conditions
+   * are met:
+   * 1. Redistributions of source code must retain the above copyright
+   *	notice, this list of conditions and the following disclaimer.
+   * 2. Redistributions in binary form must reproduce the above copyright
+   *	notice, this list of conditions and the following disclaimer in the
+   *	documentation and/or other materials provided with the distribution.
+   * 3. All advertising materials mentioning features or use of this software
+   *	must display the following acknowledgement:
+   *	This software is a component of "386BSD" developed by
+   *	William F. Jolitz, TeleMuse.
+   * 4. Neither the name of the developer nor the name "386BSD"
+   *	may be used to endorse or promote products derived from this software
+   *	without specific prior written permission.
+   *
+   * 386BSD WAS DEVELOPED BY WILLIAM F. JOLITZ.
+   * 386BSD IS INTENDED FOR RESEARCH AND EDUCATIONAL PURPOSES.
+   * THIS SOFTWARE SHOULD NOT BE CONSIDERED TO BE A COMMERCIAL PRODUCT.
+   * THE DEVELOPER URGES THAT USERS WHO REQUIRE A COMMERCIAL PRODUCT
+   * NOT MAKE USE OF THIS WORK.
+   *
+   * FOR USERS WHO WISH TO UNDERSTAND THE 386BSD SYSTEM DEVELOPED
+   * BY WILLIAM F. JOLITZ, WE RECOMMEND THE USER STUDY WRITTEN
+   * REFERENCES SUCH AS THE  "PORTING UNIX TO THE 386" SERIES
+   * (BEGINNING JANUARY 1991 "DR. DOBBS JOURNAL", USA AND BEGINNING
+   * JUNE 1991 "UNIX MAGAZIN", GERMANY) BY WILLIAM F. JOLITZ AND
+   * LYNNE GREER JOLITZ, AS WELL AS OTHER BOOKS ON UNIX AND THE
+   * ON-LINE 386BSD USER MANUAL BEFORE USE. A BOOK DISCUSSING THE INTERNALS
+   * OF 386BSD ENTITLED "386BSD FROM THE INSIDE OUT" WILL BE AVAILABLE LATE 1992.
+   *
+   * THIS SOFTWARE IS PROVIDED BY THE DEVELOPER ``AS IS'' AND
+   * ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+   * IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+   * ARE DISCLAIMED.  IN NO EVENT SHALL THE DEVELOPER BE LIABLE
+   * FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+   * DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+   * OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+   * HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+   * LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+   * OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+   * SUCH DAMAGE.
+   *
+   */
+
+
+  386BSD Copyright		  1			  July 1992
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+  386BSD Copyright		  2			  July 1992
+
+
+
+

distributions/386BSD/0.1/386BSD/DISTRIBU.HOS

@@ -0,0 +1,65 @@
+
+
+
+
+
+
+
+		    386BSD RELEASE 0.1
+		  DISTRIBUTION HOST SITES
+
+
+    agate.berkeley.edu		128.32.136.1
+    gatekeeper.dec.com		16.1.0.2
+    MATH.ORST.EDU		   128.193.16.60
+    UTKUX1.UTK.EDU		  128.169.200.67
+    terminator.cc.umich.edu	 141.211.164.8
+    nic.funet.fi		    128.214.6.100
+    dsuvax.dsu.edu		  138.247.32.2
+    altair.cis.ksu.edu		129.130.10.84
+    hpcsos.col.hp.com		15.255.240.16   [ Internal HP sites only ]
+    math.niu.edu		    131.156.3.4
+    sune.stacken.kth.se		130.237.234.42
+    raquel.doc.ic.ac.uk		146.169.11.3
+    rusmv1.rus.uni-stuttgart.de	129.69.1.12
+    HELIUM.CLUB.CC.CMU.EDU	  128.2.55.10
+    banjo.concert.net		192.101.21.6
+    kirk.bu.oz.au		   131.244.1.1
+    grand.central.org		192.54.226.100
+    pascal.math.fu-berlin.de	130.133.4.50
+    capella.eetech.mcgill.ca	132.206.1.17
+    ftp.ibr.cs.tu-bs.de		134.169.34.15
+    f.ms.uky.edu		    128.163.128.6
+    azathoth.sura.net		128.167.254.184
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+386BSD DISTRIBUTION.HOSTS    1			July 1992
+
+
+