... It makes you feel significantly less safe when using anything other than Qubes :]
> I was sad when installed VirtualBox, tried launching it and it said that something like "not supported on Xen hosts"
But why would you want to do that? You already have virtual machines at your disposal..
for development purposes, you might want other kinds. for example, vagrant is a big sticking point. its how we share and collaborate across platforms, so if you want to work on those projects, you better be able to run its vagrantfile. its also used as codified description of processes, sometimes across machines. so you can have a vagrantfile for your a web project that includes a vm for the back end database. more on that here, https://www.vagrantup.com/
another reason you might want it is nested virtualization for its own sake. for example, developing hypervisor management software.
for both cases, i just made a vagrant server to use remotely. but that has obvious limitations.
lxc or xen would work for developers only on linux. one of the benefits of vagrant is that you can share work with developers on other platforms. with lxc, theres also os limitations. at work we have linux and windows in our vagrant runs. xen could get around this, though the xen back end is pretty limited.
i think the best solution would be a qrexec vagrant back end, syntactically compatible with the more common backends (virtualbox,vmware etc),something i plan on looking into when get qubes running again. too many of the alt back ends (lxc, xen) have syntax thats not easily worked around, so they're really only good for that backend. an obvious drawback is the lack of nesting, but few need that. of course this would also need packer and/or vagrant mutate support. maybe qubes-lite is the better solution.
my isp going to start pushing ipv6 in a week or two. I'm scared lol.
Over 16% of traffic to Google is native IPv6: https://www.google.com/intl/en/ipv6/statistics.html
And as of AUgust 2016, more than 50% of the traffic to Facebook from users on the 4 major cellular (mobile data) networks in the US was via IPv6: http://www.internetsociety.org/deploy360/blog/2016/08/facebook-akamai-pass-major-milestone-over-50-ipv6-from-us-mobile-networks/
Akamai (one of the first CDNs) has some IPv6 adoption statistics, too: https://www.akamai.com/us/en/about/our-thinking/state-of-the-internet-report/state-of-the-internet-ipv6-adoption-visualization.jsp
So, IPv6 isn't quite as niche as a lot of folks in tech seem to think. My ISP started rolling it out, and while I had to do a small amount of massaging with my pfSense box to have it work properly, once it was functioning essentially the way an ISP-provided router might... essentially everything "just worked."
--Geo
I also expect to see routers for home market that will talk ipv6 externally and ipv4 internally. That will help a lot of people transition.
--
You received this message because you are subscribed to a topic in the Google Groups "qubes-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/qubes-users/rJYmO78ckxM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to qubes-users...@googlegroups.com.
To post to this group, send email to qubes...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/qubes-users/809adbd0-7716-c7b8-9adf-df3d56787d34%40gmx.com.