Unfortunately, the glabel and (especially) GPT partition ID labelling
has in-kernel race conditions that make it impossible to rely on in the
installer. This has been an open problem since FreeBSD 9; hopefully it
will be solved soon.
-Nathan
On 08/02/16 20:35, Alive 4ever wrote:
Greetings, ev
Greetings, everyone.
I am testing FreeBSD 11.0-BETA3 release on a virtual machine (qemu,
with
edkII ovmf).
Currently, bsdinstall creates device path based block device driver
scheme instead of uuid/label based device scheme.
bsdinstall-generated fstab has some drawback. For example, when
switchi
On Tue, Aug 2, 2016 at 11:12 AM, Julian Elischer wrote:
> I upgraded my VPS machine to today's current, and on reboot I couldn't get
> into it by network.
>
> A quick switch to the VNC console showed that it was up but that it
> couldn't get out.
>
>
> The xn interfaces said they were UP but atte
I upgraded my VPS machine to today's current, and on reboot I couldn't
get into it by network.
A quick switch to the VNC console showed that it was up but that it
couldn't get out.
The xn interfaces said they were UP but attempts to get out were met
with "network is down".
if I did 'tcpdu
On Tuesday, August 02, 2016 09:03:10 AM Gary Jennejohn wrote:
> On Mon, 01 Aug 2016 13:19:16 -0700
> John Baldwin wrote:
>
> > On Monday, August 01, 2016 03:31:11 PM Gary Jennejohn wrote:
> > > On Mon, 1 Aug 2016 09:34:34 +0200
> > > Gary Jennejohn wrote:
> > >
> > > > On Sun, 31 Jul 2016 14:
On 08/02/16 05:06, Mateusz Guzik wrote:
> On Mon, Aug 01, 2016 at 09:49:03PM -0400, Michael Butler wrote:
>> In the non-SMP case, ADAPTIVE_MUTEXES is not defined and a subsequent
>> reference to mtx_delay causes compilation of kern_mutex.c to fail
>> because KDTRACE_HOOKS may be,
>>
>
> Indeed, fi
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c: In function
'alloc_memseg':
/usr/src/sys/modules/vmm/../../amd64/vmm/vmm_dev.c:261:3: error: null
argument where non-null required (argument 1) [-Werror=nonnull]
error = copystr(VM_MEMSEG_NAME(mseg), name, SPECNAMELEN + 1, 0);
This is with amd
On 01.08.16 12:05, O. Hartmann wrote:
> On every(!) USB drive which worked well with 11-CURRENT up to 11-BETA, I fail
> to access with 12-CURRENT (12.0-CURRENT FreeBSD 12.0-CURRENT #14 r303475: Fri
> Jul 29 11:59:11 CEST 2016) with the error shown below.
>
> On USB flash drives I created myself, t
> On 01 Aug 2016, at 19:30, Michelle Sullivan wrote:
>
> There are reasons for using either…
Indeed, but my decision was to run ZFS. And getting a HBA in some
configurations can be difficult because vendors insist on using
RAID adapters. After all, that’s what most of their customers demand.
On Mon, 01 Aug 2016 13:19:16 -0700
John Baldwin wrote:
> On Monday, August 01, 2016 03:31:11 PM Gary Jennejohn wrote:
> > On Mon, 1 Aug 2016 09:34:34 +0200
> > Gary Jennejohn wrote:
> >
> > > On Sun, 31 Jul 2016 14:22:35 -0700
> > > John Baldwin wrote:
> > >
> > > > On Sunday, July 31, 20
10 matches
Mail list logo
