Bug#286001: please consider purging discover1 after installation

2004-12-18 Thread Sven Luther
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

Bug#286001: please consider purging discover1 after installation

2004-12-18 Thread Marco d'Itri
In article [EMAIL PROTECTED] you wrote: 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

Re: Bug#286001: please consider purging discover1 after installation

2004-12-17 Thread martin f krafft
also sprach Joey Hess [EMAIL PROTECTED] [2004.12.17.0818 +0100]: Updating pci map information in the kernel requires getting a patch to the maintainer of the driver, through the kernel lieutenants, and to Linus. Alternatively, you can use /etc/hotplug/*.usermap to provide updated information.

Bug#286001: please consider purging discover1 after installation

2004-12-17 Thread martin f krafft
also sprach Harald Dunkel [EMAIL PROTECTED] [2004.12.17.0714 +0100]: It would be possible to forward the basic information from the modules.*map into discover's database, though. Or to tell discover to read the modules.*map. Or to provide usermap files for hotplug to include those devices that

Bug#286001: please consider purging discover1 after installation

2004-12-16 Thread martin f krafft
Package: debian-installer Severity: wishlist The installation leaves discover1 installed, which is not the doing of debootstrap. With hotplug present, discover is basically useless on an operational system and really just does not need to start during boot. Moreover, X configuration uses discover

Bug#286001: please consider purging discover1 after installation

2004-12-16 Thread Harald Dunkel
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joey Hess wrote: | | What proof do you have that hotplug will discover all the same hardware as | discover1, and load the same modules for it? If it doesn't, the | installed system may not work. | hotplug uses the information in /lib/modules/$(uname

Bug#286001: please consider purging discover1 after installation

2004-12-16 Thread Joey Hess
martin f krafft wrote: The installation leaves discover1 installed, which is not the doing of debootstrap. With hotplug present, discover is basically useless on an operational system and really just does not need to start during boot. What proof do you have that hotplug will discover all

Bug#286001: please consider purging discover1 after installation

2004-12-16 Thread martin f krafft
also sprach Joey Hess [EMAIL PROTECTED] [2004.12.16.2228 +0100]: What proof do you have that hotplug will discover all the same hardware as discover1, and load the same modules for it? If it doesn't, the installed system may not work. It scans the same subsystems. I also tried on four