Linux - DistributionsThis forum is for Distribution specific questions.
Red Hat, Slackware, Debian, Novell, LFS, Mandriva, Ubuntu, Fedora - the list goes on and on...
Note: An (*) indicates there is no official participation from that distribution here at LQ.
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.
Mistakenly posted in Distributions. Should be in General, which is where I posted it, but I cannot delete this one.
After fighting to get my system to recognize my US Robotics Linmodem, I decided to read the fine print. It states that the modem is supported with Kernel 2.3 and beyond.
I checked my system and I'm currently running 2.2.16 (straight off the RH disks). I searched the CDs and found beta versions of 2.4.0 packaged as RPMs.
I've read the man pages and several other articles on RPM and have followed the directions, e.g.:
#rpm -ivh kernel.2.4.0-0.xx.i386.rpm
and all of the files were unpacked and put in /lib/modules/2.4.0/ .
At this point I cannot do anything with the data. I have followed the standard procedures to compile a kernel and have found afterwards that the bzImage does not exist.
My understanding is that the RPMs are packages that either update, patch, or install a program. Does this not work with a kernel?
If that's the case, then that brings up other questions. I've just finished reading about using kgcc instead of gcc. How can I make sure that kgcc is being used when I compile the kernel? Would I delete gcc and then symbolically link gcc to kgcc? Or what would be the best way to go about doing this?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.