From: Lucio De Re <lucio.dere@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Is Plan 9 C "Less Dangerous?"
Date: Sun, 2 Sep 2018 20:16:39 +0200 [thread overview]
Message-ID: <CAJQ9t7j0wOtcVzZqwndo1JN2zmxb_mBB+8EaPdTPMODsMWMf4g@mail.gmail.com> (raw)
In-Reply-To: <CAOk9ws1kxHh5MhRVwTMwPjM763++VmFMda-vefk8SZFt8y=OTg@mail.gmail.com>
On 9/2/18, Chris McGee <newton688@gmail.com> wrote:
> I'm reading this article about how they are going through the giant heaping
> pile of Linux kernel code and trying to come up with safer practices to
> avoid the "dangers" of C. The prevailing wisdom appears to be that things
> should eventually be rewritten in Rust some day.
>
Like hell they will! By the time they have even a minute portion of
Linux running under a different language, the language-du-jour will
have moved on. It's a monolith, it cannot be translated, unless it is
mechanically. And we know how brilliant that is likely to be.
> How does everyone feel about the Plan 9/9front kernel? Have they gone
> through hardening/testing exercises over the years? I'm curious what tools
> are available to help discover bugs.
>
Simplicity is Plan 9's most relevant trait here, but that's where you
draw the line. If anyone feels like finding possible security holes in
the Plan 9 or the 9front kernels, they have to have very strong
motivation to do it. In general that motivation is spelled M-O-N-E-Y
and no one is likely to find the 9 flavours worthy of a big lump of
that resource.
My opinions, of course.
Lucio.
next prev parent reply other threads:[~2018-09-02 18:16 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-02 16:31 Chris McGee
2018-09-02 16:52 ` hiro
2018-09-03 4:07 ` Lucio De Re
2018-09-03 12:40 ` Chris McGee
2018-09-03 17:58 ` Ethan Gardener
2018-09-04 10:51 ` Lucio De Re
2018-09-04 11:33 ` Ethan Gardener
2018-09-04 11:41 ` Chris McGee
2018-09-02 18:16 ` Lucio De Re [this message]
2018-09-02 19:18 ` Steve Simon
2018-09-02 19:21 ` Iruatã Souza
2018-09-03 1:03 ` Charles Forsyth
2018-09-03 2:03 ` Skip Tavakkolian
2018-09-04 23:17 ` Charles Forsyth
2018-09-04 23:30 ` Tyga
2018-09-05 2:29 ` Chris McGee
2018-09-05 11:23 ` Dave MacFarlane
2018-09-05 11:42 ` Chris McGee
2018-09-05 13:35 ` Ethan Gardener
2018-09-05 15:38 ` Iruatã Souza
2018-09-05 23:59 ` Chris McGee
2018-09-06 0:32 ` Bakul Shah
2018-09-06 3:40 ` Lucio De Re
2018-09-06 11:41 ` Chris McGee
2018-09-06 13:37 ` Ethan Gardener
2018-09-06 17:48 ` Richard Miller
2018-09-06 19:08 ` Skip Tavakkolian
2018-09-06 21:21 ` Chris McGee
2018-09-07 8:32 ` Richard Miller
2018-09-05 3:25 ` Ori Bernstein
2018-09-05 8:19 ` Ethan Gardener
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=CAJQ9t7j0wOtcVzZqwndo1JN2zmxb_mBB+8EaPdTPMODsMWMf4g@mail.gmail.com \
--to=lucio.dere@gmail.com \
--cc=9fans@9fans.net \
/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.
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 NNTP newsgroup(s).