public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Why /usr/bin/*.dll must be executable?
Date: Fri, 20 Apr 2012 17:46:00 -0000	[thread overview]
Message-ID: <4F91A0E9.6020606@cygwin.com> (raw)
In-Reply-To: <4F919ECB.3050909@gmail.com>

On 4/20/2012 1:37 PM, De-Jian Zhao wrote:
> On 2012-4-21 1:29, Larry Hall (Cygwin) wrote:
>> On 4/20/2012 1:25 PM, Nellis, Kenneth wrote:
>>> From: Corinna Vinschen
>>>> Windows requires the x bit for DLLs to be loadable as executable code
>>>> into the address space of a process. As Václav wrote, it's a Windows
>>>> thing.
>>>
>>> So, I had to play with "chmod -x cyg*.dll" and, of course, it
>>> totally hosed Cygwin. I recovered by reinstalling from scratch
>>> only after realizing that ATTRIB did not have an option to re-
>>> establish X--we're talking XP here. So, as this is a Windows
>>> thing, wondering how, through Windows, I could restore execute
>>> access to the DLLs.
>>
>> What's wrong with "chmod +x cyg*.dll"?
>>
>
> It doesn't work any more. You cannot restart a new terminal, either. You
> will be trapped here.

Ah, I didn't realize that Ken did this in /bin.  You could use cacls in
this case as an alternative to reinstalling.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
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

  reply	other threads:[~2012-04-20 17:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-20 13:03 De-Jian Zhao
2012-04-20 13:05 ` De-Jian Zhao
2012-04-20 13:08 ` Václav Zeman
2012-04-20 16:18   ` De-Jian Zhao
2012-04-20 16:28     ` Corinna Vinschen
2012-04-20 17:25       ` Nellis, Kenneth
2012-04-20 17:29         ` Larry Hall (Cygwin)
2012-04-20 17:37           ` De-Jian Zhao
2012-04-20 17:46             ` Larry Hall (Cygwin) [this message]
2012-04-20 17:40           ` Nellis, Kenneth
2012-04-20 17:32       ` De-Jian Zhao
2012-04-20 17:41         ` Larry Hall (Cygwin)
2012-04-20 17:47           ` De-Jian Zhao
2012-04-20 17:58             ` Larry Hall (Cygwin)
2012-04-20 18:21               ` De-Jian Zhao
2012-04-20 18:43                 ` Larry Hall (Cygwin)
2012-04-20 22:10                 ` Mike Kaganski
2012-04-22  2:29                   ` Larry Hall (Cygwin)
2012-04-20 18:05             ` Larry Hall (Cygwin)
2012-04-23 19:01   ` Warren Young
2012-04-23 20:16     ` Larry Hall (Cygwin)
2012-04-23 22:13       ` Warren Young
2012-04-23 23:55       ` Richard Troy
2012-04-24  0:19         ` Warren Young
2012-04-24 16:49           ` Larry Hall (Cygwin)
2012-04-20 19:06 ` Jon TURNEY
2012-04-21  3:37   ` De-Jian Zhao
2012-04-23 19:02   ` Warren Young
2012-04-23 19:26     ` David Sastre Medina

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=4F91A0E9.6020606@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.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).