9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] 9p devdraw
Date: Thu,  3 Nov 2011 00:05:05 -0700	[thread overview]
Message-ID: <CABwSpPDH_8PpXeuBNYhK8YX9NThjH3wcZFcMCE1+YPFoH4tQ6g@mail.gmail.com> (raw)
In-Reply-To: <CADErNDuE-rJbvv9N1irgT8n1=BWww+xdfyqrdKuLdwH9iXi-sg@mail.gmail.com>

Thanks for this  - I often wonder where to find
the code behind the papers in IWP9 proceedings.


ak

On Wed, Nov 2, 2011 at 12:29 PM, yy <yiyu.jgl@gmail.com> wrote:
> Two attached files:
>
> - 9p-srv.c is a devdraw(1) version which uses 9pclient(3) to talk with
> Plan 9-like devices and use them for its windows.
>
> - p9p.patch is a patch that has to be applied to the p9p tree to use
> this devdraw version.
>
> The drawing device expects to find draw(3), cons(3) and mouse(3) files
> in the $WSYS directory, as can be found in /dev in a Plan 9 terminal
> (including 9vx or drawterm) or /mnt/wsys when using rio. Then, those
> devices are used to run p9p programs.
>
> I wrote 9p-srv as an experiment to use wsys(4) [1] with p9p
> applications, but have found it quite useful to open p9p programs -
> like 9term or sam - in rio windows (for example, from 9vx).
>
> Although it could be argued that this is not the most efficient thing
> to do writing it was quite funny, and much easier than expected.
>
> Installation (once the patch has been applied and p9p built):
>
>        cp 9p-srv.c $PLAN9/src/cmd/devdraw
>        cd $PLAN9/src/cmd/devdraw
>        9c 9p-srv.c && 9l -o devdraw.9p 9p-srv.o
>        cp devdraw.9p $PLAN9/bin
>
> Now, to run 9term in a rio window:
>
>        # From 9vx's rio:
>        ; mount $wsys /n/w new
>        ; bind -a '#i' /n/w
>        ; aux/listen1 -t 'tcp!*!12345' /bin/exportfs -r /n/w
>
>        # From unix:
>        $ WSYS='tcp!127.0.0.1!12345'
>        $ DEVDRAW=devdraw.9p
>        $ 9term
>
> These files are also included with wsys(4), in the util directory
> (instructions are in the README). To use the drawing device with
> wsys(4) just set WSYS to "unix!/tmp/ns.$USERNAME.$DISPLAY/wsys".
> However, it is not working so well as with rio. The reason is probably
> some bug in wsys, and not in 9p-srv. I hope to fix it at some point,
> but is not an easy bug to track.
>
> If (after some more testing) the 9p drawing device could be included
> with p9p that would be great. If it has to stay in the wsys repository
> that is fine too but, could the p9p patch be applied at least? The two
> small changes shouldn't be a problem for the other versions of
> devdraw.
>
> Comments are welcomed.
>
>
> [1] http://bitbucket.org/yiyus/devwsys-prev/ (there is also a blog
> about the development of wsys(4) at
> http://summerofdevdraw.blogspot.com/ and a WIP short paper is included
> in the proceedings of the last iwp9).
>
> --
> - yiyus || JGL .
>



  reply	other threads:[~2011-11-03  7:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 19:29 yy
2011-11-03  7:05 ` Akshat Kumar [this message]
2011-11-03 10:32   ` yy
2011-11-09 21:07 ` yy

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=CABwSpPDH_8PpXeuBNYhK8YX9NThjH3wcZFcMCE1+YPFoH4tQ6g@mail.gmail.com \
    --to=akumar@mail.nanosouffle.net \
    --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).