Technology

59495 readers

3114 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

352

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

submitted 10 months ago by Gemini24601@lemmy.world to c/technology@lemmy.world

77 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

[–] just_another_person@lemmy.world -3 points 10 months ago (10 children)

Why?

[–] Limitless_screaming@kbin.social 5 points 10 months ago* (last edited 10 months ago) (4 children)

written in Rust.

[–] just_another_person@lemmy.world 1 points 10 months ago (3 children)

And ...why?

[–] leanleft@lemmy.ml 1 points 3 months ago* (last edited 3 months ago)

"In kernel development, debugging is very hard for several reasons:

Documentation is often hard to find, and BIOS implementations may be flawed (more often than you would think)
On boot, the kernel has full access to the memory and is allowed to write where it should not (its own code, for example)
Troubleshooting memory leaks is not easy. Tools such as valgrind cannot be used
gdb can be used with QEMU and VMWare, but the kernel may have a different behaviour when running on a different emulator or virtual machine. Also, those emulators may not support gdb (example VirtualBox)
Some features in the support for gdb in QEMU or VMWare are missing and gdb might even crash sometimes

All those issues are reasons for using a memory-safe language, to avoid them as much as possible.

Overall, the use of Rust in the kernel allowed for the implementation of a lot of safeguards. And I believe that it is, to this day, the best decision I have made for this project."

load more comments (2 replies)

load more comments (7 replies)