Re: Make ipconfig.c work as a loadable module.

[ebiederm@xmission.com (Eric W. Biederman)]

Russell King <rmk@arm.linux.org.uk> writes:

> On Sat, Mar 08, 2003 at 09:07:11AM -0700, Eric W. Biederman wrote:
> > With a good bootloader it does not much how big your initrd is.  I
> > totally agree that small is good and important.  At the same time
> > ipconfig.c is wrong.  It is great during development and on systems
> > with a single NIC.  But the hard coded policies can be bad for
> > production systems.  Not that hard coded policies are bad in general
> > just the kernel is the wrong place to put them.
> 
> With multi-NIC systems, it is perfectly possible to use ipconfig.c with
> one specific interface.

Sorry.  I expressed that wrong.  It is not multi-NIC that ipconfig.c gets
wrong.  It is multiple DHCP servers.   You just get multiple dhcp
servers when you have multiple NICs.

The policies in ipconfig.c are quite good, they just are not
universally applicable.  But as ipconfig.c is in the kernel it tends
to get used where it is inappropriate.

> ip=:::::eth0:dhcp
> 
> (I haven't actually tried this though.)

I had forgotten about that one, and I believe it helps in some cases.
 
> However, how do you configure your ramdisk via the boot loader to use
> a specific NIC / mount a specific filesystem, etc?

I can change the contents of my ramdisk as easily as I can change
the kernel command line.  For the complex setups just placing
a configuration file in the ramdisk is what seems to work the best
in practice.

Eric