myDSL Extensions (deprecated) :: kernel module extensions

DSL seems like the perfect was to distribute my application (http://owfs.sf.net), especially for the people who have trouble with installation. I already install in /opt with no persistent settings. Perfect! Except...

I have two complications:
1. My application depends on FUSE -- the "filesystem in user space" (http://fuse.sf.net) which is a library and kernel module. Can an extension include a kernel module? Is there an easy way to load it out of the /opt directory? Is the best practce to package it separately, or as part of my application?

2. One USB device needs a modified kernel module. (Basically, the usb-serial ftdi_sio.o module supports the device, but needs the "USB product number" in its list). Is there an easy way to override a kenel module with an updated one?

Thanks for the help. It seems better to ask about these configuration issues before blundering ahead.

Paul Alfille

alfille, I did something similar with the bcm5700.tar.gz package. The modules are in there own sub-directory of /opt, and they get loaded from a menu item with a sudo insmod /opt/bcm5700/bcm5700.o command.

I'm not sure when to use insmod vs modprobe, and I have no idea about over riding modules.

Actually, I have implemented some module support in DSL. It has been an unannounced feature. It basically works like the /optional directory. You make a /modules directory off the root device and then use the boot option modules=hda7 then the boot process will insmod each of the modules in that directory. They will be loaded in alphabetical order. I use this feature when I made the winmodem modules for the thinknic project. It works but uses the insmod and not modprobe. So, you should be able to load additional modules with this method. insmod will only load the module specified while modprobe will load it and other modules that it may depend on, kinda like the apt stuff. So, if you know the order and what you want to accomplish you can use this feature.

original here.