Bug 5177 - new kernel don't set by default
: new kernel don't set by default
Status: RESOLVED WONTFIX
Product: Desktop Bugs
Classification: ROSA Desktop
Component: Main Packages
: unspecified
: All Linux
: Normal normal
: ---
Assigned To: Konstantin Vlasov
: Desktop Triage Team
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-03-14 19:22 MSK by Vladimir Potapov
Modified: 2016-01-31 17:10 MSK (History)
1 user (show)

See Also:
RPM Package:
ISO-related:
Bad POT generating:
Upstream:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Potapov 2015-03-14 19:22:00 MSK
1) set up kernel-desktop-latest
2) The kernel don't set by default

grub set up with links, I set kernel in main system
Comment 1 Konstantin Vlasov 2015-03-14 19:58:25 MSK
If by "default" you mean the kernel that appears as primary boot menu entry, there's very little I can do. Kernels are sorted newest-to-oldest (by their names and versions), and the newest one is made the primary.

How could Grub know which one was installed first, and which one last? And even if it did, then updating the system from repository would just totally mess the list of kernels depending on the random order in which they happened to be updated.

If, taking that into account, you have any particular suggestions about kernels sorting criteria, I'm ready to discuss them.
Comment 2 Vladimir Potapov 2015-03-14 20:20:21 MSK
I expect any kernel sort method (in extended menu).
But I expect last installed kernel by default.
Comment 3 Konstantin Vlasov 2015-03-14 21:29:23 MSK
How do you suggest to solve the following problem?
1. You have ROSA Fresh with kernel-nrj-desktop-3.14.25.
2. You install kernel-desktop-3.14.25. By your suggestion it becomes default.
3. Now you make urpmi --auto-update. It updates both kernels to kernel-nrj-desktop-3.14.33 and kernel-desktop-3.14.33, respectively, but you cannot predict in which order they will be updated.

urpmi does not guarantee any order of package installation. So you may end up with either non-nrj remaining default, or nrj becoming default instead, and no way for you to control this totally random process (unless, of course, you update them manually - first nrj, then as a separate transaction - non-nrj).
Comment 4 Vladimir Potapov 2015-03-15 18:25:01 MSK
Hm. If I install -pae kernel, after kernel update I may be random load non - pae by default.
It's surprise!
Comment 5 Konstantin Vlasov 2015-03-15 21:16:01 MSK
(In reply to comment #4)
> Hm. If I install -pae kernel, after kernel update I may be random load non -
> pae by default.
> It's surprise!

For now - there is no random. All kernels are sorted by their names/versions, the last one becomes the default, no matter in which order you installed them.

Random will appear if I implement your suggestion.
Comment 6 Vladimir Potapov 2015-03-18 11:29:07 MSK
Hm. I see marathon.
I have 3.0.69 by default.
I set up kernel-nrj-desktop686-pae-latest
System set up 3.0.28 pae kernel, the kernel set by default in  grub.
Comment 7 Konstantin Vlasov 2015-03-18 21:06:41 MSK
(In reply to comment #6)
> Hm. I see marathon.
> I have 3.0.69 by default.
> I set up kernel-nrj-desktop686-pae-latest
> System set up 3.0.28 pae kernel, the kernel set by default in  grub.

Too little information, but when Marathon comes into view, it totally messes things up, because:
1. If you install kernel in Marathon, it creates its own Grub-legacy menu according to its own sorting rules which I have no influence on.
2. Therefore, if you boot using Grub-legacy, it just shows you the list of kernels. And if you are using Grub2 as main bootloader, then you update Grub2 menu, and menu entries are recreated exactly in the same order as Grub-legacy created them.
Comment 8 Denis Silakov 2016-01-31 17:10:49 MSK
It doesn't seem that we are going to change anything in this area. We are fine with the current behavior when newest kernel is set as default by grub, since this guarantees predictable behavior. If you really want to boot older kernel by default, feel free to modify your grub configuration.