Messages in this thread Patch in this message | | | Date | Fri, 29 Mar 2002 10:36:07 +0000 (GMT) | From | Tigran Aivazian <> | Subject | Re: mkinitrd w/ 2.4.18 |
| |
On Thu, 28 Mar 2002, Matthew Walburn wrote:
> 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:
diff -ur mkinitrd-3.2.6-orig/mkinitrd mkinitrd-3.2.6/mkinitrd --- mkinitrd-3.2.6-orig/mkinitrd Wed Sep 5 21:38:18 2001 +++ mkinitrd-3.2.6/mkinitrd Fri Mar 1 09:34:22 2002 @@ -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
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |