Comment by marty-oehme
6 hours ago
Very cool project! I do have to admit - looking far, far into the future - I am a bit scared of a Linux ABI-compatible kernel with an MIT license.
6 hours ago
Very cool project! I do have to admit - looking far, far into the future - I am a bit scared of a Linux ABI-compatible kernel with an MIT license.
I agree, I know a lot of people aren't huge fans of it but in the long run Linux being GPL2 was a huge factor in its success.
Too late? https://docs.freebsd.org/en/books/handbook/linuxemu/
Somewhere there is a dark timeline where the BSDs won, there are 50 commercial and open source variants all with their own kernel and userland. The only promise of interoperability is in extremely ossified layers like POSIX. There is, however, something terrible gathering its strength. A colossus. The great Shade that will eat the net. In boardroom meetings across the land, CTOs whisper its name and tremble... "OS/2."
Waaaarp
Also, AFAIK SmartOS / Ilumos has had a combat layer for it, too.
Why?
because otherwise big tech companies will take it and modify and release hardware with it without releasing patches etc? Basically being selfish and greedy?
Does this happen to freebsd? I know plenty of closed source Linux drivers.
1 reply →
It is neither selfish nor greedy to accept and use a gift freely given to you.
Receiving a gift does not confer obligations on the recipient.
2 replies →
Because unlike most other functionality, you generally need hw specs or cooperation to write drivers (see Nvidia GSP).
Anyone can write Photoshop (provided reasonable resources). The problem is going to be proprietary file format and compatibility with the ecosystem. It's same with hardware, except several orders of magnitude worse.
It will be compatible for ~5 minutes:
https://www.kernel.org/doc/html/v4.10/process/stable-api-non...
> [Moss has] binary compatibility with Linux userspace applications (currently capable of running most BusyBox commands).
Per your link
> Note: Please realize that this article describes the in kernel interfaces, not the kernel to userspace interfaces.