9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Ethan Gardener <eekee57@fastmail.fm>
To: 9fans@9fans.net
Subject: Re: [9fans] plan9port : complete system : kernel : freebsd || linux ?
Date: Tue,  2 Oct 2018 18:14:08 +0100	[thread overview]
Message-ID: <1538500448.2470811.1528100136.1AAB892D@webmail.messagingengine.com> (raw)
In-Reply-To: <CAG2UyHov1knakZF1fPCHHj4rarCa17reDK0=6270o8jru499TA@mail.gmail.com>

On Tue, Oct 2, 2018, at 3:41 PM, Dave MacFarlane wrote:
> What do you mean by "a complete, installable system for plan9ports"?

That's my question too!

> If you mean one that uses p9p in place of gnu utils, that's something
> I've thought about
> trying to do before, but I'd suggest taking it one step further and
> seeing if you could use
> a 9p root filesystem and see how far you can take the per process
> namespaces of Linux
> to make it feel like Plan 9. (AFAIK, that wouldn't be possible with
> NetBSD or FreeBSD, but
> I might be mistaken..)

I had a bit of a go at the shell tools side of things.  It was fun in a way, but I won't pretend the result was as usable as Plan 9, never mind Linux.  It wasn't worth continuing to the point where experimenting with per process namespaces might become interesting.  The same goes for making use of Linux's interesting clone() system call, which afaik close to rfork().

It was just an exercise.  I wasn't expecting too much out of it because I've experimented with minimal Linux before, running LFS from 2001 to 2003 and being involved with a source-based Linux distribution from 2004 to about 2009.  My conclusion was so much interesting software wants the whole bloatware circus that to do without it requires becoming a 1-man patching machine.  This goes all the way into the shell.  A surprising lot of software needs the shell to be the Bourne shell and the various utilities to have POSIX-specified options and behave in POSIX-specified ways.  P9P utilities don't do that.  I also got the idea that the days of hobbyist-maintained Linux distributions are over, that it takes a lot of dedication or a large team.  I personally resolved to use bloatware without paying too much attention to it for "modern" software, and to have my fun with what I call 'island systems' -- not existing to provide services for modern software but rather little universes in themselves.  They can be hosted or emulated, or run on old hardware, I don't care so long as they're not going to stop working or break programs I wrote at the drop of a hat.  P9P could be considered an island system in itself, old operating systems and hardware too, but my current primary choice of island system is Forth.

If, on the other hand, you basically want Plan 9, using Linux as a driver layer, there have been multiple attempts over the years, some with corporate or academic backing, but none of them seem to have worked out.  The guy behind most of them eventually moved on to writing an actual operating system influenced by Plan 9.

-- 
Progress might have been all right once, but it has gone on too long -- Ogden Nash



  reply	other threads:[~2018-10-02 17:14 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-02 11:30 Mayuresh Kathe
2018-10-02 12:01 ` Lucio De Re
2018-10-02 12:11   ` Mayuresh Kathe
2018-10-02 12:43     ` Lucio De Re
2018-10-02 14:26       ` Mayuresh Kathe
2018-10-02 14:32 ` Roderick
2018-10-02 14:43   ` hiro
2018-10-02 14:40     ` Roderick
2018-10-02 16:35   ` Iruatã Souza
2018-10-02 14:41 ` Dave MacFarlane
2018-10-02 17:14   ` Ethan Gardener [this message]
2018-10-02 17:22   ` Bakul Shah
2018-10-02 17:26     ` Steve Simon
2018-10-02 18:10       ` hiro
2018-10-02 19:18         ` Kurt H Maier
2018-10-03 21:23 ` Aram Hăvărneanu
2018-10-04  3:44   ` Mayuresh Kathe
2018-10-04  8:01     ` Ethan Gardener
2018-10-05  1:44     ` Bakul Shah
2018-10-04  3:49 sl
2018-10-04  5:13 ` Mayuresh Kathe
2018-10-04  5:32   ` Iruatã Souza
2018-10-04  7:38 ` Aram Hăvărneanu
2018-10-04  7:50   ` Rui Carmo
2018-10-04  8:39     ` Ethan Gardener
2018-10-04  8:50     ` Kurt H Maier
2018-10-04 10:33       ` Rui Carmo
2018-10-04 16:31         ` Iruatã Souza
2018-10-04 17:00           ` hiro
2018-10-04 18:02             ` Steve Simon
2018-10-04 18:34               ` Aram Hăvărneanu
2018-10-04 19:21               ` Steven Stallion
2018-10-04 19:41                 ` Skip Tavakkolian
2018-10-04 20:20                   ` hiro
2018-10-04 20:57                     ` Steven Stallion
2018-10-04 20:36                   ` Alexander Keller
2018-10-04 21:00                     ` hiro
2018-10-04 20:55                 ` Aram Hăvărneanu
2018-10-04 17:42         ` Kurt H Maier
2018-10-04 21:56 sl

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=1538500448.2470811.1528100136.1AAB892D@webmail.messagingengine.com \
    --to=eekee57@fastmail.fm \
    --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).