From: Skip Tavakkolian <email@example.com>
To: Fans of the OS Plan 9 from Bell Labs <firstname.lastname@example.org>
Subject: Re: [9fans] A couple questions about /dev/draw and /dev/kbmap
Date: Thu, 5 May 2016 15:38:25 +0000 [thread overview]
Message-ID: <CAJSxfmLw-jBsa5GRCb7qTBQ7DhFRxy=3O=gx1yTuAhPbDr0UfQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1519 bytes --]
The beauty of it is the uniformity and not making any assumptions about the
specifics of what's underneath; notice starting rio inside a rio window.
On Thu, May 5, 2016 at 6:12 AM Dave MacFarlane <email@example.com> wrote:
> In that case, is there any way to get the current max packet size that 9p
> will allow for
> a read or write, or to determine if you're drawing to a local machine or
> not? I'm not seeing anything obvious under /dev or /env.
> On Wed, May 4, 2016 at 10:45 PM, <firstname.lastname@example.org> wrote:
>> you wont have that limitation on devdraw on the local machine. but
>> over 9p, your reads and writes are limited by the iounit of the
>> channel over which 9p is transfered.
>> the reson for having a iounit is that you'r not the only one doing
>> stuff over the channel. you chunk stuff up in packets, so multiple
>> things can appear as simultanious even tho theres only one serial
>> channel. the bigger you make the packets, the bigger the latency
>> for concurrent packets wanting to be transmitted.
>> for the keyboard stuff. you cant do that with /dev/cons. drawterm
>> only gives you runes, but no kbmap (you'r probably seeing the cpu
>> servers kbmap, not the one in drawterm). in 9front [1,2], theres
>> /dev/kbd  which also gives you button states.
>>  http://9front.org/
>>  http://drawterm.9front.org/
>>  http://man.9front.org/8/kbdfs
> - Dave
[-- Attachment #2: Type: text/html, Size: 2476 bytes --]
prev parent reply other threads:[~2016-05-05 15:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-04 20:20 Dave MacFarlane
2016-05-04 21:53 ` hiro
2016-05-05 2:45 ` cinap_lenrek
2016-05-05 13:12 ` Dave MacFarlane
2016-05-05 13:16 ` Aram Hăvărneanu
2016-05-05 13:56 ` cinap_lenrek
2016-05-05 16:00 ` Charles Forsyth
2016-05-05 15:38 ` Skip Tavakkolian [this message]
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).