| 1 |
On Wed, Dec 04, 2019 at 04:28:26PM +0100, n952162 wrote |
| 2 |
|
| 3 |
> do I understand this correctly? In order to run qemu-nbd, you emerge |
| 4 |
> app-emulation/qemu |
| 5 |
> |
| 6 |
> but that isn't all, you've also got to emerge sys-block/nbd? |
| 7 |
|
| 8 |
nbd is a "Network Block Device" driver along the lines of NFS, but it |
| 9 |
doesn't handle concurrency. https://nbd.sourceforge.io/ But it's |
| 10 |
generic, and can handle any *REGULAR* file system, not just NFS. QCOW2, |
| 11 |
or raw, or whatever, is a special QEMU format. So it requires QEMU libs |
| 12 |
(i.e. qemu-nbd) to decode QCOW2/RAW. |
| 13 |
|
| 14 |
> Why doesn't qemu have a dependency on nbd? |
| 15 |
|
| 16 |
Why doesn't qemu have a dependency on NFS? Same answer; they're both |
| 17 |
remote network block device systems that most linux users don't need, |
| 18 |
and they're both unrelated to the core functionality of QEMU. |
| 19 |
|
| 20 |
-- |
| 21 |
Walter Dnes <waltdnes@××××××××.org> |
| 22 |
I don't run "desktop environments"; I run useful applications |
Archives