Date: Wed, 28 Nov 2001 17:24:55 -0700 From: Nate Williams <nate@yogotech.com> To: Brett Glass <brett@lariat.org> Cc: Christopher Schulte <christopher@schulte.org>, "Jay Keller" <jaykeller4@hotmail.com>, freebsd-security@FreeBSD.ORG Subject: Re: Updating ssh Message-ID: <15365.32855.717257.546724@caddis.yogotech.com> In-Reply-To: <4.3.2.7.2.20011128171207.056cd1d0@localhost> References: <4.3.2.7.2.20011128151923.041d0710@localhost> <F49Gmjm08IyFrydlb9r0001c375@hotmail.com> <4.3.2.7.2.20011128171207.056cd1d0@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
> >>Perhaps FreeBSD should put these things in /usr/local from the get-go? > > > >No. /usr/local is for software installed outside the base system. The ssh package is part of the base system, > > Not really. It's not maintained by the FreeBSD Core Team and is updated > independently. Almost nothing is maintained by the core team. It is however maintained by a non-core developer (green), who creates FreeBSD-specific patches and applies them to the released OpenSSH software. So, in effect, it is maintained as part of FreeBSD. (The installed version is different from the ports version). > It merely "comes with" the base system. That's an important > distinction. See above. > Myself, I believe that third-party products should be kept in separate > directories -- preferably in the default ones used by the developers, > unless these are totally bogus. If this were done with SSH, it would > be in /usr/local from the get-go and upgrades would work. Ditto with > Perl. The software that is part of the base system is *part of the base system*. In other words, it's required (in some sense of the word) in order for the rest of the system to work. If you want a completely modular system, go with PCIX. :) Nate 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?15365.32855.717257.546724>