From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <3aaafc130904171535j4ecac3b4t64251cb52ba81b71@mail.gmail.com> References: <13426df10904171515g571f7781x38ca528cfbce1149@mail.gmail.com> <3aaafc130904171535j4ecac3b4t64251cb52ba81b71@mail.gmail.com> Date: Fri, 17 Apr 2009 16:01:17 -0700 Message-ID: <13426df10904171601s413675a3nd88d89dbd7fa4bb2@mail.gmail.com> From: ron minnich To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [9fans] Plan9 - the next 20 years Topicbox-Message-UUID: e4bc93ca-ead4-11e9-9d60-3106f5b1d025 On Fri, Apr 17, 2009 at 3:35 PM, J.R. Mauro wrote: > Amen. Linux is currently having a seriously hard time getting C/R > working properly, just because of the issues you mention. The second > you mix in non-local resources, things get pear-shaped. it's not just non-local. It's local too. you are on a node. you open /etc/hosts. You C/R to another node with /etc/hosts open. What's that mean? You are on a node. you open a file in a ramdisk. Other programs have it open too. You are watching each other's writes. You C/R to another node with the file open. What's that mean? You are on a node. You have a pipe to a process on that node. You C/R to another node. Are you still talking at the end? And on and on. It's quite easy to get this stuff wrong. But true C/R requires that you get it right. The only system that would get this stuff mostly right that I ever used was Condor. (and, well the Apollo I think got it too, but that was a ways back). ron