From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] Canonical way to configure permanent remote cpu access
Date: Mon, 10 Dec 2012 11:30:27 +0000 [thread overview]
Message-ID: <0531d6e6b6997c360d96d62a355b7cea@hamnavoe.com> (raw)
In-Reply-To: <ee2ee9464b7943d476feb5a84ea5747f@proxima.alt.za>
> My immediate concern with the PI is that it's going to get into
> trouble, eventually, with CF memory.
The pi has no built-in flash at all; its normal non-volatile storage
is a plug-in SD card. 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. And if it does wear out, you just plug in a new one.
next prev parent reply other threads:[~2012-12-10 11:30 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 [this message]
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
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=0531d6e6b6997c360d96d62a355b7cea@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).