[qubes-users] Re: Yubikey init failed PCSCD

[Robin Lambertz]

On 02/16/2017 12:30 AM, bbrr3...@gmail.com 
wrote:


I've been able to use my Yubikey 4 on a debian 8 qube successfully. (Remember 
to patch the libccid_Info.plist). Might be worth giving it a try?



Hi,

What did you patch exactly ?

I found out after some fumbling around that the yubikey works perfectly 
well if I don't use qvm-usb, and instead assign the entire USB bus to 
the guest VM. My understanding is that this is less secure and opens me 
up to DMA attacks. It's also a lot less flexible. After digging around, 
I found out that qvm-usb uses qubes-usb-proxy[0], which seems to be the 
party at fault here.


I tried using usbmon and wireshark to find out more. The logs of the 
guest and host are attached (they log the same session). Clearly, the 
usb doesn't seem to answer in time to the Get Slot Status request. It 
looks like it times out after 100ms in both the guest and the host. Is 
it possible that the USB proxy would add latency, causing the timeout ? 
Should I try to increase the timeout in the PCSC software ?	


I also have made another wireshark log of what happens in sys-usb when 
accessing the yubikey directly from there (The scenario where the 
yubikey works) in case that's useful.


Thanks for the help,

Robin Lambertz

[0]: https://github.com/QubesOS/qubes-app-linux-usb-proxy

--
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/o847r7%24u2m%241%40blaine.gmane.org.
For more options, visit https://groups.google.com/d/optout.


host.pcap
Description: application/vnd.tcpdump.pcap


host_direct_access.pcap
Description: application/vnd.tcpdump.pcap


guest.pcap
Description: application/vnd.tcpdump.pcap

[qubes-users] Re: nouveau driver minor screen tearing advice

[Nautilus Maximus]

On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> Hi all, 
> I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> tearing with the nouveau driver. I've looked through the threads, most are 
> for the older version of qubes or installing propriety drivers. For me it's 
> not a major issue just an annoyance especially watching videos etc. Disabling 
> composition doesn't work for me unfortunately. Thanks for you time and 
> support.

I have installed chrome, the screen tearing issue is still occurring. 
performance of chrome is better as there is less stuttering.  

-- 
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/0a19eabc-019d-4558-9567-4d3784ff30b7%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Certified Hardware - Why purism and not system76 or thinkpenguin?

[taii...@gmx.com]

Purism is selling snake oil and taking money away from the honest 
companies that admit they're selling a re-badged quanta laptop that will 
never ever have libre firmware.


Here is a reddit post with more info about the situation (yeah its from 
leah but whatever its true)

https://www.reddit.com/r/linux/comments/3anjgm/on_the_librem_laptop_purism_doesnt_believe_in/

https://www.qubes-os.org/doc/certified-laptops/
"In addition, the Qubes team will receive a small portion of the revenue 
from any Librem 13 sale that comes with Qubes pre-installed."

The man that is always behind the curtain.
Does one have to pay to be included on this list? how much? how come 
real libre computer sellers like gluglug and raptor engineering aren't 
listed on here?


If you want to be honest there are only two boards in the world period 
that check all the qubes 4.0 boxes, the KCMA-D8 and the KGPE-D16 both of 
which are legitimately libre blob free and also have a user configurable 
TPM CRTM which is very important if you don't want your TPM to be 
predictable.


Instead of putting in actual effort to make a real libre laptop with a 
few ARM cpus, maybe an AMD FM2 (FM2+ has PSP) or something like that 
they instead are satisfied "making" crappy quanta rebrands, taking 
credit for other peoples work and acting like buying unfused cpus is a 
revolutionary act.


The simple fact of the matter is that if google can't convince intel to 
hand over the ME code, the FSP code, the VGA BIOS and the signing keys 
for all of those then a small company with a 160K crowdfunding campaign 
won't ever be able to do that, and even if google somehow did the 
impossible it would apply to every intel device and not just theirs thus 
making a purism purchase absolutely pointless.


--
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/1d7a5c15-e72c-fed8-253d-27b06ca725c3%40gmx.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] what is better - btrfs or ssd cache w/ qubes? (was qubes partitioning questsion)

[Oleg Artemiev]

Okay, just to make a reference in the mailing list I'm replying w/
extra details found by quickly digging the net. Hope it will be useful
to someone.

>> Use btrfs instead of LVM. That way you can do subvolumes.
>> Is btrfs is stable enough?
> I've reviewed some user notes on btrfs and found it has some disadvantages:
>
> 1. fsck is not aware of btrfs and occasional run by hands of fsck on
> btrfs may lead to partition corruption.
> 2. It stores some extra info for each file, so volumes w/ a lot of
> smal files appear to use more space than on ext3/ext4
seems not very actual - vms are usually fat enough )
 .
> 3. tools for btrfs are still in active development, so I should be
> careful to never appear to be using an alfa- or betta- grade versions
> if I
> want to be sure all is sage enough. I even consider for myself ext4 is
> not stable enough compared to ext3. btrfs is one year younger than
> ext4
Also I wonder is this is still actual in some way after 6 years of
development: https://lkml.org/lkml/2010/6/18/144 ? ?-)

