opsi Version 3.3.1 - opsi Download - uib

5. Netboot products: Automated OS installation and more
If you have a running machine with the correct drivers installed, you may use the
program 'double driver' (http://www.boozet.org/dd.htm) to extract these drivers and save
them to the opsi-server.
If you just have some differing hardware, you can take drivers as provided by the
hardware manufacturer and put this to the distribution file share.
But if you have to support a lot of different hardware, it might be convenient to use
ready packed packages for a whole bunch of Windows XP-drivers as provided by
http://driverpacks.net/.
You may download the current driverpacks (!!! about 2,5 GB !!!) from
http://driverpacks.net/DriverPacks/overview.php and save the to the server. Calling:
/opt/pcbin/install/winxppro/extract_driver_pack.py
these driver packs will be decompressed and stored in the directory
winxppro/drivers/drivers/D .
You may also use the command:
/opt/pcbin/install/winxppro/download_driver_pack.py . It will try to
download these driverpacks from a driverpack.net mirror and decompress them to the
correct directory.
Structure of the drivers directory tree:
/opt/
└─pcbin/
└─install/
└─winxppro/
└─drivers
├─classes/ (links to drivers by device classes)
├─hdaudioids/ (links to HD-Audio drivers)
├─pciids/ (links to drivers via PCI identifier)
├─pci.ids (PCI identifier data base)
├─usbids/ (links to drivers via USB identifier)
├─usb.ids (USB identifier data base)
├─vendors/ (Links to drivers by vendors)
└─drivers (space for general driver packs)
├─additional/ (for drivers that are not detected)
├─buildin/ (inf files from the i386 directory)
├─preferred/ (preferred drivers for your hardware)
└─mydriverpacks/ (example driver pack)
88