From mboxrd@z Thu Jan  1 00:00:00 1970
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Date: Mon, 27 Jun 2016 15:15:21 +0200
Subject: [TUHS] Origin year of BSD csh?
In-Reply-To: <DC2A30BA-C596-4FB8-991F-6E42F310A75E@ronnatalie.com>
References: <201606261014.u5QAE1qX015184@skeeve.com>
 <5770032F.8030306@mhorton.net> <20160626181450.GK26734@mcvoy.com>
 <CAC20D2N1gHSsQYNCmUixdK4D5hhbfMuyD7wnYPmvD-3dTgtV7Q@mail.gmail.com>
 <57710068.Y5JOWn5FNyxO2PxU%schily@schily.net>
 <DC2A30BA-C596-4FB8-991F-6E42F310A75E@ronnatalie.com>
Message-ID: <20160627131521.wRtxVeSyi%steffen@sdaoden.eu>

Ronald Natalie <ron at ronnatalie.com> wrote:
 |vfork() is of use on non-paged (and poorly implemented paging) system\
 |s.    If you implemented the copy-on-write fork() behavior, you’d not\
 | need the vfork KLUDGE.

I think there is currently going on some (i haven't really a glue)
virtually mapped stack in Linux (thread around [1]), and it seems
vfork() there doesn't even copy the page table.  So that seems to
be a measurable difference.

  [1] http://www.openwall.com/lists/kernel-hardening/2016/06/21/10

--steffen