The patch at the end of this email makes ipconfig.c work as a loadable module under the 2.5. The diff was taken against the bitkeeper tree changeset 1.1075. Currently ipconfig.o must get statically l
The right fix is to delete ipconfig.c, it has been the right fix for a long long time. There are initrd based bootp/dhcp setups that can also then mount a root NFS partition and they do *not* need an
The klibc tarball on kernel.org also has ipconfig-type code, waiting for initramfs early userspace :) Many have wanted to delete ipconfig.c for a while now... Jeff
Yep, can't the deletion wait a couple more weeks or so until klibc gets merged? It's not like ipconfig.c is broken currently, is it? -- Russell King (rmk@xxxxxxxxxxxxxxxx) The developer of ARM Linux
"klibc doesnt really matter" I'd prefer not to have to have thousands of special programs around just to be able to boot my machines, especially when it was all inkernel up until this point. klibc ye
You can build the dhcp client with glibc static into your initrd. Its hardly magic or special programs or random garbage, and last time I counted it came to one program. Dunno what the other 999 util
How about mount for nfs-root, a shell and a shell script to supply the correct parameters to mount so it doesn't go and try to mount the nfs-root with locking enabled - oh, and a few programs like se
If IBM can fit a kernel and a ramdisk containing all the utilities you describe and more in smaller than 5M of file for tftp, one would think that it could be done on Linux. That's nice. Would you mi
Hi Alan, 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 implem
Wow. 5MB eh? We currently do NFS-root in 690K. If you're suggesting above that "5MB isn't significantly larger than the size Linux can do this" then I think I've just proven you wrong. Lets see - bui
... and the size is not important only because we want to make everything smaller, but because of how it's commonly used (at least in the clustering world from which I come): the mainboard BIOS or NI
The 5Mb example is AIX. I said userspace. I did not say existing binaries. [Size comparison of the kitchen sink vs kernel code deleted because it's comparing apples and oranges]. You are asserting ae
Think _embedded_. Think "cost of flash chips". Think "not everything has a floppy disk". I'm sorry, believe it or not, but I'm not swayed by "business benefits" here. Although I have my own business
As the kernel changes there are some things that really need to remain. You need to be able to boot from a "floppy" disk. Yes, now-days it's probably not a real floppy, but a BIOS module that emulate
Hi Alan, 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 i
There's a cap on the maximum size of things various bootloaders can load via tftp; 2MB is relatively certain to blow it. ISTR the limit being something near 1MB for 2 of my boxen. -- wli