Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!aardvark.ucs.uoknor.edu!ns1.nodak.edu!netnews.nwnet.net!usenet.coe.montana.edu!
saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!caen!kuhub.cc.ukans.edu!husc-news.harvard.edu!husc.harvard.edu!haley
Newsgroups: comp.os.386bsd.misc
Subject: Re: 386BSD Release: Contributors Only Please...
Message-ID: <haley.738086416@husc.harvard.edu>
From: haley@scws5.harvard.edu (Elizabeth Haley)
Date: 22 May 93 16:00:16 GMT
References: <1te9h8$8fn@agate.berkeley.edu> <almC7BGLz.EDM@netcom.com>
<1tggls$oqi@agate.berkeley.edu> <CGD.93May22022324@gaia.CS.Berkeley.EDU> <C7FKJw.CMJ@moxie.hou.tx.us>
Nntp-Posting-Host: scws5.harvard.edu
Lines: 92
In many ways I agree with Gene, it would be nice if you guys could
work together... If not as a united front, at least as three
recognizable facets of one stone: BSD.
What I am confused about is the intention of each group, save for
BSDI, whose intention, like any business, is to make money. I would
suppose that would mean it's aims are compatibility and expandibility
and most of all stability, so their customers get the most for their
money...
After that, there appears to be *3* groups: 386bsd-Jolitz (Headed by a
pair of Jolitzen :-)), 386bsd-interim (Headed by Nate?) and NetBSD
(Headed by cgd) [note the "Headed by" more means coordinated,
dictionary-flames > /dev/null]
Now, the impression that I am under is that evaluating the various
releases as to "Best" is like comparing golden and red delicious
apples... They're both tasty...
It comes down to this: Where are they going?
Bill and Lynne apparently started this project with an eye towards
experimental work. I like this idea...
However, I was under the impression that NetBSD was to have an eye
toward stability...
As to 386bsd-interim, I think is was a "best-of-both-worlds"
approach...
But then the other day, I thought I saw a post from cgd suggesting
that NetBSD was to be experimental too?
AAAAAAAAAAUUUUUUUUGGGGGGGGGGHHHHHHHHHHHHHHHHHH!!!!!!!!!!
Can I suggest something? Could the coordinator of any applicable group
send out a post to this group answering the following questions?
1. What is your package's specific primary goal(s)?
example: improvement to various interface to fit current and near
future technology
2. Current projects that would lead to that goal:
example: "Improved virtual memory system, improved mass media device
interfaces and drivers"
3. What will determine your public interfaces?
example: POSIX
example: We will maintain library compatibility with the current
release of vanilla BSD
example: Our interfaces and formats will change, so stating a standard
is not possible at this time.
4. How often will you make a public release, and in what form?
Example: We will release diffs and patches approximately weekly.
example: We will release the entire distribution and diffs to the last
entire distribution, whenever we have completed work on a major facet
of research.
5. How will you deal with code offerings (patches and new drivers or
utilities)
example: patches will be cursorily tested and then released with the
next patchkit
example: all offerings will be evaluated for their suitability for
inclusion in the next major release... patches used will be attributed
and patches not used will dumped. You may assume patches were not used
because the system in question had changed to the point that the patch
was no longer applicable...
A note to the rest of the world: Keep your judgement to yourself!
Much as many of us like to debate the finer points of any plan, code,
or article, USENET would be a better laboratory is there were more
labor and less oratory.
If you simply must say something about a response to these posts, send
them directly to the posters. I, for one, am tired of seeing posts
where the main point was not to enlighten the readership but to make a
childish public jab.
Thank you for your time.
--
If you love your fun...
|[{(<=--=>)}]|David Charles Todd, tHE mAN wITH tHREE fIRST nAMES|[{(<=--=>)}]|
|||||||||||||||||||||||||hacksaw@headcheese.daa.uc.edu||||||||||||||||||||||||
...Die for it!