[vox-tech] Kernel Panic

[Bill Wells]

I recommend that anyone using a Linux distro subscribe to as many of the 
distro mailing lists (particularly those that mention security) as 
he/she/it feels may apply to their particular situation.  If too many are 
subscribed, you can always unsubscribe

They serve not only as a sanity check, yep, somebody else has the same 
problem, it ain't just me, but keep you up to date on other distro 
problems/development.

I am an old suse user (currently Slackware) and have not unsubscribed from 
all of suse's lists yet.  (sometimes make for interesting reading).  I had 
sent the msg I forwarded to kmail trash about 5 minutes before I a link was 
established between um, suse 9.2, and kernel panic.  was able to rescue it 
before session end.  

Merry Christmas to all!

Bill Wells


On Friday 24 December 2004 11:22 am, Rod Roark wrote:


.> On Friday 24 December 2004 10:01 am, Bill Wells wrote:
> > From the suse security announcements mail list
> >
> > could this shed any light on the problem
>
> Yes indeed - nice find!  I was wondering what the "-um"
> stuff was.  So the fix would be the second of my suggested
> alternatives:
>
> On Thursday 23 December 2004 10:00 pm, Rod Roark wrote:
> ...
>
> >   cd <mountpoint>/boot
> >   rm initrd
> >   ln -s initrd-2.6.8-24.10-default initrd
>
> By the way initrd stands for "initial ramdisk".  It's where
> kernel modules needed at boot time are stored, and makes it
> possible (for example) to boot from a reiserfs filesystem
> even though reiserfs is not statically compiled into the
> kernel.
>
> -- Rod
> _______________________________________________
> vox-tech mailing list
> vox-tech at lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech