> Combine that with natural sloth and aversion to
> flame-wars and one has a formidable barrier.
<G>
[...]
> I've offered to touch up the readme.modules (several times) but have
> gotten no response.
The general fealing is that ideas are cheap. Working patches are much more
dificult. Write a patch, and post it on linux-kernel. Comments will start
pooring in, more then likely.
> My suggestions about the module stuff would either
> have to be backwards-compatible or would require touch-ups to every
> modular driver; in either case I would be hesitant to wade into it without
> a go-ahead from those who own those areas of code.
The normal way seems to be:
1) Write the New Way in, breaking all the drivers.
2) Change one driver as an example.
3) Write a sepperate patch that steps on everyone's toes, or declare
everything obsolete <G>.
> I am willing, as I
> said, to at least do some research on it if the Linux equivalent of the
> group managers offer me some political coverage or whatever it is one is
> supposed to have to do this, which I make no pretense of understanding.
Nothing is needed. Write the code, then worry about getting it in the
offical tree.
-=- James Mastros
-- "I'd feel worse if it was the first time. I'd feel better if it was the last." -=- "(from some Niven book, doubtless not original there)" (qtd. by Chris Smith)