9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jens Staal <staal1978@gmail.com>
To: 9fans@9fans.net
Cc: Thorsten Glaser <tg@mirbsd.de>
Subject: Re: [9fans] MirOS ksh (mksh) building out-of-the box on Plan9/APE
Date: Sat, 27 Jul 2013 07:48:22 +0200	[thread overview]
Message-ID: <20130727074822.50f9af70@Krypton> (raw)
In-Reply-To: <e5998a9a676a19522953a416aee2dc43@ladd.quanstro.net>

On Fri, 26 Jul 2013 13:01:16 -0400
erik quanstrom <quanstro@quanstro.net> wrote:

> On Fri Jul 26 12:30:20 EDT 2013, cinap_lenrek@gmx.de wrote:
> > plan9 kernel doesnt send notes on process exit to the parent. i do
> > not see any trivial way to emulate SIGCHLD as ape might spawn also
> > native processes so we cannot just add code to ape to emit the
> > signal on exit.
> >
> > we might handle wait records in a separate process tho using the
> > devproc's wait file (that means also we would need to reimplement
> > the various wait functions in ape as one would get a Einuse error
> > on wait() when someone reads your wait file, ugh) and also generate
> > a signal.


Would it be interesting to know how the other mksh ports (I think
Syllable and Win32) implemented SIGCHLD emulation? I also saw after
some googling that some tests in Go had to be ignored due to SIGCHLD
issues on Plan9, so I guess there are more use-cases than this one.
Unfortunately I know too little to actually give input on the actual
solution - most of it will come out as hot air (which hopefully won't
stink...).

>
> we may also have to do this if we wish to support pthreads with
> processes. pthreads allow one thread to wait for the children started
> by a second thread.
>
> - erik
>

A native APE pthread implementation would be awesome! I have been using
Gnu Pth some, but getting a proper APE variant would be much more
preferrable :)




  reply	other threads:[~2013-07-27  5:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26  6:59 Jens Staal
2013-07-26 16:26 ` cinap_lenrek
2013-07-26 17:01   ` erik quanstrom
2013-07-27  5:48     ` Jens Staal [this message]
2013-07-27 14:01       ` erik quanstrom
2013-07-27 15:11         ` Aram Hăvărneanu
2013-07-27 15:23           ` erik quanstrom
2013-07-27 21:39             ` Kurt H Maier
2013-07-27 21:43               ` erik quanstrom
2013-07-27 22:39                 ` Aram Hăvărneanu
2013-07-28  0:55                   ` erik quanstrom
2013-07-28  5:38                 ` lucio
2013-08-16  7:26 ` Jens Staal

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=20130727074822.50f9af70@Krypton \
    --to=staal1978@gmail.com \
    --cc=9fans@9fans.net \
    --cc=tg@mirbsd.de \
    /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).