9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Tim Newsham <newsham@lava.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Cc: nemo@lsub.org
Subject: Re: [9fans] 9p resource sharing [was: Scanners]
Date: Wed,  9 Dec 2009 13:18:39 -1000	[thread overview]
Message-ID: <Pine.BSI.4.64.0912091315260.13404@malasada.lava.net> (raw)
In-Reply-To: <0EB6A4FC-1626-4F35-8F27-7C2F916EFAB8@lsub.org>

> we found it's a lot easier doing it like
> in the octopus. we'll be happy to
> discuss any of it.

Did you find 9p adequate for the resource sharing you
did or did you have to alter the protocol or augment it
with other protocols?

Did you use the normal plan9 authentication mechanisms or
did you explore other authentication alternatives?  Were
all machines in a shared authentication domain or did you
support multiple authentication domains?

What did you do about machine or resource discovery?
Is there a mechanism to discover when machines or resources
are added or removed from the network?

What papers do you recommend looking at?

Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com



  reply	other threads:[~2009-12-09 23:18 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-26 20:39 Francisco J Ballesteros
2009-12-09 23:18 ` Tim Newsham [this message]
     [not found] <<4B101734.7060102@maht0x0r.net>
2009-11-27 18:50 ` erik quanstrom
     [not found] <<4B0F0F25.7020506@maht0x0r.net>
2009-11-27  2:21 ` erik quanstrom
2009-11-27 18:15   ` matt
     [not found] <<Pine.BSI.4.64.0911261033570.13404@malasada.lava.net>
2009-11-26 20:36 ` erik quanstrom
2009-11-26 20:53   ` ron minnich
2009-11-26 21:04     ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2009-11-26 21:31       ` W B Hacker
2009-11-26 23:33         ` Enrico Weigelt
2009-11-27  5:31           ` W B Hacker
2010-01-13 16:41             ` Enrico Weigelt
2009-11-26 23:28       ` Enrico Weigelt
2009-11-28 13:33     ` Ethan Grammatikidis
2009-11-28 14:28       ` hiro
2009-11-28 15:42         ` Ethan Grammatikidis
2009-11-28 19:17           ` Jorden Mauro
2010-01-05 11:52             ` Enrico Weigelt
2010-01-08 14:44               ` Patrick Kelly
2010-01-08  5:29                 ` LiteStar numnums
2010-01-08 15:29                   ` hiro
2010-01-08 15:52                     ` Patrick Kelly
2010-01-08 19:36                     ` Taj Khattra
2010-01-08 20:03                       ` Eric Van Hensbergen
2010-01-08 21:05                       ` hiro
2010-01-08 16:08                 ` Jorden Mauro
2010-01-08 15:55                   ` Patrick Kelly
2010-01-13 16:36                 ` Enrico Weigelt
2010-01-05 11:49         ` Enrico Weigelt
2009-11-26 23:11   ` Enrico Weigelt
2009-11-26 23:28   ` matt
     [not found] <<Pine.BSI.4.64.0911261017560.13404@malasada.lava.net>
2009-11-26 20:25 ` erik quanstrom
2009-11-26 20:35   ` Tim Newsham
2009-11-26 21:18     ` W B Hacker
2009-11-28 12:51       ` Ethan Grammatikidis
  -- strict thread matches above, loose matches on Subject: below --
2009-11-26  0:07 [9fans] Scanners Charles Forsyth
2009-11-26 20:23 ` [9fans] 9p resource sharing [was: Scanners] Tim Newsham
2009-11-26 20:33   ` Tim Newsham
2009-11-26 23:39   ` Enrico Weigelt
2009-11-27  4:36     ` Tim Newsham
2009-11-27  5:30       ` Enrico Weigelt

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.64.0912091315260.13404@malasada.lava.net \
    --to=newsham@lava.net \
    --cc=9fans@9fans.net \
    --cc=nemo@lsub.org \
    /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).