Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 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 update to ACPI be > > reversed and why is it only affecting some systems. And why do you have > > to downgrade to 11.3? What are you running now? > > 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 USB on some systems. I'm running 12.1 now, but USB is > problematical (produces an error message once a second, and my UPS control > doesn't seem to work). > > Mike > There may have been two changes working together to create the problem. At some time last year, changes were made to the usb drivers to be sensitive to acpi data of some sort (maybe something about hubs, I forget the details). That alone may have been fine on most systems, but then a later update of acpi code started causing problems which in the past might not have affected usb but now does. It's just a vague theory, based on my memory of some change happening last year that injected awareness of acpi data into the usb driver subsystem. I wonder if it would be possible to add some sort of tunable to disable that awareness, if nothing else just to see if it's the cause of any usb trouble. -- Ian ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 USB on some systems. I'm running >12.1 now, but USB is problematical (produces an error message once a >second, and my UPS control doesn't seem to work). > > Mike That is sort of what my problem is also. The error message keeps displaying on the screen making using the PC impossible. I don't feel anyone is going to fix this until enough users are affected. I am on 11.3, and if this isn't fixed before 13.x is released, I may have to try another OS. -- Gerard ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
>From mike Sun Feb 23 17:24:54 2020 Received: from mx2.freebsd.org (mx2.freebsd.org [96.47.72.81]) by mail.karels.net (8.15.2/8.15.2) with ESMTP id 01NNOsPX085694 for ; Sun, 23 Feb 2020 17:24:54 -0600 (CST) (envelope-from owner-freebsd-sta...@freebsd.org) Received: from mx1.freebsd.org (mx1.freebsd.org [96.47.72.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx2.freebsd.org (Postfix) with ESMTPS id 5FA13A3513; Sun, 23 Feb 2020 23:24:47 + (UTC) (envelope-from owner-freebsd-sta...@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 48Qh9p6Fbfz3xJl; Sun, 23 Feb 2020 23:24:46 + (UTC) (envelope-from owner-freebsd-sta...@freebsd.org) Delivered-To: freebsd-sta...@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id 04F9D24C2C6 for ; Sun, 23 Feb 2020 23:24:37 + (UTC) (envelope-from gerard_seib...@outlook.com) Received: from NAM11-BN8-obe.outbound.protection.outlook.com (mail-bn8nam11olkn20826.outbound.protection.outlook.com [IPv6:2a01:111:f400:7eae::826]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "GlobalSign Organization Validation CA - SHA256 - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 48Qh9b53WSz3x2F for ; Sun, 23 Feb 2020 23:24:35 + (UTC) (envelope-from gerard_seib...@outlook.com) ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AMSFKlt/8ZUrdDwnz7WJTsy3aub9O15VIrk8qt5/0OfYdbRYyXE4rZDbA/WO/0OoCFmEJn75PwAXAwCvPkSwaawkDmi/jLpd5MKG32dr7LTgaG8P4EEVZ+pFtdATHNzhckVTZ4tO4tSno12H0OV7itBWSbnqnAALmpf01EtcRUlWTTf6hDc4xs7XO1I+TeAWhGc1sW88xU+fqDMmbgGNEQ0SJQITqToR4ZqjCIm+6QHWD0etJJ1lSioGVTZTf4fO5BshNFmkHf3leEMaJcizZ34t9lCCKBEyVgr5gkDcQaUaCshU8BYpoykcWFwctvECbl44zkr7R03ohMrKVlFf+g== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/7H6H/ZeX8qZEA81GMBBWYOhtwvj/ntJ0EXjrTaX6qQ=; b=DFLr3LN8F408Sy/vyheq7/PzDY9j/wioOsj7TY0PKuD4dMw5phgAHOrGKM44mOnIANG+w/oS7Za+Fvq4C3M9VZQm+4TrqmzM3AhU2VjGui1X4vrjSUwUiowQpjGrM/bcHRA4GcjA6V/M0eWsrBPIS6m3jGB+RqRxaa8Dqt8Px8JqEKCSx5b+jdQJ3ESAuh4hqaITQzBjtgUkdcc+35O/ZkoI8To1zVz1JfQWfn89d9/vxgyx5oMibDZfgc1WdH1rh2lsDP1XtWxGHbYzD+Ul5pMmP1Wc69IL/GyKuGETTFx9gC8ewnMFFCYzv8hiHVShfoofjeeup9uT248dHw13/w== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=outlook.com; dmarc=pass action=none header.from=outlook.com; dkim=pass header.d=outlook.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outlook.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/7H6H/ZeX8qZEA81GMBBWYOhtwvj/ntJ0EXjrTaX6qQ=; b=UcIIyK5eccsbX02EEX6R0EB3RbFo8YNcbVKVJhvyMDsGDbUdT2yEGjkmOtpbKeAFxVmt7kGImQ6Mpco2N6iLBbHYNWln2IGmlugVD56YbrITJlYOhYVYXuO8414U/hIoxGLiRorPUP5s72ePDNiClu5bKqtsIzano9VET99SqURxEqNpAw0oBEqy2wrtimKCeE9gwU+4tZqUCLGFbLQX7s8mJDOTj/Qb+nRiKUHU0iIZP3wAbf1QRe3yQ4y4MzaI9vXZWWcje9gvuYLWJGOsCZ9Tzb+6KPz4yrqwt8onVMnZoHiM8iQtaZZuWc7BiyBKX9jlOZWiE3GTGeri0n2B7w== Received: from BN8NAM11FT033.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4b::38) by BN8NAM11HT094.eop-nam11.prod.protection.outlook.com (2a01:111:e400:fc4b::213) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.18; Sun, 23 Feb 2020 23:24:33 + Received: from DM6PR02MB5228.namprd02.prod.outlook.com (2a01:111:e400:fc4b::33) by BN8NAM11FT033.mail.protection.outlook.com (2a01:111:e400:fc4b::405) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2750.18 via Frontend Transport; Sun, 23 Feb 2020 23:24:33 + X-IncomingTopHeaderMarker: OriginalChecksum:D077F37525F73E587232E7A629EB5D19F19242FB96D55719C434C6BC92671516; UpperCasedChecksum:8185AD0F282A817DA1157C3BF812408BF6624E211390DE39D887910AD6549E19; SizeAsReceived:10132; Count:53 Received: from DM6PR02MB5228.namprd02.prod.outlook.com ([fe80::518f:ba28:13dd:1f3e]) by DM6PR02MB5228.namprd02.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-Reply-To: <202002232227.01nmrfmn085...@mail.karels.net> References: <202002232227.01nmrfmn085...@mail.karels.net> Organization: seibercom.net X-Mailer:
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 update to ACPI be reversed and why is it only affecting some systems. And why do you have to downgrade to 11.3? What are you running now? -- Gerard ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 will do nothing to help resolve > the issue. I can suggest two ways folks can help get this resolved: > build and test kernels (with guidance from interested developers) to > bisect and identify the offending commit/test potential patches, or > make a system available to willing developer(s). 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. Mike ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 the issue. I can suggest two ways folks can help get this resolved: build and test kernels (with guidance from interested developers) to bisect and identify the offending commit/test potential patches, or make a system available to willing developer(s). ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 they squash that bug, they should not be in a rush to push out the door another defective model. Just my 2₵. -- Jerry ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 > > when I start working on it. With DRM and Framebuffer X11 drivers so it > > My experience is that you have to enable "Use Host I/O Cache" for the > SATA storage controller, otherwise it will lock up sooner or later. It > seems to not be the default. With it enabled, I don't have any issues. Nooo way.. that seems to help! Works slow but it works :-) I have M2 2TB SSD using encrypted ZFS on my FreeBSD laptop.. so clearly a VirtualBox drivers / config issue not the OS..? Thank you Bengt for the hint! Trust in FreeBSD restored :-) :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 drivers so it My experience is that you have to enable "Use Host I/O Cache" for the SATA storage controller, otherwise it will lock up sooner or later. It seems to not be the default. With it enabled, I don't have any issues. [...] Bengt ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 > showstopper I find. `pkg lock` after installing from ports is your friend ;-) Kind regards, Patrick -- punkt.de GmbH Patrick M. Hausen .infrastructure Kaiserallee 13a 76133 Karlsruhe Tel. +49 721 9109500 https://infrastructure.punkt.de i...@punkt.de AG Mannheim 108285 Geschäftsführer: Jürgen Egeling, Daniel Lienert, Fabian Stein ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 the end-user, maybe tester, I did no commits, so in theory I cannot complain, but it seems like more experienced kernel people could take part in this kind of solution architecture and design right from start in order to prevent avalanche of future problems and problematic solutions that will generate more problems. 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 drivers so it does not seem related. 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 showstopper I find. VirtualBox done this way is perfectly stable for me, as is DRM these days. cheers, -pete. PS; If you are running VirtualBox on top of ZFS then make sure you have the approrpiate AIO tunings in sysctl.conf though. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 I'm aware OpenBSD issues a release every six months and > supports the most recent two releases, so it seems odd to me to > complain about FreeBSD's ~1 year minor release support lifetime and 5 > year stable branch support lifetime in that context. Its more like "lets try if what I need works better over there". Not really the release timeline. The release timeline problem is more related with pushing untested features (and possible avalanche of solutions that introduce yet another complications that we observe right now). "The BSD Way", for me, was always about "it works solid or its not there". Like macOS / iOS. Unlike "The Linux Way" where things changes upside down from release to release and each one of them has its own universe of variants. Like Android. I am not sure if it is that important if there is a release in 6 month or 2 years. Not a problem at all. If in two years I get a 5 new features that work rock solid then it seems a better choice than getting new features every six months and have more problems on a production because of that. If I need to experiment there is a CURRENT branch. For well tested features I have STABLE. For rock solid "I bet my money on that" I have a RELEASE. Right? I did miss the 12.0 EoL kind of fix for DRM, sorry, it seems reasonable. I am just worried that 12.2-RELEASE will have the same problems, if not more new problems. Maybe I should go back to 11 and see how things work over there :-P Tomek -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 > supported. The problem will automatically resolve once 12.0 is no > longer supported. > > (Yes, I wish we were able to address this issue in a way other than > waiting for 12.0's EOL, but nobody in the FreeBSD development > community was able to find the time to do so.) Ah, in this case 12.0 EoL is highly desired. Now I understand. Thank you :-) 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 the end-user, maybe tester, I did no commits, so in theory I cannot complain, but it seems like more experienced kernel people could take part in this kind of solution architecture and design right from start in order to prevent avalanche of future problems and problematic solutions that will generate more problems. 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 drivers so it does not seem related. It can consume all resources and/or break graphics (i.e. Enlightenment WM). I have tried various permutations of configuration and operating systems (mostly Windoze, but also Linux). I am not sure if I am the only person having this problem as I have asked some questions before. I know there is BHYVE but its not really that easy to use as VBox (to be honest I did not manage to run anything beyond examples). Simple and efficient hypervisor is a must have nowadays in productivity work. For a modern workstation a fairly good GPU driver and Virtualization seems mandatory. Not to mention input devices like Trackpad. I cannot use them reliably at this time anymore. It worked well in the past. Thus my question - why create a new release with new features when there are still basic features missing or incomplete.. I would really care for productivity in the first place even if its 9.12 release :-) I really love FreeBSD!! I advocate it in my every project and every project I am part of. I use it as a base on my servers. It worked really nice on my desktop, but it does not anymore. I am not really comfortable to switch to macOS BSD but time is precious and clients are waiting for the results.. I just wonder: 1. Maybe if Sony uses FreeBSD on their PlayStation with AMD GPU - could they share back the solution? 2. Maybe Intel could help in development of the DRM architecture? They have really nice R in Poland.. Did anyone try that? :-) -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 the most recent two releases, so it seems odd to me to complain about FreeBSD's ~1 year minor release support lifetime and 5 year stable branch support lifetime in that context. ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 supported for 5 years. 12.0 was released at the end of 2018. I've heard many complaints that minor releases from stable branches are not frequent enough. > 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 supported. The problem will automatically resolve once 12.0 is no longer supported. (Yes, I wish we were able to address this issue in a way other than waiting for 12.0's EOL, but nobody in the FreeBSD development community was able to find the time to do so.) ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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, this should come as no surprise to anyone. > > -- > Steve O'Hara-Smith > True.. but the surprise is the Linux like bleeding edge in BSD and the quality degradation at a degree that I have just replaced my FreeBSD laptop with a MacBook :-( Maybe its a time to give OpenBSD a try.. -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD 12.0 end-of-life
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 dramatic Virtualization with VirtualBox brings back my MacBook to the desk because FreeBSD does not seem to be reliable desktop environment anymore even on a decent modern machine :-( Is it really necessary? What happened to FreeBSD? :-( Tomek On Tue, Feb 18, 2020 at 12:14 AM FreeBSD Security Officer wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA512 > > Dear FreeBSD community, > > As of February 29, 2020, FreeBSD 12.0 will reach end-of-life and will no > longer > be supported by the FreeBSD Security Team. Users of FreeBSD 12.0 are strongly > encouraged to upgrade to a newer release as soon as possible. > > The currently supported branches and releases and their expected end-of-life > dates are: > > +--+ > | Branch| Release| Release Date | Estimated EoL | > +-+--+---+-+ > | stable/12 | N/A | N/A | June 30, 2024 | > +-+--+---+-+ > | releng/12.1 | 12.1-RELEASE | November 4, 2019 | 12.2-RELEASE + 3 months | > +-+--+---+-+ > | stable/11 | N/A | N/A | September 30, 2021 | > +-+--+---+-+ > | releng/11.3 | 11.3-RELEASE | July 9, 2019 | 11.4-RELEASE + 3 months | > +--+ > > Please refer to https://security.freebsd.org/ for an up-to-date list of > supported releases and the latest security advisories. > > - -- > The FreeBSD Security Team > -BEGIN PGP SIGNATURE- > > iQKTBAEBCgB9FiEE/A6HiuWv54gCjWNV05eS9J6n5cIFAl5LHZNfFIAALgAo > aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldEZD > MEU4NzhBRTVBRkU3ODgwMjhENjM1NUQzOTc5MkY0OUVBN0U1QzIACgkQ05eS9J6n > 5cIqyA//ROIFtIsEDV5p02FnWClgWu3qxZ4uRyA0usM1DtZPBYjtfsFGdAU+9NvY > EsUB3rVjWx2HNoHKySFgjLbtGdCNoae45pjLe3UiKgrbQZwXCdUl0d1y+4ZcoR0D > cdtEY6YWio4kBHTWxd0cgCpe+Cmk3nQRB005qgvMkkCBNBGuZQcQS62CMMis3IWC > paMcRBmzkh9HMW8e9XN2mFjGJbT2HKzY+y/Qvj3NhxenYgTzQbVwRDz4JPKz7Al+ > aVq2gLEuEgRWNFG+fBnk7qikzmV7JaXI+j/ImZnrMFBDC/ymiQMbQdt0Kxv0TsZF > ajR18pQyoAONXoJs875HD54/Rj0rQNkKwyZNKuka5+NWR/6d9H52+iytkGqn2DLR > Jp9slPHBW5ofC7WlgAAeV+S1Et7fWeV96hqDVRUXZstir6hM3hYEdwnQP8aFaYO9 > No+uLd6IAKBtBCK9hxOv6O6lmWjNk4LWQb6keG+zwFDCfnILdfwVE+eML7GqLzQ1 > 5s40M7gZsB//1S27WQOhKS4Vea+68meGOzGv0KkMd4gNuV/cBqVoCj52Muu3O0gK > nbMuFHptQbL0qhFGzho4chg4TsuXs0lf28BsHYYFeEewEce7gIwCgPLQPIwLQG4h > cv7KkgwEetngUUlyMaeKu2xCUXTaDJ3KpFkwEcol1oezaWkduwg= > =viBR > -END PGP SIGNATURE- > ___ > freebsd-annou...@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-announce > To unsubscribe, send any mail to "freebsd-announce-unsubscr...@freebsd.org" -- CeDeROM, SQ7MHZ, http://www.tomek.cedro.info ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