> BTW.
> If I enable Qubes development repositories - how can I ensure that
> btrfs tools never get newer than I want?
> BTW - to the moment I don't understand - is it possible to tune btrfs
> in such a way, when it will use most oftenly writed meta data stuff
> via  hdd only?
> I.e /dev/sda is hdd , sdb is ssd - is it possible to create a btrfs
> partition that will put its metadata on ssd
Found answer on this:

mkfs.btrfs -m single /dev/sdc -d raid0 /dev/sdb /dev/sdd

metadata will be created on sdc only , data in raid 0 on sdb and sdd.

Though w/ that to avoid 'btrfs device scan' on each start we have to
specify device list in fstab like that:
/dev/sdb /mntbtrfs
device=/dev/sdb,device=/dev/sdc,device=/dev/sdd,device=/dev/sde
that seem to be not a problem.

I guess it's okay to use partitions, not entire disk drives and make
combination of partitions w/ diffrent stability level, I.e. use raid1
for both data and metadata with partitions used to store gpg appVMs
and
less safe configuration for other app/template VMs :)

Also it looks that raid0 configuration is some times dangerous:
"It is not possible to use a volume in degraded mode if raid0 has been
used for data/metadata and the device had not been properly removed
with btrfs device delete"
" The situation is even worse if RAID0 is used for the the metadata:
trying to mount a BTRFS volume in read/write mode while not all the
devices are accessible will
simply kill the remaining metadata, hence making the BTRFS volume
totally unusable."
"The situation is no better if you have used RAID1 for the metadata
and RAID0 for the data, you can mount the drive in degraded mode but
you will encounter problems while accessing your files"

the most detailed practice howto I've found is there:
http://www.funtoo.org/BTRFS_Fun

So looks like a good choice. Thanks for advice. :)


>> Separation below is due to faster reads from ssd . Also ssd drives degrade
>> in terms of stability if writes are made too often . Thus I want separate
>> app VM /template VM storage - template VMs are changed rarely. BTW - I'm not
>> sure where temporary images are stored when Qubes starts an App VM. The idea
>> is get most reads from ssd and most writes to hdd.
> This is noted here:
> https://groups.google.com/forum/#!topic/qubes-devel/hG93VcwWtRY and
> (today/yesterday) in reply to similar quesion around Subj in
> qubes-developers:
> https://groups.google.com/forum/#!topic/qubes-devel/wfqKiOYgV8Y
Also there's a howto on adding ssd cache to Qubes here:
https://groups.google.com/forum/#!msg/qubes-users/ArHTEeQAH8A/r9zzY0DLBQAJ
(breaks AntiEvilMade) - this seem to utilize
lvm caching abilities.

I'm not sure though what is better, but from my point of view there're
3 options:

1  classic LVM
1.1) use classic lvm setup w/o ssd cache, when encryption is done on
physical volume level - shouldn't 've interference w/ anti-evil-maid
1,2) same as 1, but use encryption on logical volume level
which is better?

2) use lvm w/ ssd cache - breaks current implementation of anti evil
made, faster reads, but keeping ssd in healthy state by as much as
possible avoiding writes to it seem to be questionable for me.
3) use lvm physical volumes as encryption provider and btrfs for
everything upper than physical volume and tune it to write metadata to
hdd only .
4) avoid lvm, use luks on physical partitions like /dev/sda5 /dev/sdb4
and use them as an encription provider for btrfs as in 3.
5) avoid luks use older methods to provide physical device enrcryption
for btrfs (cryptoloop/loop-AES/...).

As noted in https://help.ubuntu.com/community/EncryptedFilesystemHowto7:
The old cryptoloop / bare dm_crypt scheme provides exactly the same
encryption algorithms and security level. The only difference is that
LUKS is easier to manage, and allows multiple access keys per
partition.

With the old format, no configuration header is embedded in an
encrypted partition. It does not even store a 

[qubes-users] Re: nouveau driver minor screen tearing advice

[Grzesiek Chodzicki]

W dniu niedziela, 19 lutego 2017 02:51:17 UTC+1 użytkownik Nautilus Maximus 
napisał:
> On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> > Hi all, 
> > I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> > tearing with the nouveau driver. I've looked through the threads, most are 
> > for the older version of qubes or installing propriety drivers. For me it's 
> > not a major issue just an annoyance especially watching videos etc. 
> > Disabling composition doesn't work for me unfortunately. Thanks for you 
> > time and support.
> 
> Yeah it is plugged into the 770, I tried to over complicate things. 
> Everything displays fine it's just the minor tearing when moving windows and 
> watching youtube, netflix etc. For me it's not a major issue and I am quite 
> happy with Qubes as a daily diver. It kind of reminds me of using the old 
> legacy windows 98 preformance wise. Is it an acceleration/buffering issue and 
> is their a way to fix it? I don't know the platform is so new and the 
> community is so few. I don't want to install nvidia because a dom0 update in 
> the future might break the os.

