*BSD News Article 8865


Return to BSD News archive

Path: sserve!manuel.anu.edu.au!munnari.oz.au!uunet!mcsun!sun4nl!tuegate.tue.nl!svin09!wzv!gvr.win.tue.nl!guido
From: guido@gvr.win.tue.nl (Guido van Rooij)
Newsgroups: comp.unix.bsd
Subject: Re: call for sources for new interim release of 386bsd
Message-ID: <4174@wzv.win.tue.nl>
Date: 7 Dec 92 19:00:19 GMT
References: <1992Dec7.095032.20075@tfs.com>
Sender: news@wzv.win.tue.nl
Lines: 62

julian@tfs.com (Julian Elischer) writes:
#Well it looks like we are going to put out an interim release 
#of 386bsd with all known patches and drivers etc.

That sounds great. But is it already known when 0.2 will hit the net?
If that is not likely to happen within a few months then this sounds
a good idea to me. 
I just hope that this interim release won't mean another complete
installation. Therefore I would suggest (if it's possible) to also
put it in somekind of patchkit form. Would that be possible?

#if you have ported a driver to 386bsd or a package to 386bsd
#that you think should be part of the release, then
#please mail me (julian@ref.tfs.com) with a brief description
#of what you have.

#I will contact you when I am ready to integrate your module.

#--- module format guidelines---

#Non kernel modules should be in a subdirectory as follows:
#<name>/Makefile
#<name/<name-version>
#<name/<name-version>/[original source tree]

#The top makefile should have build, install, clean and uninstall
#options. I expect that the build and clean options will probably
#just call the makefile in the original source tree with the appropriate
#arguments.

#The tree should be capable of compiling independent of where it is put.

#Kernel modules:
#If your module replaces another module, then please
#set it up so the original module may still be compiled in
#depending on a configuration file setting.

#please include MAKEDEV entries.

#I may have to move devices around a bit it we have clashes.

#as I don't have every device I will probably ask you to take back
#a built copy of the kernel to test when I have integrated
#all the drivers, so you can test your driver.

#------------------------------------------

#Others: if you think of something that needs to be done
#on a new release do mail me 
#(e.g. probably a bigger more complete disktab file)


#+----------------------------------+       ______ _  __
#|   __--_|\  Julian Elischer       |       \     U \/ / On assignment
#|  /       \ julian@tfs.com        +------>x   USA    \ in a very strange
#| (   OZ    ) 2118 Milvia st. Berkeley CA. \___   ___ | country !
#+- X_.---._/  USA+(510) 704-3137(wk)           \_/   \\            
#          v

Succes with it!

-Guido