Date: Tue, 13 Mar 2001 16:10:27 -0800 From: Jordan Hubbard <jkh@osd.bsdi.com> To: paul@originative.co.uk Cc: kris@obsecurity.org, obrien@FreeBSD.org, cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/netinet ip_output.c Message-ID: <20010313161027E.jkh@osd.bsdi.com> In-Reply-To: <3AAEB5CC.640D6CAA@originative.co.uk> References: <3AAEA597.81830243@originative.co.uk> <20010313155059P.jkh@osd.bsdi.com> <3AAEB5CC.640D6CAA@originative.co.uk>
next in thread | previous in thread | raw e-mail | index | archive | help
> but what about the sysadmin who has to support a real world environment > where a product needs to be upgraded to fix a bug, a typical, real world > application like say the web server, or database. The sysadmin who has to do all of that doesn't need the ports collection to hold his hand (or some other appendage) just to do spot-upgrades of specific pieces. You think Solaris admins never upgrade Apache just because they don't have a ports collection? Upgrading the entire ports collection just to solve this problem is like using a sledgehammer to kill fleas. > No sysadmin in their right mind would go for an OS that requires the box > to be upgraded in order to support the applications that they want to > run. I agree, and it's a good thing we don't require that. FreeBSD still supports tar, make and cc right out of the box. :) - Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010313161027E.jkh>