9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Okay, who's been playing with the cheese wiz?
Date: Sun,  9 Feb 2003 16:51:01 -0500	[thread overview]
Message-ID: <fb9812bf58e9e8395b3b3635a229e708@plan9.bell-labs.com> (raw)
In-Reply-To: <200302092120.h19LKBM29830@augusta.math.psu.edu>

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.

I changed lib9p to do a few more checks that the
client code is behaving, and your execnet crash
shows that lib9p thinks execnet is not behaving.
It turns out that actually lib9p is not behaving -- I was
trying to clean up this particular detail (whether a
walk function should set both fid->qid and *qid),
because it always confuses me, and I got confused.
I just put out a new srv.c that makes reasonable
demands of the clients.

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.

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.

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.

Russ



  reply	other threads:[~2003-02-09 21:51 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 [this message]
2003-02-10 16:24   ` Dan Cross
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=fb9812bf58e9e8395b3b3635a229e708@plan9.bell-labs.com \
    --to=rsc@plan9.bell-labs.com \
    --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).