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