SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
It didn't strengthen his point - it weakened it. I would say that the worst wars and bloodshed in history have all occurred in civil wars rather than wars between nations. In fact "rebels" often enough become "terrorists" because of their military impotency.
Also at what point did I say anything about anyone being with us or against us?
Is this Snow a relative of yours that you should take such umbrage at a challenge to his assertion?
Excuse me; please take your discussion to a more appropriate place.
Now, if someone would like to politely answer my question: do you think I need to change anything from my current configuration? Again, I installed the generic 2.6 kernel from the slackware .tgz package; then I copied in the huge26.s bzImage and made the initrd. It would seem that I'm using the huge26.s kernel with the generic set of modules. Is that how it's supposed to work?
No, you don't need to change anything ... as long as it all works. Note that the modules that you installed work for any kernel of the same version number ... this means they work for both huge26.s and the generic 2.6.x kernel. So, everything should be just fine.
Remember ... if it ain't broke, don't fix it
BTW, I use the same trial and error strategy that you use to figure everything out ... that's why I fail so often, but also succeed where others fail
Last edited by H_TeXMeX_H; 01-12-2007 at 06:07 PM.
Thanks for the replies. I figured "if it ain't broke..." but wondered if there was a reason to think it will break
The strangest thing was that the kernel discovered a network interface called sit0 -- that was the first time I'd ever seen that. Before when I installed the huge26.s kernel it couldn't even detect eth0 (this was before installing the modules occurred to me).
Well, I've gotta go look up what the heck sit0 is...
Joel
thanks for posting your problem and solution. here is a great free resource I just found on digg that you may find useful in future Kernel explorations - Linux Kernel in a Nutshell:
Quote:
Written by a leading developer and maintainer of the Linux kernel, Linux Kernel in a Nutshell is a comprehensive overview of kernel configuration and building, a critical task for Linux users and administrators.
Sweet -- thanks for the link. I'm glad you enjoyed my story: that was my primary purpose of posting it. I want to let people know that a kernel panic is not a big deal: you should always have a way of booting another kernel, either a LiveCD, boot-floppy or another LILO entry.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.