9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: [9fans] plumber on new acme window
Date: Fri, 27 Apr 2001 12:40:09 +0900	[thread overview]
Message-ID: <20010427034026.1AA7719A6F@mail.cse.psu.edu> (raw)

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 1223 bytes --]

I'm experiencing a problem on the new 10140327.9gz (and also 03270425.9gz)
patches for plumber.

When I mount a cdrom by "Local" command for plumber on a rio's window,
I can use refleshment of plumbers namespace, and can see an image through
page2 (sorry we are still page2 here) both by "plumb" menu of rio and by
clicking right button on an acme window.
However, when I do the "Local" command in a acme window, I can see the
directory entries of the new mounted cdrom.  However, plumber does not
respond to my right button, and just treats the image for editor.

Our /sys/lib/plumb/basis and $home/lib/profile entries for this are as follows:

/sys/lib/plumb/basic
....
.....
# NASA image files go to page with scrollbars
type is text
data matches '[a-zA-Z¡-￿0-9_\-./]+'
data matches '([a-zA-Z¡-￿0-9_\-./]+)\.(img|imq)'
arg isfile	$0
plumb to pdsimage
plumb client page2 -w $file
....
....
# add a file tree to Plumber's namespace
type is text
data matches 'Local (.*)'
plumb to none
plumb start rc -c $1

/usr/okamoto/lib/profile
...
...
switch($service){
case terminal
#	plumber
	@ {rfork n; srvfs plumbspace /n; plumber}
	mount -b /srv/plumbspace /n
...
...

Kenji



             reply	other threads:[~2001-04-27  3:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-27  3:40 okamoto [this message]
2001-04-27  4:17 rsc

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=20010427034026.1AA7719A6F@mail.cse.psu.edu \
    --to=okamoto@granite.cias.osakafu-u.ac.jp \
    --cc=9fans@cse.psu.edu \
    /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).