From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Re: Kernel failure - i486
Date: Thu, 22 Jan 2004 12:56:34 +0000 [thread overview]
Message-ID: <d5a28a2a70fa441479756dd97d4f62bf@terzarima.net> (raw)
In-Reply-To: <56180b256fc8cc8d05e5b24091071cbf@terzarima.net>
>>but now it's used in port (which is the call i think is failing)
and indeed it was that call that was failing
next prev parent reply other threads:[~2004-01-22 12:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-22 11:47 [9fans] " Lucio De Re
2004-01-22 11:52 ` [9fans] " Lucio De Re
2004-01-22 12:52 ` Charles Forsyth
2004-01-22 12:56 ` Charles Forsyth [this message]
2004-01-22 13:54 ` Lucio De Re
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=d5a28a2a70fa441479756dd97d4f62bf@terzarima.net \
--to=forsyth@terzarima.net \
--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).