From: Dan Cross <cross@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Okay, who's been playing with the cheese wiz?
Date: Mon, 10 Feb 2003 11:24:22 -0500 [thread overview]
Message-ID: <200302101624.h1AGOMM04080@augusta.math.psu.edu> (raw)
In-Reply-To: Your message of "Sun, 09 Feb 2003 16:51:01 EST." <fb9812bf58e9e8395b3b3635a229e708@plan9.bell-labs.com>
> Rob and I fixed some other bugs in acme, but not
> near the code involved in your Edit 1,$d crash.
> I cannot reproduce this.
Hmm; it seems to be related to doing it in a Win window. Maybe
it has to do with win being broken; it doesn't seem to affect other
windows.
> I gave up on execnet a long time ago. It's clunky
> and not clear that the interface should work that
> way. What do you use it for? (I'm just curious.)
> Copy /386/bin/execnet off of sources and you'll
> be happy.
Thanks, that fixed execnet. I'm using it for dialing u9fs on a Unix
machine; for some reason, when I tried srv -e back in the day, it
didn't work. Maybe I should investigate it again.
> It doesn't surprise me that win is broken. I always
> forget to recompile it because it's not in the /sys/src
> tree. rc: note: peterface is an artifact of an old lib9p
> bug that I must have reintroduced. I will have a look.
Okay, thanks.
> I pushed the lib9p changes out on Friday and have
> been slowly recompiling binaries for sources as
> I know they're okay. I'm going crazy trying to keep
> my laptop, emelie (our internal fs), and sources all
> in sync (ironic, I know). You picked an unfortunate
> time to recompile the world. ;-)
>
> Sorry for the trouble.
No problem; it seems I'm the one always causing trouble, anyway. :-)
- Dan C.
next prev parent reply other threads:[~2003-02-10 16:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-09 21:20 Dan Cross
2003-02-09 21:51 ` Russ Cox
2003-02-10 16:24 ` Dan Cross [this message]
2003-02-10 1:07 ` rob pike, esq.
2003-02-18 3:49 ` Russ Cox
2003-02-18 3:55 ` Sam
2003-02-18 4:02 ` Russ Cox
2003-02-18 4:00 ` Dan Cross
2003-02-10 4:19 okamoto
2003-02-10 13:14 rog
2003-02-10 13:36 ` Russ Cox
2003-02-10 17:09 rog
2003-02-10 17:10 ` Russ Cox
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=200302101624.h1AGOMM04080@augusta.math.psu.edu \
--to=cross@math.psu.edu \
--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).