Package: ltsp-server Version: 5.2.16-1 Severity: normal
Hello, after building the ltsp client with ltsp-build-client, the client is unabled to load the "/ltsp/i386/pxelinux.0" file via tftpd-hpa. I tested it manualy : $ tftp localhost 69 -c get /ltsp/i386/pxelinux.0 Error code 0: Permission denied I solved the problem by changing the UID and the GID of the ltsp directory in /srv/tftp/ : $ sudo chown -R tftp.tftp /srv/tftp/ltsp/ And now, it works fine. But it should be done by the ltsp-build-client script directly. Thanks. -- Package-specific info: chroot information: /opt/ltsp/i386 packages in chroot: /opt/ltsp/i386 ii ldm 2:2.2.4-1 ii ltsp-client 5.2.16-1 ii ltsp-client-core 5.2.16-1 ii ltspfsd 1.0-1 ii ltspfsd-core 1.0-1 found: /opt/ltsp/i386/etc/lts.conf -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (990, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/6 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ltsp-server depends on: ii debconf [debconf-2.0] 1.5.40 ii debconf-utils 1.5.40 ii debootstrap 1.0.37 ii gettext-base 0.18.1.1-5 ii iproute 20110629-1 ii lsb-release 3.2-28 ii openssh-client 1:5.9p1-2 ii python 2.7.2-9 ii tcpd 7.6.q-21 ii update-inetd 4.40 Versions of packages ltsp-server recommends: ii nbd-server 1:2.9.24-3 ii nfs-kernel-server 1:1.2.5-2 ii openbsd-inetd [inet-superserver] 0.20091229-1 ii openssh-server 1:5.9p1-2 ii squashfs-tools 1:4.2-4+b1 ii tftpd-hpa 5.1-3 Versions of packages ltsp-server suggests: ii audiooss <none> ii isc-dhcp-server [dhcp3-server] 4.1.1-P1-17 ii kde-window-manager [x-window-manager] 4:4.6.5-3 ii ldm-server 2:2.2.4-1 ii libasound2-plugins 1.0.24-3 ii ltsp-docs 0.99+bzr120-1 ii ltspfs 1.0-1 ii pulseaudio-esound-compat 1.0-4 ii qemu-user-static <none> ii sdm <none> ii x11-utils 7.6+4 ii xauth 1:1.0.6-1 -- debconf information: ltsp-server/build_client: false -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
