Stephan Witt wrote: > One remark here (nitpick): > In the first example "cat" is not the program which overwrites the original. > It is the shell - and to avoid that stupid mistake they introduced the > variable noclobber. > When it is set and if your scripts assume overwrite of already existent files > is ok they fail - out of the blue!
your example would be appropriate if noclobber is set out of the blue by default in my distribution and all bash scripts around the world which suppose ">" overwrite stop to work. the would be big fun and i hear the scream ;) pavel
