Resend Sorry. Forgot the bug. On Fri, 2005-04-08 at 23:16 -0700, Steve Langasek wrote: > Hi Greg, > > On Tue, Apr 05, 2005 at 10:17:49PM -0400, Greg Folkert wrote: > > I can arrange an account with sudo access. > > > As long as we do the account info off-bug. > > > On Tue, 2005-04-05 at 18:06 -0700, Steve Langasek wrote: > > > Hi Greg, > > > > > > Apologies for the dormancy on this bug; yours is one of several RC bugs on > > > initrd-tools that have been long in the resolving, so it's not just you... > > > FWIW. :) > > > > > > You mentioned being able to get access to this machine for debugging. Is > > > that still a possibility? > > > > > > Thanks, > > Bad news... I can't reproduce this problem, even on your machine. :) Can > you tell me what kernel you were running at the time you saw the problem? > Your initial report was from a machine that was running 2.4.27-1-smp, so I > assume you got this kernel working using MODULES=most in mkinitrd.conf and > then reported the bug; does that agree with what you recall of the > situation? Well, that kernel that is currently running also has this problem. You need to compare the modules sym53c8xx and sym53c8xx_2, you will see they are the same module, different location. > I suspect this problem was caused by a module name change in the kernel, > where earlier you might have been using sym53c8xx instead of sym53c8xx_2, so > the wrong driver name was detected based on which module was currently > running. Fixing this in initrd-tools therefore probably means introducing > some special-casing to mangle this module name according to the selected > kernel version. This is probably what the problem is. But, I still have noticed, that installing any kernel still gets this error. You can go ahead and remove and re-install any kernel you want. If you do this, I am sure you should be able to discover it. I can recover with tftp booting, so it shouldn;t be to bad. > If you are still able to reproduce this bug on your system, please let me > know how it's manifesting, in case I'm overlooking something. I am sure, that (re)installing any kernel will give you the problem. I have given you sudo access and in the sudo group. I only ask that you don't screw up /home if you need to I can re-back it up. Pretty much the whole reason I couldn't let you in, was the firewall changes would have made a service interruption for us. I had to open undead up to more than one external host for ssh. You realize, the reason it is called undead, the machine was built on July 10, 1994 shipped to the company I worked at. I have been the admin for that machine since then. They took it out of commission and gave it to me. If you still cannot reproduce it, lemme know, I should be able to. -- greg, greg@gregfolkert.net The technology that is Stronger, better, faster: Linux
Attachment:
signature.asc
Description: This is a digitally signed message part