From: Andrey Borzenkov <arvidjaar@gmail.com>
To: zaphod@berentweb.com
Cc: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: PXE boot over NFS please
Date: Sat, 7 Jun 2014 11:24:32 +0400 [thread overview]
Message-ID: <20140607112432.4b230759@opensuse.site> (raw)
In-Reply-To: <CAPSTsktxqXEOmH_BB1gfX7gsZ4cqg6dP+7C66567X1U--NCkLQ@mail.gmail.com>
В Sat, 7 Jun 2014 09:15:51 +0300
Beeblebrox <zaphod@berentweb.com> пишет:
> >
> > Did you try pxechainloader instead? It should leave working PXE
> > environment.
> >
>
> Ah, very interesting. I have that file in the grub folder, but how / where
> is it invoked from? dhcp.conf has:
> {next-server 192.168.2.1;
> filename "grub/i386-pc/core.0";}
> You are NOT suggesting modification to this I presume?
>
> Therefore I should place it in grub.cfg? The below example did not work
> either unfortunately. It gets to the BTX loader but no PXE devices are
> available (same as before)
> menuentry 'FreeBSD amd64' --class freebsd --class bsd --class os {
> insmod pxe
It should already be present in a grub core image built for PXE.
> insmod pxechainloader
This by itself does nothing; pxechainloader is a command. This is
mostly the same as using chainloader but keeping PXE stack alive.
> kfreebsd loader
> kfreebsd_loadenv device.hints }
>
What I mean, use "pxechainloader /your/freebsd/PXE-aware/bootloader".
Probably "pxechainloader ${path_to}/boot/pxeboot". I do not know how
*BSD bootloaders work, sorry.
next prev parent reply other threads:[~2014-06-07 7:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-01 17:53 PXE boot over NFS please Beeblebrox
2014-06-02 5:15 ` Andrey Borzenkov
2014-06-02 5:35 ` Beeblebrox
2014-06-02 6:12 ` arvidjaar
2014-06-02 15:14 ` Beeblebrox
2014-06-02 15:50 ` Andrey Borzenkov
2014-06-02 17:36 ` Beeblebrox
2014-06-06 12:11 ` Beeblebrox
2014-06-07 4:59 ` Andrey Borzenkov
2014-06-07 6:15 ` Beeblebrox
2014-06-07 7:24 ` Andrey Borzenkov [this message]
2014-06-07 7:33 ` Beeblebrox
2014-06-08 5:23 ` Andrey Borzenkov
2014-06-09 4:55 ` Beeblebrox
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=20140607112432.4b230759@opensuse.site \
--to=arvidjaar@gmail.com \
--cc=grub-devel@gnu.org \
--cc=zaphod@berentweb.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.