Andreas Kotes
2007-Jan-16 16:24 UTC
[syslinux] ONERROR not triggered in PXELINUX 3.31 when ramdisk missing
Hello, I tested some things, and found the following: when the kernel image file is present, but the initrd image is not, ONERROR is not called, and PXELINUX stays in the prompt forever ... Other error scenarios tested okay, a down/unresponding TFTP server can lead to 15-20 minutes delay until all tried filenames timeout out ... Just to let you know :) Andreas -- "The problem is not how to wipe out all differences, but how to unite with all differences intact" -- Tagore "God is a comedian playing to an audience too afraid to laugh." -- H.L.Mencken
H. Peter Anvin
2007-Jan-16 18:09 UTC
[syslinux] ONERROR not triggered in PXELINUX 3.31 when ramdisk missing
Andreas Kotes wrote:> Hello, > > I tested some things, and found the following: > > when the kernel image file is present, but the initrd image is not, > ONERROR is not called, and PXELINUX stays in the prompt forever ... >Looking at the implementation, this begs the question: should ONERROR get executed if the user presses <Esc> to abort a kernel download? Right now, this is handled through the same code path.> Other error scenarios tested okay, a down/unresponding TFTP server can > lead to 15-20 minutes delay until all tried filenames timeout out ...Hard to avoid, although I'm interested in suggestions. -hpa
Reasonably Related Threads
- memdisk from 3.36 crashing on Dell PowerEdge 1955
- Fallback to second menu entry, ONERROR looping forever
- syslinux et al misbehave severely when BOOT_IMAGE= is present on append-line already
- tftp-hpa standalone in foreground
- Fallback to second menu entry, ONERROR looping forever