Earlier quoted context omitted.
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?
Moss: a Rust Linux-compatible kernel in 26,000 lines of code
51–60 of 163 posts
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#52Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#53Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#54Very 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.
It will be compatible for ~5 minutes: https://www.kernel.org/doc/html/v4.10/process/stable-api-non...
Per your link
> Note: Please realize that this article describes the in kernel interfaces, not the kernel to userspace interfaces.
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#55Earlier quoted context omitted.
Great, an MIT license to accelerate planned obsolescence and hardware junk. Truly a brilliant move
Linux magically solves this problem how? GPL isn't magic. It doesn't compel contributing upstream. And half of modern driver stacks live in userspace anyways.
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#56Earlier quoted context omitted.
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.…
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#57Earlier quoted context omitted.
Love the MIT license. If this were further along we could use this as the foundation of our business without having to "give back" device drivers and other things.
Do you think soup kitchens and food banks should only serve food to those who volunteer? MIT is a perfectly fine FOSS license.
F/LOSS is not a charity or a gift, so your analogy is not appropriate. It is a social movement and philosophy with the goal of sharing knowledge and building software for the benefit of everyone. It invites collaboration, and fosters a community of like-minded people. Trust is an implicit requirement for this to succeed, and individuals and corporations who abuse it by taking the work of others and not giving anything back are harmful to these goals. Copyleft licenses exist precisely to prevent this from happening.
MIT is a fine license for many projects, but not for an operating system kernel.
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#58Hello! For the past 8 months, or so, I've been working on a project to create a Linux-compatible kernel in nothing but Rust and assembly. I finally feel as though I have enough written that I'd like to share it with the community! I'm currently targeting the ARM64 arch, as that's what I know best. It runs on qemu as well as various dev boards that I've got lying around (pi4, jetson nano, AMD Kria, imx8, etc). It has…
Congratulations on the progress. If I may ask, I'm curious what considerations have motivated your choice of licence (especially since pushover licences seem extremely popular with all kinds of different Rust projects, as opposed to copyleft).
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#59Hello! For the past 8 months, or so, I've been working on a project to create a Linux-compatible kernel in nothing but Rust and assembly. I finally feel as though I have enough written that I'd like to share it with the community! I'm currently targeting the ARM64 arch, as that's what I know best. It runs on qemu as well as various dev boards that I've got lying around (pi4, jetson nano, AMD Kria, imx8, etc). It has…
Congratulations on the progress. If I may ask, I'm curious what considerations have motivated your choice of licence (especially since pushover licences seem extremely popular with all kinds of different Rust projects, as opposed to copyleft).
Re: Moss: a Rust Linux-compatible kernel in 26,000 lines of code
#60Earlier quoted context omitted.
> It's more like a contractual agreement with something provided and specific, non-negotiable obligations. The obligation is not to the author of the code, it is to the public. MIT-style licenses are gifts to people and companies who produce code and software, copyleft licenses are gifts to the public. I don't give a shit about the happiness of programmers any more than the happiness of garbage collectors, sorry. I d…
I get what your saying but I think it’s not the best way to describe it - “GPL is property”? Hardly - it’s a societal common good that can be used by anyone interested in helping that common good. Are parks “proprietary”? I can’t run my car dealership from one, so it’s …proprietary? No. So using the terminology of “proprietary” doesn’t do justice to what it actually is.