All of lore.kernel.org
 help / color / mirror / Atom feed
From: Colin D Bennett <colin@gibibit.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: neal@walfield.org
Subject: Re: customizing grub-mkrecue images
Date: Fri, 16 Jan 2009 20:51:45 -0800	[thread overview]
Message-ID: <20090116205145.4e3dbb03@gibibit.com> (raw)
In-Reply-To: <87fxji62u2.wl%neal@walfield.org>

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

On Sat, 17 Jan 2009 04:14:45 +0100
"Neal H. Walfield" <neal@walfield.org> wrote:

> Hi,
> 
> grub-mkrescue is quite useful, however, I'd like to be able to
> customize the image it creates a bit more than it currently supports.
> In particular, I'd like to load another config file at boot time.  The
> attached patch enables this by way of a new option, --configfile.
> 
> A more general solution to the customization problem would be to load
> a config file at image compilation time.  This could be used to solve
> my problem.  However, as it is an additional level of indirection,
> perhaps both options would be useful.
> 
> Thoughts?

You can already do this with the --overlay=DIR option.  I do this to
add fonts, images, and graphical menu themes to the resulting ISO image
in addition to my custom grub.cfg.

Your option --configfile option does make the case when you only want
to include your own grub.cfg file easier, by not requiring you to
create a directory hierarchy of DIR/boot/grub/ to contain grub.cfg
first.

Regards,
Colin

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-01-17  4:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-17  3:14 customizing grub-mkrecue images Neal H. Walfield
2009-01-17  4:51 ` Colin D Bennett [this message]
2009-02-07 21:16   ` Robert Millan

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=20090116205145.4e3dbb03@gibibit.com \
    --to=colin@gibibit.com \
    --cc=grub-devel@gnu.org \
    --cc=neal@walfield.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.