Hi Mike,
Checked on Debian Edu 12 with LTSP
Compared strace traces for two boot menu entries:
* Plain X2Go Thin Client (64-Bit).
* Plain X2Go Thin Client (64-Bit, NFS rootfs).
Both menu items request the same files via TFTP:
* /srv/tftp/ltsp/x2go-bare-amd64/vmlinuz
* /srv/tftp/ltsp/x2go-bare-amd64/ltsp.img
* /srv/tftp/ltsp/x2go-bare-amd64/initrd.img
... and can connect to the same X2Go sessions running on the server.
After unlocking the root with chroot on `/srv/ltsp/x2go-bare-amd64`, it was
possible to verify these kernel parameters on the client:
```
initrd=ltsp.img initrd=initrd.img
root=/dev/nfs
nfsroot=192.168.0.254:/srv/ltsp/x2go-bare-amd64
BOOTIF=01-52-54-00-dd-30-a4
quiet splash
```
As a result of checking these two configurations in
/srv/tftp/ltsp/ltsp.ipxe:
* x2go-bare-amd64 uses a SquashFS image;
* r_x2go-bare-amd64 uses an NFS root filesystem.
... was found:
1. Both entries use the same boot files from
`/srv/tftp/ltsp/x2go-bare-amd64/`:
* vmlinuz
* ltsp.img
* initrd.img
2. but they use different root filesystems:
* non-NFS mode:
`/srv/ltsp/images/x2go-bare-amd64.img`
* NFS mode:
`/srv/ltsp/x2go-bare-amd64`
The bug report can be closed.
Sincerely,
Serhii Horichenko
ср, 19 серп. 2026 р. о 23:24 Mike Gabriel <sunweaver@debian.org> пише: