Re: Recent changes broke mkinitrd?

Andrew Morton (akpm@digeo.com)
Thu, 17 Apr 2003 11:40:16 -0700


Stephen Hemminger <shemminger@osdl.org> wrote:
>
> Recent (post 2.5.67) versions of the kernel break the creation
> of the initial ram disk.

hmm, so it did. It'll be the ext2 changes. mkinitrd works OK if you use
ext3:

--- mkinitrd.orig 2003-04-17 11:38:49.000000000 -0700
+++ mkinitrd 2003-04-17 11:39:01.000000000 -0700
@@ -473,7 +473,7 @@

# We have to "echo y |" so that it doesn't complain about $IMAGE not
# being a block device
-echo y | mke2fs $LODEV $IMAGESIZE >/dev/null 2>/dev/null
+echo y | mke2fs -j $LODEV $IMAGESIZE >/dev/null 2>/dev/null
tune2fs -i0 $LODEV >/dev/null

if [ -n "$verbose" ]; then
@@ -481,7 +481,7 @@
fi

mkdir -p $MNTPOINT
-mount -t ext2 $LODEV $MNTPOINT || {
+mount -t ext3 $LODEV $MNTPOINT || {
echo "Can't get a loopback device"
exit 1
}

I'll take a look...
-
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/