From: Stephane Chazelas <stephane.chazelas@seebyte.com>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux-ng@vger.kernel.org
Subject: Re: [mount] --bind -o suid/exec/...
Date: Tue, 9 Feb 2010 17:09:41 +0000 [thread overview]
Message-ID: <chaz20100209170941.GA18491@seebyte.com> (raw)
In-Reply-To: <20100209162305.GG6375@nb.net.home>
2010-02-09 17:23:05 +0100, Karel Zak:
[...]
> > mount --bind /here /there
> > mount -o remount,noexec /there
[...]
> >, or better, "mount" could
> > be changed so that one can do it in a single step with:
> >
> > mount --bind -o noexec /here /there
>
> this is unsupported by kernel, the "remount" and "bind" are two
> different operations.
[...]
Thanks Karel,
but what about changing mount(8) so that it does two mount(2)s
upon --bind -o?
One thing I've not mentionned is that it makes it quite awkward
to add it in /etc/fstab.
/here /there none bind 0 0
there-remount /there none remount,noexec 0 0
works with mount -a but not with Ubuntu's mountall(8) for
instance.
Cheers,
Stephane
parent reply other threads:[~2010-02-09 17:09 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20100209162305.GG6375@nb.net.home>]
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=chaz20100209170941.GA18491@seebyte.com \
--to=stephane.chazelas@seebyte.com \
--cc=kzak@redhat.com \
--cc=util-linux-ng@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