From: YAMANASHI Takeshi uncover@campus.cc.titech.ac.jp
Subject: [9fans] plan9 on Sparc IPC ?
Date: Thu, 30 Apr 1998 09:59:28 +0900 [thread overview]
Message-ID: <19980430005928.nPNsMKu401thcDZuwl9m3CiXUm5y2uIOrkuQkPNOPdY@z> (raw)
> From: Elliott.Hughes@genedata.com
> > It's encouraging :-) that other people have the same
> > trouble.(Thanks, Andrew)
>
> Andy doesn't really have a problem. I think the behaviour he's seeing is
> the documented behaviour. It might be unfortunate, but that's not the same!
Excuse me, It's my mistake. I misread Andy's mail.
Thank you again, Andy and Elliott too, I can see
another way now. I will try to remove all SCSI
related codes from 9ss.
My IPC has following numbers:
Serial# 2112840
CPU board is labelled 501 1870 020206
It seems somewhat older than Andrew's IPC ?
__
YAMANASHI Takeshi
next reply other threads:[~1998-04-30 0:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-30 0:59 YAMANASHI [this message]
-- strict thread matches above, loose matches on Subject: below --
1998-04-29 7:31 Andrew
1998-04-28 15:12 Dave
1998-04-28 7:30 Elliott.Hughes
1998-04-28 5:04 YAMANASHI
1998-04-27 7:25 Andrew
1998-04-26 15:35 Dave
1998-04-26 12:29 YAMANASHI
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=19980430005928.nPNsMKu401thcDZuwl9m3CiXUm5y2uIOrkuQkPNOPdY@z \
--to=9fans@9fans.net \
/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).