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."
No, dont download it. Buy it! Support the brave people how work hard to get openbsd to work!
man release to get started
/usr/upgradetmp /usr/upgradetmp /usr/upgradetmp /bsd /bsd.old /bsd / / / / / .. /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.
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
mkdir -p
cd
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
cp 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
this makes managing 10+ openbsd servers a breeze.
I admin 850 linux boxes, and as far as I am concerned "release early, release often (and provide no support for older versions)" is open source's major flaw. Developers doing it for fun don't want to support old versions. They're lazy. This laziness has been turned around into some kind of virtue by the open source movement.
What open source needs is a company which provides an 18 month upgrade cycle and supports three concurrent versions. This is exactly what Sun provides with Solaris, and is something that system admins really badly need. And its not just the upgrading issue. You also lose time on the front end of this release cycle because it takes a long time for vendors to certify their software for the new release of the operating system. RedHat is starting to ge some kind of clue about this and is switching to an 18 month release cycle with their advanced server product. They still put on this godawfully stupid dog and pony show though about they'll come in and (for a price) help to upgrade all you machines every time they release a new version. This is entirely unacceptable and waste of resource and a waste of money spent on RedHat. It is basically RedHat trying to turn their laziness into a business model.
And please don't talk about how you've got a couple of scripts whipped together to make it easy to manage 10 openbsd boxes. I'm on a team that manages *850* open source boxes. Whatever you suggest doing simply doesn't scale well enough to deal with doing 850 upgrades every 6-12 months. An upgrade will take everyone on my team offline for at least a month, and we can't afford to be doing that all the time. Also, the next upgrade we're doing is from RH6.2 to RH7.2. We haven't had the time yet to certify all our software for RH7.3 or RH8.0 so we're actually going to be starting out behind once again... This is how system management works at very large sites though.
The OpenBSD team has confirmed it, OpenBSD 3.0 is dead. After an initial increase in use the decline has become visible even for them and they decided not to support it anymore. Everybody who was using it has dropped it in support for version 3.1 and 3.2. This is a clear message to the community: OpenBSD 3.0 is dead. Upgrade NOW!.
bash$