From: Stefan Schweizer <sschweizer@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: Bug in latest udev
Date: Sat, 05 Feb 2005 14:03:09 +0000 [thread overview]
Message-ID: <e796392205020506034686cbc6@mail.gmail.com> (raw)
In-Reply-To: <e7963922050205051668922de0@mail.gmail.com>
On Sat, 05 Feb 2005 14:29:46 +0100, Kay Sievers <kay.sievers@vrfy.org> wrote:
> This file is just an example and not every time up to date. The
> individual distribution rules files need to catch up now, so I wouldn't
> call this a "bug".
I am using gentoo .. so I think it should be up-to-date as the gentoo
rules are used as example.
>
> And you may use a "subsystem only"-rule for that:
> SUBSYSTEM="sound", GROUP="audio"
>
sounds reasonable, but works for me only when the subsystem rules is
before the other alsa rules.
> This will apply to all your audio devices if you don't specify any other
> GROUP with the individual rules.
>
> Ah, and please be more specific in the Subject of the mail.
sorry :(
I will try to check that before I send a mail next time
Regards,
Stefan
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
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:[~2005-02-05 14:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-05 13:16 Bug in latest udev Stefan Schweizer
2005-02-05 13:29 ` Kay Sievers
2005-02-05 14:03 ` Stefan Schweizer [this message]
2005-02-05 14:05 ` Marco d'Itri
2005-02-05 14:24 ` Kay Sievers
2005-02-05 14:40 ` Stefan Schweizer
2005-02-05 15:42 ` 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=e796392205020506034686cbc6@mail.gmail.com \
--to=sschweizer@gmail.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 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.