Hi,
On Sun, May 03, 2020 at 11:23:45PM +0200, Prof. Dipl.-Ing. Klaus Knopper wrote:
> Hello Chris,
>
> /me of little patience gave up (maybe too early), and continue to use
[...]
FWIW my suggestion for you to contact upstream was not simply a way to
push this away from being my problem, but I
Hello Chris,
/me of little patience gave up (maybe too early), and continue to use
busybox losetup ... /dev/cloop*
instead of linux-utils busybox.
I still think that losetup should not check the major device numbers of
loop-devices at all and just do what we expect.
On the other hand, most
Hello Klaus,
* Prof. Dipl.-Ing. Klaus Knopper [200503 19:20]:
> Hello Andreas,
>
[..]
> > Could you please raise your issue on the upstream mailing list
> > on vger.kernel.org directly?
>
> I thought that forwarding a problem to the programs authors is what the
> "upstream" marker in reportbug
Hello Andreas,
On Mon, Jun 06, 2016 at 12:26:11PM +0200, Andreas Henriksson wrote:
> Hello Klaus Knopper.
>
> Thanks for your bug report.
>
> On Sat, Jun 04, 2016 at 05:35:43PM +0200, Klaus Knopper wrote:
> [...]
> > Losetup was able to setup compressed loopback (cloop) devices, which
> > have
Hello Klaus Knopper.
Thanks for your bug report.
On Sat, Jun 04, 2016 at 05:35:43PM +0200, Klaus Knopper wrote:
[...]
> Losetup was able to setup compressed loopback (cloop) devices, which
> have a similar ioctl API, until recently the code in sys-utils/losetup.c
> and lib/loopdev.c was changed
Package: util-linux
Version: 2.28-5
Severity: normal
Tags: upstream
Losetup was able to setup compressed loopback (cloop) devices, which
have a similar ioctl API, until recently the code in sys-utils/losetup.c
and lib/loopdev.c was changed to only accept devices with loopbacks
major device id.
6 matches
Mail list logo
