From: Akib Azmain Turja <akib@disroot.org>
To: "Ludovic Courtès" <ludo@gnu.org>, "Leo Famulari" <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: Rust in the kernel
Date: Tue, 05 Jul 2022 14:47:09 +0600 [thread overview]
Message-ID: <87pmikkktu.fsf@disroot.org> (raw)
In-Reply-To: <878rp9c9x9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
Ludovic Courtès <ludo@gnu.org> writes:
> Hi!
>
> Leo Famulari <leo@famulari.name> skribis:
>
>> The effort to use the Rust programming language within the Linux kernel
>> is progressing and may be realized in the next few months:
>>
>> https://lwn.net/SubscriberLink/899182/6c831b90eaee015e/
>> https://www.memorysafety.org/blog/memory-safety-in-linux-kernel/
>>
>> Within Guix, we'll need to adapt our kernel build processes in order to
>> support this.
>>
>> Although I help with updating and configuring the kernel builds, I won't
>> be able to participate in the "Rust in the kernel" effort for Guix.
>
> Understood…
>
>> So, interested volunteers should begin organizing :)
>
> Yup!
>
> Now, concretely, how long will it take before key parts of the kernel
> are written in Rust? Hopefully a long time, no? Per the article above,
> it’s starting small, with Rust usage in well-defined locations.
>
> This is not to say that we shouldn’t start organizing, but rather that
> we still have a bit of time ahead.
>
> (During that time, interested readers can also take a stab at improving
> support for the Hurd, which relies on that revolutionary technology
> called “address spaces” to ensure Memory Safety™ among other things!)
>
> Ludo’.
>
Why "address spaces" is a revolutionary technology? All kernels (except
the "Hello, World!" ones) use it.
By the way, what basic features are lacking (read available) in the Hurd
port? Last time when I checked the pre-built disk image, I found that
it completely breaks after a reboot. I mailed at help-guix list[1],
but got no response.
[1]: https://lists.gnu.org/archive/html/help-guix/2021-09/msg00043.html
--
Akib Azmain Turja
This message is signed by me with my GnuPG key. It's fingerprint is:
7001 8CE5 819F 17A3 BBA6 66AF E74F 0EFA 922A E7F5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-07-05 8:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 16:37 Rust in the kernel Leo Famulari
2022-06-30 16:48 ` Leo Famulari
2022-07-04 12:57 ` Ludovic Courtès
2022-07-04 17:35 ` Akib Azmain Turja
2022-07-04 21:34 ` jbranso
2022-07-05 4:47 ` Akib Azmain Turja
2022-07-05 14:00 ` jbranso
2022-07-05 15:35 ` Akib Azmain Turja
2022-07-05 18:54 ` jbranso
2022-07-05 8:47 ` Akib Azmain Turja [this message]
2022-07-06 15:31 ` Ludovic Courtès
2022-07-06 16:25 ` Akib Azmain Turja
-- strict thread matches above, loose matches on Subject: below --
2022-07-05 18:29 Nathan Dehnel
2022-07-05 18:32 Nathan Dehnel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pmikkktu.fsf@disroot.org \
--to=akib@disroot.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.