1 |
what one doesn't use grub? |
2 |
|
3 |
rgrds, |
4 |
cm. |
5 |
|
6 |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ |
7 |
On Friday, October 18, 2019 3:36 PM, Rich Freeman <rich0@g.o> wrote: |
8 |
|
9 |
> On Fri, Oct 18, 2019 at 6:51 AM Alexander Openkowski |
10 |
> opncow@××××××××××.com wrote: |
11 |
> |
12 |
> > I struggle with the naming of genkernel generated kernels for quite a while now and have written a small wapper script for this purpose... |
13 |
> |
14 |
> Somebody else shared the same problem and wrote a fairly complex |
15 |
> wrapper, and it is installed on most reader's systems already. It is |
16 |
> called grub-mkconfig. :) |
17 |
> |
18 |
> Hey, I get it. I used to do it exactly they way you do. However, the |
19 |
> kernel's make install, and the default behavior of both dracut and |
20 |
> genkernel, all use a consistent naming convention that is compatible |
21 |
> with grub-mkconfig, and I found that it was way easier to join them |
22 |
> then to try to beat them. As a bonus it is easier to keep a library |
23 |
> of past kernel versions in my boot menu. |
24 |
> |
25 |
> Now, what I could use is a script/tool that will clean up those |
26 |
> versions using some kind of rotation strategy like: |
27 |
> |
28 |
> 1. Keep the last 5 versions of the current series. |
29 |
> 2. Keep the last version of each of the last two longterm series. |
30 |
> 3. Keep one version of every stable series between the current and |
31 |
> the last longterm series. |
32 |
> |
33 |
> And this would apply to everything in /boot except config files, and |
34 |
> to modules as well. Config files outside this range would get moved |
35 |
> into some archive directory of old configs. |
36 |
> |
37 |
> -- |
38 |
> Rich |
39 |
> |