From: sl@9front.org
To: 9front@googlegroups.com
Subject: Re: /dev/wsys/*/screen not present for nested rio?
Date: Tue, 8 May 2012 18:23:29 +0000 [thread overview]
Message-ID: <1c581e53ec2520d4989053955c2ef15b@sp.inri.net> (raw)
In-Reply-To: <7aa15ef5-85aa-4021-957c-aec99af937dd@h10g2000pbi.googlegroups.com>
>> And from within a nested rio:
>>
>> term% file /dev/wsys/1/screen
>> /dev/wsys/1/screen: plan 9 image, depth 32
>
> Here I get /dev/wsys/1/screen does not exist.
> If I type ls /dev/wsys then it shows
> /dev/wsys/1
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
> (Also this commit went in, that does not expose the screen any more in
> nested rios.)
I haven't advanced my rio to this commit, yet.
-sl
next prev parent reply other threads:[~2012-05-08 18:23 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 [this message]
2012-05-08 18:57 ` cinap_lenrek
2012-05-08 20:49 ` vrtra
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=1c581e53ec2520d4989053955c2ef15b@sp.inri.net \
--to=sl@9front.org \
--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).