Dunno about the interface but youtube plays much more smoothly to me in Chrome 
than in Firefox so maybe try switching browsers? As for the acceleration 
issues, this more of a nouveau issue than Qubes issue, nouveau drivers are much 
slower than their proprietary counterparts.

-- 
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/4e0d919d-629d-4838-a3c7-3a7e9b6a4a3d%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: efi_memmap problem powering off.. coldhak paxtest fail

[cesecurenj]

On Friday, February 10, 2017 at 8:25:49 PM UTC-5, cesec...@gmail.com wrote:
> Hello, i have qubes 3.2 installed with 4.4.38-11 kernel. Install went fine. 
> In the beginning powering off went good but now i get stuck at a screen that 
> says
> 
> efi: EFI_MEMMAP is not enabled
> 
> esrt: ESRT header is not in the memory map
> 
> .. i also installed coldhaks grsec script for debian template. after a 
> paxtest blackhat i get vulerabilities in memory , mprotect ect..  i thought 
> this might be related to efi.
> 
> I have a lenovo x260 i7 processor. Some help will be much appreciated i dont 
> want to keep powering off the wrong way. Thank you.

Still have problem. I cant seem to figure it out...:(

-- 
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/77cfb138-55a2-4549-b729-564b9df80f24%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: nouveau driver minor screen tearing advice

[Nautilus Maximus]

On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> Hi all, 
> I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> tearing with the nouveau driver. I've looked through the threads, most are 
> for the older version of qubes or installing propriety drivers. For me it's 
> not a major issue just an annoyance especially watching videos etc. Disabling 
> composition doesn't work for me unfortunately. Thanks for you time and 
> support.

Yeah it is plugged into the 770, I tried to over complicate things. Everything 
displays fine it's just the minor tearing when moving windows and watching 
youtube, netflix etc. For me it's not a major issue and I am quite happy with 
Qubes as a daily diver. It kind of reminds me of using the old legacy windows 
98 preformance wise. Is it an acceleration/buffering issue and is their a way 
to fix it? I don't know the platform is so new and the community is so few. I 
don't want to install nvidia because a dom0 update in the future might break 
the os.  

-- 
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/2a92bd00-407e-4080-b648-2c7593647afe%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: nouveau driver minor screen tearing advice

[Grzesiek Chodzicki]

W dniu niedziela, 19 lutego 2017 01:23:43 UTC+1 użytkownik Nautilus Maximus 
napisał:
> On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> > Hi all, 
> > I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> > tearing with the nouveau driver. I've looked through the threads, most are 
> > for the older version of qubes or installing propriety drivers. For me it's 
> > not a major issue just an annoyance especially watching videos etc. 
> > Disabling composition doesn't work for me unfortunately. Thanks for you 
> > time and support.
> 
> Ok. I'm not even sure if my graphics card is being utilized. I've tried the 
> usual grep commands to check but the commands do not seem to work. I'll have 
> to research more and put my results on here to hopefully help others.

If the monitor is plugged into it then it is utilized. If You're using a laptop 
with both integrated and a discrete graphics card You need to install bumblebee 
to be able to utilize the discrete card.

-- 
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/7cfc5e7c-0f09-4737-b6a3-b079eb41f53f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: nouveau driver minor screen tearing advice

[Nautilus Maximus]

On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> Hi all, 
> I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> tearing with the nouveau driver. I've looked through the threads, most are 
> for the older version of qubes or installing propriety drivers. For me it's 
> not a major issue just an annoyance especially watching videos etc. Disabling 
> composition doesn't work for me unfortunately. Thanks for you time and 
> support.

Ok. I'm not even sure if my graphics card is being utilized. I've tried the 
usual grep commands to check but the commands do not seem to work. I'll have to 
research more and put my results on here to hopefully help others.

-- 
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/9033e460-f223-43c9-b80b-079eb6495f5c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] boot problem after switching bios from uefi to legacy to uefi

[joe . m]

hi.
since i saw multiple people posting things about aem, i thought i would
also setup aem.

i looked at
https://github.com/QubesOS/qubes-antievilmaid/blob/master/anti-evil-maid/README
and saw i need to use legacy.
i installed my system while booting uefi and then switched to legacy.
i was not sure whether the system could boot again, but if it did not boot,
i would switch back again.

after switching to legacy, the system did not boot (i am not sure wheter it
should boot normally after switchin, of if that does not work).
after switching back to uefi, it still does not boot
is there a way to fix this?

also when looking at the bios, i did not find an option for TPM or TXT.
but there is some stuff like secure boot mode/control with pks (could this
be it?)
or does my laptop mybe not have this feature?

some system info:
msigp60
bios version E16GDIMS.30B (build date: 23/08/2013)

should i update the bios? (maybe the old bios version does not display the
tpm option)

i am grateful for any ideas.
wit best regards.
joe mitchell


-

ONLY AT VFEmail! - Use our Metadata Mitigator to keep your email out of the 
NSA's hands!
$24.95 ONETIME Lifetime accounts with Privacy Features!  
15GB disk! No bandwidth quotas!
Commercial and Bulk Mail Options!  


