From: De-Jian Zhao <dejian.zhao@gmail.com>
To: CygwinList <cygwin@cygwin.com>
Subject: Why /usr/bin/*.dll must be executable?
Date: Fri, 20 Apr 2012 13:03:00 -0000 [thread overview]
Message-ID: <4F915E65.8070608@gmail.com> (raw)
Hi,
When I type "cyg" and Tab, many executables starting with "cyg" are
listed (Display all 262 possibilities? (y or n) y). I find that many of
them are *.dll libraries under /usr/bin/. This is inconvenient to find
the real executable applications (*.exe). Since *.dll files are only
libraries, they are not necessary to have the attribute of "x". Thus, I
run the command "chmod a-x /usr/bin/*.dll". Unexpectedly, cygwin is
corrupted. I closed the terminal and failed to restart Cygwin. I started
my older version of Cygwin (I did not deleted it after installing a new
version), and added "x" to the previous *.dll files. The dead Cygwin
revived.
I am confused why /usr/bin/*.dll should be executable. I thought they
were only library files. When I tried to run a dll file, bash says
"cannot execute binary file". Are there some hidden stories?
The error messages are as follows:
Administrator@acer /usr/bin
$ chmod a-x *.dll
Administrator@acer /usr/bin
$ lh
18 [main] -bash 4512 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741790, errno 11
-bash: fork: retry: Resource temporarily unavailable
2020930 [main] -bash 4512 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741790, errno 11
-bash: fork: retry: Resource temporarily unavailable
4039235 [main] -bash 4512 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741790, errno 11
-bash: fork: retry: Resource temporarily unavailable
8057832 [main] -bash 4512 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741790, errno 11
-bash: fork: retry: Resource temporarily unavailable
16074662 [main] -bash 4512 fork: child -1 - forked process died
unexpectedly, retry 0, exit code -1073741790, errno 11
-bash: fork: Resource temporarily unavailable
DJ
--
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 reply other threads:[~2012-04-20 13:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-20 13:03 De-Jian Zhao [this message]
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)
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=4F915E65.8070608@gmail.com \
--to=dejian.zhao@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).