In ubcd52b1, the file
is not needeed AFAIK.
(Well, in fact several of the files in there are not really needed, but they simplify: A_ the building process of UBCD's images; B_ the pmagic's update procedure for customization.)
Although I am not necessarily suggesting this next step for the release of UBCD 5.2, there is one boot entry that should be eventually reviewed. Currently, UBCD and pmagic use the same version of Syslinux for the boot menu (not necessarily true for the included version in pmagic itself). If pmagic upgrades its Syslinux modules to version 5.0x, the current boot entry from UBCD to pmagic will still work, but some boot entries in pmagic's menu might fail (as they would use a different version of Syslinux modules than the boot loader's version). There are two possible workarounds.
The first possibility would be to edit
to point to the same Syslinux modules as UBCD already uses,
, but that complicates the pmagic's update procedure for customization.
The other possibility, much more complicated, would be to chain to
, but that only would work on optical media. For other types of media, a script would be necessary (to chain to ldlinux.bin, specific for that media) and the use of whichsys.c32.
Again, I'm not saying this is a priority at all and it is not even a current concern as pmagic is still using Syslinux 4.06 as UBCD does, but at some point some user might update to a pmagic version using Syslinux 5.0x. At that point, the customization procedure would need to be adapted, so to change the paths in
so to point to
instead of pointing to
I am posting this now, not for UBCD 5.2 itself, but for users interested in future customizations.
On another matter, just before the final release, whenever it happens (and I don't know whether there will be some more betas or not), please don't forget to update pciids (and to rename it) http://pciids.sourceforge.net/