PrawnOS
Rust-for-Linux
PrawnOS | Rust-for-Linux | |
---|---|---|
8 | 79 | |
109 | 3,797 | |
- | 0.7% | |
3.2 | 0.0 | |
8 months ago | 3 days ago | |
Shell | C | |
GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
PrawnOS
-
Am I Just Paranoid About My New Chromebook?
The OP's computer is one of those Rockchip ARM models. It is much more difficult to get an alternate OS on it compared to Intel models. Maybe this one: https://github.com/SolidHal/PrawnOS
-
How is the free firmware for the Raspberry progressing?
> I'd hardly argue that the RK3399 SoC is more "open" than any of the broadcom SoCs.
What? The gru-kevin chromebook (RK3399) can be booted without using a single binary blob, absolutely everything (even the arm trusted firmware) built from source. I use mine that way.
I've never seen a laptop with a "broadcom SoC" that could make that claim.
https://github.com/SolidHal/PrawnOS
- How to boot linux from usb on arm chormebook
- cheap ARM chromebook for GNU/Linux / chromeos not required
-
What is the linux community's opinion on chromebooks linux capabilities?
chromebooks fork linux almost as badly as androids. instead of mainline + some patches/modules you get a custom kernel made for the hardware in question, usually with lots of proprietary drivers that make it hard for users to update. this is worse for ARM chromebooks than x86 chromebooks, but often has the same result on both: instead of downloading your favorite distro's ISO and installing it, you need to find something like PrawnOS that supports your specific model. in many cases you can't dualboot either because google's gimped UEFI/uboot/whatever implementation only boots chromeOS, and once you replace it with a custom firmware chromeOS becomes unbootable
- How do I install linux on an ARM Chromebook?
-
Did you get a Chromebook for reasons other than school? If so, why?
You might want to look for an installation guide for your specific model. For example I used this one to install PrawnOS on my Acer C201P
-
Ubuntu boot on Apple M1 Macs achieved; port to be released later today
the mainstream name is core/libreboot like used here but there's various other custom firmware too
Rust-for-Linux
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
Rust is backwards compatible when you stick to stable features, but the kernel uses unstable features that can and do incur breaking changes.
https://github.com/Rust-for-Linux/linux/issues/2
- Rust in Linux Kernel
-
Mark Russinovich: “Working towards enabling Windows driver development in Rust”
> How would this work?
Don't know exactly what you're asking.
> And why would it be a better idea?
Poorly written device drivers are a significant attack vector. It's one of the reasons Linux is now exploring using Rust for its own device drivers.[0] You may be asking -- why Rust and not some other language? Rust has many of the performance and interoperability advantages of C and C++, but as noted, makes certain classes of memory safety issues impossible. Rust also has significant mindshare among systems programming communities.
[0]: https://rust-for-linux.com
-
The Linux Kernel Module Programming Guide
Ctrl-F "rust"
https://rust-for-linux.com/ links to LWN articles at https://lwn.net/Kernel/Index/#Development_tools-Rust that suggest that only basic modules are yet possible with the rust support in Linux kernels 6.2 and 6.3.
Rust-for-linux links to the Android binder module though:
> Android Binder Driver: This project is an effort to rewrite Android's Binder kernel driver in Rust.
> Motivation: Binder is one of the most security and performance critical components of Android. Android isolates apps from each other and the system by assigning each app a unique user ID (UID). This is called "application sandboxing", and is a fundamental tenet of the Android Platform Security Model.
> The majority of inter-process communication (IPC) on Android goes through Binder. Thus, memory unsafety vulnerabilities are especially critical when they happen in the Binder driver
... "Rust in the Linux kernel" (2021) https://security.googleblog.com/2021/04/rust-in-linux-kernel... :
> [...] We also need designs that allow code in the two languages to interact with each other: we're particularly interested in safe, zero-cost abstractions that allow Rust code to use kernel functionality written in C, and how to implement functionality in idiomatic Rust that can be called seamlessly from the C portions of the kernel.
> Since Rust is a new language for the kernel, we also have the opportunity to enforce best practices in terms of documentation and uniformity. For example, we have specific machine-checked requirements around the usage of unsafe code: for every unsafe function, the developer must document the requirements that need to be satisfied by callers to ensure that its usage is safe; additionally, for every call to unsafe functions (or usage of unsafe constructs like dereferencing a raw pointer), the developer must document the justification for why it is safe to do so.
> We'll now show how such a driver would be implemented in Rust, contrasting it with a C implementation. [...]
This guide with unsafe rust that calls into the C, and then with next gen much safer rust right next to it would be a helpful resource too.
What of the post-docker container support (with userspaces also written in go) should be cloned to rust first?
- Teknisk karrierevej i Danmark som softwareudvikler
-
The state of Flatpak security: major Projects are the worst?
Rust-for-Linux issue tracker
- rust devs in a nutshell
-
Rustproofing Linux (Part 1/4 Leaking Addresses)
Yes, I definitely agree that it's a problem that pr_info implicitly wraps its arguments in unsafe {}. I wrote my own Pull Request with a trival fix.
-
how to compile a rust "hello world" with kernel 6.1?
Note that this template won't work with Linux 6.1, which has very minimal Rust support. You'll want the RustForLinux tree, or maybe Linux 6.2.
-
If your dream was to be part of a big project like the linux kernel, what would be the first step if you are already an average programmer?
You can join Rust for Linux zulip chat by requesting invite using the link in https://github.com/Rust-for-Linux/linux 's README.
What are some alternatives?
cadmium - [Moved to: https://github.com/Maccraft123/Cadmium]
jakt - The Jakt Programming Language
dattobd - kernel module for taking block-level snapshots and incremental backups of Linux block devices
gccrs - GCC Front-End for Rust
rpi-open-firmware - Open source VPU side bootloader for Raspberry Pi.
rfcs - RFCs for changes to Rust
linux - Linux kernel source tree
rustig - A tool to detect code paths leading to Rust's panic handler
lk-overlay
dafny - Dafny is a verification-aware programming language
evdi - Extensible Virtual Display Interface
koka - Koka language compiler and interpreter