From: William Kenworthy <billk@iinet.net.au>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] More file system frustration
Date: Thu, 08 Nov 2012 20:39:30 +0800 [thread overview]
Message-ID: <1352378370.14159.2.camel@moriah> (raw)
In-Reply-To: <509B9065.6070104@fastmail.co.uk>
On Thu, 2012-11-08 at 10:58 +0000, Kerin Millar wrote:
> William Kenworthy wrote:
> > If I try and do:
> >
> > moriah ~ # mount -t ceph 192.168.44.68:6789:/ /mnt/ceph -o users
> > mount error 22 = Invalid argument
> >
>
> Specifying "users" in that context doesn't make sense. Try creating an
> entry in /etc/fstab. For example:
>
> 192.168.44.68:6789:/ /mnt/ceph ceph users 0 0
>
> Then see if you can mount by its mountpoint:
>
> $ mount /mnt/ceph
>
> > It turns out the driver doesnt recognise the user or users mount option
> > and gentoo wont let a user mount or access a root mount, or even let a
> > user mount. Tried adding the user to the disk group without any effect.
> >
>
> It's not a driver option. /bin/mount is suid root and refers to fstab to
> decide whether a non-root user should be allowed to mount.
>
> Generally speaking, regular user accounts should not be added to the
> disk group. That provides raw read/write access to block device nodes
> such as dev/sda, which is a potential risk both in terms of safety and
> security.
>
> > Something in gentoo's user access control is causing this problem I
> > think, so how can I get around it?
> >
> > BillK
> >
> >
Thanks Kerin, but that has the same problem - but it did allow me to
chown the mount point so its usable/testable by users.
BillK
prev parent reply other threads:[~2012-11-08 12:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-08 9:59 [gentoo-user] More file system frustration William Kenworthy
2012-11-08 10:37 ` Bill Kenworthy
2012-11-08 10:58 ` Kerin Millar
2012-11-08 12:39 ` William Kenworthy [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=1352378370.14159.2.camel@moriah \
--to=billk@iinet.net.au \
--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