From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] kernel packaging split up landing in Rawhide
Date: Wed, 30 Apr 2014 10:41:07 +0100 [thread overview]
Message-ID: <5360C533.50500@redhat.com> (raw)
In-Reply-To: <CA+5PVA5aXe2T7c-fKkQtziQ5j=dog8LqcmJ3Md0y=ju1iyn-MA@mail.gmail.com>
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.
next parent reply other threads:[~2014-04-30 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+5PVA5aXe2T7c-fKkQtziQ5j=dog8LqcmJ3Md0y=ju1iyn-MA@mail.gmail.com>
2014-04-30 9:41 ` Steven Whitehouse [this message]
2014-04-30 11:56 ` [Cluster-devel] kernel packaging split up landing in Rawhide Josh Boyer
2014-04-30 12:53 ` Bruno Wolff III
2014-05-01 17:18 ` Richard W.M. Jones
2014-05-01 19:24 ` Bruno Wolff III
2014-05-01 19:37 ` Richard W.M. Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5360C533.50500@redhat.com \
--to=swhiteho@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.