From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: 462218@bugs.debian.org, Otavio Salvador <otavio@debian.org>
Subject: Re: Bug#461442: detection of other OSes in update-grub
Date: Mon, 4 Feb 2008 16:04:00 +0100 [thread overview]
Message-ID: <20080204150400.GA12876@thorin> (raw)
In-Reply-To: <47A7257E.1090807@leat.rub.de>
On Mon, Feb 04, 2008 at 03:47:26PM +0100, Fabian Greffrath wrote:
> Robert Millan schrieb:
> >Why is that a problem?
> >
>
> Because foobar is not a block device, but grub-probe claims that it will
> print a device if '--target=device' is given.
Uhm I'm not sure if that's a good thing or may be overkill. What does everyone
else think about this?
> >I know that the call to probe() is not supposed to be reentrant, but I'd
> >prefer not to break reentrancy if it can be easily avoided; it is possible
> >that probe() needs to recurse onto itself in the future (because of
> >RAID/LVM).
> >
>
> OK, but should I keep it uninitialized?
Depends on what you want to do ;-)
> >Is it possible to share code with 10_linux.in here?
> >
>
> Only if os-prober is installed. But then, os-prober does not check for
> kernels on / and /target.
What I mean is that 10_linux.in already has code that probes for stuff like
Linux images and initrd files, and it might be a good idea to use the same
logic.
Or does os-prober provide any additional feature/knowledge about this?
--
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-02-04 15:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4790C888.6040007@leat.rub.de>
[not found] ` <87sl0v6iod.fsf@ossystems.com.br>
[not found] ` <20080119114939.GB10722@thorin>
[not found] ` <479450A9.90601@leat.rub.de>
[not found] ` <20080121112448.GD7378@thorin>
[not found] ` <47948422.8000208@leat.rub.de>
[not found] ` <20080121121828.GA9244@thorin>
[not found] ` <4795B435.20102@leat.rub.de>
[not found] ` <20080122124642.GC2017@thorin>
2008-01-22 13:14 ` Bug#461442: detection of other OSes in update-grub Fabian Greffrath
2008-01-22 16:56 ` Robert Millan
2008-01-30 10:41 ` Fabian Greffrath
2008-01-30 19:48 ` Robert Millan
2008-01-31 8:31 ` Fabian Greffrath
2008-01-31 10:10 ` Otavio Salvador
2008-01-31 11:58 ` Robert Millan
2008-01-31 14:26 ` Fabian Greffrath
2008-01-31 14:39 ` Robert Millan
2008-02-04 8:43 ` Fabian Greffrath
2008-02-04 14:18 ` Robert Millan
2008-02-04 14:47 ` Fabian Greffrath
2008-02-04 15:04 ` Robert Millan [this message]
2008-02-04 15:27 ` Marco Gerards
2008-02-06 10:12 Fabian Greffrath
2008-02-06 12:02 ` 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=20080204150400.GA12876@thorin \
--to=rmh@aybabtu.com \
--cc=462218@bugs.debian.org \
--cc=grub-devel@gnu.org \
--cc=otavio@debian.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.