Chris's suggestion was not quite right, but near enough for me to get it working. This is no reflection on Chris but is down to inconsistent naming conventions between different devs on different projects.
Chris said > > You can open a terminal in your template and run the following: > > sudo touch /var/run/qubes-service/network-manager up to here is correct, but there are two points with the following line > sudo service network-manager start Firstly, it tries to do it but suggests we use systemctl instead. Secondly systectl does not know of a service by this name. I then did a bit of searching and it turns out that the correct command is sudo systemctl start NetworkManager The rest all works as advertised. > nmcli radio wifi off > > Then shutdown the template and restart sys-net. NM should remember the > setting you made in the template and start with wifi turned off. It can > be turned on by right-clicking the systray icon and enabling the wifi > checkbox. > Many thanks Chris for putting me on the right path. Comment on Qubes design: Now I have seen it working I am also impressed with the way that touching that file makes it possible to start the service, just once, in the template, and the way that that file magically disappears before the template is rebooted. I had not realised that some template changes are volatile. As I say I am impressed :) Warmly River~~ -- 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 qubes-users+unsubscr...@googlegroups.com. To post to this group, send email to qubes-users@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/f32ab626-56de-47d5-8696-4b968897748e%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
