public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: util-linux@vger.kernel.org
Subject: [PATCH] Remove obsolete and confusing statement from mount.8
Date: Sat,  8 Feb 2014 11:44:02 -0500	[thread overview]
Message-ID: <1391877842-11247-1-git-send-email-psusi@ubuntu.com> (raw)

The wording was confusing and suidperl has gone the way
of the dodo, and really didn't need mentionting in mount.8.

Signed-off-by: Phillip Susi <psusi@ubuntu.com>
---
 sys-utils/mount.8 | 3 +--
 1 file changed, 1 insertion(+), 2 deletions(-)

diff --git a/sys-utils/mount.8 b/sys-utils/mount.8
index fd68f18..5ac5ea5 100644
--- a/sys-utils/mount.8
+++ b/sys-utils/mount.8
@@ -1078,8 +1078,7 @@ effect.
 .TP
 .B nosuid
 Do not allow set-user-identifier or set-group-identifier bits to take
-effect. (This seems safe, but is in fact rather unsafe if you have
-suidperl(1) installed.)
+effect.
 .TP
 .B silent
 Turn on the silent flag.
-- 
1.8.3.2


             reply	other threads:[~2014-02-08 16:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-08 16:44 Phillip Susi [this message]
2014-02-10 18:04 ` [PATCH] Remove obsolete and confusing statement from mount.8 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=1391877842-11247-1-git-send-email-psusi@ubuntu.com \
    --to=psusi@ubuntu.com \
    --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