From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leonardo To: 9fans <9fans@9fans.net> Subject: Re: [9fans] Object Icon, drawterm, riox Message-Id: <15989879080.F5D7.74228@composer.9fans.topicbox.com> References: <15986378520.bA424FDF.655635@composer.9fans.topicbox.com> In-Reply-To: Date: Tue, 1 Sep 2020 15:18:28 -0400 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="15989879081.eA510D5.74228" Content-Transfer-Encoding: 7bit Topicbox-Policy-Reasoning: allow: sender is a member Topicbox-Message-UUID: ea76936e-ec87-11ea-a7b3-7c6a9134e1fa --15989879081.eA510D5.74228 Date: Tue, 1 Sep 2020 15:18:28 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Tuesday, 1 September 2020, at 8:21 AM, Ethan Gardener wrote: > Is there any reason one process group cann't have multiple windows? By design, each window must have your own private namespace with your own /= dev/* files and although these files have same names when a window write to= one of them, that one is yours.=C2=A0If I didn't get it wrong, that's it.= =C2=A0This seems strange because it seems that windows use the same files, = but they don't. I think it's strange because I'm not familiar with the conc= ept of namespace:=C2=A0in other operating systems there is always just one = filesystem.=C2=A0I imagine that these issues of parent-window, child-window= and owner-window are minor, unimportant things and, therefore, had no plac= e in the design of the system: they were unnecessary complications.= --15989879081.eA510D5.74228 Date: Tue, 1 Sep 2020 15:18:28 -0400 MIME-Version: 1.0 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable
On Tuesday, 1 September 2020, at 8:21 AM, E= than Gardener wrote:
Is there any reason= one process group cann't have multiple windows?
By de= sign, each window must have your own private namespace with your own /dev/*= files and although these files have same names when a window write to one = of them, that one is yours. If I didn't get it wrong, that's it. = This seems strange because it seems that windows use the same files, but th= ey don't. I think it's strange because I'm not familiar with the concept of= namespace: in other operating systems there is always just one filesy= stem. I imagine that these issues of parent-window, child-window and o= wner-window are minor, unimportant things and, therefore, had no place in t= he design of the system: they were unnecessary complications.
= --15989879081.eA510D5.74228--