Hello! I wonder if anyone has done any automatic driver-selection scripts based on the found hardware?
This would really make the life easier for the sysadmin. I don't have that many drivers in $oem$\$1 because I don't have that dissimilar/special hardware, so I wouldn't mind the time it'll take to search through the .inf-files. I've started on a bash-script, but it should probably be converted to perl to be able to easier integrate into Unattended. The idea is to parse the PCI vendor/device (and optionally subsystem) from lspci-output (XXXX:YYYY Subsystem: ZZZZ:ZZZZ), convert to Windows-format (pci\ven_XXXX&dev_YYYY&subsys_ZZZZZZZZ) and search for that string in the *.inf-files under $oem$\$1\. Are there any drawbacks to this approach, other than being extremely slow for large libraries of drivers? One idea is to organize the drivers in $oem$\$1\<pcivendor>\<pcidevice>\<pcisubsys> to eliminate the need to search through the infs, but that requires the files to reside on a Linux-based fileserver so one can symlink other device-ids for drivers that support multiple devices. Please give feedback to this! It feels very "doable" if we can lower the overhead. I'm attaching my little script that I don't know if it works ;) -- Patrik
lspci2driverinf.sh
Description: Binary data
------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________ unattended-info mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/unattended-info
