3 ms·

Ted Tso wrote the majority of the filesystem in question, so he is pretty much the authority on the matter. He was hired by Google, and his point is that if Ub

by sharms 16y ago

Ted Tso wrote the majority of the filesystem in question, so he is pretty much the authority on the matter. He was hired by Google, and his point is that if Ubuntu is going to make a distribution, they need to have the engineers available to solve it, instead of just bugging actual engineers over and over again, which I see is reasonable given they sell support.

ajross 16y ago
To be fair, Ted was also involved in a public spit with the Ubuntu kernel team about a year ago regarding an ext4 bug that he tried to "not-a-bug" based on a strict reading of the standard. He ultimately lost the argument, and had to fix ext4. See: https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/317781 https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/31... and especially: http://lwn.net/Articles/322823/ http://lwn.net/Articles/322823/ Whether that has anything to do with this particular sniping incident, I obviously have no knowledge. But I think it's an important piece of context. Edit: after reading the whole bug report, it's also important to point out that the issue at hand here is a real and still-unfixed but in ext4 that has been worked around for Lucid. Ted's appeal that no one from Fedora has complained seems a little shallow given that there's a 7-line shell script at the top of the bug to exercise it. Really, this doesn't seem warranted here. I know the kernel team doesn't like Canonical. But I don't see what they did wrong here other than pick a different workaround than the one Ted suggested.