Re: Failure on today's CVS (stable, AMD)

2005-01-25 Thread Michael R. Wayne
On Wed, Jan 19, 2005 at 07:19:49PM -0800, Doug White wrote: > On Wed, 19 Jan 2005, Michael R. Wayne wrote: > > > CVS today. Dual Opteron running > >5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > > > Following the instructions in UPDATING, I get the following, > > indicating a bad kernel. 2

Re: Failure on today's CVS (stable, AMD)

2005-01-20 Thread Kevin Oberman
> Date: Thu, 20 Jan 2005 10:12:04 -0600 > From: Scot Hetzel <[EMAIL PROTECTED]> > Sender: [EMAIL PROTECTED] > > On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne > <[EMAIL PROTECTED]> wrote: > > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > > and the box is up BUT I am

Re: Failure on today's CVS (stable, AMD)

2005-01-20 Thread Xin LI
Hi, Michael, å 2005-01-19äç 16:42 -0500ïMichael R. Wayneåéï > 2) More importantly, I recovered by loading /boot/kernel.old/kernel >and the box is up BUT I am concerned that the NEXT time that I >do "make installkernel" I'll stomp on kernel.old losing this fallback >procedure. I can ce

Re: Failure on today's CVS (stable, AMD)

2005-01-20 Thread Scot Hetzel
On Wed, 19 Jan 2005 16:42:29 -0500, Michael R. Wayne <[EMAIL PROTECTED]> wrote: > 2) More importantly, I recovered by loading /boot/kernel.old/kernel > and the box is up BUT I am concerned that the NEXT time that I > do "make installkernel" I'll stomp on kernel.old losing this fallback > proc

Re: Failure on today's CVS (stable, AMD)

2005-01-19 Thread Doug White
On Wed, 19 Jan 2005, Michael R. Wayne wrote: > CVS today. Dual Opteron running >5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 > > Following the instructions in UPDATING, I get the following, > indicating a bad kernel. 2 questions: > > 1) Is this a known, corrected issue as of today? I ran ano

Failure on today's CVS (stable, AMD)

2005-01-19 Thread Michael R. Wayne
CVS today. Dual Opteron running 5.3-STABLE #3: Tue Nov 30 01:44:05 EST 2004 Following the instructions in UPDATING, I get the following, indicating a bad kernel. 2 questions: 1) Is this a known, corrected issue as of today? I ran another CVSUP and did not see any changed to src. 2) Mor