Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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 written a (very) simple script to swap two sets of driver modules for my wireless card. One set allows promioscusous mode (foruse with Kismet etc.) the other does not (as required by xsupplicant).
Once the new drivers have been copied to /lib/modules/etc etc I have to reboot to allow the changes to take effect.
Is there an elegant way to do this? Should I be looking to modprobe -r the driver modules, then reinsert the new ones, or is there some command to reload all modules?
Will the kernel take this sort of abuse, or is it the equivalent of having the carpet pulled out from under it?!
That all depends on whether module unloading has been compiled into your kernel. I have unloaded kernel modules before without too many ill effects. It probably also depends on the frequency with which you will be switching modules. Once a day vs. once every fifteen minutes could be a HUGE difference.
Is it a kernel you compiled yourself or is it a stock Debian kernel?
Actually, you'll know if your kernel supports unloading by trying to remove a module using "rmmod" and then the kernel module name. If it fails (assuming you actually specified a module that was loaded ), then perhaps your kernel doesn't support it as is.
Now you've reached my limit for helping you since you are using Debian. In Slack, you would issue a
command. This would stop the PCMCIA card and then I would imagine you could unload the appropriate modules. I'm not sure how to tell the PCMCIA system to stop in Debian. Perhaps Google can help you out here.