From: jsturm AT sigma6 DOT com (Jeff Sturm) Subject: Re: Use the native Symlinks. 26 Aug 1998 11:12:26 -0700 Message-ID: <35E1A540.7E2069FC.cygnus.gnu-win32@sigma6.com> References: <35E04A22 DOT 6971 AT telegenisys DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Henry J. Cobb" Cc: gnu-win32 AT cygnus DOT com 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 environment variable. Henry J. Cobb wrote: > > Why add the concepts of hard and soft links to an operating system that > already > 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. -- Jeff Sturm jsturm AT sigma6 DOT com - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".