Re: [PATCH] initrd with devfs enabled (Re: initrd and 2.6.0-test8)

From: Arkadiusz Miskiewicz
Date: Sat Oct 18 2003 - 17:02:01 EST


On Saturday 18 of October 2003 21:41, viro@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
wrote:
> OK, that should do it - the problems happened if you had devfs
> enabled; in that case late-boot code does temporary mount of devfs over
> rootfs /dev, which made /dev/initrd inaccessible. For setups without
> devfs that didn't happen.
>
> Fix is trivial - put the file in question outside of /dev; IOW,
> we simply replace "/dev/initrd" with "/initrd.image" in init/*. It works
> here; please check if it fixes all initrd problems on your boxen.
Works fine for me.

btw. is it possible to do not use initrd with some fs and instead use external
initramfs image?

I've tried to create initramfs image with unpacking initrd image, mounting it
over loop and creating cpio archive from that (find . | cpio -o -c >
../x.cpio), gzipping that cpio and placeing it instead of old initrd at
/boot/initrd + lilo reload.

It doesn't work that way unfortunately (test8 with your patch).
--
Arkadiusz Miśkiewicz CS at FoE, Wroclaw University of Technology
arekm.pld-linux.org AM2-6BONE, 1024/3DB19BBD, arekm(at)ircnet, PLD/Linux

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/