Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-25 Thread Ian Lepore
On Mon, 2020-02-24 at 19:01 -0600, Mike Karels wrote: > > From mike Sun Feb 23 17:24:54 2020 > > > Gerard E. Seibert wrote: > > On Sun, 23 Feb 2020 16:27:40 -0600, Mike Karels stated: > > > In this case (a USB failure), I bisected the problem some

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-25 Thread Gerard E. Seibert
On Mon, 24 Feb 2020 19:01:49 -0600, Mike Karels stated: >The update to ACPI was pulled from upstream, and IIRC it included >multiple changes. There have been many updates to ACPI since. I >don't have any idea which part of the change caused the problem, or >what it does; no idea how it affects

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-24 Thread Mike Karels
02.prod.outlook.com ([fe80::518f:ba28:13dd:1f3e%7]) with mapi id 15.20.2750.021; Sun, 23 Feb 2020 23:24:33 + Date: Sun, 23 Feb 2020 18:24:29 -0500 From: "Gerard E. Seibert" To: freebsd-stable@freebsd.org Subject: Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life Message-ID: In-R

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-23 Thread Gerard E. Seibert
On Sun, 23 Feb 2020 16:27:40 -0600, Mike Karels stated: >In this case (a USB failure), I bisected the problem some months ago. >The offending commit was an ACPI update. I have not yet "downgraded" >to 11.3, but I will when I have enough time. Obviously, I am not an expert here, but why can't the

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-23 Thread Mike Karels
Ed Maste wrote: > On Sun, 23 Feb 2020 at 12:48, Gerard E. Seibert > wrote: > > > > Until they squash that bug, they should not be in a rush to push out > > the door another defective model. > Unfortunately complaining that there's a bug in 12.0 or 12.1 or > providing additional reports of this

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-23 Thread Ed Maste
On Sun, 23 Feb 2020 at 12:48, Gerard E. Seibert wrote: > > Until they squash that bug, they should not be in a rush to push out > the door another defective model. Unfortunately complaining that there's a bug in 12.0 or 12.1 or providing additional reports of this will do nothing to help resolve

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-23 Thread Gerard E. Seibert
On Tue, 18 Feb 2020 04:23:35 +0100, Tomasz CEDRO stated: >12.0 was a problematic release. 12.1 brings even more problems. I agree. 12.0 & 12.1 are both flawed. Neither one will install and run correctly on certain newer systems. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=237666 Until

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-20 Thread Tomasz CEDRO
On Wed, Feb 19, 2020 at 8:24 PM Bengt Ahlgren wrote: > Tomasz CEDRO writes: > > Another problem is the VirtualBox virtualization that is not really > > usable anymore. I am aware of closed-source VBox Guest Additions > > problem. My VM works fine for a first minute or two but then it stops > >

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-19 Thread Bengt Ahlgren
Tomasz CEDRO writes: [...] > Another problem is the VirtualBox virtualization that is not really > usable anymore. I am aware of closed-source VBox Guest Additions > problem. My VM works fine for a first minute or two but then it stops > when I start working on it. With DRM and Framebuffer X11

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Patrick M. Hausen
Hi all, > Am 18.02.2020 um 18:44 schrieb Pete French : > Both the DRM issue and VirtualBox are fixed by making sure you recompile and > install the kernel modules from the source in /usr/ports when you upgrade the > OS, or if 'pkg upgrade' overwrites them. Its a bit annnoying, but hardly a >

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Pete French
On 18/Feb/2020 17:19, Tomasz CEDRO wrot> But also as this DRM user (for Intel and AMD) I have experienced the related hiccups, problems, and problems solutions. It does not look like a FreeBSD way, but more like Linux way. I never noticed anything like this before. Sure, I can see this only as

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Tomasz CEDRO
On Tue, Feb 18, 2020 at 3:51 PM Ed Maste wrote: > > On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO wrote: > > > > Maybe its a time to give OpenBSD a try.. > > I really don't understand this comment, either. Certainly give OpenBSD > a try and if it fits your needs better that's great. > > As far as

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Tomasz CEDRO
Hello Ed, thanks for your input :-) On Tue, Feb 18, 2020 at 3:46 PM Ed Maste wrote: > > 12.0 was a problematic release. 12.1 brings even more problems. > > The major issue with 12.1 is a problem with the Intel graphics kernel > module, and fixing that was held up by both 12.0 and 12.1 being >

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Ed Maste
On Tue, 18 Feb 2020 at 05:37, Tomasz CEDRO wrote: > > Maybe its a time to give OpenBSD a try.. I really don't understand this comment, either. Certainly give OpenBSD a try and if it fits your needs better that's great. As far as I'm aware OpenBSD issues a release every six months and supports

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Ed Maste
On Mon, 17 Feb 2020 at 22:24, Tomasz CEDRO wrote: > > Why so short End-Of-Life? Why so many fast and short releases? What for? > > Why pushing problems to production? What was wrong with having one > well tested stable system for a long time? I really don't understand this - FreeBSD 12 is

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-18 Thread Tomasz CEDRO
wt., 18 lut 2020, 10:20 użytkownik Steve O'Hara-Smith napisał: > On Tue, 18 Feb 2020 04:23:35 +0100 > Tomasz CEDRO wrote: > > > Why so short End-Of-Life? Why so many fast and short releases? What for? > > The new(ish) release and support policy has been announced and well > documented,

Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life

2020-02-17 Thread Tomasz CEDRO
Why so short End-Of-Life? Why so many fast and short releases? What for? Why pushing problems to production? What was wrong with having one well tested stable system for a long time? 12.0 was a problematic release. 12.1 brings even more problems. To be honest X11 Video Acceleration DRM mess and