Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: cygwin AT cygwin DOT com
From: Nick Sabalausky <nsabalausky05 AT jcu DOT edu>
Subject: Re: No /bin after installation
Date: Thu, 22 Jul 2004 19:17:01 +0000 (UTC)
Lines: 42
Message-ID: <loom.20040722T210828-344@post.gmane.org>
References: <loom DOT 20040722T094334-981 AT post DOT gmane DOT org> <20040722141119 DOT GA3457 AT trixie DOT casa DOT cgf DOT cx> <loom DOT 20040722T185240-475 AT post DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 58 DOT 0407221314470 DOT 20104 AT slinky DOT cs DOT nyu DOT edu> <loom DOT 20040722T193846-97 AT post DOT gmane DOT org> <Pine DOT GSO DOT 4 DOT 58 DOT 0407221402510 DOT 20104 AT slinky DOT cs DOT nyu DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Complaints-To: usenet AT sea DOT gmane DOT org
X-Gmane-NNTP-Posting-Host: main.gmane.org
User-Agent: Loom/3.14 (http://gmane.org/)
X-Loom-IP: 69.171.34.91 (Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; Q312461; iRider 2.10.0008; .NET CLR 1.1.4322; .NET CLR 1.0.3705))
X-IsSubscribed: yes

Igor Pechtchanski <pechtcha <at> cs.nyu.edu> writes:

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


Ok, I've deleted the entire "HKEY_LOCAL_MACHINE\Software\Cygnus Solutions"
registry tree, renamed "c:\cygnus\cygwin-b20\" to
"c:\cygnus-hidethis\cygwin-b20\", and tried to install again.
But, for some reason, it *still* went ahead and created the
directory "c:\cygnus\cygwin-b20\H-i586-cygwin32\bin", stuck
the bin files in there, and pointed the "/usr/bin" registry
key to that.

I manually copied that bin directory to "D:/cygwin/bin" and
 changed the registry entry to point to that and now I can
 get into Cygwin and a shell.

However, now the problem I have is that when I'm in that shell,
 I can't get to /cygdrive/c or /cygdrive/c.  An ls on the root
directory reveals "bin  cygwin.bat  cygwin.ico  etc  home  lib
  usr  var", but not "cygdrive".


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