similar to: [PATCH 2/2] Preserve MBR id in isohybrid

"use integer" limits integers to 2^31-1 on 32 bits, which makes imgsize to be -1 on DVD images Signed-off-by: Pascal Terjan <pterjan at mandriva.com> --- utils/isohybrid.in | 3 +-- 1 files changed, 1 insertions(+), 2 deletions(-) diff --git a/utils/isohybrid.in b/utils/isohybrid.in index 4671036..e98c59f 100644 --- a/utils/isohybrid.in +++ b/utils/isohybrid.in @@ -17,7 +17,6

FYI -------- Original Message -------- Subject: IPAPPEND on http://syslinux.zytor.com/faq.php#config Date: Mon, 31 Jan 2005 15:20:00 +0100 From: Pascal Terjan <pterjan at mandrakesoft.com> Organization: Mandrakesoft To: david at weekly.org Hi, I needed to get the MAC from which we booted using pxelinux (in order to know which interface we used to boot). I found reading the source that

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

That is with syslinux 4.05 on Slackware-14.0: bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso catalogue offset: 561 ve[0]: 1, cs: 1 ve[1]: 0, cs: 1 ve[2]: 0, cs: 1 ve[3]: 0, cs: 1 ve[4]: 0, cs: 1 ve[5]: 0, cs: 1 ve[6]: 0, cs: 1 ve[7]: 0, cs: 1 ve[8]: 0, cs: 1 ve[9]: 0, cs: 1 ve[10]: 0, cs: 1 ve[11]: 0, cs: 1 ve[12]: 0, cs: 1 ve[13]: 0, cs: 1 ve[14]: 21930, cs: 21931 ve[15]: 43605, cs:

On 01/11/2013 05:36, Ady wrote: > >> That is with syslinux 4.05 on Slackware-14.0: >> >> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >> catalogue offset: 561 >> ve[0]: 1, cs: 1 >> ve[1]: 0, cs: 1 >> ve[2]: 0, cs: 1 >> ve[3]: 0, cs: 1 >> ve[4]: 0, cs: 1 >> ve[5]: 0, cs: 1 >> ve[6]: 0, cs: 1 >> ve[7]: 0, cs: 1

> That is with syslinux 4.05 on Slackware-14.0: > > bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso > catalogue offset: 561 > ve[0]: 1, cs: 1 > ve[1]: 0, cs: 1 > ve[2]: 0, cs: 1 > ve[3]: 0, cs: 1 > ve[4]: 0, cs: 1 > ve[5]: 0, cs: 1 > ve[6]: 0, cs: 1 > ve[7]: 0, cs: 1 > ve[8]: 0, cs: 1 > ve[9]: 0, cs: 1 > ve[10]: 0, cs: 1 > ve[11]: 0, cs:

On 01/11/2013 18:40, Didier Spaier wrote: > On 01/11/2013 05:36, Ady wrote: >> >>> That is with syslinux 4.05 on Slackware-14.0: >>> >>> bash-4.2# isohybrid -v /tmp/slint64-13.3720131030-dvd.iso >>> catalogue offset: 561 >>> ve[0]: 1, cs: 1 >>> ve[1]: 0, cs: 1 >>> ve[2]: 0, cs: 1 >>> ve[3]: 0, cs: 1 >>>

Hello, I currently have a problem : There is a domain administrators group which I filled as "admin users" in smb.conf. They can do what they want on files, that's fine. Problem is the files they create are owned by root. Let's explain why this is a problem for me : - People in this group can't access their files in an unix way (ftp, shell, ...) - If one of them get removed

Hi, i wrote: > > Not only MBR writing but also reading of the Primary Volume Descriptor > > and of the El Torito catalog by isohybrid.c are currently prone to > > unwanted CR-insertion. Miscalculations can be caused by this. I have to correct myself: Carriage Return characters (byte value 13 = 0x0d) are not at risk to be inserted, but rather to be removed if they happen to be

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

Op 2014-06-20 om 15:56 schreef Ady: > > The Perl variant, isohybrid.in, seems to be getting left behind > regarding several patches. I don't recall whether there is at least > some mention in the isohybrid docs about the existence of 2 variants > included in Syslinux (and that is in addition to other isohybrid > methods outside Syslinux). Is there any reference? >

In the C part of the OCaml plugin we created a ‘bytes’ [byte array] and passed it to the OCaml pread method. The plugin is supposed to overwrite the array with the returned data. However if (eg. because of a bug) the plugin does not fill the array then whatever was in the OCaml or possibly even the C heap before the allocation is returned to the client, possibly resulting in a leak of sensitive

Make use of the new copy-attributes command to properly copy all file attributes from a file to the new version of it. --- builder/perl_edit.ml | 29 +--------------------------- edit/edit.c | 49 ++--------------------------------------------- fish/edit.c | 54 ++-------------------------------------------------- 3 files changed, 5 insertions(+), 127 deletions(-) diff --git

Compatibility updates for xserver 1.20. Adam Jackson (8): Default to 32bpp if the console is 8bpp (and we weren't told otherwise) Use own thunk functions instead of fbdevHW*Weak Pass the pci device (if any) through to fbdevhw in probe and preinit Fix shadow fb allocation size (v2) Remove dead pix24bpp variable Use shadowUpdate32to24 at 24bpp Update

On Friday, 14 July 2017 15:39:10 CEST Richard W.M. Jones wrote: > .gitignore | 6 +- > Makefile.am | 2 +- > common/mlutils/Makefile.am | 4 - > daemon/Makefile.am | 103 +++++++++++++++++++++++-- > daemon/chroot.ml | 85 +++++++++++++++++++++ > daemon/chroot.mli | 35 +++++++++ > daemon/daemon-c.c |

On 8/13/19 10:37 AM, Richard W.M. Jones wrote: > The original nbd_aio_* (non-callback) functions are removed and > replaced with the renamed callback variants. > > This is a simple mechanical change to the API: > > (1) Any existing call to nbd_aio_*_callback can simply be renamed to > nbd_aio_* > > (2) Any existing call to nbd_aio_* must have two extra NULL

On Fri, Jun 10, 2016 at 05:07:02PM +0300, Pavel Butsykin wrote: > Store the list of EFI system partitions on the inspect object in order to be > able to tune their contents later in the process. > > Signed-off-by: Pavel Butsykin <pbutsykin@virtuozzo.com> > --- > v2v/convert_linux.ml | 2 +- > v2v/inspect_source.ml | 29 +++++++++++++++++++++-------- >

When the random-seed file is found, then avoid checking its existance again. --- customize/random_seed.ml | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/customize/random_seed.ml b/customize/random_seed.ml index e4c955e..1633aed 100644 --- a/customize/random_seed.ml +++ b/customize/random_seed.ml @@ -35,7 +35,7 @@ let rec set_random_seed (g : Guestfs.guestfs) root =

This doesn't change the C API, except that it is now permitted to pass NULL, NULL for the completion callback. For the Python and OCaml APIs the parameter changes to be an optional parameter. --- generator/generator | 36 +++++++++---------- ocaml/examples/asynch_copy.ml | 5 +-- .../test_505_aio_pread_structured_callback.ml | 12 ++++---

This doesn't change the C API, except that it is now permitted to pass NULL, NULL for the completion callback. For the Python and OCaml APIs the parameter changes to be an optional parameter. --- generator/generator | 36 +++++++++---------- ocaml/examples/asynch_copy.ml | 5 +-- .../test_505_aio_pread_structured_callback.ml | 12 ++++---