On Sun, 2013-01-27 at 13:58 +0100, Polytropon wrote:
> #  1.  `cd /usr/src'       (or to the directory containing your source tree).
> #  2.  `make buildworld'
> #  3.  `make buildkernel KERNCONF=YOUR_KERNEL_HERE'     (default is GENERIC).
> #  4.  `make installkernel KERNCONF=YOUR_KERNEL_HERE'   (default is GENERIC).
> #       [steps 3. & 4. can be combined by using the "kernel" target]
> #  5.  `reboot'        (in single user mode: boot -s from the loader prompt).
> #  6.  `mergemaster -p'
> #  7.  `make installworld'
> #  8.  `make delete-old'
> #  9.  `mergemaster'            (you may wish to use -i, along with -U or -F).
> # 10.  `reboot'
> # 11.  `make delete-old-libs' (in case no 3rd party program uses them anymore)


What source tree? I only checked out the kernel source using svn and
IIRC it's using the /usr/src directory (I'm booted into Linux at the
moment), without a subdirectory /kernel. I can delete the kernel source,
since it's IMO fishy to have headers of another revision, than the
kernel is, but when I asked, I got a reply, that it should be ok for
FreeBSD. However, I never used the kernel source.

When I updated I did it like that (without subversion or cvs):

# cd /usr/ports/misc/mc && make install clean
# uname -r
8.3-RELEASE
# freebsd-update -r 9.1-RELEASE upgrade
# freebsd-update install
# shutdown -r now

# freebsd-update install
# cd /usr/ports/ports-mgmt/portupgrade && make install clean
# /usr/local/sbin/portupgrade -f ruby
# rm /var/db/pkg/pkgdb.db
# /usr/local/sbin/portupgrade -f ruby18-bdb
# rm /var/db/pkg/pkgdb.db /usr/ports/INDEX-*.db
# /usr/local/sbin/portupgrade -af
# freebsd-update install
# shutdown -r now

# freebsd-update IDS >> outfile.ids

I wanted to run it tonight, but since I don't know where my source tree
is, I can't continue.

Regards,
Ralf

_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Reply via email to