search for: libisof

Until Syslinux 3.86, isolinux.bin contained a checksum that was calculated by 'core/checksumiso.pl'. The checksum is related to the patching of the boot info table. During May 2009, a commit by Peter deleted the checksumiso.pl file. The commit is: core: LZO compress the PM part of the core repo.or.cz/syslinux.git/commit/0d82b71304d596d80f3c4520f9dcf90048ca50b7 And so, since

...048ca50b7 > And so, since version 4.00, the 'code/checksumiso.pl' file is no longer > included. > How is the checksum of isolinux.bin calculated since then? By the ISO 9660 production program which patches in the Boot Info Table. The computation of checksumiso.pl can be seen in libisofs function make_boot_info_table(): https://dev.lovelyhq.com/libburnia/libisofs/blob/master/libisofs/eltorito.c#L1252 (without Javascript https://dev.lovelyhq.com/libburnia/libisofs/raw/master/libisofs/eltorito.c you have to hop to the line yourself. Sorry. GitLab. Urghhh ...) libisofs does no...

...s/isohybrid.c#n795 This problem and more are reported in http://www.syslinux.org/archives/2012-May/017843.html http://www.syslinux.org/archives/2012-May/017871.html Fedora image (by isohybrid.c): GPT partition name : 1 49534f4879627269642049534f0049534f487962726964004170706c Archlinux (by libisofs): GPT partition name : 1 490053004f00480079006200720069006400 GPT partname local : 1 ISOHybrid (Lines from the upcomming boot equipment inspector of libisofs. See http://libburnia-project.org/wiki/ReportSystemArea ) To Kai Kang: I am willing to help with isohybrid.c but do not want...

...version 4.00, the 'code/checksumiso.pl' file is no longer > > included. > > How is the checksum of isolinux.bin calculated since then? > > By the ISO 9660 production program which patches in the Boot Info Table. > > The computation of checksumiso.pl can be seen in libisofs function > make_boot_info_table(): > > https://dev.lovelyhq.com/libburnia/libisofs/blob/master/libisofs/eltorito.c#L1252 > (without Javascript > https://dev.lovelyhq.com/libburnia/libisofs/raw/master/libisofs/eltorito.c > you have to hop to the line yourself. Sorry. GitLab....

I'll file a ticket once fedorahosted is back online. The request is to port the isohybrid script, in the syslinux package, from perl to C (and of course submit it upstream). This would let syslinux drop its dependency on perl, which would save considerable space. $ wc -l git/syslinux/utils/isohybrid.in 258 git/syslinux/utils/isohybrid.in As this is doing some simple structure unpacking

Good day, Matthew. I recently got stuck while building Syslinux as <uuid/uuid.h> doesn't exist on my system. The #inclusion was introduced in commit 2c3a24e5f4b807ec31595227afa59a818c060ca9. Whence does this file come, if you please? I'm assuming it is the Linux kernel's, but can't seem to understand the directory prefix, in that case. - Shao

When call isohybrid with option '-u', it overflows on a 32 bits host. It seeks to 512 bytes before the end of the image to install gpt header. If the size of image is larger than LONG_MAX, it overflows fseek() and cause error: isohybrid: wrlinux-image-x86-64-20140505110100.iso: seek error - 8: Invalid argument Check the offset and call fseek() multi-times if offset is too large.

I have just pushed out Syslinux 3.81-pre10. This fixes some pretty serious bugs, including the fact that, apparently, isohybrid didn't work at all in CBIOS mode. Unfortunately it means that the isohybrid handover protocol has changed, and so a new isolinux.bin isn't compatible with an old isohybrid or vice versa (as a result, the magic number has changed.) -hpa

Hi, i have now a retriever of Rock Ridge names from ISO directory records and their eventual Continuation Areas. Further i have a detector for SUSP and Rock Ridge signatures. Both have been tested in libisofs by comparing their results with the Rock Ridge info as perceived by the library. 50 ISO images tested. Some bugs repaired. Now they are in sync. (The macro case Isolinux_rockridge_in_libisofS in susp_rr.c can later be removed, when no further tests in libisofs are expected.) Most of the code is...

...he official upstream Syslinux (pre-)releases (just as Slitaz does). > > > > Again, The Syslinux Project needs more development-power-time and > > patches are welcome. > > If i fix isohybrid.c then it will stick to me. > After a while it would become the same as the libisofs/xorriso > implementation. (I would read MBRs from the SYSLINUX installation, > would drop the dependency on libuuid, ... perky changes ...) Understandable. > > Have a nice day :) > > Thomas > Just for completeness... The patch sent in http://www.syslinux.org/archive...

