Date: Wed, 7 Feb 2001 21:52:55 -0500 (EST) From: Matthew Emmerton <matt@gsicomp.on.ca> To: Dan Langille <dan@langille.org> Cc: hackers@FreeBSD.ORG Subject: Re: syscall kernel modules on 3.0-release Message-ID: <Pine.BSF.4.21.0102072147390.42056-100000@xena.gsicomp.on.ca> In-Reply-To: <200102080219.f182JAE39186@ns1.unixathome.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, 8 Feb 2001, Dan Langille wrote: > On 7 Feb 2001, at 21:14, Matthew Emmerton wrote: > > On 7 Feb 2001, Dag-Erling Smorgrav wrote: > > > > > Matthew Luckie <mjl@SDSC.EDU> writes: > > > > I completely understand your plea to not use 3.0 release. > > > > I am personally using 4.2-stable. Its not my decision to use 3.0 > > > > I beleive the computers running 3.0 have been running it for several years > > > > now - i.e. it was the latest available at the time. > > > > > > Well, it was a stupid decision at that time, and the decision not to > > > upgrade or replace these machines now is even stupider. > > Be careful how you criticize. > > > Hey now, go easy. Lots of stupid decisions are made by "managers" who > > don't understand the implications of old(er) technology. > > > > I've got a 3.2-R machine which I'm forced to maintain, and the only reason > > why it's not running 3.2-S or 4.2-S is because I can't take the stupid > > thing offline. I've haggled with my boss for a 6 hour window and the > > answer is no, no, no. I've even got a 3.2-S installation waiting in > > /usr/obj. > > What about replacing the box with a new box? Smaller window. Unfortunately, all management sees is the $2000+ cost of a new box. (I'm sure that in both my case and the other case, management has spent more than that in the additional labour required to work around the "features" of the older box.) > > The only way I'm going to get my 3.2-R machine upgraded (and the only way > > this person is going to get their 3.0-R machine upgraded) is when it > > breaks and requires a complete reinstall to become operational. > > It might pay to send an email to your boss, cc'd to yourself explaining > this. I've seen some managers who make decisions such as that and > then blame others when the crap hits. That might work, but that requires boss/manager to have some idea of the technical implications of a) upgrading and b) remaining with old OS. Depending on the organization, the situation may be next-to-impossible. (And no saying I-told-you-so when it eventually breaks.) -- Matt Emmerton To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" 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.21.0102072147390.42056-100000>