public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Mark J. Reed" <markjreed@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Reading what should not!
Date: Mon, 14 Sep 2009 15:00:00 -0000	[thread overview]
Message-ID: <f60fe000909140800l71008f78s42e58819fd93e0eb@mail.gmail.com> (raw)
In-Reply-To: <4AAE52A1.6000409@alice.it>

On Mon, Sep 14, 2009 at 10:26 AM, Angelo Graziosi  wrote:
> I do not have Fedora but Kubuntu (8.04 and 9.04). On Kubuntu the user
> created in the installation step, say 'pippo', is also 'root' in the sense
> that 'pippo' needs 'sudo' (or 'sudo su') for administrative usage.

OK, then, big difference. 'pippo' is not root, pippo is able to do
things as root when needed.  Administrative users on Windows are
treated as equivalent to root by Cygwin.

If you're saying that admin users should have to use sudo or
equivalent to gain elevated access in Cygwin, then that's a feature
request.  Does it match what Windows does?  Outside of UAC in Vista
I'm unaware of Administrators having to do anything to activate their
privileges.

-- 
Mark J. Reed <markjreed@gmail.com>

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

  parent reply	other threads:[~2009-09-14 15:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-14 14:26 Angelo Graziosi
2009-09-14 14:59 ` Thrall, Bryan
2009-09-14 15:00 ` Mark J. Reed [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-09-14 16:20 Angelo Graziosi
2009-09-14  8:29 Angelo Graziosi
2009-09-14 10:40 ` Mark J. Reed
2009-09-14 10:47 ` Dave Korn
2009-09-14 18:12 ` Matt Wozniski
2009-09-13 14:05 Angelo Graziosi
2009-09-13 23:11 ` Larry Hall (Cygwin)

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=f60fe000909140800l71008f78s42e58819fd93e0eb@mail.gmail.com \
    --to=markjreed@gmail.com \
    --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).