From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Takashi Sakamoto <o-takashi@sakamocchi.jp>
Cc: tiwai@suse.de, alsa-devel@alsa-project.org,
Jonathan Woithe <jwoithe@just42.net>,
clemens@ladisch.de, ffado-devel@lists.sf.net
Subject: Re: [PATCH 0/5] ALSA: firewire-tascam: add MIDI functionality
Date: Tue, 20 Oct 2015 09:39:07 +0200 [thread overview]
Message-ID: <20151020093907.033831d3@kant> (raw)
In-Reply-To: <56258FE6.9000304@sakamocchi.jp>
On Oct 20 Takashi Sakamoto wrote:
> When using polkit correctly, I guess users doesn't need to join in
> 'audio' group, so as PulseAudio achieved with polkit.
With regard to access to /dev/fw* files, this is true with the existing
FFADO rules too. 60-ffado.rules sets ENV{ID_FFADO}="1", and
consolekit's 70-udev-acl.rules recognizes ID_FFADO and runs udev-acl on
the device.
(I.e. the current "console" owner is granted access to the character
device file via access control list (ACL), which is a mechanism in
parallel to Unix permission flags.)
The console owner policy and ACL mechanism are not a complete replacement
for the group mechanism though:
- There may be headless systems and other occasions at which the audio
user is not console owner.
- Processes involved in capture or playback, i.e. applications beyond
mixers, may require realtime scheduling class privilege and memlocking
privilege, which are traditionally configured for Unix groups and
users (typically for a group). Not sure whether a mechanism exists
which can implement a console owner policy for realtime and memlock
privileges.
--
Stefan Richter
-=====-===== =-=- =-=--
http://arcgraph.de/sr/
next prev parent reply other threads:[~2015-10-20 7:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 10:10 [PATCH 0/5] ALSA: firewire-tascam: add MIDI functionality Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 1/5] ALSA: firewire-tascam: add support for incoming MIDI messages by asynchronous transaction Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 2/5] ALSA: firewire-tascam: add support for outgoing " Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 3/5] ALSA: firewire-tascam: add support for MIDI functionality Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 4/5] ALSA: firewire-tascam: Turn on/off FireWire LED Takashi Sakamoto
2015-10-12 10:10 ` [PATCH 5/5] ALSA: firewire-tascam: change device probing processing Takashi Sakamoto
2015-10-12 12:42 ` Stefan Richter
2015-10-13 14:12 ` Takashi Sakamoto
2015-10-12 12:21 ` [PATCH 0/5] ALSA: firewire-tascam: add MIDI functionality Takashi Iwai
2015-10-12 12:48 ` Stefan Richter
2015-10-12 22:20 ` Jonathan Woithe
2015-10-13 9:36 ` Takashi Sakamoto
2015-10-13 10:02 ` Jonathan Woithe
2015-10-13 22:20 ` Stefan Richter
2015-10-19 14:21 ` Takashi Sakamoto
2015-10-19 23:45 ` Jonathan Woithe
2015-10-13 14:15 ` Stefan Richter
2015-10-19 14:13 ` Takashi Sakamoto
2015-10-19 23:36 ` Jonathan Woithe
2015-10-20 0:50 ` Takashi Sakamoto
2015-10-20 2:09 ` Takashi Sakamoto
2015-10-20 2:57 ` Jonathan Woithe
2015-10-20 2:52 ` Jonathan Woithe
2015-10-20 7:39 ` Stefan Richter [this message]
2015-10-26 15:18 ` Takashi Sakamoto
2015-10-27 1:38 ` Stefan Richter
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=20151020093907.033831d3@kant \
--to=stefanr@s5r6.in-berlin.de \
--cc=alsa-devel@alsa-project.org \
--cc=clemens@ladisch.de \
--cc=ffado-devel@lists.sf.net \
--cc=jwoithe@just42.net \
--cc=o-takashi@sakamocchi.jp \
--cc=tiwai@suse.de \
/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