From: martin f krafft <madduck@madduck.net>
To: Neil Brown <neilb@suse.de>
Cc: Michael Tokarev <mjt@tls.msk.ru>,
linux-raid <linux-raid@vger.kernel.org>
Subject: Re: md[adm] device names
Date: Mon, 2 Nov 2009 09:24:24 +0100 [thread overview]
Message-ID: <20091102082424.GD7626@lapse.rw.madduck.net> (raw)
In-Reply-To: <19182.16585.929763.745870@notabene.brown>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
also sprach Neil Brown <neilb@suse.de> [2009.11.02.0315 +0100]:
> Numbers are meaningless. I would much rather have "/dev/md/home" or
> "/dev/md/backup" or whatever. But as I said, old names should still
> work.
… except sysfs exposes device names à la md1, right? I agree with
Michael that we should either have numbers or names, but not both.
http://bugs.debian.org/553896 came in today, which is just another
instance of confusion resulting from multiple choices.
I personally don't have a problem with numbers; they are as
meaningless or -full as partition numbers, and I used stuff like
/dev/sda5 on my systems for decades without problems. The trend
these days is dm/LVM, and that gives us decent names like
/dev/mapper/home, and I see the benefit in moving towards
/dev/md/home, but it needs to be done consistently, and either one
or the other.
--
martin | http://madduck.net/ | http://two.sentenc.es/
"if ever somethin' don't feel right to you, remember what pancho said
to the cisco kid... `let's win, before we are dancing at the end of
a rope, without music.'"
-- sailor
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/) --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-02 8:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-31 12:54 md[adm] device names Michael Tokarev
2009-11-02 2:15 ` Neil Brown
2009-11-02 8:24 ` martin f krafft [this message]
2009-11-02 11:21 ` Michael Tokarev
2009-11-02 11:14 ` Michael Tokarev
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=20091102082424.GD7626@lapse.rw.madduck.net \
--to=madduck@madduck.net \
--cc=linux-raid@vger.kernel.org \
--cc=mjt@tls.msk.ru \
--cc=neilb@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).