Followup to: <20020218222451.GA23899@main.braxis.co.uk>
By author: Krzysztof Rusocki <kszysiu@main.braxis.co.uk>
In newsgroup: linux.dev.kernel
>
> 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.
>
I don't think this is a good idea. The current behaviour should work
across the board. Diskless nodes should use a diskless bootloader
which support command lines -- that way you get to specify the mode as
well. *ALL* nodes should use the command line these days.
Can we get rid of the g----d bootsect.S, please?
-hpa
-- <hpa@transmeta.com> at work, <hpa@zytor.com> in private! "Unix gives you enough rope to shoot yourself in the foot." http://www.zytor.com/~hpa/puzzle.txt <amsp@zytor.com> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Feb 23 2002 - 21:00:16 EST