RE: version 1.3 10, problem with gunzip.exe

RE: version 1.3 10, problem with gunzip.exe

[Robert Collins]

> -----Original Message-----
> From: Robert Collins 
> Sent: Tuesday, May 21, 2002 8:46 AM
> 
> >    2. I believe setup.exe creates symbolic links as if
> > "nowinsymlinks" is 
> >       set.  So setup would create the symbolic links as 
> > Cygwin symlinks 
> >       rather than Windows shortcuts regardless of the 
> setting in the 
> >       CYGWIN environment variable.
> 
> 2 is wrong.

Actually, 2 is right. Setup could do either though.

Rob
 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: version 1.3 10, problem with gunzip.exe

[Robert Collins]

> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [mailto:lhall@rfk.com] 
> Sent: Wednesday, May 22, 2002 1:00 AM

> I guess I can see some value to having the symlinks that 
> setup generates be windows shortcuts.  The obvious plus is 
> that symbolic links to executables and other files should be 
> understood in non-Cygwin shells.  Still, while this is an 
> advantage for those packages that make using of symbolic links for 
> things like this, it's unclear to me that making such a 
> change would result in 
> something intuitive, since the user would need to add ".lnk" to the 
> executable name ("gunzip.exe.lnk" in this case) to get it to 
> work in an non- Cygwin shell.  But probably it's a plus 
> overall since using the Windows shortcuts at least allows for 
> the use of the symlink in non-Cygwin shells, despite the 
> clunkiness of its usage.  In the current case, this is not true.
> 
> There's a nice bit of philosophy for you, don't you think?! ;-)

Yes :}. We initially left setup unchanged because the long term
existence of windows shortcuts wasn't clear, and we had to be backward
compatible. I think we are far enough beyond that that we could accept
patches to alter the behaviour.

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: version 1.3 10, problem with gunzip.exe

[Larry Hall (RFK Partners, Inc)]

At 06:49 PM 5/20/2002, Robert Collins wrote:


> > -----Original Message-----
> > From: Robert Collins 
> > Sent: Tuesday, May 21, 2002 8:46 AM
> > 
> > >    2. I believe setup.exe creates symbolic links as if
> > > "nowinsymlinks" is 
> > >       set.  So setup would create the symbolic links as 
> > > Cygwin symlinks 
> > >       rather than Windows shortcuts regardless of the 
> > setting in the 
> > >       CYGWIN environment variable.
> > 
> > 2 is wrong.
>
>Actually, 2 is right. Setup could do either though.



I guess I can see some value to having the symlinks that setup generates
be windows shortcuts.  The obvious plus is that symbolic links to executables
and other files should be understood in non-Cygwin shells.  Still, while this
is an advantage for those packages that make using of symbolic links for 
things like this, it's unclear to me that making such a change would result in 
something intuitive, since the user would need to add ".lnk" to the 
executable name ("gunzip.exe.lnk" in this case) to get it to work in an non-
Cygwin shell.  But probably it's a plus overall since using the Windows
shortcuts at least allows for the use of the symlink in non-Cygwin shells,
despite the clunkiness of its usage.  In the current case, this is not true.

There's a nice bit of philosophy for you, don't you think?! ;-)





Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: version 1.3 10, problem with gunzip.exe

[Robert Collins]

> -----Original Message-----
> From: Larry Hall (RFK Partners, Inc) [mailto:lhall@rfk.com] 
> Sent: Tuesday, May 21, 2002 3:24 AM

>    2. I believe setup.exe creates symbolic links as if 
> "nowinsymlinks" is 
>       set.  So setup would create the symbolic links as 
> Cygwin symlinks 
>       rather than Windows shortcuts regardless of the setting in the 
>       CYGWIN environment variable.

2 is wrong.

> I think that covers it.  Someone will tell me if (2) is wrong. :-)

Cheers,
Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: version 1.3 10, problem with gunzip.exe

[Larry Hall (RFK Partners, Inc)]

At 01:13 PM 5/20/2002, Larry Hall (RFK Partners, Inc) wrote:
>At 12:53 PM 5/20/2002, Donszelmann, Mark wrote:
> >Version 1.3.10 net installation of cygwin seems to have the following problem:
> >
> >gunzip.exe seems to be only 19 bytes long and does not run.
>
>
>It's a symbolic link and you apparently have "nowinsymlinks" in your 
>CYGWIN environment variable.  You either need to unset that and recreate 
>the symbolic links (and others referring to executables on your system) or
>always run these from a shell like bash that understands Cygwin symbolic 
>links (not windows shortcuts).


