summaryrefslogtreecommitdiff
path: root/system/coreutils/test-df-symlink-bindmount.patch
AgeCommit message (Collapse)AuthorFilesLines
2023-04-01system/coreutils: Update to 9.2A. Wilcox1-3/+3
Fixes: #787
2022-05-01system/coreutils: Update to 9.1A. Wilcox1-3/+3
2019-09-28system/coreutils: fix test failure with bind mountsMax Rees1-0/+11
df-symlink tests whether df output is consistent in regards to where devices are mounted. Specifically, it tries to ensure that if there is a 1:1 mapping of the device ("source") corresponding to the current directory "." ("target"), then `df --output=source,target .` should be the same as `df --output=source,target $(df --out=source . | tail -n1)`. However, this is not necessarily the case in the presence of bind mounts. For example: $ df --out=source . Filesystem /dev/sda4 $ df --out=source,target /dev/sda4 Filesystem Mounted on /dev/sda4 / $ df --out=source,target . Filesystem Mounted on /dev/sda4 /git This can be fixed by adding the --all flag to ensure that duplicate devices are printed, so that the 1:1-checking if statement actually checks it correctly.