1 |
Dale, |
2 |
|
3 |
On Thursday, 2021-07-01 01:59:57 -0500, you wrote: |
4 |
|
5 |
> ... |
6 |
> |
7 |
> The subject line pretty much describes this. How does one manage the |
8 |
> system.map file in /boot? Is it needed? Should it be updated with each |
9 |
> kernel? I tend to keep 2 to 3 kernels installed. |
10 |
|
11 |
Same here. And whenever I configure a new kernel my kernel managing |
12 |
script makes sure both, the kernel I'm currenty running on and the one |
13 |
just configured are in "@world". That way "emerge --depclean" will nev- |
14 |
er remove a kernel package. |
15 |
|
16 |
When I finally decide to explicitly remove a kernel my kernel managing |
17 |
script will basically execute this before calling "grub-mkconfig": |
18 |
|
19 |
# Argument 1 must contain slot number of kernel to be removed. |
20 |
|
21 |
emerge --deselect --quiet sys-kernel/gentoo-sources:$1 |
22 |
rm -fr /lib/modules/$1-gentoo /boot/*-$1-gentoo{,.old} \ |
23 |
/usr/src/linux-$1-gentoo |
24 |
|
25 |
This is stuff I somewhere picked up from the Gentoo Handbook when I did |
26 |
my first Gentoo install. |
27 |
|
28 |
> ... |
29 |
> Should I version the |
30 |
> system.map file the same as kernels? |
31 |
|
32 |
Not sure about that. Mine ARE versioned. That's probably what "grub- |
33 |
mkconfig" is doing by default. |
34 |
|
35 |
Sincerely, |
36 |
Rainer |