9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Steve Simon" <steve@quintile.net>
To: 9fans@9fans.net
Subject: Re: [9fans] fd2path and devsrv
Date: Thu, 20 Nov 2008 12:59:38 +0000	[thread overview]
Message-ID: <cf487e1c4b1f0748df24ed1694fec287@quintile.net> (raw)
In-Reply-To: <df49a7370811200144v46e2e2e5n7ba02d84105f357c@mail.gmail.com>

The dos(1) command I wrote (in the style of cpu(1) but attaches to Windows boxen)
uses a configuration file describing how the windows directories are
mounted (using cifs(1)) on plan9. It also reads /proc/$pid/namespace to
learn of any additional mounts so it can reliable translate plan9 paths
to windows ones and back again.

for example, I mount my home directory on the Windows server at $home/work in plan9
and then add various useful parts of the windows filesystem under that.

When I cd into one of these directories and run dos(1) it can then work out where
it should chdir(2) to on the windows box before starting cmd.exe.

Aditionally dos(1) keeps track of the current directory on windows and updates
/dev/wdir so the plumber and rio (for file name completeion) work as expected
even on the output of the windows DIR command.

Overall its a bit string and sticky-tape but it works and and you cannot
see the joins.

-Steve



  reply	other threads:[~2008-11-20 12:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-19 17:45 Roman V. Shaposhnik
2008-11-19 19:36 ` Francisco J Ballesteros
2008-11-20  1:37   ` Roman V. Shaposhnik
2008-11-20  1:41     ` erik quanstrom
2008-11-20  2:56       ` Roman V. Shaposhnik
2008-11-20  2:55         ` erik quanstrom
2008-11-20  3:31           ` Roman Shaposhnik
2008-11-20  3:32             ` erik quanstrom
2008-11-20  3:57               ` Roman Shaposhnik
2008-11-20  4:14                 ` erik quanstrom
2008-11-20  5:05                   ` Roman Shaposhnik
2008-11-20  9:44   ` roger peppe
2008-11-20 12:59     ` Steve Simon [this message]
2008-11-20 13:50       ` roger peppe

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=cf487e1c4b1f0748df24ed1694fec287@quintile.net \
    --to=steve@quintile.net \
    --cc=9fans@9fans.net \
    /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).