9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: arisawa@ar.aichi-u.ac.jp
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] #!/bin/foo
Date: Sat, 16 Jul 2005 07:40:39 +0900	[thread overview]
Message-ID: <c7fa037379cdacafd309cc3b810bb984@ar.aichi-u.ac.jp> (raw)
In-Reply-To: <3c689e333f7c49b26a5ea9493ab67d2c@ar.aichi-u.ac.jp>

I said:

> Yes I know that, but I have experienced such an endless loop
> using only binary executables. the kernel crushed.
> of course the logic was not so simple.
>

sorry, the situation might have been somewhat different.

the current kernel codes manipulates both executable binary
and executable script in exec system call.
how about bringing executable script parts to library ?
that is, introducing low level _exec that handles only binary
and we have exec in libray.
then, I guess, we can get more flexibility.

Kenji Arisawa



      reply	other threads:[~2005-07-15 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-07-14 21:09 arisawa
2005-07-15 18:30 ` Dan Cross
2005-07-15 22:08   ` arisawa
2005-07-15 22:40     ` arisawa [this message]

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=c7fa037379cdacafd309cc3b810bb984@ar.aichi-u.ac.jp \
    --to=arisawa@ar.aichi-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).