public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Gilbert <floppym@gentoo.org>
To: Gentoo Dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] Documentation for sys-boot/grub:2
Date: Tue, 20 Mar 2012 12:07:28 -0400	[thread overview]
Message-ID: <CAJ0EP42rJCRNgiMxrQZnABAG+kvJCbAabaJYq5DuQZx1BGm5Xw@mail.gmail.com> (raw)

I believe the only thing keeping GRUB 2 masked is a lack of
"documentation". By this, I assume people are referring to the
handbook.

I have created a very minimal "quick start" guide that could be
adapted for the handbook. It relies on the grub2-mkconfig command
auto-detecting most things, which actually works pretty well.

http://wiki.gentoo.org/wiki/GRUB2_Quick_Start

scarabeus created a guide a while back that goes into slightly more detail:

http://dev.gentoo.org/~scarabeus/grub-2-guide.xml

The wiki also has a longer GRUB2 guide. This goes into some of the
more exotic setups. However, some of it is poorly written and I find
editing it quite tedious.

http://wiki.gentoo.org/wiki/GRUB2

So, my question to the community: what level of documentation do we
want to put in the handbook?

If the intent is just to get people up and running on Gentoo, I think
adapting the quick start guide from the wiki is enough. grub2.info has
a very detailed reference; I think we can refer people to that for
manual/advanced configuration.

Is there any other issue with grub:2 that would keep me from unmasking
(adding keywords) on x86 and amd64? I plan on waiting for the 2.00
release.



             reply	other threads:[~2012-03-20 16:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 16:07 Mike Gilbert [this message]
2012-03-20 19:31 ` [gentoo-dev] Documentation for sys-boot/grub:2 Maxim Kammerer
2012-03-20 21:34   ` [gentoo-dev] " Duncan
2012-03-20 21:44     ` Mike Gilbert
2012-03-21  1:08     ` Maxim Kammerer

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=CAJ0EP42rJCRNgiMxrQZnABAG+kvJCbAabaJYq5DuQZx1BGm5Xw@mail.gmail.com \
    --to=floppym@gentoo.org \
    --cc=gentoo-dev@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