From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: grub-devel@gnu.org
Subject: Re: Chain-booting PXE bootloaders
Date: Fri, 27 Aug 2010 01:21:56 +0200 [thread overview]
Message-ID: <4C76F714.902@gmail.com> (raw)
In-Reply-To: <D1A3B6E525F5F943AB9D12DED819DD5F013EAFB5@NYCMBX3.winmail.deshaw.com>
[-- Attachment #1: Type: text/plain, Size: 1212 bytes --]
On 08/27/2010 01:04 AM, Turner, Ian wrote:
> Hello all,
>
> We're trying to chainload PXE bootloaders. This is required in order to netboot Windows or DOS, and is also useful for Solaris jumpstart builds.
It's not supported because of a priori no clear benefits present.
@Seth can you comment on Solaris part?
DOS is best loaded using grub+memdisk (later one is a helper available
from syslinux pages).
Could you detail the windows part?
> Is this feature supported by GRUB? Simply running the following command line causes GRUB to read the configuration file the TFTP server, then either hang or reboot:
>
> chainloader --force /path/to/pxelinux.0
>
Usually if someone tells you "wrong signature" it may mean something...
--force was added because of now dead SCO (now Tarantella, don't confuse
with Litigious Bastards) Unix. Removing it may create some hassle if
someone uses it so it's kept.
> boot
>
> Thanks in advance for your thoughts.
>
> --Ian Turner
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> http://lists.gnu.org/mailman/listinfo/grub-devel
>
>
--
Regards
Vladimir 'φ-coder/phcoder' Serbinenko
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 294 bytes --]
next prev parent reply other threads:[~2010-08-26 23:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-26 23:04 Chain-booting PXE bootloaders Turner, Ian
2010-08-26 23:21 ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]
2010-08-26 23:51 ` Turner, Ian
2010-08-27 0:08 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-08-27 18:28 ` Turner, Ian
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=4C76F714.902@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.