if a kernel from 2 or 3 weeks ago worked for you, then you could
check out the sources from a month ago and build a kernel from that tree.
see the "-D" option to cvs checkout or cvs update.

when I update a machine with a -current kernel, I always save the
most recent kernel or two that worked well so that I have something
to fall back on if the new one has problems.  you really ought to be
doing this too if you're going to be running -current on production machines.

-Chuck


On Wed, Oct 31, 2001 at 01:14:04PM +0100, Xavier HUMBERT wrote:
> In message <20011026200311.A20715@spathi.chuq.com>,
> Chuck Silvers wrote:
> 
> >if you haven't had any problems with the old pmap, don't switch to the new one.
> >these pmap bugs are the sort that seem to only affect some people and not
> >others.  I've never had any problems with either pmap myself, but then
> >I don't do much with my powermac.
> 
> Well, it used to work reliably since, approx 2/3 weeks. Something
> changed, but what? And how to get a NetBSD box that prevents me to get
> back to the office on Sunday ?
> 
> Downgrading to 1.5.2 is not an answer, while since 1.5. is out, i use
> -current, sometimes had compile problem, but never had stabitilty
> problems.
> 
> I used to say (and that was true) that a -current NetBSD is more stabhle
> than a release Linux.
> 
> 
> -- 
> Xavier HUMBERT  -  Systemes et Reseaux     |     labo-info@injep.fr
> INJEP                                      |     humbert@injep.fr