public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin@cygwin.com
Subject: Re: Manipulating user privileges (was Re: SSHD, Cygwin and Windows 2003)
Date: Tue, 23 Sep 2003 13:26:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0309230920200.25002@slinky.cs.nyu.edu> (raw)
In-Reply-To: <20030923082733.GA17175@cygbert.vinschen.de>

On Tue, 23 Sep 2003, Corinna Vinschen wrote:

> On Mon, Sep 22, 2003 at 09:43:45PM +0100, Chris Rodgers wrote:
> > OK. I've had a crack at this. The packages can be found at:
> > http://rodgers.org.uk/editrights/
> > and are released under a BSD-style licence.
>
> Would you mind to send an ITP message to cygwin-apps@cygwin.com as
> described under http://cygwin.com/setup.html#submitting?
>
> The package is more or less preapproved but I would like to discuss
> a few details (on cygwin-apps, which is the appropriate list for
> package maintainer discussions).
>
> E.g. adding and removing and listing are very talkative by default.
> While the listing option allows to add a -q option, this doesn't work
> for -a and -r.
>
> It's your tool, after all, but IMHO it would be more suitable for
> scripting to turn around the behaviour:  No output on -a and -r if
> they work, error output otherwise, only listing the rights with -l.
> The lot of output only with additional verbose option.
>
> Corinna

Also error codes on failure, and the ability to check whether a user has
certain rights (without using grep).  If we decide to adopt it as a
package, could we have a CVS repository for it under cygwin-apps (like for
cygrunsrv), controlled by Chris (Rodgers), so that people can submit
patches against CVS if need be?  Unless Chris plans to release it totally
separate from Cygwin...
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

  reply	other threads:[~2003-09-23 13:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-15 19:30 SSHD, Cygwin and Windows 2003 Mark J de Jong
2003-09-16 10:26 ` Manipulating user privileges (was Re: SSHD, Cygwin and Windows 2003) Corinna Vinschen
2003-09-16 11:38   ` Brian Dessent
2003-09-16 12:57     ` Corinna Vinschen
2003-09-18  0:19   ` Chris Rodgers
2003-09-18  7:57     ` Corinna Vinschen
2003-09-22 21:10       ` Chris Rodgers
2003-09-23  8:41         ` Corinna Vinschen
2003-09-23 13:26           ` Igor Pechtchanski [this message]
2003-09-23 14:14             ` Corinna Vinschen
2003-09-23 14:22               ` Igor Pechtchanski
2003-09-23 18:42                 ` Hannu E K Nevalainen (garbage mail)
2003-09-23 18:56               ` Chris Rodgers

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=Pine.GSO.4.56.0309230920200.25002@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin@cygwin.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).