Bug#786564: Please add option for extra precision human readable output

2015-06-11 Thread Goswin von Brederlow
On Fri, May 22, 2015 at 05:37:04PM -0400, Michael Stone wrote: On Fri, May 22, 2015 at 11:24:03PM +0200, Goswin von Brederlow wrote: when using df -h the output will use the largest unit that doesn't have a leading 0. This often results in quite imprecise output, e.g. 1.1T or 1.8G. It would be

Bug#786564: Please add option for extra precision human readable output

2015-06-11 Thread Michael Stone
On Thu, Jun 11, 2015 at 11:49:42AM +0200, Goswin von Brederlow wrote: On Fri, May 22, 2015 at 05:37:04PM -0400, Michael Stone wrote: On Fri, May 22, 2015 at 11:24:03PM +0200, Goswin von Brederlow wrote: when using df -h the output will use the largest unit that doesn't have a leading 0. This

Bug#786564: Please add option for extra precision human readable output

2015-05-22 Thread Michael Stone
On Fri, May 22, 2015 at 11:24:03PM +0200, Goswin von Brederlow wrote: when using df -h the output will use the largest unit that doesn't have a leading 0. This often results in quite imprecise output, e.g. 1.1T or 1.8G. It would be nice if instead it cout use the smallest unit that use 4 or less

Bug#786564: Please add option for extra precision human readable output

2015-05-22 Thread Goswin von Brederlow
Package: coreutils Version: 8.21-1.2 Severity: wishlist File: /bin/df Hi, when using df -h the output will use the largest unit that doesn't have a leading 0. This often results in quite imprecise output, e.g. 1.1T or 1.8G. It would be nice if instead it cout use the smallest unit that use 4 or