Date: Fri, 4 Jun 1999 12:04:18 -0400 (EDT) From: Matt Behrens <matt@zigg.com> To: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> Cc: sthaug@nethelp.no, marquis@roble.com, security@FreeBSD.ORG Subject: Re: SSH2 (in FreeBSD-Questions) Message-ID: <Pine.BSF.4.10.9906041159210.22071-100000@megaweapon.zigg.com> In-Reply-To: <199906041540.IAA21218@gndrsh.aac.dev.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[ This is not really -security related anymore. Can't think of a ] [ good place to move it so followups are directed to -chat. ] On Fri, 4 Jun 1999, Rodney W. Grimes wrote: : What does a typical path variable look like on your systems??? Long : paths are bad for shells. Yea, I know, the hashing stuff should keep : a single copy of a shell pretty quick, but every time you fork off : another one your going to have to go hash the path list. Well, why not do what I do -- I have /opt/packagename/bin, /opt/packagename/sbin, etc. and I simply do this after installing a package: cd /opt/bin;ln -s ../*/bin/* . Then we can just add /opt/bin to our paths. We still keep things nice and separate, and if we want to clean up dead symlinks, we just do rm /usr/bin/* then rerun the symlink generator. : I would actually rather have sshd in /usr/local/libexec, it's not something : you really run from the command line :-) I heartily agree with this, except I put mine in /opt/sshd/libexec with symlinks to /opt/libexec :-) In case anyone wonders why I use /opt, well, I feel /usr/local should stay the property of the actual local software that I develop. Matt Behrens <matt@zigg.com> Owner/Administrator, zigg.com Chief Engineer, Nameless IRC Network To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.10.9906041159210.22071-100000>