On 17/08/17 06:28 AM, cagsm wrote:
On Wed, Aug 16, 2017 at 3:58 PM, Anton Aylward <opensuse@antonaylward.com> wrote:
Just out of curiosity ... Why are you manually removing the kernels rather than using the 'purge_kernels" utility?
I used to have situations when I reboot a machine and the newly installed kernel (via zypper up) didnt become the booted kernel.
I can think of a few reasons for that happening but the all get back to the rebuilding of the grub.conf menu of kernels. Since you are making sure you have only the one kernel you never see that the bot menu can offer a choice of the menus available.
Ever since those troubles and hassle I always remove the currently running kernel packe while still being on the machine alive, and then only the new kernel package from a zypper up remains and becomes the booted one. Learned the hard way.
There are, I suppose, ways to disable the rebuilding of the grub.conf after zypper up installs a new kernel but they don't come to mind. Maybe be it ha to do with multiversion.kernels setting in /etc/zypp/zypp.conf ? There are those of us that keep a backlog of kernels as well as specific kennels using that setting and do purge others.
Maybe its just me or its specialties and corner cases or whatever but this way I have more control, and grub2 logics and syntax and all those config files seem too hard or too cumbersome and chaos to me or I never had time so far to really get my head around all those places where you influence what gets written into grub2 places and what becomes the active to be booted entry and so on.
Just so. -- A: Yes. > Q: Are you sure? >> A: Because it reverses the logical flow of conversation. >>> Q: Why is top posting frowned upon? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org