I am not sure, but I think this is a problem with devfs and cdroms ... I saw it before when my work machine was hosed, anyway, try creating the devfs nodes for your cdrom in your normal /dev directory if you are not using devfs. That would be "mknod /dev/cdroms/cdrom0 b <maj> <min>", where "<maj> <min>" are the numbers to the left of the date on /dev/hdc, or whatever your cdrom is.
The only difference I saw in my messages was that it said "super.c:241" instead of "super.c:274" ... --- Dave Seff <[EMAIL PROTECTED]> wrote: > I too have had trouble with super.c the same thing happens when I do a df. > -Dave > > On Monday 29 October 2001 06:15, you wrote: > > >>>>> "gary" == Gary Lawrence Murphy <[EMAIL PROTECTED]> writes: > > > > gary> This is the first time this has happened, but it seems to point back > > to gary> super.c (my whole reason for upgrading the kernel ;) > > > > Is that with a new kernel (i.e. major than 2.4.8-29mdk, or with a > > recent cooker kernel, > 2.4.12-5mdk?). It is supposed to be fixed in > > that two kernels, if that is not true, I really will want to know. > > I haven't been able to reproduce it here. > > > > Later, Juan. ===== ________________________ Eugenio Diaz, BSEE/BSCE Linux Engineer [EMAIL PROTECTED] __________________________________________________ Do You Yahoo!? Make a great connection at Yahoo! Personals. http://personals.yahoo.com
