Package: nbd-server Version: 1:3.14-4 Severity: important Control: affects -1 src:ltsp ltsp-client-core ltsp-server
Thanks for maintaining NBD! Unfortunately, it appears the fix to #840612 breaks LTSP's use of NBD: #840612 initrd forces NBD section name to start with the slash A presumably unintended side-effect of that fix breaks LTSP's long-standing "default" configuration for NBD on amd64 /etc/nbd-server/conf.d/ltsp_amd64.conf: [/opt/ltsp/amd64] exportname = /opt/ltsp/images/amd64.img readonly = true authfile = /etc/ltsp/nbd-server.allow Removing the leading / in ltsp_amd64.conf works around the issue... but then is no longer backwards compatible with other clients that expect the leading / to be present. This is used in order for the NBD and NFS names used by LTSP to not require changing the DHCP configuration, as LTSP has long been able to support both NBD and NFS configurations simultaneously on the same server, selecting which to boot with from a menu. nbdroot=/opt/ltsp/amd64 or nbdroot=1.2.3.4:/opt/ltsp/amd64 are both options used for configuring NBD root in LTSP, or if not specified, falling back to the root-path specified similarly. Will look into this further tomorrow, but wanted to get this bug filed ASAP as it impacts LTSP pretty badly... Thanks for all your great work on NBD! live well, vagrant -- System Information: Debian Release: stretch/sid APT prefers testing APT policy: (500, 'testing'), (120, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 4.8.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages nbd-server depends on: ii adduser 3.115 ii debconf [debconf-2.0] 1.5.59 ii libc6 2.24-7 ii libglib2.0-0 2.50.2-2 ii ucf 3.0036 nbd-server recommends no packages. nbd-server suggests no packages. -- debconf information: nbd-server/autogen: nbd-server/filename: nbd-server/number: 0 nbd-server/name:
signature.asc
Description: PGP signature
