[watersb]

25 years ago, I configured GNOME to run a BeOS-like tabbed window manager. On a sun workstation.

But that's not what this is. Or not only:

Nexus Kernel Bridge

Nexus is Vitruvian's custom Linux kernel subsystem that brings BeOS-style node monitoring, device tracking, and messaging to Linux — making it possible to run Haiku applications on a standard Linux kernel.

It claims to run apps from Haiku, the current open-source implementation of a modern BeOS.

[zozbot234]

Looks like this is a thin translation layer for BeOS/Haiku syscalls. I wonder why they aren't relying on Syscall User Dispatch https://docs.kernel.org/6.19/admin-guide/syscall-user-dispat... which would enable them to put this compatibility layer in user space. It's already being used by recent Wine versions.

[hym_the_pawn]

It's not really a translation layer, nexus implements the same BeOS/Haiku IPC in kernel but using linux kernel primitives. It's not as much as a translation layer than any other IPC in the linux system, really BeOS/Haiku apps are first class citizens.

[p_l]

Most of BeOS IPC is in mainline Linux kernel [1] - the difference here seems to be implementing some of the services that are supposed to be available related to filesystem etc and the user land side of it (raw IPC does very little without another layer on top)

[1] - there's a reason why a bunch of BeBook reads the same as some of the oldest parts of Android documentation

[numerio]

BTW because that would not solve any problem for us, the technique you're linking can be useful only if what you want to achieve is binary compatibility otherwise it's useless. That's not really what we are after.