From: Adam Thornton <athornton@gmail.com>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] fork (Re: Systematic approach to command-line interfaces
Date: Mon, 2 Aug 2021 17:59:12 -0700 [thread overview]
Message-ID: <44B352BC-D2A3-4AE0-B01E-2A13DB1BE816@gmail.com> (raw)
In-Reply-To: <EAF70FB6-6F90-4AE3-88F2-834310A71D31@iitbombay.org>
> On Aug 2, 2021, at 5:20 PM, Bakul Shah <bakul@iitbombay.org> wrote:
>
> On Aug 2, 2021, at 2:25 PM, Dan Cross <crossd@gmail.com> wrote:
>>
>> Fork has served us well for more than five decades; I've got no argument with that. However, should we never question whether it continues to be the right, or best, abstraction as the environment around it continues to evolve?
>
> An os with no fork() can be used to reimplement fork() for backward
> compatibility. You will anyway need all the things fork() used to do
> in this brave new world.
Oh man, now I’m having flashbacks to early Cygwin and what was that, DJGPP for OS/2?
Well, I picked a lousy week to give up sniffing glue anyway.
Adam
next prev parent reply other threads:[~2021-08-03 0:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-02 2:42 [TUHS] " Douglas McIlroy
2021-08-02 14:58 ` Theodore Ts'o
2021-08-02 18:15 ` Adam Thornton
2021-08-02 18:24 ` Warner Losh
2021-08-02 20:55 ` John Cowan
2021-08-02 21:06 ` Jon Steinhart
2021-08-02 21:25 ` Dan Cross
2021-08-02 21:59 ` Jon Steinhart
2021-08-02 22:33 ` John Cowan
2021-08-03 0:20 ` [TUHS] fork (Re: " Bakul Shah
2021-08-03 0:59 ` Adam Thornton [this message]
2021-08-03 1:20 ` Steve Nickolas
2021-08-03 0:21 ` [TUHS] " Bakul Shah
2021-08-03 1:49 ` Jon Steinhart
2021-08-03 3:21 ` Adam Thornton
2021-08-03 3:27 ` Bakul Shah
2021-08-03 3:51 ` Jon Steinhart
2021-08-03 7:19 ` arnold
2021-08-03 23:12 ` Andrew Warkentin
2021-08-04 15:04 ` Paul Winalski
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=44B352BC-D2A3-4AE0-B01E-2A13DB1BE816@gmail.com \
--to=athornton@gmail.com \
--cc=tuhs@tuhs.org \
/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).