(#3759419) Ticket gesloten door support

2019-05-15 Thread MarMac
-#-#- Antwoord u boven deze lijn alstublieft -#-#- Beste freebsd-stable@freebsd.org, Uw ticket is gesloten door een supportmedewerker. Indien u van mening bent dat het probleem niet volledig is opgelost, dan kunt u antwoorden op deze e-mail. Your ticket has been marked as resolved by a member of

(#2572022) Ticket gesloten door support

2019-05-15 Thread MarMac
-#-#- Antwoord u boven deze lijn alstublieft -#-#- Beste freebsd-stable@freebsd.org, Uw ticket is gesloten door een supportmedewerker. Indien u van mening bent dat het probleem niet volledig is opgelost, dan kunt u antwoorden op deze e-mail. Your ticket has been marked as resolved by a member of

FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Julian H. Stacey
Hi core@, cc hackers@ & stable@ PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html Volunteers who contribute actual fixes are very much appreciated; But those styled as 'management' who delay announcements

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Alan Somers
On Wed, May 15, 2019 at 8:26 AM Julian H. Stacey wrote: > > Hi core@, > cc hackers@ & stable@ > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > Volunteers who contribute actual fixes are very muc

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Kurt Jaeger
Hi! > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > Volunteers who contribute actual fixes are very much appreciated; > But those styled as 'management' who delay announcements to batch floods

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Julian H. Stacey
Kurt Jaeger wrote: > Hi! > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > Volunteers who contribute actual fixes are very much appreciated; > > But those styled as 'management' who d

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Kurt Jaeger
Hi! > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > > Volunteers who contribute actual fixes are very much appreciated; > > > But those styled as 'management' who delay announ

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Julian H. Stacey
Hi, Reference: > From: Alan Somers > Date: Wed, 15 May 2019 08:32:26 -0600 Alan Somers wrote: > On Wed, May 15, 2019 at 8:26 AM Julian H. Stacey wrote: > > > > Hi core@, > > cc hackers@ & stable@ > > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > >

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Julian H. Stacey
Hi, Reference: > From: Kurt Jaeger > Date: Wed, 15 May 2019 17:38:36 +0200 Kurt Jaeger wrote: > Hi! > > > > > PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." > > > > > > > > https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html > > > > > >

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Kurt Jaeger
Hi! > > > Alternative is to for announcers to do Less work: > > > Send each announcement when ready. > > The problem is not the announcement, the problem is providing > > the freebsd-update. > > If announcements are send when ready, and the freebsd-update is > > not ready, therefore, the timefr

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Glen Barber
On Wed, May 15, 2019 at 05:58:38PM +0200, Kurt Jaeger wrote: > Hi! > > > > > Alternative is to for announcers to do Less work: > > > > Send each announcement when ready. > > > > The problem is not the announcement, the problem is providing > > > the freebsd-update. > > > > If announcements are

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Will Andrews
On Wed, May 15, 2019 at 10:45 AM Julian H. Stacey wrote: > Batching also means some of these vulnerabilities could have been > fixed earlier & less of a surge of demand on recipient admins time. > > An admin can find time to ameliorate 1 bug, not 8 suddenly together. > Avoidance is called plannin

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Matt Garber
> On May 15, 2019, at 12:12 PM, Will Andrews wrote: > > On Wed, May 15, 2019 at 10:45 AM Julian H. Stacey wrote: > >> Batching also means some of these vulnerabilities could have been >> fixed earlier & less of a surge of demand on recipient admins time. >> >> An admin can find time to amelio

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Andrea Venturoli
On 5/15/19 6:16 PM, Matt Garber wrote: Exactly. If batching 8 (or more) individual bugs/issues together into one release is really causing admin/manpower overload and angst,then maybe it’s time in your situation to use the binary updates (which would only be a single `freebsd-update` and reboot,

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Julian H. Stacey
Kurt Jaeger wrote: > Hi! > > > > > Alternative is to for announcers to do Less work: > > > > Send each announcement when ready. > > > > The problem is not the announcement, the problem is providing > > > the freebsd-update. > > > > If announcements are send when ready, and the freebsd-update is

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Matt Garber
> On May 15, 2019, at 12:28 PM, Andrea Venturoli wrote: > > On 5/15/19 6:16 PM, Matt Garber wrote: > >> Exactly. If batching 8 (or more) individual bugs/issues together into >> one release is really causing admin/manpower overload and angst,then >> maybe it’s time in your situation to use the b

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Julian H. Stacey
Thanks Will, You make some good points, but all depend on variant circustances. I prefer to be informed ASAP, to make my own decisons with max info ASAP, Not delayed. I want freebsd.org to Not Delay fix announcements into batches. If other admins want to delay being told told to do upgrades unti

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Gordon Tetlow
Hi. Your friendly neighborhood Security Officer here. I published the 5 advisories and 3 errata yesterday. On Wed, May 15, 2019 at 07:15:04PM +0200, Julian H. Stacey wrote: > Thanks Will, > You make some good points, but all depend on variant circustances. > > I prefer to be informed ASAP, to mak

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Greg Veldman
On Wed, May 15, 2019 at 07:15:04PM +0200, Julian H. Stacey wrote: > You make some good points, but all depend on variant circustances. I think there's validity to both points of view, and as you say I think a lot of it depends on circumstance. For example on my personal systems, where I can patch

12.0-RELEASE-p4 kernel panic on i386 boot

2019-05-15 Thread wintellect Auser
Hi all, Wanted to make you aware of an issue I have encountered, sorry if this is the wrong list. I upgraded from FreeBSD 12.0-RELEASE-p3 to p4 using: freebsd-fetch update freebsd-fetch install and use the GENERIC kernel. Upon reboot the system kernel panics when attempting to mount the filesys

12.0-RELEASE-p4 kernel panic on boot

2019-05-15 Thread wintellect Auser
Hi all, Wanted to make you aware of an issue I have encountered, sorry if this is the wrong list. I upgraded from FreeBSD 12.0-RELEASE-p3 to p4 using: freebsd-fetch update freebsd-fetch install and use the GENERIC kernel. Upon reboot the system kernel panics when attempting to mount the filesys

Re: 12.0-RELEASE-p4 kernel panic on i386 boot

2019-05-15 Thread Dan Langille
> Hi all, > > Wanted to make you aware of an issue I have encountered, sorry if this is > the wrong list. > > I upgraded from FreeBSD 12.0-RELEASE-p3 to p4 using: > > freebsd-fetch update > freebsd-fetch install > > and use the GENERIC kernel. Upon reboot the system kernel panics when > attempt

Re: 12.0-RELEASE-p4 kernel panic on i386 boot

2019-05-15 Thread Ed Maste
On Wed, 15 May 2019 at 15:09, wintellect Auser wrote: > > Hi all, > > Wanted to make you aware of an issue I have encountered, sorry if this is > the wrong list. This is the right place and thank you for reporting. Looking into it. ___ freebsd-stable@fr

Re: 12.0-RELEASE-p4 kernel panic on i386 boot

2019-05-15 Thread Ed Maste
On Wed, 15 May 2019 at 00:03, Ed Maste wrote: > > On Wed, 15 May 2019 at 15:09, wintellect Auser > wrote: > > > > Hi all, > > > > Wanted to make you aware of an issue I have encountered, sorry if this is > > the wrong list. > > This is the right place and thank you for reporting. Looking into it

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Steven Hartland
Is disagree, having them hatched causes us less work not more, as others have said one update not many, which result in one outage of systems that need patching not many. Regards Steve On Wed, 15 May 2019 at 16:48, Julian H. Stacey wrote: > Hi, Reference: > > From: Alan Somers >

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Mel Pilgrim
On 2019-05-15 7:25, Julian H. Stacey wrote: Hi core@, cc hackers@ & stable@ PR headline : "FreeBSD flood of 8 breakage announcements in 3 mins." https://lists.freebsd.org/pipermail/freebsd-announce/2019-May/date.html Volunteers who contribute actual fixes are very much appreciated; But those s

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Bill Sorenson
> Admins attentive to security issues will already be tracking CVEs for > the software they use and mitigating or solving the vulnerability by all > means available. > > By batching updates, FreeBSD is making administrative decisions for > other people's systems. Some folks don't need to worry abo

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Matt Garber
On Wed, May 15, 2019 at 10:28 PM Bill Sorenson wrote: > > Admins attentive to security issues will already be tracking CVEs for > > the software they use and mitigating or solving the vulnerability by all > > means available. > > > > By batching updates, FreeBSD is making administrative decisions

FreeBSD-SA-19:03 source code patch

2019-05-15 Thread Greg Balfour
After applying wpa-11.patch (and the rest of the recent patches) to my 11.2 machine I'm having build problems. Looks like a binder directory and associated files did not get created. Pilot error? # uname -a FreeBSD freebsd.example.com 11.2-RELEASE FreeBSD 11.2-RELEASE #0: Thu Jan 3 19:29:29 CST

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Miroslav Lachman
Mel Pilgrim wrote on 2019/05/16 02:30: [...] By batching updates, FreeBSD is making administrative decisions for other people's systems.  Some folks don't need to worry about scheduling downtime and will benefit from faster update availability.  Folks who need to worry about scheduling downti

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Alan Somers
On Wed, May 15, 2019 at 9:14 PM Miroslav Lachman <000.f...@quip.cz> wrote: > > Mel Pilgrim wrote on 2019/05/16 02:30: > > [...] > > > By batching updates, FreeBSD is making administrative decisions for > > other people's systems. Some folks don't need to worry about scheduling > > downtime and wil

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Bill Sorenson
> I’m not sure what you meant about Linux distros not categorizing fixes, > though — with some notable exceptions, most of the big ones certainly tag > security fixes >separately, which is what allows `unattended-upgrades` on > Debian/Ubuntu based systems (and `yum-cron` on RHEL) to work so nice

Re: FreeBSD flood of 8 breakage announcements in 3 mins.

2019-05-15 Thread Matt Garber
On Wed, May 15, 2019 at 11:15 PM Bill Sorenson wrote: > > I’m not sure what you meant about Linux distros not categorizing fixes, > though — with some notable exceptions, most of the big ones certainly tag > security fixes >separately, which is what allows `unattended-upgrades` on > Debian/Ubuntu

P5 bork

2019-05-15 Thread Chris
I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at home doing DoT TLS1.3 Thats all I do on the machine. Its a very clean boring typical install. X86. FreeBSD-update fetch freebsd-update install reboot BORKED. Just loops duing boot. Backed up to kernal.old - works perfect..

Re: P5 bork

2019-05-15 Thread Pete Wright
On 5/15/19 10:15 PM, Chris wrote: I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at home doing DoT TLS1.3 Thats all I do on the machine. Its a very clean boring typical install. X86. FreeBSD-update fetch freebsd-update install reboot BORKED. Just loops duing boot. Backe

Re: P5 bork

2019-05-15 Thread Chris
Thank you Pete :) On 5/15/2019 10:58 PM, Pete Wright wrote: On 5/15/19 10:15 PM, Chris wrote: I am not a sophsicated user.. Im running FreeBSD 12 and Unbound at home doing DoT TLS1.3 Thats all I do on the machine. Its a very clean boring typical install. X86. FreeBSD-update fetch freebsd