From: John Bradford <john@grabjohn.com>
To: jsimmons@infradead.org (James Simmons)
Cc: rick@sapphire.no-ip.com, linux-kernel@vger.kernel.org
Subject: Re: support for dual independent keyboards in devel kernel?
Date: Wed, 12 Feb 2003 21:33:41 +0000 (GMT) [thread overview]
Message-ID: <200302122133.h1CLXfZI001025@darkstar.example.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0302122113460.31435-100000@phoenix.infradead.org> from "James Simmons" at Feb 12, 2003 09:14:12 PM
> > There was a thread some months ago, called something like 'Linux as a
> > minicomputer', where we discussed this kind of thing.
>
> Yeap. This is my dream for linux. Someday :-)
Heh, yeah, a low-power RISC cpu based Linux box running of a
battery-backed 12v solar panel connected to 9600 bps serial terminals
with LCD screens all over the house is a future spare-time project for
me :-).
John
next prev parent reply other threads:[~2003-02-12 21:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-25 22:14 support for dual independent keyboards in devel kernel? Rick Warner
2003-02-12 18:40 ` James Simmons
2003-02-12 18:48 ` John Bradford
2003-02-12 21:14 ` James Simmons
2003-02-12 21:33 ` John Bradford [this message]
2003-02-13 7:36 ` Jos Hulzink
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=200302122133.h1CLXfZI001025@darkstar.example.net \
--to=john@grabjohn.com \
--cc=jsimmons@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rick@sapphire.no-ip.com \
/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