*BSD News Article 14294


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!haven.umd.edu!uunet!psgrain!percy!agora!rgrimes
From: rgrimes@agora.rain.com (Rodney Grimes)
Subject: Re: Periodic Posting, Current patchkit patches for next release
Message-ID: <C57nys.MFr@agora.rain.com>
Organization: Open Communications Forum
References: <1pvn14$4dv@agate.berkeley.edu> <C55I18.1Hv@agora.rain.com> <9304082357.af06134@gate.demon.co.uk>
Date: Fri, 9 Apr 1993 10:04:04 GMT
Lines: 51

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.

Thanks, you just made my day more pleasant, And I would like to thank the
NET at large for slowing down on the email.  I have finally got my inbox
down to size and have made progress towards getting more things into the
next pathckit.  An updated list will be posted before I go to bed tonight,
or err this morning...

>I personally would rather he took his time and made sure we don't get 
>any crud patches.

I have tried to make sure what gets into the patchkit is looked at by
2 or 3 people who have intimate knowldege of what is being patched.  This
is one of the things that keeps cruf out of the patchkit.  I also make sure
that the patchkit gets tested before a public release.  We have found some
glarring bugs that way, in fact right now there is one that may stop a
certain patch that a lot of people want in, but it is broken, and broken
in a bad way.  Jordan is working on getting that fixed for all of us.

This does not mean that crud patches well never happen in the patchkit,
some times they do.  Sometimes there is a situation that only broad
scale testing finds the bugs.  Also some times it is necessary to implement
a stop gap solution to a bug.  There is one or two of those in the next
patchkit for kmem_map panics.  These are not "final" fixes, but make the
problem a lot more livable.  As to the unlimit open file problem and
bash, simple, if X hurts don't do X, do not run your system with
ulimit files, always set it to something reasonable.. Ie 256 or so...

> I know how commercial s/w is ruined by pressure, we don't need this 
> crossing over to 386BSD :-)

Point very well made....  

>Well done chaps, keep up the good work!

I sure well, and if I might speak for the other team members I am sure
they well to.  I need to thank Nate, Jordan, Chris D., Burce Evans,
David Greenman, Julian Elischer and a few dozen other people for helping
with bugs and getting things fixed and checked out.  With out there support
and willingness to turn hatchet work into real fixes none of us would
have what we have today in the patchkit.  And of course a specail thanks
to Terry Lambert for starting the whole idea rolling..

>Damian
-- 
Rod Grimes						rgrimes@agora.rain.com
386BSD patchkit coordinator			      Wish it paid real money!
Accurate Automation Company          All opinions belong to me and my company!