Date: Mon, 3 Sep 2001 00:22:56 -0400 (EDT) From: Chris BeHanna <behanna@zbzoom.net> To: FreeBSD-Stable <stable@freebsd.org> Subject: Re: 2.2.8 -> 4.3 upgrade Message-ID: <Pine.BSF.4.32.0109030005340.575-100000@topperwein.dyndns.org> In-Reply-To: <20010902194650.A26090@freeway.dcfinc.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 2 Sep 2001, Chad R. Larson wrote:
> I'm about to bite the bullet and upgrade my old reliable server from
> 2.2.8-STABLE to 4.3-RELEASE. Biggest incentive is the increasing
> number of ports that won't build without hand-holding and desire to
> support the Ricoh MP7040S SCSI CD-ROM burner I bought for it without
> doing the basic research to realize the WORM dirvers wouldn't
> recognize it. Silly me, I thought SCSI burners would be as
> interchangeable as SCSI disks and CD-ROM drives.
>
> I worked my way through the steps of doing the source upgrade (which
> includes stops along the way at 3.5.1 and 4.1, as best I can tell)
> and decided it would be easier to try to make one large leap.
Yeow!
> So, I'm planning on:
> 1) Full backup (maybe several :->)
> 2) Boot 4.3-RELEASE CDs and select "Upgrade" (kernel and binaries
> only)
I'm not sure if this will work. When I first upgraded from 3.4 to
4.0, I had a nice chat with a nice lady at Walnut Creek who said that
upgrades across minor releases should work, but that upgrades across
major releases are unlikely to work.
You'll have a full backup, so if it doesn't work, you can install
from scratch, restore your data, restore /etc to a secondary place
(e.g., /etc.2.2.8), and put back (most of) your configuration.
> [...snip...]
>
> Things I worry about:
> 1) Are all the currently built ports going to continue to run?
> That is, should I be concerned about a.out/2.x compatability
> issues? Am I going to have to rebuild the ports now in use?
If you install the 2.x compatibility libraries from the CD, I
would expect the old stuff to continue to run; HOWEVER, you may have
to fiddle with ldconfig to get the old stuff to look for the compat
dynamic libraries in the correct places. See the ld_config_paths_aout
setting in /etc/defaults/rc.conf.
> 2) Will my elaborately constructed ghostscript/hpdj500 printer
> subsystem that now makes my antique HP DeskJet 520 think it is
> a PostScript printer going to be damaged?
If it is, install the apsfilter port and go through its
configuration. It's a *wonderful* port, and it works great. The idea
is that it sets up a printcap entry that points to a config-generated
script that invokes ghostscript with the correct options to translate
PS output to HP-PCL, then feed that to your printer. If it works on
my even-more-antique OfficeJet 350, it should work on your DeskJet
520.
> I =am= expecting that I'll have to redo my sendmail.cf and
> supporting files; that should be no problem for me. This machine
> isn't running named.
Neither is mine. The only thing I have to tweak in my sendmail.cf
is to turn MeToo back on, but then, I use fetchmail to get my mail
from my ISP (I have no MX record, and my ISP blocks inbound
connections to ports 1-1024 unless I pay for "business grade"
service), and my otherwise-stock sendmail configuration DTRT when I
send mail out. Note that for that to work, your mail delivery host
has to have a resolvable hostname. I use dyndns.org for that (and
yes, I have given them money, and so should you if you use them).
> So, gang. What else should make be duck? Will it be easier if I
> preserve some particular configuration files before I start (other
> than doing the full backups, that is).
Save /etc for sure, and probably also /usr/local/etc.
--
Chris BeHanna
Software Engineer (Remove "bogus" before responding.)
behanna@bogus.zbzoom.net
I was raised by a pack of wild corn dogs.
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-stable" 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.32.0109030005340.575-100000>