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: Install puts bin/ and terminfo/ directories in wrong directory.


Ugh, top-posting...  Reformatted.

On Fri, 20 Jan 2006, Alan Ramsey wrote:

> --- Igor Peshansky <pechtcha@XX.XXX.XXX> wrote:

<http://cygwin.com/acronyms/#PCYMNTQREAIYR>.  Thanks.

> > On Fri, 20 Jan 2006, Alan Ramsey wrote:
> >
> > > > Apparently, the PDFMerge program uses its own
> > > > min-cygwin distribution.
> > >
> > > I don't know if that is the case or not.  PDFMerge is no longer
> > > installed on that machine.  I searched for the Cygwin1.dll on the
> > > entire machine and am only finding the ones that I installed, so I
> > > don't think this is the problem.
> > >
> > > > .. other than to advise that you redo your installation and use
> > > > c:\cygwin as the root rather than letting setup.exe use the
> > > > existing root set up by PDFMerge.
> > >
> > > How do I do that?  I have tried reinstalling several time, including
> > > deleting all the cygwin directories that I know of and entering
> > > c:\cygwin into the installation program.  It still wants to go to
> > > the PDFMerge directory.  Where does the installation program get the
> > > root directory from?
> >
> > Please read and follow the Cygwin problem reporting guidelines at
> >
> > > Problem reports:      http://cygwin.com/problems.html
> >
> > to provide enough information about your system for us to be able to
> > help you.

I've slightly reordered your quotes below for a better logical flow of my
reply...

> Below is the output from cygcheck.

In the future, please *attach* the output of cygcheck, rather than include
it inline, as that litters the archive searches with false positives.

> Cygwin Configuration Diagnostics
> [snip]
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2
>   (default) = '/cygdrive'
>   cygdrive flags = 0x00000022
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/
>   (default) = 'C:\cygwin'
>   flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/bin
>   (default) = 'c:\downloads\PDFMerge\bin'
>   flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/tmp
>   (default) = 'C:\DOCUME~1\SVALLA~1\LOCALS~1\Temp'
>   flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/bin
>   (default) = 'c:\downloads\PDFMerge\bin'
>   flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/lib
>   (default) = 'C:\cygwin/lib'
>   flags = 0x0000000a
> HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2\/usr/share/terminfo
>   (default) = 'c:\downloads\PDFMerge\terminfo'
>   flags = 0x0000000a
> [snip]

Right, as I suspected, you had stale mount table entries.  I'm glad you
also found this out yourself.  Note that if we didn't ask for the output
of cygcheck, we would have had to have a long back-and-forth exchange
before getting to this point...

> C:\cygwin                           /                    system  binmode
> c:\downloads\PDFMerge\bin           /bin                 system  binmode
> C:\DOCUME~1\SVALLA~1\LOCALS~1\Temp  /tmp                 system  binmode
> c:\downloads\PDFMerge\bin           /usr/bin             system  binmode
> C:\cygwin/lib                       /usr/lib             system  binmode
> c:\downloads\PDFMerge\terminfo      /usr/share/terminfo  system  binmode
> .                                   /cygdrive            system  binmode,cygdrive

And here are the mounts that show the same problem.

> I believe I have I found the problem,

Yes, you did.

> although I also believe it is indicative of a bug in the installation
> program.

I don't think so.  The installer intentionally does not change the
existing mounts, so as to not override the settings of users who choose to
customize their on-disk layout.  It's very rare that a
<http://cygwin.com/acronyms/#3PP> application like PDFMerge leaves its own
stale mounts behind.

> The output from the cygcheck program (see below) shows me the entries in
> the registry point to the PDFMerge directory.
>
> Evidently this is what sets the location of the bin\ and terminfo\
> directories - which was the question I asked in the original email.

These aren't just *any* registry entries -- they are mount table entries.
And your original question could not have been definitively answered
without the cygcheck output.

> My guess is the user of the machine I was installing on mistakenly tried
> to install here in the first place.

My guess would be that PDFMerge misbehaved.  That's why we call them 3PPs
(see the acronym link above).

> However, evidently the installation program, probably due to a bug,
> doesn't properly reset these values once they are set, regardless of
> what is entered during subsequent re-installs, unless one wipes the
> registry manually.

You don't need to wipe the registry -- there are other tools for
manipulating the mount table (i.e., "mount").  The installation program
does not touch the mounts by design.

> I am going to drop the entire HKEY_CURRENT_USER\Software\Cygnus
> Solutions\ tree, delete the c:\cygwin directory and reinstall from
> scratch.  I think this will fix everything.  (I know I could probably
> just change the registry entries, but I don't trust that something
> somewhere else is already screwed up because of this, so I would rather
> have a vanilla install).

That's pretty drastic.

I suggest you use the "mount" and "umount" commands to reset the entries.
You want to "umount /bin /usr/bin /usr/share/terminfo" and then "mount -f
c:/cygwin/bin /usr/bin" (you may need to specify the full path to "mount"
and "umount").  Since you already moved c:\downloads\PDFMerge\bin to
c:\cygwin\bin, and c:\downloads\PDFMerge\terminfo to
c:\cygwin\usr\share\terminfo, you should just remove those directories
altogether).  You should also remove the /tmp mount (or other
users/services on the machine will not be able to access /tmp), or at
least remount it as a user mount (not a system one).

> Thanks to Christopher Faylor for your kind assistance.
> I appreciate people who really try to help.

Then you must not have seen <http://cygwin.com/acronyms/#CGF> and
<http://cygwin.com/acronyms/#WJM>. :-)
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_	    pechtcha@cs.nyu.edu | igor@watson.ibm.com
ZZZzz /,`.-'`'    -.  ;-;;,_		Igor Peshansky, Ph.D. (name changed!)
     |,4-  ) )-,_. ,\ (  `'-'		old name: Igor Pechtchanski
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"Las! je suis sot... -Mais non, tu ne l'es pas, puisque tu t'en rends compte."
"But no -- you are no fool; you call yourself a fool, there's proof enough in
that!" -- Rostand, "Cyrano de Bergerac"

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