public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ian Bloss <ianlinkcd@gmail.com>
To: Gentoo mailing list <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Human configurable boot loader, OR useful grub2 documentation
Date: Tue, 9 Jul 2019 00:30:22 -0400	[thread overview]
Message-ID: <CADopNUdrdL7CO=KX=-p0sJbdLGz4WzUxFkfeswsfp6H_M=8OzA@mail.gmail.com> (raw)
In-Reply-To: <Lj-jC9o--3-1@tutanota.com>

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

Check out syslinux if grub is too obnoxious. I've found it much more
straight forward than grub.

On Fri, Jul 5, 2019, 2:05 AM <mad.scientist.at.large@tutanota.com> wrote:

> So, is there either a boot loader that a human can configure manually that
> can handle LUKS partitions?  No uefi, but GPT would be nice.  The grub2
> "documentation"  Reads like someone in the later stages of alzheimers'
> trying to tell you how to get to the moon from scratch?  The grub "legacy"
> manual was at least usefull, the grub2 manual is incoherent and has no
> logical structure or explanations in it.  It's insane that a boot loader
> takes 60 pages to document without actually explaning itself, barely useful
> as a reference IF you new it anyway.
>
> Grub2 produces insanely huge configuration files, stuffed with
> conditionals.  It's obvious even the automatic tools don't know how to
> configure it, It can't figure out how to boot redcore, on the same drive
> though it thinks it can.  It thinks you might want to try one version of
> linux with the ram disk and kernel from another, which doesn't work very
> well and WHY?
>
> any links to sane documentation or  sane bootloaders greatly appreciated,
> it'll be months before i can work on my own bootloader or extend one that
> makes sense out side of a corporate server farm or randomly assorted
> desktops that have to all work with the same config file (possibly because
> grub2 is deciding how to work every time it loads).
>
> Yeah, I hate grub2.  I"m very willing to learn gentoo,  but it does make
> some sense and there are articles that actually explain things online.  I
> can't find anything usefull about grub2 other than "DON'T MANUALLY EDIT
> THIS FILE", if it's not human editable and understandable why even bother
> to have it in human readable text?
>
>
> "Would you like to see us rule again, my friend?   All you have to do is
> follow the worms."  Pink Floyd, The Wall, Waiting for the worms
>

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

      parent reply	other threads:[~2019-07-09  4:30 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
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 [this message]

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='CADopNUdrdL7CO=KX=-p0sJbdLGz4WzUxFkfeswsfp6H_M=8OzA@mail.gmail.com' \
    --to=ianlinkcd@gmail.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