Displaying 8 results from an estimated 8 matches for "unmaking".
Did you mean:
unmasking
2014 Jun 12
2
Using virtio for inter-VM communication
On 2014-06-12 04:27, Rusty Russell wrote:
> Henning Schild <henning.schild at siemens.com> writes:
>> Hi,
>>
>> i am working on the jailhouse[1] project and am currently looking at
>> inter-VM communication. We want to connect guests directly with virtual
>> consoles based on shared memory. The code complexity in the hypervisor
>> should be minimal, it
2014 Jun 12
2
Using virtio for inter-VM communication
On 2014-06-12 04:27, Rusty Russell wrote:
> Henning Schild <henning.schild at siemens.com> writes:
>> Hi,
>>
>> i am working on the jailhouse[1] project and am currently looking at
>> inter-VM communication. We want to connect guests directly with virtual
>> consoles based on shared memory. The code complexity in the hypervisor
>> should be minimal, it
2005 Dec 15
0
very strange nsswitch.ldap problem
.../dev.
I traced the problem to the nsswitch.ldap that I put into place as
nsswitch.conf.
If I have:
hosts: files dns
the system boots just fine. If I have:
hosts: files dns ldap
the system cannot deal with the udev devices correctly. I have
confirmed this by repeatedly making this change and unmaking it and the
system was wonky when ldap was included and worked fine when ldap wasn't
included.
Is there a logical reason why this would be happening?
I'll be happy to post any relevant info to my system if that would help
in explaining the situation, but I'm not sure if any other setti...
2014 Jun 13
0
Using virtio for inter-VM communication
Jan Kiszka <jan.kiszka at siemens.com> writes:
> On 2014-06-12 04:27, Rusty Russell wrote:
>> Henning Schild <henning.schild at siemens.com> writes:
>> It was also never implemented, and remains a thought experiment.
>> However, implementing it in lguest should be fairly easy.
>
> The reason why a trusted helper, i.e. additional logic in the
> hypervisor,
2014 Jun 13
2
Using virtio for inter-VM communication
On 2014-06-13 02:47, Rusty Russell wrote:
> Jan Kiszka <jan.kiszka at siemens.com> writes:
>> On 2014-06-12 04:27, Rusty Russell wrote:
>>> Henning Schild <henning.schild at siemens.com> writes:
>>> It was also never implemented, and remains a thought experiment.
>>> However, implementing it in lguest should be fairly easy.
>>
>> The
2014 Jun 13
2
Using virtio for inter-VM communication
On 2014-06-13 02:47, Rusty Russell wrote:
> Jan Kiszka <jan.kiszka at siemens.com> writes:
>> On 2014-06-12 04:27, Rusty Russell wrote:
>>> Henning Schild <henning.schild at siemens.com> writes:
>>> It was also never implemented, and remains a thought experiment.
>>> However, implementing it in lguest should be fairly easy.
>>
>> The
2005 Mar 04
3
Boolean values
...schema nor one specified by the user/code - it''s some random time that''s
> ''pretty close'' to those ones. i agree that in 97% percent of case it''ll be
> pretty damn close - but we all those kind of bugs are days * number_of_users
> in
> the unmaking.
>
>> Thinking about this just a little bit more, I would argue that this should
>> simply be a FAQ / Wiki entry. This whole issue is resolved by doing:
>>
>> class Foo < ActiveRecord::Base
>> protected
>> def after_create () reload end
>> end
&...
2005 Mar 03
12
bug in postgresql ''now'' time handling??
line 212 of postgresql_adapter.rb is
return Time.now.to_s if value =~ /^\(''now''::text\)::(date|timestamp)/
i don''t think this will work. in postgresql the field ''now'' is pinned to the
SAME TIME for the duration of a transaction. eg. if you do
begin transaction;
insert into t values(42, ''now'');
# sleep one minute