Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!uunet!gatech!usenet.ins.cwru.edu!agate!agate.berkeley.edu!cgd
From: cgd@eden.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Recompiling Kernel (NetBSD)
Date: 13 Jun 93 13:48:48
Organization: Kernel Hackers 'r' Us
Lines: 50
Message-ID: <CGD.93Jun13134848@eden.CS.Berkeley.EDU>
References: <1ve2of$a3@stimpy.css.itd.umich.edu> <3607@bigfoot.first.gmd.de>
NNTP-Posting-Host: eden.cs.berkeley.edu
In-reply-to: ats@bsd386.first.gmd.de's message of 13 Jun 93 11:30:00 GMT
In article <3607@bigfoot.first.gmd.de> ats@bsd386.first.gmd.de (Andreas Schulz) writes:
PS: And a light flame to the netbsd people :-), wasn't one of things
that you want to bring out a stable system, and weekly or at last
monthly functional systems ? Sorry, but in the moment, it doesn't
look so :-). Boot floppies with errors, a snapshot of a source
tree, where no one knows, if all things are running with the
other sources, and all day new changes in some interfaces :-).
But keep on with the work :-).
we *did* supply a stable system. that's NetBSD 0.8, and
it works, modulo bugs which we hadn't fixed at the time.
no, *NOT* weekly or montly "functional systems" weekly or
monthy *diffs* from the last release.
there is simply not enough time in a week to *do* a full release
every week, and certainly not enough interest.
we've (partially) gotten around the diffs problem by
updating the "netbsd-current" tree nightly, and
makeing tarfiles of it weekly.
also: note that we never said that using the "current"
sources would be either easy or straightforward. in fact
we said just the opposite. (right now, the "current"
tree is fairly unstable, for various well-known reasons,
as well.)
as for finding out what changes we've made:
the changes file documents it pretty well.
please, don't forget:
NetBSD 0.8 was released... ONE MONTH AND THREE WEEKS AGO,
and we're planning another release (probably "0.8A")
for after usenix probably around 7/20.
it's not like we're talking about six months or a year, here,
and it's not like anyone has volunteered to do release engineering.
chris
--
Chris G. Demetriou cgd@cs.berkeley.edu
"386bsd as depth first search: whenever you go to fix something you
find that 3 more things are actually broken." -- Adam Glass