public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Walter Dnes" <waltdnes@waltdnes.org>
To: Gentoo Users List <gentoo-user@lists.gentoo.org>
Subject: [gentoo-user] File-system mounting questions
Date: Fri, 18 Sep 2015 17:14:15 -0400	[thread overview]
Message-ID: <20150918211415.GA26401@waltdnes.org> (raw)

  A while ago, I mentioned that I had problems running cdda2wav as a
regular user.  While rebuilding cdrtools recently, I noticed that the
build finished with the following warnings...

>>> Installing (1 of 1) app-cdr/cdrtools-3.01_alpha17::gentoo
 * >>> SetUID: [chmod go-r] /usr/sbin/rscsi ...                          [ ok ]
 * >>> SetUID: [chmod go-r] /usr/bin/cdda2wav ...                        [ ok ]
 * >>> SetUID: [chmod go-r] /usr/bin/readcd ...                          [ ok ]
 * >>> SetUID: [chmod go-r] /usr/bin/cdrecord ...                        [ ok ]
 * Could not set caps on '/usr/bin/cdrecord' 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)
 * Could not set caps on '/usr/bin/cdda2wav' 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)
 * 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
< > The Extended 4 (ext4) filesystem

...rebuilt, and rebooted into it.  Still the same warnings on the build.
So now it appears that I have to...
> mount the fs with the user_xattr option (if not the default)
> enable the relevant FS_SECURITY option (if configurable)

  Can someone point me to an example somewhere of how to do it?  I
prefer not to muck around blindly with unknown options in /etc/fstab
BTW, I'm building cdrtools with USE="caps filecaps -acl -nls -unicode"
if that matters.

-- 
Walter Dnes <waltdnes@waltdnes.org>
I don't run "desktop environments"; I run useful applications


             reply	other threads:[~2015-09-18 21:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18 21:14 Walter Dnes [this message]
2015-09-18 21:36 ` [gentoo-user] File-system mounting questions Fernando Rodriguez
2015-09-19 19:06   ` Walter Dnes

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=20150918211415.GA26401@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