Hi Frank, I'm considering to adopt modconf, and rewrite it from scratch in python. Before I commit, I'd like a reality check as to the expected functionality:
- during package build, generate one or more files about module names and descriptions, and organise that according to the kernel source hierarchy - during runtime, use a dialog system that allows the user to browse and load modules, using the above-described file The input for the first step is by now consistently organised in the kernel's Kconfig and Makefiles, so it should be pretty straightforward. The second, should also be straightforward given a decent dialog system, with the only caveat being that one has to doublecheck which subset of all modules have actually been compiled as such for the running kernel. What about module dependencies? Would it be okay to bypass that by using modprobe instead of insmod? Any issues I should have in mind for d-installer use cases? eg, modules living somewhere else than /lib/modules/`uname -r` Please add anything else I might be missing. Thanks, Serafeim -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
