Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-19 Thread Georges Khaznadar
Hello Michael, Michael Peek a écrit : I had no idea that pv existed. I took a look at it, and they are very similar. There are a few things that bar offers over pv: - ANSI color support - Configurable progress bar characters In the manpage I only found the option display-twiddle about

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-18 Thread Michael Peek
I had no idea that pv existed. I took a look at it, and they are very similar. There are a few things that bar offers over pv: - ANSI color support - Configurable progress bar characters - Configurable I/O select() timeout - Ability to use configuration file(s) - Displaying of additional

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Georges Khaznadar
Package: wnpp Severity: wishlist Owner: Georges Khaznadar georg...@ofset.org * Package name: bar Version : 1.10.9 Upstream Author : Michael Peek p...@tiem.utk.edu * URL : http://clpbar.sourceforge.net/ * License : GPL-2 Programming Lang: C Description

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Don Armstrong
On Mon, 16 Aug 2010, Georges Khaznadar wrote: Bar is a simple tool to process a stream of data and print a display for the user on stderr showing (a) the amount of data passed, (b) the throughput of the data transfer, and, if the total size of the data stream is known, (c) estimated

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Lars Wirzenius
On ma, 2010-08-16 at 20:36 +0200, Georges Khaznadar wrote: Bar is a simple tool to process a stream of data and print a display for the user on stderr showing (a) the amount of data passed, (b) the throughput of the data transfer, and, if the total size of the data stream is known,

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Georges Khaznadar
Don Armstrong a écrit : [as a handfull of other vigilant developers] How does this [bar] differ from pv? h... I used Michael Peek's bar for a few years because I never heard about pv. Thank you for this notice. When I read pv's manpage, it appears as more featureful than bar. I use

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Lars Wirzenius
Dropped debian-devel from the Cc list. On ma, 2010-08-16 at 21:57 +0200, Georges Khaznadar wrote: with bar, the replacement would be: bar -s 4G -if someImageFile -of /dev/disk/by-id/usb-TheNiceStick_0878101B77D1D977-0:0 pv -petrb someImageFile /dev/disk/... (Or pipe to sudo dd

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Peter Samuelson
[Georges Khaznadar] Is pv able to do the same? for example how can I use pv to monitor the transfer which is done by modifying a command such as: dd if=someImageFile of=/dev/disk/by-id/usb-TheNiceStick_0878101B77D1D977-0:0 pv someImageFile

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Don Armstrong
On Mon, 16 Aug 2010, Georges Khaznadar wrote: Don Armstrong a écrit : [as a handfull of other vigilant developers] How does this [bar] differ from pv? I used Michael Peek's bar for a few years because I never heard about pv. Thank you for this notice. No problem.[1] Is pv able to do

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Georges Khaznadar
Lars Wirzenius a écrit : I haven't tried bar, but from the description it looks very similar to pv. As far as I care, both are welcome in Debian, but sometimes it is sensible to ask if duplicate tools to do the same thing are a good idea. Bar is sufficiently close to pv in terms of

Bug#593260: ITP: bar -- Show information about a data transfer

2010-08-16 Thread Georges Khaznadar
Thank you for all the feedback about pv (and bar). I shall close this bugreport and I won't upload bar. Best regards, Georges. Don Armstrong a écrit : On Mon, 16 Aug 2010, Georges Khaznadar wrote: Don Armstrong a écrit : [as a handfull of other vigilant developers]