Slashdot Mirror
Celebrating 20 Years of OpenBSD With Release 5.8 (openbsd.org)
badger.foo writes: 20 years to the day after the OpenBSD source tree was created for the new project, the project has released OpenBSD 5.8, the 38th release on CD-ROM (and 39th via FTP/HTTP). This release comes with four release songs instead of the usual one, and a long list of improvements over the last releases. (Probably a good time to donate to the project, too, even if you don't use it directly, because of all the security improvements that OpenBSD programmers contribute to the world.)
really all that needs to be said.
No I am fully aware that systemd targets Linux and OpenBSD is, well, not Linux. But seriously, what's the status of init in OpenBSD? Last time I used it (around 5.2 for some odd sparc servers that didn't support anything else apart from Solaris) it was still /etc/rc.d scripts, and no respawn if a service crashed etc.
I recently saw a video review of a new computer in a box that was too small have a CD-ROM drive but came with the drivers on a CD-ROM. *face palm* Fortunately, the drivers also came on a USB stick.
I still have a few spindles of blank CD and DVD discs lying around, but I haven't burned a disc in three or four years. Have USB sticks, will travel.
It's worth checking out in a VM. I've been enjoying GhostBSD quite a bit and have been thinking of installing it on bare metal instead of just using it in a VM. I will miss Opera though. At any rate, congrats and thanks - I'll have lots of fun poking at it. I've only played with FreeBSD and GhostBSD so I might as well give this one a shot too.
"So long and thanks for all the fish."
Not to be confused with Slashdot's Theodp (I assume)
Don't worry OpenBSD still has 3 times the number of users as NetBSD!
You are mixing apples and oranges here. You should still give to both. By OpenSSH alone, OpenBSD has saved a lot of lifetime (although in smaller pieces than Doctors Without Borders) from getting wasted. And it is a critically needed fall-back if Linux continues to go down the train.
Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
Theo has been told this hundreds of times, and he simply doesn't care. The brilliant result is that now OpenBSD has more developers than users. And this is not only a joke.
By the same token, there are plenty of more deserving causes for you to comment on.
You could instead use your time for activism in order to support Doctors Without Borders instead of commenting here.
Downvoted by one of the 17 existing OpenBSD users in the world. LOL! They are just pathetic.
How in the planet of Hell is Linux going down the drain? Been drinking a wee bit too much of the Kool Aide have you ?
You say that like it's a bad thing.
If there are plenty of developers working on an OS that is security focused, and the userbase is too small for most bad actors to target with exploits, where's the problem?
Take your head out of the sand man! Just 5 years ago there's no way we'd be celebrating 20 years of open bsd on slashdot. I'm afraid Linux has been losing its religion one political fight at a time and now it's too late. On the other hand, I can't really remember all the different *bsd versions there are now, but at least in the bsd world when you piss people off, they do something about it instead of bending over.
If you can't follow those few instructions and upgrade a machine, you really should NOT be involved in tech.
This is pretty simple stuff.
As an engineer who knows the pain of debugging someone else's locking problems, I lost it when I read this release note:
We tried to do something about all the anti-user changes in Linux. Apparently the majority of the userbase is powerless to stop corporate interests (RHEL) from shoving in anti-user changes.
That's why a lot of us Linux people started looking at other options, like FreeBSD.
They haven't learned yet ( cough ... opensmtpd), but the Internet has surely advanced in that thanks to them.
I really like OpenBSD and hope it improves the vioscsi performance, which is a showstopper for me on many servers. Not everyone can afford to have colocated servers or a room full of dedicated OpenBSD hardware like Theo.
I'd gladly give up half the SSD performance to use OpenBSD over Ubuntu, but 50 MB/s vs 750 MB/s disk io penalty (OpenBSD 5.7 vs Ubuntu 14.04) is too much on my Linodes. By comparison, FreeBSD 10.2 is about 500 MB/s for me, which is slower than Ubuntu but fast enough for my needs.
Anyway, here's to OpenBSD 5.8 and OpenBSD 5.9 getting faster on Linode, Digital Ocean, etc., especially with vioscsi.
If you can't follow those few instructions and upgrade a machine, you really should NOT be involved in tech.
Which obviously means that the whole world of "tech" is only composed by the 17 existing OpenBSD users.
Sure. Betamax tapes are not subjected to malicious hacking either. What a huge achievement.
Have you submitted bug reports or documentation with this issue?
The link you pointed to is 4 steps? Cumbersome?
1. Reboot using new kernel
2. # sysmerge
3.
4. # pkg_add -u
Lately there's been a backlash against GPL & RMS, who used to be highly praised around here. I think it has a lot to do with GPL3, but somehow the vitriol has been redirected toward his personal hygiene.
Linus is still held in pretty high regard, except for his sometimes-abrasive style. Lennart may well be the downfall of Linux fandom here.
Pretty much 3 main branches: FreeBSD, NetBSD and OpenBSD. OpenBSD is a fork of NetBSD. Dragonfly, PC-BSD and GhostBSD are all forks of FreeBSD.
Mac OS X/Darwin is a fork of 4BSD hybridized with Mach, and later sync'd with FreeBSD.
SunOS was BSD-based but replaced by the System V-based Solaris, with some BSD features folded in.
actually updates are trivial. select (u)pgrade instead of (i)nstall. let it install the new file sets. then after a reboot just enter "sysmerge". That's pretty much it!
The link you posted says this: If you have access to the system's console, the easiest and safest way to upgrade is to boot from the install kernel by boot media or bsd.rd and follow the upgrade steps
I've switched all my laptops and servers to OpenBSD from Linux a few years ago and haven't looked back. The high security has been great. But the biggest surprise for me has been how dead SIMPLE it is to run an OpenBSD system compared to Linux. Really been like a breath of fresh air for me. But I agree that in some areas the i/o and performance hasn't been as good as it could be. I think the only way to improve the performance is for people who are willing to make a dedicated effort to tune the bits of the system that matter to them. What's needed is more users with technical skills identifying bottlenecks and helping to solve them. Would love to see more of that in the future!
hah, I guess?
But in all seriousness, we have a few hundred OpenBSD users here. I think the problem is that unlike Linux where lots of users are constantly complaining because things constantly break, you never hear from OpenBSD users as much because everything just works so smoothly. For example, most projects allow things to get pretty unstable between releases. OpenBSD has zero tolerance for instability. Sure sometimes when new features like the recent tame/pledge syscalls have been added things break for a few hours. But most of the time the system remains rock solid after every single commit.
Oh the other thing I love is how the entire base system is built from 1 tree. No more fetching a kernel from here, fetching userland tools from there, building a compiler from yet another place. It's all integrated for me. I no longer have to worry about figuring out which versions to mix and match because OpenBSD has already done it for me. (same story with the other BSD projects).
Just 5 years ago there's no way we'd be celebrating 20 years of open bsd on slashdot.
Seriously? Even Haiku releases get celebrated here.
This space intentionally left blank
Tame / Pledge is interesting.
Just 5 years ago there's no way we'd be celebrating 20 years of open bsd on slashdot.
Yeah no shit, sherlock. That's because that would've been 15 years of "open bsd" (sic).
CLI paste? paste.pr0.tips!
VHS tapes aren't either. What's your point?
CLI paste? paste.pr0.tips!
Amen brother. I've moved to BSD and love it. The Linux kernel has done some pretty cool/interesting things over the years, but surprisingly they've never been able to keep up with FreeBSD when it comes to networking or security when it comes to OpenBSD.
The UNIX philosophy was always groups of simple tools that do one thing and do it well. You pipe them together and parse the data however you want. Systemd does the exact opposite of that. One monolithic service doing everything but poorly. None of these new ideas have undergone any real testing other than shipping the distro when they compile. You're beta testing this bullshit.
More accurately it's about tight versus loose coupling.
Under systemd, while there are many CLI commands, they are bound together and cannot be used independently. You can't really use journald, hostnamed, machined, timedated, etc., independently or replace them with something else that you've developed.
It's all very well to write a "better init", and maybe it has, but you're stuck with also running journald and can't put in rsyslog instead (only run in parallel). timedated may be good, and you want to use it on a SysV-based system... but you can't.
You have obviously never seen The Ring.
The UNIX philosophy was always groups of simple tools that do one thing and do it well. You pipe them together and parse the data however you want. Systemd does the exact opposite of that. One monolithic service doing everything but poorly.
If you build systemd with all configuration options enabled you will build 69 individual binaries. These binaries all serve different tasks, and are neatly separated for a number of reasons.
A package involving 69 individual binaries can hardly be called monolithic. What is different from prior solutions however, is that we ship more components in a single tarball, and maintain them upstream in a single repository with a unified release cycle.
The Biggest Myths
[2013]
You're beta testing this bullshit.
Then you are in damn good company.
Much of the debate about systemd is academic at this point because here's a truth that you'll discover in Debian 8, Ubuntu 15.04, and just about every other major distro around: systemd is here.
Debian 8: Linux's most reliable distro makes its biggest change since 1993 [May 1, 2015]
Red Hat is the inventor and primary booster of systemd, so the best distros for playing with it are Red Hat Enterprise Linux, RHEL clones like CentOS and Scientific Linux, and of course good ole Fedora Linux, which always ships with the latest, greatest, and bleeding-edgiest.
Understanding and using Systemd
That is what he just did, you dipshit.
Any "doas" experts out there?
I've recently been running this, many times over the past several days: /etc/pf.conf&&sudo pfctl -ef /etc/pf.conf
sudo pfctl -nf
It looks like "doas" won't work like that. The documentation seems to indicate that "doas" returns zero as long as it was able to call the program, even if the called program returns non-zero. (At least, there is no mention that "doas" returns something different.) What's the most effective way of having the parent process determine what happened with the kid?
Linux is better because it had the 20 years ago today moment over 4 years ago.
Escher was the first MC and Giger invented the HR department.
So, another chapter in the irrelevant systemd debate unfolds beneath this post. I love watching neckbeards and social invalids like Poettering, et al. get into slappy-hand-fights over something Linus Torvalds couldn't give a damn about- this is entertainment!
The debate -is- starting to thin a bit through attrition as a few of you get busy with life after acquiring girlfriends (albeit great, big, girlfriends that squeeze themselves into princess Leia slave-girl outfits for Comic-cons)... Remember, though, that while this novel concept of "girlfriend" may be intoxicating to some of you, you're supposed to raise livestock, not date it.
Just 5 years ago there's no way we'd be celebrating 20 years of open bsd on slashdot.
No, that wouldn't have made sense, as 5 years ago OpenBSD had only been around 15 years.
I am literally 3000 tokens away from the chaotic crossbow --Stephen
of moving my personal machines over to Free and OpenBSD. I've grown tired of the Linux balkanization, the systemd debacle, once great distros making bad decisions, and general shenanigans that doesn't seem to be present in the BSD world.
What I've found over the last few years:
- BSD is far more stable than Linux, all things considered
- BSD is engineered, Linux feels cobbled together, even in so-called "professional, enterprise-level distros"
- BSD is arguably faster on the same hardware
- BSD is arguably easier to manage -- thank you rc.conf
- BSD suffers far less infighting and seems more professional
I've been in IT for almost 20 years. I earned my degree with *nix, have been a *nix admin for many years as well as for Microsoft and Mac servers. BSD is very refreshing on a personal level. I'm currently running one of my machines on FreeBSD 10.2 and it's given me far less trouble than any Linux distro. Of the Linux distros I have used, and that would be most of them, I do have a certain feeling for openSUSE. It seems to be the least problematic distro in my experience.
Apparently the "upgrade" program on the CD twiddles with your routing tables, in case you're having problems getting packages to download. By default my system wouldn't connect to the network, so I chose the shell option, cleared the tables, used dhclient on a different interface, and then restarted the process by running "upgrade." This *still* didn't work and was kind of confusing. Control-C out of the program shows that the routing tables got changed somehow (it sets the default route to the _external_ IP, I assume some "smart" detection is making this genius decision).
Anyway, if you have this problem, use the ! in the package URL selection process to drop out and change the network settings back. It does this modification early enough in the process that this works.
It was enough work to figure out what the problem was, and I don't have enough patience to deal with a known-abrasive community to file a bug report and do back and forth. So, hope this helps someone searching.