1 |
On 02/01/18 19:26, Stroller wrote: |
2 |
> |
3 |
>> On 2 Jan 2018, at 11:54, Kruglov Sergey <kr_serge@×××××××.com> wrote: |
4 |
>> |
5 |
>> Now I have gentoo-sources-4.14.8-r1 installed. |
6 |
>> After "emerge --ask --update --deep --with-bdeps=y --newuse @world" command emerge installs old kernel in NS (after first update 4.12.12, after second update 4.9.49-r1). |
7 |
>> How can I fix it? |
8 |
>> There is sys-kernel/gentoo-sources in my world set. |
9 |
> |
10 |
> Remove sys-kernel/gentoo-sources from your world file - I believe you can do this using the emerge command, but am unsure of the right syntax; you can just edit /var/lib/portage/world and delete the appropriate line.D |
11 |
> |
12 |
> Now `emerge -n =sys-kernel/gentoo-sources-4.14.8-r1` - "This option can be used to update the world file without rebuilding the packages." |
13 |
> |
14 |
> This pins your kernel version at 4.14.8-r1 and you can update when, in future, you decide it's time to update your kernel, without being nagged about it every time a new version is release or you emerge world. |
15 |
> |
16 |
> For this reason it's always best to emerge kernels with an equals sign, pinning them at some specific version, IMO. |
17 |
> |
18 |
Why??? |
19 |
|
20 |
> This suggestion may provoke responses that the kernel is important and you should update it to ensure you get security updates - look at the attack vectors, you're probably sitting behind a NAT router, with very few ports exposed to the internet. |
21 |
> |
22 |
> It's adequate to update your kernel every 3 months. |
23 |
> |
24 |
You should also check the CVEs every time there's a new kernel! |
25 |
|
26 |
What this completely misses, is that gentoo-sources merely DOWNLOADS THE |
27 |
LATEST KERNEL SOURCE. So updating gentoo-sources every time does nothing |
28 |
to change the kernel you are running. |
29 |
|
30 |
Just leave gentoo-sources in your world file, and don't necessarily |
31 |
compile and update your running kernel just because gentoo-sources has |
32 |
had an update. |
33 |
|
34 |
I normally do not clean out kernels from my grub.conf until I've built |
35 |
up enough to be annoying, so downgrading a broken kernel is just a quick |
36 |
edit away ... |
37 |
|
38 |
Cheers, |
39 |
Wol |