SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
i just recompiled my kernel. but the lilo.conf file which i edited and ran /sbin/lilo is in my secondary hard disk (i dual boot Win98). i use a floppy boot to get to slack as lilo somehow corrupts my MBR.
my boot floppy was made during the initial install. i'm wondering now... is it booting up to my new re-compiled kernel or the old default one? if it's booting up to the old one, how do i get it to boot to the re-compiled kernel?
i tried to do a ls on the boot floppy but gives me this error:
EXT2 - fs error (device fd(2,0)) ext2_readdir: bad entry in directory #2: rec_len is smaller than minimal - offset=0, inode=0, rec_len=0, name_len=0
which er... reverts me back to the orignal question. does the floppy boot up to the newly re-compiled kernel or to the old one? (what i'm trying to say is does it read the lilo.conf found in my secondary hard disk where slack is installed?)
kinda important coz i'm troubleshooting my sound on slack.
the modprobe sound works fine, but when i try to play something on xmms, it still tells mw that either the device is busy (which it shouldn't be coz it doesn't even play the kde error beeps) or my sound card is not configured properly.
when i do a
modprobe sb io=0x220 irq=5 dam=1 dam16=3
it tells me that the device or resource is busy... why is this?
If you want to have the same kernel on a floppy like you have on your system, after you have compiled your kernel you can give this command:
cp bzImage /dev/fd0
Of course you have to be in the same dir where your bzImage resides or put the pathname to your freshly compiled bzImage in the cp command. Also, no mounting of the floppy is necessary.
This makes you a bootable disk without lilo but with the kernel you had just built.