[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21084: rm appears to no longer be POSIX compliant (as of 2013 editio
From: |
Linda Walsh |
Subject: |
bug#21084: rm appears to no longer be POSIX compliant (as of 2013 edition) re: deleting empty dirs and files under <path>/. |
Date: |
Sat, 18 Jul 2015 00:55:46 -0700 |
User-agent: |
Thunderbird |
In looking at the 2013 specification for rm
(http://pubs.opengroup.org/onlinepubs/9699919799/utilities/rm.html),
it no longer says to stop processing if the path basename equals
"." or "..".
It says that the entries "." and ".." shall not be removed. It
also says rm <empty dir> shall behave like "rmdir" -- i.e. it will
delete empty directories.
But in the case of foo/. it would be expected to process child inodes
before processing the directory itself.
But step 4 on that page says that rm should remove empty directories
without requiring other special switches.
- bug#21084: rm appears to no longer be POSIX compliant (as of 2013 edition) re: deleting empty dirs and files under <path>/.,
Linda Walsh <=
bug#21084: rm appears to no longer be POSIX compliant (as of 2013 edition) re: deleting empty dirs and files under <path>/., Andreas Schwab, 2015/07/18