From: fgergo@gmail.com
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] sheeva
Date: Sat, 25 Sep 2010 22:32:55 +0200 [thread overview]
Message-ID: <AANLkTinw59Kj7CZ-T0FhjsKH16GgYmiWg9Fu80V98POH@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikuweAhvM=FPxaRq37LVS3Wp1SNLLT0xAKHUAqz@mail.gmail.com>
You are probably interested in plan9 related issues, but you might be
interested in this as well: if you run cpu intensive stuff, the plug
will get hot. My plug practically killed 1 sd card and almost fried
another one as well. I have found several complaints on this issue.
On Sat, Sep 25, 2010 at 6:47 PM, ron minnich <rminnich@gmail.com> wrote:
> Just playing with the plug again ...
>
> Anyone using sd yet? usb disk?
>
> I'm getting errors on each one .. probably pilot error.
>
> ron
>
>
next prev parent reply other threads:[~2010-09-25 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-25 16:47 ron minnich
2010-09-25 20:32 ` fgergo [this message]
2010-09-25 21:39 ` ron minnich
2010-09-26 0:20 ` David Leimbach
2010-09-26 1:45 ` ron minnich
2010-09-26 1:55 ` ron minnich
2010-09-26 3:36 ` erik quanstrom
2010-09-26 3:39 ` erik quanstrom
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=AANLkTinw59Kj7CZ-T0FhjsKH16GgYmiWg9Fu80V98POH@mail.gmail.com \
--to=fgergo@gmail.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).