From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Cc: Otavio Salvador <otavio@debian.org>
Subject: Re: Bug#461442: detection of other OSes in update-grub
Date: Tue, 22 Jan 2008 17:56:53 +0100 [thread overview]
Message-ID: <20080122165653.GB16578@thorin> (raw)
In-Reply-To: <4795EC4D.5020207@leat.rub.de>
On Tue, Jan 22, 2008 at 02:14:53PM +0100, Fabian Greffrath wrote:
>
> We should stay with the '-t drive' option to print the GRUB drive. If no
> further option is given, the next item on the command line is expected
> to be a path - just like before.
> Then, another option, e.g. '-o', should be introduced to specify the
> origin of the said item if it is different from "path", e.g.:
>
> $ grub-probe
> Usage: grub-probe [OPTION]... [ORIGIN]
>
> Probe device information for a given path or, if the -o option is given,
> for a given GRUB drive or system device.
>
> -m, --device-map=FILE use FILE as the device map
> [default=/boot/grub/device.map]
> -t, --target=(fs|drive|device|partmap|abstraction)
> print filesystem module, GRUB drive, system
> device, partition map module or abstraction module [default=fs]
> -o, --origin=(path|drive|device)
> expect to read from path, GRUB drive or
> system device [default=path]
> -h, --help display this message and exit
> -V, --version print version information and exit
> -v, --verbose print verbose messages
>
> This way it will be possible to even convert back and forth between GRUB
> drives and system devices.
> The conversion that is needed to translate os-prober output to GRUB menu
> input will read:
> GRUB_DEVICE="`grub-probe -t drive -o device ${PARTITION}`".
>
> Hope you like this proposal (of course, "origin" is subject to change;
> it's just the first word that came to my mind that might be fitting)!
This implies that we'll have to support 6 different kinds of conversions
between path, drive and device, some of which might even be impossible.
Besides, perhaps it'd be cleaner to split this conversion to a separate
tool, so that grub-probe only operates on devices, and the other tool
converts paths to devices (but NOT necessarily devices to paths!).
What does everyone think 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-01-22 16:58 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 [this message]
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
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=20080122165653.GB16578@thorin \
--to=rmh@aybabtu.com \
--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.