This is the mail archive of the
mailing list for the Cygwin project.
Re: Use the native Symlinks.
- To: "Henry J. Cobb" <hcobb at telegenisys dot com>
- Subject: Re: Use the native Symlinks.
- From: Jeff Sturm <jsturm at sigma6 dot com>
- Date: Mon, 24 Aug 1998 13:39:12 -0400
- CC: gnu-win32 at cygnus dot com
- References: <35E04A22.firstname.lastname@example.org>
OK, shortcuts do store a path, plus a lot of other garbage. I don't see
why they couldn't represent symbolic links. Windows seems to identify
them by the ".lnk" suffix. But what are the win32 API calls to create
and read a shortcut?
You wouldn't need to modify LN.EXE since it invokes symlink() from
cygwinb19.dll. Perhaps symlink behavior could be controlled by an
Henry J. Cobb wrote:
> Why add the concepts of hard and soft links to an operating system that
> has soft links? (And that's all you need really, if you drop the flawed
> concept that
> the "operating environment" can hide the true line end markers.)
> What symbolic links on eNp-Ty? They're called shortcuts here.
> Simply tune the DLL to parse whatever.lnk files and treat them the same
> as Posixstan
> symbolic links and change the LN.EXE program to create shortcuts.
> The result is a "filesystem tree" that's browsable from both the GNU and
> eNp-Ty sides.
For help on using this list (especially unsubscribing), send a message to
"email@example.com" with one line of text: "help".