Skip to contentSkip to conversation

syslinux: Upgrade to 6.02

PATCH In review Khem Raj 2 participants 4 messages Nov 3, 2013 – Nov 10, 2013

lore
Share & tools
lore

Khem Raj

author
#0 lore raw

PATCH 1/1 syslinux: Upgrade to 6.02

---
 .../recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} | 5 ++---
 1 file changed, 2 insertions(+), 3 deletions(-)
 rename meta/recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} (94%)
meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +2 -3
similarity index 94%
rename from meta/recipes-devtools/syslinux/syslinux_6.01.bb
rename to meta/recipes-devtools/syslinux/syslinux_6.02.bb
index 4438ea8..b4ba0ad 100644
@@ -9,9 +9,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
 DEPENDS = "nasm-native util-linux"
 
 SRC_URI = "${KERNELORG_MIRROR}/linux/utils/boot/syslinux/6.xx/syslinux-${PV}.tar.bz2"
-
-SRC_URI[md5sum] = "6945ee89e29119d459baed4937bbc534"
-SRC_URI[sha256sum] = "83a04cf81e6a46b80ee5a321926eea095af3498b04317e3674b46c125c7a5b43"
+SRC_URI[md5sum] = "5410b1c2614cc8375bfc92fe308ca5c8"
+SRC_URI[sha256sum] = "16027cbc1a7d18a48f3d26fbea771896d892cb43860b8d2f596baef7f2789b6e"
 
 COMPATIBLE_HOST = '(x86_64|i.86).*-(linux|freebsd.*)'
 # Don't let the sanity checker trip on the 32 bit real mode BIOS binaries
Signature · 1 line
1.8.3.2
#1 lore raw
Quoted 15 lines · Khem Raj
---
  .../recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} | 5 ++---
  1 file changed, 2 insertions(+), 3 deletions(-)

rename meta/recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} (94%)

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +0 -0
similarity index 94%
rename from meta/recipes-devtools/syslinux/syslinux_6.01.bb
rename to meta/recipes-devtools/syslinux/syslinux_6.02.bb
index 4438ea8..b4ba0ad 100644
@@ -9,9 +9,8 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
  DEPENDS = "nasm-native util-linux"

meta/recipes-devtools/syslinux/syslinux_6.02.bb LIC_FILES_CHKSUM = "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \ · line 16

Quoted 10 lines
meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +2 -3
 
  SRC_URI = "${KERNELORG_MIRROR}/linux/utils/boot/syslinux/6.xx/syslinux-${PV}.tar.bz2"
-
-SRC_URI[md5sum] = "6945ee89e29119d459baed4937bbc534"
-SRC_URI[sha256sum] = "83a04cf81e6a46b80ee5a321926eea095af3498b04317e3674b46c125c7a5b43"
+SRC_URI[md5sum] = "5410b1c2614cc8375bfc92fe308ca5c8"
+SRC_URI[sha256sum] = "16027cbc1a7d18a48f3d26fbea771896d892cb43860b8d2f596baef7f2789b6e"
 
  COMPATIBLE_HOST = '(x86_64|i.86).*-(linux|freebsd.*)'
  # Don't let the sanity checker trip on the 32 bit real mode BIOS binaries

Note that syslinux 6.02 has a known bug which corrupts the superblock when used on BTRFS volumes due to ldlinux.sys exceeding 64000 bytes. It fixes booting memtest86+ with pxelinux though (see https://bugzilla.yoctoproject.org/show_bug.cgi?id=5501).

Regards,
Jonathan

author
#2 lore raw
Quoted 30 lines · Jonathan Liu
Quoted 29 lines · Khem Raj
---
  .../recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} | 5
++---
  1 file changed, 2 insertions(+), 3 deletions(-)

rename meta/recipes-devtools/syslinux/{syslinux_6.01.bb =>
syslinux_6.02.bb} (94%)

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +0 -0
similarity index 94%
rename from meta/recipes-devtools/syslinux/syslinux_6.01.bb
rename to meta/recipes-devtools/syslinux/syslinux_6.02.bb
index 4438ea8..b4ba0ad 100644
@@ -9,9 +9,8 @@ LIC_FILES_CHKSUM =
 "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
  DEPENDS = "nasm-native util-linux"
    SRC_URI =

