El miércoles, 17 de agosto de 2016, 10:26:23 (UTC+2), Foppe de Haan escribió:
> On Wednesday, August 17, 2016 at 10:08:24 AM UTC+2, Foppe de Haan wrote:
> > After switching the template for my vault to debian-8 (mainly because of
> > the lower memory footprint), I noticed that, for reasons that
On Tue, Aug 16, 2016 at 10:45 PM, wrote:
> The Qubes website recommends SSD drives.
>
> Is there any particular reason..?
The main one is speed. For the boot drive in workstations or
laptops, I've been using SSDs for years. The performance
gain was large enough to
Hello,
I have problems with installation Qubes R3.1.
I wrote iso to usb stick using dd on Linux.
I tried different ways install cubes to my laptop:
1. UEFI mode, "Test this media and install Qubes R3.1", got anacoda
installer screen and then black screen with non-blinking text cursor at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17.08.2016 09:47, Robin Schneider wrote:
> On 17.08.2016 04:45, neilhard...@gmail.com wrote:
>> The Qubes website recommends SSD drives.
>
>> Is there any particular reason..?
>
>> Does Qubes use read/write to the hard drive any more than
Thanks for the feedback. The fact USB is a bad idea all around for
security (and potentially stability), and the fact I was getting minor
corruption, should have been a warning to me to move the drive right onto
the SATA bus, rather than risking worse corruption. I guess I only have
myself to
On the Signal matter, just some personal paranoia Re: Signal and Google
Play Services:
I've been the subject of some rather intense and ongoing hacking (iPhone,
iPad, Android phone/tablet, PC, MacBook, cable modem connection, you name
it).
On the Android phone, I wiped it several times, and
On 08/15/2016 08:49 PM, Ben Wika wrote:
> Is F-Droid's Silence any better than Signal given it can run without Google
> Play Store?
The issue is not so much the Google Play Store, but the Google Play
Services. Silence has been forked of Signal and works completely
different now. In contrast to
johnyju...@sigaint.org:
> Well, my wild enthusiasm with Qubes has turned into complete frustration
> and exasperation this morning.
>
> The "mild" corruption I was seeing on boot (running Qubes from a USB 2.5"
> HD) wasn't quite so mild the last time I booted.
>
> This time, rather than
On Wednesday, August 17, 2016 at 2:18:33 PM UTC+2, Gorka Alonso wrote:
> El miércoles, 17 de agosto de 2016, 10:26:23 (UTC+2), Foppe de Haan escribió:
> > On Wednesday, August 17, 2016 at 10:08:24 AM UTC+2, Foppe de Haan wrote:
> > > After switching the template for my vault to debian-8 (mainly
Well, my wild enthusiasm with Qubes has turned into complete frustration
and exasperation this morning.
The "mild" corruption I was seeing on boot (running Qubes from a USB 2.5"
HD) wasn't quite so mild the last time I booted.
This time, rather than "recovering journal... done," the fsck spewed
On 08/17/2016 11:35 AM, johnyju...@sigaint.org wrote:
On the Signal matter, just some personal paranoia Re: Signal and Google
Play Services:
I've been the subject of some rather intense and ongoing hacking (iPhone,
iPad, Android phone/tablet, PC, MacBook, cable modem connection, you name
it).
On 07/26/2016 05:32 PM, gaikokujinkyofu...@gmail.com wrote:
On Monday, July 25, 2016 at 5:12:42 PM UTC-10, Chris Laprise wrote:
The shebang refers to the '#!/bin/bash' at the start of the script; that
is required for it to run.
A. Ok. Well I checked and I had forgotten to remove the
On Wednesday, August 17, 2016 at 2:45:25 PM UTC-4, zack...@gmail.com wrote:
> On Wednesday, August 17, 2016 at 1:51:37 PM UTC-4, Andrew David Wong wrote:
> > -BEGIN PGP SIGNED MESSAGE-
> > Hash: SHA512
> >
> > On 2016-08-16 20:00, zackp...@gmail.com wrote:
> > > On Tuesday, August 16,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Wed, Aug 17, 2016 at 11:58:14AM -0700, Andrew David Wong wrote:
> On 2016-08-17 11:50, zackp...@gmail.com wrote:
> > On Wednesday, August 17, 2016 at 2:45:25 PM UTC-4,
> > zack...@gmail.com wrote:
> >> On Wednesday, August 17, 2016 at 1:51:37 PM
On Wednesday, August 17, 2016 at 4:39:24 PM UTC-4, Marek Marczykowski-Górecki
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On Wed, Aug 17, 2016 at 11:58:14AM -0700, Andrew David Wong wrote:
> > On 2016-08-17 11:50, zackp...@gmail.com wrote:
> > > On Wednesday, August 17, 2016
s, visit https://groups.google.com/d/optout.
Qubes-HCL-HP-HP_EliteBook_850_G3-20160817-231937.yml
Description: application/yaml
smime.p7s
Description: S/MIME Cryptographic Signature
i have a bcm 4360 wireless card on my motherboard and I cant seam to get the
drivers installed. I was told to install this to net vm [CODE]wget
http://git.io/vuLC7 -v -O fedora23_broadcom_wl_install.sh && sh
./fedora23_broadcom_wl_install.sh;[/CODE] but I ended up getting this mess
The bumblebee docs tell you to use yum/dnf without gpg.
I haven't found their keys also. Normally it sits on a keyserver.example.com
or keys.example.com
Giving the circumstances, I'd guess there aren't any.
There is a "just works" way to do it, but I'm not the one telling how to do
that. Just
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/C6EC0392-5D2E-4A6A-9C84-0F73E4B2FF89%40scorecrow.com.
For more options, visit https://groups.google.com/d/optout.
Qubes-HCL-HP-HP_250_G5_Notebook_
ut.
Qubes-HCL-HP-HP_250_G5_Notebook_PC-20160817-193812.cpio.gz
Description: GNU Zip compressed data
---
layout:
'hcl'
type:
'notebook'
hvm:
'yes'
iommu:
'yes'
tpm:
'unknown'
brand: |
HP
model: |
HP 250 G5 Notebook PC
bios: |
F.09
cpu: |
Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz
cpu-short:
On Tuesday, May 5, 2015 at 11:45:50 AM UTC-4, Vít Šesták wrote:
> Yes, a wiki topic might be useful, but I will likely not write it until
> https://github.com/QubesOS/qubes-issues/issues/988 is fixed, because it makes
> explaining the process to all too complicated and fixing it should be
>
New Qubes 3.1 installation with Advanced (No Configuration) option.
After restoring dom0 + serviceVMs + serviceTemplates, tried to
`sudo yum remove qubes-template-fedora-23`
Received: Error in PREUN scriptlet in rpm package...
libvirt.libvirtError: Domain not found [from libvirt.py line 4066
Just migrated my Qubes 3.1 system to new hardware and it went surprisingly
smoothly :)
I noticed however that my KDE Window Rules did not get backed up / restored
(not sure which).
It's kind of irrelevant at this point since we're moving away from KDE but I'd
still like to know why that
On 08/17/2016 03:20 PM, entr0py wrote:
Just migrated my Qubes 3.1 system to new hardware and it went surprisingly
smoothly :)
I noticed however that my KDE Window Rules did not get backed up / restored
(not sure which).
It's kind of irrelevant at this point since we're moving away from KDE
> On 08/17/2016 03:20 PM, entr0py wrote:
>> Just migrated my Qubes 3.1 system to new hardware and it went surprisingly
>> smoothly :)
>>
>> I noticed however that my KDE Window Rules did not get backed up / restored
>> (not sure which).
>>
>> It's kind of irrelevant at this point since we're
On Wednesday, August 17, 2016 at 10:08:24 AM UTC+2, Foppe de Haan wrote:
> After switching the template for my vault to debian-8 (mainly because of the
> lower memory footprint), I noticed that, for reasons that elude me, Jessie
> comes with an extremely outdated keepassx build (.4.3), which
Hi Marek,
Thanks for the response and my apologies on the late follow up.
> Hmm, that's strange. I use salt regularly to update all the templates at
> once and haven't noticed anything like this.
> Do you see any not cleaned up VMs after that? Like
> `disp-mgmt-something`.
There where no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 17.08.2016 04:45, neilhard...@gmail.com wrote:
> The Qubes website recommends SSD drives.
>
> Is there any particular reason..?
>
> Does Qubes use read/write to the hard drive any more than Windows... to the
> point where it's going to cause
On Thursday, August 18, 2016 at 12:41:16 AM UTC, Chris Laprise wrote:
> On 08/17/2016 06:41 PM, entr0py wrote:
> >> On 08/17/2016 03:20 PM, entr0py wrote:
> >>> Just migrated my Qubes 3.1 system to new hardware and it went
> >>> surprisingly smoothly :)
> >>>
> >>> I noticed however that my KDE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-08-17 12:17, entr0py wrote:
> New Qubes 3.1 installation with Advanced (No Configuration)
> option.
>
> After restoring dom0 + serviceVMs + serviceTemplates, tried to
> `sudo yum remove qubes-template-fedora-23`
>
> Received: Error in
On 08/17/2016 06:41 PM, entr0py wrote:
On 08/17/2016 03:20 PM, entr0py wrote:
Just migrated my Qubes 3.1 system to new hardware and it went surprisingly
smoothly :)
I noticed however that my KDE Window Rules did not get backed up / restored
(not sure which).
It's kind of irrelevant at this
On Wednesday, August 17, 2016 at 10:42:29 PM UTC, entr0py wrote:
> > On 08/17/2016 03:20 PM, entr0py wrote:
> >> Just migrated my Qubes 3.1 system to new hardware and it went surprisingly
> >> smoothly :)
> >>
> >> I noticed however that my KDE Window Rules did not get backed up /
> >> restored
> So I took kwinrulesrc from the old system and copied it right into the new
> system manually with no issues. No idea why restoring dom0 wasn't able to do
> so. Now I gotta wade through all the other config files... Hopefully, not
> missing anything else.
Mystery is partially solved. Upon
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2016-08-17 14:35, randallrba...@gmail.com wrote:
> I was also told to install this into the fedora 23 template but
> once I do i get this
>
> [CODE] v[user@fedora-23-net ~]$ wget
> http://www.broadcom.com/docs/linux_sta/$FILE --2016-08-17
>
Hi folks,
Any davs here able to tell me how to set Qubes Manager default to use a
different archiving method other than gzip ?
gzip is the default, but I don't know how or where to change it in the manager
code, I've tried to find the command it uses, but I'm unable to find the
command
35 matches
Mail list logo