React on Rails HN RSC Demo

brynet 1d ago

OpenBSD 7.9 was already on the 6.18.y longterm support version for the drm(4) drivers, Jonathan Gray (jsg@) completed the update back in March, sponsored by the OpenBSD Foundation.

https://marc.info/?l=openbsd-cvs&m=177310343311915&w=2

I just wanted to highlight Jonathan's continued efforts backporting updates in my usual "HYPE" post series for the upcoming OpenBSD 8.0 release.

(I'm the author of the mastodon post that was shared.)

alberth 1d ago

Note that OpenBSD is on 7.9 now and all releases are possible breaking changes.

They release every six month and increment by 0.1. And after 0.9 they rollover to the next whole number.

So don’t think of version “8.0” as a major release per se, since OpenBSD is a fixed schedule release - not a Major.Minor release.

coherentpony 1d ago

> OpenBSD is on 7.9 now and all releases are possible breaking changes.

> don’t think of version “8.0” as a major release per se, since OpenBSD is a fixed schedule release - not a Major.Minor release

Are these two statements a contradiction?

Thinking out loud, maybe the spirit of your comment is, “Every OpenBSD release is possibly a breaking change; the version numbers don’t mean anything.” Otherwise, I don’t see how it’s relevant to mention the current release ends in .9, then explain how the next version is constructed.

Please help me understand. I truly have no sense of how things work in OpenBSD land. The spirit of my comment here is entirely in good faith, just trying to learn.

MYEUHD 1d ago

What they meant is that, in terms of scale, the jump from 7.8 to 7.9 is more or less the same as the jump from 7.9 to 8.0

This is similar to Linux kernel versioning

drdexebtjl 1d ago

I think they mean in addition to all releases possibly having breaking changes, the developers did not pick 8.0 instead of 7.10 because they thought this is a significant milestone, but instead because they always roll from N.9 to (N+1).0.

OpenBSD predates popular semantic versioning conventions by a few years.

bananaflag 1d ago

I think MS-DOS already used in the 80s what you call "semantic" versioning. (Most probably even earlier examples, this is just the first thing that came to mind.)

drdexebtjl 19h ago

No, MS-DOS followed a simple major.minor scheme, with major bumps signifying project milestones or marketing reasons.

Semantic versioning is not what I call it, it’s a formal specification: https://semver.org/

heavensteeth 1d ago

nta but yes your spirit reading is correct. They're saying OpenBSD treats the version number as an integer, and every update adds .1. So 7.8 -> 7.9 -> 8.0, regardless of how significant or breaking the changes are.

asmnzxklopqw 1d ago

Genuine question: if this is only a catch up game, then why not just use the original in the first place?

pjmlp 1d ago

So, AT&T UNIX System V it is then.

sidkshatriya 1d ago

I think the OP was asking the honest question: why not use Linux if the graphics stack is from Linux anyways. It's a fair question and I ask that myself.

Presumably because the other features of OpenBSD bring in some benefits to OpenBSD fans. Also you can always develop on your OpenBSD desktop (with the Linux shim) and then deploy to the server without the Linux shim.

pjmlp 1d ago

I know, but felt that it was the kind of answer one should get when discussing UNIX systems.

Many of us that enjoy UNIX, regardless of its flaws[0], and do not appreciate a GNU/Linux monoculture, similar to having Google taking over the Web with Chrome OS forks.

[0] - Remember that its creators moved on from UNIX and C, creating other systems they saw as improvements on their creation.

asmnzxklopqw 1d ago

I got your point about the monoculture, and I agree with you. Being different is not something bad.

My question was more nuanced though. It seems to me that in the past 10 years or so, openbsd didn’t invent very much. Of course that I agree that there are some punctual things where openbsd was first but that’s not the case lately. So it’s mostly a catchup game with linux features and compatibility needs for running linux software. If you open now the HN front page you will see one story about openbsd importing linux drivers and another story on openbsd struggles to support wine - and basically how wine developers don’t care too much about that.

Hence my question, if most of the effort is put to catch up with linux features, is it even worth anymore? If I want to use linux from 5 years ago, I could just do that. Putting so much effort and time into developing a linux feature clone just in case linux becomes evil, also doesn’t make sense, because you can fork when you see this. Licensing wise even less, I think there’s now a mixture on both sides.

So please take it as a genuine question, not as criticism or anything.

pjmlp 23h ago

Yes, because an OS is much more than drivers, the culture among its users and developers is quite relevant, and OpenBSD users certainly don't want to deal with many Linuxisms like systemd for example, or rather favour pkg approach to software delivery, that is why they are on a BSD in first place.

Just like others might favour Illumos, Aix, z/UNIX, macOS or whatever take on UNIX evolution.

Gracana 1d ago

How does GPL code get ported to BSD?

brynet 1d ago

Most of the common drm code and kernel gpu drivers are already MIT/X licensed for historical reasons, same goes for the Mesa GL and Xorg components.

https://github.com/openbsd/src/tree/master/sys/dev/pci/drm

derefr 1d ago

Huh; I would have thought that importing MIT code into a GPL codebase (like the Linux kernel) essentially “beats out” the original MIT-licensing and instead creates an GPL-licensed fork of said code; thus making such forked code ineligible for re-import into an MIT/BSD-licensed project like the OpenBSD kernel (unless that project wants to be infected by the component’s licensing and become GPL-licensed in turn.)

Are you saying instead that the DRM drivers in the Linux kernel (the in-tree parts, I mean, not the firmware blobs) exist as an island of MIT-licensed code inside the otherwise GPL-licensed codebase?

Or are these parts of the Linux kernel not even technically in-tree, but rather developed in a separate canonical repo and frequently synchronized into the kernel as a vendored dependency? That’s the only way I can see this working; but it’s unclear to me why this state of things would have been maintained for any length of time when the Linux kernel was the only consumer…

Tomte 1d ago

> I would have thought […]

That‘s a common misunderstanding how licenses work on HN. Often even worse: "MIT allows relicensing" (no it doesn‘t, and sub-licensing is something different).

Behold the full set of licenses and copyright notices that apply to the Linux kernel, scanned with FOSSology[1] and ScanCode[2], and curated by licensing professionals: https://raw.githubusercontent.com/Open-Source-Compliance/pac...

Yes, you need to supply all of those if you distribute the Linux kernel in binary form. No, most companies don‘t do that in practice. Yes, they are in breach of all those licenses. Yes, next kernel release there will be changes.

I‘ve long been procrastinating on writing a blog post about exactly that.

[1] https://www.fossology.org/

[2] https://github.com/aboutcode-org/scancode-toolkit

ralph84 1d ago

No, you don't get to change the license on someone else's code just because you import it into your project.

rescbr 1d ago

Each file has their own license, and they are on the same repo.

quotemstr 1d ago

The GPL is (in)famously viral. You can't base something on a GPLed codebase and say that your thing isn't covered by the GPL. The GPL is specifically designed to forbid that specific thing.

kccqzy 1d ago

You can take BSD-licensed code and package it into a GPL bundle, which is what the kernel is doing. You can also extract the BSD-licensed code without the GPL-licensed code and it will be fine.

Gracana 21h ago

TIL, thanks! I wondered if that was the case, but couldn't find a license while clicking around in the code on my phone.

pizzaiolo 1d ago

I wonder if it's downloaded after installation, like nonfree codecs in many Linux distros

rootnod3 1d ago

Yes. The firmware blobs get downloaded at the end of the install via `fw_update`.

rootnod3 1d ago

Specifically in this script https://github.com/openbsd/src/blob/master/distrib/miniroot/...

Just look for `fw_update`

doener 1d ago

Via https://news.ycombinator.com/item?id=50154649

oblio 1d ago

There are parts of me that don't want to say this but will LLMs actually help Linux and smaller OSes by accelerating reverse engineering hardware that doesn't have open/good enough specs? Will we reach a point where hibernate works reliably on Linux? Weird hardware can be used well by FreeBSD?

asveikau 1d ago

This has nothing to do with LLMs. The *BSDs have been porting Linux video drivers for years. This is just the status quo of how video drivers on OpenBSD work.

andrewchambers 1d ago

I see quite a lot of announcements of compatibility and porting efforts -you would never know if someone used an LLM to help, but I would bet money it is being done without admitting it.

asveikau 1d ago

Just because you don't know how to do it doesn't mean they don't. As I said, the same people have been doing this for years, long before LLMs. They need to re-sync with upstream periodically so that's why you see announcements of new stuff.

andrewchambers 1d ago

What makes you say I don't know how to do it?

Also, people who have been doing something for years are exactly the people who benefit the most from having pointless toil removed from the workflows.

Attitudes like yours are exactly why we won't know what level of AI assistance is used. People won't admit it because there is a lot of downside to doing so - especially in communities like this.

asveikau 1d ago

Because you assumed they would direct an LLM to do it and lie about it. Seems like projection to me.

doublerabbit 1d ago

I'm very happy and lucky to have to a modern laptop where everything just works including S3 hibernation in FreeBSD.

MSI Modern 15

OpenBSD 8.0 release will have inteldrm/radeondrm/amdgpu drivers from Linux 6.18 (bsd.network)