From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <379ca9f0562acf6f51e5f9e979c9d8a3@quanstro.net> From: erik quanstrom Date: Sun, 18 Jan 2009 17:26:38 -0500 To: 9fans@9fans.net In-Reply-To: <283f5df10901181350l4e70b9a8la2e8b975d85102a8@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] =?utf-8?q?Les_Mis=C3=A9rables?= Topicbox-Message-UUID: 82798af6-ead4-11e9-9d60-3106f5b1d025 > > >Or have a native Limbo compiler; I've been itching for that for some time, > > > > it doesn't mean anything. > > Uh, considering that ircfs is for Inferno (via Limbo), having a Limbo > compiler to native Plan9 would be a potential solution, assuming the run > time could be kept the same. de top-posted for your reading pleasure. the reason that a native limbo compiler doesn't make any sense is that inferno is not a virtual cpu, it is a virtual system, complete with system calls, file system access, etc. of course, this is the right way to do things since inferno needs to run natively and on top of other systems like windows as well as natively. i've heard that it was the opinion of some at the labs in the early days of plan 9 (can anyone confirm?) that plan 9 was a way to glue the unixes together. if that's what plan 9 is, then one should have a fs to make an inferno's /proc appear nativeish. but it's not clear to me that one could bridge enough of the gap to make this anything other than an annoyance. for example, what if you wanted to debug an inferno process? - erik