From: Jason Lunz <lunz@falooley.org>
To: Molle Bestefich <molle.bestefich@gmail.com>
Cc: linas <linas@austin.ibm.com>,
neilb@suse.de, linux-hotplug-devel@lists.sourceforge.net,
linux-raid@vger.kernel.org
Subject: Re: 2.6.15: mdrun, udev -- who creates nodes?
Date: Tue, 31 Jan 2006 15:52:03 -0500 [thread overview]
Message-ID: <20060131205202.GD27268@knob.reflex> (raw)
In-Reply-To: <62b0912f0601311219x78cbb29dof3768c1449bc8349@mail.gmail.com>
On Tue, Jan 31, 2006 at 09:19:16PM +0100, Molle Bestefich wrote:
> I *think* that "the raid developers" may be, for once, choosing words
> not-so-wisely when talking about "deprecating autoassembly".
You're right, I should be careful not to imply anything Neil didn't
actually say. What he said was:
> From: Neil Brown <neilb <at> suse.de>
...
> And if other partition styles wanted to add support for raid auto
> detect, tell them "no". It is perfectly possible and even preferable
> to live without autodetect. We should support legacy usage (those
> above) but should discourage any new usage.
which is a far cry from officially deprecating anything. My point was
that the outlined solution for having udev create /dev/md* nodes could
not work on all platforms because it required raid autodetect, and it
looks unlikely that raid autodetect will be universally supported.
Jason
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
next prev parent reply other threads:[~2006-01-31 20:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <43DCA9CA.5020505@bl.com>
[not found] ` <20060129123532.GA6158@wonderland.linux.it>
[not found] ` <43DCD614.20705@pobox.com>
[not found] ` <20060130204231.GP19465@austin.ibm.com>
[not found] ` <20060130204743.GA13902@wonderland.linux.it>
[not found] ` <dro3ue$ntb$1@sea.gmane.org>
2006-01-31 19:26 ` 2.6.15: mdrun, udev -- who creates nodes? linas
2006-01-31 20:19 ` Molle Bestefich
2006-01-31 20:52 ` Jason Lunz [this message]
2006-01-31 21:13 ` linas
2006-01-31 21:58 ` Molle Bestefich
2006-02-01 9:27 ` Andy Smith
2006-02-01 19:44 ` Luca Berra
2006-02-01 22:14 ` Andy Smith
2006-02-02 1:27 ` Neil Brown
2006-01-31 21:44 ` Luca Berra
2006-02-10 22:46 ` Bill Davidsen
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=20060131205202.GD27268@knob.reflex \
--to=lunz@falooley.org \
--cc=linas@austin.ibm.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
--cc=linux-raid@vger.kernel.org \
--cc=molle.bestefich@gmail.com \
--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).