From fnaumann@mail.cs.uni-magdeburg.de  Fri Jan 30 20:42:48 2004
Message-ID: <0c0301c3e767$a9d60890$0e0a63d9@blaszak>
Reply-To: "Konrad Kokoszkiewicz" <draco@obta.uw.edu.pl>
From: "Konrad Kokoszkiewicz" <draco@obta.uw.edu.pl>
To: <mint@fishpool.com>
References: <20040122144133.GC17739@haddock.cd.chalmers.se> <00d401c3e198$9a156d80$0e0a63d9@blaszak> <Pine.NEB.4.58.0401231324200.27393@wh58-508.st.uni-magdeburg.de> <20040123191858.GA28238@haddock.cd.chalmers.se> <Pine.NEB.4.58.0401240939400.13500@wh58-508.st.uni-magdeburg.de> <20040124160439.GA24271@haddock.cd.chalmers.se> <035f01c3e333$a67d1b80$0e0a63d9@blaszak> <Pine.NEB.4.58.0401251345220.13500@wh58-508.st.uni-magdeburg.de> <03d701c3e4af$accb24f0$0e0a63d9@blaszak> <1075193841.3713.14.camel@joy.sophics> <07ba01c3e58b$26865ae0$0e0a63d9@blaszak> <Pine.NEB.4.58.0401281351470.13500@wh58-508.st.uni-magdeburg.de> <20040128184741.Y99259@antyk.obta.uw.edu.pl> <Pine.NEB.4.58.0401282237510.13500@wh58-508.st.uni-magdeburg.de> <092f01c3e675$8cf8bee0$0e0a63d9@blaszak> <Pine.NEB.4.58.0401291615120.13500@wh58-508.st.uni-magdeburg.de> <0a3701c3e69a$38f6db40$0e0a63d9@blaszak> <Pine.NEB.4.58.0401292301160.13500@wh58-508.st.uni-magdeburg.de>
Subject: Re: [MiNT] fVDI issues
Date: Fri, 30 Jan 2004 19:56:24 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2720.3000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2727.1300
X-Virus-Scanned: by amavisd-new
X-MIME-Autoconverted: from 8bit to quoted-printable by antyk.obta.uw.edu.pl id i0UJTjYZ075083
Delivered-To: mint@fishpool.com
Delivered-To: mint@lists.fishpool.fi
X-ecartis-version: Ecartis v1.0.0
Sender: mint-bounce@lists.fishpool.fi
Errors-to: mint-bounce@lists.fishpool.fi
X-original-sender: draco@obta.uw.edu.pl
Precedence: bulk
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
List-ID: <mint.lists.fishpool.fi>
X-List-ID: <mint.lists.fishpool.fi>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by prinz.cs.uni-magdeburg.de id i0UJgko26502

>> of the parent, or the one of the child. When the parent has created
>> the child with fork(), that is. This is so because the AES is a
>> separate
>
> Btw. this is an interesting question in general. What is the right
> behaviour if an AES process fork? And is an AES process allowed to
> fork?

Yes and no, I suppose. AFAIK fork() is allowed for any process, regardless
of what libraries or system functions it uses. At the other hand, Atari
programmers, while designing their multitasking AES 4.0 probably didn't
think/know, that MultiTOS is supposed to have Pfork().

--
CVV
Konrad M.Kokoszkiewicz, http://draco.atari.org

** Ea natura multitudinis est, aut seruit humiliter, aut superbe dominatur.
** Taka to juz natura pospólstwa, albo sluzalczo sie plaszczy,
** albo bezczelnie sie panoszy. (T. Liuius XXIV, 25).