Now that grub is slotted (slot:2 is grub2; slot:0 is legacy grub),
an update world will merge grub-2.00 along side my current
grub-0.97-r12.

Am I correct in believing that, if I *do* the emerge but *not* do
anything else with grub, I will continue to use legacy grub (-0.97-r12)
whenever I boot?

I realize I can add
sys-boot/grub:2
to package.mask

thanks,
allan

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 29.06.2012 20:46, Allan Gottlieb wrote:
> Now that grub is slotted (slot:2 is grub2; slot:0 is legacy grub),
> an update world will merge grub-2.00 along side my current
> grub-0.97-r12.
>
> Am I correct in believing that, if I *do* the emerge but *not* do
> anything else with grub, I will continue to use legacy grub
> (-0.97-r12) whenever I boot?
>
> I realize I can add sys-boot/grub:2 to package.mask
>
> thanks, allan
>

Yes - to both

- - you can mask the slot for grub2
- - you can install grub2 (that is the binaries) and continue to use
grub legacy (until you issue grub2-install <device>).

Personally I use grub2 for at least 2 years (1.97 or something like
that) and encountered few to none problems.
I find it even more comfortable (due to automatic config generation).

WKR
Hinnerk
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP7fpbAAoJEJwwOFaNFkYc2EwIAItuXOtIVl M5cliFnuYTrCgA
eQ7iXSgE0PuBW7ShEIG2GU5HNzxhkMwNZbmxF4fUS6AEbbI/b9ie0YIdAOBwS1FB
bRxHGtW2DxcnR4f6ih7QKjBZ9Mc7wKmIma1+/7NfkCfcvEG3BT2SkWPRxPTU8xOV
GWKH2ZuYEk00R1mvhD7tScVEhFS0xs82iS6K3KLd+kptKd6K0u PDphfTg+5yfqam
dAV0RHO2cYAswB/nNTRpTJ3uGQZnR+HJCsyF0NplZ4skqbtp3yas324x0UaHdOw0
8rTkJFDA0BPN4JnN+L58Po00jJLVzGcWO5t9WGLEStaavLeNds MEfIDxoZtPUeY=
=T0Ig
-----END PGP SIGNATURE-----

* Allan Gottlieb <gottlieb@nyu.edu> [120629 14:53]:
> Now that grub is slotted (slot:2 is grub2; slot:0 is legacy grub),
> an update world will merge grub-2.00 along side my current
> grub-0.97-r12.
>
> Am I correct in believing that, if I *do* the emerge but *not* do
> anything else with grub, I will continue to use legacy grub (-0.97-r12)
> whenever I boot?
>
> I realize I can add
> sys-boot/grub:2
> to package.mask
>
> thanks,
> allan

I believe that's the case. Until you run grub2-install you'll still run
your old grub 0.92-r12.

Make sure you do the step mentioned in the emerge output though and get
grub:0 in your world file or else the next emerge --depclean will remove
your grub-0.97-r12.

Todd

On Fri, Jun 29 2012, Hinnerk van Bruinehsen wrote:

> On 29.06.2012 20:46, Allan Gottlieb wrote:
>> Now that grub is slotted (slot:2 is grub2; slot:0 is legacy grub),
>> an update world will merge grub-2.00 along side my current
>> grub-0.97-r12.
>>
>> Am I correct in believing that, if I *do* the emerge but *not* do
>> anything else with grub, I will continue to use legacy grub
>> (-0.97-r12) whenever I boot?
>>
>> I realize I can add sys-boot/grub:2 to package.mask
>>
>> thanks, allan
>>
>
> Yes - to both
>
> - you can mask the slot for grub2
> - you can install grub2 (that is the binaries) and continue to use
> grub legacy (until you issue grub2-install <device>).

Great. As I thought.
thanks,
allan

On Fri, Jun 29 2012, Todd Goodman wrote:

> * Allan Gottlieb <gottlieb@nyu.edu> [120629 14:53]:
>> Now that grub is slotted (slot:2 is grub2; slot:0 is legacy grub),
>> an update world will merge grub-2.00 along side my current
>> grub-0.97-r12.
>>
>> Am I correct in believing that, if I *do* the emerge but *not* do
>> anything else with grub, I will continue to use legacy grub (-0.97-r12)
>> whenever I boot?
>>
>> I realize I can add
>> sys-boot/grub:2
>> to package.mask
>>
>> thanks,
>> allan
>
> I believe that's the case. Until you run grub2-install you'll still run
> your old grub 0.92-r12.
>
> Make sure you do the step mentioned in the emerge output though and get
> grub:0 in your world file or else the next emerge --depclean will remove
> your grub-0.97-r12.

Thanks for the heads-up.
allan