Steven Blackery wrote:
> From: Pierre Bourgin [pierre.bour...@arteris.com]
>
>> you can perhaps continue to use the automated search for PCI devices and
>> keep your own systems for other, betting that all of them will be
>> supported in the future ?
>
> Sadly not, as my 'old' (and now current again) method involves hand
> crafting OemPnPDriverPath which means it clashes with yours. Unless you
> could edit your script so it reads in that value and then appends what
> it finds from the scan?
search-windrivers stuff does not interfere with "manual" choose of
drivers (present below /os/osfoldername/$OEM$/$1/) : it appends it own
stuff in OemPnPDriverPath value.
I don't have the code available of install.pl, but I think I've also
added anti-collision mechanism on folder names, especially if you set
$u->{'_temp'}->{'scan_windrivers_dest'} = 'drivers' and also use
'drivers' as folder name in /os/osfoldername/$OEM$/$1/ folder stuff: no
collision on sub-folders name of 'drivers' should happen, and
search-windrivers uses numeric (%d) as sub-folder(s) names, rather rare
in manual choose.
On my side, I still have "manual" drivers in $OEM$/$1/ for printers for
instance, no trouble with search-windrivers .
my $0.02
Pierre Bourgin
------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
unattended-devel mailing list
unattended-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/unattended-devel
