On 8/9/07, Hendrik Sattler <[EMAIL PROTECTED]> wrote: > Am Mittwoch 08 August 2007 23:02 schrieb Petter Reinholdtsen: > > [Julian Andres Klode] > > > > > We should try to use binary packages provided by linux-modules-* or > > > other modules packages by default and fallback to m-a. > > > > You might want to check out the recent changes to discover and > > discover-data. It already had support for installing hardware > > specific packages using the discover-pkginstall script, and I added > > code to run module-assistant to build the kernel module if the > > hardware specific package is supported by module-assistant. I hope it > > bring us at least one step closer to automatic driver activation for > > out-of-tree kernel modules. > > Is discover still installed by default on new installs? If yes, is this > activated by default? > I ask because I would like to get a "no" for both question and a big "NO" if > the first question is answered with "yes".
You've no for both questions with the exception that 'desktop' task installs discover1 we've 2 already packaged. Petter, couldn't we replace discover1 with discover (2) into the desktop task ? Is this a list of supported hardware issue, something else or there's no issue? Btw, it seems that xdebconfigurator already support discover (2) or discover1 but xserver-xorg recommends is on 'discover1 | discover' and in ltsp-client-core we depend on discover1 (not desktop task related though) regards, -- stratus http://stratusandtheswirl.blogspot.com get debian @ http://get.debian.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
