On Sat, 2018-09-08 at 08:10 +1000, Cameron Simpson wrote:
On 07Sep2018 15:56, JD <jd1008(a)gmail.com> wrote:
> On 09/07/2018 03:34 PM, Michael D. Setzer II wrote:
> > > On Fri, 7 Sep 2018 16:37:49 -0400 Tony Nelson
<tonynelson(a)georgeanelson.com>
> > > wrote:
> >
> > The line for the cloning process in my g4l is like this.
> > dd bs=1M if=$clonesource 2>/dev/null |jetcat-mod -f 5000 -p $clonesize
> > 2>$progout |dd bs=1M of=$clonetarget 2>/dev/null &
[...]
> > Uses a dialog script to set the variables, and then runs the copy command in
> > background. The foreground script takes the data written to the progout file
> > and displays a progress bar via dialog.
[...]
> Michael D. Setzer II,
> What is the purpose of inserting the utility
> jetcat-mod between the 2 dd commands?
Apologies, I think I've lost track of the attributions.
I'd expect jetcat to (a) provide an agressive buffering beyond what a pipe
provides (letting the first dd get ahead more) and (b) report progress.
Never heard of jetcat and it appears to be unknown to dnf.
poc