ts-7000
[Top] [All Lists]

Re: [ts-7000] Re: Solving the USB drive journalling issue please critici

To:
Subject: Re: [ts-7000] Re: Solving the USB drive journalling issue please criticize
From: "Don W. Carr" <>
Date: Tue, 19 Sep 2006 16:11:22 -0500
Wouldn't it be nice if we had self ejecting SD like the floppies on a Mac, so the user could push a button to eject the SD, and it would eject after it was unmounted.

On 9/19/06, Chris <> wrote:

> Hmmm.... there's a scenario I didn't count on. Do the SD cards
suffer
> from the same fate ?
> >
> > I wish you well. If you have time I'd be interested in an
outline
> > of what
> > you end up doing and how it performs in practice.
>
> By the sounds of it whatever I do will have random results...

Let me preface this with the notation that I am NOT a programmer, I
just monitor this list to assist our software/hardware engineers, as
well as learn a little bit more about the inner workings of our
upcoming products. I handle service, support and tech writing, so
look at my comments from that perspective.

As a tech support guy, I appreciate that you are trying to make the
system as bulletproof for the customer/user as you can, allowing
them to plug/unplug the USB stick at will.

However, I also don't deem it unreasonable to provide some sort of
visual/audio feedback that tells the users they absolutely CANNOT
remove insert the stick at that time.

>From my (limited) understanding of your question and Linux, unless
you're writing particularly large files or writing very frequently,
most write/read/sync operations to the USB stick should be
relatively quick. Something as simple as an LED that comes on
during a write/read operation would provide (to my mind) sufficient
feedback - IE, "Don't remove/insert the USB stick IF this light is
ON." As long as the light doesn't stay on long, or doesn't come on
so frequently as to make it impossible, asking the user to delay a
few seconds until a light goes out seems like a reasonable
compromise.

If you throw in some sort of "error trapping" routine that gives
negative (but not catastrophic) consequences (like an error message
or alarm) for failing to observe the LED, most people will quickly
learn the process (provided it's sufficiently documented).

This seems to be one of those cases where throwing a few extra
dollars to the circuit design (LED and associated circuitry) and the
operating instructions might be a better payoff than trying to
anticipate every stupid thing a user can do and spending the time
coding for all those stupid things. Because, sure enough, you won't
catch everyone of them.

Anyway, that's my $0.02.

Chris Heismann




--
Dr. Don W. Carr
J. G. Montenegro 2258
Guadalajara, Mexico
+52-333-630-0704
+52-333-836-4500 ext 2930 __._,_.___


SPONSORED LINKS
Single board computer Hardware Computer running slow
Linux os Single board

Your email settings: Individual Email|Traditional
Change settings via the Web (Yahoo! ID required)
Change settings via email: =Email Delivery: Digest | m("yahoogroups.com?subject","ts-7000-fullfeatured");=Change Delivery Format: Fully Featured">Switch to Fully Featured
Visit Your Group | Yahoo! Groups Terms of Use | =Unsubscribe

__,_._,___
<Prev in Thread] Current Thread [Next in Thread>
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU