Linux - HardwareThis forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with 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 have dug out my old Zip 100 (paralell port) drive from my closet (also found many Zip disks I could use hehe). Any way, I've tried to get it to work (and actually did, see later). I use Red Hat 9, I have upgraded to the latest kernel (RH's official) 2.4.20-19.9. I'm able to load the module via modprobe or insmod, but if I create an entry for the drive on fstab and then reboot my computer (I actually shut down my system every time I'm done working on it) the fstab entry will be lost and I end up having to re-do the modprobing-fstab-add thing.
However when I first compiled kernel 2.4.21 and told the configuration to build the module ppa into the kernel, everytime the computer booted it was there. My question is simple... what could I possibly did when I compiled that kernel that in my current build of 2.4.21-ck3 kernel the drive is not recognized? I'm not worry about the problem with the Red Hat kernel I can always modprobe and mount /dev/sda4 (BTW how can I make a user be able to mount without any fstab entry?).
Anyway if I end up with a problem remotely similar to that of the RH kernel, how could I force the module to load at boot?