mkinitrd w/ 2.4.18

mkinitrd w/ 2.4.18

[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
-- 
o--------------------oo0oo-------------------------o
| matthew walburn      |  mit dept. of mathematics |
| network staff asst.  0  building 2 - room 236    |
| matt@math.mit.edu    0  77 massachusetts avenue  |
o--------------------oo0oo-------------------------o

Re: mkinitrd w/ 2.4.18

[Tigran Aivazian]

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

Re: mkinitrd w/ 2.4.18

[Matthew Walburn]

Thanks everyone for the advice, it's now working. Embarringly enough it
was a simple case of insmoding loop.o.

thanks again.

matt

Re: mkinitrd w/ 2.4.18

[Pete Zaitcev]

>[...]
> 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?

I would appreciate if you hit enter about every 70 keystrokes.

Also, describing a symptom rather than vague "i'm having problems"
may help.

-- Pete

Re: mkinitrd w/ 2.4.18

[Matthew Walburn]

> I would appreciate if you hit enter about every 70 keystrokes.

Sorry about that didnt realize it wasn't wrapping.

> Also, describing a symptom rather than vague "i'm having problems"
> may help.

Specifically, i get the error message:
"all of your loopback devices are in use"

I have the follow kernel options enabled, using Redhat's kernel
config as a guide:

CONFIG_BLK_DEV_LOOP=m
CONFIG_BLK_DEV_NBD=m
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_SIZE=4096
CONFIG_BLK_DEV_INITRD=y

Thanks for the help.

-Matt

Re: mkinitrd w/ 2.4.18

[Pete Zaitcev]

> Date: Thu, 28 Mar 2002 22:01:30 -0500
> From: Matthew Walburn <matt@math.mit.edu>

> Specifically, i get the error message:
> "all of your loopback devices are in use"

Unfortunately, it only says that setting up the loopback failed.
You are not necesserily running out of free loopback devices.
Does mounting anything on the loopback work?
mount -t iso9660 -o loop /your/favourite/something.iso /mnt/cdrom

I'll drop cc on the next round.

-- Pete

Re: mkinitrd w/ 2.4.18

[arjan]

In article <20020328220130.A2627@math.mit.edu> you wrote:
>> I would appreciate if you hit enter about every 70 keystrokes.
> 
> Sorry about that didnt realize it wasn't wrapping.
> 
>> Also, describing a symptom rather than vague "i'm having problems"
>> may help.
> 
> Specifically, i get the error message:
> "all of your loopback devices are in use"

are you using tmpfs on /tmp ?

Re: mkinitrd w/ 2.4.18

[NyQuist]

[-- Attachment #1: Type: text/plain, Size: 1337 bytes --]

On Fri, 2002-03-29 at 03:01, Matthew Walburn wrote:
> > I would appreciate if you hit enter about every 70 keystrokes.
> 
> Sorry about that didnt realize it wasn't wrapping.
> 
> > Also, describing a symptom rather than vague "i'm having problems"
> > may help.
> 
> Specifically, i get the error message:
> "all of your loopback devices are in use"
> 
you need to have loop.o insmodd'ed (insmod loop) to mkinitrd. If you're
using rh's stock kernel, I *believe* this is included as a module. If
you're running mkinitrd from your rebuilt kernel, check
/lib/modules/2.4.18/kernel/drivers/net for loop.o (methinks).
hth

> I have the follow kernel options enabled, using Redhat's kernel
> config as a guide:
> 
> CONFIG_BLK_DEV_LOOP=m
> CONFIG_BLK_DEV_NBD=m
> CONFIG_BLK_DEV_RAM=y
> CONFIG_BLK_DEV_RAM_SIZE=4096
> CONFIG_BLK_DEV_INITRD=y
> 
> Thanks for the help.
> 
> -Matt
> -
> 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/
-- 
NyQuist | Matthew Hall -- NyQuist at ntlworld dot com --
http://NyQuist.port5.com
Sig: Any sufficiently advanced technology is indistinguishable from a
rigged demo.


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 232 bytes --]