...;AFP" in the help text of isohybrid.c. It should be "APM". ---------------------------------------------------------------- Known Variants up to now: - isohybrid.in -> isohybrid.pl from SYSLINUX, no EFI/GPT support - isohybrid.c -> isohybrid from SYSLINUX - libisofs/make_isohybrid_mbr.c from libburnia, needs isohdp[fp]x*.bin -> libisofs, xorriso from SYSLINUX - isohybrid.sh from SliTaz, no EFI/GPT support - iso2exe.c -> isohybrid.exe from SliTaz, no EFI/GPT support -------------------...

...less rounds up the outfile_len to finally yield full blocks of 2048 bytes size. So up to 2047 bytes of arbitrary discarded memory content could end up in the compressed isolinux.bin. But those bytes would also be part of prepcore's checksum computation. So the checksum should match the one from libisofs. I further tried to provoke the initial checksum of isolinux.bin by spoiling the byte order of the 4-byte unsigned integers which get added. But prepcode's function get_32() in both variants yields on amd64 the same integer values as libisofs sees. Willfully reverting byte order of the intege...

Allow the user to define the type of partition and its number from the command line. The following example creates partition numer 4 with type 1c (hidden FAT32 LBA): isohybrid -fstype=28 -pentry=4 hybrid.iso --- utils/isohybrid.in | 11 ++++++++--- 1 files changed, 8 insertions(+), 3 deletions(-) diff --git a/utils/isohybrid.in b/utils/isohybrid.in index 83f9dc0..d67a2b5 100644 ---

I have addressed all the issues that I know about (including, hopefully, the isohybrid version dependence...). I would like to release this this week so please let me know as soon as possible if this version is "go". -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.

...o large to fit into these fields, the tuple (1023, 254, 63) is typically used today," Since the only intended audience of the partition is UEFI firmware, i'd say it is safe to assume that it can address by LBA. I will have to examine whether the invalidated CHS value is an old bug in libisofs-1.3.6 (and maybe fixed meanwhile) or if there is a reason why the EFI partition got no valid CHS addresses. Have a nice day :) Thomas

...l, btw.) These features suffer from bugs, which obviously do not hamper booting of Fedora ISOs. http://download.fedoraproject.org/pub/fedora/linux/releases/20/Live/x86_64/Fedora-Live-Desktop-x86_64-20-1.iso Debian, Ubuntu, and Archlinux ISOs with EFI support are made with isohybrid from xorriso/libisofs using "isohdp[fp]x*.bin" MBRs from the SYSLINUX installation. intrigeri: > Would it help if someone with the needed > Perl skills stepped up and volunteered to maintain the Perl version, > at least to port bugfixes from the C version? I am willing to explain what is unclear a...

...0FE tells that the decimal address is 8785 whereas the requested address was 8444. So here we clearly have a wrong translation from LBA to C/H/S. But the result differs from what David reports. My run did read a block although it was the wrong one. I have a guesser function for disk geometry in libisofs. It says that HC= 32 , SH= 63 is the only valid combination where HC * SH * 4 + SH * 11 + 29 - 1 = 8785 (The function works by brute force, simply trying all combinations of {1...255} x {1 ... 63}. Often it finds more than one solution.) The only solution for 8444 = (4,11,29) is just th...

Hi, i began to implement a common lookup function for SUSP and Rock Ridge entries: /* Obtain the payload bytes of all SUSP entries with a given signature. @param fs The data source from which to read CE blocks. @param dir_rec Memory containing the whole ISO 9660 directory record. @param sig Two characters of SUSP signature. E.g. "NM", "ER", ...

I'm going to get the hang of this mailing list eventually. Apologies for any duplicate emails.. >Ian Bannerman: >> While I did know the .exe variant was not official / untrusted, >Is there a special reason for this ? (Except the known bugs which affect Linux binaries, too.) Not really. I had never found a convincing source for it and had seen previous list entries like this

On 04/25/2013 07:03 AM, syslinux-bot for Thomas Schmitt wrote: > Commit-ID: 5de463f724da515fd6c5ea49ded6dde178362181 > Gitweb: http://www.syslinux.org/commit/5de463f724da515fd6c5ea49ded6dde178362181 > Author: Thomas Schmitt <scdbackup at gmx.net> > AuthorDate: Thu, 4 Apr 2013 20:02:37 +0200 > Committer: Matt Fleming <matt.fleming at intel.com> > CommitDate: