mkinitrd w/ 2.4.18
hi there,
i'm having problems getting mkinitrd to work with 2.4.18 in a redhat 7.2 system. are there any kernel options that i should be aware of to get this to work properly that i'm somehow missing?
thanks
-matt
Signature · 5 lines
o--------------------oo0oo-------------------------o | matthew walburn | mit dept. of mathematics | | network staff asst. 0 building 2 - room 236 | | [email protected] 0 77 massachusetts avenue | o--------------------oo0oo-------------------------o
Quoted 6 lines · Matthew Walburn
hi there,
i'm having problems getting mkinitrd to work with 2.4.18 in a redhat 7.2 system. are there any kernel options that i should be aware of to get this to work properly that i'm somehow missing?
thanks
-matt
Try this patch:
mkinitrd Fri Mar 1 09:34:22 2002 renamed from mkinitrd Wed Sep 5 21:38:18 2001 +3 -3
@@ -309,9 +309,9 @@ echo "Using modules: $MODULES" fi -MNTIMAGE=`mktemp -d /tmp/initrd.XXXXXX` -IMAGE=`mktemp /tmp/initrd.img.XXXXXX` -MNTPOINT=`mktemp -d /tmp/initrd.mnt.XXXXXX` +MNTIMAGE=$(mktemp -d $TMPDIR/initrd.XXXXXX) || exit 1 +IMAGE=$(mktemp $TMPDIR/initrd.img.XXXXXX) || exit 1 +MNTPOINT=$(mktemp -d $TMPDIR/initrd.mnt.XXXXXX) || exit 1 RCFILE=$MNTIMAGE/linuxrc if [ -z "$MNTIMAGE" -o -z "$IMAGE" -o -z "$MNTPOINT" ]; then
As far as I know Red Hat's latest mkinitrd (in rawhide?) has fixed this problem. Also, don't forget to set TMPDIR to somewhere other than a tmpfs filesystem. You see, you cannot bind regular files on a tmpfs to loopback devices.
Regards,
Tigran
Thanks everyone for the advice, it's now working. Embarringly enough it was a simple case of insmoding loop.o.
thanks again.
matt