Date: Wed, 15 May 2019 22:15:08 -0500 From: Bill Sorenson <instructionset@gmail.com> To: Matt Garber <matt.garber@gmail.com> Cc: "Julian H. Stacey" <jhs@berklix.com>, Mel Pilgrim <list_freebsd@bluerosetech.com>, core@freebsd.org, hackers@freebsd.org, stable@freebsd.org Subject: Re: FreeBSD flood of 8 breakage announcements in 3 mins. Message-ID: <CACcTwYn1PegBWYY9wQ_h9Nh4vV7PXu949yiSB_PkO3BpV0ZrUA@mail.gmail.com> In-Reply-To: <CANwXMPMyi96hFx-joD-ReZGYWO_P5KcRZnBu2C2j9QfJ-g1t_A@mail.gmail.com> References: <201905151425.x4FEPNqk065975@fire.js.berklix.net> <e8125e97-6308-5ad0-b850-6825069683d4@bluerosetech.com> <CACcTwYkr55Vxx-jk7uyhppT0LBxfKYDEzTxmhJLL-Se7EJVAew@mail.gmail.com> <CANwXMPMyi96hFx-joD-ReZGYWO_P5KcRZnBu2C2j9QfJ-g1t_A@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
> 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 nicely automatically as scheduled on > *only* security errata, while leaving all other types of updates alone for admin intervention. My comment about Linux was not in regards to any particular distro, they all have interesting policies of varying effectiveness when it comes to release engineering, but specifically about the Linux kernel team (Torvalds Et al,) which last I checked had a policy of specifically not handling security issues any different from any generic bug. Distros may do their own kernel release engineering and handling that themselves which is fine.help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CACcTwYn1PegBWYY9wQ_h9Nh4vV7PXu949yiSB_PkO3BpV0ZrUA>