From: Ludwig Nussel <ludwig.nussel@suse.de>
To: util-linux@vger.kernel.org
Subject: Re: su(1) wish list
Date: Tue, 29 May 2012 14:15:29 +0200 [thread overview]
Message-ID: <4FC4BDE1.7000303@suse.de> (raw)
In-Reply-To: <20120529113418.GB374@x2.net.home>
Karel Zak wrote:
> On Tue, May 29, 2012 at 11:06:09AM +0200, Karel Zak wrote:
>> On Thu, May 24, 2012 at 02:58:01PM +0200, Ludwig Nussel wrote:
>>> I've also filed a pull request on github:
>>> https://github.com/karelzak/util-linux/pull/10
>>
>> Merged, but you forgot man page ;-) I don't think we need whole
>> history for the man page, so just copy and edit any existing su.1
>> man page and send it as a patch.
The su man page from coreutils is pretty brief. More docu is in the
info page. The license is the FDL, would that be ok or would a new
man page from scratch be better? Or maybe the one from shadow-utils?
> another issue:
>
> - why su.c expects "PATH" and "SUPATH" login default variables, but
> login.c expects "ENV_PATH" and "ENV_SUPATH"?
>
> See also login.def man page from shadow-utils where ENV_* is
> documented (for login as well as for su).
>
> IMHO we need to share the configuration between login and su.
No idea why it is different. Probably legacy stuff. I see no reason
why to use different values than login though.
> and wish list:
ACK
cu
Ludwig
--
(o_ Ludwig Nussel
//\
V_/_ http://www.suse.de/
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2012-05-29 12:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-24 12:58 [PULL] su Ludwig Nussel
2012-05-25 7:41 ` Karel Zak
2012-05-25 9:55 ` Ludwig Nussel
2012-05-29 9:06 ` Karel Zak
2012-05-29 11:34 ` su(1) wish list Karel Zak
2012-05-29 12:15 ` Ludwig Nussel [this message]
2012-05-29 12:30 ` Voelker, Bernhard
2012-05-30 13:42 ` 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=4FC4BDE1.7000303@suse.de \
--to=ludwig.nussel@suse.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.