From: Rich Freeman <rich0@gentoo.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] abi_x86_32 FLAG
Date: Tue, 21 Apr 2015 14:33:21 -0400 [thread overview]
Message-ID: <CAGfcS_kS0Z=SUVitC4S0Ru6b2KTi8K7e0ixxtWQxJcuzXQxjfA@mail.gmail.com> (raw)
In-Reply-To: <5536937C.5020003@baums-on-web.de>
On Tue, Apr 21, 2015 at 2:14 PM, Heiko Baums <lists@baums-on-web.de> wrote:
> Am 21.04.2015 um 20:06 schrieb Mike Gilbert:
>> On Mon, Apr 20, 2015 at 7:51 PM, Heiko Baums <lists@baums-on-web.de> wrote:
>>> Am 21.04.2015 um 01:27 schrieb Mike Gilbert:
>>>
>>>> Better yet, upgrade to grub:2 already.
>>>
>>> Why? As long as grub legacy is working there's no need to upgrade. I'm
>>> still running grub legacy, too.
>>>
>>
>> In this context, because you can build it without having any 32-bit
>> libs installed.
>
> That's what grub-static is for. So why would I upgrade to grub:2 if
> grub:0 is still working?
>
You don't have to, other than avoiding stuff like this, or for the
additional features.
While all the guides seem to be written around grub2-mkconfig you can
still use grub the old way and just create your own config file.
Grub2 is more flexible in terms of supported filesystems and such -
which is helpful if you're using lvm, mdadm, btrfs, and so on.
However, I don't think it accepts the old config file syntax so there
is some effort required to migrate. You'll of course want a rescue
boot device (but I'd say that applies whether you're migrating or
not).
I started out with a grub1-like approach and ended up moving to the
grub2 style. I just install my kernels with make install and then let
grub2-mkconfig set up my config files. The only issue I found is that
if you're playing with git kernels it doesn't always order the
versioning right (a.b.c+ isn't > a.b.c and things like this).
However, you can add your own rules to get entries auto-created which
can be helpful.
--
Rich
next prev parent reply other threads:[~2015-04-21 18:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 22:22 [gentoo-user] abi_x86_32 FLAG Joseph
2015-04-20 22:47 ` Heiko Baums
2015-04-20 23:27 ` Mike Gilbert
2015-04-20 23:51 ` Heiko Baums
2015-04-21 18:06 ` Mike Gilbert
2015-04-21 18:14 ` Heiko Baums
2015-04-21 18:33 ` Rich Freeman [this message]
2015-04-21 18:54 ` Mike Gilbert
2015-04-21 1:36 ` Daniel Frey
2015-04-21 10:05 ` Neil Bothwick
2015-04-21 14:06 ` [gentoo-user] " Grant Edwards
2015-04-21 1:14 ` [gentoo-user] " Joseph
2015-04-21 1:30 ` covici
2015-04-21 10:48 ` Heiko Baums
2015-04-21 1:37 ` Daniel Frey
2015-04-21 10:38 ` Heiko Baums
2015-04-21 11:19 ` Peter Humphrey
2015-04-22 8:10 ` Fernando Rodriguez
2015-04-22 8:54 ` Peter Humphrey
2015-04-22 9:20 ` Peter Humphrey
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAGfcS_kS0Z=SUVitC4S0Ru6b2KTi8K7e0ixxtWQxJcuzXQxjfA@mail.gmail.com' \
--to=rich0@gentoo.org \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox