Hi.
It looks like a PR was in fact filed: https://savannah.gnu.org/bugs/?41447
Is there anything I should add to it? Seems prety complete.
Before my other reported problem, I had gotten FreeBSD to boot with this
entry. If I can figure out how to load kernel module from grub, I won't
need to
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
В Sat, 7 Jun 2014 09:15:51 +0300
Beeblebrox zap...@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;
I was just preparing this email when yours arrived.
The example below does not work either - client just reboots.
The module in my grub/i386-pc folder is named pxechain, so I have corrected
the insmod to that.
menuentry 'FreeBSD amd64' --class freebsd --class bsd --class os {
insmod pxechain
В Sat, 7 Jun 2014 10:33:29 +0300
Beeblebrox zap...@berentweb.com пишет:
I was just preparing this email when yours arrived.
The example below does not work either - client just reboots.
The module in my grub/i386-pc folder is named pxechain, so I have corrected
the insmod to that.
I must also boot FreeBSD on NFS via TFTP (not HTTP), but this won't work:
menuentry 'FreeBSD chainload BTX' {
kfreebsd boot/loader
or kfreebsd boot/pxeboot }
This is because the BTX loader has not been booted in PXE mode and has no
record of available PXE devices. Booting into
В Fri, 6 Jun 2014 15:11:22 +0300
Beeblebrox zap...@berentweb.com пишет:
I must also boot FreeBSD on NFS via TFTP (not HTTP), but this won't work:
menuentry 'FreeBSD chainload BTX' {
kfreebsd boot/loader
or kfreebsd boot/pxeboot }
This is because the BTX loader has not
Отправлено с iPhone
02 июня 2014 г., в 9:35, Beeblebrox zap...@berentweb.com написал(а):
Hello Andrey,
The linked article, under the Advanced Options title (just past middle of
page) covers two interesting aspects of non-tftp transfer alternatives.
One is Faster Transfers With HTTP,
Hello.
It seems I misunderstood the article I had referenced. I emailed the author
of that article for clarification and his response (partially) is below. My
apologies to the members of the list for this mistake I have made.
Actually, the kernel there is being loaded by TFTP, although HTTP can
В Mon, 2 Jun 2014 18:14:31 +0300
Beeblebrox zap...@berentweb.com пишет:
Grub already supports HTTP. Did you try it?
Not yet. I was planning on getting around to that, but I had wanted to
clarify the NFS option first. Can you advise what the syntax is for HTTP
booting the kernel with
set root=http,192.168.2.1
loopback loop0 ($root)/tftp/$isofile
Thank you - that was very useful and solves the iso-boot problem.
I must also boot FreeBSD on NFS via TFTP (not HTTP), but this won't work:
menuentry 'FreeBSD chainload BTX' {
kfreebsd boot/loader }
It's probably
В Sun, 1 Jun 2014 20:53:27 +0300
Beeblebrox zap...@berentweb.com пишет:
In a previous discussion on this list, I was advised grub does not boot
over NFS, and that it must use TFTP only.
I had asked the questionn because of this article [
http://www.wonkity.com/~wblock/docs/html/pxe.html)
Hello Andrey,
The linked article, under the Advanced Options title (just past middle of
page) covers two interesting aspects of non-tftp transfer alternatives.
One is Faster Transfers With HTTP,
The other is NFS.
Neither method / description has anything to do with issue of mount_nfs
after the
13 matches
Mail list logo
