bug#15348: [PATCH 11/19] libparted: don't canonicalize /dev/md/ paths (#872361)

[Phillip Susi]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Now that I look more closely at the named md situation, it seems it
doesn't quite face the same issue as dm.  With dm, you must not
canonicalize the name when generating the partition device name, since
there is no /dev/dm-0p1 ( so we would fail to open the partition dev
node ).  With md, there is a /dev/md0p1, in addition to the
/dev/md/foo1 symlink pointing to it, so either way should work.

I guess now the purpose of this patch is purely for the user
experience?  If a user runs parted on /dev/md/foo then they expect
parted to state that is what it is working on instead of /dev/md0?  Is
the reverse true, or should parted always favor the name even if run
on the number?  What if it is invoked on /dev/disk/by-id?

On 9/29/2013 10:21 PM, Phillip Susi wrote:
> I just posted a patch refactoring the existing dm fix in the way
> that I described.  I'm not sure what ioctls are needed to retrieve
> the correct name for md devices, so I haven't tried to do that part
> yet. If you know how to do that, you should be able to see the
> direction I went with the dm devices and follow suit with md.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (MingW32)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQEcBAEBAgAGBQJSSdExAAoJEJrBOlT6nu75mMAH/iXGT9r6SftVnyTgTHmi1cV2
iY+WTy/LlzPDoXz/b3NhLU/+v7HG/fYSiee3itG1Qim/YT3ytc/1xBc9EaMqhXCL
myh6bOwheMovD+TuFRySbTi7KamWFy7f9pQafmHsYN6Hiy9ueDzTL3do0SrVshU4
VmMa8hcwFAvYdmrSIwvbSLY/UUmj/7GvJ1QeE9QgVs7Flu4Zi4tmSXpEMni1Xy8f
Sm+A3bUzOhEQegiYlwyFiBqyzNQfIy6Bz2Fomnw4w7A3PICjiH9pzUP7SM3EG20R
CbPKMdYmNWaX2d9XNHQIPGC4w3xOl1D9tuvIn57lWZJ4cXDzX6T37JDVZZsvfCw=
=qM1I
-----END PGP SIGNATURE-----