Bug#286001: please consider purging discover1 after installation
On Fri, Dec 17, 2004 at 02:18:20AM -0500, Joey Hess wrote:
> Harald Dunkel wrote:
> > hotplug uses the information in /lib/modules/$(uname -r)/modules.*map,
> > i.e. the kernel developers knowledge about which hardware is
> > supported by their drivers. These tables are updated for each new
> > kernel by running 'depmod -a'.
> > discover uses some manually edited table that gets updated
> > by the discover workers, e.g. if they receive a bug report about
> > some unsupported hardware. Sorry to say, but usually this table
> > is out of date.
> I'm not really interested in opinions for making this decision (to the
> limited extent that I have to play in making it). Show me a good
> analysis of some hard data (such as that below) to back that up,
> otherwise it's just a guess.
> An alternative guess might be this:
> Updating pci map information in the kernel requires getting a patch to
> the maintainer of the driver, through the kernel lieutenants, and to
> Linus. Then it takes a kernel release, which happens increasingly
> infrequently for 2.4 kernels and is not very common anyway. So the
> kernel's information is updated slowly and is increasingly out of date.
> Conversely discover's data is updated everytime someone sends a report
> to the d-i team, with a very short lag, and we've processed hundreds of
> these reports this year.
well, you fill a bug against the debian kernel package, and we include a patch ?
The debian kernel team may well be more responsive than the discover guys, not
BTW, once sarge is out of the way, will we move to discover2 for d-i ?