[OpenAFS] when openafs becomes a windows IFS
Fri, 5 Sep 2008 07:36:30 +0300
Thanks for looking in this.
Too bad it's not that useful after all (except for debugging maybe).
From: Jeffrey Altman [email@example.com]
Sent: Friday, September 05, 2008 7:22 AM
Cc: firstname.lastname@example.org; Christof Hanke; Christof Hanke; Christopher D=
Subject: Re: [OpenAFS] when openafs becomes a windows IFS
I believe I was quite clear that Explorer ignores the information.
Explorer on XP and Vista simply do not attempt to obtain information
regarding the reparse point data when the file system is SMB.
I am very reluctant to ship this code when it has no visible
benefit and the potential risks of breaking existing user expectations
is exceedingly high.
David Bear wrote:
> This is EXCELLENT.
> Maybe with the code in place, Explorer and other file managers will
> catch up... .. maybe its just wishfull thinking.
> What happens if you use a cygwin bash shell and do a ls ??
> On 9/4/08, *Jeffrey Altman* <email@example.com
> <mailto:firstname.lastname@example.org>> wrote:
> I added the code to the SMB Server to identify mount points and
> as reparse points. The output using 4NT/TCMD from JP Software become=
> Directory of \\afs\athena#user.jaltman\*
> 12/31/1969 23:59 <DIR> .
> 12/31/1969 23:59 <DIR> ..
> 12/31/1969 23:59 <JUNCTION> krbdev
> 12/31/1969 23:59 <DIR> Mail
> 12/31/1969 23:59 <JUNCTION> OldFiles
> 12/31/1969 23:59 <DIR> Private
> 12/31/1969 23:59 <DIR> Public
> 12/31/1969 23:59 <DIR> SysInternals
> 12/31/1969 23:59 <DIR> WinData
> 12/31/1969 23:59 <DIR> WINDOWS
> 12/31/1969 23:59 <DIR> www
> 12/31/1969 23:59 0 afsdrive.ico
> 12/31/1969 23:59 0 desktop.ini
> 12/31/1969 23:59 0 README.mail
> 12/31/1969 23:59 <SYMLINK> sysinternals
> 12/31/1969 23:59 0 welcome
> 0 bytes in 5 files and 11 dirs
> 300,320,768 bytes free
> but the cmd and explorer behaviors remain the same as if the objects
> were not marked as reparse points.
> Jeffrey Altman
> David Bear
> College of Public Programs at ASU