From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Keyboard woes
Date: Fri, 1 Sep 2000 10:16:31 +0900 [thread overview]
Message-ID: <200009010117.VAA25825@cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
I've never seen it while running about two months of Release 3.
I have only one display and keyboard for CPU and file server
and another machine. In most times keyboard is off from the
CPU server...
By the way, thanks for your patch to Alef, now I'm running news
file server written in Alef (by Charles) on Release 3 Plan 9 system.
Yesterday, my release 2 CPU server retired from our office with best
respects from me. That file server was turned off the power, and still
is waiting when I'll meet neccessity of updated release 2 sources.
Kenji
[-- Attachment #2: Type: message/rfc822, Size: 2443 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans mailing list <9fans@cse.psu.edu>
Subject: [9fans] Keyboard woes
Date: Thu, 31 Aug 2000 14:49:12 +0200
Message-ID: <20000831144912.D2399@cackle.proxima.alt.za>
Has anyone else noticed that their i386 CPU server loses the keyboard
altogether?
I've been sharing the same disk on two totally different motherboards,
and the keyboard eventually (it is not clear when, but presumably
after an interval unused) dies altogether.
It could be something here, naturally, and the fact that the CPU
server is not linked to a network may also be significant: another CPU
server that is actually connected is still perfectly functional.
The main difference is that the CPU server that loses the keyboard is
running entirely off its IDE drive, the other off a 2ed fileserver,
the former starts off with graphics, the latter doesn't.
++L
next reply other threads:[~2000-09-01 1:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-09-01 1:16 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-09-01 4:05 okamoto
2000-09-01 3:36 forsyth
2000-08-31 12:49 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=200009010117.VAA25825@cse.psu.edu \
--to=okamoto@granite.cias.osakafu-u.ac.jp \
--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).