Yeah I was playing with du last night.
It doesn’t look to output actual byte sizes though so it may be that ncdu is still favored depending on what you’re looking for.
I added a link to the bottom of the post with a GitHub repo someone else did on formatting ncdu outputs.
I also have a Python script that does this as well. But my post was focused on available utils.
Regards,
Richard Schoen
Web:
http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
message: 3
date: Thu, 15 Aug 2024 07:39:20 -0400
from: John Yeung <gallium.arsenide@xxxxxxxxx>
subject: Re: Who stole my IBM i disk space ?
On Wed, Aug 14, 2024 at 4:07?PM James H. H. Lampert via MIDRANGE-L
<midrange-l@xxxxxxxxxxxxxxxxxx> wrote:
Here's what I got on our cloud V7 box, once I remembered how to *get* a
PASE command line:
$
yum install ncdu
/QOpenSys/usr/bin/-sh: yum: not found.
$
All the new open source stuff, including yum, is in
/QOpenSys/pkgs/bin, which is not in the path by default.
But Patrik brings up a good point: It may be that du is sufficient for
your needs.
Now, it so happens that there is "old" PASE du, from before they
started doing RPMs with yum; and new, from after. They are at,
respectively:
/QOpenSys/usr/bin/du
/QOpenSys/pkgs/bin/du
Generally speaking, the stuff in /QOpenSys/pkgs is going to be better,
though either might serve your purpose in this case.
John Y.
midrange.com
