From: "Chris J. Breisch" <chris.ml@breisch.org>
To: cygwin@cygwin.com
Subject: Re: Baffled: is it Cygwin (64-bits) or Windows that causes the invocation of regedit (from bash) to fail?
Date: Sat, 10 May 2014 14:11:00 -0000 [thread overview]
Message-ID: <536E339A.6030200@breisch.org> (raw)
In-Reply-To: <849f1f5420ebf77d7a591d6c9b6bfa4b.squirrel@webmail.xs4all.nl>
Houder wrote:
> Hi,
>
> At my place I have installed both versions of Cygwin (i.e. 32-bits and 64-bits) -- of course,
> in different places. As "some" of you will have the "same" setup, I would like you to confirm
> the following (UNexpected, to me) result:
>
> - I canNOT invoke regedit from 64-bits bash (Yes, I can if bash has been invoked in ELEVATED mode)
> - I can invoke regedit from 64-bits bash (not elevated) as follows: cygstart regedit
> - however, I can invoke regedit from 32-bits bash (not elevated) ...
> - likewise, I can invoke regedit from 64-bits cmd (not elevated) ...
>
> By UNexpected result I mean: I cannot explain why I canNOT invoke regedit from 64-bits bash ...
[snip]
> E:\Cygwin64\bin\bash: /drv/c/WINDOWS/regedit: Permission denied
I can not duplicate your behavior. I can not invoke regedit from any
non-elevated bash prompt, regardless of whether it is 32-bit or 64-bit.
I get the above error in both cases.
--
Chris J. Breisch
--
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
next prev parent reply other threads:[~2014-05-10 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-10 13:42 Houder
2014-05-10 14:11 ` Chris J. Breisch [this message]
2014-05-12 12:50 ` Houder
2014-05-12 12:51 ` Andrey Repin
2014-05-12 17:13 ` Houder
2014-05-12 13:01 ` Corinna Vinschen
2014-05-12 13:15 ` Shaddy Baddah
2014-05-12 13:23 ` Corinna Vinschen
2014-05-12 18:47 ` Houder
2014-05-12 17:31 ` Houder
2014-05-13 15:10 ` Houder
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=536E339A.6030200@breisch.org \
--to=chris.ml@breisch.org \
--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).