1 |
On 2/9/21 2:56 PM, Michael wrote: |
2 |
> On Tuesday, 9 February 2021 13:25:01 GMT n952162 wrote: |
3 |
>> On 2/9/21 12:57 PM, Michael wrote: |
4 |
>>> On Tuesday, 9 February 2021 10:01:04 GMT n952162 wrote: |
5 |
>>>> On 2/9/21 10:05 AM, Dale wrote: |
6 |
>>>>> n952162 wrote: |
7 |
>>>>>> Are extra administrative steps necessary when --sync brings in a new |
8 |
>>>>>> |
9 |
>>>>>> kernel, as in: |
10 |
>>>>>> https://wiki.gentoo.org/wiki/Kernel/Upgrade |
11 |
>>>>>> |
12 |
>>>>>> I currently have this situation: |
13 |
>>>>>> |
14 |
>>>>>> $ uname -a |
15 |
>>>>>> Linux host *4.19.72-gentoo* #7 SMP Tue Jun 9 19:51:52 CEST 2020 x86_64 |
16 |
>>>>>> GNU/Linux |
17 |
>>>>>> |
18 |
>>>>>> $ eselect kernel list |
19 |
>>>>>> |
20 |
>>>>>> Available kernel symlink targets: |
21 |
>>>>>> [1] linux-5.4.72-gentoo |
22 |
>>>>>> [2] linux-5.4.80-gentoo-r1 |
23 |
>>>>>> [3] linux-5.4.92-gentoo |
24 |
>>>>>> |
25 |
>>>>>> If an update requires additional steps, shouldn't that have appeared |
26 |
>>>>>> in the news? |
27 |
>>>>> It depends I think. I say think because there may be a binary kernel |
28 |
>>>>> available which will upgrade itself. I seem to recall reading about it |
29 |
>>>>> on a mailing list somewhere. I have no experience with it tho. That |
30 |
>>>>> said, if you use the old method, you have to upgrade the kernel |
31 |
>>>>> yourself. There are scripts you can use to help automate it a good bit |
32 |
>>>>> but some of us still do it the manual way. When you do updates, emerge |
33 |
>>>>> will pull in the new sources but the rest is up to you. I suspect most |
34 |
>>>>> that do it the old way, copy .config over to the new kernel directory, |
35 |
>>>>> run make oldconfig and answer the questions, compile the new kernel, |
36 |
>>>>> copy it to /boot using the right method which there is a few of and then |
37 |
>>>>> configure your bootloader if needed. The link you posted explains this |
38 |
>>>>> in more detail, and may be more complete too. |
39 |
>>>>> |
40 |
>>>>> I'm trying to remember what that binary kernel thing is called. I just |
41 |
>>>>> skimmed the messages so it could be something else or not even in the |
42 |
>>>>> tree yet. |
43 |
>>>>> |
44 |
>>>>> Dale |
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 |
51 |
>>>> that... |
52 |
>>> I'm not sure I understand completely why there should be a news item from |
53 |
>>> portage whenever new kernel sources are updated and downloaded. It is up |
54 |
>>> the system administrator to configure and build the new sources if |
55 |
>>> desired. |
56 |
>> gentoo policy is that administrators need to keep their systems |
57 |
>> up-to-date. The promise is, if they do so, the dependency system will |
58 |
>> be reliable. |
59 |
>> |
60 |
>> The kernel version is apparently an exception to this. The updating |
61 |
>> mechanism does not require that this track the synchronization of the |
62 |
>> portage tree. Administrators are free to decide what kernel they want |
63 |
>> to use. This works - except for virtualbox-modules. |
64 |
>> |
65 |
>>> Each time you upgrade your kernel on the host, external modules will |
66 |
>>> require updating/rebuilding. The set '@module-rebuild' does that instead |
67 |
>>> of having to re-emerge manually each external module. |
68 |
>> Yes, in another context, your tip about this helped me to solve a |
69 |
>> separate problem with vbox. A quick survey didn't find mention of this |
70 |
>> facility in the handbook. Perhaps I missed it. |
71 |
> Yes, I just found it in the Handbook here: |
72 |
> |
73 |
> https://wiki.gentoo.org/wiki/Handbook:AMD64/Installation/Kernel#Post-install. |
74 |
> 2Fupgrade_tasks |
75 |
> |
76 |
> |
77 |
> and in the wiki here: |
78 |
> |
79 |
> https://wiki.gentoo.org/wiki/Kernel/ |
80 |
> Upgrade#Reinstalling_external_kernel_modules |
81 |
> |
82 |
|
83 |
Okay, good. Thank you. |
84 |
|
85 |
|
86 |
|
87 |
> Or you could shoot for the latest stable 5.4.92, which |
88 |
> works fine here, also on a host which runs VBox. |
89 |
|
90 |
|
91 |
Yes, I'll do that. |