Re: reading 1 hardsector size, not one block size

From: Peter Samuelson (peter@cadcamlab.org)
Date: Sat Sep 30 2000 - 02:20:22 EST


  [Hedrick]
> > FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF FS-DeStroke
> > DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD OEM-DeStroke
> > OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO MAN-DeStroke
> > AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA MAN-ALL

[Viro]
> It would help if you started with decoding TLA and TLAs...

I guess FS is FS like you said ... OEM is who labels the box on the
shelf, and I guess MAN is manufacturer. I would have said "Mfr".

I'm still not clear on the difference between the roles of the OEM and
the Mfr here -- are they really two different parties that *both* muck
with the drive firmware to change the visible sector count? What does
the OEM do that the Mfr hasn't already done, and why?

Peter
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/



This archive was generated by hypermail 2b29 : Sat Sep 30 2000 - 21:00:26 EST