From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: grub2 back to lilo ?
Date: Mon, 17 May 2010 13:23:52 +0200 [thread overview]
Message-ID: <4BF12748.3050803@gmail.com> (raw)
In-Reply-To: <20100517104030.GA6872@riva.ucam.org>
[-- Attachment #1: Type: text/plain, Size: 1073 bytes --]
Colin Watson wrote:
> On Sat, May 15, 2010 at 01:41:09PM +0530, BVK Chaitanya wrote:
>
>> On Sat, May 15, 2010 at 12:41 PM, Colin Watson <cjwatson@ubuntu.com> wrote:
>>
>>> On Sat, May 15, 2010 at 08:02:22AM +0530, BVK Chaitanya wrote:
>>>
>>>> With GRUB2 that simplicity is not there anymore.
>>>>
>>> Simplicity ... except when it broke. Which it did, all the time. Let's
>>> not follow the model of those marker comments!
>>>
>> Given the GRUB script capabilities, we can get this simply by adding
>>
>> include $prefix/custom.cfg
>>
>> or similar to grub.cfg.
>>
>
> I could support that. It might be simpler than expecting people to edit
> /etc/grub.d/40_custom and re-run update-grub.
>
>
This is a good and acceptable possibility. Just keep in mind that it has
to be
#!/bin/sh
echo <<EOF
if [ -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
EOF
If nobody opposes in one week I'll add 41_custom alongside 40_custom.
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 293 bytes --]
next prev parent reply other threads:[~2010-05-17 11:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 1:55 grub2 back to lilo ? bc w
2010-05-15 2:32 ` BVK Chaitanya
2010-05-15 7:11 ` Colin Watson
2010-05-15 7:21 ` Marc Haber
2010-05-15 7:41 ` Colin Watson
2010-05-15 8:47 ` Marc Haber
2010-05-15 8:11 ` BVK Chaitanya
2010-05-17 10:40 ` Colin Watson
2010-05-17 11:23 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-05-15 5:13 ` Colin D Bennett
2010-05-15 5:51 ` Bruce Dubbs
2010-05-15 12:07 ` Vladimir 'φ-coder/phcoder' Serbinenko
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=4BF12748.3050803@gmail.com \
--to=phcoder@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.