Linux Hotplug development
 help / color / mirror / Atom feed
From: Tom Gundersen <teg@jklm.no>
To: linux-hotplug@vger.kernel.org
Subject: Re: [PATCH] rules: set the correct group of the static
Date: Mon, 30 May 2011 12:02:08 +0000	[thread overview]
Message-ID: <BANLkTiks3jnFwt0o49r4xAgYCpuJLNtVrg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTi=GMO3+6dPk654AUeg49nQezj-u=w@mail.gmail.com>

On Mon, May 30, 2011 at 2:27 AM, Kay Sievers <kay.sievers@vrfy.org> wrote:
> On Mon, May 30, 2011 at 01:35, Tom Gundersen <teg@jklm.no> wrote:
>> On Fri, May 27, 2011 at 2:52 AM, Kay Sievers <kay.sievers@vrfy.org> wrote:
>>> On Tue, May 24, 2011 at 15:33, Tom Gundersen <teg@jklm.no> wrote:
>>>> When removing some of our custom rules from Arch we found that
>>>> a user in the audio group could no longer autoload the snd_seq
>>>> module. This fixes it, as proposed by Kay.
>>>
>>> Found out that we can use something simpler. Should work now.
>>
>> Close, but no cigar. Looks like the static nodes are not assigned
>> permissions 0660 even if a gid is set (the nodes have perms 0600).
>
> rules: static_node - use 0660 if group is given to get the cigar
> http://git.kernel.org/?p=linux/hotplug/udev.git;a=commitdiff;h¡12873b5bc9ebbae39c32f502bc6211f33546cc

Thanks!

-t
--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-05-30 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-24 13:33 [PATCH] rules: set the correct group of the static snd/{seq,timer} nodes Tom Gundersen
2011-05-27  0:52 ` [PATCH] rules: set the correct group of the static Kay Sievers
2011-05-29 23:35 ` Tom Gundersen
2011-05-30  0:27 ` Kay Sievers
2011-05-30 12:02 ` Tom Gundersen [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=BANLkTiks3jnFwt0o49r4xAgYCpuJLNtVrg@mail.gmail.com \
    --to=teg@jklm.no \
    --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