Re: [qubes-users] Can I speed up the loading of an APP?

2016-12-21 Thread Chris Laprise


On 12/21/2016 03:02 PM, Patrick Bouldin wrote:

On Wednesday, December 21, 2016 at 2:03:15 PM UTC-5, Chris Laprise wrote:

On 12/20/2016 08:53 PM, Patrick Bouldin wrote:

Hi, compared to running a certain app in windows (Anki), installing it in the Fedora 
template in Qubes means the first time to run is very slow to launch. Maybe up to a 
minute. To install it to the template I just said "sudo yum install anki"

Otherwise, other things running are very fast. If I do launch it manually from 
the fedora CLI it's the same slow launch. Maybe it comes down to compiling it?

Thanks,
Patrick


Did you accidentally turn off memory balancing in the Fedora VM? That
would slow it down a lot.

Chris

Hi Chris, well that is a new topic for me, but did some checking. To clarify, one would adjust that 
at the CLI right? A command like "sudo systemctl stop qubes-qmemman" ?  If so, I haven't 
done that. I also see a setting related to the memory balancing in the advanced part of the memory 
allocation, a checkmark for "include in memory balancing" - and that is checked, I think 
it's default.


You can check this in Qubes Manager settings for the VM, on the Advanced 
tab.


Chris

--
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/f1cf6431-ca16-c91c-8043-548284ca95e0%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Fedora 23 EOL December 20; Update Your Templates!

2016-12-21 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-21 22:11, Andrew David Wong wrote:
> On 2016-12-21 21:56, Chris Laprise wrote:
>> On 12/19/2016 12:33 AM, Andrew David Wong wrote:
>>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>>>
>>> On 2016-12-18 17:27, iamthech...@gmail.com wrote:
 Is there a guide to update an existing VM to Fedora 24 while 
 preserving it's contents? I upgraded the template per the 
 instructions [1], but can't figure out how to upgrade my
 existing VMs while saving their data.

 I can do a fresh Qubes install if necessary but would rather
 avoid it, if possible.

 [1]
 https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/

>>> If you're referring to TemplateBasedVMs such as AppVMs, then
>>> there's no need to upgrade them. One of the main features of the
>>> template system is that you only have to update and upgrade the
>>> templates, and all VMs based on those TemplateVMs will get their
>>> root filesystems from the TemplateVMs. So, just make sure that
>>> your TemplateBasedVMs are based on your Fedora 24 TemplateVM(s),
>>> and you're good to go.
>>>
>>> If, on the other hand, you're referring to Fedora StandaloneVMs,
>>> then the procedure for upgrading those is the same as for
>>> TemplateVMs, except that StandaloneVMs can't be `qvm-trim`ed
>>> (AFAIK).
>>>
> 
>> IIRC, internal 'fstrim' works on standalone root fs because it
>> doesn't have the COW overlay. So it doesn't need the dom0 tool.
> 
> 
> Thanks. Just reclaimed 125 GB in a three-year-old StandaloneVM. ^_^
> 
> For others, the command I used (in the StandaloneVM):
> 
> $ sudo fstrim -v -a
> 

Added to docs:

https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/#upgrading-standalonevms

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYW3FfAAoJENtN07w5UDAwO2UQAKxYOyv8DmnPyNawAHufcFW0
Ea+oaQbkRfLopehZAEfbzGg9O5dqRf+xgujlf8L2PhYN7ACCYKJ2+2Sb8L03bnfg
TRy+dh1AQ0rQKaQGBl03nPGiHXvUFeEuUhHSDO63k1M3EjNwliDHz7fR8ahqVqhf
EeF6Y/AQcoOshwpPoIJlVX5yoxgTXlOWCFfensaxiU1IUnb25JDM3EMvo51BriOC
AAW+hNQWjVeBMPPHeci8Ln5tcandT/0ZiNDHJ/CIOvYwripF1ij8FwhgVxXSCTJ6
9l26fI3AitlykYErWizgtnnR6hwCYhnhgggKJ0P1Id8j8kUVQ+9UQbJ7nMebe5HZ
bkMogDeRlt3vkJJY1IhCAcxWSa4rpSBZO4VNR/Ikd+CyMUSxzjXRGnk3AcFifyi4
8Gh0KbnVQ4/2PsJcR/f3WECkV2+2zEDDsdMi5KHAlnkDu+DFryotvrYFuY7Ppe6X
ZSPw2V2MdebC8D/P4DR8Wjj3bleQ56V0h+AK19+Sx3Obc1HelD+S6VSK0gYHbH9A
qB5olhdGvyKy8Goe7NxkMGRjFhyfI39kSJYCffVYfGsJyW7I+4PMuS4lfc1h8OVR
2LaBEDFCwjqHANMoxbr95I7S32Ig4oIRPqpGy7eoFOkX1CDZuTv7vW7L1eMN1AIw
isY/v1ps2/NIoBEKCHQy
=p8oA
-END PGP SIGNATURE-

-- 
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/81ec2918-8650-ca9c-df40-60079ea148db%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Fedora Desktop in Qubes

2016-12-21 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-21 19:21, Patrick Bouldin wrote:
> On Wednesday, December 21, 2016 at 6:13:24 AM UTC-5, Patrick
> Bouldin wrote:
>> Hi, I saw some threads on this but am not clear at a high level.
>> 
>> I thought I would install dropbox client on one of my Fedora VMs
>> so that working with files is much smoother than from a browser.
>> So, is installing a Fedora Desktop the best plan to do that?
>> Don't assume I know enough of native Qubes ability please - maybe
>> I'm missing a key point!
>> 

You'll want to install Dropbox in your TemplateVM so that you can use it
in AppVMs based on that TemplateVM. You can follow the instructions on
Dropbox's website for adding their repo in your Fedora TemplateVM, then:

$ sudo dnf install nautilus-dropbox

> one day of poking around more, let me just ask this. I looked but
> could not find, is it normal to be able to launch Fedora GNOME
> inside a Fedora 24 VM? How does one do that? I tried StartX... that
> doesn't work. Do I need to install something?
> 

Quoting Marek's answer to this in another thread:
> This isn't possible for standard AppVMs - this part (emulated GPU)
> is intentionally disabled there. If you really want, for whatever
> reason, you can: - start vncserver in the VM and connect to it from
> the same VM - create HVM and install some linux (or other system)
> there - HVMs are running with emulated GPU and can be viewed with
> full desktop in a window: https://www.qubes-os.org/doc/hvm/

https://groups.google.com/d/msg/qubes-users/Z8XXbz5wofE/caDe72DjCgAJ

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYW2/dAAoJENtN07w5UDAwLmUP/3JIgXfUfUkvYEoX1lWvrqfk
NDUHO/E9wyW/jHItJVyFdQznxKu3KT3QcZVJ8s1EKxYfLgTTqGmNi6+MUVbcDODM
uUHGZpmfS+XJyvkXJaoje3DlMzhf59RJ/eq4D6whyFibHZeb1FSZJvcDuEcFAtol
Tpsz7Em9Ay/oPaVAN2Flithn50eetQdOkmW7RwCFyoulUyPnygLzj2u+ZQWBmBqs
WV5h2drq92lZrTfUDpgTeZFUcYuL/Bb7k/uBfvbGSakSkOhMrsU6xst64udrdbiK
P1F5WB0J7bV9wrlHLWNcn+qJ/oW/TTAu022nd4og+av6lWfU448nYvGcMDtjZyMU
AiwSj8eZ/p/u5s5wrYHF6e896ldTjC6ddKQL7n+YS6nZ3boD05Yrc6/xhv/GMjHT
8StXuZyfMoIzPf0dytwAc5uPZK2il+0YyVeoImTFaBWIH9UghwEwGgC1H/aARJtR
ncX1Cfak3ZmnpG4tyuoZZwjVzlfGk9WljQ2LepgrWl+fpzeOngJnkT6hJX8OH4if
9M5vw/VjN6WWp0Mz1CI8Tc0HzLZUa5pXawI08dVidnRvT1k6iDxCRUwJVpGxlpdS
1fqYmdQSdv/aAKfQK6JWvpRsd8ftdb11NW/qRrKW+K9chEwBKYrsgyCn4Zj4ZA/p
WQOhyn+b326VeT2Dw2M1
=TYcM
-END PGP SIGNATURE-

