From: kokamoto@hera.eonet.ne.jp
To: 9fans@9fans.net
Subject: Re: [9fans] Octopus viewer?
Date: Tue, 8 May 2012 15:23:30 +0900 [thread overview]
Message-ID: <a9ccacb3c98b29a6b3c272b985fafd65@hera.eonet.ne.jp> (raw)
In-Reply-To: <b92924dede42a28b7f85d91a03d4cb69@hera.eonet.ne.jp>
I might have been not so specific.
I'll try once more.
I dispatched the command on the terminal's olive window:
!cp DSCN1549.jpg /mnt/view
Nothing happens.
Hoever, on the terminal's local window where octopus command
was dispatched, I see tow lines of messages of:
sh: plumbing write error: no matching plumb rule
view: cmd plumb /usr/octopus/tmp/view.2.DSCN1549.jpg <<<<
Then, I hided the olive window, and inferno's shell window raised,
and examined ls -l /tmp on the inferno's sh window.
Here, I can find the file of view.2.DSCN1549.jpg.
However, lc /usr/octopus/tmp shows nothing but error.
/usr/okamoto/tmp, neither.
Then I think the arrorwd line above shows that the program tryed
to do plumb the file on a wrong place, because of confusion of
namespaces.
Kenji
>> /mnt/view is used for that.
>> open in olive will use it when in a
>> terminal.
>
> I tried this, but fails.
next prev parent reply other threads:[~2012-05-08 6:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-22 7:45 kokamoto
2012-04-22 7:55 ` kokamoto
2012-04-22 13:11 ` Francisco J Ballesteros
2012-04-26 13:28 ` kokamoto
2012-04-26 13:38 ` Francisco J Ballesteros
2012-04-28 2:02 ` kokamoto
2012-04-28 8:23 ` kokamoto
2012-04-28 12:39 ` Nemo
2012-04-28 14:06 ` kokamoto
2012-04-30 1:19 ` kokamoto
2012-04-30 8:01 ` Nemo
2012-05-06 1:09 ` kokamoto
2012-05-08 6:23 ` kokamoto [this message]
2012-05-08 8:27 ` Francisco J Ballesteros
2012-05-10 7:58 ` kokamoto
2012-05-10 8:02 ` Francisco J Ballesteros
2012-05-11 1:50 ` kokamoto
2012-05-11 6:33 ` Nemo
2012-05-11 9:18 ` Charles Forsyth
2012-05-11 13:08 ` kokamoto
2012-04-22 13:10 ` Francisco J Ballesteros
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=a9ccacb3c98b29a6b3c272b985fafd65@hera.eonet.ne.jp \
--to=kokamoto@hera.eonet.ne.jp \
--cc=9fans@9fans.net \
/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).