Roger Oberholtzer pecked at the keyboard and wrote:
On Thu, 2008-02-14 at 09:21 +0200, Dave Plater wrote:
Tom Patton wrote: the module loader once and once after each kernel change.
Of course. But if SUSE had left vboxdrv alone, having the 'setup' make a new module, then the SUSE RPM could have done an 'insserv vboxdrv'. Then (1) we would not be having this discussion because everyone's kernel modules would load as expected, and (2) new kernels could be handled by either a new vb rpm, or a simple run of 'vboxdrv setup'. As it stands now, 'vboxdrv setup' from SUSE does NOT remake the module no matter. The code is removed unconditionally from that part of the script. You are running the virtualbox from SUSE's RPM, no?
Dave
Compiling the kernel module when you have the OSE version installed is not necessary as the module is supplied as a separate package. Therefore the code in the init script that was removed was done so for a very good reason. If you are using the OSE version of virtualbox install the kernel module package and you will be all set to go. You don't need the kernel sources installed either. -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org