Zbigniew Szalbot wrote:
Hello again,

How do I update the kernel manually then?

Do I have to fetch the latest source and then follow the advice given here?

http://www.freebsd.org/doc/en_US.ISO8859-1/books/handbook/kernelconfig-building.html

Thanks!

Zbigniew Szalbot


It will not update your kernel, but if you do freebsd-update install you
will get an updated GENERIC kernel in /boot/GENERIC.

This is what I did:

freebsd-update -r 6.3-RELEASE upgrade

(got the warning you mentioned)

freebsd-update install

Got a message about installing kernel updates. Got a new generic kernel
in /boot/GENERIC (check to see this exists!)

Depending on whether you have console access to the machine or not:

1. If you don't have console access (you are doing this remotely), mv
/boot/kernel /boot/mykernel.old and mv /boot/GENERIC /boot/kernel and
reboot. This is because you can't (normally) interrupt the loader
remotely - unless someone does it for you. Continue from step 3.

2. If you are in front of the machine, reboot. Stop the boot sequence
when the boot loader comes up, and escape to loader prompt. Type:

    unload
    load /boot/GENERIC/kernel
    boot

3. You are now running a 6.3-RELEASE kernel, albeit a GENERIC one. Run
freebsd-update install again to install the rest of the system.

4. Recompile your custom kernel the usual way, i.e.

I do have to fetch the latest sources before building a custom kernel, don't I?

    make buildkernel KERNCONF=MYKERNEL
    make installkernel KERNCONF=MYKERNEL
    reboot

5. You are done!

Thanks!

Zbigniew Szalbot

Assuming you had the sources for 6.2 installed (how else could you had compiled a custom kernel anyway?), freebsd-update will also update your sources (look at freebsd-update.conf and you will realize it immediately). Just go ahead and compile your new custom kernel!

Manolis
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"

Reply via email to