From: lyndon@orthanc.ca (Lyndon Nerenberg)
Subject: [TUHS] Charles Forsyth on putting Unix on a diet.
Date: Fri, 27 Oct 2017 19:42:28 -0700 [thread overview]
Message-ID: <34B45923-EA5D-47C9-BF73-90AECEB87171@orthanc.ca> (raw)
In-Reply-To: <921D6FFC-DD60-406F-B90E-EC40DB638624@orthanc.ca>
> On Oct 27, 2017, at 7:34 PM, Lyndon Nerenberg <lyndon at orthanc.ca> wrote:
>
> But if you try to turn Plan9 into a lean UNIX, you lose everything that Plan9 advocates. In particular, I don't see how you can possibly integrate namespaces into UNIX in any meaningful way. Without those, it's no longer Plan9, and therefore a pointless endeavour.
But as a thought experiment, I have long wondered how one might approach the UNIX kernel with the view of removing ioctl(2). What would the aftermath look like? That's probably the most invasive attack Plan9 could take on UNIX. It would be very interesting to see what falls out. It might be practical to attempt this with 10th Edition, just to see ...
--lyndon
next prev parent reply other threads:[~2017-10-28 2:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-27 10:36 Noel Chiappa
2017-10-27 13:03 ` Clem Cole
2017-10-27 13:23 ` Steve Nickolas
2017-10-27 21:51 ` Andy Kosela
2017-10-27 23:04 ` Larry McVoy
2017-10-27 23:15 ` Steve Simon
2017-10-27 23:39 ` Tim Bradshaw
2017-10-28 2:00 ` Bakul Shah
2017-10-28 2:34 ` Lyndon Nerenberg
2017-10-28 2:42 ` Lyndon Nerenberg [this message]
2017-10-28 6:38 ` Bakul Shah
2017-10-27 21:43 ` Dave Horsfall
-- strict thread matches above, loose matches on Subject: below --
2017-10-28 13:11 Norman Wilson
2017-10-27 21:30 Norman Wilson
2017-10-27 22:49 ` Chris Torek
2017-10-26 14:57 Doug McIlroy
2017-10-26 22:07 ` George Michaelson
2017-10-25 2:51 Dan Cross
2017-10-25 3:14 ` Larry McVoy
2017-10-26 17:27 ` Larry McVoy
2017-10-26 22:12 ` George Michaelson
2017-10-27 3:49 ` Steve Nickolas
2017-10-27 6:55 ` arnold
2017-10-27 7:30 ` Derek Fawcus
2017-10-27 9:44 ` David Arnold
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=34B45923-EA5D-47C9-BF73-90AECEB87171@orthanc.ca \
--to=lyndon@orthanc.ca \
/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).