Re: New daily builds: Links 'R Us
"Douglas E. Engert" <[email protected]>
| Newsgroups | gmane.comp.file-systems.openafs.devel.win32 |
|---|---|
| Message-ID | <[email protected]> |
What might be nice, is add a show symlink to the Explore AFS shell. or beter still AFS properties that could list symlinks, hardlinks, mount points etc. I see the symlink list -name file can show symlinks. Jeffrey Altman wrote: > I have uploaded new daily builds to their usual location: > > /afs/athena.mit.edu/user/j/a/jaltman/Public/OpenAFS/ > \\afs\athena.mit.edu\user\j\a\jaltman\Public\OpenAFS\ > http://web.mit.edu/~jaltman/Public/OpenAFS/ > > The list of changes since 1.3.71 include: > > * smb_ReceiveCoreRename() was factored to produce smb_Rename() > which is used by both the original function and the new > smb_ReceiveNTRename(). smb_ReceiveNTRename() supports the > creation of HardLinks in addition to Renaming. smb_Link() > is a new function which creates HardLinks via cm_Link(). > cm_Link() is a new vnodeops function which creates links > using RXAFS_Link(). > > smb_ReceiveNTRename() does not support the File Copy and > Move Cluster Information operations described in its interface. > ReceiveNTRename is under documented in CIFS-TR-1p00_FINAL.pdf. > > * When opening files via symlinks, we should follow the symlinks > until we reach the actual file stat cache entry. The stat cache > entry of the file should then be stored in the FID instead of > stat scache entry of the symlink. > > * return bad operation errors for all unimplemented functions > even if we do not know the functions exist. > > * Log bad packets and unknown operation packets to the trace log > > * Map CM_ERROR_BADOP to STATUS_NOT_SUPPORTED instead of > 0xC09820FF > > * Update list of known CIFS operations to include all those listed > in CIFS-TR-1p00_FINAL.pdf. > > > You can create Hard Links in AFS using JPSoft's 4NT.EXE built-in > command: MKLNK <source> <link>. If you are not currently using 4NT.EXE > I strongly recommend it. http://www.jpsoft.com/. > > Softlinks can be created and removed using the softlink.exe tool which > is part of the OpenAFS distribution or the Explorer Shell AFS menu. > > Does anyone believe that a "Create Hardlink ..." menu item should be > added to the Explorer Shell AFS menu? I noticed that Windows provides > absolutely no UI for the creation of hard links even though it is > supported by the base Win32 File APIs. > > There will soon be a 1.3.72 release issued primarily for Unix. Even > though there is no pressing reason to issue a new build for Windows I > will package one just in case people want to have support for hard and > soft links. > > Jeffrey Altman > > -- Douglas E. Engert <[email protected]> Argonne National Laboratory 9700 South Cass Avenue Argonne, Illinois 60439 (630) 252-5444