From mboxrd@z Thu Jan 1 00:00:00 1970 From: Russell King Subject: Re: Make ipconfig.c work as a loadable module. Date: Sat, 8 Mar 2003 16:19:36 +0000 Sender: netdev-bounce@oss.sgi.com Message-ID: <20030308161936.C1896@flint.arm.linux.org.uk> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Bogdan Costescu , Chris Dukes , Alan Cox , Jeff Garzik , Robin Holt , Linux Kernel Mailing List , netdev@oss.sgi.com Return-path: To: "Eric W. Biederman" Content-Disposition: inline In-Reply-To: ; from ebiederm@xmission.com on Sat, Mar 08, 2003 at 09:07:11AM -0700 Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org 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. /* * Decode any IP configuration options in the "ip=" or "nfsaddrs=" kernel * command line parameter. It consists of option fields separated by colons in * the following order: * * :::::: * * Any of the fields can be empty which means to use a default value: * - address given by BOOTP or RARP * - address of host returning BOOTP or RARP packet * - none, or the address returned by BOOTP * - automatically determined from , or the * one returned by BOOTP * - in ASCII notation, or the name returned * by BOOTP * - use all available devices * : * off|none - don't do autoconfig at all (DEFAULT) * on|any - use any configured protocol * dhcp|bootp|rarp - use only the specified protocol * both - use both BOOTP and RARP (not DHCP) */ ip=:::::eth0:dhcp (I haven't actually tried this though.) However, how do you configure your ramdisk via the boot loader to use a specific NIC / mount a specific filesystem, etc? -- Russell King (rmk@arm.linux.org.uk) The developer of ARM Linux http://www.arm.linux.org.uk/personal/aboutme.html