[CentOS-devel] [EXT] Balancing the needs around the CentOS platform
Mark Mielke
mark.mielke at gmail.comSat Dec 19 20:31:03 UTC 2020
- Previous message: [CentOS-devel] [EXT] Balancing the needs around the CentOS platform
- Next message: [CentOS-devel] [EXT] Balancing the needs around the CentOS platform
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Sat, Dec 19, 2020 at 3:09 PM Gordon Messmer <gordon.messmer at gmail.com> wrote: > Stream is going to continue to get the same kernel that RHEL gets, it's > just going to get updates earlier. This is false. > In the past, users with binary 3rd party drivers would need to wait a > while after a point release before they could update their kernel. In > CentOS Stream, they'll have to wait a while after a kernel package > update before they can update their kernel. This is hugely problematic. > There's really very little changing, here. The point releases are going > away, so the date of kernel updates is less predictable, but the > solution hasn't changed at all: If you use a binary 3rd party kernel > module, you need a process in place to block kernel updates until your > 3rd party kernel modules are available. This is hugely problematic. But, I want to respond with details to a different post. -- Mark Mielke <mark.mielke at gmail.com>
- Previous message: [CentOS-devel] [EXT] Balancing the needs around the CentOS platform
- Next message: [CentOS-devel] [EXT] Balancing the needs around the CentOS platform
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list