Please don't cuss the kernel - it is one of best tested
(& least understood) portions of any Linux distribution
Potential > In Linux there is always alternate solutions:
The "standard practice" is to edit the loader
to boot any (uniquely named) kernel version desired.
Just as long as the path is correct.
I.E. The loader may have several "test" versions
concurrent to your (stable/production) favourite.
Another reason- it's not wise to use "make CLEAN or MRPROPER"
at least until certain old headers/etal are no longer desired.
What better way to have a fail-safe_fall-back escape route?
RFE ? >
it did whatever it is that it does while it is doing what it does when one doesn't know what it is doing. So that worked. I guess.
As I have & can personally
Automation will never replace backups (or outguess user)