Date: Fri, 14 Jul 2000 00:10:37 -0400 (EDT) From: "Brandon D. Valentine" <bandix@looksharp.net> To: Kris Kennaway <kris@FreeBSD.ORG> Cc: Andreas Klemm <andreas@klemm.gtn.com>, "Sameer R. Manek" <manek@ecst.csuchico.edu>, freebsd-stable@FreeBSD.ORG Subject: Re: how to update from FreeBSD 2.2.8 to RELENG_4 Message-ID: <Pine.BSF.4.21.0007132124460.32138-200000@turtle.looksharp.net> In-Reply-To: <Pine.BSF.4.21.0007131708241.3577-100000@freefall.freebsd.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Thu, 13 Jul 2000, Kris Kennaway wrote:
>On Thu, 13 Jul 2000, Andreas Klemm wrote:
>
>> On Thu, Jul 13, 2000 at 01:55:50AM -0700, Sameer R. Manek wrote:
>> > Really a fresh install of 4.0, or soon 4.1 would be your best bet.
>>
>> If doing backup and restore of applications in /usr/local ...
>> Would they run after a fresh 4.1 installation ?
>
>It would work as well as they would if you did a source-level
>upgrade; specifically, some things dig into kernel memory and are thus
>fragile against kernel changes. But most things should just work if you
>install the compat22 libs.
I would generate a list of installed packages by doing:
ls /var/db/pkg > /backupmnt/packages.txt
Then backup any 2.2 software you have which cannot be installed from
ports/packages and install 4.1 on the machine. Then I'd run that list
of installed packages through the attached perl script like so:
chmod 755 pkginst.pl && ./pkginst.pl < packages.txt
and you'll have all of your software back.
Brandon D. Valentine
--
bandix at looksharp.net | bandix at structbio.vanderbilt.edu
"Truth suffers from too much analysis." -- Ancient Fremen Saying
[-- Attachment #2 --]
#!/usr/bin/perl
$pkgcmd = '/usr/sbin/pkg_add -rn';
while ($pkg = <STDIN>) {
$pkg =~ s/-.+//;
print `$pkgcmd $pkg`;
}
help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0007132124460.32138-200000>