On Fri, 21.03.14 21:58, Wouter Verhelst (w...@uter.be) wrote:
In addition, nbd-client needs to fork() and open() the /dev/nbdX device
to support partitioned NBD devices (due to a deadlock issue, that can't
be done from the initial NBD_DO_IT ioctl handling, so it is done in the
first
Hi,
So, now that it looks like Debian is going to support systemd in the future,
I've been looking into writing systemd units for NBD, of which I
maintain the userspace both upstream and in Debian.
The user space consists of two bits that matter as far as bootup is
concerned: the client, and the
On Fri, 21.03.14 13:05, Wouter Verhelst (wou...@debian.org) wrote:
Heya,
The client side of the NBD protocol is implemented partially in
user space, and partially in kernel space. The user space part handles
connecting and the initial protocol negotiation; but once that has been
done,
On Fri, Mar 21, 2014 at 4:05 PM, Wouter Verhelst wou...@debian.org wrote:
First, let me explain how NBD works.
The client side of the NBD protocol is implemented partially in
user space, and partially in kernel space. The user space part handles
connecting and the initial protocol
