From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Q4kfd-0008EM-BU for mharc-grub-devel@gnu.org; Tue, 29 Mar 2011 21:58:05 -0400 Received: from [140.186.70.92] (port=43293 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Q4kfb-0008AC-8r for grub-devel@gnu.org; Tue, 29 Mar 2011 21:58:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Q4kfa-0000xF-4N for grub-devel@gnu.org; Tue, 29 Mar 2011 21:58:03 -0400 Received: from mail-yw0-f41.google.com ([209.85.213.41]:37812) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Q4kfa-0000x7-1x for grub-devel@gnu.org; Tue, 29 Mar 2011 21:58:02 -0400 Received: by yws5 with SMTP id 5so397649yws.0 for ; Tue, 29 Mar 2011 18:58:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RmbQOrNN4M0kUD0gVqG3Mc3F+4JSbf0TrtTxY0qoP+0=; b=Kh8dj8vGD8xWya4cDdZKej5BenO7Xh5JEbT3bLwi3EsmEOHgjsCeqwCC7mCJ46ex5y Ec+EySXjCHt0hqdshFbVIhbg6NBercVVe09p9mIDvvySgZYaPeVBmrQo+F9WEMm3gek5 7EaFCcpf9un5p3q9UauYHrFKjRl8NinKF4/wg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; b=SP/ycSmqc1D9azbWoiKfBaXVioXR2cZc+2p5ABHi+HuFk9qS+9w61qSSBSvnVogupO DIP++IXQxKEhteY/24RoxKA5K0630vxzEgGww2hyCG0cgmscfGvHiQ4j89uSDBcT1J4/ hBQUCKQiTJkSSPM5ONAajBfO/K6981uYn+Bbk= Received: by 10.236.180.232 with SMTP id j68mr836229yhm.353.1301450281158; Tue, 29 Mar 2011 18:58:01 -0700 (PDT) Received: from [192.168.0.75] (cpe-72-181-111-242.satx.res.rr.com [72.181.111.242]) by mx.google.com with ESMTPS id h59sm2792794yhm.99.2011.03.29.18.58.00 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 29 Mar 2011 18:58:00 -0700 (PDT) Message-ID: <4D928E27.9040804@gmail.com> Date: Tue, 29 Mar 2011 20:57:59 -0500 From: Bruce Dubbs User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.16) Gecko/20080722 SeaMonkey/1.1.11 MIME-Version: 1.0 To: The development of GNU GRUB References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 2) X-Received-From: 209.85.213.41 Subject: Re: Full documentation for GRUB2 X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Mar 2011 01:58:04 -0000 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