9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Fariborz "Skip" Tavakkolian fst@real.com
Subject: [9fans] Re: Anyone still running plan9?
Date: Tue, 26 Aug 1997 12:39:26 -0700	[thread overview]
Message-ID: <19970826193926.B11uiVThQyxXL-2uJ3PTQW7C7QYeBEEtL1gxjqjGH7w@z> (raw)

At 01:41 PM 8/26/97 -0500, you wrote:
>On Mon, 25 Aug 1997, David Hogan wrote:
>
>> Michel Oosterhof wrote:
>> > cwr@cts.COM (Will Rose) writes:
>> > >Michel Oosterhof (kirth@cal044204.student.utwente.NL) wrote:
>> > >: Hello, to whoever might read this.  Is anyone still running plan9?
>> > >: Further more, is someone still working on the UNIX ports of several
>> > >: plan9 utilities? (the rc shell, the 9wm (8 1/2) window manager, etc?
>>
>> I run Plan 9 at home.  The company I work for uses Plan 9.  `<gasp!>'
>> I think we're the only one ;-)
>>
>> > >Me.  And I don't think I've seen a post in this group for the last
>> > >3-4 months - I assumed the distribution was screwed.
>>
>> Well, it used to be bidirectionally gatewayed with the 9fans list;
>> I don't think this is happening any more.  I'm cc-ing this to 9fans
>> for comment/elucidation.
>>
>> > 9wm is a clone of 8 1/2, and runs on linux too, I'm using it at the
>> > moment. (1.2pre version).
>>
>> I guess I should do another release of 9wm one of these days.  It's
>> been ``1.2pre'' for over a year now ;-)  I guess I should just say,
>> well, that _was_ 1.2, and here's 1.3.  Though, there aren't that
>> many changes that I've made -- a few bug fixes.  Might be time for
>> a ``maintenance release''.  I'm such a procrastinator...
>>
>
>It really irks me a little that so many people want *nix ports of Plan 9's
>window manager, or editor, etc... but nobody wants to take the really
>great ideas.  WHy won't somebody take things like the namespacing stuff,
>the 9P and IL protocols, the fileserver/cpuserver/terminal concepts... all
>the good "internals" of Plan 9 and make an effort to bring those ideas
>into modern freeware *nix clones.  Merge it into Linux, or NetBSD, or
>HURD....   That would be a much more worthwhile effort.
>

No one does it, perhaps for the same reasons that compelled the Labs folk to
start with a clean slate.

>Brandon
>
>





             reply	other threads:[~1997-08-26 19:39 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-26 19:39 Fariborz [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-08-29 17:59 ozan
1997-08-29 15:50 Scott
1997-08-29 15:34 Brandon
1997-08-28 13:56 Steve_Kilbane
1997-08-28 13:46 Boyd
1997-08-28 13:00 Michel
1997-08-28  1:33 Scott
1997-08-27  8:32 Will
1997-08-27  8:32 Bengt
1997-08-27  8:32 Gary
1997-08-27  8:11 Boyd
1997-08-27  7:15 Steve_Kilbane
1997-08-27  4:11 Gary
1997-08-26 18:41 Brandon
1997-08-26  0:55 Martin
1997-08-25 22:34 David
1997-08-25 21:56 Scott
1997-08-25 21:46 David
1997-08-22 17:01 Tim
1997-08-22 15:57 Michel
1997-08-22 13:30 Will
1997-08-22  9:30 D.M.Pick

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=19970826193926.B11uiVThQyxXL-2uJ3PTQW7C7QYeBEEtL1gxjqjGH7w@z \
    --to=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).