Date: Fri, 4 Jun 1999 15:40:25 +0000 (GMT) From: "Rodney W. Grimes" <rgrimes@gndrsh.aac.dev.com> To: sthaug@nethelp.no Cc: marquis@roble.com, security@FreeBSD.ORG Subject: Re: SSH2 (in FreeBSD-Questions) Message-ID: <199906041540.IAA21218@gndrsh.aac.dev.com> In-Reply-To: <96085.928510202@verdi.nethelp.no> from "sthaug@nethelp.no" at "Jun 4, 1999 05:30:02 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
> > One thing ports don't do well is install themselves in predictable > > locations. Instead you'll find them installing files in > > /usr/local/etc, /usr/local/bin, /usr/local/sbin, /usr/local/libexec, > > /var, etc. When I install ssh2 I want it all under /usr/local/ssh. 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. > > This alone is a good reason to use ports sparingly (after reviewing the > > patches). > > Having everything under /usr/local/ssh is convenient in many way, but > I don't believe there is any kind of agreement that this is *the* only > correct way. Myself, I'm happy to have ssh, ssh-keygen etc. under > /usr/local/bin (actually /local/bin here) and sshd under /usr/local/sbin. I would actually rather have sshd in /usr/local/libexec, it's not something you really run from the command line :-) -- Rod Grimes - KD7CAX - (RWG25) rgrimes@gndrsh.dnsmgr.net 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?199906041540.IAA21218>