Well, rather than whine about bad docs, I'm going to try to help improve them. I've taken a cursory look at the Admin Guide, and I see what you mean.
As for that magic syntax, it's very appealing, because it would make one of the things EFS will have to do fairly frequently into something trivial: adding mount points to volumes. I would rather not have to engineer the scratch space I would need to make temporary mounts for this purpose. Hell, I built the MS AFS environment on top of all kinds of tricks like that, many of which I know were never documented back when I was still an AFS guy. If it break, then I'll fix it... On Thu, Sep 30, 2010 at 10:59 AM, Andrew Deason <[email protected]>wrote: > On Thu, 30 Sep 2010 09:10:31 -0400 > Phillip Moore <[email protected]> wrote: > > > The AFS documentation is in a pretty pathetic state, I have to say. > > The changes I'm making to the Quick Start Guide are just a drop in the > > bucket of what's needed. > > The man pages tend to be a little bit better than the QSG. But I would > agree for the QSG, and don't even think about trying to use the Admin > Guide... > > > This magic syntax is VERY powerful, but I don't see it in ANY of the > > fs docs I've looked at so far. > > Those paths are not a feature of 'fs'; they are a feature of the client, > like @sys expansion. And I've never heard of anyone actually using them, > which is at least partially why it's not documented; the document Steven > mentioned says they were just introduced for the NFS translator to use > internally. > > -- > Andrew Deason > [email protected] > > _______________________________________________ > EFS-dev mailing list > [email protected] > http://mailman.openefs.org/mailman/listinfo/efs-dev >
_______________________________________________ EFS-dev mailing list [email protected] http://mailman.openefs.org/mailman/listinfo/efs-dev
