Comment 5 for bug 280129

Hi, I'm still concerned about this issue. As far as I understand, the ghc in hardy has a bug which returns random data when asked for the inode number. This causes any darcs executable built with that ghc to run very slowly (presumably because it is trying to use a bunch of random bogus inode numbers?). Until this is fixed in Hardy, I have to ask people to be careful not to use ghc on Hardy, which raises the question of what they should do instead. If this is fixed, I can instead ask them just to upgrade to the fix.