The eject command forces a media-change indication internal to the kernel. The reader doesn't need to do anything after that -- the block-cache has been dumped and everything about the device (i.e. write-protect, size, etc.) has been forgotten.
Very few devices act like the Hexa, where if you do an eject it will
actually prevent you from accessing the device until a re-insert.
You could do it the other way around, but I find that if I give the
directions that way people are likely to put a card in, eject, remove the
card, then insert a different one -- and depending on what might have
happened in the background (i.e. automounter, etc.), they might not be in a
good state.
Matt
On Tue, Aug 12, 2003 at 11:43:40AM +0900, BLACKSON Jim wrote:
> Hi Matt,
>
> Matthew Dharm wrote on Sun, 10 Aug 2003 13:01:23 -0700:
> Subject: RE: [Linux-usb-users] Sandisk CF Mem card reader and flash card
> > Likely the card is stuffed. To be sure, make sure you do an 'eject
> > /dev/sda' after you insert the card (but before you try to access it.
> > If the error still happens, then the card is likely bad.
>
> I am wondering, why do an eject after inserting the card? Seems to me you
> would need to re-insert the card to force media change signaling, otherwise
> you would not be able to access the card. I think that's how the Y-E Data
> HexaMedia 6-in-1 card reader works.
>
> Best regards,
> jimb.
--
Matthew Dharm Home: [EMAIL PROTECTED]
Maintainer, Linux USB Mass Storage Driver
C: They kicked your ass, didn't they?
S: They were cheating!
-- The Chief and Stef
User Friendly, 11/19/1997
pgp00000.pgp
Description: PGP signature
