From: vrtra <9@vrtra.net>
To: 9front <9front@googlegroups.com>
Subject: /dev/wsys/*/screen not present for nested rio?
Date: Sun, 6 May 2012 22:28:44 -0700 (PDT) [thread overview]
Message-ID: <3f17e7a5-6970-46f4-b55d-ef0b25a6a627@g6g2000pbq.googlegroups.com> (raw)
Hi,
I notice that /dev/wsys/*/screen is visible only on the top rio
windows. If I start a nested rio instance, 'ls' still shows me that
the file is present, but on access, it returns back saying file does
not exist.
i.e from top:
% ls /dev/wsys/1
...
/dev/wsys/1/screen
% file /dev/wsys/1/screen
plan9 image
Now start a rio instance in the term, and do the same,
% ls /dev/wsys/2
...
/dev/wsys/2/screen
% file /dev/wsys/2/screen
Unable to acces, file /dev/wsys/2/screen does not exist
Why does it do so? I would have expected the screen to either provide
access to the original display or the screen from which rio was
started. If not, I would have expected 'ls' not to report the file to
be present. So is this intensional? if not, does copying the window of
the child rio over to child screen provide an acceptable behavior?
next reply other threads:[~2012-05-07 5:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 5:28 vrtra [this message]
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
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=3f17e7a5-6970-46f4-b55d-ef0b25a6a627@g6g2000pbq.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).