From: Ryan Thomas <ryan@coraid.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] Standard rules for AoE devices.
Date: Tue, 09 Dec 2008 11:23:43 +0000 [thread overview]
Message-ID: <493E553F.3030902@coraid.com> (raw)
In-Reply-To: <493DB75B.5090309@coraid.com>
Kay Sievers wrote:
> On Tue, Dec 9, 2008 at 04:07, Ryan Thomas <ryan@coraid.com> wrote:
>> Kay Sievers wrote:
>>> On Tue, Dec 9, 2008 at 01:49, Marco d'Itri <md@linux.it> wrote:
>>>> On Dec 09, Ryan Thomas <ryan@coraid.com> wrote:
>>>>
>>>>> In the interest of standardizing udev rules, please consider the
>>>>> following patch that adds udev rules for the ATA over Ethernet character
>>>>> and block devices. The aoe module has been a long-time member of the
>>>>> kernel and needs inclusion in the standard udev rules.
>>>> Debian so far has used these rules which are more generic and much
>>>> simpler. Are they incorrect in some way?
>>>>
>>>> # AOE character devices
>>>> SUBSYSTEM="aoe", NAME="etherd/%k"
>>>>
>>>> SUBSYSTEM="aoe", MODE="0220", GROUP="disk"
>>>> SUBSYSTEM="aoe", KERNEL="err", MODE="0440", GROUP="disk"
>>> That looks fine.
>>>
>>> I wonder why we have this comment:
>>> +# aoe block devices
>>> +SUBSYSTEM="aoe", KERNEL="etherd*", NAME="%k", GROUP="disk"
>>>
>>> They can not be block devices if they have SUBSYSTEM="aoe". Do the
>>> etherd* devices belong into the subdir or not?
>>>
>>> We have:
>>> SUBSYSTEM="aoe", NAME="etherd/%k", GROUP="disk"
>>> in the current default rules.
>>>
>>> I guess doing:
>>> # ATA over Ethernet
>>> SUBSYSTEM="aoe", NAME="etherd/%k", GROUP="disk", MODE="0220"
>>> SUBSYSTEM="aoe", KERNEL="err", MODE="0440"
>>> would be all we need.
>
>> My previous patch should be backed out as you are right that it's not
>> needed.
>>
>> A patch to the default rules to correct the mode on the etherd/err character
>> device is all that is needed.
>
> Applied. Please check:
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h/c635fb67dbd509f4ee532c8bf0d3885cc71989
>
> The block device are never moved to the subdir, they all just stay in
> /dev, right?
>
The block device does go in the subdir. The kernel name for the block
device is "etherd!eX.Y" which means that the subdir is automatically
taken care of.
Ryan
next prev parent reply other threads:[~2008-12-09 11:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-09 0:10 [PATCH] Standard rules for AoE devices Ryan Thomas
2008-12-09 0:36 ` Kay Sievers
2008-12-09 0:49 ` Marco d'Itri
2008-12-09 1:01 ` Kay Sievers
2008-12-09 3:07 ` Ryan Thomas
2008-12-09 3:23 ` Kay Sievers
2008-12-09 11:23 ` Ryan Thomas [this message]
2008-12-09 16:17 ` 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=493E553F.3030902@coraid.com \
--to=ryan@coraid.com \
--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).