From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] ituner minibox
Date: Mon, 10 May 2004 07:01:03 +0200 [thread overview]
Message-ID: <59a8106fd075cb00f15aef6ee418f22f@proxima.alt.za> (raw)
In-Reply-To: <200405082145.i48Ljtev004257@adat.davidashen.net>
> 1) kfs is unusable -- it is too slow to put it on a CF; fossil works fine.
Will you please explain? It is not clear whether CF is used as the
KFS storage or merely to hold kfs itself.
I ask because CF has a limited write lifetime, being intended more as
read-only storage (a few thousand write cycles?). I'm not sure all
reader of this list are aware of this, so I thought I'd mention it.
++L
next prev parent reply other threads:[~2004-05-10 5:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200405082145.i48Ljtev004257@adat.davidashen.net>
2004-05-09 5:04 ` ron minnich
2004-05-10 5:01 ` lucio [this message]
2004-05-10 8:57 ` dvd
[not found] <b06abcb24e2e4bd865c4b8842e00d883@davidashen.net>
2004-05-13 9:22 ` Kenji Okamoto
2004-05-13 13:57 ` ron minnich
2004-05-14 1:05 ` Kenji Okamoto
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=59a8106fd075cb00f15aef6ee418f22f@proxima.alt.za \
--to=lucio@proxima.alt.za \
--cc=9fans@cse.psu.edu \
/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).