On Fri, Jul 28, 2017 at 07:04:51PM +0200, Peter wrote:
> Glen Barber wrote:
> > On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote:
> > > After upgrading to 11.1-RELEASE, a new line appears in the output of "top"
> > > which contains rubbish:
> >
On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote:
> After upgrading to 11.1-RELEASE, a new line appears in the output of "top"
> which contains rubbish:
>
> > last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46
> > 03:23:51
> > 1030 processes:9 running, 1004 sleeping, 17 wa
On Fri, Jul 28, 2017 at 03:24:50PM +0200, Peter wrote:
> After upgrading to 11.1-RELEASE, a new line appears in the output of "top"
> which contains rubbish:
>
> > last pid: 10789; load averages: 5.75, 5.19, 3.89up 0+00:34:46
> 03:23:51
> > 1030 processes:9 running, 1004 sleeping, 17 waiti
Hi Sydney,
The release date in UPDATING actually was a mistake. (I looked at the
wrong month...)
Glen
On Sun, Jul 23, 2017 at 10:23:43PM +0200, Sydney Meyer via freebsd-stable wrote:
> Hi Dimitry,
>
> thank you for your reply.
>
> Please excuse me if i came across impatiently, that was not my
On Mon, Jul 17, 2017 at 03:47:08PM +0200, Vlad K. wrote:
> On 2017-07-17 15:33, Glen Barber wrote:
> >
> > No, this is not available in the 11.1 installer.
> >
>
> Thanks but that's why I asked why's that. r320674 said MFC after 1 day. Is
> it too late
On Mon, Jul 17, 2017 at 11:54:06AM +0200, Vlad K. wrote:
> Hello list,
>
> the stack_guard hardening option in bsdinstall is now setting 512 pages of
> it in CURRENT, as of r320674. It's said to MFC after 1 day (on Jul 5th), but
> STABLE hasn't got it yet. Is this simply an omission (understandabl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The third RC build of the 11.1-RELEASE release cycle is now available.
This is expected to be the final RC build of the 11.1-RELEASE cycle.
Installation images are available for:
o 11.1-RC3 amd64 GENERIC
o 11.1-RC3 i386 GENERIC
o 11.1-RC3 powerpc G
On Thu, Jul 13, 2017 at 05:06:12PM -0700, Mark Johnston wrote:
> On Thu, Jul 13, 2017 at 01:06:30PM +0000, Glen Barber wrote:
> > On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote:
> > > On 07/10/2017 10:48 PM, Konstantin Belousov wrote:
> > > > On Mon, Ju
On Wed, Jul 12, 2017 at 11:29:05PM -0700, jungle boogie wrote:
> On 07/10/2017 10:48 PM, Konstantin Belousov wrote:
> > On Mon, Jul 10, 2017 at 01:00:05PM -0700, Mark Johnston wrote:
> > > I suspect that this is a result of r320763. That change removed a field
> > > from struct vm_map_entry, which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
[Note: The only revised part of the email is sending with inline PGP
signing.]
The second RC build of the 11.1-RELEASE release cycle is now available.
Installation images are available for:
o 11.1-RC2 amd64 GENERIC
o 11.1-RC2 i386 GENERIC
o 11.1-R
The second RC build of the 11.1-RELEASE release cycle is now available.
Installation images are available for:
o 11.1-RC2 amd64 GENERIC
o 11.1-RC2 i386 GENERIC
o 11.1-RC2 powerpc GENERIC
o 11.1-RC2 powerpc64 GENERIC64
o 11.1-RC2 sparc64 GENERIC
o 11.1-RC2 armv6 BANANAPI
o 11.1-RC2 armv6 BEAGLEBON
Hi,
Just an FYI, the 11.1-RC2 builds scheduled to begin on July 7 will be
delayed by about a day while re@ waits for a pending change to hit the
releng/11.1 branch.
The schedule at https://www.FreeBSD.org/releases/11.1R/schedule.html
will be updated when they are started.
Glen
On behalf of: re
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first RC build of the 11.1-RELEASE release cycle is now available.
Installation images are available for:
o 11.1-RC1 amd64 GENERIC
o 11.1-RC1 i386 GENERIC
o 11.1-RC1 powerpc GENERIC
o 11.1-RC1 powerpc64 GENERIC64
o 11.1-RC1 sparc64 GENERIC
o 11
On Fri, Jun 30, 2017 at 10:32:23AM +1200, Jonathan Chen wrote:
> On 30 June 2017 at 10:27, Glen Barber wrote:
> > On Fri, Jun 30, 2017 at 10:23:26AM +1200, Jonathan Chen wrote:
> >> Hi,
> >>
> >> I've got a dual boot system at home, booting into Windows 1
On Fri, Jun 30, 2017 at 10:23:26AM +1200, Jonathan Chen wrote:
> Hi,
>
> I've got a dual boot system at home, booting into Windows 10 for
> games. I've noticed that since I updated to 11.1-BETA3, a reboot from
> Windows into FreeBSD results in a endless reboot cycle. In order to
> reboot FreeBSD,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The third BETA build of the 11.1-RELEASE release cycle is now available.
Installation images are available for:
o 11.1-BETA3 amd64 GENERIC
o 11.1-BETA3 i386 GENERIC
o 11.1-BETA3 powerpc GENERIC
o 11.1-BETA3 powerpc64 GENERIC64
o 11.1-BETA3 sparc64
On Mon, Jun 19, 2017 at 08:29:08PM +, Glen Barber wrote:
> On Mon, Jun 19, 2017 at 10:24:59PM +0200, Ed Schouten wrote:
> > Hi Glen,
> >
> > [ +stable ]
> >
> > 2017-06-15 18:54 GMT+02:00 Glen Barber :
> > > As a reminder, the 11.1-BETA2 builds are s
On Mon, Jun 19, 2017 at 10:24:59PM +0200, Ed Schouten wrote:
> Hi Glen,
>
> [ +stable ]
>
> 2017-06-15 18:54 GMT+02:00 Glen Barber :
> > As a reminder, the 11.1-BETA2 builds are scheduled to begin 16 June 2017
> > at 00:00 UTC (roughly 7 hours from now).
>
> I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The second BETA build of the 11.1-RELEASE release cycle is now
available.
Installation images are available for:
o 11.1-BETA2 amd64 GENERIC
o 11.1-BETA2 i386 GENERIC
o 11.1-BETA2 powerpc GENERIC
o 11.1-BETA2 powerpc64 GENERIC64
o 11.1-BETA2 sparc64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first BETA build of the 11.1-RELEASE release cycle is now available.
Installation images are available for:
o 11.1-BETA1 amd64 GENERIC
o 11.1-BETA1 i386 GENERIC
o 11.1-BETA1 powerpc GENERIC
o 11.1-BETA1 powerpc64 GENERIC64
o 11.1-BETA1 sparc64
On Wed, May 24, 2017 at 08:28:37AM -0700, jungle Boogie wrote:
> On 24 May 2017 at 08:19, Glen Barber wrote:
> > On Tue, May 23, 2017 at 01:14:56PM -0700, jungle Boogie wrote:
> >> Hi Eric,
> >> On 23 May 2017 at 05:47, Eric Badger wrote:
> >> > O
On Tue, May 23, 2017 at 01:14:56PM -0700, jungle Boogie wrote:
> Hi Eric,
> On 23 May 2017 at 05:47, Eric Badger wrote:
> > On 04/26/2017 09:01 AM, David Boyd wrote:
> >>
> >> Using 11.0-STABLE VM image snapshots, since April 05, 2017, FreeBSD
> >> panics when VBoxService starts.
> >>
> >> using s
On Sat, Nov 05, 2016 at 02:46:49PM +1100, Ian Smith wrote:
> On Fri, 4 Nov 2016 14:44:52 +0000, Glen Barber wrote:
> > On Fri, Nov 04, 2016 at 06:50:16PM +1100, Ian Smith wrote:
>
> > > 1431696 2048 md0p4 freebsd-swap (1.0M)
>
> > I would need to l
On Fri, Nov 04, 2016 at 06:50:16PM +1100, Ian Smith wrote:
> Still wondering .. I have no spare box to install 11.0 on at present but
> want to be sure the memstick mentioned below will be fit for purpose.
> I can easily add a 1.0MB swap partition to that, but is it necessary?
>
> From:
> # $Fr
On Fri, Oct 07, 2016 at 10:52:37AM +0200, Johan Hendriks wrote:
> Op 06/10/2016 om 22:18 schreef Glen Barber:
> > As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
> > several issues that were discovered after the release was built. Extra
> > caution is b
On Fri, Oct 07, 2016 at 08:57:26AM -0700, jungle Boogie wrote:
> On 6 October 2016 at 13:18, Glen Barber wrote:
> > the final release announcement is planned for Monday, October 10.
>
> suggestion:
> update the schedule
> https://www.freebsd.org/releases/11.0R/schedule.htm
As many of you are aware, 11.0-RELEASE needed to be rebuilt to address
several issues that were discovered after the release was built. Extra
caution is being taken in testing the rebuilt releases, so at present,
the final release announcement is planned for Monday, October 10.
Thank you for your
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear FreeBSD Community:
[Corrected the date.]
Although the FreeBSD 11.0-RELEASE has not yet been officially announced,
many have found images on the Project FTP mirrors.
However, please be aware the final 11.0-RELEASE will be rebuilt and
republish
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Dear FreeBSD Community:
Although the FreeBSD 11.0-RELEASE has not yet been officially announced,
many have found images on the Project FTP mirrors.
However, please be aware the final 11.0-RELEASE will be rebuilt and
republished on the Project mirro
Bah.
I'll add this to the errata.html page that it was turned off. It's my
fault.
Glen
On Thu, Sep 22, 2016 at 12:30:40PM -0700, Mark Millard wrote:
> https://svnweb.freebsd.org/base/releng/11.0/release/doc/en_US.ISO8859-1/relnotes/article.xml?revision=306207&view=markup
>
> says. . .
>
>
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The third RC build of the 11.0-RELEASE release cycle is now available.
Installation images are available for:
o 11.0-RC3 amd64 GENERIC
o 11.0-RC3 i386 GENERIC
o 11.0-RC3 powerpc GENERIC
o 11.0-RC3 powerpc64 GENERIC64
o 11.0-RC3 sparc64 GENERIC
o 11
On Fri, Sep 16, 2016 at 12:35:40PM -0700, Lacey Powers wrote:
> Hello Everyone,
>
> Whenever I try to run freebsd-update to go from 11.0-RC2 to 11.0-RC3, I
> get the following error:
>
> # freebsd-update upgrade -r 11.0-RC3
>
> Looking up update.FreeBSD.org mirrors... 4 mirrors found.
> Fetching
There is one issue that was brought to our attention, which we are
waiting for feedback before classifying as an EN candidate. Once we
receive feedback, the 11.0-RELEASE schedule should be updated to reflect
reality.
At present, I am hopeful 11.0-RC3 builds should start 9/14/2016 at 00:00
UTC (ab
On Fri, Sep 09, 2016 at 10:08:50AM -0400, Shawn Webb wrote:
> Hey Glen,
>
> I'm just checking in to see if you saw this bug report I filed:
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212418
>
> It affects 11.0-RC2.
>
Sorry for the delayed reply. No, I did not.
Superficially, it lo
On Thu, Sep 08, 2016 at 07:04:25PM -0600, Brett Glass wrote:
> At 09:50 PM 9/7/2016, you wrote:
>
> >I find reading the freebsd-stable@freebsd.org list, particularly the
> >messages from one Glen Barber on behalf of re@ particularly helpful in
> >this regard.
>
>
On Fri, Sep 02, 2016 at 12:13:51AM +0300, Slawa Olhovchenkov wrote:
> Do you planed to fix issuse with missied and delete libmap32.conf?
>
Is there a PR about this? This issue does not sound familiar, so I am
not sure it is (or was) on our radar.
Glen
signature.asc
Description: PGP signature
As some of you may be aware, a few last-minute showstoppers appeared
since 11.0-RC1 (and before RC1).
One of the showstoppers has been fixed in 12-CURRENT, and merged to
stable/11 and releng/11.0 that affected booting from large volumes:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=212139
On Thu, Aug 25, 2016 at 08:43:18AM +0200, Jochen Neumeister wrote:
> On 25.08.2016 08:32, Glen Barber wrote:
> > On Thu, Aug 25, 2016 at 08:29:11AM +0200, Jochen Neumeister wrote:
> >> On 25.08.2016 06:53, Glen Barber wrote:
> >>> On Thu, Aug 25, 2016 at 03:14
On Thu, Aug 25, 2016 at 08:29:11AM +0200, Jochen Neumeister wrote:
> On 25.08.2016 06:53, Glen Barber wrote:
> > On Thu, Aug 25, 2016 at 03:14:20AM +0000, Glen Barber wrote:
> >> [...]
> >> === Upgrading ===
> >>
> >> The freebsd-update(8) utili
On Thu, Aug 25, 2016 at 03:14:20AM +, Glen Barber wrote:
> [...]
> === Upgrading ===
>
> The freebsd-update(8) utility supports binary upgrades of amd64 and i386
> systems running earlier FreeBSD releases. Systems running earlier
> FreeBSD releases can
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The second RC build of the 11.0-RELEASE release cycle is now available.
Installation images are available for:
o 11.0-RC2 amd64 GENERIC
o 11.0-RC2 i386 GENERIC
o 11.0-RC2 powerpc GENERIC
o 11.0-RC2 powerpc64 GENERIC64
o 11.0-RC2 sparc64 GENERIC
o 1
On Mon, Aug 22, 2016 at 10:53:06PM -0500, Karl Denninger wrote:
> On 8/22/2016 22:43, Glen Barber wrote:
> > On Thu, Aug 18, 2016 at 11:30:24PM +0000, Glen Barber wrote:
> >> Two issues have been brought to our attention, and as a result, 11.0-RC2
> >> builds will be
On Thu, Aug 18, 2016 at 11:30:24PM +, Glen Barber wrote:
> Two issues have been brought to our attention, and as a result, 11.0-RC2
> builds will be delayed a day or two while these are investigated.
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872
> https://b
Two issues have been brought to our attention, and as a result, 11.0-RC2
builds will be delayed a day or two while these are investigated.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211872
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211926
An update will be sent if the delay is lon
On Sat, Aug 13, 2016 at 01:30:56AM +, Glen Barber wrote:
> o OpenSSH DSA keys have been disabled by default. Users upgrading from
> prior FreeBSD versions are urged to update their SSH keys to DSA or
> ECDSA keys before upgrading to 11.0-RC1.
>
Note, this should have suggest
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first RC build of the 11.0-RELEASE release cycle is now available.
Installation images are available for:
o 11.0-RC1 amd64 GENERIC
o 11.0-RC1 i386 GENERIC
o 11.0-RC1 powerpc GENERIC
o 11.0-RC1 powerpc64 GENERIC64
o 11.0-RC1 sparc64 GENERIC
o 11
On Mon, Aug 08, 2016 at 11:22:27AM -0700, Nathan Whitehorn wrote:
>
>
> On 08/08/16 10:56, Glen Barber wrote:
> >On Mon, Aug 08, 2016 at 10:53:26AM -0700, Nathan Whitehorn wrote:
> >>
> >>On 08/08/16 10:43, Lars Engels wrote:
> >>>On Mon, Aug 08
On Mon, Aug 08, 2016 at 10:53:26AM -0700, Nathan Whitehorn wrote:
>
>
> On 08/08/16 10:43, Lars Engels wrote:
> >On Mon, Aug 08, 2016 at 10:15:07AM -0700, Devin Teske wrote:
> >>>On Aug 8, 2016, at 8:02 AM, Lars Engels wrote:
> >>>
> >>>On
On Mon, Aug 08, 2016 at 10:48:30AM +0200, Lars Engels wrote:
> On Sat, Aug 06, 2016 at 09:05:26PM +0000, Glen Barber wrote:
> > -BEGIN PGP SIGNED MESSAGE-
>
> > o The new system hardening options have been fixed to avoid overwriting
> > other options sele
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The fourth BETA build of the 11.0-RELEASE release cycle is now
available.
Installation images are available for:
o 11.0-BETA4 amd64 GENERIC
o 11.0-BETA4 i386 GENERIC
o 11.0-BETA4 powerpc GENERIC
o 11.0-BETA4 powerpc64 GENERIC64
o 11.0-BETA4 sparc64
On Fri, Aug 05, 2016 at 01:59:18AM +, Glen Barber wrote:
> This is a heads-up that OpenSSH keys are deprecated upstream by OpenSSH,
> and will be deprecated effective 11.0-RELEASE (and preceeding RCs).
>
Stupid editor mistake. OpenSSH DSA keys are deprecated upstream. Sorr
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
This is a heads-up that OpenSSH keys are deprecated upstream by OpenSSH,
and will be deprecated effective 11.0-RELEASE (and preceeding RCs).
Please see r303716 for details on the relevant commit, but upstream no
longer considers them secure. Please
As those of you tracking our PR system are probably aware, re@ is aware
of an issue related to ZFS and VFS that we feel is urgent enough to have
fixed for 11.0-RELEASE.
https://lists.freebsd.org/pipermail/freebsd-current/2016-August/062829.html
As such, instead of branching releng/11.0 today and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The third BETA build of the 11.0-RELEASE release cycle is now available.
Installation images are available for:
o 11.0-BETA3 amd64 GENERIC
o 11.0-BETA3 i386 GENERIC
o 11.0-BETA3 powerpc GENERIC
o 11.0-BETA3 powerpc64 GENERIC64
o 11.0-BETA3 sparc64
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The second BETA build of the 11.0-RELEASE release cycle is now
available.
Installation images are available for:
o 11.0-BETA2 amd64 GENERIC
o 11.0-BETA2 i386 GENERIC
o 11.0-BETA2 powerpc GENERIC
o 11.0-BETA2 powerpc64 GENERIC64
o 11.0-BETA2 sparc64
On Fri, Jul 15, 2016 at 12:08:57AM +, Glen Barber wrote:
> On Wed, Jul 13, 2016 at 11:10:17PM +0000, Glen Barber wrote:
> > As I am sure you have already seen, there is an issue in 11.0-BETA1 that
> > has caused some headaches for people.
> >
> > https:
On Wed, Jul 13, 2016 at 11:10:17PM +, Glen Barber wrote:
> As I am sure you have already seen, there is an issue in 11.0-BETA1 that
> has caused some headaches for people.
>
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
>
> The issue is actively being investi
As I am sure you have already seen, there is an issue in 11.0-BETA1 that
has caused some headaches for people.
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210884
The issue is actively being investigated, and despite the KBI freeze,
the fix may need to break KBI in stable/11, at least as fa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first BETA build of the 11.0-BETA1 release cycle is now available.
Installation images are available for:
o 11.0-BETA1 amd64 GENERIC
o 11.0-BETA1 i386 GENERIC
o 11.0-BETA1 powerpc GENERIC
o 11.0-BETA1 powerpc64 GENERIC64
o 11.0-BETA1 sparc64 GE
On Fri, Jul 08, 2016 at 02:14:48PM -0700, Mark Millard wrote:
> On Fri, Jul 08, 2016 at 09:23:43AM -0400, Michael Butler wrote: > Seems to be
> a typo .. TARGET_CPUARCH should be TARGET_ARCH ..
> >
>
> ${TARGET_CPUARCH} != "arm" apparently was an attempt to not explicitly test
> for each
Despite my dissatisfaction with this status update, I'll reply to an
email in public...
On Sun, May 01, 2016 at 08:16:38PM -0700, Jordan Hubbard wrote:
>
> > On May 1, 2016, at 5:49 PM, Warren Block wrote:
> >
> > The first quarter of 2016 showed that FreeBSD retains a strong sense of
> > i
On Wed, Mar 09, 2016 at 05:07:57AM +, Glen Barber wrote:
> On Wed, Mar 09, 2016 at 03:54:07PM +1100, Morgan Reed wrote:
> > Hi All,
> >
> > Been fighting this one for a while and I figure it's time to take it to
> > the brainstrust.
> >
> > I&#
On Wed, Mar 09, 2016 at 03:54:07PM +1100, Morgan Reed wrote:
> Hi All,
>
> Been fighting this one for a while and I figure it's time to take it to
> the brainstrust.
>
> I've recently added a third storage array to my NAS, it's a RAID-Z pool the
> same as the other two arrays in the box, the
On Mon, Mar 07, 2016 at 08:33:17PM +, David Boyd wrote:
> /usr/sbin/unbound-control-setup is missing from the 10.3-RC1 release media
> (at least disc1.iso and memstick.img).
>
>
> I have filed PR 207748 reporting this.
>
It was removed in r295690.
Glen
signature.asc
Description: PGP si
On Thu, Mar 03, 2016 at 02:30:53PM -0800, Maxim Sobolev wrote:
> Got this nice crash after switching base system from 10.2 to 10.3-beta
> (without updating installing packages):
>
> File "/usr/local/lib/python2.7/site-packages/cffi/verifier.py", line 207,
> in _load_library
> return self._ve
On Fri, Jan 29, 2016 at 05:47:46PM +, Glen Barber wrote:
> CC'd smh, who committed an update recently in this file. I have
> confirmed the failure (but do not understand why I did not see it when
> testing the patch...).
>
> Steven, can you please take a look at thi
CC'd smh, who committed an update recently in this file. I have
confirmed the failure (but do not understand why I did not see it when
testing the patch...).
Steven, can you please take a look at this?
Glen
On Fri, Jan 29, 2016 at 05:42:10PM +, John wrote:
> Hi,
>
> I get the following err
On Wed, Jan 06, 2016 at 06:07:24AM -0800, David Wolfskill wrote:
> On Wed, Jan 06, 2016 at 01:43:22PM +0000, Glen Barber wrote:
> > On Wed, Jan 06, 2016 at 05:40:15AM -0800, David Wolfskill wrote:
> > > On Wed, Jan 06, 2016 at 01:32:10PM +, Glen Barber wrote:
> > > &
On Wed, Jan 06, 2016 at 05:40:15AM -0800, David Wolfskill wrote:
> On Wed, Jan 06, 2016 at 01:32:10PM +0000, Glen Barber wrote:
> > ...
> > > > Maybe it's simply a matter of overriding KERNCONF at the command line
> > > > while running make installkernel.
&g
On Wed, Jan 06, 2016 at 01:28:33PM +, Glen Barber wrote:
> On Wed, Jan 06, 2016 at 01:45:39PM +0100, Trond Endrestøl wrote:
> > Hi,
> >
> > I'm running stable/10, amd64, r293231, and KERNCONF in /etc/src.conf
> > lists three kernel configuration files, E5530
On Wed, Jan 06, 2016 at 01:45:39PM +0100, Trond Endrestøl wrote:
> Hi,
>
> I'm running stable/10, amd64, r293231, and KERNCONF in /etc/src.conf
> lists three kernel configuration files, E5530, GENERIC, and ZFS, in
> that order.
>
> The former is the preferred kernel, while the other two simply
On Thu, Nov 26, 2015 at 01:39:37AM +0800, Li-Wen Hsu wrote:
> On Wed, Nov 25, 2015 at 10:34:47 +0000, Glen Barber wrote:
> > On Wed, Nov 25, 2015 at 10:31:28AM +0000, Glen Barber wrote:
> > > On Mon, Nov 23, 2015 at 07:15:40PM +0100, Baptiste Daroussin wrote:
> > > >
On Wed, Nov 25, 2015 at 10:31:28AM +, Glen Barber wrote:
> On Mon, Nov 23, 2015 at 07:15:40PM +0100, Baptiste Daroussin wrote:
> > > The build happens in a jail built every time the job starts, by fetching
> > > the latest snapshot from:
> > >
> >
On Mon, Nov 23, 2015 at 07:15:40PM +0100, Baptiste Daroussin wrote:
> > The build happens in a jail built every time the job starts, by fetching
> > the latest snapshot from:
> >
> > http://ftp.freebsd.org/pub/FreeBSD/snapshots/i386/i386/11.0-CURRENT/base.txz
> >
> > It looks there is no /usr/bin
On Mon, Aug 17, 2015 at 06:50:22PM +0300, Slawa Olhovchenkov wrote:
> On Sun, Aug 16, 2015 at 07:16:03PM +0200, Christian Kratzer wrote:
>
> > Hi,
> >
> > I have been trying to update several of my FreeBSD 10.1 amd64 VM to
> > 10.2-RELEASE with freebsd-update and have been failing with an incorr
On Thu, Aug 13, 2015 at 04:04:54AM +, jenkins-ad...@freebsd.org wrote:
> FreeBSD_stable_10 - Build #1616 - Failure:
>
> Build information: https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/1616/
> Full change log:
> https://jenkins.FreeBSD.org/job/FreeBSD_stable_10/1616/changes
> Full build l
On Wed, Aug 12, 2015 at 03:54:42PM -0700, Sean Bruno wrote:
> On 08/12/15 15:43, Glen Barber wrote:
> > On Wed, Aug 12, 2015 at 03:41:21PM -0700, Sean Bruno wrote:
> >> On 08/12/15 15:15, Glen Barber wrote:
> >>> On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote
On Wed, Aug 12, 2015 at 03:41:21PM -0700, Sean Bruno wrote:
> On 08/12/15 15:15, Glen Barber wrote:
> > On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
> >> I was reading through the Release notes, and decided to enable
> >> net.inet.tcp.pmtud_blackhole_detec
On Wed, Aug 12, 2015 at 01:09:31PM -0500, dweimer wrote:
> I was reading through the Release notes, and decided to enable
> net.inet.tcp.pmtud_blackhole_detection in my test environment. It appears
> that the monitoring tunable net.inet.tcp.pmtud_blackhole_min_activated is
> incorrectly listed. Usi
Hopefully the final status update before the final release announcement.
As of r28, releng/10.2 has been renamed to reflect -RELEASE status,
and the 10.2-RELEASE builds have been started (a bit earlier than the
original schedule planned).
Please keep in mind, the release is not final until th
On Sat, Aug 08, 2015 at 10:47:09AM +0900, Daisuke Aoyama wrote:
> Hi all,
>
> I have a problem with build kernel.
> You cannot use "device qlxgbe" in kernel config.
> I don't check but 11-current have same problem.
>
> It is caused by r284982 and r284741.
> New files were added but static files w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The third RC build of the 10.2-RELEASE release cycle is now available.
This is expected to be the final RC build of this release cycle.
Installation images are available for:
o amd64 GENERIC
o i386 GENERIC
o ia64 GENERIC
o powerpc GENERIC
o powerpc
Now that I'm fairly certain I have the day of the week straightened out,
let's try this again...
10.2-RC3 builds will begin in just under 20 hours.
At this time, re@ is not accepting commit approval requests for the
releng/10.2 branch, and all known critical issues we are aware of at
this time ha
On Wed, Aug 05, 2015 at 05:09:49PM -0300, Marcelo Gondim wrote:
> On 05-08-2015 16:53, Glen Barber wrote:
> >On Wed, Aug 05, 2015 at 04:41:40PM -0300, Marcelo Gondim wrote:
> >>I found the following problem with the pw:
> >>
> >>FreeBSD srv.teste.com.br 10.1-ST
On Wed, Aug 05, 2015 at 04:41:40PM -0300, Marcelo Gondim wrote:
> I found the following problem with the pw:
>
> FreeBSD srv.teste.com.br 10.1-STABLE FreeBSD 10.1-STABLE #14 r276979: Wed
> Jan 21 11:50:11 BRST 2015 r...@srv.teste.com.br:/usr/obj/usr/src/sys/TESTE
> amd64
>
> # pw useradd foo
> #
On Wed, Aug 05, 2015 at 01:33:24AM +, Glen Barber wrote:
> As noted in the previous heads-up email, we will have 10.2-RC3 as part
> of this release cycle. The 10.2-RC3 builds will begin in just under 22
> hours.
>
Sigh. I've clearly lost all track of what day
As noted in the previous heads-up email, we will have 10.2-RC3 as part
of this release cycle. The 10.2-RC3 builds will begin in just under 22
hours.
At this time, re@ is not accepting commit request approvals for the
releng/10.2 branch, and all known critical issues we are aware of at
this time h
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The second RC build of the 10.2-RELEASE release cycle is now available.
Installation images are available for:
o amd64 GENERIC
o i386 GENERIC
o ia64 GENERIC
o powerpc GENERIC
o powerpc64 GENERIC64
o sparc64 GENERIC
The image checksums follow at th
On Fri, Jul 31, 2015 at 01:48:32AM +, Glen Barber wrote:
> The new driver for PMC Sierra SAS/SATA HBAs does not properly validate
> that both the vendor ID and device ID of some storage device drivers.
> At present, we know there is a conflict with ahd(4), it is possible
> th
On Fri, Jul 31, 2015 at 09:20:49AM +0200, Kurt Jaeger wrote:
> Hi!
>
> > prior to the releng/10.2 branch), please exercise caution when upgrading
> > to the latest stable/10 or releng/10.2 if your storage controller
> > matches any of the following PCI device IDs:
>
> Which field of pciconf -lvb
The new driver for PMC Sierra SAS/SATA HBAs does not properly validate
that both the vendor ID and device ID of some storage device drivers.
At present, we know there is a conflict with ahd(4), it is possible
there are more.
The issue was reported on the -current@ mailing list in this thread:
htt
The 10.2-RC2 builds will begin in just under 5 hours.
At this time, re@ is no longer accepting commit request approvals to the
releng/10.2 branch, however a last-minute issue was discovered with the
pms(4) driver for PMC Sierra SAS/SATA HBA cards that is currently being
investigated.
It is unclea
On Wed, Jul 29, 2015 at 01:09:05AM +0300, Slawa Olhovchenkov wrote:
> On Tue, Jul 28, 2015 at 09:45:28PM +0000, Glen Barber wrote:
>
> > On Wed, Jul 29, 2015 at 12:42:12AM +0300, Slawa Olhovchenkov wrote:
> > > On Sat, Jul 25, 2015 at 02:27:50AM +, Glen Barber wrote:
On Wed, Jul 29, 2015 at 12:42:12AM +0300, Slawa Olhovchenkov wrote:
> On Sat, Jul 25, 2015 at 02:27:50AM +0000, Glen Barber wrote:
>
> > On Fri, Jul 24, 2015 at 06:36:32PM +0300, Slawa Olhovchenkov wrote:
> > > On Fri, Jul 24, 2015 at 08:25:55AM -0700, Navdeep Parhar wrote:
On Mon, Jul 27, 2015 at 04:32:34PM +0200, Willem Jan Withagen wrote:
> On 27/07/2015 16:25, Glen Barber wrote:
> > On Mon, Jul 27, 2015 at 04:14:54PM +0200, Willem Jan Withagen wrote:
> >> On 27/07/2015 04:39, Benjamin Kaduk wrote:
> >>> * Separated email service
On Mon, Jul 27, 2015 at 04:14:54PM +0200, Willem Jan Withagen wrote:
> On 27/07/2015 04:39, Benjamin Kaduk wrote:
> > * Separated email services (and single-point-of-failure cases) from
> > the machine that has been handling this task for over 18 years, to
> > new, single-purpose service
On Fri, Jul 24, 2015 at 06:36:32PM +0300, Slawa Olhovchenkov wrote:
> On Fri, Jul 24, 2015 at 08:25:55AM -0700, Navdeep Parhar wrote:
>
> > On Fri, Jul 24, 2015 at 10:50:10AM +0300, Slawa Olhovchenkov wrote:
> > > > >
> > > > > For me -- degradate network performance, about 30%. I am do
> > > > >
On Fri, Jul 24, 2015 at 09:23:12PM -0400, Nikolai Lifanov wrote:
> On 2015-07-24 17:27, Glen Barber wrote:
> >On Fri, Jul 24, 2015 at 05:15:52PM -0400, Nikolai Lifanov wrote:
> >>I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from
> >>using
> >>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The first RC build of the 10.2-RELEASE release cycle is now available.
Installation images are available for:
o amd64 GENERIC
o i386 GENERIC
o ia64 GENERIC
o powerpc GENERIC
o powerpc64 GENERIC64
o sparc64 GENERIC
The image checksums follow at the
On Fri, Jul 24, 2015 at 05:15:52PM -0400, Nikolai Lifanov wrote:
> I noticed that in stable/10, /etc/pkg/FreeBSD.conf was switched from using
> latest package set to whichever one that is "quarterly" word is pointing to
> at the moment. What is the motivation for this change?
>
This was not done
101 - 200 of 389 matches
Mail list logo
