grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrei Borzenkov <arvidjaar@gmail.com>
To: grub-devel@gnu.org
Subject: Re: grub_machine_get_bootlocation and partitions
Date: Sat, 5 Dec 2015 09:37:12 +0300	[thread overview]
Message-ID: <56628618.8030906@gmail.com> (raw)
In-Reply-To: <CAEaD8JPAeGpti=pbaeX+8pbGyA6vmZ43j=gN9z7jEqryagGa7A@mail.gmail.com>

01.12.2015 20:45, Vladimir 'phcoder' Serbinenko пишет:
> Do you have a failure scenario? hd0,1 is not recommended but it's still
> valid and so should still work

Yes, I misunderstood what I have seen. Sorry.

> Le 1 déc. 2015 5:19 PM, "Andrei Borzenkov" <arvidjaar@gmail.com> a écrit :
> 
>> If partition information is actually present, it results in bogus and
>> invalid device name like
>>
>> hd0,1
>>
>> This device cannot be opened as it requires partmap name.
>>
>> One obvious case when partition *is* passed to GRUB is multiboot. I
>> suppose nobody ever noticed it because standard grub-install generates
>> fixed partition part.
>>
>> We probably can fallback to probing partmap on current level in this
>> case, except it means more code again. But current situation is rather
>> useless as is.
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
>>
> 
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



      reply	other threads:[~2015-12-05  6:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-01 16:18 grub_machine_get_bootlocation and partitions Andrei Borzenkov
2015-12-01 17:45 ` Vladimir 'phcoder' Serbinenko
2015-12-05  6:37   ` Andrei Borzenkov [this message]

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=56628618.8030906@gmail.com \
    --to=arvidjaar@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).