From: "Walter Dnes" <waltdnes@waltdnes.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] File-system mounting questions
Date: Sat, 19 Sep 2015 15:06:51 -0400 [thread overview]
Message-ID: <20150919190651.GA20920@waltdnes.org> (raw)
In-Reply-To: <BLU436-SMTP171981D8F5157F66F5897AD8D590@phx.gbl>
On Fri, Sep 18, 2015 at 05:36:35PM -0400, Fernando Rodriguez wrote
> On Friday, September 18, 2015 5:14:15 PM Walter Dnes wrote:
> > * Could not set caps on '/usr/bin/readcd' due to missing filesystem support:
> > * * enable XATTR support for 'ext2/ext3' in your kernel (if configurable)
> > * * mount the fs with the user_xattr option (if not the default)
> > * * enable the relevant FS_SECURITY option (if configurable)
> > >>> Auto-cleaning packages...
> >
> > That might explain my problems. So I modified my kernel as below...
> >
> > <*> Second extended fs support
> > [*] Ext2 extended attributes
> > [ ] Ext2 POSIX Access Control Lists
> > [ ] Ext2 Security Labels
> > <*> Ext3 journalling file system support
> > [*] Default to 'data=ordered' in ext3
> > [*] Ext3 extended attributes
> > [ ] Ext3 POSIX Access Control Lists
> > [ ] Ext3 Security Labels
>
> You'll also need this ^
[...deletia...]
> Just add the user_xattr unde <opts> column. Like:
>
> UUID=34868f06-d56b-4539-a649-33ec96b50d74 / ext3 noatime,user_xattr 0 1
Thanks. It has greatly improved things. I added...
[*] Ext2 Security Labels
[*] Ext3 Security Labels
Thank you very much; it works. The number of warnings as regular user
is greatly reduced. It no longer complains about insufficient device
permissions or the possibility of jitter. There are now only 2 lines of
meddages. They're about "Operation not permitted", like so...
No media catalog number present.
scanning for ISRCs: 20 ...
index scan: 20...
samplefile size will be 494726780 bytes.
recording 2804.5733 seconds stereo with 16 bits @ 44100.0 Hz ->'audio'...
using lib paranoia for reading.
cdda2wav: Operation not permitted. Cannot set process capabilities.
cdda2wav: Operation not permitted. Cannot set posix realtime scheduling policy.
But everything seems to work OK, so I'm satisfied.
--
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications
prev parent reply other threads:[~2015-09-19 23:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-18 21:14 [gentoo-user] File-system mounting questions Walter Dnes
2015-09-18 21:36 ` Fernando Rodriguez
2015-09-19 19:06 ` Walter Dnes [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=20150919190651.GA20920@waltdnes.org \
--to=waltdnes@waltdnes.org \
--cc=gentoo-user@lists.gentoo.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