All of lore.kernel.org
 help / color / mirror / Atom feed
From: phcoder <phcoder@gmail.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [RFC] Boot parameters and geometrical stability
Date: Thu, 04 Sep 2008 23:37:43 +0200	[thread overview]
Message-ID: <48C05527.1020903@gmail.com> (raw)
In-Reply-To: <20080904193347.GD9133@thorin>

Robert Millan wrote:
> On Wed, Sep 03, 2008 at 02:31:10PM +0200, phcoder wrote:
>>> I assume you talk about GRUB loading itself;  what kind of information would
>>> you pass from one GRUB to the other?
>> Boot device,
> 
> Multiboot already handles that (although it's not reliable; I don't
> think this feature should be used anyway).
> 
Feature in multiboot is hmm..: it gives bios device and grub supports
also other devices.
>> configuration file, parameters for scripts.
> 
> This assumes the loader knows more than the loadee about this information.
> In which situation would this happen?  Note that both loader and loadee can
> obtain user input.
> 
> Which parameters do you have in mind?
> 
I thought of it more like about instruction like: boot from strange
place or enter debug mode in early stage.
>> But much more
>> useful this is for network boot. In this case GRUB can recieve server
>> info in boot parameters so when this info changes there is no need to
>> regenerate grub images.
> 
> Doesn't PXE already handle this?
> 
I'm not really familiar with it. Does it support multiple servers. If
let's say we have multiple menus like:
<load linux from server1 (normal copy)>
<load linux from server2 (experimental copy)>
<load freebsd from server3>
Then having recieved names of servers as parameters could sometimes be a
good thing. But still for me this feature is just an idea. I'm still not
persuaded myself whether it's needed.
Vladimir 'phcoder' Serbinenko



  reply	other threads:[~2008-09-04 21:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-03  9:50 [RFC] Boot parameters and geometrical stability phcoder
2008-09-03 10:36 ` Robert Millan
2008-09-03 12:31   ` phcoder
2008-09-03 16:51     ` Vesa Jääskeläinen
2008-09-03 17:17       ` phcoder
2008-09-03 17:49         ` Vesa Jääskeläinen
2008-09-03 18:36           ` phcoder
2008-09-03 19:07             ` Vesa Jääskeläinen
2008-09-03 19:23               ` phcoder
2008-09-04 19:37           ` Robert Millan
2008-09-04 21:40             ` phcoder
2008-09-05  9:58               ` Robert Millan
2008-09-04 19:33     ` Robert Millan
2008-09-04 21:37       ` phcoder [this message]
2008-09-05 10:05         ` 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=48C05527.1020903@gmail.com \
    --to=phcoder@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 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.