From: Steve Simon <steve@quintile.net>
To: 9fans <9fans@9fans.net>
Subject: Re: Posix implementation of Plan 9 cpu(1) (Was: [9fans] Command to set samterm label)
Date: Wed, 21 Jul 2021 22:41:58 +0100 [thread overview]
Message-ID: <57466CDD-17C9-4B44-AE5D-877EFF50935A@quintile.net> (raw)
In-Reply-To: <CAFSF3XNWmzHOYYnmXDWQohCcirqb0yF0s9tVW9kmn03UGpZPEg@mail.gmail.com>
i wrote a cpu like client/server for windows (called dos).
my code and test environment lived on a microsoft smb server. i ran cifs(1) to get access to this from plan9 and sam.
dos(1) allowed me to start an rc(1) running on win32 in the same directory as my current directory on plan9. it also kept my local /dev/wdir up to date with that on windows - massaging paths as needed.
all this allowed me to bounce between windows and plan9 fairly transparently like cpu(1) would on plan9. i could also plumb files i saw and plan9 would do the right thing.
it should use the cpu(1) protocol but i never got round to it - what i have just works.
my current employer uses Macs rather than windows so this has fallen into disuse.
i am happy to share if anyone has a use for it.
-Steve
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T09fcdec9c87bfde4-M90430f1d0d3a94dcd370712f
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
next prev parent reply other threads:[~2021-07-21 21:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 4:52 Lucio De Re
2021-07-19 5:20 ` Michael Misch
2021-07-19 7:13 ` Steve Simon
2021-07-21 3:52 ` Lucio De Re
2021-07-21 14:59 ` Xiao-Yong Jin
2021-07-21 15:11 ` hiro
2021-07-21 16:08 ` Dan Cross
2021-07-21 16:16 ` Xiao-Yong Jin
2021-07-21 16:42 ` Dan Cross
2021-07-21 17:08 ` Xiao-Yong Jin
2021-07-21 17:16 ` Dan Cross
2021-07-21 17:31 ` Xiao-Yong Jin
2021-07-21 17:57 ` Dan Cross
2021-07-21 18:09 ` hiro
2021-07-21 18:11 ` hiro
2021-07-21 21:41 ` Steve Simon [this message]
2021-07-21 17:41 ` hiro
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=57466CDD-17C9-4B44-AE5D-877EFF50935A@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).