Posted on by Justin Sherrill
DragonFly 4.0.3 images available

ISO/IMG files for DragonFly 4.0.3 have been uploaded and by now should be available on your favorite mirror.  You should update for the OpenSSL upgrade.  If you already have DragonFly 4.0.x installed, the normal ‘make buildworld && make buildkernel && make installkernel && make installworld && make upgrade’ cycle should work just fine.

8 Replies to “DragonFly 4.0.3 images available”

  1. Is this way correct:
    cd /usr
    make src-create
    cd /usr/src
    make buildworld
    make buildkernel
    make installkernel
    make installworld
    make upgrade
    (reboot)

  2. Assuming you have already done make src-create once as above, this is what I do, I have it in a script.

    #!/bin/sh

    NUMCPU=`sysctl -n hw.ncpu`
    NUMCPU=`expr $NUMCPU + 1`

    cd /usr/src

    git pull && nice -n 20 make -j $NUMCPU buildworld && nice -n 20 make -j $NUMCPU buildkernel && nice -n 20 make installworld && nice -n 20 make installkernel && nice -n 20 make upgrade && nice -n 20 make rescue

  3. @Nobody: Yes, that is the correct way.

    @Anonymous: Be careful with running ‘make rescue’ that way. You have installed the new kernel and modules already at this point (but are not yet running the new kernel) and ‘make rescue’ will load the vn(4) module (if it is not already loaded from loader.conf or compiled into your kernel), which means it will load a _new_ vn(4) module but your _old_ kernel is still running. We had issues/crashes with this in the past, which is why we decoupled ‘make rescue’ from ‘make upgrade’ some time ago. It is probably safer to reboot between ‘upgrade’ and ‘rescue’ there so that the running kernel and the modules are in sync.

  4. @Anonymous: Sorry for responding but if i have already done make src-create i do the following:

    cd /usr/src
    git pull
    make quickworld
    make quickkernel
    make installkernel
    make installworld
    make upgrade
    (reboot)

    A’m i right?

  5. Nobody – that should work. If for some reason you get an error on the ‘quick’ stage, change it to buildworld/buildkernel, and it should be fine.

  6. @Sascha, thanks for the advice
    @Nobody, just keep in mind that will only use 1 CPU

Comments are closed.