>Great! I installed the deb off the repository. >Now it is time to place the module in a separate source package that can be >compiled and installed using m-a.
>The old postinst method worked on each kernel after I booted it (yes, there >are those of us playing with more than one host kernel!). The new method, in >my mind more convenient, does NOT. Only works for the first kernel on which >it is used. My old trick of vi-ing the module and changing the >"magic" (provided that string is the same length) also did not work. >m-a takes care of all of this correctly. /etc/init.d/vboxdrv setup needs >similar arguments or reading the current kernel (uname, other tools) to set >itself up correctly. OK, it is looking in /usr/src/linux no matter what. Pointing this to the sources of the target kernel works fine. I found this out by running the script in the $INSTALDIR/src directory :-) Sometimes hiding output hides too much. The script might check uname against /usr/src/linux and complain (there are symlinks in the modules that point back to the source tree, I believe). m-a does accept arguments and can set things up correctly but I have found that /usr/src/linux had better point to the target kernel's source directory anyway or certain things will be changed in where it does point incorrecctly. I filed a bug at Debian about this but was not believed :-) _______________________________________________ vbox-users mailing list [email protected] http://vbox.innotek.de/mailman/listinfo/vbox-users
