-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tuesday, 2009-06-09 at 10:22 -0400, Dan Goodman wrote:
Good to know that "gory little detail". Thanks for the concise what- and how- summary, Carlos.
One other possibility to consider, if even this procedure doesn't bring satisfaction, is that perhaps, if the drive has been handled, that some sort of hardware read-only switch or jumper has been altered.
Could be...
But Carlos' interpretation seems quite probable, as well. Could be either. I'd check/do both.
Short of reading the kernel source tree, is there someplace where one can find more details of kernel behavior under duress, such as what Carlos has described? I'm thinking something a bit more comprehensive than release notes, but not as dry as a complete bugzilla list.
Not that I know. It is... know how, experience, what you have seen before or heard from someone or read... unless you happen to be a kernel developer and then you really /know/. In Linux, there is not a book you can read and know everything, and that knowledge be and stay current. Unfortunately. Documentation is distributed, somewhat difficult to find, and changes rapidly. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAkou4GkACgkQtTMYHG2NR9WS0wCeJ7IBWakPNJWx13XBRCR6cNCC WcAAn3Q7gpL5Mz6p4eHySAOKZC4WDNIP =fyZw -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org