search for: unapplying

On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: > Il 17/06/2014 11:03, David Marchand ha scritto: > >>Unless someone steps up and maintains ivshmem, I think it should be > >>deprecated and dropped from QEMU. > > > >Then I can maintain ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding

On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: > Il 17/06/2014 11:03, David Marchand ha scritto: > >>Unless someone steps up and maintains ivshmem, I think it should be > >>deprecated and dropped from QEMU. > > > >Then I can maintain ivshmem for QEMU. > >If this is ok, I will send a patch for MAINTAINERS file. > > Typically, adding

Hello I use xen and I am trying to use the parallel port of Centos 5.2 host from a Windows XP (HVM) guest. I have tried to transfer control of the port by blacklisting lp, parport and parport_pc + adding: ioports = [ "0378-037a" ] to the xen configuration file. However, in the presence of this line, xm create replies with: Error: function takes exactly 4 arguments (3

On 12/04/2014 03:22 PM, James B. Byrne wrote: > On Thu, December 4, 2014 12:29, James B. Byrne wrote: >> Re: SELinux. Do I just build a local policy or is there some boolean setting >> needed to handle this? I could not find one if there is but. . . >> > Anyone see any problem with generating a custom policy consisting of the > following? > > grep avc

After joining a Samba server to domain using either Winbind or using ADBridge (PBIS), enumeration time of listing files from windows file explorer for that share is roughly (9) seconds for a folder containing 30k files consisting of both large (upto 15GB in size) and small size files (as low as KB's). Intitially, without setting logging to "0" and disabling smb max server protocol in

On Fri, December 5, 2014 04:53, Daniel J Walsh wrote: > > On 12/04/2014 03:22 PM, James B. Byrne wrote: >> On Thu, December 4, 2014 12:29, James B. Byrne wrote: >>> Re: SELinux. Do I just build a local policy or is there some boolean >>> setting >>> needed to handle this? I could not find one if there is but. . . >>> >> Anyone see any problem

On Fri, January 23, 2015 06:50, Bill Maltby (C4B) wrote: > > I don't want this stupid thing popping up every time I switch from my > normal active user logons to my "dead" one (used to get around the > unaddressed bug I filed over a month ago about switching run levels > causing crashes and running multiple users as I'd been doing for ... > over a decade(?) on

...Adds Group Policy support for the Samba kdc. Applies password policies > (minimum/maximum password age, minimum password length, and password > complexity) and kerberos policies (user/service ticket lifetime and > renew lifetime). > > Adds the samba_gpoupdate script for applying and unapplying > policy. Can be applied automatically by setting > > 'apply group policies = yes'. > Hello,     I have a few questions on the above. My upgrades since Samba 4.0 has always been in place as reference. The first change regarding 'New GUID index mode'.  Does this mea...

There''s some confusion as to what the :limit option should mean when used against integer columns in migrations. Patch #2900 added support for limits in PostgreSQL mapping mapping limit < 4 to smallint, > 4 to bigint, and anything else to integer (so the limit is the number of bytes) However, the mysql adapter uses limit to specify the ''display width'' in digits,

Is there a list of GPO functions that are known not to work with samba 4.1 ? We have a case where some settings in a GPO will get applied, and others don't. -- David Bear mobile: (602) 903-6476

Hello Stefan, On 06/18/2014 12:48 PM, Stefan Hajnoczi wrote: > One more thing to add to the list: > > static void ivshmem_read(void *opaque, const uint8_t * buf, int flags) > > The "flags" argument should be "size". Size should be checked before > accessing buf. You are welcome to send a fix and I will review it. > > Please also see the bug fixes in

Hello Stefan, On 06/18/2014 12:48 PM, Stefan Hajnoczi wrote: > One more thing to add to the list: > > static void ivshmem_read(void *opaque, const uint8_t * buf, int flags) > > The "flags" argument should be "size". Size should be checked before > accessing buf. You are welcome to send a fix and I will review it. > > Please also see the bug fixes in

Hello Dovecot users, Recently I was asked to use Mercurial for the ManageSieve development just like Dovecot. As a matter of fact I have been using Mercurial for some time now. Now that I am back from a short and active vacation I am ready to publish my repositories. The repositories are publicly available at: http://hg.rename-it.nl/ The -patch repositories are so-called Mercurial Queues (MQ)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 18.06.2014 12:48, schrieb Stefan Hajnoczi: > On Tue, Jun 17, 2014 at 11:44:11AM +0200, Paolo Bonzini wrote: >> Il 17/06/2014 11:03, David Marchand ha scritto: >>>> Unless someone steps up and maintains ivshmem, I think it >>>> should be deprecated and dropped from QEMU. >>> >>> Then I can maintain

On 05/06/2015 03:04 AM, Jatin Davey wrote: > On 5/6/2015 1:18 PM, Leon Fauster wrote: >> Am 06.05.2015 um 09:33 schrieb Jatin Davey <jashokda at cisco.com>: >>> My guest is a CentOS 5.4 VM: >> >> Best practice: update to the latest OS version: >> >> # cat /etc/redhat-release >> CentOS release 5.11 (Final) >> >> >> >>>

Hello all, On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote: > ivshmem has a performance disadvantage for guest-to-host > communication. Since the shared memory is exposed as PCI BARs, the > guest has to memcpy into the shared memory. > > vhost-user can access guest memory directly and avoid the copy inside the guest. Actually, you can avoid this memory copy using frameworks like

Hello all, On 06/17/2014 04:54 AM, Stefan Hajnoczi wrote: > ivshmem has a performance disadvantage for guest-to-host > communication. Since the shared memory is exposed as PCI BARs, the > guest has to memcpy into the shared memory. > > vhost-user can access guest memory directly and avoid the copy inside the guest. Actually, you can avoid this memory copy using frameworks like

Hi I''ve been doing this a while now. If I have a class that responds to : [], and all I''m interested in stubbing is that method, then instead of using a mock I just create a hash. (Similarly, you could create an array when you are testing an Enumerable object.) Example from code I just worked on, where uses MigrationGraph#[] looks up graph vertices by name:

Rails Core Weekly May 29 - June 4 Dear List, Another week has passed, here''s RCW, the McCartney Edition: This weeks kicks of with Josh Susser fixing has_and_belongs_to_many #create method to properly populate joins with new records :http://www.ruby-forum.com/topic/67478#new. Check out his test: def test_create_by_new_record devel = Developer.new(:name => "Marcel",

On 5/6/2015 1:18 PM, Leon Fauster wrote: > Am 06.05.2015 um 09:33 schrieb Jatin Davey <jashokda at cisco.com>: >> My guest is a CentOS 5.4 VM: > > Best practice: update to the latest OS version: > > # cat /etc/redhat-release > CentOS release 5.11 (Final) > > > >> [root at localhost ~]# uname -a >> Linux localhost 2.6.18-164.el5 #1 SMP Thu Sep 3