From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [PATCH] improve atomicity of device creation
Date: Tue, 11 Dec 2007 17:53:59 +0000 [thread overview]
Message-ID: <20071211175359.GV22311@agk.fab.redhat.com> (raw)
In-Reply-To: <1197394828.25082.39.camel@quest>
On Tue, Dec 11, 2007 at 05:40:28PM +0000, Scott James Remnant wrote:
> 1) udev creates device node and sets permissions
> 2) devmapper no-ops since it already exists
...because libdevmapper has no notion that something other than itself
could have created it. That's a bug, but provided the proper udev
integration isn't much longer in coming, I shan't bother to fix it.
Alasdair
--
agk@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: linux-hotplug-devel@lists.sourceforge.net
Subject: Re: [dm-devel] [PATCH] improve atomicity of device creation
Date: Tue, 11 Dec 2007 17:53:59 +0000 [thread overview]
Message-ID: <20071211175359.GV22311@agk.fab.redhat.com> (raw)
In-Reply-To: <1197394828.25082.39.camel@quest>
On Tue, Dec 11, 2007 at 05:40:28PM +0000, Scott James Remnant wrote:
> 1) udev creates device node and sets permissions
> 2) devmapper no-ops since it already exists
...because libdevmapper has no notion that something other than itself
could have created it. That's a bug, but provided the proper udev
integration isn't much longer in coming, I shan't bother to fix it.
Alasdair
--
agk@redhat.com
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://sourceforge.net/services/buy/index.php
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next prev parent reply other threads:[~2007-12-11 17:53 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-11 16:08 [PATCH] improve atomicity of device creation Scott James Remnant
2007-12-11 16:25 ` Alasdair G Kergon
2007-12-11 16:25 ` [dm-devel] " Alasdair G Kergon
2007-12-11 16:42 ` Scott James Remnant
2007-12-11 17:03 ` Alasdair G Kergon
2007-12-11 17:03 ` [dm-devel] " Alasdair G Kergon
2007-12-11 17:18 ` Scott James Remnant
2007-12-11 17:51 ` Kay Sievers
2007-12-11 17:51 ` Kay Sievers
2007-12-11 18:08 ` Alasdair G Kergon
2007-12-11 18:08 ` [dm-devel] " Alasdair G Kergon
2007-12-11 18:25 ` Kay Sievers
2007-12-11 18:25 ` Kay Sievers
2007-12-11 19:13 ` Alasdair G Kergon
2007-12-11 19:13 ` [dm-devel] " Alasdair G Kergon
2007-12-11 19:43 ` Alasdair G Kergon
2007-12-11 19:43 ` [dm-devel] " Alasdair G Kergon
2007-12-11 17:35 ` Kay Sievers
2007-12-11 17:35 ` Kay Sievers
2007-12-11 17:40 ` Scott James Remnant
2007-12-11 17:53 ` Alasdair G Kergon [this message]
2007-12-11 17:53 ` Alasdair G Kergon
2007-12-11 19:09 ` Scott James Remnant
2007-12-11 18:03 ` Kay Sievers
2007-12-11 18:03 ` [dm-devel] " Kay Sievers
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=20071211175359.GV22311@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-hotplug-devel@lists.sourceforge.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.