On Tue, Sep 27, 2016 at 09:46:29PM -0600, Ross Alexander wrote:
> On Fri, 23 Sep 2016 22:19:15 +, Glenn Barber wrote:
>
> >On Sat, Sep 24, 2016 at 12:54:05AM +0300, Boris Samorodov wrote:
> >> 24.09.2016 00:44, Boris Samorodov ?:
> >> > 24.09.2016 00:39, Glen Barber ?:
> >> >> On Sat,
On Tuesday, September 27, 2016 10:31:24 PM Piotr Kubaj wrote:
> No, I get only messages about allocating window.
>
> On 09/26/16 22:48, John Baldwin wrote:
> > On Wednesday, September 21, 2016 11:19:05 AM Piotr Kubaj wrote:
> >> I'm trying to boot the ASUS F2A85-M board with flashed Coreboot 4.4
Hello,
I am currently trying to replace a disk that was offlined and getting the
following error:
# zpool replace tank 14989197580381994958
gptid/31be0527-84f0-11e6-bbbc-fcaa14edc6a6
invalid vdev specification
use '-f' to override the following errors:
No, I get only messages about allocating window.
On 09/26/16 22:48, John Baldwin wrote:
On Wednesday, September 21, 2016 11:19:05 AM Piotr Kubaj wrote:
I'm trying to boot the ASUS F2A85-M board with flashed Coreboot 4.4 and
SeaBIOS 1.9.1 as a payload.
This board works nicely with stock UEFI,
On Tue, Sep 27, 2016 at 07:32:36AM +, Thomas Mueller wrote:
> If I want to keep up with FreeBSD-current with new graphics drivers, is it
> sufficient to keep only the freebsd-base-graphics source tree to avoid the
> redundancy of keeping the regular src tree as well?
I use the drm-next-4.7
If I want to keep up with FreeBSD-current with new graphics drivers, is it
sufficient to keep only the freebsd-base-graphics source tree to avoid the
redundancy of keeping the regular src tree as well?
I notice some things are not updated as frequently in the freebsd-base-graphics
tree; "git
