public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: base-files-4.2-3 : attention maintainer
Date: Sat, 26 Sep 2015 09:57:00 -0000	[thread overview]
Message-ID: <87mvw9ijv0.fsf@Rainer.invalid> (raw)
In-Reply-To: <5605983C.8060909@cornell.edu> (Ken Brown's message of "Fri, 25	Sep 2015 14:53:48 -0400")

Ken Brown writes:
> As long as you're updating base-files anyway, maybe you could
> implement one of the previously-discussed proposals for showing a
> prompt of "#" instead of "$" in shells with sufficient privileges.
> Unfortunately, I don't remember if there was ever a consensus reached
> on exactly how that should be done.

You'd need to check that group 544 is in your user token.  Some folks
say 114 too, but if you use cygdrop -l, this group will stay in your
token, while you are _not_ having local admin rights anymore.

But calling id on a domain member machine can, under unfavorable
circumstances, take more than a minute to complete.  The AD integration
for Cygwin has developed further since I last saw this problem so it's
possible it's been solved along with some other things.  However since
I've not had the time yet to try and re-create the setup that most
consistently showed the problem I don't want to put it into any standard
startup files.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Samples for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra

--
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:[~2015-09-26  9:57 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-22 23:04 Issues encountered with new Cygwin version Walter L.
2015-09-23  8:20 ` Andrey Repin
2015-09-23 14:47   ` Walter L.
2015-09-23 16:20     ` Andrey Repin
2015-09-24  2:39     ` Linda Walsh
2015-09-24  4:34       ` Walter L.
2015-09-24  4:43         ` Linda Walsh
2015-09-24 10:35           ` Andrey Repin
2015-09-24 13:21           ` Walter L.
2015-09-24 16:49             ` Linda Walsh
2015-09-24 18:35               ` Andrey Repin
2015-09-25 15:01               ` Walter L.
2015-09-25 15:23                 ` Ken Brown
2015-09-25 16:04                   ` Ken Brown
2015-09-25 18:01                     ` Walter L.
2015-09-25 18:24                       ` Ken Brown
2015-09-25 18:37                         ` Walter L.
2015-09-26  9:21                 ` Andrey Repin
2015-09-26 20:26                   ` Walter L.
2015-09-26 22:10                     ` Ken Brown
2015-09-27  3:56                       ` Walter L.
2015-09-27 10:05                         ` Andrey Repin
2015-09-27 14:45                           ` Walter L.
2015-09-24  2:26   ` Linda Walsh
2015-09-24  5:35 ` Marco Atzeri
2015-09-24 14:24 ` base-files-4.2-3 : attention maintainer Marco Atzeri
2015-09-24 17:29   ` Achim Gratz
2015-09-25 18:53     ` Ken Brown
2015-09-26  9:21       ` Andrey Repin
2015-09-26  9:57       ` Achim Gratz [this message]

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=87mvw9ijv0.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).