Re: "df /" output missing "Filesystem" after r351187 -> r351211

2019-08-19 Thread Cy Schubert
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

Re: HEADSUP: drm-current-kmod now installs sources

2019-08-19 Thread John Baldwin
On 8/16/19 5:33 PM, Rozhuk Ivan wrote: > On Fri, 16 Aug 2019 17:23:08 -0700 > John Baldwin wrote: > >>> I use better way: >>> /etc/make.conf: >>> # Modules to build with kernel. >>> PORTS_MODULES+= graphics/drm-fbsd12.0-kmod >>> graphics/gpu-firmware-kmod >> >> This doesn't work for folks who u

Re: "df /" output missing "Filesystem" after r351187 -> r351211

2019-08-19 Thread Warner Losh
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

Re: "df /" output missing "Filesystem" after r351187 -> r351211

2019-08-19 Thread Mateusz Guzik
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

Re: "df /" output missing "Filesystem" after r351187 -> r351211

2019-08-19 Thread Alan Somers
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 /" output missing "Filesystem" after r351187 -> r351211

2019-08-19 Thread David Wolfskill
"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

Re: Installing drm-current-kmod from ports

2019-08-19 Thread Gary Jennejohn
On Sun, 18 Aug 2019 15:59:34 -0500 "Clay Daniels Jr." wrote: > I intend to buy buy a new computer, and it will be in a tower > case that you can easily get into, maybe with a clear glass or > plastic side. I like to see the lights blink. And I have my > heart set on a Threadripper... > If you