Linux Hotplug development
 help / color / mirror / Atom feed
From: Neil Brown <neilb@suse.de>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] 64-md-raid.rules fixes v2
Date: Tue, 14 Apr 2009 01:33:34 +0000	[thread overview]
Message-ID: <18915.59374.663499.384069@notabene.brown> (raw)
In-Reply-To: <7fe3a91a4b0971f1be490bdaccf37479047ac0a0.1237151296.git.soltys@ziu.info>

On Sunday March 15, soltys@ziu.info wrote:
(sorry for taking nearly a month to reply...)

> 1) introduced in commit b822542608326092e177fd1707ca7fb53b2846c4
> 
> md/array_state in case of partition doesn't exists, so all uevents
> for partitions didn't execute any SYMLINK rules

Thanks.  I've applies this (with a slightly more verbose comment) in
the version of the rules file to be released with mdadm-3.0

> 
> 2) add compat rule, so both MD_DEVNAME (mdadm 3.0) and MD_NAME
>    (mdadm 2.9.x) can be used

I probably don't agree with this.
mdadm 2.x created dev files in /dev directly.  So it does not expect
udev to do anything, particularly with names.

mdadm 3.x by contrast doesn't create anything in /dev (if udev seems
to be installed) so the rules file must create everything.

So I think that 'compat' rule is wrong.  I'm happy to listen to more
details arguments though.

http://neil.brown.name/git?p=mdadm;a=commitdiff;hú5090285af9401f950aa5c1a3a82708c69c4906

Thanks,
NeilBrown

      parent reply	other threads:[~2009-04-14  1:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 21:21 [PATCH] 64-md-raid.rules fixes v2 Michal Soltys
2009-03-16  0:51 ` Kay Sievers
2009-04-14  1:33 ` Neil Brown [this message]

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=18915.59374.663499.384069@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-hotplug@vger.kernel.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