On Wed, 03 Nov 2004 10:34:53 -0600, Cameron, Thomas <thomas.cameron@xxxxxxxxxxxxxxxxx> wrote: > I assume from the deafening silence that my proposed solution doesn't have any objectors? Is this they way to go? Its ugly and you'll then have an RPM database out of sync. I'm not sure when the functionality to allow specification of module path was introduced into moutils, but my recollection was that it was years ago. If AS2.1 has the feature adding the path to /etc/modules.conf is the easiest fix. The syntax is something like (I'm at home and don't have a linux box here, so can't be sure) path[addons]=/lib/modules/`uname -r`/updates/qla2xxx (you don't want to put it into the kernel dir - the kernel owns that directory and may remove the module on an update) Then build the module and put it into the directory you specified. If the AS 2.1 modutils doesn't have that feature, you might want to consider updateing it (modutils) to a newer version - the one that comes with RH3 for example. > > Thomas > richard. -- ----------------------------------------------------------------------- richard offer @ gmail "Specialization is for insects" _______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
