linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kay Sievers <kay.sievers@vrfy.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Chris Mason <chris.mason@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] Btrfs updates for 2.6.29-rc
Date: Sun, 8 Feb 2009 11:16:53 +0100	[thread overview]
Message-ID: <ac3eb2510902080216k55d525dam68aefeb0b45257ab@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0902070837350.3048@localhost.localdomain>

On Sat, Feb 7, 2009 at 17:37, Linus Torvalds
<torvalds@linux-foundation.org> wrote:
> On Fri, 6 Feb 2009, Chris Mason wrote:
>>
>> Crud, the confusion would be me.  I missed the cleanups and bug fixes
>> between 2.6.29-rc1 and rc3.   The correct diffstat and short log are
>> below, and the only non-btrfs change is to the MAINTAINERS file.
>
> Ok.
>
> I notice that it now asks about ACL's, and says
>
>        If you don't know what Access Control Lists are, say N
>
> which is all fine, but last I saw some (most?) distributions use POSIX
> ACL's for things like desktop access permissions to /dev/audio etc.
>
> I don't particularly have to like it, but it does mean that if you don't
> do POSIX ACL's, and have btrfs as your root filesystem, you'll quite
> likely not get sound when logging in.
>
> I dunno. I haven't actually yet tried to convert my laptop, so I just
> reacted to this thanks to the new question..

Systems using ACLs to grant device permissions to logged-in users have
/dev on a tmpfs mount, where the content will not survive a reboot.
This should not be a problem for btrfs, or the rootfs fs type, but
TMPFS_POSIX_ACL. Maybe we want to have a comment there?

Thanks,
Kay

  parent reply	other threads:[~2009-02-08 10:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-06 16:22 [GIT PULL] Btrfs updates for 2.6.29-rc Chris Mason
2009-02-06 16:53 ` Linus Torvalds
2009-02-06 21:51   ` Chris Mason
2009-02-06 21:59     ` Linus Torvalds
2009-02-07  0:10       ` Chris Mason
2009-02-07 16:37         ` Linus Torvalds
2009-02-07 23:50           ` Chris Mason
2009-02-08 10:16           ` Kay Sievers [this message]
2009-02-13 20:25 Chris Mason
2009-02-26 15:09 Chris Mason
2009-02-26 15:11 Chris Mason

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=ac3eb2510902080216k55d525dam68aefeb0b45257ab@mail.gmail.com \
    --to=kay.sievers@vrfy.org \
    --cc=chris.mason@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).