| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Fri, 1 Dec 2017 16:53:03 -0600 From: Tracy Smith <tlsmith3777@...il.com> To: BILL ENGVALD <bengvald@...il.com> Cc: linux-kernel@...r.kernel.org Subject: Re: [feature request] Linux should never break, it should rebuild/repair itself automatically 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@...il.com> wrote: > > I would like it if Linux became > completely stable regardless of memory failures, general hardware > failures, hacking, etc.
Powered by blists - more mailing lists