All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Full documentation for GRUB2
Date: Tue, 29 Mar 2011 20:57:59 -0500	[thread overview]
Message-ID: <4D928E27.9040804@gmail.com> (raw)
In-Reply-To: <B6.07.09483.EC4829D4@cdptpa-omtalb.mail.rr.com>

Leslie Rhorer wrote:

> 	I sympathize, but only to a point.  No matter how dreary or how
> daunting the volume of work, it is essential it be done.

I agree.  I looked into helping do some of the documentation, but found 
that I just did not know enough of the internals to properly do it.

> 	I think a good example of this is the sort order of the items in the
> boot list.  Under GRUB legacy, editing the menu list order was quite simple.
> I did some significant searching to try to find a way to do this with GRUB
> 2, but as far as I was able to determine, there is no way to do it.

There is a way.  Use emacs or vim.  There is nothing that demands you 
use grub-mkconfig.  It is fine for someone who uses a distribution and 
knows very little about the internals, but in my opinion, it just gets 
in the way of knowledgeable users.

>>> I'd like to contribute examples that I found to the grub docs, but the
>>> manual gives no hint how to do so... ;-)
>> Send patches against docs/grub.texi in GRUB trunk.  If that's too hard,
>> send plain-text suggestions and somebody can deal with marking them up.

> 	Well, I might also like to contribute in some way, but speaking for
> myself, I don't even know where to start.  Knowing where and how to submit
> documentation is not really the starting point.  First one must know what
> GRUB can do and how one can make it do it.  For those of us who did not
> develop GRUB 2, it's rather a chicken and egg problem.

I agree.  About the only was is to study the source and look at other 
(e.g. Multiboot) documentation.  Unfortunately the source is really hard 
for a newbie to follow.  You really have to understand the intricacies 
of a lot of different systems.  I understand what's needed for the PC 
for DOS and Linux, but get lost in all the other file systems and BIOS 
issues.

   -- Bruce



  parent reply	other threads:[~2011-03-30  1:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-24 15:06 Full documentation for GRUB2 Treutwein Bernhard
2011-03-24 18:32 ` kf
2011-03-26  7:03 ` Jordan Uggla
2011-03-29 15:19 ` Patrick Strasser
2011-03-29 15:58   ` Chris Murphy
2011-03-31  6:19     ` Bruce Dubbs
2011-03-31  9:20     ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-03-29 17:09   ` Colin Watson
2011-03-30  1:18     ` Leslie Rhorer
2011-03-30  1:28       ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-03-30  1:57       ` Bruce Dubbs [this message]
2011-03-30  2:01       ` Isaac Dupree
2011-03-30  2:25       ` Colin Watson
2011-03-31  1:15         ` Leslie Rhorer
2011-03-31  7:51           ` Colin Watson
2011-03-31 13:59             ` richardvoigt
2011-03-31 14:24               ` Colin Watson
2011-04-01 10:42             ` Robert Wolf
2011-04-06 14:12               ` Treutwein Bernhard
2011-03-31  8:39           ` Isaac Dupree
2011-03-31  8:58             ` Vladimir 'φ-coder/phcoder' Serbinenko
2011-03-31 10:21             ` Colin Watson
2011-03-31 11:22     ` Patrick Strasser
     [not found] <239CEBDEE83EB949A48B6DB812AA19F60124B386@ex2.zuv.uni-muenchen.de>
2011-04-08  9:21 ` Treutwein Bernhard

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=4D928E27.9040804@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.