I'm experimenting with the mISDN driver, so I frequently exchange the fritzcapi driver and this mISDN driver. For the latter I wrote an init script that simply loads the needed modules. I also have some special pppd init script that needs some kind of capi layer. IMHO it would be a clean solution to have /etc/init.d/capi renamed to capi4k or something like this, and introduce a new virtual dependency "capi" that could also be provided by mISDN.
currently I have an ebuild in testing for misdn: http://genstef.homelinux.org/misdn-20050409.ebuild and for files/: http://genstef.homelinux.org/misdn.modulesd the modulesd file cares for that the modules are loaded in the right order. It should work to just add your driver name to capi.conf and have /etc/init.d/capi load the module then, good luck :)
I will take care of misdn, please dont commit it yet.
i agree, two init-scripts are NOT the solution we want to have. Even the current is mostly a hack. But we're still working on this issue and we get better and better. ;) mISDN doesn't need it's own init-script. It works pretty w/o. But it would be nice to test Stefan's ebuild and then give us feedback. It's not the final solution, but it should work.
net-dialup/misdn is in portage now. Please test it and give us feedback. Thanks!
and there is also a capi init-script modification to make working with mISDN easy. Upgrade to the new capi4k-utils -r1 and uncomment the appropriate mISDN driver in your capi.conf, no more problems with module autoload :)
