End Of OpenBSD 3.0-STABLE Branch - Upgrade To 3.2 72
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."
Re:What World Do These People Live In? (Score:3, Interesting)
So I've had six months? Great --- that's about how much time it takes to do testing for a substantial site. Now I'm done and can work on other tasks? Nope, gotta do it again for the new release.
You're right: the problem isn't the amount of notice they give. I was off on that point. However, the amount of time you get isn't enough for me to use OpenBSD at a customer's site. Eighteen months as the lifespan of a product isn't substantial enough, in my opinion.
Re:Release Cycles are Open Source's major flaw (Score:3, Interesting)
They could support OpenBSD releases for five years and it wouldn't be long enough for some folks.
Newbie (Score:2, Interesting)
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.
Re:Release Cycles are Open Source's major flaw (Score:1, Interesting)
Hey you want your software certified on new versions of redhat? I'm sure they'd be glad to do it for you... PAY THEM. Quit bitching about how "you don't have enough time", developers are not going to put security and reliability patches on hold so you can make sure everything works just spiffy for you. Hire some people who can do their job faster.
And it seems like you don't like even redhat...fine go elsewhere.... if you hate their release cycle so much who the fuck is holding your head to the chopping block that is preventing you from switching to something else?