From: "Ludovic Courtès" <ludo@gnu.org>
To: Akib Azmain Turja <akib@disroot.org>
Cc: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Rust in the kernel
Date: Wed, 06 Jul 2022 17:31:50 +0200 [thread overview]
Message-ID: <878rp62r6h.fsf@gnu.org> (raw)
In-Reply-To: <87pmikkktu.fsf@disroot.org> (Akib Azmain Turja's message of "Tue, 05 Jul 2022 14:47:09 +0600")
Hi,
Akib Azmain Turja <akib@disroot.org> skribis:
>> (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.
That was an ironic remark from my part. Virtual memory management and
address spaces are not revolutionary at all: that’s how we protect
processes from stomping onto each other’s toes since the 70’s.
If the goal really is to improve OS reliability through a
multi-person-year effort, then I believe pouring that effort into a
microkernel-based design would be more fruitful. My 2¢!
Ludo’.
next prev parent reply other threads:[~2022-07-06 15:32 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
2022-07-06 15:31 ` Ludovic Courtès [this message]
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878rp62r6h.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=akib@disroot.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).