mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tracy Smith <tlsmith3777@gmail.com>
To: BILL ENGVALD <bengvald@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [feature request] Linux should never break, it should rebuild/repair itself automatically
Date: Fri, 1 Dec 2017 16:53:03 -0600	[thread overview]
Message-ID: <6F82B3F8-2C19-4AF0-8195-30D5A0F8AF3D@gmail.com> (raw)
In-Reply-To: <CAP+WZ=R8w85MuiX4b_REaLnp-5Fq6huPWCYTQEAiWoBjZ4KfoQ@mail.gmail.com>

Being nice but this sounds like a contradiction if not an oxymoron. 

Explain how a kernel or OS can be completely stable while having memory failures, general hardware failures, hacking, etc.  C++ is not the best language for writing operating systems. IBM and Apple attempted this with the Taligent OS and it became spaghetti code. Similarly, the Chorus OS was C++ and no longer commercial often criticized for performance issues.

You seem to be asking for a redundancy or robust error recovery mechanism in the kernel, which is what watch dog timers and graceful shutdown is intended to provide, as well as any failover features, that a user might introduce. 

A fault tolerance mechanism discussion might be the focus of the discussion instead of complete stability in the face of gross hardware failures and endless hacking by the NSA, CIA, and FBI lol.

“I would like it if Linux became
completely stable regardless of memory failures, general hardware
failures, hacking, etc.”

Sent from my iPhone

> On Dec 1, 2017, at 4:25 PM, BILL ENGVALD <bengvald@gmail.com> wrote:
> 
> I would like it if Linux became
> completely stable regardless of memory failures, general hardware
> failures, hacking, etc.

  reply	other threads:[~2017-12-01 22:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-01 22:25 BILL ENGVALD
2017-12-01 22:53 ` Tracy Smith [this message]
2017-12-04  1:13 ` Casey Schaufler

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=6F82B3F8-2C19-4AF0-8195-30D5A0F8AF3D@gmail.com \
    --to=tlsmith3777@gmail.com \
    --cc=bengvald@gmail.com \
    --cc=linux-kernel@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®