From mboxrd@z Thu Jan 1 00:00:00 1970 From: Steven Whitehouse Date: Tue, 13 Oct 2009 16:43:21 +0100 Subject: [Cluster-devel] Re: [PATCH 1/2] dlm: Send lockspace name with uevents In-Reply-To: <20091013152330.GC27036@redhat.com> References: <1255445776-3112-1-git-send-email-swhiteho@redhat.com> <1255445776-3112-2-git-send-email-swhiteho@redhat.com> <20091013145337.GA27036@redhat.com> <20091013152330.GC27036@redhat.com> Message-ID: <1255448601.6052.571.camel@localhost.localdomain> List-Id: To: cluster-devel.redhat.com MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi, On Tue, 2009-10-13 at 10:23 -0500, David Teigland wrote: > On Tue, Oct 13, 2009 at 09:53:37AM -0500, David Teigland wrote: > > On Tue, Oct 13, 2009 at 03:56:15PM +0100, Steven Whitehouse wrote: > > > Although it is possible to get this information from the path, > > > its much easier to provide the lockspace as a seperate env > > > variable. > > > > I don't mind this, but it's more or less a style issue. I'm going to try to > > keep upstream and rhel as close as possible for a while to minimize the > > backporting work in the early stages when it's usually heaviest. That means > > putting off things like this until later. > > Also, libudev may make this less relevant, > http://www.kernel.org/pub/linux/utils/kernel/hotplug/libudev/ > > Dave > I don't think so. The udev code is written on the basis that it looks at the individual env variables, so I think its likely to be more useful in the future, Steve.