Technology

58061 readers

31 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each another!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed

Approved Bots

founded 1 year ago

MODERATORS

[email protected]

352

Maestro, a Linux compatible kernel written in Rust. (blog.lenot.re)

submitted 8 months ago by [email protected] to c/[email protected]

79 comments fedilink hide all child comments

Enter Maestro, a unix-like monolithic kernel that aims to be compatible with Linux in order to ensure wide compatibility. Interestingly, it is written in Rust. It includes Solfége, a boot system and daemon manager, maestro-utils, which is a collection of system utility commands, and blimp, a package manager. According to Luc, it’s creator, the following third-party software has been tested and is working on the OS: musl (C standard library), bash, Some GNU coreutils commands such as ls, cat, mkdir, rm, rmdir, uname, whoami, etc… neofetch (a patched version, since the original neofetch does not know about the OS). If you want to test it out, fire up a VM with at least 1 GB of ram.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 94 points 8 months ago* (last edited 8 months ago) (7 children)

This sounds cool, but troubling because of its license. Trying to write a linux compatible kernel and licensing as MIT is basically asking to get railroaded by gigantic organizations. I hope they reconsider in the future.

[–] [email protected] 3 points 8 months ago (1 children)

Could someone detail why? Why is MIT license troublibg?

[–] [email protected] 4 points 8 months ago

MIT is basically "do anything you want with it, I don't care". I means some company can reuse it in its closed source projects freely and without notice or royalty.

There are plenty of other licenses that require you to also go open source if you include and/or modify it. Basically "you can use ot however you want, but if you modify it, it has to be open source as well"

load more comments (5 replies)