-- 
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/03fe23b7-1ebb-87aa-9c45-89cc8e4d3a35%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Fedora 23 EOL December 20; Update Your Templates!

2016-12-21 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-21 21:56, Chris Laprise wrote:
> On 12/19/2016 12:33 AM, Andrew David Wong wrote:
>> -BEGIN PGP SIGNED MESSAGE- Hash: SHA512
>> 
>> On 2016-12-18 17:27, iamthech...@gmail.com wrote:
>>> Is there a guide to update an existing VM to Fedora 24 while 
>>> preserving it's contents? I upgraded the template per the 
>>> instructions [1], but can't figure out how to upgrade my
>>> existing VMs while saving their data.
>>> 
>>> I can do a fresh Qubes install if necessary but would rather
>>> avoid it, if possible.
>>> 
>>> [1]
>>> https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/
>>> 
>> If you're referring to TemplateBasedVMs such as AppVMs, then
>> there's no need to upgrade them. One of the main features of the
>> template system is that you only have to update and upgrade the
>> templates, and all VMs based on those TemplateVMs will get their
>> root filesystems from the TemplateVMs. So, just make sure that
>> your TemplateBasedVMs are based on your Fedora 24 TemplateVM(s),
>> and you're good to go.
>> 
>> If, on the other hand, you're referring to Fedora StandaloneVMs,
>> then the procedure for upgrading those is the same as for
>> TemplateVMs, except that StandaloneVMs can't be `qvm-trim`ed
>> (AFAIK).
>> 
> 
> IIRC, internal 'fstrim' works on standalone root fs because it
> doesn't have the COW overlay. So it doesn't need the dom0 tool.
> 

Thanks. Just reclaimed 125 GB in a three-year-old StandaloneVM. ^_^

For others, the command I used (in the StandaloneVM):

$ sudo fstrim -v -a

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYW26bAAoJENtN07w5UDAw2jsP/1UEYQA/Lt1o2NMnGMLpban6
0pnMrGLjyEWz7caTGA1UkmF+e+0Mj0D/wS2KNv6nVHJ2mzYt9ySk4xaEfLATqtW4
ekSd9eAuwMjahI599ZoGxHisPbdCJOQVDVj6hN7Vg0d2QgvGRLKKDZYZqigsnKHS
YaCVLSO9QGlz1dWJ6jl4HuF8yHa5/sQjxOYtDq+5bLiQczpkKg7xn8QMwcn9egIs
Mz2EOdpfLZh4ncpli1snfm2FMpPebwqebGIq++IJMx6nhd7Ft/Vt2AfnCbJjiCgE
ilD8gmWF1HHeeSfkVi4tH5ZB/Wl7NqKULyl43GYKa360E1ViBuaolRHdpUT91f8/
Ka2atlbt7vLMv8sdQlCN4iO9keiqUakjNB16YJoX2G4Vqk433YGZBsbUfFlgunrL
f3S1lQnx7VW3QSLRokvkNE56Y7gZ5HN83S3sM5FNgJleGH6CdFe6hctP64OBBe2R
riCG1Wsv3fc8m/b65ouseNjzr3BCCp01hmu6MGWxGuHv2MH2doNY6VhY1y50g2jA
qsarxIeGhDP3U7DNaZ8i7KnfGcGaM5SqZTaOUNMnteR5XN7XtTYFh152eduSiREO
9dpCSgvc58LLyTekukk+srmuEGzp7P1NWqozs7Aa1f0b1HewL9nLMubbnlFd1Fvm
+VloGnkSOmUmvZCLdCAH
=9RHR
-END PGP SIGNATURE-

-- 
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/1de8cb53-d36c-ec1b-81b6-b30e98137b17%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Fedora 23 EOL December 20; Update Your Templates!

2016-12-21 Thread Chris Laprise

On 12/19/2016 12:33 AM, Andrew David Wong wrote:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-18 17:27, iamthech...@gmail.com wrote:

Is there a guide to update an existing VM to Fedora 24 while
preserving it's contents? I upgraded the template per the
instructions [1], but can't figure out how to upgrade my existing
VMs while saving their data.

I can do a fresh Qubes install if necessary but would rather avoid
it, if possible.

[1] https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/


If you're referring to TemplateBasedVMs such as AppVMs, then there's
no need to upgrade them. One of the main features of the template
system is that you only have to update and upgrade the templates, and
all VMs based on those TemplateVMs will get their root filesystems
from the TemplateVMs. So, just make sure that your TemplateBasedVMs
are based on your Fedora 24 TemplateVM(s), and you're good to go.

If, on the other hand, you're referring to Fedora StandaloneVMs, then
the procedure for upgrading those is the same as for TemplateVMs,
except that StandaloneVMs can't be `qvm-trim`ed (AFAIK).



IIRC, internal 'fstrim' works on standalone root fs because it doesn't 
have the COW overlay. So it doesn't need the dom0 tool.


Chris

--
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/5e190ffe-eaa3-34c9-c7c5-c4a9af807d5e%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: qubes 3.2 question

2016-12-21 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-21 04:14, Gmail wrote:
> hi
> can i use virtualbox? im finding a lot of people saying it doesnt work
> 
> thanks
> j
> 

Some users have been able to do this, but it is neither recommended nor 
supported. Qubes should be installed bare-metal. (After all, it uses its own 
bare-metal hypervisor!)

https://www.qubes-os.org/doc/user-faq/#can-i-install-qubes-in-a-virtual-machine-eg-on-vmware

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org
-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYW08UAAoJENtN07w5UDAw2oAP/A9OCcliV1erpkjrN1XtGo1w
mG9r6kjCzsIfYUHC5yKNyvf7z8B9eCpZinXkOzOmQkW0Bp6PDp+/4jwfVdTQqGl4
pfNrjWvS4AH4EHMf+ipgQPyeTCMv4NRFJjYG0u7OwuK3u4oBhEmdyv2uImnN3cxY
kiTdtsDHz5mg+f7PBPRptjAL/vo+tOaix15S0y8s41xmne4KXN5f2kwHF08mP25f
dQVZ/e1U2TDAAtUkqyb5up8hSz6xNiEYQeE9B07ek65wk0yrgSrO++XkkaEvY2sk
3mdmR0+dvUi6OhJLiIqBaURFP5iVJ0bgu92JS2f99+8t85Rdzbq6QVRfCGTQQi+1
xT/iMDrvifsdtUtjszy8Wf8v7RS6v8IDU82zqj13Vk0CofKFBg5G3KhSneXeNCEj
F84Kf5yagK8+ybFF0d8Hu4F0uOTUXyQPVBc8iU0C6zUMMoDnAgOmMQSPrfErADYh
O2zsdiUzMquckRFrIp5aPAXi6gf21Q0yv5OYD7PfVVvm9ZnawC5nrZMRemExWp3i
D/+lrUrGqMgzB3uIWTG9iA9/EIR7r6wBr4AZeRvdCVwHCKiBfDwWI2GSug8/R7OT
Il8e285bqUdOSYU+1CiQdoMIvskOLFk/TE2g4vuMJ4XmkKZ/ftLsyFfg814jHtOo
aWYj3+OcOmUbUihDzUOG
=dh9v
-END PGP SIGNATURE-

-- 
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/3cf4d5ba-7bf7-41f7-9828-ab46c5c08861%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Fedora 23 EOL December 20; Update Your Templates!

2016-12-21 Thread raahelps
On Friday, December 9, 2016 at 8:37:19 AM UTC-5, Daniel Moerner wrote:
> Hi all,
> 
> Just a friendly reminder that Fedora 23 End of Life is December 20.[1] You 
> may want to make sure you've updated your templates; there is a guide in the 
> Qubes Documentation.[2]
> 
> I know I don't get to decide what people talk about, but I'd like to ask that 
> people NOT use this thread to rehash the debate about the dom0 distribution. 
> :)
> 
> Best,
> Daniel
> 
> [1] https://fedoramagazine.org/fedora-23-end-of-life/
> [2] https://www.qubes-os.org/doc/template/fedora/upgrade-23-to-24/

jst updated tks for the heads up.

-- 
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/e2ad2626-e5a2-43a4-b5b9-01f21c702fc2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Qubes refuses to boot

