| 1 |
On Mon, 21 Oct 2019 22:54:26 +0000, Caveman Al Toraboran wrote: |
| 2 |
|
| 3 |
> you are just wrongly assuming that they are mutually |
| 4 |
> exclusive... |
| 5 |
> |
| 6 |
> seriously, one could have kernels named, |
| 7 |
> without versions, as: |
| 8 |
> |
| 9 |
> vmlinuz |
| 10 |
> vmlinuz-older |
| 11 |
> vmlinuz-older2 |
| 12 |
> . |
| 13 |
> . |
| 14 |
> . |
| 15 |
> vmlinuz-olderN |
| 16 |
> |
| 17 |
> this way, new kernel installation, and rotation, |
| 18 |
> will be decoupled from the boot loader's configs, |
| 19 |
> effectively removing any housekeeping for the |
| 20 |
> boot loader. |
| 21 |
|
| 22 |
make install will create symlinks for vmlinuz and vmlinuz.old to the |
| 23 |
latest and previous kernel, doing much of what you need. You need /boot |
| 24 |
to be on a filesystem that supports symlinks and ISTR that it only |
| 25 |
updates the symlinks if already present but doesn't create them from |
| 26 |
scratch. |
| 27 |
|
| 28 |
|
| 29 |
-- |
| 30 |
Neil Bothwick |
| 31 |
|
| 32 |
A journey of a thousand miles begins with a cash advance from Mom. |
Archives