From: Kay Sievers <kay.sievers@vrfy.org>
To: linux-hotplug@vger.kernel.org
Subject: Re: add rules for new aoe character devices
Date: Mon, 03 Dec 2007 18:42:58 +0000 [thread overview]
Message-ID: <1196707378.6044.17.camel@lov.site> (raw)
In-Reply-To: <20071129171100.GF11161@coraid.com>
On Mon, 2007-12-03 at 13:38 -0500, Ed L. Cashin wrote:
> On Mon, Dec 03, 2007 at 07:15:03PM +0100, Kay Sievers wrote:
> > On Nov 29, 2007 6:11 PM, Ed L. Cashin <ecashin@coraid.com> wrote:
> > > The patch below adds support for new aoe driver character "flush" and
> > > "revalidate" devices to the existing aoe rules in udev-117.
> > >
> > > The current aoe driver version in the Linux kernel does not include
> > > the "flush" feature, but I have already submitted patches to the LKML
> > > adding that support and am now working on updating those patches for
> > > resubmission. Those using the aoe driver on the Coraid website
> > > already have the "flush" feature.
> >
> > The distro rules are just a copy from the distro packages and changes made
> > here will not get into the packages. We can add the rules only to the "default"
> > rules.
>
> Ah. Thank you.
>
> > Does this rule work for you? It should move all nodes into a subdir:
> > SUBSYSTEM="aoe", NAME="etherd/%k"
>
> Yes, that's good for the block devices. In the past it seems that
> rule doesn't guarantee the creation of the character device nodes,
> though, and that is why there is a separate rule for each character
> node in the patch I sent. I haven't checked yet whether the latest
> udev and kernel still behave the same way.
Block devices always have SUBSYSTEM="block", this will only handle the
char devices. You want the block devices to be in a subdir?
Kay
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
_______________________________________________
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-03 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 17:11 add rules for new aoe character devices Ed L. Cashin
2007-12-03 18:15 ` Kay Sievers
2007-12-03 18:38 ` Ed L. Cashin
2007-12-03 18:42 ` Kay Sievers [this message]
2007-12-03 18:52 ` Matthias Schwarzott
2007-12-10 15:34 ` Ed L. Cashin
2007-12-10 19:21 ` Kay Sievers
2007-12-10 20:07 ` Ed L. Cashin
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=1196707378.6044.17.camel@lov.site \
--to=kay.sievers@vrfy.org \
--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;
as well as URLs for NNTP newsgroup(s).