On Tue, Feb 11, 2003 at 04:19:24PM -0500, Daniel Barclay wrote: > I wrote: > > > ... > > Next, it says: > > > > Herbert Xu wrote: > > No it does not, all you have to do to use a filesystem other > > than CRAMFS is to set MKIMAGE in /etc/mkinitrd/mkinitrd.conf. > > > > Of course, it doesn't say anything about what you can set MKIMAGE to > > [to] do that. > > > > My etc/mkinitrd/mkinitrd.conf says: > > > > MKIMAGE='mkcramfs %s %s > /dev/null' > > > > but no other mk*fs executable on my system takes the same arguments > > that mkcramfs does. > > Okay, I found and installed genromfs. That got a ramdisk built. > > Unfortunately, it was too big. > > Fortunately, lilo's ramdisk=xxx option solved that problem. > > Unfortunately, after the booting kernel says that it found a > romfs file system, it says: > > cramfs: bad magic > > > So how do I get the kernel to access a romfs initrd image? > > Or is there a way to make a cramfs filesystem? Ah...I've often wondered what changes Debian makes to mainline kernels in the kernel-source packages, and I guess we have our answer :) I guess if you're really set on making initrd-ified kernel, you'll need to get the Debian kernel source. This is a rather large download, but I'm fairly sure there is a short cut: instead of getting the full source tree, just go get the patch Debian applies to it; it'll be in the pool on your local mirror, you want 'kernel-source-2.4.20.diff.gz'. Either that, or go find the cramfs patch's upstream and download it directly. I must say, I've never really played with cramfs and initrds before, so please excuse me if I'm completely wrong :) > (Recall that I'm trying to build from vanilla kernel sources (2.4.20), > not from Debian-patches sources (latest 2.4.18 in woody).) You can just get it from the sid section; from a quick look at it's dependencies, it appears it'll work fine on sarge or woody. -- Rob Weir <rweir@ertius.org> http://ertius.org/
Attachment:
pgpp1MYl8ALjF.pgp
Description: PGP signature