Joseph Kowalski wrote: > Kyle McDonald wrote: >> Joseph Kowalski wrote: >>> >>> That all said, what problems (other than asthetics) does having >>> gnome in >>> /usr/bin cause? A properly constructed path should let you interpose >>> another. >>> >> Really only if you are wililng to install it local to the machine. >> >> Isn't the network the computer? ;) >> >> -Kyle > I don't understand. Is this to be robust in the face of a failed NFS > server? We offer > many mechanisms to address that problem, the simplest of which is > replicated servers. > I think, it's generally a bad idea to put a network path first in your PATH no matter how robust you make the network services.
I also think it's bad form for many reasons to *not* put /usr/bin (or your preferred env.) first in your path. There are security reasons, at least for this. Lastly, I don't think pushing people to invest in replicated or HA NFS services is the right solution. If someone is willing to accept the risks of a single NFS server for access to gcc, then they shouldn't have to invest in that stuff just to keep ls, cp, and rm working. -Kyle > - jek3
