29.06.2023 12:31, Thomas Huth wrote:
..
This is actually a question to QEMU upstream, - I think the same reasoning
applies there as well.
Looking at our docs, it seems like we're lacking an introduction to the the "configure" switches like --enable-system and --enable-user completely,
indeed :
On 29/06/2023 10.12, Michael Tokarev wrote:
29.06.2023 11:02, Thomas Huth wrote:
There is no package called "qemu" here - thus use the two meta-packages
"qemu-system" and "qemu-user" instead.
There are 2 questions here.
1. Do we really want to suggest users to install the whole thing?
qemu-us
On 29/6/23 10:12, Michael Tokarev wrote:
29.06.2023 11:02, Thomas Huth wrote:
There is no package called "qemu" here - thus use the two meta-packages
"qemu-system" and "qemu-user" instead.
There are 2 questions here.
1. Do we really want to suggest users to install the whole thing?
qemu-user
29.06.2023 11:02, Thomas Huth wrote:
There is no package called "qemu" here - thus use the two meta-packages
"qemu-system" and "qemu-user" instead.
There are 2 questions here.
1. Do we really want to suggest users to install the whole thing?
qemu-user and qemu-system are two entirely different
There is no package called "qemu" here - thus use the two meta-packages
"qemu-system" and "qemu-user" instead.
Resolves: https://gitlab.com/qemu-project/qemu-web/-/issues/8
Signed-off-by: Thomas Huth
---
_download/linux.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/_down
