Ed Avis wrote: > Jim Meyering wrote: > >I looked into it a little, and am now even less enthusiastic. Doing > >it right would mean changes that are way too invasive. They'd have > >to handle failed chdir, opendir, readdir and retry after a chmod. > > Well - that's one way to do it, the other way is to chmod every file > before doing anything with it. But that might be slow (I haven't > benchmarked).
But the directory containing the file would need the chmod, not the file itself. The permission of the file has nothing to do with whether you can remove the file or not. It is the permission of the directory containing the file which controls that. Bob _______________________________________________ Bug-coreutils mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-coreutils
