You are not logged in.
Hi,
when I run pdflatex or lualatex in an AFS directory (mounted by openafs) I get the error:
$ lualatex talk.tex
This is LuaHBTeX, Version 1.24.0 (TeX Live 2026/Arch Linux)
restricted system commands enabled.
(./talk.texlualatex: dwmoreau: No such deviceor
$ pdflatex talk.tex
This is pdfTeX, Version 3.141592653-2.6-1.40.29 (TeX Live 2026/Arch Linux) (preloaded format=pdflatex)
restricted \write18 enabled.
entering extended mode
(./talk.texpdflatex: dwmoreau: No such device.
But if I copy the talk.tex file in a local directory and run the commands there it works.
Offline
The message output looks a bit weird, almost like it's searching for the wrong path.
Does it work if you give an absolute path to the file on AFS ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
@Lone_Wolf
Thanks for the help.
Yes indeed, if I give the full path it works but giving only ./talk.tex does not work.
Offline
What does file ./talk.tex output ?
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline
The same as above:
$ lualatex ./talk.tex
This is LuaHBTeX, Version 1.24.0 (TeX Live 2026/Arch Linux)
restricted system commands enabled.
(./talk.texlualatex: dwmoreau: No such deviceOffline
It works withe the older version texlive-bin-2026.0-1.
Offline
I sent an email to the tex-live list.
See: https://tug.org/pipermail/tex-live/2026 … 52458.html
I also sent an email to the openaffs list, I will put the link here once it has been accepted.
Last edited by drslmr (Today 12:09:20)
Offline
Good idea, could you post a link to the discussion so interested readers can follow it ?
If no one has responded to one of your posts please edit the post instead of creating a new one.
That makes the thread easier to follow.
Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.
clean chroot building not flexible enough ?
Try clean chroot manager by graysky
Offline