Victor Chew wrote:
Quote:
In ubcd52b1, the file pmagic/boot/syslinux/isolinux.boot is not needeed AFAIK.
I try not to modify/remove any files from the Parted Magic distribution.Actually, you already modified at least one file (syslinux.cfg). I am not saying that you should "control" anything coming from pmagic, but adding what is already known to be unnecessary files doesn't make much sense to me. If someone that wants to customize the release adds such unnecessary file, that's up to the user, but what's the point on releasing UBCD with unnecessary files?
IMO, there should be a script in UBCD, using the same type of techniques already used in other scripts (under "tools"), so to copy "all but the unnecessary" files from a certain "pmagic-extracted" directory into "ubcd-extracted/pmagic/", and then used "sed" in the script so to change the content of any *.cfg file in "/pmagic/boot/syslinux/". The "unnecessary" files are known, and the changes in the relevant cfg file are also known. I could provide more details, if this is of any interest.
Quote:
Quote:
Where "COM32 linux.c32" is used in the Syslinux boot menu, it should be corrected to "COM32 /boot/syslinux/linux.c32" and then the rest of the line.
In the next release, I was actually planning to remove all those references to /boot/syslinux from all the other entries (memdisk, menu.c32 etc.) since syslinux from look for them in /boot/syslinux anyway. Any downside to that?Sorry, I don't understand what you intend to do. If you want to reduce the paths (or their length) in cfg files, then a different CWD shall be used (I actually use a different CWD in my customized UBCD, including for pmagic), or you would need to change the whole structure of UBCD. If you want feedback about this question, please clarify your plans / intention.
EDIT:
If what you mean is that you want to change from:
Code:
/boot/syslinux/
(including the first space character) to use just a space character in all "/ubcd/menu/syslinux/*.cfg" (and in subdirectories too), then there shouldn't be any problem in syslinux itself (except maybe that the "syslinux2grub4dos" scripts should be adapted too). Some paths will use absolute notation and "/boot/syslinux/" will be used in relative notation. BTW, there are other alternatives too.TIA,
Ady.