kumon at flab.fujitsu.co.jp
2003-Sep-14 18:55 UTC
FWD: [syslinux] Network Boot IP Configuration Dilemma
If you want eth0 to be used and no dynamic IP configuration request should not occur in the Linux kernel, specify *both* APPEND and IPAPPEND options like: APPEND ip=:::::eth0:none IPAPPEND 1 It's very tricky but it works, at least Linux 2.4.18 which I tested. The IP-PNP routine in the kernel doesn't modify values if the option values are not explicitly specified. IPAPPEND doesn't provide the <device> option and <autoconf> option, so the values for the options set by the previous APPEND will survive. K.Kumon>Fred Feirtag wrote:> I never wanted to "always" do that. My hack always does that, but > my suggestion was maintain the "1" flag for the current behavior, > but have any other string passed through as the device: > IPAPPEND 1 > --same as now > IPAPPEND eth0 > --passes ip=#:#:#:#::eth0: > IPAPPEND eth1 > --passes ip=#:#:#:#::eth1: > IPAPPEND fd0 > --passes ip=#:#:#:#::fd0: for fddi devices or whatever. > Of course something like > IPDEVAPPEND eth0 > would be good or even better.
H. Peter Anvin
2003-Sep-15 04:22 UTC
FWD: [syslinux] Network Boot IP Configuration Dilemma
kumon at flab.fujitsu.co.jp wrote:> If you want eth0 to be used and no dynamic IP > configuration request should not occur in the Linux > kernel, specify *both* APPEND and IPAPPEND options > like: > > APPEND ip=:::::eth0:none > IPAPPEND 1 > > It's very tricky but it works, at least Linux 2.4.18 > which I tested. The IP-PNP routine in the kernel > doesn't modify values if the option values are not > explicitly specified. IPAPPEND doesn't provide the > <device> option and <autoconf> option, so the values > for the options set by the previous APPEND will > survive. >Excellent... -hpa
Hey that's great! It certainly does work, and as long as each "ip=" on the cmdline repeatedly sets up a call to ip_auto_config_setup (in ipconfig.c) and user_dev_name is a static variable (initialized only once by the compiler), it looks like it will continue to work. I can't believe I failed to try it that way. Thanks!!! --Fred kumon at flab.fujitsu.co.jp wrote:>If you want eth0 to be used and no dynamic IP >configuration request should not occur in the Linux >kernel, specify *both* APPEND and IPAPPEND options >like: > >APPEND ip=:::::eth0:none >IPAPPEND 1 > > >
Reasonably Related Threads
- pxelinux: 2.04 works but 2.09 doesn't
- Network Boot IP Configuration Dilemma
- [bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
- [bug] Syslinux-5.11-pre2: IPAPPEND/SYSAPPEND inconsistent base
- [5.11-pre1] SYSAPPEND does not work (IPAPPEND alias works)