This message is from the T13 list server.
[EMAIL PROTECTED] wrote:
This message is from the T13 list server.
Questions arise:
1) Why would it 'never be the "correct value" ?
Is this referring to the fact (acknowleged) that different
operating environments require different values ?
Of course. We can see that an offset of zero is unacceptable today. If
zero is unacceptable what makes any non-zero value acceptable?
What if there were a tool that would 'fix' your file system
to match the alignment of the device that is actually present ?
And who would create and support this utility?
Such a tool would, of course, have to be 'very' careful about
what it does, but there exists software today that mucks around
with partitions and such and finds a way to protect user data.
No kidding!
2) The proposal states that the alignment is not changeable in the field
So, a DCO to change it would be prohibited.
There would be no data integrity issue due to changing the alignment.
We all know this will become a DCO changeable value.
Hale
--
++ Hale Landis ++ www.ata-atapi.com ++
