From: vrtra <9@vrtra.net>
To: 9front <9front@googlegroups.com>
Subject: Re: /dev/wsys/*/screen not present for nested rio?
Date: Tue, 8 May 2012 13:49:48 -0700 (PDT) [thread overview]
Message-ID: <bfdda498-625b-4587-a075-422b1135b0fd@ot8g2000pbb.googlegroups.com> (raw)
In-Reply-To: <1c581e53ec2520d4989053955c2ef15b@sp.inri.net>
>
> Interesting. I do run a slightly modified rio, but it's not clear to me
> that the modifications should cause it to behave differently in this
> instance. My rio is here:
>
> http://plan9.stanleylieber.com/pkg/386/hjrio-2012.04.17.tbz
It works perfectly in your rio. :)
- that is, /dev/wsys/*/screen is accessible always.
I see that in fsys.c, only /dev/snarf is skipped. (in the main line,
both /dev/screen and /dev/snar are skipped.)
next prev parent reply other threads:[~2012-05-08 20:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 5:28 vrtra
2012-05-07 20:09 ` sl
2012-05-08 4:13 ` vrtra
2012-05-08 12:10 ` sl
2012-05-08 17:56 ` vrtra
2012-05-08 18:23 ` sl
2012-05-08 18:57 ` cinap_lenrek
2012-05-08 20:49 ` vrtra [this message]
2012-05-08 21:10 ` cinap_lenrek
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=bfdda498-625b-4587-a075-422b1135b0fd@ot8g2000pbb.googlegroups.com \
--to=9@vrtra.net \
--cc=9front@googlegroups.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;
as well as URLs for NNTP newsgroup(s).