[prev] [thread] [next] [lurker] [Date index for 2004/11/21]
CALL THIS A FUCKING FILESYSTEM? $ ls -l ../parrot-clean/ops/core.ops -rw-r--r-- 8 nick nick 25106 19 Nov 15:35 ../parrot-clean/ops/core.ops $ ln ../parrot-clean/ops/core.ops ops/core.ops $ ls -l ops/core.ops ---------- 1 root wheel 0 6 Oct 2003 ops/core.ops Yes, that's right. If I hardlink a file owned by *me*, then it's quite correct for it to be owned by *root* now. And I can repeat this little loop ad nauseum. Nothing short of rebooting will cure it. I KNOW, BECAUSE I'VE BEEN HERE FUCKING SO MANY TIMES BEFORE. You're corrupting your data structures in RAM, FUCKTARD. I'm praying you don't manage to SHIT the corruption to the disk, given how awe inspiring the OS X disk recovery tools are. People pay money for this CRAP? I can get disk corruption on Linux for free, if that's what I want. Nicholas Clark
Generated at 23:00 on 18 May 2005 by mariachi 0.52