-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/09/2019 3.46 AM, 'Heinrich Ulbricht' via qubes-users wrote:
>> Personally, I would just stick with this. In other words, I would treat
>> the new Qubes installation as completely new and use qvm-backup-restore
>> as the only mechanism for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 01/09/2019 8.03 AM, Claudia wrote:
> Andrew David Wong:
>> On 31/08/2019 11.23 AM, Claudia wrote:
>>> The "Custom Installation" doc gives instructions about how to
>>> create a non-default dm-crypt partition, or other custom setup,
>>> and
Andrew David Wong:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 31/08/2019 11.23 AM, Claudia wrote:
The "Custom Installation" doc gives instructions about how to
create a non-default dm-crypt partition, or other custom setup, and
install Qubes to it. But when I follow these instructions
On Sunday, September 1, 2019 at 12:00:20 PM UTC+2, donoban wrote:
>
> On 9/1/19 10:46 AM, 'Heinrich Ulbricht' via qubes-users wrote:
> > Thank you very much for helping me out on this, awokd and Andrew.
> > Currently I'm leaning toward taking the safe path. If I understand
> > correctly that
'awokd' via qubes-users:
> 'awokd' via qubes-users:
>
>>> HYP: 0 0 0 0 Hypervisor callback
>>> interrupts
>>> HRE: 0 0 0 0 Hyper-V reenlightenment
>>> interrupts
>>> HVS: 0 0 0 0
On Sunday, September 1, 2019 at 3:46:00 PM UTC+2, Антон Чехов wrote:
>
>
>
> On Sunday, September 1, 2019 at 3:32:24 PM UTC+2, awokd wrote:
>>
>> 'Антон Чехов' via qubes-users:
>> > Hi,
>> >
>> > I have a small problem that I don't know how to tackle.
>> > I've installed a language
On 9/1/19 7:38 AM, 'awokd' via qubes-users wrote:
'Heinrich Ulbricht' via qubes-users:
1. Backup everything that's on the SSD *and* the external storage pool
HDDs - this will take a lot of time and space but that's the price I have
to pay for the safety I get
2. Connect the new
Le vendredi 30 août 2019 21:02:44 UTC+2, rec wins a écrit :
>
> On 8/30/19 2:40 AM, unman wrote:
> > On Thu, Aug 29, 2019 at 08:58:33PM -1000, rec wins wrote:
> >> On 8/29/19 1:49 AM, unman wrote:
> >>> On Wed, Aug 28, 2019 at 09:01:46PM -1000, rec wins wrote:
> On 5/27/19 6:09 AM,
Le vendredi 30 août 2019 14:40:51 UTC+2, unman a écrit :
>
> On Thu, Aug 29, 2019 at 08:58:33PM -1000, rec wins wrote:
> > On 8/29/19 1:49 AM, unman wrote:
> > > On Wed, Aug 28, 2019 at 09:01:46PM -1000, rec wins wrote:
> > >> On 5/27/19 6:09 AM, Stumpy wrote:
> > >>> I am trying to use an
Is there any timeline for the release of 4.0.2 Final?
Steve
--
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 view
On Sunday, September 1, 2019 at 3:32:24 PM UTC+2, awokd wrote:
>
> 'Антон Чехов' via qubes-users:
> > Hi,
> >
> > I have a small problem that I don't know how to tackle.
> > I've installed a language software/dictionary in a clone of the Fedora
> 30
> > Template. The parent folder in the
'Антон Чехов' via qubes-users:
> Hi,
>
> I have a small problem that I don't know how to tackle.
> I've installed a language software/dictionary in a clone of the Fedora 30
> Template. The parent folder in the template is /home/user/. I can start the
> program by going to the folder and using a
Hi,
I have a small problem that I don't know how to tackle.
I've installed a language software/dictionary in a clone of the Fedora 30
Template. The parent folder in the template is /home/user/. I can start the
program by going to the folder and using a shell script ( ./script-name).
When I shut
'awokd' via qubes-users:
>> HYP: 0 0 0 0 Hypervisor callback
>> interrupts
>> HRE: 0 0 0 0 Hyper-V reenlightenment
>> interrupts
>> HVS: 0 0 0 0 Hyper-V stimer0
>> interrupts
>
'Heinrich Ulbricht' via qubes-users:
>1. Backup everything that's on the SSD *and* the external storage pool
>HDDs - this will take a lot of time and space but that's the price I have
>to pay for the safety I get
>2. Connect the new SSD, wipe the external drives
>3. Install
I would advise against wiping any disks until you are sure the full set of
restores are complete and tested.
I’ve learned the hard way to never put myself
into a situation where I cannot revert to my original configuration.
Brendan
--
You received this message because you are subscribed to
Guest:
> The requested details are inline below.
>
> Below are the outputs of /proc/interrupts, lspci, lsusb, and uname. Taken on
> the latest tails, with all possible peripherals disabled in the bios.
>
> ---snip---
> cat /proc/interrupts:
> CPU0 CPU1 CPU2 CPU3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 8/31/19 9:12 PM, donoban wrote:
> On 9/1/19 10:46 AM, 'Heinrich Ulbricht' via qubes-users wrote:
>> Thank you very much for helping me out on this, awokd and
>> Andrew. Currently I'm leaning toward taking the safe path. If I
>> understand
On 9/1/19 10:46 AM, 'Heinrich Ulbricht' via qubes-users wrote:
Thank you very much for helping me out on this, awokd and Andrew.
Currently I'm leaning toward taking the safe path. If I understand
correctly that means:
1. Backup everything that's on the SSD /and/ the external storage pool
> Personally, I would just stick with this. In other words, I would treat
> the new Qubes installation as completely new and use qvm-backup-restore
> as the only mechanism for migrating my old data to the new installation.
> This is the only way I would be confident that I weren't screwing
>
The requested details are inline below.
I really appreciate you looking into this - Thanks. If there are any other
thoughts and ideas to try to isolate the problem am happy to try and revert.
At 20:21 31/08/2019, 'awokd' via qubes-users wrote:
>>> At 23:22 28/08/2019, 'awokd' via qubes-users
21 matches
Mail list logo
