X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org From: "Dave Korn" To: References: <4b20672a0709180904j70296a32o18ba0df7e36d8a97 AT mail DOT gmail DOT com> Subject: RE: cygwin.bat/bash fails after install Date: Tue, 18 Sep 2007 18:50:21 +0100 Message-ID: <005a01c7fa1c$61e69c40$2e08a8c0@CAM.ARTIMI.COM> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <4b20672a0709180904j70296a32o18ba0df7e36d8a97@mail.gmail.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 18 September 2007 17:05, Jim Allen wrote: > After a successful installation of cygwin you run cygwin.bat and the > following message flashes briefly on your screen: > > bash: can't find configuration file /usr/local/etc/profile.global; exiting. Nope, that doesn't happen to anyone else: there is no such file as "profile.global" anywhere in any cygwin package at all. > The problem can be recreated by doing the following: > > Open a command shell (Run/cmd) > Switch to a drive other than C: > u: > exit > > Run setup.exe. The install will work, but you will get the error message. You need to understand a bit better how your computer works to realise how impossible this is. The current drive and current path settings exist purely on a per-process basis (they are maintained in local storage controlled by ntdll.dll, since you ask), and as per-process settings, once the process has exited, all trace of them is lost. The moment you close the DOS shell, there is no difference in your system than if you had never changed drive at all. Thinking it could somehow cause a change in the behaviour of a subsequent run of setup.exe is a false assumption (the computer equivalent of homeopathy, in fact!). > Resolution > Switch to C: in the command shell before running setup.exe > > Workaround: > See http://sourceware.org/ml/cygwin/2005-10/msg00651.html No, the real resolution would be to understand what had actually caused the error, which you haven't taken the time to find out yet, and then to fix the thing that actually caused the error. cheers, DaveK -- Can't think of a witty .sigline today.... -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/