RE: What kind of executable is zcat? Crashes from cmd.exe
Larry Hall writes: Bakken, Luke writes: $ ls -l zcat* lrwxrwxrwx1 lukebUsers 19 Sep 21 16:29 zcat.exe - gzip.exe $ rm zcat.exe $ ln gzip.exe zcat.exe Thanks, Luke, now I can use zcat from the Windows command line. Sure, that's another option but one that eats up disk space if your partition isn't formatted for NTFS. Replacing ln with ln -s in your examples above will get you Windows shortcuts which you can use at the command prompt directly, so long as you don't mind typing .lnk at the end of each linked executable. This assumes you haven't added nowinsymlinks to your CYGWIN environment variable of course. This approach will save the disk space on non-NTFS partitions. I really think it's worth a few bytes of disk space (even then only on non-NTFS partitions) to have zcat work out of the box in the Windows Command Prompt. That definitely seems like a much better option to having zcat crash or having to type zcat.lnk, right? Should I file an enhancement request? Thanks, Jamshid -- 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/
RE: What kind of executable is zcat? Crashes from cmd.exe
At 06:27 PM 2/13/2004, [EMAIL PROTECTED] you wrote: Larry Hall writes: Bakken, Luke writes: $ ls -l zcat* lrwxrwxrwx1 lukebUsers 19 Sep 21 16:29 zcat.exe - gzip.exe $ rm zcat.exe $ ln gzip.exe zcat.exe Thanks, Luke, now I can use zcat from the Windows command line. Sure, that's another option but one that eats up disk space if your partition isn't formatted for NTFS. Replacing ln with ln -s in your examples above will get you Windows shortcuts which you can use at the command prompt directly, so long as you don't mind typing .lnk at the end of each linked executable. This assumes you haven't added nowinsymlinks to your CYGWIN environment variable of course. This approach will save the disk space on non-NTFS partitions. I really think it's worth a few bytes of disk space (even then only on non-NTFS partitions) to have zcat work out of the box in the Windows Command Prompt. OK, if you can get everyone that uses Cygwin on non-NTFS partitions to agree to have all the currently linked programs become copies instead, let the list know. ;-) That definitely seems like a much better option to having zcat crash or having to type zcat.lnk, right? Depends on your point of view, I guess. The Cygwin lot can be a fickle bunch. Actually, what's been discussed before is to move in the direction of Windows shortcuts, which you poo-poo above too. Should I file an enhancement request? Nah. It's a known issue so you'd just be covering the same ground again. Clearly, it's not a high-priority for anyone since the issue has been known for a while. If you really are interested in seeing some kind of change here, a patch to setup might stir-up some action (or further discussion). -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
What kind of executable is zcat? Crashes from cmd.exe
I just installed Cygwin. What kind of executable is zcat.exe? It doesn't show up when I dir c:\cygwin\bin\zc* (only zcmp), but I see it's 19 bytes in Explorer. It works fine within bash, but I want UNIX utilities I can use in the regular Windows Command Prompt. Thanks, Jamshid Afshar [EMAIL PROTECTED] -- 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/
Re: What kind of executable is zcat? Crashes from cmd.exe
Jamshid Afshar wrote: I just installed Cygwin. What kind of executable is zcat.exe? It doesn't show up when I dir c:\cygwin\bin\zc* (only zcmp), but I see it's 19 bytes in Explorer. It works fine within bash, but I want UNIX utilities I can use in the regular Windows Command Prompt. $ ls -l zcat.exe lrwxrwxrwx1 rcampbel Users 19 Jan 6 17:06 zcat.exe - gzip.exe As you can see from the ls output, it's a symbolic link (doesn't work in cmd). You can still call gunzip -c (or whatever). -- 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/
RE: What kind of executable is zcat? Crashes from cmd.exe
Jamshid Afshar wrote: I just installed Cygwin. What kind of executable is zcat.exe? It doesn't show up when I dir c:\cygwin\bin\zc* (only zcmp), but I see it's 19 bytes in Explorer. It works fine within bash, but I want UNIX utilities I can use in the regular Windows Command Prompt. $ ls -l zcat.exe lrwxrwxrwx1 rcampbel Users 19 Jan 6 17:06 zcat.exe - gzip.exe As you can see from the ls output, it's a symbolic link (doesn't work in cmd). You can still call gunzip -c (or whatever). I had a similar problem when trying to use gunzip from a cmd prompt outside of a cygwin shell - I was getting illegal ntvdm CPU errors. The fix is to replace the softlink with a hard link: $ cd /bin /bin $ ls -l zcat* lrwxrwxrwx1 lukebUsers 19 Sep 21 16:29 zcat.exe - gzip.exe /bin $ rm zcat.exe /bin $ ln gzip.exe zcat.exe /bin $ ls -li zcat* gzip* gunzip* 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 gunzip.exe 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 gzip.exe 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 zcat.exe I would suggest doing the same with any other cygwin executable that is a symbolic link that you intend to use outside cygwin. -- 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/
RE: What kind of executable is zcat? Crashes from cmd.exe
At 03:22 PM 2/12/2004, Bakken, Luke you wrote: Jamshid Afshar wrote: I just installed Cygwin. What kind of executable is zcat.exe? It doesn't show up when I dir c:\cygwin\bin\zc* (only zcmp), but I see it's 19 bytes in Explorer. It works fine within bash, but I want UNIX utilities I can use in the regular Windows Command Prompt. $ ls -l zcat.exe lrwxrwxrwx1 rcampbel Users 19 Jan 6 17:06 zcat.exe - gzip.exe As you can see from the ls output, it's a symbolic link (doesn't work in cmd). You can still call gunzip -c (or whatever). I had a similar problem when trying to use gunzip from a cmd prompt outside of a cygwin shell - I was getting illegal ntvdm CPU errors. The fix is to replace the softlink with a hard link: $ cd /bin /bin $ ls -l zcat* lrwxrwxrwx1 lukebUsers 19 Sep 21 16:29 zcat.exe - gzip.exe /bin $ rm zcat.exe /bin $ ln gzip.exe zcat.exe /bin $ ls -li zcat* gzip* gunzip* 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 gunzip.exe 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 gzip.exe 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 zcat.exe I would suggest doing the same with any other cygwin executable that is a symbolic link that you intend to use outside cygwin. Sure, that's another option but one that eats up disk space if your partition isn't formatted for NTFS. Replacing ln with ln -s in your examples above will get you Windows shortcuts which you can use at the command prompt directly, so long as you don't mind typing .lnk at the end of each linked executable. This assumes you haven't added nowinsymlinks to your CYGWIN environment variable of course. This approach will save the disk space on non-NTFS partitions. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 838 Washington Street (508) 893-9889 - FAX Holliston, MA 01746 -- 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/
RE: What kind of executable is zcat? Crashes from cmd.exe
At 03:22 PM 2/12/2004, Bakken, Luke you wrote: Jamshid Afshar wrote: I just installed Cygwin. What kind of executable is zcat.exe? It doesn't show up when I dir c:\cygwin\bin\zc* (only zcmp), but I see it's 19 bytes in Explorer. It works fine within bash, but I want UNIX utilities I can use in the regular Windows Command Prompt. $ ls -l zcat.exe lrwxrwxrwx1 rcampbel Users 19 Jan 6 17:06 zcat.exe - gzip.exe As you can see from the ls output, it's a symbolic link (doesn't work in cmd). You can still call gunzip -c (or whatever). I had a similar problem when trying to use gunzip from a cmd prompt outside of a cygwin shell - I was getting illegal ntvdm CPU errors. The fix is to replace the softlink with a hard link: $ cd /bin /bin $ ls -l zcat* lrwxrwxrwx1 lukebUsers 19 Sep 21 16:29 zcat.exe - gzip.exe /bin $ rm zcat.exe /bin $ ln gzip.exe zcat.exe /bin $ ls -li zcat* gzip* gunzip* 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 gunzip.exe 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 gzip.exe 1125899906888251 -rwxr-xr-x+ 3 lukebUsers 62976 Jul 23 2003 zcat.exe I would suggest doing the same with any other cygwin executable that is a symbolic link that you intend to use outside cygwin. Sure, that's another option but one that eats up disk space if your partition isn't formatted for NTFS. Replacing ln with ln -s in your examples above will get you Windows shortcuts which you can use at the command prompt directly, so long as you don't mind typing .lnk at the end of each linked executable. This assumes you haven't added nowinsymlinks to your CYGWIN environment variable of course. This approach will save the disk space on non-NTFS partitions. One other caveat I have found with using hard links (on an NTFS partition) involves upgrades. I changed the symlink for ksh.exe - pdksh.exe to a hard link. When an new version of pdksh was installed, it resulted in two non linked files. I had the new version as psksh.exe and the old version as ksh.exe. Ross -- 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/
Re: What kind of executable is zcat? Crashes from cmd.exe
On Thu, Feb 12, 2004 at 03:46:44PM -0600, Ross Boulet wrote: One other caveat I have found with using hard links (on an NTFS partition) involves upgrades. I changed the symlink for ksh.exe - pdksh.exe to a hard link. When an new version of pdksh was installed, it resulted in two non linked files. I had the new version as psksh.exe and the old version as ksh.exe. Huh. I wonder why that happened. I would expect setup.exe to just overwrite one file, resulting in the change being reflected in the linked copy. I'm no longer familiar enough with setup's internals to say for sure if that is what happening but it does appear that the file is being deleted. That behavior could probably be changed with an appropriate PTC. cgf -- 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/
Re: What kind of executable is zcat? Crashes from cmd.exe
On Thu, 12 Feb 2004, Christopher Faylor wrote: On Thu, Feb 12, 2004 at 03:46:44PM -0600, Ross Boulet wrote: One other caveat I have found with using hard links (on an NTFS partition) involves upgrades. I changed the symlink for ksh.exe - pdksh.exe to a hard link. When an new version of pdksh was installed, it resulted in two non linked files. I had the new version as psksh.exe and the old version as ksh.exe. Huh. I wonder why that happened. I would expect setup.exe to just overwrite one file, resulting in the change being reflected in the linked copy. I'm no longer familiar enough with setup's internals to say for sure if that is what happening but it does appear that the file is being deleted. That behavior could probably be changed with an appropriate PTC. cgf AFAIK, setup has always behaved this way. It first uninstalls the old versions of all packages being upgraded (that's how the old pdksh.exe got unlinked), and then installs the new versions (creating new files, essentially). It never did overwrite the file in-place. Changing this will probably involve radical modifications to setup's internal logic. Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,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/
Re: What kind of executable is zcat? Crashes from cmd.exe
On Thu, Feb 12, 2004 at 05:05:30PM -0500, Igor Pechtchanski wrote: On Thu, 12 Feb 2004, Christopher Faylor wrote: On Thu, Feb 12, 2004 at 03:46:44PM -0600, Ross Boulet wrote: One other caveat I have found with using hard links (on an NTFS partition) involves upgrades. I changed the symlink for ksh.exe - pdksh.exe to a hard link. When an new version of pdksh was installed, it resulted in two non linked files. I had the new version as psksh.exe and the old version as ksh.exe. Huh. I wonder why that happened. I would expect setup.exe to just overwrite one file, resulting in the change being reflected in the linked copy. I'm no longer familiar enough with setup's internals to say for sure if that is what happening but it does appear that the file is being deleted. That behavior could probably be changed with an appropriate PTC. AFAIK, setup has always behaved this way. It first uninstalls the old versions of all packages being upgraded (that's how the old pdksh.exe got unlinked), and then installs the new versions (creating new files, essentially). It never did overwrite the file in-place. Changing this will probably involve radical modifications to setup's internal logic. Duh. Right. It deletes everything first. I knew that. Sorry for the noise. cgf -- 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/
Re: What kind of executable is zcat? Crashes from cmd.exe
On Fri, 2004-02-13 at 08:59, Christopher Faylor wrote: On Thu, Feb 12, 2004 at 03:46:44PM -0600, Ross Boulet wrote: One other caveat I have found with using hard links (on an NTFS partition) involves upgrades. I changed the symlink for ksh.exe - pdksh.exe to a hard link. When an new version of pdksh was installed, it resulted in two non linked files. I had the new version as psksh.exe and the old version as ksh.exe. Huh. I wonder why that happened. I would expect setup.exe to just overwrite one file, resulting in the change being reflected in the linked copy. I'm no longer familiar enough with setup's internals to say for sure if that is what happening but it does appear that the file is being deleted. That behavior could probably be changed with an appropriate PTC. Uninstall + install is the setup process. To fix it is possible... but not trivial. Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
Re: What kind of executable is zcat? Crashes from cmd.exe
On Fri, 2004-02-13 at 09:05, Igor Pechtchanski wrote: AFAIK, setup has always behaved this way. It first uninstalls the old versions of all packages being upgraded (that's how the old pdksh.exe got unlinked), and then installs the new versions (creating new files, essentially). It never did overwrite the file in-place. Changing this will probably involve radical modifications to setup's internal logic. Not that big a change actually - we already have the concept of upgrading internally, it just needs to be taught that an upgrade isn't an uninstall + install, but rather an unpack followed by removing files no longer present in the package. Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. signature.asc Description: This is a digitally signed message part
Re: What kind of executable is zcat? Crashes from cmd.exe
On Fri, Feb 13, 2004 at 09:14:57AM +1100, Robert Collins wrote: On Fri, 2004-02-13 at 09:05, Igor Pechtchanski wrote: AFAIK, setup has always behaved this way. It first uninstalls the old versions of all packages being upgraded (that's how the old pdksh.exe got unlinked), and then installs the new versions (creating new files, essentially). It never did overwrite the file in-place. Changing this will probably involve radical modifications to setup's internal logic. Not that big a change actually - we already have the concept of upgrading internally, it just needs to be taught that an upgrade isn't an uninstall + install, but rather an unpack followed by removing files no longer present in the package. Another nice change would be to make setup's tar understand hard links. I think it treats them as a copy now, doesn't it? cgf -- 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/
RE: What kind of executable is zcat? Crashes from cmd.exe
A suggestion for another setup feature: When upgrading package foo requires reinstallation of package bar afterwards, figuring that out and then doing it. Thanks for all the good work. - Barry -Original Message- From: Robert Collins [mailto:[EMAIL PROTECTED] Sent: Thursday, February 12, 2004 5:15 PM To: [EMAIL PROTECTED] Subject: Re: What kind of executable is zcat? Crashes from cmd.exe On Fri, 2004-02-13 at 09:05, Igor Pechtchanski wrote: AFAIK, setup has always behaved this way. It first uninstalls the old versions of all packages being upgraded (that's how the old pdksh.exe got unlinked), and then installs the new versions (creating new files, essentially). It never did overwrite the file in-place. Changing this will probably involve radical modifications to setup's internal logic. Not that big a change actually - we already have the concept of upgrading internally, it just needs to be taught that an upgrade isn't an uninstall + install, but rather an unpack followed by removing files no longer present in the package. Rob -- GPG key available at: http://www.robertcollins.net/keys.txt. -- 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/
