public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Robert Collins" <robert.collins@syncretize.net>
To: <cygwin@cygwin.com>, "Randall R Schulz" <rrschulz@cris.com>
Subject: Re: gzip.exe as symlink breaks NTEmacs's jka-compr.el
Date: Tue, 16 Jul 2002 23:42:00 -0000	[thread overview]
Message-ID: <006701c22d3f$d6b486e0$d500a8c0@study2> (raw)
In-Reply-To: <5.1.0.14.2.20020716193950.03031af8@pop3.cris.com>


----- Original Message -----
From: "Randall R Schulz" <rrschulz@cris.com>
To: "Robert Collins" <robert.collins@syncretize.net>; <cygwin@cygwin.com>

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

Huh? Cygwin1.dll doesn't make a copy on FAT - it fails as you have just
noted.. Setup.exe's cygfile:// handler makes copies.

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/

  reply	other threads:[~2002-07-17  3:12 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-15  2:20 Matt Swift
2002-07-15  2:26 ` Robert Collins
2002-07-15  5:36   ` gzip.exe as symlink Max Bowsher
2002-07-15  5:38     ` Robert Collins
2002-07-15 12:41       ` Jon Cast
2002-07-15 14:47         ` Nicholas Wourms
2002-07-15 15:57         ` Robert Collins
2002-07-15 22:22       ` Max Bowsher
2002-07-15  9:21     ` Dario Alcocer
2002-07-15 12:02   ` gzip.exe as symlink breaks NTEmacs's jka-compr.el Jon Cast
2002-07-15 17:05   ` Gerrit P. Haase
2002-07-16  8:59   ` Matt Swift
2002-07-16  9:14     ` David Starks-Browning
2002-07-16  9:17       ` Nicholas Wourms
2002-07-16 10:21     ` Randall R Schulz
2002-07-16 19:27       ` Jon Cast
2002-07-16 19:43         ` Randall R Schulz
2002-07-16 19:51           ` Jon Cast
2002-07-16 20:12             ` Randall R Schulz
2002-07-16 20:14               ` Robert Collins
2002-07-16 23:05                 ` Randall R Schulz
2002-07-16 23:42                   ` Robert Collins [this message]
2002-07-17  0:53                     ` Randall R Schulz
2002-07-17  0:58                     ` Christopher Faylor
2002-07-17  0:59                       ` Robert Collins
2002-07-16 20:36               ` Jon Cast
2002-07-16 23:54                 ` Randall R Schulz
2002-07-18 17:08                   ` Jon Cast
2002-07-16 19:49         ` Nicholas Wourms
2002-07-16 19:52           ` Jon Cast
2002-07-15 15:46 gzip.exe as symlink Robinow, David
2002-07-15 15:48 ` Nicholas Wourms
2002-07-16 18:51   ` Jon Cast
2002-07-16 18:50 files and directories distinction: Aldi Kraja
2002-07-16 19:34 ` Randall R Schulz
2002-07-16 19:37   ` Jon Cast
     [not found] <rrschulz@cris.com>
2003-03-29  4:00 ` Mozilla 1.3 built on cygwin? Jeff.Hodges

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='006701c22d3f$d6b486e0$d500a8c0@study2' \
    --to=robert.collins@syncretize.net \
    --cc=cygwin@cygwin.com \
    --cc=rrschulz@cris.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).