From: Russ Cox <russcox@gmail.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] fs(3) problem (kernel)
Date: Tue, 13 Apr 2004 09:16:57 -0700 [thread overview]
Message-ID: <0A366BA7.3FF2505E@mail.gmail.com> (raw)
In-Reply-To: <23a7eee254996cbcb2d1c1d04463e467@plan9.escet.urjc.es>
Before you start hooking up serial cables, download the
new devfs.c from sources. I'm sure it fixes your problem.
I ran into this a month ago. The error stack when you
get to this is big enough that it scrolls way off the screen.
Russ
next prev parent reply other threads:[~2004-04-13 16:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <86smf8lye7.fsf@menkar.cifrid.net>
[not found] ` <0f0c7449becb54d6b914b4450f775d57@plan9.ucalgary.ca>
2004-04-13 15:32 ` Artur Meski
2004-04-13 15:46 ` andrey mirtchovski
2004-04-13 15:46 ` Fco.J.Ballesteros
2004-04-13 16:16 ` Russ Cox [this message]
2004-04-13 20:09 ` Artur Meski
2004-04-13 22:25 ` Russ Cox
2004-04-14 9:13 ` Artur Meski
2004-04-19 10:04 Artur Meski
2004-04-19 10:30 ` Fco.J.Ballesteros
2004-04-19 15:04 ` Russ Cox
2004-04-20 1:17 ` splite
-- strict thread matches above, loose matches on Subject: below --
2004-04-13 7:05 Artur Meski
2004-04-13 8:43 ` Geoff Collyer
2004-04-13 10:13 ` Artur Meski
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=0A366BA7.3FF2505E@mail.gmail.com \
--to=russcox@gmail.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).