Greg Ercolano wrote:
> When I recover from shock, I'll do some more tests within Rush.
Wow, yeah, Vista's symlinks to UNC network drives works
inside Rush too.
This is pretty cool.. it means you can finally use regular
pathnames to your file server, without the double leading slash,
and without being locked to hostnames in paths.
It also means that if a server dies, you can change the symlinks
to point to a different server, just like unix.
Pardon me while I have a heart attack.
And holy crap, in DOS you can even 'CD' to the symlink, and
end up with your server as the 'current directory'. In the past,
this was impossible (*); DOS wouldn't let you CD to a UNC path, it
had to be a drive map. But DOS has no trouble following a symlink
to a UNC path. So this kinda obsoletes drive letters, and all that
weird baggage they imply.
BTW, in a directory listing, the symlink shows up displayed
in a reasonable manner as well:
C:\>dir c:\ | findstr jobs
05/29/2007 10:07 PM <SYMLINKD> jobs [\\tahoe\jobs]
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Be sure to use RMDIR to remove a symlink created with MKLINK /D.
Do NOT use 'DEL'.. it tries to *follow* the symlink, and delete
the files on the server. This behavior is unlike rm(1) in unix.
So symlinks in Windows.. apparently hell has frozen over.
I need a drink.
(*) There's actually a registry tweak that allows a UNC path to be
the current working directory in DOS:
http://support.microsoft.com/kb/156276
Allow UNC paths at command prompt
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Command Processor]
"DisableUNCCheck"=dword:00000001
|