9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Mike Haertel <mike@ducky.net>
To: 9fans@cse.psu.edu
Subject: [9fans] getting at Windows files from VMware-hosted Plan 9
Date: Wed,  1 May 2002 17:59:46 -0700	[thread overview]
Message-ID: <200205020059.g420xkvQ012820@ducky.net> (raw)

First of all, here is a cute 1-liner for running u9fs without inetd
(useful if your local system administrator refuses to run u9fs from inetd,
or you hate rhosts-style authentication, or whatever...)

% ssh myname@remotehost u9fs -a none -u myname <[0=1] | echo 0 > /srv/remotehost
% mount /srv/remotehost /n/kremvax

I thought people might be interested in how I'm using this: I have an ssh
daemon running on my Windows box at work, courtesy of Cygwin.  I run Plan 9
under VMware on the same box.

I ported u9fs to Windows, again courtesy of Cygwin.  (Main changes: Cygwin has
no setre[ug]id(), no ruserok(), no <inttypes.h>, and no pread()/pwrite().
Diffs available upon request.)

So, in my VMware-hosted Plan 9 running under Windows, I do the following:

% ssh Administrator@windows u9fs -a none -u Administrator <[0=1] | echo 0 > /srv/windows
% mount /srv/windows /n/kremvax
% bind /n/kremvax/cygdrive/c /n/c

and thus I can use /n/c from VMware to look at the windows partition, just
as if Plan 9 were running on the bare hardware.

Moreover, this hack allows Plan 9 to see the contents of any SMB file server
that the host Windows environment can access.  Very useful if you're stuck
in a mixed network of evil operating systems.


             reply	other threads:[~2002-05-02  0:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-02  0:59 Mike Haertel [this message]
2002-05-02  1:47 Russ Cox
2002-05-02 20:20 ` Mike Haertel
2002-05-02  1:57 rob pike, esq.
2002-05-02 20:39 Scott Schwartz

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=200205020059.g420xkvQ012820@ducky.net \
    --to=mike@ducky.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).