All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabian Greffrath <greffrath@leat.rub.de>
To: Robert Millan <rmh@aybabtu.com>
Cc: The development of GRUB 2 <grub-devel@gnu.org>,
	462218@bugs.debian.org, Otavio Salvador <otavio@debian.org>
Subject: Re: Bug#461442: detection of other OSes in update-grub
Date: Mon, 04 Feb 2008 15:47:26 +0100	[thread overview]
Message-ID: <47A7257E.1090807@leat.rub.de> (raw)
In-Reply-To: <20080204141837.GB7432@thorin>

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.

> I think this function could be called from the other part of this file which
> performs similar checks (if this functionality is to be kept, that is).
>   

Yes, I am fine with 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?

> Please remember to fix that in later versions of the patch ;-)
>   

Sure, my copyright assignment paper is on it's way...

> 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.

> Maybe this can be simplified with "echo something | read a b c d" feature?
>   

For cosmetic reasons, yes. ;)

Cheers,
Fabian

-- 
Dipl.-Phys. Fabian Greffrath

Ruhr-Universität Bochum
Lehrstuhl für Energieanlagen und Energieprozesstechnik (LEAT)
Universitätsstr. 150, IB 3/134
D-44780 Bochum

Telefon: +49 (0)234 / 32-26334
Fax:     +49 (0)234 / 32-14227
E-Mail:  greffrath@leat.ruhr-uni-bochum.de




  reply	other threads:[~2008-02-04 14:47 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 [this message]
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=47A7257E.1090807@leat.rub.de \
    --to=greffrath@leat.rub.de \
    --cc=462218@bugs.debian.org \
    --cc=grub-devel@gnu.org \
    --cc=otavio@debian.org \
    --cc=rmh@aybabtu.com \
    /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.