From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] hacking issue: memory resizing
Date: Fri, 9 Sep 2005 09:59:38 -1000 [thread overview]
Message-ID: <Pine.BSI.4.61.0509090951110.20507@malasada.lava.net> (raw)
In-Reply-To: <4321A7E3.1040106@lanl.gov>
On Fri, 9 Sep 2005, Ronald G Minnich wrote:
> My impression in general is that the device stuff in Plan 9 is not terribly
> dynamic -- not surprising, given the time in which the code was written.
This brings up something I've been wondering about lately. Plan 9 was
written for a particular environment (file server, cpu servers, many
terminals). It works well there but obviously lacks some features that a
more "modern" environment might desire. You hear it sometimes on this
mailing list "I want to do so and so." "well, so and so doesn't really
work well, remember the typical setup is a fileserver, cpu servers and
terminals."
So the big question here is -- what would a more modern environment be,
and what could plan9 (or a system like it) do to fit in better. Plan B
looks like its addressing this issue in one sense (although perhaps not in
the type of environment I would typically use computers in today).
I think this "hot swappable devices and services" thread is one instance
of grappling with this larger issue. What are the other big problems out
there and what environment do people think is reasonable? Seems like
everyone has several fast machines, many of them mobile, often being
disconnected from one network and attached to another (or used
disconnected). Often people want a filesystem and cpu server on their
portable platform. There are lots of small ultra-mobile platforms. Energy
use is more a concern than it was before.
Tim Newsham
http://www.lava.net/~newsham/
next prev parent reply other threads:[~2005-09-09 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-07 15:45 Ronald G Minnich
2005-09-07 15:59 ` Francisco Ballesteros
2005-09-07 18:09 ` Ronald G Minnich
2005-09-08 11:50 ` Dave Lukes
2005-09-08 15:25 ` Ronald G Minnich
2005-09-09 14:52 ` erik quanstrom
2005-09-09 15:18 ` Ronald G Minnich
2005-09-09 15:31 ` jmk
2005-09-09 18:04 ` erik quanstrom
2005-09-09 18:09 ` jmk
2005-09-09 18:14 ` Eric Van Hensbergen
2005-09-09 19:06 ` Ronald G Minnich
2005-09-09 19:59 ` Tim Newsham [this message]
2005-09-09 20:46 ` Francisco Ballesteros
2005-09-10 2:16 ` Brian L. Stuart
2005-09-10 21:41 ` Francisco Ballesteros
2005-09-11 2:11 ` Brian L. Stuart
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=Pine.BSI.4.61.0509090951110.20507@malasada.lava.net \
--to=newsham@lava.net \
--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).