similar to: global APPEND vs initrd= override

changing i386 COMMAND_LINE_SIZE to 1024 attached is a simplistic fix to change kernel's command-line size from 256 to 1024, tomatch capability in syslinux 3.08. It seems to work. Is this all there is to it ? One of the reasons I did this was to figure out what extra options are appearing, and why. b4 extending: (the last bit is truncated) Jun 4 06:31:05 truck kernel: Kernel command

folks, Im trying to boot to runlevel 4 explicitly, using this stanza: ie with a single 4 at end of APPEND line. LABEL 2.6.11-r10c2-soekris-v1 MENU LABEL ^j. runlevel 4 2.6.11-r10c2-soekris-v1 # 4 MENU DEFAULT KERNEL vmlinuz-2.6.11-r10c2-soekris-v1 APPEND console=ttyS0,19200n81 root=/dev/nfs nfsroot=192.168.42.1:/nfshost/foo

the following config-file triggers a couple of odd corner-cases in 3.08-pre5 ; SERIAL 0 19200 CONSOLE 0 APPEND console=ttyS0,19200n81 root=/dev/hda1 IMPLICIT 0 #DEFAULT sk1 #DEFAULT menu.c32 DEFAULT sk1 PROMPT 0 MENU TITLE Simple Boot Menu LABEL sk1 KERNEL vmlinuz-2.6.10-sk1 APPEND console=ttyS0,19200n81 root=/dev/nfs

hpa etal, Im trying to get PIRT running on an SBC which has no CD-ROM drive. (an 8 MB ISO which demo's RTAI - RealTime Application Interface, on linux patched with Adeos) (BTW, PIRT uses isolinux) anyway, Im trying to use pxelinux to chainload / memdisk / mboot it, Im having no success. Ive also tried booting memtest86, which I can boot on my laptop using grub, ie title memtest

1. \ at end of lines (in pxelinux.cfg/default, etc) causing/allowing line-wrap ? for those of us who prefer 80 column screens, and 1 item per line. 2. label-specific APPEND adds onto global APPEND ( currently replaces it IIUC ) maybe this needs a separate keyword ADDAPPEND (255 char limit still applies im sure) 3. strip trailing # comments ( I havent verified that it

Hi, I've got another one... NFS error 101 with NFSROOT has been discussed a lot, and hpa gave an answer to it which appears right. It's ENETUNREACH, and I suspect my diskless box does not set its IP parameters right. PXElinux is set up as follows: label linvdr kernel kernel-linvdr append initrd=initrd-linvdr acpi=off root=/dev/nfs \

I have released SYSLINUX 3.08-pre5. Sparse files should now work correctly in extlinux. Symlink support still needs to be added, though. -hpa

Hi, I am trying to load kernel 2.6.6 on a Soekris net4521 from the network using PXE. I built my initrd with mkinitrd. RedHat nash (while running linuxrc) hangs after mounting /proc and says "Creating block devices". I am using the pxelinux.0 from the syslinux-2.10 distribution and the kernel and initrd were built on redhat 9.0. I built my kernel with BLK_DEV_RAM, RAMFS, TMPFS,

Okay, now, before 3.10 is finalized... what bug reports am I still forgetting? -hpa

I have finished the work of transmitting sparc64 ROM parameters to kinit via the file /arch.cmd in rootfs. The result is pretty nice, as it gives a clean interface for any other architectures which want to collect architecture-specific options at initialization time. I have also merged my tree with v2.6.17-rc5, although it was a completely orthogonal merge set. The following issues are

SYSLINUX 3.11-pre5 is hereby a bug fix release candidate. If I don't receive any problem reports, I will release it as-is on Tuesday, August 30. http://www.kernel.org/pub/linux/utils/boot/syslinux/Testing/ -hpa

Hi, Thanks for your reply Josef. > In netstat -p |grep rpc I get: > dgram 56732 rpc.nfsd > dgram 55905 rpc.mountd > While client looks for socket 100003/2 or 100005/1, mine rpc.mountd is on socket 55905. Maybe it is a reason for an error 22. >The port numbers are RPC numbers, not sockets. Try 'rpcinfo -p' for these. rpcinfo -p 100005 mountd 100003 nfs So this looks

I have been successful with configuring TCP on a 2.4.23 kernel that was built with the "IP: kernel level autoconfiguration" turned on with the following append line: APPEND initrd=rootfs.gz root=/dev/ram0 rw ip=192.168.0.175::192.168.0.1:255.255.255.0 ^ ^ ^ | |

Sir or Madam, I am in a new project writing software for embedded apps. We use a single board computer consisting of (a) linux (b) syslinux boot loader (c) compact flash file system (d) x86 processor. (see www.embeddedx86.com) (e) other HW and SW. Using vendor provided files, I can easily prepare a compact flash (CF) system which boots 2.4.23 linux just fine. I can telnet in and so on and so

hey folks, Im using pxelinux to boot a Soekris box (which works fine to a default image) Ive added a bunch of LABEL, KERNEL pairs, but I cant read the display; Im buried in escape codes. Ive captured some of it to a typescript file: it starts out kosher, but goes unreadable rather quickly, 0005520 \r T F T P . 0005540 / \b \r 0005560 *

I get this when I type: brianherman at windows-8-[REDACTED] ~ $ nm libgcc_eh.a | grep register_frame nm: 'libgcc_eh.a': No such file brianherman at windows-8-[REDACTED] ~ $ nm libgcc_eh.a | grep register_fram nm: 'libgcc_eh.a': No such file brianherman at windows-8-[REDACTED] ~ $ On Tue, Jul 30, 2013 at 7:51 AM, Duncan Sands <baldrick at free.fr> wrote: > Hi

Hi Brian, On 29/07/13 23:42, Brian Herman wrote: > I got the following error while compiling llvm and clang under cygwin. > > /cygdrive/c/Users/brianherman/Desktop/llvm/llvm-3.3.src/Release+Asserts/lib/libLLVMMCJIT.a(SectionMemoryManager.o):SectionMemoryManager.cpp:(.text+0x3b): > undefined reference to `__register_frame' I register_frame is used to enable the debugger (gdb) to

Greetings all, Is there currently any mechanism in pxelinux the would send a mac address of the pxe booted interface through to the linux kernel much like ipappend can send the ip address? Kickstarting a system with multiple interfaces can be troublesome. ksdevice is helpful but only in some circumstances such as forcing eth0, but that doesn't always work since probe order changes depending

Hi. Version 0.5 of llvm-py, Python bindings for LLVM, has been released. This version supports (only) LLVM 2.4. New instructions of LLVM 2.4 (vicmp, vfcmp, insertvalue, extractvalue) are available. Home page: http://mdevan.nfshost.com/llvm-py/ Feedback welcome. Thanks & Regards, -Mahadevan.

llvm[2]: Compiling FileSystemStatCache.cpp for Release+Asserts build FileSystemStatCache.cpp: In static member function 'static bool clang::FileSystemStatCache::get(const char*, stat&, bool, int*, clang::FileSystemStatCache*)': FileSystemStatCache.cpp:63: error: 'openFileForRead' is not a member of 'llvm::sys::fs' make[2]: ***