On Friday 12 February 2010 01:18:33 Iain Buchanan wrote: > On Fri, 2010-02-12 at 01:58 +0800, ubiquitous1980 wrote: > > With this command or similar, I made my directory and one file in / > > unreadable: > > > > for entry in $(find $HOME); do $entry >> found; done > > er... you just executed everything in your home directory and piped the > output to a file... I think you wanted "do echo $entry"? or the simpler > "find $HOME >> found"? > > anyway, it shouldn't have corrupted your filesystem, but it looks like > it did.
I thought the same and wondered "How? How could it corrupt stuff?" So assuming the for did do the corruption and it isn't coincidence, what would make this happen? Or is the OP just seriously out of luck and hit the one in a gazillion unjackpot? -- alan dot mckinnon at gmail dot com