X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-5.6 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,KHOP_RCVD_TRUST,KHOP_THREADED,RCVD_IN_DNSWL_LOW,RCVD_IN_HOSTKARMA_YE X-Spam-Check-By: sourceware.org Message-ID: <4F918C2A.2080300@gmail.com> Date: Sat, 21 Apr 2012 00:17:46 +0800 From: De-Jian Zhao User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:11.0) Gecko/20120312 Thunderbird/11.0 MIME-Version: 1.0 To: cygwin AT cygwin DOT com CC: vhaisman AT gmail DOT com Subject: Re: Why /usr/bin/*.dll must be executable? References: <4F915E65 DOT 8070608 AT gmail DOT com> In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com On 2012-4-20 21:07, Václav Zeman wrote: > On 20 April 2012 15:02, De-Jian Zhao wrote: >> 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? > DLLs are executables thus they need the +x bit. This is a Windows thing. > If this is a windows thing, removing the x bit should not affect Cygwin. Instead, Cygwin is corrupted after removing the x bit. -- 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