Ncdu – NCurses Disk Usage
131–140 of 168 posts
Re: Ncdu – NCurses Disk Usage
#132Earlier quoted context omitted.
The Bash CLI is my file manager. So I've got ncdu built right in. Try it, you'll love it. I almost never touch the rodent.
Except that running "ls" doesn't show you the directory content size, and "ncdu" requires the user to make a tea first. The above poster is right in saying that having this built-in to the filesystem metrics would be a huge win.
Re: Ncdu – NCurses Disk Usage
#133One thing ncdu does not improve on over du | sort is that it still needs to scan the full directory structure before even displaying any result. I would like something that starts estimating sizes immediately, and then refines those estimations as it is able to spend more time. I tried writing it myself, but I ended up not quite knowing how to go about it, because just getting the count of files in a directory takes…
Re: Ncdu – NCurses Disk Usage
#134One thing ncdu does not improve on over du | sort is that it still needs to scan the full directory structure before even displaying any result. I would like something that starts estimating sizes immediately, and then refines those estimations as it is able to spend more time. I tried writing it myself, but I ended up not quite knowing how to go about it, because just getting the count of files in a directory takes…
btdu
Seems to be specific for btrfs
Re: Ncdu – NCurses Disk Usage
#135Re: Ncdu – NCurses Disk Usage
#136I love ncdu and install it on all of my machines. But at the risk of sounding like a broken record - why isn’t its functionality baked into stock file managers on windows and Linux? Why can’t either of these systems do what the Mac has been able to do since the 90s, and display the recursive size of a directory in bytes in the file manager, allowing one to sort directories by recursive size? I am not exaggerating to…
Re: Ncdu – NCurses Disk Usage
#137Earlier quoted context omitted.
The Bash CLI is my file manager. So I've got ncdu built right in. Try it, you'll love it. I almost never touch the rodent.
Except that running "ls" doesn't show you the directory content size, and "ncdu" requires the user to make a tea first. The above poster is right in saying that having this built-in to the filesystem metrics would be a huge win.
use a cronjob for `duc index`, then you can use `duc ui` to see the index. it doesn’t immediately update on change so it’s not quite what you’re looking for, but it might be the closest thing.
Re: Ncdu – NCurses Disk Usage
#138I use this tool all the time! On my Windows boxes, I use an old tool called "Scanner" that presents the results in an interactive pie chart: http://steffengerlach.de/freeware/ I've used it on everything from Windows 10 to my Win98SE oldschool gaming box.
Re: Ncdu – NCurses Disk Usage
#139Broadly, 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.
Go take a trip through the GNU userland tools and you'll find a lot of dodgy code that hasn't been touched in 30+ years.
Re: Ncdu – NCurses Disk Usage
#140If you like ncdu, you might also like dua[0]. You can run `dua i` to get an interface similar to ncdu, and can also run `dua` to list file sizes in the current directory, similar to `du`. Or `dua filename ` to get the size of a given file. [0] https://github.com/Byron/dua-cli
Not in any repo, I'll pass, thanks