-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
FreeBSD Project Quarterly Status Report - Second Quarter 2016
Now available: the 2016Q2 model of the FreeBSD Project Status Report!
This quarter brings several exciting improvements over previous models.
We have enhancements from
I'm running today's top of tree, and it doesn't seem to want to connect:
re0: flags=8843 metric 0 mtu 1500
options=8209b
ether 20:47:47:73:07:5f
inet6
On 2016-07-27 22:05, Randy Westlund wrote:
> I'm trying to follow Michael Dexter's post about using bhyve with boot
> environments. It involves moving all child datasets under
> zroot/ROOT/default, so that you can have entirely independent systems.
>
>
I'm trying to follow Michael Dexter's post about using bhyve with boot
environments. It involves moving all child datasets under
zroot/ROOT/default, so that you can have entirely independent systems.
http://callfortesting.org/bhyve-boot-environments/
> Let's change the datasets with "canmount
FreeBSD_HEAD_i386 - Build #3702 - Fixed:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3702/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3702/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3702/console
Change summaries:
On Wed, Jul 27, 2016 at 5:05 PM, Shawn Webb wrote:
> On Wed, Jul 27, 2016 at 05:02:07PM -0700, Conrad Meyer wrote:
>> The problem appears to be an upstream limitation of
>> -fsanitize=safe-stack: "Most programs, static libraries, or individual
>> files can be compiled
On Wed, Jul 27, 2016 at 05:11:12PM -0700, Conrad Meyer wrote:
> On Wed, Jul 27, 2016 at 5:05 PM, Shawn Webb
> wrote:
> > On Wed, Jul 27, 2016 at 05:02:07PM -0700, Conrad Meyer wrote:
> >> The problem appears to be an upstream limitation of
> >> -fsanitize=safe-stack:
On Wed, Jul 27, 2016 at 05:02:07PM -0700, Conrad Meyer wrote:
> On Wed, Jul 27, 2016 at 3:55 PM, Shawn Webb
> wrote:
> > Hey All,
> >
> > I'm interested in getting SafeStack working in FreeBSD base. Below is a
> > link to a simplistic (maybe too simplistic?) patch to
On 7/27/2016 4:55 PM, David Wolfskill wrote:
> On Wed, Jul 27, 2016 at 04:34:39PM -0700, Bryan Drewery wrote:
>> ...
>> These shouldn't happen since libgcc is build in startup_libs and krb5 is
>> built in prebuild_libs, which waits on startup_libs. Very strange.
>>
>> Can you send me the
On Wed, Jul 27, 2016 at 3:55 PM, Shawn Webb wrote:
> Hey All,
>
> I'm interested in getting SafeStack working in FreeBSD base. Below is a
> link to a simplistic (maybe too simplistic?) patch to enable SafeStack.
> The patch applies against HardenedBSD's
On Wed, Jul 27, 2016 at 04:34:39PM -0700, Bryan Drewery wrote:
> ...
> These shouldn't happen since libgcc is build in startup_libs and krb5 is
> built in prebuild_libs, which waits on startup_libs. Very strange.
>
> Can you send me the typescript please?
>
(For folks playing along at home,
On 7/27/2016 5:49 AM, David Wolfskill wrote:
> I track head daily on both my laptop and a "build machine;" I only saw a
> problem on the latter -- not on my laptop.
>
> (The build machine is a bit beefier, and uses an SSD as its non-volatile
> storage; the laptop uses a hybrid disk -- in case
Hey All,
I'm interested in getting SafeStack working in FreeBSD base. Below is a
link to a simplistic (maybe too simplistic?) patch to enable SafeStack.
The patch applies against HardenedBSD's hardened/current/master branch.
Given how simple the patch is, it'd be extremely easy to port over to
On Wed, 27 Jul 2016 14:43:36 -0700
John Baldwin wrote:
> On Tuesday, June 07, 2016 12:06:54 PM Gary Jennejohn wrote:
> > On Tue, 31 May 2016 13:10:06 -0700
> > John Baldwin wrote:
> >
> > > On Saturday, May 28, 2016 02:11:41 PM Gary Jennejohn wrote:
> >
FreeBSD_HEAD_i386 - Build #3701 - Failure:
Build information: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3701/
Full change log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3701/changes
Full build log: https://jenkins.FreeBSD.org/job/FreeBSD_HEAD_i386/3701/console
Change summaries:
On Tuesday, June 07, 2016 12:06:54 PM Gary Jennejohn wrote:
> On Tue, 31 May 2016 13:10:06 -0700
> John Baldwin wrote:
>
> > On Saturday, May 28, 2016 02:11:41 PM Gary Jennejohn wrote:
> > > On Fri, 27 May 2016 09:50:05 +0200
> > > Gary Jennejohn wrote:
>
David Wolfskill wrote:
> The build failed (initially -- a restart worked):
That's usually a good indicator of a race.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To
I track head daily on both my laptop and a "build machine;" I only saw a
problem on the latter -- not on my laptop.
(The build machine is a bit beefier, and uses an SSD as its non-volatile
storage; the laptop uses a hybrid disk -- in case that is useful.)
As indicated in the Subject, in each
On 27/07/2016 7:22 PM, Peter Jeremy wrote:
> I'm trying to boot the 11.0-BETA2/amd64 memory stick image and the
> kernel panics: (Following copied by hand):
>
> ACPI APIC Table:
> ...
> acpi0: on motherboard
> ACPI Error: Hardware did not change modes (20160527/hwacpi-160)
> ACPI Error: Could
I'm trying to boot the 11.0-BETA2/amd64 memory stick image and the
kernel panics: (Following copied by hand):
ACPI APIC Table:
...
acpi0: on motherboard
ACPI Error: Hardware did not change modes (20160527/hwacpi-160)
ACPI Error: Could not transition to APCI mode (20160527/evxfevnt-105)
ACPI
20 matches
Mail list logo