2016-12-21 Thread raahelps
On Monday, December 19, 2016 at 2:38:38 PM UTC-5, awesome...@gmail.com wrote:
> On Monday, December 19, 2016 at 12:13:36 AM UTC-5, tai...@gmx.com wrote:
> > Try enabling EFI-CSM mode in your BIOS configuration.
> > 
> > "awesomebunny777" damn thats a cool unique handle, takes me back to the 
> > earlier days of the internet before everyone on a mailing list had both 
> > a first and a last name.
> 
> Yeah, I made it a really long time ago, but I never bothered to make a new 
> one. 
> 
> On Sunday, December 18, 2016 at 7:32:48 PM UTC-5, Chris Laprise wrote:
> > Do you know if your system is set to boot in BIOS or UEFI mode? Maybe 
> > switching to BIOS/legacy mode would help.
> > 
> > Chris
> 
> When I went into my BIOS, I didn't see any option to change the boot mode or 
> legacy any mention of legacy USB. My (pretty old) laptop didn't come with 
> Win8, so I'm not sure it has UEFI firmware. I don't have any problems booting 
> from any other linux distros, as I have set up a dual boot of Win7 and Kali 
> with GRUB on my internal HDD and have a multiboot USB using grub4dos that can 
> boot Debain, Linux Mint, etc. perfectly fine. When I boot the installer, I 
> can see the GRUB menu fine and install it without any problems. It's just the 
> installation drive that will not boot.

maybe a silly question but can you boot another os from usb drive?

-- 
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/0708f15b-bdfb-469b-a38c-cefc52a1be13%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: GRUB fix GUI: Qubes community invitation to the other Linuxes for a collaboration?

