From: Adriano Verardo <a.verardo@tecmav.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Diskless cpu servers
Date: Fri, 9 Jun 2006 16:41:46 +0200 [thread overview]
Message-ID: <448988AA.8070006@tecmav.com> (raw)
In-Reply-To: <14ec7b180606081735h1019f5e6rbc81a6507945548b@mail.gmail.com>
andrey mirtchovski wrote:
> i've modified libauth to add a cmos device as nvram in the past... you
> can just go with it and not worry about sending a patch, unless you
> think it's valuable :)
>
>
The solution I found its really trivial. Instead, the problem I'm dealig
with could be interesting
for the community.
I think that Plan9 could be effectively used in industrial automation
systems
to coordinate leaf nodes devotes, for example, to data acquisition.
There are many situations in which real time is not a true constraint.
Thanks to the Plan9 design it should be easier to share
information among
graphical monitoring stations etc etc etc.
The typical scenario is: many very small (486/P100) acq. (leaf) nodes,
mix of
new and obsolete HW, strict constraint about budget, ....
So I built a cluster of very small (chep and old) CPUs (motherboards+acq
dev+eth)
and I'm trying to have them up and running just turning them on without
human intervention
(they could be a lot and distributed in a large area) and downloading a
small Plan9.
I would like not to have many customized kernels. Probably to have the
nvram info embedded in the kernel, in such a particular scenario, could be
a good solution.
I'm also looking at Plan9 as a platform for distributed computing on
a company network. Really some of my clients have networks of
hundreds of modern PCs that don't work in the night ...
But this is another story
Adriano
next prev parent reply other threads:[~2006-06-09 14:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-09 0:31 Adriano Verardo
2006-06-09 0:35 ` andrey mirtchovski
2006-06-09 14:41 ` Adriano Verardo [this message]
2006-06-09 4:13 ` Ronald G Minnich
[not found] ` <000b01c68b7b$503cadb0$14aaa8c0@utelsystems.local>
2006-06-09 7:58 ` "Nils O. Selåsdal"
2006-06-09 13:02 ` Ronald G Minnich
2006-06-09 13:09 ` Charles Forsyth
2006-06-09 13:23 ` Ronald G Minnich
2006-06-09 13:27 ` Charles Forsyth
2006-06-09 14:43 ` Ronald G Minnich
2006-06-09 13:42 ` Adriano Verardo
2006-06-09 13:53 ` Federico G. Benavento
2006-06-09 9:22 ` Steve Simon
2006-06-09 10:53 ` Charles Forsyth
2006-06-09 13:28 ` Adriano Verardo
2006-06-09 13:03 ` Ronald G Minnich
2006-06-10 18:32 ` Adriano Verardo
2006-06-09 14:30 jmk
2006-06-09 16:54 ` Dave Lukes
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=448988AA.8070006@tecmav.com \
--to=a.verardo@tecmav.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).