[8] in Locker Maintainers
attaching lockers before use
daemon@ATHENA.MIT.EDU (Erik Nygren)
Tue Nov 25 18:13:18 1997
To: locker-maintainers@MIT.EDU
Date: Mon, 24 Nov 1997 21:26:22 EST
From: Erik Nygren <nygren@MIT.EDU>
I hope this doesn't start a religious war,
but should we require users (or programs)
to attach lockers before running programs out of them?
More practically, should binaries have /afs/.../foo/bar paths
or /mit/foo/bar paths hard coded into them (eg, for shared
library search paths)?
In order to allow testing of programs without
releasing them to read-only volumes, I'd tend
towards saying that /mit/foo/bar paths should
be used and therefore lockers need to be attached
before being used.
I've seen both schemes used in different places,
but it may make sense to have a convention
for the sanity of everyone.
(On a much less important and even more religious
note, it might be nice to have a convention for whether
arch-independant files should go in locker/common,
locker/share, locker/arch/common, locker/arch/share,
or something else.)
Suggestions and comments are welcome.
Erik
