[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Changing di-netboot-assistants directory within the TFTP-root

Hello Hermann,

On Mon, Dec 18, 2017 at 12:03:02PM +0100, Hermann Lauer wrote:
> On Sun, Dec 17, 2017 at 05:22:57PM +0300, Andreas B. Mundt wrote:
> > Hi everybody,
> >
> > I plan to move di-netboot-assistant's directory within the TFTP-root.
> >
> > Right now, '$TFTP_ROOT/debian-installer/' is used to set up and serve
> > the netboot-images.  If you also serve preseedings from the canonical
> just wondering if this is the default location or the only supported
> location for network installs.
> Please see also the email attached which seems not to have hit the list
> about grub not obeying an initial path send with dhcp.
> Thanks and sorry if I misunderstood something here,
>  greetings

Do you use di-netboot-assistant [1] or just the debian-installer netboot
packages/images [2]?

> when doing network installation with the files from
> debian/dists/stretch/main/installer-amd64/current/images/netboot/netboot.tar.gz
> grub didn't find it's files if using a nonstandard tftp server layout:
> RRQ from filename /debian/amd64_stretch/debian-installer/amd64/bootnetx64.efi
> tftp: client does not accept options
> RRQ from filename /debian/amd64_stretch/debian-installer/amd64/bootnetx64.efi
> RRQ from filename debian-installer/amd64/grub/x86_64-efi/command.lst
> RRQ from filename debian-installer/amd64/grub/x86_64-efi/fs.lst
> RRQ from filename debian-installer/amd64/grub/x86_64-efi/crypto.lst
> RRQ from filename debian-installer/amd64/grub/x86_64-efi/terminal.lst
> RRQ from filename debian-installer/amd64/grub/grub.cfg
> PXE BIOS with pxelinux has no problems with finding it's files in such a layout.
> Is there any functionality in grub to enable relative pathes at that point of the debian
> installation ? If not, is that a bug/regression to report against grub ?

In di-netboot-assistant, a grub-EFI image is prepared which then
includes the grub.conf files of the debian-installer images, with the
correct paths.  You get an idea in [3].  Perhaps you can follow this
approach (or even better: use di-netboot-assistant) too.

On the other hand, if you are already talking about a problem with
di-netboot-assistant, we should open a bug against
di-netboot-assistant and take a closer look at what went wrong.  I
only tested the grub-EFI stuff in di-netboot-assistant within a
virtual machine setup, as I currently have no EFI system around.

Best regards,


[1] <URL:https://wiki.debian.org/DebianInstaller/NetbootAssistant>
[2] <URL:https://packages.debian.org/stretch/debian-installer-9-netboot-amd64>
[3] <URL:https://anonscm.debian.org/cgit/d-i/netboot-assistant.git/tree/di-netboot-assistant#n239>

Reply to: