All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Steven Maresca <steve.maresca@gmail.com>
Cc: xen-devel@lists.xensource.com
Subject: Re: PV-Grub and PXE
Date: Wed, 15 Jul 2009 22:13:43 -0400	[thread overview]
Message-ID: <20090716021343.GB10581@const> (raw)
In-Reply-To: <7e9718f20907151852r210ef8cbs180cd5b5b7947da6@mail.gmail.com>

Steven Maresca, le Wed 15 Jul 2009 21:52:40 -0400, a écrit :
> For PV, we can cheat and skip most of that pain. In my mind - and as
> you suggested - that means just parsing PXE configurations.
> 
> For the most basic case, all we need is:
> 1) access to the network device
> 2) ability to pull a lease from dhcp (with next-server and filename options set)
> 3) tftp to $next-server to grab not the pxelinux.0 binary (or its
> equivalent) but the configuration alone
> 4) mechanism for presenting the configuration and emulating the (text) menu
> 5) acting upon the choice

Yes, that's the kind of things I was thinking about.

> Assumption: no more graphical menu is employed.

Not necessarily, grub's graphical menu is just a graphical rendering of
the text menu, it's basically the same content.

> Please note: I'm not necessarily advocating that pv-grub should be
> bent and twisted to this task, though that was the topic that led us
> to this discussion.

I think it could still be done that way: there could be a pxelinux.cfg
to menu.lst converter and pv-grub can be fed with it.

Samuel

      reply	other threads:[~2009-07-16  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7e9718f20907150839h1e194bc0wd3741c66824727a1@mail.gmail.com>
     [not found] ` <20090715173604.GE4903@const.linuxsymposium.org>
     [not found]   ` <7e9718f20907151133r3469f3cjde86cd45f4fb65fe@mail.gmail.com>
2009-07-15 22:33     ` PV-Grub and PXE Samuel Thibault
2009-07-16  1:52       ` Steven Maresca
2009-07-16  2:13         ` Samuel Thibault [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=20090716021343.GB10581@const \
    --to=samuel.thibault@ens-lyon.org \
    --cc=steve.maresca@gmail.com \
    --cc=xen-devel@lists.xensource.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.