9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: [9fans] p9p on win32?
Date: Tue, 14 Mar 2006 11:32:25 +0000	[thread overview]
Message-ID: <1e9d65c3485c20086ab31b43abc7f35c@quintile.net> (raw)

Hi,

A Longterm project.

I would like to get p9p going on win32, I have no real need for /dev/draw,
I always rsh into win32, though I can see others would want it.

I assume the best compiler to use is mingw as knows about at least some plan9-isms

The big issue is I would also like to get a cpu server going.

Currently I use rsh which doesn't pass keyboard interrupt to the remote host.
I could run openssh under cygwin which would give that functionality and
on-the-wire encryption which is nice these days.

My favorite solution is to use the plan9 cpu protocol. This would allow
me to access files on the local plan9 system, pass interrupts (by reading
/mnt/term/dev/cpunote), and pass the win32 current directory back to plan9
(rc writes to /mnt/term/dev/wdir) so plumbed error messages will open the
correct file in sam/acme.

I would need a 9p client written against stdio, and a port of openssl to provide
the equivilent of pushssl(2), or alternatively if most of p9p is comming acrross
easily I could just use the plan9 code (except that ssl/tls is in the plan9 kernel).

Windows filesystem drivers seem to live in the kernel, which would make debugging them
tiresome, however I have found two frameworks for creating user space synthetic
filesystems on Win32, one creates a local cifs server [1] the other uses a proxy
device driver to allow a psudo filesystem to live in user space [2]. This still
leaves the problem of mounting/unmounting a filesystem on each cpu(1)
connect/disconnect.

Anyone any thoughts?

-Steve

A quick look at the code reveals both of these are pretty darn complex.
[1] http://www.usenix.org/publications/library/proceedings/usenix-nt99/full_papers/almeida/almeida.pdf
[2] http://research.microsoft.com/~galenh/Publications/HuntUsenixNt97.pdf



             reply	other threads:[~2006-03-14 11:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-14 11:32 Steve Simon [this message]
2006-03-14 12:43 ` Anselm R. Garbe
2006-03-14 13:02   ` Axel Belinfante
2006-03-14 13:15     ` Anselm R. Garbe
2006-03-14 13:22       ` Axel Belinfante
2006-03-14 12:48 ` fgergo
2006-03-14 14:15   ` Steve Simon
2006-03-14 13:04 ` Russ Cox
2006-03-17 14:15   ` Derek Fawcus
2006-03-17 18:48     ` LiteStar numnums
2006-03-29  6:46   ` Martin C. Atkins
2006-03-29  8:44     ` quanstro
2006-03-14 13:43 ` John Stalker

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=1e9d65c3485c20086ab31b43abc7f35c@quintile.net \
    --to=steve@quintile.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).