systat(1)?  Really?  I thought it only useful for swap ... and swap isn't at issue here, is it?  -- [[KevinDKinsey]]

> Looks like only NetBSD's systat has the disk usage "df" display. So briefly mention only for NetBSD.
>
> Also don't mention swap disk space here, but just refer to section [[Monitor_the_virtual_memory_system]].
>
> And show examples of using find(1) to find large files. For extra details on find, refer to [[Find_a_file_with_a_given_set_of_attributes]].
>
> Maybe this section should also mention how files that are unlinked (deleted) but still open make df and du have different information.
>
> --reed

----

On DragonFly: no du -m, no df -c

On OpenBSD: no df -m, no du -m, no df -c

On NetBSD: no df -c

I see you don't mention -m so that is good. It is good they all now support -h.

So maybe just put note in parenthesis: (On FreeBSD, using "-c" with df provides an overall total.)

Also please mention "du -s"

Thanks for teaching me "du -c" :)

Also find -size +900M is not portable. Only k,M,G,T,P are supported by FreeBSD's find(1).
(Anyone use "P" :)
The portable way is using -size +940000000c (rounded off). (Check this?)

And please mention about when a disk space is full according to du, but not full according to df.

--reed

------

The **du -hc \* | sort -n | grep "[0-9]M" | tail** example may be misleading by a novice,
because if they use it they may miss larger files (due to du -h switch) like G or T or P
and will be sorted wrong. Not very friendly, but maybe the following is simplest and most portable:

"" du -kc | sort -n | tail

(Wildcard \* not need either as that will exclude hidden .dot files.)
--reed

----

Also "du -d" in practice exercise is not portable (and not explained). I'll check later to see what BSDs have it. --reed

> Neither Open nor Net ... axed. Thanks.  ---KevinDKinsey

