From: "Sander van Dijk" <a.h.vandijk@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@9fans.net>
Subject: Re: [9fans] USB keyboard error
Date: Sun, 13 Jul 2008 14:47:47 +0200 [thread overview]
Message-ID: <ba0d3bc70807130547r4bcf1979g2a61a34cb2a3304e@mail.gmail.com> (raw)
In-Reply-To: <17019d32fad3e8c00470b5f79448a209@quanstro.net>
On 7/13/08, erik quanstrom <quanstro@quanstro.net> wrote:
> it seems the prior diagnosis is correct. the cpu kernels
> cpu, cpuf don't have the kbin device built in.
>
> however i'm a little confused. do you start rio automaticly
> on your cpu server?
It seems that pcf doesn't have the kbin device built in either.
Greetings, Sander.
next prev parent reply other threads:[~2008-07-13 12:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 4:48 Matt Adams
2008-07-13 7:39 ` Anthony Martin
2008-07-13 7:52 ` Anthony Martin
2008-07-13 14:45 ` Matt Adams
2008-07-13 11:27 ` erik quanstrom
2008-07-13 12:47 ` Sander van Dijk [this message]
2008-07-13 20:10 ` geoff
2008-07-14 18:44 ` Sander van Dijk
[not found] ` <b2220e2bf18163d7e9e8672e1a2447c1@quanstro.net>
2008-07-13 14:48 ` Matt Adams
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=ba0d3bc70807130547r4bcf1979g2a61a34cb2a3304e@mail.gmail.com \
--to=a.h.vandijk@gmail.com \
--cc=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).