Re: fdatasync() error in shred from coreutils-5.2.1 on AIX 5.2

[Paul Eggert]

Eli Zaretskii <address@hidden> writes:

>> The former name is valid in an 8.3 system, but the latter isn't, so the
>> rename will fail.
>
> That's your mistake: it won't fail.  What you get is a file named
> "00000000" (8 zeros), i.e. the OS silently truncates the name to the
> 8+3 limits.

Ouch.  Oh well.  There could be more problems here, e.g., renaming
"0000000000" to "000000000".  To be honest, though, this stuff is
pretty low priority, since "shred -u" doesn't wipe the name at all
reliably.  Personally I'm starting to think we should just dump all
this "name wiping" stuff and just remove the file; that'd be more
honest.  If you really want to shred metadata in a file system you
have to shred the underlying device.

> Btw, Jim: shred.c use a literal comparison with '/' in file names
> where it should use the ISSLASH macro instead.

Already fixed in CVS.