UWIN does symlinks by creating Windows shortcut files. During file traversal 
when a shortcut file is detected, and symlinks are followed, the code restarts 
the path search with the file named in the shortcut.

Windows Vista used a different method by addition of an attribute flag to 
indicate to reparse filenames from some information embedded in the file. 

UNIX symlinks are files with a special bit indicating it is a symbolic link. 
The file contents of the symbolic link are the name of the actual file the 
symbolic link points to. During filename processing when a symbolic link is 
detected and they are to be followed, the kernel reads the file contents and 
restarts the pathname traversal.

I don't know about NFSv4 referral points, but it probably is a special file 
mode whose file contents or meta data contain the name of the actual referred 
to file.

Jeff Fellin

-----Original Message-----
From: [email protected] 
[mailto:[email protected]] On Behalf Of ????? ????????????
Sent: Friday, August 24, 2012 16:50
To: FOWLER, GLENN S (GLENN S)
Cc: [email protected]
Subject: Windows symlink and NFSv4 referrals points (was: Re: [uwin-users] 
Problem with rm'ing a Vista symbolic link)

Glenn, can you explain how UWIN does symlinks, and how they differ from Windows 
Vista symlinks, and how these differ from traditional UNIX symlinks and NFSv4 
referral points
(http://tools.ietf.org/html/draft-ietf-nfsv4-referrals-00 , 
http://docs.oracle.com/cd/E19963-01/html/821-1454/gjuaj.html)?

Olga

On Fri, Aug 24, 2012 at 10:03 PM, Glenn Fowler <[email protected]> wrote:
>
> correction
> I logged in again and was able to reproduce the problem bit from 32 
> and 64 bit ksh+rm
>
> with a little more digging dgk & jkf found the problem it has to do 
> with DeleteFile() and an interaction between FILE_FLAG_DELETE_ON_CLOSE 
> and win32 symlinks we'll post something monday
>
> thanks
>
> On Fri, 24 Aug 2012 10:13:29 -0700 Jon Pile wrote:
>> On Fri, Aug 24, 2012 at 7:00 AM, Glenn Fowler <[email protected]> wrote:
>> >
>> > I haven't been able to reproduce the problem what is the ouput of
>> >
>> >         uname -a
>> >         rm --?-version
>
>> Well, that's good news. I guess I should bump to the2012- 08-06 
>> release - hadn't noticed that was out.
>
>> $ uname -a
>> UWIN-W7 jpile-w510 5.0/6.1 2012-02-29 i686-64 x64 64/64 UWIN $ rm --? 
>> -version
>>   version         rm (AT&T Research) 2012-02-14
>
>> -jP
>
> _______________________________________________
> uwin-users mailing list
> [email protected]
> https://mailman.research.att.com/mailman/listinfo/uwin-users



-- 
      ,   _                                    _   ,
     { \/`o;====-    Olga Kryzhanovska   -====;o`\/ }
.----'-/`-/     [email protected]   \-`\-'----.
 `'-..-| /       http://twitter.com/fleyta     \ |-..-'`
      /\/\     Solaris/BSD//C/C++ programmer   /\/\
      `--`                                      `--`
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users

_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users

Reply via email to