I think I might have a handle on it... I line item
checked my lilo and the wrong initrd was associated
with vmlinuz. I don't know when that happened though,
maybe the first busted kernel upgrade where I lost the
groups and everything else.
We shall see with the next update....
--- SI Reasoning <[EMAIL PROTECTED]> wrote:
> Same problem continues....
> -------------------
> > >Possibly could be the fact there is a initrd and
> an
> > >initrd.img. initrd.img is the one linked
> (correctly)
> > >to 2.4.8-17mdk while initrd is linked (correctly)
> to
> > >an older kernel. Should I delete initrd?
>
> > yes, please.
> I did, still have same problem with 18. This problem
> has only surfaced in the last few updates. It was
> working fine for awhile. I do have other initrd's
> from
> backup kernels (in case something goes wrong) but
> those are like initrd-2.4.3-27mdk. Some are linked
> to
> copies I keep in backup directories, but it should
> not
> really affect the script... it had not in the past.
>
>
> =====
> SI Reasoning
> [EMAIL PROTECTED]
> gnupg/pgp key id 035213BC
>
> __________________________________________________
> Do You Yahoo!?
> Get email alerts & NEW webcam video instant
> messaging with Yahoo! Messenger
> http://im.yahoo.com
>
=====
SI Reasoning
[EMAIL PROTECTED]
gnupg/pgp key id 035213BC
__________________________________________________
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.yahoo.com
