[1971] in SIPB-AFS-requests
Re: Moving /afs/sipb/service/@sys
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Sun May 7 02:30:13 1995
From: mhpower@MIT.EDU
To: ghudson@MIT.EDU
Cc: sipb-afsreq@MIT.EDU
In-Reply-To: "[1969] in SIPB-AFS-requests"
Date: Sun, 07 May 95 02:29:48 EDT
>I would like to move all of the /afs/sipb/service/@sys directories to
>/afs/sipb/service/arch/@sys/bin.
I don't think this is an especially good idea. My personal preference
would be to stay with the current directories because it's less for me
to type, and I often (at least a few times a day) type in the entire
thing since I don't happen to want to put it in my path. I don't
suspect this is a convincing reason for anyone else, of course.
If they need to be moved because it looks wrong to have both sysnames
and SIPB service names as top-level entries in /afs/sipb/service, then
I think the right place is /afs/sipb/service/afs/arch/@sys/bin. My
rationale is that they're files associated with sipb's "afs" service
(At least, they're used for accessing the service. They could also be,
in part, considered the AFS copies of the client-side files that are
run from local disk in /usr/afs/bin to provide services. I guess that
would currently apply mainly to pmax_ul4/bin/vos, for the nightly
releases, although it could conceivably expand to others later.).
I'd think that the "afs" service should be at the same level as other
SIPB service names in the organization of the service volume. If
there's a reason it has a particularly special role such that it needs
to have the top-level arch directory, I've missed that so far...
Matt
