Hi All,
As part of the F21 "Modular Kernel Packaging for Cloud" Feature[1], I've committed and pushed the kernel packaging split up into kernel-core and kernel-drivers subpackages. For those of you running rawhide, this really shouldn't be a major impact at all. When you do a yum update, you will see "kernel", "kernel-core", and "kernel-drivers" packages being installed. The end result should be in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall the kernel or kernel-drivers packages. The machine may boot with just kernel-core, but it will lack drivers for a significant portion of bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two snuck through. In the event that you do have an issue with this, please file a bug against the kernel package.
josh
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
Hi,
On 29/04/14 22:41, Josh Boyer wrote:
Hi All,
As part of the F21 "Modular Kernel Packaging for Cloud" Feature[1], I've committed and pushed the kernel packaging split up into kernel-core and kernel-drivers subpackages. For those of you running rawhide, this really shouldn't be a major impact at all. When you do a yum update, you will see "kernel", "kernel-core", and "kernel-drivers" packages being installed. The end result should be in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall the kernel or kernel-drivers packages. The machine may boot with just kernel-core, but it will lack drivers for a significant portion of bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two snuck through. In the event that you do have an issue with this, please file a bug against the kernel package.
josh
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
Just wondering how this will (or will not) affect kernel-module-extras ?
Currently there is a dependency (largely for backwards compatibility purposes) on kernel-module-extras from gfs2-utils and I'm wondering if that will need to be changed (or dropped) as a result of this,
Steve.
On Wed, Apr 30, 2014 at 5:41 AM, Steven Whitehouse swhiteho@redhat.com wrote:
Hi,
On 29/04/14 22:41, Josh Boyer wrote:
Hi All,
As part of the F21 "Modular Kernel Packaging for Cloud" Feature[1], I've committed and pushed the kernel packaging split up into kernel-core and kernel-drivers subpackages. For those of you running rawhide, this really shouldn't be a major impact at all. When you do a yum update, you will see "kernel", "kernel-core", and "kernel-drivers" packages being installed. The end result should be in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall the kernel or kernel-drivers packages. The machine may boot with just kernel-core, but it will lack drivers for a significant portion of bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two snuck through. In the event that you do have an issue with this, please file a bug against the kernel package.
josh
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
Just wondering how this will (or will not) affect kernel-module-extras ?
Great question. It won't affect it.
Currently there is a dependency (largely for backwards compatibility purposes) on kernel-module-extras from gfs2-utils and I'm wondering if that will need to be changed (or dropped) as a result of this,
Nothing at the moment. Later this week I'm going to look at enabling auto-provides for kernel modules in the various kernel packages. This will make situations like this much more flexible, as gfs2-utils will be able to Requires: gfs2.ko (or whatever it is) instead of the package name. That will allow us to move modules around without breaking packages, and potentially get ride of k-m-e down the road.
Once the auto-provides are enabled, I'll go through the tracker bug Bruno has open and fix up the userspace package requires.
josh
On Wed, Apr 30, 2014 at 07:56:29 -0400, Josh Boyer jwboyer@fedoraproject.org wrote:
Nothing at the moment. Later this week I'm going to look at enabling auto-provides for kernel modules in the various kernel packages. This will make situations like this much more flexible, as gfs2-utils will be able to Requires: gfs2.ko (or whatever it is) instead of the package name. That will allow us to move modules around without breaking packages, and potentially get ride of k-m-e down the road.
Once the auto-provides are enabled, I'll go through the tracker bug Bruno has open and fix up the userspace package requires.
Thanks for this update. I was going to nag about this soon, if someone else hadn't.
On Wed, Apr 30, 2014 at 07:56:29AM -0400, Josh Boyer wrote:
Nothing at the moment. Later this week I'm going to look at enabling auto-provides for kernel modules in the various kernel packages. This will make situations like this much more flexible, as gfs2-utils will be able to Requires: gfs2.ko (or whatever it is) instead of the package name. That will allow us to move modules around without breaking packages, and potentially get ride of k-m-e down the road.
That would be useful for libguestfs too. It has a pretty well defined list of kernel modules that it needs.
Once the auto-provides are enabled, I'll go through the tracker bug Bruno has open and fix up the userspace package requires.
Which is the tracker bug?
Rich.
On Thu, May 01, 2014 at 18:18:43 +0100, "Richard W.M. Jones" rjones@redhat.com wrote:
Which is the tracker bug?
https://bugzilla.redhat.com/show_bug.cgi?id=1058331
I added everything that depended on kernel_modules_extra. There might be other things that should be changed, that depend on modules that are currently in kernel-drivers in case the modules move from one to the other.
On Thu, May 01, 2014 at 02:24:14PM -0500, Bruno Wolff III wrote:
On Thu, May 01, 2014 at 18:18:43 +0100, "Richard W.M. Jones" rjones@redhat.com wrote:
Which is the tracker bug?
https://bugzilla.redhat.com/show_bug.cgi?id=1058331
I added everything that depended on kernel_modules_extra. There might be other things that should be changed, that depend on modules that are currently in kernel-drivers in case the modules move from one to the other.
Thanks. I think that particular bug isn't relevant to libguestfs.
Adding 'Requires: foo.ko, bar.ko' will be possible. Whether it will make libguestfs pull in a smaller kernel sub-dependency is unlikely.
Rich.
Am 29.04.2014 23:41, schrieb Josh Boyer:
As part of the F21 "Modular Kernel Packaging for Cloud" Feature[1], I've committed and pushed the kernel packaging split up into kernel-core and kernel-drivers subpackages. For those of you running rawhide, this really shouldn't be a major impact at all. When you do a yum update, you will see "kernel", "kernel-core", and "kernel-drivers" packages being installed. The end result should be in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall the kernel or kernel-drivers packages. The machine may boot with just kernel-core, but it will lack drivers for a significant portion of bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two snuck through. In the event that you do have an issue with this, please file a bug against the kernel package.
josh
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
thank you - looks pretty fine for VMware guests
[root@rawhide ~]# rpm -qa | grep kernel kernel-core-3.15.0-0.rc3.git1.10.fc21.x86_64
[root@rawhide ~]# lsmod Module Size Used by zram 19948 2 crct10dif_pclmul 14268 0 crc32_pclmul 13133 0 crc32c_intel 22094 0 vmw_balloon 13487 0 ghash_clmulni_intel 13230 0 vmxnet3 53723 0 vmw_pvscsi 27370 2
[root@rawhide ~]# df Filesystem Type Size Used Avail Use% Mounted on /dev/sdb1 ext4 12G 682M 11G 6% / /dev/sda1 ext4 487M 37M 447M 8% /boot
On 04/29/2014 05:41 PM, Josh Boyer wrote:
Hi All,
As part of the F21 "Modular Kernel Packaging for Cloud" Feature[1], I've committed and pushed the kernel packaging split up into kernel-core and kernel-drivers subpackages. For those of you running rawhide, this really shouldn't be a major impact at all. When you do a yum update, you will see "kernel", "kernel-core", and "kernel-drivers" packages being installed. The end result should be in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall the kernel or kernel-drivers packages. The machine may boot with just kernel-core, but it will lack drivers for a significant portion of bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two snuck through. In the event that you do have an issue with this, please file a bug against the kernel package.
josh
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
I think you need a little work on this. Ok, to update (install) a new kernel you execute: yum update kernel that same as it was previously.
BUT, if you want to remove that same kernel, for example doing: yum remove kernel-3.15.0-0.rc3.git5.3.fc21 will only remove the kernel package and not kernel-core and kernel-modules. Instead, you need to execute yum remove kernel-core-3.15.0-0.rc3.git5.3.fc21 to get kernel, kernel-core, and kernel-modules removed.
I believe that for regular (non cloud usage) we should just need to deal with the kernel package in both update and remove situations.
Gene
On Mon, May 5, 2014 at 8:26 AM, Gene Czarcinski gczarcinski@gmail.com wrote:
On 04/29/2014 05:41 PM, Josh Boyer wrote:
Hi All,
As part of the F21 "Modular Kernel Packaging for Cloud" Feature[1], I've committed and pushed the kernel packaging split up into kernel-core and kernel-drivers subpackages. For those of you running rawhide, this really shouldn't be a major impact at all. When you do a yum update, you will see "kernel", "kernel-core", and "kernel-drivers" packages being installed. The end result should be in line with today's rawhide kernels.
Note: Unless you're using a typical VM or Cloud image, don't uninstall the kernel or kernel-drivers packages. The machine may boot with just kernel-core, but it will lack drivers for a significant portion of bare-metal hardware without kernel-drivers installed.
Despite best efforts in testing, it's always possible a bug or two snuck through. In the event that you do have an issue with this, please file a bug against the kernel package.
josh
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
I think you need a little work on this. Ok, to update (install) a new kernel you execute: yum update kernel that same as it was previously.
BUT, if you want to remove that same kernel, for example doing: yum remove kernel-3.15.0-0.rc3.git5.3.fc21 will only remove the kernel package and not kernel-core and kernel-modules. Instead, you need to execute yum remove kernel-core-3.15.0-0.rc3.git5.3.fc21 to get kernel, kernel-core, and kernel-modules removed.
From a kernel.spec standpoint, the only way I'm aware of making 'yum
remove kernel' remove the kernel, kernel-core, and kernel-modules packages is to make kernel-core Requires: kernel. If it did that, then you couldn't just install kernel-core, which would defeat the entire point of the Feature the Cloud people wanted.
I believe that for regular (non cloud usage) we should just need to deal with the kernel package in both update and remove situations.
I would love to see patches that accomplish this.
josh
On Mon, May 05, 2014 at 08:26:59 -0400, Gene Czarcinski gczarcinski@gmail.com wrote:
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
I think you need a little work on this. Ok, to update (install) a new kernel you execute: yum update kernel that same as it was previously.
BUT, if you want to remove that same kernel, for example doing: yum remove kernel-3.15.0-0.rc3.git5.3.fc21 will only remove the kernel package and not kernel-core and kernel-modules. Instead, you need to execute yum remove kernel-core-3.15.0-0.rc3.git5.3.fc21 to get kernel, kernel-core, and kernel-modules removed.
I believe that for regular (non cloud usage) we should just need to deal with the kernel package in both update and remove situations.
I don't think that can be made to work with dependencies. To work kernel-core would need to depend on kernel, so that installing kernel-core would require kernel which requires kernel-modules, which is a problem.
In most cases old kernels get removed by updates, so most people aren't going to try to be removing specific old kernels by hand. For those that do, using kernel-core instead of kernel isn't a big deal. The main thing is that the change should be documented in the release notes (and perhaps other places) to avoid confusion.
Am 05.05.2014 14:36, schrieb Bruno Wolff III:
On Mon, May 05, 2014 at 08:26:59 -0400, Gene Czarcinski gczarcinski@gmail.com wrote:
[1]https://fedoraproject.org/wiki/Changes/Modular_Kernel_Packaging_for_Cloud
I think you need a little work on this. Ok, to update (install) a new kernel you execute: yum update kernel that same as it was previously.
BUT, if you want to remove that same kernel, for example doing: yum remove kernel-3.15.0-0.rc3.git5.3.fc21 will only remove the kernel package and not kernel-core and kernel-modules. Instead, you need to execute yum remove kernel-core-3.15.0-0.rc3.git5.3.fc21 to get kernel, kernel-core, and kernel-modules removed.
I believe that for regular (non cloud usage) we should just need to deal with the kernel package in both update and remove situations.
I don't think that can be made to work with dependencies. To work kernel-core would need to depend on kernel, so that installing kernel-core would require kernel which requires kernel-modules, which is a problem.
In most cases old kernels get removed by updates, so most people aren't going to try to be removing specific old kernels by hand. For those that do, using kernel-core instead of kernel isn't a big deal. The main thing is that the change should be documented in the release notes (and perhaps other places) to avoid confusion.
in fact on a VM with only "kernel-core" installed "yum remove kernel" wroks the same way as all the years before
devel@lists.stg.fedoraproject.org
-
Bruno Wolff III -
Gene Czarcinski -
Josh Boyer -
Reindl Harald -
Richard W.M. Jones -
Steven Whitehouse