Adam Chlipala <[EMAIL PROTECTED]> wrote: > Christopher D. Clausen wrote: >> Uhh, why do users seem to have home directories within their user >> volumes? This is dumb IMHO. The home directory should be the root >> of the user volume like nearly every other AFS site. >> > You shouldn't assume that we remember/know how any other AFS site does > things. We started this with my vague recollections of my AFS user's > perspective from my time at CMU and whatever amount of research Davor > had done. None of us have ever done this professionally or even in > any kind of environment with high-reliability requirements, though > that's what we're aiming for now.
Whoa, I'm just wondering how you came to this. I saw no mention of a discussion on the -sysadmin list. I would think it would be discussed there, at a minimum. Its seems to me that something was simply decided without any input or feedback from any users. Remember, sysadmins serve the users. IMHO (and note that this is just my opinion) there should be seperate volumes when someone needs to do something else. For instance, a seperate db.<user> volume or www.<user> volume can be created to hold databases or websites as needed. These other user volumes do not need to have "a" granted to the user (if that is even an issue,) they can deal with just having "write" access, again if needed to their data. Users should have implicit "a" rights on their user volume by owning the root directory of it to allow them to fix things if they manage to break perms somehow. (Hopefully they won't do this.) These per-user per service volumes can be used to track quota, even if it determined that users should only get read access to this data. <<CDC _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
