Slashdot Mirror


End Of OpenBSD 3.0-STABLE Branch - Upgrade To 3.2

jukal writes "From here: "Hello folks, Due to the upcoming release of OpenBSD 3.2, the 3.0-STABLE branch will be out of regular maintainance starting december 1st. There will be NO MORE fixes commited to this branch after this day. People relying on 3.0-STABLE (or older releases even) are strongly advised to upgrade to a more recent release (preferrably 3.2 as it becomes available) as soon as possible. Thanks for reading, Miod" Download from your preferred FTP mirror."

1 of 72 comments (clear)

  1. do what i do: make your own release by honold · · Score: 4, Informative

    man release to get started

    i have a single master system that builds a release distribution and publishes it to a private site. i run the following script to do an in-place binary upgrade of all my systems:

    #!/bin/sh
    rm -rf /usr/upgradetmp
    mkdir -p /usr/upgradetmp
    cd /usr/upgradetmp
    ftp http://WEBSITE/3.1/i386/bsd
    ftp http://WEBSITE/3.1/i386/base31.tgz
    ftp http://WEBSITE/3.1/i386/comp31.tgz
    ftp http://WEBSITE/3.1/i386/game31.tgz
    ftp http://WEBSITE/3.1/i386/man31.tgz
    ftp http://WEBSITE/3.1/i386/misc31.tgz
    cp /bsd /bsd.old
    cp bsd /bsd
    tar xzvpf base31.tgz -C /
    tar xzvpf comp31.tgz -C /
    tar xzvpf game31.tgz -C /
    tar xzvpf man31.tgz -C /
    tar xzvpf misc31.tgz -C /
    cd ..
    rm -rf upgradetmp
    reboot /etc changes have to be merged manually but i keep my global configs in private cvs. bsd tar unlinks everything before overwriting, so doing it multi-user isn't a problem.

    this makes managing 10+ openbsd servers a breeze.