Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!agate.berkeley.edu!cgd
From: cgd@toe.CS.Berkeley.EDU (Chris G. Demetriou)
Newsgroups: comp.os.386bsd.bugs
Subject: Re: Periodic Posting, Current patchkit patches for next release
Date: 9 Apr 93 01:51:08
Organization: Kernel Hackers 'r' Us
Lines: 53
Message-ID: <CGD.93Apr9015108@toe.CS.Berkeley.EDU>
References: <1pvn14$4dv@agate.berkeley.edu> <C55I18.1Hv@agora.rain.com>
<9304082357.af06134@gate.demon.co.uk>
NNTP-Posting-Host: toe.cs.berkeley.edu
In-reply-to: damian@centrix.demon.co.uk's message of Thu, 8 Apr 1993 21:29:34 +0000
In article <9304082357.af06134@gate.demon.co.uk> damian@centrix.demon.co.uk (damian) writes:
>I would like to say to Rodney and his pals at the 386BSD patch team, that
>I appreciate everything they are doing very much.
can't argue with this... 8-)
>I personally would rather
>he took his time and made sure we don't get any crud patches.
i'd rather see patches ASAP (or on a reasonable schedule).
if you'd like to be on the bleeding edge, then, at least, you've got
the option to be... on the other hand, if you want to run
a stable system, you stay a few sets back...
>I know how
>commercial s/w is ruined by pressure, we don't need this crossing over to
>386BSD :-)
no, but there's one major difference between (most... 8-)
commercial software, and 386bsd:
most commercial software is *stable*, mostly...
there are lots of *stupid* problems and instabilities in
386bsd which are only now being solved; people should have
the opportunity to play with them as soon as they become
available...
basically, the "kill the engineer" problem comes up --
the people working on this software, me included,
would love to see it *perfect*. the reason that i've
not done an interim release yet is *exactly* that...
however, at some point, you've gotta draw a line,
and say "it's a wrap". you can't get everything
right, no matter how hard you try.
and there's always "next week"...
(or next day, if it's really serious...)
chris
who's not flaming, just sorta exposing another point of view,
which, i feel, has been largely ignored by developers of 386bsd,
especially those working on the patchkit, and WFJ himself...
--
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