OpenBSD 5.5 Brings Y2038 Compliance, Better Hardware Support

[phoronix]

Phoronix: OpenBSD 5.5 Brings Y2038 Compliance, Better Hardware Support

OpenBSD 5.5 has been released! OpenBSD 5.5 is now Year 2038 compliant for all platforms by making time_t 64-bit, there's new hardware support, and other changes...

http://www.phoronix.com/vr.php?view=MTY3NzY

[Zplay]

As an OpenBSD user I find it confusing that they didn't patch OpenSSL in the final release. One will have to compile base system in order to fix this issue, or to use OpenBSD-current :/

[wargames]

What's going on?

Michael, are you ok???? you put a link to an external site!

[archibald]

As an OpenBSD user I find it confusing that they didn't patch OpenSSL in the final release. One will have to compile base system in order to fix this issue, or to use OpenBSD-current :/

It isn't necessary to compile the base system, a patch for -release is already on www.openbsd.org/errata55.html and it only requires rebuilding libssl (and FTP).

Updating to -stable would require rebuilding the base system however (but would also fix the issue).

[BSDude]

I don't think the OpenBSD devs have ported the Radeon DRM from the FreeBSD project. OpenBSD had the stack committed several weeks in advance of the FreeBSD guys.

[endman]

As an OpenBSD user I find it confusing that they didn't patch OpenSSL in the final release. One will have to compile base system in order to fix this issue, or to use OpenBSD-current :/

That's why OpenBSD sucks along with the rest of BSD. They make such a big noise about heartbleed while at the same time openly expose their users to the very same bug.

I recommend you switch to Linux, it's much more secure, secure updates are applied in a second and it's much more user friendly. OpenBSD has at least few security holes willingly planted by the developers for the NSA and CIA to use.

[brad0]

I don't think the OpenBSD devs have ported the Radeon DRM from the FreeBSD project. OpenBSD had the stack committed several weeks in advance of the FreeBSD guys.

Correct. Michael seems to make up crap all too often.

[brad0]

That's why OpenBSD sucks along with the rest of BSD. They make such a big noise about heartbleed while at the same time openly expose their users to the very same bug.

I recommend you switch to Linux, it's much more secure, secure updates are applied in a second and it's much more user friendly. OpenBSD has at least few security holes willingly planted by the developers for the NSA and CIA to use.

LOL. Batshit crazy go back to your cave.

[endman]

It isn't necessary to compile the base system, a patch for -release is already on www.openbsd.org/errata55.html and it only requires rebuilding libssl (and FTP).

Updating to -stable would require rebuilding the base system however (but would also fix the issue).

Mind showing us how to do it? Links, Steps etc.? Because I hear OpenBSD doesn't allow you to compile individual components. Only either the whole kernel or userland.

I don't think the OpenBSD devs have ported the Radeon DRM from the FreeBSD project. OpenBSD had the stack committed several weeks in advance of the FreeBSD guys.

No, they did.

They do not have the man power nor the tenacity to port it straight from Linux.

[endman]

Correct. Michael seems to make up crap all too often.

Brad0, the BSD fayboy.

Looks with you're just pissed that OpenBSD's "new" radeon is old and outdated from Linux 3.8.

In Linux today, we use radeon from Linux 3.15. OpenBSD is years behind Linux in everything.