From: Andrew Warkentin <andreww591@gmail.com>
To: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Celebrating 50 years of Unix
Date: Mon, 14 Oct 2019 19:56:38 -0600 [thread overview]
Message-ID: <CAD-qYGopG00nCB7YAaKLVj1QxCvaRgBkJ95pZNu18KRbHZfgRg@mail.gmail.com> (raw)
In-Reply-To: <8053C456-12E7-478D-A391-BAA0D0D1A7F1@163.com>
On 10/14/19, Caipenghui <Caipenghui_c@163.com> wrote:
> Unix has a history of 50 years. Unix has a tremendous impact on the
> Internet. Is Unix ready for the next computing era?
I don't think conventional Unix (SysV/BSD/Linux) has aged very well at
all. As far as I'm concerned, all "modern" conventional Unices are
basically cargo cult Unix at this point (especially Linux, but I'd
also say it's true of current BSD and SysV). They're just carrying
forward the architecture of late-70s research Unix without really
understanding the design philosophy. The conventional Unix
architecture was fine on a PDP-11, but it doesn't scale well to
larger, more complex systems. A modern OS should be designed with
security and extensibility in mind.
That being said, I believe it is still possible to write a truly
modern OS that is Unix-like and compatible with programs written for
conventional Unix while still being secure and extensible. That's what
I'm doing with the OS I'm writing <https://gitlab.com/uxrt>. It will
be a thoroughly modern OS that will take the Unix philosophy further
than it's ever been taken before (even further than Plan 9 does) and
will be binary compatible with Linux.
prev parent reply other threads:[~2019-10-15 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 23:46 Caipenghui
2019-10-15 1:56 ` Andrew Warkentin [this message]
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=CAD-qYGopG00nCB7YAaKLVj1QxCvaRgBkJ95pZNu18KRbHZfgRg@mail.gmail.com \
--to=andreww591@gmail.com \
--cc=tuhs@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).