From mboxrd@z Thu Jan  1 00:00:00 1970
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\))
From: arisawa <arisawa@ar.aichi-u.ac.jp>
In-Reply-To: <CA+db=n0QRRyADKErsbxgLwBK0OELmjgqd4J3XgTUN8eg3iDv9A@mail.gmail.com>
Date: Sun, 30 Nov 2014 19:27:16 +0900
Content-Transfer-Encoding: quoted-printable
Message-Id: <49E625C4-892E-4AF1-AF9E-E1B1CF7A87A0@ar.aichi-u.ac.jp>
References: <23F46ED5-A8A6-4677-A01E-6CF1BCC51C7D@ar.aichi-u.ac.jp>
	<CA+db=n0QRRyADKErsbxgLwBK0OELmjgqd4J3XgTUN8eg3iDv9A@mail.gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] bug in rc(1) ?
Topicbox-Message-UUID: 2fb91f70-ead9-11e9-9d60-3106f5b1d025

OK, thanks

> 2014/11/29 13:57=E3=80=81minux <minux.ma@gmail.com> =E3=81=AE=E3=83=A1=E3=
=83=BC=E3=83=AB=EF=BC=9A
>=20
> On Fri, Nov 28, 2014 at 11:42 PM, arisawa <arisawa@ar.aichi-u.ac.jp> =
wrote:
>> rc(1) says:
>>=20
>>          rfork [nNeEsfFm]
>>               Become a new process group using rfork(flags) where
>>               flags is composed of the bitwise OR of the rfork flags
>>               specified by the option letters (see fork(2)). If no
>>               flags are given, they default to ens.  The flags and
>>               their meanings are: n is RFNAMEG; N is RFCNAMEG; e is
>>               RFENVG; E is RFCENVG; s is RFNOTEG; f is RFFDG; F is
>>               RFCFDG; and m is RFNOMNT.
>>=20
>> this sounds to me
>>        rfork
>> is equivalent to
>>        rfork ens
> yes. it also agrees with the source code.
> =
http://plan9.bell-labs.com/sources/plan9/sys/src/cmd/rc/plan9.c:/^execnewp=
grp