>
> > ... so it's not that stupid to leave . out and let users put it in, nor
> > is it uncommon ...
> >
> > -dave
>
> On your system maybe, but in the context of the Zoo I don't think that
not just mine, most systems i've used, including commercial isps, and the
security threat is legitimate and widely-recognized, although as i said, i
agree that zoo users in particular probably all would want . in the path,
so the decision is a bit suspect ... i really don't believe elitism is
involved here, this is something any student who is at the level of
compiling executable code should learn, and i think it's hard to argue
otherwise ...
> while the rest of us take on the burden of having to explain to users how
> to add . to their path, or to force them to type './foo' everytime,
i agree with this too, and i think instructions should have been in a
Readme sent to new zoo users and/or explained in the intro classes ...
______________________________________________________________________________
dave caputo | And you may ask yourself \ ceci n'est ___ /
dvc3@pantheon.yale.edu | Am I right?...Am I wrong? \ pas une ___ //~~/
caputo@cs.yale.edu | And you may say to yourself \ pipe [ ]_// /
http://glazunov.dc.yale.edu | MY GOD!...WHAT HAVE I DONE? \ `---' /