Re: [gentoo-user] Re: redoing grub-2 after emerge updates it

[Walter Dnes]

On Fri, Jul 07, 2017 at 02:14:55PM -0400, Harry Putnam wrote

> You are correct.. `emerge world' made some kind of upgrade/update to
> grub2 which I've been using a fair good while.  The install process
> ended with some kind of heads up.  I didn't keep the wording emerge
> used but it made me think I might aught to redo actually installing
> into /dev/sda and grub/grub.cfg... hence my question

  See if you have the message the grub buildlog in /var/log/portage/
or in /var/log/portage/elog.  The logfile name should contain
"sys-boot:grub".  Try the following...

find /var/log/portage -name sys-boot*

  This will give you a list of logfile names.  You can feed the most
recent one into "less" and look for a message, usually near the end.

-- 
Walter Dnes 
I don't run "desktop environments"; I run useful applications

[gentoo-user] Re: redoing grub-2 after emerge updates it

[Harry Putnam]

Mike Gilbert  writes:


[...]

Mick wrote:

>> As has already stated you could stay put with your old version, provided you
>> have no specific reason to stop using it.  GRUB2 can be installed and left
>> unused.  I guess from a usability perspective as long as you have no need to
>> employ GRUB2's new functionality/features, main difference between GRUB 
>> legacy
>> and GRUB2 can be boiled down to what you need to do each time you install a
>> new kernel.
>>
>> With GRUB legacy you edit on your own your /boot/grub/grub.conf to add the
>> name and version of your newly installed kernel and initrd (if you use one of
>> these).
>>
>> With GRUB2 you run a single command line and leave it to GRUB2's scripts to
>> scan your boot and other drives, discover their contents and auto-complete
>> /boot/grub/grub.cfg.

Mike wrote:

> Harry made no mention of GRUB Legacy in his original email. I assume
> he was upgrading from grub-2.02~beta3 to grub-2.02.

You are correct.. `emerge world' made some kind of upgrade/update to
grub2 which I've been using a fair good while.  The install process
ended with some kind of heads up.  I didn't keep the wording emerge
used but it made me think I might aught to redo actually installing
into /dev/sda and grub/grub.cfg... hence my question

You mentioned the version change.. but I didn't bother to investigate
what the change really was.

I spent a good bit of time, about 7/8 mnths ago, fearing the switch
just when I had become at least sort of competent with legacy grub
after years of use, and knew squat about grub 2.  Finally braved up
and discovered it was really very easy to get thru.

Re: [gentoo-user] Re: redoing grub-2 after emerge updates it

[Mike Gilbert]

On Fri, Jul 7, 2017 at 12:16 PM, Mick  wrote:
> On Friday 07 Jul 2017 11:49:11 Harry Putnam wrote:
>> Mike Gilbert  writes:
>>
>> [...]
>>
>> > If you want to use the new version to boot your system, you should
>> > re-run grub-install, which will copy the modules to /boot/grub and
>> > will install the core image to your MBR or EFI system partition.
>>
>> Thanks for the info.
>>
>> I don't know what the update was but since its easy enough to run
>> `grub-install /dev/sda' and I guess also run
>> grub-mkconfig -o /boot/grub/grub.cfg
>>
>> Anyway, I did those two things... just being on the safe side.
>
> As has already stated you could stay put with your old version, provided you
> have no specific reason to stop using it.  GRUB2 can be installed and left
> unused.  I guess from a usability perspective as long as you have no need to
> employ GRUB2's new functionality/features, main difference between GRUB legacy
> and GRUB2 can be boiled down to what you need to do each time you install a
> new kernel.
>
> With GRUB legacy you edit on your own your /boot/grub/grub.conf to add the
> name and version of your newly installed kernel and initrd (if you use one of
> these).
>
> With GRUB2 you run a single command line and leave it to GRUB2's scripts to
> scan your boot and other drives, discover their contents and auto-complete
> /boot/grub/grub.cfg.

Harry made no mention of GRUB Legacy in his original email. I assume
he was upgrading from grub-2.02~beta3 to grub-2.02.

Also, it is perfectly acceptable to hand-write your GRUB2
configuration file; grub-mkconfig is not mandatory. It's just often
easier for new users with simple boot configurations, or for people
who don't want to worry about hand-editing the config for every kernel
upgrade.

Re: [gentoo-user] Re: redoing grub-2 after emerge updates it

[Mick]

On Friday 07 Jul 2017 11:49:11 Harry Putnam wrote:
> Mike Gilbert  writes:
> 
> [...]
> 
> > If you want to use the new version to boot your system, you should
> > re-run grub-install, which will copy the modules to /boot/grub and
> > will install the core image to your MBR or EFI system partition.
> 
> Thanks for the info.
> 
> I don't know what the update was but since its easy enough to run
> `grub-install /dev/sda' and I guess also run
> grub-mkconfig -o /boot/grub/grub.cfg
> 
> Anyway, I did those two things... just being on the safe side.

As has already stated you could stay put with your old version, provided you 
have no specific reason to stop using it.  GRUB2 can be installed and left 
unused.  I guess from a usability perspective as long as you have no need to 
employ GRUB2's new functionality/features, main difference between GRUB legacy 
and GRUB2 can be boiled down to what you need to do each time you install a 
new kernel.

With GRUB legacy you edit on your own your /boot/grub/grub.conf to add the 
name and version of your newly installed kernel and initrd (if you use one of 
these).

With GRUB2 you run a single command line and leave it to GRUB2's scripts to 
scan your boot and other drives, discover their contents and auto-complete 
/boot/grub/grub.cfg.
-- 
Regards,
Mick

signature.asc
Description: This is a digitally signed message part.

[gentoo-user] Re: redoing grub-2 after emerge updates it

[Harry Putnam]

Mike Gilbert  writes:

[...]

> If you want to use the new version to boot your system, you should
> re-run grub-install, which will copy the modules to /boot/grub and
> will install the core image to your MBR or EFI system partition.

Thanks for the info.

I don't know what the update was but since its easy enough to run
`grub-install /dev/sda' and I guess also run
grub-mkconfig -o /boot/grub/grub.cfg

Anyway, I did those two things... just being on the safe side.