Bug 158740 - Misleading message in 'su' info document
Misleading message in 'su' info document
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: coreutils (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Tim Waugh
Depends On: 102697
Blocks: 156320
  Show dependency treegraph
Reported: 2005-05-25 08:19 EDT by Tim Waugh
Modified: 2007-11-30 17:07 EST (History)
0 users

See Also:
Fixed In Version: RHBA-2005-544
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-28 13:02:26 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Tim Waugh 2005-05-25 08:19:49 EDT
+++ This bug was initially created as a clone of Bug #102697 +++

[The following was originally sent to rhl-devel-list and is being posted on
bugzilla by request.]

I'm sure by now most of you have read the "Why GNU 'su' does not support
the 'wheel' group" rant from RMS written years ago.  If you have not
seen it yet do a quick 'info su' and scroll down to the bottom.

What surprises me is this has not been pulled from the 'su' info page
years(?) after pam_wheel showed up in pam.  The statement that GNU 'su'
does not support the 'wheel' group may be technically true in the form
shipped by the GNU but it is misleading when used in Red Hat.  If I were
looking for wheel support and decided to check the su info page (as
suggested by the su man page) I would have read this statement and may
never have figured out the functionality was actually being provided!

In my opinion such historical baggage is harmful and should be pulled
from at least Red Hat's copy of the 'su' info page.
Comment 8 Red Hat Bugzilla 2005-09-28 13:02:26 EDT
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.