| 1 |
On Saturday 30 Jun 2012 23:01:40 Neil Bothwick wrote: |
| 2 |
> On Sat, 30 Jun 2012 09:07:30 -0500, Dale wrote: |
| 3 |
|
| 4 |
> > It seems to expect to keep |
| 5 |
> > only two kernels around and I'm real bad to have more than that, |
| 6 |
> > sometimes way more than that. |
| 7 |
> |
| 8 |
> No it doesn't, it only installs kernels, not uninstalls them. Sure, there |
| 9 |
> are only two symlinks but those are less relevant with GRUB2 since |
| 10 |
> grub2-mkconfig creates menu entries for all your kernels anyway. |
| 11 |
|
| 12 |
Aha! This will be useful for me. |
| 13 |
|
| 14 |
I have not used make install because I found that it would override previous |
| 15 |
kernels of mine that I might needed to revert to. |
| 16 |
|
| 17 |
I remember you (or someone as knowledgeable) had mentioned of a way to |
| 18 |
automate the linkage and naming of vmlinuz so that older kernels were retained |
| 19 |
and versioned, but I never went as far as experimenting with it. |
| 20 |
|
| 21 |
> > Plus, if I do it myself, I know what I am |
| 22 |
> > doing. If I use make install, I don't know if something was changed in |
| 23 |
> > how it does it. |
| 24 |
> |
| 25 |
> So you trust make to compile and link hundreds of object files and create |
| 26 |
> the kernels and modules. You also trust it to copy all the modules, but |
| 27 |
> you just want to copy that one last file manually so you can pretend you |
| 28 |
> are in control? ;-) |
| 29 |
|
| 30 |
Well, he and I are at least in control of this copying and naming actions? |
| 31 |
;-) |
| 32 |
-- |
| 33 |
Regards, |
| 34 |
Mick |
Archives