1 |
On 2/9/21 10:05 AM, Dale wrote: |
2 |
> n952162 wrote: |
3 |
>> Are extra administrative steps necessary when --sync brings in a new |
4 |
>> kernel, as in: |
5 |
>> |
6 |
>> https://wiki.gentoo.org/wiki/Kernel/Upgrade |
7 |
>> |
8 |
>> I currently have this situation: |
9 |
>> |
10 |
>> $ uname -a |
11 |
>> Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 |
12 |
>> GNU/Linux |
13 |
>> |
14 |
>> $ eselect kernel list |
15 |
>> Available kernel symlink targets: |
16 |
>> [1] linux-5.4.72-gentoo |
17 |
>> [2] linux-5.4.80-gentoo-r1 |
18 |
>> [3] linux-5.4.92-gentoo |
19 |
>> |
20 |
>> If an update requires additional steps, shouldn't that have appeared |
21 |
>> in the news? |
22 |
>> |
23 |
>> |
24 |
> |
25 |
> It depends I think. I say think because there may be a binary kernel |
26 |
> available which will upgrade itself. I seem to recall reading about it |
27 |
> on a mailing list somewhere. I have no experience with it tho. That |
28 |
> said, if you use the old method, you have to upgrade the kernel |
29 |
> yourself. There are scripts you can use to help automate it a good bit |
30 |
> but some of us still do it the manual way. When you do updates, emerge |
31 |
> will pull in the new sources but the rest is up to you. I suspect most |
32 |
> that do it the old way, copy .config over to the new kernel directory, |
33 |
> run make oldconfig and answer the questions, compile the new kernel, |
34 |
> copy it to /boot using the right method which there is a few of and then |
35 |
> configure your bootloader if needed. The link you posted explains this |
36 |
> in more detail, and may be more complete too. |
37 |
> |
38 |
> I'm trying to remember what that binary kernel thing is called. I just |
39 |
> skimmed the messages so it could be something else or not even in the |
40 |
> tree yet. |
41 |
> |
42 |
> Dale |
43 |
> |
44 |
> :-) :-) |
45 |
> |
46 |
|
47 |
Ah, maybe I have a theory what's going on ... maybe there's no news that |
48 |
it's time to upgrade the kernel, because it's not meant that the kernel |
49 |
necessarily needs to be upgraded ... except that it seems that the |
50 |
virtualbox-modules package might have a (unfortunate) dependency on that... |