From: okamoto@granite.cias.osakafu-u.ac.jp
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/lib/plumb/basic
Date: Tue, 23 Jul 2002 15:41:41 +0900 [thread overview]
Message-ID: <0333b8db493f8e2204c99f0fbc2e76c3@granite.cias.osakafu-u.ac.jp> (raw)
[-- Attachment #1: Type: text/plain, Size: 183 bytes --]
No, I don't like it, because too much cumbersome. :-)
Kenji
PS. Why redrawing the acme window is so slow on dual pentium
termianl + nvidia card? Of course, I'm using AGP...
[-- Attachment #2: Type: message/rfc822, Size: 2870 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /sys/lib/plumb/basic
Date: Tue, 23 Jul 2002 08:58:05 +0200
Message-ID: <20020723085804.W19813@cackle.proxima.alt.za>
On Tue, Jul 23, 2002 at 03:24:53PM +0900, okamoto@granite.cias.osakafu-u.ac.jp wrote:
>
> Then, I changed the line to
> arg isfile ./$1 /sys/include/$1
> , and killed the plumber processes, and restarted it.
> Then, I got the expected result.
>
> Kenji --sorry my vague English (anytime ;_;)
I think the idea is not to have both trees available simultaneously:
bind /3e/sys /sys
at least in some of the windows, and the plumbing rules will take
care of themselves. You could just start a new plumber in the new
namespace, but I would feel more comfortable with a new rio, I
think.
++L
next reply other threads:[~2002-07-23 6:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-23 6:41 okamoto [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-07-24 0:40 okamoto
2002-07-23 12:29 rob pike, esq.
2002-07-23 6:37 okamoto
2002-07-23 6:24 okamoto
2002-07-23 6:58 ` Lucio De Re
2002-07-23 4:37 rob pike, esq.
2002-07-23 4:07 okamoto
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=0333b8db493f8e2204c99f0fbc2e76c3@granite.cias.osakafu-u.ac.jp \
--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).