You are not logged in.
The next version of kernel26archck will install to (variously) *-archck rather than *-archck?
This will remove the need for rebuilding the modules everytime - dunno why I never did this before!
Just so you all know
And, before anyone mentions it, yes I will add cramfs as well...
Offline
*-archck rather than *-archck?
It looks like the same thing. Is there a typo or is there something that I misundertand? :?
Offline
Is there a typo or is there something that I misundertand? :?
I think you're missing the '?'. it should stay for the version number, like -archck8
Offline
Yeah, the ? is the version number which I wll be removing from the fs nomenclature to avoid the need to rebuild the modules all the time, as they have already done with stock. Check the PKGBUILD in HEAD if you would
Offline
I thought the ? was a regular question mark. :oops: I haven't tried yet the archck kernel. I wanted to but recent reports that it was slower than the stock kernel made me stick with the latter. I'll try the next version.
Offline
Am I missing something here, or am I just thick?
This will remove the need for rebuilding the modules everytime
Don't we always need to rebuild modules when we change kernel? I rebuild my wlan-ng modules for every kernel - have I been wasting my time?
Offline
Possibly - I don't belive it is always necessary, especially if it is just a change in the .y branch
Offline
Am I missing something here, or am I just thick?
dibblethewrecker wrote:This will remove the need for rebuilding the modules everytime
Don't we always need to rebuild modules when we change kernel? I rebuild my wlan-ng modules for every kernel - have I been wasting my time?
It highly depends on what changes were made - Linus has stated several times that he will never enforce a stable module ABI, because that goes against progress - that doesn't mean that from, say, 2.6.13.x to 2.6.13.y the module ABI *was* changed - maybe no one touched it. Maybe other work was done.
And when that stuff does change, alot of the time it is either general stuff that affects all modules, or something specific to one "class" of modules - i.e. you must recompile network modules, but "nvidia" can remain the same.
Offline
Thanks guys - that's a bit clearer.
Offline
I suppose a good rule of thumb is...install your new kernel, if the modules work that's good, if they don't then rebuild them
The trick is getting the kernel to always install the modules to the same dir It's not a hard trick, especially if you follow the stock kernel PKGBUILD...
Offline