Ralph Shumaker wrote: >.. > You probably won't have to do this to see the flaw, but here's how to > recreate a skeleton of what I had: >.. > ln -s /temp/obscure/test.folder ~/test.folder > mv ~/Pictures/* ~/test.folder/Pictures > rmdir ~/Pictures (assuming empty) > ln -s ~/test.folder/Pictures ~/Pictures > ln -s ~/test.folder/1.sub.folder/Music ~/Music
so far; so good, eh > rm ~/test.folder boom! > > This assumes that ln creates links the same way that Nautilus does, ln creates links the way you tell it to. I thought Nautilus sometimes does favors in some non-specified way. readlink and stat are useful diagnostic/discovery commands! > namely that it uses the path given to it instead of the absolute path to > the actual physical location of the file. There are no other > assumptions of which I am aware. > > Given this series, with no delays between steps, it's probably easy to > see what happened. But given several days delay between a few of the > steps (even weeks), and you can forget that you made links that depend > on other links. In Nautilus, I opened ~ and freaked when I saw broken > links for Pictures, Music, Videos, and others. Heh. Now you can give a presentation on this, I think. :-) Or.. how about a writeup on the wiki Regards, ..jim -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-newbie
