Return to BSD News archive
Newsgroups: comp.unix.bsd.netbsd.misc,comp.unix.bsd.freebsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!yarrina.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.cis.okstate.edu!news.ksu.ksu.edu!news.physics.uiowa.edu!math.ohio-state.edu!howland.reston.ans.net!nntp.crl.com!pacbell.com!gw2.att.com!nntpa!not-for-mail From: dyson@inuxs.inh.att.com (John S. Dyson) Subject: Re: NetBSD camp reaction to OpenBSD? Message-ID: <DJ2JvE.7yM@nntpa.cb.att.com> Sender: news@nntpa.cb.att.com (Netnews Administration) Nntp-Posting-Host: inuxs.inh.att.com Organization: AT&T References: <30B6A790.41C67EA6@FreeBSD.org> <1995Nov29.102918.7769@wavehh.hanse.de> <49tm37$2hs@cnn.nas.nasa.gov> Date: Mon, 4 Dec 1995 15:47:37 GMT Lines: 31 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.netbsd.misc:1479 comp.unix.bsd.freebsd.misc:9805 In article <49tm37$2hs@cnn.nas.nasa.gov>, Jason R. Thorpe <thorpej@lestat.nas.nasa.gov> wrote: >In article <1995Nov29.102918.7769@wavehh.hanse.de>, >Martin Cracauer <cracauer@wavehh.hanse.de> wrote: > >>Well, one thing that seems really more "open" in OpenBSD is public >>readonly CVS access (as advertised, don't know if this is up for >>now). >> >>I'd really like to see this for NetBSD/FreeBSD, too. As an example, it >>would make it much easier to look at John Dyson's work on the VM >>system without having to ask someone to check out all these changes. > >OpenBSD is in an interesting position re. read-only CVS access that the >other (FreeBSD and NetBSD) camps don't enjoy: the code base is >unencumbered. FreeBSD and NetBSD both have RCS files with Net/2 origins. >Some of these files were later found to be (pr possibly be) tainted >with AT&T or otherwise encumbered code. If either project were to allow >the general public to have access to the first revisions of these files, >it could mean legal trouble. > AFAIK, FreeBSD started from scratch with the 4.4Lite sources, we have no CVS history before that. There might have been a leak or two by errant commits being made -- those were corrected, and we took the legal agreement literally. That is the reason that it took us a while to come up with a stable system again (e.g. FreeBSD 2.0 -- the epitome of "stability" :-)). John dyson@freebsd.org