[syslinux] Issue with ldlinux.c32 when symlinked on Windows

john doe johndoe65534 at mail.com
Thu Sep 26 07:14:40 PDT 2019


Hi, thank you for your answer.


On 9/25/2019 6:26 PM, Ady Ady via Syslinux wrote:
>> As shown above, the file ldlinux.c32 can not be downloaded because it is
>> a symlink, if I do remove the symlink and copy the file in the tftp root
>> directory it works.
>
>
> Are you creating a symlink on NTFS?
>

Yes, I'm creating symlink on NTFS partition.

> One possible reason, perhaps, IIRC... PXELINUX does not understand
> symlinks on NTFS volumes. Having said that, I might be misremembering
> and/or confused about this.
>

Any chance that can be looked at and fixed up if pxelinux.0 can't handle
symlink on NTFS?


> Independently of using symlinks or not, ldlinux.c32 should be located
> in the same directory as the bootloader file (e.g. pxelinux.0).
> Unfortunately, Debian not always follows this basic advice, thus
> complicating the matter (unnecessarily).
>

Couldn't agree more.

I guess I will need to open an Debian-installer bug report on this.
Does the same hold true for other *.c32 files (libcom32.c32 libutil.c32
esamenu.c32)?

Other then pxelinux.0 and ldlinux.c32 that are to be in the same
directory, is there other things that should be corrected by Debian
(guideline best practices)?

In other words, what should be corrected in the Debian netboot.tar.gz
tarball.


I realy appriciate your help and any feedback you can give me.

--
John Doe



More information about the Syslinux mailing list