Hi,
Just noticed that IP-Config behavior when no ip= parm is used has changed in
2.2.18.
Up to 2.2.17 IP-Config was enabled even when ip= was omitted. I think that
it's good for use in i.e. diskless nodes.
Since 2.2.18, IP-Config does nothing at all until ip= is passed to the
kernel, however Documentation/nfsroot.txt still says that IP-Config is
enabled by default. Was that intentional change?
Such behavior remains in both 2.2.20 and 2.4.18-rc1. Following patches
(against these two kernel trees) make IP-Config enabled by default.
Cheers,
Krzysztof
PS
please CC, not a subscriber.
PS2
this was also sent to linux-net but got spamfiltered, i suppose
(checked on marc.theaimsgroup.com)
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:16 EST