From: "pankaj chauhan" <chauhan_ait@yahoo.co.in>
To: 9fans@cse.psu.edu
Subject: [9fans] how the cpu is exported ?????
Date: Mon, 14 Apr 2003 14:14:35 +0100 [thread overview]
Message-ID: <20030414131435.62151.qmail@web8206.mail.in.yahoo.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 598 bytes --]
hi every body ,
i am new to plan 9 , want to know how exactly the cpu servers provide processing power to the machines on the network ( actually how it is implemented in the operating system ) .
my problem is , what i am getting every where on inter net is : how to use plan 9 , but i am interested in its operating system design and architecture , please tell me from where can i get this thing .
right now i am not the part of mailing list so please reply at my mail id.
thanks ,
Regards,
pankaj chauhan
Catch all the cricket action. Download Yahoo! Score tracker
[-- Attachment #2: Type: text/html, Size: 846 bytes --]
next reply other threads:[~2003-04-14 13:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-14 13:14 pankaj chauhan [this message]
2003-04-21 17:04 ` Russ Cox
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=20030414131435.62151.qmail@web8206.mail.in.yahoo.com \
--to=chauhan_ait@yahoo.co.in \
--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).