--
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/20170218035148.Horde.5vsGnlMVjJZ9SuAwC2e0ZQ1%40www.vfemail.net.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] qubes partitioning questsion

[Oleg Artemiev]

On Sat, Feb 18, 2017 at 9:59 PM, Oleg Artemiev  wrote:
>
>
> On Feb 18, 2017 21:07, "Manuel Amador (Rudd-O)"  wrote:
>
> Separate /usr is not supported.
>
> I have separated /usr over 2 years and had no problem. Unix like OS allows
> this by design. What do you mean by 'not supported'?
>
>
> There is no point in sub mount points under /var/lib/qubes. /var/lib/Qubes
> is enough as a single mountpoint.
>
> Unless we talk about read and write optimizations in hdd vs ssd.
>
>
> There is no point in /var/lib/* sub mount points. Or /var/log for that
> matter.
>
> /var/log separation is must have.  Once you have some repeating log events
> overflowed  your root you will understand why. I had a problem w/ not
> separated /var/log w/ older qubes - no need to step over same trap.
>
>
> You don't have to have /home under a mountpoint. Dom0 /home should be empty
> if you are using Qubes right.
>
> /home/username is subject to often write operations by window manager and
> all user software - like I'm any other unix-like  when you login all user
> settings and some temp files are stored under /home/username. Having this on
> sad saves time, but smokes out ssd life - as usual - smoking is pretty
> habbit, but kills your health in long term - same w/ regular writes on ssd .
>
>
>
> Use btrfs instead of LVM. That way you can do subvolumes.
>
>
> Is btrfs is stable enough?
I've reviewed some user notes on btrfs and found it has some disadvantages:

1. fsck is not aware of btrfs and occasional run by hands of fsck on
btrfs may lead to partition corruption.
2. It stores some extra info for each file, so volumes w/ a lot of
smal files appear to use more space than on ext3/ext4  .

3. tools for btrfs are still in active development, so I should be
careful to never appear to be using an alfa- or betta- grade versions
if I
want to be sure all is sage enough. I even consider for myself ext4 is
not stable enough compared to ext3. btrfs is one year younger than
ext4 BTW.
If I enable Qubes development repositories - how can I ensure that
btrfs tools never get newer than I want?

BTW - to the moment I don't understand - is it possible to tune btrfs
in such a way, when it will use most oftenly writed meta data stuff
via  hdd only?
I.e /dev/sda is hdd , sdb is ssd - is it possible to create a btrfs
partition that will put its metadata on ssd


> Separation below is due to faster reads from ssd . Also ssd drives degrade
> in terms of stability if writes are made too often . Thus I want separate
> app VM /template VM storage - template VMs are changed rarely. BTW - I'm not
> sure where temporary images are stored when Qubes starts an App VM. The idea
> is get most reads from ssd and most writes to hdd.
This is noted here:
https://groups.google.com/forum/#!topic/qubes-devel/hG93VcwWtRY and
(today/yesterday) in reply to similar quesion around Subj in
qubes-developers:
https://groups.google.com/forum/#!topic/qubes-devel/wfqKiOYgV8Y


> On February 18, 2017 8:21:10 AM PST, Oleg Artemiev 
> wrote:
>>
>> Hello,
>>
>> I'm about to upgrade from Qubes 3.0 to Qubes 3.2 now.
>>
>> I've two terabites (1 ssd and 1 hdd) in my laptop and 16Gigs of
>> memory. Is separation to different mount points as proposed below
>> is a good idea? Please note if you think that something could also be
>> moved to ssd. My criteria for ssd stuff is "oftenly read, very rare
>> write".
>>
>>
>> As everything is encrypted , thus no need in gpt - dos partition table.
>>
>> ssd:
>> /   - 400Мb
>> /usr - 5G0b
>> /boot - 300Mb
>> /var/lib/qubes/vm-templates - 350Gb
>> /var/lib/qubes/vm-kernels   - 3.5Gb
>> /var/lib/rpm- 100Mb
>> /var/lib/yum- 50Mb
>>
>> individual catalogues under /home// - up to 100 mount points ,
>> unsure which ones are rewritten rarely an thus worth moving to ssd,
>> thus will move after upgrade.
>>
>> hdd:
>> /a_copy_of_/boot - 300Mb
>> /tmp - 32Gb - looks like it has to be not less
>> then biggest VM size
>> swap - 32Gb
>> /home - 100Мб
>> /var/log - 300Mb
>> /var/log/
>>
>> BTW: Looks like LVM thin provisioning gives at least two times slower
>> writes, so I'm about to use usual LVM.



-- 
Bye.Olli.
gpg --search-keys grey_olli , use key w/ fingerprint below:
Key fingerprint = 9901 6808 768C 8B89 544C  9BE0 49F9 5A46 2B98 147E
Blog keys (the blog is mostly in Russian): http://grey-olli.livejournal.com/tag/

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

[qubes-users] Re: nouveau driver minor screen tearing advice

[Grzesiek Chodzicki]

W dniu sobota, 18 lutego 2017 15:24:18 UTC+1 użytkownik Nautilus Maximus 
napisał:
> On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> > Hi all, 
> > I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> > tearing with the nouveau driver. I've looked through the threads, most are 
> > for the older version of qubes or installing propriety drivers. For me it's 
> > not a major issue just an annoyance especially watching videos etc. 
> > Disabling composition doesn't work for me unfortunately. Thanks for you 
> > time and support.
> 
> I have done that; however, the video tearing still persists. Thanks for the 
> reply though, I appreciate it.

If You're using VLC to watch videos, change the video output to X11.

-- 
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/3e3da377-426f-407a-9521-2b15f9adbc2f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] MP3 support but SMB issues on DebVM or SMB support with MP3 issues on FedVM?

['.' via qubes-users]

 Original Message 

Subject: Re: [qubes-users] MP3 support but SMB issues on DebVM or SMB support 
with MP3 issues on FedVM?
Local Time: February 18, 2017 9:24 PM
UTC Time: February 18, 2017 9:24 PM
From: un...@thirdeyesecurity.org
To: . 
qubes-users@googlegroups.com 

On Sat, Feb 18, 2017 at 12:05:57PM -0500, '.' via qubes-users wrote:
> I have been trying to get a "proper" music setup working on my Qubes (3.2) 
> machine and am having issues. On a Fed24VM I can't seem to get mp3 support 
> (tried installing gstreamer no go) and on Deb9 I can connect to my file 
> server via the filemanager but can't find where it is mounting (where as I 
> can just type "mount" in Fed and the last entry is usuall the mount point).
>
> I love VLC for videos, but despise it for music (compared to what I want in a 
> music player). I was able to run foobar2k with wine before (which apparently 
> took care of MP3 support issue in Fed) but that is an unweildy option and I 
> think Quod Libet player will suffice (which I have installed on both Deb/Fed 
> VMs no prob).
>
> I would prefer to use a debVM for my music but could use some suggestions on 
> how to include a line to mount it to a point i can find. I have tried mount 
> -t smb //fileserver/directory /media/testmountdirectory and a few variations 
> (like CIFS) but nothing. I don't have a password on set on the server at the 
> moment and when I mount via the file manager I just put in 
> smb://fileserver/directory it prompts me to connect and I'm in.
>
> How can I set a Deb "AudioVM" to automatically mount the music_directory so 
> it can be accessible to something like Quod Libet?

You should be able to see the mount using gvfs-mount. In Debian the
mount point from nautilus would be under /run/user/.

You don't say exactly what happens when you try a manual mount - unless
"nothing" is a full description, of course. If you looked on the server
you might find helpful logs.
(I'm assuming you have cifs-utils installed .)
Then "mount -v -t cifs //server/mount mountpoint -o user=nobody" should
work and provide useful information.
You could equally well put this in to .bashrc rather than in a
Template, or add an entry to /etc/fstab using the mechanism in
/rw/config/rc.local.

unman
Thx unman.
gvfs-mount did not work for me. I do not no why, maybe it is not install?
I tried the suggestion you made for cifs and first it did not work but it seems 
I did not have it installed. I thought because my fileserver mounted in 
nautilus that everything needed is installd.
I installd cifs and now mountnig works well. Your idea for the .bashrc is good 
because it is better I keep changes to the template minimuml.
Thx so much for the support.

-- 
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/zpQ4IKS3zWyaYpOTgf4_JchhXyvaoq1bpNFyDw9NRXeULNqq7iA6M4zNXpOQrZ81d8UqkrGPRP1mCycmaf8KeqLfPfYvbaGFNo_rBuOEuWE%3D%40protonmail.ch.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] MP3 support but SMB issues on DebVM or SMB support with MP3 issues on FedVM?

[Unman]

On Sat, Feb 18, 2017 at 12:05:57PM -0500, '.' via qubes-users wrote:
> I have been trying to get a "proper" music setup working on my Qubes (3.2) 
> machine and am having issues. On a Fed24VM I can't seem to get mp3 support 
> (tried installing gstreamer no go) and on Deb9 I can connect to my file 
> server via the filemanager but can't find where it is mounting (where as I 
> can just type "mount" in Fed and the last entry is usuall the mount point).
> 
> I love VLC for videos, but despise it for music (compared to what I want in a 
> music player). I was able to run foobar2k with wine before (which apparently 
> took care of MP3 support issue in Fed) but that is an unweildy option and I 
> think Quod Libet player will suffice (which I have installed on both Deb/Fed 
> VMs no prob).
> 
> I would prefer to use a debVM for my music but could use some suggestions on 
> how to include a line to mount it to a point i can find. I have tried mount 
> -t smb //fileserver/directory /media/testmountdirectory and a few variations 
> (like CIFS) but nothing. I don't have a password on set on the server at the 
> moment and when I mount via the file manager I just put in 
> smb://fileserver/directory it prompts me to connect and I'm in.
> 
> How can I set a Deb "AudioVM" to automatically mount the music_directory so 
> it can be accessible to something like Quod Libet?

You should be able to see the mount using gvfs-mount. In Debian the
mount point from nautilus would be under /run/user/.

You don't say exactly what happens when you try a manual mount - unless
"nothing" is a full description, of course. If you looked on the server
you might find helpful logs.
(I'm assuming you have cifs-utils installed .)
Then "mount -v -t cifs //server/mount mountpoint -o user=nobody" should
work and provide useful information. 
You could equally well put this in to .bashrc rather than in a
Template, or add an entry to /etc/fstab using the mechanism in
/rw/config/rc.local.

unman

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

Re: [qubes-users] NetVM without firewall, no PING from outside?

[Unman]

On Fri, Feb 17, 2017 at 06:01:14PM -0800, Manuel Amador (Rudd-O) wrote:
> Qubes-network-server takes care of this for you.
> 
> On February 14, 2017 2:02:18 AM PST, Jarle Thorsen  
> wrote:
> >> Unman:
> >> Thank you, it seems like using proxy arp is the way to go for me.
> >That way I can still use a dynamic address for my NetVM.
> >
> >I'm getting back to this thread, still haven't got everything working:
> >
> >My NetVM is connected to a local network 10.0.0.0/16, and gets a
> >dynamic IP via DHCP.
> >
> >AppVMs connect directly to the NetVM, without any firewall, and all
> >firewall rules has been removed from NetVM.
> >
> >All networking is now working fine, both between AppVMs and from AppVMs
> >and into the 10.0.0.0/16 network.
> >
> >Now I need to have the AppVMs available from the 10.0.0.0/16 network...
> >
> >Where do I need to enable arp_proxy to make this happen? Only on the
> >NetVM interface connected to the 10.0.0.0/16 network, or also on the
> >vif interfaces on the NetVM, or in the AppVMs also??
> >

This really isn't very helpful to someone who is trying to understand
what is happening. Perhaps the need for brevity prevented a fuller
answer. But just saying there's a tool, (although I understand your
wish to promote your software) isn't the way to go imo.

Jarle - there are a few things you could do. One of them would be to
distribute a static route using your DHCP server -  implementing
a classless static route if your server supports it would be best. You
would need to put the external iface of the netVM as the gateway to the
internal 10.137.0.0/16 network. This won't be easy with DHCP unless you
put a reservation in place.

Alternatively you use proxy arp on the external interface of the netVM,
as you suggest. You don't need it on the vif interfaces because  you
have the relevant routing information in the netVM. (As you are
connecting qubes directly to the netVM these routes will be set up
automatically. You can check this with 'ip route' - If you DID use a
firewall you would need to add a static route on the netVM with the fw
as gateway to the qubes connected to it.)

It may be that Rudd-0's tool will do this for you. I dont know.

unman

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

Re: [qubes-users] qubes partitioning questsion

[Oleg Artemiev]

On Feb 18, 2017 21:07, "Manuel Amador (Rudd-O)"  wrote:

Separate /usr is not supported.

I have separated /usr over 2 years and had no problem. Unix like OS allows
this by design. What do you mean by 'not supported'?


There is no point in sub mount points under /var/lib/qubes. /var/lib/Qubes
is enough as a single mountpoint.

Unless we talk about read and write optimizations in hdd vs ssd.


There is no point in /var/lib/* sub mount points. Or /var/log for that
matter.

/var/log separation is must have.  Once you have some repeating log events
overflowed  your root you will understand why. I had a problem w/ not
separated /var/log w/ older qubes - no need to step over same trap.


You don't have to have /home under a mountpoint. Dom0 /home should be empty
if you are using Qubes right.

/home/username is subject to often write operations by window manager and
all user software - like I'm any other unix-like  when you login all user
settings and some temp files are stored under /home/username. Having this
on sad saves time, but smokes out ssd life - as usual - smoking is pretty
habbit, but kills your health in long term - same w/ regular writes on ssd .



Use btrfs instead of LVM. That way you can do subvolumes.


Is btrfs is stable enough?

Separation below is due to faster reads from ssd . Also ssd drives degrade
in terms of stability if writes are made too often . Thus I want separate
app VM /template VM storage - template VMs are changed rarely. BTW - I'm
not sure where temporary images are stored when Qubes starts an App VM. The
idea is get most reads from ssd and most writes to hdd.




On February 18, 2017 8:21:10 AM PST, Oleg Artemiev 
wrote:
>
> Hello,
>
> I'm about to upgrade from Qubes 3.0 to Qubes 3.2 now.
>
> I've two terabites (1 ssd and 1 hdd) in my laptop and 16Gigs of
> memory. Is separation to different mount points as proposed below
> is a good idea? Please note if you think that something could also be
> moved to ssd. My criteria for ssd stuff is "oftenly read, very rare
> write".
>
>
> As everything is encrypted , thus no need in gpt - dos partition table.
>
> ssd:
> /   - 400Мb
> /usr - 5G0b
> /boot - 300Mb
> /var/lib/qubes/vm-templates - 350Gb
> /var/lib/qubes/vm-kernels   - 3.5Gb
> /var/lib/rpm- 100Mb
> /var/lib/yum- 50Mb
>
> individual catalogues under /home// - up to 100 mount points ,
> unsure which ones are rewritten rarely an thus worth moving to ssd,
> thus will move after upgrade.
>
> hdd:
> /a_copy_of_/boot - 300Mb
> /tmp - 32Gb - looks like it has to be not less
> then biggest VM size
> swap - 32Gb
> /home - 100Мб
> /var/log - 300Mb
> /var/log/
>
> BTW: Looks like LVM thin provisioning gives at least two times slower
> writes, so I'm about to use usual LVM.
>
>
-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

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

Re: [qubes-users] qubes partitioning questsion

[Manuel Amador (Rudd-O)]

Separate /usr is not supported.

There is no point in sub mount points under /var/lib/qubes.  /var/lib/Qubes is 
enough as a single mountpoint.

There is no point in /var/lib/* sub mount points.  Or /var/log for that matter. 

You don't have to have /home under a mountpoint.  Dom0 /home should be empty if 
you are using Qubes right.

Use btrfs instead of LVM.  That way you can do subvolumes.

On February 18, 2017 8:21:10 AM PST, Oleg Artemiev  wrote:
>Hello,
>
>I'm about to upgrade from Qubes 3.0 to Qubes 3.2 now.
>
>I've two terabites (1 ssd and 1 hdd) in my laptop and 16Gigs of
>memory. Is separation to different mount points as proposed below
>is a good idea? Please note if you think that something could also be
>moved to ssd. My criteria for ssd stuff is "oftenly read, very rare
>write".
>
>
>As everything is encrypted , thus no need in gpt - dos partition table.
>
>ssd:
>/   - 400Мb
>/usr - 5G0b
>/boot - 300Mb
>/var/lib/qubes/vm-templates - 350Gb
>/var/lib/qubes/vm-kernels   - 3.5Gb
>/var/lib/rpm- 100Mb
>/var/lib/yum- 50Mb
>
>individual catalogues under /home// - up to 100 mount points ,
>unsure which ones are rewritten rarely an thus worth moving to ssd,
>thus will move after upgrade.
>
>hdd:
>/a_copy_of_/boot - 300Mb
>/tmp - 32Gb - looks like it has to be not less
>then biggest VM size
>swap - 32Gb
>/home - 100Мб
>/var/log - 300Mb
>/var/log/
>
>BTW: Looks like LVM thin provisioning gives at least two times slower
>writes, so I'm about to use usual LVM.
>
>
>-- 
>Bye.Olli.
>gpg --search-keys grey_olli , use key w/ fingerprint below:
>Key fingerprint = 9901 6808 768C 8B89 544C  9BE0 49F9 5A46 2B98 147E
>Blog keys (the blog is mostly in Russian):
>http://grey-olli.livejournal.com/tag/
>
>-- 
>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/CABunX6MReuC_Q9B2NYjHjKnvRLc%2BJeaWaywxF%3DLV8rYpiT32DQ%40mail.gmail.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/E7D8002A-6C9C-46DE-A29B-CC354E62C469%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Resize dom0

[Manuel Amador (Rudd-O)]

It is the standard procedure to enlarge any root partition on any Linux — 
enlarge encrypted volume, enlarge LVM physical volume, enlarge enlarge LVM 
logical volume, enlarge root file system.  You will have to do this from a 
rescue initramfs or another Linux system you booted from.

On February 18, 2017 2:23:29 AM PST, "Zbigniew Łukasiak"  
wrote:
>There are instructions how to resize a VM at
>https://www.qubes-os.org/doc/resize-root-disk-image/ - but this cannot
>apply to dom0 - because it requires stopping the VM and then running
>commands in dom0. What would be the procedure for resizing dom0 root
>partition?
>
>-- 
>Zbigniew Lukasiak
>http://brudnopis.blogspot.com/
>http://perlalchemy.blogspot.com/
>
>-- 
>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/CAGL_UUvH1mT_LP57dS6DO5ksNDEf%3DZWA0XiruH7rzM455GHkdg%40mail.gmail.com.
>For more options, visit https://groups.google.com/d/optout.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/395BD576-E36E-442E-AEEF-152205714914%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] MP3 support but SMB issues on DebVM or SMB support with MP3 issues on FedVM?

[Manuel Amador (Rudd-O)]

Create a mount unit in your template of the Deb VM, which does the mount.  Have 
it WantedBy=multi-user.target.  Enable it.

Add a ConditionPathExists=/var/run/qubes-service/mediamount to the unit.

Power off the template and the Deb VM.

Thru Qubes Manager, add a Qubes service to the DebVM, naming it mediamount.

Power on the template.

Bam, now that thing mounts only in the Deb VM.

I have an Ansible play for this.  Will publish it soon.

On February 18, 2017 9:05:57 AM PST, "'.' via qubes-users" 
 wrote:
>I have been trying to get a "proper" music setup working on my Qubes
>(3.2) machine and am having issues. On a Fed24VM I can't seem to get
>mp3 support (tried installing gstreamer no go) and on Deb9 I can
>connect to my file server via the filemanager but can't find where it
>is mounting (where as I can just type "mount" in Fed and the last entry
>is usuall the mount point).
>
>I love VLC for videos, but despise it for music (compared to what I
>want in a music player). I was able to run foobar2k with wine before
>(which apparently took care of MP3 support issue in Fed) but that is an
>unweildy option and I think Quod Libet player will suffice (which I
>have installed on both Deb/Fed VMs no prob).
>
>I would prefer to use a debVM for my music but could use some
>suggestions on how to include a line to mount it to a point i can find.
>I have tried mount -t smb //fileserver/directory
>/media/testmountdirectory and a few variations (like CIFS) but nothing.
>I don't have a password on set on the server at the moment and when I
>mount via the file manager I just put in smb://fileserver/directory it
>prompts me to connect and I'm in.
>
>How can I set a Deb "AudioVM" to automatically mount the
>music_directory so it can be accessible to something like Quod Libet?
>
>-- 
>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/vS162_w02q8XeVvlJYqXCAPP0iOD1oRX3Pr8Bw_YVyTlMqv60sDcBeRbDle1W0m02n_GT2k7oyLC1cL9GBOQZMbG7qaHPgQOqv6odmYrEUw%3D%40protonmail.ch.
>For more options, visit https://groups.google.com/d/optout.

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

-- 
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/55D5F7FA-B2FC-4403-99B1-535C7BD4DE9E%40rudd-o.com.
For more options, visit https://groups.google.com/d/optout.

[qubes-users] Re: nouveau driver minor screen tearing advice

[Nautilus Maximus]

On Saturday, 18 February 2017 02:35:03 UTC+10, Nautilus Maximus  wrote:
> Hi all, 
> I thought I'd ask if any one had any tips or tricks on fixing minor screen 
> tearing with the nouveau driver. I've looked through the threads, most are 
> for the older version of qubes or installing propriety drivers. For me it's 
> not a major issue just an annoyance especially watching videos etc. Disabling 
> composition doesn't work for me unfortunately. Thanks for you time and 
> support.

I have done that; however, the video tearing still persists. Thanks for the 
reply though, I appreciate it. 

-- 
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/42b9e464-0b18-464c-a2f0-2326890cd9bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [qubes-users] Resize dom0

[tezeb]

On 02/18/17 11:23, Zbigniew Łukasiak wrote:
> There are instructions how to resize a VM at
> https://www.qubes-os.org/doc/resize-root-disk-image/ - but this cannot
> apply to dom0 - because it requires stopping the VM and then running
> commands in dom0. What would be the procedure for resizing dom0 root
> partition?
> 

It's just a linux, and by default dom0 root fs is ext4, which can be
grown while mounted, so 'standard' resizing procedure should do. Please
take into account that there is ext4 on LVM on LUKS and each have to be
grown separately. All commands run as root from dom0(do backups and be
carefull!!!).
Thanks to LVM there are two alternative solutions.

First one, if you have space after LUKS partition on your HDD/SSD:
0. grow physical partition using fdisk or gparted.
1. grow LUKS container using "cryptsetup resize".
2. grow (LVM) physical volume using "pvresize".
3. grow (LVM) logical volume(default name: root) using "lvextend".
4. grow ext4 filesystem using "resize2fs".

Alternatively you can extend root by extending LVM, but this will
require providing two(or more) passwords while booting(because each part
of LVM will need to be decrypted before "merging" it into root partition).
0. Create new partition using fdisk/gparted.
1. Create new encrypted luks container using "cryptsetup luksFormat".
2. Mount newly created luks container.
3. Initialize (LVM) physical volume on newly created luks container
using pvcreate.
4. Add newly created physical volume to LVM volume group (by default
named: qubes_dom0) using "vgextend".
5. grow (LVM) logical volume using "lvextend".
6. grow ext4 filesystem using "resize2fs".
7. remember to recreate initramfs including both LUKS containers and new
lvm settings

As always with filesystem changing operations, backup everything before
proceding and be extremly carefull. I'm also not providing full
commands(it's hard to do from the top of my head), so RTFM to get better
understanding of each of above-mentioned commands.

To analyze current state of LVM useful commands are: pvdisplay,
vgdisplay and lvdisplay. Additionally all used devices shall be visible
in /dev/mapper.

Regards,
tezeb

-- 
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/1a246833-2a32-7c54-e523-e7afa48a11e0%40outoftheblue.pl.
For more options, visit https://groups.google.com/d/optout.


signature.asc
Description: OpenPGP digital signature

[qubes-users] Resize dom0

[Zbigniew Łukasiak]

There are instructions how to resize a VM at
https://www.qubes-os.org/doc/resize-root-disk-image/ - but this cannot
apply to dom0 - because it requires stopping the VM and then running
commands in dom0. What would be the procedure for resizing dom0 root
partition?

-- 
Zbigniew Lukasiak
http://brudnopis.blogspot.com/
http://perlalchemy.blogspot.com/

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