From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <9241c6d862536673c767d4d1df999a0d@quanstro.net> References: <13426df10904180807k29e2a188y9a5d93bb37540c04@mail.gmail.com> <9241c6d862536673c767d4d1df999a0d@quanstro.net> Date: Sat, 18 Apr 2009 12:13:33 -0400 Message-ID: <3aaafc130904180913y37375463t661cf6c2a1061ac0@mail.gmail.com> From: "J.R. Mauro" To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Subject: Re: [9fans] Plan9 - the next 20 years Topicbox-Message-UUID: e62f0ada-ead4-11e9-9d60-3106f5b1d025 On Sat, Apr 18, 2009 at 11:11 AM, erik quanstrom wr= ote: > On Sat Apr 18 11:08:21 EDT 2009, rminnich@gmail.com wrote: >> On Sat, Apr 18, 2009 at 6:50 AM, erik quanstrom = wrote: >> >> > in a plan 9 system, the only files that i can think of which many proc= esses >> > have open at the same time are log files, append-only files. =A0just r= eopening >> > log file would solve the problem. >> >> you're not thinking in terms of parallel applications if you make this >> statement. > > you're right. =A0i assume you specificly mean hpc things. =A0the gulf bet= ween hpc > and anything else is pretty big. > > - erik > > Not necessarily. There are plenty of files that a normal process run by any user will access which, upon migrating to another node, will be different or will need to be restored. I gave examples in my earlier email. It's *not* just an HPC problem. It's a problem when you want to be able to move process around even two computers on a home LAN.