2016-12-21 Thread raahelps
On Tuesday, December 20, 2016 at 5:21:07 AM UTC-5, Leeteqxv wrote:
> I have long wondered when the various Linux communities will
>   finally be able to co-operate and make a common solution for
>   having the system fix Grub by itself through a GUI that newcomers
>   have a chance of using without technical knowledge.
> 
> Something like a simple menu with "fix Grub" options like "Update
>   the menu with entries for all the found operating systems."
> 
> 
> 
> See the examples below, they all seem to be of the kind that a
>   system function should be able to provide now in 2016.
> 
> 
> 
> Is this a good moment in history for Qubes to reach out to the
>   other Linuxes and ask for a collaboration to fix this once and for
>   all? It would remove a huge barrier for loads of people wanting to
>   explore the options of getting away from Windows.
> 
> I know this defeats the purpose of the SECURITY aspect of Qubes,
>   but bear with me a moment:
> 
> This is for EVALUATION purposes, for the time where a normal user
>   that runs Windows or the like already without much protection. It
>   is only to provide a testing ground. After a while, the users will
>   familiarize themselves with Qubes and for sure get to understand
>   the Security implications communiacated by the Qubes community and
>   docs. Then, when each user gets ready, it becomes possible to let
>   Qubes take over the whole system and have some serious security.
> 
> But that is not the point at all during evaluation.
> 
> I think we would benefit from lowering the barrier here, to reach
>   critical mass, which could help finance further developments, etc.
>   etc...
> 
> LeeteqXV
> 
> 
> 
> **
> 
> Related thread: "[qubes-users] I recently installed Qubes and I
>   now have several problems"
> 
> 
> 
> "Last night I was able to install Linux Mint beside the other
>   operating systems.  It is not that I wanted to use Mint, it is
>   just that by installing it it redid the GRUB file so now I can
>   boot to Windows 7 or Qubes (or Mint).  So that solves the first
>   problem."
> 
>   
> 
>   "Also, I just realized that I may have the same problem again when
>   I reinstall Qubes; I don't want it to change the GRUB file so that
>   again I can only go into Qubes and not Windows 7.  I guess I will
>   have to study this page [https://www.qubes-os.org/doc/multiboot/]
>   to try to not have that problem repeat."
> 
>   
> 
>   "To triple boot mint, qubes and win 7 with the mint grub.   edit
>   the /etc/grub.d/40_custom file in mint.   append in there
>   everything between the xen sections of the grub.config file
>   located on the qubes boot partition. 
> 
>   Then update grub on mint and reboot and qubes should boot from
>   menu.  You will have to do this everytime qubes updates kernel or
>   it errors again."
> 
> 
> 
> (To view this discussion on the web visit 
> https://groups.google.com/d/msgid/qubes-users/CAEgwnuSSNfbsP2nYfPp24LKwrGpAaho_ddreqL84_q9mPinYBQ%40mail.gmail.com.)
> 
> ***

I'm not sure whty u mean,  but debians installer has a "fix grub" option.  
probably just re installs it.

If mint recognizes qubes then thats awesome.  the xen section I mean is in the 
the qubes grub.config file on the boot partition. 

-- 
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/b785f9b4-6fd2-49b1-8fac-d38b2f4b05ae%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: anybody elses chrome having trouble playing media files at times.

2016-12-21 Thread raahelps
On Tuesday, December 20, 2016 at 9:02:36 PM UTC-5, Patrick Bouldin wrote:
> On Tuesday, December 20, 2016 at 5:46:56 PM UTC-5, raah...@gmail.com wrote:
> > I have to reset preferences.  even deleted the vm it comes back. for 
> > example bandcamp or soundcloud, you click and nothing happens, it 
> > constantly tries to load/play but nothing.  I'm ready to go back to firefox 
> > for a while again but unfortunately firefox don't work fullscreen,  so we 
> > kind of stuck with chrome on Qubes.
> > 
> > I've always switched back and forth over the years on baremetal o/s's.  
> > Sometimes I feel its necessary.
> 
> Question, are you plugging in at the standard mini jack on the machine or are 
> you by chance plugging into the audio jack of an hdmi monitor?  I was using 
> the hdmi monitor and had serious intermittent issues. Once I replugged into 
> the standard audio output it was 100%. Note: I downloaded Google Chrome into 
> the Fedora VM template and run ALL the audio within Chrome. I had problems 
> running some sound out of the other browsers so I just use Chrome now.
> 
> Patrick
> Dallas
standard.  but yes i have not been able to get audio through hdmi either on my 
board to a 2nd monitor.  but I don't need so haven't bothered to tinker further.

but his issue of google ot playing the music from bandcamp.com or soundcloud is 
weird.  I have to go into the googe settings and reset the preferences and then 
it works again.

-- 
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/dba1219d-9920-4bc3-95c0-e966822054fb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: One step foerward, two steps back on Macbook 11,1 - can't boot into Qubes

2016-12-21 Thread dumbcyber
On Wednesday, 16 November 2016 22:52:16 UTC+11, dumbcyber  wrote:
> On Wednesday, 16 November 2016 11:33:03 UTC+11, dumbcyber  wrote:
> > On Tuesday, 15 November 2016 18:14:00 UTC+11, Jean-Philippe Ouellet  wrote:
> > > On Tue, Nov 15, 2016 at 12:17 AM, dumbcyber <> wrote:
> > > > On Tuesday, 15 November 2016 10:28:52 UTC+11, Marek 
> > > > Marczykowski-Górecki  wrote:
> > > >> you need to remove 'rd.qubes.hide_all_usb' from kernel parameters.
> > > >
> > > > Thanks for the info. For me a noob, how do I remove that parameter from 
> > > > kernel?  Thank you.
> > > 
> > > From the installer, use your favorite editor on
> > > /boot/efi/EFI/qubes/xen.cfg to remove just the rd.qubes.hide_all_usb
> > > parameter from the kernel= line. It will probably be at the end of the
> > > line.
> > > 
> > > Note that your EFI partition might be mounted somewhere other than
> > > /boot/efi (I don't remember). The `mount` command should tell you
> > > where. Look for something like:
> > > /dev/nvme0n1p1 on /boot/efi type vfat (rw,relatime,fmask=0077,dmask=...
> > 
> > Thanks for the guide.  My boot64x.cfg does not contain this parameter. Here 
> > is the full CFG file
> > 
> > [global]
> > default=4.4.14-11.pvops.qubes.x86_64
> > 
> > [4.4.14-11.pvops.qubes.x86_64]
> > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
> > kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 
> > root=/dev/mapper/qubes_dom0-root 
> > rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e 
> > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap 
> > i915.preliminary_hw_support=1 rhgb quiet
> > ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img
> > 
> > [4.4.14-11.pvops.qubes.x86_64]
> > options=loglvl=all dom0_mem=min:1024M dom0_mem=max:4096M
> > kernel=vmlinuz-4.4.14-11.pvops.qubes.x86_64 
> > root=/dev/mapper/qubes_dom0-root 
> > rd.luks.uuid=luks-9b163fd2-93d9-4498-a83d-712baae8432e 
> > rd.lvm.lv=qubes_dom0/root rd.lvm.lv=qubes_dom0/swap 
> > i915.preliminary_hw_support=1 rhgb quiet
> > ramdisk=initramfs-4.4.14-11.pvops.qubes.x86_64.img
> > 
> > 
> > Thanks for your help.
> > PS I'm building another Qubes install where I'll uncheck "use sys-usb" 
> > later today
> 
> Finally its working. I rebuilt everything from the beginning making sure 
> sys-usb was unchecked during installation. Qubes boots on the Mac fine - 
> little slow but gets there in the end. I can log, keyboard works. Now the 
> next challenge, getting it networked but thats not for this post. Thanks for 
> your help everyone.


Sorry to revive this thread, but I've been building another Qubes installation 
for someone else. I've run into the same problem - the Macbook Pro keyboard is 
not responsive. I've tried many times during installation to get to the screen 
where I can select/deselect the sys-usb option but do not get it at all!   I've 
already checked if rd.qubes.hide_all_usb is present and its not!  I'm an idiot 
for not writing it down the first time. 

-- 
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/5535afcd-03d8-4592-b379-4bf186ddbaef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Re: Fedora Desktop in Qubes

2016-12-21 Thread Patrick Bouldin
On Wednesday, December 21, 2016 at 6:13:24 AM UTC-5, Patrick Bouldin wrote:
> Hi, I saw some threads on this but am not clear at a high level.
> 
> I thought I would install dropbox client on one of my Fedora VMs so that 
> working with files is much smoother than from a browser. So, is installing a 
> Fedora Desktop the best plan to do that? Don't assume I know enough of native 
> Qubes ability please - maybe I'm missing a key point!
> 
> Thanks,
> Patrick

one day of poking around more, let me just ask this. I looked but could not 
find, is it normal to be able to launch Fedora GNOME inside a Fedora 24 VM? How 
does one do that? I tried StartX... that doesn't work. Do I need to install 
something?

-- 
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/5d0e0554-90ff-484b-88e8-002c4643effb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] config-vm and inter vm file transfer

2016-12-21 Thread Marek Marczykowski-Górecki
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

On Wed, Dec 21, 2016 at 05:35:37PM +, john.david.r.smith wrote:
> what do you think about adding such a `qvm-inter-vm-copy`-command to dom0?
> (the functionality (intervm copy) should mostly already be there).
> 
> Or is there some other/better way?

Few ideas:
1. Implement poor man qvm-inter-vm-copy like this:

qvm-run -p source-vm 'tar c source-file-dir' | qvm-run -p dest-vm
'tar x -C dest-dir'

Better use qfile format instead of tar, to have something even simpler,
but currently qfile-unpacker (equivalent for 'tar x') have hardcoded
QubesIncoming path. In this case it isn't that important because the
transfer is unidirectional, from more trusted to less trusted (at least
I assume that configvm in your case is indeed more trusted, right?).

2. Implement simple service for target VM to ask for specific file/dir from
config VM. This needs to be done carefully, to really allow only
selected file/dir, not anything else. Qrexec service argument could be
used for this. So target VM could download the file
for itself (this can be called from salt, rc.local or anywhere else).

Proof of concept:

configvm:/usr/local/etc/qubes-rpc/local.GetFileDir (executable):

#!/bin/sh

set -e

# allow access only to files/directories in ConfigData directory
cd /home/user/ConfigData

# use tar to handle directories too; $1 is service argument (see
# below); qrexec policy already sanitized '/' and other dangerous
# characters in policy argument, by replacing them with '_'
tar c $1

dom0:/etc/qubes-rpc/policy/local.GetFileDir+somefilename:

# allow transfer of /home/user/ConfigData/somefilename to
# dest-vm
dest-vm configvm allow

# deny transfer somefilename anywhere else (can be omitted, as
# default action is deny)
$anyvm $anyvm deny

dom0:/etc/qubes-rpc/policy/local.GetFileDir:

# deny any call without argument, or with argument not explicitly
# allowed/denied above; without this file, you'd get rather annoying
# prompt to create policy file (but the call would not be allowed
# without your explicit consent)
$anyvm $anyvm deny


dest-vm - retrieve file(s):

# extract to the current directory
qrexec-client-vm configvm local.GetFileDir+somefilename | tar x


You can also go with easier option - creating per-VM directory and
creating a service allowing the transfer of this directory only (instead
of selected one). Basically use $QREXEC_REMOTE_DOMAIN instead of $1 in
the first script. And drop argument (the thing after '+') from policy
and the qrexec-client-vm call.

More details here:
https://www.qubes-os.org/doc/qrexec3/

PS It is not widely known feature that VM's local service files can be
also in /usr/local/etc/qubes-rpc/, not only in /etc/qubes-rpc. In fact
this isn't stable part of the API and can be changed without prior
notice some day (until officially documented). But it will stay there
for now. And looking at 'proposal to move from /rw to /usr/local for new
Qubes developments' proposal on qubes-devel, most likely will eventually
become a stable API.

PPS We've considered thing exactly like this while designing VM
management. Here is (rather unreadable) picture:
https://github.com/QubesOS/qubes-issues/issues/1541#issuecomment-188697805
The service is the arrow at its left edge ;)

- -- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
-BEGIN PGP SIGNATURE-
Version: GnuPG v2

iQEcBAEBCAAGBQJYWycPAAoJENuP0xzK19csKMkH/00wrCT8E6SOZnefbNT2M2Pm
Oh/2vt3Cd0w7BBQuRLWGbN4ESu5bIwzcczFqwOuKq7cR9AROcUOrEGwtKgdL3ro1
P0qLThbx8Eb10fO4LIbakVNKBO5wTTislg/kAnlZv08k8ctUXOXWs5vsRxeJvW9p
7+hygKZ4G8SxWpMfdskWhTNZq2F/V/N/A8sK4sEW1zp43V25uO+peRejM7m4bCUV
3QH0m+o4VDvwzOar6GMxKzm+zSYW9fyLZaCO/S9l5qWGoABjxMRI2qdHcf+SwU0q
DORixdm2G6vUtezJIYO3rM6IAXAj+OgDD0MJz3e9UwFtIZ5vnP87buJp5oBKAcw=
=Z8r3
-END PGP SIGNATURE-

-- 
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/20161222010622.GZ1239%40mail-itl.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] config-vm and inter vm file transfer

2016-12-21 Thread Unman
On Wed, Dec 21, 2016 at 05:35:37PM +, john.david.r.smith wrote:
> hi.
> currently i am configuring salt to create and configure all my vms.
> my target is to have only a minimal set of vms i need to backup (vault,
> config, data, custom systemd based services for my vms) and a set of salt
> files to create my whole setup.
> 
> creating vms and installing software works.
> but for some vms i need additional config data (ssh-keys, openvpn-config
> file, etc).
> I want to store this data in the config vm.
> 
> now i need to get the config data for each vm from my config-vm.
> i have multiple ideas, but i am not satisfied with any:
> 1) run `qvm-copy-to-vm` in config-vm + run some copy commands in the
> target-vm
> 2) get the file to dom0 via `qvm-run --pass-io "cat " > file_in_dom_0` +
> transfer the file to the targetvm
> 3) use managed file from salt
> 
> why i don't like the solutions:
> 1) needs user interaction to allow the transaction or i need to allow all
> file transfers from my config-vm.
> i like neither of these options.
> additionally i need to to issue two commands.
> 2) i don't like the part about transferring anything to dom0.
> also it would be difficult to handle directories.
> 3) i would transfer the files to dom0 (i don't want to do this)
> 
> I am currently searching for a nice way to solve all of this.
> 
> I have an idea but it would require some new functionality (at leas i think
> so).
> 
> in my config-vm i have multiple config folders for each target property
> (e.g. autoshutdown, QubesOutgoing for my own services).
> each folder contains files to copy to /rw)
> in dom0 i would run something like this
> `qvm-inter-vm-copy config-vm:~/autoshutdown/* some-template:/rw/`
> this command would copy all files/directories from ~/autoshutdown/ in
> config-vm to /rw in some-template.
> the command qvm-inter-vm-copy would only be available in dom0, so it would
> not need additional user interaction.
> 
> what do you think about adding such a `qvm-inter-vm-copy`-command to dom0?
> (the functionality (intervm copy) should mostly already be there).
> 
> Or is there some other/better way?
> 
> -john
> 

