All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Orr <martin@martinorr.name>
To: Daniel J Walsh <dwalsh@redhat.com>
Cc: selinux@tycho.nsa.gov
Subject: Re: alsactl policy
Date: Tue, 18 Sep 2007 16:03:47 +0100	[thread overview]
Message-ID: <46EFE8D3.6060309@martinorr.name> (raw)
In-Reply-To: <46EE8D70.2080804@redhat.com>

On 17/09/07 15:21, Daniel J Walsh wrote:
>>  type alsa_etc_rw_t;
>>  files_type(alsa_etc_rw_t)
> 
>> +type alsa_var_lib_t;
>> +files_type(alsa_var_lib_t)
>> +
>> +type alsa_state_t;
>> +files_type(alsa_state_t)
>> +
> We already have alsa_etc_rw_t for this.  So we could either change
> alsa_etc_rw_t to this context and typealias it or leave it as rw_t.
> Or alternatively just allow alsa to write to alsa_var_lib_t,

OK, I thought that alsa_etc_rw_t was for something else.  Since I don't have
any /etc/alsa/pcm directory, I didn't know what it was for.

> Fedora stores asound.state under etc.  Although it probably would be
> better in var/lib
> 
> I have opened a bugzilla for Fedora to write their asound.state file there.
> 
> https://bugzilla.redhat.com/show_bug.cgi?id=293301

There is a bug in the upstream BTS to change this as well:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=3128

Thanks for your reviewing time,

-- 
Martin Orr

--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.

  reply	other threads:[~2007-09-18 15:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 20:13 alsactl policy Martin Orr
2007-09-17 14:21 ` Daniel J Walsh
2007-09-18 15:03   ` Martin Orr [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-07-23 19:49 Martin Orr
2007-07-27 13:11 ` Christopher J. PeBenito

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=46EFE8D3.6060309@martinorr.name \
    --to=martin@martinorr.name \
    --cc=dwalsh@redhat.com \
    --cc=selinux@tycho.nsa.gov \
    /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.