[5502] in Athena Bugs
SOMEBODY FIBBED TO ME ABOUT REMOVE.
daemon@ATHENA.MIT.EDU (Jonathan I. Kamens)
Wed Jul 11 13:35:04 1990
Date: Wed, 11 Jul 90 13:34:39 -0400
From: "Jonathan I. Kamens" <jik@pit-manager.MIT.EDU>
To: wdc@ATHENA.MIT.EDU
Cc: bugs@ATHENA.MIT.EDU, athena-ws@ATHENA.MIT.EDU, f_l@ATHENA.MIT.EDU
In-Reply-To: Bill Cattey's message of Tue, 10 Jul 90 22:07:48 -0400 (EDT) <MaacbowGG02=IrDbhE@athena.mit.edu>
Bill, I say you've still got things wrong.
The "advertised solution of using remove" DOES work, if you use it
when you're supposed to, i.e. after using "setup". Remove was NEVER
meant to be able to clean up after an "add". We never designed any
method at all for cleaning up after an "add"; we decided it wasn't
necessary.
All "add" does is add a path to the user's PATH and his MANPATH. A
simple "detach" of the same filesystem will get make the directories
which were added to the PATH and MANPATH, which means nothing will
ever get done with them again, which is pretty much a complete
clean-up. Sure, the directories hang around in the PATH and MANPATH,
but so what? The effort that software will go through to discover
they no longer exist is quite minimal, and besides that, the frequency
of this actually happening is also quite minimal.
I just don't think there's much of a problem here at all. You're
"sounding general quarters" over something that just isn't a big deal.
Perhaps we should write a new alias to undo what add does. I
personally don't think we need it, but I might be convinced otherwise.
However, I do NOT think this is such an urgent problem that we have to
worry about getting something to fix it into 7.1. It just isn't a big
deal.
jik
