Since
v8.21-172-g33660b4, df not only treats symbolic link arguments
differently, as stated there, but now generally processes special file
arguments in a non-canonicalized form correctly:
$ cd /dev && df-old sdb
Filesystem 1K-blocks Used Available Use% Mounted on
devtmpfs
1014572 48
1014524 1% /dev
$ cd /dev && df-new sdb
Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sdb
10190136 6039532 3609932 63% /home
Document df's new behavior.
* doc/coreutils.texi (df invocation): In the paragraph describing
df's behavior regarding special file arguments, relax the condition
for such special files from "... is an absolute name of ..." to
"... resolves to ...".
* NEWS (Bug fixes): Mention the new behavior also here.
mount points. Previously it may have failed to output some mount points.
[bug introduced in coreutils-8.21]
- df now processes symbolic links to disk device nodes correctly. Previously
- df displayed the symlink's device rather than that for the device node.
+ df now processes symbolic links and relative paths to special files containing
+ a mounted file system correctly. Previously df displayed the statistics about
+ the file system the file is stored on rather than the one inside.
[This bug was present in "the beginning".]
df now processes disk device nodes correctly in the presence of bind mounts.
@cindex disk device file
@cindex device file, disk
-If an argument @var{file} is an absolute name of a disk device node containing
+If an argument @var{file} resolves to a special file containing
a mounted file system, @command{df} shows the space available on that
file system rather than on the file system containing the device node.
GNU @command{df} does not attempt to determine the disk usage