Date: Tue, 9 Dec 1997 11:55:54 -0600 From: "Kent S. Gordon" <kgor@inetspace.com> To: dag-erli@ifi.uio.no Cc: nate@mt.sri.com, hackers@freebsd.org Subject: Re: isa.c Message-ID: <199712091755.LAA01224@chess.inetspace.com> In-Reply-To: <xzpd8j74jpr.fsf@hrotti.ifi.uio.no> (dag-erli@ifi.uio.no)
next in thread | previous in thread | raw e-mail | index | archive | help
>>>>> "dag-erli" == Dag-Erling Coidan Smørgrav <dag-erli@ifi.uio.no> writes:
> Nate Williams <nate@mt.sri.com> writes:
>> > > > > You'd be much better off upgrading to 2.2.5R, as I
>> suspect his patches > > > > apply to that pretty cleanly. > >
>> > I have a list of good reasons for not upgrading to 2.2.2R,
>> and a > > > longer one for not upgrading to 2.2.5R. > > And
>> those would be? > Amongst other items, lack of a suitable
>> backup device No need to backup. It's a piece of cake to
>> upgrade w/out doing a
> In my book, there is a difference between what is possible and
> what is actually advisable. For instance, it is quite possible
> to just switch your computer off when you're done, without
> thrashing your file systems; however, most people prefer to quit
> all applications, log out, and shut down properly, because they
> want to be *sure* not to thrash their file systems. Similarly,
> although it is possible to install 2.2.5 over 2.2.1 without any
> problems, most people will prefer to back up their data first.
> Some day, IMCFT, I'll try what you suggest, then 'accidentally'
> screw up, lose everything, and watch you trying very hard not to
> tell me I should have backed up.
> By the way, one of the other items on my list is that I need to
> repartition my hard drive. I'm sure you'll tell me I can do that
> without backing up, too.
>> backup/restore. Just download the sources, do a 'make world',
>> re-config
> "Just download the sources" is easier said than done with a v34
> modem.
>> and install a new kernel, and reboot. A few hours work, but
>> certainly not rocket science.
> What if my system is slightly "customized", and things stop
> working after the upgrade? Amongst other things, there is quite
> a bit of brain damage in 2.2.1 boot scripts, which I have tried
> to remedy by custom- izing said scripts.
>> > and reports of degraded performance in 2.2.5R. I haven't
>> seen many of those reports, and I haven't experienced any
> I know people (*not* FOAFs, but real people with names and
> faces) who have experienced quite serious problems, amongst
> other things with SCSI performance, after upgrading from 2.2.1R
> to 2.2.5R.
Or worse, a machine that would no longer boot. This happened to me going
from 2.2.2R to 2.2.5R. The machine in question now runs linux :(.
This is documented in PR kern/4864.
> -- * Finrod (INTJ) * Unix weenie * dag-erli@ifi.uio.no *
> cellular +47-92835919 * RFC1123: "Be liberal in what you accept,
> and conservative in what you send" # unzip ; strip ; touch ;
> finger ; mount ; fsck ; more ; yes ; umount ; sleep
Kent S. Gordon
Architect
iNetSpace Co.
voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199712091755.LAA01224>