From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] cpu(1) design...
Date: Fri, 9 Nov 2007 09:40:30 -0500 [thread overview]
Message-ID: <509071940711090640y7dd8f2d7u1605033984cacde3@mail.gmail.com> (raw)
In-Reply-To: <691e7ca02963cc4348bfb160ec4357de@quintile.net>
On 11/9/07, Steve Simon <steve@quintile.net> wrote:
// was there ever any thought that cpu could/should put you
// onto the least loaded machine in your authdom...
That seems more a server function than a client function to me; thus,
cpu(1) would be the wrong place to do it. I'd rather the servers in
some cluster figure out amongst themselves who handles a given call,
rather than the client having to do some sort of polling or inquiry.
Also, that keeps a more consistent user experience.
// ...is the idea that you would only want to cpu(1) to another
// machine because of the services or network topology you
// (as a human) want rather than just to find more grunt.
Certainly originally cpu(1) was frequently used simply to get to a
bigger machine. That's the way many of the early docs describe its
use, and was also the practice at the Labs a decade ago. This use has
become less common (at least for me) as terminals become so much more
powerful.
Wanting to get at particular resources is also a valid reason, of
course, although in my usage import and friends more often serve that
need.
// why does cpu not have a default argument?
I'm not sure I follow what you're asking for here. $cpu *is* the
default; if you want something else, you can give it.
Anthony
next prev parent reply other threads:[~2007-11-09 14:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 12:50 Steve Simon
2007-11-09 14:40 ` Anthony Sorace [this message]
2007-11-09 14:45 ` roger peppe
2007-11-09 14:55 ` Anthony Sorace
2007-11-09 15:33 ` Steve Simon
2007-11-09 15:46 ` ron minnich
2007-11-09 15:57 ` erik quanstrom
2007-11-09 14:52 ` erik quanstrom
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=509071940711090640y7dd8f2d7u1605033984cacde3@mail.gmail.com \
--to=anothy@gmail.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).