chere + mintty doesn't work with mapped drives

[Corinna Vinschen]

On Dec  2 23:58, Charles Butterfield wrote:
> > -----Original Message-----
> > From: Dave Kilroy [mailto:BZZZZZ]


http://cygwin.com/acronyms/#PCYMTNQREAIYR


> > On 01/12/2013 21:09, Corinna Vinschen wrote:
> > > Are you starting mintty with "run as administrator" by any chance?
> > Corrina's right - check that the same user is being used in both cases.
> > I don't think this would explain why it's not working from the context menus
> > though. Finding out why bash under mintty doesn't think /cygdrive/y/apps is
> > a directory is the key.
> 
> SOLVED
> 
> Yes, I was starting mintty "as admin" and yes this was the culprit.
> I was doing this by using a shortcut (similar, but not identical to the installed
> "Cygwin Terminal" shortcut), that had the checkbox 
> "Compatibility|Run this program as an administrator" enabled.
> 
> I ASSUMED this would only affect mintty when launched from this shortcut.
> 
> HOWEVER, it seems that this changes a property associated with mintty
> regardless of how it is launched.  Apparently another "Wonder of Windows".
> 
> Unchecking the "run as admin" fixed the problem associated with accessing
> the mapped drives everywhere (including the "Bash Prompt Here" xhere
> Processing).
> 
> The reason I was running as admin was that many of the network centric
> scripts that I use frequently during certain phases of various projects seem
> to require admin privs and simply fail without any attempt to escalate (which
> I seem to recall is due to a mismatch between the Windows and Unix
> Security models).  I guess I'll have to rethink that approach.
>  
> Any suggestions on how to have a shortcut (or something similar) that
> runs mintty as admin, but has no global effect on other mintty launches?

You seem to have gotten something else wrong here.  If the shortcut has
the "run as admin" flag, it only affects this shortcut.  I have two
shortcuts on the desktop, one called "Cygwin64 Terminal", the other one
"Cygwin64 Admin".  The second shortcut is a simple copy of the first
one, so it starts "C:\cygwin64\bin\mintty.exe -i /Cygwin-Terminal.ico -"
just like the first.  Only the second shortcut has the "Run as admin"
flag set.  If I start mintty from the first shell, id prints:

  uid=11001(corinna) gid=11125(vinschen) groups=11125(vinschen),
  559(Performance Log Users),545(Users),
  10572(Denied RODC Password Replication Group),10513(Domain Users)

If I start mintty from the second shortcut, id prints

  uid=11001(corinna) gid=11125(vinschen) groups=11125(vinschen),
  544(Administrators),559(Performance Log Users),545(Users),        !!!
  10572(Denied RODC Password Replication Group),10513(Domain Users)

And, btw., I created the Admin shortcut just for testing.  Otherwise
I usually only do a right click on the shortcut and use the "Run as
administrator" entry there.  It's much less hassle than creating
an extra shortcut for this task.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20131203/8718787f/attachment.sig>