similar to: isohybrid.c, problem reports and questions

EFI systems typically don't support booting off ISO 9660 filesystems, even if written to USB sticks. This patch adds support for generating a GPT that covers the stick as well, with an additional partition entry pointing purely at the secondary El Torito image. When burned to CD the secondary El Torito will be used as an EFI boot image, and when written to a USB stick the GPT partition

The block counts in the APM partitions assumed 512 bytes per block, whereas the start block numbers assume 2048 as announced in the APM header. This change divides the affected block counts by 4 to correct the assumption. --- utils/isohybrid.c | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index c5b4281..7d0864e 100644 ---

Hi, following will be 6 patch proposals for isohybrid.c 1: Encode GPT partition names as UTF-16LE 2: Correct blocking factor in APM partition block counts 3: Correct end block address of first GPT partition 4: Write GPT backup to the very end of the image 5: Change all fseek(3) to fseeko(3) 6: Introduce option --mbr and make isohybrid.c compilable standalone If the form needs adjustments,

The worst sin of isohybrid.c was to compose GPT partition names by 8-bit characters and to memcpy() them as if they were 16 bit wide. GPT names are encoded as UTF-16LE. It is trivial to create this encoding from 7-bit ASCII. This change introduces two byte arrays with the desired UTF-16LE names which replace the string constants "ISOHybrid ISO" and "ISOHybrid". ---

Op 2014-06-23 om 20:09 schreef syslinux-bot for H. Peter Anvin: > Commit-ID: f9dad5340bcefe34d860e991e8743be01a4d6c3c > Gitweb: http://www.syslinux.org/commit/f9dad5340bcefe34d860e991e8743be01a4d6c3c > Author: H. Peter Anvin <hpa at zytor.com> > AuthorDate: Mon, 23 Jun 2014 20:06:51 -0700 > Committer: H. Peter Anvin <hpa at zytor.com> > CommitDate: Mon, 23

Various EFI systems insist that there be no active flag in the pMBR in order to parse the GPT. The only way around this is to also generate a valid MBR - the firmware will then pick that up and use the system partition provided there. In order to deal with other EFI "sanity" checks, the partition type for the non-EFI partitions is set to 0 to skip the firmware bailing because of

The GPT partition 1 covers the whole ISO filesystem size. GPT specs demand that the partition end block number shall be the last valid block in the partition. isohybrid.c rather wrote the number of the first block after the partition end. This change reduces the number by 1. --- utils/isohybrid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/utils/isohybrid.c

The GPT backup header block should start 512 bytes before the end of the image file (resp. end of the disk device). This block and the backup GPT array were wrongly written 512 bytes too early. This change brings the backup GPT at its correct position. --- utils/isohybrid.c | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index

It seems unwise to offer future programmers fseek(3) calls for copy+paste. They are simply insufficient for large image files. This change switches all calls of fseek(3) to fseeko(3) and takes care that the offset value if of type off_t. --- utils/isohybrid.c | 19 +++++++++---------- 1 file changed, 9 insertions(+), 10 deletions(-) diff --git a/utils/isohybrid.c b/utils/isohybrid.c index

On 10. Nov 2020, at 15.45, Timo Sirainen <timo at sirainen.com> wrote: > > On 4. Nov 2020, at 13.24, Renaud M?trich <rmetrich at redhat.com <mailto:rmetrich at redhat.com>> wrote: >> I would like to report an issue which is 100% reproducible with a specific mail available in the reproducer attached to Red Hat's bugzilla

Joakim Bech <joakim.bech at linaro.org> writes: > On Fri, Sep 25, 2020 at 01:51:43PM +0100, Alex Benn?e wrote: >> With this command we are finally updating data to the backing store >> and cycling the write_count and each successful write. We also include >> the write count in all response frames as the spec is a little unclear >> but the example test code

Fix Bug to corrupt the img file Reproduce steps: > dd if=/dev/zero of=btrfs-small.img bs=1M count=1 > ls -lh btrfs-small.img -rw-rw-r--. 1 rock rock 1.0M Oct 24 09:51 btrfs-small.img > mkfs.btrfs btrfs-small.img -rw-rw-r--. 1 rock rock 2.0M Oct 24 09:53 btrfs-small.img Here you can see the original img file''s size goes larger to 2Mbytes. Signed-off-by: Rock Lee

On 4. Nov 2020, at 13.24, Renaud M?trich <rmetrich at redhat.com> wrote: > I would like to report an issue which is 100% reproducible with a specific mail available in the reproducer attached to Red Hat's bugzilla <https://bugzilla.redhat.com/show_bug.cgi?id=1894418>(https://bugzilla.redhat.com/attachment.cgi?id=1726535

Hi, i have Dovecot Director and Dovecot Backends with 2.2.32. i have found a email that my web server send with only one character "=" in the body of the email and it generate a log error in Dovecot log like this: Oct 23 13:16:50 dovecot_2.2.32 dovecot: imap(user at domain): Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 ||

i have a system with panics/crashes and seem to be able to trigger the problem. dovecot version: 2.2.33.2 (from ius rpm-package-repository) maillog: Dec 14 10:55:00 vimap01 dovecot: imap(XXX): Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0 || block_idx+1 == block_count) Dec 14 10:55:00 vimap01 dovecot: imap(XXX): Error: Raw backtrace:

> Hi, > > Ady wrote: > > so, why the original isohybrid image from Debian and many other > > isohybrid images have mostly (but not all) "00s" in place of the "90s"? > > That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. > Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. > > * Fedora

Dear list, I have been trying to debug a build failure for a while in the utils directory on isohybrid which seems to be distro specific. On Fedora 17 64bit the build completes without problems, but under both Ubuntu 32/64bit 11.10 and 12.04 I get the following: tim at oxygen:/usr/src/git/syslinux/utils$ make gcc -O2 -luuid -o isohybrid isohybrid.o isohdpfx.o isohybrid.o: In function

Hi, Ady wrote: > so, why the original isohybrid image from Debian and many other > isohybrid images have mostly (but not all) "00s" in place of the "90s"? That's a fake Block0 of an Apple Partition Map. Part of mjg's layout. Caused by isohybrid option --mac or xorrisofs option -isohybrid-apm-hfsplus. * Fedora has it with EFI FAT filesystem in one partition

Running Win2k terminal server against samba-2.0.7, we're seeing single character files being created at various times - these files appear to be "index.dat" data (e.g. ie\cookies\index.dat); Some details: Samba version: 2.0.7 OS: Solaris 2.6 Compiler: cc: WorkShop Compilers 4.2 30 Oct 1996 C 4.2 [lobster][/] # uname -a SunOS lobster.bath.ac.uk 5.6 Generic_105181-17

> > Same result as yours. > > > Have a nice day :) > > Thomas > I was under the impression (apparently the wrong one) that your pseudo-code was adding 4 cylinders to the first example, from 132 to 136, which would be non-optimal. Since I am not a developer, I believe you when you say that such jump won't happen :). Perhaps the code will be more clear to me