On Mon, May 22, 2017 at 10:33:30PM -0300, Franz wrote:
> @Unman,
>
>
> On Mon, May 22, 2017 at 5:05 PM, Unman wrote:
>
> > On Mon, May 22, 2017 at 04:39:50PM -0300, Franz wrote:
> > > Many thanks Unman for trying so hard to help me :-))
> > >
> > > >
> > > > The next error arose because you wer
@Unman,
On Mon, May 22, 2017 at 5:05 PM, Unman wrote:
> On Mon, May 22, 2017 at 04:39:50PM -0300, Franz wrote:
> > Many thanks Unman for trying so hard to help me :-))
> >
> > >
> > > The next error arose because you were using the qvm-prefs command
> > > incorrectly.
> > >
> > > And so I dont
On Mon, May 22, 2017 at 04:39:50PM -0300, Franz wrote:
> Many thanks Unman for trying so hard to help me :-))
>
> >
> > The next error arose because you were using the qvm-prefs command
> > incorrectly.
> >
> > And so I dont understand what you mean by "gives the same error".
> >
> >
> It is the f
On Mon, May 22, 2017 at 2:10 PM, Unman wrote:
> On Sat, May 20, 2017 at 11:27:01PM -0300, Franz wrote:
> > On Sat, May 20, 2017 at 7:49 PM, Unman
> wrote:
> >
> > > On Sat, May 20, 2017 at 07:34:28PM -0300, Franz wrote:
> > > > On Sat, May 20, 2017 at 7:20 PM, Unman
> > > wrote:
> > > >
> > > >
On Sat, May 20, 2017 at 11:27:01PM -0300, Franz wrote:
> On Sat, May 20, 2017 at 7:49 PM, Unman wrote:
>
> > On Sat, May 20, 2017 at 07:34:28PM -0300, Franz wrote:
> > > On Sat, May 20, 2017 at 7:20 PM, Unman
> > wrote:
> > >
> > > > On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrote:
> > > >
On Sat, May 20, 2017 at 11:27 PM, Franz <169...@gmail.com> wrote:
>
>
> On Sat, May 20, 2017 at 7:49 PM, Unman wrote:
>
>> On Sat, May 20, 2017 at 07:34:28PM -0300, Franz wrote:
>> > On Sat, May 20, 2017 at 7:20 PM, Unman
>> wrote:
>> >
>> > > On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrot
On Sat, May 20, 2017 at 7:49 PM, Unman wrote:
> On Sat, May 20, 2017 at 07:34:28PM -0300, Franz wrote:
> > On Sat, May 20, 2017 at 7:20 PM, Unman
> wrote:
> >
> > > On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrote:
> > > > Hello,
> > > >
> > > > the usual trick of selecting other kernel in
On Sat, May 20, 2017 at 07:34:28PM -0300, Franz wrote:
> On Sat, May 20, 2017 at 7:20 PM, Unman wrote:
>
> > On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrote:
> > > Hello,
> > >
> > > the usual trick of selecting other kernel in Qubes manager does not work
> > > running
> > > qvm-prefs -s ke
On Sat, May 20, 2017 at 7:20 PM, Unman wrote:
> On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrote:
> > Hello,
> >
> > the usual trick of selecting other kernel in Qubes manager does not work
> > running
> > qvm-prefs -s kernel default
> > gives
> > A VM with the name 'kernel" does not exist i
On Sat, May 20, 2017 at 04:27:24PM -0300, Franz wrote:
> Hello,
>
> the usual trick of selecting other kernel in Qubes manager does not work
> running
> qvm-prefs -s kernel default
> gives
> A VM with the name 'kernel" does not exist in tne system
>
> ls /var/lib/qubes/vm-kernels/
> gives
> 4.4.5
Hello,
the usual trick of selecting other kernel in Qubes manager does not work
running
qvm-prefs -s kernel default
gives
A VM with the name 'kernel" does not exist in tne system
ls /var/lib/qubes/vm-kernels/
gives
4.4.55-11 4.4.62-12 4.4.67-12
However one of the VMs does correctly starts. this
11 matches
Mail list logo
