similar to: chain.c32 memcmp bug

Displaying 20 results from an estimated 1000 matches similar to: "chain.c32 memcmp bug"

2014 Jun 29
0
[PATCH 4/6] chain: add missing pi_del() in find*() functions
As partiter doesn't deallocate itself after finish (anymore), it should be deleted after each loop iteration. diff --git a/com32/chain/chain.c b/com32/chain/chain.c index c08ec6e..f86cd7d 100644 --- a/com32/chain/chain.c +++ b/com32/chain/chain.c @@ -64,27 +64,23 @@ static int is_phys(uint8_t sdifs) static int find_by_sig(uint32_t mbr_sig, struct part_iter **_boot_part) { - struct
2010 Aug 08
1
PATCH/RFC chain.c: update iterator code, yank from chain.c, move both to separate directory
1) code split and move Iterator related functionality is yanked from chain.c and moved to iterator.{c,h}. Both are moved to com32/chain and this way chain.c is ready for further splitting. Alternatively, partiter could be moved to com32/lib at any time in the future. It's potentially useful for other modules (e.g. if someone wanted to code partition dumper or editor). 2) Iterator updates
2016 Jul 17
0
[PATCH] Restore - chain.c32: Allow both "guid" and "uuid"
The GPT specification calls it "guid", but the Unix world generally calls it "uuid". Ref. http://git.zytor.com/syslinux/syslinux.git/commit/?id=3905382 This restores "uuid" as a synonym for GPT "guid" --- com32/chain/chain.c | 3 ++- com32/chain/options.c | 2 ++ 2 files changed, 4 insertions(+), 1 deletion(-) diff --git a/com32/chain/chain.c
2012 Nov 06
50
chain.c32 (and partiter) updates v2
This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.
2016 Jul 17
0
[PATCH] : Adding dlabel option to chain.c32
On 16.07.2016 10:39, Erwan Velu wrote: > The idea is to boot a disk in an mbr fashion while using the GPT (not > filesystem) label to detect the disk. > > That is useful when you use grub2 & gpt. I was in case where my nodes > (100s) have 8 disks each and no guarantee of which disk is "bootable" in > the disk. > > This way I can tell "please boot the
2016 Jul 28
0
[PATCH] : Adding dlabel option to chain.c32
https://github.com/ErwanAliasr1/syslinux/commit/6993cc151a67f68673bf58372870b301a3d1022a sorry. 2016-07-28 15:52 GMT+02:00 Erwan Velu <erwanaliasr1 at gmail.com>: > That is perfectly true. I had a beautiful bug in the code .... Switching > from python to C have some weird side-effect. Indenting is not enough, > brackets are required.... > > So I pushed >
2016 Jul 28
2
[PATCH] : Adding dlabel option to chain.c32
That is perfectly true. I had a beautiful bug in the code .... Switching from python to C have some weird side-effect. Indenting is not enough, brackets are required.... So I pushed https://github.com/ErwanAliasr1/syslinux/commit/5a122d218553a6d4019273653ba9fad66d6ae79e with the fix. I tested it on my multi-disk system with success. I also changed the name of the function. 2016-07-17 8:21
2014 Jun 02
2
[PATCH] NTFS: fix incorrect file->offset usage in ntfs_readdir
file->offset is used to store position in index root between ntfs_readdir calls. Previously, pointer to buffer was stored in this field. However this buffer is reallocated and read each ntfs_readdir call so the pointer may become incorrect. Now offset in index root rather than pointer is stored in this field. Signed-off-by: Andy Alex <andy at r-tt.com> --- diff -uprN
2014 May 28
1
PXELINUX problems with 6.03-pre12
Hi, I have been using 6.03-pre11 lpxelinux.0 to deliver standard (TFTP) and HTTP based vmlinuz and kernel images. Things are working fine. When I upgraded the same to 6.03-pre12 it stopped working. On the console of the machine that is booting, is stalls infinitely at the line: PXELINUX 6.03 lwIP 6.03-pre12 Copyright (C) 1994-2014 H. Peter Anvin et al Screen shot attached. FWIW: 1. the
2013 Jan 09
1
gdisk dependancy problem
I followed the instructions here for enabling EHEL: http://www.thegeekstuff.com/2012/06/enable-epel-repository/ And tried to do a yum gdisk install on a new CentOS 6.2 fully updated install. yum install gdisk Loaded plugins: fastestmirror, security Loading mirror speeds from cached hostfile * base: mirror.flhsi.com * epel: www.gtlib.gatech.edu * extras: mirror.us.leaseweb.net * rpmforge:
2013 Oct 18
0
[RFC/PATCH 1/3] Move partiter from com32/chain to com32/lib/syslinux
From: Raphael S. Carvalho <raphael.scarv at gmail.com> MultiFS depends on the availability of partiter to find a partition. Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> --- com32/chain/Makefile | 2 +- com32/chain/chain.c | 4 +- com32/chain/mangle.c | 4 +- com32/chain/mangle.h | 2 +-
2015 Jul 22
0
[PULL 1/8] Move partiter from com32/chain to com32/lib/syslinux
From: "Raphael S. Carvalho" <raphael.scarv at gmail.com> MultiFS depends on the availability of partiter to find a partition. Cc: Gene Cumm <gene.cumm at gmail.com> Signed-off-by: Raphael S. Carvalho <raphael.scarv at gmail.com> Signed-off-by: Paulo Alcantara <pcacjr at zytor.com> --- com32/chain/Makefile | 2 +- com32/chain/chain.c
2014 Jun 02
0
[PATCH] NTFS: fix incorrect file->offset usage in ntfs_readdir
file->offset is used to store position in index root between ntfs_readdir calls. Previously, pointer to buffer was stored in this field. However this buffer is reallocated and read each ntfs_readdir call so the pointer may become incorrect. Now offset in index root rather than pointer is stored in this field. Signed-off-by: Andy Alex <andy at r-tt.com> --- diff -uprN
2014 Jun 20
0
testing out 6.03 network booting...
On Thu, Jun 19, 2014 at 2:51 PM, Andrew Rae <A.M.Rae at leeds.ac.uk> wrote: > Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. I'd say this is an excellent place to start. I'm getting some similar results here with the precompiled
2016 Jul 18
0
[PATCH] : Adding dlabel option to chain.c32
On 17.07.2016 17:21, Ady Ady via Syslinux wrote: >> >> As opposed to "label", >> "dlabel" ... >> https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf >> >> SeaBIOS / GRUB2 >> >> ... >> ... >> <target dev='vdc' bus='virtio'/> >> <boot order='3'/>
2014 Jun 20
0
testing out 6.03 network booting...
> Hi all, > > wasnt sure whether this was the best place to put this information; but something seems to have gone 'backwards' in the later pre-releases of 6.03 regarding network booting. > > below are results of me testing - i did each a few times to make sure they are valid results. > > hope it helps identify something that's gone awry ? > so far, 6.03
2016 Jul 17
2
[PATCH] : Adding dlabel option to chain.c32
> > As opposed to "label", > "dlabel" ... > https://github.com/ErwanAliasr1/syslinux/commit/ebf8cbf > > SeaBIOS / GRUB2 > > ... > ... > <target dev='vdc' bus='virtio'/> > <boot order='3'/> > ... > ... > <target dev='vdd' bus='virtio'/>
2014 Feb 09
1
isohybrid --mac doesn't find the mac efi image
On 02/08/14 17:40, Thomas Schmitt wrote: > -eltorito-id "MAC" \ thanks a lot, that seems to allow isohybrid --mac to work \o/ for the curious this is the image before and after isohybrid as shown by gparted * output from xorriso xorriso 1.3.2 : RockRidge filesystem manipulator, libburnia project. Drive current: -outdev 'stdio:../image.iso' Media current: stdio file,
2016 Jan 19
0
[PATCHv2 3/3] resize: preserve GPT disk GUID.
Changed disk GUID makes some OSes fail to boot. To enable virt-resize to support such OSes we have to preserve disk GUID. --- resize/resize.ml | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/resize/resize.ml b/resize/resize.ml index d6dd9a5..8ff4793 100644 --- a/resize/resize.ml +++ b/resize/resize.ml @@ -407,6 +407,13 @@ read the man page virt-resize(1).
2019 Apr 15
1
[PATCH] daemon: drop error message check in do_part_expand_gpt
part-expand-gpt takes extreme cautions and doesn't proceed to writing to the disk if the preliminary dry run of sgdisk has generated any warnings on stdout. This blocks the use of part-expand-gpt on disk shrink (with disk resize being the main usecase for part-expand-gpt), because sgdisk dry run produces a warning in that case. So remove the excessive safety check, and leave it up to the