Re: Resolving relative path on AFS broken in newer version

Hi Michael,

On Tue, 2026-06-30 at 15:04 +0200, [email protected] wrote:
> using lualatex ./talk.tex in a directory within the AFS file system
> fails to do a proper path resolution. It works both, when using the
> full file path and with relative file path on a local directory.
>
> So it is probably difficult for many people to reproduce, since you need
> an AFS mounted using openafs.
>
> lualatex ./talk.tex
> This is LuaHBTeX, Version 1.24.0 (TeX Live 2026/Arch Linux)
>   restricted system commands enabled.
> (./talk.texlualatex: dwmoreau: No such device
>
> See the post I started:
> https://bbs.archlinux.org/viewtopic.php?pid=3D2303320#p2303320

Hmm, interesting. Are you able to reproduce this with pdfTeX in --ini
mode?

    $ cat test.tex
    \catcode`\{=3D1
    \catcode`\}=3D2
    \message{Hello, world!}
    \end
    $ pdftex --ini ./test.tex
    This is pdfTeX, Version 3.141592653-2.6-1.40.29 (TeX Live 2026) (INITEX=
)
     restricted \write18 enabled.
    (./test.tex Hello, world! )
    No pages of output.
    Transcript written on test.log.

If so, could you please reply with the output from strace:

    $ strace -ffs65535 -e '!read,write,brk,mmap,pread64' pdftex --ini ./tes=
t.tex

If you can't reproduce the problem with "pdftex --ini", then replace
"pdftex ..." with your original "pdflatex ..." command.

Thanks,
-- Max