9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Anthony Sorace <a@9srv.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Canonical way to configure permanent remote cpu access
Date: Mon, 10 Dec 2012 10:41:56 -0500	[thread overview]
Message-ID: <45F11F0A-ED95-4756-AB56-F98040EC4937@9srv.net> (raw)
In-Reply-To: <0531d6e6b6997c360d96d62a355b7cea@hamnavoe.com>

> 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.

Last night, as part of a few experiments, I connected a 15GB
external spinning HD over USB (with kfs on it). It's funny to see
the actual computer dwarfed by the physical size of the disk.




  parent reply	other threads:[~2012-12-10 15:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-10  9:37 Luke Evans
2012-12-10 10:12 ` lucio
2012-12-10 11:30   ` Richard Miller
2012-12-10 11:38     ` Charles Forsyth
2012-12-10 11:53       ` Richard Miller
2012-12-10 12:02     ` lucio
2012-12-10 15:41     ` Anthony Sorace [this message]
2012-12-10 16:47       ` Bakul Shah
2012-12-11  5:43         ` hiro
2012-12-10 11:23 ` Richard Miller
2012-12-11  9:36   ` [9fans] Canonical way to configure permanent remote Luke Evans
2012-12-11 12:21     ` Richard Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=45F11F0A-ED95-4756-AB56-F98040EC4937@9srv.net \
    --to=a@9srv.net \
    --cc=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).