public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Grant Taylor <gtaylor@gentoo.tnetconsulting.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Human configurable boot loader, OR useful grub2 documentation
Date: Fri, 5 Jul 2019 14:56:45 -0600	[thread overview]
Message-ID: <0a87881f-1d15-b082-b4a2-bc5e7c690ba0@spamtrap.tnetconsulting.net> (raw)
In-Reply-To: <20190705205754.4757190d@digimed.co.uk>

On 7/5/19 1:57 PM, Neil Bothwick wrote:
> In the case of GRUB2 that is unlikely to be the case, as it is meant 
> to do everything. That's why the auto-generated config files are so 
> long and full of conditionals. On a system you have full control over, 
> you can remove all the conditionals.

I had grub-mkconfig puke on me recently.  I've not spent time diagnosing 
why.

/boot was a local disk (/dev/sda1) per Gentoo install documents.

/ (root) was special in that it was /dev/nfs.

Grub (grub-mkconfig) tossed it's salad, saying:

/usr/sbin/grub-probe: error: failed to get canonical path of 
'192.0.2.1:/export/hostname/root'

With a return code of 1.

> GRUB2 is incredibly bendy, if only the documentation were as compliant 
> to the wishes of its users,

Sometimes I wonder just how bendy it really is.



-- 
Grant. . . .
unix || die


  reply	other threads:[~2019-07-05 20:56 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-05  6:05 [gentoo-user] Human configurable boot loader, OR useful grub2 documentation mad.scientist.at.large
2019-07-05  7:18 ` Francesco Turco
2019-07-05  7:24   ` mad.scientist.at.large
2019-07-05  8:10     ` Mick
2019-07-05 14:04       ` Rich Freeman
2019-07-05 15:32         ` Grant Taylor
2019-07-05 19:57           ` Neil Bothwick
2019-07-05 20:56             ` Grant Taylor [this message]
2019-07-05 14:25   ` [gentoo-user] " Grant Edwards
2019-07-09  3:05     ` mad.scientist.at.large
2019-07-09 17:17     ` Ian Zimmerman
2019-07-09 19:53       ` Grant Edwards
2019-07-05  9:03 ` [gentoo-user] " Philip Webb
2019-07-09  4:30 ` Ian Bloss

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=0a87881f-1d15-b082-b4a2-bc5e7c690ba0@spamtrap.tnetconsulting.net \
    --to=gtaylor@gentoo.tnetconsulting.net \
    --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