From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: we need help...
Date: Tue, 28 Oct 2003 20:43:22 +0000 [thread overview]
Message-ID: <28e932c0976b7937d4870192f66f3779@caldo.demon.co.uk> (raw)
In-Reply-To: <62856.135.214.42.162.1067367520.squirrel@www.infernopark.com>
[-- Attachment #1: Type: text/plain, Size: 96 bytes --]
it's the same version of charon, but emu and its
applications can disguise themselves better.
[-- Attachment #2: Type: message/rfc822, Size: 3340 bytes --]
From: <vdharani@infernopark.com>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: we need help...
Date: Tue, 28 Oct 2003 13:58:40 -0500 (EST)
Message-ID: <62856.135.214.42.162.1067367520.squirrel@www.infernopark.com>
> roger has been working on charon running in a Plan 9
> window (ie, using Plan 9's /dev/draw directly).
> it seemed to work fine--unsurprisingly, since the
> models are currently the same--and once we've installed something
> suitable to replace the hack his script(s) relied on (that i removed
> yesterday), we'll parcel it up somehow so that anyone can use it.
> he hasn't come in today so i haven't been able to discuss
> possible replacements for the hack, but it shouldn't be too long.
i am not able to understand. how is it any different from charon running on
inferno? if it is the same, why are we doing it like this? and is it that
this will leave us two versions of charon?
thanks
dharani
next prev parent reply other threads:[~2003-10-28 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-20 16:15 steve-simon
2003-10-20 20:27 ` a
2003-10-27 17:26 ` David Presotto
2003-10-28 12:40 ` matt
2003-10-28 13:59 ` ron minnich
2003-10-28 14:10 ` David Presotto
2003-10-28 16:15 ` ron minnich
2003-10-28 16:25 ` Charles Forsyth
2003-10-28 18:58 ` vdharani
2003-10-28 20:43 ` Charles Forsyth [this message]
2003-10-28 16:08 ` C H Forsyth
2003-10-28 16:38 ` matt
2003-11-11 17:12 ` [9fans] mothra Richard Miller
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=28e932c0976b7937d4870192f66f3779@caldo.demon.co.uk \
--to=forsyth@caldo.demon.co.uk \
--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).