9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Fco. J. Ballesteros" <nemo@lsub.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Plan9 and resource discovery
Date: Wed, 24 Nov 2004 11:12:56 +0100	[thread overview]
Message-ID: <87a16ff4dce11c9dfb0e8456d661dc84@plan9.escet.urjc.es> (raw)
In-Reply-To: <41A42D1A.7090902@chunder.com>

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

The Plan 9 derivative that I'm using, which we call Plan B,
has all its services `discovered'.

For example, /bin comes from
	mount -V /bin/!$cputype /bin

BTW, this beast can also redirect some I/O devices (eg mouse)
for usage with remote machines.

☺

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

From: Bruce Ellis <brucee@chunder.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] Plan9 and resource discovery
Date: Wed, 24 Nov 2004 17:41:30 +1100
Message-ID: <41A42D1A.7090902@chunder.com>

inferno has virgil, tho it's rarely used in the wild.
i find it good for "anyone out there got a /dev/mathlink?".

brucee

Roman Shaposhnick wrote:

> Just the other day I've been having this hallway conversation where
> I tried to make Plan9 sound as a solution to all the problems 
> (excluding world's hunger, perhaps) and the question that made
> me write this email and humbly ask for your ideas was this:
> "Well, it seems that Plan9 is really good about making *use*
> of resources, but how does it help you *discover* them?".

      reply	other threads:[~2004-11-24 10:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-24  4:05 Roman Shaposhnick
2004-11-24  4:22 ` andrey mirtchovski
2004-11-24 10:15   ` Fco. J. Ballesteros
2004-11-24  6:29 ` Taj Khattra
2004-11-24  6:30   ` boyd, rounin
2004-11-24  6:41 ` Bruce Ellis
2004-11-24 10:12   ` Fco. J. Ballesteros [this message]

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=87a16ff4dce11c9dfb0e8456d661dc84@plan9.escet.urjc.es \
    --to=nemo@lsub.org \
    --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).