Driver updates should be located using arbitrary revision matching
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| DKMS |
Invalid
|
Medium
|
Unassigned | ||
| casper (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: casper
When installing driver updates, the correct updates are selected by folders
named with the first three places of the kernel version (2.6.20). It would be
helpful to have the possibility of discriminating between a finer selection of
kernels, such as 2.6.20-15-generic, vs. 2.6.20-16-generic. This is a needed
function of DKMS driver installation, however, it may be done inside the DKMS
debian packages. It would be preferred if we could get past this, and do it
properly.
The matching was intentional to make dealing with security updates more straightforward. This can still be implemented using the old 2.6.20 folder, but my request is for an expansion of functionality.
Question: could we possibly allow matching any length of the folder name to the current kernel name?
Ie. If [ "`uname -r | egrep '^$folder'`" ]; then use contents; fi
Obviously it is a bit more complex than this, but this is the general idea.
Related branches
| Changed in dkms: | |
| importance: | Undecided → Medium |
| Colin Watson (cjwatson) wrote | #1 |
| Changed in casper: | |
| status: | New → Fix Released |
| Changed in dkms: | |
| status: | New → Invalid |
casper (1.109) gutsy; urgency=low
* Cache the stty binary before ejecting the CD.
* Skip the CD eject prompt if 'noprompt' is on the kernel command line
(LP: #149159).
* Try each of (e.g.) 2.6.22-13-generic, 2.6.22-13, and 2.6.22 in turn as
directory names for driver updates (LP: #122430).
-- Colin Watson <email address hidden> Fri, 05 Oct 2007 03:24:43 +0100