bug#37702: Suggestion for 'df' utility

[Bernhard Voelker]

On 2019-10-13 23:28, Paul Eggert wrote:
> In any sane system there would be only 
> four lines of non-header output (for tmpfs etc, /, /home, and 
> /media/eggert/B827-D456), but df is outputting 28 lines.

What is so special about tmpfs so that you would like to see it?

Here on my openSUSE:Tumbleweed system, I see the following:

  $ df -T
  Filesystem     Type     1K-blocks      Used Available Use% Mounted on
  devtmpfs       devtmpfs  10187924         8  10187916   1% /dev
  tmpfs          tmpfs     10199048     45788  10153260   1% /dev/shm
  tmpfs          tmpfs     10199048     18036  10181012   1% /run
  tmpfs          tmpfs     10199048         0  10199048   0% /sys/fs/cgroup
  /dev/sda2      ext4      20511312  12141864   7304488  63% /
  /dev/loop0     ext2         31729     31729         0 100% 
/FULL_PARTITION_TMPDIR
  /dev/sda5      ext4     619142920 390088908 229037628  64% /media/big_data
  /dev/sda3      ext3     103085876  90714416   7128248  93% /home
  tmpfs          tmpfs      2039808        20   2039788   1% /run/user/1000

(The /FULL_PARTITION_TMPDIR is used by a special coreutils test.)

I think I could well live with adding 'devtmpfs' and 'tmpfs' to the
pseudo file systems in gnulib's "mountlist.c".

This seems to be a small change, and not satisfying the snap case.
Yet, I agree with Assaf that changing the defaults has to be done
with caution.  Eliding r/o filesystems or where usage<1% doesn't
look like such.

Have a nice day,
Berny