search for: v1.0

OASIS members and other interested parties, The Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 04 / Public Review Draft 04 28 May 2015 Specification overview: This document describes the specifications of the

OASIS members and other interested parties, The Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 04 / Public Review Draft 04 28 May 2015 Specification overview: This document describes the specifications of the

As you can probably guess from my today's burst of activity, I'm no longer extremely busy. Actually it looks like for the next 3-4 weeks I don't have anything especially time consuming to do. So it's time to get Dovecot v1.0 released :) I've now read all the mails from this list again, and it looks like pretty much the only problems with rc10 was the mbox assert crash, which

----- Forwarded message from Chet Ensign <chet.ensign at oasis-open.org> ----- Date: Fri, 28 Mar 2014 17:54:16 -0400 From: Chet Ensign <chet.ensign at oasis-open.org> To: tc-announce at lists.oasis-open.org, members at lists.oasis-open.org, virtio at lists.oasis-open.org, virtio-comment at lists.oasis-open.org Subject: [members] 15-day Public Review for Virtual I/O Device (VIRTIO)

----- Forwarded message from Chet Ensign <chet.ensign at oasis-open.org> ----- Date: Fri, 28 Mar 2014 17:54:16 -0400 From: Chet Ensign <chet.ensign at oasis-open.org> To: tc-announce at lists.oasis-open.org, members at lists.oasis-open.org, virtio at lists.oasis-open.org, virtio-comment at lists.oasis-open.org Subject: [members] 15-day Public Review for Virtual I/O Device (VIRTIO)

On Sun, Jan 13, 2013 at 7:39 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> > wrote: > >> Good points David, I don't feel qualified to evaluate the differences > >> between those versions though... Perhaps Richard or Doug could comment > here? > > > > Unless

On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> wrote: >> Good points David, I don't feel qualified to evaluate the differences >> between those versions though... Perhaps Richard or Doug could comment here? > > Unless I'm misreading the buildbots, we don't actually have anything > trying to build with MSVC. Have we considered how

Hi List, Does anyone know why the above URL is still using TLS V1.0. I can't connect to it unless I enable TLS V1.0 which I was under the impression that it should not be used anymore. Thanks for any enlightenment. Steve --

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

http://dovecot.org/releases/dovecot-1.0.0.tar.gz http://dovecot.org/releases/dovecot-1.0.0.tar.gz.sig It took almost 5 years, but it's finally ready. I'm not expecting to release v1.0.1 anytime soon, unless someone's been sitting on a major bug just waiting for v1.0 to be released. :) People wanting new features should start testing the upcoming v1.1. http://dovecot.org/nightly/

v1.1 plans have changed a bit. I'll release v1.1.alpha1 soon and hope to have a stable v1.1 in a month or two. The rest of the features that didn't make it into v1.1 will go to v1.2. I'll write more about this when v1.1 alpha is released. I also did a bit of benchmarking. v1.1's performance improvements are looking pretty great, it seems to be twice as fast as v1.0. v1.0:

Can you just compile the latest from the git repo on to raspian os? On Sat, Mar 31, 2018, 11:21 AM Ramses <ramses.sevilla at gmail.com> wrote: > El 29 de marzo de 2018 23:41:24 CEST, Ramses <ramses.sevilla at gmail.com> > escribió: > >Hi everyone, > > > >I have installed Tinc-VPN v1.0.19-3, that is the last version that > >there is in Raspbian 7,

Hi everyone, I need know if there is any command that show the hosts connected, networks, etc... in a Tinc-VPN v1.0 how in Tinc-VPN v1.1 Regards, Ramses

Hi everyone, I have installed Tinc-VPN v1.0.19-3 that is the last, versión that there is in Raspbian 7, installed with the apt-get command. I will like know what will be the best way to migrate this version to Tinc-VPN v1.1 Regards, Ramses

OASIS members and other interested parties, The OASIS Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 05 / Public Review Draft 05 29 October 2015 Specification Overview: This document describes the

OASIS members and other interested parties, The OASIS Virtual I/O Device (VIRTIO) TC members [1] have produced an updated Committee Specification Draft (CSD) and submitted this specification for 15-day public review: Virtual I/O Device (VIRTIO) Version 1.0 Committee Specification Draft 05 / Public Review Draft 05 29 October 2015 Specification Overview: This document describes the

http://dovecot.org/test/ Keywords are finally stored in maildir filenames and listed in "dovecot-keywords" file. It should be possible to just rename 0.99.x's .customflags file to dovecot-keywords (but it can't be renamed back after modification). Also fixed another uid/sequence mixup bug with setting keywords in general (in mbox too). Fixed SHA1 checksum generation with

On Tue, Nov 25, 2014 at 06:55:16PM +0100, Cornelia Huck wrote: > On Tue, 25 Nov 2014 18:42:18 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > Based on patch by Cornelia Huck. > > > > Note: for consistency, and to avoid sparse errors, > > convert all fields, even those no longer in use > > for virtio v1.0. > >

On Tue, Nov 25, 2014 at 06:55:16PM +0100, Cornelia Huck wrote: > On Tue, 25 Nov 2014 18:42:18 +0200 > "Michael S. Tsirkin" <mst at redhat.com> wrote: > > > Based on patch by Cornelia Huck. > > > > Note: for consistency, and to avoid sparse errors, > > convert all fields, even those no longer in use > > for virtio v1.0. > >

Hi Timo I use LDAP auth on a system with around 2000 email account. I use dual OpenLDAP servers. I haven't noticed a leak of memory. Is there any more information and I will have a look to see if I can see anything that might help. Is it only affecting certain machines or all? Regards Daniel Rowe Date: Mon, 16 Oct 2006 02:39:26 +0300 From: Timo Sirainen <tss at iki.fi> Subject: