3:07 a.m.
I appreciate that Rawhide always has the latest kernel snapshot as the
one and only kernel and that it is up to users to manage their own
kernels. However I wonder if there should be a simple, standard way of
being able to install the last released kernel, perhaps a package last-
release-kernel or something.
The problem for me is that the release kernel only ever seems to be in
Rawhide for one day, and if I miss updating on that day, I have missed
capturing that kernel – it just happened with 4.10 so I am stuck with
an rc8 rather than the release. (And 4.11 won't actually work for a few
rcs yet, same for every new kernel.)
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
5:07 a.m.
On Wed, Mar 1, 2017 at 9:07 AM, Russel Winder <russel(a)winder.org.uk> wrote:
I appreciate that Rawhide always has the latest kernel snapshot as
the
one and only kernel and that it is up to users to manage their own
kernels. However I wonder if there should be a simple, standard way of
being able to install the last released kernel, perhaps a package last-
release-kernel or something.
The problem for me is that the release kernel only ever seems to be in
Rawhide for one day, and if I miss updating on that day, I have missed
capturing that kernel – it just happened with 4.10 so I am stuck with
an rc8 rather than the release. (And 4.11 won't actually work for a few
rcs yet, same for every new kernel.)
You can always just pull it from koji either via the website or cli.
For cli you can use "koji download-build --arch=x86_64 kernel-4.10.0-1.fc26"
For web grab what ever version you want from
https://koji.fedoraproject.org/koji/packageinfo?packageID=8
6:10 a.m.
On Wed, 2017-03-01 at 11:07 +0000, Peter Robinson wrote:
[…]
> You can always just pull it from koji either via the website or cli.
> For cli you can use "koji download-build
--arch=x86_64 kernel-4.10.0-
> 1.fc26"
> For web grab what ever version you want from
> https://koji.fedoraproject.org/koji/packageinfo?packageID=8
> _______________________________________________
OK, so downloading from Koji into a private local repo is the standard
model. I guess, given this is Rawhide, this is a good solution. The CLI
saves remembering a URL ;-) I have now downloaded and refreshed my
local repo so it looks all good to go.
Thanks.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
6:17 a.m.
On 01.03.2017 10:07, Russel Winder wrote:
I appreciate that Rawhide always has the latest kernel snapshot as
the
one and only kernel and that it is up to users to manage their own
kernels. However I wonder if there should be a simple, standard way of
being able to install the last released kernel, perhaps a package last-
release-kernel or something.
The problem for me is that the release kernel only ever seems to be in
Rawhide for one day, and if I miss updating on that day, I have missed
capturing that kernel – it just happened with 4.10 so I am stuck with
an rc8 rather than the release. (And 4.11 won't actually work for a few
rcs yet, same for every new kernel.)
Don't know if this helps, but I have
exclude=kernel*
in dnf.conf and use a script like
ver=$(( $(cat /etc/redhat-release | awk '{print $3}') - 1 ))
dnf -y --disablerepo=* --releasever=$ver --enablerepo=updates*
--disableexcludes=all --nogpgcheck update kernel*
dnf -y --enablerepo=* --releasever=$ver clean all
grub2-mkconfig -o /boot/grub2/grub.cfg
which I run periodically to update to the latest kernel from the current
stable release.
Sandro
6:23 a.m.
On Wed, 2017-03-01 at 12:10 +0000, Russel Winder wrote:
On Wed, 2017-03-01 at 11:07 +0000, Peter Robinson wrote:
>
[…]
> You can always just pull it from koji either via the website or
> cli.
>
> For cli you can use "koji download-build --arch=x86_64 kernel-
> 4.10.0-
> 1.fc26"
>
These packages appear not to be signed. Is that as it is supposed to
be?
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
6:30 a.m.
On Wed, 2017-03-01 at 13:17 +0100, Sandro Mani wrote:
[…]
> Don't know if this helps, but I have
> exclude=kernel*
> in dnf.conf and use a script like
> ver=$(( $(cat /etc/redhat-release | awk '{print
$3}') - 1 ))
> dnf -y --disablerepo=* --releasever=$ver --enablerepo=updates*
> --disableexcludes=all --nogpgcheck update kernel*
> dnf -y --enablerepo=* --releasever=$ver clean all
> grub2-mkconfig -o /boot/grub2/grub.cfg
> which I run periodically to update to the latest kernel
from the
> current
> stable release.
So get the latest kernel from the latest release fork?
I wonder if there is a way of doing this without dnf in this way to
avoid needing the clean all?
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
7:24 a.m.
On Wed, Mar 1, 2017 at 12:23 PM, Russel Winder <russel(a)winder.org.uk> wrote:
On Wed, 2017-03-01 at 12:10 +0000, Russel Winder wrote:
> On Wed, 2017-03-01 at 11:07 +0000, Peter Robinson wrote:
> >
>
> […]
> > You can always just pull it from koji either via the website or
> > cli.
> >
> > For cli you can use "koji download-build --arch=x86_64 kernel-
> > 4.10.0-
> > 1.fc26"
> >
These packages appear not to be signed. Is that as it is supposed to
be?
It depends, sometimes they might still be in the signing queue,
sometimes they might have been replaced before they were signed but I
suspect you're using a f26 kernel on a different release which means
it'll be signed with a different key.
7:29 a.m.
On 01.03.2017 13:30, Russel Winder wrote:
On Wed, 2017-03-01 at 13:17 +0100, Sandro Mani wrote:
[…]
> Don't know if this helps, but I have
>
> exclude=kernel*
>
> in dnf.conf and use a script like
>
> ver=$(( $(cat /etc/redhat-release | awk '{print $3}') - 1 ))
> dnf -y --disablerepo=* --releasever=$ver --enablerepo=updates*
> --disableexcludes=all --nogpgcheck update kernel*
> dnf -y --enablerepo=* --releasever=$ver clean all
> grub2-mkconfig -o /boot/grub2/grub.cfg
>
> which I run periodically to update to the latest kernel from the
> current
> stable release.
So get the latest kernel from the latest release fork?
I wonder if there is a way of doing this without dnf in this way to
avoid needing the clean all?
This should work:
koji download-build --quiet --arch=$(uname -m) $(koji latest-build
--quiet f25 kernel | awk '{print $1}')
but it downloads all the rpms of the kernel package so in the end it
might be slower than the dnf update.
7:53 a.m.
On Wed, 2017-03-01 at 13:24 +0000, Peter Robinson wrote:
[…]
It depends, sometimes they might still be in the signing queue,
sometimes they might have been replaced before they were signed but I
suspect you're using a f26 kernel on a different release which means
it'll be signed with a different key.
I am running Rawhide and used the koji command you suggested to
download stuff. I guess this always going to lead to a signing issue?
Not really a problem, just wanting to know really.
--
Russel.
=============================================================================
Dr Russel Winder t: +44 20 7585 2200 voip: sip:russel.winder@ekiga.net
41 Buckmaster Road m: +44 7770 465 077 xmpp: russel(a)winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype: russel_winder
11:16 a.m.
On Wed, 1 Mar 2017 13:24:29 +0000
Peter Robinson <pbrobinson(a)gmail.com> wrote:
On Wed, Mar 1, 2017 at 12:23 PM, Russel Winder
<russel(a)winder.org.uk>
wrote:
> On Wed, 2017-03-01 at 12:10 +0000, Russel Winder wrote:
>> On Wed, 2017-03-01 at 11:07 +0000, Peter Robinson wrote:
>> >
>>
>> […]
>> > You can always just pull it from koji either via the website or
>> > cli.
>> >
>> > For cli you can use "koji download-build --arch=x86_64 kernel-
>> > 4.10.0-
>> > 1.fc26"
>> >
>
> These packages appear not to be signed. Is that as it is supposed to
> be?
It depends, sometimes they might still be in the signing queue,
sometimes they might have been replaced before they were signed but I
suspect you're using a f26 kernel on a different release which means
it'll be signed with a different key.
Note that if a package is signed and there's a written out rpm with
that signature you can download the signed copy with:
koji download-build --key=<keyid> --arch=x86_64 kernel-whatever
where keyid is the id of the key you want.
Things are signed and written out, but later garbage collected when
they are not tagged in any tag thats released.
kevin
11:58 a.m.
On Wed, 2017-03-01 at 14:29 +0100, Sandro Mani wrote:
[…]
This should work:
koji download-build --quiet --arch=$(uname -m) $(koji latest-build
--quiet f25 kernel | awk '{print $1}')
but it downloads all the rpms of the kernel package so in the end it
might be slower than the dnf update.
I shall have a play with the ideas, thanks for posting them.
Time is less of a problem for me, running a release kernel under Rawhide,
rather than the latest kernel, is the crucial element.
--
Russel.
=============================================================================
Dr Russel Winder t:+44 20 7585 2200 voip:sip:
russel.winder(a)ekiga.net
41 Buckmaster Road m:+44 7770 465 077 xmpp:russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder
12:04 p.m.
On Wed, 2017-03-01 at 17:58 +0000, Russel Winder wrote:
On Wed, 2017-03-01 at 14:29 +0100, Sandro Mani wrote:
> […]
>
> This should work:
>
> koji download-build --quiet --arch=$(uname -m) $(koji latest-build
> --quiet f25 kernel | awk '{print $1}')
I guess the import point here is that you have to track the previous release
kernels, so for Rawhide as F26 follow the 4.9 kernels built for F25, For the
4.10 kernels updates will only happen when Rawhide moves to F27 and F26
tracks the releases. Will using a kernel built for a previous release always
work?
--
Russel.
=============================================================================
Dr Russel Winder t:+44 20 7585 2200 voip:sip:
russel.winder(a)ekiga.net
41 Buckmaster Road m:+44 7770 465 077 xmpp:russel@winder.org.uk
London SW11 1EN, UK w: www.russel.org.uk skype:russel_winder
1:18 p.m.
On Wed, Mar 1, 2017 at 2:07 AM, Russel Winder <russel(a)winder.org.uk> wrote:
I appreciate that Rawhide always has the latest kernel snapshot as
the
one and only kernel and that it is up to users to manage their own
kernels. However I wonder if there should be a simple, standard way of
being able to install the last released kernel, perhaps a package last-
release-kernel or something.
The problem for me is that the release kernel only ever seems to be in
Rawhide for one day, and if I miss updating on that day, I have missed
capturing that kernel – it just happened with 4.10 so I am stuck with
an rc8 rather than the release. (And 4.11 won't actually work for a few
rcs yet, same for every new kernel.)
In dnf.conf add an exclude for the kernel, and then just manually
install them from koji. So you download kernel kernel-core and
kernel-modules RPMs from koji, then you can do 'dnf install *rpm'
while in the same directory that has the RPMs and it'll install them.
What you want to do isn't really possible right now I think. Fedora 24
and 25 are still on 4.9 kernels, they haven't rebased to 4.10. So
there is no repo with 4.10 in it, and in fact 4.10.1 has not been
built yet.
--
Chris Murphy
1:22 p.m.
On 03/01/2017 11:18 AM, Chris Murphy wrote:
On Wed, Mar 1, 2017 at 2:07 AM, Russel Winder
<russel(a)winder.org.uk> wrote:
> I appreciate that Rawhide always has the latest kernel snapshot as the
> one and only kernel and that it is up to users to manage their own
> kernels. However I wonder if there should be a simple, standard way of
> being able to install the last released kernel, perhaps a package last-
> release-kernel or something.
>
> The problem for me is that the release kernel only ever seems to be in
> Rawhide for one day, and if I miss updating on that day, I have missed
> capturing that kernel – it just happened with 4.10 so I am stuck with
> an rc8 rather than the release. (And 4.11 won't actually work for a few
> rcs yet, same for every new kernel.)
In dnf.conf add an exclude for the kernel, and then just manually
install them from koji. So you download kernel kernel-core and
kernel-modules RPMs from koji, then you can do 'dnf install *rpm'
while in the same directory that has the RPMs and it'll install them.
What you want to do isn't really possible right now I think. Fedora 24
and 25 are still on 4.9 kernels, they haven't rebased to 4.10. So
there is no repo with 4.10 in it, and in fact 4.10.1 has not been
built yet.
Fedora 25 is indeed on the 4.9 kernels (latest release is 4.9.12-200).
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital ricks(a)alldigital.com -
- AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 -
- -
- Is that a buffer overflow or are you just happy to see me? -
----------------------------------------------------------------------
6:21 p.m.
On Wed, 01 Mar 2017 18:04:04 +0000
Russel Winder <russel(a)winder.org.uk> wrote:
On Wed, 2017-03-01 at 17:58 +0000, Russel Winder wrote:
> On Wed, 2017-03-01 at 14:29 +0100, Sandro Mani wrote:
> > […]
> >
> > This should work:
> >
> > koji download-build --quiet --arch=$(uname -m) $(koji
> > latest-build --quiet f25 kernel | awk '{print $1}')
I guess the import point here is that you have to track the previous
release kernels, so for Rawhide as F26 follow the 4.9 kernels built
for F25, For the 4.10 kernels updates will only happen when Rawhide
moves to F27 and F26 tracks the releases. Will using a kernel built
for a previous release always work?
I suspect the answer is 'it depends'. If rawhide has introduced a
change to the dependencies of the kernel that is not backward
compatible, then using a kernel compiled with earlier versions of those
dependencies will probably fail on rawhide.
If you compile from the earlier src.rpm, and then install the locally
built kernel, it will work, because the kernel will use the
dependencies you have installed (they will be newer) to build.
There are instructions for building the kernel in the Fedora wiki, that
you can probably find with a search. Then, so dnf doesn't get upset,
just install with
dnf -C [local kernel rpms]
When the install is done, just delete the local rpms. And when you
update rawhide, be sure to use
dnf -x kernel\* update
so the kernel doesn't get replaced with a later version.
As long as you leave a good kernel around, you can always download the
earlier binary packages from koji, and just install those rpms with
dnf -C [downloaded kernel rpms]
If it breaks, boot the earlier good kernel, and dnf remove the failed
earlier kernel.
2614
days inactive
2615
days old
14 comments
7 participants
participants (7)
-
Chris Murphy -
Kevin Fenzi -
Peter Robinson -
Rick Stevens -
Russel Winder -
Sandro Mani -
stan