public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: "mike@trausch.us" <mike@trausch.us>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] grub vs grub2
Date: Tue, 14 Feb 2012 15:44:42 -0500	[thread overview]
Message-ID: <4F3AC7BA.4000500@trausch.us> (raw)
In-Reply-To: <CAL3tS1a0gsAvVDvF_ZFR5g1A_mYYUsA1rHOFvH4Hh6NAu56b-Q@mail.gmail.com>

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

On 02/14/2012 02:59 PM, Michael Cook wrote:
> You can't edit /etc/default/grub to customize how grub-mkconfig
> generates grub.cfg. Mint probably has update-grub like Ubuntu does which
> just allows you to use that command instead of grub2-mkconfig -o
> /boot/grub/grub.cfg

grub-mkconfig (grub2-mkconfig in Gentoo) uses the scripts in /etc/grub.d
to generate the configuration file.  It runs them in sequential order.
You can add, remove or rename the scripts in order to have them do what
you want.

You can also edit the 40_custom file, which will insert its contents
verbatim (sans its shebang and exec lines) into the configuration file
when grub(2)-mkconfig is run.

For the paranoid, you can put a failsafe boot option in that file.

	--- Mike

-- 
A man who reasons deliberately, manages it better after studying Logic
than he could before, if he is sincere about it and has common sense.
                                   --- Carveth Read, “Logic”


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 729 bytes --]

  reply	other threads:[~2012-02-14 20:50 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-14 17:36 [gentoo-user] grub vs grub 2 james
2012-02-14 17:53 ` Florian Philipp
2012-02-14 18:08   ` LK
2012-02-14 18:24     ` mike
2012-02-14 18:40       ` LK
2012-02-14 18:46         ` Alecks Gates
2012-02-14 18:52         ` mike
2012-02-14 19:04           ` Michael Mol
2012-02-14 20:35             ` mike
2012-02-14 20:45               ` Michael Mol
2012-02-14 23:47           ` Paul Hartman
2012-02-14 23:53             ` mike
2012-02-14 19:29         ` Andrea Conti
2012-02-14 19:53           ` [gentoo-user] grub vs grub2 LK
2012-02-14 19:59             ` Michael Cook
2012-02-14 20:44               ` mike [this message]
2012-02-14 20:58                 ` LK
2012-02-14 21:19                   ` Michael Mol
2012-02-14 20:30             ` Alex Schuster
2012-02-14 20:46             ` mike
2012-02-14 20:42           ` [gentoo-user] grub vs grub 2 mike
2012-02-14 20:57             ` LK
2012-02-14 21:44               ` Neil Bothwick
2012-02-14 23:19               ` mike
2012-02-15 12:19                 ` Tanstaafl
2012-02-15 12:28                   ` Neil Bothwick
2012-02-15 12:33                   ` Michael Mol
2012-02-15 14:37                   ` mike
2012-02-15 14:47                     ` Tanstaafl
2012-02-15 15:02                       ` Neil Bothwick
2012-02-14 21:46           ` Neil Bothwick
2012-02-15 15:57             ` [gentoo-user] " James
2012-02-15 16:11               ` Neil Bothwick
2012-02-15 16:28                 ` Claudio Roberto França Pereira
2012-02-15 17:17                   ` Paul Hartman
2012-02-15 17:33                 ` Doug Hunley
2012-02-15 17:40                   ` Neil Bothwick
2012-02-15  8:10           ` [gentoo-user] " ny6p01
2012-02-14 20:57   ` [gentoo-user] " James
2012-02-14 18:07 ` [gentoo-user] " Stefano Crocco

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=4F3AC7BA.4000500@trausch.us \
    --to=mike@trausch.us \
    --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