9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usage of CPU server
Date: Mon,  6 Nov 2000 08:05:21 -0500	[thread overview]
Message-ID: <20001106130538.ED79F199EF@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 83 bytes --]

The discussions I was having at the time were with the System V people.

-rob


[-- Attachment #2: Type: message/rfc822, Size: 1762 bytes --]

From: "Douglas A. Gwyn" <DAGwyn@null.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usage of CPU server
Date: Mon, 6 Nov 2000 09:44:05 GMT
Message-ID: <3A0604E3.9E11CCCB@null.net>

rob pike wrote:
> Sure, the environment gets big; so give it more space.

How?  I think you're spoiled by being in a position to
modify the operating system.  For most commercial OSes
we don't have that luxury, and therefore design choices
we make may well reflect the reality we're stuck with.

             reply	other threads:[~2000-11-06 13:05 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-06 13:05 rob pike [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-11-03 14:56 rob pike
2000-11-03 16:55 ` Elliott Hughes
2000-11-03 18:54   ` Boyd Roberts
2000-11-06  9:44 ` Douglas A. Gwyn
2000-11-02 18:02 rob pike
2000-11-03 14:22 ` Douglas A. Gwyn
2000-11-02 10:20 forsyth
2000-11-02 10:02 nigel
2000-11-02 16:03 ` Rick Hohensee
2000-11-02 16:27   ` Boyd Roberts
2000-11-01  9:53 okamoto
2000-11-01 10:03 ` Lucio De Re
2000-11-01 14:46   ` Rick Hohensee
2000-11-01 15:19     ` nigel
2000-11-02  1:06       ` Rick Hohensee
2000-11-02  1:24         ` Boyd Roberts
2000-11-02  8:21           ` Rick Hohensee
2000-11-02 17:44           ` Douglas A. Gwyn
2000-11-02  7:55         ` Steve Kilbane
2000-11-02 11:25           ` Boyd Roberts
2000-11-01  9:08 forsyth
2000-11-01  7:27 okamoto
2000-11-01  8:21 ` Lucio De Re
2000-11-01  6:03 Russ Cox
2000-11-01  4:09 okamoto

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=20001106130538.ED79F199EF@mail.cse.psu.edu \
    --to=rob@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /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).