Petter Reinholdtsen <[EMAIL PROTECTED]> writes:
> Not very many kernel module source packages are recognized by the
> discover-data package at the moment. Two devices using the
> qla2x00-source package is all there is at the moment. The problem
> with maintaining the mapping from hardware to debian package still
> remain. At the moment it depend on manual updates based on user
> feedback. If you know some hardware that is supported by a given
> kernel module source package, please report them as wishlist bugs
> against discover-data. If you want to test this feature you can add
> entries to the /lib/discover/pci-device.xml file yourself. :)
I think it can be improved. Let me explain my idea:
If we build the module that we want to add on the database and write a
small script that uses modules.alias file updated with it we can write
the database will full module knownledge available. This would all
make possible to write a small script that does make this
automatically.
grep ata_piix /lib/modules/2.6.22-1-686/modules.alias \
| sed 's,pci:v0000\(.*\)d0000\(.*\)sv.*,\1:\2,g' \
| sort -u
> I believe the next step is to call the discover-pkginstall script from
> d-i during installation, to get the required packages installed.
Can you please elaborate a little more how do you intend to do that? I
personally wouldn't like to have my system with gcc and like, needed
to build the module, so would be nice if we might purge those packages
after building it. I also don't know where do you think it might fit
better?
TIA,
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
