[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Fwd: unable to mount loop device
From:       Harald Becker <ralda () gmx ! de>
Date:       2011-09-18 18:16:42
Message-ID: 4E76358A.8020507 () gmx ! de
[Download RAW message or body]

 Hi!

On 18.09.2011 19:42, mehdi karamnejad wrote:
> well as you told omitting the GNUish extension solved the problem :
> $ mount -t ext2 -o loop /image_holder/boot/imgfile.img
> /path/to/mount/point
> so can't we specify the loop device we want to use using this syntax?

Correct, it auto selects the first free loop device. For normal usage
that is what you want to do and you need not to know which loop device
is actually used for mounting an image file.

Where did you get this "-o loop=LOOPDEVICE" from? Have you used that on
the same kernel version as your failing system now? The normal behavior
of mount is to pass those options to the kernel where they are handled.
So could it be a difference in kernel versions that blocks the (possibly
new/extended) loop mounting syntax? Have you any references for this
extended syntax?

--
Harald

>
> ---------- Forwarded message ----------
> From: *Harald Becker* <ralda@gmx.de <mailto:ralda@gmx.de>>
> Date: Sat, Sep 17, 2011 at 4:43 AM
> Subject: Re: unable to mount loop device
> To: mehdi karamnejad <mehdi.karamnejad@gmail.com
> <mailto:mehdi.karamnejad@gmail.com>>
>
>
>
> >
> >
> >     ./busybox mount -t ext2 -o "loop=/dev/loop0" /boot/initrdimg.img
> >     /mnt/local/
> >
>
> Wow, were got you that command from? Had some look in mount docu and
> can't find that "-o loop=LOOPDEVICE" syntax. I consider only the usage
> of "-o loop" to be correct. May be it is a GNUish extension? So please
> try without appending a loop device name.
>
> --
> Harald
>
>
>
> -- 
> :-----:
> > Mehdi Karamnejad
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]