Jeremy A. Rosengren wrote: > man modprobe > > " -r --remove > This option causes modprobe to remove, rather than insert > a module. If the modules it depends on are also unused, modprobe > will try to remove them, too. Unlike insertion, more than one module > can be specified on the command line (it does not make sense to > specify module parameters when removing modules). > > There is usually no reason to remove modules, but some > buggy modules require it. Your kernel may not support removal of modules. Warning: I had an answer prepared earlier, showing how you could automate the removal of all modules marked as "Used by 0" in lsmod's output. Then I tried it out. And discovered that I had af_packet[1] compiled as a module, and was marked as "used by 0". I was logged onto this machine through ssh, and suddenly discovered all my sessions were logged out... "But that always used to work..." So I didn't get to post that answer. James. [1] If that's not obvious, af_packet is the packet filter, a.k.a. the firewall. -- E-mail address: james@ | "A child of 5 could understand this! westexe.demon.co.uk | Fetch me a child of 5."
