For the inclusion of this set of programs in UBCD using pmagic's kernel, it would probably be better (or even necessary) to use
COM32 /boot/syslinux/linux.c32 /pmagic/bzImage
instead of using "
" in the Syslinux boot entry.
I don't understand, why is this change necessary?
What's the difference between the two?
1_ The key word "KERNEL" in Syslinux cfg files is more generic. Its behavior depends on the file extension of the specific kernel. For example, to boot linux kernels that use the "*.bin" file extension, the "KERNEL" key word should NOT be used. Use "LINUX" instead.
2_ The second difference is more relevant to this particular case. In Syslinux 4.06 (and older), linux.c32 is capable of booting newer (bigger) Linux kernels (like the one used in PMagic). The "traditional" directives ("KERNEL" or "LINUX") might fail in these cases. Note that the linux.c32 module included in Syslinux 4.06 (used by UBCD 5.2 pre-releases), although capable of booting newer Linux kernels, is still under development, so there are cases where it might fail. Having said that, I strongly suggest using it for pmagic's kernels, since the original PMagic distro already uses it (and has been using it for a long time).
Also, adding a help text as DISPLAY file would be recommended (let me know if I can help).
What do you mean as a display file?
In Syslinux, DISPLAY files are those "help text" files that can be displayed before the boot prompt, or by pressing F1-F12 keys (among other possible options).
Instead of (or in addition to) using different boot entries in the main boot menu, there could be a help screen (help text in a DISPLAY file) where the user gets all the available options for each stress-like test, including explanations for each "boot cheat code".
UBCD has some examples of DISPLAY files. "F1" and "F2" for pmagic, when booted from UBCD's menu. PMagic itself has them too, with its own content, of course. DBAN and memtest86 4.1.0 (included in UBCD 5.2b3) have their respective DISPLAY files. There are several alternative ways to show their contents, and the aforementioned examples use different variations of them.
I guess I should first wait for Victor to include the new set of stress-like tools and then I may try to come up with some possible DISPLAY files for them, if
there is any real interest / utility for UBCD.