Linked by Thom Holwerda on Thu 13th Apr 2006 22:55 UTC, submitted by Hans Kwint
Thread beginning with comment 115016
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Don't talk about drivers...
by leech on Sat 15th Apr 2006 12:38
in reply to "RE: Don't talk about drivers..."
"still, its not a perfect solution, i give you that. it would be nice if someone could come up with a way for the drivers to have their kernel interface be recompiled transparently when a new kernel got installed."
Debian does this with LIRC if I recall correctly, when there is a kernel update, the LIRC package will re-compile the modules for it. Though I saw it do this one time and it failed since I hadn't installed the proper linux-headers package as well. But the capability is already there with Debian via the module-assistant program.
Leech
RE[3]: Don't talk about drivers...
by hobgoblin on Sat 15th Apr 2006 14:56
in reply to "RE[2]: Don't talk about drivers..."






Member since:
2005-07-06
it realy depends. they keep releasing new versions
and often the only thing you need to do with the linux driver is recompile the kernel interface, not redownload the whole thing again.
still, its not a perfect solution, i give you that. it would be nice if someone could come up with a way for the drivers to have their kernel interface be recompiled transparently when a new kernel got installed.
like say one could agree on a default place to put the makefiles and other stuff so that distros could have a script in the package go over and compile them when needed. and if failed, tell the user to go download a new version of the drivers that had problems.