[Top] [All Lists]

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

To: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
Subject: Re: Make ipconfig.c work as a loadable module.
From: malware@xxxxxxxxxxx (Michael Mueller)
Date: Fri, 07 Mar 2003 22:33:07 +0100
Cc: Russell King <rmk@xxxxxxxxxxxxxxxx>, Jeff Garzik <jgarzik@xxxxxxxxx>, Robin Holt <holt@xxxxxxx>, Linux Kernel Mailing List <linux-kernel@xxxxxxxxxxxxxxx>, netdev@xxxxxxxxxxx
References: <Pine.LNX.4.44.0303061500310.31368-100000@xxxxxxxxxxxxxxxxxxxxxxxxx> <1046990052.18158.121.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030306221136.GB26732@xxxxxxx> <20030306222546.K838@xxxxxxxxxxxxxxxxxxxxxx> <1046996037.18158.142.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <20030306231905.M838@xxxxxxxxxxxxxxxxxxxxxx> <1046996987.17718.144.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <200303070715.IAA27138@xxxxxxxxxxxxxxx> <1047041676.20793.12.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: netdev-bounce@xxxxxxxxxxx
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.



<Prev in Thread] Current Thread [Next in Thread>