It's not better but you could do it right now.
A short script that writes to the policy file allowing FileCopy from
config-vm to targets.
qvm-run config-vm 'qvm-copy-to-vm target Dir'
Remove permissive rule from policy file
qvm-run target 'mv .'
salt

-- 
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/20161221234602.GD19689%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Change screen dimension in qubes

2016-12-21 Thread Unman
On Wed, Dec 21, 2016 at 10:18:54AM -, pl1...@sigaint.org wrote:
> > On Sat, Dec 17, 2016 at 11:05:54AM -, pl1...@sigaint.org wrote:
> >> > Hi
> >> > Is there a guide to change screen resolution in qubes? I mean that
> >> > "fingerprint" the sites track and can see on whoer.net
> >> >
> >> > Thank you in advance
> >> >
> >>
> >> Nobody know how do it?
> >>
> > Use xrandr in dom0, or the Display tool from System Settings under the
> > Xfce menu.
> > Either will let you change resolution.
> > qubes started after a change will show the new resolution, so you can
> > run different qubes reporting different screen sizesat the same time if
> > you wish.
> >
> > unman
> >
> Thank you
> Can I create and use a custom resolution for LVDS mode?
> 

Of course, something like this:
Generate a modeline using cvt
cvt 1100 700 60

Paste the modeline to xrandr as a new mode.
xrandr --newmode 

xrandr --addmode LVDS-0 1100x700_60.00

Then apply:
xrandr -s  1100x700







-- 
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/2016122126.GC19689%40thirdeyesecurity.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can I speed up the loading of an APP?

2016-12-21 Thread Patrick Bouldin
On Wednesday, December 21, 2016 at 2:03:15 PM UTC-5, Chris Laprise wrote:
> On 12/20/2016 08:53 PM, Patrick Bouldin wrote:
> > Hi, compared to running a certain app in windows (Anki), installing it in 
> > the Fedora template in Qubes means the first time to run is very slow to 
> > launch. Maybe up to a minute. To install it to the template I just said 
> > "sudo yum install anki"
> >
> > Otherwise, other things running are very fast. If I do launch it manually 
> > from the fedora CLI it's the same slow launch. Maybe it comes down to 
> > compiling it?
> >
> > Thanks,
> > Patrick
> >
> 
> Did you accidentally turn off memory balancing in the Fedora VM? That 
> would slow it down a lot.
> 
> Chris

Hi Chris, well that is a new topic for me, but did some checking. To clarify, 
one would adjust that at the CLI right? A command like "sudo systemctl stop 
qubes-qmemman" ?  If so, I haven't done that. I also see a setting related to 
the memory balancing in the advanced part of the memory allocation, a checkmark 
for "include in memory balancing" - and that is checked, I think it's default.

Is that what you referred to? Incidentally, I've not installed it on the 
template yet, just testing on a created VM until I see it working well.

Thanks,
Patrick
Dallas

-- 
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/17a3372d-c5a3-4f76-9da8-36ef6f1f66c9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Can I speed up the loading of an APP?

2016-12-21 Thread Chris Laprise

On 12/20/2016 08:53 PM, Patrick Bouldin wrote:

Hi, compared to running a certain app in windows (Anki), installing it in the Fedora 
template in Qubes means the first time to run is very slow to launch. Maybe up to a 
minute. To install it to the template I just said "sudo yum install anki"

Otherwise, other things running are very fast. If I do launch it manually from 
the fedora CLI it's the same slow launch. Maybe it comes down to compiling it?

Thanks,
Patrick



Did you accidentally turn off memory balancing in the Fedora VM? That 
would slow it down a lot.


Chris

--
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/114dbf06-cdaf-9db0-7269-4ee4f895db09%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Split GPG: thunderbird+enigmail stopped cache password

2016-12-21 Thread Jean-Philippe Ouellet
On Wed, Dec 21, 2016 at 1:11 PM, Jean-Philippe Ouellet  wrote:
> I have various others in between, such as one with only a browser (for
> online banking and such).

I should clarify, this is a template with only a browser, and an
individual VM used for only online banking. The "and such" each have
their own respective VMs derived from the browser-only template.

-- 
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/CABQWM_D-ynUTMRH42G0vE3%2Bq6Fj6VRr8nF4bgywH8aKf8k_%2BTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Split GPG: thunderbird+enigmail stopped cache password

2016-12-21 Thread Jean-Philippe Ouellet
On Wed, Dec 21, 2016 at 4:20 AM, 'Gaea' via qubes-users
 wrote:
>  Please what are the differences between:
>
> Minimal:

fedora-24-minimal + text editor, openssh, git, zsh, etc.

> Extremely Minimal

fedora-24-minimal + a text editor -- nothing else

> Full ?? VMs

All the crap. Browser, photo editor, media player, all the giant
pieces of software that pull in half the world as dependencies.


I have various others in between, such as one with only a browser (for
online banking and such).

-- 
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/CABQWM_AUjufxnkhR8QrY4sELd63e7qG7PhZejpOzMyYTLygBLw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] config-vm and inter vm file transfer

2016-12-21 Thread john.david.r.smith

hi.
currently i am configuring salt to create and configure all my vms.
my target is to have only a minimal set of vms i need to backup (vault, 
config, data, custom systemd based services for my vms) and a set of 
salt files to create my whole setup.


creating vms and installing software works.
but for some vms i need additional config data (ssh-keys, openvpn-config 
file, etc).

I want to store this data in the config vm.

now i need to get the config data for each vm from my config-vm.
i have multiple ideas, but i am not satisfied with any:
1) run `qvm-copy-to-vm` in config-vm + run some copy commands in the 
target-vm
2) get the file to dom0 via `qvm-run --pass-io "cat " > 
file_in_dom_0` + transfer the file to the targetvm

3) use managed file from salt

why i don't like the solutions:
1) needs user interaction to allow the transaction or i need to allow 
all file transfers from my config-vm.

i like neither of these options.
additionally i need to to issue two commands.
2) i don't like the part about transferring anything to dom0.
also it would be difficult to handle directories.
3) i would transfer the files to dom0 (i don't want to do this)

I am currently searching for a nice way to solve all of this.

I have an idea but it would require some new functionality (at leas i 
think so).


in my config-vm i have multiple config folders for each target property 
(e.g. autoshutdown, QubesOutgoing for my own services).

each folder contains files to copy to /rw)
in dom0 i would run something like this
`qvm-inter-vm-copy config-vm:~/autoshutdown/* some-template:/rw/`
this command would copy all files/directories from ~/autoshutdown/ in 
config-vm to /rw in some-template.
the command qvm-inter-vm-copy would only be available in dom0, so it 
would not need additional user interaction.


what do you think about adding such a `qvm-inter-vm-copy`-command to 
dom0? (the functionality (intervm copy) should mostly already be there).


Or is there some other/better way?

-john

--
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/24804f51-5109-95c4-a09a-2f3d8904b661%40openmailbox.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes and Broadcom BCM4360 - A Success Story

2016-12-21 Thread Kent Davis
Maybe you could use sleep, e.g., sleep 30 at the beginning of your
rc.local? kinda hacky though...

On Wed, Dec 21, 2016 at 9:58 AM, Dave Cohen  wrote:
>
>
> On Wed, Dec 21, 2016, at 08:53 AM, Kent Davis wrote:
>> I'm not certain, but based on when wireless comes up, I think it runs
>> towards the end of the boot process.
>>
>
> I mean rc.local.  Can I put some instruction in there and make sure it is 
> performed at the very end of startup?

