Date: Wed, 20 Apr 2005 19:20:24 -0600 From: Brett Glass <brett@lariat.org> To: Kevin Kinsey <kdk@daleco.biz> Cc: questions@freebsd.org Subject: Re: Can't build ports on older FreeBSD machine Message-ID: <6.2.1.2.2.20050420191559.06cd0368@localhost> In-Reply-To: <4266ECBB.6000703@daleco.biz> References: <20050419043330.GA92736@xor.obsecurity.org> <6.2.1.2.2.20050419203347.05bed918@localhost> <20050420120120.9D06.REES@ddcom.co.jp> <6.2.1.2.2.20050420170705.06dc6050@localhost> <4266ECBB.6000703@daleco.biz>
next in thread | previous in thread | raw e-mail | index | archive | help
At 05:58 PM 4/20/2005, Kevin Kinsey wrote: >Not in my experience. More oft than not, it's FreeBSD I "fix" and >that other OS I "flatten". > >But then, maybe we work in different environments, although >I'm betting my experience is more common than yours I consult with, and provide service to, quite a few sysadmins at small companies. Most of them won't bother to fix a FreeBSD system that's gone awry like that; they'll just reinstall. They do not have the time to investigate the subtleties of what went wrong. But again, I guess I believe (to bring things back on topic) that a standard, recommended procedure should never leave your machine, or a major subsystem thereof, unusable. It's not hard to fix this, though in this particular case it's not just a matter of setting code but setting a little policy. That's why, contrary to what one recent taunting message in this thread suggests, I can't just "go fix it." The fix has to be in the way things are done more than in the code. Ironically, in the FreeBSD world, this is the harder kind of change to make. --Brett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.2.1.2.2.20050420191559.06cd0368>