Installation How-To Draft

[Robert Collins]

I use cygwin=ntsec,
when I reinstalled the entire cygwin suite I got c0000022 errors in perl,
and
when I upgraded to the current X binaries I recieved the same error for Xwin
etc.. I didn't fix the issue with perl - but I was apparently searching the
wrong list archive - as the chmod o+x,g+x,u+x *.dll cmd did fix it for me.

I suspect there is a problem untarring or setting x when cygwin=ntsec.

I don't use cygwin=ntsec at the office, and I had no problems there.

Rob


----- Original Message -----
From: "Chris Faylor" <cgf@cygnus.com>
To: <cygwin-xfree@sources.redhat.com>
Cc: <Olivier.Jacquemin@DialogSystems.be>
Sent: Wednesday, September 13, 2000 7:15 AM
Subject: Re: Installation How-To Draft


> On Tue, Sep 12, 2000 at 05:51:15PM +0200, Olivier Jacquemin wrote:
> >Harold,
> >
> >My PC is part of a domain.  I am also part of the Administrators group of
my
> >machine.
> >
> >An 'ls -l *.dll' gives the following result if I do it just after
> >un-tarring:
> >-rw-r--r--   1 oja      None        72704 Jul 16 19:30 libICE.dll
> >-rw-r--r--   1 oja      None       203776 Jul 16 19:30 libPEX5.dll
> >-rw-r--r--   1 oja      None        29184 Jul 16 19:30 libSM.dll
> >
> >An important difference with your result is that the owner is myself
instead
> >of "administ".  This is due to the fact that my bash prompt is
"oja@Pc_oja"
> >instead of "administrator@Pc_oja" (and I don't remember how to change
this).
> >
> >Now I have reduced the necessary command for correct initialization of X
to
> >'chmod u+x *.dll'
> >Of course, I can get the same result by adding "Execute (X)" permission
for
> >user OJA on all these files using the GUI of Win NT.
> >
> >I hope you will find this information useful.
>
> What Cygwin options are you using?
>
> As I've previously indicated, 'chmod u+x' really should only has meaning
to
> Cygwin and only if you are using a specific option in the Cygwin
> environment variable.
>
> cgf
>