Im trying to get 2.6.17-rc4-mm1 (which includes klibc) working on an nfs-root setup. Its not working, so I started adding printf()s (not printk()s !) 1st thing I notice is arg5 is empty, but arg 6 is real I could imagine this unexpected situation confusing kinit (will check..) Or is that empty arg intentional, so that it marks the beginning of pxelinux addons ? kinit:main: init-arg 0: /init cmd-arg 0: /init cmd-arg 1: console=ttyS0,115200n81 cmd-arg 2: root=/dev/nfs cmd-arg 3: ip=::::soekris:eth0 cmd-arg 4: panic=5 cmd-arg 5: cmd-arg 6: BOOT_IMAGE=vm[ 28.428147] eth0: DSPCFG accepted after 0 usec. [ 28.433724] eth0: link up. [ 28.436495] eth0: Setting full-duplex based on negotiated link capability. linuz-2.6.17-rc4-mm1-sk Running ipconfig OK, I just did another test, introducing extra whitespaces int APPEND string. result is not good. Whitespace ended up as lead char in 2 args so ' ip=<stuff>' was not recognized LABEL H 2.6.17-rc4-mm1-sk MENU LABEL ^h. 2.6.17-rc4-mm1-sk KERNEL vmlinuz-2.6.17-rc4-mm1-sk APPEND console=ttyS0,115200n81 root=/dev/nfs ip=::::soekris:eth0 panic=5 kinit:main: init-arg 0: /init cmd-arg 0: /init cmd-arg 1: console=ttyS0,115200n81 cmd-arg 2: root=/dev/nfs cmd-arg 3: ip=::::soekris:eth0 cmd-arg 4: panic=5 cmd-arg 5: cmd-arg 6: BOOT_IMAGE=vmlinuz-2.6.17-rc4-mm1-sk Running ipconfig IP-Config: argc == 2 argv[1]: '-n' IP-Config: no devices to configure kinit: do_mounts kinit: name_to_dev_t(/dev/nfs) = dev(0,255) kinit: root_dev = dev(0,255) Ro[ 25.030001] Kernel panic - not syncing: Attempted to kill init! ot-NFS: no serve[ 25.037537] r defined <0>Rebooting in 5 seconds.. I think this qualifies as a bug; its not what folks expect. A docpatch WITH LARGE LETTERS would rectify it, if you want to preserve this behavior. Also, APPEND doc should probably say that stanza-specific APPENDs dont append to global APPENDs, they overrride it. I'll write the docpatch if you like. tia -jimc
Jim Cromie
2006-May-19 16:06 UTC
[syslinux] Re: pxelinux cmdline preparation for klibc kinit
Jim Cromie wrote:> > I think this qualifies as a bug; its not what folks expect. > A docpatch WITH LARGE LETTERS would rectify it, if you want to > preserve this behavior.let me temper that .. I just tested a non-klibc kernel with extra spaces in APPEND, all went smoothly, so from that perspective, its kinit which is too sensitive, and pxelinux is (maybe) doing the correct-minimum thing, and passing the string thru without otherwize touching it. I also just tested this (note the panic=15 on KERNEL spec) LABEL D 2.6.17-rc3-mm1-addhrt-sk MENU LABEL ^d. 2.6.17-rc3-mm1-addhrt-sk KERNEL vmlinuz-2.6.17-rc3-mm1-addhrt-sk panic=15 APPEND console=ttyS0,115200n81 root=/dev/nfs ip=::::soekris:eth0 panic=5 this booted as: [ 23.612311] Kernel command line: panic=15 console=ttyS0,115200n81 root=/dev/nfs ip=::::soekris:eth0 panic=5 BOOT_IMAGE=vmlinuz-2.6.17-rc3-mm1-addhrt-sk Note that the panic=15 came thru, and was appended to afterwards. Is this intentional, another consequence of minimal string handling, or other ? Its perhaps what this doc-bit is alluding to: APPEND options... Add one or more options to the kernel command line. These are added both for automatic and manual boots. The options are added at the very beginning of the kernel command line, (especially this part) usually permitting explicitly entered kernel options to override them. This is the equivalent of the LILO "append" option. but maybe Im imagining it. Also, while Im at it, this paragraph suggests that order of arg processing matters in the kernel. Is there rule / default / unstated-standard wrt last-one-wins, (ie panic=5) (I looked in Doc/kernel-parameters)> Also, APPEND doc should probably say that stanza-specific APPENDs > dont append to global APPENDs, they overrride it. > I'll write the docpatch if you like.heres a -p0 patch FYC> > tia > -jimc >-------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: patch-doc URL: <http://www.zytor.com/pipermail/syslinux/attachments/20060519/445f34b0/attachment.ksh>