On Tue, Feb 04, 2014 at 04:11:16PM -0500, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 2/4/2014 3:51 PM, ael wrote:
> > If just -o loop rather than -o loop=/dev/loop[1..n] is used, the
> > problem seems to vanish, at least with the latest kernels.
> >
> > Thus this becomes a bug in the mount man page? Hence reasssigning
> > back
>
> Ahh... strange.. so what is wrong exactly with the man page?
"
THE LOOP DEVICE
One further possible type is a mount via the loop device. For example,
the command
mount /tmp/disk.img /mnt -t vfat -o loop=/dev/loop
will set up the loop device /dev/loop3 to correspond to the file
/tmp/disk.img, and then mount this device on /mnt.
"
Remove explict device /dev/loop.. from the example. Slightly modify
following text.
I haven't searched the kernel archives (if that is where to look) to see
when this mandatory automatic handling of the loop devices was introduced.
Presumably the motivation was to reduce the burdon on the user of
keeping track. Perhaps.
ael
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
