similar to: Success!!

Hi again... The text under "BTX loader..." should appear as a block where each line is 56 characters long. "BTX halted" is on its own line. Apologies for my mailer... -Chris -----Original Message----- From: McMahon, Chris Sent: Wednesday, November 19, 2003 8:32 AM To: 'H. Peter Anvin'; McMahon, Chris Cc: 'syslinux at zytor.com'; 'mike at

The stack dump message is white text on black background. Right above the stack dump message, still in yellow-on-blue from the PXELINUX settings, is the text: Building the boot loader arguments Relocating the loader and the BTX Starting the BTX loader <change to white-on-black> BTX loader 1.00 BTX version is 1.01 <stack dump> Would that business of "arguments...

Hello... With syslinux pre7, I am consistently getting what looks like a stack dump out of the FreeBSD loader. I have seen this behavior from pxeboot before. Maybe once out of every fifty or so runs of pxeboot, I would see an error message like the one below, but it was both rare and inconsistent. Now I am getting this message every time pxelinux invokes pxeboot: BTX loader 1.00 BTX

Hello... In the split-second before the reboot, I can see that the pxeboot.0 process is indeed started-- pxeboot gets out just over 2 lines of text before the reboot occurs. So it's not a "ready" message. The text in question is (without *'s): ****************************************** PXE Loader 1.00 Building the boot loader arguments Relocating the loader and the

I've been working with Matt Burgess here on this problem, and have found the following: syslinux 3.08-pre10 ? broken >>> config.inc:max_cmd_len=255 syslinux 3.08-pre11 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.08 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre1 ? works >>> config.inc:max_cmd_len=1023 syslinux 3.09-pre2 ? broken

> > To be clear, I am not saying there is no bug - there might be. > I performed the following test with several versions of Syslinux: 1_ Execute: 'extlinux --once=non_default_label --install /mnt/sda1' ; 2_ In first reboot, the "non_default_label" should be executed; 3_ In second reboot, the default label should be executed. Results: _ 4.05 to 4.07: OK. _

> On 06/08/2014 02:58 PM, Ady wrote: > >> > >> To be clear, I am not saying there is no bug - there might be. > >> > > > > I performed the following test with several versions of Syslinux: > > > > 1_ Execute: > > 'extlinux --once=non_default_label --install /mnt/sda1' ; > > 2_ In first reboot, the

At first I thought, I was dealing with the known EBIOS/CBIOS-problem. The symptom was exactly the same (hangs at ...EBIOS). As 3.10-pre8 and 3.10-pre9, in contrary what was mentioned in the ML, did not bring any improvement, I looked deeper into what could be my specific problem. I found out that the program just halted at 'cmp [esi],edx' (line 658; ldlinux.asm 3.10-pre9)! By replacing

I have just released SYSLINUX 3.00-pre9. The only change versus 3.00-pre8 is that the MEMDISK query API now reports the boot loader ID byte, per Bernd's suggestion. This is a release candidate, and I plan to release it as 3.00 *tomorrow*, unless I hear back anything bad. -hpa

Hi All, A colleague of mine is using syslinux-3.20-pre8, syslinux.com, under DOS to install syslinux loader. It gives "sector read error". He re-compiled syslinux.com under a linux box, and used it successfully to install the loader from DOS. He is installing it on a hard drive (C:) He booted from a floppy and ran: "syslinux.com C:" at A:\ prompt He tried with

On 06/08/2014 02:58 PM, Ady wrote: >> >> To be clear, I am not saying there is no bug - there might be. >> > > I performed the following test with several versions of Syslinux: > > 1_ Execute: > 'extlinux --once=non_default_label --install /mnt/sda1' ; > 2_ In first reboot, the "non_default_label" should be executed; > 3_ In second

I have released SYSLINUX 1.75-pre9... it's just a simple one-line bug fix over -pre8. I expect this will be the final 1.75. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi... I''m interested to find out how many people are running tftp-hpa versus atftpd. I''m almost a bit surprised in how many people seem to be using tftp-hpa; for modern Unix systems (including Linux), I would in general assume atftpd to be a better choice. If you have tried both and specifically chosen (as opposed to "it was already installed", etc.) I''d

Hello everyone! We are working on writing a paper about testing the reliability of C compilers by using Csmith (a random C99 program generator). A previous testing effort, using Csmith, found 202 LLVM bugs, which represented 2% of all reported bugs at that time (PDF: https://www.flux.utah.edu/download?uid=114 <https://www.flux.utah.edu/download?uid=114>): . However, after this paper was

Hello... Last week I demonstrated a problem with PXELINUX's ability to launch the FreeBSD "pxeboot" program. Mr. Anvin suggests that this can be fixed. I'm glad, because this PXELINUX/pxeboot problem is the very last technical issue for a project on which I've been working since September. My company has a proprietary disk-imaging system that they would like to replace.

--k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi! It is my duty to inform you about this very unfortunate security issue in the IRC DCC connection tracking code. The following mail has just been sent to bugtraq, Linux Vendors have been informed two weeks in advance in order to prepare their advisories.

Hello, I have recently upgraded from an older version of OpenSSH to the newer 3.3p1 (first) and now to 3.4p1 - because of the discovered vulnerabilities. The default setting for these versions is to use privilege separation, and this seems to trigger some weird bug with my systems, causing sshd to consume memory until it barfs. Details: 1. OpenSSH 3.3p1, privsep on, compression on:

Hello everyone, I have released SYSLINUX 3.63. The main update is a fix to EXTLINUX, which would get confused by directories with deleted file entries. Special thanks to Stas Kysel of rPath, Inc. for spotting this problem and giving me an excellent test case; and of course to rPath, Inc. in general for being my employer and being extremely supportive of my SYSLINUX work! I have also

Hello... I have PXELINUX working nicely on FreeBSD, but I have exactly zero experience with Windows Server. What I would like to do is: Have PXE client connect to Windows DHCP server to get value "filename pxelinux.0" Have PXE client connect to Windows TFTP server to download pxelinux.0, display, pxelinux.cfg/default, memdisk, and appropriate initrd files (really bootable floppy

Tested floppy boot on two machines (one PII 350, one 486DX4) Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux kernel from floppy on the 2 machines. Tested with 3 different disquettes that were know to work, boot is reached after this very long time. Noise from floppy head make think floppy wait approximatly one minute between each read. No problem with pxe boot with