> Status:Resolved / Resolution: Won't Fix
What?
> it's problematic to do properly with the real Windows.
Nevertheless you can run real Windows on Qubes: https://forum.qubes-os.org/t/wip-windows-qwt-user-reports/96....
See also discussion of Spectrum OS on Qubes forum: https://forum.qubes-os.org/t/spectrum-os-discussion/1531.
I love that you can explicitly compartmentalize your digital live into independent VMs with a great unified interface. I have "work" VM which contains all work stuff and "personal" VM for personal things. More thoughts from me: https://forum.qubes-os.org/t/how-to-pitch-qubes-os/4499/15.
[0] https://www.qubes-os.org/faq/#can-i-run-applications-like-ga...
[1] https://www.qubes-os.org/security/xsa/
[2] https://www.qubes-os.org/doc/templates/#official
In short: we believe the Xen architecture allows for the creation of more secure systems (i.e. with a much smaller TCB, which translates to a smaller attack surface). We discuss this in much greater depth in our Architecture Specification document:
https://forum.qubes-os.org/t/qubes-gpu-passthrough/661
https://forum.qubes-os.org/t/another-2-gpu-passthrough-post/...
See also: https://github.com/QubesOS/qubes-issues/issues/4321.
https://rillabs.org/posts/installing-qubes-os
Overall an impressive and surprisingly well functioning software, given what it does.
Unfortunately - which I didn't write in the post yet, should do - is that I felt I had to switch back to a normal distro again because of a combination of a couple of annoyances:
- The need to manually redirect the USB-keyboard to each qube
- The fact that I couldn't get Debian-based Qubes to respect the font size settings
- The overall relative slowness of the system, causing some already slow software to be even slower
- The last straw: Inability to run Virtualbox VMs in Qubes (which I use to create some course content etc).
https://forum.qubes-os.org/t/fonts-are-too-small-by-default/...
> - The overall relative slowness of the system, causing some already slow software to be even slower
Often connected to the fact that hyperthreading is enabled in BIOS (and it shouldn't be).
In general, you should try to ask for help on the Qubes forums. Most problems get resolved quickly.
>The magic SysRq key is a key combination understood by the Linux kernel, which allows the user to perform various low-level commands regardless of the system's state. It is often used to recover from freezes, or to reboot a computer without corrupting the filesystem.[1] Its effect is similar to the computer's hardware reset button (or power switch) but with many more options and much more control.
https://forum.qubes-os.org/t/dark-mode-in-debian-10-vm/3855/...
https://multicians.org/security.html
On X11 and Unix, XTerm's "secure keyboard" input makes X11 snooping impossible.
Regarding the Dvorak: It's a PITA. I'm running Svorak A5 currently so the current procedure is:
* Make sure it's the default setting in each template
* Make sure it's the default in XFCE
* Run a cronjob in dom0, this make sure that newly connected USB keyboards are changed to the correct layout aswell.
* * * * * DISPLAY=:0 ~/fix-scripts-xkb
#!/bin/sh
[ "$(setxkbmap -query | grep -oP '(?<=variant: )[a-z]+')" == "svorak" ] || ( setxkbmap se svorak; echo fixed xkbmap )
If you follow this simple step, USB keyboard and mouse input should Just Work in all your Qubes: https://www.qubes-os.org/doc/usb-qubes/#how-to-create-a-usb-...
If you follow this simple step, USB keyboard and mouse input should Just Work in all your Qubes: https://www.qubes-os.org/doc/usb-qubes/#how-to-create-a-usb-...
You can use Salt to automate this work: https://www.qubes-os.org/doc/salt/.
edit: maybe i'm being a bit optimistic for sys-net, which is the vm hosting the driver for the network card: these drivers are included in the linux tree and would need to be extracted and packaged into an unikernel. But for every non-driver vm it "should be easy" to get an unikernel implementation (drivers for paravirtual devices are easy to write).
Points 2 and 3 you're right about.
You can convert virtualbox VMs to qubes hvms[1] although it requires a bit of CLI work.
[1]https://www.qubes-os.org/doc/standalones-and-hvms/#convertin...
Since them all "modern" systems keep rediscovering in limited, limited and bug ridden ways what historical systems have done far better decades before...
I think many should just see classic advertisement like https://youtu.be/M0zgj2p7Ww4 than see it's date and where we are today...
It's not only security it's the overall design. In the past hw resources was limited an so hacks and slowness were common, hw itself being "in a pioneering phase" was full of hacks and ugliness but evolving those systems would have led us too the moon while we are still in the middle age...