-- 
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/CADbtXuCHiN0tGHGcsgBEs%2B8%2BZum-8Luzo%2Bcf6h3z5vezb%2ByQ3w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes and Broadcom BCM4360 - A Success Story

2016-12-21 Thread Dave Cohen


On Wed, Dec 21, 2016, at 08:53 AM, Kent Davis wrote:
> I'm not certain, but based on when wireless comes up, I think it runs
> towards the end of the boot process.
> 

I mean rc.local.  Can I put some instruction in there and make sure it is 
performed at the very end of startup?

-- 
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/1482339516.4028111.826120297.211DB97F%40webmail.messagingengine.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes and Broadcom BCM4360 - A Success Story

2016-12-21 Thread Kent Davis
I'm not certain, but based on when wireless comes up, I think it runs
towards the end of the boot process.

On Wed, Dec 21, 2016 at 9:52 AM, Dave C  wrote:
> On Wednesday, December 21, 2016 at 8:47:49 AM UTC-8, Kent Davis wrote:
>> My solution involves directly modifying the sys-net VM and I handle
>> all the modules in sys-net:/rw/config/rc.local.
>>
>> Is your rc.local executable?
>>
>
> It is:
>
> [user@net-powerbook24 ~]$ ls -l /rw/config/rc.local
> -rwxr-xr-x 1 root root 523 Dec 18 15:57 /rw/config/rc.local
>
> And I had a simple rc.local working for earlier version of fedora.  But with 
> 24, there are conflicting modules and I haven't managed to get it right.
>
> I'm wondering when rc.local is executed during startup, and whether I need to 
> explicitly wait for other startup to complete.  As I mentioned, my script 
> works only after startup, when I manually run in a terminal.
>
> -Dave
>
> --
> 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/VVwWqvz5dX4/unsubscribe.
> To unsubscribe from this group and all its topics, 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/ee19bba7-99dc-4b65-ba66-8f09d9ef588f%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

-- 
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/CADbtXuCaxtU9XW--HoYEXfnUJ7hNS%2B4FGNLrZoOrjsbYPXth%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes and Broadcom BCM4360 - A Success Story

2016-12-21 Thread Dave C
On Wednesday, December 21, 2016 at 8:47:49 AM UTC-8, Kent Davis wrote:
> My solution involves directly modifying the sys-net VM and I handle
> all the modules in sys-net:/rw/config/rc.local.
> 
> Is your rc.local executable?
> 

It is:

[user@net-powerbook24 ~]$ ls -l /rw/config/rc.local
-rwxr-xr-x 1 root root 523 Dec 18 15:57 /rw/config/rc.local

And I had a simple rc.local working for earlier version of fedora.  But with 
24, there are conflicting modules and I haven't managed to get it right.

I'm wondering when rc.local is executed during startup, and whether I need to 
explicitly wait for other startup to complete.  As I mentioned, my script works 
only after startup, when I manually run in a terminal.

-Dave

-- 
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/ee19bba7-99dc-4b65-ba66-8f09d9ef588f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Qubes and Broadcom BCM4360 - A Success Story

2016-12-21 Thread Kent Davis
My solution involves directly modifying the sys-net VM and I handle
all the modules in sys-net:/rw/config/rc.local.

Is your rc.local executable?

