From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] cwfs trouble on my laptop
Date: Sun, 20 Oct 2019 20:04:13 +0200 [thread overview]
Message-ID: <CAFSF3XNfHA-X3MmgWZgxQmyzoARNkfwV+gptpLF7d-uZ0pt_Wg@mail.gmail.com> (raw)
In-Reply-To: <20191020161723.2c0e662f@riseup.net>
yeah, definitely avoid SD cards.
i recommend
1) use SD cards only for storing media for playback on mobile devices,
like for music in an mp3 player (with your main library still on
proper and backed up disks).
2) throw all rpi <4 into the trash
3) get used to the overhead of the xhci, there are cheap enclosures
with consumer SSDs that are more performant and reliable than any SD
based storage I have come across so far.
On 10/20/19, raingloom <raingloom@riseup.net> wrote:
> I was having similar issues on my Raspberry Pi when its microSD card
> started dying. As far as I know, HDDs don't always fail very gracefully.
>
next prev parent reply other threads:[~2019-10-20 18:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-20 14:17 raingloom
2019-10-20 18:04 ` hiro [this message]
2019-10-20 23:10 kokamoto
2019-10-20 23:17 ` Steve Simon
2019-10-21 8:23 ` hiro
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=CAFSF3XNfHA-X3MmgWZgxQmyzoARNkfwV+gptpLF7d-uZ0pt_Wg@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.org \
/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).