[Bug 593227] [NEW] feature request: add a root-path parameter

[Alkis Georgopoulos]

Public bug reported:

Currently nbd-server and nbd-client communicate using a different port
for each image. So if e.g. an LTSP admin wants to use a chroot for
nvidia-based clients and a chroot for the rest of his clients, he'd need
to use two ports. And he wanted nbd swapping a third port would be
needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
 * A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
 * A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.

** Affects: ltsp (Ubuntu)
     Importance: Undecided
         Status: New

** Affects: nbd (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: ltsp (Ubuntu)
   Importance: Undecided
       Status: New

-- 
feature request: add a root-path parameter
https://bugs.launchpad.net/bugs/593227
You received this bug notification because you are a member of Edubuntu
Bugsquad, which is subscribed to ltsp in ubuntu.

Status in “ltsp” package in Ubuntu: New
Status in “nbd” package in Ubuntu: New

Bug description:
Currently nbd-server and nbd-client communicate using a different port for each image. So if e.g. an LTSP admin wants to use a chroot for nvidia-based clients and a chroot for the rest of his clients, he'd need to use two ports. And he wanted nbd swapping a third port would be needed.

This is inconvenient and makes IANA applications to standarize the nbd port impossible.
It'd be better if nbd-client supported two additional parameters, to be sent and processed by nbd-server at the negotiation stage:
 * A -path=/path/to/desired/root option (which of course the server could ignore, if it wasn't in a pool of allowed paths), and
 * A -swap=<requested size> option (to replace the current -swap option). If the server configuration allowed it, nbd-server (or some callback scripts) would create an appropriate swap flie of that size for the client.