Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs Date: Thu, 22 Jul 2004 14:10:51 -0400 (EDT) From: Igor Pechtchanski Reply-To: cygwin AT cygwin DOT com To: Nick Sabalausky cc: cygwin AT cygwin DOT com Subject: Re: No /bin after installation In-Reply-To: Message-ID: References: <20040722141119 DOT GA3457 AT trixie DOT casa DOT cgf DOT cx> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Scanned-By: MIMEDefang 2.39 On Thu, 22 Jul 2004, Nick Sabalausky wrote: > Igor Pechtchanski cs.nyu.edu> writes: > > > Just a WAG: is there a "C:/cygwin/bin"? Also, is there an > > "HKLM\Software\Cygnus Solutions" key in the registry? What are its > > contents? > > Igor > > There is no "C:/cygwin/bin". > There is an "HKEY_LOCAL_MACHINE\Software\Cygnus Solutions". > It contains the keys: "Cygwin", "Cygwin B20", > "CYGWIN.DLL setup", and "GNUPro". > > The "Cygwin B20" just contains the key "B20.1", but neither > contain any values. > > Hmm, the "Cygwin" key has a key "mounts v2" containing the keys "/", > "/usr/bin", "/usr/lib", and "/usr/X11R6/lib/X11/fonts". All of those > have a value labeled "native". The value for "native" in "/" is > "D:/Cygwin" which if my installation directory, the values for "native" > in "/usr/lib" and "/usr/X11R6/lib/X11/fonts" are both subdirectories of > D:/Cygwin, but for some reason in "/usr/bin" it's > "c:\cygnus\cygwin-b20\H-i586-cygwin32\bin". *THAT'S IT*. That's your problem right here. Basically, setup will not change an existing /usr/bin mount, if there is one, and it will install things into /usr/bin, not /bin, so all of the new apps just went to wherever /usr/bin pointed to. Your best bet would probably be to remove the "HKLM/SOFTWARE/Cygnus Solutions" key altogether, remove "D:\cygwin", and reinstall from scratch (you may also want to remove "c:\cygnus\cygwin-b20\H-i586-cygwin32", as it now contains the new Cygwin executables and is probably unusable). > That's not good if the installer is mixing up old and new installations > from completely different paths... Good point. This is debatably a bug in the installer. It *will* check whether the root mount is different and change the others accordingly, but it will not touch the /usr/bin and /usr/lib mounts if they point outside of the root. Perhaps it should at least issue a warning if this is the case (as most of the Cygwin software relies on /usr/bin = /bin). In the meantime, perhaps the installation guide should mention that if you had an old (really old) version of Cygwin on your machine, its mounts may confuse setup. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_ pechtcha AT cs DOT nyu DOT edu ZZZzz /,`.-'`' -. ;-;;,_ igor AT watson DOT ibm DOT com |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! "I have since come to realize that being between your mentor and his route to the bathroom is a major career booster." -- Patrick Naughton -- 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/