| 1 |
On 2/9/21 3:55 PM, Neil Bothwick wrote: |
| 2 |
> On Tue, 9 Feb 2021 14:25:01 +0100, n952162 wrote: |
| 3 |
> |
| 4 |
>> gentoo policy is that administrators need to keep their systems |
| 5 |
>> up-to-date. The promise is, if they do so, the dependency system will |
| 6 |
>> be reliable. |
| 7 |
>> |
| 8 |
>> The kernel version is apparently an exception to this. The updating |
| 9 |
>> mechanism does not require that this track the synchronization of the |
| 10 |
>> portage tree. Administrators are free to decide what kernel they want |
| 11 |
>> to use. This works - except for virtualbox-modules. |
| 12 |
> Portage should check that the kernel pointed to by the /usr/src/linux |
| 13 |
> symlink is of a suitable version and has the necessary configuration |
| 14 |
> settings. Lots of ebuilds already do this. If the virtualbox-modules |
| 15 |
> ebuild is failing in this respect, it may well be a bug. |
| 16 |
> |
| 17 |
>> what is the most efficient way for an administrator to known when a new |
| 18 |
>> kernel is available and advisable? |
| 19 |
> You'll know because you'll see it in the list of packages to install when |
| 20 |
> upgrading. Additionally, there is an elog message when a new set of |
| 21 |
> kernel sources is installed, If you have |
| 22 |
> |
| 23 |
> PORTAGE_ELOG_SYSTEM="save mail" |
| 24 |
> PORTAGE_ELOG_MAILURI="you@..." |
| 25 |
> |
| 26 |
> in make.conf, you will be emailed this info. See man make.conf for more |
| 27 |
> on this. |
| 28 |
> |
| 29 |
> |
| 30 |
|
| 31 |
Excellent. I'll use that. |
Archives