Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!apple!sun-barr!ccut!titcca!cc.titech.ac.jp!necom830!mohta
From: mohta@necom830.cc.titech.ac.jp (Masataka Ohta)
Newsgroups: comp.arch
Subject: Re: vfork (was Re: Paging page tables)
Message-ID: <5891@titcce.cc.titech.ac.jp>
Date: 19 Jul 90 07:11:11 GMT
References: <920@dgis.dtic.dla.mil> <5830@titcce.cc.titech.ac.jp> <5DL4SPD@xds13.ferranti.com> <5855@titcce.cc.titech.ac.jp> <774@sibyl.eleceng.ua.OZ>
Sender: news@cc.titech.ac.jp
Organization: Tokyo Institute of Technology
Lines: 26

In article <774@sibyl.eleceng.ua.OZ> ian@sibyl.OZ (Ian Dall) writes:

>Masataka seems to live in a binary world were there is only the BSD
>and the SysV implimentations.

No. I live in a unary world of BSD UNIX. But, I know of SysV and VMS
well enough.

>To the user the
>system will appear to have deadlocked, but not to the super user who
>can at least run ps and kill.

It is not a solution.

>Others might think up more elegant solutions.

The elegant solution is vfork.

>The point is you
>shouldn't throw out the baby with the bath water. Copy on write
>is an elegant idea. Don't stomp on it just to keep vfork!

I don't mind if COW exists, if it is not overly complex nor results
in deadlock or other unpleasant thing.

						Masataka Ohta