Bug#704160: kpartx says it will create /dev/loop0p1 but uses other names

[Stefan Monnier]

>> The problem that needs fixing is that "kpartx -l /dev/loop0" says
>> /dev/loop0p1 even though it ends not using this name.
> It doesn't report so on my box.
> rrs at zan:~$ sudo kpartx -l /dev/loop0
> loop0p1 : 0 4091904 /dev/loop0 2048

Ah, indeed, it doesn't say "/dev/".  OK, so maybe it's not a bug
strictly speaking, but still saying "loop0p1" here strongly suggests
there'd be a /dev/loop0p1.

>> I suggested to fix it by adding a /dev/loop0p1 symlink,
> Why? That part is anyways taken care by partx.

So maybe the problem is in partx.  I must say I don't know what's the
relationship between partx and kpartx.  All I know is that the "loop0p1"
mentioned in the output of "kpartx -l" (made a lot of sense and) created
for me the expectation to find a /dev/loop0p1.  Instead I had to look by
hand for some symlink in /dev/disk to figure out which name can be used.


        Stefan