From: Ronald G Minnich <rminnich@lanl.gov>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] xcpu fix for Plan9.c
Date: Thu, 20 Oct 2005 09:40:45 -0600 [thread overview]
Message-ID: <4357BA7D.5040004@lanl.gov> (raw)
In-Reply-To: <2e38dc2dba2dfd0b245acbd7b22f7581@orthanc.cc.titech.ac.jp>
YAMANASHI Takeshi wrote:
>>sorry about the error, I have put a fix (untested, no time this morning)
>>on /n/sources/9grid/Plan9.c
>
>
> Thanks, but you forgot to put "int kidfds[3]" in, it seems.
>
> ===
> void runit(void *ac) {
> Client *c = ac;
> :
> int kidfds[3];
> ===
thanks, fixed.
>
> With this addition in Plan9.c, I was able to run xcpusrv on Plan 9
> while /n/xcpu/0/arch always returns "linux". :)
fixed, for 386; will try to put in a read of the right # files but I
just ran out of time today.
>
> By the way, tokenize() in runit() will abort if c->argv is nil.
> You can do this by issuing "echo exec > ctl" without
> "echo something > argv" done beforehand.
I think it might be sensible to not let the echo exec > ctl operation
happen until argv is set? What do you think? I don't see a point in
letting it run without args.
This argv model was in the original xcpu stuff, should we really instead
be doing this:
echo exec date > ctl, i.e. just require the args as part of the exec
command? It seems easier to me somehow to do it this way.
>
> Oh, one more thing in xcpu.pdf.
>
> There seems to be a typo in the example for setting up argv on p.12.
> Next, argv:
> for i in $NODES
> do
> echo date > /mnt/xcpu/0/xcpu/$i/exec&
> done
> wait
>
> The file date is echoed should be argv, not exec.
thanks, fixed.
thanks for looking at this. It is much appreciated.
ron
next prev parent reply other threads:[~2005-10-20 15:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 2:58 YAMANASHI Takeshi
2005-10-20 14:33 ` Ronald G Minnich
2005-10-20 15:40 ` Ronald G Minnich [this message]
2005-10-20 15:56 ` Ronald G Minnich
2005-10-22 3:43 ` kokamoto
2005-10-24 14:46 ` Ronald G Minnich
2005-10-25 2:24 ` Kenji Okamoto
2005-10-25 2:29 ` Kenji Okamoto
2005-10-25 20:56 ` Ronald G Minnich
-- strict thread matches above, loose matches on Subject: below --
2005-10-24 1:01 YAMANASHI Takeshi
2005-10-21 5:55 YAMANASHI Takeshi
2005-10-21 4:24 YAMANASHI Takeshi
2005-10-21 4:31 ` Russ Cox
2005-10-21 2:14 YAMANASHI Takeshi
2005-10-24 14:40 ` Ronald G Minnich
2005-10-24 14:57 ` Lucio De Re
2005-10-24 15:06 ` Lucio De Re
2005-10-19 13:28 Ronald G Minnich
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=4357BA7D.5040004@lanl.gov \
--to=rminnich@lanl.gov \
--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).