From: Francisco J Ballesteros <nemo@lsub.org>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] multiple mice?
Date: Tue, 6 Dec 2005 23:15:55 +0100 [thread overview]
Message-ID: <8ccc8ba40512061415r527eb0c0lc4e9ef752269a101@mail.gmail.com> (raw)
In-Reply-To: <20051206214908.40223.qmail@web51110.mail.yahoo.com>
If they are usb, as many as you can plug, AFAIK.
You may even import your mice for use on other machines,
or redirect them as we do here.
Of course, your window system is likely to read just /dev/mouse,
but that may be multiplexed. I think we placed mousefs/kbdfs
in sources contrib.
On 12/6/05, Kenneth Long <kelong_2000@yahoo.com> wrote:
> how many mouse devices can plan9 support on one PC at
> the same time?
>
> looking at limitations other OSs have like
> http://link.mywwwserver.com/~jstookey/arcade/rawmouse/
>
> curious...
>
>
>
> __________________________________________
> Yahoo! DSL – Something to write home about.
> Just $16.99/mo. or less.
> dsl.yahoo.com
>
prev parent reply other threads:[~2005-12-06 22:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 21:49 Kenneth Long
2005-12-06 22:15 ` Francisco J Ballesteros [this message]
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=8ccc8ba40512061415r527eb0c0lc4e9ef752269a101@mail.gmail.com \
--to=nemo@lsub.org \
--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).