On Wed, Dec 21, 2016 at 9:37 AM, Dave C  wrote:
> Since starting this thread, I've (belatedly) upgraded to Qubes 3.2.  In doing 
> so, I never figured out how to get the old kernel for which I compiled the wl 
> module to migrate over to the new install.  Unfortunately a VM's kernel is 
> not included when backing it up.
>
> Anyway, I thought of that as an excuse to upgrade my net vm for broadcom to 
> the latest version of fedora.  Unfortunately things are not working 100%.  So 
> while I've made progress, this is actually a call for help to get things 
> working on fedora 24.
>
> # Give the PCI Device Permissive Passthrough (on dom0)
>
> https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues
>
> My /etc/systemd/system/qubes-pre-netvm.service ended up like this:
>
> ```
> [Unit]
> Description=permission pci netvm fixup
> Before=qubes-netvm.servce
>
> [Service]
> Type=oneshot
> RemainAfterExit=yes
> ExecStart=/bin/sh -c 'echo ":03:00.0" > 
> /sys/bus/pci/drivers/pciback/permissive'
>
> [Install]
> WantedBy=multi-user.target
> ```
>
> # Preparation to compile modules
>
> Start a VM running same template and kernel version that your netvm
> will use.  This can be a dispvm.
>
> From 
> https://www.broadcom.com/support/download-search/?pf=Wireless+LAN+Infrastructure
>
> Move tarball to that vm (if not there already) and extract with
>
> ```
> tar xvzf hybrid-v25_64-nodebug-nopcoem-6_30_223_271.tar.gz
> ```
>
> Conveniently the README is not included.  You might find it at
> https://docs.broadcom.com/docs/1211168561592, a link which will soon
> be just as broken as all its predecessors scattered all over the
> internet.
>
>
> ## Compile the modules
>
>
> ```
> # Install kernel-devel that matches running kernel!
> sudo yum install "kernel-devel-uname-r == $(uname -r)"
>
> # I think necessary (?)
> sudo modprobe cfg80211
>
> # possibly necessary (?)
> sudo yum install gcc
>
> # Finally
> make
> ```
>
> ## Install
>
> I compiled in a dvm, so my install procedure was...
>
> First, on the dvm where I compiled:
>
> ```
> # Copy the built module
> qvm-copy-to-vm net-powerbook24 wl.ko
>
> # Find out what the install command will be.  Note -n will not actually 
> install.
> make -n install
> ```
>
> Now we can use the command shown by `make -n install` earlier, in the new net 
> vm (net-powerbook24 in my case).
>
> ```
> install -D -m 755 QubesIncoming/disp2/wl.ko /lib/modules/`uname 
> -r`/kernel/drivers/net/wireless
>
> # This is documented in the readme, but not done by the install command.
> depmod -a
> ```
>
> But we want the module to be loaded automatically when the netvm starts.  
> This is the part I'm having trouble with!  If anyone can suggest a better 
> way, please let me know.
>
> Start by using Marek's technique for custom modules.  
> (https://groups.google.com/forum/#!msg/qubes-users/Wt9Nm7posho/msTN_v2oa_oJ)
>
> I've been experimenting with what to put in /rw/config/rc.local.  What I have 
> at the moment is shown below.  But here's the problem...
>
> When first starting the netvm, it does not successfully use the wifi.  
> However, if I manually open a terminal and run `sudo /rw/config/rc.local` 
> then it will be able to connect to wifi.  So, something about this script is 
> working, but not working on initial vm startup!
>
> I have the following in /rw/config/rc.local:
>
> ```
> # Unload conflicting modules.
> rmmod ssb
> rmmod bcma
> rmmod b43
> rmmod brcmsmac
> rmmod wl
>
> # blacklist modules that may interfere with wl (broadcom)
> # (Not convinced these actually prevent the modules from loading!)
> echo "blacklist ssb" >> /etc/modprobe.d/blacklist.conf
> echo "blacklist bcma" >> /etc/modprobe.d/blacklist.conf
> echo "blacklist b43" >> /etc/modprobe.d/blacklist.conf
> echo "blacklist brcmsmac" >> /etc/modprobe.d/blacklist.conf
>
> mount --bind /rw/modules /lib/modules
> systemctl restart systemd-udevd
>
> modprobe wl
> ```
>
> ...and make that rc.local executable.
>
> I've tried various experiments. I've changed the order in that script of when 
> I remove conflicting modules.  Nothing I've tried makes that script work 
> successfully on startup.  I suspect that conflicting modules are loaded 
> despite my attempt to blacklist them.  But when I run the script manually in 
> a terminal, it works as hoped, and I can connect to wifi.  As I said earlier, 
> I'd appreciate any help!
>
> --
> 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/VVwWqvz5dX4/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to 
> qubes-users+unsubscr...@googlegroups.com.
> To post to this group, send email to qubes-users@googlegroups.com.
> To view this 

[qubes-users] Re: Qubes and Broadcom BCM4360 - A Success Story

2016-12-21 Thread Dave C
Since starting this thread, I've (belatedly) upgraded to Qubes 3.2.  In doing 
so, I never figured out how to get the old kernel for which I compiled the wl 
module to migrate over to the new install.  Unfortunately a VM's kernel is not 
included when backing it up.

Anyway, I thought of that as an excuse to upgrade my net vm for broadcom to the 
latest version of fedora.  Unfortunately things are not working 100%.  So while 
I've made progress, this is actually a call for help to get things working on 
fedora 24.

# Give the PCI Device Permissive Passthrough (on dom0)

https://www.qubes-os.org/doc/assigning-devices/#pci-passthrough-issues

My /etc/systemd/system/qubes-pre-netvm.service ended up like this:

```
[Unit]
Description=permission pci netvm fixup
Before=qubes-netvm.servce

[Service]
Type=oneshot
RemainAfterExit=yes
ExecStart=/bin/sh -c 'echo ":03:00.0" > 
/sys/bus/pci/drivers/pciback/permissive'

[Install]
WantedBy=multi-user.target
```

# Preparation to compile modules

Start a VM running same template and kernel version that your netvm
will use.  This can be a dispvm.

>From 
>https://www.broadcom.com/support/download-search/?pf=Wireless+LAN+Infrastructure

Move tarball to that vm (if not there already) and extract with

```
tar xvzf hybrid-v25_64-nodebug-nopcoem-6_30_223_271.tar.gz
```

Conveniently the README is not included.  You might find it at
https://docs.broadcom.com/docs/1211168561592, a link which will soon
be just as broken as all its predecessors scattered all over the
internet.


## Compile the modules


```
# Install kernel-devel that matches running kernel!
sudo yum install "kernel-devel-uname-r == $(uname -r)"

# I think necessary (?)
sudo modprobe cfg80211

# possibly necessary (?)
sudo yum install gcc

# Finally
make
```

## Install

I compiled in a dvm, so my install procedure was...

First, on the dvm where I compiled:

```
# Copy the built module
qvm-copy-to-vm net-powerbook24 wl.ko

# Find out what the install command will be.  Note -n will not actually install.
make -n install
```

Now we can use the command shown by `make -n install` earlier, in the new net 
vm (net-powerbook24 in my case).

```
install -D -m 755 QubesIncoming/disp2/wl.ko /lib/modules/`uname 
-r`/kernel/drivers/net/wireless

# This is documented in the readme, but not done by the install command.
depmod -a
```

But we want the module to be loaded automatically when the netvm starts.  This 
is the part I'm having trouble with!  If anyone can suggest a better way, 
please let me know.

Start by using Marek's technique for custom modules.  
(https://groups.google.com/forum/#!msg/qubes-users/Wt9Nm7posho/msTN_v2oa_oJ)

I've been experimenting with what to put in /rw/config/rc.local.  What I have 
at the moment is shown below.  But here's the problem...

When first starting the netvm, it does not successfully use the wifi.  However, 
if I manually open a terminal and run `sudo /rw/config/rc.local` then it will 
be able to connect to wifi.  So, something about this script is working, but 
not working on initial vm startup!

I have the following in /rw/config/rc.local:

```
# Unload conflicting modules.
rmmod ssb
rmmod bcma
rmmod b43
rmmod brcmsmac
rmmod wl

# blacklist modules that may interfere with wl (broadcom)
# (Not convinced these actually prevent the modules from loading!)
echo "blacklist ssb" >> /etc/modprobe.d/blacklist.conf
echo "blacklist bcma" >> /etc/modprobe.d/blacklist.conf
echo "blacklist b43" >> /etc/modprobe.d/blacklist.conf
echo "blacklist brcmsmac" >> /etc/modprobe.d/blacklist.conf

mount --bind /rw/modules /lib/modules
systemctl restart systemd-udevd

modprobe wl
```

...and make that rc.local executable.

I've tried various experiments. I've changed the order in that script of when I 
remove conflicting modules.  Nothing I've tried makes that script work 
successfully on startup.  I suspect that conflicting modules are loaded despite 
my attempt to blacklist them.  But when I run the script manually in a 
terminal, it works as hoped, and I can connect to wifi.  As I said earlier, I'd 
appreciate any help!

-- 
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/f191cec7-3514-427f-9e78-3ec066b9cec8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


RE: RE: Re: [qubes-users] RE: Thinkpad p50: Qubes installs but won't boot

2016-12-21 Thread 5nh54b+1lzuncok348sg via qubes-users
In the end, I made it work and Qubes boots now on the P50. It's taken way more 
effort than I'd have thought though, but the cause was my lack of knowledge on 
how to get there; the necessary changes were in the Documentation.

In case anyone else hits a similar wall with a P50 in the near future, the 
missing part for me was the boot device not being recognized [1]. The detail 
that may not be super well explained in the documentation (probably because its 
too basic) is that in order to cp and mv the necessary files we need to access 
the LUKS partition by using the Qubes installation device and selecting the 
*repair* option. As I explained in a previous email, I had tried to do this 
before through a Lubuntu LiveCD and couldn't get access (Lubuntu said 
unreadable).

Now that it boots and seems that at least the basics work, I will look into any 
hardware issues.

[1] 
https://www.qubes-os.org/doc/uefi-troubleshooting/#boot-device-not-recognized-after-installing






Sent using Guerrillamail.com
Block or report abuse: 
https://www.guerrillamail.com/abuse/?a=UFR2AB5NVqcQmh2U93EQdRjCStifx8dDiadNcQ%3D%3D


-- 
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/53e81ebd707228792241efb46c0d61a1ab9%40guerrillamail.com.
For more options, visit https://groups.google.com/d/optout.


[qubes-users] Fedora Desktop in Qubes

2016-12-21 Thread Patrick Bouldin
Hi, I saw some threads on this but am not clear at a high level.

I thought I would install dropbox client on one of my Fedora VMs so that 
working with files is much smoother than from a browser. So, is installing a 
Fedora Desktop the best plan to do that? Don't assume I know enough of native 
Qubes ability please - maybe I'm missing a key point!

Thanks,
Patrick

-- 
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/481ebd07-9d6c-4323-bd01-e113ef839fc9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Change screen dimension in qubes

2016-12-21 Thread pl11ty
> On Sat, Dec 17, 2016 at 11:05:54AM -, pl1...@sigaint.org wrote:
>> > Hi
>> > Is there a guide to change screen resolution in qubes? I mean that
>> > "fingerprint" the sites track and can see on whoer.net
>> >
>> > Thank you in advance
>> >
>>
>> Nobody know how do it?
>>
> Use xrandr in dom0, or the Display tool from System Settings under the
> Xfce menu.
> Either will let you change resolution.
> qubes started after a change will show the new resolution, so you can
> run different qubes reporting different screen sizesat the same time if
> you wish.
>
> unman
>
Thank you
Can I create and use a custom resolution for LVDS mode?

-- 
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/44cf8adbabdebd1c3569c69c60a06e2f.webmail%40localhost.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Split GPG: thunderbird+enigmail stopped cache password

2016-12-21 Thread 'Gaea' via qubes-users
 Please what are the differences between:

Minimal:
Extremely Minimal
Full ?? VMs

Jean-Philippe Ouellet:
> On Tue, Dec 20, 2016 at 3:08 PM, 5n7xyb+qphld0j5ytif4l via qubes-users
>  wrote:
>> I also don't want to remove the password from my private key since I used it 
>> in different devices and I don't want to use a different template as I have 
>> many things installed on my debian 8 template.
> 
> Using a separate (minimal) template may be a good idea regardless
> simply to reduce the number of things which must be trusted to not be
> actively malicious in order to maintain the confidentiality of your
> pgp key.
> 
> I have several templates ranging from "extremely minimal" to "kitchen
> sink" for exactly this reason, and would recommend the practice for
> its own merit regardless of split-gpg / enigmail / whatever.
> 

-- 
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/aa646755-fc48-5cda-74f2-ce8c3f5f6140%40lelantos.org.
For more options, visit https://groups.google.com/d/optout.


Re: [qubes-users] Re: Screensavers : Qubes Questions!

2016-12-21 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Hi Mike,

Would you please read through our mailing list guidelines?

https://www.qubes-os.org/mailing-lists/

Specifically, please avoid top-posting. Instead, reply interleaved or
bottom-post. This helps keep the mailing lists more organized. Thanks!

On 2016-12-20 15:57, Mike Mez wrote:
> "I understand your position. At this point, I think you should
> read, learn, and try (i.e., download, install, and use) as much as
> you can about your viable options to figure out which solution is
> right for you.
> 
> While there is a fair amount of code and functionality that is
> unique to Qubes, knowledge of Linux and Xen would still be very
> helpful. Really, though, if you just want to try Qubes out, it
> shouldn't be necessary to learn Linux or Xen at all. If you run
> into any problems, some basic familiarity with the command-line
> will help, though."
> 
> So nothing too crazy advanced then? Alright, when the time comes
> I'll give it a shot. As it is right now, it seems on all the
> Distro/VM combinations I've found and looked into I have to figure
> out how to do the GPU pass through so that I can use the CPU/GPU
> intensive programs I wish to use off of the windows kernel. Having
> Xen as a core base just helps me skip a step or two.
> 

I think that, at this point, users with a pure Windows background can
transition fully to Qubes, as long as they possess the qualities I
mentioned to a sufficient degree. :)

