thank you unman. I tried to use it as sys-net, but
1) network-manager did not start on boot
2) when starting it by hand, I got the impression that the
network-manager data is stored elsewhere under debian than under fedora
- to the effect that I lost all saved wireless connections!
Is there an easy way to cure that? Bernhard
Andrew has quite correclty pointed out the complete absence of any
documentation on how to use the debian-9-minimal template. I'll try to
remedy this soon.
In the meantime you could follow the guidelines for using the
fedora-minimal template. (Apologies if you've already done this.)
Remark: I did manage to run debian-minimal as sys-usb that way (let me
mention that the required package qubes-proxy is not mentioned in the
online DOC! this is the same for fedora-minimal and debian-minimal ).
That did not work exactly the same for sys-net, since
NetworkManager-wifi will be called network-manager under debian
I guess that is the one I need?
Are there other packages to be added ??
dejavu-sans-fonts does not seem to exist under debian
Is it really needed?
Of course I added firmware for my wireless chipset.
The wireless connection information is actually stored under /rw/config , so it
wont be lost.(Check it's there)
Yes, it is there, no worries.
In Debian, Network manager information is held under
/etc/NetworkManager, which is, I would have thought, the same as Fedora.
maybe you're right and the problem is somewhere else. I re-bootet
sys-net with debian-minimal, and here is what I see (no clue what it
means, though). Any ideas? Bernhard
root@sys-net:~# service network-manager status
● NetworkManager.service - Network Manager
Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled;
vendor preset: enabled)
Drop-In: /lib/systemd/system/NetworkManager.service.d
└─30_qubes.conf
Active: failed (Result: exit-code) since Tue 2019-02-05 12:00:59
AEDT; 45s ago
Docs: man:NetworkManager(8)
Process: 568
ExecStartPre=/usr/lib/qubes/network-manager-prepare-conf-dir
(code=exited, status=203/EXEC)
Feb 05 12:00:58 sys-net systemd[1]: Failed to start Network Manager.
Feb 05 12:00:58 sys-net systemd[1]: NetworkManager.service: Unit entered
failed state.
Feb 05 12:00:58 sys-net systemd[1]: NetworkManager.service: Failed with
result 'exit-code'.
Feb 05 12:00:59 sys-net systemd[1]: NetworkManager.service: Service
hold-off time over, scheduling restart.
Feb 05 12:00:59 sys-net systemd[1]: Stopped Network Manager.
Feb 05 12:00:59 sys-net systemd[1]: NetworkManager.service: Start
request repeated too quickly.
Feb 05 12:00:59 sys-net systemd[1]: Failed to start Network Manager.
Feb 05 12:00:59 sys-net systemd[1]: NetworkManager.service: Unit entered
failed state.
Feb 05 12:00:59 sys-net systemd[1]: NetworkManager.service: Failed with
result 'exit-code'.
root@sys-net:~#
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-users/1d1dd534-b97d-34cb-0339-c1001f9c1796%40web.de.
For more options, visit https://groups.google.com/d/optout.
