On 2/10/2011 7:46 AM, Alan Cox wrote: > About ten years of distributions, drive hiding magic for old BIOSes and > other pain. So a few systems made over a decade ago used the HPA to hide the true size of the drive from a broken bios, and it was a good idea for the OS to unlock it? How did Windows run on such systems? That seems like a radically obscure case for always unlocking. Tejun's change already fixes such a system anyhow. Is there any other pain that makes unlocking a good idea? Would any of it still fail with Tejun's change? > It's unfortunate you won't listen but continue to spout stuff from a > standard no vendor, no OS and no product ever followed. ATA is not built > on strict adherance to formal standards, nor is the PC. Microsoft's OS follows it. > I see no point continuing this discussion if all you want to do is wave a > 'standard' that isn't followed by anyone and breaks stuff and demand we > follow it. Always unlock in the kernel, make both sets of geometry > available via sysfs and then fix dmraid. It's an easy problem to solve > and because dmraid knows a lot about fakeraid stuff it also knows enough > to peer in various locations and figure out which to use - something that > the kernel quite intentionally does not. Even if dmraid works around it, you are still left with: 1) Possibly trashing data the bios put on the hd and told you not to touch 2) Rebooting after running Linux leaves the drive unlocked, which causes the fakeraid bios to complain that your raid is broken. People don't like that. -- 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
