Mick wrote: > On Saturday 30 Jun 2012 23:01:40 Neil Bothwick wrote: >> On Sat, 30 Jun 2012 09:07:30 -0500, Dale wrote: >>> It seems to expect to keep >>> only two kernels around and I'm real bad to have more than that, >>> sometimes way more than that. >> No it doesn't, it only installs kernels, not uninstalls them. Sure, there >> are only two symlinks but those are less relevant with GRUB2 since >> grub2-mkconfig creates menu entries for all your kernels anyway. > Aha! This will be useful for me. > > I have not used make install because I found that it would override previous > kernels of mine that I might needed to revert to. > > I remember you (or someone as knowledgeable) had mentioned of a way to > automate the linkage and naming of vmlinuz so that older kernels were > retained > and versioned, but I never went as far as experimenting with it.
Me either. I just do it the easy way using cp. That way, I know what is what and that I have not overwritten anything I might need later. I like to be sure since I have had kernels with bugs for my system. > >>> Plus, if I do it myself, I know what I am >>> doing. If I use make install, I don't know if something was changed in >>> how it does it. >> So you trust make to compile and link hundreds of object files and create >> the kernels and modules. You also trust it to copy all the modules, but >> you just want to copy that one last file manually so you can pretend you >> are in control? ;-) > Well, he and I are at least in control of this copying and naming actions? > ;-) I might add, I don't use modules except for nvidia which is outside the kernel. So, I may be in more control than you think. ;-) Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words!
