gzip.exe as symlink breaks NTEmacs's jka-compr.el
Randall R Schulz
rrschulz@cris.com
Tue Jul 16 23:05:00 GMT 2002
Rob,
At 19:33 2002-07-16, you wrote:
>----- Original Message -----
>From: "Randall R Schulz" <rrschulz@cris.com>
>To: "Jon Cast" <jcast@ou.edu>
>
> > I know that if one just uses the "ln" command (no "-s" option) on a FAT
> > volume you get a copy. If Cygwin packages used hard links for program
> > aliases (does the TAR format support hard links?) and Setup.exe was given
> > the same smarts as the "ln" command, you'd get space-wasting copies on FAT
> > volumes and fast, space-efficient hard links on NTFS.
>
>It's not the ln smarts that are needed, its the cygwin1.dll hard link
>smarts. I'd happily accept a patch to the cygfile:// handler in setup to
>perform hard links rather thank copies. Of course, the package maintainers
>will suddenly all need to build on NTFS as well, and with hardlinks to boot,
>before anything changes.
It occurred to me that Cygwin1.dll might be making the copy on FAT file
systems, but that didn't seem to make much sense, since the "hard link
fails on FAT" case seems awfully close to the "cross-dev link fails" case
that a conventional Unix "ln" already has to deal with.
"Real Users Use NTFS" (sm)
>Rob
Randall Schulz
Mountain View, CA USA
--
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/
More information about the Cygwin
mailing list