Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path. - Those who used our shipped install script, will end up in a none menu based syslinux shell. - Manual installers need to do the same or it will stay on the old version.
I think manual installers should know how to update a major version from syslinux.
Do we need a install message? And yes what should it mention?
Thanks for your input on this task. greetings tpowa
On 01/31/2013 12:09 PM, Tobias Powalowski wrote:
Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path.
Not all *.c32 modules, just what you want to use plus needed lib*.c32. (mostly libcom32.c32 and libutil.c32) [See output of readelf -d xxx.c32] and the most important ldlinux.c32
Please do this update after release of 2013.02 snapshot install medium, since some small things need to be changed to work.
Thanks.
Am 31.01.2013 16:53, schrieb Gerardo Exequiel Pozzi:
Not all *.c32 modules, just what you want to use plus needed lib*.c32. (mostly libcom32.c32 and libutil.c32) [See output of readelf -d xxx.c32] and the most important ldlinux.c32
Well, should this be mentioned somewhere? And if yes what exactly? I think it's bad to complicate an update message.
Please do this update after release of 2013.02 snapshot install medium, since some small things need to be changed to work.
Thanks.
When do you plan to release a new ISO?
greetings tpowa
On 01/31/2013 01:07 PM, Tobias Powalowski wrote:
Am 31.01.2013 16:53, schrieb Gerardo Exequiel Pozzi:
Not all *.c32 modules, just what you want to use plus needed lib*.c32. (mostly libcom32.c32 and libutil.c32) [See output of readelf -d xxx.c32] and the most important ldlinux.c32
Well, should this be mentioned somewhere? And if yes what exactly? I think it's bad to complicate an update message.
For upgrade/install message I guess, just "copy all *.c32 modules" seems to be fine, in the wiki could be documented with more detail what is needed really.
Please do this update after release of 2013.02 snapshot install medium, since some small things need to be changed to work.
Thanks.
When do you plan to release a new ISO?
Pierre does this, and will be tomorrow.
greetings tpowa
PS: At least, whichsys.c32 and ifcpu.c32 seems to be broken, I need to report to upstream (does not follow/execute labels)
Am 31.01.2013 17:07, schrieb Tobias Powalowski:
Am 31.01.2013 16:53, schrieb Gerardo Exequiel Pozzi:
Not all *.c32 modules, just what you want to use plus needed lib*.c32. (mostly libcom32.c32 and libutil.c32) [See output of readelf -d xxx.c32] and the most important ldlinux.c32
Well, should this be mentioned somewhere? And if yes what exactly? I think it's bad to complicate an update message.
Please do this update after release of 2013.02 snapshot install medium, since some small things need to be changed to work.
Thanks.
When do you plan to release a new ISO?
greetings tpowa
Pierre will probably push one out this weekend. We can keep syslinux in testing until then.
On 01/31/2013 12:09 PM, Tobias Powalowski wrote:
Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path.
- Those who used our shipped install script, will end up in a none menu
based syslinux shell.
- Manual installers need to do the same or it will stay on the old version.
I think manual installers should know how to update a major version from syslinux.
Do we need a install message? And yes what should it mention?
Thanks for your input on this task. greetings tpowa
kernel command line looks a bit weird, full path to kernel is added two times!, of course does not cause any harm. Just for example:
/init: eval: line 1: boot/i686/vmlinuz=y: not found /init: eval: line 1: boot/i686/vmlinuz=y: not found
# cat /proc/cmdline boot/i686/vmlinuz boot/i686/vmlinuz archisobasedir=arch archisolabel=ARCH_201301 initrd=boot/i686/archiso.img console=ttyS0
Am 31.01.2013 16:09, schrieb Tobias Powalowski:
Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path.
- Those who used our shipped install script, will end up in a none menu
based syslinux shell.
As long as we ship this install script we should maintain it. So this script needs to be altered to copy the needed files.
Am 31.01.2013 18:43, schrieb Pierre Schmitz:
Am 31.01.2013 16:09, schrieb Tobias Powalowski:
Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path.
- Those who used our shipped install script, will end up in a none menu
based syslinux shell.
As long as we ship this install script we should maintain it. So this script needs to be altered to copy the needed files.
The script has already been modified to at least to syslinux shell. If it should do more, Pyther needs to change it.
greetings tpowa
On 01/31/2013 12:09 PM, Tobias Powalowski wrote:
Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path.
- Those who used our shipped install script, will end up in a none menu
based syslinux shell.
- Manual installers need to do the same or it will stay on the old version.
I think manual installers should know how to update a major version from syslinux.
Do we need a install message? And yes what should it mention?
Thanks for your input on this task. greetings tpowa
I reported described issues to syslinux mailing list (looks like need approval, so I can not paste links now)
I still more time to research and report why PXE (gpxelinux.0) is broken with 5.01 (does not found UI or DEFAULT directive in config file).
On 02/01/2013 01:13 PM, Gerardo Exequiel Pozzi wrote:
On 01/31/2013 12:09 PM, Tobias Powalowski wrote:
Hi, ok syslinux 5.0 series should come to testing again. The problem with this release: You need to copy all .c32 modules to your /boot/syslinux path.
- Those who used our shipped install script, will end up in a none menu
based syslinux shell.
- Manual installers need to do the same or it will stay on the old version.
I think manual installers should know how to update a major version from syslinux.
Do we need a install message? And yes what should it mention?
Thanks for your input on this task. greetings tpowa
I reported described issues to syslinux mailing list (looks like need approval, so I can not paste links now)
I still more time to research and report why PXE (gpxelinux.0) is broken with 5.01 (does not found UI or DEFAULT directive in config file).
(please do not move syslinux 5.01 to [core], thanks)
Just for reference:
5.01 whichsys.c32 / ifcpu64.c32 does not execute labels http://www.syslinux.org/archives/2013-February/019423.html
5.01 BOOT_IMAGE= is missing in cmdline but path appears two times http://www.syslinux.org/archives/2013-February/019424.html
5.01 problems with gpxelinux.0 (file paths related TFTP and HTTP) http://www.syslinux.org/archives/2013-February/019426.html
(please do not move syslinux 5.01 to [core], thanks)
Just for reference:
5.01 whichsys.c32 / ifcpu64.c32 does not execute labels http://www.syslinux.org/archives/2013-February/019423.html
5.01 BOOT_IMAGE= is missing in cmdline but path appears two times http://www.syslinux.org/archives/2013-February/019424.html
5.01 problems with gpxelinux.0 (file paths related TFTP and HTTP) http://www.syslinux.org/archives/2013-February/019426.html
Any progress on this issues? Can syslinux be moved?
greetings tpowa
On 03/05/2013 08:51 AM, Tobias Powalowski wrote:
(please do not move syslinux 5.01 to [core], thanks)
Just for reference:
5.01 whichsys.c32 / ifcpu64.c32 does not execute labels http://www.syslinux.org/archives/2013-February/019423.html
Fixed (in -pre2)
5.01 BOOT_IMAGE= is missing in cmdline but path appears two times http://www.syslinux.org/archives/2013-February/019424.html
Fixed (in -pre2)
5.01 problems with gpxelinux.0 (file paths related TFTP and HTTP) http://www.syslinux.org/archives/2013-February/019426.html
Not fixed. Still waiting for final fix, Matt Fleming is working for it.
Any progress on this issues? Can syslinux be moved?
Please do not move it. But if you want to move, breaking PXE boot, at least use -pre3 version.
greetings tpowa
arch-dev-public@lists.archlinux.org