>
> > Sounds to me like you've got it the wrong way round. Lots of people want to
> build
> > kernels, very few as far as I can see want to build just a module.
>
> You'll be suprised. I can now accept that distributing the kernel
> sources like that is a very good compromise, useful for doing
> exactly that - building new kernel modules.
>
> Personally I've had to do this now a few times... for example,
> the newer bttv modules my voodoo3 card uses, and the vmware
> driver modules. Having the sources installed from the rpm in
> that state meant that the modules could be compiled right away
> against the sources, no fuss at all.
Still a significantly small minority.
> Perhaps the kernel Makefile could be patched so that "make
> {menu,x,}config" or "make dep" (or whatever) will first do a sanity
> check to see if the intention is to build a new kernel while in a
> default post-configured state.
That's not necessarily a problem. I often make minor changes and rebuild - I think
I've built 2.4.4-ac5 around five times so far - all for the one computer.
(2.4.4 is broken; otherwise I'd probably only have built it once or twice).
--
Cheers
John Summerfield
http://www2.ami.com.au/ for OS/2 & linux information.
Configuration, networking, combined IBM ftpsites index.
Microsoft's most solid OS: http://www.geocities.com/rcwoolley/
Note: mail delivered to me is deemed to be intended for me, for my disposition.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
