Busy upgrading machines now, lots of nice new things. Looking forward to checking out the new execpromises in pledge. I use pledge in all my C stuff and have added it to a few other apps. Thanks OpenBSD devs!
OpenBSD 6.3 released
31–40 of 62 posts
Re: OpenBSD 6.3 released
#32From the release notes: > o Support the sun4v hypervisor interrupt cookie API, adding support for SPARC T7-1/2/4 machines. Who is running OpenBSD on a big expensive SPARC T7 and why? I'm genuinely curious as to what possible use cases there are which make this a desirable combination.
In general, OpenBSD support for Sparc helps with testing - the Sparc is architecturally quite a bit different from other CPUs: https://www.openbsd.org/sparc64.html "The other architectures that OpenBSD supports have benefited because some kinds of bugs are exposed more often by the 64-bit big endian nature of UltraSPARC."
Re: OpenBSD 6.3 released
#33I apologize for being an ignorant for so many years but... who is the OpenBSD target audience? In which areas it is the most popular OS? I worked with Windows, GNU/Linux and macOS (OSX) but never tried OpenBSD.
Also, installation was quite fast if you knew what you were doing.
Re: OpenBSD 6.3 released
#34I apologize for being an ignorant for so many years but... who is the OpenBSD target audience? In which areas it is the most popular OS? I worked with Windows, GNU/Linux and macOS (OSX) but never tried OpenBSD.
BSD people, usually networking. And people who like security (though OpenBSD has detractors). It was used a lot as firewall for critical infrastructure a few years ago, perhaps still is. Also, installation was quite fast if you knew what you were doing.
I'm weird, dunno if others agree ~
Re: OpenBSD 6.3 released
#35I apologize for being an ignorant for so many years but... who is the OpenBSD target audience? In which areas it is the most popular OS? I worked with Windows, GNU/Linux and macOS (OSX) but never tried OpenBSD.
BSD people, usually networking. And people who like security (though OpenBSD has detractors). It was used a lot as firewall for critical infrastructure a few years ago, perhaps still is. Also, installation was quite fast if you knew what you were doing.
Re: OpenBSD 6.3 released
#36Busy upgrading machines now, lots of nice new things. Looking forward to checking out the new execpromises in pledge. I use pledge in all my C stuff and have added it to a few other apps. Thanks OpenBSD devs!
What type of machines do you run OpenBSD on, out of curiosity? Routers, workstations, web servers, embedded devices?
Re: OpenBSD 6.3 released
#37I apologize for being an ignorant for so many years but... who is the OpenBSD target audience? In which areas it is the most popular OS? I worked with Windows, GNU/Linux and macOS (OSX) but never tried OpenBSD.
Re: OpenBSD 6.3 released
#38Earlier quoted context omitted.
BSD people, usually networking. And people who like security (though OpenBSD has detractors). It was used a lot as firewall for critical infrastructure a few years ago, perhaps still is. Also, installation was quite fast if you knew what you were doing.
It has been my daily driver on laptops and desktops for eight years. I have run home servers with it as well.
I don't hack on the internals or build my own ports, I just use it. It stays out of my way and I like that.
Re: OpenBSD 6.3 released
#39Earlier quoted context omitted.
It was probably for testing, but that platform supports partitioning up the hardware through LDOMs, which OpenBSD supports as both a host and guest. https://www.tedunangst.com/flak/post/OpenBSD-on-a-Sun-T5120 (Not expired, Ted runs his own CA) http://man.openbsd.org/man8/sparc64/ldomctl.8
unrelated, but I found his post about running his own CA quite interesting: https://www.tedunangst.com/flak/post/moving-to-https
Re: OpenBSD 6.3 released
#40Busy upgrading machines now, lots of nice new things. Looking forward to checking out the new execpromises in pledge. I use pledge in all my C stuff and have added it to a few other apps. Thanks OpenBSD devs!
> Looking forward to checking out the new execpromises in pledge Interesting that they just changed the interface from `int pledge(const char * promises, const char * paths[]);` to `int pledge(const char * promises, const char * execpromises);`. I guess that is the power they have by being a BSD and integrated system, they do not worry about userland compatibility.
"BUGS. The path whitelist feature is not available at this time."
So the second argument was previously unused, and thus could be repurposed without hurting backwards compatability.