"${KERNELORG_MIRROR}/linux/utils/boot/syslinux/6.xx/syslinux-${PV}.tar.bz2"

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +0 -3
-
-SRC_URI[md5sum] = "6945ee89e29119d459baed4937bbc534"
-SRC_URI[sha256sum] =

"83a04cf81e6a46b80ee5a321926eea095af3498b04317e3674b46c125c7a5b43"

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +2 -0
+SRC_URI[md5sum] = "5410b1c2614cc8375bfc92fe308ca5c8"
+SRC_URI[sha256sum] =

"16027cbc1a7d18a48f3d26fbea771896d892cb43860b8d2f596baef7f2789b6e"

Quoted 8 lines
Quoted 3 lines
    COMPATIBLE_HOST = '(x86_64|i.86).*-(linux|freebsd.*)'

# Don't let the sanity checker trip on the 32 bit real mode BIOS
binaries

Note that syslinux 6.02 has a known bug which corrupts the superblock when used on BTRFS volumes due to ldlinux.sys exceeding 64000 bytes. It fixes booting memtest86+ with pxelinux though (see
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5501).

so it fixes one and regresses 1 and then for third one we can backport a patch is btrfs volume issue a blocker ? if not I would say a v2 with
http://git.kernel.org/cgit/boot/syslinux/syslinux.git/commit/?h=firmware&id=4ac63b5ac412d54462e292daf65a309775bc0448
applied would be good.
atleast it will give us more testing and time to find issues before 6.03 comes out

Quoted 3 lines

Regards,
Jonathan

#3 lore raw
Quoted 38 lines · Khem Raj
Quoted 28 lines · Jonathan Liu
Quoted 27 lines · Khem Raj
---
   .../recipes-devtools/syslinux/{syslinux_6.01.bb => syslinux_6.02.bb} | 5
++---
   1 file changed, 2 insertions(+), 3 deletions(-)

rename meta/recipes-devtools/syslinux/{syslinux_6.01.bb =>
syslinux_6.02.bb} (94%)

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +0 -0
similarity index 94%
rename from meta/recipes-devtools/syslinux/syslinux_6.01.bb
rename to meta/recipes-devtools/syslinux/syslinux_6.02.bb
index 4438ea8..b4ba0ad 100644
@@ -9,9 +9,8 @@ LIC_FILES_CHKSUM =
 "file://COPYING;md5=0636e73ff0215e8d672dc4c32c317bb3 \
   DEPENDS = "nasm-native util-linux"
     SRC_URI =

"${KERNELORG_MIRROR}/linux/utils/boot/syslinux/6.xx/syslinux-${PV}.tar.bz2"

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +0 -3
-
-SRC_URI[md5sum] = "6945ee89e29119d459baed4937bbc534"
-SRC_URI[sha256sum] =

"83a04cf81e6a46b80ee5a321926eea095af3498b04317e3674b46c125c7a5b43"

meta/recipes-devtools/syslinux/syslinux_6.02.bb renamed from meta/recipes-devtools/syslinux/syslinux_6.01.bb +2 -0
+SRC_URI[md5sum] = "5410b1c2614cc8375bfc92fe308ca5c8"
+SRC_URI[sha256sum] =
Quoted 8 lines
Quoted 4 lines

"16027cbc1a7d18a48f3d26fbea771896d892cb43860b8d2f596baef7f2789b6e"

     COMPATIBLE_HOST = '(x86_64|i.86).*-(linux|freebsd.*)'

# Don't let the sanity checker trip on the 32 bit real mode BIOS
binaries

Note that syslinux 6.02 has a known bug which corrupts the superblock when used on BTRFS volumes due to ldlinux.sys exceeding 64000 bytes. It fixes booting memtest86+ with pxelinux though (see
https://bugzilla.yoctoproject.org/show_bug.cgi?id=5501).

Quoted 9 lines

so it fixes one and regresses 1 and then for third one we can backport a patch is btrfs volume issue a blocker ? if not I would say a v2 with
http://git.kernel.org/cgit/boot/syslinux/syslinux.git/commit/?h=firmware&id=4ac63b5ac412d54462e292daf65a309775bc0448
applied would be good.
atleast it will give us more testing and time to find issues before 6.03 comes out

Quoted 2 lines

Regards,
Jonathan

I don't know of anyone using BTRFS volumes in production. It's not a blocker for me at least.

Regards,
Jonathan