Re: [qubes-users] How to assign keyboard shortcuts to a VM?
Hi Michael, I don't have the time currently to figure this out and send you a working solution. So instead I'll share things I know: 1) if you inquire the window property "_QUBES_VMNAME" of the active window, you'll get the name of the qube 2) you should be able to get to this with wmctrl or maybe xdotool Then write a little bash script in dom0 and hook it up to a shortcut, is what I think. Good luck! /Sven -- public key: https://www.svensemmler.org/2A632C537D744BC7.asc fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c1670d6c-93be-67c6-f8ba-64e0c61835a4%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] VPN up/down pop up not working?
Hi @stumpy, I don't know what your goals are exactly, but if you'd like a debian-minimal based qube to connect to a OpenVPN than this will work for sure: Template (cloned from debian-minimal): apt install qubes-repo-contrib apt update apt install qubes-tunnel openvpn qubes-core-agent-networking Qube (based on above template) Obviously provide netvm and set provides_network to true. Also 'qvm-service sys-vpn qubes-tunnel on' Then inside the qube /usr/lib/qubes/qtunnel-setup --config and finally copy and rename the .ovpn file provided by your VPN provider to /rw/config/qtunnel/qtunnel.conf That's all there is. Restart the qube and be happy. /Sven -- public key: https://www.svensemmler.org/2A632C537D744BC7.asc fingerprint: DA59 75C9 ABC4 0C83 3B2F 620B 2A63 2C53 7D74 4BC7 -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/c2589593-c201-a932-04fc-14638fa7ca63%40SvenSemmler.org. OpenPGP_signature Description: OpenPGP digital signature
Re: [qubes-users] Dual booting different Qubes versions on same machine
Already was thinking about this too... Have both OSes on two different SSDs. 4.1 on a 1TB m.2 card (slot 1) and 4.0.4 on a 512 GB m.2 card (slot 2). 4.1 was installed on the P50 while th 4.0.4 version was plugged out. After 4.0.4 was plugged in again, both cards can be shown in BIOS but 4.1 is booting with it's boot screen cause it actually isn't aware of the second m.2 card, which should be quiet normal. GRUB have to be edited. unman schrieb am Dienstag, 22. Juni 2021 um 07:07:01 UTC-4: > On Tue, Jun 22, 2021 at 10:29:54AM +0100, River~~ wrote: > > Hi all, > > > > I noticed the new "alpha" level isos in the downloads and feel > > motivated to help testing it. > > > > I obviously do not want to go over to alpha for my normal work, but > > would be interested if I can install it alongside my existing current > > release. That way I would be testing that it works on the exact > > hardware that I would eventually be running it on when it reaches > > production quality. > > > > Do I proceed as for the instructions for installing Qubes as a second > > boot option to Linux? If not, what would be different? > > > > What additional risks might I introduce by running a development > > version of Qubes on the same physical machine as the production > > version? > > > > Obviously I would not have any files/partitions shared apart from the > > EFI partition. > > > > Would it make sense to install it onto an EFI partition on a different > > internal disk? Would it be better for any reason to install it onto a > > USB drive? (my guess to both of these is no, because when the test > > system is running the production system would be on the host even if > > not mounted) > > > > My current production version is R4.0.3 and I will shortly be > > replacing it with R4.0.4. At the time of writing the current alpha is > > R4.1.0 but that my (or may not) change by the time I get around to > > installing it. > > > > I thought I would dual boot the new R4.0.4 with the existing R4.0.3, > > then once R4.0.4 is verified as working for me I would transfer the > > user level files and then overwrite the older production version with > > the alpha test version. Anyone who can think why that might be a bad > > idea please speak now or forever hold your peace (as they say in > > English weddings) > > > > I did a google search for "dual boot qubes versions site:qubes-os.org" > > but it only pointed me to info about dual booting with non-Qubes > > systems. > > > > Once successful, would ppl welcome my spending time adding a section > > to the dual boot online documentation? I would be happy to do so if > > just one person thinks it might be useful > > > > WArmly > > River~~ > > With classic GRUB it's straightforward, and (imo) doesn't warrant new > docs. > I cant help with UEFI at all, and that probably *does*. > > That said, you would be running alpha software alongside your main > system. Having separate encrypted drives/partitions will undoubtedly aid > separation, but it's still a risk, and not something I would advocate if > you value your data. > If it's possible for you to swap out your drives, and have a separate > 4.1 drive, I would recommend that instead. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/5648120e-32fe-435f-8a93-a06cc62fd20en%40googlegroups.com.
Re: [qubes-users] Dual booting different Qubes versions on same machine
On Tue, Jun 22, 2021 at 10:29:54AM +0100, River~~ wrote: > Hi all, > > I noticed the new "alpha" level isos in the downloads and feel > motivated to help testing it. > > I obviously do not want to go over to alpha for my normal work, but > would be interested if I can install it alongside my existing current > release. That way I would be testing that it works on the exact > hardware that I would eventually be running it on when it reaches > production quality. > > Do I proceed as for the instructions for installing Qubes as a second > boot option to Linux? If not, what would be different? > > What additional risks might I introduce by running a development > version of Qubes on the same physical machine as the production > version? > > Obviously I would not have any files/partitions shared apart from the > EFI partition. > > Would it make sense to install it onto an EFI partition on a different > internal disk? Would it be better for any reason to install it onto a > USB drive? (my guess to both of these is no, because when the test > system is running the production system would be on the host even if > not mounted) > > My current production version is R4.0.3 and I will shortly be > replacing it with R4.0.4. At the time of writing the current alpha is > R4.1.0 but that my (or may not) change by the time I get around to > installing it. > > I thought I would dual boot the new R4.0.4 with the existing R4.0.3, > then once R4.0.4 is verified as working for me I would transfer the > user level files and then overwrite the older production version with > the alpha test version. Anyone who can think why that might be a bad > idea please speak now or forever hold your peace (as they say in > English weddings) > > I did a google search for "dual boot qubes versions site:qubes-os.org" > but it only pointed me to info about dual booting with non-Qubes > systems. > > Once successful, would ppl welcome my spending time adding a section > to the dual boot online documentation? I would be happy to do so if > just one person thinks it might be useful > > WArmly > River~~ With classic GRUB it's straightforward, and (imo) doesn't warrant new docs. I cant help with UEFI at all, and that probably *does*. That said, you would be running alpha software alongside your main system. Having separate encrypted drives/partitions will undoubtedly aid separation, but it's still a risk, and not something I would advocate if you value your data. If it's possible for you to swap out your drives, and have a separate 4.1 drive, I would recommend that instead. -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/20210622110657.GE20642%40thirdeyesecurity.org.
[qubes-users] Dual booting different Qubes versions on same machine
Hi all, I noticed the new "alpha" level isos in the downloads and feel motivated to help testing it. I obviously do not want to go over to alpha for my normal work, but would be interested if I can install it alongside my existing current release. That way I would be testing that it works on the exact hardware that I would eventually be running it on when it reaches production quality. Do I proceed as for the instructions for installing Qubes as a second boot option to Linux? If not, what would be different? What additional risks might I introduce by running a development version of Qubes on the same physical machine as the production version? Obviously I would not have any files/partitions shared apart from the EFI partition. Would it make sense to install it onto an EFI partition on a different internal disk? Would it be better for any reason to install it onto a USB drive? (my guess to both of these is no, because when the test system is running the production system would be on the host even if not mounted) My current production version is R4.0.3 and I will shortly be replacing it with R4.0.4. At the time of writing the current alpha is R4.1.0 but that my (or may not) change by the time I get around to installing it. I thought I would dual boot the new R4.0.4 with the existing R4.0.3, then once R4.0.4 is verified as working for me I would transfer the user level files and then overwrite the older production version with the alpha test version. Anyone who can think why that might be a bad idea please speak now or forever hold your peace (as they say in English weddings) I did a google search for "dual boot qubes versions site:qubes-os.org" but it only pointed me to info about dual booting with non-Qubes systems. Once successful, would ppl welcome my spending time adding a section to the dual boot online documentation? I would be happy to do so if just one person thinks it might be useful WArmly River~~ -- 9831*2^1441403+1 is prime, >400k digits -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/CAK3jUKovJGHW1m45D8_5c%2BJmLWV8RoDTQyzCdFRjQ%3DixRg_XRA%40mail.gmail.com.
