On Sun, 2002-06-09 at 15:49, Thunder from the hill wrote:
> Hi,
>
> On 9 Jun 2002, Nicholas Miell wrote:
> > Note that there's nothing stopping you from unpacking the tarball in
> > cygwin, with it's own (nicely contained, and not nearly as ugly) symlink
> > hack.
>
> That's a hack in the cygwin libc, isn't it? It's the lib which opens
> another file instead of the original, isn't it?
Yeah, and it uses the native IShellLink COM interface to do it, which
guarantees future (Windows) compatibility. Misusing the comment field to
store the path is a bit questionable, though.
Actually, if people are so hell-bent on making symlinks work on VFAT,
I'd suggest that they make a LD_PRELOAD'd shared library that intercepts
the open, lstat, symlink, etc. calls and Does The Right Thing on VFAT
filesystems. Much cleaner than putting it in the kernel or in all the
apps that might be used on a VFAT filesystem.
> I think VFAT is really the only real flexible transport fs for
> linux->windows.
Yeah, I'd agree with that (until NTFS can do writing, anyway). I was
just pointing out that there are lots of filesystems that Windows can
use, not just VFAT.
- Nicholas
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Jun 15 2002 - 22:00:15 EST