On 25/08/2018 05:51, Glenn English wrote:
This thread on grub2 is getting really scary. I'm afraid to make
changes in the grub2 configs because an error could easily brick my
machine. And futzing with /etc/default doesn't seem to impress grub2 a
whole lot. Not concerning what I want to do,
On Fri 24 Aug 2018 at 17:51:20 (+), Glenn English wrote:
> On Fri, Aug 24, 2018 at 6:57 AM wrote:
>
> > Indeed -- I had to do this a couple of days ago, and in my notes
> > (I do take notes when doing such things: age and that) I see
> >
> > "Jeez. What a Rube Goldberg. Should I say Grube
On Fri, Aug 24, 2018 at 6:57 AM wrote:
> Indeed -- I had to do this a couple of days ago, and in my notes
> (I do take notes when doing such things: age and that) I see
>
> "Jeez. What a Rube Goldberg. Should I say Grube Goldberg?"
>
> It's one of those cases where each step towards building
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Fri, Aug 24, 2018 at 10:37:43AM +1200, Ben Caradoc-Davies wrote:
> On 24/08/2018 06:14, Glenn English wrote:
> >I'm told that grub.cfg is a place I don't want to be. Can someone tell
> >me how to get grub to boot the working OS, or maybe how to fix
On 24/08/2018 10:41, Ben Caradoc-Davies wrote:
On 24/08/2018 10:37, Ben Caradoc-Davies wrote:
The new format to specify a different default kernel is horrific; it
contains menu items separated with ">". You need to get the full label
from your generated grub.conf because it likely contains
On 24/08/2018 10:37, Ben Caradoc-Davies wrote:
The new format to specify a different default kernel is horrific; it
contains menu items separated with ">". You need to get the full label
from your generated grub.conf because it likely contains device UUIDs:
On 24/08/2018 06:14, Glenn English wrote:
I'm told that grub.cfg is a place I don't want to be. Can someone tell
me how to get grub to boot the working OS, or maybe how to fix the new
one?
The recommended way to configure Grub 2 on Debian is to edit
/etc/default/grub and run update-grub .
7 matches
Mail list logo
