I haven't been able to reproduce the problem
what is the ouput of
uname -a
rm --?-version
On Thu, 23 Aug 2012 16:06:25 -0700 Jon Pile wrote:
> On Thu, Aug 23, 2012 at 3:52 PM, Glenn Fowler <[email protected]> wrote:
> > just to make sure we debug the same entity
> > can you show how the vista symlink was created
> > (win32 call or ms shell or ??)
> Good question! A quick experiment shows the same results whether the
> link is created with the win32 "CreateSymbolicLink" call, or the MS
> console "mklink" builtin...
> K:\tmp>mklink newlink src\target
> symbolic link created for newlink <<===>> src\target
> # back to ksh...
> $ ls -l newlink src/target
> lrwx------ 1 Administrators Domain+Users 7 Aug 23 15:58
> newlink -> /K/tmp/src/target
> -rw-r--r-- 1 jpile Domain+Users 12 Aug 23 15:58 src/target
> $ rm newlink
> $ ls -l newlink src/target
> ls: src/target: not found
> lrwx------ 1 Administrators Domain+Users 7 Aug 23 15:55
> newlink -> /K/tmp/newlink
> Same results when the link is created with a small program I have here:
> $ touch src/target2
> $ symlink src/target2 cpplink
> $ ls -l cpplink src/target2
> l--------- 1 jpile Domain+Users 7 Aug 23 16:01 cpplink ->
> /K/tmp/src/target2
> -rw-r--r-- 1 jpile Domain+Users 9 Aug 23 16:01 src/target2
> $ rm cpplink
> $ ls -l cpplink src/target2
> ls: src/target2: not found
> l--------- 1 jpile Domain+Users 7 Aug 23 16:01 cpplink ->
> /K/tmp/cpplink
> Oh, a little detail just in case it saves you some time (it really
> messed up my day yesterday). If the target you pass to
> CreateSymbolicLink uses '/' as the path separator, it claims success
> but creates a bogus symlink. Wonderful! (The symlink tool above does
> slash-swapping accordingly).
> -jP
_______________________________________________
uwin-users mailing list
[email protected]
https://mailman.research.att.com/mailman/listinfo/uwin-users
