This is the mail archive of the cygwin mailing list for the Cygwin project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: No /bin after installation


On Thu, 22 Jul 2004, Nick Sabalausky wrote:

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

Umm, I should have mentioned the user mounts (stored under
"HKEY_CURRENT_USER\Software\Cygnus Solutions").  Those may have been wrong
too...  Weird.

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

One thing to have looked at is the "How do I uninstall all of Cygwin" FAQ
entry: <http://cygwin.com/faq/faq_2.html#SEC19>.

> 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".

/cygdrive is a virtual filesystem (just like /proc and /dev).  You can
create a /cygdrive directory if you want to, for tab completion and the
like.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.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/


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]