From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [NEW PATCH] Add option to grub-probe to accept system devices as arguments
Date: Mon, 3 Mar 2008 22:06:56 +0100 [thread overview]
Message-ID: <20080303210656.GD22431@thorin> (raw)
In-Reply-To: <47C7C349.6040303@leat.rub.de>
On Fri, Feb 29, 2008 at 09:33:13AM +0100, Fabian Greffrath wrote:
> >For this one, I think it'd be much better to rework 10_hurd so that code is
> >shared, rather than duplicating the whole blurb.
>
> Yes, we could source out the complete linux/hurd kernel-adding blurbs
> into an external shell library that is shared with 10_* and 30_os-prober.
>
> However, please don't forget these are two different things. 10_* look
> on / and /boot, while os-prober looks on all *other* partitions.
For 10_linux it isn't that important since the boot parameters are so small,
it's 10_hurd that has more reusable stuff (that big blurb).
> >Do you plan to do that later?
>
> Not a concrete plan yet, However, we should first get thinks *working*
> before we care about cosmetics, IMHO. ;)
In that case maybe it's better to leave Hurd support for later, than
duplicating the whole thing.
> >Maybe it's better to echo something here, otherwise it gives the impression
> >OS FooBar was just detected and properly added.
>
> Definitely. I'll add a short warning message.
>
> Furthermore, I am going to modify the script to immediately 'exit 0'
> if it turns out it misses the tools required to update the boot menu
> (i.e. os-prober, linux-boot-prober, grub-probe (>= 20080228)). These
> tests are spread all over the script at the moment.
Ok.
> PS: Shouldn't 30_os-prober be an upstream feature of os-prober?!
Not sure about that. My initial intention was that in general one could plug
in scripts from other system components, but often the code in them depends on
many update-grub interfaces which makes it likely to break if something is
changed.
For now only very simple add-ons exist (memtest86, invaders...). But this
one will probably end up being more intermangled with other GRUB parts (see
that we're already discussing how to reduce code duplication with 10_hurd).
I'd suggest putting it in GRUB, at least for now, if that is fine with you.
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-03-03 21:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 13:17 [PATCH] Add option to grub-probe to accept system devices as arguments Fabian Greffrath
2008-02-13 13:03 ` Fabian Greffrath
2008-02-13 15:42 ` Robert Millan
2008-02-13 16:51 ` Fabian Greffrath
2008-02-13 19:35 ` Robert Millan
2008-02-14 8:33 ` Fabian Greffrath
2008-02-17 13:42 ` Robert Millan
2008-02-18 12:54 ` Fabian Greffrath
2008-02-20 14:14 ` Fabian Greffrath
2008-02-22 14:32 ` [NEW PATCH] " Fabian Greffrath
2008-02-22 15:36 ` Fabian Greffrath
2008-02-24 15:22 ` Robert Millan
2008-02-25 9:49 ` Fabian Greffrath
2008-02-25 14:20 ` Robert Millan
2008-02-28 7:26 ` Fabian Greffrath
2008-02-28 10:10 ` Robert Millan
2008-02-28 10:28 ` Fabian Greffrath
2008-02-28 10:41 ` Robert Millan
2008-02-28 11:46 ` Fabian Greffrath
2008-02-28 17:07 ` Robert Millan
2008-02-29 8:33 ` Fabian Greffrath
2008-03-03 21:06 ` Robert Millan [this message]
2008-03-04 7:57 ` Fabian Greffrath
2008-03-05 12:27 ` [NEW PATCH] os-prober output parser Fabian Greffrath
2008-03-13 7:56 ` Fabian Greffrath
2008-03-19 14:38 ` Robert Millan
2008-03-19 15:18 ` Fabian Greffrath
2008-03-19 16:10 ` Robert Millan
2008-03-20 10:02 ` Fabian Greffrath
2008-03-20 10:36 ` Robert Millan
2008-03-25 7:27 ` Fabian Greffrath
2008-04-07 8:39 ` Fabian Greffrath
2008-04-09 8:32 ` Fabian Greffrath
2008-04-09 10:11 ` Robert Millan
2008-04-09 12:41 ` Fabian Greffrath
2008-04-13 10:52 ` Robert Millan
2008-04-14 11:11 ` Fabian Greffrath
2008-02-29 13:46 ` [NEW PATCH] Add option to grub-probe to accept system devices as arguments Fabian Greffrath
2008-03-03 20:58 ` Robert Millan
2008-02-24 15:23 ` 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=20080303210656.GD22431@thorin \
--to=rmh@aybabtu.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.