On 13:59:09, 29.02.16, Theo de Raadt wrote:
> > On 2016-02-29, Michal Mazurek wrote:
> >
> > > If the number of filesystem inodes or blocks is too big, the columns in
> > > the
> > > output of df will become misaligned.
> > >
> > > I'm resending the patch that adds variable width columns to df.
> I could imagine that, but the columns aren't in a fixed place if the number
> of blocks or inodes is greater than a particular value, wouldn't this break
> those scripts already?
On very few machines with long paths, and where people do such foolish
system-dependent parsing operations.
However
> On 2016-02-29, Michal Mazurek wrote:
>
> > If the number of filesystem inodes or blocks is too big, the columns in the
> > output of df will become misaligned.
> >
> > I'm resending the patch that adds variable width columns to df.
>
> I am somewhat worried about scripts that examine the df ou
On 2016-02-29, Michal Mazurek wrote:
> If the number of filesystem inodes or blocks is too big, the columns in the
> output of df will become misaligned.
>
> I'm resending the patch that adds variable width columns to df.
I am somewhat worried about scripts that examine the df output and
expect
If the number of filesystem inodes or blocks is too big, the columns in the
output of df will become misaligned.
I'm resending the patch that adds variable width columns to df. The display
parts of the code have been rewritten, the information gathering code
remains unchanged.
The code first gath
