From: Phillip Susi <psusi-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
To: device-mapper development
<dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Curtis Gedak <gedakc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org,
Debian LVM Team
<pkg-lvm-maintainers-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org>,
parted-deve
Subject: What is the deal with the partition separator?
Date: Tue, 15 Feb 2011 22:21:34 -0500 [thread overview]
Message-ID: <4D5B42BE.3050301@cfl.rr.com> (raw)
It used to be that partitions device names just had a digit added on to
the base disk device name. It seems that this became problematic at
some point with device mapper and oddly named disks, and there have been
several responses to it:
1) dmraid and (lib)parted now always add a 'p' between the base name
and the partition number
2) kpartx from multipath-tools adds the 'p' only if the base name ends
in a digit
3) Debian and Ubuntu's udev and init scripts tell kpartx to use 'part'
instead of just 'p'.
4) gparted now explicitly tells dmraid to not use any character so that
it behaves like older versions and is therefore compatible with the
kpartx method that gparted has adopted, at least when the base name does
not end with a digit.
Each of these components needs to agree on what the correct name is or
chaos ensues. I would like to discuss the merits of each and try to
decide on a standard.
Having thought about it for a moment, it seems to me that deciding on
always adding the 'p' is the way to go, since the 'art' just makes
things longer for no good reason, and if you only sometimes add the 'p'
then you can't tell if a device name that ends in a digit that does not
follow a 'p' is a whole disk, or a partition.
next reply other threads:[~2011-02-16 3:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 3:21 Phillip Susi [this message]
2011-02-16 7:38 ` What is the deal with the partition separator? Hannes Reinecke
[not found] ` <4D5B7ED9.20304-l3A5Bk7waGM@public.gmane.org>
2011-02-16 17:19 ` [dm-devel] " Curtis Gedak
[not found] ` <4D5C073F.3020502-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-02-16 19:33 ` Phillip Susi
[not found] ` <4D5C268B.6070507-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-16 20:18 ` Curtis Gedak
2011-02-16 19:37 ` Phillip Susi
[not found] ` <4D5C2793.1020601-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-17 7:29 ` Hannes Reinecke
[not found] ` <4D5CCE75.5090202-l3A5Bk7waGM@public.gmane.org>
2011-02-17 14:57 ` Phillip Susi
[not found] ` <4D5D375F.9070106-3tLf1voIkJTQT0dZR+AlfA@public.gmane.org>
2011-02-17 15:13 ` Hannes Reinecke
[not found] ` <4D5D3B34.4000005-l3A5Bk7waGM@public.gmane.org>
2011-02-17 15:13 ` Phillip Susi
2011-02-17 16:53 ` Alasdair G Kergon
2011-02-17 16:58 ` Alasdair G Kergon
[not found] ` <20110217165332.GE28729-FDJ95KluN3Z0klwcnFlA1dvLeJWuRmrY@public.gmane.org>
2011-02-20 5:04 ` [dm-devel] " Phillip Susi
2011-02-17 16:54 ` Curtis Gedak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D5B42BE.3050301@cfl.rr.com \
--to=psusi-3tlf1voikjtqt0dzr+alfa@public.gmane.org \
--cc=dm-devel-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=gedakc-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=pkg-lvm-maintainers-XbBxUvOt3X2LieD7tvxI8l/i77bcL1HB@public.gmane.org \
--cc=serge.hallyn-GeWIH/nMZzLQT0dZR+AlfA@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox