On 26.11.2013 12:26, Beeblebrox wrote: >>> This doesn't seem to be a GRUB problem at all. I use tftpd which serves > from /var/tftpd > You are right, it is not a GRUB problem; it's a folder structure error > in the way I approached the problem. > >>> boot/grub ($prefix) is where grub.cfg goes. Judging from your first >>> question, is it possible you serve from a different folder than you think >>> you do? > No, the dhcp-tftp chain is correct. Because /data/amd64 is a jail > (like a chroot) and the chroot is where dhcp and tftpd are running, I > thought maybe the correct sytax should be "grub-mknetdir > --net-directory=/ --subdir=boot/grub", then copy the files to > boot/grub under the chroot folder. No difference, however and client > drops to "grub rescue". /var/log/xferlog shows: > in.tftpd[41762]: RRQ from 192.168.2.34 filename i386-pc/core.0 > in.tftpd[41762]: tftp: client does not accept options > in.tftpd[41763]: RRQ from 192.168.2.34 filename i386-pc/core.0 > in.tftpd[41764]: RRQ from 192.168.2.34 filename /boot/grub/i386-pc/normal.mod > in.tftpd[41764]: sending NAK (1, File not found) to 192.168.2.34 > You misconfigured your server --net-directory is where root of tftp is. --subdir is subdirectory of it. Yet your server has root in /boot/grub and not subdirectory > grub rescue> set > cmdpath=(tftp,192.168.2.1)i386-pc > prefix=(tftp,192.168.2.1)/boot/grub > root=tftp,192.168.2.1 > net_pxe_boot_file=i386-pc/core.0 > > I changed the dhcp-tftpd configuration from prefix /boot/grub/i386-pc, > to test whether the problem lay in tftpd's inability to rad giles from > folders one level up (cd ..). Same result. > > _______________________________________________ > Grub-devel mailing list > Grub-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/grub-devel >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Grub-devel mailing list Grub-devel@gnu.org https://lists.gnu.org/mailman/listinfo/grub-devel
