Re: multimple domain authentication

> no, because you don't want them using YOUR fossil, you want them using 
> THEIR fossil. You might let them use a caching fs, but that would probably 
> be it. Grids are for cycles, not disk blocks (in spite of what all the 
> now-failing grids might say).

OK.  Let's say it isn't fossil, it's a "grid service" of
some kind.  It's still a 9P server with the idea of user
and group permissions.  How do we assign group memberships
for non-local users?  Do we throw out the idea of groups
and just use user@domain usernames, or do we give all
remote users the same privileges, or do we have a
per-auth-domain user so that andrey@ucalgary corresponds
to the local user 'ucalgary'?

The last one is livable, but I don't really like any of
those ideas.  I like users and groups, and controlling
group membership per-user.  I guess the answer is just
to create local users for those people who need more than
the simplest "grid" services.  Factotum keeps this
managable, but it doesn't seem perfectly clean.

Still, it isn't worthwhile to drop fossil from the
discussion.  All services are file services.  If we don't
get it right for fossil, we haven't gotten it right.

Micah