Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-23 Thread Kenneth Macdoald Karlsen
On Fri, 2004-04-23 at 05:39, Derek Broughton wrote: > From: "Kenneth Macdoald Karlsen" <[EMAIL PROTECTED]> > > [sorry Kenneth if you got a private copy. my bad...] > > > On Thu, 2004-04-22 at 20:41, Richard Weil wrote: > > > > > > The source for 2.6.5 came into Sarge a day or two ago. > > > I co

Re: Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-23 Thread Jamin W. Collins
On Fri, Apr 23, 2004 at 05:13:33AM -0700, Richard Weil wrote: > I guess there could be a bug. I'll file a bug report > against 2.6.5, though it seems like such an odd > problem. I've already filed a bug against 2.6.5[1] for something similar, it's since been reassigned to initrd-tools. [1] - http

Re: Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-23 Thread Richard Weil
I guess there could be a bug. I'll file a bug report against 2.6.5, though it seems like such an odd problem. Richard --- Mike Chandler <[EMAIL PROTECTED]> wrote: > I have been able to duplicate the problem you > describe, to the letter. > But, I can't say why, or what to do about it. > You're no

Re: Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-22 Thread Mike Chandler
I have been able to duplicate the problem you describe, to the letter. But, I can't say why, or what to do about it. You're not alone! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-22 Thread Richard Weil
I used all the right options, like --initrd, when building the kernel. I've been building my own kernels for awhile, and actually only recently switched back to using debian sources, and I've never had a problem like this before. Of course it's on the remote machine, so my diagnostics are limited .

Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-22 Thread Derek Broughton
From: "Kenneth Macdoald Karlsen" <[EMAIL PROTECTED]> [sorry Kenneth if you got a private copy. my bad...] > On Thu, 2004-04-22 at 20:41, Richard Weil wrote: > > > > The source for 2.6.5 came into Sarge a day or two ago. > > I complied it using the exact same configuration as > > 2.6.4. I checked

Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-22 Thread Jamin W. Collins
On Thu, Apr 22, 2004 at 11:41:35AM -0700, Richard Weil wrote: > A 2.6.4 versus 2.6.5 oddity in Sarge ... > > I have a hosted machine that is running Sarge with a self-compiled > 2.6.4 kernel. The kernel matches the hardware very well, the kernel > was made using kpkg, and update-grub is linked int

Re: 2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-22 Thread Kenneth Macdoald Karlsen
On Thu, 2004-04-22 at 20:41, Richard Weil wrote: > A 2.6.4 versus 2.6.5 oddity in Sarge ... > > I have a hosted machine that is running Sarge with a > self-compiled 2.6.4 kernel. The kernel matches the > hardware very well, the kernel was made using kpkg, > and update-grub is linked into the proce

2.6.4 to 2.6.5 problems w/ a sarge machine

2004-04-22 Thread Richard Weil
A 2.6.4 versus 2.6.5 oddity in Sarge ... I have a hosted machine that is running Sarge with a self-compiled 2.6.4 kernel. The kernel matches the hardware very well, the kernel was made using kpkg, and update-grub is linked into the process of installing or uninstalling a kernel. The source for 2.