Create SLES/SLED universal DUDs by default
Many times driver kits can be used equally for SLES or SLED because the kernel is common. Unfortunately the DUD file structure is different for each product flavor.
SLES:
linux/suse/<ARCH>-sles<VERSION>SLED:
linux/suse/<ARCH>-sled<VERSION>Now the tools will create DUDs that work with both product flavors by either by duplicating the directory trees, or creating a symlink (in the case of DUD structure embedded in the initrd).
This behavior can be disabled with the option --no-uni-dud in which case the DUD will only support the specified base product.
Merge user provided DUD scripts with defaults
SUSE Driver Tools automatically generates DUD pre/post scripts. Previous behavior was to overwrite these scripts with any user provided scripts - thereby losing the functionality provided by the Tools.
Now we merge (append) the auto-generated scripts with any user provides scripts.
Replace existing modspecs in module.config
The previous implementation only appended user supplied modspecs to the end of the specified section in module.config. Now we search for an existing modspec of the given kernel module and replace it. All new modspecs are appended as before.
kISO and Driver Kits get proper headings in nextmedia text
New option --merge for driverkit and kiso commands will merge the driverkit or kISO result with the base SUSE Linux Enterprise installation media so that everything is contained on one media.
The --base option for driverkit, kISO, dud, initrd etc… now accepts path to ISO image. ISO image is automatically mounted for use by SUSE Driver Tools command.
Added support for grub2 uEFI media structure that comes with SUSE Linux Enterprise 11 Service Pack 3
Added unpackinitrd command that simply unpacks an initrd image to a given location.
kiso, pxe, and unpackinitrd commands.sdt man pageImplement fixiso command Use to fix broken El Torito uEFI alternate boot on existing iso images. Some ISO generation tools get this wrong.
Added --include-dud driverkit option to add DUD structure to base of driverkit media
Bootable driver kits will get the full update media path (linux/suse/<arch>-<slever>) from the settings in the base distro media.
When generating standard driver kit, the --distro and --arch-version options must be specified or the initrd from the base distro media placed in the updates path (the tool will get the proper path spec from the initrd).
Add unpackinitrd command to unpack an initrd to a specified location.
Add --no-initrd-mod-updates switch Useful when making other kinds of update to the initrd and but wanting to keep the modules untouched.
Add alias to add-on URL in add_on_products.xml
Without the alias, the addon repo will have an autogenerated name which looks confusing to the user. We set an alias equal to the add-on product name (converting spaces to underscores).
This only applies to SLE11. SLE10 uses a different mechanism and does not suffer from this issue.
It appears that both mkisofs and genisoimage fail to create proper boot catalog entries for UEFI and they fail differently. Updated code to handle genisoimage as well as mkisofs images.
Make call to magic.open compatible with older versions of python-magic
Fix man page builds
Before we only looked for a pre-made installkey.gpg file and replaced the default one from the base media. Now the user can pass additional keys or keyrings to be added to the default installkey.gpg keyring from the base media.
As in the past, if an installkey.gpg keyring is provided as an update, it will replace the existing one. Any additional keys/keyrings will be added to this updeated installkey.gpg keyring