From: Karel Zak <kzak@redhat.com>
To: Benno Schulenberg <bensberg@justemail.net>
Cc: Util-Linux <util-linux@vger.kernel.org>
Subject: Re: mount: what is the point of 'nouser' on the command line?
Date: Tue, 15 Jul 2014 10:02:34 +0200 [thread overview]
Message-ID: <20140715080234.GP30288@x2.net.home> (raw)
In-Reply-To: <1405351467.26224.141460601.7C1F0818@webmail.messagingengine.com>
On Mon, Jul 14, 2014 at 05:24:27PM +0200, Benno Schulenberg wrote:
>
> On Mon, Jul 14, 2014, at 16:57, Karel Zak wrote:
> > The "user" option is alias to "noexec,nosuid,nodev" mount flags.
>
> Ehm... Not quite. It *implies* those options, to lightly protect
> the user from some dangers, but its main purpose is to allow
> ordinary users to mount the filesystem so marked in fstab. No?
Sure, I have talked about the options and how the options are
evaluated.
> > > So, is it ever useful to specify '-o nouser' on the command line?
> >
> > No, it would be better to remove it from the example
>
> Will submit a patch later.
Thanks.
> > > Something else. On the man page of umount, shouldn't it say that
> > > the -O and -t options are only effective in combination with -a?
> >
> > The -t is generic and it's usable in more case (for example to
> > specify filesystem that should be tried for the device).
>
> Ehm... I was talking about umount here, not mount. :)
Oh... sorry :-) Anyway, it's the same, the "-t" is usable without -a
too.
umount -a -t <type, ...>
the <type> is interpreted as pattern.
umount -t <type>
the <type> is filesystem type (so you can force umount to use for
example /sbin/umount.<type>).
The -O is usable with -a only.
Karel
--
Karel Zak <kzak@redhat.com>
http://karelzak.blogspot.com
next prev parent reply other threads:[~2014-07-15 8:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 9:57 mount: what is the point of 'nouser' on the command line? Benno Schulenberg
2014-07-14 14:57 ` Karel Zak
2014-07-14 15:24 ` Benno Schulenberg
2014-07-15 8:02 ` Karel Zak [this message]
2014-07-15 9:02 ` umount: --types does not limit Benno Schulenberg
2014-07-15 9:56 ` Karel Zak
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=20140715080234.GP30288@x2.net.home \
--to=kzak@redhat.com \
--cc=bensberg@justemail.net \
--cc=util-linux@vger.kernel.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