Bug#74913: modconf does not find modules for 2.4.0 kernels
> On Mon, Feb 19, 2001 at 11:38:32PM +0100, Martin Schulze wrote:
> > Hi,
> > I've worked on modconf recently. Could you give it a try?
> > http://master.debian.org/~joey/NMU/modconf_0.2.30.0.1_all.deb
> > (it's no NMU but a MU, but well...)
> This looks alright, except you've unravelled all the nesting. Plus
That was the only way to get a fix done within hours so we'll have something
> modconf quits and I need to do 'reset' when I select anything. And it
Ugh, I've seen this once, tried to redo it and then it worked, so...
works for me... cannot fix. :(
> doesn't show alsa any more. ;)
Please send me the output of (cd /lib/modules; find `uname -r` -type f)
> My own suggestion for layout would be to expand 'kernel/*' in the main
> menu, and then expand '(/*).*' inside.
> |----- /block
> |----- /char
> |----- /char/ftape/compressor
> \----- ....etc
Feel free to implement this. :)
It may be nicer, though it will also confuse people who don't expect
By displaying all path components they will see irda twice at least.
> But that might be too hard, I don't know. I think it would be a decent
> tradeoff between menu length and nesting depth if it can be done.
It will require a redisign of the menu handling, nothing that can
be done in a couple of hours you can affort on fixing this. Since
tausq is rewriting the whole thing, that may give you an improvement.
However, if you are interested, please file a separate whishlist bug
against modconf for using tree structures. That way the idea won't
Let's call it an accidental feature. --Larry Wall
Please always Cc to me when replying to me on the lists.