FreeBSD6.3 upgrade to FreeBSD7.0

[Ofloo]

Typed make update in /usr/src to have cvsup update the directory, .. i copied the GENERIC kernel file to a new one and edited that, .. then i typed config <kernelfile> ..? Weird no such command .. checked /usr/sbin config was there though only rw mode chmod +x .. didn't work checked what was in the config file apparently it was some script so: "cd /usr/src/usr.sbin/config && make install"

ERROR: version of config(8) does not match kernel!
config version = 600003, version required = 600004

Make sure that /usr/src/usr.sbin/config is in sync
with your /usr/src/sys and install a new config binary
before trying this again.

If running the new config fails check your config
file against the GENERIC or LINT config files for
changes in config syntax, or option/device naming
conventions

Figured it's due the freebsd7 source tree, so i downloaded with cvsup freebsd6.3 source tree still the same, how can i fix this ?

I have noticed that i still can compile when the configuration and src tree is FreeBSD6, though after reinstalling world and upgrading the kernel to 6.3p2 i still have this issue with config, when i try to compile a freebsd7 kernel, i've tried building world before using config without any effects ..

[phoenix]

You have to do a full buildworld cycle to upgrade between versions. You can't just compile the kernel.

[Ofloo]

I will try to do make buildworld again if that's what you mean though I have already tried this.. once before, or how do you suggest i do this ?

[phoenix]

Clean out the /usr/obj directory:

# cd /usr/src
# make cleanworld

Update to the FreeBSD 7.0 source tree by setting tag=RELENG_7_0 in your supfile, then run:

# csup /path/to/supfile

Build the new world:

# cd /usr/src
# make -j2 buildworld

(Change the 2 to 1 more than the number of CPUs you have.)

Build a new GENERIC kernel:

# make buildkernel

Install the new GENERIC kernel:

# make installkernel

Reboot. If it boots correctly, then you can proceed to install the world:

# cd /usr/src
# make installworld

Then run mergemaster (be sure to only install files you haven't edited, and to merge files you have edited, like passwd and group):

# mergemaster -iU

Then reboot once more to load the new world. And then rebuild all your ports. If everything is working correctly, then you can edit your kernel config file, and build your custom kernel:

# cd /usr/src
# make KERNCONF=MYKERNEL buildkernel
# make KERNCONF=MYKERNEL installkernel

(where MYKERNEL is whatever your kernel config file is called)

[Ofloo]

hmm, I havn't tried it yet with a GENERIC kernel though, .. but i get a lot of this

kldxref: file isn't dynamically-linked

I'll give it a try with a GENERIC kernel and let you know what happens..

[tonywob]

Originally Posted by phoenix

Reboot. If it boots correctly, then you can proceed to install the world:

# cd /usr/src
# make installworld

It is recommended that you boot into single user mode to run "make installworld" and run mergemaster. After that, you can continue.

[Ofloo]

hmm but isn't "kldxref: file isn't dynamically-linked" a problem i get a lot of those on the end .. after running make installkernel (KERNCONF is defined in make.conf)

[erno]

Originally Posted by Ofloo

hmm but isn't "kldxref: file isn't dynamically-linked" a problem i get a lot of those on the end .. after running make installkernel (KERNCONF is defined in make.conf)

Just ignore it. http://lists.freebsd.org/pipermail/f...ay/072805.html

[Ofloo]

Apparently it worked by just ignoring it so far it works just fine, ..

Thanks for all the replay's it really helped.

[Ofloo]

Oh one more thing can I run make check-old && make delete-old after a successful upgrade ?

EDIT:

also i've noticed pkgdb is acting weird, ..

# pkgdb -F
--->  Checking the package registry database
[Rebuilding the pkgdb <format:bdb_btree> in /var/db/pkg ... - 56 packages found (-0 +56) ........................................................ done]
Stale dependency: BitchX-1.1.0.1_1 -> perl-5.8.8_1 (lang/perl5.8):
Install stale dependency? ([y]es/[n]o/[a]ll) [yes]

...

# pwd
/var/db/pkg
# ls | grep perl
perl-5.8.8_1/
# perl -v

This is perl, v5.8.8 built for i386-freebsd-64int
(with 1 registered patch, see perl -V for more detail)

Copyright 1987-2006, Larry Wall

Perl may be copied only under the terms of either the Artistic License or the
GNU General Public License, which may be found in the Perl 5 source kit.

Complete documentation for Perl, including FAQ lists, should be found on
this system using "man perl" or "perldoc perl".  If you have access to the
Internet, point your browser at http://www.perl.org/, the Perl Home Page.

[KernelPanic]

There are some major library changes between 6.3 and 7.0.

You will need to reinstall most (if not all) of your ports so that they are linked to the correct ones.

[tofumaster]

So, if I've been installing my ports via the packages most of the time, do I still have to reinstall all my ports?

Looking at the ports-supfile, it doesn't seem like it makes a distinction between 6.x and 7.x.

Also, is there a command that I could use to "force refresh" install of all the ports?

(Just wondering how painful this might be...)

Thanks!

[graudeejs]

check portmaster port, read man

[qsecofr]

Hi,

I Will at some point shortly upgrade from 6.4 to 7.1 release. I've been reasonably OK doing source upgrades using pretty much the same steps as Phoenix detailed - from 4.3 to 4.11 and 6.1 to 6.4. My question is in regards to generic kernel. Was it an outright recommendation to install a generic kernel when first building 7.0 release?

I've seen a couple other recommendations - specifically one describing a binary upgrade - state that the GENERIC kernel in 7.x has SMP by default. And for that reason users should build & install GENERIC first.

But i've got a custom kernel including dummynet for ipfw among a few other options. And if possible I would prefer to upgrade to 7.x with my custom kernel, without having to first build & install GENERIC first.

Can I ask what reasons exist for building/installing GENERIC first?

Thanks!

[phoenix]

To make sure that the system works. If you can't run GENERIC, you probably can't run FreeBSD. So you do upgrades using GENERIC. If it doesn't work, you put back the old kernel. If it does work, then you build a new custom kernel. This also avoids the "that option no longer exists" and "we've changed the defaults, so now your custom kernel is missing things" traps.

[qsecofr]

got it. Thanks!

[qsecofr]

Hi,
Am in the process of rebuilding all ports after upgrading from 6.4 to 7.1. So far have built/installed world & kernel (both generic & custom kernels install and run). Am running custom kernel now w/o any noticeable problems.

After all ports are rebuilt should I

cd /usr/src
make delete-old-libs

Is it safe to answer 'y' to each prompt? Should I check each first to verify that I'm not removing the highest numbered lib?