On Sat, Jan 20, 2018 at 10:47 AM, Tom Horsley wrote:
> On Sat, 20 Jan 2018 10:24:26 -0500
> Sam Varshavchik wrote:
>>
>> Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and then
>> subsequently installed kernels new without grubby causing any issues?
>
> I never use /etc/default/
On Sat, Jan 20, 2018 at 10:24 AM, Sam Varshavchik wrote:
> I edited GRUB_CMDLINE_LINUX in /etc/default/grub before I installed
> the most recent kernel update. However the grub entry for the new
> kernel did not reflect my changes in the updated /boot/grub2/grub.cfg
>
> Digging into this, it app
On 21/1/18 12:50 pm, stan wrote:
On Sun, 21 Jan 2018 11:30:46 +1100
Stephen Morris wrote:
I have always used grub2-mkconfig and the old grub equivalent as I
have never liked the boot menus that grubby generates. The one thing
I don't like about this process is that I also boot Ubuntu and
Windo
On Sun, 21 Jan 2018 11:30:46 +1100
Stephen Morris wrote:
> I have always used grub2-mkconfig and the old grub equivalent as I
> have never liked the boot menus that grubby generates. The one thing
> I don't like about this process is that I also boot Ubuntu and
> Windows from the grub menu as wel
On 21/1/18 4:58 am, stan wrote:
On Sat, 20 Jan 2018 10:24:26 -0500
Sam Varshavchik wrote:
Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and
then subsequently installed kernels new without grubby causing any
issues?
Yes, I've done this without any problems. Grubby puts the
On Sat, 20 Jan 2018 10:24:26 -0500
Sam Varshavchik wrote:
> Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and
> then subsequently installed kernels new without grubby causing any
> issues?
Yes, I've done this without any problems. Grubby puts the latest entry
on its own line
On Sat, 20 Jan 2018 10:24:26 -0500
Sam Varshavchik wrote:
> Did anyone use grub2-mkconfig before, to generate a new grub.cfg, and then
> subsequently installed kernels new without grubby causing any issues?
I never use /etc/default/grub, I always edit the grub.cfg file by hand.
The whole grub2-
I edited GRUB_CMDLINE_LINUX in /etc/default/grub before I installed the most
recent kernel update. However the grub entry for the new kernel did not
reflect my changes in the updated /boot/grub2/grub.cfg
Digging into this, it appears that the kernel packages run the grubby tool
which appear
