Linux tool to show progress for cp, mv, dd

• advcpmv

  8 708 3.1 Shell

  A patch for GNU Core Utilities cp, mv to add progress bars

I went looking and I found this:

* https://github.com/jarun/advcpmv

This one got lost because the original author's WWW site just vanished, according to the doco.

• progress

  10 8,195 5.2 C

  Linux tool to show progress for cp, mv, dd, ... (formerly known as cv)

• InfluxDB

  www.influxdata.com sponsored

  Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.

  

• pv

  9 204 0.0 C

  Pipe Viewer Mirror - 1.6

• doas

  29 725 4.6 C

  A port of OpenBSD's doas which runs on FreeBSD, Linux, NetBSD, and illumos

It's more likely that this is the entire "upstream downstream" development model in action again.

There are vast numbers of improvements to softwares that never get sent to the places where they will do the most good (or at least have a proper record of why they were rejected by their authors). A quick perusal of the bug trackers of Debian or Ubuntu will reveal tonnes of local patches that the original authors of the softwares often never even hear about.

Things don't "stick" often times simply because they get lost.

I was looking at something like that just the other day. Here's a bug report that describes a problem with "doas" not opening the controlling terminal to do its authentication dialogue. This is actually a problem with a package named LinuxPAM, and doesn't occur when "doas" uses OpenPAM or BSD Auth. It's LinuxPAM that's where the code in question is. Fixing LinuxPAM would improve the lives of everyone that uses LinuxPAM, because the behaviour of not allowing standard input through in a command pipeline is not confined to "doas" but affects everything that uses LinuxPAM to do login authentication.

But time and again stuff like this languishes in the wrong place, for years and decades.

* https://github.com/slicer69/doas/issues/17

• linux

  980 170,074 10.0 C

  Linux kernel source tree

One of my quick-and-dirty gotos for getting a rough idea of buffered-writes size + disk-write activity on random linux systems is: `watch -n1 grep -ie dirty -e writeback /proc/meminfo`.

You can invoke `sync` to watch the buffered-writes queue burn down when you have lots of pending writes.

see: `LESS=+/meminfo man proc` or https://github.com/torvalds/linux/blob/master/Documentation/... for more info

• progress.pl

  2 1 10.0 Python

  Simple perl utility to measure progress of operation based on filedescriptor position from /proc/$PID/fdinfo/

Suggest a related project