Actually, this may be overstating the case a tad:

   1. The above is true if "nowinsymlinks" is set.

   2. I believe setup.exe creates symbolic links as if "nowinsymlinks" is 
      set.  So setup would create the symbolic links as Cygwin symlinks 
      rather than Windows shortcuts regardless of the setting in the 
      CYGWIN environment variable.

   3. Running gunzip from a non-Cygwin aware shell (like cmd.exe or
      command.com) would require specifying the name of the symlink recreated
      as a shortcut.  In this case, that means "gunzip.exe.lnk".

I think that covers it.  Someone will tell me if (2) is wrong. :-)



Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: version 1.3 10, problem with gunzip.exe

[Larry Hall (RFK Partners, Inc)]

At 12:53 PM 5/20/2002, Donszelmann, Mark wrote:
>Version 1.3.10 net installation of cygwin seems to have the following problem:
>
>gunzip.exe seems to be only 19 bytes long and does not run.


It's a symbolic link and you apparently have "nowinsymlinks" in your 
CYGWIN environment variable.  You either need to unset that and recreate 
the symbolic links (and others referring to executables on your system) or
always run these from a shell like bash that understands Cygwin symbolic 
links (not windows shortcuts).


Larry Hall                              lhall@rfk.com
RFK Partners, Inc.                      http://www.rfk.com
838 Washington Street                   (508) 893-9779 - RFK Office
Holliston, MA 01746                     (508) 893-9889 - FAX


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: version 1.3 10, problem with gunzip.exe

[Randall R Schulz]

Mark,

This is how these things are set up on a properly installed Cygwin:

% ll $( type -p -a gunzip )
lrwxrwxrwx    1 Administ None           19 Nov 26 09:04 /bin/gunzip -> 
gzip.exe*
lrwxrwxrwx    1 Administ None           19 Nov 26 09:04 /usr/bin/gunzip -> 
gzip.exe*

% ll $( type -p -a gzip )
-rwxrwxrwx    1 Administ None        50176 Nov 25 17:48 /bin/gzip*
-rwxrwxrwx    1 Administ None        50176 Nov 25 17:48 /usr/bin/gzip*

% ll /{usr/,}bin/gzip.exe
-rwxrwxrwx    1 Administ None        50176 Nov 25 17:48 /bin/gzip.exe*
-rwxrwxrwx    1 Administ None        50176 Nov 25 17:48 /usr/bin/gzip.exe*


Your nineteen byte "gunzip" file is a symlink, or should be.

Randall Schulz
Mountain View, CA USA


At 09:53 2002-05-20, Donszelmann, Mark wrote:
>Version 1.3.10 net installation of cygwin seems to have the following problem:
>
>gunzip.exe seems to be only 19 bytes long and does not run.
>
>Regards
>Mark Donszelmann


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: version 1.3 10, problem with gunzip.exe

[Christopher Faylor]

On Mon, May 20, 2002 at 12:07:25PM -0500, Keen Wayne A Contr AFRL/MNGG wrote:
>Mine is listed as that length using ls -l, and it does run (successfully -
>never take that
>for granted).
>
>I am running 1.3.10, updated this morning.

gunzip.exe is a symbolic link.  So, it must be run from a bash shell.

19 bytes is the correct length.

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: version 1.3 10, problem with gunzip.exe

[Charles Wilson]

Donszelmann, Mark wrote:

> Version 1.3.10 net installation of cygwin seems to have the following problem:
> 
> gunzip.exe seems to be only 19 bytes long and does not run.


It's a symbolic link to gzip.exe.  So, it works under cygwin (e.g. 
within a bash shell) but not from Explorer or from a plain DOS box.

--Chuck




--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: version 1.3 10, problem with gunzip.exe

[Keen Wayne A Contr AFRL/MNGG]

Mine is listed as that length using ls -l, and it does run (successfully -
never take that
for granted).

I am running 1.3.10, updated this morning.

Wayne Keen

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

version 1.3 10, problem with gunzip.exe

[Donszelmann, Mark]

Version 1.3.10 net installation of cygwin seems to have the following problem:

gunzip.exe seems to be only 19 bytes long and does not run.

Regards
Mark Donszelmann

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/