public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alec Ten Harmsel <alec@alectenharmsel.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] grub-2 update
Date: Thu, 16 Jul 2015 15:58:40 -0400	[thread overview]
Message-ID: <EAAC2AAD-547F-4FBA-BFF6-9E083ED4D553@alectenharmsel.com> (raw)
In-Reply-To: <55A80A2F.3010501@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]


> On Jul 16, 2015, at 3:46 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> 
> On 16/07/2015 21:34, James wrote:
>> Hello::
>> 
>> Background::
>> I have had many challenges with grub 2, in the past (as have many).
>> 
>> Current::
>> Grub-2.02_beta2-r3  wants to upgrade to
>> grub-2.02_beta2-r7   It appears to be marked stable.....
>> 
>> 
> 
> The don't use it, grub:0 still works just fine :-)
> 

It looks like he’s going from grub-2.02 to grub-2.02. I don’t think any action is necessary.

> I gave grub-2 a try earlier this week and once again couldn;t figure out
> how to install that mini-OS that bootstraps a boot loader which
> bootstraps a boot loader which loads code that loads a kernel. So back
> to grub:0 for me
> 
> 
> -- 
> Alan McKinnon
> alan.mckinnon@gmail.com <mailto:alan.mckinnon@gmail.com>
How complicated is your partitioning? I have always used a single partition for all of my personal machines, and it’s always been a simple process.

    grub-install --recheck /dev/sda
    grub-mkconfig -o /boot/grub/grub.cfg

I know that for servers it’s common to have a bunch of partitions to prevent a rogue process from filling up the entire disk and tanking the entire system, but I can’t imagine it’s that much more complex.

Alec

[-- Attachment #2: Type: text/html, Size: 9828 bytes --]

  reply	other threads:[~2015-07-16 19:58 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-16 19:34 [gentoo-user] grub-2 update James
2015-07-16 19:46 ` Alan McKinnon
2015-07-16 19:58   ` Alec Ten Harmsel [this message]
2015-07-16 20:05     ` [gentoo-user] " James
2015-07-16 21:26       ` Heiko Baums
2015-07-16 20:01   ` James
2015-07-16 21:41     ` Neil Bothwick
2015-07-16 23:54       ` Jonathan Callen
2015-07-17  7:36         ` Neil Bothwick
2015-07-17  8:45           ` wraeth
2015-07-17  9:40             ` Neil Bothwick
2015-07-17 10:07               ` wraeth
2015-07-16 20:02 ` [gentoo-user] " Jarry
2015-07-16 20:08   ` [gentoo-user] " James
2015-07-16 20:14     ` Jarry
2015-07-16 20:44       ` Steven Lembark
2015-07-17 14:30         ` James
2015-07-16 21:40 ` [gentoo-user] " Neil Bothwick
2015-07-17 14:20   ` [gentoo-user] " James

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=EAAC2AAD-547F-4FBA-BFF6-9E083ED4D553@alectenharmsel.com \
    --to=alec@alectenharmsel.com \
    --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