> years ago when libata was written, and certain distributions decided to > risk breaking compatibility with hardware that runs Windows just fine in > favor of not breaking upgrades from systems installed with the old ide > driver that did default to unlocking. The old IDE driver defaulted to unlocking based upon years of experience in the real world. Jeff insisted on being different, and surprise surprise everyone ended up setting distro defaults that were different. > The discussion at hand is about a change made a few months ago that is a > good compromise between always unlocking, and never unlocking. Both of > those have problems, so a good compromise can have the benefits of both, > and the drawbacks of neither. Furthermore, it is already in the kernel, > so continuing to argue about whether it should have been done or not > seems a moot point. I disagree, and again you are still missing the entire point. For the RAID stuff you don't care if we unlock, you don't need to care if we unlock. You need to care about getting the raid tools figuring out what geometry the raid creation was using. -- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
