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!
They think that in two months I can take all of my production servers, build replacement boxes, test them, and put the new boxes into production? When the newest release of the OS isn't even available yet? (Why upgrade to the intermediate release when that'll be dropped as soon as the next one comes out...)
Do they assume I have only one box, or that I don't bother to test things, or that I don't lose any money if the upgrade is perfectly smooth? Do they assume that I won't switch to something with a better support policy (and more notice for dropping support) than what they do?
Do any of these people know anyone who manages systems for a living, or do they only talk to other developers?
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 do 'lynx -dump http://WEBSITE/upgrade.sh|sh' to upgrade so i don't have to keep local copies of the script incase it changes
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.
I know this should really be an "Ask Slashdot" question, but I am _really_ interested in learning how to admin OpenBSD systems, and I am having a hard time trying to find books and websites aimed for beginners. Here is my question:
Any good (Open)BSD books on the shelves?
I am currently a sysadmin/netadmin/sys-support guy for a (really) small isp/hsoting company. Our boxes are a mixture of NT/W2K and I'm looking into operating systems for our new servers whenever they arrive. I feel adequate running a linux distro such as Slackware as a new web server, but I would love to put up a *bsd box. (As well as run mySQL, radius, ids[snort], on *nix flavours, as opposed to MS)
I've played with Linux for about 5 years, but not consistently until this past year, where I ran Apache under Mandrake for a websrever for my friends and I (that didn't last long), as well as installed Slack 8.0 on an old p133 for a router/firewall and Slack 8.0 on my laptop. I'm not 100% fluent in *nix scripting and such, but I'm trying really hard to become less reliant on Windows. Both at home (desktop) and at work (servers). Back to my question, now that I can pull my weight with Linux, what is the best way to teach myself more OpenBSD? I've tried using it on a couple of different occasions, but I found the command names and devices so.. so... cryptic(?) to me. I have extra boxes to play on (including two new Celerons 1.3's) at home, but my spare time is almost non-existent, so I'd rather have a book I can read on the shitter or before I go to bed.
Any ideas are GREATLY appreciated.
(I haven't looked into this for about 6 months, but this slashdot article renewed my appreciation and lust for OpenBSD. There may have been kick-ass books and websites written within the past 6 months that deal with BSD administration, but like I said, I'm really busy and my time is tight, so even if you have a pointer that seems obvious to you, please post it up.)
Submit/Preview?? I'll take Submit.
HURD - Hurd's Under Research & Development
Nevertheless there is enough documentation on the web and plenty of help on IRC (esp irc.openprojects.net #open-bsd), the newbie openbsd mailinglist, O'Reilly and man pages, so go for it and join up. Even Lowendpc has a good openbsd section for newbies. It's easier than you think, and the installation is a doddle.
if there were sufficient demand for COMMERCIAL ENTITIES (e.g. red hat) to support 5 versions, they would do it. that's because they have the money to throw resources at it.
openbsd could offer to support 5 versions too, and that would place forward development at a virtual stand-still because of the overhead required.
when the world needs that level of support from red hat, they will have it. that level of support from totally volunteer-based projects will show up WAY later.
as an aside to all this, openbsd simply isn't the kind of os people put on 850 machines. if there's a single grouping of 500 somewhere i'd still eat my hat. it's not a performance/clustering os, it's an edge/internet server os. even if it had exponentially greater development resources, the focus would likely still be on the future as opposed to the past because farms of it simply don't exist.
If you can't make it work, you're doing it wrong. I've got about 120 FreeBSD boxes here, I can upgrade them all in about 2.5 days assuming there are no serious issues (and it is just me). If you can't do something similar, your doing it wrong. The biggest problem I have is accidently forgetting a box.And what the fuck do you care if the OBSD people aren't maintaining the release anymore.. you have the source code!
There is no reason they cannot continue to use 3.0 if it suits their needs. It's not like it's going to roll up and die in December.
And, ignoring the 'technically superior' issue, because that's a whole different argument, what issue is it that lets you not be able to run something?
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$
Wow an old version of OpenBSD is being EOL'd. I don't see how this is even remotely news worthy. This happens every release.
Hello Anonymous Coward, feel free to recognize a parody when you bump into one.
bash$
Okay... so fetching source from the openbsd cvs mirrors.
All the docs on the openbsd site are a bit dated, and you have to piece things together..
everyone talks of -stable and -current. Are these actual CVS tags?
Can I do a cvs get -rSTABLE and get the latest stable?
I know that, for instance, OPENBSD_3_1 is the 3.1-stable tree....
is there somewhere where the cvs tagging is properly documented?
A good source of 'how to' for OpenBSD is www.geodsoft.com's guide to installing and locking down OpenBSD. Whenever I do a fresh installation, I always double-check said site to make sure I haven't forgotten anything. It isn't complete, but it's a damned good start.
Really, though, the best way to learn OpenBSD is to just start using it. As you need to do new things, you'll learn how to effectively use the man pages, sites like Geodsoft, and the misc@OpenBSD mailing list to tackle your questions.
--Ryv
You don't recommend Debian because the OpenBSD project has a new major release every 6 months? Would you mind clarifying that?
As for OpenBSD, you only need to upgrade when there is a flaw in some part of the system that you use, or a security risk. That should take less than 6 months to test. Hell, if you can wait 6 months before rolling out a security fix, then what's the sudden rush? You don't need to install OpenBSD 3.1, by the time you are done evaluating each security fix, just install OpenBSD 3.3 or 3.4.
Seriously, if you can't handle the 1 year (6 + 6 months) upgrade cycle, then just use Debian stable. You really need to explain that unfounded pot shot at Debian, which is very stable, and doesn't force you to reinstall at all... just keep up to date with the security patches, and you shouldn't have to upgrade in your hardware's lifetime.
Oh, and screw H-PU-X , Slowlaris or ACHES, your customers need to demand IRIX!
http://pics.bash.org/swim-bsd.jpg
[o]_O
So anything older than 1 year gets no security updates?
Guess when 3.1 gets killed I'm going to be putting Linux on my firewall.
Comment removed based on user account deletion