On Sat, 1 Apr 2017 01:36:54 +0300 "Andrey V. Elsukov" wrote
> On 01.04.2017 00:58, Chris H wrote:
> > So. I spin up an old 11 server I have sitting in the closet, with
> > this external drive attached to it. I do *NOT* get the corrupt GPT
> > message. So I blank/partition/newfs the external drive
On 2017-Mar-30, at 7:51 PM, Mark Millard wrote:
> On 2017-Mar-30, at 1:22 PM, Mark Millard wrote:
>
>> Sounds like the ALLOW_OPTIMIZATIONS_FOR_WITH_DEBUG technique
>> would not change the "WITNESS and INVARIANTS"-like part of the
>> issue. In fact if WITH_DEBUG= causes the cmake debug-style
>>
On 01.04.2017 00:58, Chris H wrote:
> So. I spin up an old 11 server I have sitting in the closet, with
> this external drive attached to it. I do *NOT* get the corrupt GPT
> message. So I blank/partition/newfs the external drive &&
> mount the partitions individually to /mnt && restore again. When
Hi I brought this up earlier, but didn't have as
much to go on as I do now. So I'd like to try this again;
On a recent(ish) install of CURRENT followed by a new
kernel/world. I'm finding I can't depend on geom(8) for
anything, but the primary (SATA3) drive, it's installed on
(if even that). To the
On 31 Mar 2017, at 13:57, Pavel Timofeev wrote:
Hello, dear freebsd-current@!
There was FreeBSD Foundation report back in 2016Q2 where it told us
about VNET (VIMAGE) update project sponsored by foundation.
What is the current situation? Is it committed into base? If not
what's the plan?
Chang
Hello, dear freebsd-current@!
There was FreeBSD Foundation report back in 2016Q2 where it told us
about VNET (VIMAGE) update project sponsored by foundation.
What is the current situation? Is it committed into base? If not
what's the plan?
___
freebsd-cu
On Fri, 31 Mar 2017, Andrey Chernov wrote:
On 30.03.2017 21:53, Bruce Evans wrote:
I think it was the sizing. The non-updated mode is 80x25, so the row
address can be out of bounds in the teken layer.
I have text 80x30 mode set at rc stage, and _after_ that may have many
kernel messages on c