public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Peter Humphrey <peter@prh.myzen.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] grub-0.97-r16 and profile 17.0 change
Date: Thu, 07 Dec 2017 14:22:30 +0000	[thread overview]
Message-ID: <2039504.HaU7QUVC4l@peak> (raw)
In-Reply-To: <ecdf2071574f873405215ad3d11019e7@lists.gentoo.org>

On Thursday, 7 December 2017 12:04:08 GMT Kai Peter wrote:
> On 2017-12-06 13:28, Peter Humphrey wrote:
> > On Sunday, 3 December 2017 15:12:21 GMT Mick wrote:
> >> On 03-12-2017 ,10:57:33, Peter Humphrey wrote:

--->8

> > Sys-boot/grub-0.97-r17 compiled and installed all right, as a package,
> > but when I went to install it to the MBR I got an error complaining of a
> > mismatch or corruption in stage X. The wording was something like that,
> > and I forget the value of X. There was no mention of disk space, and the
> > boot partition is 2GB, so I think it's something else.
> > 
> > Installing sys-boot/grub-static-0.97-r12 instead went smoothly, so I've
> > left it like that for the moment.
> > 
> > Does the team think I should go back to grub-0.97-r17, take proper
> > records and file a bug report?
> 
> I question if this makes sense for a masked ebuild.

Masked? Not here, it isn't.

> I'm curious about what was discussed until now. The issue seems to be
> quite simple to solve.
> 
> The build fails but portage/gcc does give clear info in this case: the
> option "-nopie" have to be changed to "-no-pie". This option is set in
> 860_all_grub-0.97-pie.patch. Here is a diff:

--->8

Yes, this has been made clear already, but it's not the problem I had.

> Maybe the easiest way is to create a new grub-patches package, but there
> are other ways to change this too. I'm expected the upstream will change
> this soon - within the remaining 5 weeks ;-).
> 
> Another thing is I question that grub-legacy have to be rebuild at all.
> I'm pretty sure it is save to remove it from the world file or comment
> it out.

Then the first emerge -c will remove it from the system.

> Anyhow, upgrading to grub2 is IMHO the right way. There are some
> examples given in parallel threads how to write a grub.cfg by hand - and
> keep it simple :-). Then nothing else then the grub2 binary and
> grub2-install is required usually.

Long-standing readers may remember that I have reasons for avoiding grub-2. 
I still think it's a monstrosity and I'd much prefer never to have to 
wrestle with it again.

On the other hand, I suppose I could have another go at writing my own 
grub.cfg, just for the one little Atom box, if only for a quiet life.

-- 
Regards,
Peter.



  reply	other threads:[~2017-12-07 14:22 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-02 12:30 [gentoo-user] grub-0.97-r16 and profile 17.0 change Mick
2017-12-02 21:28 ` [gentoo-user] " Ian Zimmerman
2017-12-02 23:28   ` Mick
2017-12-03  2:11     ` Adam Carter
2017-12-02 23:33   ` Michael Orlitzky
2017-12-03  1:07     ` Heiko Baums
2017-12-03  1:14       ` Michael Orlitzky
2017-12-03  2:18         ` Ian Zimmerman
2017-12-03  2:27           ` Michael Orlitzky
2017-12-03 10:57 ` [gentoo-user] " Peter Humphrey
2017-12-03 15:12   ` Mick
2017-12-05  1:54     ` Daniel Frey
2017-12-05  2:13       ` Daniel Frey
2017-12-05  2:15         ` Michael Orlitzky
2017-12-05  3:39           ` Daniel Frey
2017-12-05 10:15             ` Peter Humphrey
2017-12-05 10:44             ` Tom H
2017-12-05  7:06         ` [gentoo-user] " Ian Zimmerman
2017-12-05  2:20       ` [gentoo-user] " wabe
2017-12-05 10:11         ` Mick
2017-12-05 10:21           ` Raffaele Belardi
2017-12-05 12:48             ` Mick
2017-12-06  1:58           ` wabe
2017-12-06 12:28     ` Peter Humphrey
2017-12-07 12:04       ` Kai Peter
2017-12-07 14:22         ` Peter Humphrey [this message]
2017-12-07 15:06           ` Helmut Jarausch
2017-12-07 16:51           ` Kai Peter

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=2039504.HaU7QUVC4l@peak \
    --to=peter@prh.myzen.co.uk \
    --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