On 09/15/2014 10:02 PM, Thomas Schmitt wrote:
Hi,
'Warning: Creating filesystem that does not conform to iso-9660.'
This is issued if one of the relaxation options is present
which violate the strict prescriptions of ISO 9660 about
character set and name components.
Like -max-iso9660-filenames, -L, -N, ...
But i do not see such an option in scripts/Create-ISO.
It might of course be introduced via $bootoptions which are
read into the script from build/$id/TOOLCHAIN/isofs.txt.
I understand the decisive line begins by the word BOOT.
(I realized that the read input comes from this file
and not from stdin.)
Well, if the boot options deem it necessary to relax the
restrictions, then it should be ok for the purpose of booting.
Using isolinux as the CD Loader in the Build,
'Failed to load LDlinux.c32'
(Are you sure with upper-lower-case of your quoted messages ?)
yes, that was what I copied down for one (install), but the other (live)
says it in lower case which is in part why the queery. Maybe I wrote it
down wrong or my typeahead (which keeps turning itself on, even with it
configured off) was responsable.
Does your ISO image contain a file "ldlinux.c32" ?
mount /dev/sr0 /mnt/iso
find /mnt/iso -name "ldlinux.c32"
no, although the first cd doesn't exist anymore!
None of my cd's using isolinux have it either so i wondered if it was an
internal package.
SYSLINUX wiki states that it is needed since version 5.00:
http://www.syslinux.org/wiki/index.php/Library_modules
debian-7.5.0-amd64-netinst.iso uses SYSLINUX 4.05 and does not
have ldlinux.c32 in its directory /isolinux.
archlinux-2013.11.01-dual.iso uses 6.02 and has /isolinux/ldlinux.c32.
(t2-8.0-minimal-i486.iso uses GRUB 0.97.)
If you used SYSLINUX >= 5.00 and the file ldlinux.c32 is missing
in the ISO, then it was probably not copied to the file locations
which are listed in build/$id/TOOLCHAIN/isofs.txt .
One will have to inspect the producer of this file.
The package is listed as syslinux-5.10 and looking inside the compiled
package it is their.
I shall update it to the latest 6.02 and see what happens, it now
resides on kernel.org's repository in case your interested.I couldn't
see anything in the syslinux package to stop this being ok.
Also had a look at the syslinux changelogs, but there was no mention of
ldlinux.c32 as a problem.
Have a nice day :)
Thomas
Thanks Thomas, I was wondering if my brain was beginning to fry as i was
just starting to go around in circles burning cd's, testing, rebuilding,
burning ...
regards
jon
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[email protected] with a subject of: unsubscribe t2
