> D. C. Sessions wrote on Friday 18 April 2003 10:52 in message
>>>> linuxfux said something about Symbolic-link??:
>>>>> does such thing exist in xp???
>> Maybe, but every time someone asks you how to create
>> one you suddenly drop out of the thread.
> Symlinks are supported by NTFS-5 and you can create them with third-party
> software like the MKS Toolkit, so they say. I don't know if it works in MKS
> like in Cygwin, as it's been at least five years since I've dealt with MKS.
> In Cygwin,
> "ln -s" actually creates a Windows shortcut, which isn't the same (for
> one thing, you have to append ".lnk" to the filename if you want to
> access it with scripts. It's pretty pointless to use it for "symlinks".
> However, "ln" does create a hard link to a file. The hardlinks do
> work, both when you're in Cygwin and for Windows applications once the
> links are created. There are some other utilities that do hard links
> on Windows; search Google for "'hard link' Windows"
> Cygwin's "ls" utility does NOT create symlinks to directories, but
> shortcuts. These are practically worthless, as they can't be used by
> typing or pasting their names in file dialogs. Instead it's
> click...click...click. Hardlinks are not allowed for directories, so
> using ls on dirs isn't worth the effort.
> However, there's a utility called Junction on Sysinternals.com that lets
> you create symlinks to directories (but not files). They appear to be
> proper symlinks and works across volumes and works for GUI apps and at the
> command line. However, XP's Explorer apparently doesn't know anything about
> symlinks, so you'll have to use Junction at the command line if you want to
> identify and manage them. It's useful enough that I'm using Junction to
> replace the shortcuts to other volumes that were in my "My Documents"
> partition (yes, I use an entire partition for that).
> Cygwin and Junction together give you much of what you get on Unix.
So, to sum up: MSWindows has limited hard-link capability, in that it
can inode files (handy for message queueing) but not directories, which
is a key use for them (in my experience more than half, but YMMV)
In addition, there are workarounds which depend on the application
and thus are likely to be more trouble than help, at least one of which
works only for directories but not files.
In none of these cases is there a way to actually create symbolic
linkages at the OS/filesystem level, and the hard linkages which
*are* at the OS/filesystem level aren't orthogonal.
Does that sum it up adequately?
| In the course of every project there comes a time |
| when the best de* is a can of gasoline. |