Re: Proposal to use patterns in fake-files style

[Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx>]

On 2007-04-30 at 13:08 +0100, Peter Stephenson wrote:
> The reason I want this is that our Netapp file server has a magic
> ".snapshot" directory within every directory that doesn't appear in the
> listing (except, for some reason, in the home directory).

It's documented; you might want to ask your filer admins if they've put
a copy of the supplied man-pages anywhere convenient, so that you can
add it to your man search-path.

na_snap(1):

       Volume  snapshots are exported to all CIFS or NFS clients.  They can be
       accessed from each directory in the file system. From any directory,  a
       user  can  access the set of snapshots from a hidden sub-directory that
       appears to a CIFS client as ~snapsht and to an NFS client as .snapshot.
       These  hidden  sub-directories are special in that they can be accessed
       from every directory, but they only show up in directory listings at an
       NFS mount point or at the root of CIFS share.

Probably not worth the portability complexity of dealing with
statfs/statvfs/other and looking for something like f_mnttoname to
compare with the canonicalised path ... but might be worth letting
zstyle set a list of directories which are mountpoints to ignore
.snapshot in, default list value (/home) ?

I'm unable to remember what the EMC Celerra NAS heads name their
snapshot directories but I think it was something different, so
.snapshot itself could be a zstyle'd var?

And a search engine check for Sun's ZFS, (zfs NFS snapshot), turned up
<URL:http://www.solarisinternals.com/wiki/index.php/ZFS_Best_Practices_Guide>
which says the special directory is called ".zfs".

In neither case do I know if the entry is ever returned in a readdir().

But the completion stuff still gives me headaches, so I'm not supplying
a patch.  Sorry.

-Phil