> "Fair warning, though: If you do decide to go with Qubes and
> attempt to do DIY GPU passthrough, that's likely to be *much* more
> challenging from a technical perspective (though generous users
> have provided detailed guides on this list already). You should
> also be aware that it inherently comes with significant security
> trade-offs."
> 
> I would say that goes without saying, as such is one of the
> eternal struggles of security. When one fights monsters..., yet
> with out the ability to do my job, hobby, ... I want to say or
> simply pass the time, yet that would be different... so. If I can't
> do what I must, why have it? Yet I like the added security, it's a
> nice feature to have on the side, as security isn't my main deal.
> What I do isn't exactly a threat unless suddenly I work under a
> government that is a fan of 1984 Grey on all the things. Oh my.
> Such a task. I guess once you start doubting you never stop.
> 

Well, it's not necessarily an all-or-nothing matter. For example, I
have a separate (untrusted) machine with baremetal Windows 10
installed just for media and gaming, while I do all of my serious work
on my physically distinct Qubes machines. Granted, this entails a
greater investment in hardware, but it doesn't have to break the bank
if you build your own PCs.

This way, I don't have to worry that Windows 10 infantilizes its users
by removing all choice and control over fundamental things like
whether the operating system uploads data from your local machine to
Microsoft's servers, since I have nothing important on there anyway. I
also enjoy having baremetal performance when it comes to any kind of
competitive gaming (though, admittedly, I haven't analyzed any
benchmarks on the magnitude of the overhead entailed by running games
in Windows on top of Xen).

> Well, I suppose if I do come across an error or an issue about GPU
> pass trough, I'll email "qubes-users" and hopefully be able to come
> up with a solution. It may be technically over my head, way over in
> fact currently. Yet Microsoft's actions with 10, that they have
> also pushed into 8 & 7, just. Ugh.
> 
> Thank you once again,
> 
> - Mike Mez
> 
> On Tue, Dec 20, 2016 at 4:04 AM, Andrew David Wong
>  wrote:
> 
> On 2016-12-19 16:29, Mike Mez wrote:
 Wow! I wasn't actually expecting my "dream" scenario to be
 so possibly ... probably ... maybe in fact viable. I
 understand that since the main focus in Qubes early stages
 (or perhaps it's far more proper to say at whole,) is
 security that this is what your main marketing point would
 be. Yet with the "windows integration", if I understand this
 properly, is a big deal. I mean shoot, the only reason (the
 only reason?) people use windows now a days is its entrenched
 ubiquitous nature. Shoot, as mentioned the only reason I
 use(d) it is because that is what the programs I use... use.
 So the ability to co-op that... am I over thinking this? It 
 just sounds cool to me.
 
 "It depends highly on the individual, but if you're coming
 from a purely Windows background, the biggest thing might be
 adjusting to a Linux environment. In general, the most
 important qualities will be perseverance, a willingness to
 learn, and the ability to solve your own problems. (Of
 course, the mailing lists are here to help, but things
 generally don't work very well if someone makes no effort and
 expects to be spoon-fed 

Re: [qubes-users] Re: Unable to install qubes... (Intel GTX 970 problem)

2016-12-21 Thread Andrew David Wong
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

On 2016-12-20 17:28, Rob wrote:
> Hi Andrew,
> 
> That is great, I am getting further.  I now know to investigate the
> Fedora text based installer (Anaconda). I would be happy to try and
> report back on the Fedora bare metal install, as my laptop is new
> and has nothing on it yet (hopefully Qubes soon). Do you happen to
> know what version of Fedora is used for Qubes 3.2?  - as I have 
> successfully installed Fedora 25 Workstation (which is the latest),
> but I am guessing Qubes uses an older build.
> 

Qubes 3.2 uses Fedora 23 in dom0.

> Ideally, I would like to install Qubes-OS latest version (not sure
>  when v4 will be released). Pretty sure the reason why my laptop is
>  having installation issues, is that it has an Nvidia GPU and until
>  the installation is successful, I can then try to install the 
> Nvidia drivers onto Dom0.
> 

No official ETA on Qubes 4.0 yet. Best guess is that the first release
candidate might appear in Q1 2017.

> The guide does not say much at all about the installation (unless 
> the GUI installation asks no questions and just works).  All I am 
> saying is it looks like the installation can be hit or miss, so I 
> am surprised that there is not a guide for those more complex 
> installs, as opposed to the easiest install, where there are no 
> issues anyway. I will be happy to assist in getting a basic guide 
> written, once I can get Qubes installed.  - This can then get 
> fleshed out with further input from others.
> 

I see what you're saying. Yes, I think it's difficult to write a guide
that covers the unusual hardware compatibility issues that people run
into, since it can be hardware-specific. It would be great if you could
help us improve the documentation in this regard. Thank you for your
willingness to help!

> Previously to this post, I was just Googling for clues to help me 
> install Qubes, however, I am now subscribed to this "Qubes-Users" 
> group and I can now see that there is a lot of activity. Although,
> my initial comment regarding development was more regarding the
> installation side of the OS.  As it does (to me) appear to be
> lacking, compared to other Distro's slick installation.  I am
> guessing this is more to do with the incorporation of strict
> security and the inclusion of Xen.
> 

I understand. That's probably true.

- -- 
Andrew David Wong (Axon)
Community Manager, Qubes OS
https://www.qubes-os.org

-BEGIN PGP SIGNATURE-

iQIcBAEBCgAGBQJYWkBGAAoJENtN07w5UDAw9vgQAJab2enX6qdjjWRzyukyXAB4
KsEoDjK7JC2tdcZfUEyAgW00bsQctEPiq7WQBPmj6Z6Q3CstOjE7rUNJ9rW0ee2J
qbv3NO07crbyaG/PoC+vdtpcn0Ph41sBw/I4evz5ajdKch5j0aMxNlvWmu+WPtqy
4dlhkmiTbP4pr6K4Ogzjz35rD9abMtBKhn+0f3WVJeTT9w2y5OeTY+a8nQqNDP0s
iliNam1mgrWzgDIAe8VkuJtwigChFMhz6Z0r2nzq7fkoZZ5cpgfmdgYiQSMw5Eok
RQx2W+d+7uoKccHY+8z6D/OMfXH9SYXNFQp7iXtm0lCf5PCunIclgSOV4akg1Su9
VQCN02GvrOHgOdQCp0iHc6h3leUUJAwZZxe7ponD9oWfNGSCy+npaKKJASJ4vcf9
fYBw3jb1rWA+cg2YRm2F+qHzER9DlQMtJMQMbgpDn7jchBCPBNb2IXrlAllcfpWd
KoRBPp+Rg+PDdyA/ztdEc0WBTqV2hsoUGV5S4nAZwmrlAintn+T+Ph3j4Vxj+K5s
wbhsxw+JEB+bZNFaKk9njWG+49WYtDvihgSNjUlMPVo8+ICOup5M86oo5vnm3Xh6
708bVIpwivN1FBMCAP3F0FQ+oAb5L5SO+CITjUrOWn6lK20MkbTE9tiVOMhnZHAf
yCi0FvefoBinXfSvUQ6q
=uZh4
-END PGP SIGNATURE-

-- 
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/47b69a42-22db-9791-f649-1466548be521%40qubes-os.org.
For more options, visit https://groups.google.com/d/optout.