From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] grub-probefs --root-device
Date: Sat, 23 Sep 2006 05:20:37 +0200 [thread overview]
Message-ID: <200609230520.37732.okuji@enbug.org> (raw)
In-Reply-To: <20060922163313.GA29160@khazad.dyndns.org>
On Friday 22 September 2006 18:33, Robert Millan wrote:
> This would be very useful to get rid of ugly kludges in Debian, such as
> this one:
>
> http://svn.debian.org/wsvn/pkg-grub/grub2/trunk/debian/update-grub?op=file&
>rev=0&sc=0 (look for convert() here)
>
> Fortunately grub-probefs is already doing what we need, we just need a way
> to tell it to print the information.
However, this usage is against the original meaning, thus the naming is not
appropriate any longer. In addition, I don't like that we make an ad-hoc text
output (the first line is a fs module name, the second line is a root device
name, etc.).
So I propose that we rename the utility to "grub-probe" and add some options
to change the target of grub-probe. The default should be probing a fs to
help people who are used to grub-probefs. Here is an example:
$ grub-probe --target=fs
ufs
$ grub-probe
ufs
$ grub-probe --target=drive
(hd0,1)
$ grub-probe --target=device
/dev/hda1
What do you think?
Okuji
next prev parent reply other threads:[~2006-09-23 3:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 16:33 [PATCH] grub-probefs --root-device Robert Millan
2006-09-22 21:12 ` Robert Millan
2006-09-23 3:20 ` Yoshinori K. Okuji [this message]
2006-09-23 7:26 ` Robert Millan
2006-09-23 8:37 ` Robert Millan
2006-09-25 10:09 ` Robert Millan
2006-09-26 2:42 ` grub 2 on debian amd64 Colin Lamarre
2006-09-26 2:53 ` Hollis Blanchard
2006-09-26 16:32 ` Robert Millan
2006-09-26 17:29 ` [PATCH] grub-probefs --root-device Vesa Jääskeläinen
2006-09-28 14:39 ` Robert Millan
2006-10-01 19:27 ` Robert Millan
2006-10-14 10:06 ` ping (Re: [PATCH] grub-probefs --root-device) Robert Millan
2006-10-14 10:10 ` Yoshinori K. Okuji
2006-10-14 19:04 ` Robert Millan
2006-10-14 19:11 ` 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=200609230520.37732.okuji@enbug.org \
--to=okuji@enbug.org \
--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.