From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] register dummy drive
Date: Tue, 03 Jun 2008 18:03:51 -0400 [thread overview]
Message-ID: <1212530631.11375.4.camel@dv> (raw)
In-Reply-To: <20080603211257.GB10712@thorin>
On Tue, 2008-06-03 at 23:12 +0200, Robert Millan wrote:
> On Mon, Jun 02, 2008 at 10:11:50AM -0400, Pavel Roskin wrote:
> > On Mon, 2008-06-02 at 15:50 +0200, Robert Millan wrote:
> > > There's no reason grub-probe should fail if it can't resolve drive, when we
> > > just asked for -t fs, -t fs_uuid or -t partmap.
> > >
> > > This patch solves the problem by spliting device/drive map[] entry registration
> > > into a separate function, and using that from grub-probe.c to register a dummy
> > > drive that will last during the current execution.
> >
> > Cannot hostfs be used by default for all userspace utilities?
>
> Part of what makes grub-probe interesting is that it shares a lot of code with
> the freestanding GRUB you will run later, so when it is used during
> grub-install & update-grub, it is very useful to catch possible problems. I
> think hostfs would defeat that purpose.
Well, then we probably don't want to ignore any errors. When do you
have the situation that the drive cannot be resolved?
My concern is that introducing a dummy object for non-testing purposes
could indicate bad code quality.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2008-06-03 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-02 13:50 [PATCH] register dummy drive Robert Millan
2008-06-02 14:11 ` Pavel Roskin
2008-06-03 21:12 ` Robert Millan
2008-06-03 22:03 ` Pavel Roskin [this message]
2008-06-04 12:07 ` Robert Millan
2008-06-04 16:41 ` Pavel Roskin
2008-06-02 14:12 ` 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=1212530631.11375.4.camel@dv \
--to=proski@gnu.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.