From mboxrd@z Thu Jan 1 00:00:00 1970 From: malware@t-online.de (Michael Mueller) Subject: Re: Make ipconfig.c work as a loadable module. Date: Fri, 07 Mar 2003 22:33:07 +0100 Sender: netdev-bounce@oss.sgi.com Message-ID: <200303072132.WAA02244@fire.malware.de> References: <1046990052.18158.121.camel@irongate.swansea.linux.org.uk> <20030306221136.GB26732@gtf.org> <20030306222546.K838@flint.arm.linux.org.uk> <1046996037.18158.142.camel@irongate.swansea.linux.org.uk> <20030306231905.M838@flint.arm.linux.org.uk> <1046996987.17718.144.camel@irongate.swansea.linux.org.uk> <200303070715.IAA27138@fire.malware.de> <1047041676.20793.12.camel@irongate.swansea.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: Russell King , Jeff Garzik , Robin Holt , Linux Kernel Mailing List , netdev@oss.sgi.com Return-path: To: Alan Cox Errors-to: netdev-bounce@oss.sgi.com List-Id: netdev.vger.kernel.org Hi Alan, you wrote: > > Sorry, but I must join Russel here. I have atleast one machine which has > > a bootloader able to load exactly one file only. There is currently no > > way to load an initrd. It would need to implement the whole (BOOTP+)TFTP > > stuff again, just to get the initrd. So I was quite happy linux 2.4 > > still knows about mounting a NFS root filesystem without user-space > > help. > > Just glue the initrd to the kernel. This is not rocket science Do you have a sort of glue fixing the ramdisk support on m68k to support physically non-continous memory too? Otherwhise I have only 1 MiB for the whole initrd. So hopefully the removal of ipconfig.c, if decided for, does not propagate back into the 2.4 series. It would add a heap of useless work to do, just to get it up again. Michael -- Linux@TekXpress http://www-users.rwth-aachen.de/Michael.Mueller4/tekxp/tekxp.html