9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Louis Beleos <beleos@cs.unr.edu>
To: 9fans@cse.psu.edu
Cc: Steve Simon <steve@savan.demon.co.uk>
Subject: Re: [9fans] Rio panic
Date: Tue, 15 Aug 2000 15:35:11 -0700	[thread overview]
Message-ID: <Pine.SOL.4.05.10008151528500.16416-100000@banyan.cs.unr.edu> (raw)

On Tue, 15 Aug 2000, Steve Simon wrote:

> Hi,
> 
> Before I start delving, I wonder if I have missed an upddate?
> 
> I have the 1st August installation
> 
> I rebuilt the entire system:
> 
> 	mk 'CONF=pc' install
> 
> now rio regularly panics - every 5 mins or so.
> ...

Have you applied the following patch?

 From rob@plan9.bell-labs.com Tue Aug 15 15:36:44 2000
Date: Sun, 30 Jul 2000 10:53:31 -0400
From: rob pike <rob@plan9.bell-labs.com>
Reply-To: 9fans@cse.psu.edu
To: 9fans@cse.psu.edu
Subject: [9fans] rio
Status: RO
X-Status: 

Stupid bug introduced in rio, caused by our attempts to clean up
uses of %.*s.  /sys/src/cmd/rio/xfid.c:508 is missing an argument.
diff /n/dump/2000/0730/sys/src/cmd/rio/xfid.c xfid.c
508c508
< 			sprint(p, "%s/%.*s", w->dir, utfnlen(x->data, cnt));
---
> 			sprint(p, "%s/%.*s", w->dir, utfnlen(x->data, cnt), x->data);

The distributed binary is OK, but if you build from the unfixed
source all hell will break loose.

Mea culpa.  The compiler warns you and in all the furious building
I missed the warning.

-rob




             reply	other threads:[~2000-08-15 22:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-15 22:35 Louis Beleos [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-08-15  9:00 Steve Simon

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=Pine.SOL.4.05.10008151528500.16416-100000@banyan.cs.unr.edu \
    --to=beleos@cs.unr.edu \
    --cc=9fans@cse.psu.edu \
    --cc=steve@savan.demon.co.uk \
    /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).