From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.236.50.47 with SMTP id y35csp156745yhb; Sun, 6 May 2012 22:28:45 -0700 (PDT) Received: by 10.220.150.12 with SMTP id w12mr4452507vcv.39.1336368524878; Sun, 06 May 2012 22:28:44 -0700 (PDT) Return-Path: <9front+bncCP2Z1en5GxCMu539BBoEgzfkyA@googlegroups.com> Received: from mail-vx0-f191.google.com (mail-vc0-f191.google.com [209.85.220.191]) by mx.google.com with ESMTPS id m6si2765906vdi.129.2012.05.06.22.28.44 (version=TLSv1/SSLv3 cipher=OTHER); Sun, 06 May 2012 22:28:44 -0700 (PDT) Received-SPF: pass (google.com: domain of 9front+bncCP2Z1en5GxCMu539BBoEgzfkyA@googlegroups.com designates 209.85.220.191 as permitted sender) client-ip=209.85.220.191; Authentication-Results: mx.google.com; spf=pass (google.com: domain of 9front+bncCP2Z1en5GxCMu539BBoEgzfkyA@googlegroups.com designates 209.85.220.191 as permitted sender) smtp.mail=9front+bncCP2Z1en5GxCMu539BBoEgzfkyA@googlegroups.com; dkim=pass header.i=@googlegroups.com Received: by vcbgb30 with SMTP id gb30sf5834698vcb.18 for ; Sun, 06 May 2012 22:28:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=beta; h=x-beenthere:mime-version:date:user-agent:x-http-useragent :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type; bh=zCIWJB8ZX+6FL3F7PupEPSNM/1oJT6nDU7+X7PEs0ao=; b=2/Ijv9wUyFpfm1HyKcSvfJUSCZ70czU41e9Ivdp9+iehXCPsKyBXqhwMWdhJDla0Wo jc7D1V8nVoqBnAazXJsVX2B1xfDdkliYIEBlOH6WeYCaNIWasm4sXmdIuag4JQG/FoKz ke/cY2pDoeavis+J191iPeeyQL7rkWpZ2g/ZY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-beenthere:mime-version:date:user-agent:x-http-useragent :message-id:subject:from:to:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:x-google-group-id:list-post:list-help:list-archive:sender :list-subscribe:list-unsubscribe:content-type:x-gm-message-state; bh=zCIWJB8ZX+6FL3F7PupEPSNM/1oJT6nDU7+X7PEs0ao=; b=fWkhIYH5ib1NEPyB74e4zZQS2n8tOIfx8Rlp0Zka/JUgjBDic74bheVKdc0/L6l+7T Wp3bJf1LqfZzuMMl3NfNCh0siarFn5jwv6NRn/Ef3qd5sfbRE3aoslW9kFSFhMriwWm5 ZdEHrshAtOA7GngQzTTjkhx32wjA3UNrECJbspzUJN3fBfUtfIzPd6ZewiBpngaSov+h UI+nb7p5v4clFYFy8VFuk3F22+m76mJAp61Uzf2bbrRrjcK6b7DSfCd1fFpvXw0o4ecS d/Z1IwcA8dB2Ndeo8u56PFWwNpSA+cRvN7NLFJWe3JXZo1nhw/Gh7znEqT4g4yWDpsPV s5SQ== Received: by 10.68.190.36 with SMTP id gn4mr1552175pbc.19.1336368524559; Sun, 06 May 2012 22:28:44 -0700 (PDT) X-BeenThere: 9front@googlegroups.com Received: by 10.68.75.45 with SMTP id z13ls12302241pbv.7.gmail; Sun, 06 May 2012 22:28:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.68.229.100 with SMTP id sp4mr1545857pbc.10.1336368524395; Sun, 06 May 2012 22:28:44 -0700 (PDT) Received: by g6g2000pbq.googlegroups.com with HTTP; Sun, 6 May 2012 22:28:44 -0700 (PDT) Date: Sun, 6 May 2012 22:28:44 -0700 (PDT) User-Agent: G2/1.0 X-HTTP-UserAgent: Opera/9.80 (X11; Linux i686; U; en) Presto/2.10.229 Version/11.62,gzip(gfe) Message-ID: <3f17e7a5-6970-46f4-b55d-ef0b25a6a627@g6g2000pbq.googlegroups.com> Subject: /dev/wsys/*/screen not present for nested rio? From: vrtra <9@vrtra.net> To: 9front <9front@googlegroups.com> X-Original-Sender: 9@vrtra.net X-Original-Authentication-Results: ls.google.com; spf=pass (google.com: domain of 9@vrtra.net designates internal as permitted sender) smtp.mail=9@vrtra.net; dkim=pass header.i=@vrtra.net Reply-To: 9front@googlegroups.com Precedence: list Mailing-list: list 9front@googlegroups.com; contact 9front+owners@googlegroups.com List-ID: <9front.googlegroups.com> X-Google-Group-Id: 831096995978 List-Post: , List-Help: , List-Archive: Sender: 9front@googlegroups.com List-Subscribe: , List-Unsubscribe: , Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQmbGJmdVoFylqCtesYcCL/kav0I0sFLh/BvLImadCzEl+4OGsU4WD1tRi/Eolq2VLYI3ksK 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?