Named after Enkidu, the ancient Sumerian mythological figure? https://en.m.wikipedia.org/wiki/Enkidu
Most likely just a coincidence due to abbreviating NC urses D isk U sage
Dense
Edit, to spell it out: op was surely joking
Ncdu – NCurses Disk Usage
71–80 of 168 posts
Re: Ncdu – NCurses Disk Usage
#72`rclone ncdu` is also a jewel
Re: Ncdu – NCurses Disk Usage
#73Broadly, is anyone aware of a generalized list of "new versions of classic tools?" There are so many now that are better than the old stuff; I almost feel like a unified round up of these, maybe even in a distro form, might be good for linux enthusiasts, newcomers, old-timers, etc.
One thing that comes to mind as someone who is not in the know of these new tools would be, are they safe?
The old tools have been there forever and used everywhere. My assumption would be these are safe and don't change often. For better or for worse, I would be concerned about using the newer tools unless they are backed and/or approved by a large open source org.
Re: Ncdu – NCurses Disk Usage
#74The trick with ncdu is to install it BEFORE your disk gets full from some random error log going haywire.
Or a "journalctl --vacuum-time=1d" will usually clear a lot of space
Re: Ncdu – NCurses Disk Usage
#75Interesting. I’ve just used df-m | sort -n and walked the tree from the CLI for so long. I’ve also used windirstat (I think that’s what it was called) years ago on Windows and Disk Inventory X on MacOS graphically. This seems like a nice in between that could replace both methods for me. I’ll have to try. The GUI bunch of squares is really only useful when you can hover with a mouse and would be clunky in a TUI even…
> I’ve also used windirstat (I think that’s what it was called) years ago on Windows and Disk Inventory X on MacOS graphically.
On Windows, the new hotness is WizTree, which rather than recursively calling directory listing functions, it directly reads and parses the file tables itself. This makes it orders of magnitude faster. I have a 2 TB hard drive full of a million files, and WizTree reads and parses it all in under a minute, whereas I can expect WinDirStat to take half an hour.
Re: Ncdu – NCurses Disk Usage
#76The best tool I've used on Windows for that is "Scanner" by Steffen Gerlach: http://www.steffengerlach.de/freeware/
I use WinDirStat on Windows https://windirstat.net/
You should switch to WizTree. Rather than recursively calling directory listing functions, it directly reads and parses the file tables itself. This makes it orders of magnitude faster. I have a 2 TB hard drive full of a million files, and WizTree reads and parses it all in under a minute, whereas I can expect WinDirStat to take half an hour.
On an SSD, WizTree only takes a couple seconds.
Re: Ncdu – NCurses Disk Usage
#77The best tool I've used on Windows for that is "Scanner" by Steffen Gerlach: http://www.steffengerlach.de/freeware/
I find myself using WinDirStat on Windows systems, but often use ncdu in WSL.
On Windows, you should switch to WizTree. Rather than recursively calling directory listing functions, it directly reads and parses the file tables itself. This makes it orders of magnitude faster. I have a 2 TB hard drive full of a million files, and WizTree reads and parses it all in under a minute, whereas I can expect WinDirStat to take half an hour.
On an SSD, WizTree only takes a couple seconds.
Re: Ncdu – NCurses Disk Usage
#78See also tkdu for a graphical version: https://github.com/daniel-beck/tkdu
It's abandoned but it still works, and I like it because you can pipe the output of du into it, which is useful for visualizing remote systems.
Re: Ncdu – NCurses Disk Usage
#79The trick with ncdu is to install it BEFORE your disk gets full from some random error log going haywire.
I've saved the day once or twice by having a built of ncdu that I can just copy to /dev/shm to figure out what went haywire.
Re: Ncdu – NCurses Disk Usage
#80While ncdu does the job I've found gdu (similar tool written in Go) significantly faster for larger directories. https://github.com/dundee/gdu
Someone's gotta write rdu.