*BSD News Article 9668


Return to BSD News archive

Received: by minnie.vk1xwt.ampr.org with NNTP
	id AA6247 ; Wed, 06 Jan 93 07:03:00 EST
Xref: sserve comp.os.mach:2487 comp.unix.bsd:9725 comp.os.linux:21950
Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!ames!nsisrv!Pt!john
From: john@Pt.hq.af.mil (John Ryan)
Newsgroups: comp.os.mach,comp.unix.bsd,comp.os.linux
Subject: 386BSDSS Porting Effort -- Volunteers
Keywords: BSDSS, Volunteers
Message-ID: <15820@hq.hq.af.mil>
Date: 8 Jan 93 18:19:20 GMT
Followup-To: poster
Organization: Headquarters Air Force, The Pentagon Washington, DC
Lines: 47

Hi,
	After reading everything it seems apparent that no-one
is going to be releasing the BNR2SS code for a vanilla 386 PC, 
so some friends and I have decided to start doing it ourselves.  
If I am wrong and some people are already working on a single 
server for the 386 please tell me and we will join your effort, 
otherwise...We are looking for volunteers to help us. As I see 
it these are the things that need to be done.

	o get an archive site (not CMU)
	o get a wd subsystem for i386
	o fix the makefiles for mach
	o hack 386BSD 0.1 (0.2 when available)

First, the archive site, as a last resort we would be willing to
do this, but other people will be annoyed at milnet.  The archive 
should place everything under RCS so that we avoid the version
chaos that applies to most volunteer efforts.

Next, a wd subsystem, look everyone has 386 PC's so we need to write
for IDE drives on AT bus's. There are drivers in linux, 386BSD and 
elswhere, these "just" need to be systematized for mach. (Of course
if you have good starting points for this we would be very glad to hear
from you)

The makefiles need overhauling so that gnu make will work. Sure the
hurd people have something but it builds the hurd not BSD4.3 on top
of mach. That doesn't mean we can't lean heavily on them just means
we can't scoop up their stuff wholesale.

Lastly, we need to hack 386BSD in the same way as was done at CMU 
but not under their auspices.  This means we have faith that if we
do it for research purposes that nothing bad will happen to us. I 
believe that although GNU is doing almost the same thing that the
copyleft is too restrictive and that our port should have a true PD
copyright.

All comments, hints, flames welcome.

John Ryan -- john@hq.af.mil

P.S. Please try and respond by E-Mail I will summarize. Thanks in advance.
-- 
-------
John Ryan             john@hq.af.mil        ..uunet!hq!john