| 1 |
you are just wrongly assuming that they are mutually |
| 2 |
exclusive... |
| 3 |
|
| 4 |
seriously, one could have kernels named, |
| 5 |
without versions, as: |
| 6 |
|
| 7 |
vmlinuz |
| 8 |
vmlinuz-older |
| 9 |
vmlinuz-older2 |
| 10 |
. |
| 11 |
. |
| 12 |
. |
| 13 |
vmlinuz-olderN |
| 14 |
|
| 15 |
this way, new kernel installation, and rotation, |
| 16 |
will be decoupled from the boot loader's configs, |
| 17 |
effectively removing any housekeeping for the |
| 18 |
boot loader. |
| 19 |
|
| 20 |
|
| 21 |
rgrds, |
| 22 |
cm. |
| 23 |
|
| 24 |
‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐ |
| 25 |
On Monday, October 21, 2019 7:07 PM, Wols Lists <antlists@××××××××××××.uk> wrote: |
| 26 |
> |
| 27 |
> You just want a nasty recovery job if the update screws up ... |
| 28 |
> |
| 29 |
> Seriously, I always just add new kernels as the new default option, |
| 30 |
> precisely so as I can go back to a working one if things go wrogn ... |
| 31 |
> |
| 32 |
> Cheers, |
| 33 |
> Wol |
Archives