>>> On Tue, Jun 3, 2008 at 8:02 PM, in message <[EMAIL PROTECTED]>, Patrick Spinler <[EMAIL PROTECTED]> wrote: -snip- > Unfortunately, the vmcp module isn't unloadable, so I can't test this > right now. (Mind, unloading modules can be a bad idea anyway ...)
Eh? It most certainly can be unloaded, at least on my SLES9 SP4, SLES10 SP1, and SLES10 SP2 systems. And unloading modules is certainly not a bad idea. Being able to load and unload them dynamically is one of the reasons why they were created in the first place. Using the recently-introduced --force option when the kernel won't unload a module (because it is in use) is almost always a bad idea, but that's not the general case we're talking about here. Mark Post ---------------------------------------------------------------------- For LINUX-390 subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit http://www.marist.edu/htbin/wlvindex?LINUX-390
