From mboxrd@z Thu Jan 1 00:00:00 1970 MIME-Version: 1.0 In-Reply-To: <20121210164758.6B15DB827@mail.bitblocks.com> References: <0531d6e6b6997c360d96d62a355b7cea@hamnavoe.com> <45F11F0A-ED95-4756-AB56-F98040EC4937@9srv.net> <20121210164758.6B15DB827@mail.bitblocks.com> Date: Tue, 11 Dec 2012 06:43:39 +0100 Message-ID: From: hiro <23hiro@gmail.com> To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net> Content-Type: text/plain; charset=UTF-8 Subject: Re: [9fans] Canonical way to configure permanent remote cpu access Topicbox-Message-UUID: f560b212-ead7-11e9-9d60-3106f5b1d025 is that allowed to tinker with terrorist arms on flight in america? On 12/10/12, Bakul Shah wrote: > On Mon, 10 Dec 2012 10:41:56 EST Anthony Sorace wrote: >> > I think the wear-levelling on these is sufficient that you can run a >> > normal fossil file system for quite a while before it wears out. >> >> Or, of course, just don't run a local file system at all. This is Plan 9, >> after all. Using the fs in the basement has worked great for me >> throughout. You then free up the RAM that would otherwise be >> devoted to the fs (and that's fixed size on the pi). Maybe not >> something you can do today if this is your first Plan 9 system, >> but worth keeping in mind. > > The combination of plan9 + the low cost Pi opens up new > possibilities where other configurations can make sense. For > instance, sensor data collection with periodic syncing. plan9 > can make a nice embedded os. Another example: I can use a > pi-dock (pi + atrix lapdock) for hours on an airplane given > atrix's (supposed) 36 Wh battery. There is no one true way. > >