On August 19, 2019 7:15:53 AM PDT, Warner Losh wrote:
>On Mon, Aug 19, 2019 at 8:14 AM Mateusz Guzik
>wrote:
>
>> On 8/19/19, David Wolfskill wrote:
>> > "df" (without the mountpoint specification) is normal, but
>specifying
>> > the mountpoint appears to cause a large number of "space"
>charact
On Mon, Aug 19, 2019 at 8:14 AM Mateusz Guzik wrote:
> On 8/19/19, David Wolfskill wrote:
> > "df" (without the mountpoint specification) is normal, but specifying
> > the mountpoint appears to cause a large number of "space" characters
> > to be emitted after "Filesystem" in the heading, and th
On 8/19/19, David Wolfskill wrote:
> "df" (without the mountpoint specification) is normal, but specifying
> the mountpoint appears to cause a large number of "space" characters
> to be emitted after "Filesystem" in the heading, and the actual
> "filesystem" data to be elided.
>
Should be fixed w
On Mon, Aug 19, 2019 at 5:39 AM David Wolfskill wrote:
>
> "df" (without the mountpoint specification) is normal, but specifying
> the mountpoint appears to cause a large number of "space" characters
> to be emitted after "Filesystem" in the heading, and the actual
> "filesystem" data to be elided
"df" (without the mountpoint specification) is normal, but specifying
the mountpoint appears to cause a large number of "space" characters
to be emitted after "Filesystem" in the heading, and the actual
"filesystem" data to be elided.
E.g.:
freebeast(13.0-C)[1] uname -aUK
FreeBSD freebeast.catwhi
