From mirageos-devel-bounces@lists.xenproject.org Tue Dec 03 16:23:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Dec 2013 16:23:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vnskv-000449-Q2 for archives@lists.xenproject.org; Tue, 03 Dec 2013 16:23:25 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Welcome to the "Mirageos-devel" mailing list From: mirageos-devel-request@lists.xenproject.org To: archives@lists.xenproject.org X-No-Archive: yes Message-ID: Date: Tue, 03 Dec 2013 16:23:24 +0000 Precedence: bulk X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 List-Id: Developer list for MirageOS X-List-Administrivia: yes Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Welcome to the Mirageos-devel@lists.xenproject.org mailing list! To post to this list, send your email to: mirageos-devel@lists.xenproject.org General information about the mailing list is at: http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://lists.xenproject.org/cgi-bin/mailman/options/mirageos-devel/archives%40lists.xenproject.org You can also make such adjustments via email by sending a message to: Mirageos-devel-request@lists.xenproject.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: ehuvasxe Normally, Mailman will remind you of your lists.xenproject.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you. From mirageos-devel-bounces@lists.xenproject.org Tue Dec 03 16:23:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 03 Dec 2013 16:23:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vnskv-000449-Q2 for archives@lists.xenproject.org; Tue, 03 Dec 2013 16:23:25 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Welcome to the "Mirageos-devel" mailing list From: mirageos-devel-request@lists.xenproject.org To: archives@lists.xenproject.org X-No-Archive: yes Message-ID: Date: Tue, 03 Dec 2013 16:23:24 +0000 Precedence: bulk X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 List-Id: Developer list for MirageOS X-List-Administrivia: yes Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Welcome to the Mirageos-devel@lists.xenproject.org mailing list! To post to this list, send your email to: mirageos-devel@lists.xenproject.org General information about the mailing list is at: http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: http://lists.xenproject.org/cgi-bin/mailman/options/mirageos-devel/archives%40lists.xenproject.org You can also make such adjustments via email by sending a message to: Mirageos-devel-request@lists.xenproject.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: ehuvasxe Normally, Mailman will remind you of your lists.xenproject.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you. From mirageos-devel-bounces@lists.xenproject.org Wed Dec 04 13:11:01 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Dec 2013 13:11:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VoCEE-0000Kv-BJ; Wed, 04 Dec 2013 13:10:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VoCDZ-0000Dg-3x for mirageos-devel@lists.xenproject.org; Wed, 04 Dec 2013 13:10:17 +0000 Received: from [85.158.143.35:22964] by server-2.bemta-4.messagelabs.com id C7/2F-11386-8B92F925; Wed, 04 Dec 2013 13:10:16 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1386162614!3309734!1 X-Originating-IP: [74.125.83.54] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21924 invoked from network); 4 Dec 2013 13:10:15 -0000 Received: from mail-ee0-f54.google.com (HELO mail-ee0-f54.google.com) (74.125.83.54) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2013 13:10:14 -0000 Received: by mail-ee0-f54.google.com with SMTP id e51so2343456eek.41 for ; Wed, 04 Dec 2013 05:10:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=YciHz6gCvox/08Fy2QrvN3AcdimFA8mxmFysNebL/c0=; b=tozx/nEjxw1/g2UaBi8JqeLfnRUb5zlR9BfKNMXppGK+6/kw5wJHAB7mAfU7THAvVY xpHGSY5+hwc1cfAPYepNL+SXTzyyT3Q/fC2tmE8gfGNXcAv248GHeUwJLAn71SsK1xBv Q54V8BB9wGL+O3J3SIGKRz9sg5yBkKKuuP04RrOhqV+4X7XxWvU6e21qDixp/tPvOkOz uK4Yp4C2tRfJ6Hz7SolMlEgGw7asYyBU6owGCk+qdRarSCZLuYhI9DgZdVoNCwYCCsjB n3ONRTPsEURfYokMS4v+sX0VGYQADv0062qP2GcJkLKMuBYnnRMhyeI2YWah9pvXCnYU fNAQ== X-Received: by 10.15.82.8 with SMTP id z8mr53088916eey.25.1386162614580; Wed, 04 Dec 2013 05:10:14 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id z42sm22011047eeo.17.2013.12.04.05.10.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Dec 2013 05:10:13 -0800 (PST) Message-ID: <529F29B4.1000409@xen.org> Date: Wed, 04 Dec 2013 13:10:12 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <529F28F9.6070901@xen.org> In-Reply-To: <529F28F9.6070901@xen.org> X-Forwarded-Message-Id: <529F28F9.6070901@xen.org> X-Mailman-Approved-At: Wed, 04 Dec 2013 13:10:57 +0000 Subject: [MirageOS-devel] Migrating the Mirage List on Friday (Test E-Mail) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6837078638901046994==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============6837078638901046994== Content-Type: multipart/alternative; boundary="------------060208070704050501000800" This is a multi-part message in MIME format. --------------060208070704050501000800 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This is a test e-mail Regards -------- Original Message -------- Subject: Re: Migrating the Mirage List on Friday Date: Wed, 04 Dec 2013 13:07:05 +0000 From: Lars Kurth Reply-To: lars.kurth@xen.org To: cl-mirage@lists.cam.ac.uk Hi all, the new list exists at http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel - it is in emergency moderation mode right now, such that we can have a clean switch-over. I signed you all up and am about to forward this mail as test mail. Best Regards Lars On 03/12/2013 16:54, Amir Chaudhry wrote: > Dear all, > > As mentioned a few months ago, we've been planning to move the Mirage list to xen.org. That will now happen on Friday morning and here's how it'll go (you don't need to do anything). > > 1. A new list will be created at lists.xenproject.org (mirageos-devel@) > > 2. List members will be added to the new list. > > 3a. On Friday morning, this list will be put into moderation mode (ie to stop further messages being sent). Either myself or Anil will let everyone know when this happens. > > 3b. Shortly after the above, an email will be sent on the new list and it'll be open for business. > > 4. Archives will be ported across at a later date. > > The first two are already done (or underway). Just be aware of the new list address from Friday onwards. > > Thanks all! > > Best wishes, > Amir > > -- > sent via mobile --------------060208070704050501000800 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit This is a test e-mail
Regards

-------- Original Message --------
Subject: Re: Migrating the Mirage List on Friday
Date: Wed, 04 Dec 2013 13:07:05 +0000
From: Lars Kurth <lars.kurth@xen.org>
Reply-To: lars.kurth@xen.org
To: cl-mirage@lists.cam.ac.uk 


Hi all,
the new list exists at 
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel - it 
is in emergency moderation mode right now, such that we can have a clean 
switch-over. I signed you all up and am about to forward this mail as 
test mail.
Best Regards
Lars

On 03/12/2013 16:54, Amir Chaudhry wrote:
> Dear all,
>
> As mentioned a few months ago, we've been planning to move the Mirage list to xen.org. That will now happen on Friday morning and here's how it'll go (you don't need to do anything).
>
> 1. A new list will be created at lists.xenproject.org (mirageos-devel@)
>
> 2. List members will be added to the new list.
>
> 3a. On Friday morning, this list will be put into moderation mode (ie to stop further messages being sent). Either myself or Anil will let everyone know when this happens.
>
> 3b. Shortly after the above, an email will be sent on the new list and it'll be open for business.
>
> 4. Archives will be ported across at a later date.
>
> The first two are already done (or underway).  Just be aware of the new list address from Friday onwards.
>
> Thanks all!
>
> Best wishes,
> Amir
>
> --
> sent via mobile


--------------060208070704050501000800-- --===============6837078638901046994== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6837078638901046994==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 04 13:11:01 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 04 Dec 2013 13:11:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VoCEE-0000Kv-BJ; Wed, 04 Dec 2013 13:10:58 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VoCDZ-0000Dg-3x for mirageos-devel@lists.xenproject.org; Wed, 04 Dec 2013 13:10:17 +0000 Received: from [85.158.143.35:22964] by server-2.bemta-4.messagelabs.com id C7/2F-11386-8B92F925; Wed, 04 Dec 2013 13:10:16 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-14.tower-21.messagelabs.com!1386162614!3309734!1 X-Originating-IP: [74.125.83.54] X-SpamReason: No, hits=0.3 required=7.0 tests=HTML_50_60,HTML_MESSAGE, RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21924 invoked from network); 4 Dec 2013 13:10:15 -0000 Received: from mail-ee0-f54.google.com (HELO mail-ee0-f54.google.com) (74.125.83.54) by server-14.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 4 Dec 2013 13:10:14 -0000 Received: by mail-ee0-f54.google.com with SMTP id e51so2343456eek.41 for ; Wed, 04 Dec 2013 05:10:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:references:in-reply-to:content-type; bh=YciHz6gCvox/08Fy2QrvN3AcdimFA8mxmFysNebL/c0=; b=tozx/nEjxw1/g2UaBi8JqeLfnRUb5zlR9BfKNMXppGK+6/kw5wJHAB7mAfU7THAvVY xpHGSY5+hwc1cfAPYepNL+SXTzyyT3Q/fC2tmE8gfGNXcAv248GHeUwJLAn71SsK1xBv Q54V8BB9wGL+O3J3SIGKRz9sg5yBkKKuuP04RrOhqV+4X7XxWvU6e21qDixp/tPvOkOz uK4Yp4C2tRfJ6Hz7SolMlEgGw7asYyBU6owGCk+qdRarSCZLuYhI9DgZdVoNCwYCCsjB n3ONRTPsEURfYokMS4v+sX0VGYQADv0062qP2GcJkLKMuBYnnRMhyeI2YWah9pvXCnYU fNAQ== X-Received: by 10.15.82.8 with SMTP id z8mr53088916eey.25.1386162614580; Wed, 04 Dec 2013 05:10:14 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id z42sm22011047eeo.17.2013.12.04.05.10.13 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Dec 2013 05:10:13 -0800 (PST) Message-ID: <529F29B4.1000409@xen.org> Date: Wed, 04 Dec 2013 13:10:12 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <529F28F9.6070901@xen.org> In-Reply-To: <529F28F9.6070901@xen.org> X-Forwarded-Message-Id: <529F28F9.6070901@xen.org> X-Mailman-Approved-At: Wed, 04 Dec 2013 13:10:57 +0000 Subject: [MirageOS-devel] Migrating the Mirage List on Friday (Test E-Mail) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6837078638901046994==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a multi-part message in MIME format. --===============6837078638901046994== Content-Type: multipart/alternative; boundary="------------060208070704050501000800" This is a multi-part message in MIME format. --------------060208070704050501000800 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit This is a test e-mail Regards -------- Original Message -------- Subject: Re: Migrating the Mirage List on Friday Date: Wed, 04 Dec 2013 13:07:05 +0000 From: Lars Kurth Reply-To: lars.kurth@xen.org To: cl-mirage@lists.cam.ac.uk Hi all, the new list exists at http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel - it is in emergency moderation mode right now, such that we can have a clean switch-over. I signed you all up and am about to forward this mail as test mail. Best Regards Lars On 03/12/2013 16:54, Amir Chaudhry wrote: > Dear all, > > As mentioned a few months ago, we've been planning to move the Mirage list to xen.org. That will now happen on Friday morning and here's how it'll go (you don't need to do anything). > > 1. A new list will be created at lists.xenproject.org (mirageos-devel@) > > 2. List members will be added to the new list. > > 3a. On Friday morning, this list will be put into moderation mode (ie to stop further messages being sent). Either myself or Anil will let everyone know when this happens. > > 3b. Shortly after the above, an email will be sent on the new list and it'll be open for business. > > 4. Archives will be ported across at a later date. > > The first two are already done (or underway). Just be aware of the new list address from Friday onwards. > > Thanks all! > > Best wishes, > Amir > > -- > sent via mobile --------------060208070704050501000800 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit This is a test e-mail
Regards

-------- Original Message --------
Subject: Re: Migrating the Mirage List on Friday
Date: Wed, 04 Dec 2013 13:07:05 +0000
From: Lars Kurth <lars.kurth@xen.org>
Reply-To: lars.kurth@xen.org
To: cl-mirage@lists.cam.ac.uk 


Hi all,
the new list exists at 
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel - it 
is in emergency moderation mode right now, such that we can have a clean 
switch-over. I signed you all up and am about to forward this mail as 
test mail.
Best Regards
Lars

On 03/12/2013 16:54, Amir Chaudhry wrote:
> Dear all,
>
> As mentioned a few months ago, we've been planning to move the Mirage list to xen.org. That will now happen on Friday morning and here's how it'll go (you don't need to do anything).
>
> 1. A new list will be created at lists.xenproject.org (mirageos-devel@)
>
> 2. List members will be added to the new list.
>
> 3a. On Friday morning, this list will be put into moderation mode (ie to stop further messages being sent). Either myself or Anil will let everyone know when this happens.
>
> 3b. Shortly after the above, an email will be sent on the new list and it'll be open for business.
>
> 4. Archives will be ported across at a later date.
>
> The first two are already done (or underway).  Just be aware of the new list address from Friday onwards.
>
> Thanks all!
>
> Best wishes,
> Amir
>
> --
> sent via mobile


--------------060208070704050501000800-- --===============6837078638901046994== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6837078638901046994==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 06 22:27:39 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Dec 2013 22:27:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp3ry-0003sm-4j; Fri, 06 Dec 2013 22:27:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp3pk-0003sD-4R for mirageos-devel@lists.xenproject.org; Fri, 06 Dec 2013 22:25:16 +0000 Received: from [85.158.143.35:29027] by server-1.bemta-4.messagelabs.com id F9/0E-02132-BCE42A25; Fri, 06 Dec 2013 22:25:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1386368714!3962701!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18746 invoked from network); 6 Dec 2013 22:25:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 6 Dec 2013 22:25:14 -0000 Received: (qmail 26460 invoked by uid 634); 6 Dec 2013 22:25:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 06 Dec 2013 22:25:13 +0000 From: Anil Madhavapeddy Date: Fri, 6 Dec 2013 22:25:12 +0000 Message-Id: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 06 Dec 2013 22:27:33 +0000 Cc: Jeremy Yallop Subject: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli File "lib/v1.mli", line 250, characters 4-23: Error: This variant or record definition does not match that of type error Their kinds differ. Command exited with code 2. We're trying to define progressively richer modules -- a DEVICE that becomes a KV_RO (a read-only key/value store), which can be included into becoming a FS (filesystem). At each stage though, the error type is intended to grow some more. The error substitution seems to work for DEVICE->KV_RO, but fails with this in KV_RO->FS. Any thoughts welcome... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 06 22:27:39 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 06 Dec 2013 22:27:39 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp3ry-0003sm-4j; Fri, 06 Dec 2013 22:27:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp3pk-0003sD-4R for mirageos-devel@lists.xenproject.org; Fri, 06 Dec 2013 22:25:16 +0000 Received: from [85.158.143.35:29027] by server-1.bemta-4.messagelabs.com id F9/0E-02132-BCE42A25; Fri, 06 Dec 2013 22:25:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-21.messagelabs.com!1386368714!3962701!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18746 invoked from network); 6 Dec 2013 22:25:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-21.messagelabs.com with SMTP; 6 Dec 2013 22:25:14 -0000 Received: (qmail 26460 invoked by uid 634); 6 Dec 2013 22:25:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 06 Dec 2013 22:25:13 +0000 From: Anil Madhavapeddy Date: Fri, 6 Dec 2013 22:25:12 +0000 Message-Id: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org X-Mailman-Approved-At: Fri, 06 Dec 2013 22:27:33 +0000 Cc: Jeremy Yallop Subject: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli File "lib/v1.mli", line 250, characters 4-23: Error: This variant or record definition does not match that of type error Their kinds differ. Command exited with code 2. We're trying to define progressively richer modules -- a DEVICE that becomes a KV_RO (a read-only key/value store), which can be included into becoming a FS (filesystem). At each stage though, the error type is intended to grow some more. The error substitution seems to work for DEVICE->KV_RO, but fails with this in KV_RO->FS. Any thoughts welcome... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 07 00:08:16 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 07 Dec 2013 00:08:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5RP-00021e-4z; Sat, 07 Dec 2013 00:08:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5RN-00020y-2g for mirageos-devel@lists.xenproject.org; Sat, 07 Dec 2013 00:08:13 +0000 Received: from [85.158.139.211:53220] by server-12.bemta-5.messagelabs.com id 78/48-30017-CE662A25; Sat, 07 Dec 2013 00:08:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1386374891!2885128!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25565 invoked from network); 7 Dec 2013 00:08:11 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 7 Dec 2013 00:08:11 -0000 Received: (qmail 18892 invoked by uid 634); 7 Dec 2013 00:08:10 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 07 Dec 2013 00:08:09 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> Date: Sat, 7 Dec 2013 00:08:11 +0000 Message-Id: <06874914-70D9-417F-8C5C-8ADAC6264D6F@recoil.org> References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Jeremy Yallop , David Sheets Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 Dec 2013, at 22:25, Anil Madhavapeddy wrote: > Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): > > https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli > > File "lib/v1.mli", line 250, characters 4-23: > Error: This variant or record definition does not match that of type error > Their kinds differ. > Command exited with code 2. > > We're trying to define progressively richer modules -- a DEVICE that becomes a KV_RO (a read-only key/value store), which can be included into becoming a FS (filesystem). At each stage though, the error type is intended to grow some more. The error substitution seems to work for DEVICE->KV_RO, but fails with this in KV_RO->FS. The original error was due to an errant mismatch between a polymorphic variant and a normal one, now fixed. There's still some difficulty in the variance of the polymorphic variant for the error type, so Dave's just duplicated the FS/KV_RO definitions in mirage/mirage-types for now. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 07 00:08:16 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 07 Dec 2013 00:08:16 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5RP-00021e-4z; Sat, 07 Dec 2013 00:08:15 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5RN-00020y-2g for mirageos-devel@lists.xenproject.org; Sat, 07 Dec 2013 00:08:13 +0000 Received: from [85.158.139.211:53220] by server-12.bemta-5.messagelabs.com id 78/48-30017-CE662A25; Sat, 07 Dec 2013 00:08:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-206.messagelabs.com!1386374891!2885128!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25565 invoked from network); 7 Dec 2013 00:08:11 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-206.messagelabs.com with SMTP; 7 Dec 2013 00:08:11 -0000 Received: (qmail 18892 invoked by uid 634); 7 Dec 2013 00:08:10 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 07 Dec 2013 00:08:09 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> Date: Sat, 7 Dec 2013 00:08:11 +0000 Message-Id: <06874914-70D9-417F-8C5C-8ADAC6264D6F@recoil.org> References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: mirageos-devel@lists.xenproject.org X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Jeremy Yallop , David Sheets Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 Dec 2013, at 22:25, Anil Madhavapeddy wrote: > Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): > > https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli > > File "lib/v1.mli", line 250, characters 4-23: > Error: This variant or record definition does not match that of type error > Their kinds differ. > Command exited with code 2. > > We're trying to define progressively richer modules -- a DEVICE that becomes a KV_RO (a read-only key/value store), which can be included into becoming a FS (filesystem). At each stage though, the error type is intended to grow some more. The error substitution seems to work for DEVICE->KV_RO, but fails with this in KV_RO->FS. The original error was due to an errant mismatch between a polymorphic variant and a normal one, now fixed. There's still some difficulty in the variance of the polymorphic variant for the error type, so Dave's just duplicated the FS/KV_RO definitions in mirage/mirage-types for now. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 07 00:18:00 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 07 Dec 2013 00:18:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5ap-0002xK-3I; Sat, 07 Dec 2013 00:17:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5Xi-0002wa-2s for mirageos-devel@lists.xenproject.org; Sat, 07 Dec 2013 00:14:46 +0000 Received: from [193.109.254.147:51249] by server-15.bemta-14.messagelabs.com id 3D/1C-22186-57862A25; Sat, 07 Dec 2013 00:14:45 +0000 X-Env-Sender: jdy22@hermes.cam.ac.uk X-Msg-Ref: server-6.tower-27.messagelabs.com!1386375284!3546264!1 X-Originating-IP: [131.111.8.142] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32076 invoked from network); 7 Dec 2013 00:14:44 -0000 Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk) (131.111.8.142) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Dec 2013 00:14:44 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-wg0-f41.google.com ([74.125.82.41]:38789) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jdy22) (TLSv1:RC4-SHA:128) id 1Vp5Xg-0008IX-7d (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Sat, 07 Dec 2013 00:14:44 +0000 Received: by mail-wg0-f41.google.com with SMTP id y10so1448482wgg.0 for ; Fri, 06 Dec 2013 16:14:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=moincFPzjd1wvmXLy+7hts1L4FzJYBHwLZdIXuxkL3c=; b=DPpxmUy2FW4N1wjD99FcMxsNCLxxKLwfeCs5spafBAI/9CMWQ/40fn3sxrLYmFJqEV 5EleKecJ1LBLyEnuJd5JejiouBaHY5l0R5o/iBPtr/SSAV3d2p6es5JQu29o7OvHACHk eXcnT8ooFJkB6w3KOjZCRO/Q6ualuOc78t1keze3J9Fu7xS4iyL/L5uI5rRCjsF4mZj5 KpDevbtPtlT3FMgs+4Crph5PVSMQ7ldUoM1BpRKdQIbkjp7CFfUNgHnezpwqBqrYZ6p/ ij2vz5aVUC4jCoYv5zH/LIn/wjR3ndaUqpeJOhTC5vO6miK5T/82U6rYc38T3emw/ZWO lbeA== MIME-Version: 1.0 X-Received: by 10.180.82.161 with SMTP id j1mr4711042wiy.23.1386375281128; Fri, 06 Dec 2013 16:14:41 -0800 (PST) Received: by 10.216.33.4 with HTTP; Fri, 6 Dec 2013 16:14:41 -0800 (PST) In-Reply-To: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> Date: Sat, 7 Dec 2013 00:14:41 +0000 Message-ID: From: Jeremy Yallop To: Anil Madhavapeddy X-Mailman-Approved-At: Sat, 07 Dec 2013 00:17:57 +0000 Cc: Jeremy Yallop , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 December 2013 22:25, Anil Madhavapeddy wrote: > Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): > > https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli > > File "lib/v1.mli", line 250, characters 4-23: > Error: This variant or record definition does not match that of type error > Their kinds differ. > Command exited with code 2. This is due to the fix for PR6005 (http://caml.inria.fr/mantis/view.php?id=6005). There's also some useful discussion under PR6159. The high-level summary is that you can't use destructive substitution to replace concrete types in signatures with incompatible types, although OCaml versions before 4.01.0 didn't properly enforce that. The simplest fix is to simply leave the error type abstract until the leaf module types. There's a slightly neater approach in this case, though: make the error type in KV_RO a private row, and extend it in FS. The definition of error in KV_RO would then be type error = private [> `Unknown_key of string ] and the definition of error in FS would become type error = [ | `Not_a_directory of string (* ... *) | `Block_device of block_device_error | `Unknown_key of string ] (The minor downside is that callers of KV_RO.read would need to handle both `Error (`Unknown_key s) and some unspecified/unknowable set of tags.) Jeremy. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 07 00:18:00 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 07 Dec 2013 00:18:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5ap-0002xK-3I; Sat, 07 Dec 2013 00:17:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vp5Xi-0002wa-2s for mirageos-devel@lists.xenproject.org; Sat, 07 Dec 2013 00:14:46 +0000 Received: from [193.109.254.147:51249] by server-15.bemta-14.messagelabs.com id 3D/1C-22186-57862A25; Sat, 07 Dec 2013 00:14:45 +0000 X-Env-Sender: jdy22@hermes.cam.ac.uk X-Msg-Ref: server-6.tower-27.messagelabs.com!1386375284!3546264!1 X-Originating-IP: [131.111.8.142] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE0MiA9PiAxMTg0OA==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32076 invoked from network); 7 Dec 2013 00:14:44 -0000 Received: from ppsw-42.csi.cam.ac.uk (HELO ppsw-42.csi.cam.ac.uk) (131.111.8.142) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 7 Dec 2013 00:14:44 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-wg0-f41.google.com ([74.125.82.41]:38789) by ppsw-42.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.159]:587) with esmtpsa (PLAIN:jdy22) (TLSv1:RC4-SHA:128) id 1Vp5Xg-0008IX-7d (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Sat, 07 Dec 2013 00:14:44 +0000 Received: by mail-wg0-f41.google.com with SMTP id y10so1448482wgg.0 for ; Fri, 06 Dec 2013 16:14:41 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=moincFPzjd1wvmXLy+7hts1L4FzJYBHwLZdIXuxkL3c=; b=DPpxmUy2FW4N1wjD99FcMxsNCLxxKLwfeCs5spafBAI/9CMWQ/40fn3sxrLYmFJqEV 5EleKecJ1LBLyEnuJd5JejiouBaHY5l0R5o/iBPtr/SSAV3d2p6es5JQu29o7OvHACHk eXcnT8ooFJkB6w3KOjZCRO/Q6ualuOc78t1keze3J9Fu7xS4iyL/L5uI5rRCjsF4mZj5 KpDevbtPtlT3FMgs+4Crph5PVSMQ7ldUoM1BpRKdQIbkjp7CFfUNgHnezpwqBqrYZ6p/ ij2vz5aVUC4jCoYv5zH/LIn/wjR3ndaUqpeJOhTC5vO6miK5T/82U6rYc38T3emw/ZWO lbeA== MIME-Version: 1.0 X-Received: by 10.180.82.161 with SMTP id j1mr4711042wiy.23.1386375281128; Fri, 06 Dec 2013 16:14:41 -0800 (PST) Received: by 10.216.33.4 with HTTP; Fri, 6 Dec 2013 16:14:41 -0800 (PST) In-Reply-To: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> Date: Sat, 7 Dec 2013 00:14:41 +0000 Message-ID: From: Jeremy Yallop To: Anil Madhavapeddy X-Mailman-Approved-At: Sat, 07 Dec 2013 00:17:57 +0000 Cc: Jeremy Yallop , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 6 December 2013 22:25, Anil Madhavapeddy wrote: > Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): > > https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli > > File "lib/v1.mli", line 250, characters 4-23: > Error: This variant or record definition does not match that of type error > Their kinds differ. > Command exited with code 2. This is due to the fix for PR6005 (http://caml.inria.fr/mantis/view.php?id=6005). There's also some useful discussion under PR6159. The high-level summary is that you can't use destructive substitution to replace concrete types in signatures with incompatible types, although OCaml versions before 4.01.0 didn't properly enforce that. The simplest fix is to simply leave the error type abstract until the leaf module types. There's a slightly neater approach in this case, though: make the error type in KV_RO a private row, and extend it in FS. The definition of error in KV_RO would then be type error = private [> `Unknown_key of string ] and the definition of error in FS would become type error = [ | `Not_a_directory of string (* ... *) | `Block_device of block_device_error | `Unknown_key of string ] (The minor downside is that callers of KV_RO.read would need to handle both `Error (`Unknown_key s) and some unspecified/unknowable set of tags.) Jeremy. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 13:32:01 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 13:32:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpeSi-0000bU-LI; Sun, 08 Dec 2013 13:31:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpeSh-0000bP-R4 for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 13:31:56 +0000 Received: from [85.158.137.68:45496] by server-17.bemta-3.messagelabs.com id 77/EE-15965-AC474A25; Sun, 08 Dec 2013 13:31:54 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-31.messagelabs.com!1386509513!2494172!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16015 invoked from network); 8 Dec 2013 13:31:54 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-2.tower-31.messagelabs.com with SMTP; 8 Dec 2013 13:31:54 -0000 Received: (qmail 19209 invoked from network); 8 Dec 2013 13:31:50 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 8 Dec 2013 13:31:50 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 18594-09 for ; Sun, 8 Dec 2013 13:31:49 +0000 (GMT) Received: (qmail 19193 invoked by uid 599); 8 Dec 2013 13:31:49 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 13:31:49 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VpeSd-0000lK-Bf for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 13:31:51 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" , Mirage List Date: Sun, 8 Dec 2013 13:31:50 +0000 Thread-Topic: opam repository problems Thread-Index: Ac70Gdnju7cCRJnlRv+A1/IBfu/v2w== Message-ID: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Subject: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org is anyone else noticing anything? from what i can currently observe, + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 are these know problems, or should i file issues somewhere? (the combination is holding up some PRs for dependencies for the mirage blogging libraries because they can't pass travis...) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 13:32:01 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 13:32:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpeSi-0000bU-LI; Sun, 08 Dec 2013 13:31:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpeSh-0000bP-R4 for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 13:31:56 +0000 Received: from [85.158.137.68:45496] by server-17.bemta-3.messagelabs.com id 77/EE-15965-AC474A25; Sun, 08 Dec 2013 13:31:54 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-2.tower-31.messagelabs.com!1386509513!2494172!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16015 invoked from network); 8 Dec 2013 13:31:54 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-2.tower-31.messagelabs.com with SMTP; 8 Dec 2013 13:31:54 -0000 Received: (qmail 19209 invoked from network); 8 Dec 2013 13:31:50 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 8 Dec 2013 13:31:50 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 18594-09 for ; Sun, 8 Dec 2013 13:31:49 +0000 (GMT) Received: (qmail 19193 invoked by uid 599); 8 Dec 2013 13:31:49 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 13:31:49 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VpeSd-0000lK-Bf for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 13:31:51 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" , Mirage List Date: Sun, 8 Dec 2013 13:31:50 +0000 Thread-Topic: opam repository problems Thread-Index: Ac70Gdnju7cCRJnlRv+A1/IBfu/v2w== Message-ID: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Subject: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org is anyone else noticing anything? from what i can currently observe, + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 are these know problems, or should i file issues somewhere? (the combination is holding up some PRs for dependencies for the mirage blogging libraries because they can't pass travis...) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:02:21 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:02:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpew8-0001k5-67; Sun, 08 Dec 2013 14:02:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpew6-0001k0-Rg for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:02:19 +0000 Received: from [193.109.254.147:44896] by server-4.bemta-14.messagelabs.com id 89/64-03916-9EB74A25; Sun, 08 Dec 2013 14:02:17 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1386511337!2221909!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12490 invoked from network); 8 Dec 2013 14:02:17 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-27.messagelabs.com with SMTP; 8 Dec 2013 14:02:17 -0000 Received: (qmail 4648 invoked by uid 634); 8 Dec 2013 14:02:16 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-212-230.in-addr.btopenworld.com (HELO [10.0.1.33]) (81.149.212.230) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Dec 2013 14:02:13 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> Date: Sun, 8 Dec 2013 14:02:11 +0000 Message-Id: <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 13:31, Richard Mortier wrote: > is anyone else noticing anything? from what i can currently observe, > > + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) > > + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 [CCing opam-devel] OPAM 1.1 changed the repository format sufficiently that an OPAM 1.0 client can no longer read a 1.1-format repository. Therefore, the transition to OPAM 1.1 also involved setting up a new 1.1-only repository, which we put at https://opam.ocaml.org. In order to migrate people from the old repo to the new one, we also added a 'repo' file that can issue a redirect when a 1.1 client connects to the old 1.0 repositories. So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org. OPAM 1.0 is now deprecated. I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that. In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in. Which packages are you blocked on atm? Sylvain just fixed forge.ocamlcore.org, which also went down last night and broke some packages. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:02:21 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:02:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpew8-0001k5-67; Sun, 08 Dec 2013 14:02:20 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpew6-0001k0-Rg for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:02:19 +0000 Received: from [193.109.254.147:44896] by server-4.bemta-14.messagelabs.com id 89/64-03916-9EB74A25; Sun, 08 Dec 2013 14:02:17 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-16.tower-27.messagelabs.com!1386511337!2221909!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 12490 invoked from network); 8 Dec 2013 14:02:17 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-16.tower-27.messagelabs.com with SMTP; 8 Dec 2013 14:02:17 -0000 Received: (qmail 4648 invoked by uid 634); 8 Dec 2013 14:02:16 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-212-230.in-addr.btopenworld.com (HELO [10.0.1.33]) (81.149.212.230) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Dec 2013 14:02:13 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> Date: Sun, 8 Dec 2013 14:02:11 +0000 Message-Id: <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 13:31, Richard Mortier wrote: > is anyone else noticing anything? from what i can currently observe, > > + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) > > + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 [CCing opam-devel] OPAM 1.1 changed the repository format sufficiently that an OPAM 1.0 client can no longer read a 1.1-format repository. Therefore, the transition to OPAM 1.1 also involved setting up a new 1.1-only repository, which we put at https://opam.ocaml.org. In order to migrate people from the old repo to the new one, we also added a 'repo' file that can issue a redirect when a 1.1 client connects to the old 1.0 repositories. So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org. OPAM 1.0 is now deprecated. I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that. In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in. Which packages are you blocked on atm? Sylvain just fixed forge.ocamlcore.org, which also went down last night and broke some packages. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:08:01 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:08:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf1c-0001lW-N3; Sun, 08 Dec 2013 14:08:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf1b-0001lR-R9 for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:08:00 +0000 Received: from [85.158.143.35:58377] by server-2.bemta-4.messagelabs.com id 9A/8F-11386-F3D74A25; Sun, 08 Dec 2013 14:07:59 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1386511678!4135366!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6179 invoked from network); 8 Dec 2013 14:07:58 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-12.tower-21.messagelabs.com with SMTP; 8 Dec 2013 14:07:58 -0000 Received: (qmail 12224 invoked from network); 8 Dec 2013 14:07:54 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 8 Dec 2013 14:07:54 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 10770-04 for ; Sun, 8 Dec 2013 14:07:52 +0000 (GMT) Received: (qmail 12212 invoked by uid 599); 8 Dec 2013 14:07:51 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 14:07:51 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vpf1W-0001Jp-9a; Sun, 08 Dec 2013 14:07:54 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 8 Dec 2013 14:07:54 +0000 Thread-Topic: opam repository problems Thread-Index: Ac70HuMVHD+YU2nmTK+NSvuMXIe7cg== Message-ID: <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> In-Reply-To: <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:02, Anil Madhavapeddy wrote: > On 8 Dec 2013, at 13:31, Richard Mortier wrote: > >> is anyone else noticing anything? from what i can currently observe, >> >> + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) >> >> + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 > ... > So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org. OPAM 1.0 is now deprecated. I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that. In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in. don't think it's anything to do with non-http remotes. ok-- just to be clear then: + we're only interested in opam.1.1.0 *not* in opam.1.0.0 + the correct default opam repo to use is http://opam.ocaml.org ? in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please? > Which packages are you blocked on atm? Sylvain just fixed forge.ocamlcore.org, which also went down last night and broke some packages. patches to ocaml-cow to support omd (requires omd >= 0.8 or so), required by patches to cowabloga and (soon perhaps) mirage-www (and right now, my new website though noone else need care about that :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:08:01 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:08:01 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf1c-0001lW-N3; Sun, 08 Dec 2013 14:08:00 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf1b-0001lR-R9 for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:08:00 +0000 Received: from [85.158.143.35:58377] by server-2.bemta-4.messagelabs.com id 9A/8F-11386-F3D74A25; Sun, 08 Dec 2013 14:07:59 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1386511678!4135366!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6179 invoked from network); 8 Dec 2013 14:07:58 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-12.tower-21.messagelabs.com with SMTP; 8 Dec 2013 14:07:58 -0000 Received: (qmail 12224 invoked from network); 8 Dec 2013 14:07:54 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 8 Dec 2013 14:07:54 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 10770-04 for ; Sun, 8 Dec 2013 14:07:52 +0000 (GMT) Received: (qmail 12212 invoked by uid 599); 8 Dec 2013 14:07:51 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 14:07:51 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vpf1W-0001Jp-9a; Sun, 08 Dec 2013 14:07:54 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 8 Dec 2013 14:07:54 +0000 Thread-Topic: opam repository problems Thread-Index: Ac70HuMVHD+YU2nmTK+NSvuMXIe7cg== Message-ID: <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> In-Reply-To: <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:02, Anil Madhavapeddy wrote: > On 8 Dec 2013, at 13:31, Richard Mortier wrote: > >> is anyone else noticing anything? from what i can currently observe, >> >> + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) >> >> + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 > ... > So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org. OPAM 1.0 is now deprecated. I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that. In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in. don't think it's anything to do with non-http remotes. ok-- just to be clear then: + we're only interested in opam.1.1.0 *not* in opam.1.0.0 + the correct default opam repo to use is http://opam.ocaml.org ? in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please? > Which packages are you blocked on atm? Sylvain just fixed forge.ocamlcore.org, which also went down last night and broke some packages. patches to ocaml-cow to support omd (requires omd >= 0.8 or so), required by patches to cowabloga and (soon perhaps) mirage-www (and right now, my new website though noone else need care about that :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:12:00 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:12:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf5U-00024p-2F; Sun, 08 Dec 2013 14:12:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf5S-00024k-KF for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:11:58 +0000 Received: from [193.109.254.147:37974] by server-5.bemta-14.messagelabs.com id 4E/B3-03510-E2E74A25; Sun, 08 Dec 2013 14:11:58 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1386511916!3705048!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10118 invoked from network); 8 Dec 2013 14:11:57 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-27.messagelabs.com with SMTP; 8 Dec 2013 14:11:57 -0000 Received: (qmail 2629 invoked by uid 634); 8 Dec 2013 14:11:56 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-212-230.in-addr.btopenworld.com (HELO [10.0.1.33]) (81.149.212.230) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Dec 2013 14:11:56 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> Date: Sun, 8 Dec 2013 14:11:53 +0000 Message-Id: References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:07, Richard Mortier wrote: > > On 8 Dec 2013, at 14:02, Anil Madhavapeddy wrote: > >> On 8 Dec 2013, at 13:31, Richard Mortier wrote: >> >>> is anyone else noticing anything? from what i can currently observe, >>> >>> + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) >>> >>> + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 >> > ... >> So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org. OPAM 1.0 is now deprecated. I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that. In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in. > > don't think it's anything to do with non-http remotes. ok-- just to be clear then: > > + we're only interested in opam.1.1.0 *not* in opam.1.0.0 > > + the correct default opam repo to use is http://opam.ocaml.org That's correct (to clarify, https://opam.ocaml.org works too, not just the http:// URL). OPAM 1.1 is in both Debian unstable and Homebrew now, so there's no point supporting the older version. > > in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please? I'm confused -- which PPA has opam.ocamlpro.com hardcoded in? They should all be on OPAM 1.1 now. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:12:00 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:12:00 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf5U-00024p-2F; Sun, 08 Dec 2013 14:12:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf5S-00024k-KF for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:11:58 +0000 Received: from [193.109.254.147:37974] by server-5.bemta-14.messagelabs.com id 4E/B3-03510-E2E74A25; Sun, 08 Dec 2013 14:11:58 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-12.tower-27.messagelabs.com!1386511916!3705048!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10118 invoked from network); 8 Dec 2013 14:11:57 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-12.tower-27.messagelabs.com with SMTP; 8 Dec 2013 14:11:57 -0000 Received: (qmail 2629 invoked by uid 634); 8 Dec 2013 14:11:56 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-212-230.in-addr.btopenworld.com (HELO [10.0.1.33]) (81.149.212.230) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Dec 2013 14:11:56 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> Date: Sun, 8 Dec 2013 14:11:53 +0000 Message-Id: References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:07, Richard Mortier wrote: > > On 8 Dec 2013, at 14:02, Anil Madhavapeddy wrote: > >> On 8 Dec 2013, at 13:31, Richard Mortier wrote: >> >>> is anyone else noticing anything? from what i can currently observe, >>> >>> + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 rather than omd.0.8.2 for example) >>> >>> + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opam.1.0.0 >> > ... >> So the summary of all this is that you should be using OPAM 1.1, and only with opam.ocaml.org. OPAM 1.0 is now deprecated. I don't think we've done a particularly good job of communicating this on the OPAM website though, so I'd quite like to clarify that. In particular, if someone was using opam.ocamlpro.com via a non-HTTP remote (e.g. git), then the repo redirect will not kick in. > > don't think it's anything to do with non-http remotes. ok-- just to be clear then: > > + we're only interested in opam.1.1.0 *not* in opam.1.0.0 > > + the correct default opam repo to use is http://opam.ocaml.org That's correct (to clarify, https://opam.ocaml.org works too, not just the http:// URL). OPAM 1.1 is in both Debian unstable and Homebrew now, so there's no point supporting the older version. > > in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please? I'm confused -- which PPA has opam.ocamlpro.com hardcoded in? They should all be on OPAM 1.1 now. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:14:12 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:14:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf7a-000269-AA; Sun, 08 Dec 2013 14:14:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf7Y-000264-Jp for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:14:08 +0000 Received: from [85.158.137.68:28564] by server-13.bemta-3.messagelabs.com id 2E/07-28603-FAE74A25; Sun, 08 Dec 2013 14:14:07 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-31.messagelabs.com!1386512047!2423510!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13170 invoked from network); 8 Dec 2013 14:14:07 -0000 Received: from unknown (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-12.tower-31.messagelabs.com with SMTP; 8 Dec 2013 14:14:07 -0000 Received: (qmail 844 invoked from network); 8 Dec 2013 14:13:01 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 8 Dec 2013 14:13:01 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 32661-10 for ; Sun, 8 Dec 2013 14:13:00 +0000 (GMT) Received: (qmail 832 invoked by uid 599); 8 Dec 2013 14:13:00 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 14:13:00 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vpf6V-0001NA-Gt; Sun, 08 Dec 2013 14:13:03 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 8 Dec 2013 14:13:04 +0000 Thread-Topic: opam repository problems Thread-Index: Ac70H5t8FN6bAoEgQ+ubyU6hIz/dOg== Message-ID: <5B416A28-39ED-4C09-98BD-BE2BA62941C3@nottingham.ac.uk> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:11, Anil Madhavapeddy wrote: > On 8 Dec 2013, at 14:07, Richard Mortier wrote: > >> don't think it's anything to do with non-http remotes. ok-- just to be clear then: >> >> + we're only interested in opam.1.1.0 *not* in opam.1.0.0 >> >> + the correct default opam repo to use is http://opam.ocaml.org > > That's correct (to clarify, https://opam.ocaml.org works too, not just the http:// URL). > > OPAM 1.1 is in both Debian unstable and Homebrew now, so there's no point supporting the older version. ok. >> in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please? > > I'm confused -- which PPA has opam.ocamlpro.com hardcoded in? They should all be on OPAM 1.1 now. hm. maybe it was only the old opam.1.0.0 ones. let me check again. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:14:12 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:14:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf7a-000269-AA; Sun, 08 Dec 2013 14:14:10 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpf7Y-000264-Jp for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:14:08 +0000 Received: from [85.158.137.68:28564] by server-13.bemta-3.messagelabs.com id 2E/07-28603-FAE74A25; Sun, 08 Dec 2013 14:14:07 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-31.messagelabs.com!1386512047!2423510!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13170 invoked from network); 8 Dec 2013 14:14:07 -0000 Received: from unknown (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-12.tower-31.messagelabs.com with SMTP; 8 Dec 2013 14:14:07 -0000 Received: (qmail 844 invoked from network); 8 Dec 2013 14:13:01 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 8 Dec 2013 14:13:01 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 32661-10 for ; Sun, 8 Dec 2013 14:13:00 +0000 (GMT) Received: (qmail 832 invoked by uid 599); 8 Dec 2013 14:13:00 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 14:13:00 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vpf6V-0001NA-Gt; Sun, 08 Dec 2013 14:13:03 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 8 Dec 2013 14:13:04 +0000 Thread-Topic: opam repository problems Thread-Index: Ac70H5t8FN6bAoEgQ+ubyU6hIz/dOg== Message-ID: <5B416A28-39ED-4C09-98BD-BE2BA62941C3@nottingham.ac.uk> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:11, Anil Madhavapeddy wrote: > On 8 Dec 2013, at 14:07, Richard Mortier wrote: > >> don't think it's anything to do with non-http remotes. ok-- just to be clear then: >> >> + we're only interested in opam.1.1.0 *not* in opam.1.0.0 >> >> + the correct default opam repo to use is http://opam.ocaml.org > > That's correct (to clarify, https://opam.ocaml.org works too, not just the http:// URL). > > OPAM 1.1 is in both Debian unstable and Homebrew now, so there's no point supporting the older version. ok. >> in which case i'm fine, things build under those conditions. but i'll strip out the needless tests from the .travis.yml in at least a few repos; and could you update your ppa sometime so that the default opam remote is opam.ocaml.org rather than opam.ocamlpro.org please? > > I'm confused -- which PPA has opam.ocamlpro.com hardcoded in? They should all be on OPAM 1.1 now. hm. maybe it was only the old opam.1.0.0 ones. let me check again. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:16:57 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:16:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpfAH-00027H-J1; Sun, 08 Dec 2013 14:16:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpfAG-00027C-6P for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:16:56 +0000 Received: from [85.158.137.68:37120] by server-9.bemta-3.messagelabs.com id 9B/75-13104-75F74A25; Sun, 08 Dec 2013 14:16:55 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-31.messagelabs.com!1386512214!2464470!1 X-Originating-IP: [93.95.15.170] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1992 invoked from network); 8 Dec 2013 14:16:54 -0000 Received: from engine03-20433-3.icritical.com (HELO engine03-20433-3.icritical.com) (93.95.15.170) by server-14.tower-31.messagelabs.com with SMTP; 8 Dec 2013 14:16:54 -0000 Received: (qmail 25937 invoked from network); 8 Dec 2013 14:16:53 -0000 Received: from localhost (127.0.0.1) by engine03-20433-3.icritical.com with SMTP; 8 Dec 2013 14:16:53 -0000 Received: from engine03-20433-3.icritical.com ([127.0.0.1]) by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 24879-07 for ; Sun, 8 Dec 2013 14:16:52 +0000 (GMT) Received: (qmail 25925 invoked by uid 599); 8 Dec 2013 14:16:52 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 14:16:52 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VpfAA-0005xC-L0; Sun, 08 Dec 2013 14:16:50 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 8 Dec 2013 14:16:51 +0000 Thread-Topic: [MirageOS-devel] opam repository problems Thread-Index: Ac70ICKodtocYfyQQaGXy/UB3jTqUA== Message-ID: <9040CCC8-5B93-43D0-8B4C-16B0D1F472C1@nottingham.ac.uk> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> <5B416A28-39ED-4C09-98BD-BE2BA62941C3@nottingham.ac.uk> In-Reply-To: <5B416A28-39ED-4C09-98BD-BE2BA62941C3@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:13, Richard Mortier wrote: > > On 8 Dec 2013, at 14:11, Anil Madhavapeddy wrote: >> >> I'm confused -- which PPA has opam.ocamlpro.com hardcoded in? They should all be on OPAM 1.1 now. > > hm. maybe it was only the old opam.1.0.0 ones. let me check again. it was. problem solved :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 14:16:57 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 14:16:57 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpfAH-00027H-J1; Sun, 08 Dec 2013 14:16:57 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VpfAG-00027C-6P for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 14:16:56 +0000 Received: from [85.158.137.68:37120] by server-9.bemta-3.messagelabs.com id 9B/75-13104-75F74A25; Sun, 08 Dec 2013 14:16:55 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-31.messagelabs.com!1386512214!2464470!1 X-Originating-IP: [93.95.15.170] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1992 invoked from network); 8 Dec 2013 14:16:54 -0000 Received: from engine03-20433-3.icritical.com (HELO engine03-20433-3.icritical.com) (93.95.15.170) by server-14.tower-31.messagelabs.com with SMTP; 8 Dec 2013 14:16:54 -0000 Received: (qmail 25937 invoked from network); 8 Dec 2013 14:16:53 -0000 Received: from localhost (127.0.0.1) by engine03-20433-3.icritical.com with SMTP; 8 Dec 2013 14:16:53 -0000 Received: from engine03-20433-3.icritical.com ([127.0.0.1]) by localhost (engine03-20433-3.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 24879-07 for ; Sun, 8 Dec 2013 14:16:52 +0000 (GMT) Received: (qmail 25925 invoked by uid 599); 8 Dec 2013 14:16:52 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine03-20433-3.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 14:16:52 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VpfAA-0005xC-L0; Sun, 08 Dec 2013 14:16:50 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 8 Dec 2013 14:16:51 +0000 Thread-Topic: [MirageOS-devel] opam repository problems Thread-Index: Ac70ICKodtocYfyQQaGXy/UB3jTqUA== Message-ID: <9040CCC8-5B93-43D0-8B4C-16B0D1F472C1@nottingham.ac.uk> References: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> <0315AFDF-1C7D-4A20-AF81-A21E1408199B@recoil.org> <5426EE3E-1737-4909-85A9-630A7AD4305F@nottingham.ac.uk> <5B416A28-39ED-4C09-98BD-BE2BA62941C3@nottingham.ac.uk> In-Reply-To: <5B416A28-39ED-4C09-98BD-BE2BA62941C3@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-3.icritical.com Cc: opam-devel , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] opam repository problems X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 14:13, Richard Mortier wrote: > > On 8 Dec 2013, at 14:11, Anil Madhavapeddy wrote: >> >> I'm confused -- which PPA has opam.ocamlpro.com hardcoded in? They should all be on OPAM 1.1 now. > > hm. maybe it was only the old opam.1.0.0 ones. let me check again. it was. problem solved :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 20:34:12 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 20:34:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl3H-0007bC-6g; Sun, 08 Dec 2013 20:34:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl3F-0007b7-3r for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 20:34:05 +0000 Received: from [85.158.137.68:58709] by server-2.bemta-3.messagelabs.com id 5E/A4-17329-BB7D4A25; Sun, 08 Dec 2013 20:34:03 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-6.tower-31.messagelabs.com!1386534468!2541053!1 X-Originating-IP: [131.111.8.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5709 invoked from network); 8 Dec 2013 20:27:49 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Dec 2013 20:27:49 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-212-230.in-addr.btopenworld.com ([81.149.212.230]:12624 helo=[10.0.1.34]) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VpkxA-00006u-24 (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Sun, 08 Dec 2013 20:27:48 +0000 From: Amir Chaudhry Message-Id: <2C109F91-1F30-4DE8-8F63-0A4592647E13@cam.ac.uk> Date: Sun, 8 Dec 2013 20:27:48 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] New GitHub org: ocaml-attic X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, We have a new org on GitHub, ocaml-attic (https://github.com/ocaml-attic). There are some repos there already but if you know of others that should be moved please do migrate them. Thanks, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 20:34:12 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 20:34:12 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl3H-0007bC-6g; Sun, 08 Dec 2013 20:34:07 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl3F-0007b7-3r for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 20:34:05 +0000 Received: from [85.158.137.68:58709] by server-2.bemta-3.messagelabs.com id 5E/A4-17329-BB7D4A25; Sun, 08 Dec 2013 20:34:03 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-6.tower-31.messagelabs.com!1386534468!2541053!1 X-Originating-IP: [131.111.8.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 5709 invoked from network); 8 Dec 2013 20:27:49 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-6.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 8 Dec 2013 20:27:49 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-212-230.in-addr.btopenworld.com ([81.149.212.230]:12624 helo=[10.0.1.34]) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VpkxA-00006u-24 (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Sun, 08 Dec 2013 20:27:48 +0000 From: Amir Chaudhry Message-Id: <2C109F91-1F30-4DE8-8F63-0A4592647E13@cam.ac.uk> Date: Sun, 8 Dec 2013 20:27:48 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) Subject: [MirageOS-devel] New GitHub org: ocaml-attic X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, We have a new org on GitHub, ocaml-attic (https://github.com/ocaml-attic). There are some repos there already but if you know of others that should be moved please do migrate them. Thanks, Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 20:37:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 20:37:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl6T-0007cb-K5; Sun, 08 Dec 2013 20:37:25 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl6S-0007cW-Km for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 20:37:24 +0000 Received: from [193.109.254.147:51784] by server-14.bemta-14.messagelabs.com id 29/32-12628-388D4A25; Sun, 08 Dec 2013 20:37:23 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1386535043!3750564!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 923 invoked from network); 8 Dec 2013 20:37:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-27.messagelabs.com with SMTP; 8 Dec 2013 20:37:23 -0000 Received: (qmail 23263 invoked by uid 634); 8 Dec 2013 20:37:23 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-212-230.in-addr.btopenworld.com (HELO [10.0.1.33]) (81.149.212.230) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Dec 2013 20:37:21 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <2C109F91-1F30-4DE8-8F63-0A4592647E13@cam.ac.uk> Date: Sun, 8 Dec 2013 20:37:17 +0000 Message-Id: <4A217144-1DBF-406F-A60E-C8301F97DE55@recoil.org> References: <2C109F91-1F30-4DE8-8F63-0A4592647E13@cam.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] New GitHub org: ocaml-attic X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 20:27, Amir Chaudhry wrote: > Hi folks, > > We have a new org on GitHub, ocaml-attic (https://github.com/ocaml-attic). > There are some repos there already but if you know of others that should be moved please do migrate them. I've moved the following unused repos from github.com/mirage, so that the repo list on there reflects our forthcoming release and not a bunch of random other repositories: - homebrew-ocaml (now obsolete as we are upstream in Homebrew) - mirage-tutorial (very obsolete, was from CUFP 2011 tutorial, can be resurrected later) - opam-repo (used for original opam port, now all upstream) - ocaml-build-skeleton (incomplete) - cohttp-server (replaced by cohttp repo) - cohttp.old (err...not sure, but last updated 4 years ago). If anyone needed these for any reason, then give me a shout. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 08 20:37:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 08 Dec 2013 20:37:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl6T-0007cb-K5; Sun, 08 Dec 2013 20:37:25 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vpl6S-0007cW-Km for mirageos-devel@lists.xenproject.org; Sun, 08 Dec 2013 20:37:24 +0000 Received: from [193.109.254.147:51784] by server-14.bemta-14.messagelabs.com id 29/32-12628-388D4A25; Sun, 08 Dec 2013 20:37:23 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-27.messagelabs.com!1386535043!3750564!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.3 required=7.0 tests=MAILTO_TO_SPAM_ADDR X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 923 invoked from network); 8 Dec 2013 20:37:23 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-27.messagelabs.com with SMTP; 8 Dec 2013 20:37:23 -0000 Received: (qmail 23263 invoked by uid 634); 8 Dec 2013 20:37:23 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-212-230.in-addr.btopenworld.com (HELO [10.0.1.33]) (81.149.212.230) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 08 Dec 2013 20:37:21 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <2C109F91-1F30-4DE8-8F63-0A4592647E13@cam.ac.uk> Date: Sun, 8 Dec 2013 20:37:17 +0000 Message-Id: <4A217144-1DBF-406F-A60E-C8301F97DE55@recoil.org> References: <2C109F91-1F30-4DE8-8F63-0A4592647E13@cam.ac.uk> To: Amir M Chaudhry X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] New GitHub org: ocaml-attic X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 8 Dec 2013, at 20:27, Amir Chaudhry wrote: > Hi folks, > > We have a new org on GitHub, ocaml-attic (https://github.com/ocaml-attic). > There are some repos there already but if you know of others that should be moved please do migrate them. I've moved the following unused repos from github.com/mirage, so that the repo list on there reflects our forthcoming release and not a bunch of random other repositories: - homebrew-ocaml (now obsolete as we are upstream in Homebrew) - mirage-tutorial (very obsolete, was from CUFP 2011 tutorial, can be resurrected later) - opam-repo (used for original opam port, now all upstream) - ocaml-build-skeleton (incomplete) - cohttp-server (replaced by cohttp repo) - cohttp.old (err...not sure, but last updated 4 years ago). If anyone needed these for any reason, then give me a shout. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 09 17:31:59 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Dec 2013 17:31:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vq4gU-0000ll-RU; Mon, 09 Dec 2013 17:31:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vq4fi-0000lI-Vl for mirageos-devel@lists.xenproject.org; Mon, 09 Dec 2013 17:31:07 +0000 Received: from [85.158.139.211:60536] by server-4.bemta-5.messagelabs.com id E3/F3-26791-A5EF5A25; Mon, 09 Dec 2013 17:31:06 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1386610265!3267636!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9685 invoked from network); 9 Dec 2013 17:31:05 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Dec 2013 17:31:05 -0000 Received: by mail-wi0-f175.google.com with SMTP id hi5so4158551wib.2 for ; Mon, 09 Dec 2013 09:31:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=ept4j38ydEmwH6lrbcPk4bfct2CU9LobXK6bA2grB2s=; b=SRBOvICFGssznfAlTRdcoLius3LmWfhTLea3fE4NFSJnA4HFROkLoGx+etmvt8R5H2 m8tHsjeq6V83X8s/2telJ/SzuYnWMtoeBP2tPZqbULbNvA97OKd/JL9A3tsdTWy34Myo 2sWClaWQp8kZnHAgF/tdCoLkyoZ/7Xw0cz3dXJe0qJapIACV31cX254M3s/1nmENdUv7 MIHxIP6c6LazJfnb0GjXKPqcKmtbmnd9QRmlLcPB0qBR8SmZFoIHeQEi8vxyLPX4mVyx OqvJjGfQeMnBakXpVIspwO9HnR1O8o+oI7urj6gt1590p1GkRt3IncR1L2tTHHwOzdss yXQQ== X-Received: by 10.180.10.138 with SMTP id i10mr15364860wib.44.1386610264870; Mon, 09 Dec 2013 09:31:04 -0800 (PST) Received: from dhcp-172-17-154-231.eduroam.lapwing.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id uc18sm26662266wib.11.2013.12.09.09.31.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 09:31:04 -0800 (PST) From: Amir Chaudhry Message-Id: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Mon, 9 Dec 2013 17:31:07 +0000 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-Mailman-Approved-At: Mon, 09 Dec 2013 17:31:53 +0000 Subject: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, Great work today! Now that Mirage 1.0 is out, we need to put together a bunch of posts to describe the system and help people (and each-other) get to grips with it. This will effectively form some of the documentation so it's more than just blog posts and wiki pages -- getting this content in written form is important and we can come back to each one to properly cross-reference. :) I've made a new issue on the mirage repo [1] with some ideas for posts Anil/Dave think are needed and also some people who could write them. If you're ok with the list please say so on the issue's comments. The idea is that once we've agreed on *what* posts we need, we'll create a *separate* issue for each post, where we can discuss what the contents need to include. I'd also like us to agree on a schedule of posts so that this doesn't slip and we can (1) keep the cadence up while (2) spreading the work. [1] https://github.com/mirage/mirage/issues/128 Thoughts? Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 09 17:31:59 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 09 Dec 2013 17:31:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vq4gU-0000ll-RU; Mon, 09 Dec 2013 17:31:54 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vq4fi-0000lI-Vl for mirageos-devel@lists.xenproject.org; Mon, 09 Dec 2013 17:31:07 +0000 Received: from [85.158.139.211:60536] by server-4.bemta-5.messagelabs.com id E3/F3-26791-A5EF5A25; Mon, 09 Dec 2013 17:31:06 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-11.tower-206.messagelabs.com!1386610265!3267636!1 X-Originating-IP: [209.85.212.175] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9685 invoked from network); 9 Dec 2013 17:31:05 -0000 Received: from mail-wi0-f175.google.com (HELO mail-wi0-f175.google.com) (209.85.212.175) by server-11.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 9 Dec 2013 17:31:05 -0000 Received: by mail-wi0-f175.google.com with SMTP id hi5so4158551wib.2 for ; Mon, 09 Dec 2013 09:31:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:content-transfer-encoding:subject:message-id:date :to:mime-version; bh=ept4j38ydEmwH6lrbcPk4bfct2CU9LobXK6bA2grB2s=; b=SRBOvICFGssznfAlTRdcoLius3LmWfhTLea3fE4NFSJnA4HFROkLoGx+etmvt8R5H2 m8tHsjeq6V83X8s/2telJ/SzuYnWMtoeBP2tPZqbULbNvA97OKd/JL9A3tsdTWy34Myo 2sWClaWQp8kZnHAgF/tdCoLkyoZ/7Xw0cz3dXJe0qJapIACV31cX254M3s/1nmENdUv7 MIHxIP6c6LazJfnb0GjXKPqcKmtbmnd9QRmlLcPB0qBR8SmZFoIHeQEi8vxyLPX4mVyx OqvJjGfQeMnBakXpVIspwO9HnR1O8o+oI7urj6gt1590p1GkRt3IncR1L2tTHHwOzdss yXQQ== X-Received: by 10.180.10.138 with SMTP id i10mr15364860wib.44.1386610264870; Mon, 09 Dec 2013 09:31:04 -0800 (PST) Received: from dhcp-172-17-154-231.eduroam.lapwing.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id uc18sm26662266wib.11.2013.12.09.09.31.04 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 09 Dec 2013 09:31:04 -0800 (PST) From: Amir Chaudhry Message-Id: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Mon, 9 Dec 2013 17:31:07 +0000 To: "mirageos-devel@lists.xenproject.org" Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) X-Mailer: Apple Mail (2.1510) X-Mailman-Approved-At: Mon, 09 Dec 2013 17:31:53 +0000 Subject: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi folks, Great work today! Now that Mirage 1.0 is out, we need to put together a bunch of posts to describe the system and help people (and each-other) get to grips with it. This will effectively form some of the documentation so it's more than just blog posts and wiki pages -- getting this content in written form is important and we can come back to each one to properly cross-reference. :) I've made a new issue on the mirage repo [1] with some ideas for posts Anil/Dave think are needed and also some people who could write them. If you're ok with the list please say so on the issue's comments. The idea is that once we've agreed on *what* posts we need, we'll create a *separate* issue for each post, where we can discuss what the contents need to include. I'd also like us to agree on a schedule of posts so that this doesn't slip and we can (1) keep the cadence up while (2) spreading the work. [1] https://github.com/mirage/mirage/issues/128 Thoughts? Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 00:46:17 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 00:46:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqBSn-0003QW-Hy; Tue, 10 Dec 2013 00:46:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqBSl-0003QR-Cw for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 00:46:11 +0000 Received: from [85.158.139.211:57490] by server-3.bemta-5.messagelabs.com id 45/EF-05884-25466A25; Tue, 10 Dec 2013 00:46:10 +0000 X-Env-Sender: jdy22@cam.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1386636368!3361630!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31238 invoked from network); 10 Dec 2013 00:46:08 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Dec 2013 00:46:08 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-wi0-f178.google.com ([209.85.212.178]:34358) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:jdy22) (TLSv1:RC4-SHA:128) id 1VqBSi-00021w-ES (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 10 Dec 2013 00:46:08 +0000 Received: by mail-wi0-f178.google.com with SMTP id bz8so4504645wib.5 for ; Mon, 09 Dec 2013 16:46:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=peTbMiDgBDt5yqThmWE1XCmeS+MqeZATHLaixAmNNso=; b=YiatwarUdloI8GjgGiI3tqfGbSa0BD4+hlStVvtvOgYbCwgsFx4XoLLvFoDaXPZBXy SgP+zcjlsYS5jCaXXP4NkySQm5EXbkL36hlVoLA98SzKGAAOIr05KP2J9RvkPOD1Vrg/ NtCCk5d7Odu0vizhuR1XwKwMofgRSYFINkUs3lzPfG9SpFPlQ6Mt6UQzQPLTj2pktLbV r509M5taHt3XUcOJOsB/9cdEycFrpEH26OshwAfPoZp5iTi+Fs5Na8IgPgqxN43wtqOu PcwQzJ6tzFqFJeoxGXnGDbsnUJd7VgbGnH/8NkXPYkmK3ledJh5SFo8ngjTfJTHMWmDe Niew== MIME-Version: 1.0 X-Received: by 10.180.20.15 with SMTP id j15mr16890360wie.4.1386636368230; Mon, 09 Dec 2013 16:46:08 -0800 (PST) Received: by 10.216.33.4 with HTTP; Mon, 9 Dec 2013 16:46:08 -0800 (PST) Date: Tue, 10 Dec 2013 00:46:08 +0000 Message-ID: From: Jeremy Yallop To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Where's the best place to report issues with the openmirage site? The atom feed isn't quite working for me: the title URLs become broken links in my aggregator, perhaps because they're relative rather than absolute. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 00:46:17 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 00:46:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqBSn-0003QW-Hy; Tue, 10 Dec 2013 00:46:13 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqBSl-0003QR-Cw for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 00:46:11 +0000 Received: from [85.158.139.211:57490] by server-3.bemta-5.messagelabs.com id 45/EF-05884-25466A25; Tue, 10 Dec 2013 00:46:10 +0000 X-Env-Sender: jdy22@cam.ac.uk X-Msg-Ref: server-15.tower-206.messagelabs.com!1386636368!3361630!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31238 invoked from network); 10 Dec 2013 00:46:08 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Dec 2013 00:46:08 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from mail-wi0-f178.google.com ([209.85.212.178]:34358) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:jdy22) (TLSv1:RC4-SHA:128) id 1VqBSi-00021w-ES (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Tue, 10 Dec 2013 00:46:08 +0000 Received: by mail-wi0-f178.google.com with SMTP id bz8so4504645wib.5 for ; Mon, 09 Dec 2013 16:46:08 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:date:message-id:subject:from:to:content-type; bh=peTbMiDgBDt5yqThmWE1XCmeS+MqeZATHLaixAmNNso=; b=YiatwarUdloI8GjgGiI3tqfGbSa0BD4+hlStVvtvOgYbCwgsFx4XoLLvFoDaXPZBXy SgP+zcjlsYS5jCaXXP4NkySQm5EXbkL36hlVoLA98SzKGAAOIr05KP2J9RvkPOD1Vrg/ NtCCk5d7Odu0vizhuR1XwKwMofgRSYFINkUs3lzPfG9SpFPlQ6Mt6UQzQPLTj2pktLbV r509M5taHt3XUcOJOsB/9cdEycFrpEH26OshwAfPoZp5iTi+Fs5Na8IgPgqxN43wtqOu PcwQzJ6tzFqFJeoxGXnGDbsnUJd7VgbGnH/8NkXPYkmK3ledJh5SFo8ngjTfJTHMWmDe Niew== MIME-Version: 1.0 X-Received: by 10.180.20.15 with SMTP id j15mr16890360wie.4.1386636368230; Mon, 09 Dec 2013 16:46:08 -0800 (PST) Received: by 10.216.33.4 with HTTP; Mon, 9 Dec 2013 16:46:08 -0800 (PST) Date: Tue, 10 Dec 2013 00:46:08 +0000 Message-ID: From: Jeremy Yallop To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Where's the best place to report issues with the openmirage site? The atom feed isn't quite working for me: the title URLs become broken links in my aggregator, perhaps because they're relative rather than absolute. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 09:42:30 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 09:42:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqJpi-000141-I2; Tue, 10 Dec 2013 09:42:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqJph-00013u-9o for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 09:42:25 +0000 Received: from [85.158.139.211:49027] by server-9.bemta-5.messagelabs.com id A8/5E-15098-002E6A25; Tue, 10 Dec 2013 09:42:24 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1386668543!2215328!1 X-Originating-IP: [195.62.217.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2384 invoked from network); 10 Dec 2013 09:42:23 -0000 Received: from engine04-20433-4.icritical.com (HELO engine04-20433-4.icritical.com) (195.62.217.152) by server-16.tower-206.messagelabs.com with SMTP; 10 Dec 2013 09:42:23 -0000 Received: (qmail 20319 invoked from network); 10 Dec 2013 09:42:21 -0000 Received: from localhost (127.0.0.1) by engine04-20433-4.icritical.com with SMTP; 10 Dec 2013 09:42:21 -0000 Received: from engine04-20433-4.icritical.com ([127.0.0.1]) by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20168-05 for ; Tue, 10 Dec 2013 09:42:20 +0000 (GMT) Received: (qmail 19749 invoked by uid 599); 10 Dec 2013 09:41:52 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 10 Dec 2013 09:41:52 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VqJmv-0007Nc-AZ for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 09:39:33 +0000 From: Richard Mortier To: Jeremy Yallop Date: Tue, 10 Dec 2013 09:39:32 +0000 Thread-Topic: [MirageOS-devel] openmirage.org issue tracker? Thread-Index: Ac71i7sTLPVl+8BiQCGDaesVFe9ZYw== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 00:46, Jeremy Yallop wrote: > Where's the best place to report issues with the openmirage site? for specific website content related bugs like this, probably filing an issue against github.com/mirage/mirage-www is the best thing to do; more generally i think we're intending that issues are best filed against github.com/mirage/mirage so they can be triaged to the correct repository/ies. but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) > The atom feed isn't quite working for me: the title URLs become broken > links in my aggregator, perhaps because they're relative rather than > absolute. yup, that's certainly a brokenness. hopefully reasonably soon the website is going to get a thorough overhaul to use cowabloga, zurb foundation, etc. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 09:42:30 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 09:42:30 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqJpi-000141-I2; Tue, 10 Dec 2013 09:42:26 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqJph-00013u-9o for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 09:42:25 +0000 Received: from [85.158.139.211:49027] by server-9.bemta-5.messagelabs.com id A8/5E-15098-002E6A25; Tue, 10 Dec 2013 09:42:24 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-16.tower-206.messagelabs.com!1386668543!2215328!1 X-Originating-IP: [195.62.217.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTIgPT4gMTY3OTY=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2384 invoked from network); 10 Dec 2013 09:42:23 -0000 Received: from engine04-20433-4.icritical.com (HELO engine04-20433-4.icritical.com) (195.62.217.152) by server-16.tower-206.messagelabs.com with SMTP; 10 Dec 2013 09:42:23 -0000 Received: (qmail 20319 invoked from network); 10 Dec 2013 09:42:21 -0000 Received: from localhost (127.0.0.1) by engine04-20433-4.icritical.com with SMTP; 10 Dec 2013 09:42:21 -0000 Received: from engine04-20433-4.icritical.com ([127.0.0.1]) by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 20168-05 for ; Tue, 10 Dec 2013 09:42:20 +0000 (GMT) Received: (qmail 19749 invoked by uid 599); 10 Dec 2013 09:41:52 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 10 Dec 2013 09:41:52 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VqJmv-0007Nc-AZ for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 09:39:33 +0000 From: Richard Mortier To: Jeremy Yallop Date: Tue, 10 Dec 2013 09:39:32 +0000 Thread-Topic: [MirageOS-devel] openmirage.org issue tracker? Thread-Index: Ac71i7sTLPVl+8BiQCGDaesVFe9ZYw== Message-ID: References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 00:46, Jeremy Yallop wrote: > Where's the best place to report issues with the openmirage site? for specific website content related bugs like this, probably filing an issue against github.com/mirage/mirage-www is the best thing to do; more generally i think we're intending that issues are best filed against github.com/mirage/mirage so they can be triaged to the correct repository/ies. but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) > The atom feed isn't quite working for me: the title URLs become broken > links in my aggregator, perhaps because they're relative rather than > absolute. yup, that's certainly a brokenness. hopefully reasonably soon the website is going to get a thorough overhaul to use cowabloga, zurb foundation, etc. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 10:48:21 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 10:48:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqKrR-0006FX-Uu; Tue, 10 Dec 2013 10:48:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqKrQ-0006FK-F5 for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 10:48:16 +0000 Received: from [85.158.137.68:62503] by server-1.bemta-3.messagelabs.com id 16/E2-29598-F61F6A25; Tue, 10 Dec 2013 10:48:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1386672494!2926986!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28702 invoked from network); 10 Dec 2013 10:48:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 10 Dec 2013 10:48:14 -0000 Received: (qmail 32221 invoked by uid 634); 10 Dec 2013 10:48:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO flick.home) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 10 Dec 2013 10:48:13 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 10 Dec 2013 10:48:12 +0000 Message-Id: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 09:39, Richard Mortier wrote: > > On 10 Dec 2013, at 00:46, Jeremy Yallop wrote: > >> Where's the best place to report issues with the openmirage site? > > for specific website content related bugs like this, probably filing an issue against github.com/mirage/mirage-www is the best thing to do; more generally i think we're intending that issues are best filed against github.com/mirage/mirage so they can be triaged to the correct repository/ies. > > but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) Good timing for this question -- I've been looking at how other projects do this, and there's a real mix of approaches. My inclination is to focus all the issues in mirage/mirage, and use the label/milestone system to prioritise issues. This works well for libraries that are clearly 'mirage', but less so for ones like cohttp that are used in a number of different contexts. A simple rule might be to activate issues for those more general libraries, and point people in the README for dependent libraries to mirage/mirage. For mirage/mirage-www, you'll need to delete your fork Mort, since the mirage/mirage-www repo is pointing in the wrong direction. > >> The atom feed isn't quite working for me: the title URLs become broken >> links in my aggregator, perhaps because they're relative rather than >> absolute. > > yup, that's certainly a brokenness. hopefully reasonably soon the website is going to get a thorough overhaul to use cowabloga, zurb foundation, etc. And to the actual issue, this is indeed a bug but easy to fix. I can fix the immediate problem today in my next run through it just as soon as I refresh the production toolchain to 1.0. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 10:48:21 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 10:48:21 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqKrR-0006FX-Uu; Tue, 10 Dec 2013 10:48:17 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqKrQ-0006FK-F5 for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 10:48:16 +0000 Received: from [85.158.137.68:62503] by server-1.bemta-3.messagelabs.com id 16/E2-29598-F61F6A25; Tue, 10 Dec 2013 10:48:15 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-31.messagelabs.com!1386672494!2926986!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28702 invoked from network); 10 Dec 2013 10:48:14 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-31.messagelabs.com with SMTP; 10 Dec 2013 10:48:14 -0000 Received: (qmail 32221 invoked by uid 634); 10 Dec 2013 10:48:14 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from host81-149-102-120.in-addr.btopenworld.com (HELO flick.home) (81.149.102.120) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 10 Dec 2013 10:48:13 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Tue, 10 Dec 2013 10:48:12 +0000 Message-Id: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> References: To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 09:39, Richard Mortier wrote: > > On 10 Dec 2013, at 00:46, Jeremy Yallop wrote: > >> Where's the best place to report issues with the openmirage site? > > for specific website content related bugs like this, probably filing an issue against github.com/mirage/mirage-www is the best thing to do; more generally i think we're intending that issues are best filed against github.com/mirage/mirage so they can be triaged to the correct repository/ies. > > but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) Good timing for this question -- I've been looking at how other projects do this, and there's a real mix of approaches. My inclination is to focus all the issues in mirage/mirage, and use the label/milestone system to prioritise issues. This works well for libraries that are clearly 'mirage', but less so for ones like cohttp that are used in a number of different contexts. A simple rule might be to activate issues for those more general libraries, and point people in the README for dependent libraries to mirage/mirage. For mirage/mirage-www, you'll need to delete your fork Mort, since the mirage/mirage-www repo is pointing in the wrong direction. > >> The atom feed isn't quite working for me: the title URLs become broken >> links in my aggregator, perhaps because they're relative rather than >> absolute. > > yup, that's certainly a brokenness. hopefully reasonably soon the website is going to get a thorough overhaul to use cowabloga, zurb foundation, etc. And to the actual issue, this is indeed a bug but easy to fix. I can fix the immediate problem today in my next run through it just as soon as I refresh the production toolchain to 1.0. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 11:34:22 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 11:34:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLa1-0001Uh-Et; Tue, 10 Dec 2013 11:34:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLZz-0001UZ-TW for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 11:34:20 +0000 Received: from [85.158.137.68:19693] by server-11.bemta-3.messagelabs.com id 16/27-19379-B3CF6A25; Tue, 10 Dec 2013 11:34:19 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-31.messagelabs.com!1386675258!1780161!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25755 invoked from network); 10 Dec 2013 11:34:18 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-9.tower-31.messagelabs.com with SMTP; 10 Dec 2013 11:34:18 -0000 Received: (qmail 19163 invoked from network); 10 Dec 2013 11:34:11 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 10 Dec 2013 11:34:11 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 19060-02 for ; Tue, 10 Dec 2013 11:34:11 +0000 (GMT) Received: (qmail 16021 invoked by uid 599); 10 Dec 2013 11:26:35 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 10 Dec 2013 11:26:35 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VqLRe-0002pN-FP; Tue, 10 Dec 2013 11:25:42 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Tue, 10 Dec 2013 11:25:41 +0000 Thread-Topic: [MirageOS-devel] openmirage.org issue tracker? Thread-Index: Ac71mo8QO8mlDIaMT9+aveaz+gNCLw== Message-ID: <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> References: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> In-Reply-To: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote: > On 10 Dec 2013, at 09:39, Richard Mortier wrote: > >> but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) > > Good timing for this question -- I've been looking at how other projects do this, and there's a real mix of approaches. My inclination is to focus all the issues in mirage/mirage, and use the label/milestone system to prioritise issues. > > This works well for libraries that are clearly 'mirage', but less so for ones like cohttp that are used in a number of different contexts. issue referencing will make that ok won't it? (or are there limits to how references can work?) > A simple rule might be to activate issues for those more general libraries, and point people in the README for dependent libraries to mirage/mirage. sure. > For mirage/mirage-www, you'll need to delete your fork Mort, since the mirage/mirage-www repo is pointing in the wrong direction. ack; done. though i note that mirage/mirage-www now believes itself to have been forked from balrajsingh/mirage-www so not sure it's helped much... -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 11:34:22 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 11:34:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLa1-0001Uh-Et; Tue, 10 Dec 2013 11:34:21 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLZz-0001UZ-TW for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 11:34:20 +0000 Received: from [85.158.137.68:19693] by server-11.bemta-3.messagelabs.com id 16/27-19379-B3CF6A25; Tue, 10 Dec 2013 11:34:19 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-31.messagelabs.com!1386675258!1780161!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25755 invoked from network); 10 Dec 2013 11:34:18 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-9.tower-31.messagelabs.com with SMTP; 10 Dec 2013 11:34:18 -0000 Received: (qmail 19163 invoked from network); 10 Dec 2013 11:34:11 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 10 Dec 2013 11:34:11 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 19060-02 for ; Tue, 10 Dec 2013 11:34:11 +0000 (GMT) Received: (qmail 16021 invoked by uid 599); 10 Dec 2013 11:26:35 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 10 Dec 2013 11:26:35 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VqLRe-0002pN-FP; Tue, 10 Dec 2013 11:25:42 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Tue, 10 Dec 2013 11:25:41 +0000 Thread-Topic: [MirageOS-devel] openmirage.org issue tracker? Thread-Index: Ac71mo8QO8mlDIaMT9+aveaz+gNCLw== Message-ID: <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> References: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> In-Reply-To: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote: > On 10 Dec 2013, at 09:39, Richard Mortier wrote: > >> but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) > > Good timing for this question -- I've been looking at how other projects do this, and there's a real mix of approaches. My inclination is to focus all the issues in mirage/mirage, and use the label/milestone system to prioritise issues. > > This works well for libraries that are clearly 'mirage', but less so for ones like cohttp that are used in a number of different contexts. issue referencing will make that ok won't it? (or are there limits to how references can work?) > A simple rule might be to activate issues for those more general libraries, and point people in the README for dependent libraries to mirage/mirage. sure. > For mirage/mirage-www, you'll need to delete your fork Mort, since the mirage/mirage-www repo is pointing in the wrong direction. ack; done. though i note that mirage/mirage-www now believes itself to have been forked from balrajsingh/mirage-www so not sure it's helped much... -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 11:52:54 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 11:52:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLrx-0002dU-Co; Tue, 10 Dec 2013 11:52:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLrw-0002dP-5d for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 11:52:52 +0000 Received: from [85.158.137.68:48850] by server-1.bemta-3.messagelabs.com id FB/9F-29598-39007A25; Tue, 10 Dec 2013 11:52:51 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-2.tower-31.messagelabs.com!1386676370!2935959!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16996 invoked from network); 10 Dec 2013 11:52:50 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Dec 2013 11:52:50 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net ([86.6.155.105]:56770 helo=[192.168.0.3]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VqLrs-0008LN-Fv (Exim 4.82_3-c0e5623) (return-path ); Tue, 10 Dec 2013 11:52:49 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> Date: Tue, 10 Dec 2013 11:52:47 +0000 Message-Id: <0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk> References: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 11:25, Richard Mortier wrote: > > On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote: > >> On 10 Dec 2013, at 09:39, Richard Mortier wrote: >> >>> but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) >> >> Good timing for this question -- I've been looking at how other projects do this, and there's a real mix of approaches. My inclination is to focus all the issues in mirage/mirage, and use the label/milestone system to prioritise issues. >> >> This works well for libraries that are clearly 'mirage', but less so for ones like cohttp that are used in a number of different contexts. > > issue referencing will make that ok won't it? (or are there limits to how references can work?) Also worth remembering that GitHub has a useful overview page for organisations so you can see all issues across all repos. Annoyingly, it only shows you the overview for the subset of repos you have push/pull access to -- so it's more useful for admins (also it took me 20mins to find that damn page). https://github.com/organizations/mirage/dashboard/issues Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 10 11:52:54 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 10 Dec 2013 11:52:54 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLrx-0002dU-Co; Tue, 10 Dec 2013 11:52:53 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqLrw-0002dP-5d for mirageos-devel@lists.xenproject.org; Tue, 10 Dec 2013 11:52:52 +0000 Received: from [85.158.137.68:48850] by server-1.bemta-3.messagelabs.com id FB/9F-29598-39007A25; Tue, 10 Dec 2013 11:52:51 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-2.tower-31.messagelabs.com!1386676370!2935959!1 X-Originating-IP: [131.111.8.152] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTMxLjExMS44LjE1MiA9PiA4MDU1Mw==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 16996 invoked from network); 10 Dec 2013 11:52:50 -0000 Received: from ppsw-52.csi.cam.ac.uk (HELO ppsw-52.csi.cam.ac.uk) (131.111.8.152) by server-2.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 10 Dec 2013 11:52:50 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from cpc17-cmbg14-2-0-cust360.5-4.cable.virginm.net ([86.6.155.105]:56770 helo=[192.168.0.3]) by ppsw-52.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.158]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VqLrs-0008LN-Fv (Exim 4.82_3-c0e5623) (return-path ); Tue, 10 Dec 2013 11:52:49 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> Date: Tue, 10 Dec 2013 11:52:47 +0000 Message-Id: <0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk> References: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 10 Dec 2013, at 11:25, Richard Mortier wrote: > > On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote: > >> On 10 Dec 2013, at 09:39, Richard Mortier wrote: >> >>> but that was only the latest discussion on the matter that i remember -- anil, any further thoughts on that? :) >> >> Good timing for this question -- I've been looking at how other projects do this, and there's a real mix of approaches. My inclination is to focus all the issues in mirage/mirage, and use the label/milestone system to prioritise issues. >> >> This works well for libraries that are clearly 'mirage', but less so for ones like cohttp that are used in a number of different contexts. > > issue referencing will make that ok won't it? (or are there limits to how references can work?) Also worth remembering that GitHub has a useful overview page for organisations so you can see all issues across all repos. Annoyingly, it only shows you the overview for the subset of repos you have push/pull access to -- so it's more useful for admins (also it took me 20mins to find that damn page). https://github.com/organizations/mirage/dashboard/issues Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 01:35:03 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 01:35:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqYhX-0007S0-4D; Wed, 11 Dec 2013 01:34:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqYhV-0007Rv-FT for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 01:34:57 +0000 Received: from [193.109.254.147:4952] by server-16.bemta-14.messagelabs.com id 1E/77-20600-041C7A25; Wed, 11 Dec 2013 01:34:56 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1386725695!2079711!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3009 invoked from network); 11 Dec 2013 01:34:55 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-27.messagelabs.com with SMTP; 11 Dec 2013 01:34:55 -0000 Received: (qmail 30050 invoked by uid 634); 11 Dec 2013 01:34:54 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 01:34:52 +0000 From: Anil Madhavapeddy Message-Id: <2991A30A-E216-4A9B-B220-CE3D59CE6FA3@recoil.org> Date: Wed, 11 Dec 2013 01:34:50 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] mirage 1.0.2 released X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org A flurry of activity today to fill in the libraries on the Xen side, to follow the Unix libraries from the Monday 1.0 release. A summary of what's been uploaded to OPAM today. - mirage 1.0.2 released, with support for HTTP and various bugfixes. - mirage-net-xen : new package that implements Xen Netfront, and works with the Mirage lib_test/netif case. - mirage-tcpip-unix + - mirage-tcpip-xen : This is the old mirage-net stack with the socket backend removed, the build structure simplified, and compiled against the relevant backend. - cohttp 0.9.13, with support for the Mirage 1.0 interfaces. If you opam update to these, then HTTP traffic is served just fine from a Xen kernel too! Mirage-www should be straightforward to swap out tomorrow, and we're back to feature parity for Xen/Unix! -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 01:35:03 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 01:35:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqYhX-0007S0-4D; Wed, 11 Dec 2013 01:34:59 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqYhV-0007Rv-FT for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 01:34:57 +0000 Received: from [193.109.254.147:4952] by server-16.bemta-14.messagelabs.com id 1E/77-20600-041C7A25; Wed, 11 Dec 2013 01:34:56 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-27.messagelabs.com!1386725695!2079711!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3009 invoked from network); 11 Dec 2013 01:34:55 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-27.messagelabs.com with SMTP; 11 Dec 2013 01:34:55 -0000 Received: (qmail 30050 invoked by uid 634); 11 Dec 2013 01:34:54 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 01:34:52 +0000 From: Anil Madhavapeddy Message-Id: <2991A30A-E216-4A9B-B220-CE3D59CE6FA3@recoil.org> Date: Wed, 11 Dec 2013 01:34:50 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] mirage 1.0.2 released X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org A flurry of activity today to fill in the libraries on the Xen side, to follow the Unix libraries from the Monday 1.0 release. A summary of what's been uploaded to OPAM today. - mirage 1.0.2 released, with support for HTTP and various bugfixes. - mirage-net-xen : new package that implements Xen Netfront, and works with the Mirage lib_test/netif case. - mirage-tcpip-unix + - mirage-tcpip-xen : This is the old mirage-net stack with the socket backend removed, the build structure simplified, and compiled against the relevant backend. - cohttp 0.9.13, with support for the Mirage 1.0 interfaces. If you opam update to these, then HTTP traffic is served just fine from a Xen kernel too! Mirage-www should be straightforward to swap out tomorrow, and we're back to feature parity for Xen/Unix! -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 10:54:26 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 10:54:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhQj-0002ev-P0; Wed, 11 Dec 2013 10:54:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhQi-0002cX-7N for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 10:54:12 +0000 Received: from [193.109.254.147:12352] by server-1.bemta-14.messagelabs.com id D6/6D-15600-35448A25; Wed, 11 Dec 2013 10:54:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1386759250!4430751!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11004 invoked from network); 11 Dec 2013 10:54:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-27.messagelabs.com with SMTP; 11 Dec 2013 10:54:10 -0000 Received: (qmail 16471 invoked by uid 634); 11 Dec 2013 10:54:10 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 10:54:06 +0000 From: Anil Madhavapeddy Message-Id: <52464421-CD5D-4EF4-A24B-345D593E31E0@recoil.org> Date: Wed, 11 Dec 2013 10:54:04 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] -2 days to Mirage 1.0! Weekly call today, 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org We're fast approaching...no, wait, we've released! Now that Mirage 1.0 is out, we're going to use the weekly call to plan the round of tutorial blog posts, and moving our homepages to the brave new world. Please join me on the Mirage call at 4pm GMT today (wednesday), there'll be lots of exciting bugs to talk about. 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Meeting ID: 591-890-401 -- Anil Madhavapeddy _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 10:54:26 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 10:54:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhQj-0002ev-P0; Wed, 11 Dec 2013 10:54:13 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhQi-0002cX-7N for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 10:54:12 +0000 Received: from [193.109.254.147:12352] by server-1.bemta-14.messagelabs.com id D6/6D-15600-35448A25; Wed, 11 Dec 2013 10:54:11 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-27.messagelabs.com!1386759250!4430751!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11004 invoked from network); 11 Dec 2013 10:54:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-27.messagelabs.com with SMTP; 11 Dec 2013 10:54:10 -0000 Received: (qmail 16471 invoked by uid 634); 11 Dec 2013 10:54:10 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 10:54:06 +0000 From: Anil Madhavapeddy Message-Id: <52464421-CD5D-4EF4-A24B-345D593E31E0@recoil.org> Date: Wed, 11 Dec 2013 10:54:04 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] -2 days to Mirage 1.0! Weekly call today, 4pm GMT X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org We're fast approaching...no, wait, we've released! Now that Mirage 1.0 is out, we're going to use the weekly call to plan the round of tutorial blog posts, and moving our homepages to the brave new world. Please join me on the Mirage call at 4pm GMT today (wednesday), there'll be lots of exciting bugs to talk about. 1. Please join my meeting. https://www1.gotomeeting.com/join/591890401 2. Use your microphone and speakers (VoIP) - a headset is recommended. Or, call in using your telephone. United Kingdom (toll-free): 0 808 168 0209 United Kingdom: +44 (0) 207 151 1817 United States (toll-free): 1 877 309 2070 United States: +1 (626) 521-0017 Access Code: 591-890-401 Audio PIN: Shown after joining the meeting Meeting ID: 591-890-401 -- Anil Madhavapeddy _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:08:19 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:08:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqheG-0003rz-PU; Wed, 11 Dec 2013 11:08:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqheF-0003rm-3l; Wed, 11 Dec 2013 11:08:11 +0000 Received: from [85.158.137.68:11393] by server-5.bemta-3.messagelabs.com id 1C/89-25188-99748A25; Wed, 11 Dec 2013 11:08:09 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1386760088!3188808!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3649 invoked from network); 11 Dec 2013 11:08:08 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 11:08:08 -0000 Received: by mail-wg0-f41.google.com with SMTP id y10so5815889wgg.4 for ; Wed, 11 Dec 2013 03:08:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3Uh3v5rmpRGKCJ2HYIcd2EgLTtGSw27DzXB63CKox0w=; b=cv+tGLf9uTfm86yFeEgJuJn2s6g/GgCFdUDhDoOQGwjFm4SKJxCPp21662w7mTIKv4 AEY8coIjBPRhxSHXymKUikaIbROjNhxYxJnzDk8RkKmmoY0N6qc35bJRmZX22znll3Ow 5Nf0L/Pyamn6flLuCvDU66DbX1QWXacsnHT20VNlM5k8KEPjUopXlfpbcjWBifysx3kq 6+Q3obXjJCxdhFWvpnbhp3eLFzW3XCa6H1+ritoldIwLkHWRTooNd4ENN/X1qXvZoYii z4fahmSyXL7da9zmgVNxMBnZZxfgQRXaBIyQCzEdAW7J9bvI50o0yVrJZQhF4luGJ4jO LWhQ== X-Received: by 10.194.75.165 with SMTP id d5mr922455wjw.18.1386760088355; Wed, 11 Dec 2013 03:08:08 -0800 (PST) Received: from dhcp-172-17-153-196.eduroam.lapwing.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id q19sm13832705wiw.4.2013.12.11.03.08.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Dec 2013 03:08:07 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 11 Dec 2013 11:08:07 +0000 Message-Id: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> To: Lars Kurth X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Great! I'm looking forward to the report. I have a Google Alert set up but that's going to be delayed by indexing (and is a little crude). I can tell you that we had nice write ups in Dutch and Catalan :) Amir On 11 Dec 2013, at 10:21, Lars Kurth wrote: > Adding publicity > > > On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth wrote: > Amir, > > seems we got quite good coverage indeed. I will send the media report to the list (and to the Advisory Board). > > You and others may want to sign up to publicity@lists.xenproject.org via http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use this to coordinate blog posts, articles on Linux.com, LWN.net, ... , other PR, etc. > > It is also entirely acceptable to re-post the same content in several places. Typically what you do is to change the title slightly for SEO reasons. For example we frequently post some content on the xen blog first and then copy to the wiki, or publish something on Linux.com and then repost on the blog. > > Regards > Lars > > > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a bunch of posts to describe the system and help people (and each-other) get to grips with it. > > This will effectively form some of the documentation so it's more than just blog posts and wiki pages -- getting this content in written form is important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts Anil/Dave think are needed and also some people who could write them. If you're ok with the list please say so on the issue's comments. The idea is that once we've agreed on *what* posts we need, we'll create a *separate* issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:08:19 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:08:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqheG-0003rz-PU; Wed, 11 Dec 2013 11:08:12 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqheF-0003rm-3l; Wed, 11 Dec 2013 11:08:11 +0000 Received: from [85.158.137.68:11393] by server-5.bemta-3.messagelabs.com id 1C/89-25188-99748A25; Wed, 11 Dec 2013 11:08:09 +0000 X-Env-Sender: amirmc@gmail.com X-Msg-Ref: server-2.tower-31.messagelabs.com!1386760088!3188808!1 X-Originating-IP: [74.125.82.41] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 3649 invoked from network); 11 Dec 2013 11:08:08 -0000 Received: from mail-wg0-f41.google.com (HELO mail-wg0-f41.google.com) (74.125.82.41) by server-2.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 11:08:08 -0000 Received: by mail-wg0-f41.google.com with SMTP id y10so5815889wgg.4 for ; Wed, 11 Dec 2013 03:08:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=3Uh3v5rmpRGKCJ2HYIcd2EgLTtGSw27DzXB63CKox0w=; b=cv+tGLf9uTfm86yFeEgJuJn2s6g/GgCFdUDhDoOQGwjFm4SKJxCPp21662w7mTIKv4 AEY8coIjBPRhxSHXymKUikaIbROjNhxYxJnzDk8RkKmmoY0N6qc35bJRmZX22znll3Ow 5Nf0L/Pyamn6flLuCvDU66DbX1QWXacsnHT20VNlM5k8KEPjUopXlfpbcjWBifysx3kq 6+Q3obXjJCxdhFWvpnbhp3eLFzW3XCa6H1+ritoldIwLkHWRTooNd4ENN/X1qXvZoYii z4fahmSyXL7da9zmgVNxMBnZZxfgQRXaBIyQCzEdAW7J9bvI50o0yVrJZQhF4luGJ4jO LWhQ== X-Received: by 10.194.75.165 with SMTP id d5mr922455wjw.18.1386760088355; Wed, 11 Dec 2013 03:08:08 -0800 (PST) Received: from dhcp-172-17-153-196.eduroam.lapwing.private.cam.ac.uk (global-1-26.nat.csx.cam.ac.uk. [131.111.184.26]) by mx.google.com with ESMTPSA id q19sm13832705wiw.4.2013.12.11.03.08.07 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 11 Dec 2013 03:08:07 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: Date: Wed, 11 Dec 2013 11:08:07 +0000 Message-Id: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> To: Lars Kurth X-Mailer: Apple Mail (2.1510) Cc: "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Great! I'm looking forward to the report. I have a Google Alert set up but that's going to be delayed by indexing (and is a little crude). I can tell you that we had nice write ups in Dutch and Catalan :) Amir On 11 Dec 2013, at 10:21, Lars Kurth wrote: > Adding publicity > > > On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth wrote: > Amir, > > seems we got quite good coverage indeed. I will send the media report to the list (and to the Advisory Board). > > You and others may want to sign up to publicity@lists.xenproject.org via http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use this to coordinate blog posts, articles on Linux.com, LWN.net, ... , other PR, etc. > > It is also entirely acceptable to re-post the same content in several places. Typically what you do is to change the title slightly for SEO reasons. For example we frequently post some content on the xen blog first and then copy to the wiki, or publish something on Linux.com and then repost on the blog. > > Regards > Lars > > > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a bunch of posts to describe the system and help people (and each-other) get to grips with it. > > This will effectively form some of the documentation so it's more than just blog posts and wiki pages -- getting this content in written form is important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts Anil/Dave think are needed and also some people who could write them. If you're ok with the list please say so on the issue's comments. The idea is that once we've agreed on *what* posts we need, we'll create a *separate* issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > > > _______________________________________________ > Publicity mailing list > Publicity@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:12:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:12:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhiO-0004XR-CY; Wed, 11 Dec 2013 11:12:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqgtN-0008FB-Vz for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 10:19:46 +0000 Received: from [193.109.254.147:8570] by server-1.bemta-14.messagelabs.com id A9/D6-15600-14C38A25; Wed, 11 Dec 2013 10:19:45 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1386757182!4425417!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6736 invoked from network); 11 Dec 2013 10:19:43 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 10:19:43 -0000 Received: by mail-ob0-f169.google.com with SMTP id wm4so6713468obc.14 for ; Wed, 11 Dec 2013 02:19:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kr76NQ8xugvTCbwD/2+LJudE84Hn7wtZ10w5/7Enu0c=; b=ea8ES8DkgX3xb9LATmVFX0w5hQe6SjekcQli3MzCcaNzoXHShHyxyhVhOU24myFVB6 ioIc2OW/mbf/PKrkyY4kCB7CfItAV6VSibJRUxWnk0RoqRoCijg9MTTiSTz78k0NDvI8 6Kc+ETtTW9pQ6i+zqlUe4D51opJCKnmEO3rjAnu1TXXv1M1TMG0qYV+6F7qiaDT4cmk+ mUI57IriKebHuETzCXyfhn4vjblwyJPJPZh0MGuaarmSlh1g8WcFbjo8D1xGcTFwm/4Z yV+s7XObPPaG+lS1mWThY09Jr8ACZ78dqYFZzs6e0/JkKFr4VQoFQYHEEdl5TsPwyYGA 79PA== MIME-Version: 1.0 X-Received: by 10.182.220.225 with SMTP id pz1mr416884obc.51.1386757182177; Wed, 11 Dec 2013 02:19:42 -0800 (PST) Received: by 10.60.29.39 with HTTP; Wed, 11 Dec 2013 02:19:42 -0800 (PST) In-Reply-To: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Wed, 11 Dec 2013 10:19:42 +0000 Message-ID: From: Lars Kurth To: Amir Chaudhry X-Mailman-Approved-At: Wed, 11 Dec 2013 11:12:27 +0000 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6533364421204439659==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6533364421204439659== Content-Type: multipart/alternative; boundary=001a11c30fac3bc82e04ed3f91b3 --001a11c30fac3bc82e04ed3f91b3 Content-Type: text/plain; charset=ISO-8859-1 Amir, seems we got quite good coverage indeed. I will send the media report to the list (and to the Advisory Board). You and others may want to sign up to publicity@lists.xenproject.org via http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use this to coordinate blog posts, articles on Linux.com, LWN.net, ... , other PR, etc. It is also entirely acceptable to re-post the same content in several places. Typically what you do is to change the title slightly for SEO reasons. For example we frequently post some content on the xen blog first and then copy to the wiki, or publish something on Linux.com and then repost on the blog. Regards Lars On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a > bunch of posts to describe the system and help people (and each-other) get > to grips with it. > > This will effectively form some of the documentation so it's more than > just blog posts and wiki pages -- getting this content in written form is > important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts > Anil/Dave think are needed and also some people who could write them. If > you're ok with the list please say so on the issue's comments. The idea is > that once we've agreed on *what* posts we need, we'll create a *separate* > issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip > and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11c30fac3bc82e04ed3f91b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Mon, Dec 9, 2013 at 5:31 PM, Am= ir Chaudhry <amirmc@gmail.com> wrote:
Hi folks,

Great work today! =A0Now that Mirage 1.0 is out, we need to put together a = bunch of posts to describe the system and help people (and each-other) get = to grips with it.

This will effectively form some of the documentation so it's more than = just blog posts and wiki pages -- getting this content in written form is i= mportant and we can come back to each one to properly cross-reference. :)
I've made a new issue on the mirage repo [1] with some ideas for posts = Anil/Dave think are needed and also some people who could write them. =A0If= you're ok with the list please say so on the issue's comments. =A0= The idea is that once we've agreed on *what* posts we need, we'll c= reate a *separate* issue for each post, where we can discuss what the conte= nts need to include.

I'd also like us to agree on a schedule of posts so that this doesn'= ;t slip and we can (1) keep the cadence up while (2) spreading the work.
[1] https://github.com/mirage/mirage/issues/128

Thoughts?

Amir
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--001a11c30fac3bc82e04ed3f91b3-- --===============6533364421204439659== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6533364421204439659==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:12:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:12:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhiO-0004XM-Ac; Wed, 11 Dec 2013 11:12:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqgkt-00072H-8x for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 10:10:59 +0000 Received: from [85.158.139.211:42773] by server-15.bemta-5.messagelabs.com id 4F/93-08490-23A38A25; Wed, 11 Dec 2013 10:10:58 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1386756655!2518557!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21519 invoked from network); 11 Dec 2013 10:10:57 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 10:10:57 -0000 Received: by mail-ob0-f169.google.com with SMTP id wm4so6704208obc.14 for ; Wed, 11 Dec 2013 02:10:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=syRq4IDUq6m39S+VHs+64Etc2qOroO37CVnVFxeyGw8=; b=seHMnFVEKK2mYfIxs8zmrV4m2Q7AFk+STFgeUCDUWynRQfwpUIFqID3sb9xu9VhK8S YbbDIYFqwKZeGB3elnbSeghqiS2Zxmc6yp+k+VAdzHgbhyHqWDfjnsyYpGyoQQuZ9ICm Q07JZBuRr4WLb+o1QIIABstrQ9E1gW4OqdslwvkGrL1u5pokVuxlVqjEqI/7bIWM6Ksj M0eRkJbp5ay7PtBDpz+JXlSzD8RFTfy1FVQ3BvAxe+TlXhGftkvdtO4ZglLcp5WrpOSD gxauwm7SzNF5N6GizhBwX6xkcwG79baH3sKhfu8LUoxPGGFzdZVjOLOib2gCVkrPsolz vxSg== MIME-Version: 1.0 X-Received: by 10.60.144.228 with SMTP id sp4mr405242oeb.29.1386756652797; Wed, 11 Dec 2013 02:10:52 -0800 (PST) Received: by 10.60.29.39 with HTTP; Wed, 11 Dec 2013 02:10:52 -0800 (PST) In-Reply-To: <0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk> References: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> <0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk> Date: Wed, 11 Dec 2013 10:10:52 +0000 Message-ID: From: Lars Kurth To: Amir Chaudhry X-Mailman-Approved-At: Wed, 11 Dec 2013 11:12:27 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6205642328570618946==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6205642328570618946== Content-Type: multipart/alternative; boundary=047d7b41ccbcae16f004ed3f71ce --047d7b41ccbcae16f004ed3f71ce Content-Type: text/plain; charset=ISO-8859-1 Hi all, once you decided how to do this, could you create a page on the xen project or your own wiki? I can then link to it from the relevant places. Regards Lars On Tue, Dec 10, 2013 at 11:52 AM, Amir Chaudhry wrote: > > On 10 Dec 2013, at 11:25, Richard Mortier < > Richard.Mortier@nottingham.ac.uk> wrote: > > > > > On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote: > > > >> On 10 Dec 2013, at 09:39, Richard Mortier < > Richard.Mortier@nottingham.ac.uk> wrote: > >> > >>> but that was only the latest discussion on the matter that i remember > -- anil, any further thoughts on that? :) > >> > >> Good timing for this question -- I've been looking at how other > projects do this, and there's a real mix of approaches. My inclination is > to focus all the issues in mirage/mirage, and use the label/milestone > system to prioritise issues. > >> > >> This works well for libraries that are clearly 'mirage', but less so > for ones like cohttp that are used in a number of different contexts. > > > > issue referencing will make that ok won't it? (or are there limits to > how references can work?) > > Also worth remembering that GitHub has a useful overview page for > organisations so you can see all issues across all repos. Annoyingly, it > only shows you the overview for the subset of repos you have push/pull > access to -- so it's more useful for admins (also it took me 20mins to find > that damn page). > > https://github.com/organizations/mirage/dashboard/issues > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --047d7b41ccbcae16f004ed3f71ce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
once you decided how to do this, could you cre= ate a page on the xen project or your own wiki? I can then link to it from = the relevant places.
Regards
Lars


On Tue, Dec 10, 2013 at 11:52 AM, Amir C= haudhry <amc79@cam.ac.uk> wrote:

On 10 Dec 2013, at 11:25, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

>
> On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote:
>
>> On 10 Dec 2013, at 09:39, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wr= ote:
>>
>>> but that was only the latest discussion on the matter that i r= emember -- anil, any further thoughts on that? :)
>>
>> Good timing for this question -- I've been looking at how othe= r projects do this, and there's a real mix of approaches. =A0My inclina= tion is to focus all the issues in mirage/mirage, and use the label/milesto= ne system to prioritise issues.
>>
>> This works well for libraries that are clearly 'mirage', b= ut less so for ones like cohttp that are used in a number of different cont= exts.
>
> issue referencing will make that ok won't it? =A0(or are there lim= its to how references can work?)

Also worth remembering that GitHub has a useful overview page for org= anisations so you can see all issues across all repos. =A0Annoyingly, it on= ly shows you the overview for the subset of repos you have push/pull access= to -- so it's more useful for admins (also it took me 20mins to find t= hat damn page).

https://github.com/organizations/mirage/dashboard/issues
Amir
_____________________= __________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--047d7b41ccbcae16f004ed3f71ce-- --===============6205642328570618946== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6205642328570618946==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:12:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:12:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhiO-0004XM-Ac; Wed, 11 Dec 2013 11:12:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqgkt-00072H-8x for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 10:10:59 +0000 Received: from [85.158.139.211:42773] by server-15.bemta-5.messagelabs.com id 4F/93-08490-23A38A25; Wed, 11 Dec 2013 10:10:58 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-206.messagelabs.com!1386756655!2518557!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.7 required=7.0 tests=HTML_30_40,HTML_MESSAGE, MAILTO_TO_SPAM_ADDR,ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21519 invoked from network); 11 Dec 2013 10:10:57 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-16.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 10:10:57 -0000 Received: by mail-ob0-f169.google.com with SMTP id wm4so6704208obc.14 for ; Wed, 11 Dec 2013 02:10:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=syRq4IDUq6m39S+VHs+64Etc2qOroO37CVnVFxeyGw8=; b=seHMnFVEKK2mYfIxs8zmrV4m2Q7AFk+STFgeUCDUWynRQfwpUIFqID3sb9xu9VhK8S YbbDIYFqwKZeGB3elnbSeghqiS2Zxmc6yp+k+VAdzHgbhyHqWDfjnsyYpGyoQQuZ9ICm Q07JZBuRr4WLb+o1QIIABstrQ9E1gW4OqdslwvkGrL1u5pokVuxlVqjEqI/7bIWM6Ksj M0eRkJbp5ay7PtBDpz+JXlSzD8RFTfy1FVQ3BvAxe+TlXhGftkvdtO4ZglLcp5WrpOSD gxauwm7SzNF5N6GizhBwX6xkcwG79baH3sKhfu8LUoxPGGFzdZVjOLOib2gCVkrPsolz vxSg== MIME-Version: 1.0 X-Received: by 10.60.144.228 with SMTP id sp4mr405242oeb.29.1386756652797; Wed, 11 Dec 2013 02:10:52 -0800 (PST) Received: by 10.60.29.39 with HTTP; Wed, 11 Dec 2013 02:10:52 -0800 (PST) In-Reply-To: <0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk> References: <092BF08C-57A9-49EF-93AD-129DC133A231@recoil.org> <1E61DF74-231A-4BDA-BF8D-CD317E923FDF@nottingham.ac.uk> <0B0524FA-4837-4A59-91C7-CA1C279DCCCD@cam.ac.uk> Date: Wed, 11 Dec 2013 10:10:52 +0000 Message-ID: From: Lars Kurth To: Amir Chaudhry X-Mailman-Approved-At: Wed, 11 Dec 2013 11:12:27 +0000 Cc: "mirageos-devel@lists.xenproject.org" , Anil Madhavapeddy Subject: Re: [MirageOS-devel] openmirage.org issue tracker? X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6205642328570618946==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6205642328570618946== Content-Type: multipart/alternative; boundary=047d7b41ccbcae16f004ed3f71ce --047d7b41ccbcae16f004ed3f71ce Content-Type: text/plain; charset=ISO-8859-1 Hi all, once you decided how to do this, could you create a page on the xen project or your own wiki? I can then link to it from the relevant places. Regards Lars On Tue, Dec 10, 2013 at 11:52 AM, Amir Chaudhry wrote: > > On 10 Dec 2013, at 11:25, Richard Mortier < > Richard.Mortier@nottingham.ac.uk> wrote: > > > > > On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote: > > > >> On 10 Dec 2013, at 09:39, Richard Mortier < > Richard.Mortier@nottingham.ac.uk> wrote: > >> > >>> but that was only the latest discussion on the matter that i remember > -- anil, any further thoughts on that? :) > >> > >> Good timing for this question -- I've been looking at how other > projects do this, and there's a real mix of approaches. My inclination is > to focus all the issues in mirage/mirage, and use the label/milestone > system to prioritise issues. > >> > >> This works well for libraries that are clearly 'mirage', but less so > for ones like cohttp that are used in a number of different contexts. > > > > issue referencing will make that ok won't it? (or are there limits to > how references can work?) > > Also worth remembering that GitHub has a useful overview page for > organisations so you can see all issues across all repos. Annoyingly, it > only shows you the overview for the subset of repos you have push/pull > access to -- so it's more useful for admins (also it took me 20mins to find > that damn page). > > https://github.com/organizations/mirage/dashboard/issues > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --047d7b41ccbcae16f004ed3f71ce Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi all,
once you decided how to do this, could you cre= ate a page on the xen project or your own wiki? I can then link to it from = the relevant places.
Regards
Lars


On Tue, Dec 10, 2013 at 11:52 AM, Amir C= haudhry <amc79@cam.ac.uk> wrote:

On 10 Dec 2013, at 11:25, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wrote:

>
> On 10 Dec 2013, at 10:48, Anil Madhavapeddy wrote:
>
>> On 10 Dec 2013, at 09:39, Richard Mortier <Richard.Mortier@nottingham.ac.uk> wr= ote:
>>
>>> but that was only the latest discussion on the matter that i r= emember -- anil, any further thoughts on that? :)
>>
>> Good timing for this question -- I've been looking at how othe= r projects do this, and there's a real mix of approaches. =A0My inclina= tion is to focus all the issues in mirage/mirage, and use the label/milesto= ne system to prioritise issues.
>>
>> This works well for libraries that are clearly 'mirage', b= ut less so for ones like cohttp that are used in a number of different cont= exts.
>
> issue referencing will make that ok won't it? =A0(or are there lim= its to how references can work?)

Also worth remembering that GitHub has a useful overview page for org= anisations so you can see all issues across all repos. =A0Annoyingly, it on= ly shows you the overview for the subset of repos you have push/pull access= to -- so it's more useful for admins (also it took me 20mins to find t= hat damn page).

https://github.com/organizations/mirage/dashboard/issues
Amir
_____________________= __________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--047d7b41ccbcae16f004ed3f71ce-- --===============6205642328570618946== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6205642328570618946==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:12:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:12:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhiO-0004XY-EY; Wed, 11 Dec 2013 11:12:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqgva-0008Mz-Cy; Wed, 11 Dec 2013 10:22:02 +0000 Received: from [85.158.137.68:31699] by server-8.bemta-3.messagelabs.com id C6/05-31081-9CC38A25; Wed, 11 Dec 2013 10:22:01 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1386757318!3184280!1 X-Originating-IP: [209.85.214.172] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23652 invoked from network); 11 Dec 2013 10:21:59 -0000 Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 10:21:59 -0000 Received: by mail-ob0-f172.google.com with SMTP id gq1so6780964obb.31 for ; Wed, 11 Dec 2013 02:21:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=k15At8OQ1IkzMR9L/N5WbkU7Gi17YHZIGvSS0J2SMuk=; b=aia+gSX6VLwcyj2hJfAhtrrtYfYARXOHPYLS8ay2zQFTkafqf0EM4ej2VK1f7qC18O qSPNX4AiHK7AwscLk3Akj7jV7Tmd3sZlEyI056EoDprVLKLkHQ++W6g84YU40ftLhd44 O2PI3N+VJxFY+M1L+mKWJH3Lr/y216sAWXuV4afxjnZHEq3ila7K2tJxIrEfDoiFYNYE k2+rcl5xSYu+ysiGlG/hc3VG4R2zSbC/WfeX8cidIfglBiyDg73hSIjnxWy0Guik3930 evNIUvxLZ3ffwLOTmo1poF+ksxZqeJoMhtOumyy4Qr3IXLk/78Q0XXoYJQAwFn/dfhZz GiYg== MIME-Version: 1.0 X-Received: by 10.182.144.136 with SMTP id sm8mr423364obb.63.1386757318206; Wed, 11 Dec 2013 02:21:58 -0800 (PST) Received: by 10.60.29.39 with HTTP; Wed, 11 Dec 2013 02:21:58 -0800 (PST) In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Wed, 11 Dec 2013 10:21:58 +0000 Message-ID: From: Lars Kurth To: Amir Chaudhry X-Mailman-Approved-At: Wed, 11 Dec 2013 11:12:27 +0000 Cc: Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1300052241233744082==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1300052241233744082== Content-Type: multipart/alternative; boundary=089e0149cd5e576b9104ed3f99d4 --089e0149cd5e576b9104ed3f99d4 Content-Type: text/plain; charset=ISO-8859-1 Adding publicity On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth wrote: > Amir, > > seems we got quite good coverage indeed. I will send the media report to > the list (and to the Advisory Board). > > You and others may want to sign up to publicity@lists.xenproject.org via > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use > this to coordinate blog posts, articles on Linux.com, LWN.net, ... , other > PR, etc. > > It is also entirely acceptable to re-post the same content in several > places. Typically what you do is to change the title slightly for SEO > reasons. For example we frequently post some content on the xen blog first > and then copy to the wiki, or publish something on Linux.com and then > repost on the blog. > > Regards > Lars > > > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry wrote: > >> Hi folks, >> >> Great work today! Now that Mirage 1.0 is out, we need to put together a >> bunch of posts to describe the system and help people (and each-other) get >> to grips with it. >> >> This will effectively form some of the documentation so it's more than >> just blog posts and wiki pages -- getting this content in written form is >> important and we can come back to each one to properly cross-reference. :) >> >> I've made a new issue on the mirage repo [1] with some ideas for posts >> Anil/Dave think are needed and also some people who could write them. If >> you're ok with the list please say so on the issue's comments. The idea is >> that once we've agreed on *what* posts we need, we'll create a *separate* >> issue for each post, where we can discuss what the contents need to include. >> >> I'd also like us to agree on a schedule of posts so that this doesn't >> slip and we can (1) keep the cadence up while (2) spreading the work. >> >> [1] https://github.com/mirage/mirage/issues/128 >> >> Thoughts? >> >> Amir >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > --089e0149cd5e576b9104ed3f99d4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Adding publicity


<= div class=3D"gmail_quote">On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth <lars.kurth.xen@gmail.com> wrote:
Amir,

se= ems we got quite good coverage indeed. I will send the media report to the = list (and to the Advisory Board).

You and others may want to sign up to publicity@lists.xenproje= ct.org via=A0http://lists.xenproject.org/cgi-bin/mai= lman/listinfo/publicity... we use this to coordinate blog posts, articl= es on Linux.com, LWN.net, ... , other PR, etc.

It is also entirely acceptable to re-post the same cont= ent in several places. Typically what you do is to change the title slightl= y for SEO reasons. For example we frequently post some content on the xen b= log first and then copy to the wiki, or publish something on Linux.com and = then repost on the blog.=A0

Regards
Lars


On Mon, = Dec 9, 2013 at 5:31 PM, Amir Chaudhry <amirmc@gmail.com> wrot= e:
Hi folks,

Great work today! =A0Now that Mirage 1.0 is out, we need to put together a = bunch of posts to describe the system and help people (and each-other) get = to grips with it.

This will effectively form some of the documentation so it's more than = just blog posts and wiki pages -- getting this content in written form is i= mportant and we can come back to each one to properly cross-reference. :)
I've made a new issue on the mirage repo [1] with some ideas for posts = Anil/Dave think are needed and also some people who could write them. =A0If= you're ok with the list please say so on the issue's comments. =A0= The idea is that once we've agreed on *what* posts we need, we'll c= reate a *separate* issue for each post, where we can discuss what the conte= nts need to include.

I'd also like us to agree on a schedule of posts so that this doesn'= ;t slip and we can (1) keep the cadence up while (2) spreading the work.
[1] https://github.com/mirage/mirage/issues/128

Thoughts?

Amir
_______________________________________________
MirageOS-devel mailing list
Mi= rageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel


--089e0149cd5e576b9104ed3f99d4-- --===============1300052241233744082== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1300052241233744082==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:12:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:12:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhiO-0004XR-CY; Wed, 11 Dec 2013 11:12:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqgtN-0008FB-Vz for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 10:19:46 +0000 Received: from [193.109.254.147:8570] by server-1.bemta-14.messagelabs.com id A9/D6-15600-14C38A25; Wed, 11 Dec 2013 10:19:45 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-7.tower-27.messagelabs.com!1386757182!4425417!1 X-Originating-IP: [209.85.214.169] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6736 invoked from network); 11 Dec 2013 10:19:43 -0000 Received: from mail-ob0-f169.google.com (HELO mail-ob0-f169.google.com) (209.85.214.169) by server-7.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 10:19:43 -0000 Received: by mail-ob0-f169.google.com with SMTP id wm4so6713468obc.14 for ; Wed, 11 Dec 2013 02:19:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=Kr76NQ8xugvTCbwD/2+LJudE84Hn7wtZ10w5/7Enu0c=; b=ea8ES8DkgX3xb9LATmVFX0w5hQe6SjekcQli3MzCcaNzoXHShHyxyhVhOU24myFVB6 ioIc2OW/mbf/PKrkyY4kCB7CfItAV6VSibJRUxWnk0RoqRoCijg9MTTiSTz78k0NDvI8 6Kc+ETtTW9pQ6i+zqlUe4D51opJCKnmEO3rjAnu1TXXv1M1TMG0qYV+6F7qiaDT4cmk+ mUI57IriKebHuETzCXyfhn4vjblwyJPJPZh0MGuaarmSlh1g8WcFbjo8D1xGcTFwm/4Z yV+s7XObPPaG+lS1mWThY09Jr8ACZ78dqYFZzs6e0/JkKFr4VQoFQYHEEdl5TsPwyYGA 79PA== MIME-Version: 1.0 X-Received: by 10.182.220.225 with SMTP id pz1mr416884obc.51.1386757182177; Wed, 11 Dec 2013 02:19:42 -0800 (PST) Received: by 10.60.29.39 with HTTP; Wed, 11 Dec 2013 02:19:42 -0800 (PST) In-Reply-To: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Wed, 11 Dec 2013 10:19:42 +0000 Message-ID: From: Lars Kurth To: Amir Chaudhry X-Mailman-Approved-At: Wed, 11 Dec 2013 11:12:27 +0000 Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6533364421204439659==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6533364421204439659== Content-Type: multipart/alternative; boundary=001a11c30fac3bc82e04ed3f91b3 --001a11c30fac3bc82e04ed3f91b3 Content-Type: text/plain; charset=ISO-8859-1 Amir, seems we got quite good coverage indeed. I will send the media report to the list (and to the Advisory Board). You and others may want to sign up to publicity@lists.xenproject.org via http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use this to coordinate blog posts, articles on Linux.com, LWN.net, ... , other PR, etc. It is also entirely acceptable to re-post the same content in several places. Typically what you do is to change the title slightly for SEO reasons. For example we frequently post some content on the xen blog first and then copy to the wiki, or publish something on Linux.com and then repost on the blog. Regards Lars On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a > bunch of posts to describe the system and help people (and each-other) get > to grips with it. > > This will effectively form some of the documentation so it's more than > just blog posts and wiki pages -- getting this content in written form is > important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts > Anil/Dave think are needed and also some people who could write them. If > you're ok with the list please say so on the issue's comments. The idea is > that once we've agreed on *what* posts we need, we'll create a *separate* > issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip > and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? > > Amir > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > --001a11c30fac3bc82e04ed3f91b3 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On Mon, Dec 9, 2013 at 5:31 PM, Am= ir Chaudhry <amirmc@gmail.com> wrote:
Hi folks,

Great work today! =A0Now that Mirage 1.0 is out, we need to put together a = bunch of posts to describe the system and help people (and each-other) get = to grips with it.

This will effectively form some of the documentation so it's more than = just blog posts and wiki pages -- getting this content in written form is i= mportant and we can come back to each one to properly cross-reference. :)
I've made a new issue on the mirage repo [1] with some ideas for posts = Anil/Dave think are needed and also some people who could write them. =A0If= you're ok with the list please say so on the issue's comments. =A0= The idea is that once we've agreed on *what* posts we need, we'll c= reate a *separate* issue for each post, where we can discuss what the conte= nts need to include.

I'd also like us to agree on a schedule of posts so that this doesn'= ;t slip and we can (1) keep the cadence up while (2) spreading the work.
[1] https://github.com/mirage/mirage/issues/128

Thoughts?

Amir
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel

--001a11c30fac3bc82e04ed3f91b3-- --===============6533364421204439659== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6533364421204439659==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:12:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:12:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqhiO-0004XY-EY; Wed, 11 Dec 2013 11:12:28 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqgva-0008Mz-Cy; Wed, 11 Dec 2013 10:22:02 +0000 Received: from [85.158.137.68:31699] by server-8.bemta-3.messagelabs.com id C6/05-31081-9CC38A25; Wed, 11 Dec 2013 10:22:01 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-6.tower-31.messagelabs.com!1386757318!3184280!1 X-Originating-IP: [209.85.214.172] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23652 invoked from network); 11 Dec 2013 10:21:59 -0000 Received: from mail-ob0-f172.google.com (HELO mail-ob0-f172.google.com) (209.85.214.172) by server-6.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 11 Dec 2013 10:21:59 -0000 Received: by mail-ob0-f172.google.com with SMTP id gq1so6780964obb.31 for ; Wed, 11 Dec 2013 02:21:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=k15At8OQ1IkzMR9L/N5WbkU7Gi17YHZIGvSS0J2SMuk=; b=aia+gSX6VLwcyj2hJfAhtrrtYfYARXOHPYLS8ay2zQFTkafqf0EM4ej2VK1f7qC18O qSPNX4AiHK7AwscLk3Akj7jV7Tmd3sZlEyI056EoDprVLKLkHQ++W6g84YU40ftLhd44 O2PI3N+VJxFY+M1L+mKWJH3Lr/y216sAWXuV4afxjnZHEq3ila7K2tJxIrEfDoiFYNYE k2+rcl5xSYu+ysiGlG/hc3VG4R2zSbC/WfeX8cidIfglBiyDg73hSIjnxWy0Guik3930 evNIUvxLZ3ffwLOTmo1poF+ksxZqeJoMhtOumyy4Qr3IXLk/78Q0XXoYJQAwFn/dfhZz GiYg== MIME-Version: 1.0 X-Received: by 10.182.144.136 with SMTP id sm8mr423364obb.63.1386757318206; Wed, 11 Dec 2013 02:21:58 -0800 (PST) Received: by 10.60.29.39 with HTTP; Wed, 11 Dec 2013 02:21:58 -0800 (PST) In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Wed, 11 Dec 2013 10:21:58 +0000 Message-ID: From: Lars Kurth To: Amir Chaudhry X-Mailman-Approved-At: Wed, 11 Dec 2013 11:12:27 +0000 Cc: Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1300052241233744082==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============1300052241233744082== Content-Type: multipart/alternative; boundary=089e0149cd5e576b9104ed3f99d4 --089e0149cd5e576b9104ed3f99d4 Content-Type: text/plain; charset=ISO-8859-1 Adding publicity On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth wrote: > Amir, > > seems we got quite good coverage indeed. I will send the media report to > the list (and to the Advisory Board). > > You and others may want to sign up to publicity@lists.xenproject.org via > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity... we use > this to coordinate blog posts, articles on Linux.com, LWN.net, ... , other > PR, etc. > > It is also entirely acceptable to re-post the same content in several > places. Typically what you do is to change the title slightly for SEO > reasons. For example we frequently post some content on the xen blog first > and then copy to the wiki, or publish something on Linux.com and then > repost on the blog. > > Regards > Lars > > > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry wrote: > >> Hi folks, >> >> Great work today! Now that Mirage 1.0 is out, we need to put together a >> bunch of posts to describe the system and help people (and each-other) get >> to grips with it. >> >> This will effectively form some of the documentation so it's more than >> just blog posts and wiki pages -- getting this content in written form is >> important and we can come back to each one to properly cross-reference. :) >> >> I've made a new issue on the mirage repo [1] with some ideas for posts >> Anil/Dave think are needed and also some people who could write them. If >> you're ok with the list please say so on the issue's comments. The idea is >> that once we've agreed on *what* posts we need, we'll create a *separate* >> issue for each post, where we can discuss what the contents need to include. >> >> I'd also like us to agree on a schedule of posts so that this doesn't >> slip and we can (1) keep the cadence up while (2) spreading the work. >> >> [1] https://github.com/mirage/mirage/issues/128 >> >> Thoughts? >> >> Amir >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >> > > --089e0149cd5e576b9104ed3f99d4 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Adding publicity


<= div class=3D"gmail_quote">On Wed, Dec 11, 2013 at 10:19 AM, Lars Kurth <lars.kurth.xen@gmail.com> wrote:
Amir,

se= ems we got quite good coverage indeed. I will send the media report to the = list (and to the Advisory Board).

You and others may want to sign up to publicity@lists.xenproje= ct.org via=A0http://lists.xenproject.org/cgi-bin/mai= lman/listinfo/publicity... we use this to coordinate blog posts, articl= es on Linux.com, LWN.net, ... , other PR, etc.

It is also entirely acceptable to re-post the same cont= ent in several places. Typically what you do is to change the title slightl= y for SEO reasons. For example we frequently post some content on the xen b= log first and then copy to the wiki, or publish something on Linux.com and = then repost on the blog.=A0

Regards
Lars


On Mon, = Dec 9, 2013 at 5:31 PM, Amir Chaudhry <amirmc@gmail.com> wrot= e:
Hi folks,

Great work today! =A0Now that Mirage 1.0 is out, we need to put together a = bunch of posts to describe the system and help people (and each-other) get = to grips with it.

This will effectively form some of the documentation so it's more than = just blog posts and wiki pages -- getting this content in written form is i= mportant and we can come back to each one to properly cross-reference. :)
I've made a new issue on the mirage repo [1] with some ideas for posts = Anil/Dave think are needed and also some people who could write them. =A0If= you're ok with the list please say so on the issue's comments. =A0= The idea is that once we've agreed on *what* posts we need, we'll c= reate a *separate* issue for each post, where we can discuss what the conte= nts need to include.

I'd also like us to agree on a schedule of posts so that this doesn'= ;t slip and we can (1) keep the cadence up while (2) spreading the work.
[1] https://github.com/mirage/mirage/issues/128

Thoughts?

Amir
_______________________________________________
MirageOS-devel mailing list
Mi= rageOS-devel@lists.xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel


--089e0149cd5e576b9104ed3f99d4-- --===============1300052241233744082== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1300052241233744082==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:14:15 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:14:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqhk1-0004dx-67; Wed, 11 Dec 2013 11:14:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqhjz-0004dX-18 for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 11:14:07 +0000 Received: from [85.158.143.35:10213] by server-3.bemta-4.messagelabs.com id 9E/55-32360-EF848A25; Wed, 11 Dec 2013 11:14:06 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-21.messagelabs.com!1386760445!4870653!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10117 invoked from network); 11 Dec 2013 11:14:05 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-21.messagelabs.com with SMTP; 11 Dec 2013 11:14:05 -0000 Received: (qmail 17144 invoked by uid 634); 11 Dec 2013 11:14:05 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 11:14:04 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Wed, 11 Dec 2013 11:14:02 +0000 Message-Id: <875189C7-412D-432D-8341-2ADD3EB12E40@recoil.org> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> To: Amir Chaudhry X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: publicity@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Dec 2013, at 17:31, Amir Chaudhry wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a bunch of posts to describe the system and help people (and each-other) get to grips with it. > > This will effectively form some of the documentation so it's more than just blog posts and wiki pages -- getting this content in written form is important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts Anil/Dave think are needed and also some people who could write them. If you're ok with the list please say so on the issue's comments. The idea is that once we've agreed on *what* posts we need, we'll create a *separate* issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? I've edited the issue to reflect a better ordering -- most of the requests coming in have been for the high-level explanation of the toolchain and how to run a homepage on it, so let's focus on those first and go back and fill in the blanks with the other posts later. I also started working on a simple new backend/frontend driver to deliver entropy more reliably to the guest, in the form of Randomfront/Randomback. Nothing like this exists at the moment, as far as I can tell, and it's an obvious prerequisite for any bindings we want to do. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 11:14:15 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 11:14:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqhk1-0004dx-67; Wed, 11 Dec 2013 11:14:09 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vqhjz-0004dX-18 for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 11:14:07 +0000 Received: from [85.158.143.35:10213] by server-3.bemta-4.messagelabs.com id 9E/55-32360-EF848A25; Wed, 11 Dec 2013 11:14:06 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-21.messagelabs.com!1386760445!4870653!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10117 invoked from network); 11 Dec 2013 11:14:05 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-21.messagelabs.com with SMTP; 11 Dec 2013 11:14:05 -0000 Received: (qmail 17144 invoked by uid 634); 11 Dec 2013 11:14:05 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 11:14:04 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Date: Wed, 11 Dec 2013 11:14:02 +0000 Message-Id: <875189C7-412D-432D-8341-2ADD3EB12E40@recoil.org> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> To: Amir Chaudhry X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: publicity@lists.xenproject.org, "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 9 Dec 2013, at 17:31, Amir Chaudhry wrote: > Hi folks, > > Great work today! Now that Mirage 1.0 is out, we need to put together a bunch of posts to describe the system and help people (and each-other) get to grips with it. > > This will effectively form some of the documentation so it's more than just blog posts and wiki pages -- getting this content in written form is important and we can come back to each one to properly cross-reference. :) > > I've made a new issue on the mirage repo [1] with some ideas for posts Anil/Dave think are needed and also some people who could write them. If you're ok with the list please say so on the issue's comments. The idea is that once we've agreed on *what* posts we need, we'll create a *separate* issue for each post, where we can discuss what the contents need to include. > > I'd also like us to agree on a schedule of posts so that this doesn't slip and we can (1) keep the cadence up while (2) spreading the work. > > [1] https://github.com/mirage/mirage/issues/128 > > Thoughts? I've edited the issue to reflect a better ordering -- most of the requests coming in have been for the high-level explanation of the toolchain and how to run a homepage on it, so let's focus on those first and go back and fill in the blanks with the other posts later. I also started working on a simple new backend/frontend driver to deliver entropy more reliably to the guest, in the form of Randomfront/Randomback. Nothing like this exists at the moment, as far as I can tell, and it's an obvious prerequisite for any bindings we want to do. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 15:12:53 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 15:12:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqlSy-0005Cb-1U; Wed, 11 Dec 2013 15:12:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqlSx-0005CW-Bw for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 15:12:47 +0000 Received: from [193.109.254.147:47314] by server-13.bemta-14.messagelabs.com id 3D/CA-19374-EE088A25; Wed, 11 Dec 2013 15:12:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1386774755!4480719!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTI2MTAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27665 invoked from network); 11 Dec 2013 15:12:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-27.messagelabs.com with SMTP; 11 Dec 2013 15:12:35 -0000 Received: (qmail 29716 invoked by uid 634); 11 Dec 2013 15:12:35 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 15:12:34 +0000 From: Anil Madhavapeddy Date: Wed, 11 Dec 2013 15:12:32 +0000 References: <52A87FB7.8010807@frisch.fr> To: mirageos-devel@lists.xenproject.org Message-Id: <87C6D331-8537-4A96-A271-2CC77717698E@recoil.org> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Fwd: [Caml-list] Dead code detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a really interesting new feature in the next OCaml. We should be able to use it to do comprehensive dead code elimination on both Unix and Xen Mirage binaries on native code (since we don't need dynamic linking). This, in combination with the new module aliases feature, should shrink binary sizes considerably. -anil Begin forwarded message: > From: Alain Frisch > Subject: Re: [Caml-list] Dead code detection > Date: 11 December 2013 15:07:35 GMT > To: Pierre-Yves Strub , caml-list@inria.fr > Reply-To: Alain Frisch > > At LexiFi, we use two different techniques for detecting dead code: > > - Bisect, for a dynamic notion of "dead code" (i.e. code which is not exercised by our testsuite). > > - A custom static detection tool, which parses .cmt and .cmi files to detect exported components (values, exceptions, etc) used by no other module in the project. This is of course combined with the existing compiler warnings on locally unused and non-exported declarations. > > > The next version of OCaml will make it extremely simple to implement such a static detection tool. This is because of the new -keep-locs compiler flag, which allows us to keep the location of exported values in .cmi files, and thus retrieve the same locations on references to such values in .cmt files. It makes it very easy to create the link between an exported value and its references in external modules, even if this goes through e.g. module inclusions. As a proof of concept of this approach, we can already try the tool experimental/frisch/unused_exported_values.ml in the trunk: > > http://caml.inria.fr/cgi-bin/viewvc.cgi/ocaml/trunk/experimental/frisch/unused_exported_values.ml?revision=HEAD&view=markup > > > (-keep-locs also gives "for free" a jump-to-definition feature, just by parsing .cmt or .annot files.) > > > Hope this helps, > > Alain > > > > > On 12/11/2013 03:52 PM, Pierre-Yves Strub wrote: >> Hi all, >> >> Does any of you know a tool for doing dead code detection? >> >> Thanks, >> -- Pierre-Yves. >> >> > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 11 15:12:53 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 11 Dec 2013 15:12:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqlSy-0005Cb-1U; Wed, 11 Dec 2013 15:12:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VqlSx-0005CW-Bw for mirageos-devel@lists.xenproject.org; Wed, 11 Dec 2013 15:12:47 +0000 Received: from [193.109.254.147:47314] by server-13.bemta-14.messagelabs.com id 3D/CA-19374-EE088A25; Wed, 11 Dec 2013 15:12:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-27.messagelabs.com!1386774755!4480719!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNTI2MTAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27665 invoked from network); 11 Dec 2013 15:12:35 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-27.messagelabs.com with SMTP; 11 Dec 2013 15:12:35 -0000 Received: (qmail 29716 invoked by uid 634); 11 Dec 2013 15:12:35 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 11 Dec 2013 15:12:34 +0000 From: Anil Madhavapeddy Date: Wed, 11 Dec 2013 15:12:32 +0000 References: <52A87FB7.8010807@frisch.fr> To: mirageos-devel@lists.xenproject.org Message-Id: <87C6D331-8537-4A96-A271-2CC77717698E@recoil.org> Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Fwd: [Caml-list] Dead code detection X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a really interesting new feature in the next OCaml. We should be able to use it to do comprehensive dead code elimination on both Unix and Xen Mirage binaries on native code (since we don't need dynamic linking). This, in combination with the new module aliases feature, should shrink binary sizes considerably. -anil Begin forwarded message: > From: Alain Frisch > Subject: Re: [Caml-list] Dead code detection > Date: 11 December 2013 15:07:35 GMT > To: Pierre-Yves Strub , caml-list@inria.fr > Reply-To: Alain Frisch > > At LexiFi, we use two different techniques for detecting dead code: > > - Bisect, for a dynamic notion of "dead code" (i.e. code which is not exercised by our testsuite). > > - A custom static detection tool, which parses .cmt and .cmi files to detect exported components (values, exceptions, etc) used by no other module in the project. This is of course combined with the existing compiler warnings on locally unused and non-exported declarations. > > > The next version of OCaml will make it extremely simple to implement such a static detection tool. This is because of the new -keep-locs compiler flag, which allows us to keep the location of exported values in .cmi files, and thus retrieve the same locations on references to such values in .cmt files. It makes it very easy to create the link between an exported value and its references in external modules, even if this goes through e.g. module inclusions. As a proof of concept of this approach, we can already try the tool experimental/frisch/unused_exported_values.ml in the trunk: > > http://caml.inria.fr/cgi-bin/viewvc.cgi/ocaml/trunk/experimental/frisch/unused_exported_values.ml?revision=HEAD&view=markup > > > (-keep-locs also gives "for free" a jump-to-definition feature, just by parsing .cmt or .annot files.) > > > Hope this helps, > > Alain > > > > > On 12/11/2013 03:52 PM, Pierre-Yves Strub wrote: >> Hi all, >> >> Does any of you know a tool for doing dead code detection? >> >> Thanks, >> -- Pierre-Yves. >> >> > > > -- > Caml-list mailing list. Subscription management and archives: > https://sympa.inria.fr/sympa/arc/caml-list > Beginner's list: http://groups.yahoo.com/group/ocaml_beginners > Bug reports: http://caml.inria.fr/bin/caml-bugs > _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Dec 12 09:41:32 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Dec 2013 09:41:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr2ls-0005F2-OM; Thu, 12 Dec 2013 09:41:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr2Gh-0002IO-M9; Thu, 12 Dec 2013 09:09:15 +0000 Received: from [193.109.254.147:46182] by server-16.bemta-14.messagelabs.com id 3C/86-20600-A3D79A25; Thu, 12 Dec 2013 09:09:14 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1386839352!2390354!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiBhYm91dC5tZS9kYXJpby5mYWdnaW9s\naSk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2375 invoked from network); 12 Dec 2013 09:09:14 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 12 Dec 2013 09:09:14 -0000 X-IronPort-AV: E=Sophos;i="4.93,877,1378857600"; d="asc'?scan'208";a="81248523" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 12 Dec 2013 09:08:57 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Thu, 12 Dec 2013 04:08:56 -0500 Message-ID: <1386839335.14726.50.camel@Abyss> From: Dario Faggioli To: Lars Kurth Date: Thu, 12 Dec 2013 10:08:55 +0100 In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Organization: Citrix Ltd X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA1 X-Mailman-Approved-At: Thu, 12 Dec 2013 09:41:27 +0000 Cc: Amir Chaudhry , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6353567660924182753==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6353567660924182753== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2icj5LMjuPJf7z8KRexI" --=-2icj5LMjuPJf7z8KRexI Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mer, 2013-12-11 at 10:21 +0000, Lars Kurth wrote: > Adding publicity >=20 Thanks! ;-P > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry > wrote: > Hi folks, > =20 > Great work today! Now that Mirage 1.0 is out, we need > to put together a bunch of posts to describe the > system and help people (and each-other) get to grips > with it. > =20 > This will effectively form some of the documentation > so it's more than just blog posts and wiki pages -- > getting this content in written form is important and > we can come back to each one to properly > cross-reference. :) > =20 > I've made a new issue on the mirage repo [1] with some > ideas for posts Anil/Dave think are needed and also > some people who could write them. If you're ok with > the list please say so on the issue's comments. The > idea is that once we've agreed on *what* posts we > need, we'll create a *separate* issue for each post, > where we can discuss what the contents need to > include. > =20 > I'd also like us to agree on a schedule of posts so > that this doesn't slip and we can (1) keep the cadence > up while (2) spreading the work. > =20 > [1] https://github.com/mirage/mirage/issues/128 > =20 Wow... Lots of materials here! Just for clarity, these are intended for the Mirage blog, right? Or is it the Xen-Project blog that you're targeting (also)? If the former, well, personally, I think it would be great to have most (if not all) of them in Xen's blog too. As Lars said, we often publish stuff sort of multiple time to amplify the effect. However, if we're worried that would mean too much information duplication, perhaps someone could write a summary, for instance, of the various posts in the 'Homepage' category for the Xen's blog? What I'm sure is that, from just looking at the titles, we _badly_ want something about "Deployment on Amazon" on the Xen-Project blog! :-) The same applies, without even the need to say it, to pretty much everything in the "Xen and the art of /motorcycle/ VM Maintenence" category (especially the first 3 topics) and in the "Lwt" category. Whether a summary or just the post as they are/will be, it depends on the posts themselves... Anyway, that is all very cool, so, please, keep the Xen-Project blog in mind when doing this and let us know (via this publicity@lists.xenproject.org ML) if there is any help you need in that regard. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-2icj5LMjuPJf7z8KRexI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iEYEABECAAYFAlKpfScACgkQk4XaBE3IOsSdFgCglmgz62gp5HOTgpqrcWAOfdz8 rXgAn3AUbV7OgPTEXK8duXZVvcL4TZdC =4GQa -----END PGP SIGNATURE----- --=-2icj5LMjuPJf7z8KRexI-- --===============6353567660924182753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6353567660924182753==-- From mirageos-devel-bounces@lists.xenproject.org Thu Dec 12 09:41:32 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Dec 2013 09:41:32 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr2ls-0005F2-OM; Thu, 12 Dec 2013 09:41:28 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr2Gh-0002IO-M9; Thu, 12 Dec 2013 09:09:15 +0000 Received: from [193.109.254.147:46182] by server-16.bemta-14.messagelabs.com id 3C/86-20600-A3D79A25; Thu, 12 Dec 2013 09:09:14 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1386839352!2390354!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , surbl: (ASYNC_NO) c3VyYmxfcmVjaGVja19kZWxheTogMCAoYWJhbmRv bmVkOiBhYm91dC5tZS9kYXJpby5mYWdnaW9s\naSk=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2375 invoked from network); 12 Dec 2013 09:09:14 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 12 Dec 2013 09:09:14 -0000 X-IronPort-AV: E=Sophos;i="4.93,877,1378857600"; d="asc'?scan'208";a="81248523" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 12 Dec 2013 09:08:57 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Thu, 12 Dec 2013 04:08:56 -0500 Message-ID: <1386839335.14726.50.camel@Abyss> From: Dario Faggioli To: Lars Kurth Date: Thu, 12 Dec 2013 10:08:55 +0100 In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> Organization: Citrix Ltd X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA1 X-Mailman-Approved-At: Thu, 12 Dec 2013 09:41:27 +0000 Cc: Amir Chaudhry , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6353567660924182753==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6353567660924182753== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-2icj5LMjuPJf7z8KRexI" --=-2icj5LMjuPJf7z8KRexI Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mer, 2013-12-11 at 10:21 +0000, Lars Kurth wrote: > Adding publicity >=20 Thanks! ;-P > On Mon, Dec 9, 2013 at 5:31 PM, Amir Chaudhry > wrote: > Hi folks, > =20 > Great work today! Now that Mirage 1.0 is out, we need > to put together a bunch of posts to describe the > system and help people (and each-other) get to grips > with it. > =20 > This will effectively form some of the documentation > so it's more than just blog posts and wiki pages -- > getting this content in written form is important and > we can come back to each one to properly > cross-reference. :) > =20 > I've made a new issue on the mirage repo [1] with some > ideas for posts Anil/Dave think are needed and also > some people who could write them. If you're ok with > the list please say so on the issue's comments. The > idea is that once we've agreed on *what* posts we > need, we'll create a *separate* issue for each post, > where we can discuss what the contents need to > include. > =20 > I'd also like us to agree on a schedule of posts so > that this doesn't slip and we can (1) keep the cadence > up while (2) spreading the work. > =20 > [1] https://github.com/mirage/mirage/issues/128 > =20 Wow... Lots of materials here! Just for clarity, these are intended for the Mirage blog, right? Or is it the Xen-Project blog that you're targeting (also)? If the former, well, personally, I think it would be great to have most (if not all) of them in Xen's blog too. As Lars said, we often publish stuff sort of multiple time to amplify the effect. However, if we're worried that would mean too much information duplication, perhaps someone could write a summary, for instance, of the various posts in the 'Homepage' category for the Xen's blog? What I'm sure is that, from just looking at the titles, we _badly_ want something about "Deployment on Amazon" on the Xen-Project blog! :-) The same applies, without even the need to say it, to pretty much everything in the "Xen and the art of /motorcycle/ VM Maintenence" category (especially the first 3 topics) and in the "Lwt" category. Whether a summary or just the post as they are/will be, it depends on the posts themselves... Anyway, that is all very cool, so, please, keep the Xen-Project blog in mind when doing this and let us know (via this publicity@lists.xenproject.org ML) if there is any help you need in that regard. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-2icj5LMjuPJf7z8KRexI Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iEYEABECAAYFAlKpfScACgkQk4XaBE3IOsSdFgCglmgz62gp5HOTgpqrcWAOfdz8 rXgAn3AUbV7OgPTEXK8duXZVvcL4TZdC =4GQa -----END PGP SIGNATURE----- --=-2icj5LMjuPJf7z8KRexI-- --===============6353567660924182753== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6353567660924182753==-- From mirageos-devel-bounces@lists.xenproject.org Thu Dec 12 11:55:51 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Dec 2013 11:55:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr4rt-0000mO-Dx; Thu, 12 Dec 2013 11:55:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr4rr-0000m1-CG for mirageos-devel@lists.xenproject.org; Thu, 12 Dec 2013 11:55:47 +0000 Received: from [85.158.139.211:27963] by server-15.bemta-5.messagelabs.com id 45/64-08490-244A9A25; Thu, 12 Dec 2013 11:55:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1386849345!4008287!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 744 invoked from network); 12 Dec 2013 11:55:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 12 Dec 2013 11:55:46 -0000 Received: (qmail 20867 invoked by uid 634); 12 Dec 2013 11:55:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 12 Dec 2013 11:55:42 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1386839335.14726.50.camel@Abyss> Date: Thu, 12 Dec 2013 11:55:40 +0000 Message-Id: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> To: Dario Faggioli X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , Amir Chaudhry , Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Dec 2013, at 09:08, Dario Faggioli wrote: >> > Wow... Lots of materials here! > > Just for clarity, these are intended for the Mirage blog, right? Or is > it the Xen-Project blog that you're targeting (also)? These are for the Mirage blog, but I would very much like to distill them into summary documentation suitable for the Xen blog. The audiences for both are fairly different -- the Mirage readers would want more of the mechanics of the toolchain, whereas the Xen crowd probably care more about the details of the protocols. > > If the former, well, personally, I think it would be great to have most > (if not all) of them in Xen's blog too. As Lars said, we often publish > stuff sort of multiple time to amplify the effect. However, if we're > worried that would mean too much information duplication, perhaps > someone could write a summary, for instance, of the various posts in the > 'Homepage' category for the Xen's blog? Agreed -- I suggest we push these out to the Mirage blog over December (the GitHub issue now has target dates on it for those who 'volunteered' on the Mirage call), and then summarise for the Xen blog. > What I'm sure is that, from just looking at the titles, we _badly_ want > something about "Deployment on Amazon" on the Xen-Project blog! :-) > > The same applies, without even the need to say it, to pretty much > everything in the "Xen and the art of /motorcycle/ VM Maintenence" > category (especially the first 3 topics) and in the "Lwt" category. > Whether a summary or just the post as they are/will be, it depends on > the posts themselves... Definitely agree. The OSv folk also have a lot of nice information about deploying custom kernels to EC2, so I'll href their wiki when writing that up. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Dec 12 11:55:51 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 12 Dec 2013 11:55:51 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr4rt-0000mO-Dx; Thu, 12 Dec 2013 11:55:49 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vr4rr-0000m1-CG for mirageos-devel@lists.xenproject.org; Thu, 12 Dec 2013 11:55:47 +0000 Received: from [85.158.139.211:27963] by server-15.bemta-5.messagelabs.com id 45/64-08490-244A9A25; Thu, 12 Dec 2013 11:55:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1386849345!4008287!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.5 required=7.0 tests=BODY_RANDOM_LONG X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 744 invoked from network); 12 Dec 2013 11:55:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 12 Dec 2013 11:55:46 -0000 Received: (qmail 20867 invoked by uid 634); 12 Dec 2013 11:55:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.110]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 12 Dec 2013 11:55:42 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1386839335.14726.50.camel@Abyss> Date: Thu, 12 Dec 2013 11:55:40 +0000 Message-Id: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> To: Dario Faggioli X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Lars Kurth , Amir Chaudhry , Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 12 Dec 2013, at 09:08, Dario Faggioli wrote: >> > Wow... Lots of materials here! > > Just for clarity, these are intended for the Mirage blog, right? Or is > it the Xen-Project blog that you're targeting (also)? These are for the Mirage blog, but I would very much like to distill them into summary documentation suitable for the Xen blog. The audiences for both are fairly different -- the Mirage readers would want more of the mechanics of the toolchain, whereas the Xen crowd probably care more about the details of the protocols. > > If the former, well, personally, I think it would be great to have most > (if not all) of them in Xen's blog too. As Lars said, we often publish > stuff sort of multiple time to amplify the effect. However, if we're > worried that would mean too much information duplication, perhaps > someone could write a summary, for instance, of the various posts in the > 'Homepage' category for the Xen's blog? Agreed -- I suggest we push these out to the Mirage blog over December (the GitHub issue now has target dates on it for those who 'volunteered' on the Mirage call), and then summarise for the Xen blog. > What I'm sure is that, from just looking at the titles, we _badly_ want > something about "Deployment on Amazon" on the Xen-Project blog! :-) > > The same applies, without even the need to say it, to pretty much > everything in the "Xen and the art of /motorcycle/ VM Maintenence" > category (especially the first 3 topics) and in the "Lwt" category. > Whether a summary or just the post as they are/will be, it depends on > the posts themselves... Definitely agree. The OSv folk also have a lot of nice information about deploying custom kernels to EC2, so I'll href their wiki when writing that up. cheers, Anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 02:34:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 02:34:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrIZp-0006Oh-EL; Fri, 13 Dec 2013 02:34:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrIZo-0006OY-EH; Fri, 13 Dec 2013 02:34:04 +0000 Received: from [85.158.137.68:12663] by server-12.bemta-3.messagelabs.com id 61/88-20055-B127AA25; Fri, 13 Dec 2013 02:34:03 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1386902033!3586787!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNjQyMTAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25665 invoked from network); 13 Dec 2013 02:33:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Dec 2013 02:33:54 -0000 X-IronPort-AV: E=Sophos;i="4.95,476,1384300800"; d="asc'?scan'208";a="84026652" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 13 Dec 2013 02:33:52 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Thu, 12 Dec 2013 21:33:52 -0500 Message-ID: <1386902030.5488.157.camel@Solace> From: Dario Faggioli To: Anil Madhavapeddy Date: Fri, 13 Dec 2013 03:33:50 +0100 In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: Lars Kurth , Amir Chaudhry , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3793040012621837164==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3793040012621837164== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NFPbTInpI4xTlbk2MtMc" --=-NFPbTInpI4xTlbk2MtMc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On gio, 2013-12-12 at 11:55 +0000, Anil Madhavapeddy wrote: > On 12 Dec 2013, at 09:08, Dario Faggioli wrot= e: > > If the former, well, personally, I think it would be great to have most > > (if not all) of them in Xen's blog too. As Lars said, we often publish > > stuff sort of multiple time to amplify the effect. However, if we're > > worried that would mean too much information duplication, perhaps > > someone could write a summary, for instance, of the various posts in th= e > > 'Homepage' category for the Xen's blog? >=20 > Agreed -- I suggest we push these out to the Mirage blog over December > (the GitHub issue now has target dates on it for those who 'volunteered'= =20 > on the Mirage call), and then summarise for the Xen blog. >=20 Ok then. Ping us here whenever you think you have a date for such a summary(ies), and we'll put the in our schedule. > Definitely agree. The OSv folk also have a lot of nice information about > deploying custom kernels to EC2, so I'll href their wiki when writing > that up. >=20 Definitely. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-NFPbTInpI4xTlbk2MtMc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iEYEABECAAYFAlKqcg4ACgkQk4XaBE3IOsSY+ACgj0BS1FTQiE1wCdFD5D2DAGs3 KnAAoKzQGQnSCOxIpGni4N525IGWR6Wg =RyJc -----END PGP SIGNATURE----- --=-NFPbTInpI4xTlbk2MtMc-- --===============3793040012621837164== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3793040012621837164==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 02:34:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 02:34:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrIZp-0006Oh-EL; Fri, 13 Dec 2013 02:34:05 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrIZo-0006OY-EH; Fri, 13 Dec 2013 02:34:04 +0000 Received: from [85.158.137.68:12663] by server-12.bemta-3.messagelabs.com id 61/88-20055-B127AA25; Fri, 13 Dec 2013 02:34:03 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-5.tower-31.messagelabs.com!1386902033!3586787!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n, ML_RADAR_SPEW_LINKS_8, spamassassin: , async_handler: YXN5bmNfZGVsYXk6IDcwNjQyMTAgKHRpbWVvdXQp\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25665 invoked from network); 13 Dec 2013 02:33:54 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-5.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 13 Dec 2013 02:33:54 -0000 X-IronPort-AV: E=Sophos;i="4.95,476,1384300800"; d="asc'?scan'208";a="84026652" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 13 Dec 2013 02:33:52 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Thu, 12 Dec 2013 21:33:52 -0500 Message-ID: <1386902030.5488.157.camel@Solace> From: Dario Faggioli To: Anil Madhavapeddy Date: Fri, 13 Dec 2013 03:33:50 +0100 In-Reply-To: References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <1386839335.14726.50.camel@Abyss> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: Lars Kurth , Amir Chaudhry , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3793040012621837164==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3793040012621837164== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-NFPbTInpI4xTlbk2MtMc" --=-NFPbTInpI4xTlbk2MtMc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On gio, 2013-12-12 at 11:55 +0000, Anil Madhavapeddy wrote: > On 12 Dec 2013, at 09:08, Dario Faggioli wrot= e: > > If the former, well, personally, I think it would be great to have most > > (if not all) of them in Xen's blog too. As Lars said, we often publish > > stuff sort of multiple time to amplify the effect. However, if we're > > worried that would mean too much information duplication, perhaps > > someone could write a summary, for instance, of the various posts in th= e > > 'Homepage' category for the Xen's blog? >=20 > Agreed -- I suggest we push these out to the Mirage blog over December > (the GitHub issue now has target dates on it for those who 'volunteered'= =20 > on the Mirage call), and then summarise for the Xen blog. >=20 Ok then. Ping us here whenever you think you have a date for such a summary(ies), and we'll put the in our schedule. > Definitely agree. The OSv folk also have a lot of nice information about > deploying custom kernels to EC2, so I'll href their wiki when writing > that up. >=20 Definitely. Thanks and Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-NFPbTInpI4xTlbk2MtMc Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iEYEABECAAYFAlKqcg4ACgkQk4XaBE3IOsSY+ACgj0BS1FTQiE1wCdFD5D2DAGs3 KnAAoKzQGQnSCOxIpGni4N525IGWR6Wg =RyJc -----END PGP SIGNATURE----- --=-NFPbTInpI4xTlbk2MtMc-- --===============3793040012621837164== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3793040012621837164==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 10:18:59 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 10:18:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPpf-000410-Vm; Fri, 13 Dec 2013 10:18:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPNp-0001nF-6A; Fri, 13 Dec 2013 09:50:09 +0000 Received: from [193.109.254.147:16526] by server-8.bemta-14.messagelabs.com id E4/98-30921-058DAA25; Fri, 13 Dec 2013 09:50:08 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1386928206!4972840!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10186 invoked from network); 13 Dec 2013 09:50:07 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Dec 2013 09:50:07 -0000 X-IronPort-AV: E=Sophos;i="4.95,477,1384300800"; d="scan'208";a="84213120" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 13 Dec 2013 09:50:06 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Fri, 13 Dec 2013 04:50:05 -0500 Message-ID: <52AAD84C.3020803@citrix.com> Date: Fri, 13 Dec 2013 10:50:04 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Amir Chaudhry , Lars Kurth References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 X-DLP: MIA2 X-Mailman-Approved-At: Fri, 13 Dec 2013 10:18:54 +0000 Cc: Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11/12/13 12:08, Amir Chaudhry wrote: > Great! I'm looking forward to the report. I have a Google Alert set up but that's going to be delayed by indexing (and is a little crude). I can tell you that we had nice write ups in Dutch and Catalan :) Out of curiosity, could you point me to the Catalan write up? I'm a Catalan speaker and I would like to give it a look. :) Roger. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 10:18:59 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 10:18:59 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPpf-000410-Vm; Fri, 13 Dec 2013 10:18:55 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPNp-0001nF-6A; Fri, 13 Dec 2013 09:50:09 +0000 Received: from [193.109.254.147:16526] by server-8.bemta-14.messagelabs.com id E4/98-30921-058DAA25; Fri, 13 Dec 2013 09:50:08 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-15.tower-27.messagelabs.com!1386928206!4972840!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10186 invoked from network); 13 Dec 2013 09:50:07 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-15.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 13 Dec 2013 09:50:07 -0000 X-IronPort-AV: E=Sophos;i="4.95,477,1384300800"; d="scan'208";a="84213120" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 13 Dec 2013 09:50:06 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Fri, 13 Dec 2013 04:50:05 -0500 Message-ID: <52AAD84C.3020803@citrix.com> Date: Fri, 13 Dec 2013 10:50:04 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Amir Chaudhry , Lars Kurth References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> In-Reply-To: X-Enigmail-Version: 1.6 X-DLP: MIA2 X-Mailman-Approved-At: Fri, 13 Dec 2013 10:18:54 +0000 Cc: Publicity list , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 11/12/13 12:08, Amir Chaudhry wrote: > Great! I'm looking forward to the report. I have a Google Alert set up but that's going to be delayed by indexing (and is a little crude). I can tell you that we had nice write ups in Dutch and Catalan :) Out of curiosity, could you point me to the Catalan write up? I'm a Catalan speaker and I would like to give it a look. :) Roger. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 10:23:36 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 10:23:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPuC-00047O-CS; Fri, 13 Dec 2013 10:23:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPuA-00047G-GB; Fri, 13 Dec 2013 10:23:34 +0000 Received: from [193.109.254.147:13176] by server-3.bemta-14.messagelabs.com id 74/9E-11000-520EAA25; Fri, 13 Dec 2013 10:23:33 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-15.tower-27.messagelabs.com!1386930213!4982349!1 X-Originating-IP: [131.111.8.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25312 invoked from network); 13 Dec 2013 10:23:33 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Dec 2013 10:23:33 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:54236 helo=amirmacbook.home) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VrPu8-0000uZ-0s (Exim 4.82_3-c0e5623) (return-path ); Fri, 13 Dec 2013 10:23:32 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <52AAD84C.3020803@citrix.com> Date: Fri, 13 Dec 2013 10:23:32 +0000 Message-Id: <8BF0D9E1-64E5-4F3E-81D3-5EC724F27C31@cam.ac.uk> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <52AAD84C.3020803@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1510) Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 13 Dec 2013, at 09:50, Roger Pau Monn=E9 wrote: > On 11/12/13 12:08, Amir Chaudhry wrote: >> Great! I'm looking forward to the report. I have a Google Alert set up= but that's going to be delayed by indexing (and is a little crude). I can= tell you that we had nice write ups in Dutch and Catalan :) > = > Out of curiosity, could you point me to the Catalan write up? I'm a > Catalan speaker and I would like to give it a look. :) http://cat.imatica.org/arxiu/noticies/23567/mirage-os-el-sistema-operatiu-o= ptimitzat-per-aplicacions-cloud I had to run it through Google Translate, which told me it was Catalan. :) Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 10:23:36 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 10:23:36 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPuC-00047O-CS; Fri, 13 Dec 2013 10:23:36 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrPuA-00047G-GB; Fri, 13 Dec 2013 10:23:34 +0000 Received: from [193.109.254.147:13176] by server-3.bemta-14.messagelabs.com id 74/9E-11000-520EAA25; Fri, 13 Dec 2013 10:23:33 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-15.tower-27.messagelabs.com!1386930213!4982349!1 X-Originating-IP: [131.111.8.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25312 invoked from network); 13 Dec 2013 10:23:33 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-15.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 13 Dec 2013 10:23:33 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from host81-149-102-120.in-addr.btopenworld.com ([81.149.102.120]:54236 helo=amirmacbook.home) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VrPu8-0000uZ-0s (Exim 4.82_3-c0e5623) (return-path ); Fri, 13 Dec 2013 10:23:32 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <52AAD84C.3020803@citrix.com> Date: Fri, 13 Dec 2013 10:23:32 +0000 Message-Id: <8BF0D9E1-64E5-4F3E-81D3-5EC724F27C31@cam.ac.uk> References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <52AAD84C.3020803@citrix.com> To: =?iso-8859-1?Q?Roger_Pau_Monn=E9?= X-Mailer: Apple Mail (2.1510) Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 13 Dec 2013, at 09:50, Roger Pau Monn=E9 wrote: > On 11/12/13 12:08, Amir Chaudhry wrote: >> Great! I'm looking forward to the report. I have a Google Alert set up= but that's going to be delayed by indexing (and is a little crude). I can= tell you that we had nice write ups in Dutch and Catalan :) > = > Out of curiosity, could you point me to the Catalan write up? I'm a > Catalan speaker and I would like to give it a look. :) http://cat.imatica.org/arxiu/noticies/23567/mirage-os-el-sistema-operatiu-o= ptimitzat-per-aplicacions-cloud I had to run it through Google Translate, which told me it was Catalan. :) Amir _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 10:45:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 10:45:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrQF1-00054M-Fw; Fri, 13 Dec 2013 10:45:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrQF0-000549-MY; Fri, 13 Dec 2013 10:45:06 +0000 Received: from [85.158.143.35:64343] by server-1.bemta-4.messagelabs.com id 0A/76-02132-135EAA25; Fri, 13 Dec 2013 10:45:05 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1386931503!5462728!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28343 invoked from network); 13 Dec 2013 10:45:05 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Dec 2013 10:45:05 -0000 X-IronPort-AV: E=Sophos;i="4.95,477,1384300800"; d="scan'208";a="81931735" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 13 Dec 2013 10:44:51 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Fri, 13 Dec 2013 05:44:51 -0500 Message-ID: <52AAE522.6060405@citrix.com> Date: Fri, 13 Dec 2013 11:44:50 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Amir Chaudhry References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <52AAD84C.3020803@citrix.com> <8BF0D9E1-64E5-4F3E-81D3-5EC724F27C31@cam.ac.uk> In-Reply-To: <8BF0D9E1-64E5-4F3E-81D3-5EC724F27C31@cam.ac.uk> X-Enigmail-Version: 1.6 X-DLP: MIA1 Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 13/12/13 11:23, Amir Chaudhry wrote: > = > On 13 Dec 2013, at 09:50, Roger Pau Monn=E9 wrote: > = >> On 11/12/13 12:08, Amir Chaudhry wrote: >>> Great! I'm looking forward to the report. I have a Google Alert set u= p but that's going to be delayed by indexing (and is a little crude). I ca= n tell you that we had nice write ups in Dutch and Catalan :) >> >> Out of curiosity, could you point me to the Catalan write up? I'm a >> Catalan speaker and I would like to give it a look. :) > = > http://cat.imatica.org/arxiu/noticies/23567/mirage-os-el-sistema-operatiu= -optimitzat-per-aplicacions-cloud > = > I had to run it through Google Translate, which told me it was Catalan. :) Thanks, it's a nice write up and it also covers the recent addition of ARM into the Xen Project, I've made a comment :). Roger. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 13 10:45:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 13 Dec 2013 10:45:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrQF1-00054M-Fw; Fri, 13 Dec 2013 10:45:07 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VrQF0-000549-MY; Fri, 13 Dec 2013 10:45:06 +0000 Received: from [85.158.143.35:64343] by server-1.bemta-4.messagelabs.com id 0A/76-02132-135EAA25; Fri, 13 Dec 2013 10:45:05 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1386931503!5462728!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28343 invoked from network); 13 Dec 2013 10:45:05 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 13 Dec 2013 10:45:05 -0000 X-IronPort-AV: E=Sophos;i="4.95,477,1384300800"; d="scan'208";a="81931735" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 13 Dec 2013 10:44:51 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Fri, 13 Dec 2013 05:44:51 -0500 Message-ID: <52AAE522.6060405@citrix.com> Date: Fri, 13 Dec 2013 11:44:50 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Amir Chaudhry References: <99DF25E9-B4D5-48BE-B7D1-0DD06C4EDE8B@gmail.com> <52AAD84C.3020803@citrix.com> <8BF0D9E1-64E5-4F3E-81D3-5EC724F27C31@cam.ac.uk> In-Reply-To: <8BF0D9E1-64E5-4F3E-81D3-5EC724F27C31@cam.ac.uk> X-Enigmail-Version: 1.6 X-DLP: MIA1 Cc: Lars Kurth , "mirageos-devel@lists.xenproject.org" , Publicity list Subject: Re: [MirageOS-devel] [Publicity] Scheduling some posts for openmirage.org X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 13/12/13 11:23, Amir Chaudhry wrote: > = > On 13 Dec 2013, at 09:50, Roger Pau Monn=E9 wrote: > = >> On 11/12/13 12:08, Amir Chaudhry wrote: >>> Great! I'm looking forward to the report. I have a Google Alert set u= p but that's going to be delayed by indexing (and is a little crude). I ca= n tell you that we had nice write ups in Dutch and Catalan :) >> >> Out of curiosity, could you point me to the Catalan write up? I'm a >> Catalan speaker and I would like to give it a look. :) > = > http://cat.imatica.org/arxiu/noticies/23567/mirage-os-el-sistema-operatiu= -optimitzat-per-aplicacions-cloud > = > I had to run it through Google Translate, which told me it was Catalan. :) Thanks, it's a nice write up and it also covers the recent addition of ARM into the Xen Project, I've made a comment :). Roger. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 15 19:26:15 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Dec 2013 19:26:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHKN-0002hP-RT; Sun, 15 Dec 2013 19:26:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHKL-0002hJ-W5 for mirageos-devel@lists.xenproject.org; Sun, 15 Dec 2013 19:26:10 +0000 Received: from [85.158.143.35:15669] by server-3.bemta-4.messagelabs.com id C6/F3-32360-1520EA25; Sun, 15 Dec 2013 19:26:09 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1387135568!5874649!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 466 invoked from network); 15 Dec 2013 19:26:08 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 15 Dec 2013 19:26:08 -0000 Received: (qmail 8162 invoked by uid 634); 15 Dec 2013 19:26:08 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 15 Dec 2013 19:26:07 +0000 From: Anil Madhavapeddy Message-Id: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> Date: Sun, 15 Dec 2013 19:26:04 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The main website now compiles with 1.0 and crunch, with this (now-merged) pull request: https://github.com/mirage/mirage-www/pull/56 It was a fairly brute-force merge, but makes it much easier to break up the old website into a cleaner one based on the Cowabloga library. I then took a shot at recompiling the website to use a dynamic FAT block device instead of the static crunch filesystem. This required a few minor changes to libraries: - Add a KV_RO compatible mode to FAT which simplifies its normally read/write FS interface: https://github.com/mirage/mirage/pull/160 - Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160 - Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57 This plumbing was all pretty straightforward, but triggers a bug somewhere in the FAT directory traversal, so the resulting website doesn't actually read the files in FAT mode yet. Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, and we'll have a pass-through to the filesystem to make it easier to develop code without recompiling all the time. TL;DR: blog post very soon, forgive the slight delay :-) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 15 19:26:15 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Dec 2013 19:26:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHKN-0002hP-RT; Sun, 15 Dec 2013 19:26:11 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHKL-0002hJ-W5 for mirageos-devel@lists.xenproject.org; Sun, 15 Dec 2013 19:26:10 +0000 Received: from [85.158.143.35:15669] by server-3.bemta-4.messagelabs.com id C6/F3-32360-1520EA25; Sun, 15 Dec 2013 19:26:09 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-7.tower-21.messagelabs.com!1387135568!5874649!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 466 invoked from network); 15 Dec 2013 19:26:08 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-7.tower-21.messagelabs.com with SMTP; 15 Dec 2013 19:26:08 -0000 Received: (qmail 8162 invoked by uid 634); 15 Dec 2013 19:26:08 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sun, 15 Dec 2013 19:26:07 +0000 From: Anil Madhavapeddy Message-Id: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> Date: Sun, 15 Dec 2013 19:26:04 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The main website now compiles with 1.0 and crunch, with this (now-merged) pull request: https://github.com/mirage/mirage-www/pull/56 It was a fairly brute-force merge, but makes it much easier to break up the old website into a cleaner one based on the Cowabloga library. I then took a shot at recompiling the website to use a dynamic FAT block device instead of the static crunch filesystem. This required a few minor changes to libraries: - Add a KV_RO compatible mode to FAT which simplifies its normally read/write FS interface: https://github.com/mirage/mirage/pull/160 - Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160 - Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57 This plumbing was all pretty straightforward, but triggers a bug somewhere in the FAT directory traversal, so the resulting website doesn't actually read the files in FAT mode yet. Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, and we'll have a pass-through to the filesystem to make it easier to develop code without recompiling all the time. TL;DR: blog post very soon, forgive the slight delay :-) -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 15 19:38:33 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Dec 2013 19:38:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHWK-0003QL-Pj; Sun, 15 Dec 2013 19:38:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHWJ-0003Pa-LD for mirageos-devel@lists.xenproject.org; Sun, 15 Dec 2013 19:38:31 +0000 Received: from [85.158.143.35:26137] by server-3.bemta-4.messagelabs.com id C0/48-32360-7350EA25; Sun, 15 Dec 2013 19:38:31 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-6.tower-21.messagelabs.com!1387136310!5933234!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15568 invoked from network); 15 Dec 2013 19:38:30 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-6.tower-21.messagelabs.com with SMTP; 15 Dec 2013 19:38:30 -0000 Received: (qmail 24394 invoked from network); 15 Dec 2013 19:38:26 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 15 Dec 2013 19:38:26 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 23987-06 for ; Sun, 15 Dec 2013 19:38:25 +0000 (GMT) Received: (qmail 24360 invoked by uid 599); 15 Dec 2013 19:38:21 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 15 Dec 2013 19:38:21 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VsHWB-0003RS-65; Sun, 15 Dec 2013 19:38:23 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 15 Dec 2013 19:38:22 +0000 Thread-Topic: [MirageOS-devel] Mirage-WWW porting status Thread-Index: Ac75zTcgqlKcE9h8Qsmj4oLVzqwrsQ== Message-ID: <2E68401E-9593-4847-BDD9-4B4B1BCE7DF8@nottingham.ac.uk> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> In-Reply-To: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 Dec 2013, at 19:26, Anil Madhavapeddy wrote: > I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The main website now compiles with 1.0 and crunch, with this (now-merged) pull request: > https://github.com/mirage/mirage-www/pull/56 > > It was a fairly brute-force merge, but makes it much easier to break up the old website into a cleaner one based on the Cowabloga library. ...cool. i'll try and have a go at mirage-decks in light of these changes to mirage-www tomorrow on the train then :) > Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, and we'll have a pass-through to the filesystem to make it easier to develop code without recompiling all the time. > > TL;DR: blog post very soon, forgive the slight delay :-) ditto :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sun Dec 15 19:38:33 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sun, 15 Dec 2013 19:38:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHWK-0003QL-Pj; Sun, 15 Dec 2013 19:38:32 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsHWJ-0003Pa-LD for mirageos-devel@lists.xenproject.org; Sun, 15 Dec 2013 19:38:31 +0000 Received: from [85.158.143.35:26137] by server-3.bemta-4.messagelabs.com id C0/48-32360-7350EA25; Sun, 15 Dec 2013 19:38:31 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-6.tower-21.messagelabs.com!1387136310!5933234!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15568 invoked from network); 15 Dec 2013 19:38:30 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-6.tower-21.messagelabs.com with SMTP; 15 Dec 2013 19:38:30 -0000 Received: (qmail 24394 invoked from network); 15 Dec 2013 19:38:26 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 15 Dec 2013 19:38:26 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 23987-06 for ; Sun, 15 Dec 2013 19:38:25 +0000 (GMT) Received: (qmail 24360 invoked by uid 599); 15 Dec 2013 19:38:21 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 15 Dec 2013 19:38:21 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VsHWB-0003RS-65; Sun, 15 Dec 2013 19:38:23 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Sun, 15 Dec 2013 19:38:22 +0000 Thread-Topic: [MirageOS-devel] Mirage-WWW porting status Thread-Index: Ac75zTcgqlKcE9h8Qsmj4oLVzqwrsQ== Message-ID: <2E68401E-9593-4847-BDD9-4B4B1BCE7DF8@nottingham.ac.uk> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> In-Reply-To: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 Dec 2013, at 19:26, Anil Madhavapeddy wrote: > I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The main website now compiles with 1.0 and crunch, with this (now-merged) pull request: > https://github.com/mirage/mirage-www/pull/56 > > It was a fairly brute-force merge, but makes it much easier to break up the old website into a cleaner one based on the Cowabloga library. ...cool. i'll try and have a go at mirage-decks in light of these changes to mirage-www tomorrow on the train then :) > Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, and we'll have a pass-through to the filesystem to make it easier to develop code without recompiling all the time. > > TL;DR: blog post very soon, forgive the slight delay :-) ditto :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 16 11:24:17 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Dec 2013 11:24:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsWHU-00084r-PJ; Mon, 16 Dec 2013 11:24:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsWHT-00084m-FJ for mirageos-devel@lists.xenproject.org; Mon, 16 Dec 2013 11:24:11 +0000 Received: from [85.158.139.211:28628] by server-13.bemta-5.messagelabs.com id 17/65-11357-AD2EEA25; Mon, 16 Dec 2013 11:24:10 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1387193049!4734386!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6664 invoked from network); 16 Dec 2013 11:24:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-206.messagelabs.com with SMTP; 16 Dec 2013 11:24:10 -0000 Received: (qmail 19169 invoked by uid 634); 16 Dec 2013 11:24:09 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 16 Dec 2013 11:24:09 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <2E68401E-9593-4847-BDD9-4B4B1BCE7DF8@nottingham.ac.uk> Date: Mon, 16 Dec 2013 11:24:06 +0000 Message-Id: <7C54B1AD-A89A-4C79-A8CF-3B7C382565AB@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> <2E68401E-9593-4847-BDD9-4B4B1BCE7DF8@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 Dec 2013, at 19:38, Richard Mortier wrote: > > On 15 Dec 2013, at 19:26, Anil Madhavapeddy wrote: > >> I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The main website now compiles with 1.0 and crunch, with this (now-merged) pull request: >> https://github.com/mirage/mirage-www/pull/56 >> >> It was a fairly brute-force merge, but makes it much easier to break up the old website into a cleaner one based on the Cowabloga library. > > ...cool. i'll try and have a go at mirage-decks in light of these changes to mirage-www tomorrow on the train then :) > I've made one more change to the pull request at: https://github.com/mirage/mirage/pull/160 With the new mirage/mirage-fs-unix (not packaged in OPAM yet), the Unix version will pass through to the underlying filesystem. This gets us back to the convenient mode of developing under Unix without needing to recompile for every datafile change, but still being able to crunch it up for deployment on Xen. Thomas, I think we need to think about how to abstract this matrix of Xen/Unix Fs/Block/KV_RO a little more in the Mirage cmdline tool, since it's getting to be quite combinatorial now (and every possibility has a good use in some deployment). -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 16 11:24:17 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Dec 2013 11:24:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsWHU-00084r-PJ; Mon, 16 Dec 2013 11:24:12 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsWHT-00084m-FJ for mirageos-devel@lists.xenproject.org; Mon, 16 Dec 2013 11:24:11 +0000 Received: from [85.158.139.211:28628] by server-13.bemta-5.messagelabs.com id 17/65-11357-AD2EEA25; Mon, 16 Dec 2013 11:24:10 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-206.messagelabs.com!1387193049!4734386!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6664 invoked from network); 16 Dec 2013 11:24:10 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-206.messagelabs.com with SMTP; 16 Dec 2013 11:24:10 -0000 Received: (qmail 19169 invoked by uid 634); 16 Dec 2013 11:24:09 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 16 Dec 2013 11:24:09 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <2E68401E-9593-4847-BDD9-4B4B1BCE7DF8@nottingham.ac.uk> Date: Mon, 16 Dec 2013 11:24:06 +0000 Message-Id: <7C54B1AD-A89A-4C79-A8CF-3B7C382565AB@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> <2E68401E-9593-4847-BDD9-4B4B1BCE7DF8@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 15 Dec 2013, at 19:38, Richard Mortier wrote: > > On 15 Dec 2013, at 19:26, Anil Madhavapeddy wrote: > >> I've been making good progress on porting Mirage/WWW to the 1.0 libraries. The main website now compiles with 1.0 and crunch, with this (now-merged) pull request: >> https://github.com/mirage/mirage-www/pull/56 >> >> It was a fairly brute-force merge, but makes it much easier to break up the old website into a cleaner one based on the Cowabloga library. > > ...cool. i'll try and have a go at mirage-decks in light of these changes to mirage-www tomorrow on the train then :) > I've made one more change to the pull request at: https://github.com/mirage/mirage/pull/160 With the new mirage/mirage-fs-unix (not packaged in OPAM yet), the Unix version will pass through to the underlying filesystem. This gets us back to the convenient mode of developing under Unix without needing to recompile for every datafile change, but still being able to crunch it up for deployment on Xen. Thomas, I think we need to think about how to abstract this matrix of Xen/Unix Fs/Block/KV_RO a little more in the Mirage cmdline tool, since it's getting to be quite combinatorial now (and every possibility has a good use in some deployment). -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 16 19:10:26 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Dec 2013 19:10:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsdYd-0001Ux-Az; Mon, 16 Dec 2013 19:10:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsdYb-0001Us-MX for mirageos-devel@lists.xenproject.org; Mon, 16 Dec 2013 19:10:22 +0000 Received: from [193.109.254.147:62247] by server-10.bemta-14.messagelabs.com id 93/24-20752-D105FA25; Mon, 16 Dec 2013 19:10:21 +0000 X-Env-Sender: jamesjb@jamesjb.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1387221018!5642119!1 X-Originating-IP: [173.230.155.117] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28110 invoked from network); 16 Dec 2013 19:10:19 -0000 Received: from coda.jamesjb.com (HELO coda.jamesjb.com) (173.230.155.117) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Dec 2013 19:10:19 -0000 Received: from [192.168.40.164] (pdx.galois.com [66.162.129.26]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by coda.jamesjb.com (Postfix) with ESMTPSA id 00947C323 for ; Mon, 16 Dec 2013 11:10:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jamesjb.com; s=mail; t=1387221018; bh=IZgaeUVNR80b/Yu52/a+BO+hDJInFRgh5d88pJWPDDU=; h=Date:From:To:Subject:From; b=memwarITPwXAieCQ/iXlt8ukFocTR4eXdeBlV/nIIRD43cD1YCjXjBN7KUHGg3b1J D5VVNmSfTJPRupBTV8OmfCCASSIb64Xy2ez7iHTZTIur02UMnBwV6bCfLByFaXw4bv 0cNf8RVnKN/XGqDjG4LGNz2m2ycTBAMmfUBxSl0I= Message-ID: <52AF5019.8050105@jamesjb.com> Date: Mon, 16 Dec 2013 11:10:17 -0800 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Enigmail-Version: 1.5.2 Subject: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1694089591805376213==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============1694089591805376213== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070308030109040804030900" This is a cryptographically signed message in MIME format. --------------ms070308030109040804030900 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all, I'm using Mirage to build a Xen kernel, and would like to include a C library compiled against the Mirage runtime (along with OCaml stubs for i= t). My question is about the build process, especially when installing via OPAM. mirage-platform doesn't seem to install the headers for its dietlibc anywhere that a dependent project can find them. I could require a user to have a checkout of mirage-platform at hand to build, but that feels awkward when previously everything could be installed via OPAM except for the kernel itself (which builds with mirari= ). Does anyone have any recommendations about how to export build dependencies like header files (and also matching the CFLAGS/LDFLAGS used for the Mirage runtime would be nice to have as well). Thanks! James --------------ms070308030109040804030900 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSzCC BkIwggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0 aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJp bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIx MDgzMTIzNTk1OVowgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3Jh dGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29u YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg U3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn /R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEiVzAhJZCao/SsKsaIF4ZhchN2LuwDyyeb jyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+DeyxtmSSq5937hEH5u6P4wG/tgjT0hR I2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/xhR7DtryBeTTgwKmxWlwtKnk VunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28ODC7iCbDZ2ZmtLR3+cCh xw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQABo4ICRDCCAkAwOAYI KwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsG AQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRw Oi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXE Cl4aATCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsT MShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBD BgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaP wdqbiPKzbE0fWC+6AVFddMFG6MO4e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKM YJsrnGVJlMSiOCRIpVylUEto6WIip5PomSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBi Te/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP95WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26t lcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ 3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXidE0HbYQwggcBMIIF6aADAgECAhBF ZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UE ChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdv cmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMg Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzA3MjUwMDAwMDBa Fw0xNDA3MjYyMzU5NTlaMIHFMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0ZWQgLSAx Mzc0NzY5NTI5NzQ0MSIwIAYJKoZIhvcNAQkBFhNqYW1lc2piQGphbWVzamIuY29tMQ8wDQYD VQQLDAZTL01JTUUxHjAcBgNVBAsMFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEfMB0GA1UECwwW U3ltYW50ZWMgVHJ1c3QgTmV0d29yazEdMBsGA1UECgwUU3ltYW50ZWMgQ29ycG9yYXRpb24w ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCeYv0utKyX/A6tXdd9HE8cpVWbw5tq CfyEkqKDzIvDq9qmS1R9MpsIKphabrC8EtGLikEqaDcI67YbfvwNLXApUGfL5CzUNBz5j3SY 1uqgUeSV3+ShaFQ2SeLE+9WHvHAmJuHPnk6INaHhhUe+s4GduOGlD7juDc98VB5jwsw665oE QYrkadbQxfhMgOiHDtp+z3f8KafpRpgpY8QgIAhoXcMHycelPGcRFoAsDRN0dm9vG7i4IKaJ 5wi+zm8EegnWUyKYYHjx9s9wxtR+1byN9QF/gN9bf5ZQXTlBjZ6cjXXyWzBcNzYHwmRJfDPJ az+ybb5NJJIM8XobQT2CGFaBAgMBAAGjggMIMIIDBDAMBgNVHRMBAf8EAjAAMA4GA1UdDwEB /wQEAwIFoDAgBgNVHSUBAf8EFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwHQYDVR0OBBYEFHjg 3KlUkzacyiWvqJ5g0ZBF1clUMB4GA1UdEQQXMBWBE2phbWVzamJAamFtZXNqYi5jb20wHwYD VR0jBBgwFoAUrfnDk3IttbkoYeSk12DVxApeGgEwggErBggrBgEFBQcBAQSCAR0wggEZMIIB FQYIKwYBBQUHMAKGggEHbGRhcDovL2RpcmVjdG9yeS52ZXJpc2lnbi5jb20vQ04lMjAlM0Ql MjBTeW1hbnRlYyUyMENsYXNzJTIwMSUyMEluZGl2aWR1YWwlMjBTdWJzY3JpYmVyJTIwQ0El MjAtJTIwRzQlMkMlMjBPVSUyMCUzRCUyMFBlcnNvbmElMjBOb3QlMjBWYWxpZGF0ZWQlMkMl MjBPVSUyMCUzRCUyMFN5bWFudGVjJTIwVHJ1c3QlMjBOZXR3b3JrJTJDJTIwTyUyMCUzRCUy MFN5bWFudGVjJTIwQ29ycG9yYXRpb24lMkMlMjBDJTIwJTNEJTIwVVM/Y0FDZXJ0aWZpY2F0 ZTtiaW5hcnkwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL3BraS1jcmwuc3ltYXV0aC5jb20v Y2FfNTYxYzEwMzY5MGM5N2E2OTI0N2EwZWYwNzFhYzgxYWYvTGF0ZXN0Q1JMLmNybDBsBgNV HSAEZTBjMGEGC2CGSAGG+EUBBxcBMFIwJgYIKwYBBQUHAgEWGmh0dHA6Ly93d3cuc3ltYXV0 aC5jb20vY3BzMCgGCCsGAQUFBwICMBwaGmh0dHA6Ly93d3cuc3ltYXV0aC5jb20vcnBhMCsG CmCGSAGG+EUBEAMEHTAbBhJghkgBhvhFARABAgIEAYbHzm8WBTEwOTIyMDkGCmCGSAGG+EUB EAUEKzApAgEAFiRhSFIwY0hNNkx5OXdhMmt0Y21FdWMzbHRZWFYwYUM1amIyMD0wDQYJKoZI hvcNAQEFBQADggEBAHEzHvbp3O2aQGCu8zVjdo+AxkY0T0G1+YC4kMJVmnJZ3Wm9d7qivNHm zIibkH4m3TSTgLtY6TXK8VtlYvm96ncdl5FGvbDTLQXo9iCclR5G6yn7Cz6LKy2LfIcp34O/ vHhOwArd0UazKYpSvLp5+6dblSSYTrKXL8qQmxcPPlajkJrO0tyBMKC87c3Z32wHvjcIjdJb ZHrxBpRX6p8QNVwDRTQxlT+HBtsfdERLD34aFpGIBatWsRVsOfeWwwk50WSnHIVJszre5gZU bSDa2YTdyyoBPtiV4HSM4gplErir6Ap7AcVyx5FhNN9jWk+PZzO3HjdQbkM3j4dRCGUD8N0x ggRSMIIETgIBATCBuzCBpjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBv cmF0aW9uMR8wHQYDVQQLExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJz b25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVh bCBTdWJzY3JpYmVyIENBIC0gRzQCEEVlgc9T9D6PvS4ymACFUlswCQYFKw4DAhoFAKCCAmsw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE2MTkxMDE3 WjAjBgkqhkiG9w0BCQQxFgQUATD+jnCL7S/C7TjkRCBwgdRI2GIwbAYJKoZIhvcNAQkPMV8w XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBzAYJKwYBBAGCNxAE MYG+MIG7MIGmMQswCQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24x HzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90 IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNj cmliZXIgQ0EgLSBHNAIQRWWBz1P0Po+9LjKYAIVSWzCBzgYLKoZIhvcNAQkQAgsxgb6ggbsw gaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UE CxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRh dGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD QSAtIEc0AhBFZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBAQUABIIBAJjPWiN4y79UWHdb Qa9HwaUeGnlBOuOJw6XPpGtwtRDti8jFY6ola1VVnYQ+e8+w7sfX81TYgsubKxSTxT5TLZlP jauBwJt6ZJGUMItX9UtOlCBh/xhCvkHmK3pK8hE/5GQhZiNHZEUOEX6LXqf9eN00VYkIWXAL 5ruWRoFT92GRPDMgM3T64TvdjvVPb41FWatnKcMXgg9I1wpBwYJm7YIUTYD5fP8cWkpxqwub oLeD0kx5kWMktC+8ZFcGpTxB9ums83+3ZYmfeTh6Sjtg//ZdOqsl1uBRaFsQupm8161KGt/W JBVnKb4xvXK+x/2gqQk2H0WkISV3a5g5atQfVWMAAAAAAAA= --------------ms070308030109040804030900-- --===============1694089591805376213== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1694089591805376213==-- From mirageos-devel-bounces@lists.xenproject.org Mon Dec 16 19:10:26 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 16 Dec 2013 19:10:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsdYd-0001Ux-Az; Mon, 16 Dec 2013 19:10:23 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsdYb-0001Us-MX for mirageos-devel@lists.xenproject.org; Mon, 16 Dec 2013 19:10:22 +0000 Received: from [193.109.254.147:62247] by server-10.bemta-14.messagelabs.com id 93/24-20752-D105FA25; Mon, 16 Dec 2013 19:10:21 +0000 X-Env-Sender: jamesjb@jamesjb.com X-Msg-Ref: server-6.tower-27.messagelabs.com!1387221018!5642119!1 X-Originating-IP: [173.230.155.117] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28110 invoked from network); 16 Dec 2013 19:10:19 -0000 Received: from coda.jamesjb.com (HELO coda.jamesjb.com) (173.230.155.117) by server-6.tower-27.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 16 Dec 2013 19:10:19 -0000 Received: from [192.168.40.164] (pdx.galois.com [66.162.129.26]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by coda.jamesjb.com (Postfix) with ESMTPSA id 00947C323 for ; Mon, 16 Dec 2013 11:10:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jamesjb.com; s=mail; t=1387221018; bh=IZgaeUVNR80b/Yu52/a+BO+hDJInFRgh5d88pJWPDDU=; h=Date:From:To:Subject:From; b=memwarITPwXAieCQ/iXlt8ukFocTR4eXdeBlV/nIIRD43cD1YCjXjBN7KUHGg3b1J D5VVNmSfTJPRupBTV8OmfCCASSIb64Xy2ez7iHTZTIur02UMnBwV6bCfLByFaXw4bv 0cNf8RVnKN/XGqDjG4LGNz2m2ycTBAMmfUBxSl0I= Message-ID: <52AF5019.8050105@jamesjb.com> Date: Mon, 16 Dec 2013 11:10:17 -0800 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org X-Enigmail-Version: 1.5.2 Subject: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1694089591805376213==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============1694089591805376213== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms070308030109040804030900" This is a cryptographically signed message in MIME format. --------------ms070308030109040804030900 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hi all, I'm using Mirage to build a Xen kernel, and would like to include a C library compiled against the Mirage runtime (along with OCaml stubs for i= t). My question is about the build process, especially when installing via OPAM. mirage-platform doesn't seem to install the headers for its dietlibc anywhere that a dependent project can find them. I could require a user to have a checkout of mirage-platform at hand to build, but that feels awkward when previously everything could be installed via OPAM except for the kernel itself (which builds with mirari= ). Does anyone have any recommendations about how to export build dependencies like header files (and also matching the CFLAGS/LDFLAGS used for the Mirage runtime would be nice to have as well). Thanks! James --------------ms070308030109040804030900 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSzCC BkIwggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0 aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJp bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIx MDgzMTIzNTk1OVowgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3Jh dGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29u YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg U3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn /R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEiVzAhJZCao/SsKsaIF4ZhchN2LuwDyyeb jyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+DeyxtmSSq5937hEH5u6P4wG/tgjT0hR I2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/xhR7DtryBeTTgwKmxWlwtKnk VunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28ODC7iCbDZ2ZmtLR3+cCh xw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQABo4ICRDCCAkAwOAYI KwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsG AQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRw Oi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXE Cl4aATCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsT MShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBD BgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaP wdqbiPKzbE0fWC+6AVFddMFG6MO4e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKM YJsrnGVJlMSiOCRIpVylUEto6WIip5PomSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBi Te/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP95WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26t lcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ 3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXidE0HbYQwggcBMIIF6aADAgECAhBF ZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UE ChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdv cmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMg Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzA3MjUwMDAwMDBa Fw0xNDA3MjYyMzU5NTlaMIHFMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0ZWQgLSAx Mzc0NzY5NTI5NzQ0MSIwIAYJKoZIhvcNAQkBFhNqYW1lc2piQGphbWVzamIuY29tMQ8wDQYD VQQLDAZTL01JTUUxHjAcBgNVBAsMFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEfMB0GA1UECwwW U3ltYW50ZWMgVHJ1c3QgTmV0d29yazEdMBsGA1UECgwUU3ltYW50ZWMgQ29ycG9yYXRpb24w ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCeYv0utKyX/A6tXdd9HE8cpVWbw5tq CfyEkqKDzIvDq9qmS1R9MpsIKphabrC8EtGLikEqaDcI67YbfvwNLXApUGfL5CzUNBz5j3SY 1uqgUeSV3+ShaFQ2SeLE+9WHvHAmJuHPnk6INaHhhUe+s4GduOGlD7juDc98VB5jwsw665oE QYrkadbQxfhMgOiHDtp+z3f8KafpRpgpY8QgIAhoXcMHycelPGcRFoAsDRN0dm9vG7i4IKaJ 5wi+zm8EegnWUyKYYHjx9s9wxtR+1byN9QF/gN9bf5ZQXTlBjZ6cjXXyWzBcNzYHwmRJfDPJ az+ybb5NJJIM8XobQT2CGFaBAgMBAAGjggMIMIIDBDAMBgNVHRMBAf8EAjAAMA4GA1UdDwEB /wQEAwIFoDAgBgNVHSUBAf8EFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwHQYDVR0OBBYEFHjg 3KlUkzacyiWvqJ5g0ZBF1clUMB4GA1UdEQQXMBWBE2phbWVzamJAamFtZXNqYi5jb20wHwYD VR0jBBgwFoAUrfnDk3IttbkoYeSk12DVxApeGgEwggErBggrBgEFBQcBAQSCAR0wggEZMIIB FQYIKwYBBQUHMAKGggEHbGRhcDovL2RpcmVjdG9yeS52ZXJpc2lnbi5jb20vQ04lMjAlM0Ql MjBTeW1hbnRlYyUyMENsYXNzJTIwMSUyMEluZGl2aWR1YWwlMjBTdWJzY3JpYmVyJTIwQ0El MjAtJTIwRzQlMkMlMjBPVSUyMCUzRCUyMFBlcnNvbmElMjBOb3QlMjBWYWxpZGF0ZWQlMkMl MjBPVSUyMCUzRCUyMFN5bWFudGVjJTIwVHJ1c3QlMjBOZXR3b3JrJTJDJTIwTyUyMCUzRCUy MFN5bWFudGVjJTIwQ29ycG9yYXRpb24lMkMlMjBDJTIwJTNEJTIwVVM/Y0FDZXJ0aWZpY2F0 ZTtiaW5hcnkwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL3BraS1jcmwuc3ltYXV0aC5jb20v Y2FfNTYxYzEwMzY5MGM5N2E2OTI0N2EwZWYwNzFhYzgxYWYvTGF0ZXN0Q1JMLmNybDBsBgNV HSAEZTBjMGEGC2CGSAGG+EUBBxcBMFIwJgYIKwYBBQUHAgEWGmh0dHA6Ly93d3cuc3ltYXV0 aC5jb20vY3BzMCgGCCsGAQUFBwICMBwaGmh0dHA6Ly93d3cuc3ltYXV0aC5jb20vcnBhMCsG CmCGSAGG+EUBEAMEHTAbBhJghkgBhvhFARABAgIEAYbHzm8WBTEwOTIyMDkGCmCGSAGG+EUB EAUEKzApAgEAFiRhSFIwY0hNNkx5OXdhMmt0Y21FdWMzbHRZWFYwYUM1amIyMD0wDQYJKoZI hvcNAQEFBQADggEBAHEzHvbp3O2aQGCu8zVjdo+AxkY0T0G1+YC4kMJVmnJZ3Wm9d7qivNHm zIibkH4m3TSTgLtY6TXK8VtlYvm96ncdl5FGvbDTLQXo9iCclR5G6yn7Cz6LKy2LfIcp34O/ vHhOwArd0UazKYpSvLp5+6dblSSYTrKXL8qQmxcPPlajkJrO0tyBMKC87c3Z32wHvjcIjdJb ZHrxBpRX6p8QNVwDRTQxlT+HBtsfdERLD34aFpGIBatWsRVsOfeWwwk50WSnHIVJszre5gZU bSDa2YTdyyoBPtiV4HSM4gplErir6Ap7AcVyx5FhNN9jWk+PZzO3HjdQbkM3j4dRCGUD8N0x ggRSMIIETgIBATCBuzCBpjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBv cmF0aW9uMR8wHQYDVQQLExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJz b25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVh bCBTdWJzY3JpYmVyIENBIC0gRzQCEEVlgc9T9D6PvS4ymACFUlswCQYFKw4DAhoFAKCCAmsw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE2MTkxMDE3 WjAjBgkqhkiG9w0BCQQxFgQUATD+jnCL7S/C7TjkRCBwgdRI2GIwbAYJKoZIhvcNAQkPMV8w XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBzAYJKwYBBAGCNxAE MYG+MIG7MIGmMQswCQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24x HzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90 IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNj cmliZXIgQ0EgLSBHNAIQRWWBz1P0Po+9LjKYAIVSWzCBzgYLKoZIhvcNAQkQAgsxgb6ggbsw gaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UE CxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRh dGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD QSAtIEc0AhBFZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBAQUABIIBAJjPWiN4y79UWHdb Qa9HwaUeGnlBOuOJw6XPpGtwtRDti8jFY6ola1VVnYQ+e8+w7sfX81TYgsubKxSTxT5TLZlP jauBwJt6ZJGUMItX9UtOlCBh/xhCvkHmK3pK8hE/5GQhZiNHZEUOEX6LXqf9eN00VYkIWXAL 5ruWRoFT92GRPDMgM3T64TvdjvVPb41FWatnKcMXgg9I1wpBwYJm7YIUTYD5fP8cWkpxqwub oLeD0kx5kWMktC+8ZFcGpTxB9ums83+3ZYmfeTh6Sjtg//ZdOqsl1uBRaFsQupm8161KGt/W JBVnKb4xvXK+x/2gqQk2H0WkISV3a5g5atQfVWMAAAAAAAA= --------------ms070308030109040804030900-- --===============1694089591805376213== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============1694089591805376213==-- From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 11:49:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 11:49:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vst96-0001gu-Qr; Tue, 17 Dec 2013 11:49:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vst94-0001fH-Rd; Tue, 17 Dec 2013 11:49:03 +0000 Received: from [193.109.254.147:29616] by server-12.bemta-14.messagelabs.com id 44/61-13681-E2A30B25; Tue, 17 Dec 2013 11:49:02 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1387280941!5786437!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=2.4 required=7.0 tests=RCVD_ILLEGAL_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9842 invoked from network); 17 Dec 2013 11:49:01 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Dec 2013 11:49:01 -0000 Received: by mail-wg0-f47.google.com with SMTP id n12so5791133wgh.2 for ; Tue, 17 Dec 2013 03:49:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=XDxH6RP4LerYX/NQCSmmM2TZbcIW2+mBi02OVpzZ+MM=; b=RdZN+2VW5tNQvbmtZUzsrlzote9HgwbTlf/7qaJZBV+YZrcbBrodjF7oOd47ZOe4yJ DbPsmdCG4/xCT/VmI4Ynrt5z/81k/TQY/YXc0D+TUaERs5++pwjmKT7NePuIjj9Qgjl3 KmBmMh+7pFiEIgEhxDNanZ+SCTSoWMCh4Bc5IPCB7tZXkM+iPbBrRftmwgieszAnN9Mh aikA/lo9gq/xeEzBEGdXFf4yjjtwuH+U8tlqk7jjVF17ke8a/yoKT5D1Io38ZVsKMJdl tHYGWJ3WTN1NBjmoJXYar66AWgkcbtS1sspxfsS86OVQO22M5fLc3H5VjgCeoSLDCAzW 2EMg== X-Received: by 10.194.237.99 with SMTP id vb3mr18930926wjc.28.1387280940992; Tue, 17 Dec 2013 03:49:00 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id q19sm34217028wiw.4.2013.12.17.03.48.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 03:49:00 -0800 (PST) Message-ID: <52B03A2A.807@xen.org> Date: Tue, 17 Dec 2013 11:48:58 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-users@lists.xen.org" Cc: "publicity@lists.xenproject.org" Subject: [MirageOS-devel] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, I was just informed by the FOSDEM organizers. I wanted to invite community members (as well as vendors who do open source stuff and didn't get a booth) to help man the booth, show demos, have your hand-outs/swag there, etc. If you are interested, please a) Sign up to http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity or send a mail to publicity-request@lists.xenproject.org with subscribe in the subject line, where we will be discussing details b) respond to this thread on what you may want to Best Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 11:49:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 11:49:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vst96-0001gu-Qr; Tue, 17 Dec 2013 11:49:04 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vst94-0001fH-Rd; Tue, 17 Dec 2013 11:49:03 +0000 Received: from [193.109.254.147:29616] by server-12.bemta-14.messagelabs.com id 44/61-13681-E2A30B25; Tue, 17 Dec 2013 11:49:02 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-9.tower-27.messagelabs.com!1387280941!5786437!1 X-Originating-IP: [74.125.82.47] X-SpamReason: No, hits=2.4 required=7.0 tests=RCVD_ILLEGAL_IP, SUSPICIOUS_RECIPS X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9842 invoked from network); 17 Dec 2013 11:49:01 -0000 Received: from mail-wg0-f47.google.com (HELO mail-wg0-f47.google.com) (74.125.82.47) by server-9.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 17 Dec 2013 11:49:01 -0000 Received: by mail-wg0-f47.google.com with SMTP id n12so5791133wgh.2 for ; Tue, 17 Dec 2013 03:49:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:content-type:content-transfer-encoding; bh=XDxH6RP4LerYX/NQCSmmM2TZbcIW2+mBi02OVpzZ+MM=; b=RdZN+2VW5tNQvbmtZUzsrlzote9HgwbTlf/7qaJZBV+YZrcbBrodjF7oOd47ZOe4yJ DbPsmdCG4/xCT/VmI4Ynrt5z/81k/TQY/YXc0D+TUaERs5++pwjmKT7NePuIjj9Qgjl3 KmBmMh+7pFiEIgEhxDNanZ+SCTSoWMCh4Bc5IPCB7tZXkM+iPbBrRftmwgieszAnN9Mh aikA/lo9gq/xeEzBEGdXFf4yjjtwuH+U8tlqk7jjVF17ke8a/yoKT5D1Io38ZVsKMJdl tHYGWJ3WTN1NBjmoJXYar66AWgkcbtS1sspxfsS86OVQO22M5fLc3H5VjgCeoSLDCAzW 2EMg== X-Received: by 10.194.237.99 with SMTP id vb3mr18930926wjc.28.1387280940992; Tue, 17 Dec 2013 03:49:00 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id q19sm34217028wiw.4.2013.12.17.03.48.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 03:49:00 -0800 (PST) Message-ID: <52B03A2A.807@xen.org> Date: Tue, 17 Dec 2013 11:48:58 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-users@lists.xen.org" Cc: "publicity@lists.xenproject.org" Subject: [MirageOS-devel] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, I was just informed by the FOSDEM organizers. I wanted to invite community members (as well as vendors who do open source stuff and didn't get a booth) to help man the booth, show demos, have your hand-outs/swag there, etc. If you are interested, please a) Sign up to http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity or send a mail to publicity-request@lists.xenproject.org with subscribe in the subject line, where we will be discussing details b) respond to this thread on what you may want to Best Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:08:09 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:08:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsy7p-0003K4-N8; Tue, 17 Dec 2013 17:08:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsy7o-0003Jz-Sa for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:08:05 +0000 Received: from [85.158.143.35:15659] by server-3.bemta-4.messagelabs.com id C6/40-32360-4F480B25; Tue, 17 Dec 2013 17:08:04 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1387300083!6516377!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21718 invoked from network); 17 Dec 2013 17:08:03 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Dec 2013 17:08:03 -0000 Received: by mail-wi0-f171.google.com with SMTP id bz8so4032880wib.4 for ; Tue, 17 Dec 2013 09:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=MZcCAZ1qt407PEucxBAt5/psn/peMnc7jbJRDw+iHUY=; b=Mi4djwQv+BZPUg/Lb4MJY+GZHH4es813jlFQA4T1ig9lEsCnfAXxx4yNUndMcNd8H2 oYQjVoaOw2Txxe3MYIJkPqKl8yO+ftr9aSShctF+s71VIrsOPpCZ/QNJCPiZwhKEPYcL 2KKavBV87vVnpH7OBU0l/4vldJ08ROLPgygDVzbP6pEyJvKVxZicqiWqxyzyuoHKCAG7 jU64KFUkIjg+PRR2pshtFYDvelD6KVhDWnuq8uSgWOxOxJvOQ0W0Lem6CamKxu1EhGOs odUV3tDMXRDrpdwL6kCMwTL2p/LcoWRHQxaEv7xWsh0iLTfy4K87mMI7xyXW9BP89yyN v/IQ== X-Received: by 10.180.79.67 with SMTP id h3mr4052791wix.58.1387300083197; Tue, 17 Dec 2013 09:08:03 -0800 (PST) Received: from [192.168.1.125] (m.cb1.com. [217.155.139.150]) by mx.google.com with ESMTPSA id md9sm8381584wic.1.2013.12.17.09.08.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 09:08:00 -0800 (PST) From: Thomas Gazagnaire Message-Id: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> Date: Tue, 17 Dec 2013 17:07:59 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] io-page X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I've been looking at the code of io-pages[1] and the mls and mlis look quite similar to me. Anyone has an objection if I refactor this into: a package "io-page": lib/io_page.ml lib/io_page.mli a package "io-page/unix": lib/stub_alloc_pages.c Dave, Ani, maybe you had any future plans for io-page that I should be aware of ? -- Thomas [1] https://github.com/mirage/io-page _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:08:09 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:08:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsy7p-0003K4-N8; Tue, 17 Dec 2013 17:08:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsy7o-0003Jz-Sa for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:08:05 +0000 Received: from [85.158.143.35:15659] by server-3.bemta-4.messagelabs.com id C6/40-32360-4F480B25; Tue, 17 Dec 2013 17:08:04 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-5.tower-21.messagelabs.com!1387300083!6516377!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 21718 invoked from network); 17 Dec 2013 17:08:03 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-5.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 17 Dec 2013 17:08:03 -0000 Received: by mail-wi0-f171.google.com with SMTP id bz8so4032880wib.4 for ; Tue, 17 Dec 2013 09:08:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=MZcCAZ1qt407PEucxBAt5/psn/peMnc7jbJRDw+iHUY=; b=Mi4djwQv+BZPUg/Lb4MJY+GZHH4es813jlFQA4T1ig9lEsCnfAXxx4yNUndMcNd8H2 oYQjVoaOw2Txxe3MYIJkPqKl8yO+ftr9aSShctF+s71VIrsOPpCZ/QNJCPiZwhKEPYcL 2KKavBV87vVnpH7OBU0l/4vldJ08ROLPgygDVzbP6pEyJvKVxZicqiWqxyzyuoHKCAG7 jU64KFUkIjg+PRR2pshtFYDvelD6KVhDWnuq8uSgWOxOxJvOQ0W0Lem6CamKxu1EhGOs odUV3tDMXRDrpdwL6kCMwTL2p/LcoWRHQxaEv7xWsh0iLTfy4K87mMI7xyXW9BP89yyN v/IQ== X-Received: by 10.180.79.67 with SMTP id h3mr4052791wix.58.1387300083197; Tue, 17 Dec 2013 09:08:03 -0800 (PST) Received: from [192.168.1.125] (m.cb1.com. [217.155.139.150]) by mx.google.com with ESMTPSA id md9sm8381584wic.1.2013.12.17.09.08.00 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 09:08:00 -0800 (PST) From: Thomas Gazagnaire Message-Id: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> Date: Tue, 17 Dec 2013 17:07:59 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] io-page X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I've been looking at the code of io-pages[1] and the mls and mlis look quite similar to me. Anyone has an objection if I refactor this into: a package "io-page": lib/io_page.ml lib/io_page.mli a package "io-page/unix": lib/stub_alloc_pages.c Dave, Ani, maybe you had any future plans for io-page that I should be aware of ? -- Thomas [1] https://github.com/mirage/io-page _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:23:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:23:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyMx-0004Lr-CE; Tue, 17 Dec 2013 17:23:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyIM-0003cT-Np for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:18:58 +0000 Received: from [85.158.139.211:56878] by server-12.bemta-5.messagelabs.com id FC/8D-30017-18780B25; Tue, 17 Dec 2013 17:18:57 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1387300735!5117777!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15509 invoked from network); 17 Dec 2013 17:18:57 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Dec 2013 17:18:57 -0000 X-IronPort-AV: E=Sophos;i="4.95,502,1384300800"; d="scan'208";a="83152566" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 17 Dec 2013 17:18:54 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 17 Dec 2013 12:18:54 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.38]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Tue, 17 Dec 2013 18:18:53 +0100 From: Dave Scott To: 'Thomas Gazagnaire' , "mirageos-devel@lists.xenproject.org" Thread-Topic: [MirageOS-devel] io-page Thread-Index: AQHO+0qXOziPNYZl50an6Js8FNc4S5pYoR3A Date: Tue, 17 Dec 2013 17:18:52 +0000 Message-ID: <6FB4516F0E9B0F43B54F88D855ABB790DA44E3@AMSPEX01CL03.citrite.net> References: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> In-Reply-To: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.57] MIME-Version: 1.0 X-DLP: MIA1 X-Mailman-Approved-At: Tue, 17 Dec 2013 17:23:41 +0000 Subject: Re: [MirageOS-devel] io-page X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Thomas, I have no cunning plan... feel free to refactor! Cheers, Dave > -----Original Message----- > From: mirageos-devel-bounces@lists.xenproject.org [mailto:mirageos- > devel-bounces@lists.xenproject.org] On Behalf Of Thomas Gazagnaire > Sent: 17 December 2013 5:08 PM > To: mirageos-devel@lists.xenproject.org > Subject: [MirageOS-devel] io-page > > Hi, > > I've been looking at the code of io-pages[1] and the mls and mlis look quite > similar to me. Anyone has an objection if I refactor this into: > > a package "io-page": > lib/io_page.ml > lib/io_page.mli > > a package "io-page/unix": > lib/stub_alloc_pages.c > > Dave, Ani, maybe you had any future plans for io-page that I should be > aware of ? > > -- > Thomas > > [1] https://github.com/mirage/io-page > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:23:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:23:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyMx-0004Lr-CE; Tue, 17 Dec 2013 17:23:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyIM-0003cT-Np for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:18:58 +0000 Received: from [85.158.139.211:56878] by server-12.bemta-5.messagelabs.com id FC/8D-30017-18780B25; Tue, 17 Dec 2013 17:18:57 +0000 X-Env-Sender: Dave.Scott@citrix.com X-Msg-Ref: server-8.tower-206.messagelabs.com!1387300735!5117777!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15509 invoked from network); 17 Dec 2013 17:18:57 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-8.tower-206.messagelabs.com with RC4-SHA encrypted SMTP; 17 Dec 2013 17:18:57 -0000 X-IronPort-AV: E=Sophos;i="4.95,502,1384300800"; d="scan'208";a="83152566" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 17 Dec 2013 17:18:54 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Tue, 17 Dec 2013 12:18:54 -0500 Received: from AMSPEX01CL03.citrite.net ([169.254.8.38]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Tue, 17 Dec 2013 18:18:53 +0100 From: Dave Scott To: 'Thomas Gazagnaire' , "mirageos-devel@lists.xenproject.org" Thread-Topic: [MirageOS-devel] io-page Thread-Index: AQHO+0qXOziPNYZl50an6Js8FNc4S5pYoR3A Date: Tue, 17 Dec 2013 17:18:52 +0000 Message-ID: <6FB4516F0E9B0F43B54F88D855ABB790DA44E3@AMSPEX01CL03.citrite.net> References: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> In-Reply-To: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.69.129.57] MIME-Version: 1.0 X-DLP: MIA1 X-Mailman-Approved-At: Tue, 17 Dec 2013 17:23:41 +0000 Subject: Re: [MirageOS-devel] io-page X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi Thomas, I have no cunning plan... feel free to refactor! Cheers, Dave > -----Original Message----- > From: mirageos-devel-bounces@lists.xenproject.org [mailto:mirageos- > devel-bounces@lists.xenproject.org] On Behalf Of Thomas Gazagnaire > Sent: 17 December 2013 5:08 PM > To: mirageos-devel@lists.xenproject.org > Subject: [MirageOS-devel] io-page > > Hi, > > I've been looking at the code of io-pages[1] and the mls and mlis look quite > similar to me. Anyone has an objection if I refactor this into: > > a package "io-page": > lib/io_page.ml > lib/io_page.mli > > a package "io-page/unix": > lib/stub_alloc_pages.c > > Dave, Ani, maybe you had any future plans for io-page that I should be > aware of ? > > -- > Thomas > > [1] https://github.com/mirage/io-page > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:25:28 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:25:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyOe-0004U5-IL; Tue, 17 Dec 2013 17:25:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyOc-0004U0-HR for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:25:26 +0000 Received: from [85.158.139.211:63294] by server-8.bemta-5.messagelabs.com id 4C/38-29838-50980B25; Tue, 17 Dec 2013 17:25:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1387301124!5149827!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23015 invoked from network); 17 Dec 2013 17:25:24 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-206.messagelabs.com with SMTP; 17 Dec 2013 17:25:24 -0000 Received: (qmail 3616 invoked by uid 634); 17 Dec 2013 17:25:24 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Dec 2013 17:25:23 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <52AF5019.8050105@jamesjb.com> Date: Tue, 17 Dec 2013 17:25:20 +0000 Message-Id: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> References: <52AF5019.8050105@jamesjb.com> To: James Bielman X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Adam Wick , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Dec 2013, at 19:10, James Bielman wrote: > Hi all, > > I'm using Mirage to build a Xen kernel, and would like to include a C > library compiled against the Mirage runtime (along with OCaml stubs for it). > > My question is about the build process, especially when installing via > OPAM. mirage-platform doesn't seem to install the headers for its > dietlibc anywhere that a dependent project can find them. > > I could require a user to have a checkout of mirage-platform at hand to > build, but that feels awkward when previously everything could be > installed via OPAM except for the kernel itself (which builds with mirari). > > Does anyone have any recommendations about how to export build > dependencies like header files (and also matching the CFLAGS/LDFLAGS > used for the Mirage runtime would be nice to have as well). Hi James, Good timing; you've hit on something I have active diffs for in my trees. The dietlibc headers aren't installed deliberately since the plan was always to use it for bootstrapping and not require the whole thing to be in the tree (hard to maintain). The only bits we really use now are the malloc memory management functions, and the printf calls. As part of Gabor Pali's work to port Mirage to a FreeBSD kernel module, he showed that the libkern present in FreeBSD gives us a pretty good printf implementation (caveat: no floating point printing). However, we do need a libc environment for SSL in the short term too, so we can't escape some build system refactoring. Does your C library have any special requirements beyond the functionality currently provides by dietlibc? Current solution: fork mirage-platform and add your library directly into the repository (there are several other stubs in kernel/ that use the OCaml headers, such as checksum_stubs.c). You can still distribute your fork via a custom OPAM remote that overrides mirage-platform-xen. Medium term solution: I'm splitting out the dietlibc dependency from the MiniOS kernel, and merging us back to the MiniOS version found in Xen upstream. I'd like to bolt on a libm and libc on top of this, but I need to investigate the latest in embedded cross-compilation, since this also needs to support ARM (and more experimentally, MIPS64) as well as x86. Anyone have any recommendations in this space? I'm CCing Adam Wick on this too, since he also has a libm extracted from OpenBSD. Sharing this sort of code between HalVM/Mirage will make longer term maintenance a lot easier, so I'm happy to adopt something if it can be easily split out of the HalVM tree. Alternative medium term solution: the ocamllabs/ocaml-ctypes library will get stub generation support shortly, which may make it easier to interface with the OCaml runtime. It can also talk over a shared memory channel, so C libraries could be treated as RPC servers. Luckily, most of this work can happen behind the scenes, as the OPAM package for mirage-xen can pull in the new dependencies without affecting existing code. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:25:28 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:25:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyOe-0004U5-IL; Tue, 17 Dec 2013 17:25:28 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyOc-0004U0-HR for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:25:26 +0000 Received: from [85.158.139.211:63294] by server-8.bemta-5.messagelabs.com id 4C/38-29838-50980B25; Tue, 17 Dec 2013 17:25:25 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1387301124!5149827!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 23015 invoked from network); 17 Dec 2013 17:25:24 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-206.messagelabs.com with SMTP; 17 Dec 2013 17:25:24 -0000 Received: (qmail 3616 invoked by uid 634); 17 Dec 2013 17:25:24 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Dec 2013 17:25:23 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <52AF5019.8050105@jamesjb.com> Date: Tue, 17 Dec 2013 17:25:20 +0000 Message-Id: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> References: <52AF5019.8050105@jamesjb.com> To: James Bielman X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Adam Wick , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 16 Dec 2013, at 19:10, James Bielman wrote: > Hi all, > > I'm using Mirage to build a Xen kernel, and would like to include a C > library compiled against the Mirage runtime (along with OCaml stubs for it). > > My question is about the build process, especially when installing via > OPAM. mirage-platform doesn't seem to install the headers for its > dietlibc anywhere that a dependent project can find them. > > I could require a user to have a checkout of mirage-platform at hand to > build, but that feels awkward when previously everything could be > installed via OPAM except for the kernel itself (which builds with mirari). > > Does anyone have any recommendations about how to export build > dependencies like header files (and also matching the CFLAGS/LDFLAGS > used for the Mirage runtime would be nice to have as well). Hi James, Good timing; you've hit on something I have active diffs for in my trees. The dietlibc headers aren't installed deliberately since the plan was always to use it for bootstrapping and not require the whole thing to be in the tree (hard to maintain). The only bits we really use now are the malloc memory management functions, and the printf calls. As part of Gabor Pali's work to port Mirage to a FreeBSD kernel module, he showed that the libkern present in FreeBSD gives us a pretty good printf implementation (caveat: no floating point printing). However, we do need a libc environment for SSL in the short term too, so we can't escape some build system refactoring. Does your C library have any special requirements beyond the functionality currently provides by dietlibc? Current solution: fork mirage-platform and add your library directly into the repository (there are several other stubs in kernel/ that use the OCaml headers, such as checksum_stubs.c). You can still distribute your fork via a custom OPAM remote that overrides mirage-platform-xen. Medium term solution: I'm splitting out the dietlibc dependency from the MiniOS kernel, and merging us back to the MiniOS version found in Xen upstream. I'd like to bolt on a libm and libc on top of this, but I need to investigate the latest in embedded cross-compilation, since this also needs to support ARM (and more experimentally, MIPS64) as well as x86. Anyone have any recommendations in this space? I'm CCing Adam Wick on this too, since he also has a libm extracted from OpenBSD. Sharing this sort of code between HalVM/Mirage will make longer term maintenance a lot easier, so I'm happy to adopt something if it can be easily split out of the HalVM tree. Alternative medium term solution: the ocamllabs/ocaml-ctypes library will get stub generation support shortly, which may make it easier to interface with the OCaml runtime. It can also talk over a shared memory channel, so C libraries could be treated as RPC servers. Luckily, most of this work can happen behind the scenes, as the OPAM package for mirage-xen can pull in the new dependencies without affecting existing code. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:29:22 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:29:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsySP-0004a6-Ub; Tue, 17 Dec 2013 17:29:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsySO-0004a1-DV for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:29:20 +0000 Received: from [85.158.139.211:22180] by server-7.bemta-5.messagelabs.com id 3C/43-04824-FE980B25; Tue, 17 Dec 2013 17:29:19 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1387301358!5116705!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22382 invoked from network); 17 Dec 2013 17:29:18 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 17 Dec 2013 17:29:18 -0000 Received: (qmail 8434 invoked by uid 634); 17 Dec 2013 17:29:18 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Dec 2013 17:29:17 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> Date: Tue, 17 Dec 2013 17:29:15 +0000 Message-Id: <5B1BFCD5-5A46-4945-8A2C-3A2B7A24A541@recoil.org> References: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] io-page X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 Dec 2013, at 17:07, Thomas Gazagnaire wrote: > Hi, > > I've been looking at the code of io-pages[1] and the mls and mlis look quite similar to me. Anyone has an objection if I refactor this into: > > a package "io-page": > lib/io_page.ml > lib/io_page.mli > > a package "io-page/unix": > lib/stub_alloc_pages.c > > Dave, Ani, maybe you had any future plans for io-page that I should be aware of ? I'm ok with this being merged, with a subpackage for io-page.unix that includes the C stubs. See my previous mail about the cross-compilation environment for Xen -- I think it's far easier to agree on an external symbol for IO page allocation, and ensure that all the backends supply that symbol at compile-time. Raphael: do you have a sense for whether we should use typed-arrays (or something from asm.js) for the io-page.js backend in JavaScript? Really just making sure that the interface won't be radically different from the existing Io_page API (which is essentially Bigarray). -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:29:22 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:29:22 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsySP-0004a6-Ub; Tue, 17 Dec 2013 17:29:21 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsySO-0004a1-DV for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:29:20 +0000 Received: from [85.158.139.211:22180] by server-7.bemta-5.messagelabs.com id 3C/43-04824-FE980B25; Tue, 17 Dec 2013 17:29:19 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1387301358!5116705!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 22382 invoked from network); 17 Dec 2013 17:29:18 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 17 Dec 2013 17:29:18 -0000 Received: (qmail 8434 invoked by uid 634); 17 Dec 2013 17:29:18 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Dec 2013 17:29:17 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> Date: Tue, 17 Dec 2013 17:29:15 +0000 Message-Id: <5B1BFCD5-5A46-4945-8A2C-3A2B7A24A541@recoil.org> References: <24638E00-F4B2-4400-90A2-CB771E62799D@gazagnaire.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] io-page X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17 Dec 2013, at 17:07, Thomas Gazagnaire wrote: > Hi, > > I've been looking at the code of io-pages[1] and the mls and mlis look quite similar to me. Anyone has an objection if I refactor this into: > > a package "io-page": > lib/io_page.ml > lib/io_page.mli > > a package "io-page/unix": > lib/stub_alloc_pages.c > > Dave, Ani, maybe you had any future plans for io-page that I should be aware of ? I'm ok with this being merged, with a subpackage for io-page.unix that includes the C stubs. See my previous mail about the cross-compilation environment for Xen -- I think it's far easier to agree on an external symbol for IO page allocation, and ensure that all the backends supply that symbol at compile-time. Raphael: do you have a sense for whether we should use typed-arrays (or something from asm.js) for the io-page.js backend in JavaScript? Really just making sure that the interface won't be radically different from the existing Io_page API (which is essentially Bigarray). -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:34:43 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:34:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyXa-0005Pn-5i; Tue, 17 Dec 2013 17:34:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyXZ-0005Pa-3M for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:34:41 +0000 Received: from [85.158.139.211:26005] by server-11.bemta-5.messagelabs.com id FF/04-23268-03B80B25; Tue, 17 Dec 2013 17:34:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1387301678!5118002!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14728 invoked from network); 17 Dec 2013 17:34:38 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 17 Dec 2013 17:34:38 -0000 Received: (qmail 11485 invoked by uid 634); 17 Dec 2013 17:34:37 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Dec 2013 17:34:37 +0000 From: Anil Madhavapeddy Message-Id: <08964E3D-6C1C-4EB4-A405-559EC6E0C576@recoil.org> Date: Tue, 17 Dec 2013 17:34:35 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] ANN: mirage-fs-unix-1.0.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Just uploaded mirage-fs-unix-1.0.0 to OPAM. This is a very trivial "pass through" filesystem that converts a root directory into a KV_RO store suitable for Unix use. When recompiled into (e.g.) Xen, the same interface will be a static crunch. It's going to be integrated into Mirage-1.0.3 shortly and used by default when using a KV_RO on Unix, which in turns makes the website a heck of a lot easier to work with. https://github.com/mirage/mirage-fs-unix https://github.com/ocaml/opam-repository/pull/1452 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:34:43 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:34:43 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyXa-0005Pn-5i; Tue, 17 Dec 2013 17:34:42 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VsyXZ-0005Pa-3M for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:34:41 +0000 Received: from [85.158.139.211:26005] by server-11.bemta-5.messagelabs.com id FF/04-23268-03B80B25; Tue, 17 Dec 2013 17:34:40 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-206.messagelabs.com!1387301678!5118002!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 14728 invoked from network); 17 Dec 2013 17:34:38 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-206.messagelabs.com with SMTP; 17 Dec 2013 17:34:38 -0000 Received: (qmail 11485 invoked by uid 634); 17 Dec 2013 17:34:37 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.94]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Tue, 17 Dec 2013 17:34:37 +0000 From: Anil Madhavapeddy Message-Id: <08964E3D-6C1C-4EB4-A405-559EC6E0C576@recoil.org> Date: Tue, 17 Dec 2013 17:34:35 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] ANN: mirage-fs-unix-1.0.0 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Just uploaded mirage-fs-unix-1.0.0 to OPAM. This is a very trivial "pass through" filesystem that converts a root directory into a KV_RO store suitable for Unix use. When recompiled into (e.g.) Xen, the same interface will be a static crunch. It's going to be integrated into Mirage-1.0.3 shortly and used by default when using a KV_RO on Unix, which in turns makes the website a heck of a lot easier to work with. https://github.com/mirage/mirage-fs-unix https://github.com/ocaml/opam-repository/pull/1452 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:52:45 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:52:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsyp1-0006R7-LF; Tue, 17 Dec 2013 17:52:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsyp0-0006R2-LM for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:52:43 +0000 Received: from [85.158.137.68:25323] by server-9.bemta-3.messagelabs.com id 68/42-13104-96F80B25; Tue, 17 Dec 2013 17:52:41 +0000 X-Env-Sender: jamesjb@jamesjb.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1387302759!4547994!1 X-Originating-IP: [173.230.155.117] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9232 invoked from network); 17 Dec 2013 17:52:40 -0000 Received: from coda.jamesjb.com (HELO coda.jamesjb.com) (173.230.155.117) by server-4.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Dec 2013 17:52:40 -0000 Received: from [192.168.40.164] (pdx.galois.com [66.162.129.26]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by coda.jamesjb.com (Postfix) with ESMTPSA id 56A5CC81D; Tue, 17 Dec 2013 09:52:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jamesjb.com; s=mail; t=1387302758; bh=pbGvEtWvOD7DScSTFOPr4evtDQ7v9n4ouDRUBG6Ue1Q=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=nAPVAMMkldSruovfk1rvgigwptlQBWL+XJw2VH9p8brq/UHaggbZtWUFJIYDQJk3f Y2eGP/8f0qfNsJkGQtCxEs2OfRrtT9su/Cd7zl7+nDxqT0dfw0VBOObZ7RGTbIGJ9j exCRfWY44FTbsbQkd7xCCwk7fXUkYKzghWS6zvAQ= Message-ID: <52B08F65.6010506@jamesjb.com> Date: Tue, 17 Dec 2013 09:52:37 -0800 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> X-Enigmail-Version: 1.5.2 Cc: Adam Wick , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2931793487053668504==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============2931793487053668504== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010507080804020504090001" This is a cryptographically signed message in MIME format. --------------ms010507080804020504090001 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > Current solution: fork mirage-platform and add your library directly in= to > the repository (there are several other stubs in kernel/ that use the O= Caml > headers, such as checksum_stubs.c). You can still distribute your fork= via > a custom OPAM remote that overrides mirage-platform-xen. Thanks, Anil. I will just include my dependencies in mirage-platform for the time being since I've already forked it as you described. I did have to add a few files from upstream dietlibc that I needed---I had to upgrade "stdint.h" as it was missing some definitions, and included the inet headers (to get some socket #define's and inet_nto*). > Medium term solution: I'm splitting out the dietlibc dependency from th= e > MiniOS kernel, and merging us back to the MiniOS version found in Xen > upstream. I'd like to bolt on a libm and libc on top of this, but I ne= ed > to investigate the latest in embedded cross-compilation, since this als= o > needs to support ARM (and more experimentally, MIPS64) as well as x86. > Anyone have any recommendations in this space? Putting my embedded systems developer hat on and throwing my "get-this-library-working-asap" role under the bus a bit, I think it'd be reasonable for Mirage to supply a pretty minimal libc if you're targeting an embedded environment, but it'd be nice to have a compatibility path for folks that need a richer set of libc functions. I'm still getting up to speed on all the Ocaml build tools, but it seems like the hurdle to getting embedded-style cross-compilation working is figuring out how to share toolchain configuration between ocamlfind, ocamlbuild, opam, mirari, and plain old Makefiles. Currently it's pretty easy to end up accidentally using the host compiler, libraries, et= c. Cheers, James --------------ms010507080804020504090001 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSzCC BkIwggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0 aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJp bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIx MDgzMTIzNTk1OVowgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3Jh dGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29u YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg U3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn /R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEiVzAhJZCao/SsKsaIF4ZhchN2LuwDyyeb jyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+DeyxtmSSq5937hEH5u6P4wG/tgjT0hR I2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/xhR7DtryBeTTgwKmxWlwtKnk VunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28ODC7iCbDZ2ZmtLR3+cCh xw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQABo4ICRDCCAkAwOAYI KwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsG AQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRw Oi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXE Cl4aATCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsT MShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBD BgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaP wdqbiPKzbE0fWC+6AVFddMFG6MO4e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKM YJsrnGVJlMSiOCRIpVylUEto6WIip5PomSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBi Te/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP95WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26t lcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ 3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXidE0HbYQwggcBMIIF6aADAgECAhBF ZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UE ChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdv cmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMg Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzA3MjUwMDAwMDBa Fw0xNDA3MjYyMzU5NTlaMIHFMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0ZWQgLSAx Mzc0NzY5NTI5NzQ0MSIwIAYJKoZIhvcNAQkBFhNqYW1lc2piQGphbWVzamIuY29tMQ8wDQYD VQQLDAZTL01JTUUxHjAcBgNVBAsMFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEfMB0GA1UECwwW U3ltYW50ZWMgVHJ1c3QgTmV0d29yazEdMBsGA1UECgwUU3ltYW50ZWMgQ29ycG9yYXRpb24w ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCeYv0utKyX/A6tXdd9HE8cpVWbw5tq CfyEkqKDzIvDq9qmS1R9MpsIKphabrC8EtGLikEqaDcI67YbfvwNLXApUGfL5CzUNBz5j3SY 1uqgUeSV3+ShaFQ2SeLE+9WHvHAmJuHPnk6INaHhhUe+s4GduOGlD7juDc98VB5jwsw665oE QYrkadbQxfhMgOiHDtp+z3f8KafpRpgpY8QgIAhoXcMHycelPGcRFoAsDRN0dm9vG7i4IKaJ 5wi+zm8EegnWUyKYYHjx9s9wxtR+1byN9QF/gN9bf5ZQXTlBjZ6cjXXyWzBcNzYHwmRJfDPJ az+ybb5NJJIM8XobQT2CGFaBAgMBAAGjggMIMIIDBDAMBgNVHRMBAf8EAjAAMA4GA1UdDwEB /wQEAwIFoDAgBgNVHSUBAf8EFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwHQYDVR0OBBYEFHjg 3KlUkzacyiWvqJ5g0ZBF1clUMB4GA1UdEQQXMBWBE2phbWVzamJAamFtZXNqYi5jb20wHwYD VR0jBBgwFoAUrfnDk3IttbkoYeSk12DVxApeGgEwggErBggrBgEFBQcBAQSCAR0wggEZMIIB FQYIKwYBBQUHMAKGggEHbGRhcDovL2RpcmVjdG9yeS52ZXJpc2lnbi5jb20vQ04lMjAlM0Ql MjBTeW1hbnRlYyUyMENsYXNzJTIwMSUyMEluZGl2aWR1YWwlMjBTdWJzY3JpYmVyJTIwQ0El MjAtJTIwRzQlMkMlMjBPVSUyMCUzRCUyMFBlcnNvbmElMjBOb3QlMjBWYWxpZGF0ZWQlMkMl MjBPVSUyMCUzRCUyMFN5bWFudGVjJTIwVHJ1c3QlMjBOZXR3b3JrJTJDJTIwTyUyMCUzRCUy MFN5bWFudGVjJTIwQ29ycG9yYXRpb24lMkMlMjBDJTIwJTNEJTIwVVM/Y0FDZXJ0aWZpY2F0 ZTtiaW5hcnkwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL3BraS1jcmwuc3ltYXV0aC5jb20v Y2FfNTYxYzEwMzY5MGM5N2E2OTI0N2EwZWYwNzFhYzgxYWYvTGF0ZXN0Q1JMLmNybDBsBgNV HSAEZTBjMGEGC2CGSAGG+EUBBxcBMFIwJgYIKwYBBQUHAgEWGmh0dHA6Ly93d3cuc3ltYXV0 aC5jb20vY3BzMCgGCCsGAQUFBwICMBwaGmh0dHA6Ly93d3cuc3ltYXV0aC5jb20vcnBhMCsG CmCGSAGG+EUBEAMEHTAbBhJghkgBhvhFARABAgIEAYbHzm8WBTEwOTIyMDkGCmCGSAGG+EUB EAUEKzApAgEAFiRhSFIwY0hNNkx5OXdhMmt0Y21FdWMzbHRZWFYwYUM1amIyMD0wDQYJKoZI hvcNAQEFBQADggEBAHEzHvbp3O2aQGCu8zVjdo+AxkY0T0G1+YC4kMJVmnJZ3Wm9d7qivNHm zIibkH4m3TSTgLtY6TXK8VtlYvm96ncdl5FGvbDTLQXo9iCclR5G6yn7Cz6LKy2LfIcp34O/ vHhOwArd0UazKYpSvLp5+6dblSSYTrKXL8qQmxcPPlajkJrO0tyBMKC87c3Z32wHvjcIjdJb ZHrxBpRX6p8QNVwDRTQxlT+HBtsfdERLD34aFpGIBatWsRVsOfeWwwk50WSnHIVJszre5gZU bSDa2YTdyyoBPtiV4HSM4gplErir6Ap7AcVyx5FhNN9jWk+PZzO3HjdQbkM3j4dRCGUD8N0x ggRSMIIETgIBATCBuzCBpjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBv cmF0aW9uMR8wHQYDVQQLExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJz b25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVh bCBTdWJzY3JpYmVyIENBIC0gRzQCEEVlgc9T9D6PvS4ymACFUlswCQYFKw4DAhoFAKCCAmsw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE3MTc1MjM3 WjAjBgkqhkiG9w0BCQQxFgQU4DaN1aELOyK7MyOMGHyH4aScpyswbAYJKoZIhvcNAQkPMV8w XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBzAYJKwYBBAGCNxAE MYG+MIG7MIGmMQswCQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24x HzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90 IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNj cmliZXIgQ0EgLSBHNAIQRWWBz1P0Po+9LjKYAIVSWzCBzgYLKoZIhvcNAQkQAgsxgb6ggbsw gaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UE CxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRh dGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD QSAtIEc0AhBFZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBAQUABIIBAGD0MT6ql4zRx+IT 07C4Ih6uXPcfniV4a4nsOHfO8sRdCQKrm59XZMe50GZ7gi2fIoUOtsAgM3fKlY/5BFSfhJfz nigLKp/ZNOCfTGio19lSE/BZ2bjxoYeRtqmXTlXbWm1cjNG05D5J0eC21YLGUpdAKb/Akxmd tIHCFhKX2thYe/3q7194FYJ7ls/uzRvg/xP/pV7XzryfyaalarVimsuSGwF+cryTefkLpZtY D1fonQDNgZ3ZJlRTE66hv6WGD/8u23ewuXqvHDMBuazOKQqSQTklJw3eg0zGivg9Y/V88ONg 7Ds6HU8HN1aMQt5RarwTSqwqy700uWPy/Mfje9cAAAAAAAA= --------------ms010507080804020504090001-- --===============2931793487053668504== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2931793487053668504==-- From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 17:52:45 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 17:52:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsyp1-0006R7-LF; Tue, 17 Dec 2013 17:52:43 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsyp0-0006R2-LM for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 17:52:43 +0000 Received: from [85.158.137.68:25323] by server-9.bemta-3.messagelabs.com id 68/42-13104-96F80B25; Tue, 17 Dec 2013 17:52:41 +0000 X-Env-Sender: jamesjb@jamesjb.com X-Msg-Ref: server-4.tower-31.messagelabs.com!1387302759!4547994!1 X-Originating-IP: [173.230.155.117] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 9232 invoked from network); 17 Dec 2013 17:52:40 -0000 Received: from coda.jamesjb.com (HELO coda.jamesjb.com) (173.230.155.117) by server-4.tower-31.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Dec 2013 17:52:40 -0000 Received: from [192.168.40.164] (pdx.galois.com [66.162.129.26]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by coda.jamesjb.com (Postfix) with ESMTPSA id 56A5CC81D; Tue, 17 Dec 2013 09:52:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jamesjb.com; s=mail; t=1387302758; bh=pbGvEtWvOD7DScSTFOPr4evtDQ7v9n4ouDRUBG6Ue1Q=; h=Date:From:To:CC:Subject:References:In-Reply-To:From; b=nAPVAMMkldSruovfk1rvgigwptlQBWL+XJw2VH9p8brq/UHaggbZtWUFJIYDQJk3f Y2eGP/8f0qfNsJkGQtCxEs2OfRrtT9su/Cd7zl7+nDxqT0dfw0VBOObZ7RGTbIGJ9j exCRfWY44FTbsbQkd7xCCwk7fXUkYKzghWS6zvAQ= Message-ID: <52B08F65.6010506@jamesjb.com> Date: Tue, 17 Dec 2013 09:52:37 -0800 From: James Bielman User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.0 MIME-Version: 1.0 To: Anil Madhavapeddy References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> X-Enigmail-Version: 1.5.2 Cc: Adam Wick , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2931793487053668504==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org This is a cryptographically signed message in MIME format. --===============2931793487053668504== Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="------------ms010507080804020504090001" This is a cryptographically signed message in MIME format. --------------ms010507080804020504090001 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable > Current solution: fork mirage-platform and add your library directly in= to > the repository (there are several other stubs in kernel/ that use the O= Caml > headers, such as checksum_stubs.c). You can still distribute your fork= via > a custom OPAM remote that overrides mirage-platform-xen. Thanks, Anil. I will just include my dependencies in mirage-platform for the time being since I've already forked it as you described. I did have to add a few files from upstream dietlibc that I needed---I had to upgrade "stdint.h" as it was missing some definitions, and included the inet headers (to get some socket #define's and inet_nto*). > Medium term solution: I'm splitting out the dietlibc dependency from th= e > MiniOS kernel, and merging us back to the MiniOS version found in Xen > upstream. I'd like to bolt on a libm and libc on top of this, but I ne= ed > to investigate the latest in embedded cross-compilation, since this als= o > needs to support ARM (and more experimentally, MIPS64) as well as x86. > Anyone have any recommendations in this space? Putting my embedded systems developer hat on and throwing my "get-this-library-working-asap" role under the bus a bit, I think it'd be reasonable for Mirage to supply a pretty minimal libc if you're targeting an embedded environment, but it'd be nice to have a compatibility path for folks that need a richer set of libc functions. I'm still getting up to speed on all the Ocaml build tools, but it seems like the hurdle to getting embedded-style cross-compilation working is figuring out how to share toolchain configuration between ocamlfind, ocamlbuild, opam, mirari, and plain old Makefiles. Currently it's pretty easy to end up accidentally using the host compiler, libraries, et= c. Cheers, James --------------ms010507080804020504090001 Content-Type: application/pkcs7-signature; name="smime.p7s" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIINSzCC BkIwggUqoAMCAQICEDirAC//rpa3Vv85Wvtd5xswDQYJKoZIhvcNAQEFBQAwgcoxCzAJBgNV BAYTAlVTMRcwFQYDVQQKEw5WZXJpU2lnbiwgSW5jLjEfMB0GA1UECxMWVmVyaVNpZ24gVHJ1 c3QgTmV0d29yazE6MDgGA1UECxMxKGMpIDE5OTkgVmVyaVNpZ24sIEluYy4gLSBGb3IgYXV0 aG9yaXplZCB1c2Ugb25seTFFMEMGA1UEAxM8VmVyaVNpZ24gQ2xhc3MgMSBQdWJsaWMgUHJp bWFyeSBDZXJ0aWZpY2F0aW9uIEF1dGhvcml0eSAtIEczMB4XDTExMDkwMTAwMDAwMFoXDTIx MDgzMTIzNTk1OVowgaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3Jh dGlvbjEfMB0GA1UECxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29u YSBOb3QgVmFsaWRhdGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwg U3Vic2NyaWJlciBDQSAtIEc0MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAxuwn /R1j9DsdisHTHMjIgoa2uEqGkqqBXHLKMA0vnkEiVzAhJZCao/SsKsaIF4ZhchN2LuwDyyeb jyCAN+DkitpVplAP/LlcI2mJQqG6H6/vDvmkyQrx+DeyxtmSSq5937hEH5u6P4wG/tgjT0hR I2pghKjuJy9g35byGiqMPI8AzE/L+iCOvDX24fCatgXz/B0/xhR7DtryBeTTgwKmxWlwtKnk VunbHVz0pjbia7UeKi3cvrvuOgSwMAitX2hsxr0GloiE5+apZC28ODC7iCbDZ2ZmtLR3+cCh xw5y72bi5bnK4POFdzWY3tQcsP5mceI4y258T0BV65fZqBge7QIDAQABo4ICRDCCAkAwOAYI KwYBBQUHAQEELDAqMCgGCCsGAQUFBzABhhxodHRwOi8vcGtpLW9jc3AudmVyaXNpZ24uY29t MBIGA1UdEwEB/wQIMAYBAf8CAQAwbAYDVR0gBGUwYzBhBgtghkgBhvhFAQcXATBSMCYGCCsG AQUFBwIBFhpodHRwOi8vd3d3LnN5bWF1dGguY29tL2NwczAoBggrBgEFBQcCAjAcGhpodHRw Oi8vd3d3LnN5bWF1dGguY29tL3JwYTA0BgNVHR8ELTArMCmgJ6AlhiNodHRwOi8vY3JsLnZl cmlzaWduLmNvbS9wY2ExLWczLmNybDAOBgNVHQ8BAf8EBAMCAQYwKQYDVR0RBCIwIKQeMBwx GjAYBgNVBAMTEVZlcmlTaWduTVBLSS0yLTk3MB0GA1UdDgQWBBSt+cOTci21uShh5KTXYNXE Cl4aATCB8QYDVR0jBIHpMIHmoYHQpIHNMIHKMQswCQYDVQQGEwJVUzEXMBUGA1UEChMOVmVy aVNpZ24sIEluYy4xHzAdBgNVBAsTFlZlcmlTaWduIFRydXN0IE5ldHdvcmsxOjA4BgNVBAsT MShjKSAxOTk5IFZlcmlTaWduLCBJbmMuIC0gRm9yIGF1dGhvcml6ZWQgdXNlIG9ubHkxRTBD BgNVBAMTPFZlcmlTaWduIENsYXNzIDEgUHVibGljIFByaW1hcnkgQ2VydGlmaWNhdGlvbiBB dXRob3JpdHkgLSBHM4IRAItbdVaEVIULAM+vOEjOsaQwDQYJKoZIhvcNAQEFBQADggEBANaP wdqbiPKzbE0fWC+6AVFddMFG6MO4e5/WQPHv/zK6iWvADjRDn6SZ5qTwXUgzYoWFYf4jiCKM YJsrnGVJlMSiOCRIpVylUEto6WIip5PomSJuPVu7EEIOH0x1RzRWCY/4vYw881y70pZwVHBi Te/REL6dSCxe7IZrB4LwPeElJygs4BZ2HrP95WKW0oo9Xyuu+1zCE7dlY8s0dkOf1oeZq26t lcEAP0Yngf813iMOQ9wUXzL5yinvwlIw9ZnduYH4OiUgjYJo8rkhhXRmBOGGORYy8i3WKqjJ 3tkAAk/jGCDFpYFWtpXe04Kt+HslvmR8LqC6cCz4+XXidE0HbYQwggcBMIIF6aADAgECAhBF ZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBBQUAMIGmMQswCQYDVQQGEwJVUzEdMBsGA1UE ChMUU3ltYW50ZWMgQ29ycG9yYXRpb24xHzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdv cmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMg Q2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNjcmliZXIgQ0EgLSBHNDAeFw0xMzA3MjUwMDAwMDBa Fw0xNDA3MjYyMzU5NTlaMIHFMS4wLAYDVQQDDCVQZXJzb25hIE5vdCBWYWxpZGF0ZWQgLSAx Mzc0NzY5NTI5NzQ0MSIwIAYJKoZIhvcNAQkBFhNqYW1lc2piQGphbWVzamIuY29tMQ8wDQYD VQQLDAZTL01JTUUxHjAcBgNVBAsMFVBlcnNvbmEgTm90IFZhbGlkYXRlZDEfMB0GA1UECwwW U3ltYW50ZWMgVHJ1c3QgTmV0d29yazEdMBsGA1UECgwUU3ltYW50ZWMgQ29ycG9yYXRpb24w ggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCeYv0utKyX/A6tXdd9HE8cpVWbw5tq CfyEkqKDzIvDq9qmS1R9MpsIKphabrC8EtGLikEqaDcI67YbfvwNLXApUGfL5CzUNBz5j3SY 1uqgUeSV3+ShaFQ2SeLE+9WHvHAmJuHPnk6INaHhhUe+s4GduOGlD7juDc98VB5jwsw665oE QYrkadbQxfhMgOiHDtp+z3f8KafpRpgpY8QgIAhoXcMHycelPGcRFoAsDRN0dm9vG7i4IKaJ 5wi+zm8EegnWUyKYYHjx9s9wxtR+1byN9QF/gN9bf5ZQXTlBjZ6cjXXyWzBcNzYHwmRJfDPJ az+ybb5NJJIM8XobQT2CGFaBAgMBAAGjggMIMIIDBDAMBgNVHRMBAf8EAjAAMA4GA1UdDwEB /wQEAwIFoDAgBgNVHSUBAf8EFjAUBggrBgEFBQcDBAYIKwYBBQUHAwIwHQYDVR0OBBYEFHjg 3KlUkzacyiWvqJ5g0ZBF1clUMB4GA1UdEQQXMBWBE2phbWVzamJAamFtZXNqYi5jb20wHwYD VR0jBBgwFoAUrfnDk3IttbkoYeSk12DVxApeGgEwggErBggrBgEFBQcBAQSCAR0wggEZMIIB FQYIKwYBBQUHMAKGggEHbGRhcDovL2RpcmVjdG9yeS52ZXJpc2lnbi5jb20vQ04lMjAlM0Ql MjBTeW1hbnRlYyUyMENsYXNzJTIwMSUyMEluZGl2aWR1YWwlMjBTdWJzY3JpYmVyJTIwQ0El MjAtJTIwRzQlMkMlMjBPVSUyMCUzRCUyMFBlcnNvbmElMjBOb3QlMjBWYWxpZGF0ZWQlMkMl MjBPVSUyMCUzRCUyMFN5bWFudGVjJTIwVHJ1c3QlMjBOZXR3b3JrJTJDJTIwTyUyMCUzRCUy MFN5bWFudGVjJTIwQ29ycG9yYXRpb24lMkMlMjBDJTIwJTNEJTIwVVM/Y0FDZXJ0aWZpY2F0 ZTtiaW5hcnkwXQYDVR0fBFYwVDBSoFCgToZMaHR0cDovL3BraS1jcmwuc3ltYXV0aC5jb20v Y2FfNTYxYzEwMzY5MGM5N2E2OTI0N2EwZWYwNzFhYzgxYWYvTGF0ZXN0Q1JMLmNybDBsBgNV HSAEZTBjMGEGC2CGSAGG+EUBBxcBMFIwJgYIKwYBBQUHAgEWGmh0dHA6Ly93d3cuc3ltYXV0 aC5jb20vY3BzMCgGCCsGAQUFBwICMBwaGmh0dHA6Ly93d3cuc3ltYXV0aC5jb20vcnBhMCsG CmCGSAGG+EUBEAMEHTAbBhJghkgBhvhFARABAgIEAYbHzm8WBTEwOTIyMDkGCmCGSAGG+EUB EAUEKzApAgEAFiRhSFIwY0hNNkx5OXdhMmt0Y21FdWMzbHRZWFYwYUM1amIyMD0wDQYJKoZI hvcNAQEFBQADggEBAHEzHvbp3O2aQGCu8zVjdo+AxkY0T0G1+YC4kMJVmnJZ3Wm9d7qivNHm zIibkH4m3TSTgLtY6TXK8VtlYvm96ncdl5FGvbDTLQXo9iCclR5G6yn7Cz6LKy2LfIcp34O/ vHhOwArd0UazKYpSvLp5+6dblSSYTrKXL8qQmxcPPlajkJrO0tyBMKC87c3Z32wHvjcIjdJb ZHrxBpRX6p8QNVwDRTQxlT+HBtsfdERLD34aFpGIBatWsRVsOfeWwwk50WSnHIVJszre5gZU bSDa2YTdyyoBPtiV4HSM4gplErir6Ap7AcVyx5FhNN9jWk+PZzO3HjdQbkM3j4dRCGUD8N0x ggRSMIIETgIBATCBuzCBpjELMAkGA1UEBhMCVVMxHTAbBgNVBAoTFFN5bWFudGVjIENvcnBv cmF0aW9uMR8wHQYDVQQLExZTeW1hbnRlYyBUcnVzdCBOZXR3b3JrMR4wHAYDVQQLExVQZXJz b25hIE5vdCBWYWxpZGF0ZWQxNzA1BgNVBAMTLlN5bWFudGVjIENsYXNzIDEgSW5kaXZpZHVh bCBTdWJzY3JpYmVyIENBIC0gRzQCEEVlgc9T9D6PvS4ymACFUlswCQYFKw4DAhoFAKCCAmsw GAYJKoZIhvcNAQkDMQsGCSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE3MTc1MjM3 WjAjBgkqhkiG9w0BCQQxFgQU4DaN1aELOyK7MyOMGHyH4aScpyswbAYJKoZIhvcNAQkPMV8w XTALBglghkgBZQMEASowCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDCBzAYJKwYBBAGCNxAE MYG+MIG7MIGmMQswCQYDVQQGEwJVUzEdMBsGA1UEChMUU3ltYW50ZWMgQ29ycG9yYXRpb24x HzAdBgNVBAsTFlN5bWFudGVjIFRydXN0IE5ldHdvcmsxHjAcBgNVBAsTFVBlcnNvbmEgTm90 IFZhbGlkYXRlZDE3MDUGA1UEAxMuU3ltYW50ZWMgQ2xhc3MgMSBJbmRpdmlkdWFsIFN1YnNj cmliZXIgQ0EgLSBHNAIQRWWBz1P0Po+9LjKYAIVSWzCBzgYLKoZIhvcNAQkQAgsxgb6ggbsw gaYxCzAJBgNVBAYTAlVTMR0wGwYDVQQKExRTeW1hbnRlYyBDb3Jwb3JhdGlvbjEfMB0GA1UE CxMWU3ltYW50ZWMgVHJ1c3QgTmV0d29yazEeMBwGA1UECxMVUGVyc29uYSBOb3QgVmFsaWRh dGVkMTcwNQYDVQQDEy5TeW1hbnRlYyBDbGFzcyAxIEluZGl2aWR1YWwgU3Vic2NyaWJlciBD QSAtIEc0AhBFZYHPU/Q+j70uMpgAhVJbMA0GCSqGSIb3DQEBAQUABIIBAGD0MT6ql4zRx+IT 07C4Ih6uXPcfniV4a4nsOHfO8sRdCQKrm59XZMe50GZ7gi2fIoUOtsAgM3fKlY/5BFSfhJfz nigLKp/ZNOCfTGio19lSE/BZ2bjxoYeRtqmXTlXbWm1cjNG05D5J0eC21YLGUpdAKb/Akxmd tIHCFhKX2thYe/3q7194FYJ7ls/uzRvg/xP/pV7XzryfyaalarVimsuSGwF+cryTefkLpZtY D1fonQDNgZ3ZJlRTE66hv6WGD/8u23ewuXqvHDMBuazOKQqSQTklJw3eg0zGivg9Y/V88ONg 7Ds6HU8HN1aMQt5RarwTSqwqy700uWPy/Mfje9cAAAAAAAA= --------------ms010507080804020504090001-- --===============2931793487053668504== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2931793487053668504==-- From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 21:17:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 21:17:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vt21K-0008K5-Nd; Tue, 17 Dec 2013 21:17:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vt21I-0008K0-N7 for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 21:17:36 +0000 Received: from [193.109.254.147:44260] by server-10.bemta-14.messagelabs.com id A8/8D-20752-07FB0B25; Tue, 17 Dec 2013 21:17:36 +0000 X-Env-Sender: pgj@login03.caesar.elte.hu X-Msg-Ref: server-7.tower-27.messagelabs.com!1387315054!5958480!1 X-Originating-IP: [157.181.1.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20311 invoked from network); 17 Dec 2013 21:17:35 -0000 Received: from mx3.mail.elte.hu (HELO mx3.mail.elte.hu) (157.181.1.138) by server-7.tower-27.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 17 Dec 2013 21:17:35 -0000 Received: from login03.caesar.elte.hu ([157.181.151.132]) by mx3.mail.elte.hu with esmtp (Exim) id 1Vt218-0002Os-PY from ; Tue, 17 Dec 2013 22:17:30 +0100 Received: (Authenticated sender: pgj) by login03.caesar.elte.hu with local (Exim 4.80) (envelope-from ) id 1Vt216-0000Eb-NY; Tue, 17 Dec 2013 22:17:24 +0100 Date: Tue, 17 Dec 2013 22:17:24 +0100 From: PALI Gabor Janos To: Anil Madhavapeddy Message-ID: <20131217211724.GA32562@caesar.elte.hu> References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 3.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00, T_RP_MATCHES_RCVD autolearn=no SpamAssassin version=3.3.2 -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: Adam Wick , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Tue, Dec 17, 2013 at 05:25:20PM +0000, Anil Madhavapeddy wrote: > As part of Gabor Pali's work to port Mirage to a > FreeBSD kernel module, he showed that the libkern present in FreeBSD gives > us a pretty good printf implementation (caveat: no floating point printing). Actually, there is support for printing floating-point values in the referenced kernel module backend. I used fixed-point "floats" that may be rendered as a string, thus the floating-point format specifiers will work with them. This is done in the adapted OCaml run-time [1] which is then passed to the kernel's printf() function as a string [2], so it does not expect from kernel library to format any string. [1] https://github.com/pgj/mirage-platform/blob/master/kfreebsd/runtime/ocaml/floats.c#L160 [2] https://github.com/pgj/mirage-platform/blob/master/kfreebsd/runtime/ocaml/io.c#L196 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 17 21:17:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 17 Dec 2013 21:17:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vt21K-0008K5-Nd; Tue, 17 Dec 2013 21:17:38 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vt21I-0008K0-N7 for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 21:17:36 +0000 Received: from [193.109.254.147:44260] by server-10.bemta-14.messagelabs.com id A8/8D-20752-07FB0B25; Tue, 17 Dec 2013 21:17:36 +0000 X-Env-Sender: pgj@login03.caesar.elte.hu X-Msg-Ref: server-7.tower-27.messagelabs.com!1387315054!5958480!1 X-Originating-IP: [157.181.1.138] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20311 invoked from network); 17 Dec 2013 21:17:35 -0000 Received: from mx3.mail.elte.hu (HELO mx3.mail.elte.hu) (157.181.1.138) by server-7.tower-27.messagelabs.com with DHE-RSA-AES128-SHA encrypted SMTP; 17 Dec 2013 21:17:35 -0000 Received: from login03.caesar.elte.hu ([157.181.151.132]) by mx3.mail.elte.hu with esmtp (Exim) id 1Vt218-0002Os-PY from ; Tue, 17 Dec 2013 22:17:30 +0100 Received: (Authenticated sender: pgj) by login03.caesar.elte.hu with local (Exim 4.80) (envelope-from ) id 1Vt216-0000Eb-NY; Tue, 17 Dec 2013 22:17:24 +0100 Date: Tue, 17 Dec 2013 22:17:24 +0100 From: PALI Gabor Janos To: Anil Madhavapeddy Message-ID: <20131217211724.GA32562@caesar.elte.hu> References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> User-Agent: Mutt/1.5.21 (2010-09-15) X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 3.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00, T_RP_MATCHES_RCVD autolearn=no SpamAssassin version=3.3.2 -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -2.0 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] Cc: Adam Wick , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Tue, Dec 17, 2013 at 05:25:20PM +0000, Anil Madhavapeddy wrote: > As part of Gabor Pali's work to port Mirage to a > FreeBSD kernel module, he showed that the libkern present in FreeBSD gives > us a pretty good printf implementation (caveat: no floating point printing). Actually, there is support for printing floating-point values in the referenced kernel module backend. I used fixed-point "floats" that may be rendered as a string, thus the floating-point format specifiers will work with them. This is done in the adapted OCaml run-time [1] which is then passed to the kernel's printf() function as a string [2], so it does not expect from kernel library to format any string. [1] https://github.com/pgj/mirage-platform/blob/master/kfreebsd/runtime/ocaml/floats.c#L160 [2] https://github.com/pgj/mirage-platform/blob/master/kfreebsd/runtime/ocaml/io.c#L196 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 10:12:19 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 10:12:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtE6y-0004vu-N4; Wed, 18 Dec 2013 10:12:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsz1L-0007Xz-17 for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 18:05:27 +0000 Received: from [85.158.139.211:13687] by server-2.bemta-5.messagelabs.com id 5A/D9-29392-66290B25; Tue, 17 Dec 2013 18:05:26 +0000 X-Env-Sender: awick@galois.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1387303523!5154633!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30577 invoked from network); 17 Dec 2013 18:05:24 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Dec 2013 18:05:24 -0000 Received: from hurricane.galois.com (hurricane.galois.com [66.193.37.211]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id rBHI5KS0014008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 17 Dec 2013 10:05:20 -0800 Received: from [IPv6:::1] (c-71-193-160-194.hsd1.or.comcast.net [71.193.160.194]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id rBHI5H1r021156 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 17 Dec 2013 10:05:19 -0800 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) From: Adam Wick In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> Date: Tue, 17 Dec 2013 13:05:15 -0500 Message-Id: <57CF88C0-6492-443A-89E2-25824228B660@galois.com> References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1822) X-Spam-Status: No, score=-1.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com X-Mailman-Approved-At: Wed, 18 Dec 2013 10:12:15 +0000 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7034436780809870211==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7034436780809870211== Content-Type: multipart/signed; boundary="Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C"; protocol="application/pkcs7-signature"; micalg=sha1 --Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 17, 2013, at 12:25 PM, Anil Madhavapeddy wrote: > On 1I'm CCing Adam Wick on this too, since he also has a libm = extracted from > OpenBSD. Sharing this sort of code between HalVM/Mirage will make = longer > term maintenance a lot easier, so I'm happy to adopt something if it = can > be easily split out of the HalVM tree. They=92re a lot easier to pull out in the HaLVM 2.0 work, as they=92re = basically in their own subtrees. Unfortunately, libc and libm are in two = different repositories for, um, not-great-yet-annoyingly-important = reasons: https://github.com/GaloisInc/HaLVM/tree/master/src/libm [src/libm from = the HaLVM tree] https://github.com/GaloisInc/halvm-ghc/tree/halvm/rts/minlibc = [rts/minlibc from the halvm branch of halvm-ghc] The libc stuff is fairly recent, but definitely not optimized. The libm = work is circa ~2007. I think it specializes for x86_32. I=92ve been = meaning to go back and add more optimal implementations for x86_64 and = ARM, but haven=92t gotten to it yet. This is definitely something we = could share and help each other out with, though. Combining the two may = also bear fruit in interesting ways. If I pulled the libc and libm code from the HaLVM out and made a = =93minlib=94 git tree, would that be something you=92d be willing to = start using? I haven=92t pulled it out yet because I wasn=92t sure = there=92d be payoff against the added git submodule pain, but if there=92s= a clear user I=92ll make it happen. - Adam= --Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFIDCCBRww ggQEoAMCAQICARYwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAk9SMREw DwYDVQQHEwhQb3J0bGFuZDEVMBMGA1UEChMMR2Fsb2lzLCBJbmMuMRgwFgYDVQQDEw9HYWxvaXMs IEluYy4gQ0ExHTAbBgkqhkiG9w0BCQEWDnBraUBnYWxvaXMuY29tMB4XDTA4MDYxMzE4MjEzNVoX DTE4MDYxMTE4MjEzNVowgYAxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJPUjERMA8GA1UEBxMIUG9y dGxhbmQxFTATBgNVBAoTDEdhbG9pcywgSW5jLjEZMBcGA1UEAxQQYXdpY2tAZ2Fsb2lzLmNvbTEf MB0GCSqGSIb3DQEJARYQYXdpY2tAZ2Fsb2lzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAL4YM1aIa0Sz7DUZf/euqBSWI02tSDFNgIbIv8Sl82cfjr4P2yNku5hwl5A4jHrSD30Z BIlZoAz0t5G+Ya40a39adbbWGwBhDfsu5kVPFm7ltHCpzqk7xO+xBWDUB43uF90tybqlvAWmODDD CixVdZSu9Efq1afOGl0xcyAZIooornUgW6rNO4LADqLJFxiDjcJQBviwrVBVVm9TA4SuP24AozC+ pizNyO9+8tfppMxZiW47tJmUi/3Cbk6Jl2v/0evxmrGs03cA+rXxh2V4cK+7YeQqv0pD0WOc2TeF GbtxEDVLpPhrMw6QlbLEPyA2m/0Gbazhqoq9qHIWPSJqoF0CAwEAAaOCAaEwggGdMAkGA1UdEwQC MAAwCwYDVR0PBAQDAgTwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDARBglghkgBhvhC AQEEBAMCBaAwMAYJYIZIAYb4QgENBCMWIUdhbG9pcywgSW5jLiBFbXBsb3llZSBDZXJ0aWZpY2F0 ZTAdBgNVHQ4EFgQUBU8DOIQjTwVzTxB1lxSebo9oHgIwgbAGA1UdIwSBqDCBpYAUJgbWcbk3f/kF RBqdm7fBoNWiz0yhgYGkfzB9MQswCQYDVQQGEwJVUzELMAkGA1UECBMCT1IxETAPBgNVBAcTCFBv cnRsYW5kMRUwEwYDVQQKEwxHYWxvaXMsIEluYy4xGDAWBgNVBAMTD0dhbG9pcywgSW5jLiBDQTEd MBsGCSqGSIb3DQEJARYOcGtpQGdhbG9pcy5jb22CCQDxc4pNMpbRXDAxBgNVHR8EKjAoMCagJKAi hiBodHRwOi8vd3d3LmdhbG9pcy5jb20vY2EvY3JsLnBlbTAaBgNVHR4EEzARoA8wDYELLmdhbG9p cy5jb20wDQYJKoZIhvcNAQEFBQADggEBAJWsI/KvtIz3eQoyeHSnCK+fGb1kp/wiWH1xk4TyCoDa 620zSeJa5KPlE057l7WDrU5hKTKau1z6cjkL6P297bzVhcsV9etHH/iO7wOX1jkgG5e6eyzBSUGD NRHV78tQIrBFGK9RlyAjyr5rSWvZQGwl9cq2QRZtHQwiKypxsxBNuei1F7KyKv3yIoDvwaNS3Nh6 +AHLV80FamlMFlhz1dIA0LdwnOlReCcdg6xo797XJ3G7TXDZRI/GclI+CDrDsWDdmD/qQRinG4CK xn5adMjUc0RGR4j6BB0EHB4I6ZoDtzNNSuHhlgZjLR4xcoh6DxA/oaZ78wLOSTPYsXSy67UxggM5 MIIDNQIBATCBgjB9MQswCQYDVQQGEwJVUzELMAkGA1UECBMCT1IxETAPBgNVBAcTCFBvcnRsYW5k MRUwEwYDVQQKEwxHYWxvaXMsIEluYy4xGDAWBgNVBAMTD0dhbG9pcywgSW5jLiBDQTEdMBsGCSqG SIb3DQEJARYOcGtpQGdhbG9pcy5jb20CARYwCQYFKw4DAhoFAKCCAYswGAYJKoZIhvcNAQkDMQsG CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE3MTgwNTE2WjAjBgkqhkiG9w0BCQQxFgQU qOyjDtOCKOUkR/P+4NfexRzLa7AwgZMGCSsGAQQBgjcQBDGBhTCBgjB9MQswCQYDVQQGEwJVUzEL MAkGA1UECBMCT1IxETAPBgNVBAcTCFBvcnRsYW5kMRUwEwYDVQQKEwxHYWxvaXMsIEluYy4xGDAW BgNVBAMTD0dhbG9pcywgSW5jLiBDQTEdMBsGCSqGSIb3DQEJARYOcGtpQGdhbG9pcy5jb20CARYw gZUGCyqGSIb3DQEJEAILMYGFoIGCMH0xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJPUjERMA8GA1UE BxMIUG9ydGxhbmQxFTATBgNVBAoTDEdhbG9pcywgSW5jLjEYMBYGA1UEAxMPR2Fsb2lzLCBJbmMu IENBMR0wGwYJKoZIhvcNAQkBFg5wa2lAZ2Fsb2lzLmNvbQIBFjANBgkqhkiG9w0BAQEFAASCAQBc XjzWZw5IvQmpnk1+uNaJDfV/JVx5/OikGkvc+V+0ps03b6lX0PP/U4DUshMv516SmflMY6RF4B4B 2/N4rlNjcfLnIUnn1VywERUHjOhETjvzqIUxxKaO9qhKu1+OHex9q7NWB9DiUDNGnW55aihD+fdr VXZHOlPPMtZtlBBTVZ1PsCuMwzpxDEft3dfhYxg0iXAejrast88o1MmoS0WRY6SoHNGnXXpzaS66 6aGDuD4NBwSsMd+3gtqRVzSxFAkIMl5BhzfVA3rnXIR49nr8R7kgtIP9ZCZVTMcDPwd+1zu7Zpe4 xC7kMjuv+cDzx/zgXsDAmKsoFWa0ewAVxc9lAAAAAAAA --Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C-- --===============7034436780809870211== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7034436780809870211==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 10:12:19 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 10:12:19 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtE6y-0004vu-N4; Wed, 18 Dec 2013 10:12:16 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vsz1L-0007Xz-17 for mirageos-devel@lists.xenproject.org; Tue, 17 Dec 2013 18:05:27 +0000 Received: from [85.158.139.211:13687] by server-2.bemta-5.messagelabs.com id 5A/D9-29392-66290B25; Tue, 17 Dec 2013 18:05:26 +0000 X-Env-Sender: awick@galois.com X-Msg-Ref: server-15.tower-206.messagelabs.com!1387303523!5154633!1 X-Originating-IP: [66.193.37.198] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30577 invoked from network); 17 Dec 2013 18:05:24 -0000 Received: from quintic.galois.com (HELO mail.galois.com) (66.193.37.198) by server-15.tower-206.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 17 Dec 2013 18:05:24 -0000 Received: from hurricane.galois.com (hurricane.galois.com [66.193.37.211]) by mail.galois.com (8.14.4/8.14.4) with ESMTP id rBHI5KS0014008 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Tue, 17 Dec 2013 10:05:20 -0800 Received: from [IPv6:::1] (c-71-193-160-194.hsd1.or.comcast.net [71.193.160.194]) (authenticated bits=0) by hurricane.galois.com (8.14.4/8.14.4) with ESMTP id rBHI5H1r021156 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Tue, 17 Dec 2013 10:05:19 -0800 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) From: Adam Wick In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> Date: Tue, 17 Dec 2013 13:05:15 -0500 Message-Id: <57CF88C0-6492-443A-89E2-25824228B660@galois.com> References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> To: Anil Madhavapeddy X-Mailer: Apple Mail (2.1822) X-Spam-Status: No, score=-1.0 required=4.5 tests=BAYES_00,RP_MATCHES_RCVD shortcircuit=no autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on quintic.galois.com X-Mailman-Approved-At: Wed, 18 Dec 2013 10:12:15 +0000 Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7034436780809870211==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7034436780809870211== Content-Type: multipart/signed; boundary="Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C"; protocol="application/pkcs7-signature"; micalg=sha1 --Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 On Dec 17, 2013, at 12:25 PM, Anil Madhavapeddy wrote: > On 1I'm CCing Adam Wick on this too, since he also has a libm = extracted from > OpenBSD. Sharing this sort of code between HalVM/Mirage will make = longer > term maintenance a lot easier, so I'm happy to adopt something if it = can > be easily split out of the HalVM tree. They=92re a lot easier to pull out in the HaLVM 2.0 work, as they=92re = basically in their own subtrees. Unfortunately, libc and libm are in two = different repositories for, um, not-great-yet-annoyingly-important = reasons: https://github.com/GaloisInc/HaLVM/tree/master/src/libm [src/libm from = the HaLVM tree] https://github.com/GaloisInc/halvm-ghc/tree/halvm/rts/minlibc = [rts/minlibc from the halvm branch of halvm-ghc] The libc stuff is fairly recent, but definitely not optimized. The libm = work is circa ~2007. I think it specializes for x86_32. I=92ve been = meaning to go back and add more optimal implementations for x86_64 and = ARM, but haven=92t gotten to it yet. This is definitely something we = could share and help each other out with, though. Combining the two may = also bear fruit in interesting ways. If I pulled the libc and libm code from the HaLVM out and made a = =93minlib=94 git tree, would that be something you=92d be willing to = start using? I haven=92t pulled it out yet because I wasn=92t sure = there=92d be payoff against the added git submodule pain, but if there=92s= a clear user I=92ll make it happen. - Adam= --Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIFIDCCBRww ggQEoAMCAQICARYwDQYJKoZIhvcNAQEFBQAwfTELMAkGA1UEBhMCVVMxCzAJBgNVBAgTAk9SMREw DwYDVQQHEwhQb3J0bGFuZDEVMBMGA1UEChMMR2Fsb2lzLCBJbmMuMRgwFgYDVQQDEw9HYWxvaXMs IEluYy4gQ0ExHTAbBgkqhkiG9w0BCQEWDnBraUBnYWxvaXMuY29tMB4XDTA4MDYxMzE4MjEzNVoX DTE4MDYxMTE4MjEzNVowgYAxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJPUjERMA8GA1UEBxMIUG9y dGxhbmQxFTATBgNVBAoTDEdhbG9pcywgSW5jLjEZMBcGA1UEAxQQYXdpY2tAZ2Fsb2lzLmNvbTEf MB0GCSqGSIb3DQEJARYQYXdpY2tAZ2Fsb2lzLmNvbTCCASIwDQYJKoZIhvcNAQEBBQADggEPADCC AQoCggEBAL4YM1aIa0Sz7DUZf/euqBSWI02tSDFNgIbIv8Sl82cfjr4P2yNku5hwl5A4jHrSD30Z BIlZoAz0t5G+Ya40a39adbbWGwBhDfsu5kVPFm7ltHCpzqk7xO+xBWDUB43uF90tybqlvAWmODDD CixVdZSu9Efq1afOGl0xcyAZIooornUgW6rNO4LADqLJFxiDjcJQBviwrVBVVm9TA4SuP24AozC+ pizNyO9+8tfppMxZiW47tJmUi/3Cbk6Jl2v/0evxmrGs03cA+rXxh2V4cK+7YeQqv0pD0WOc2TeF GbtxEDVLpPhrMw6QlbLEPyA2m/0Gbazhqoq9qHIWPSJqoF0CAwEAAaOCAaEwggGdMAkGA1UdEwQC MAAwCwYDVR0PBAQDAgTwMB0GA1UdJQQWMBQGCCsGAQUFBwMCBggrBgEFBQcDBDARBglghkgBhvhC AQEEBAMCBaAwMAYJYIZIAYb4QgENBCMWIUdhbG9pcywgSW5jLiBFbXBsb3llZSBDZXJ0aWZpY2F0 ZTAdBgNVHQ4EFgQUBU8DOIQjTwVzTxB1lxSebo9oHgIwgbAGA1UdIwSBqDCBpYAUJgbWcbk3f/kF RBqdm7fBoNWiz0yhgYGkfzB9MQswCQYDVQQGEwJVUzELMAkGA1UECBMCT1IxETAPBgNVBAcTCFBv cnRsYW5kMRUwEwYDVQQKEwxHYWxvaXMsIEluYy4xGDAWBgNVBAMTD0dhbG9pcywgSW5jLiBDQTEd MBsGCSqGSIb3DQEJARYOcGtpQGdhbG9pcy5jb22CCQDxc4pNMpbRXDAxBgNVHR8EKjAoMCagJKAi hiBodHRwOi8vd3d3LmdhbG9pcy5jb20vY2EvY3JsLnBlbTAaBgNVHR4EEzARoA8wDYELLmdhbG9p cy5jb20wDQYJKoZIhvcNAQEFBQADggEBAJWsI/KvtIz3eQoyeHSnCK+fGb1kp/wiWH1xk4TyCoDa 620zSeJa5KPlE057l7WDrU5hKTKau1z6cjkL6P297bzVhcsV9etHH/iO7wOX1jkgG5e6eyzBSUGD NRHV78tQIrBFGK9RlyAjyr5rSWvZQGwl9cq2QRZtHQwiKypxsxBNuei1F7KyKv3yIoDvwaNS3Nh6 +AHLV80FamlMFlhz1dIA0LdwnOlReCcdg6xo797XJ3G7TXDZRI/GclI+CDrDsWDdmD/qQRinG4CK xn5adMjUc0RGR4j6BB0EHB4I6ZoDtzNNSuHhlgZjLR4xcoh6DxA/oaZ78wLOSTPYsXSy67UxggM5 MIIDNQIBATCBgjB9MQswCQYDVQQGEwJVUzELMAkGA1UECBMCT1IxETAPBgNVBAcTCFBvcnRsYW5k MRUwEwYDVQQKEwxHYWxvaXMsIEluYy4xGDAWBgNVBAMTD0dhbG9pcywgSW5jLiBDQTEdMBsGCSqG SIb3DQEJARYOcGtpQGdhbG9pcy5jb20CARYwCQYFKw4DAhoFAKCCAYswGAYJKoZIhvcNAQkDMQsG CSqGSIb3DQEHATAcBgkqhkiG9w0BCQUxDxcNMTMxMjE3MTgwNTE2WjAjBgkqhkiG9w0BCQQxFgQU qOyjDtOCKOUkR/P+4NfexRzLa7AwgZMGCSsGAQQBgjcQBDGBhTCBgjB9MQswCQYDVQQGEwJVUzEL MAkGA1UECBMCT1IxETAPBgNVBAcTCFBvcnRsYW5kMRUwEwYDVQQKEwxHYWxvaXMsIEluYy4xGDAW BgNVBAMTD0dhbG9pcywgSW5jLiBDQTEdMBsGCSqGSIb3DQEJARYOcGtpQGdhbG9pcy5jb20CARYw gZUGCyqGSIb3DQEJEAILMYGFoIGCMH0xCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJPUjERMA8GA1UE BxMIUG9ydGxhbmQxFTATBgNVBAoTDEdhbG9pcywgSW5jLjEYMBYGA1UEAxMPR2Fsb2lzLCBJbmMu IENBMR0wGwYJKoZIhvcNAQkBFg5wa2lAZ2Fsb2lzLmNvbQIBFjANBgkqhkiG9w0BAQEFAASCAQBc XjzWZw5IvQmpnk1+uNaJDfV/JVx5/OikGkvc+V+0ps03b6lX0PP/U4DUshMv516SmflMY6RF4B4B 2/N4rlNjcfLnIUnn1VywERUHjOhETjvzqIUxxKaO9qhKu1+OHex9q7NWB9DiUDNGnW55aihD+fdr VXZHOlPPMtZtlBBTVZ1PsCuMwzpxDEft3dfhYxg0iXAejrast88o1MmoS0WRY6SoHNGnXXpzaS66 6aGDuD4NBwSsMd+3gtqRVzSxFAkIMl5BhzfVA3rnXIR49nr8R7kgtIP9ZCZVTMcDPwd+1zu7Zpe4 xC7kMjuv+cDzx/zgXsDAmKsoFWa0ewAVxc9lAAAAAAAA --Apple-Mail=_729DCD53-79DD-49C4-B1F1-1C70A6498A2C-- --===============7034436780809870211== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7034436780809870211==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 10:21:34 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 10:21:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtEFy-0005NG-16; Wed, 18 Dec 2013 10:21:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtEFx-0005NB-0h for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 10:21:33 +0000 Received: from [85.158.143.35:53230] by server-1.bemta-4.messagelabs.com id DC/F3-02132-C2771B25; Wed, 18 Dec 2013 10:21:32 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-15.tower-21.messagelabs.com!1387362091!4008204!1 X-Originating-IP: [131.111.8.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26543 invoked from network); 18 Dec 2013 10:21:31 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Dec 2013 10:21:31 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [185.25.64.249] (port=11934 helo=[10.80.3.75]) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) id 1VtEFv-0006SY-1a (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 18 Dec 2013 10:21:31 +0000 Message-ID: <52B1772B.5050007@cam.ac.uk> Date: Wed, 18 Dec 2013 10:21:31 +0000 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17/12/13 17:25, Anil Madhavapeddy wrote: > Alternative medium term solution: the ocamllabs/ocaml-ctypes library > will get stub generation support shortly, which may make it easier to > interface with the OCaml runtime. It can also talk over a shared > memory channel, so C libraries could be treated as RPC servers. This sounds interesting - I can see how you'd use event channels for xen to signal that there's data in the shared mem to read, which would be very lightweight and nice. There are many options to do this in the unix backend, though, so which one were you intending to use? Jon _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 10:21:34 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 10:21:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtEFy-0005NG-16; Wed, 18 Dec 2013 10:21:34 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtEFx-0005NB-0h for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 10:21:33 +0000 Received: from [85.158.143.35:53230] by server-1.bemta-4.messagelabs.com id DC/F3-02132-C2771B25; Wed, 18 Dec 2013 10:21:32 +0000 X-Env-Sender: jjl25@cam.ac.uk X-Msg-Ref: server-15.tower-21.messagelabs.com!1387362091!4008204!1 X-Originating-IP: [131.111.8.132] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26543 invoked from network); 18 Dec 2013 10:21:31 -0000 Received: from ppsw-32.csi.cam.ac.uk (HELO ppsw-32.csi.cam.ac.uk) (131.111.8.132) by server-15.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Dec 2013 10:21:31 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from [185.25.64.249] (port=11934 helo=[10.80.3.75]) by ppsw-32.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.156]:587) with esmtpsa (PLAIN:jjl25) (TLSv1:DHE-RSA-CAMELLIA256-SHA:256) id 1VtEFv-0006SY-1a (Exim 4.82_3-c0e5623) for mirageos-devel@lists.xenproject.org (return-path ); Wed, 18 Dec 2013 10:21:31 +0000 Message-ID: <52B1772B.5050007@cam.ac.uk> Date: Wed, 18 Dec 2013 10:21:31 +0000 From: Jon Ludlam User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org References: <52AF5019.8050105@jamesjb.com> <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> In-Reply-To: <9B4E111E-0AAA-4F99-88D4-006D4DC46608@recoil.org> Subject: Re: [MirageOS-devel] Including a C Library in a Mirage Xen Kernel X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 17/12/13 17:25, Anil Madhavapeddy wrote: > Alternative medium term solution: the ocamllabs/ocaml-ctypes library > will get stub generation support shortly, which may make it easier to > interface with the OCaml runtime. It can also talk over a shared > memory channel, so C libraries could be treated as RPC servers. This sounds interesting - I can see how you'd use event channels for xen to signal that there's data in the shared mem to read, which would be very lightweight and nice. There are many options to do this in the unix backend, though, so which one were you intending to use? Jon _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 12:52:33 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 12:52:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtGc1-0001ta-R7; Wed, 18 Dec 2013 12:52:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtGc0-0001tQ-7R for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 12:52:28 +0000 Received: from [85.158.137.68:49917] by server-5.bemta-3.messagelabs.com id D2/34-25188-A8A91B25; Wed, 18 Dec 2013 12:52:26 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1387371143!4771796!1 X-Originating-IP: [209.85.220.51] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29901 invoked from network); 18 Dec 2013 12:52:25 -0000 Received: from mail-pa0-f51.google.com (HELO mail-pa0-f51.google.com) (209.85.220.51) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 12:52:25 -0000 Received: by mail-pa0-f51.google.com with SMTP id fa1so5934598pad.38 for ; Wed, 18 Dec 2013 04:52:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+W+uFUinnEL6xLzDOeFHzwy4BEdWXPABl7c/K5YM1Qk=; b=srl5ivVYlvmslQqhZVFgN1ggduUE90tz4C07TkF5pm8VHIaCRqMHlTBwKCXNvHn1mp OpEKzvZg5w44Cc5I0T66WyD4LsoFmBZ+LDm+eGLbt9+XvnFjNM7CqabYxGEeXG8SlUWV PiFo/7OWGIobYhNvbeF3jSeiwsZHgIAY/JCxF3tmojoy6cMSTuA/EOIFSNmiL+Hb2MeA csD59+bamMt+OWPdzsdpABdJh79U4z4arhc7fxQLp3O7SFDQywz9DmVjO+ghMU0asoHl astbmZD3k30v4RlEaJ02TLKl1VQfWcDBAQon6ci7GxjN6tURFaEsC9iARdaJ5p2869bE RFJw== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr33569362pbc.42.1387371143207; Wed, 18 Dec 2013 04:52:23 -0800 (PST) Received: by 10.70.61.136 with HTTP; Wed, 18 Dec 2013 04:52:23 -0800 (PST) In-Reply-To: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> Date: Wed, 18 Dec 2013 12:52:23 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3334296801793859255==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3334296801793859255== Content-Type: multipart/alternative; boundary=e89a8ff1c94c29a3a704edce84de --e89a8ff1c94c29a3a704edce84de Content-Type: text/plain; charset=ISO-8859-1 Hi, The problem reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to seek() and read(), allowing two parallel threads to interleave badly. With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've tagged mirage -block-unix.1.2.0. I've also sped up the construction of the FAT images via the 'fat' command-line tool by making it use buffered I/O. I've tagged the new faster-fat as 0.10.0. Note the default Unix block device uses unbuffered I/O, the same as xen. Some apps would clearly benefit from caching (like the webserver) -- perhaps we should add an optional caching layer over KV_RO? Cheers, Dave On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy wrote: > I've been making good progress on porting Mirage/WWW to the 1.0 libraries. > The main website now compiles with 1.0 and crunch, with this (now-merged) > pull request: > https://github.com/mirage/mirage-www/pull/56 > > It was a fairly brute-force merge, but makes it much easier to break up > the old website into a cleaner one based on the Cowabloga library. > > I then took a shot at recompiling the website to use a dynamic FAT block > device instead of the static crunch filesystem. This required a few minor > changes to libraries: > > - Add a KV_RO compatible mode to FAT which simplifies its normally > read/write FS interface: https://github.com/mirage/mirage/pull/160 > - Modify the Mirage command line to have a FAT_KV_RO option: > https://github.com/mirage/mirage/pull/160 > - Parameterise the Mirage-WWW config.ml to use either crunch or static; > https://github.com/mirage/mirage-www/pull/57 > > This plumbing was all pretty straightforward, but triggers a bug somewhere > in the FAT directory traversal, so the resulting website doesn't actually > read the files in FAT mode yet. > > Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, > and we'll have a pass-through to the filesystem to make it easier to > develop code without recompiling all the time. > > TL;DR: blog post very soon, forgive the slight delay :-) > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --e89a8ff1c94c29a3a704edce84de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

=
The proble= m reading files from a FAT filesystem turned out to be a bug in=A0mirage-block-unix: there was no mutex around calls to seek()= and read(), allowing two parallel threads to interleave badly. With this f= ixed I was able to run a Unix=A0mirage-www, and it = all seemed to work. I've tagged=A0mirage-block-= unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool = by making it use buffered I/O. I've tagged the new faster-fat as 0.10.0= .

Note the default Unix = block device uses unbuffered I/O, the same as xen. Some apps would clearly = benefit from caching (like the webserver) -- perhaps we should add an optio= nal caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil Ma= dhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 librari= es. The main website now compiles with 1.0 and crunch, with this (now-merge= d) pull request:
= https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up the= old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block de= vice instead of the static crunch filesystem. =A0This required a few minor = changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally read/wri= te FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.co= m/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/m= irage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug somewhere = in the FAT directory traversal, so the resulting website doesn't actual= ly read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module t= oo, and we'll have a pass-through to the filesystem to make it easier t= o develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel



--
Dave Scott
--e89a8ff1c94c29a3a704edce84de-- --===============3334296801793859255== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3334296801793859255==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 12:52:33 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 12:52:33 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtGc1-0001ta-R7; Wed, 18 Dec 2013 12:52:29 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtGc0-0001tQ-7R for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 12:52:28 +0000 Received: from [85.158.137.68:49917] by server-5.bemta-3.messagelabs.com id D2/34-25188-A8A91B25; Wed, 18 Dec 2013 12:52:26 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1387371143!4771796!1 X-Originating-IP: [209.85.220.51] X-SpamReason: No, hits=0.9 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29901 invoked from network); 18 Dec 2013 12:52:25 -0000 Received: from mail-pa0-f51.google.com (HELO mail-pa0-f51.google.com) (209.85.220.51) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 12:52:25 -0000 Received: by mail-pa0-f51.google.com with SMTP id fa1so5934598pad.38 for ; Wed, 18 Dec 2013 04:52:23 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+W+uFUinnEL6xLzDOeFHzwy4BEdWXPABl7c/K5YM1Qk=; b=srl5ivVYlvmslQqhZVFgN1ggduUE90tz4C07TkF5pm8VHIaCRqMHlTBwKCXNvHn1mp OpEKzvZg5w44Cc5I0T66WyD4LsoFmBZ+LDm+eGLbt9+XvnFjNM7CqabYxGEeXG8SlUWV PiFo/7OWGIobYhNvbeF3jSeiwsZHgIAY/JCxF3tmojoy6cMSTuA/EOIFSNmiL+Hb2MeA csD59+bamMt+OWPdzsdpABdJh79U4z4arhc7fxQLp3O7SFDQywz9DmVjO+ghMU0asoHl astbmZD3k30v4RlEaJ02TLKl1VQfWcDBAQon6ci7GxjN6tURFaEsC9iARdaJ5p2869bE RFJw== MIME-Version: 1.0 X-Received: by 10.68.189.5 with SMTP id ge5mr33569362pbc.42.1387371143207; Wed, 18 Dec 2013 04:52:23 -0800 (PST) Received: by 10.70.61.136 with HTTP; Wed, 18 Dec 2013 04:52:23 -0800 (PST) In-Reply-To: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> Date: Wed, 18 Dec 2013 12:52:23 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3334296801793859255==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3334296801793859255== Content-Type: multipart/alternative; boundary=e89a8ff1c94c29a3a704edce84de --e89a8ff1c94c29a3a704edce84de Content-Type: text/plain; charset=ISO-8859-1 Hi, The problem reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to seek() and read(), allowing two parallel threads to interleave badly. With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've tagged mirage -block-unix.1.2.0. I've also sped up the construction of the FAT images via the 'fat' command-line tool by making it use buffered I/O. I've tagged the new faster-fat as 0.10.0. Note the default Unix block device uses unbuffered I/O, the same as xen. Some apps would clearly benefit from caching (like the webserver) -- perhaps we should add an optional caching layer over KV_RO? Cheers, Dave On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy wrote: > I've been making good progress on porting Mirage/WWW to the 1.0 libraries. > The main website now compiles with 1.0 and crunch, with this (now-merged) > pull request: > https://github.com/mirage/mirage-www/pull/56 > > It was a fairly brute-force merge, but makes it much easier to break up > the old website into a cleaner one based on the Cowabloga library. > > I then took a shot at recompiling the website to use a dynamic FAT block > device instead of the static crunch filesystem. This required a few minor > changes to libraries: > > - Add a KV_RO compatible mode to FAT which simplifies its normally > read/write FS interface: https://github.com/mirage/mirage/pull/160 > - Modify the Mirage command line to have a FAT_KV_RO option: > https://github.com/mirage/mirage/pull/160 > - Parameterise the Mirage-WWW config.ml to use either crunch or static; > https://github.com/mirage/mirage-www/pull/57 > > This plumbing was all pretty straightforward, but triggers a bug somewhere > in the FAT directory traversal, so the resulting website doesn't actually > read the files in FAT mode yet. > > Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module too, > and we'll have a pass-through to the filesystem to make it easier to > develop code without recompiling all the time. > > TL;DR: blog post very soon, forgive the slight delay :-) > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel > -- Dave Scott --e89a8ff1c94c29a3a704edce84de Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

=
The proble= m reading files from a FAT filesystem turned out to be a bug in=A0mirage-block-unix: there was no mutex around calls to seek()= and read(), allowing two parallel threads to interleave badly. With this f= ixed I was able to run a Unix=A0mirage-www, and it = all seemed to work. I've tagged=A0mirage-block-= unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool = by making it use buffered I/O. I've tagged the new faster-fat as 0.10.0= .

Note the default Unix = block device uses unbuffered I/O, the same as xen. Some apps would clearly = benefit from caching (like the webserver) -- perhaps we should add an optio= nal caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil Ma= dhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 librari= es. The main website now compiles with 1.0 and crunch, with this (now-merge= d) pull request:
= https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up the= old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block de= vice instead of the static crunch filesystem. =A0This required a few minor = changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally read/wri= te FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.co= m/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/m= irage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug somewhere = in the FAT directory traversal, so the resulting website doesn't actual= ly read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module t= oo, and we'll have a pass-through to the filesystem to make it easier t= o develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists= .xenproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo= /mirageos-devel



--
Dave Scott
--e89a8ff1c94c29a3a704edce84de-- --===============3334296801793859255== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3334296801793859255==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 13:59:15 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 13:59:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtHeb-0007Kf-SF; Wed, 18 Dec 2013 13:59:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtHea-0007KA-Ja for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 13:59:12 +0000 Received: from [85.158.137.68:15724] by server-14.bemta-3.messagelabs.com id 54/4C-06105-F2AA1B25; Wed, 18 Dec 2013 13:59:11 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1387375151!4790142!1 X-Originating-IP: [74.125.83.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31924 invoked from network); 18 Dec 2013 13:59:11 -0000 Received: from mail-ee0-f51.google.com (HELO mail-ee0-f51.google.com) (74.125.83.51) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 13:59:11 -0000 Received: by mail-ee0-f51.google.com with SMTP id b15so3567922eek.38 for ; Wed, 18 Dec 2013 05:59:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=CU94zGkIPusb3C+PMFWkRslglqA4HMuS2P8yWPyDkSU=; b=jVEh5spviuvApQ233DMr0TfH2fjyzYAsThaytW7D5yzC44oygUg8FncsBAHAtC19V3 pTrSElyuYVs14JjOSrPXViynirTRnWq//xSJ20ys4GPCAGgjoOOTIXMpKIXU+evDY6+Y joIYs55FB2JVfIpgizioAfE4oJhw6RyB4oqvIIf/3rGjBVREXdaNKQyFZ8hpS7OGBE5L tMJC/2yeL1CT2pZNqrK1p44Ca09+nMY3F8icTeX2Cz0RmF471LokX5y1EdbW6dKSsKCf zul3pzvjvvTjvG5C9UxEzPvm4qLV8jK09MNcxG49inqi8RGBPvZqc4DhFiWzfz5ddPA0 8MNg== X-Received: by 10.14.251.68 with SMTP id a44mr29557018ees.64.1387375150898; Wed, 18 Dec 2013 05:59:10 -0800 (PST) Received: from [172.16.25.10] ([185.25.64.249]) by mx.google.com with ESMTPSA id 44sm319195eek.5.2013.12.18.05.59.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 05:59:10 -0800 (PST) Message-ID: <52B1AA2D.3030808@xen.org> Date: Wed, 18 Dec 2013 13:59:09 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Issues with the list (+ proposal to fix it) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, it seems that every person who posts to mirageos-devel for the first time gets caught in a moderator filter. I went through all the settings and cannot explain why this is happening. I believe, that this is due to the way how we imported the list of users. I just did a bulk import, without notification mail, as this what I was asked to do. Normally, when email addresses are import into a list, imported users get a registration mail with instructions to complete (i.e. set up passwords, etc.). Because those mails were not sent, it is conceivable that subscribers to mirageos-devel, are not seen as fully registered by mailman. Here is what I propose: next week (when it is quiet) I would * bulk remove everybody I bulk imported * re-import all those e-mail addresses including notification mails This should then allow you to set up passwords, settings, etc. and complete the registration within mailmain. Please scream, if you have an issue Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 13:59:15 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 13:59:15 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtHeb-0007Kf-SF; Wed, 18 Dec 2013 13:59:13 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtHea-0007KA-Ja for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 13:59:12 +0000 Received: from [85.158.137.68:15724] by server-14.bemta-3.messagelabs.com id 54/4C-06105-F2AA1B25; Wed, 18 Dec 2013 13:59:11 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-3.tower-31.messagelabs.com!1387375151!4790142!1 X-Originating-IP: [74.125.83.51] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31924 invoked from network); 18 Dec 2013 13:59:11 -0000 Received: from mail-ee0-f51.google.com (HELO mail-ee0-f51.google.com) (74.125.83.51) by server-3.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 13:59:11 -0000 Received: by mail-ee0-f51.google.com with SMTP id b15so3567922eek.38 for ; Wed, 18 Dec 2013 05:59:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=CU94zGkIPusb3C+PMFWkRslglqA4HMuS2P8yWPyDkSU=; b=jVEh5spviuvApQ233DMr0TfH2fjyzYAsThaytW7D5yzC44oygUg8FncsBAHAtC19V3 pTrSElyuYVs14JjOSrPXViynirTRnWq//xSJ20ys4GPCAGgjoOOTIXMpKIXU+evDY6+Y joIYs55FB2JVfIpgizioAfE4oJhw6RyB4oqvIIf/3rGjBVREXdaNKQyFZ8hpS7OGBE5L tMJC/2yeL1CT2pZNqrK1p44Ca09+nMY3F8icTeX2Cz0RmF471LokX5y1EdbW6dKSsKCf zul3pzvjvvTjvG5C9UxEzPvm4qLV8jK09MNcxG49inqi8RGBPvZqc4DhFiWzfz5ddPA0 8MNg== X-Received: by 10.14.251.68 with SMTP id a44mr29557018ees.64.1387375150898; Wed, 18 Dec 2013 05:59:10 -0800 (PST) Received: from [172.16.25.10] ([185.25.64.249]) by mx.google.com with ESMTPSA id 44sm319195eek.5.2013.12.18.05.59.09 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 05:59:10 -0800 (PST) Message-ID: <52B1AA2D.3030808@xen.org> Date: Wed, 18 Dec 2013 13:59:09 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Issues with the list (+ proposal to fix it) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, it seems that every person who posts to mirageos-devel for the first time gets caught in a moderator filter. I went through all the settings and cannot explain why this is happening. I believe, that this is due to the way how we imported the list of users. I just did a bulk import, without notification mail, as this what I was asked to do. Normally, when email addresses are import into a list, imported users get a registration mail with instructions to complete (i.e. set up passwords, etc.). Because those mails were not sent, it is conceivable that subscribers to mirageos-devel, are not seen as fully registered by mailman. Here is what I propose: next week (when it is quiet) I would * bulk remove everybody I bulk imported * re-import all those e-mail addresses including notification mails This should then allow you to set up passwords, settings, etc. and complete the registration within mailmain. Please scream, if you have an issue Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 14:32:27 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 14:32:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIAk-0002Cs-T2; Wed, 18 Dec 2013 14:32:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIAk-0002Cm-97 for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 14:32:26 +0000 Received: from [85.158.143.35:64451] by server-1.bemta-4.messagelabs.com id 06/CD-02132-9F1B1B25; Wed, 18 Dec 2013 14:32:25 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-21.messagelabs.com!1387377144!6772692!1 X-Originating-IP: [131.111.8.133] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6835 invoked from network); 18 Dec 2013 14:32:24 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Dec 2013 14:32:24 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-154-165.eduroam.lapwing.private.cam.ac.uk ([172.17.154.165]:64022) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VtIAi-0001dy-hV (Exim 4.82_3-c0e5623) (return-path ); Wed, 18 Dec 2013 14:32:24 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <52B1AA2D.3030808@xen.org> Date: Wed, 18 Dec 2013 14:32:23 +0000 Message-Id: References: <52B1AA2D.3030808@xen.org> To: lars.kurth@xen.org X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Issues with the list (+ proposal to fix it) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm not sure there's a problem here. People are posting to the list from addresses that are not subscribed. This happens when (1) we bring new people into a discussion who may not have explicitly subscribed or (2) if existing people send an email from an account that isn't subscribed. I'm guilty of the latter because I'm subscribed on my @cam account but have sent messages from my Gmail account (which I've added to the 'approved senders' list). My penance is that I get duplicate copies of every reply whenever I use my Gmail account :) In hindsight, what I should have done is given you the list of 'accepted senders' so they don't get stuck in moderation. I'd suggest we just let that build up organically over time. If you think I'm wring about the above, and if anyone has had problems posting to the list, please say so. Otherwise, I think we can leave things as they are. Best wishes, Amir On 18 Dec 2013, at 13:59, Lars Kurth wrote: > Hi all, > > it seems that every person who posts to mirageos-devel for the first time gets caught in a moderator filter. I went through all the settings and cannot explain why this is happening. > > I believe, that this is due to the way how we imported the list of users. I just did a bulk import, without notification mail, as this what I was asked to do. Normally, when email addresses are import into a list, imported users get a registration mail with instructions to complete (i.e. set up passwords, etc.). Because those mails were not sent, it is conceivable that subscribers to mirageos-devel, are not seen as fully registered by mailman. > > Here is what I propose: next week (when it is quiet) I would > * bulk remove everybody I bulk imported > * re-import all those e-mail addresses including notification mails > > This should then allow you to set up passwords, settings, etc. and complete the registration within mailmain. Please scream, if you have an issue > > Regards > Lars > > > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 14:32:27 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 14:32:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIAk-0002Cs-T2; Wed, 18 Dec 2013 14:32:26 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIAk-0002Cm-97 for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 14:32:26 +0000 Received: from [85.158.143.35:64451] by server-1.bemta-4.messagelabs.com id 06/CD-02132-9F1B1B25; Wed, 18 Dec 2013 14:32:25 +0000 X-Env-Sender: amc79@cam.ac.uk X-Msg-Ref: server-4.tower-21.messagelabs.com!1387377144!6772692!1 X-Originating-IP: [131.111.8.133] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 6835 invoked from network); 18 Dec 2013 14:32:24 -0000 Received: from ppsw-33.csi.cam.ac.uk (HELO ppsw-33.csi.cam.ac.uk) (131.111.8.133) by server-4.tower-21.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 18 Dec 2013 14:32:24 -0000 X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from dhcp-172-17-154-165.eduroam.lapwing.private.cam.ac.uk ([172.17.154.165]:64022) by ppsw-33.csi.cam.ac.uk (smtp.hermes.cam.ac.uk [131.111.8.157]:587) with esmtpsa (PLAIN:amc79) (TLSv1:AES128-SHA:128) id 1VtIAi-0001dy-hV (Exim 4.82_3-c0e5623) (return-path ); Wed, 18 Dec 2013 14:32:24 +0000 Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\)) From: Amir Chaudhry In-Reply-To: <52B1AA2D.3030808@xen.org> Date: Wed, 18 Dec 2013 14:32:23 +0000 Message-Id: References: <52B1AA2D.3030808@xen.org> To: lars.kurth@xen.org X-Mailer: Apple Mail (2.1510) Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Issues with the list (+ proposal to fix it) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org I'm not sure there's a problem here. People are posting to the list from addresses that are not subscribed. This happens when (1) we bring new people into a discussion who may not have explicitly subscribed or (2) if existing people send an email from an account that isn't subscribed. I'm guilty of the latter because I'm subscribed on my @cam account but have sent messages from my Gmail account (which I've added to the 'approved senders' list). My penance is that I get duplicate copies of every reply whenever I use my Gmail account :) In hindsight, what I should have done is given you the list of 'accepted senders' so they don't get stuck in moderation. I'd suggest we just let that build up organically over time. If you think I'm wring about the above, and if anyone has had problems posting to the list, please say so. Otherwise, I think we can leave things as they are. Best wishes, Amir On 18 Dec 2013, at 13:59, Lars Kurth wrote: > Hi all, > > it seems that every person who posts to mirageos-devel for the first time gets caught in a moderator filter. I went through all the settings and cannot explain why this is happening. > > I believe, that this is due to the way how we imported the list of users. I just did a bulk import, without notification mail, as this what I was asked to do. Normally, when email addresses are import into a list, imported users get a registration mail with instructions to complete (i.e. set up passwords, etc.). Because those mails were not sent, it is conceivable that subscribers to mirageos-devel, are not seen as fully registered by mailman. > > Here is what I propose: next week (when it is quiet) I would > * bulk remove everybody I bulk imported > * re-import all those e-mail addresses including notification mails > > This should then allow you to set up passwords, settings, etc. and complete the registration within mailmain. Please scream, if you have an issue > > Regards > Lars > > > > > > > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 14:38:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 14:38:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIGX-0003AZ-0j; Wed, 18 Dec 2013 14:38:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIGW-0003AL-5w for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 14:38:24 +0000 Received: from [85.158.143.35:64229] by server-1.bemta-4.messagelabs.com id 08/AA-02132-F53B1B25; Wed, 18 Dec 2013 14:38:23 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1387377502!6780856!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18447 invoked from network); 18 Dec 2013 14:38:22 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 14:38:22 -0000 Received: by mail-wg0-f48.google.com with SMTP id z12so7473257wgg.15 for ; Wed, 18 Dec 2013 06:38:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=b7v21MQCbQJ6FNvFMog81e5G1fDSp8O2bWd9ax0qpLw=; b=1KZwJpkAWOf2IKnhpAytFBAqp8bw3J6dnyRepdK8eYAEUQMYsr6h4La4XZg612D78w T632kH1t4v3D6QKBw8r8cx/HzFiWoFy6z4RwMdrfyn4Nlh7ZPZTc2rf5Ga5WgK3YGYJQ bJqfa/pubc+d6134tZ3fzV3wyA3DjTylANOpp6zXBFmrC4ZONVHPM305MvnWBr+mYwSN uhchXqZCeutlWFRinCOOW/7m2Yo+xOJfluZsuLNqc+B3mMBFH6tXyubggle7g4G0XAjS LJO4g59yE5MCpKtrabRARkPfYoAs7siGzJUcIMqFhKKzGSYYrg88dAVIryGRrh+1f2fC SbuQ== X-Received: by 10.194.8.229 with SMTP id u5mr2531765wja.80.1387377502006; Wed, 18 Dec 2013 06:38:22 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id p9sm1445686wia.10.2013.12.18.06.38.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 06:38:21 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 18 Dec 2013 14:38:18 +0000 Message-Id: References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: Jeremy Yallop X-Mailer: Apple Mail (2.1827) Cc: mirageos-devel@lists.xenproject.org, Anil Madhavapeddy Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): >> >> https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli >> >> File "lib/v1.mli", line 250, characters 4-23: >> Error: This variant or record definition does not match that of type error >> Their kinds differ. >> Command exited with code 2. > > The simplest fix is to simply leave the error type abstract until the > leaf module types. I've implemented that solution there: https://github.com/samoht/mirage-types/commit/98bf70a92cbbab5ba38d80f45f344a32c474864c -- Thomas > There's a slightly neater approach in this case, > though: make the error type in KV_RO a private row, and extend it in > FS. The definition of error in KV_RO would then be > > type error = > private [> `Unknown_key of string ] > > and the definition of error in FS would become > > type error = [ > | `Not_a_directory of string > (* ... *) > | `Block_device of block_device_error > | `Unknown_key of string > ] > > (The minor downside is that callers of KV_RO.read would need to handle > both `Error (`Unknown_key s) and some unspecified/unknowable set of > tags.) > > Jeremy. > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 14:38:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 14:38:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIGX-0003AZ-0j; Wed, 18 Dec 2013 14:38:25 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtIGW-0003AL-5w for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 14:38:24 +0000 Received: from [85.158.143.35:64229] by server-1.bemta-4.messagelabs.com id 08/AA-02132-F53B1B25; Wed, 18 Dec 2013 14:38:23 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-8.tower-21.messagelabs.com!1387377502!6780856!1 X-Originating-IP: [74.125.82.48] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 18447 invoked from network); 18 Dec 2013 14:38:22 -0000 Received: from mail-wg0-f48.google.com (HELO mail-wg0-f48.google.com) (74.125.82.48) by server-8.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 14:38:22 -0000 Received: by mail-wg0-f48.google.com with SMTP id z12so7473257wgg.15 for ; Wed, 18 Dec 2013 06:38:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=b7v21MQCbQJ6FNvFMog81e5G1fDSp8O2bWd9ax0qpLw=; b=1KZwJpkAWOf2IKnhpAytFBAqp8bw3J6dnyRepdK8eYAEUQMYsr6h4La4XZg612D78w T632kH1t4v3D6QKBw8r8cx/HzFiWoFy6z4RwMdrfyn4Nlh7ZPZTc2rf5Ga5WgK3YGYJQ bJqfa/pubc+d6134tZ3fzV3wyA3DjTylANOpp6zXBFmrC4ZONVHPM305MvnWBr+mYwSN uhchXqZCeutlWFRinCOOW/7m2Yo+xOJfluZsuLNqc+B3mMBFH6tXyubggle7g4G0XAjS LJO4g59yE5MCpKtrabRARkPfYoAs7siGzJUcIMqFhKKzGSYYrg88dAVIryGRrh+1f2fC SbuQ== X-Received: by 10.194.8.229 with SMTP id u5mr2531765wja.80.1387377502006; Wed, 18 Dec 2013 06:38:22 -0800 (PST) Received: from piana.mac.cl.cam.ac.uk (piana.mac.cl.cam.ac.uk. [128.232.56.38]) by mx.google.com with ESMTPSA id p9sm1445686wia.10.2013.12.18.06.38.20 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 06:38:21 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: Date: Wed, 18 Dec 2013 14:38:18 +0000 Message-Id: References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: Jeremy Yallop X-Mailer: Apple Mail (2.1827) Cc: mirageos-devel@lists.xenproject.org, Anil Madhavapeddy Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org >> Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): >> >> https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli >> >> File "lib/v1.mli", line 250, characters 4-23: >> Error: This variant or record definition does not match that of type error >> Their kinds differ. >> Command exited with code 2. > > The simplest fix is to simply leave the error type abstract until the > leaf module types. I've implemented that solution there: https://github.com/samoht/mirage-types/commit/98bf70a92cbbab5ba38d80f45f344a32c474864c -- Thomas > There's a slightly neater approach in this case, > though: make the error type in KV_RO a private row, and extend it in > FS. The definition of error in KV_RO would then be > > type error = > private [> `Unknown_key of string ] > > and the definition of error in FS would become > > type error = [ > | `Not_a_directory of string > (* ... *) > | `Block_device of block_device_error > | `Unknown_key of string > ] > > (The minor downside is that callers of KV_RO.read would need to handle > both `Error (`Unknown_key s) and some unspecified/unknowable set of > tags.) > > Jeremy. > > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 15:58:47 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 15:58:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtJWF-0005Di-Pp; Wed, 18 Dec 2013 15:58:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtJWE-0005DZ-Bi for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 15:58:42 +0000 Received: from [85.158.143.35:7209] by server-3.bemta-4.messagelabs.com id 6C/27-32360-136C1B25; Wed, 18 Dec 2013 15:58:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1387382319!5538118!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24507 invoked from network); 18 Dec 2013 15:58:39 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-21.messagelabs.com with SMTP; 18 Dec 2013 15:58:39 -0000 Received: (qmail 10173 invoked by uid 634); 18 Dec 2013 15:58:22 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Dec 2013 15:58:18 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Dec 2013 15:58:17 +0000 Message-Id: References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9090283345836220364==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9090283345836220364== Content-Type: multipart/alternative; boundary="Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2" --Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Perfect, this works for me now with Mirage-WWW! I've also fixed a build issue with the HTTP libraries, by splitting them = out into: https://github.com/mirage/mirage-http-unix https://github.com/mirage/mirage-http-xen See https://github.com/mirage/mirage/issues/161 for the details. With all of this merged into OPAM shortly, Mirage 1.0.3 will be good to = be released, and will build the Mirage website in the following modes: - Unix: filesystem passthrough to make editing files locally easy - Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat - Xen: crunch filesystem That's finally good enough for the blog post, yay! Only 3 days late, a = new Mirage record :-) -anil On 18 Dec 2013, at 12:52, David Scott wrote: > Hi, >=20 > The problem reading files from a FAT filesystem turned out to be a bug = in mirage-block-unix: there was no mutex around calls to seek() and = read(), allowing two parallel threads to interleave badly. With this = fixed I was able to run a Unix mirage-www, and it all seemed to work. = I've tagged mirage-block-unix.1.2.0. >=20 > I've also sped up the construction of the FAT images via the 'fat' = command-line tool by making it use buffered I/O. I've tagged the new = faster-fat as 0.10.0. >=20 > Note the default Unix block device uses unbuffered I/O, the same as = xen. Some apps would clearly benefit from caching (like the webserver) = -- perhaps we should add an optional caching layer over KV_RO? >=20 > Cheers, > Dave >=20 >=20 > On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy = wrote: > I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request: > https://github.com/mirage/mirage-www/pull/56 >=20 > It was a fairly brute-force merge, but makes it much easier to break = up the old website into a cleaner one based on the Cowabloga library. >=20 > I then took a shot at recompiling the website to use a dynamic FAT = block device instead of the static crunch filesystem. This required a = few minor changes to libraries: >=20 > - Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160 > - Modify the Mirage command line to have a FAT_KV_RO option: = https://github.com/mirage/mirage/pull/160 > - Parameterise the Mirage-WWW config.ml to use either crunch or = static; https://github.com/mirage/mirage-www/pull/57 >=20 > This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet. >=20 > Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time. >=20 > TL;DR: blog post very soon, forgive the slight delay :-) >=20 > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 >=20 > --=20 > Dave Scott --Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Perfect, this works for me now with = Mirage-WWW!

I've also fixed a build issue with the = HTTP libraries, by splitting them out into:



With all of this merged into OPAM = shortly, Mirage 1.0.3 will be good to be released, and will build the = Mirage website in the following modes:

- Unix: = filesystem passthrough to make editing files locally easy
- = Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat
- = Xen: crunch filesystem

That's finally good = enough for the blog post,  yay!  Only 3 days late, a new = Mirage record = :-)

-anil

On 18 = Dec 2013, at 12:52, David Scott <scott.dj@gmail.com> = wrote:

Hi,

The problem = reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to = seek() and read(), allowing two parallel threads to interleave badly. = With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've = tagged mirage-block-unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool by = making it use buffered I/O. I've tagged the new faster-fat as = 0.10.0.

Note the default = Unix block device uses unbuffered I/O, the same as xen. Some apps would = clearly benefit from caching (like the webserver) -- perhaps we should = add an optional caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil = Madhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up = the old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block = device instead of the static crunch filesystem.  This required a = few minor changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



--
Dave = Scott

= --Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2-- --===============9090283345836220364== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============9090283345836220364==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 15:58:47 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 15:58:47 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtJWF-0005Di-Pp; Wed, 18 Dec 2013 15:58:43 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtJWE-0005DZ-Bi for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 15:58:42 +0000 Received: from [85.158.143.35:7209] by server-3.bemta-4.messagelabs.com id 6C/27-32360-136C1B25; Wed, 18 Dec 2013 15:58:41 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-21.messagelabs.com!1387382319!5538118!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24507 invoked from network); 18 Dec 2013 15:58:39 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-21.messagelabs.com with SMTP; 18 Dec 2013 15:58:39 -0000 Received: (qmail 10173 invoked by uid 634); 18 Dec 2013 15:58:22 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Dec 2013 15:58:18 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Dec 2013 15:58:17 +0000 Message-Id: References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============9090283345836220364==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============9090283345836220364== Content-Type: multipart/alternative; boundary="Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2" --Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Perfect, this works for me now with Mirage-WWW! I've also fixed a build issue with the HTTP libraries, by splitting them = out into: https://github.com/mirage/mirage-http-unix https://github.com/mirage/mirage-http-xen See https://github.com/mirage/mirage/issues/161 for the details. With all of this merged into OPAM shortly, Mirage 1.0.3 will be good to = be released, and will build the Mirage website in the following modes: - Unix: filesystem passthrough to make editing files locally easy - Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat - Xen: crunch filesystem That's finally good enough for the blog post, yay! Only 3 days late, a = new Mirage record :-) -anil On 18 Dec 2013, at 12:52, David Scott wrote: > Hi, >=20 > The problem reading files from a FAT filesystem turned out to be a bug = in mirage-block-unix: there was no mutex around calls to seek() and = read(), allowing two parallel threads to interleave badly. With this = fixed I was able to run a Unix mirage-www, and it all seemed to work. = I've tagged mirage-block-unix.1.2.0. >=20 > I've also sped up the construction of the FAT images via the 'fat' = command-line tool by making it use buffered I/O. I've tagged the new = faster-fat as 0.10.0. >=20 > Note the default Unix block device uses unbuffered I/O, the same as = xen. Some apps would clearly benefit from caching (like the webserver) = -- perhaps we should add an optional caching layer over KV_RO? >=20 > Cheers, > Dave >=20 >=20 > On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy = wrote: > I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request: > https://github.com/mirage/mirage-www/pull/56 >=20 > It was a fairly brute-force merge, but makes it much easier to break = up the old website into a cleaner one based on the Cowabloga library. >=20 > I then took a shot at recompiling the website to use a dynamic FAT = block device instead of the static crunch filesystem. This required a = few minor changes to libraries: >=20 > - Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160 > - Modify the Mirage command line to have a FAT_KV_RO option: = https://github.com/mirage/mirage/pull/160 > - Parameterise the Mirage-WWW config.ml to use either crunch or = static; https://github.com/mirage/mirage-www/pull/57 >=20 > This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet. >=20 > Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time. >=20 > TL;DR: blog post very soon, forgive the slight delay :-) >=20 > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 >=20 >=20 > --=20 > Dave Scott --Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Perfect, this works for me now with = Mirage-WWW!

I've also fixed a build issue with the = HTTP libraries, by splitting them out into:



With all of this merged into OPAM = shortly, Mirage 1.0.3 will be good to be released, and will build the = Mirage website in the following modes:

- Unix: = filesystem passthrough to make editing files locally easy
- = Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat
- = Xen: crunch filesystem

That's finally good = enough for the blog post,  yay!  Only 3 days late, a new = Mirage record = :-)

-anil

On 18 = Dec 2013, at 12:52, David Scott <scott.dj@gmail.com> = wrote:

Hi,

The problem = reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to = seek() and read(), allowing two parallel threads to interleave badly. = With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've = tagged mirage-block-unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool by = making it use buffered I/O. I've tagged the new faster-fat as = 0.10.0.

Note the default = Unix block device uses unbuffered I/O, the same as xen. Some apps would = clearly benefit from caching (like the webserver) -- perhaps we should = add an optional caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil = Madhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up = the old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block = device instead of the static crunch filesystem.  This required a = few minor changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



--
Dave = Scott

= --Apple-Mail=_576567F2-854B-4745-A320-57334B3178D2-- --===============9090283345836220364== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============9090283345836220364==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 16:39:53 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 16:39:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtKA3-0001C5-GF; Wed, 18 Dec 2013 16:39:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtKA2-0001C0-It for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 16:39:50 +0000 Received: from [193.109.254.147:7384] by server-16.bemta-14.messagelabs.com id 50/02-20600-5DFC1B25; Wed, 18 Dec 2013 16:39:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1387384787!6174678!1 X-Originating-IP: [209.85.215.182] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25621 invoked from network); 18 Dec 2013 16:39:47 -0000 Received: from mail-ea0-f182.google.com (HELO mail-ea0-f182.google.com) (209.85.215.182) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 16:39:47 -0000 Received: by mail-ea0-f182.google.com with SMTP id a15so3695916eae.13 for ; Wed, 18 Dec 2013 08:39:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7zWWlJlo9n49EcEJXrC4wV1xqb4z9XjRhZkNW1OVBS8=; b=DFBRDTMhsr4EfklzxZ3I0M9nfu9/C4huLCziGdxPkt3yPTolkPlYxxH0uVVdtcEJQ0 mL+zg97eT5hBg4NPeaVaFllFPd9mcQByhfHqNBu2nptITtg5JhUCOBBoNY4nqHZiBS/p X2dXYQIdLRdK0b0TqX1RyJ9xylIWf2LwW3Y5QCzmummk2+ZeA0vCpeXflogiLd5/zvaL OsKVZRQ3zbTjKVy64pIW4GukwgLWx+FT26Fp3B3ORt7xVyAkW6bEkkR56IvKwcXugCWZ Sxj9wEJUWZWFWY50XsZp5heDtPnueMVIoQ+Pxy9FKVjCRpl8RwMV2D7mgPSctrXsN9hj 8MfQ== X-Received: by 10.15.61.134 with SMTP id i6mr29712156eex.48.1387384787398; Wed, 18 Dec 2013 08:39:47 -0800 (PST) Received: from [172.16.25.10] ([185.25.64.249]) by mx.google.com with ESMTPSA id h3sm1473537eem.15.2013.12.18.08.39.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 08:39:46 -0800 (PST) Message-ID: <52B1CFD0.5020903@xen.org> Date: Wed, 18 Dec 2013 16:39:44 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Amir Chaudhry References: <52B1AA2D.3030808@xen.org> In-Reply-To: Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Issues with the list (+ proposal to fix it) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 18/12/2013 14:32, Amir Chaudhry wrote: > I'm not sure there's a problem here. > > People are posting to the list from addresses that are not subscribed. This happens when (1) we bring new people into a discussion who may not have explicitly subscribed or (2) if existing people send an email from an account that isn't subscribed. > > I'm guilty of the latter because I'm subscribed on my @cam account but have sent messages from my Gmail account (which I've added to the 'approved senders' list). My penance is that I get duplicate copies of every reply whenever I use my Gmail account :) > > In hindsight, what I should have done is given you the list of 'accepted senders' so they don't get stuck in moderation. I'd suggest we just let that build up organically over time. > > If you think I'm wrong about the above, and if anyone has had problems posting to the list, please say so. Otherwise, I think we can leave things as they are. That works for me Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 16:39:53 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 16:39:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtKA3-0001C5-GF; Wed, 18 Dec 2013 16:39:51 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtKA2-0001C0-It for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 16:39:50 +0000 Received: from [193.109.254.147:7384] by server-16.bemta-14.messagelabs.com id 50/02-20600-5DFC1B25; Wed, 18 Dec 2013 16:39:49 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-12.tower-27.messagelabs.com!1387384787!6174678!1 X-Originating-IP: [209.85.215.182] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 25621 invoked from network); 18 Dec 2013 16:39:47 -0000 Received: from mail-ea0-f182.google.com (HELO mail-ea0-f182.google.com) (209.85.215.182) by server-12.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 18 Dec 2013 16:39:47 -0000 Received: by mail-ea0-f182.google.com with SMTP id a15so3695916eae.13 for ; Wed, 18 Dec 2013 08:39:47 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=7zWWlJlo9n49EcEJXrC4wV1xqb4z9XjRhZkNW1OVBS8=; b=DFBRDTMhsr4EfklzxZ3I0M9nfu9/C4huLCziGdxPkt3yPTolkPlYxxH0uVVdtcEJQ0 mL+zg97eT5hBg4NPeaVaFllFPd9mcQByhfHqNBu2nptITtg5JhUCOBBoNY4nqHZiBS/p X2dXYQIdLRdK0b0TqX1RyJ9xylIWf2LwW3Y5QCzmummk2+ZeA0vCpeXflogiLd5/zvaL OsKVZRQ3zbTjKVy64pIW4GukwgLWx+FT26Fp3B3ORt7xVyAkW6bEkkR56IvKwcXugCWZ Sxj9wEJUWZWFWY50XsZp5heDtPnueMVIoQ+Pxy9FKVjCRpl8RwMV2D7mgPSctrXsN9hj 8MfQ== X-Received: by 10.15.61.134 with SMTP id i6mr29712156eex.48.1387384787398; Wed, 18 Dec 2013 08:39:47 -0800 (PST) Received: from [172.16.25.10] ([185.25.64.249]) by mx.google.com with ESMTPSA id h3sm1473537eem.15.2013.12.18.08.39.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 18 Dec 2013 08:39:46 -0800 (PST) Message-ID: <52B1CFD0.5020903@xen.org> Date: Wed, 18 Dec 2013 16:39:44 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Amir Chaudhry References: <52B1AA2D.3030808@xen.org> In-Reply-To: Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Issues with the list (+ proposal to fix it) X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 18/12/2013 14:32, Amir Chaudhry wrote: > I'm not sure there's a problem here. > > People are posting to the list from addresses that are not subscribed. This happens when (1) we bring new people into a discussion who may not have explicitly subscribed or (2) if existing people send an email from an account that isn't subscribed. > > I'm guilty of the latter because I'm subscribed on my @cam account but have sent messages from my Gmail account (which I've added to the 'approved senders' list). My penance is that I get duplicate copies of every reply whenever I use my Gmail account :) > > In hindsight, what I should have done is given you the list of 'accepted senders' so they don't get stuck in moderation. I'd suggest we just let that build up organically over time. > > If you think I'm wrong about the above, and if anyone has had problems posting to the list, please say so. Otherwise, I think we can leave things as they are. That works for me Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 19:01:17 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 19:01:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtMMs-0004SP-9a; Wed, 18 Dec 2013 19:01:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtMMr-0004SK-7T for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 19:01:13 +0000 Received: from [85.158.137.68:9702] by server-1.bemta-3.messagelabs.com id 07/E7-29598-8F0F1B25; Wed, 18 Dec 2013 19:01:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1387393269!4853379!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32231 invoked from network); 18 Dec 2013 19:01:09 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-31.messagelabs.com with SMTP; 18 Dec 2013 19:01:09 -0000 Received: (qmail 23377 invoked by uid 634); 18 Dec 2013 19:01:06 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Dec 2013 19:01:05 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Dec 2013 19:01:03 +0000 Message-Id: <0D4F644A-AEF6-43A7-BD13-89C52BD538A6@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7359498376935547985==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7359498376935547985== Content-Type: multipart/alternative; boundary="Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE" --Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I've tagged a Mirage-1.0.3 in OPAM that contains all the fixes. Once it = goes through Travis, I'll test it over and update the website with it = and add a blog post. -anil On 18 Dec 2013, at 15:58, Anil Madhavapeddy wrote: > Perfect, this works for me now with Mirage-WWW! >=20 > I've also fixed a build issue with the HTTP libraries, by splitting = them out into: >=20 > https://github.com/mirage/mirage-http-unix > https://github.com/mirage/mirage-http-xen >=20 > See https://github.com/mirage/mirage/issues/161 for the details. >=20 > With all of this merged into OPAM shortly, Mirage 1.0.3 will be good = to be released, and will build the Mirage website in the following = modes: >=20 > - Unix: filesystem passthrough to make editing files locally easy > - Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat > - Xen: crunch filesystem >=20 > That's finally good enough for the blog post, yay! Only 3 days late, = a new Mirage record :-) >=20 > -anil >=20 > On 18 Dec 2013, at 12:52, David Scott wrote: >=20 >> Hi, >>=20 >> The problem reading files from a FAT filesystem turned out to be a = bug in mirage-block-unix: there was no mutex around calls to seek() and = read(), allowing two parallel threads to interleave badly. With this = fixed I was able to run a Unix mirage-www, and it all seemed to work. = I've tagged mirage-block-unix.1.2.0. >>=20 >> I've also sped up the construction of the FAT images via the 'fat' = command-line tool by making it use buffered I/O. I've tagged the new = faster-fat as 0.10.0. >>=20 >> Note the default Unix block device uses unbuffered I/O, the same as = xen. Some apps would clearly benefit from caching (like the webserver) = -- perhaps we should add an optional caching layer over KV_RO? >>=20 >> Cheers, >> Dave >>=20 >>=20 >> On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy = wrote: >> I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request: >> https://github.com/mirage/mirage-www/pull/56 >>=20 >> It was a fairly brute-force merge, but makes it much easier to break = up the old website into a cleaner one based on the Cowabloga library. >>=20 >> I then took a shot at recompiling the website to use a dynamic FAT = block device instead of the static crunch filesystem. This required a = few minor changes to libraries: >>=20 >> - Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160 >> - Modify the Mirage command line to have a FAT_KV_RO option: = https://github.com/mirage/mirage/pull/160 >> - Parameterise the Mirage-WWW config.ml to use either crunch or = static; https://github.com/mirage/mirage-www/pull/57 >>=20 >> This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet. >>=20 >> Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time. >>=20 >> TL;DR: blog post very soon, forgive the slight delay :-) >>=20 >> -anil >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=20 >>=20 >>=20 >> --=20 >> Dave Scott >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I've = tagged a Mirage-1.0.3 in OPAM that contains all the fixes.  Once it = goes through Travis, I'll test it over and update the website with it = and add a blog post.

-anil

On = 18 Dec 2013, at 15:58, Anil Madhavapeddy <anil@recoil.org> wrote:

Perfect, this works for me now with = Mirage-WWW!

I've also fixed a build issue with the = HTTP libraries, by splitting them out into:



With all of this merged into OPAM = shortly, Mirage 1.0.3 will be good to be released, and will build the = Mirage website in the following modes:

- Unix: = filesystem passthrough to make editing files locally easy
- = Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat
- = Xen: crunch filesystem

That's finally good = enough for the blog post,  yay!  Only 3 days late, a new = Mirage record = :-)

-anil

On 18 = Dec 2013, at 12:52, David Scott <scott.dj@gmail.com> = wrote:

Hi,

The problem = reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to = seek() and read(), allowing two parallel threads to interleave badly. = With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've = tagged mirage-block-unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool by = making it use buffered I/O. I've tagged the new faster-fat as = 0.10.0.

Note the default = Unix block device uses unbuffered I/O, the same as xen. Some apps would = clearly benefit from caching (like the webserver) -- perhaps we should = add an optional caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil = Madhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up = the old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block = device instead of the static crunch filesystem.  This required a = few minor changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



--
Dave = Scott
=

_______________________________________= ________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE-- --===============7359498376935547985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7359498376935547985==-- From mirageos-devel-bounces@lists.xenproject.org Wed Dec 18 19:01:17 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Wed, 18 Dec 2013 19:01:17 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtMMs-0004SP-9a; Wed, 18 Dec 2013 19:01:14 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtMMr-0004SK-7T for mirageos-devel@lists.xenproject.org; Wed, 18 Dec 2013 19:01:13 +0000 Received: from [85.158.137.68:9702] by server-1.bemta-3.messagelabs.com id 07/E7-29598-8F0F1B25; Wed, 18 Dec 2013 19:01:12 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1387393269!4853379!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 32231 invoked from network); 18 Dec 2013 19:01:09 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-31.messagelabs.com with SMTP; 18 Dec 2013 19:01:09 -0000 Received: (qmail 23377 invoked by uid 634); 18 Dec 2013 19:01:06 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from volstagg-0.srg.cl.cam.ac.uk (HELO flick.office) (128.232.32.232) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Wed, 18 Dec 2013 19:01:05 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Wed, 18 Dec 2013 19:01:03 +0000 Message-Id: <0D4F644A-AEF6-43A7-BD13-89C52BD538A6@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============7359498376935547985==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============7359498376935547985== Content-Type: multipart/alternative; boundary="Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE" --Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I've tagged a Mirage-1.0.3 in OPAM that contains all the fixes. Once it = goes through Travis, I'll test it over and update the website with it = and add a blog post. -anil On 18 Dec 2013, at 15:58, Anil Madhavapeddy wrote: > Perfect, this works for me now with Mirage-WWW! >=20 > I've also fixed a build issue with the HTTP libraries, by splitting = them out into: >=20 > https://github.com/mirage/mirage-http-unix > https://github.com/mirage/mirage-http-xen >=20 > See https://github.com/mirage/mirage/issues/161 for the details. >=20 > With all of this merged into OPAM shortly, Mirage 1.0.3 will be good = to be released, and will build the Mirage website in the following = modes: >=20 > - Unix: filesystem passthrough to make editing files locally easy > - Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat > - Xen: crunch filesystem >=20 > That's finally good enough for the blog post, yay! Only 3 days late, = a new Mirage record :-) >=20 > -anil >=20 > On 18 Dec 2013, at 12:52, David Scott wrote: >=20 >> Hi, >>=20 >> The problem reading files from a FAT filesystem turned out to be a = bug in mirage-block-unix: there was no mutex around calls to seek() and = read(), allowing two parallel threads to interleave badly. With this = fixed I was able to run a Unix mirage-www, and it all seemed to work. = I've tagged mirage-block-unix.1.2.0. >>=20 >> I've also sped up the construction of the FAT images via the 'fat' = command-line tool by making it use buffered I/O. I've tagged the new = faster-fat as 0.10.0. >>=20 >> Note the default Unix block device uses unbuffered I/O, the same as = xen. Some apps would clearly benefit from caching (like the webserver) = -- perhaps we should add an optional caching layer over KV_RO? >>=20 >> Cheers, >> Dave >>=20 >>=20 >> On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy = wrote: >> I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request: >> https://github.com/mirage/mirage-www/pull/56 >>=20 >> It was a fairly brute-force merge, but makes it much easier to break = up the old website into a cleaner one based on the Cowabloga library. >>=20 >> I then took a shot at recompiling the website to use a dynamic FAT = block device instead of the static crunch filesystem. This required a = few minor changes to libraries: >>=20 >> - Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160 >> - Modify the Mirage command line to have a FAT_KV_RO option: = https://github.com/mirage/mirage/pull/160 >> - Parameterise the Mirage-WWW config.ml to use either crunch or = static; https://github.com/mirage/mirage-www/pull/57 >>=20 >> This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet. >>=20 >> Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time. >>=20 >> TL;DR: blog post very soon, forgive the slight delay :-) >>=20 >> -anil >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>=20 >>=20 >>=20 >> --=20 >> Dave Scott >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I've = tagged a Mirage-1.0.3 in OPAM that contains all the fixes.  Once it = goes through Travis, I'll test it over and update the website with it = and add a blog post.

-anil

On = 18 Dec 2013, at 15:58, Anil Madhavapeddy <anil@recoil.org> wrote:

Perfect, this works for me now with = Mirage-WWW!

I've also fixed a build issue with the = HTTP libraries, by splitting them out into:



With all of this merged into OPAM = shortly, Mirage 1.0.3 will be good to be released, and will build the = Mirage website in the following modes:

- Unix: = filesystem passthrough to make editing files locally easy
- = Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat
- = Xen: crunch filesystem

That's finally good = enough for the blog post,  yay!  Only 3 days late, a new = Mirage record = :-)

-anil

On 18 = Dec 2013, at 12:52, David Scott <scott.dj@gmail.com> = wrote:

Hi,

The problem = reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to = seek() and read(), allowing two parallel threads to interleave badly. = With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've = tagged mirage-block-unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool by = making it use buffered I/O. I've tagged the new faster-fat as = 0.10.0.

Note the default = Unix block device uses unbuffered I/O, the same as xen. Some apps would = clearly benefit from caching (like the webserver) -- perhaps we should = add an optional caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil = Madhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up = the old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block = device instead of the static crunch filesystem.  This required a = few minor changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



--
Dave = Scott
=

_______________________________________= ________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_001AA1E5-E85B-433F-A17F-BAB37ECD8ACE-- --===============7359498376935547985== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============7359498376935547985==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 02:26:46 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 02:26:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtpnV-00052r-QJ; Fri, 20 Dec 2013 02:26:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtpnS-00052m-V9 for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 02:26:39 +0000 Received: from [85.158.139.211:45604] by server-7.bemta-5.messagelabs.com id 72/E1-04824-EDAA3B25; Fri, 20 Dec 2013 02:26:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1387506395!5755703!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8031 invoked from network); 20 Dec 2013 02:26:36 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-206.messagelabs.com with SMTP; 20 Dec 2013 02:26:36 -0000 Received: (qmail 590 invoked by uid 634); 20 Dec 2013 02:26:35 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Dec 2013 02:26:33 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0D4F644A-AEF6-43A7-BD13-89C52BD538A6@recoil.org> Date: Fri, 20 Dec 2013 02:26:31 +0000 Message-Id: <541ED5DE-DB94-4C87-909B-D58663F0C967@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> <0D4F644A-AEF6-43A7-BD13-89C52BD538A6@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8475221677676760682==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8475221677676760682== Content-Type: multipart/alternative; boundary="Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B" --Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I've now released Mirage 1.0.3 to OPAM and put up a blog post: http://openmirage.org/blog/mirage-1.0.3-released There is a new wiki entry on how to build the website: http://openmirage.org/wiki/mirage-www Over to you for the decks.openmirage.org one, Mort! -anil On 18 Dec 2013, at 19:01, Anil Madhavapeddy wrote: > I've tagged a Mirage-1.0.3 in OPAM that contains all the fixes. Once = it goes through Travis, I'll test it over and update the website with it = and add a blog post. >=20 > -anil >=20 > On 18 Dec 2013, at 15:58, Anil Madhavapeddy wrote: >=20 >> Perfect, this works for me now with Mirage-WWW! >>=20 >> I've also fixed a build issue with the HTTP libraries, by splitting = them out into: >>=20 >> https://github.com/mirage/mirage-http-unix >> https://github.com/mirage/mirage-http-xen >>=20 >> See https://github.com/mirage/mirage/issues/161 for the details. >>=20 >> With all of this merged into OPAM shortly, Mirage 1.0.3 will be good = to be released, and will build the Mirage website in the following = modes: >>=20 >> - Unix: filesystem passthrough to make editing files locally easy >> - Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat >> - Xen: crunch filesystem >>=20 >> That's finally good enough for the blog post, yay! Only 3 days = late, a new Mirage record :-) >>=20 >> -anil >>=20 >> On 18 Dec 2013, at 12:52, David Scott wrote: >>=20 >>> Hi, >>>=20 >>> The problem reading files from a FAT filesystem turned out to be a = bug in mirage-block-unix: there was no mutex around calls to seek() and = read(), allowing two parallel threads to interleave badly. With this = fixed I was able to run a Unix mirage-www, and it all seemed to work. = I've tagged mirage-block-unix.1.2.0. >>>=20 >>> I've also sped up the construction of the FAT images via the 'fat' = command-line tool by making it use buffered I/O. I've tagged the new = faster-fat as 0.10.0. >>>=20 >>> Note the default Unix block device uses unbuffered I/O, the same as = xen. Some apps would clearly benefit from caching (like the webserver) = -- perhaps we should add an optional caching layer over KV_RO? >>>=20 >>> Cheers, >>> Dave >>>=20 >>>=20 >>> On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy = wrote: >>> I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request: >>> https://github.com/mirage/mirage-www/pull/56 >>>=20 >>> It was a fairly brute-force merge, but makes it much easier to break = up the old website into a cleaner one based on the Cowabloga library. >>>=20 >>> I then took a shot at recompiling the website to use a dynamic FAT = block device instead of the static crunch filesystem. This required a = few minor changes to libraries: >>>=20 >>> - Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160 >>> - Modify the Mirage command line to have a FAT_KV_RO option: = https://github.com/mirage/mirage/pull/160 >>> - Parameterise the Mirage-WWW config.ml to use either crunch or = static; https://github.com/mirage/mirage-www/pull/57 >>>=20 >>> This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet. >>>=20 >>> Once that's tracked down (hello Dave!), I can add a Unix_KV_RO = module too, and we'll have a pass-through to the filesystem to make it = easier to develop code without recompiling all the time. >>>=20 >>> TL;DR: blog post very soon, forgive the slight delay :-) >>>=20 >>> -anil >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>=20 >>>=20 >>>=20 >>> --=20 >>> Dave Scott >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I've = now released Mirage 1.0.3 to OPAM and put up a blog post:

There is a = new wiki entry on how to build the website:

Over to you for the decks.openmirage.org one, = Mort!

-anil

On 18 Dec = 2013, at 19:01, Anil Madhavapeddy <anil@recoil.org> wrote:

I've = tagged a Mirage-1.0.3 in OPAM that contains all the fixes.  Once it = goes through Travis, I'll test it over and update the website with it = and add a blog post.

-anil

On = 18 Dec 2013, at 15:58, Anil Madhavapeddy <anil@recoil.org> wrote:

Perfect, this works for me now with = Mirage-WWW!

I've also fixed a build issue with the = HTTP libraries, by splitting them out into:



With all of this merged into OPAM = shortly, Mirage 1.0.3 will be good to be released, and will build the = Mirage website in the following modes:

- Unix: = filesystem passthrough to make editing files locally easy
- = Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat
- = Xen: crunch filesystem

That's finally good = enough for the blog post,  yay!  Only 3 days late, a new = Mirage record = :-)

-anil

On 18 = Dec 2013, at 12:52, David Scott <scott.dj@gmail.com> = wrote:

Hi,

The problem = reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to = seek() and read(), allowing two parallel threads to interleave badly. = With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've = tagged mirage-block-unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool by = making it use buffered I/O. I've tagged the new faster-fat as = 0.10.0.

Note the default = Unix block device uses unbuffered I/O, the same as xen. Some apps would = clearly benefit from caching (like the webserver) -- perhaps we should = add an optional caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil = Madhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up = the old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block = device instead of the static crunch filesystem.  This required a = few minor changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



--
Dave = Scott
=

_______________________________________= ________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel=

___________________________________= ____________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B-- --===============8475221677676760682== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============8475221677676760682==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 02:26:46 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 02:26:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtpnV-00052r-QJ; Fri, 20 Dec 2013 02:26:41 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtpnS-00052m-V9 for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 02:26:39 +0000 Received: from [85.158.139.211:45604] by server-7.bemta-5.messagelabs.com id 72/E1-04824-EDAA3B25; Fri, 20 Dec 2013 02:26:38 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-9.tower-206.messagelabs.com!1387506395!5755703!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.6 required=7.0 tests=HTML_40_50,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_23,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8031 invoked from network); 20 Dec 2013 02:26:36 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-9.tower-206.messagelabs.com with SMTP; 20 Dec 2013 02:26:36 -0000 Received: (qmail 590 invoked by uid 634); 20 Dec 2013 02:26:35 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Dec 2013 02:26:33 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0D4F644A-AEF6-43A7-BD13-89C52BD538A6@recoil.org> Date: Fri, 20 Dec 2013 02:26:31 +0000 Message-Id: <541ED5DE-DB94-4C87-909B-D58663F0C967@recoil.org> References: <74C92A76-D99B-4F4A-9185-A6535FC3DC98@recoil.org> <0D4F644A-AEF6-43A7-BD13-89C52BD538A6@recoil.org> To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Mirage-WWW porting status X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8475221677676760682==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8475221677676760682== Content-Type: multipart/alternative; boundary="Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B" --Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 I've now released Mirage 1.0.3 to OPAM and put up a blog post: http://openmirage.org/blog/mirage-1.0.3-released There is a new wiki entry on how to build the website: http://openmirage.org/wiki/mirage-www Over to you for the decks.openmirage.org one, Mort! -anil On 18 Dec 2013, at 19:01, Anil Madhavapeddy wrote: > I've tagged a Mirage-1.0.3 in OPAM that contains all the fixes. Once = it goes through Travis, I'll test it over and update the website with it = and add a blog post. >=20 > -anil >=20 > On 18 Dec 2013, at 15:58, Anil Madhavapeddy wrote: >=20 >> Perfect, this works for me now with Mirage-WWW! >>=20 >> I've also fixed a build issue with the HTTP libraries, by splitting = them out into: >>=20 >> https://github.com/mirage/mirage-http-unix >> https://github.com/mirage/mirage-http-xen >>=20 >> See https://github.com/mirage/mirage/issues/161 for the details. >>=20 >> With all of this merged into OPAM shortly, Mirage 1.0.3 will be good = to be released, and will build the Mirage website in the following = modes: >>=20 >> - Unix: filesystem passthrough to make editing files locally easy >> - Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat >> - Xen: crunch filesystem >>=20 >> That's finally good enough for the blog post, yay! Only 3 days = late, a new Mirage record :-) >>=20 >> -anil >>=20 >> On 18 Dec 2013, at 12:52, David Scott wrote: >>=20 >>> Hi, >>>=20 >>> The problem reading files from a FAT filesystem turned out to be a = bug in mirage-block-unix: there was no mutex around calls to seek() and = read(), allowing two parallel threads to interleave badly. With this = fixed I was able to run a Unix mirage-www, and it all seemed to work. = I've tagged mirage-block-unix.1.2.0. >>>=20 >>> I've also sped up the construction of the FAT images via the 'fat' = command-line tool by making it use buffered I/O. I've tagged the new = faster-fat as 0.10.0. >>>=20 >>> Note the default Unix block device uses unbuffered I/O, the same as = xen. Some apps would clearly benefit from caching (like the webserver) = -- perhaps we should add an optional caching layer over KV_RO? >>>=20 >>> Cheers, >>> Dave >>>=20 >>>=20 >>> On Sun, Dec 15, 2013 at 7:26 PM, Anil Madhavapeddy = wrote: >>> I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request: >>> https://github.com/mirage/mirage-www/pull/56 >>>=20 >>> It was a fairly brute-force merge, but makes it much easier to break = up the old website into a cleaner one based on the Cowabloga library. >>>=20 >>> I then took a shot at recompiling the website to use a dynamic FAT = block device instead of the static crunch filesystem. This required a = few minor changes to libraries: >>>=20 >>> - Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160 >>> - Modify the Mirage command line to have a FAT_KV_RO option: = https://github.com/mirage/mirage/pull/160 >>> - Parameterise the Mirage-WWW config.ml to use either crunch or = static; https://github.com/mirage/mirage-www/pull/57 >>>=20 >>> This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet. >>>=20 >>> Once that's tracked down (hello Dave!), I can add a Unix_KV_RO = module too, and we'll have a pass-through to the filesystem to make it = easier to develop code without recompiling all the time. >>>=20 >>> TL;DR: blog post very soon, forgive the slight delay :-) >>>=20 >>> -anil >>> _______________________________________________ >>> MirageOS-devel mailing list >>> MirageOS-devel@lists.xenproject.org >>> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >>>=20 >>>=20 >>>=20 >>> --=20 >>> Dave Scott >>=20 >> _______________________________________________ >> MirageOS-devel mailing list >> MirageOS-devel@lists.xenproject.org >> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel >=20 > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 I've = now released Mirage 1.0.3 to OPAM and put up a blog post:

There is a = new wiki entry on how to build the website:

Over to you for the decks.openmirage.org one, = Mort!

-anil

On 18 Dec = 2013, at 19:01, Anil Madhavapeddy <anil@recoil.org> wrote:

I've = tagged a Mirage-1.0.3 in OPAM that contains all the fixes.  Once it = goes through Travis, I'll test it over and update the website with it = and add a blog post.

-anil

On = 18 Dec 2013, at 15:58, Anil Madhavapeddy <anil@recoil.org> wrote:

Perfect, this works for me now with = Mirage-WWW!

I've also fixed a build issue with the = HTTP libraries, by splitting them out into:



With all of this merged into OPAM = shortly, Mirage 1.0.3 will be good to be released, and will build the = Mirage website in the following modes:

- Unix: = filesystem passthrough to make editing files locally easy
- = Unix: FAT filesystem parsed in userspace via mmap/ocaml-fat
- = Xen: crunch filesystem

That's finally good = enough for the blog post,  yay!  Only 3 days late, a new = Mirage record = :-)

-anil

On 18 = Dec 2013, at 12:52, David Scott <scott.dj@gmail.com> = wrote:

Hi,

The problem = reading files from a FAT filesystem turned out to be a bug in mirage-block-unix: there was no mutex around calls to = seek() and read(), allowing two parallel threads to interleave badly. = With this fixed I was able to run a Unix mirage-www, and it all seemed to work. I've = tagged mirage-block-unix.1.2.0.

I've also sped up = the construction of the FAT images via the 'fat' command-line tool by = making it use buffered I/O. I've tagged the new faster-fat as = 0.10.0.

Note the default = Unix block device uses unbuffered I/O, the same as xen. Some apps would = clearly benefit from caching (like the webserver) -- perhaps we should = add an optional caching layer over KV_RO?

Cheers,
Dave


On Sun, Dec 15, 2013 at 7:26 PM, Anil = Madhavapeddy <anil@recoil.org> wrote:
I've been making good progress on porting Mirage/WWW to the 1.0 = libraries. The main website now compiles with 1.0 and crunch, with this = (now-merged) pull request:
https://github.com/mirage/mirage-www/pull/56

It was a fairly brute-force merge, but makes it much easier to break up = the old website into a cleaner one based on the Cowabloga library.

I then took a shot at recompiling the website to use a dynamic FAT block = device instead of the static crunch filesystem.  This required a = few minor changes to libraries:

- Add a KV_RO compatible mode to FAT which simplifies its normally = read/write FS interface: https://github.com/mirage/mirage/pull/160
- Modify the Mirage command line to have a FAT_KV_RO option: https://github.com/mirage/mirage/pull/160
- Parameterise the Mirage-WWW config.ml to use either crunch or static; https://github.com/mirage/mirage-www/pull/57

This plumbing was all pretty straightforward, but triggers a bug = somewhere in the FAT directory traversal, so the resulting website = doesn't actually read the files in FAT mode yet.

Once that's tracked down (hello Dave!), I can add a Unix_KV_RO module = too, and we'll have a pass-through to the filesystem to make it easier = to develop code without recompiling all the time.

TL;DR: blog post very soon, forgive the slight delay :-)

-anil
_______________________________________________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mir= ageos-devel



--
Dave = Scott
=

_______________________________________= ________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel=

___________________________________= ____________
MirageOS-devel mailing list
MirageOS-devel@lists.x= enproject.org
http://lists.xenproject.org/cgi-bin/mailman/listinfo/= mirageos-devel

= --Apple-Mail=_30F55C52-6668-44CE-BAE9-E2AA4BAC791B-- --===============8475221677676760682== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============8475221677676760682==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 02:30:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 02:30:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtprQ-0005bk-8N; Fri, 20 Dec 2013 02:30:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtprP-0005bd-Kw for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 02:30:43 +0000 Received: from [85.158.139.211:62087] by server-1.bemta-5.messagelabs.com id F2/A6-21065-2DBA3B25; Fri, 20 Dec 2013 02:30:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1387506641!5538025!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28450 invoked from network); 20 Dec 2013 02:30:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 20 Dec 2013 02:30:42 -0000 Received: (qmail 9198 invoked by uid 634); 20 Dec 2013 02:30:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Dec 2013 02:30:41 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 20 Dec 2013 02:30:40 +0000 Message-Id: <8818A288-A915-4279-B80A-825471E7549A@recoil.org> References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Jeremy Yallop , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 18 Dec 2013, at 14:38, Thomas Gazagnaire wrote: >>> Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): >>> >>> https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli >>> >>> File "lib/v1.mli", line 250, characters 4-23: >>> Error: This variant or record definition does not match that of type error >>> Their kinds differ. >>> Command exited with code 2. >> >> The simplest fix is to simply leave the error type abstract until the >> leaf module types. > > I've implemented that solution there: > > https://github.com/samoht/mirage-types/commit/98bf70a92cbbab5ba38d80f45f344a32c474864c This is looking much better! Would it be possible to separate out the various bits of the pull request though? - The V1 module type shouldn't have any interface breaking changes, as those can be reserved for V2 (and we can just bump all the dependent libraries at our leisure then to the new scheme). - Do we really need OASIS for this? -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 02:30:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 02:30:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtprQ-0005bk-8N; Fri, 20 Dec 2013 02:30:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtprP-0005bd-Kw for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 02:30:43 +0000 Received: from [85.158.139.211:62087] by server-1.bemta-5.messagelabs.com id F2/A6-21065-2DBA3B25; Fri, 20 Dec 2013 02:30:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-3.tower-206.messagelabs.com!1387506641!5538025!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 28450 invoked from network); 20 Dec 2013 02:30:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-3.tower-206.messagelabs.com with SMTP; 20 Dec 2013 02:30:42 -0000 Received: (qmail 9198 invoked by uid 634); 20 Dec 2013 02:30:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Dec 2013 02:30:41 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Fri, 20 Dec 2013 02:30:40 +0000 Message-Id: <8818A288-A915-4279-B80A-825471E7549A@recoil.org> References: <5539BF58-8684-41AF-8108-BDF4A2799F60@recoil.org> To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Jeremy Yallop , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] Module inclusion error in 4.01 X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 18 Dec 2013, at 14:38, Thomas Gazagnaire wrote: >>> Dave and I are seeing a new error with 4.01.0 with this standalone MLI file in mirage-types (it works with 4.00.1): >>> >>> https://raw.github.com/djs55/mirage-types/2634b03bcf99f0aba9696ede5a60bf8b67f0db30/lib/v1.mli >>> >>> File "lib/v1.mli", line 250, characters 4-23: >>> Error: This variant or record definition does not match that of type error >>> Their kinds differ. >>> Command exited with code 2. >> >> The simplest fix is to simply leave the error type abstract until the >> leaf module types. > > I've implemented that solution there: > > https://github.com/samoht/mirage-types/commit/98bf70a92cbbab5ba38d80f45f344a32c474864c This is looking much better! Would it be possible to separate out the various bits of the pull request though? - The V1 module type shouldn't have any interface breaking changes, as those can be reserved for V2 (and we can just bump all the dependent libraries at our leisure then to the new scheme). - Do we really need OASIS for this? -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:12:24 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:12:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzsL-0005zM-OZ; Fri, 20 Dec 2013 13:12:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzsK-0005z8-Hi for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:12:20 +0000 Received: from [85.158.143.35:21131] by server-2.bemta-4.messagelabs.com id DE/50-11386-33244B25; Fri, 20 Dec 2013 13:12:19 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1387545139!6082595!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19236 invoked from network); 20 Dec 2013 13:12:19 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 13:12:19 -0000 Received: by mail-wi0-f180.google.com with SMTP id hm19so3653963wib.7 for ; Fri, 20 Dec 2013 05:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=PGEtjNik1Mwli6uXDUrAgPnDeRpXPk9ubmsJqp/FesU=; b=pud7IxtxDv0O1Lhzhk6RgvwToZwsUp3yOE5USrrLD/fhv5CROKtoRPYhRTtW0KuXj1 hiOfhdtzB7Ch1dEexl9G474cuAZDay2dgi8aJUOs7IKStpQUvg2KOFPoG1w9SMNQ4r8A nC49C8KImBp0AMmyOEsL6+yR3qwiAf5LohvVfGQngzmPknzZYUYmGOeu91pwqaGXgwu6 uo8FMyUGcCiOgXQlSQj5YZHY6WcsALgHRh1t+6j2AcAyZoJ34czOTdUxy6q5ErTwSh2+ PzAbI74HGRkIfaBqHgKgbXv8Rsq/psHAYbAxNbw4OVcH3n3qI42AX/8Zs1c4nxzDiK/5 9lZw== X-Received: by 10.194.201.225 with SMTP id kd1mr6717548wjc.35.1387545139223; Fri, 20 Dec 2013 05:12:19 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id j3sm14579424wiy.3.2013.12.20.05.12.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Dec 2013 05:12:17 -0800 (PST) Message-ID: <52B44230.20209@xen.org> Date: Fri, 20 Dec 2013 13:12:16 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, I was just approached by a FOSS project which we have ties with, and it is possible that we can have some space (including sponsored food) on the 31st of Jan in Brussells to collaborate with other projects. If we get enough people who would be interested to attend, I will help coorganize it. If you would go, please reply +1. Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:12:24 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:12:24 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzsL-0005zM-OZ; Fri, 20 Dec 2013 13:12:21 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzsK-0005z8-Hi for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:12:20 +0000 Received: from [85.158.143.35:21131] by server-2.bemta-4.messagelabs.com id DE/50-11386-33244B25; Fri, 20 Dec 2013 13:12:19 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-13.tower-21.messagelabs.com!1387545139!6082595!1 X-Originating-IP: [209.85.212.180] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19236 invoked from network); 20 Dec 2013 13:12:19 -0000 Received: from mail-wi0-f180.google.com (HELO mail-wi0-f180.google.com) (209.85.212.180) by server-13.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 13:12:19 -0000 Received: by mail-wi0-f180.google.com with SMTP id hm19so3653963wib.7 for ; Fri, 20 Dec 2013 05:12:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=PGEtjNik1Mwli6uXDUrAgPnDeRpXPk9ubmsJqp/FesU=; b=pud7IxtxDv0O1Lhzhk6RgvwToZwsUp3yOE5USrrLD/fhv5CROKtoRPYhRTtW0KuXj1 hiOfhdtzB7Ch1dEexl9G474cuAZDay2dgi8aJUOs7IKStpQUvg2KOFPoG1w9SMNQ4r8A nC49C8KImBp0AMmyOEsL6+yR3qwiAf5LohvVfGQngzmPknzZYUYmGOeu91pwqaGXgwu6 uo8FMyUGcCiOgXQlSQj5YZHY6WcsALgHRh1t+6j2AcAyZoJ34czOTdUxy6q5ErTwSh2+ PzAbI74HGRkIfaBqHgKgbXv8Rsq/psHAYbAxNbw4OVcH3n3qI42AX/8Zs1c4nxzDiK/5 9lZw== X-Received: by 10.194.201.225 with SMTP id kd1mr6717548wjc.35.1387545139223; Fri, 20 Dec 2013 05:12:19 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id j3sm14579424wiy.3.2013.12.20.05.12.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 20 Dec 2013 05:12:17 -0800 (PST) Message-ID: <52B44230.20209@xen.org> Date: Fri, 20 Dec 2013 13:12:16 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi all, I was just approached by a FOSS project which we have ties with, and it is possible that we can have some space (including sponsored food) on the 31st of Jan in Brussells to collaborate with other projects. If we get enough people who would be interested to attend, I will help coorganize it. If you would go, please reply +1. Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:17:28 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:17:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzxI-0006Xw-FE; Fri, 20 Dec 2013 13:17:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzvg-0006Cs-AG for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:15:48 +0000 Received: from [85.158.143.35:64369] by server-1.bemta-4.messagelabs.com id D0/35-02132-30344B25; Fri, 20 Dec 2013 13:15:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1387545345!7271019!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13642 invoked from network); 20 Dec 2013 13:15:46 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 13:15:46 -0000 X-IronPort-AV: E=Sophos;i="4.95,520,1384300800"; d="scan'208";a="86537060" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 20 Dec 2013 13:15:45 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Fri, 20 Dec 2013 08:15:44 -0500 Message-ID: <1387545343.17289.73.camel@kazak.uk.xensource.com> From: Ian Campbell To: Date: Fri, 20 Dec 2013 13:15:43 +0000 In-Reply-To: <52B44230.20209@xen.org> References: <52B44230.20209@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Fri, 20 Dec 2013 13:17:28 +0000 Cc: "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Fri, 2013-12-20 at 13:12 +0000, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and it > is possible that we can have some space (including sponsored food) on > the 31st of Jan in Brussells to collaborate with other projects. If we > get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. +1 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:17:28 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:17:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzxI-0006Y1-H1; Fri, 20 Dec 2013 13:17:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzwr-0006RK-GG for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:17:01 +0000 Received: from [85.158.143.35:16739] by server-3.bemta-4.messagelabs.com id 47/58-32360-C4344B25; Fri, 20 Dec 2013 13:17:00 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1387545420!226064!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8765 invoked from network); 20 Dec 2013 13:17:00 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 13:17:00 -0000 Received: by mail-wi0-f171.google.com with SMTP id bz8so8340639wib.16 for ; Fri, 20 Dec 2013 05:17:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tKaXxmUTt81Uq/NuF6a0U85CKUBbZqTqEbO7eUQK1A4=; b=RzDrx6kTQNNiShL+IGK1ghBGaWA2c1nqyy8tA9gs3FkgChXqepqjq5bXXPxdR2Swpy 3SUH/q8B7pHnnveC/bGlnTYnbBi1GXwRQbS1KmSXYhiGawyRJdj4fJIxuxYEJkInM7eg Ii8Zn6zOGFv6HYpvEr1+AkqjTYvD2n+dJpCDqUCn4aVg2+3JZThlwMDYAFcm/xchBguz qZC+WvLCYLGc0tzCmkya0GTW33Auvj9PTeadZ8HNDfSSO5slhd+xpKpZn5FlHEwp6hRb fTay6BugbdcHilhRS4fywJJzx7TciFxkBQIeEBHna9VdUAKTtYOnhnclWrwg1ONLkY8e TNUw== MIME-Version: 1.0 X-Received: by 10.180.73.173 with SMTP id m13mr7826518wiv.28.1387545420040; Fri, 20 Dec 2013 05:17:00 -0800 (PST) Received: by 10.194.242.162 with HTTP; Fri, 20 Dec 2013 05:16:59 -0800 (PST) In-Reply-To: <52B44230.20209@xen.org> References: <52B44230.20209@xen.org> Date: Fri, 20 Dec 2013 13:16:59 +0000 X-Google-Sender-Auth: XTYTgbW1Q_uwbsu0KxwaZPgjMVg Message-ID: From: George Dunlap To: Lars Kurth X-Mailman-Approved-At: Fri, 20 Dec 2013 13:17:28 +0000 Cc: "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Fri, Dec 20, 2013 at 1:12 PM, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and it is > possible that we can have some space (including sponsored food) on the 31st > of Jan in Brussells to collaborate with other projects. If we get enough > people who would be interested to attend, I will help coorganize it. If you > would go, please reply +1. I'd be game -- obviously contingent on getting budget approval... +1 -George _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:17:28 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:17:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzxI-0006Xw-FE; Fri, 20 Dec 2013 13:17:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzvg-0006Cs-AG for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:15:48 +0000 Received: from [85.158.143.35:64369] by server-1.bemta-4.messagelabs.com id D0/35-02132-30344B25; Fri, 20 Dec 2013 13:15:47 +0000 X-Env-Sender: Ian.Campbell@citrix.com X-Msg-Ref: server-7.tower-21.messagelabs.com!1387545345!7271019!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13642 invoked from network); 20 Dec 2013 13:15:46 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-7.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 13:15:46 -0000 X-IronPort-AV: E=Sophos;i="4.95,520,1384300800"; d="scan'208";a="86537060" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 20 Dec 2013 13:15:45 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Fri, 20 Dec 2013 08:15:44 -0500 Message-ID: <1387545343.17289.73.camel@kazak.uk.xensource.com> From: Ian Campbell To: Date: Fri, 20 Dec 2013 13:15:43 +0000 In-Reply-To: <52B44230.20209@xen.org> References: <52B44230.20209@xen.org> Organization: Citrix Systems, Inc. X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 X-Originating-IP: [10.80.2.80] X-DLP: MIA1 X-Mailman-Approved-At: Fri, 20 Dec 2013 13:17:28 +0000 Cc: "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Fri, 2013-12-20 at 13:12 +0000, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and it > is possible that we can have some space (including sponsored food) on > the 31st of Jan in Brussells to collaborate with other projects. If we > get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. +1 _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:17:28 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:17:28 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VtzxI-0006Y1-H1; Fri, 20 Dec 2013 13:17:28 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzwr-0006RK-GG for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:17:01 +0000 Received: from [85.158.143.35:16739] by server-3.bemta-4.messagelabs.com id 47/58-32360-C4344B25; Fri, 20 Dec 2013 13:17:00 +0000 X-Env-Sender: dunlapg@gmail.com X-Msg-Ref: server-6.tower-21.messagelabs.com!1387545420!226064!1 X-Originating-IP: [209.85.212.171] X-SpamReason: No, hits=0.3 required=7.0 tests=RCVD_BY_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 8765 invoked from network); 20 Dec 2013 13:17:00 -0000 Received: from mail-wi0-f171.google.com (HELO mail-wi0-f171.google.com) (209.85.212.171) by server-6.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 13:17:00 -0000 Received: by mail-wi0-f171.google.com with SMTP id bz8so8340639wib.16 for ; Fri, 20 Dec 2013 05:17:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=tKaXxmUTt81Uq/NuF6a0U85CKUBbZqTqEbO7eUQK1A4=; b=RzDrx6kTQNNiShL+IGK1ghBGaWA2c1nqyy8tA9gs3FkgChXqepqjq5bXXPxdR2Swpy 3SUH/q8B7pHnnveC/bGlnTYnbBi1GXwRQbS1KmSXYhiGawyRJdj4fJIxuxYEJkInM7eg Ii8Zn6zOGFv6HYpvEr1+AkqjTYvD2n+dJpCDqUCn4aVg2+3JZThlwMDYAFcm/xchBguz qZC+WvLCYLGc0tzCmkya0GTW33Auvj9PTeadZ8HNDfSSO5slhd+xpKpZn5FlHEwp6hRb fTay6BugbdcHilhRS4fywJJzx7TciFxkBQIeEBHna9VdUAKTtYOnhnclWrwg1ONLkY8e TNUw== MIME-Version: 1.0 X-Received: by 10.180.73.173 with SMTP id m13mr7826518wiv.28.1387545420040; Fri, 20 Dec 2013 05:17:00 -0800 (PST) Received: by 10.194.242.162 with HTTP; Fri, 20 Dec 2013 05:16:59 -0800 (PST) In-Reply-To: <52B44230.20209@xen.org> References: <52B44230.20209@xen.org> Date: Fri, 20 Dec 2013 13:16:59 +0000 X-Google-Sender-Auth: XTYTgbW1Q_uwbsu0KxwaZPgjMVg Message-ID: From: George Dunlap To: Lars Kurth X-Mailman-Approved-At: Fri, 20 Dec 2013 13:17:28 +0000 Cc: "xen-api@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On Fri, Dec 20, 2013 at 1:12 PM, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and it is > possible that we can have some space (including sponsored food) on the 31st > of Jan in Brussells to collaborate with other projects. If we get enough > people who would be interested to attend, I will help coorganize it. If you > would go, please reply +1. I'd be game -- obviously contingent on getting budget approval... +1 -George _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:17:58 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:17:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzxm-0006fp-Ti; Fri, 20 Dec 2013 13:17:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzxk-0006ew-Ng for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:17:56 +0000 Received: from [85.158.137.68:26945] by server-3.bemta-3.messagelabs.com id 16/9C-10658-38344B25; Fri, 20 Dec 2013 13:17:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1387545475!5269701!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17060 invoked from network); 20 Dec 2013 13:17:55 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-31.messagelabs.com with SMTP; 20 Dec 2013 13:17:55 -0000 Received: (qmail 28529 invoked by uid 634); 20 Dec 2013 13:17:54 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Dec 2013 13:17:54 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1387545343.17289.73.camel@kazak.uk.xensource.com> Date: Fri, 20 Dec 2013 13:17:52 +0000 Message-Id: <3308CE87-0E7D-4621-8296-B707AFE4A913@recoil.org> References: <52B44230.20209@xen.org> <1387545343.17289.73.camel@kazak.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-devel@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 20 Dec 2013, at 13:15, Ian Campbell wrote: > On Fri, 2013-12-20 at 13:12 +0000, Lars Kurth wrote: >> Hi all, >> I was just approached by a FOSS project which we have ties with, and it >> is possible that we can have some space (including sponsored food) on >> the 31st of Jan in Brussells to collaborate with other projects. If we >> get enough people who would be interested to attend, I will help >> coorganize it. If you would go, please reply +1. > > +1 +1 from me too. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 13:17:58 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 13:17:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzxm-0006fp-Ti; Fri, 20 Dec 2013 13:17:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vtzxk-0006ew-Ng for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 13:17:56 +0000 Received: from [85.158.137.68:26945] by server-3.bemta-3.messagelabs.com id 16/9C-10658-38344B25; Fri, 20 Dec 2013 13:17:55 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-6.tower-31.messagelabs.com!1387545475!5269701!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 17060 invoked from network); 20 Dec 2013 13:17:55 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-6.tower-31.messagelabs.com with SMTP; 20 Dec 2013 13:17:55 -0000 Received: (qmail 28529 invoked by uid 634); 20 Dec 2013 13:17:54 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 20 Dec 2013 13:17:54 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <1387545343.17289.73.camel@kazak.uk.xensource.com> Date: Fri, 20 Dec 2013 13:17:52 +0000 Message-Id: <3308CE87-0E7D-4621-8296-B707AFE4A913@recoil.org> References: <52B44230.20209@xen.org> <1387545343.17289.73.camel@kazak.uk.xensource.com> To: Ian Campbell X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "xen-devel@lists.xen.org" , mirageos-devel@lists.xenproject.org, "xen-api@lists.xen.org" Subject: Re: [MirageOS-devel] [Xen-API] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 20 Dec 2013, at 13:15, Ian Campbell wrote: > On Fri, 2013-12-20 at 13:12 +0000, Lars Kurth wrote: >> Hi all, >> I was just approached by a FOSS project which we have ties with, and it >> is possible that we can have some space (including sponsored food) on >> the 31st of Jan in Brussells to collaborate with other projects. If we >> get enough people who would be interested to attend, I will help >> coorganize it. If you would go, please reply +1. > > +1 +1 from me too. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 16:03:31 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 16:03:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu2Xu-000658-UC; Fri, 20 Dec 2013 16:03:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu2Xt-000653-Re for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 16:03:26 +0000 Received: from [193.109.254.147:55534] by server-13.bemta-14.messagelabs.com id 3D/BD-19374-D4A64B25; Fri, 20 Dec 2013 16:03:25 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1387555402!6721167!1 X-Originating-IP: [209.85.192.180] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13799 invoked from network); 20 Dec 2013 16:03:24 -0000 Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com) (209.85.192.180) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 16:03:24 -0000 Received: by mail-pd0-f180.google.com with SMTP id q10so2685223pdj.25 for ; Fri, 20 Dec 2013 08:03:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=POLIiDsiECMpGNnccqShV5WWfmGc5Da01HYYYL9tx5Y=; b=f/FfBi1DBfWvlbkUH4gTCwXmJoD1ZQ0JPsdLmFo15TyRGP5C44Ii8JJj7S1GjUvQV3 ylNQ6H6QenANnvBwsR0cFh9+A5O753ijoOCv7Yi3tH0q47pfafaVXkVHTB803oY8quxX 76oszUDekuCDj/z9YodF61+wk92qBSaAWG9U0hoxoVsrrlgtxieyO65FuqFxQdV5FvIK zFhzUaUMhRt9xnks6KJ1dPeq5glEdHO11WWYivsJikSJm6fBd8SMdJnIKon0BEzaDRPi 2Bz8kb+WmY7VaSSyFCpBWOcO7bPetZ5QnNl8d70T6FVlWHP+4vs5w7RAmCH6f6cf+TCO sxTw== MIME-Version: 1.0 X-Received: by 10.66.25.36 with SMTP id z4mr9452620paf.101.1387555402023; Fri, 20 Dec 2013 08:03:22 -0800 (PST) Received: by 10.70.61.136 with HTTP; Fri, 20 Dec 2013 08:03:21 -0800 (PST) Date: Fri, 20 Dec 2013 16:03:21 +0000 Message-ID: From: David Scott To: mirageos-devel@lists.xenproject.org, Jon Ludlam Subject: [MirageOS-devel] (LVM compatible) block volume manager library X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8044879669022707194==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8044879669022707194== Content-Type: multipart/alternative; boundary=bcaec52be999d8138104edf96ae6 --bcaec52be999d8138104edf96ae6 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've added a new repo: https://github.com/mirage/mirage-block-volume which contains a "logical volume manager" for Mirage. This library allows you to combine multiple physical volumes (disks) into a large pool of blocks, from which you can allocate independent logical volumes. The library aims to use the same on-disk format as Linux LVM, so you could also use it for manipulating/ visualising/ repairing broken metadata or disks. The library is partially functorised over the mirage-types V1.BLOCK signature. The command-line tool therefore uses mirage-block-unix. The interface isn't stable (and I may have broken the Linux LVM compatibility) but I'm working on it. The code was all originally written by Jon Ludlam, I've only done the Mirage port (and probably introduced the bugs) Cheers, Dave --bcaec52be999d8138104edf96ae6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I've added a new repo:


= which contains a "logical volume manager" for Mirage. This librar= y allows you to combine multiple physical volumes (disks) into a large pool= of blocks, from which you can allocate independent logical volumes. The li= brary aims to use the same on-disk format as Linux LVM, so you could also u= se it for manipulating/ visualising/ repairing broken metadata or disks.

The library is partially functorised over the mirage-ty= pes V1.BLOCK signature. The command-line tool therefore uses mirage-block-u= nix.

The interface isn't stable (and I may hav= e broken the Linux LVM compatibility) but I'm working on it.

The code was all originally written by Jon Ludlam, I= 9;ve only done the Mirage port (and probably introduced the bugs)

Cheers,
Dave
--bcaec52be999d8138104edf96ae6-- --===============8044879669022707194== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============8044879669022707194==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 16:03:31 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 16:03:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu2Xu-000658-UC; Fri, 20 Dec 2013 16:03:26 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu2Xt-000653-Re for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 16:03:26 +0000 Received: from [193.109.254.147:55534] by server-13.bemta-14.messagelabs.com id 3D/BD-19374-D4A64B25; Fri, 20 Dec 2013 16:03:25 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-5.tower-27.messagelabs.com!1387555402!6721167!1 X-Originating-IP: [209.85.192.180] X-SpamReason: No, hits=1.2 required=7.0 tests=HTML_20_30,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 13799 invoked from network); 20 Dec 2013 16:03:24 -0000 Received: from mail-pd0-f180.google.com (HELO mail-pd0-f180.google.com) (209.85.192.180) by server-5.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 16:03:24 -0000 Received: by mail-pd0-f180.google.com with SMTP id q10so2685223pdj.25 for ; Fri, 20 Dec 2013 08:03:22 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=POLIiDsiECMpGNnccqShV5WWfmGc5Da01HYYYL9tx5Y=; b=f/FfBi1DBfWvlbkUH4gTCwXmJoD1ZQ0JPsdLmFo15TyRGP5C44Ii8JJj7S1GjUvQV3 ylNQ6H6QenANnvBwsR0cFh9+A5O753ijoOCv7Yi3tH0q47pfafaVXkVHTB803oY8quxX 76oszUDekuCDj/z9YodF61+wk92qBSaAWG9U0hoxoVsrrlgtxieyO65FuqFxQdV5FvIK zFhzUaUMhRt9xnks6KJ1dPeq5glEdHO11WWYivsJikSJm6fBd8SMdJnIKon0BEzaDRPi 2Bz8kb+WmY7VaSSyFCpBWOcO7bPetZ5QnNl8d70T6FVlWHP+4vs5w7RAmCH6f6cf+TCO sxTw== MIME-Version: 1.0 X-Received: by 10.66.25.36 with SMTP id z4mr9452620paf.101.1387555402023; Fri, 20 Dec 2013 08:03:22 -0800 (PST) Received: by 10.70.61.136 with HTTP; Fri, 20 Dec 2013 08:03:21 -0800 (PST) Date: Fri, 20 Dec 2013 16:03:21 +0000 Message-ID: From: David Scott To: mirageos-devel@lists.xenproject.org, Jon Ludlam Subject: [MirageOS-devel] (LVM compatible) block volume manager library X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============8044879669022707194==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============8044879669022707194== Content-Type: multipart/alternative; boundary=bcaec52be999d8138104edf96ae6 --bcaec52be999d8138104edf96ae6 Content-Type: text/plain; charset=ISO-8859-1 Hi, I've added a new repo: https://github.com/mirage/mirage-block-volume which contains a "logical volume manager" for Mirage. This library allows you to combine multiple physical volumes (disks) into a large pool of blocks, from which you can allocate independent logical volumes. The library aims to use the same on-disk format as Linux LVM, so you could also use it for manipulating/ visualising/ repairing broken metadata or disks. The library is partially functorised over the mirage-types V1.BLOCK signature. The command-line tool therefore uses mirage-block-unix. The interface isn't stable (and I may have broken the Linux LVM compatibility) but I'm working on it. The code was all originally written by Jon Ludlam, I've only done the Mirage port (and probably introduced the bugs) Cheers, Dave --bcaec52be999d8138104edf96ae6 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I've added a new repo:


= which contains a "logical volume manager" for Mirage. This librar= y allows you to combine multiple physical volumes (disks) into a large pool= of blocks, from which you can allocate independent logical volumes. The li= brary aims to use the same on-disk format as Linux LVM, so you could also u= se it for manipulating/ visualising/ repairing broken metadata or disks.

The library is partially functorised over the mirage-ty= pes V1.BLOCK signature. The command-line tool therefore uses mirage-block-u= nix.

The interface isn't stable (and I may hav= e broken the Linux LVM compatibility) but I'm working on it.

The code was all originally written by Jon Ludlam, I= 9;ve only done the Mirage port (and probably introduced the bugs)

Cheers,
Dave
--bcaec52be999d8138104edf96ae6-- --===============8044879669022707194== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============8044879669022707194==-- From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 19:06:31 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 19:06:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu5P1-0004TS-65; Fri, 20 Dec 2013 19:06:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu5Oz-0004TG-S5 for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 19:06:25 +0000 Received: from [85.158.143.35:24702] by server-3.bemta-4.messagelabs.com id 70/CA-32360-13594B25; Fri, 20 Dec 2013 19:06:25 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1387566383!7431566!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31580 invoked from network); 20 Dec 2013 19:06:24 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 19:06:24 -0000 X-IronPort-AV: E=Sophos;i="4.95,522,1384300800"; d="scan'208";a="84448263" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 20 Dec 2013 19:06:22 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Fri, 20 Dec 2013 14:06:21 -0500 Message-ID: <52B49506.4080702@citrix.com> Date: Fri, 20 Dec 2013 20:05:42 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , References: <52B44230.20209@xen.org> In-Reply-To: <52B44230.20209@xen.org> X-Enigmail-Version: 1.6 X-DLP: MIA1 Subject: Re: [MirageOS-devel] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 20/12/13 14:12, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and it > is possible that we can have some space (including sponsored food) on > the 31st of Jan in Brussells to collaborate with other projects. If we > get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. +1 Roger. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 20 19:06:31 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 20 Dec 2013 19:06:31 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu5P1-0004TS-65; Fri, 20 Dec 2013 19:06:27 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vu5Oz-0004TG-S5 for mirageos-devel@lists.xenproject.org; Fri, 20 Dec 2013 19:06:25 +0000 Received: from [85.158.143.35:24702] by server-3.bemta-4.messagelabs.com id 70/CA-32360-13594B25; Fri, 20 Dec 2013 19:06:25 +0000 X-Env-Sender: roger.pau@citrix.com X-Msg-Ref: server-4.tower-21.messagelabs.com!1387566383!7431566!1 X-Originating-IP: [66.165.176.63] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni42MyA9PiAzMDYwNDg=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 31580 invoked from network); 20 Dec 2013 19:06:24 -0000 Received: from smtp02.citrix.com (HELO SMTP02.CITRIX.COM) (66.165.176.63) by server-4.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 20 Dec 2013 19:06:24 -0000 X-IronPort-AV: E=Sophos;i="4.95,522,1384300800"; d="scan'208";a="84448263" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 20 Dec 2013 19:06:22 +0000 Received: from [IPv6:::1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Fri, 20 Dec 2013 14:06:21 -0500 Message-ID: <52B49506.4080702@citrix.com> Date: Fri, 20 Dec 2013 20:05:42 +0100 From: =?ISO-8859-1?Q?Roger_Pau_Monn=E9?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: , "xen-devel@lists.xen.org" , "xen-api@lists.xen.org" , References: <52B44230.20209@xen.org> In-Reply-To: <52B44230.20209@xen.org> X-Enigmail-Version: 1.6 X-DLP: MIA1 Subject: Re: [MirageOS-devel] [Xen-devel] Pre FOSDEM Hackathon [Urgent, please vote] X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 20/12/13 14:12, Lars Kurth wrote: > Hi all, > I was just approached by a FOSS project which we have ties with, and it > is possible that we can have some space (including sponsored food) on > the 31st of Jan in Brussells to collaborate with other projects. If we > get enough people who would be interested to attend, I will help > coorganize it. If you would go, please reply +1. +1 Roger. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 12:00:05 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 12:00:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4Aw-00024H-H3; Mon, 23 Dec 2013 11:59:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4Av-00024C-Ik for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 11:59:57 +0000 Received: from [85.158.137.68:64262] by server-9.bemta-3.messagelabs.com id EB/C9-13104-CB528B25; Mon, 23 Dec 2013 11:59:56 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1387799995!4526124!1 X-Originating-IP: [151.236.209.34] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20480 invoked from network); 23 Dec 2013 11:59:55 -0000 Received: from engine01-20433-9.icritical.com (HELO engine01-20433-9.icritical.com) (151.236.209.34) by server-10.tower-31.messagelabs.com with SMTP; 23 Dec 2013 11:59:55 -0000 Received: (qmail 29760 invoked from network); 23 Dec 2013 11:59:48 -0000 Received: from localhost (127.0.0.1) by engine01-20433-9.icritical.com with SMTP; 23 Dec 2013 11:59:48 -0000 Received: from engine01-20433-9.icritical.com ([127.0.0.1]) by localhost (engine01-20433-9.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 29499-09 for ; Mon, 23 Dec 2013 11:59:46 +0000 (GMT) Received: (qmail 29704 invoked by uid 599); 23 Dec 2013 11:59:42 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-9.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 11:59:42 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vv4Am-0003hq-1U for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 11:59:48 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Mon, 23 Dec 2013 11:59:46 +0000 Thread-Topic: using cow Thread-Index: Ac7/1nn8q8DhL5WBR/uuF4QAoX8UOw== Message-ID: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-9.icritical.com Subject: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org i'm having a few issues using cow to recreate mirage-decks and wonder whether i'm missing something really obvious. code at . each slideshow on decks is served up using reveal.js which itself ends up using an in-browser markdown renderer to render slides from markdown fragments between
tags. at the moment, each deck is in its own directory containing an (incomplete) index.html file which contains the slides as
fragments plus all the images referred to. when a deck is requested i then read the relevant index.html file in, and insert it into a template which is an <:html< ... >> fragment. it's this insertion that's causing me problems. if i insert into the template as the anti-qutoation $str:deck$ then all the html in deck is escaped (< becomes < etc). obviously this doesn't render correctly. if i read in the index.html and parse it, then i can insert as $deck$ and that works but it's meant i've needed to do a fair amount of tidying up of the index.html files for all the slide decks to get past cow's parser. so-- is there a way to say "just insert this string verbatim" in a quotation (or anti-quotation or whatever the things between $$ are called in cow)? fwiw i've had similar issues with literal js between tags which i've overcome by pulling it out into a file and then serving that appropriately. i could probably do something similar here by just having the template as html fragments that are manually prepended/appended, but that feels like a kludge -- given that type-checking is good, being able to typecheck the template as valid html, even if i can't type-check the entire page, seems a good thing... :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 12:00:05 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 12:00:05 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4Aw-00024H-H3; Mon, 23 Dec 2013 11:59:58 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4Av-00024C-Ik for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 11:59:57 +0000 Received: from [85.158.137.68:64262] by server-9.bemta-3.messagelabs.com id EB/C9-13104-CB528B25; Mon, 23 Dec 2013 11:59:56 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-10.tower-31.messagelabs.com!1387799995!4526124!1 X-Originating-IP: [151.236.209.34] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20480 invoked from network); 23 Dec 2013 11:59:55 -0000 Received: from engine01-20433-9.icritical.com (HELO engine01-20433-9.icritical.com) (151.236.209.34) by server-10.tower-31.messagelabs.com with SMTP; 23 Dec 2013 11:59:55 -0000 Received: (qmail 29760 invoked from network); 23 Dec 2013 11:59:48 -0000 Received: from localhost (127.0.0.1) by engine01-20433-9.icritical.com with SMTP; 23 Dec 2013 11:59:48 -0000 Received: from engine01-20433-9.icritical.com ([127.0.0.1]) by localhost (engine01-20433-9.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 29499-09 for ; Mon, 23 Dec 2013 11:59:46 +0000 (GMT) Received: (qmail 29704 invoked by uid 599); 23 Dec 2013 11:59:42 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-9.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 11:59:42 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vv4Am-0003hq-1U for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 11:59:48 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Mon, 23 Dec 2013 11:59:46 +0000 Thread-Topic: using cow Thread-Index: Ac7/1nn8q8DhL5WBR/uuF4QAoX8UOw== Message-ID: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-9.icritical.com Subject: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org i'm having a few issues using cow to recreate mirage-decks and wonder whether i'm missing something really obvious. code at . each slideshow on decks is served up using reveal.js which itself ends up using an in-browser markdown renderer to render slides from markdown fragments between
tags. at the moment, each deck is in its own directory containing an (incomplete) index.html file which contains the slides as
fragments plus all the images referred to. when a deck is requested i then read the relevant index.html file in, and insert it into a template which is an <:html< ... >> fragment. it's this insertion that's causing me problems. if i insert into the template as the anti-qutoation $str:deck$ then all the html in deck is escaped (< becomes < etc). obviously this doesn't render correctly. if i read in the index.html and parse it, then i can insert as $deck$ and that works but it's meant i've needed to do a fair amount of tidying up of the index.html files for all the slide decks to get past cow's parser. so-- is there a way to say "just insert this string verbatim" in a quotation (or anti-quotation or whatever the things between $$ are called in cow)? fwiw i've had similar issues with literal js between tags which i've overcome by pulling it out into a file and then serving that appropriately. i could probably do something similar here by just having the template as html fragments that are manually prepended/appended, but that feels like a kludge -- given that type-checking is good, being able to typecheck the template as valid html, even if i can't type-check the entire page, seems a good thing... :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 12:32:02 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 12:32:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4fw-0003WS-A3; Mon, 23 Dec 2013 12:32:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4fu-0003WN-FM for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 12:31:58 +0000 Received: from [193.109.254.147:40042] by server-7.bemta-14.messagelabs.com id 55/71-15500-D3D28B25; Mon, 23 Dec 2013 12:31:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-27.messagelabs.com!1387801916!7121595!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19460 invoked from network); 23 Dec 2013 12:31:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-27.messagelabs.com with SMTP; 23 Dec 2013 12:31:56 -0000 Received: (qmail 30454 invoked by uid 634); 23 Dec 2013 12:31:56 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 12:31:55 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> Date: Mon, 23 Dec 2013 12:31:52 +0000 Message-Id: <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 11:59, Richard Mortier wrote: > i'm having a few issues using cow to recreate mirage-decks and wonder whether i'm missing something really obvious. code at . > > each slideshow on decks is served up using reveal.js which itself ends up using an in-browser markdown renderer to render slides from markdown fragments between
tags. > > at the moment, each deck is in its own directory containing an (incomplete) index.html file which contains the slides as
fragments plus all the images referred to. when a deck is requested i then read the relevant index.html file in, and insert it into a template which is an <:html< ... >> fragment. > > it's this insertion that's causing me problems. if i insert into the template as the anti-qutoation $str:deck$ then all the html in deck is escaped (< becomes < etc). obviously this doesn't render correctly. if i read in the index.html and parse it, then i can insert as $deck$ and that works but it's meant i've needed to do a fair amount of tidying up of the index.html files for all the slide decks to get past cow's parser. > > so-- is there a way to say "just insert this string verbatim" in a quotation (or anti-quotation or whatever the things between $$ are called in cow)? You can't insert the string verbatim, as the type of the $$ must be a Cow.Xml.t. The whole point of $str:$ is to take care of escaping. However, you should be able to just parse the template fragment into Cow.Xml.t and insert it as such. I'm guessing it doesn't parse because of... > fwiw i've had similar issues with literal js between tags which i've overcome by pulling it out into a file and then serving that appropriately. i could probably do something similar here by just having the template as html fragments that are manually prepended/appended, but that feels like a kludge -- given that type-checking is good, being able to typecheck the template as valid html, even if i can't type-check the entire page, seems a good thing... :) And here you hit the biggest drawback with Cow's parser: the $ anti-quotations mean that there's no way to escape them (that I know of). So if you have: <:html< >> You need insert the dollar without typing it in. I use this: let d = [`Data "$"] <:html< >> Alternatively, you could make it valid XHTML by wrapping it in a CDATA. <:html< // var foo = $bar; //]]> >> The latter is probably the best solution, since we serve the MIME type as XHTML anyway. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 12:32:02 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 12:32:02 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4fw-0003WS-A3; Mon, 23 Dec 2013 12:32:00 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv4fu-0003WN-FM for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 12:31:58 +0000 Received: from [193.109.254.147:40042] by server-7.bemta-14.messagelabs.com id 55/71-15500-D3D28B25; Mon, 23 Dec 2013 12:31:57 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-27.messagelabs.com!1387801916!7121595!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 19460 invoked from network); 23 Dec 2013 12:31:56 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-27.messagelabs.com with SMTP; 23 Dec 2013 12:31:56 -0000 Received: (qmail 30454 invoked by uid 634); 23 Dec 2013 12:31:56 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 12:31:55 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> Date: Mon, 23 Dec 2013 12:31:52 +0000 Message-Id: <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 11:59, Richard Mortier wrote: > i'm having a few issues using cow to recreate mirage-decks and wonder whether i'm missing something really obvious. code at . > > each slideshow on decks is served up using reveal.js which itself ends up using an in-browser markdown renderer to render slides from markdown fragments between
tags. > > at the moment, each deck is in its own directory containing an (incomplete) index.html file which contains the slides as
fragments plus all the images referred to. when a deck is requested i then read the relevant index.html file in, and insert it into a template which is an <:html< ... >> fragment. > > it's this insertion that's causing me problems. if i insert into the template as the anti-qutoation $str:deck$ then all the html in deck is escaped (< becomes < etc). obviously this doesn't render correctly. if i read in the index.html and parse it, then i can insert as $deck$ and that works but it's meant i've needed to do a fair amount of tidying up of the index.html files for all the slide decks to get past cow's parser. > > so-- is there a way to say "just insert this string verbatim" in a quotation (or anti-quotation or whatever the things between $$ are called in cow)? You can't insert the string verbatim, as the type of the $$ must be a Cow.Xml.t. The whole point of $str:$ is to take care of escaping. However, you should be able to just parse the template fragment into Cow.Xml.t and insert it as such. I'm guessing it doesn't parse because of... > fwiw i've had similar issues with literal js between tags which i've overcome by pulling it out into a file and then serving that appropriately. i could probably do something similar here by just having the template as html fragments that are manually prepended/appended, but that feels like a kludge -- given that type-checking is good, being able to typecheck the template as valid html, even if i can't type-check the entire page, seems a good thing... :) And here you hit the biggest drawback with Cow's parser: the $ anti-quotations mean that there's no way to escape them (that I know of). So if you have: <:html< >> You need insert the dollar without typing it in. I use this: let d = [`Data "$"] <:html< >> Alternatively, you could make it valid XHTML by wrapping it in a CDATA. <:html< // var foo = $bar; //]]> >> The latter is probably the best solution, since we serve the MIME type as XHTML anyway. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 14:56:46 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 14:56:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv6vz-00008P-7r; Mon, 23 Dec 2013 14:56:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv6vy-00008K-23 for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 14:56:42 +0000 Received: from [85.158.139.211:9934] by server-13.bemta-5.messagelabs.com id 1F/2E-11357-92F48B25; Mon, 23 Dec 2013 14:56:41 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-206.messagelabs.com!1387810600!6274595!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 885 invoked from network); 23 Dec 2013 14:56:40 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-14.tower-206.messagelabs.com with SMTP; 23 Dec 2013 14:56:40 -0000 Received: (qmail 2211 invoked from network); 23 Dec 2013 14:56:34 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 23 Dec 2013 14:56:34 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 01608-07 for ; Mon, 23 Dec 2013 14:56:32 +0000 (GMT) Received: (qmail 2199 invoked by uid 599); 23 Dec 2013 14:56:32 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 14:56:32 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vv6vs-000701-Js; Mon, 23 Dec 2013 14:56:36 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 14:56:35 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac7/7yzfyyVSfixBRwKv0wIpjV3upA== Message-ID: References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> In-Reply-To: <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 12:31, Anil Madhavapeddy wrote: > You can't insert the string verbatim, as the type of the $$ must be a Cow.Xml.t. The whole point of $str:$ is to take care of escaping. > > However, you should be able to just parse the template fragment into Cow.Xml.t and insert it as such. no-- the template fragment encloses the slides content, and as cow (quite reasonably) doesn't allow unbalanced expressions i can't break down the ... chunk further, viz: """
$slides$
""" i could do something grim with printf and friends, avoid cow completely, and just read chunks from files like i did with the old version of decks, but i was hoping to avoid that... > I'm guessing it doesn't parse because of... a concrete example-- in the cam13/index.html there're slides like: """
""" this can't be parsed by cow because of (among other things that i can fix easily enough, notably data-markdown being an empty attribute -- fix is to write data-markdown="" instead -- for which i believe i saw an issue already raised) the ">" characters in the ocaml example. > Alternatively, you could make it valid XHTML by wrapping it in a CDATA. > > ...The latter is probably the best solution, since we serve the MIME type > as XHTML anyway. yes -- CDATA is the obvious thing i was missing. probably the most workable fix is to wrap the code fragments in
(the manual pre/code elements are needed because the ``` code block delimiter doesn't escape the contents from the XML parser, but applying it with the CDATA delimiters causes the > to render (literally) as > etc.) thought: given the use and abuse to which xml/html are put though (or, if you prefer, the flexibility which they provide), having some kind of [`Raw of string] might be useful. kind of like a CDATA but which doesn't leave any tag in the xml when rendered to a string (ie. the element tag never gets to the browser). -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 14:56:46 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 14:56:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv6vz-00008P-7r; Mon, 23 Dec 2013 14:56:43 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vv6vy-00008K-23 for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 14:56:42 +0000 Received: from [85.158.139.211:9934] by server-13.bemta-5.messagelabs.com id 1F/2E-11357-92F48B25; Mon, 23 Dec 2013 14:56:41 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-14.tower-206.messagelabs.com!1387810600!6274595!1 X-Originating-IP: [93.159.202.52] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 885 invoked from network); 23 Dec 2013 14:56:40 -0000 Received: from engine03-20433-8.icritical.com (HELO engine03-20433-8.icritical.com) (93.159.202.52) by server-14.tower-206.messagelabs.com with SMTP; 23 Dec 2013 14:56:40 -0000 Received: (qmail 2211 invoked from network); 23 Dec 2013 14:56:34 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 23 Dec 2013 14:56:34 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 01608-07 for ; Mon, 23 Dec 2013 14:56:32 +0000 (GMT) Received: (qmail 2199 invoked by uid 599); 23 Dec 2013 14:56:32 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 14:56:32 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1Vv6vs-000701-Js; Mon, 23 Dec 2013 14:56:36 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 14:56:35 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac7/7yzfyyVSfixBRwKv0wIpjV3upA== Message-ID: References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> In-Reply-To: <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 12:31, Anil Madhavapeddy wrote: > You can't insert the string verbatim, as the type of the $$ must be a Cow.Xml.t. The whole point of $str:$ is to take care of escaping. > > However, you should be able to just parse the template fragment into Cow.Xml.t and insert it as such. no-- the template fragment encloses the slides content, and as cow (quite reasonably) doesn't allow unbalanced expressions i can't break down the ... chunk further, viz: """
$slides$
""" i could do something grim with printf and friends, avoid cow completely, and just read chunks from files like i did with the old version of decks, but i was hoping to avoid that... > I'm guessing it doesn't parse because of... a concrete example-- in the cam13/index.html there're slides like: """
""" this can't be parsed by cow because of (among other things that i can fix easily enough, notably data-markdown being an empty attribute -- fix is to write data-markdown="" instead -- for which i believe i saw an issue already raised) the ">" characters in the ocaml example. > Alternatively, you could make it valid XHTML by wrapping it in a CDATA. > > ...The latter is probably the best solution, since we serve the MIME type > as XHTML anyway. yes -- CDATA is the obvious thing i was missing. probably the most workable fix is to wrap the code fragments in
(the manual pre/code elements are needed because the ``` code block delimiter doesn't escape the contents from the XML parser, but applying it with the CDATA delimiters causes the > to render (literally) as > etc.) thought: given the use and abuse to which xml/html are put though (or, if you prefer, the flexibility which they provide), having some kind of [`Raw of string] might be useful. kind of like a CDATA but which doesn't leave any tag in the xml when rendered to a string (ie. the element tag never gets to the browser). -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 18:54:37 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 18:54:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvAe8-0000Sc-CE; Mon, 23 Dec 2013 18:54:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvAe6-0000SV-O1 for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 18:54:30 +0000 Received: from [85.158.137.68:17295] by server-4.bemta-3.messagelabs.com id D9/64-10414-5E688B25; Mon, 23 Dec 2013 18:54:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1387824868!5702381!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29792 invoked from network); 23 Dec 2013 18:54:29 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-31.messagelabs.com with SMTP; 23 Dec 2013 18:54:29 -0000 Received: (qmail 15983 invoked by uid 634); 23 Dec 2013 18:54:28 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 18:54:28 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 23 Dec 2013 18:54:25 +0000 Message-Id: <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 14:56, Richard Mortier wrote: > thought: given the use and abuse to which xml/html are put though (or, if you prefer, the flexibility which they provide), having some kind of [`Raw of string] might be useful. kind of like a CDATA but which doesn't leave any tag in the xml when rendered to a string (ie. the element tag never gets to the browser). We're trying to avoid that, since Cow is only an XML parser. What we're missing is a proper HTML parser, which can be built on top of XMLM easily enough. Just needs someone to map the XMLM signals onto the HTML-specific rules (some tags shouldn't be closed at all, and a set of entities is predefined). So for now, think of Cow.Html as actually being Cow.XHtml, and you should be set. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 18:54:37 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 18:54:37 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvAe8-0000Sc-CE; Mon, 23 Dec 2013 18:54:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvAe6-0000SV-O1 for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 18:54:30 +0000 Received: from [85.158.137.68:17295] by server-4.bemta-3.messagelabs.com id D9/64-10414-5E688B25; Mon, 23 Dec 2013 18:54:29 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-8.tower-31.messagelabs.com!1387824868!5702381!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29792 invoked from network); 23 Dec 2013 18:54:29 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-8.tower-31.messagelabs.com with SMTP; 23 Dec 2013 18:54:29 -0000 Received: (qmail 15983 invoked by uid 634); 23 Dec 2013 18:54:28 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 18:54:28 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Mon, 23 Dec 2013 18:54:25 +0000 Message-Id: <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 14:56, Richard Mortier wrote: > thought: given the use and abuse to which xml/html are put though (or, if you prefer, the flexibility which they provide), having some kind of [`Raw of string] might be useful. kind of like a CDATA but which doesn't leave any tag in the xml when rendered to a string (ie. the element tag never gets to the browser). We're trying to avoid that, since Cow is only an XML parser. What we're missing is a proper HTML parser, which can be built on top of XMLM easily enough. Just needs someone to map the XMLM signals onto the HTML-specific rules (some tags shouldn't be closed at all, and a set of entities is predefined). So for now, think of Cow.Html as actually being Cow.XHtml, and you should be set. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:36:34 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:36:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDAu-0005Fj-3p; Mon, 23 Dec 2013 21:36:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDAs-0005Fe-FD for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:36:30 +0000 Received: from [85.158.137.68:46322] by server-9.bemta-3.messagelabs.com id E0/75-13104-DDCA8B25; Mon, 23 Dec 2013 21:36:29 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-5.tower-31.messagelabs.com!1387834588!5720001!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30619 invoked from network); 23 Dec 2013 21:36:28 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-5.tower-31.messagelabs.com with SMTP; 23 Dec 2013 21:36:28 -0000 Received: (qmail 14178 invoked from network); 23 Dec 2013 21:36:46 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 23 Dec 2013 21:36:46 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 12248-07 for ; Mon, 23 Dec 2013 21:36:45 +0000 (GMT) Received: (qmail 14170 invoked by uid 599); 23 Dec 2013 21:36:45 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 21:36:45 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvDAo-0005N6-Bl; Mon, 23 Dec 2013 21:36:26 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 21:36:25 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac8AJwgtJuoJiAx5TCW2ID9Rlpxz1g== Message-ID: <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> In-Reply-To: <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 18:54, Anil Madhavapeddy wrote: > On 23 Dec 2013, at 14:56, Richard Mortier wrote: > >> thought: given the use and abuse to which xml/html are put though (or, if you prefer, the flexibility which they provide), having some kind of [`Raw of string] might be useful. kind of like a CDATA but which doesn't leave any tag in the xml when rendered to a string (ie. the element tag never gets to the browser). > > We're trying to avoid that, since Cow is only an XML parser. What we're missing is a proper HTML parser, which can be built on top of XMLM easily enough. Just needs someone to map the XMLM signals onto the HTML-specific rules (some tags shouldn't be closed at all, and a set of entities is predefined). > > So for now, think of Cow.Html as actually being Cow.XHtml, and you should be set. hm-- i'm not sure an html parser will actually help. some of the inline markdown content is invalid html (i believe). eg., rendering the blockquotes from your slides is another piece of inline markdown that has to be done manually: > this is a blockquote rendered as > a

...

needs to have the
...etc put in manually. surrounding with CDATA allows cow to escape the to > similarly some of the indentation in code blocks isn't passed through by CDATA correctly. i've managed to make most of them except your lectures look ok. i'll push changes -- if you can figure out a solution, let me know. else i'll have to go back to serving fragments from files i think. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:36:34 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:36:34 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDAu-0005Fj-3p; Mon, 23 Dec 2013 21:36:32 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDAs-0005Fe-FD for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:36:30 +0000 Received: from [85.158.137.68:46322] by server-9.bemta-3.messagelabs.com id E0/75-13104-DDCA8B25; Mon, 23 Dec 2013 21:36:29 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-5.tower-31.messagelabs.com!1387834588!5720001!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 30619 invoked from network); 23 Dec 2013 21:36:28 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-5.tower-31.messagelabs.com with SMTP; 23 Dec 2013 21:36:28 -0000 Received: (qmail 14178 invoked from network); 23 Dec 2013 21:36:46 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 23 Dec 2013 21:36:46 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 12248-07 for ; Mon, 23 Dec 2013 21:36:45 +0000 (GMT) Received: (qmail 14170 invoked by uid 599); 23 Dec 2013 21:36:45 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 21:36:45 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvDAo-0005N6-Bl; Mon, 23 Dec 2013 21:36:26 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 21:36:25 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac8AJwgtJuoJiAx5TCW2ID9Rlpxz1g== Message-ID: <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> In-Reply-To: <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 18:54, Anil Madhavapeddy wrote: > On 23 Dec 2013, at 14:56, Richard Mortier wrote: > >> thought: given the use and abuse to which xml/html are put though (or, if you prefer, the flexibility which they provide), having some kind of [`Raw of string] might be useful. kind of like a CDATA but which doesn't leave any tag in the xml when rendered to a string (ie. the element tag never gets to the browser). > > We're trying to avoid that, since Cow is only an XML parser. What we're missing is a proper HTML parser, which can be built on top of XMLM easily enough. Just needs someone to map the XMLM signals onto the HTML-specific rules (some tags shouldn't be closed at all, and a set of entities is predefined). > > So for now, think of Cow.Html as actually being Cow.XHtml, and you should be set. hm-- i'm not sure an html parser will actually help. some of the inline markdown content is invalid html (i believe). eg., rendering the blockquotes from your slides is another piece of inline markdown that has to be done manually: > this is a blockquote rendered as > a

...

needs to have the
...etc put in manually. surrounding with CDATA allows cow to escape the to > similarly some of the indentation in code blocks isn't passed through by CDATA correctly. i've managed to make most of them except your lectures look ok. i'll push changes -- if you can figure out a solution, let me know. else i'll have to go back to serving fragments from files i think. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:39:03 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:39:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDDL-0005Xg-Bk; Mon, 23 Dec 2013 21:39:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDDJ-0005Xa-2o for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:39:01 +0000 Received: from [85.158.139.211:42269] by server-15.bemta-5.messagelabs.com id 3C/8A-08490-47DA8B25; Mon, 23 Dec 2013 21:39:00 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1387834739!6178691!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20078 invoked from network); 23 Dec 2013 21:38:59 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-206.messagelabs.com with SMTP; 23 Dec 2013 21:38:59 -0000 Received: (qmail 25682 invoked by uid 634); 23 Dec 2013 21:38:59 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 21:38:58 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> Date: Mon, 23 Dec 2013 21:38:55 +0000 Message-Id: <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:36, Richard Mortier wrote: > > hm-- i'm not sure an html parser will actually help. some of the inline markdown content is invalid html (i believe). > > eg., rendering the blockquotes from your slides is another piece of inline markdown that has to be done manually: > >> this is a blockquote rendered as >> a

...

> > needs to have the
...etc put in manually. surrounding with CDATA allows cow to escape the to > > > similarly some of the indentation in code blocks isn't passed through by CDATA correctly. > > i've managed to make most of them except your lectures look ok. i'll push changes -- if you can figure out a solution, let me know. else i'll have to go back to serving fragments from files i think. Does the CDATA solution work for the Markdown, or does it get in the way? It should be pretty much the same, in theory. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:39:03 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:39:03 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDDL-0005Xg-Bk; Mon, 23 Dec 2013 21:39:03 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDDJ-0005Xa-2o for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:39:01 +0000 Received: from [85.158.139.211:42269] by server-15.bemta-5.messagelabs.com id 3C/8A-08490-47DA8B25; Mon, 23 Dec 2013 21:39:00 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-11.tower-206.messagelabs.com!1387834739!6178691!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20078 invoked from network); 23 Dec 2013 21:38:59 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-11.tower-206.messagelabs.com with SMTP; 23 Dec 2013 21:38:59 -0000 Received: (qmail 25682 invoked by uid 634); 23 Dec 2013 21:38:59 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 21:38:58 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> Date: Mon, 23 Dec 2013 21:38:55 +0000 Message-Id: <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:36, Richard Mortier wrote: > > hm-- i'm not sure an html parser will actually help. some of the inline markdown content is invalid html (i believe). > > eg., rendering the blockquotes from your slides is another piece of inline markdown that has to be done manually: > >> this is a blockquote rendered as >> a

...

> > needs to have the
...etc put in manually. surrounding with CDATA allows cow to escape the to > > > similarly some of the indentation in code blocks isn't passed through by CDATA correctly. > > i've managed to make most of them except your lectures look ok. i'll push changes -- if you can figure out a solution, let me know. else i'll have to go back to serving fragments from files i think. Does the CDATA solution work for the Markdown, or does it get in the way? It should be pretty much the same, in theory. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:54:13 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:54:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDRz-0005yb-UZ; Mon, 23 Dec 2013 21:54:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDRy-0005yW-Ri for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:54:11 +0000 Received: from [85.158.139.211:39815] by server-1.bemta-5.messagelabs.com id 4D/CA-21065-201B8B25; Mon, 23 Dec 2013 21:54:10 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1387835649!6373338!1 X-Originating-IP: [195.62.217.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11998 invoked from network); 23 Dec 2013 21:54:09 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-9.tower-206.messagelabs.com with SMTP; 23 Dec 2013 21:54:09 -0000 Received: (qmail 27996 invoked from network); 23 Dec 2013 21:54:04 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 23 Dec 2013 21:54:04 -0000 Received: from engine02-20433-2.icritical.com ([127.0.0.1]) by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 27631-03 for ; Mon, 23 Dec 2013 21:54:03 +0000 (GMT) Received: (qmail 27987 invoked by uid 599); 23 Dec 2013 21:54:03 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 21:54:03 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvDRu-0005Xx-2o; Mon, 23 Dec 2013 21:54:06 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 21:54:04 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac8AKX+LXAjn7zWRRLm8lml+K5+qfg== Message-ID: <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> In-Reply-To: <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:38, Anil Madhavapeddy wrote: > On 23 Dec 2013, at 21:36, Richard Mortier wrote: >> >> hm-- i'm not sure an html parser will actually help. some of the inline markdown content is invalid html (i believe). >> >> eg., rendering the blockquotes from your slides is another piece of inline markdown that has to be done manually: >> >>> this is a blockquote rendered as >>> a

...

>> >> needs to have the
...etc put in manually. surrounding with CDATA allows cow to escape the to > >> >> similarly some of the indentation in code blocks isn't passed through by CDATA correctly. >> >> i've managed to make most of them except your lectures look ok. i'll push changes -- if you can figure out a solution, let me know. else i'll have to go back to serving fragments from files i think. > > Does the CDATA solution work for the Markdown, or does it get in the way? It should be pretty much the same, in theory. it works for some of the markdown, but there are some things it doesn't help. basically, it stops cow barfing if there are characters like & < > when it parses the input; but cow then escapes these which means the js in the page that parses the markdown can't recognise them. eg., `<&>` in a markdown fragment either causes cow to barf (parse error), or if surrounded by CDATA cow turns it into `<&>` in the html returned to the browser, so the js then renders it as the corresponding string literal (in html, "&lt;&amp;&gt;") in a monospaced font. the best i can think of is some way to explicitly tell cow to not parse a chunk of input and leave it "raw". or else i'll have to revert to serving fragments out of files and not use cow at all. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:54:13 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:54:13 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDRz-0005yb-UZ; Mon, 23 Dec 2013 21:54:11 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDRy-0005yW-Ri for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:54:11 +0000 Received: from [85.158.139.211:39815] by server-1.bemta-5.messagelabs.com id 4D/CA-21065-201B8B25; Mon, 23 Dec 2013 21:54:10 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-9.tower-206.messagelabs.com!1387835649!6373338!1 X-Originating-IP: [195.62.217.151] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTEgPT4gMTE1MjA=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 11998 invoked from network); 23 Dec 2013 21:54:09 -0000 Received: from engine02-20433-2.icritical.com (HELO engine02-20433-2.icritical.com) (195.62.217.151) by server-9.tower-206.messagelabs.com with SMTP; 23 Dec 2013 21:54:09 -0000 Received: (qmail 27996 invoked from network); 23 Dec 2013 21:54:04 -0000 Received: from localhost (127.0.0.1) by engine02-20433-2.icritical.com with SMTP; 23 Dec 2013 21:54:04 -0000 Received: from engine02-20433-2.icritical.com ([127.0.0.1]) by localhost (engine02-20433-2.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 27631-03 for ; Mon, 23 Dec 2013 21:54:03 +0000 (GMT) Received: (qmail 27987 invoked by uid 599); 23 Dec 2013 21:54:03 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine02-20433-2.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 21:54:03 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvDRu-0005Xx-2o; Mon, 23 Dec 2013 21:54:06 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 21:54:04 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac8AKX+LXAjn7zWRRLm8lml+K5+qfg== Message-ID: <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> In-Reply-To: <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine02-20433-2.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:38, Anil Madhavapeddy wrote: > On 23 Dec 2013, at 21:36, Richard Mortier wrote: >> >> hm-- i'm not sure an html parser will actually help. some of the inline markdown content is invalid html (i believe). >> >> eg., rendering the blockquotes from your slides is another piece of inline markdown that has to be done manually: >> >>> this is a blockquote rendered as >>> a

...

>> >> needs to have the
...etc put in manually. surrounding with CDATA allows cow to escape the to > >> >> similarly some of the indentation in code blocks isn't passed through by CDATA correctly. >> >> i've managed to make most of them except your lectures look ok. i'll push changes -- if you can figure out a solution, let me know. else i'll have to go back to serving fragments from files i think. > > Does the CDATA solution work for the Markdown, or does it get in the way? It should be pretty much the same, in theory. it works for some of the markdown, but there are some things it doesn't help. basically, it stops cow barfing if there are characters like & < > when it parses the input; but cow then escapes these which means the js in the page that parses the markdown can't recognise them. eg., `<&>` in a markdown fragment either causes cow to barf (parse error), or if surrounded by CDATA cow turns it into `<&>` in the html returned to the browser, so the js then renders it as the corresponding string literal (in html, "&lt;&amp;&gt;") in a monospaced font. the best i can think of is some way to explicitly tell cow to not parse a chunk of input and leave it "raw". or else i'll have to revert to serving fragments out of files and not use cow at all. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:57:45 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:57:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDVR-000604-A6; Mon, 23 Dec 2013 21:57:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDVP-0005zx-Sv for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:57:44 +0000 Received: from [85.158.139.211:60744] by server-1.bemta-5.messagelabs.com id CE/5C-21065-7D1B8B25; Mon, 23 Dec 2013 21:57:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1387835862!6359862!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4481 invoked from network); 23 Dec 2013 21:57:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-206.messagelabs.com with SMTP; 23 Dec 2013 21:57:42 -0000 Received: (qmail 16953 invoked by uid 634); 23 Dec 2013 21:57:42 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 21:57:41 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> Date: Mon, 23 Dec 2013 21:57:38 +0000 Message-Id: <7021C024-83F9-40F6-A9A0-5A633130BD73@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:54, Richard Mortier wrote: > > it works for some of the markdown, but there are some things it doesn't help. basically, it stops cow barfing if there are characters like & < > when it parses the input; but cow then escapes these which means the js in the page that parses the markdown can't recognise them. > > eg., `<&>` in a markdown fragment either causes cow to barf (parse error), or if surrounded by CDATA cow turns it into `<&>` in the html returned to the browser, so the js then renders it as the corresponding string literal (in html, "&lt;&amp;&gt;") in a monospaced font. > > the best i can think of is some way to explicitly tell cow to not parse a chunk of input and leave it "raw". or else i'll have to revert to serving fragments out of files and not use cow at all. I can't think of anything else immediately that might help, short of an HTML parser (which is more permissive about such things than an XML parser). Could you create an issue on https://github.com/mirage/ocaml-cow/issues about this so we don't forget? In the meanwhile, serving it from files like we used to sounds fine to me... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 21:57:45 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 21:57:45 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDVR-000604-A6; Mon, 23 Dec 2013 21:57:45 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvDVP-0005zx-Sv for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 21:57:44 +0000 Received: from [85.158.139.211:60744] by server-1.bemta-5.messagelabs.com id CE/5C-21065-7D1B8B25; Mon, 23 Dec 2013 21:57:43 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-10.tower-206.messagelabs.com!1387835862!6359862!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 4481 invoked from network); 23 Dec 2013 21:57:42 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-10.tower-206.messagelabs.com with SMTP; 23 Dec 2013 21:57:42 -0000 Received: (qmail 16953 invoked by uid 634); 23 Dec 2013 21:57:42 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 23 Dec 2013 21:57:41 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> Date: Mon, 23 Dec 2013 21:57:38 +0000 Message-Id: <7021C024-83F9-40F6-A9A0-5A633130BD73@recoil.org> References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:54, Richard Mortier wrote: > > it works for some of the markdown, but there are some things it doesn't help. basically, it stops cow barfing if there are characters like & < > when it parses the input; but cow then escapes these which means the js in the page that parses the markdown can't recognise them. > > eg., `<&>` in a markdown fragment either causes cow to barf (parse error), or if surrounded by CDATA cow turns it into `<&>` in the html returned to the browser, so the js then renders it as the corresponding string literal (in html, "&lt;&amp;&gt;") in a monospaced font. > > the best i can think of is some way to explicitly tell cow to not parse a chunk of input and leave it "raw". or else i'll have to revert to serving fragments out of files and not use cow at all. I can't think of anything else immediately that might help, short of an HTML parser (which is more permissive about such things than an XML parser). Could you create an issue on https://github.com/mirage/ocaml-cow/issues about this so we don't forget? In the meanwhile, serving it from files like we used to sounds fine to me... -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 22:50:58 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 22:50:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvEKt-0007cE-WF; Mon, 23 Dec 2013 22:50:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvEKs-0007c9-Dy for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 22:50:54 +0000 Received: from [85.158.137.68:26657] by server-11.bemta-3.messagelabs.com id 91/70-19379-D4EB8B25; Mon, 23 Dec 2013 22:50:53 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-5.tower-31.messagelabs.com!1387839052!5725164!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1847 invoked from network); 23 Dec 2013 22:50:52 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-5.tower-31.messagelabs.com with SMTP; 23 Dec 2013 22:50:52 -0000 Received: (qmail 1743 invoked from network); 23 Dec 2013 22:50:48 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 23 Dec 2013 22:50:48 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 32236-08 for ; Mon, 23 Dec 2013 22:50:46 +0000 (GMT) Received: (qmail 1732 invoked by uid 599); 23 Dec 2013 22:50:46 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 22:50:46 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvEKn-0001bD-16; Mon, 23 Dec 2013 22:50:49 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 22:50:47 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac8AMWvQ1ZBf2INFTeq0O8zBnLaqCw== Message-ID: References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> <7021C024-83F9-40F6-A9A0-5A633130BD73@recoil.org> In-Reply-To: <7021C024-83F9-40F6-A9A0-5A633130BD73@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:57, Anil Madhavapeddy wrote: > I can't think of anything else immediately that might help, short of an HTML parser (which is more permissive about such things than an XML parser). Could you create an issue on https://github.com/mirage/ocaml-cow/issues about this so we don't forget? done. > In the meanwhile, serving it from files like we used to sounds fine to me... done; pr sent. index page could still do with some styling, but everything else is done i think. let me know if you spot anything. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 23 22:50:58 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 23 Dec 2013 22:50:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvEKt-0007cE-WF; Mon, 23 Dec 2013 22:50:56 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvEKs-0007c9-Dy for mirageos-devel@lists.xenproject.org; Mon, 23 Dec 2013 22:50:54 +0000 Received: from [85.158.137.68:26657] by server-11.bemta-3.messagelabs.com id 91/70-19379-D4EB8B25; Mon, 23 Dec 2013 22:50:53 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-5.tower-31.messagelabs.com!1387839052!5725164!1 X-Originating-IP: [195.62.217.150] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogMTk1LjYyLjIxNy4xNTAgPT4gNzU3Mg==\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 1847 invoked from network); 23 Dec 2013 22:50:52 -0000 Received: from engine06-20433-6.icritical.com (HELO engine06-20433-6.icritical.com) (195.62.217.150) by server-5.tower-31.messagelabs.com with SMTP; 23 Dec 2013 22:50:52 -0000 Received: (qmail 1743 invoked from network); 23 Dec 2013 22:50:48 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 23 Dec 2013 22:50:48 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 32236-08 for ; Mon, 23 Dec 2013 22:50:46 +0000 (GMT) Received: (qmail 1732 invoked by uid 599); 23 Dec 2013 22:50:46 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Mon, 23 Dec 2013 22:50:46 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvEKn-0001bD-16; Mon, 23 Dec 2013 22:50:49 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Mon, 23 Dec 2013 22:50:47 +0000 Thread-Topic: [MirageOS-devel] using cow Thread-Index: Ac8AMWvQ1ZBf2INFTeq0O8zBnLaqCw== Message-ID: References: <672E6AFC-AA76-4473-81E6-299946FFCBF7@nottingham.ac.uk> <2481DA59-BAB9-4933-A840-67AA8EC32AE3@recoil.org> <8F4631AA-7E2E-4DEB-BB2E-96589C76ADEC@recoil.org> <806F8B04-A03D-4A89-927B-AE281782D6BF@nottingham.ac.uk> <2B39FAFF-D3D3-40FB-80B1-BE26F6D6A120@recoil.org> <0FB6A0B6-5C8C-4143-873B-43A212232BAF@nottingham.ac.uk> <7021C024-83F9-40F6-A9A0-5A633130BD73@recoil.org> In-Reply-To: <7021C024-83F9-40F6-A9A0-5A633130BD73@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] using cow X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 23 Dec 2013, at 21:57, Anil Madhavapeddy wrote: > I can't think of anything else immediately that might help, short of an HTML parser (which is more permissive about such things than an XML parser). Could you create an issue on https://github.com/mirage/ocaml-cow/issues about this so we don't forget? done. > In the meanwhile, serving it from files like we used to sounds fine to me... done; pr sent. index page could still do with some styling, but everything else is done i think. let me know if you spot anything. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 24 09:28:41 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Dec 2013 09:28:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOI0-00066y-FO; Tue, 24 Dec 2013 09:28:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOHz-00066t-5q for mirageos-devel@lists.xenproject.org; Tue, 24 Dec 2013 09:28:35 +0000 Received: from [85.158.143.35:16365] by server-1.bemta-4.messagelabs.com id 78/01-02132-2C359B25; Tue, 24 Dec 2013 09:28:34 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1387877313!7842833!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15303 invoked from network); 24 Dec 2013 09:28:33 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-12.tower-21.messagelabs.com with SMTP; 24 Dec 2013 09:28:33 -0000 Received: (qmail 16722 invoked from network); 24 Dec 2013 09:28:49 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 24 Dec 2013 09:28:49 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15882-09 for ; Tue, 24 Dec 2013 09:28:48 +0000 (GMT) Received: (qmail 16710 invoked by uid 599); 24 Dec 2013 09:28:48 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 24 Dec 2013 09:28:48 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvOHv-0004qf-3U for mirageos-devel@lists.xenproject.org; Tue, 24 Dec 2013 09:28:31 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Tue, 24 Dec 2013 09:28:29 +0000 Thread-Topic: mirage-decks-- getting dependencies right Thread-Index: Ac8AioHYbE6LBNjcRE6FaxXergBkPg== Message-ID: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Subject: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org having trouble with a couple of dependencies in travis xen builds for mirage-decks. 1/ i currently have the line add_to_ocamlfind_libraries ["cow.syntax"; "cowabloga"; "cohttp.mirage-unix"]; in my config.ml. this obviously fails when travis builds for xen -- but what do i put instead of cohttp.mirage-unix? do i need to (shock!) write code to determine what the build target is to add the right ocamlfind library? 2/ the xen build also fails with the following error: """ File "static_assets.ml", line 6, characters 37-44: Parse error: currified constructor Preprocessing error on file static_assets.ml Error while running external preprocessor Command line: camlp4 '-I' '/usr/lib/ocaml/camlp4' '-I' '/usr/lib/ocaml' '-I' '/home/travis/.opam/system/lib/type_conv' '-I' '/home/travis/.opam/system/lib/dyntype' '-I' '/home/travis/.opam/system/lib/xmlm' '-I' '/home/travis/.opam/system/lib/cow' '-I' '/home/travis/.opam/system/lib/lwt' '-I' '/home/travis/.opam/system/lib/lwt' '-parser' 'o' '-parser' 'op' '-printer' 'p' 'str.cma' 'pa_type_conv.cma' 'pa_dyntype.cma' 'xmlm.cma' 'xmlm.cma' 'str.cma' 'pa_cow.cma' 'lwt-syntax-options.cma' 'lwt-syntax.cma' 'static_assets.ml' > /tmp/ocamlpp182cc7 """ i'll try and debug this later (need to fire up the xen vm) but wondered if it was something obvious & well-known that i was missing as this is a generated file? full travis output at https://travis-ci.org/mor1/mirage-decks/jobs/15922469 -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 24 09:28:41 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Dec 2013 09:28:41 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOI0-00066y-FO; Tue, 24 Dec 2013 09:28:36 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOHz-00066t-5q for mirageos-devel@lists.xenproject.org; Tue, 24 Dec 2013 09:28:35 +0000 Received: from [85.158.143.35:16365] by server-1.bemta-4.messagelabs.com id 78/01-02132-2C359B25; Tue, 24 Dec 2013 09:28:34 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-12.tower-21.messagelabs.com!1387877313!7842833!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15303 invoked from network); 24 Dec 2013 09:28:33 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-12.tower-21.messagelabs.com with SMTP; 24 Dec 2013 09:28:33 -0000 Received: (qmail 16722 invoked from network); 24 Dec 2013 09:28:49 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 24 Dec 2013 09:28:49 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15882-09 for ; Tue, 24 Dec 2013 09:28:48 +0000 (GMT) Received: (qmail 16710 invoked by uid 599); 24 Dec 2013 09:28:48 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Tue, 24 Dec 2013 09:28:48 +0000 Received: from uiwexhub01.ad.nottingham.ac.uk ([128.243.15.133]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VvOHv-0004qf-3U for mirageos-devel@lists.xenproject.org; Tue, 24 Dec 2013 09:28:31 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" Date: Tue, 24 Dec 2013 09:28:29 +0000 Thread-Topic: mirage-decks-- getting dependencies right Thread-Index: Ac8AioHYbE6LBNjcRE6FaxXergBkPg== Message-ID: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Subject: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org having trouble with a couple of dependencies in travis xen builds for mirage-decks. 1/ i currently have the line add_to_ocamlfind_libraries ["cow.syntax"; "cowabloga"; "cohttp.mirage-unix"]; in my config.ml. this obviously fails when travis builds for xen -- but what do i put instead of cohttp.mirage-unix? do i need to (shock!) write code to determine what the build target is to add the right ocamlfind library? 2/ the xen build also fails with the following error: """ File "static_assets.ml", line 6, characters 37-44: Parse error: currified constructor Preprocessing error on file static_assets.ml Error while running external preprocessor Command line: camlp4 '-I' '/usr/lib/ocaml/camlp4' '-I' '/usr/lib/ocaml' '-I' '/home/travis/.opam/system/lib/type_conv' '-I' '/home/travis/.opam/system/lib/dyntype' '-I' '/home/travis/.opam/system/lib/xmlm' '-I' '/home/travis/.opam/system/lib/cow' '-I' '/home/travis/.opam/system/lib/lwt' '-I' '/home/travis/.opam/system/lib/lwt' '-parser' 'o' '-parser' 'op' '-printer' 'p' 'str.cma' 'pa_type_conv.cma' 'pa_dyntype.cma' 'xmlm.cma' 'xmlm.cma' 'str.cma' 'pa_cow.cma' 'lwt-syntax-options.cma' 'lwt-syntax.cma' 'static_assets.ml' > /tmp/ocamlpp182cc7 """ i'll try and debug this later (need to fire up the xen vm) but wondered if it was something obvious & well-known that i was missing as this is a generated file? full travis output at https://travis-ci.org/mor1/mirage-decks/jobs/15922469 -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 24 10:09:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Dec 2013 10:09:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOvU-0007VK-BT; Tue, 24 Dec 2013 10:09:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOvT-0007VE-4z for mirageos-devel@lists.xenproject.org; Tue, 24 Dec 2013 10:09:23 +0000 Received: from [85.158.143.35:36618] by server-3.bemta-4.messagelabs.com id 0A/04-32360-25D59B25; Tue, 24 Dec 2013 10:09:22 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1387879761!5325763!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26936 invoked from network); 24 Dec 2013 10:09:21 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Dec 2013 10:09:21 -0000 Received: by mail-wi0-f177.google.com with SMTP id cc10so7127771wib.16 for ; Tue, 24 Dec 2013 02:09:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=BOCceItn38LeVOMY0JQ5PJWa0k5Qjtc5GEqVYQXhWKA=; b=SXPjCvosFDh5dTc5NL5PNMGqIM5PUs4zRwdi6G9DqR6njHYg6hKix5IXL7e60Nvw1Q +bcgNVQf2oblgai5yK9GYiKMOlPsIUkkbUIastC9/vZaADb36lPkfwr+SATQpZbOUCmT zg6TVbtf1E2PEZc1tfuid/lwP9kP7cb5QjBOBwK3rlOCkRsWoAMNNHPzNJ0FQRcP2jkH UexfEYodaTs2oNaayCsInjp0qIDvmPO3u3E0sXThcazwjwyeQIF/DRDF4gOUNSlBLExb 5Y7CrJ0TVaI4mJnk91O7he4yf6V+TMorkjPlu5zu0q0k0f9GB+91apb2Fa7w/xKisH9g kxVw== X-Received: by 10.180.14.7 with SMTP id l7mr4050192wic.23.1387879761567; Tue, 24 Dec 2013 02:09:21 -0800 (PST) Received: from [192.168.0.5] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id bc5sm35391078wib.4.2013.12.24.02.09.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Dec 2013 02:09:18 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Dec 2013 11:09:18 +0100 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1827) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > add_to_ocamlfind_libraries ["cow.syntax"; "cowabloga"; "cohttp.mirage-unix"]; In the same way that my other comment: the "cohttp-*" dependency should be inferred automatically by the mirage tool. > 2/ the xen build also fails with the following error: [...] seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 24 10:09:25 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 24 Dec 2013 10:09:25 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOvU-0007VK-BT; Tue, 24 Dec 2013 10:09:24 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VvOvT-0007VE-4z for mirageos-devel@lists.xenproject.org; Tue, 24 Dec 2013 10:09:23 +0000 Received: from [85.158.143.35:36618] by server-3.bemta-4.messagelabs.com id 0A/04-32360-25D59B25; Tue, 24 Dec 2013 10:09:22 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-15.tower-21.messagelabs.com!1387879761!5325763!1 X-Originating-IP: [209.85.212.177] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 26936 invoked from network); 24 Dec 2013 10:09:21 -0000 Received: from mail-wi0-f177.google.com (HELO mail-wi0-f177.google.com) (209.85.212.177) by server-15.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 24 Dec 2013 10:09:21 -0000 Received: by mail-wi0-f177.google.com with SMTP id cc10so7127771wib.16 for ; Tue, 24 Dec 2013 02:09:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=BOCceItn38LeVOMY0JQ5PJWa0k5Qjtc5GEqVYQXhWKA=; b=SXPjCvosFDh5dTc5NL5PNMGqIM5PUs4zRwdi6G9DqR6njHYg6hKix5IXL7e60Nvw1Q +bcgNVQf2oblgai5yK9GYiKMOlPsIUkkbUIastC9/vZaADb36lPkfwr+SATQpZbOUCmT zg6TVbtf1E2PEZc1tfuid/lwP9kP7cb5QjBOBwK3rlOCkRsWoAMNNHPzNJ0FQRcP2jkH UexfEYodaTs2oNaayCsInjp0qIDvmPO3u3E0sXThcazwjwyeQIF/DRDF4gOUNSlBLExb 5Y7CrJ0TVaI4mJnk91O7he4yf6V+TMorkjPlu5zu0q0k0f9GB+91apb2Fa7w/xKisH9g kxVw== X-Received: by 10.180.14.7 with SMTP id l7mr4050192wic.23.1387879761567; Tue, 24 Dec 2013 02:09:21 -0800 (PST) Received: from [192.168.0.5] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id bc5sm35391078wib.4.2013.12.24.02.09.17 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 24 Dec 2013 02:09:18 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) From: Thomas Gazagnaire In-Reply-To: Date: Tue, 24 Dec 2013 11:09:18 +0100 Message-Id: References: To: Richard Mortier X-Mailer: Apple Mail (2.1827) Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org > add_to_ocamlfind_libraries ["cow.syntax"; "cowabloga"; "cohttp.mirage-unix"]; In the same way that my other comment: the "cohttp-*" dependency should be inferred automatically by the mirage tool. > 2/ the xen build also fails with the following error: [...] seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Dec 26 14:19:53 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 26 Dec 2013 14:19:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwBmu-0002WM-De; Thu, 26 Dec 2013 14:19:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwBmt-0002WH-Kr for mirageos-devel@lists.xenproject.org; Thu, 26 Dec 2013 14:19:47 +0000 Received: from [193.109.254.147:64651] by server-10.bemta-14.messagelabs.com id 2D/6C-20752-20B3CB25; Thu, 26 Dec 2013 14:19:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-27.messagelabs.com!1388067586!7593580!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20325 invoked from network); 26 Dec 2013 14:19:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-27.messagelabs.com with SMTP; 26 Dec 2013 14:19:46 -0000 Received: (qmail 18192 invoked by uid 634); 26 Dec 2013 14:19:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 26 Dec 2013 14:19:41 +0000 From: Anil Madhavapeddy Message-Id: <495AE323-B317-4E24-B7AB-F4BDF72F8E84@recoil.org> Date: Thu, 26 Dec 2013 14:19:39 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Zurbed up the live website X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Mort and I did some relaxing hacking over the holidays to convert it to a nicer Zurb Foundation-based site, and it's all live now at: http://openmirage.org/ Also put together more information on how the Travis/www deployment works here: http://openmirage.org/wiki/deploying-via-ci The new site also is using the Cowabloga library more to hold the logic of the site so that it can be re-used elsewhere (like my own homepage!). That's still a work-in-progress, but it's a good place to put all the boring logic for Atom feeds for (e.g.) papers, bookmarks and so on. Happy St Stephen's day! -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Thu Dec 26 14:19:53 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Thu, 26 Dec 2013 14:19:53 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwBmu-0002WM-De; Thu, 26 Dec 2013 14:19:48 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwBmt-0002WH-Kr for mirageos-devel@lists.xenproject.org; Thu, 26 Dec 2013 14:19:47 +0000 Received: from [193.109.254.147:64651] by server-10.bemta-14.messagelabs.com id 2D/6C-20752-20B3CB25; Thu, 26 Dec 2013 14:19:46 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-14.tower-27.messagelabs.com!1388067586!7593580!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests=ML_RADAR_SPEW_LINKS_23, spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 20325 invoked from network); 26 Dec 2013 14:19:46 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-14.tower-27.messagelabs.com with SMTP; 26 Dec 2013 14:19:46 -0000 Received: (qmail 18192 invoked by uid 634); 26 Dec 2013 14:19:45 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Thu, 26 Dec 2013 14:19:41 +0000 From: Anil Madhavapeddy Message-Id: <495AE323-B317-4E24-B7AB-F4BDF72F8E84@recoil.org> Date: Thu, 26 Dec 2013 14:19:39 +0000 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Subject: [MirageOS-devel] Zurbed up the live website X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Mort and I did some relaxing hacking over the holidays to convert it to a nicer Zurb Foundation-based site, and it's all live now at: http://openmirage.org/ Also put together more information on how the Travis/www deployment works here: http://openmirage.org/wiki/deploying-via-ci The new site also is using the Cowabloga library more to hold the logic of the site so that it can be re-used elsewhere (like my own homepage!). That's still a work-in-progress, but it's a good place to put all the boring logic for Atom feeds for (e.g.) papers, bookmarks and so on. Happy St Stephen's day! -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 12:14:58 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 12:14:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwWJa-0002n3-LY; Fri, 27 Dec 2013 12:14:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwWJa-0002my-0I for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 12:14:54 +0000 Received: from [193.109.254.147:3457] by server-15.bemta-14.messagelabs.com id 68/AD-22186-D3F6DB25; Fri, 27 Dec 2013 12:14:53 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1388146492!5398056!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24934 invoked from network); 27 Dec 2013 12:14:52 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Dec 2013 12:14:52 -0000 Received: by mail-we0-f176.google.com with SMTP id p61so7952285wes.7 for ; Fri, 27 Dec 2013 04:14:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=aD2p+LqB968Ndh6Ad5OFVf1zLxqgSppuWFizBQQXzcE=; b=sPKoZmQZAr/g1tgZmWPvk3m/T75GZ5W11Cc1Y/evPOcBOJssq273oA61jiK3YD5m0A 7QQEbU290fp3NL/1T9bihAmV/TE3CWw4HopFO/6JxeWcAWLMzuJ/8tMVcJ84KAhWbFq0 yv+a4kGX9Nc+iiythntBQAaaIC4GmQ2I69hPV2x8I5gcbbBRb2PBqWQ7K2jK3sU1Am2v aWXuMBUzH182NdueB8i4Uq7r37jS4upigjUOgCT3WQrRf63bWGvtecyYIK+WUuSojgrX xW6HcC2D9djAq95MKVMB15f1pZP0BQyxtrX2ImzHimVejswcvzy2FTk9qEoiXXYbwhyt pKvg== X-Received: by 10.194.240.41 with SMTP id vx9mr5414603wjc.70.1388146491893; Fri, 27 Dec 2013 04:14:51 -0800 (PST) Received: from [192.168.0.5] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id pl7sm19069729wjc.16.2013.12.27.04.14.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Dec 2013 04:14:47 -0800 (PST) From: Thomas Gazagnaire Message-Id: Date: Fri, 27 Dec 2013 13:14:50 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: https://github.com/mirage/mirage/pull/178 The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli Some examples: * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... -- Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 12:14:58 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 12:14:58 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwWJa-0002n3-LY; Fri, 27 Dec 2013 12:14:54 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwWJa-0002my-0I for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 12:14:54 +0000 Received: from [193.109.254.147:3457] by server-15.bemta-14.messagelabs.com id 68/AD-22186-D3F6DB25; Fri, 27 Dec 2013 12:14:53 +0000 X-Env-Sender: thomas.gazagnaire@gmail.com X-Msg-Ref: server-13.tower-27.messagelabs.com!1388146492!5398056!1 X-Originating-IP: [74.125.82.176] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24934 invoked from network); 27 Dec 2013 12:14:52 -0000 Received: from mail-we0-f176.google.com (HELO mail-we0-f176.google.com) (74.125.82.176) by server-13.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 27 Dec 2013 12:14:52 -0000 Received: by mail-we0-f176.google.com with SMTP id p61so7952285wes.7 for ; Fri, 27 Dec 2013 04:14:52 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=aD2p+LqB968Ndh6Ad5OFVf1zLxqgSppuWFizBQQXzcE=; b=sPKoZmQZAr/g1tgZmWPvk3m/T75GZ5W11Cc1Y/evPOcBOJssq273oA61jiK3YD5m0A 7QQEbU290fp3NL/1T9bihAmV/TE3CWw4HopFO/6JxeWcAWLMzuJ/8tMVcJ84KAhWbFq0 yv+a4kGX9Nc+iiythntBQAaaIC4GmQ2I69hPV2x8I5gcbbBRb2PBqWQ7K2jK3sU1Am2v aWXuMBUzH182NdueB8i4Uq7r37jS4upigjUOgCT3WQrRf63bWGvtecyYIK+WUuSojgrX xW6HcC2D9djAq95MKVMB15f1pZP0BQyxtrX2ImzHimVejswcvzy2FTk9qEoiXXYbwhyt pKvg== X-Received: by 10.194.240.41 with SMTP id vx9mr5414603wjc.70.1388146491893; Fri, 27 Dec 2013 04:14:51 -0800 (PST) Received: from [192.168.0.5] (bar06-2-82-224-156-126.fbx.proxad.net. [82.224.156.126]) by mx.google.com with ESMTPSA id pl7sm19069729wjc.16.2013.12.27.04.14.47 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 27 Dec 2013 04:14:47 -0800 (PST) From: Thomas Gazagnaire Message-Id: Date: Fri, 27 Dec 2013 13:14:50 +0100 To: mirageos-devel@lists.xenproject.org Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) X-Mailer: Apple Mail (2.1827) Subject: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: https://github.com/mirage/mirage/pull/178 The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli Some examples: * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... -- Thomas _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 13:24:49 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 13:24:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwXPA-0005Ht-2t; Fri, 27 Dec 2013 13:24:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwXP8-0005Hm-RO for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 13:24:43 +0000 Received: from [85.158.139.211:14740] by server-9.bemta-5.messagelabs.com id 49/C2-15098-A9F7DB25; Fri, 27 Dec 2013 13:24:42 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1388150681!6787021!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29675 invoked from network); 27 Dec 2013 13:24:41 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-8.tower-206.messagelabs.com with SMTP; 27 Dec 2013 13:24:41 -0000 Received: (qmail 3320 invoked from network); 27 Dec 2013 13:24:38 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 27 Dec 2013 13:24:38 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 01701-08 for ; Fri, 27 Dec 2013 13:24:36 +0000 (GMT) Received: (qmail 3238 invoked by uid 599); 27 Dec 2013 13:24:36 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 27 Dec 2013 13:24:36 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VwXP4-0001d3-0y; Fri, 27 Dec 2013 13:24:38 +0000 From: Richard Mortier To: Thomas Gazagnaire Date: Fri, 27 Dec 2013 13:24:36 +0000 Thread-Topic: [MirageOS-devel] mirage-decks-- getting dependencies right Thread-Index: Ac8DBv12t7JSpvVrQyulPPZZBm5r5Q== Message-ID: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Dec 2013, at 10:09, Thomas Gazagnaire wrote: >> add_to_ocamlfind_libraries ["cow.syntax"; "cowabloga"; "cohttp.mirage-unix"]; > > In the same way that my other comment: the "cohttp-*" dependency should be inferred automatically by the mirage tool. ack, thanks. don't know how it had crept in, but it does seem i can remove it. >> 2/ the xen build also fails with the following error: > [...] > seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? don't know -- don't have the autogen files from travis. i'll do some more debugging in a vm and post again if i can't figure it out... :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 13:24:49 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 13:24:49 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwXPA-0005Ht-2t; Fri, 27 Dec 2013 13:24:44 +0000 Received: from mail6.bemta5.messagelabs.com ([195.245.231.135]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwXP8-0005Hm-RO for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 13:24:43 +0000 Received: from [85.158.139.211:14740] by server-9.bemta-5.messagelabs.com id 49/C2-15098-A9F7DB25; Fri, 27 Dec 2013 13:24:42 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-8.tower-206.messagelabs.com!1388150681!6787021!1 X-Originating-IP: [151.236.209.33] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 29675 invoked from network); 27 Dec 2013 13:24:41 -0000 Received: from engine01-20433-7.icritical.com (HELO engine01-20433-7.icritical.com) (151.236.209.33) by server-8.tower-206.messagelabs.com with SMTP; 27 Dec 2013 13:24:41 -0000 Received: (qmail 3320 invoked from network); 27 Dec 2013 13:24:38 -0000 Received: from localhost (127.0.0.1) by engine01-20433-7.icritical.com with SMTP; 27 Dec 2013 13:24:38 -0000 Received: from engine01-20433-7.icritical.com ([127.0.0.1]) by localhost (engine01-20433-7.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 01701-08 for ; Fri, 27 Dec 2013 13:24:36 +0000 (GMT) Received: (qmail 3238 invoked by uid 599); 27 Dec 2013 13:24:36 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-7.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 27 Dec 2013 13:24:36 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VwXP4-0001d3-0y; Fri, 27 Dec 2013 13:24:38 +0000 From: Richard Mortier To: Thomas Gazagnaire Date: Fri, 27 Dec 2013 13:24:36 +0000 Thread-Topic: [MirageOS-devel] mirage-decks-- getting dependencies right Thread-Index: Ac8DBv12t7JSpvVrQyulPPZZBm5r5Q== Message-ID: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> References: In-Reply-To: Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-7.icritical.com Cc: "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 24 Dec 2013, at 10:09, Thomas Gazagnaire wrote: >> add_to_ocamlfind_libraries ["cow.syntax"; "cowabloga"; "cohttp.mirage-unix"]; > > In the same way that my other comment: the "cohttp-*" dependency should be inferred automatically by the mirage tool. ack, thanks. don't know how it had crept in, but it does seem i can remove it. >> 2/ the xen build also fails with the following error: > [...] > seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? don't know -- don't have the autogen files from travis. i'll do some more debugging in a vm and post again if i can't figure it out... :) -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 15:57:09 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 15:57:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZmb-0003XJ-SQ; Fri, 27 Dec 2013 15:57:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZmZ-0003X8-SI for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 15:57:03 +0000 Received: from [85.158.143.35:25573] by server-3.bemta-4.messagelabs.com id 7A/3B-32360-F43ADB25; Fri, 27 Dec 2013 15:57:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1388159822!8486584!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7719 invoked from network); 27 Dec 2013 15:57:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-21.messagelabs.com with SMTP; 27 Dec 2013 15:57:02 -0000 Received: (qmail 7537 invoked by uid 634); 27 Dec 2013 15:57:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 27 Dec 2013 15:56:59 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> Date: Fri, 27 Dec 2013 15:56:52 +0000 Message-Id: <94294949-AF8F-4FAD-BAB1-E3B0BF3168CA@recoil.org> References: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 27 Dec 2013, at 13:24, Richard Mortier wrote: > >>> 2/ the xen build also fails with the following error: >> [...] >> seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? > > don't know -- don't have the autogen files from travis. i'll do some more debugging in a vm and post again if i can't figure it out... :) > My bad -- I fixed it and didn't reply to this. It was due to a zero-length file not being handled currently by crunch. It's now fixed in crunch-1.2.3, so if you upgrade and recompile all should be sorted. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 15:57:09 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 15:57:09 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZmb-0003XJ-SQ; Fri, 27 Dec 2013 15:57:05 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZmZ-0003X8-SI for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 15:57:03 +0000 Received: from [85.158.143.35:25573] by server-3.bemta-4.messagelabs.com id 7A/3B-32360-F43ADB25; Fri, 27 Dec 2013 15:57:03 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-5.tower-21.messagelabs.com!1388159822!8486584!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7719 invoked from network); 27 Dec 2013 15:57:02 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-5.tower-21.messagelabs.com with SMTP; 27 Dec 2013 15:57:02 -0000 Received: (qmail 7537 invoked by uid 634); 27 Dec 2013 15:57:02 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Fri, 27 Dec 2013 15:56:59 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> Date: Fri, 27 Dec 2013 15:56:52 +0000 Message-Id: <94294949-AF8F-4FAD-BAB1-E3B0BF3168CA@recoil.org> References: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> To: Richard Mortier X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 27 Dec 2013, at 13:24, Richard Mortier wrote: > >>> 2/ the xen build also fails with the following error: >> [...] >> seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? > > don't know -- don't have the autogen files from travis. i'll do some more debugging in a vm and post again if i can't figure it out... :) > My bad -- I fixed it and didn't reply to this. It was due to a zero-length file not being handled currently by crunch. It's now fixed in crunch-1.2.3, so if you upgrade and recompile all should be sorted. -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 16:00:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 16:00:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZq1-0004FC-Lv; Fri, 27 Dec 2013 16:00:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZq0-0004F4-3R for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 16:00:36 +0000 Received: from [85.158.143.35:42286] by server-3.bemta-4.messagelabs.com id F9/6D-32360-324ADB25; Fri, 27 Dec 2013 16:00:35 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-3.tower-21.messagelabs.com!1388160034!8430339!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10682 invoked from network); 27 Dec 2013 16:00:34 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-3.tower-21.messagelabs.com with SMTP; 27 Dec 2013 16:00:34 -0000 Received: (qmail 32147 invoked from network); 27 Dec 2013 16:00:35 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 27 Dec 2013 16:00:35 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 31942-02 for ; Fri, 27 Dec 2013 16:00:35 +0000 (GMT) Received: (qmail 32131 invoked by uid 599); 27 Dec 2013 16:00:35 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 27 Dec 2013 16:00:35 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VwZpv-0003qE-Bq; Fri, 27 Dec 2013 16:00:31 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Fri, 27 Dec 2013 16:00:30 +0000 Thread-Topic: [MirageOS-devel] mirage-decks-- getting dependencies right Thread-Index: Ac8DHMREW0LDfKl3QqyfGX4nG8295Q== Message-ID: <2870344A-4C79-46DF-A6EA-9C5DC4C1DD13@nottingham.ac.uk> References: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> <94294949-AF8F-4FAD-BAB1-E3B0BF3168CA@recoil.org> In-Reply-To: <94294949-AF8F-4FAD-BAB1-E3B0BF3168CA@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 27 Dec 2013, at 15:56, Anil Madhavapeddy wrote: > On 27 Dec 2013, at 13:24, Richard Mortier wrote: >> >>>> 2/ the xen build also fails with the following error: >>> [...] >>> seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? >> >> don't know -- don't have the autogen files from travis. i'll do some more debugging in a vm and post again if i can't figure it out... :) > > My bad -- I fixed it and didn't reply to this. It was due to a zero-length file not being handled currently by crunch. It's now fixed in crunch-1.2.3, so if you upgrade and recompile all should be sorted. ah cool- thanks. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Fri Dec 27 16:00:38 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Fri, 27 Dec 2013 16:00:38 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZq1-0004FC-Lv; Fri, 27 Dec 2013 16:00:37 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwZq0-0004F4-3R for mirageos-devel@lists.xenproject.org; Fri, 27 Dec 2013 16:00:36 +0000 Received: from [85.158.143.35:42286] by server-3.bemta-4.messagelabs.com id F9/6D-32360-324ADB25; Fri, 27 Dec 2013 16:00:35 +0000 X-Env-Sender: Richard.Mortier@nottingham.ac.uk X-Msg-Ref: server-3.tower-21.messagelabs.com!1388160034!8430339!1 X-Originating-IP: [93.95.15.169] X-SpamReason: No, hits=0.7 required=7.0 tests=BODY_RANDOM_LONG, MIME_QP_LONG_LINE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 10682 invoked from network); 27 Dec 2013 16:00:34 -0000 Received: from engine01-20433-1.icritical.com (HELO engine01-20433-1.icritical.com) (93.95.15.169) by server-3.tower-21.messagelabs.com with SMTP; 27 Dec 2013 16:00:34 -0000 Received: (qmail 32147 invoked from network); 27 Dec 2013 16:00:35 -0000 Received: from localhost (127.0.0.1) by engine01-20433-1.icritical.com with SMTP; 27 Dec 2013 16:00:35 -0000 Received: from engine01-20433-1.icritical.com ([127.0.0.1]) by localhost (engine01-20433-1.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 31942-02 for ; Fri, 27 Dec 2013 16:00:35 +0000 (GMT) Received: (qmail 32131 invoked by uid 599); 27 Dec 2013 16:00:35 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine01-20433-1.icritical.com (qpsmtpd/0.28) with ESMTP; Fri, 27 Dec 2013 16:00:35 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VwZpv-0003qE-Bq; Fri, 27 Dec 2013 16:00:31 +0000 From: Richard Mortier To: Anil Madhavapeddy Date: Fri, 27 Dec 2013 16:00:30 +0000 Thread-Topic: [MirageOS-devel] mirage-decks-- getting dependencies right Thread-Index: Ac8DHMREW0LDfKl3QqyfGX4nG8295Q== Message-ID: <2870344A-4C79-46DF-A6EA-9C5DC4C1DD13@nottingham.ac.uk> References: <0ABD7AF2-B7A7-4157-B6BA-A6B3D4C98982@nottingham.ac.uk> <94294949-AF8F-4FAD-BAB1-E3B0BF3168CA@recoil.org> In-Reply-To: <94294949-AF8F-4FAD-BAB1-E3B0BF3168CA@recoil.org> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine01-20433-1.icritical.com Cc: Thomas Gazagnaire , "mirageos-devel@lists.xenproject.org" Subject: Re: [MirageOS-devel] mirage-decks-- getting dependencies right X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 27 Dec 2013, at 15:56, Anil Madhavapeddy wrote: > On 27 Dec 2013, at 13:24, Richard Mortier wrote: >> >>>> 2/ the xen build also fails with the following error: >>> [...] >>> seems a camlp4 related bug but not sure where it comes from. What the line 6 of of static_assets.ml ? >> >> don't know -- don't have the autogen files from travis. i'll do some more debugging in a vm and post again if i can't figure it out... :) > > My bad -- I fixed it and didn't reply to this. It was due to a zero-length file not being handled currently by crunch. It's now fixed in crunch-1.2.3, so if you upgrade and recompile all should be sorted. ah cool- thanks. -- Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 00:01:27 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 00:01:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwhLH-0001ha-2L; Sat, 28 Dec 2013 00:01:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwhLG-0001hV-41 for mirageos-devel@lists.xenproject.org; Sat, 28 Dec 2013 00:01:22 +0000 Received: from [85.158.137.68:45644] by server-3.bemta-3.messagelabs.com id 7A/9C-10658-1D41EB25; Sat, 28 Dec 2013 00:01:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-31.messagelabs.com!1388188879!6273634!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24524 invoked from network); 28 Dec 2013 00:01:20 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-31.messagelabs.com with SMTP; 28 Dec 2013 00:01:20 -0000 Received: (qmail 29727 invoked by uid 634); 28 Dec 2013 00:01:16 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 28 Dec 2013 00:01:16 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 28 Dec 2013 00:01:15 +0000 Message-Id: References: To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 27 Dec 2013, at 12:14, Thomas Gazagnaire wrote: > Hi, > > During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: > > https://github.com/mirage/mirage/pull/178 > > The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. > > The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli > > Some examples: > * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml > * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml > * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml At a quick run-through, this looks like exactly what we need to layer interesting transformer drivers together. I'll take a shot at a buffer cache for KV_RO using your branch and see what it looks like (do you already have code for this somewhere, Dave?) > Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... Indeed! -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 00:01:27 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 00:01:27 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwhLH-0001ha-2L; Sat, 28 Dec 2013 00:01:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwhLG-0001hV-41 for mirageos-devel@lists.xenproject.org; Sat, 28 Dec 2013 00:01:22 +0000 Received: from [85.158.137.68:45644] by server-3.bemta-3.messagelabs.com id 7A/9C-10658-1D41EB25; Sat, 28 Dec 2013 00:01:21 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-13.tower-31.messagelabs.com!1388188879!6273634!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.0 required=7.0 tests= X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 24524 invoked from network); 28 Dec 2013 00:01:20 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-13.tower-31.messagelabs.com with SMTP; 28 Dec 2013 00:01:20 -0000 Received: (qmail 29727 invoked by uid 634); 28 Dec 2013 00:01:16 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 28 Dec 2013 00:01:16 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 28 Dec 2013 00:01:15 +0000 Message-Id: References: To: Thomas Gazagnaire X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 27 Dec 2013, at 12:14, Thomas Gazagnaire wrote: > Hi, > > During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: > > https://github.com/mirage/mirage/pull/178 > > The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. > > The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli > > Some examples: > * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml > * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml > * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml At a quick run-through, this looks like exactly what we need to layer interesting transformer drivers together. I'll take a shot at a buffer cache for KV_RO using your branch and see what it looks like (do you already have code for this somewhere, Dave?) > Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... Indeed! -anil _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 09:23:55 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 09:23:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vwq7c-00045P-9g; Sat, 28 Dec 2013 09:23:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vwq7a-00045K-Lu for mirageos-devel@lists.xenproject.org; Sat, 28 Dec 2013 09:23:50 +0000 Received: from [193.109.254.147:33821] by server-6.bemta-14.messagelabs.com id 22/47-14958-5A89EB25; Sat, 28 Dec 2013 09:23:49 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1388222626!6315569!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15876 invoked from network); 28 Dec 2013 09:23:47 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Dec 2013 09:23:47 -0000 Received: by mail-pa0-f47.google.com with SMTP id kq14so10044299pab.34 for ; Sat, 28 Dec 2013 01:23:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z9lVv47sondPEi4YSzaKWNvDbLsMHLD3PDocBszVefQ=; b=nHI/L3ABTnrbVUTSD5WSMTv83UgRV7E/7+R3sImDCm4Uzr+7lrgHgmUogRrJ7c1brd jIbJ7A6RqrjOaOMVml3glaN1u6PVFJFGK5/1MHMZVjaQYIDVROU/gLMcoeVWPV8XGp1h GidNHZ6sFOEDTGKXDpunZLvykdQiHQHPBMQfz/WrSvOf/kWZGqWwiH12zxrJzxYaCgVh NWmDKBQ4BSunFW5dgh1QxccAd6ZWOFbt77oW1rAXJYdzMtXIQObXgbWPl2VYFQx/9h9R LDKwhGJI48mqbwg5bcxHG2EMXsbvKWucrVdYsbgwY1VNy1OqWAQ9PG2Oy42z0HkKoWG+ tcpQ== MIME-Version: 1.0 X-Received: by 10.68.234.67 with SMTP id uc3mr42446665pbc.27.1388222625938; Sat, 28 Dec 2013 01:23:45 -0800 (PST) Received: by 10.70.61.136 with HTTP; Sat, 28 Dec 2013 01:23:45 -0800 (PST) Received: by 10.70.61.136 with HTTP; Sat, 28 Dec 2013 01:23:45 -0800 (PST) In-Reply-To: References: Date: Sat, 28 Dec 2013 09:23:45 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: Thomas Gazagnaire , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6272841739948363146==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6272841739948363146== Content-Type: multipart/alternative; boundary=047d7b33d7a87d02c404ee94c493 --047d7b33d7a87d02c404ee94c493 Content-Type: text/plain; charset=ISO-8859-1 On 28 Dec 2013 00:01, "Anil Madhavapeddy" wrote: > > On 27 Dec 2013, at 12:14, Thomas Gazagnaire wrote: > > > Hi, > > > > During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: > > > > https://github.com/mirage/mirage/pull/178 > > > > The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. > > > > The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli > > > > Some examples: > > * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml > > * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml > > * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml > Fancy! > At a quick run-through, this looks like exactly what we need to layer interesting transformer drivers together. I'll take a shot at a buffer cache for KV_RO using your branch and see what it looks like (do you already have code for this somewhere, Dave?) I've been threatening to write a cache but haven't got round to it. I was wondering about creating a reusable LRU thing and allowing it to be used in multiple places. > > > Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... > > Indeed! > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --047d7b33d7a87d02c404ee94c493 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On 28 Dec 2013 00:01, "Anil Madhavapeddy" <anil@recoil.org> wrote:
>
> On 27 Dec 2013, at 12:14, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
>
> > Hi,
> >
> > During the last days, I've been working on a new version of t= he mirage API which should be easier to extend and where defining new opera= tors would be easier. I'm starting to be happy with the result, which i= s available here:
> >
> > https://git= hub.com/mirage/mirage/pull/178
> >
> > The branch is not ready to merge yet, but I've published it a= nyway to get early feedback, so feel free to shout if you dislike it or hav= e better ideas.
> >
> > The new API: https://github.com/samoht/mirage/blob/combinators/= lib/mirage.mli
> >
> > Some examples:
> > * https://github.com/samoht/mirage/blob/combinators/lib= _test/fat/config.ml
> > * https://github.com/samoht/mirage/blob/combinators/li= b_test/http/config.ml
> > * some combinator examples: https://github.com/s= amoht/mirage/blob/combinators/lib_test/combinator/config.ml
>

Fancy!

> At a quick run-through, this looks like exactly what we= need to layer interesting transformer drivers together. =A0I'll take a= shot at a buffer cache for KV_RO using your branch and see what it looks l= ike (do you already have code for this somewhere, Dave?)

I've been threatening to write a cache but haven't g= ot round to it. I was wondering about creating a reusable LRU thing and all= owing it to be used in multiple places.

>
> > Some of you might have noticed some similarity with the great cty= pe library -- it's not a coincidence at all: the goal here is to meta-p= rogram at the modules/functors level, which is not very far from trying to = interface with a foreign language ...
>
> Indeed!
>
> -anil
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@= lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-dev= el

--047d7b33d7a87d02c404ee94c493-- --===============6272841739948363146== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6272841739948363146==-- From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 09:23:55 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 09:23:55 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vwq7c-00045P-9g; Sat, 28 Dec 2013 09:23:52 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vwq7a-00045K-Lu for mirageos-devel@lists.xenproject.org; Sat, 28 Dec 2013 09:23:50 +0000 Received: from [193.109.254.147:33821] by server-6.bemta-14.messagelabs.com id 22/47-14958-5A89EB25; Sat, 28 Dec 2013 09:23:49 +0000 X-Env-Sender: scott.dj@gmail.com X-Msg-Ref: server-16.tower-27.messagelabs.com!1388222626!6315569!1 X-Originating-IP: [209.85.220.47] X-SpamReason: No, hits=0.4 required=7.0 tests=HTML_30_40,HTML_MESSAGE, ML_RADAR_SPEW_LINKS_14,RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15876 invoked from network); 28 Dec 2013 09:23:47 -0000 Received: from mail-pa0-f47.google.com (HELO mail-pa0-f47.google.com) (209.85.220.47) by server-16.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 28 Dec 2013 09:23:47 -0000 Received: by mail-pa0-f47.google.com with SMTP id kq14so10044299pab.34 for ; Sat, 28 Dec 2013 01:23:46 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z9lVv47sondPEi4YSzaKWNvDbLsMHLD3PDocBszVefQ=; b=nHI/L3ABTnrbVUTSD5WSMTv83UgRV7E/7+R3sImDCm4Uzr+7lrgHgmUogRrJ7c1brd jIbJ7A6RqrjOaOMVml3glaN1u6PVFJFGK5/1MHMZVjaQYIDVROU/gLMcoeVWPV8XGp1h GidNHZ6sFOEDTGKXDpunZLvykdQiHQHPBMQfz/WrSvOf/kWZGqWwiH12zxrJzxYaCgVh NWmDKBQ4BSunFW5dgh1QxccAd6ZWOFbt77oW1rAXJYdzMtXIQObXgbWPl2VYFQx/9h9R LDKwhGJI48mqbwg5bcxHG2EMXsbvKWucrVdYsbgwY1VNy1OqWAQ9PG2Oy42z0HkKoWG+ tcpQ== MIME-Version: 1.0 X-Received: by 10.68.234.67 with SMTP id uc3mr42446665pbc.27.1388222625938; Sat, 28 Dec 2013 01:23:45 -0800 (PST) Received: by 10.70.61.136 with HTTP; Sat, 28 Dec 2013 01:23:45 -0800 (PST) Received: by 10.70.61.136 with HTTP; Sat, 28 Dec 2013 01:23:45 -0800 (PST) In-Reply-To: References: Date: Sat, 28 Dec 2013 09:23:45 +0000 Message-ID: From: David Scott To: Anil Madhavapeddy Cc: Thomas Gazagnaire , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============6272841739948363146==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============6272841739948363146== Content-Type: multipart/alternative; boundary=047d7b33d7a87d02c404ee94c493 --047d7b33d7a87d02c404ee94c493 Content-Type: text/plain; charset=ISO-8859-1 On 28 Dec 2013 00:01, "Anil Madhavapeddy" wrote: > > On 27 Dec 2013, at 12:14, Thomas Gazagnaire wrote: > > > Hi, > > > > During the last days, I've been working on a new version of the mirage API which should be easier to extend and where defining new operators would be easier. I'm starting to be happy with the result, which is available here: > > > > https://github.com/mirage/mirage/pull/178 > > > > The branch is not ready to merge yet, but I've published it anyway to get early feedback, so feel free to shout if you dislike it or have better ideas. > > > > The new API: https://github.com/samoht/mirage/blob/combinators/lib/mirage.mli > > > > Some examples: > > * https://github.com/samoht/mirage/blob/combinators/lib_test/fat/config.ml > > * https://github.com/samoht/mirage/blob/combinators/lib_test/http/config.ml > > * some combinator examples: https://github.com/samoht/mirage/blob/combinators/lib_test/combinator/config.ml > Fancy! > At a quick run-through, this looks like exactly what we need to layer interesting transformer drivers together. I'll take a shot at a buffer cache for KV_RO using your branch and see what it looks like (do you already have code for this somewhere, Dave?) I've been threatening to write a cache but haven't got round to it. I was wondering about creating a reusable LRU thing and allowing it to be used in multiple places. > > > Some of you might have noticed some similarity with the great ctype library -- it's not a coincidence at all: the goal here is to meta-program at the modules/functors level, which is not very far from trying to interface with a foreign language ... > > Indeed! > > -anil > _______________________________________________ > MirageOS-devel mailing list > MirageOS-devel@lists.xenproject.org > http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --047d7b33d7a87d02c404ee94c493 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable


On 28 Dec 2013 00:01, "Anil Madhavapeddy" <anil@recoil.org> wrote:
>
> On 27 Dec 2013, at 12:14, Thomas Gazagnaire <thomas@gazagnaire.org> wrote:
>
> > Hi,
> >
> > During the last days, I've been working on a new version of t= he mirage API which should be easier to extend and where defining new opera= tors would be easier. I'm starting to be happy with the result, which i= s available here:
> >
> > https://git= hub.com/mirage/mirage/pull/178
> >
> > The branch is not ready to merge yet, but I've published it a= nyway to get early feedback, so feel free to shout if you dislike it or hav= e better ideas.
> >
> > The new API: https://github.com/samoht/mirage/blob/combinators/= lib/mirage.mli
> >
> > Some examples:
> > * https://github.com/samoht/mirage/blob/combinators/lib= _test/fat/config.ml
> > * https://github.com/samoht/mirage/blob/combinators/li= b_test/http/config.ml
> > * some combinator examples: https://github.com/s= amoht/mirage/blob/combinators/lib_test/combinator/config.ml
>

Fancy!

> At a quick run-through, this looks like exactly what we= need to layer interesting transformer drivers together. =A0I'll take a= shot at a buffer cache for KV_RO using your branch and see what it looks l= ike (do you already have code for this somewhere, Dave?)

I've been threatening to write a cache but haven't g= ot round to it. I was wondering about creating a reusable LRU thing and all= owing it to be used in multiple places.

>
> > Some of you might have noticed some similarity with the great cty= pe library -- it's not a coincidence at all: the goal here is to meta-p= rogram at the modules/functors level, which is not very far from trying to = interface with a foreign language ...
>
> Indeed!
>
> -anil
> _______________________________________________
> MirageOS-devel mailing list
> MirageOS-devel@= lists.xenproject.org
> http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-dev= el

--047d7b33d7a87d02c404ee94c493-- --===============6272841739948363146== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============6272841739948363146==-- From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 09:26:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 09:26:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwqAO-00046p-KM; Sat, 28 Dec 2013 09:26:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwqAN-00046i-7H for mirageos-devel@lists.xenproject.org; Sat, 28 Dec 2013 09:26:43 +0000 Received: from [85.158.143.35:51463] by server-3.bemta-4.messagelabs.com id 7F/86-32360-2599EB25; Sat, 28 Dec 2013 09:26:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-21.messagelabs.com!1388222801!8469974!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2385 invoked from network); 28 Dec 2013 09:26:41 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-21.messagelabs.com with SMTP; 28 Dec 2013 09:26:41 -0000 Received: (qmail 11811 invoked by uid 634); 28 Dec 2013 09:26:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 28 Dec 2013 09:26:41 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 28 Dec 2013 09:26:39 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2207126252080327857==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2207126252080327857== Content-Type: multipart/alternative; boundary="Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882" --Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 28 Dec 2013, at 09:23, David Scott wrote: > I've been threatening to write a cache but haven't got round to it. I = was wondering about creating a reusable LRU thing and allowing it to be = used in multiple places. >=20 There are a lot of fixed-size pooled data structures in Core (in the = Zero module). Worth looking there for inspiration. I'm a bit reluctant = to put a dependency on Core until module aliases show up (due to the = binary sizes that'll result if all of Core.Std is pulled in). -anil= --Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 28 = Dec 2013, at 09:23, David Scott <scott.dj@gmail.com> = wrote:

I've been threatening to write a cache = but haven't got round to it. I was wondering about creating a reusable = LRU thing and allowing it to be used in multiple = places.

There are a lot of fixed-size pooled data = structures in Core (in the Zero module).  Worth looking there for = inspiration.  I'm a bit reluctant to put a dependency on Core until = module aliases show up (due to the binary sizes that'll result if all of = Core.Std is pulled in).

-anil
= --Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882-- --===============2207126252080327857== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2207126252080327857==-- From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 09:26:44 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 09:26:44 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwqAO-00046p-KM; Sat, 28 Dec 2013 09:26:44 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwqAN-00046i-7H for mirageos-devel@lists.xenproject.org; Sat, 28 Dec 2013 09:26:43 +0000 Received: from [85.158.143.35:51463] by server-3.bemta-4.messagelabs.com id 7F/86-32360-2599EB25; Sat, 28 Dec 2013 09:26:42 +0000 X-Env-Sender: anil@recoil.org X-Msg-Ref: server-2.tower-21.messagelabs.com!1388222801!8469974!1 X-Originating-IP: [89.16.177.154] X-SpamReason: No, hits=0.1 required=7.0 tests=HTML_50_60,HTML_MESSAGE X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 2385 invoked from network); 28 Dec 2013 09:26:41 -0000 Received: from recoil.dh.bytemark.co.uk (HELO dark.recoil.org) (89.16.177.154) by server-2.tower-21.messagelabs.com with SMTP; 28 Dec 2013 09:26:41 -0000 Received: (qmail 11811 invoked by uid 634); 28 Dec 2013 09:26:41 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc2-belf1-0-0-cust23.2-1.cable.virginm.net (HELO [10.0.1.15]) (82.29.224.24) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Sat, 28 Dec 2013 09:26:41 +0000 Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) From: Anil Madhavapeddy In-Reply-To: Date: Sat, 28 Dec 2013 09:26:39 +0000 Message-Id: References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Thomas Gazagnaire , mirageos-devel@lists.xenproject.org Subject: Re: [MirageOS-devel] thought on a new API for mirage X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2207126252080327857==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============2207126252080327857== Content-Type: multipart/alternative; boundary="Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882" --Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 On 28 Dec 2013, at 09:23, David Scott wrote: > I've been threatening to write a cache but haven't got round to it. I = was wondering about creating a reusable LRU thing and allowing it to be = used in multiple places. >=20 There are a lot of fixed-size pooled data structures in Core (in the = Zero module). Worth looking there for inspiration. I'm a bit reluctant = to put a dependency on Core until module aliases show up (due to the = binary sizes that'll result if all of Core.Std is pulled in). -anil= --Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 On 28 = Dec 2013, at 09:23, David Scott <scott.dj@gmail.com> = wrote:

I've been threatening to write a cache = but haven't got round to it. I was wondering about creating a reusable = LRU thing and allowing it to be used in multiple = places.

There are a lot of fixed-size pooled data = structures in Core (in the Zero module).  Worth looking there for = inspiration.  I'm a bit reluctant to put a dependency on Core until = module aliases show up (due to the binary sizes that'll result if all of = Core.Std is pulled in).

-anil
= --Apple-Mail=_FFFA4936-5958-4B96-835F-96A96EF57882-- --===============2207126252080327857== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============2207126252080327857==-- From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 15:57:26 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 15:57:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwwGR-00068I-Dj; Sat, 28 Dec 2013 15:57:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwwGP-00067C-5p; Sat, 28 Dec 2013 15:57:21 +0000 Received: from [85.158.137.68:9518] by server-1.bemta-3.messagelabs.com id D9/43-29598-0E4FEB25; Sat, 28 Dec 2013 15:57:20 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1388246237!6321069!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27437 invoked from network); 28 Dec 2013 15:57:19 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 28 Dec 2013 15:57:19 -0000 X-IronPort-AV: E=Sophos;i="4.95,566,1384300800"; d="asc'?scan'208";a="88283519" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 28 Dec 2013 15:57:16 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Sat, 28 Dec 2013 10:57:15 -0500 Message-ID: <1388246226.15148.4.camel@Solace> From: Dario Faggioli To: Date: Sat, 28 Dec 2013 16:57:06 +0100 In-Reply-To: <52B03A2A.807@xen.org> References: <52B03A2A.807@xen.org> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "publicity@lists.xenproject.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3173450148132965699==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3173450148132965699== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-8xfV9F2fs6DyPs8VSOWG" --=-8xfV9F2fs6DyPs8VSOWG Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-17 at 11:48 +0000, Lars Kurth wrote: > Hi all, >=20 > I was just informed by the FOSDEM organizers. I wanted to invite=20 > community members (as well as vendors who do open source stuff and=20 > didn't get a booth) to help man the booth, show demos, have your=20 > hand-outs/swag there, etc. >=20 > If you are interested, please > a) Sign up to=20 > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity or send a= =20 > mail to publicity-request@lists.xenproject.org with subscribe in the=20 > subject line, where we will be discussing details > b) respond to this thread on what you may want to >=20 So I was wondering, we did not get that much of a response about this (or perhaps we did, but not in public, in which case, ignore me). I know, holidays are not helping, etc. but, anyway, should we turn this e-mail into a blog post to send out in early January? I'm up for it if we think it's a good thing to do. Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-8xfV9F2fs6DyPs8VSOWG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlK+9NIACgkQk4XaBE3IOsSHLACfWQJ40Ipm8LP281mNDnQmzZo9 B0YAnA/J6ZfGyUwu+k/dXvaW3kyqHke/ =L5yw -----END PGP SIGNATURE----- --=-8xfV9F2fs6DyPs8VSOWG-- --===============3173450148132965699== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3173450148132965699==-- From mirageos-devel-bounces@lists.xenproject.org Sat Dec 28 15:57:26 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Sat, 28 Dec 2013 15:57:26 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwwGR-00068I-Dj; Sat, 28 Dec 2013 15:57:23 +0000 Received: from mail6.bemta3.messagelabs.com ([195.245.230.39]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VwwGP-00067C-5p; Sat, 28 Dec 2013 15:57:21 +0000 Received: from [85.158.137.68:9518] by server-1.bemta-3.messagelabs.com id D9/43-29598-0E4FEB25; Sat, 28 Dec 2013 15:57:20 +0000 X-Env-Sender: dario.faggioli@citrix.com X-Msg-Ref: server-11.tower-31.messagelabs.com!1388246237!6321069!1 X-Originating-IP: [66.165.176.89] X-SpamReason: No, hits=0.0 required=7.0 tests=sa_preprocessor: VHJ1c3RlZCBJUDogNjYuMTY1LjE3Ni44OSA9PiAyMDMwMDc=\n X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 27437 invoked from network); 28 Dec 2013 15:57:19 -0000 Received: from smtp.citrix.com (HELO SMTP.CITRIX.COM) (66.165.176.89) by server-11.tower-31.messagelabs.com with RC4-SHA encrypted SMTP; 28 Dec 2013 15:57:19 -0000 X-IronPort-AV: E=Sophos;i="4.95,566,1384300800"; d="asc'?scan'208";a="88283519" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 28 Dec 2013 15:57:16 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Sat, 28 Dec 2013 10:57:15 -0500 Message-ID: <1388246226.15148.4.camel@Solace> From: Dario Faggioli To: Date: Sat, 28 Dec 2013 16:57:06 +0100 In-Reply-To: <52B03A2A.807@xen.org> References: <52B03A2A.807@xen.org> X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "publicity@lists.xenproject.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============3173450148132965699==" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org --===============3173450148132965699== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-8xfV9F2fs6DyPs8VSOWG" --=-8xfV9F2fs6DyPs8VSOWG Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-17 at 11:48 +0000, Lars Kurth wrote: > Hi all, >=20 > I was just informed by the FOSDEM organizers. I wanted to invite=20 > community members (as well as vendors who do open source stuff and=20 > didn't get a booth) to help man the booth, show demos, have your=20 > hand-outs/swag there, etc. >=20 > If you are interested, please > a) Sign up to=20 > http://lists.xenproject.org/cgi-bin/mailman/listinfo/publicity or send a= =20 > mail to publicity-request@lists.xenproject.org with subscribe in the=20 > subject line, where we will be discussing details > b) respond to this thread on what you may want to >=20 So I was wondering, we did not get that much of a response about this (or perhaps we did, but not in public, in which case, ignore me). I know, holidays are not helping, etc. but, anyway, should we turn this e-mail into a blog post to send out in early January? I'm up for it if we think it's a good thing to do. Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-8xfV9F2fs6DyPs8VSOWG Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEABECAAYFAlK+9NIACgkQk4XaBE3IOsSHLACfWQJ40Ipm8LP281mNDnQmzZo9 B0YAnA/J6ZfGyUwu+k/dXvaW3kyqHke/ =L5yw -----END PGP SIGNATURE----- --=-8xfV9F2fs6DyPs8VSOWG-- --===============3173450148132965699== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel --===============3173450148132965699==-- From mirageos-devel-bounces@lists.xenproject.org Mon Dec 30 19:28:46 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Dec 2013 19:28:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VxiW0-000144-5K; Mon, 30 Dec 2013 19:28:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VxiVz-00013x-1C for mirageos-devel@lists.xenproject.org; Mon, 30 Dec 2013 19:28:39 +0000 Received: from [193.109.254.147:30884] by server-6.bemta-14.messagelabs.com id C9/27-14958-669C1C25; Mon, 30 Dec 2013 19:28:38 +0000 X-Env-Sender: hugo.heuzard@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1388431716!8127741!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15304 invoked from network); 30 Dec 2013 19:28:37 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Dec 2013 19:28:37 -0000 Received: by mail-qc0-f170.google.com with SMTP id x13so11305709qcv.15 for ; Mon, 30 Dec 2013 11:28:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=lsUYV3PeBcmZDEma6Di0EE+3iJY1rbvIk37Vt71Lfxw=; b=ceRnQ2sYpD6rwk/D0u7bjXmaUfIYt0ToKIGIopMCe8Um3HmK72KTOpzMGZX0KgN2Pg VVh0cCxZsvMjVfQNsgkZiAvGJ6Rv+HAH5L32fIZZW85kiqMl6ELdI/HoFqYI+TNrpicM cJspWJIDhZAJFLazQcgGYjGo+UB2ihha10pU9PcAZ5GBeU4s7cCAQaf7Jf8xRha1/2z1 GvqOshImE2eeY+A2d2sRo6SP8mbbofSLXmHY4+6JRZVELsCzbHYZATEojkN9cnSKFpZU EjeCOxBq6xW4NlcfEOdEqoGFiMmBBP6D0zfyXuWu19ek7Szo8BR3oQTr0p/5z0AdDr7j Ui6g== X-Received: by 10.49.53.66 with SMTP id z2mr113202482qeo.45.1388431716391; Mon, 30 Dec 2013 11:28:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.118.33 with HTTP; Mon, 30 Dec 2013 11:28:16 -0800 (PST) From: hugo Date: Mon, 30 Dec 2013 11:28:16 -0800 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] porting ocsigenserver X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I would like to experiment with mirage and try to port ocsigen/eliom project. Are there any ongoing work in that direction ? Any advice ? What's the status of (native) dynlink ? Thanks, Hugo BTW: broken link on http://openmirage.org/community/ : [ Mirage issue tracker -> https://github.com/mirage/mirage/issue*s* ] _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Mon Dec 30 19:28:46 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Mon, 30 Dec 2013 19:28:46 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VxiW0-000144-5K; Mon, 30 Dec 2013 19:28:40 +0000 Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1VxiVz-00013x-1C for mirageos-devel@lists.xenproject.org; Mon, 30 Dec 2013 19:28:39 +0000 Received: from [193.109.254.147:30884] by server-6.bemta-14.messagelabs.com id C9/27-14958-669C1C25; Mon, 30 Dec 2013 19:28:38 +0000 X-Env-Sender: hugo.heuzard@gmail.com X-Msg-Ref: server-8.tower-27.messagelabs.com!1388431716!8127741!1 X-Originating-IP: [209.85.216.170] X-SpamReason: No, hits=0.3 required=7.0 tests=ML_RADAR_SPEW_LINKS_14, RCVD_BY_IP,spamassassin: X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15304 invoked from network); 30 Dec 2013 19:28:37 -0000 Received: from mail-qc0-f170.google.com (HELO mail-qc0-f170.google.com) (209.85.216.170) by server-8.tower-27.messagelabs.com with RC4-SHA encrypted SMTP; 30 Dec 2013 19:28:37 -0000 Received: by mail-qc0-f170.google.com with SMTP id x13so11305709qcv.15 for ; Mon, 30 Dec 2013 11:28:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=lsUYV3PeBcmZDEma6Di0EE+3iJY1rbvIk37Vt71Lfxw=; b=ceRnQ2sYpD6rwk/D0u7bjXmaUfIYt0ToKIGIopMCe8Um3HmK72KTOpzMGZX0KgN2Pg VVh0cCxZsvMjVfQNsgkZiAvGJ6Rv+HAH5L32fIZZW85kiqMl6ELdI/HoFqYI+TNrpicM cJspWJIDhZAJFLazQcgGYjGo+UB2ihha10pU9PcAZ5GBeU4s7cCAQaf7Jf8xRha1/2z1 GvqOshImE2eeY+A2d2sRo6SP8mbbofSLXmHY4+6JRZVELsCzbHYZATEojkN9cnSKFpZU EjeCOxBq6xW4NlcfEOdEqoGFiMmBBP6D0zfyXuWu19ek7Szo8BR3oQTr0p/5z0AdDr7j Ui6g== X-Received: by 10.49.53.66 with SMTP id z2mr113202482qeo.45.1388431716391; Mon, 30 Dec 2013 11:28:36 -0800 (PST) MIME-Version: 1.0 Received: by 10.96.118.33 with HTTP; Mon, 30 Dec 2013 11:28:16 -0800 (PST) From: hugo Date: Mon, 30 Dec 2013 11:28:16 -0800 Message-ID: To: mirageos-devel@lists.xenproject.org Subject: [MirageOS-devel] porting ocsigenserver X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org Hi, I would like to experiment with mirage and try to port ocsigen/eliom project. Are there any ongoing work in that direction ? Any advice ? What's the status of (native) dynlink ? Thanks, Hugo BTW: broken link on http://openmirage.org/community/ : [ Mirage issue tracker -> https://github.com/mirage/mirage/issue*s* ] _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 31 13:58:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 31 Dec 2013 13:58:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vxzpc-00026B-Dd; Tue, 31 Dec 2013 13:58:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vxzpa-00025V-K3; Tue, 31 Dec 2013 13:58:02 +0000 Received: from [85.158.143.35:28613] by server-2.bemta-4.messagelabs.com id 1B/47-11386-96DC2C25; Tue, 31 Dec 2013 13:58:01 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1388498280!8911260!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7757 invoked from network); 31 Dec 2013 13:58:00 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 31 Dec 2013 13:58:00 -0000 Received: by mail-wg0-f54.google.com with SMTP id n12so10870524wgh.21 for ; Tue, 31 Dec 2013 05:58:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GpQCyMwnMLJJa4Shm/9xymBhGt/ljc1Zu30CZy8IbGY=; b=wDdSVO9ZNPhxi5aoxtHyP5etq/R//FyauAmyhBjF07vGMxRwG/7gtu96cOGZkuLUs+ f3DwWq9gkw02SnTpEHQgqio5UvODHG+LeehI9AJrotsLlnvIAiSH3Xm5MrRtHl5UEgyC 6/7wgNJEAQN63k/cINSEVu28kUMBYv6qnOtmZnsQh5DGevcjbVGpaoLLwLRAm5e299xN /QBCzO1GhHPrFYbEvzusNRw/ZZk1FM4ggcfqPqgosEF4i/1oMqUVxWMQMbiZ7TP/yJrK RO8g+FPThV++LULFeUKGM9XldBT3wu6koRbAmFLPOd1RCzYb8vyhuR/05SgZo8BHlRPE foXw== X-Received: by 10.180.103.68 with SMTP id fu4mr48063573wib.19.1388498280545; Tue, 31 Dec 2013 05:58:00 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id gd5sm30079311wic.0.2013.12.31.05.57.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 31 Dec 2013 05:57:59 -0800 (PST) Message-ID: <52C2CD67.6050603@xen.org> Date: Tue, 31 Dec 2013 13:57:59 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Dario Faggioli References: <52B03A2A.807@xen.org> <1388246226.15148.4.camel@Solace> In-Reply-To: <1388246226.15148.4.camel@Solace> Cc: "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "publicity@lists.xenproject.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 28/12/2013 15:57, Dario Faggioli wrote: > So I was wondering, we did not get that much of a response about this > (or perhaps we did, but not in public, in which case, ignore me). > > I know, holidays are not helping, etc. but, anyway, should we turn this > e-mail into a blog post to send out in early January? I'm up for it if > we think it's a good thing to do. It is probably the holidays: I know that Cloudious Systems (the makers of OSv) are interested showing OSv running on top of Xen and so do the XO guys. A blog post could be a good idea (tying it up with the DevRoom program, which has not yet been published). Another approach would be to reach out pro-actively to people we want to do demos (e.g. Samsung, people/projects with RT schedulers, ...). Unfortunuately I will struggle to do this given that I am in China. Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From mirageos-devel-bounces@lists.xenproject.org Tue Dec 31 13:58:08 2013 Return-path: Envelope-to: archives@lists.xenproject.org Delivery-date: Tue, 31 Dec 2013 13:58:08 +0000 Received: from localhost ([127.0.0.1] helo=lists.xen.org) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vxzpc-00026B-Dd; Tue, 31 Dec 2013 13:58:04 +0000 Received: from mail6.bemta4.messagelabs.com ([85.158.143.247]) by lists.xen.org with esmtp (Exim 4.72) (envelope-from ) id 1Vxzpa-00025V-K3; Tue, 31 Dec 2013 13:58:02 +0000 Received: from [85.158.143.35:28613] by server-2.bemta-4.messagelabs.com id 1B/47-11386-96DC2C25; Tue, 31 Dec 2013 13:58:01 +0000 X-Env-Sender: lars.kurth.xen@gmail.com X-Msg-Ref: server-16.tower-21.messagelabs.com!1388498280!8911260!1 X-Originating-IP: [74.125.82.54] X-SpamReason: No, hits=0.2 required=7.0 tests=RCVD_ILLEGAL_IP X-StarScan-Received: X-StarScan-Version: 6.9.16; banners=-,-,- X-VirusChecked: Checked Received: (qmail 7757 invoked from network); 31 Dec 2013 13:58:00 -0000 Received: from mail-wg0-f54.google.com (HELO mail-wg0-f54.google.com) (74.125.82.54) by server-16.tower-21.messagelabs.com with RC4-SHA encrypted SMTP; 31 Dec 2013 13:58:00 -0000 Received: by mail-wg0-f54.google.com with SMTP id n12so10870524wgh.21 for ; Tue, 31 Dec 2013 05:58:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:message-id:date:from:reply-to:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=GpQCyMwnMLJJa4Shm/9xymBhGt/ljc1Zu30CZy8IbGY=; b=wDdSVO9ZNPhxi5aoxtHyP5etq/R//FyauAmyhBjF07vGMxRwG/7gtu96cOGZkuLUs+ f3DwWq9gkw02SnTpEHQgqio5UvODHG+LeehI9AJrotsLlnvIAiSH3Xm5MrRtHl5UEgyC 6/7wgNJEAQN63k/cINSEVu28kUMBYv6qnOtmZnsQh5DGevcjbVGpaoLLwLRAm5e299xN /QBCzO1GhHPrFYbEvzusNRw/ZZk1FM4ggcfqPqgosEF4i/1oMqUVxWMQMbiZ7TP/yJrK RO8g+FPThV++LULFeUKGM9XldBT3wu6koRbAmFLPOd1RCzYb8vyhuR/05SgZo8BHlRPE foXw== X-Received: by 10.180.103.68 with SMTP id fu4mr48063573wib.19.1388498280545; Tue, 31 Dec 2013 05:58:00 -0800 (PST) Received: from [172.16.26.11] ([2.122.219.75]) by mx.google.com with ESMTPSA id gd5sm30079311wic.0.2013.12.31.05.57.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 31 Dec 2013 05:57:59 -0800 (PST) Message-ID: <52C2CD67.6050603@xen.org> Date: Tue, 31 Dec 2013 13:57:59 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Dario Faggioli References: <52B03A2A.807@xen.org> <1388246226.15148.4.camel@Solace> In-Reply-To: <1388246226.15148.4.camel@Solace> Cc: "xen-users@lists.xen.org" , "xen-api@lists.xen.org" , "publicity@lists.xenproject.org" , mirageos-devel@lists.xenproject.org, "xen-devel@lists.xen.org" Subject: Re: [MirageOS-devel] [Publicity] Xen booth at FOSDEM : invitation to community members to help man the booth, show demos, have your hand-outs there, etc. X-BeenThere: mirageos-devel@lists.xenproject.org X-Mailman-Version: 2.1.13 Precedence: list Reply-To: lars.kurth@xen.org List-Id: Developer list for MirageOS List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: mirageos-devel-bounces@lists.xenproject.org Errors-To: mirageos-devel-bounces@lists.xenproject.org On 28/12/2013 15:57, Dario Faggioli wrote: > So I was wondering, we did not get that much of a response about this > (or perhaps we did, but not in public, in which case, ignore me). > > I know, holidays are not helping, etc. but, anyway, should we turn this > e-mail into a blog post to send out in early January? I'm up for it if > we think it's a good thing to do. It is probably the holidays: I know that Cloudious Systems (the makers of OSv) are interested showing OSv running on top of Xen and so do the XO guys. A blog post could be a good idea (tying it up with the DevRoom program, which has not yet been published). Another approach would be to reach out pro-actively to people we want to do demos (e.g. Samsung, people/projects with RT schedulers, ...). Unfortunuately I will struggle to do this given that I am in China. Regards Lars _______________________________________________ MirageOS-devel mailing list MirageOS-devel@lists.xenproject.org http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel From dunlapg@gmail.com Mon Dec 02 15:55:53 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VnVqj-0005P6-Fb (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 02 Dec 2013 15:55:53 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1546791 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.42 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (dunlapg[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wg0-f42.google.com ([74.125.82.42]:41746) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VnVqi-0000lm-1d (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 02 Dec 2013 15:55:53 +0000 Received: by mail-wg0-f42.google.com with SMTP id a1so4447119wgh.5 for ; Mon, 02 Dec 2013 07:55:52 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.95.73 with SMTP id di9mr18629185wib.28.1385999752228; Mon, 02 Dec 2013 07:55:52 -0800 (PST) Sender: dunlapg@gmail.com Received: by 10.194.242.162 with HTTP; Mon, 2 Dec 2013 07:55:52 -0800 (PST) In-Reply-To: <5294A073.9000209@xen.org> References: <5294A073.9000209@xen.org> Date: Mon, 2 Dec 2013 15:55:52 +0000 X-Google-Sender-Auth: lkjVYfV4mMGWUBQNSpu9h5Y66Tg Message-ID: Subject: Re: [Xen-devel] Testing for the Xen Project From: George Dunlap To: Lars Kurth Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 15:55:53 -0000 Content-Length: 1348 Lines: 35 On Tue, Nov 26, 2013 at 1:21 PM, Lars Kurth wrote: > Hi all, > > you probably have all heard by now that the Xen Project Advisory Board (a > group of vendors who provide funds to the Xen Project that are intended t= o > be used for the good of the community) recently created the Test Framewor= k > Working Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontain= s > more information about the group. The working group had its first meeting= a > few weeks ago and one of the actions I had was to kick off a thread on > development lists to figure out what would help the developer community. > > I was planning to kick off this thread with some questions and options, > which reflect some discussions I had with individuals in the community, > various meetings (WG and AB meetings), etc. which I condensed into a > picture. > > This reflects my personal opinion (not a Citrix opinion) and is merely > intended to get a discussion going. Feel free to pick it apart: I won=92t= be > upset. While I have a few quibbles, what you wrote seems to be a fair reflection of the situation as a whole. But I don't really see any action items, or questions. So other than quibble with little details, I don't see a way to engage with this and actually have a discussion. :-) What do you need from us right now? -George From scott.dj@gmail.com Mon Dec 02 22:49:26 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VncIw-000442-1q (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 02 Dec 2013 22:49:26 +0000 X-Cam-SpamDetails: score 0.6 from SpamAssassin-3.3.2-1546791 * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (scott.dj[at]gmail.com) * 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is * CUSTOM_MED * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.220.48 listed in list.dnswl.dnsbl.ja.net] * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid * 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing * list X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-pa0-f48.google.com ([209.85.220.48]:43311) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VncIv-0004GQ-7Q (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 02 Dec 2013 22:49:26 +0000 Received: by mail-pa0-f48.google.com with SMTP id rd3so2007702pab.21 for ; Mon, 02 Dec 2013 14:49:23 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.68.162.131 with SMTP id ya3mr34391716pbb.102.1386024563426; Mon, 02 Dec 2013 14:49:23 -0800 (PST) Received: by 10.70.56.36 with HTTP; Mon, 2 Dec 2013 14:49:23 -0800 (PST) Date: Mon, 2 Dec 2013 22:49:23 +0000 Message-ID: Subject: pre-1.0 progress From: David Scott To: Mirage List Content-Type: multipart/alternative; boundary=047d7b6d7c2ec0cbba04ec94fd74 X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 22:49:26 -0000 Content-Length: 4055 Lines: 86 --047d7b6d7c2ec0cbba04ec94fd74 Content-Type: text/plain; charset=ISO-8859-1 Hi, I thought I'd give a quick update on where I've got to with my current block hacking. I've experimentally added a "mirage-block" virtual package to my opam fork: https://github.com/djs55/opam-repository/tree/mirage-types It's a bit like the "mirage" package; it comes in two flavours: "mirage-block-unix" and "mirage-block-xen". Higher-level libraries like "fat-filesystem" (also in my fork) depend on "mirage-block" and the correct version should be installed depending on whether you're working on "mirage-unix" or "mirage-xen". Inside mirage-platform itself, I've added an experimental block driver registration facility common to both unix and xen: https://github.com/djs55/mirage-platform/blob/add-block/xen/lib/block.mli My plan is to modify the mirage-skeleton webserver example to read its resources from a fat-filesystem on a block device. Stuff left to do includes: 1. adjust mirage-block-xen to use the new BLOCK_DEVICE signature 2. figure out if there's any way of hiding the "register" step (otherwise all clients have to remember to register their block devices) 3. fix mirage-block-unix on OSX (currently broken due to use of Linux ioctls) 4. make the unix examples in fat-filesystem conditionally compile (they won't work on xen) Separately I've been working on Jon Ludlam's LVM library, refactoring it to use the same BLOCK_DEVICE signature as everything else. Part of this involves creating a simple on-disk persistent queue (like the existing shared-memory-ring). Perhaps this will be useful for something else in future. Cheers, -- Dave Scott --047d7b6d7c2ec0cbba04ec94fd74 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I thought I'd give a quick upda= te on where I've got to with my current block hacking. I've experim= entally added a "mirage-block" virtual package to my opam fork:



Higher-level libraries like "fat-filesystem" = (also in my fork) depend on "mirage-block" and the correct versio= n should be installed depending on whether you're working on "mira= ge-unix" or "mirage-xen".

Inside mirage-platform itself, I've added an experi= mental block driver registration facility common to both unix and xen:

My plan is to modify the mirage-skeleton webserver exam= ple to read its resources from a fat-filesystem on a block device. Stuff le= ft to do includes:

1. adjust mirage-block-xen to u= se the new BLOCK_DEVICE signature
2. figure out if there's any way of hiding the "register"= ; step (otherwise all clients have to remember to register their block devi= ces)
3. fix mirage-block-unix on OSX (currently broken due to use= of Linux ioctls)
4. make the unix examples in fat-filesystem conditionally compile (the= y won't work on xen)

Separately I've been = working on Jon Ludlam's LVM library, refactoring it to use the same BLO= CK_DEVICE signature as everything else. Part of this involves creating a si= mple on-disk persistent queue (like the existing shared-memory-ring). Perha= ps this will be useful for something else in future.

Cheers,
--
Dave Scott
--047d7b6d7c2ec0cbba04ec94fd74-- From anil@recoil.org Mon Dec 02 22:57:37 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VncQq-0004GK-Vm (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 02 Dec 2013 22:57:37 +0000 X-Cam-SpamDetails: score 0.0 from SpamAssassin-3.3.2-1546791 * 0.0 HTML_MESSAGE BODY: HTML included in message X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from recoil.dh.bytemark.co.uk ([89.16.177.154]:44958 helo=dark.recoil.org) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with smtp id 1VncQq-00069G-gq (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 02 Dec 2013 22:57:36 +0000 Received: (qmail 3864 invoked by uid 634); 2 Dec 2013 22:57:36 -0000 X-Spam-Level: * X-Spam-Status: No, hits=-1.0 required=5.0 tests=ALL_TRUSTED,HTML_MESSAGE X-Spam-Check-By: dark.recoil.org Received: from cpc7-cmbg14-2-0-cust238.5-4.cable.virginm.net (HELO [192.168.1.62]) (86.30.244.239) (smtp-auth username remote@recoil.org, mechanism cram-md5) by dark.recoil.org (qpsmtpd/0.84) with ESMTPA; Mon, 02 Dec 2013 22:57:31 +0000 Content-Type: multipart/alternative; boundary="Apple-Mail=_2D161A60-C444-4C08-B107-2D1555FC7110" Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1812\)) Subject: Re: pre-1.0 progress From: Anil Madhavapeddy In-Reply-To: Date: Mon, 2 Dec 2013 22:57:29 +0000 Message-Id: <2059CB73-E752-4ADB-AEDC-4367CF676005@recoil.org> References: To: David Scott X-Mailer: Apple Mail (2.1812) X-Virus-Checked: Checked by ClamAV on dark.recoil.org Cc: Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 02 Dec 2013 22:57:37 -0000 Content-Length: 7074 Lines: 145 --Apple-Mail=_2D161A60-C444-4C08-B107-2D1555FC7110 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Meanwhile, Thomas and I've been fixing up the Unix execution environment = to use the Release framework, so that the binaries running have a = similar execution model, with a well-specified lifecycle. The model (that Thomas is hacking on) is that mirari spawns a child = process that drops as much privilege as possible, and establishes an IPC = interface with the privileged master process, from which it gets all of = its resources. There is a per-user ~/.mirage directory which stores = sockets of all the active instances, so that `mirari list` will work in = Unix as well as Xen. One important module type that needs to be added that of a JOB, which = represents the lifecycle of a single unikernel process (such as a single = webserver). Since a job will need to satisfy some device dependencies, = this is likely how we can wrap the register step in 2) below. I'll make = sure these both align up tomorrow... PS: lots more slides available on http://decks.openmirage.org too -- I'm = teaching using some of these tomorrow, so we can adapt them for tutorial = purposes with a little more detail too. -anil On 2 Dec 2013, at 22:49, David Scott wrote: > Hi, >=20 > I thought I'd give a quick update on where I've got to with my current = block hacking. I've experimentally added a "mirage-block" virtual = package to my opam fork: >=20 > https://github.com/djs55/opam-repository/tree/mirage-types >=20 > It's a bit like the "mirage" package; it comes in two flavours: = "mirage-block-unix" and "mirage-block-xen". >=20 > Higher-level libraries like "fat-filesystem" (also in my fork) depend = on "mirage-block" and the correct version should be installed depending = on whether you're working on "mirage-unix" or "mirage-xen". >=20 > Inside mirage-platform itself, I've added an experimental block driver = registration facility common to both unix and xen: >=20 > = https://github.com/djs55/mirage-platform/blob/add-block/xen/lib/block.mli >=20 > My plan is to modify the mirage-skeleton webserver example to read its = resources from a fat-filesystem on a block device. Stuff left to do = includes: >=20 > 1. adjust mirage-block-xen to use the new BLOCK_DEVICE signature > 2. figure out if there's any way of hiding the "register" step = (otherwise all clients have to remember to register their block devices) > 3. fix mirage-block-unix on OSX (currently broken due to use of Linux = ioctls) > 4. make the unix examples in fat-filesystem conditionally compile = (they won't work on xen) >=20 > Separately I've been working on Jon Ludlam's LVM library, refactoring = it to use the same BLOCK_DEVICE signature as everything else. Part of = this involves creating a simple on-disk persistent queue (like the = existing shared-memory-ring). Perhaps this will be useful for something = else in future. >=20 > Cheers, > --=20 > Dave Scott --Apple-Mail=_2D161A60-C444-4C08-B107-2D1555FC7110 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 Meanwhile, Thomas and I've been fixing up the Unix = execution environment to use the Release framework, so that the binaries = running have a similar execution model, with a well-specified = lifecycle.

The model (that Thomas is hacking on) is = that mirari spawns a child process that drops as much privilege as = possible, and establishes an IPC interface with the privileged master = process, from which it gets all of its resources.  There is a = per-user ~/.mirage directory which stores sockets of all the active = instances, so that `mirari list` will work in Unix as well as = Xen.

One important module type that needs to be = added that of a JOB, which represents the lifecycle of a single = unikernel process (such as a single webserver).  Since a job will = need to satisfy some device dependencies, this is likely how we can wrap = the register step in 2) below.  I'll make sure these both align up = tomorrow...

PS: lots more slides available on = http://decks.openmirage.org = too -- I'm teaching using some of these tomorrow, so we can adapt them = for tutorial purposes with a little more detail = too.

-anil

On 2 Dec = 2013, at 22:49, David Scott <scott.dj@gmail.com> = wrote:

Hi,

I thought I'd give = a quick update on where I've got to with my current block hacking. I've = experimentally added a "mirage-block" virtual package to my opam = fork:


It's a bit like the "mirage" package; it comes in two flavours: = "mirage-block-unix" and "mirage-block-xen".

Higher-level libraries like "fat-filesystem" (also = in my fork) depend on "mirage-block" and the correct version should be = installed depending on whether you're working on "mirage-unix" or = "mirage-xen".

Inside mirage-platform itself, I've added an = experimental block driver registration facility common to both unix and = xen:


My plan is to modify the mirage-skeleton webserver = example to read its resources from a fat-filesystem on a block device. = Stuff left to do includes:

1. adjust = mirage-block-xen to use the new BLOCK_DEVICE signature
2. figure out if there's any way of hiding the "register" step = (otherwise all clients have to remember to register their block = devices)
3. fix mirage-block-unix on OSX (currently broken due = to use of Linux ioctls)
4. make the unix examples in fat-filesystem conditionally compile = (they won't work on xen)

Separately I've been = working on Jon Ludlam's LVM library, refactoring it to use the same = BLOCK_DEVICE signature as everything else. Part of this involves = creating a simple on-disk persistent queue (like the existing = shared-memory-ring). Perhaps this will be useful for something else in = future.

Cheers,
--
Dave Scott

= --Apple-Mail=_2D161A60-C444-4C08-B107-2D1555FC7110-- From balraj885@gmail.com Tue Dec 03 13:00:24 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VnpaS-0006hQ-H4 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 03 Dec 2013 13:00:24 +0000 X-Cam-SpamDetails: score -0.3 from SpamAssassin-3.3.2-1546929 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.47 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (balraj885[at]gmail.com) * 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in * digit (balraj885[at]gmail.com) * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wg0-f47.google.com ([74.125.82.47]:44039) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VnpaS-0004os-0N (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 03 Dec 2013 13:00:24 +0000 Received: by mail-wg0-f47.google.com with SMTP id n12so12181480wgh.2 for ; Tue, 03 Dec 2013 05:00:23 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.221.38 with SMTP id qb6mr2384086wic.8.1386075623357; Tue, 03 Dec 2013 05:00:23 -0800 (PST) Sender: balraj885@gmail.com Received: by 10.216.91.6 with HTTP; Tue, 3 Dec 2013 05:00:23 -0800 (PST) Date: Tue, 3 Dec 2013 13:00:23 +0000 X-Google-Sender-Auth: Or04NJhBZIMhjgaDt-h8P_O_sks Message-ID: Subject: Question about TCP checksum offload in Xen From: Balraj Singh To: Mirage List Content-Type: multipart/alternative; boundary=001a1134d2da2985a204eca0e1c1 X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 13:00:24 -0000 Content-Length: 2851 Lines: 56 --001a1134d2da2985a204eca0e1c1 Content-Type: text/plain; charset=ISO-8859-1 Hi, I'm working on verifying TCP checksums on incoming packets in Mirage, but I've run into a bit of a problem. If TCP checksum offload is turned on on a virtual interface (this is the default), and if the TCP connection is local to the machine, it looks like Xen does not calculate the checksum at all. This may be valid because Xen may be providing a stronger guarantee, but it means that incoming packets don't have a valid checksum in the header. This then means that in Mirage we can't just have checksum verification turned on all the time. This would have been the safe fall back option and detecting that checksum offload is on, and then not duplicating the verification in Mirage would have been an optimisation. But it looks like this is not an option. Now I need to know for every incoming packet whether checksum verification should be done or not. It should ideally be for every packet since chksum offload can be turned off and on on the VIF and existing tcp connections should continue. If not every packet, I need to get a notification or efficiently detect right away that the setting is changed on the VIF. Help / suggestions please. Thanks, Balraj --001a1134d2da2985a204eca0e1c1 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Hi,

I'm working on verifying TCP ch= ecksums on incoming packets in Mirage, but I've run into a bit of a pro= blem.=A0

If TCP checksum offload is turned on on a= virtual interface=A0(this is the default), and if the TCP connection is lo= cal to the machine, it looks like Xen does not calculate the checksum at al= l. =A0This may be valid because Xen may be providing a stronger guarantee, = but it means that incoming packets don't have a valid checksum in the h= eader. =A0This then means that in Mirage we can't just have checksum ve= rification turned on all the time. =A0This would have been the safe fall ba= ck option and detecting that checksum offload is on, and then not duplicati= ng the verification in Mirage would have been an optimisation. =A0But it lo= oks like this is not an option. =A0Now I need to know for every incoming pa= cket whether checksum verification should be done or not. =A0It should idea= lly be for every packet since chksum offload can be turned off and on on th= e VIF and existing tcp connections should continue. =A0If not every packet,= I need to get a notification or efficiently detect right away that the set= ting is changed on the VIF.

Help / suggestions please.

Tha= nks,

Balraj



--001a1134d2da2985a204eca0e1c1-- From amirmc@gmail.com Tue Dec 03 16:55:04 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VntFY-00058B-4Z (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 03 Dec 2013 16:55:04 +0000 X-Cam-SpamDetails: score 0.6 from SpamAssassin-3.3.2-1546929 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.214.51 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (amirmc[at]gmail.com) * 0.0 DKIM_ADSP_CUSTOM_MED No valid author signature, adsp_override is * CUSTOM_MED * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid * 1.2 NML_ADSP_CUSTOM_MED ADSP custom_med hit, and not from a mailing * list X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-bk0-f51.google.com ([209.85.214.51]:54974) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VntFX-0000aY-8f (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 03 Dec 2013 16:55:04 +0000 Received: by mail-bk0-f51.google.com with SMTP id 6so6105017bkj.38 for ; Tue, 03 Dec 2013 08:55:03 -0800 (PST) X-Received: by 10.204.108.2 with SMTP id d2mr1178692bkp.79.1386089703262; Tue, 03 Dec 2013 08:55:03 -0800 (PST) Received: from [10.144.5.182] (dab-crx1-h-1-2.dab.02.net. [82.132.224.222]) by mx.google.com with ESMTPSA id qe6sm78883047bkb.5.2013.12.03.08.55.01 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 03 Dec 2013 08:55:02 -0800 (PST) Subject: Migrating the Mirage List on Friday From: Amir Chaudhry Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (11A465) Message-Id: Date: Tue, 3 Dec 2013 16:54:58 +0000 To: Mirage List Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 03 Dec 2013 16:55:04 -0000 Content-Length: 831 Lines: 30 Dear all,=20 As mentioned a few months ago, we've been planning to move the Mirage list t= o xen.org. That will now happen on Friday morning and here's how it'll go (y= ou don't need to do anything). 1. A new list will be created at lists.xenproject.org (mirageos-devel@) 2. List members will be added to the new list.=20 3a. On Friday morning, this list will be put into moderation mode (ie to sto= p further messages being sent). Either myself or Anil will let everyone know= when this happens.=20 3b. Shortly after the above, an email will be sent on the new list and it'll= be open for business.=20 4. Archives will be ported across at a later date.=20 The first two are already done (or underway). Just be aware of the new list= address from Friday onwards.=20 Thanks all! Best wishes, Amir -- sent via mobile= From lars.kurth.xen@gmail.com Wed Dec 04 13:07:08 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoCAW-0000Uv-KU (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 04 Dec 2013 13:07:08 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1547315 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.83.52 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (lars.kurth.xen[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-ee0-f52.google.com ([74.125.83.52]:51676) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoCAV-0008Sz-3B (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 04 Dec 2013 13:07:08 +0000 Received: by mail-ee0-f52.google.com with SMTP id d17so2177319eek.39 for ; Wed, 04 Dec 2013 05:07:07 -0800 (PST) X-Received: by 10.15.76.6 with SMTP id m6mr11347161eey.37.1386162427690; Wed, 04 Dec 2013 05:07:07 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id a51sm94058860eeh.8.2013.12.04.05.07.06 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 04 Dec 2013 05:07:06 -0800 (PST) Sender: Lars Kurth Message-ID: <529F28F9.6070901@xen.org> Date: Wed, 04 Dec 2013 13:07:05 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: cl-mirage@lists.cam.ac.uk Subject: Re: Migrating the Mirage List on Friday References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list Reply-To: lars.kurth@xen.org List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 04 Dec 2013 13:07:08 -0000 Content-Length: 1160 Lines: 35 Hi all, the new list exists at http://lists.xenproject.org/cgi-bin/mailman/listinfo/mirageos-devel - it is in emergency moderation mode right now, such that we can have a clean switch-over. I signed you all up and am about to forward this mail as test mail. Best Regards Lars On 03/12/2013 16:54, Amir Chaudhry wrote: > Dear all, > > As mentioned a few months ago, we've been planning to move the Mirage list to xen.org. That will now happen on Friday morning and here's how it'll go (you don't need to do anything). > > 1. A new list will be created at lists.xenproject.org (mirageos-devel@) > > 2. List members will be added to the new list. > > 3a. On Friday morning, this list will be put into moderation mode (ie to stop further messages being sent). Either myself or Anil will let everyone know when this happens. > > 3b. Shortly after the above, an email will be sent on the new list and it'll be open for business. > > 4. Archives will be ported across at a later date. > > The first two are already done (or underway). Just be aware of the new list address from Friday onwards. > > Thanks all! > > Best wishes, > Amir > > -- > sent via mobile From avsm@dark.recoil.org Thu Dec 05 11:29:54 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoX7y-00078l-Lu (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:29:54 +0000 X-Cam-SpamDetails: score 0.0 from SpamAssassin-3.3.2-1547729 X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from recoil.dh.bytemark.co.uk ([89.16.177.154]:26645 helo=dark.recoil.org) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with smtp id 1VoX7y-00068L-6W (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:29:54 +0000 Received: (qmail 15904 invoked by uid 10000); 5 Dec 2013 11:29:53 -0000 Date: Thu, 5 Dec 2013 11:29:53 +0000 From: Anil Madhavapeddy To: Balraj Singh , xen-devel@lists.xenproject.org Subject: Re: Question about TCP checksum offload in Xen Message-ID: <20131205112952.GF14792@dark.recoil.org> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 11:29:54 -0000 Content-Length: 1634 Lines: 31 On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > Hi, > > I'm working on verifying TCP checksums on incoming packets in Mirage, but > I've run into a bit of a problem. > > If TCP checksum offload is turned on on a virtual interface (this is the > default), and if the TCP connection is local to the machine, it looks like > Xen does not calculate the checksum at all. This may be valid because Xen > may be providing a stronger guarantee, but it means that incoming packets > don't have a valid checksum in the header. This then means that in Mirage > we can't just have checksum verification turned on all the time. This > would have been the safe fall back option and detecting that checksum > offload is on, and then not duplicating the verification in Mirage would > have been an optimisation. But it looks like this is not an option. Now I > need to know for every incoming packet whether checksum verification should > be done or not. It should ideally be for every packet since chksum offload > can be turned off and on on the VIF and existing tcp connections should > continue. If not every packet, I need to get a notification or efficiently > detect right away that the setting is changed on the VIF. This is a question that seems to keep coming up even for Linux and Windows, as the combination of local<->local VMs vs local<->off-host and the checksum offload is quite confusing. CCing xen-devel: is the appropriate behaviour for a guest VM that wants to use checksum offloading in all situations documented anywhere? -- Anil Madhavapeddy http://anil.recoil.org From Ian.Campbell@citrix.com Thu Dec 05 11:39:10 2013 Received: from ppsw-52.csi.cam.ac.uk ([131.111.8.152]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoXGw-0007V6-RR (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:39:10 +0000 X-Cam-SpamDetails: score -0.7 from SpamAssassin-3.3.2-1547729 * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [66.165.176.63 listed in list.dnswl.dnsbl.ja.net] X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp02.citrix.com ([66.165.176.63]:29837) by ppsw-52.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.148]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoXGw-0007Mn-DV (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:39:10 +0000 X-IronPort-AV: E=Sophos;i="4.93,832,1378857600"; d="scan'208";a="78530786" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Dec 2013 11:39:08 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Thu, 5 Dec 2013 06:39:07 -0500 Message-ID: <1386243546.20047.26.camel@kazak.uk.xensource.com> Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen From: Ian Campbell To: Anil Madhavapeddy Date: Thu, 5 Dec 2013 11:39:06 +0000 In-Reply-To: <20131205112952.GF14792@dark.recoil.org> References: <20131205112952.GF14792@dark.recoil.org> Organization: Citrix Systems, Inc. Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: xen-devel@lists.xenproject.org, Balraj Singh , Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 11:39:10 -0000 Content-Length: 1848 Lines: 36 On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > > Hi, > > > > I'm working on verifying TCP checksums on incoming packets in Mirage, but > > I've run into a bit of a problem. > > > > If TCP checksum offload is turned on on a virtual interface (this is the > > default), and if the TCP connection is local to the machine, it looks like > > Xen does not calculate the checksum at all. This may be valid because Xen > > may be providing a stronger guarantee, but it means that incoming packets > > don't have a valid checksum in the header. This then means that in Mirage > > we can't just have checksum verification turned on all the time. This > > would have been the safe fall back option and detecting that checksum > > offload is on, and then not duplicating the verification in Mirage would > > have been an optimisation. But it looks like this is not an option. Now I > > need to know for every incoming packet whether checksum verification should > > be done or not. It should ideally be for every packet since chksum offload > > can be turned off and on on the VIF and existing tcp connections should > > continue. If not every packet, I need to get a notification or efficiently > > detect right away that the setting is changed on the VIF. > > This is a question that seems to keep coming up even for Linux and > Windows, as the combination of local<->local VMs vs local<->off-host and > the checksum offload is quite confusing. > > CCing xen-devel: is the appropriate behaviour for a guest VM that wants to > use checksum offloading in all situations documented anywhere? I don't understand the question/concern. If you have enabled checksum offload then of course you don't recalculate the checksum, that's the whole point of offloading it. Ian. From Richard.Mortier@nottingham.ac.uk Thu Dec 05 11:45:50 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoXNO-0007lO-Ts (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:45:50 +0000 X-Cam-SpamDetails: score 0.0 from SpamAssassin-3.3.2-1547729 * 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from engine04-20433-4.icritical.com ([195.62.217.152]:37663) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with smtp id 1VoXNO-0002Re-hB (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:45:50 +0000 Received: (qmail 15239 invoked from network); 5 Dec 2013 11:45:37 -0000 Received: from localhost (127.0.0.1) by engine04-20433-4.icritical.com with SMTP; 5 Dec 2013 11:45:37 -0000 Received: from engine04-20433-4.icritical.com ([127.0.0.1]) by localhost (engine04-20433-4.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 15174-02 for ; Thu, 5 Dec 2013 11:45:36 +0000 (GMT) Received: (qmail 14668 invoked by uid 599); 5 Dec 2013 11:45:02 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine04-20433-4.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 05 Dec 2013 11:45:02 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VoXMg-0001Wm-QQ for cl-mirage@lists.cam.ac.uk; Thu, 05 Dec 2013 11:45:06 +0000 From: Richard Mortier To: Ian Campbell Date: Thu, 5 Dec 2013 11:45:08 +0000 Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen Thread-Topic: [Xen-devel] Question about TCP checksum offload in Xen Thread-Index: Ac7xr3EQ+nUcApuDQaifq0XZjTYYdw== Message-ID: <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> In-Reply-To: <1386243546.20047.26.camel@kazak.uk.xensource.com> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine04-20433-4.icritical.com Cc: "xen-devel@lists.xenproject.org" , Mirage, Balraj Singh , List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 11:45:51 -0000 Content-Length: 2874 Lines: 70 On 5 Dec 2013, at 11:39, Ian Campbell wrote: > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: >> On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: >>> Hi, >>>=20 >>> I'm working on verifying TCP checksums on incoming packets in Mirage, b= ut >>> I've run into a bit of a problem. >>>=20 >>> If TCP checksum offload is turned on on a virtual interface (this is th= e >>> default), and if the TCP connection is local to the machine, it looks l= ike >>> Xen does not calculate the checksum at all. This may be valid because = Xen >>> may be providing a stronger guarantee, but it means that incoming packe= ts >>> don't have a valid checksum in the header. This then means that in Mir= age >>> we can't just have checksum verification turned on all the time. This >>> would have been the safe fall back option and detecting that checksum >>> offload is on, and then not duplicating the verification in Mirage woul= d >>> have been an optimisation. But it looks like this is not an option. N= ow I >>> need to know for every incoming packet whether checksum verification sh= ould >>> be done or not. It should ideally be for every packet since chksum off= load >>> can be turned off and on on the VIF and existing tcp connections should >>> continue. If not every packet, I need to get a notification or efficie= ntly >>> detect right away that the setting is changed on the VIF. >>=20 >> This is a question that seems to keep coming up even for Linux and >> Windows, as the combination of local<->local VMs vs local<->off-host and >> the checksum offload is quite confusing. >>=20 >> CCing xen-devel: is the appropriate behaviour for a guest VM that wants = to >> use checksum offloading in all situations documented anywhere? >=20 > I don't understand the question/concern. If you have enabled checksum > offload then of course you don't recalculate the checksum, that's the > whole point of offloading it. i think balraj's question arises because the status of checksum offload can= change mid-tcp-flow. how does he know whether it's on or off for a given p= acket? --=20 Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. From Paul.Durrant@citrix.com Thu Dec 05 11:47:14 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoXOk-00006V-GJ (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:47:14 +0000 X-Cam-SpamDetails: score -5.0 from SpamAssassin-3.3.2-1547729 * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [66.165.176.89 listed in list.dnswl.dnsbl.ja.net] * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp.citrix.com ([66.165.176.89]:56533) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoXOj-0003HV-if (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:47:14 +0000 X-IronPort-AV: E=Sophos;i="4.93,832,1378857600"; d="scan'208";a="80866830" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Dec 2013 11:47:12 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 5 Dec 2013 06:47:11 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.128]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Thu, 5 Dec 2013 12:47:10 +0100 From: Paul Durrant To: Ian Campbell , Anil Madhavapeddy Subject: RE: [Xen-devel] Question about TCP checksum offload in Xen Thread-Topic: [Xen-devel] Question about TCP checksum offload in Xen Thread-Index: AQHO8a2PE5HQHW0giUOjF4n3P+kuVZpFaRYAgAAScSA= Date: Thu, 5 Dec 2013 11:47:09 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD01A4261@AMSPEX01CL01.citrite.net> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> In-Reply-To: <1386243546.20047.26.camel@kazak.uk.xensource.com> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-DLP: MIA1 Cc: "xen-devel@lists.xenproject.org" , Balraj, Singh , Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 11:47:14 -0000 Content-Length: 2693 Lines: 67 > -----Original Message----- > From: xen-devel-bounces@lists.xen.org [mailto:xen-devel- > bounces@lists.xen.org] On Behalf Of Ian Campbell > Sent: 05 December 2013 11:39 > To: Anil Madhavapeddy > Cc: xen-devel@lists.xenproject.org; Balraj Singh; Mirage List > Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen >=20 > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > > > Hi, > > > > > > I'm working on verifying TCP checksums on incoming packets in Mirage, > but > > > I've run into a bit of a problem. > > > > > > If TCP checksum offload is turned on on a virtual interface (this is = the > > > default), and if the TCP connection is local to the machine, it looks= like > > > Xen does not calculate the checksum at all. This may be valid becaus= e > Xen > > > may be providing a stronger guarantee, but it means that incoming > packets > > > don't have a valid checksum in the header. This then means that in > Mirage > > > we can't just have checksum verification turned on all the time. Thi= s > > > would have been the safe fall back option and detecting that checksum > > > offload is on, and then not duplicating the verification in Mirage wo= uld > > > have been an optimisation. But it looks like this is not an option. = Now I > > > need to know for every incoming packet whether checksum verification > should > > > be done or not. It should ideally be for every packet since chksum > offload > > > can be turned off and on on the VIF and existing tcp connections shou= ld > > > continue. If not every packet, I need to get a notification or effic= iently > > > detect right away that the setting is changed on the VIF. > > > > This is a question that seems to keep coming up even for Linux and > > Windows, as the combination of local<->local VMs vs local<->off-host an= d > > the checksum offload is quite confusing. > > > > CCing xen-devel: is the appropriate behaviour for a guest VM that wants= to > > use checksum offloading in all situations documented anywhere? >=20 > I don't understand the question/concern. If you have enabled checksum > offload then of course you don't recalculate the checksum, that's the > whole point of offloading it. >=20 If your frontend doesn't advertise checksum offload at ring connect time th= en the backend should not advertise checksum offload to the network stack a= nd hence all packets passing to the VM should have valid checksum. If your = frontend *does* advertise offload then you need to look at the NETRXF flags= in the head descriptor of any packet you handle to determine the presence/= validity of any checksum. Paul From Ian.Campbell@citrix.com Thu Dec 05 11:52:34 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoXTu-0000Lo-SU (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:52:34 +0000 X-Cam-SpamDetails: score -0.7 from SpamAssassin-3.3.2-1547729 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [66.165.176.63 listed in list.dnswl.dnsbl.ja.net] * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp02.citrix.com ([66.165.176.63]:8029) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoXTt-0007cR-2E (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 11:52:34 +0000 X-IronPort-AV: E=Sophos;i="4.93,832,1378857600"; d="scan'208";a="78534142" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 05 Dec 2013 11:52:32 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Thu, 5 Dec 2013 06:52:31 -0500 Message-ID: <1386244350.20047.36.camel@kazak.uk.xensource.com> Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen From: Ian Campbell To: Richard Mortier Date: Thu, 5 Dec 2013 11:52:30 +0000 In-Reply-To: <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> Organization: Citrix Systems, Inc. Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: "xen-devel@lists.xenproject.org" , Mirage, Balraj Singh , List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 11:52:34 -0000 Content-Length: 2364 Lines: 48 On Thu, 2013-12-05 at 11:45 +0000, Richard Mortier wrote: > On 5 Dec 2013, at 11:39, Ian Campbell wrote: > > > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > >> On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > >>> Hi, > >>> > >>> I'm working on verifying TCP checksums on incoming packets in Mirage, but > >>> I've run into a bit of a problem. > >>> > >>> If TCP checksum offload is turned on on a virtual interface (this is the > >>> default), and if the TCP connection is local to the machine, it looks like > >>> Xen does not calculate the checksum at all. This may be valid because Xen > >>> may be providing a stronger guarantee, but it means that incoming packets > >>> don't have a valid checksum in the header. This then means that in Mirage > >>> we can't just have checksum verification turned on all the time. This > >>> would have been the safe fall back option and detecting that checksum > >>> offload is on, and then not duplicating the verification in Mirage would > >>> have been an optimisation. But it looks like this is not an option. Now I > >>> need to know for every incoming packet whether checksum verification should > >>> be done or not. It should ideally be for every packet since chksum offload > >>> can be turned off and on on the VIF and existing tcp connections should > >>> continue. If not every packet, I need to get a notification or efficiently > >>> detect right away that the setting is changed on the VIF. > >> > >> This is a question that seems to keep coming up even for Linux and > >> Windows, as the combination of local<->local VMs vs local<->off-host and > >> the checksum offload is quite confusing. > >> > >> CCing xen-devel: is the appropriate behaviour for a guest VM that wants to > >> use checksum offloading in all situations documented anywhere? > > > > I don't understand the question/concern. If you have enabled checksum > > offload then of course you don't recalculate the checksum, that's the > > whole point of offloading it. > > i think balraj's question arises because the status of checksum > offload can change mid-tcp-flow. how does he know whether it's on or > off for a given packet? It's a property of the NIC configuration. In Linux for example a received skb gets a field set which indicates the offload state at the time it was received. Ian. From john.haxby@oracle.com Thu Dec 05 12:38:04 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoYBv-0002Dd-VP (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 12:38:03 +0000 X-Cam-SpamDetails: score -2.3 from SpamAssassin-3.3.2-1547729 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [141.146.126.69 listed in list.dnswl.dnsbl.ja.net] * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain * 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay * lines X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from aserp1040.oracle.com ([141.146.126.69]:37987) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) id 1VoYBv-0005Hc-gu (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 12:38:03 +0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by aserp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id rB5CbwtT012594 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Dec 2013 12:37:59 GMT Received: from aserz7022.oracle.com (aserz7022.oracle.com [141.146.126.231]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id rB5CbtMV028550 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Dec 2013 12:37:56 GMT Received: from abhmp0002.oracle.com (abhmp0002.oracle.com [141.146.116.8]) by aserz7022.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id rB5Cbtn9013991; Thu, 5 Dec 2013 12:37:55 GMT Received: from sheep.uk.oracle.com (/10.167.241.51) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 05 Dec 2013 04:37:55 -0800 Message-ID: <52A073A1.4000102@oracle.com> Date: Thu, 05 Dec 2013 12:37:53 +0000 From: John Haxby User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Ian Campbell , Anil Madhavapeddy Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> In-Reply-To: <1386243546.20047.26.camel@kazak.uk.xensource.com> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: xen-devel@lists.xenproject.org, Balraj Singh , Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 12:38:04 -0000 Content-Length: 3494 Lines: 67 On 05/12/13 11:39, Ian Campbell wrote: > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: >> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: >>> > > Hi, >>> > > >>> > > I'm working on verifying TCP checksums on incoming packets in Mirage, but >>> > > I've run into a bit of a problem. >>> > > >>> > > If TCP checksum offload is turned on on a virtual interface (this is the >>> > > default), and if the TCP connection is local to the machine, it looks like >>> > > Xen does not calculate the checksum at all. This may be valid because Xen >>> > > may be providing a stronger guarantee, but it means that incoming packets >>> > > don't have a valid checksum in the header. This then means that in Mirage >>> > > we can't just have checksum verification turned on all the time. This >>> > > would have been the safe fall back option and detecting that checksum >>> > > offload is on, and then not duplicating the verification in Mirage would >>> > > have been an optimisation. But it looks like this is not an option. Now I >>> > > need to know for every incoming packet whether checksum verification should >>> > > be done or not. It should ideally be for every packet since chksum offload >>> > > can be turned off and on on the VIF and existing tcp connections should >>> > > continue. If not every packet, I need to get a notification or efficiently >>> > > detect right away that the setting is changed on the VIF. >> > >> > This is a question that seems to keep coming up even for Linux and >> > Windows, as the combination of local<->local VMs vs local<->off-host and >> > the checksum offload is quite confusing. >> > >> > CCing xen-devel: is the appropriate behaviour for a guest VM that wants to >> > use checksum offloading in all situations documented anywhere? > I don't understand the question/concern. If you have enabled checksum > offload then of course you don't recalculate the checksum, that's the > whole point of offloading it. I get this a lot. There are a few different cases: * domain to domain traffic * domain to external traffic with egress from a NIC that does offload * domain to external through a non-offloading NIC With xen checksum offloading, domain to domain traffic appears to be received with a bad checksum. This is OK, there is no point in calculating a checksum if the packets are only going through memory. If your memory is going to randomly corrupt packets you have more bigger problems to worry about. However, this does upset at least Solaris: if you're using a Solaris guest for NAT then the NAT module on Solaris gets all upset if the checksum is wrong and drops the packets. (This is Solaris's NAT module being overly picky, it may need to recalculate or at least invalidate the existing checksum, but it doesn't need to check it as well.) The second two cases are of interest from the domain perspective. A domain has no way of knowing how any given packet is going to leave the host (or even if it is) so it can't know ahead of time whether to calculate any checksums: the skb's are just marked with "checksum needed" as usual and either the egress NIC will do the job or dom0 will do it. There is absolutely nothing wrong in any of this (Solaris notwithstanding). The difficulty is getting people to realise that checksums are only calculated when a packet hits the cat-5. It doesn't need documenting, it just needs a little thought. I got tired of hammering the point home :) jch From Paul.Durrant@citrix.com Thu Dec 05 12:47:47 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoYLL-0002jy-H4 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 12:47:47 +0000 X-Cam-SpamDetails: score -5.0 from SpamAssassin-3.3.2-1547729 * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [66.165.176.89 listed in list.dnswl.dnsbl.ja.net] * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp.citrix.com ([66.165.176.89]:32082) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoYLK-00029x-gi (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 12:47:47 +0000 X-IronPort-AV: E=Sophos;i="4.93,832,1378857600"; d="scan'208";a="80884167" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Dec 2013 12:47:44 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 5 Dec 2013 07:47:43 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.128]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Thu, 5 Dec 2013 13:47:42 +0100 From: Paul Durrant To: Richard Mortier , Ian Campbell Subject: RE: [Xen-devel] Question about TCP checksum offload in Xen Thread-Topic: [Xen-devel] Question about TCP checksum offload in Xen Thread-Index: AQHO8a2PE5HQHW0giUOjF4n3P+kuVZpFaRYAgAABsACAACGfIA== Date: Thu, 5 Dec 2013 12:47:42 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD01A44B7@AMSPEX01CL01.citrite.net> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> In-Reply-To: <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-DLP: MIA1 Cc: Anil, Singh , Madhavapeddy , Balraj, "xen-devel@lists.xenproject.org" , Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 12:47:47 -0000 Content-Length: 2887 Lines: 76 > -----Original Message----- > From: xen-devel-bounces@lists.xen.org [mailto:xen-devel- > bounces@lists.xen.org] On Behalf Of Richard Mortier > Sent: 05 December 2013 11:45 > To: Ian Campbell > Cc: xen-devel@lists.xenproject.org; Balraj Singh; Mirage List; Anil > Madhavapeddy > Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen >=20 >=20 > On 5 Dec 2013, at 11:39, Ian Campbell wrote: >=20 > > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > >> On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > >>> Hi, > >>> > >>> I'm working on verifying TCP checksums on incoming packets in Mirage, > but > >>> I've run into a bit of a problem. > >>> > >>> If TCP checksum offload is turned on on a virtual interface (this is = the > >>> default), and if the TCP connection is local to the machine, it looks= like > >>> Xen does not calculate the checksum at all. This may be valid becaus= e > Xen > >>> may be providing a stronger guarantee, but it means that incoming > packets > >>> don't have a valid checksum in the header. This then means that in > Mirage > >>> we can't just have checksum verification turned on all the time. Thi= s > >>> would have been the safe fall back option and detecting that checksum > >>> offload is on, and then not duplicating the verification in Mirage wo= uld > >>> have been an optimisation. But it looks like this is not an option. = Now I > >>> need to know for every incoming packet whether checksum verification > should > >>> be done or not. It should ideally be for every packet since chksum > offload > >>> can be turned off and on on the VIF and existing tcp connections shou= ld > >>> continue. If not every packet, I need to get a notification or effic= iently > >>> detect right away that the setting is changed on the VIF. > >> > >> This is a question that seems to keep coming up even for Linux and > >> Windows, as the combination of local<->local VMs vs local<->off-host a= nd > >> the checksum offload is quite confusing. > >> > >> CCing xen-devel: is the appropriate behaviour for a guest VM that want= s > to > >> use checksum offloading in all situations documented anywhere? > > > > I don't understand the question/concern. If you have enabled checksum > > offload then of course you don't recalculate the checksum, that's the > > whole point of offloading it. >=20 > i think balraj's question arises because the status of checksum offload c= an > change mid-tcp-flow. how does he know whether it's on or off for a given > packet? >=20 Why do you assert that it can change mid-flow? The configuration is decided= at ring connect time. Nothing should change after that. If, at that time, = the frontend declares it can handle packets with no checksum then clearly i= t may get some packets that do have checksum as well as ones that don't, de= pending on where they originated. Paul From Richard.Mortier@nottingham.ac.uk Thu Dec 05 13:00:04 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoYXE-0003BS-A5 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:00:04 +0000 X-Cam-SpamDetails: score 0.0 from SpamAssassin-3.3.2-1547729 * 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from engine06-20433-6.icritical.com ([195.62.217.150]:57718) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with smtp id 1VoYXD-000640-9X (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:00:04 +0000 Received: (qmail 21642 invoked from network); 5 Dec 2013 12:59:58 -0000 Received: from localhost (127.0.0.1) by engine06-20433-6.icritical.com with SMTP; 5 Dec 2013 12:59:58 -0000 Received: from engine06-20433-6.icritical.com ([127.0.0.1]) by localhost (engine06-20433-6.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 21356-10 for ; Thu, 5 Dec 2013 12:59:58 +0000 (GMT) Received: (qmail 19760 invoked by uid 599); 5 Dec 2013 12:55:12 -0000 Received: from unknown (HELO smtp4.nottingham.ac.uk) (128.243.220.65) by engine06-20433-6.icritical.com (qpsmtpd/0.28) with ESMTP; Thu, 05 Dec 2013 12:55:12 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp4.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VoYSa-00026H-28 for cl-mirage@lists.cam.ac.uk; Thu, 05 Dec 2013 12:55:16 +0000 From: Richard Mortier To: Paul Durrant , Balraj Singh Date: Thu, 5 Dec 2013 12:55:15 +0000 Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen Thread-Topic: [Xen-devel] Question about TCP checksum offload in Xen Thread-Index: Ac7xuT4GFwudVOcPSAe0ocbwWQdyoQ== Message-ID: <74A8AF4B-21DE-4E43-A5F9-51A30E08FE9F@nottingham.ac.uk> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> <9AAE0902D5BC7E449B7C8E4E778ABCD01A44B7@AMSPEX01CL01.citrite.net> In-Reply-To: <9AAE0902D5BC7E449B7C8E4E778ABCD01A44B7@AMSPEX01CL01.citrite.net> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine06-20433-6.icritical.com Cc: "xen-devel@lists.xenproject.org" , Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 13:00:04 -0000 Content-Length: 1886 Lines: 50 On 5 Dec 2013, at 12:47, Paul Durrant wrote: ... >>>> On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: >>>>=20 ... >>>>> It should ideally be for every packet since chksum >> offload >>>>> can be turned off and on on the VIF and existing tcp connections shou= ld >>>>> continue. If not every packet, I need to get a notification or effic= iently >>>>> detect right away that the setting is changed on the VIF. ... > earlier today, i wrote: >=20 >> i think balraj's question arises because the status of checksum offload = can >> change mid-tcp-flow. how does he know whether it's on or off for a given >> packet? >=20 > Why do you assert that it can change mid-flow? The configuration is decid= ed at ring connect time. Nothing should change after that. If, at that time= , the frontend declares it can handle packets with no checksum then clearly= it may get some packets that do have checksum as well as ones that don't, = depending on where they originated. i didn't mean to :) i was just trying to point out to ian the reason for ba= lraj's question -- i'll leave it to balraj from here... --=20 Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. From balraj885@gmail.com Thu Dec 05 12:56:55 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoYUB-0002yA-0a (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 12:56:55 +0000 X-Cam-SpamDetails: score -0.3 from SpamAssassin-3.3.2-1547729 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.181 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (balraj885[at]gmail.com) * 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in * digit (balraj885[at]gmail.com) * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-we0-f181.google.com ([74.125.82.181]:47749) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoYUA-0004f1-7H (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 12:56:55 +0000 Received: by mail-we0-f181.google.com with SMTP id x55so16774013wes.12 for ; Thu, 05 Dec 2013 04:56:54 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.106.41 with SMTP id gr9mr12089649wib.41.1386248213859; Thu, 05 Dec 2013 04:56:53 -0800 (PST) Sender: balraj885@gmail.com Received: by 10.216.91.6 with HTTP; Thu, 5 Dec 2013 04:56:53 -0800 (PST) In-Reply-To: <52A073A1.4000102@oracle.com> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <52A073A1.4000102@oracle.com> Date: Thu, 5 Dec 2013 12:56:53 +0000 X-Google-Sender-Auth: NsN50hAfQZFO84EcGb90Bec_A7E Message-ID: Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen From: Balraj Singh To: John Haxby Content-Type: multipart/alternative; boundary=f46d04451a1b5b918304ecc91047 Cc: xen-devel@lists.xenproject.org, Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 12:56:55 -0000 Content-Length: 9885 Lines: 224 --f46d04451a1b5b918304ecc91047 Content-Type: text/plain; charset=ISO-8859-1 Thanks very much. This is fine and exactly what is observed (that the checksum is only calculated going to/from a real wire). The engineering choice makes sense. But this does mean that I need to know when the stack receives a pkt if the checksum should be verified for that packet. I can't do a redundant verification because a bad chksum may be because the field was clobbered (not set) during earlier verification. So, what I wanted to know was where to look for this flag - a snippet of code or a ptr to a file :). Thanks, Balraj On Thu, Dec 5, 2013 at 12:37 PM, John Haxby wrote: > On 05/12/13 11:39, Ian Campbell wrote: > > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > >> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > >>> > > Hi, > >>> > > > >>> > > I'm working on verifying TCP checksums on incoming packets in > Mirage, but > >>> > > I've run into a bit of a problem. > >>> > > > >>> > > If TCP checksum offload is turned on on a virtual interface (this > is the > >>> > > default), and if the TCP connection is local to the machine, it > looks like > >>> > > Xen does not calculate the checksum at all. This may be valid > because Xen > >>> > > may be providing a stronger guarantee, but it means that incoming > packets > >>> > > don't have a valid checksum in the header. This then means that > in Mirage > >>> > > we can't just have checksum verification turned on all the time. > This > >>> > > would have been the safe fall back option and detecting that > checksum > >>> > > offload is on, and then not duplicating the verification in Mirage > would > >>> > > have been an optimisation. But it looks like this is not an > option. Now I > >>> > > need to know for every incoming packet whether checksum > verification should > >>> > > be done or not. It should ideally be for every packet since > chksum offload > >>> > > can be turned off and on on the VIF and existing tcp connections > should > >>> > > continue. If not every packet, I need to get a notification or > efficiently > >>> > > detect right away that the setting is changed on the VIF. > >> > > >> > This is a question that seems to keep coming up even for Linux and > >> > Windows, as the combination of local<->local VMs vs local<->off-host > and > >> > the checksum offload is quite confusing. > >> > > >> > CCing xen-devel: is the appropriate behaviour for a guest VM that > wants to > >> > use checksum offloading in all situations documented anywhere? > > I don't understand the question/concern. If you have enabled checksum > > offload then of course you don't recalculate the checksum, that's the > > whole point of offloading it. > > I get this a lot. > > There are a few different cases: > > * domain to domain traffic > * domain to external traffic with egress from a NIC that does offload > * domain to external through a non-offloading NIC > > With xen checksum offloading, domain to domain traffic appears to be > received with a bad checksum. This is OK, there is no point in > calculating a checksum if the packets are only going through memory. If > your memory is going to randomly corrupt packets you have more bigger > problems to worry about. However, this does upset at least Solaris: if > you're using a Solaris guest for NAT then the NAT module on Solaris gets > all upset if the checksum is wrong and drops the packets. (This is > Solaris's NAT module being overly picky, it may need to recalculate or > at least invalidate the existing checksum, but it doesn't need to check > it as well.) > > The second two cases are of interest from the domain perspective. A > domain has no way of knowing how any given packet is going to leave the > host (or even if it is) so it can't know ahead of time whether to > calculate any checksums: the skb's are just marked with "checksum > needed" as usual and either the egress NIC will do the job or dom0 will > do it. > > There is absolutely nothing wrong in any of this (Solaris > notwithstanding). The difficulty is getting people to realise that > checksums are only calculated when a packet hits the cat-5. It doesn't > need documenting, it just needs a little thought. I got tired of > hammering the point home :) > > jch > --f46d04451a1b5b918304ecc91047 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks very much. =A0This is fine and exactly what is obse= rved (that the checksum is only calculated going to/from a real wire). =A0T= he engineering choice makes sense. =A0But this does mean that I need to kno= w when the stack receives a pkt if the checksum should be verified for that= packet. =A0I can't do a redundant verification because a bad chksum ma= y be because the field was clobbered (not set) during earlier verification.= =A0So, what I wanted to know was where to look for this flag - a snippet o= f code or a ptr to a file :).

Thanks,

Balraj

=


On Thu,= Dec 5, 2013 at 12:37 PM, John Haxby <john.haxby@oracle.com> wrote:
On 0= 5/12/13 11:39, Ian Campbell wrote:
> On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote:
>> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote:=
>>> > > Hi,
>>> > >
>>> > > I'm working on verifying TCP checksums on incomi= ng packets in Mirage, but
>>> > > I've run into a bit of a problem.
>>> > >
>>> > > If TCP checksum offload is turned on on a virtual in= terface (this is the
>>> > > default), and if the TCP connection is local to the = machine, it looks like
>>> > > Xen does not calculate the checksum at all. =A0This = may be valid because Xen
>>> > > may be providing a stronger guarantee, but it means = that incoming packets
>>> > > don't have a valid checksum in the header. =A0Th= is then means that in Mirage
>>> > > we can't just have checksum verification turned = on all the time. =A0This
>>> > > would have been the safe fall back option and detect= ing that checksum
>>> > > offload is on, and then not duplicating the verifica= tion in Mirage would
>>> > > have been an optimisation. =A0But it looks like this= is not an option. =A0Now I
>>> > > need to know for every incoming packet whether check= sum verification should
>>> > > be done or not. =A0It should ideally be for every pa= cket since chksum offload
>>> > > can be turned off and on on the VIF and existing tcp= connections should
>>> > > continue. =A0If not every packet, I need to get a no= tification or efficiently
>>> > > detect right away that the setting is changed on the= VIF.
>> >
>> > This is a question that seems to keep coming up even for Linu= x and
>> > Windows, as the combination of local<->local VMs vs loc= al<->off-host and
>> > the checksum offload is quite confusing.
>> >
>> > CCing xen-devel: is the appropriate behaviour for a guest VM = that wants to
>> > use checksum offloading in all situations documented anywhere= ?
> I don't understand the question/concern. If you have enabled check= sum
> offload then of course you don't recalculate the checksum, that= 9;s the
> whole point of offloading it.

I get this a lot.

There are a few different cases:

=A0 * domain to domain traffic
=A0 * domain to external traffic with egress from a NIC that does offload =A0 * domain to external through a non-offloading NIC

With xen checksum offloading, domain to domain traffic appears to be
received with a bad checksum. =A0This is OK, there is no point in
calculating a checksum if the packets are only going through memory. =A0If<= br> your memory is going to randomly corrupt packets you have more bigger
problems to worry about. =A0 However, this does upset at least Solaris: if<= br> you're using a Solaris guest for NAT then the NAT module on Solaris get= s
all upset if the checksum is wrong and drops the packets. =A0(This is
Solaris's NAT module being overly picky, it may need to recalculate or<= br> at least invalidate the existing checksum, but it doesn't need to check=
it as well.)

The second two cases are of interest from the domain perspective. =A0A
domain has no way of knowing how any given packet is going to leave the
host (or even if it is) so it can't know ahead of time whether to
calculate any checksums: the skb's are just marked with "checksum<= br> needed" as usual and either the egress NIC will do the job or dom0 wil= l
do it.

There is absolutely nothing wrong in any of this (Solaris
notwithstanding). =A0 The difficulty is getting people to realise that
checksums are only calculated when a packet hits the cat-5. =A0It doesn'= ;t
need documenting, it just needs a little thought. =A0 I got tired of
hammering the point home :)

jch

--f46d04451a1b5b918304ecc91047-- From crowcroft@gmail.com Thu Dec 05 13:15:17 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoYlx-0004If-60 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:15:17 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1547729 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.175 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (crowcroft[at]gmail.com) * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-we0-f175.google.com ([74.125.82.175]:37147) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoYlw-0005CE-8G (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:15:17 +0000 Received: by mail-we0-f175.google.com with SMTP id t60so774846wes.20 for ; Thu, 05 Dec 2013 05:15:16 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.194.110.138 with SMTP id ia10mr69297493wjb.3.1386249316233; Thu, 05 Dec 2013 05:15:16 -0800 (PST) Sender: crowcroft@gmail.com Received: by 10.217.107.6 with HTTP; Thu, 5 Dec 2013 05:15:16 -0800 (PST) In-Reply-To: <52A073A1.4000102@oracle.com> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <52A073A1.4000102@oracle.com> Date: Thu, 5 Dec 2013 13:15:16 +0000 X-Google-Sender-Auth: DSwMNAAHlTzdAOMBYfI-Q22Fs5A Message-ID: Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen From: Jon Crowcroft To: John Haxby Content-Type: multipart/alternative; boundary=047d7bf10aa81078c604ecc952df Cc: Balraj Singh , xen-devel@lists.xenproject.org, Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 13:15:17 -0000 Content-Length: 9066 Lines: 211 --047d7bf10aa81078c604ecc952df Content-Type: text/plain; charset=ISO-8859-1 i thought a value of 0 in the tcp chcksum field indicated "no checksum" and could be used in the cases you identify and ought not to trigger problems in correct code? On Thu, Dec 5, 2013 at 12:37 PM, John Haxby wrote: > On 05/12/13 11:39, Ian Campbell wrote: > > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > >> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > >>> > > Hi, > >>> > > > >>> > > I'm working on verifying TCP checksums on incoming packets in > Mirage, but > >>> > > I've run into a bit of a problem. > >>> > > > >>> > > If TCP checksum offload is turned on on a virtual interface (this > is the > >>> > > default), and if the TCP connection is local to the machine, it > looks like > >>> > > Xen does not calculate the checksum at all. This may be valid > because Xen > >>> > > may be providing a stronger guarantee, but it means that incoming > packets > >>> > > don't have a valid checksum in the header. This then means that > in Mirage > >>> > > we can't just have checksum verification turned on all the time. > This > >>> > > would have been the safe fall back option and detecting that > checksum > >>> > > offload is on, and then not duplicating the verification in Mirage > would > >>> > > have been an optimisation. But it looks like this is not an > option. Now I > >>> > > need to know for every incoming packet whether checksum > verification should > >>> > > be done or not. It should ideally be for every packet since > chksum offload > >>> > > can be turned off and on on the VIF and existing tcp connections > should > >>> > > continue. If not every packet, I need to get a notification or > efficiently > >>> > > detect right away that the setting is changed on the VIF. > >> > > >> > This is a question that seems to keep coming up even for Linux and > >> > Windows, as the combination of local<->local VMs vs local<->off-host > and > >> > the checksum offload is quite confusing. > >> > > >> > CCing xen-devel: is the appropriate behaviour for a guest VM that > wants to > >> > use checksum offloading in all situations documented anywhere? > > I don't understand the question/concern. If you have enabled checksum > > offload then of course you don't recalculate the checksum, that's the > > whole point of offloading it. > > I get this a lot. > > There are a few different cases: > > * domain to domain traffic > * domain to external traffic with egress from a NIC that does offload > * domain to external through a non-offloading NIC > > With xen checksum offloading, domain to domain traffic appears to be > received with a bad checksum. This is OK, there is no point in > calculating a checksum if the packets are only going through memory. If > your memory is going to randomly corrupt packets you have more bigger > problems to worry about. However, this does upset at least Solaris: if > you're using a Solaris guest for NAT then the NAT module on Solaris gets > all upset if the checksum is wrong and drops the packets. (This is > Solaris's NAT module being overly picky, it may need to recalculate or > at least invalidate the existing checksum, but it doesn't need to check > it as well.) > > The second two cases are of interest from the domain perspective. A > domain has no way of knowing how any given packet is going to leave the > host (or even if it is) so it can't know ahead of time whether to > calculate any checksums: the skb's are just marked with "checksum > needed" as usual and either the egress NIC will do the job or dom0 will > do it. > > There is absolutely nothing wrong in any of this (Solaris > notwithstanding). The difficulty is getting people to realise that > checksums are only calculated when a packet hits the cat-5. It doesn't > need documenting, it just needs a little thought. I got tired of > hammering the point home :) > > jch > > --047d7bf10aa81078c604ecc952df Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
i thought a value of 0 in the tcp chcksum field indicated = "no checksum" and could be used in the cases you identify and oug= ht not to trigger problems in correct code?


On Thu, Dec 5, 2013 at 12:37 PM, John Ha= xby <john.haxby@oracle.com> wrote:
On 05/12/13 11:39, Ian Campbell wro= te:
> On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote:
>> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote:=
>>> > > Hi,
>>> > >
>>> > > I'm working on verifying TCP checksums on incomi= ng packets in Mirage, but
>>> > > I've run into a bit of a problem.
>>> > >
>>> > > If TCP checksum offload is turned on on a virtual in= terface (this is the
>>> > > default), and if the TCP connection is local to the = machine, it looks like
>>> > > Xen does not calculate the checksum at all. =A0This = may be valid because Xen
>>> > > may be providing a stronger guarantee, but it means = that incoming packets
>>> > > don't have a valid checksum in the header. =A0Th= is then means that in Mirage
>>> > > we can't just have checksum verification turned = on all the time. =A0This
>>> > > would have been the safe fall back option and detect= ing that checksum
>>> > > offload is on, and then not duplicating the verifica= tion in Mirage would
>>> > > have been an optimisation. =A0But it looks like this= is not an option. =A0Now I
>>> > > need to know for every incoming packet whether check= sum verification should
>>> > > be done or not. =A0It should ideally be for every pa= cket since chksum offload
>>> > > can be turned off and on on the VIF and existing tcp= connections should
>>> > > continue. =A0If not every packet, I need to get a no= tification or efficiently
>>> > > detect right away that the setting is changed on the= VIF.
>> >
>> > This is a question that seems to keep coming up even for Linu= x and
>> > Windows, as the combination of local<->local VMs vs loc= al<->off-host and
>> > the checksum offload is quite confusing.
>> >
>> > CCing xen-devel: is the appropriate behaviour for a guest VM = that wants to
>> > use checksum offloading in all situations documented anywhere= ?
> I don't understand the question/concern. If you have enabled check= sum
> offload then of course you don't recalculate the checksum, that= 9;s the
> whole point of offloading it.

I get this a lot.

There are a few different cases:

=A0 * domain to domain traffic
=A0 * domain to external traffic with egress from a NIC that does offload =A0 * domain to external through a non-offloading NIC

With xen checksum offloading, domain to domain traffic appears to be
received with a bad checksum. =A0This is OK, there is no point in
calculating a checksum if the packets are only going through memory. =A0If<= br> your memory is going to randomly corrupt packets you have more bigger
problems to worry about. =A0 However, this does upset at least Solaris: if<= br> you're using a Solaris guest for NAT then the NAT module on Solaris get= s
all upset if the checksum is wrong and drops the packets. =A0(This is
Solaris's NAT module being overly picky, it may need to recalculate or<= br> at least invalidate the existing checksum, but it doesn't need to check=
it as well.)

The second two cases are of interest from the domain perspective. =A0A
domain has no way of knowing how any given packet is going to leave the
host (or even if it is) so it can't know ahead of time whether to
calculate any checksums: the skb's are just marked with "checksum<= br> needed" as usual and either the egress NIC will do the job or dom0 wil= l
do it.

There is absolutely nothing wrong in any of this (Solaris
notwithstanding). =A0 The difficulty is getting people to realise that
checksums are only calculated when a packet hits the cat-5. =A0It doesn'= ;t
need documenting, it just needs a little thought. =A0 I got tired of
hammering the point home :)

jch


--047d7bf10aa81078c604ecc952df-- From balraj885@gmail.com Thu Dec 05 13:33:16 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoZ3M-0004gw-7A (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:33:16 +0000 X-Cam-SpamDetails: score -0.3 from SpamAssassin-3.3.2-1547729 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.212.180 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (balraj885[at]gmail.com) * 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in * digit (balraj885[at]gmail.com) * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wi0-f180.google.com ([209.85.212.180]:50819) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoZ3K-0001jf-0Y (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:33:14 +0000 Received: by mail-wi0-f180.google.com with SMTP id hn9so5422816wib.13 for ; Thu, 05 Dec 2013 05:33:13 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.189.68 with SMTP id gg4mr12164269wic.46.1386250393924; Thu, 05 Dec 2013 05:33:13 -0800 (PST) Sender: balraj885@gmail.com Received: by 10.216.91.6 with HTTP; Thu, 5 Dec 2013 05:33:13 -0800 (PST) In-Reply-To: <74A8AF4B-21DE-4E43-A5F9-51A30E08FE9F@nottingham.ac.uk> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> <9AAE0902D5BC7E449B7C8E4E778ABCD01A44B7@AMSPEX01CL01.citrite.net> <74A8AF4B-21DE-4E43-A5F9-51A30E08FE9F@nottingham.ac.uk> Date: Thu, 5 Dec 2013 13:33:13 +0000 X-Google-Sender-Auth: lvMa8iF6o-Bu4U2PT6j_9asNRXU Message-ID: Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen From: Balraj Singh To: Richard Mortier Content-Type: multipart/alternative; boundary=001a11c353004cbab704ecc9922b Cc: "xen-devel@lists.xenproject.org" , Paul Durrant , Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 13:33:16 -0000 Content-Length: 7472 Lines: 188 --001a11c353004cbab704ecc9922b Content-Type: text/plain; charset=ISO-8859-1 Thanks for clarifying Mort. I did this test: I set up a long lived TCP connection from a linux guest to a mirage guest each thru a VIF to the s/w bridge. The various offload settings including checksum offload were the default which is ON. All packets received by Mirage had bad checksums. Now from dom0 I changed the offload settings on the VIFs using ethtool, so the checksum offload was OFF. Now all packets had good checksums. So to have no packets in the jeopardy of being accepted without their checksum verified, I would like to know on each received pkt if the checksum was already verified. Detecting immediately that the setting on the VIF has changed could also work, but it would involve throwing away some packets. Then again, I may have misunderstood something about how the stack should interact with the backend. We do declare (maybe just by staying mute, I think) that we can handle packets with no checksums. But does that mean that we never need to do a checksum verification on RX packets? If so that's the best. Though then I will need to think about what was going on in my test. Thanks, Balraj On Thu, Dec 5, 2013 at 12:55 PM, Richard Mortier < Richard.Mortier@nottingham.ac.uk> wrote: > > On 5 Dec 2013, at 12:47, Paul Durrant wrote: > > ... > >>>> On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > >>>> > ... > >>>>> It should ideally be for every packet since chksum > >> offload > >>>>> can be turned off and on on the VIF and existing tcp connections > should > >>>>> continue. If not every packet, I need to get a notification or > efficiently > >>>>> detect right away that the setting is changed on the VIF. > > ... > > > earlier today, i wrote: > > > >> i think balraj's question arises because the status of checksum offload > can > >> change mid-tcp-flow. how does he know whether it's on or off for a given > >> packet? > > > > Why do you assert that it can change mid-flow? The configuration is > decided at ring connect time. Nothing should change after that. If, at that > time, the frontend declares it can handle packets with no checksum then > clearly it may get some packets that do have checksum as well as ones that > don't, depending on where they originated. > > i didn't mean to :) i was just trying to point out to ian the reason for > balraj's question -- i'll leave it to balraj from here... > > -- > Cheers, > > R. > > > > > This message and any attachment are intended solely for the addressee and > may contain confidential information. If you have received this message in > error, please send it back to me, and immediately delete it. Please do > not use, copy or disclose the information contained in this message or in > any attachment. Any views or opinions expressed by the author of this > email do not necessarily reflect the views of the University of Nottingham. > > This message has been checked for viruses but the contents of an attachment > may still contain software viruses which could damage your computer > system, you are advised to perform your own checks. Email communications > with the University of Nottingham may be monitored as permitted by UK > legislation. > > > > > --001a11c353004cbab704ecc9922b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Thanks for clarifying Mort. =A0I did this test: I set up a= long lived TCP connection from a linux guest to a mirage guest each thru a= VIF to the s/w bridge. =A0The various offload settings including checksum = offload were the default which is ON. =A0All packets received by Mirage had= bad checksums. =A0Now from dom0 I changed the offload settings on the VIFs= using ethtool, so the checksum offload was OFF. =A0Now all packets had goo= d checksums.

So to have no packets in the jeopardy of being accepted with= out their checksum verified, I would like to know on each received pkt if t= he checksum was already verified. =A0Detecting immediately that the setting= on the VIF has changed could also work, but it would involve throwing away= some packets.

Then again, I may have misunderstood something about ho= w the stack should interact with the backend. =A0We do declare (maybe just = by staying mute, I think) that we can handle packets with no checksums. =A0= But does that mean that we never need to do a checksum verification on RX p= ackets? =A0If so that's the best. =A0Though then I will need to think a= bout what was going on in my test.

Thanks,

Balraj


On Thu, Dec 5, 20= 13 at 12:55 PM, Richard Mortier <Richard.Mortier@nottingham= .ac.uk> wrote:

On 5 Dec 2013, at 12:47, Paul Durrant wrote:

...
>>>> On Tue, Dec 03, 2013 at 01:00:23PM +0000= , Balraj Singh wrote:
>>>>
...
>>>>> It should ideally be for every packe= t since chksum
>> offload
>>>>> can be turned off and on on the VIF and existing tcp c= onnections should
>>>>> continue. =A0If not every packet, I need to get a noti= fication or efficiently
>>>>> detect right away that the setting is changed on the V= IF.

...

> earlier today, i wrote:
>
>> i think balraj's question arises because the status of checksu= m offload can
>> change mid-tcp-flow. how does he know whether it's on or off f= or a given
>> packet?
>
> Why do you assert that it can change mid-flow? The configuration is de= cided at ring connect time. Nothing should change after that. If, at that t= ime, the frontend declares it can handle packets with no checksum then clea= rly it may get some packets that do have checksum as well as ones that don&= #39;t, depending on where they originated.

i didn't mean to :) i was just trying to point out to ian the rea= son for balraj's question -- i'll leave it to balraj from here...

--
Cheers,

R.




This message and any attachment are intended solely for the addressee and m= ay contain confidential information. If you have received this message in e= rror, please send it back to me, and immediately delete it. =A0 Please do n= ot use, copy or disclose the information contained in this message or in an= y attachment. =A0Any views or opinions expressed by the author of this emai= l do not necessarily reflect the views of the University of Nottingham.

This message has been checked for viruses but the contents of an attachment=
may still contain software viruses which could damage your computer system,= you are advised to perform your own checks. Email communications with the = University of Nottingham may be monitored as permitted by UK legislation.




--001a11c353004cbab704ecc9922b-- From Paul.Durrant@citrix.com Thu Dec 05 13:42:54 2013 Received: from ppsw-52.csi.cam.ac.uk ([131.111.8.152]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoZCg-0004wb-KE (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:42:54 +0000 X-Cam-SpamDetails: score -5.0 from SpamAssassin-3.3.2-1547729 * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain * -5.0 RCVD_IN_DNSWL_HI RBL: Sender listed at http://www.dnswl.org/, high * trust * [66.165.176.89 listed in list.dnswl.dnsbl.ja.net] X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp.citrix.com ([66.165.176.89]:31420) by ppsw-52.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.148]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoZCf-0004xk-Fc (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:42:54 +0000 X-IronPort-AV: E=Sophos;i="4.93,833,1378857600"; d="scan'208";a="80900023" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO01.CITRIX.COM with ESMTP; 05 Dec 2013 13:42:52 +0000 Received: from AMSPEX01CL02.citrite.net (10.69.46.33) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server (TLS) id 14.2.342.4; Thu, 5 Dec 2013 08:42:52 -0500 Received: from AMSPEX01CL01.citrite.net ([169.254.6.128]) by AMSPEX01CL02.citrite.net ([10.69.46.33]) with mapi id 14.02.0342.004; Thu, 5 Dec 2013 14:42:50 +0100 From: Paul Durrant To: Balraj Singh , Richard Mortier Subject: RE: [Xen-devel] Question about TCP checksum offload in Xen Thread-Topic: [Xen-devel] Question about TCP checksum offload in Xen Thread-Index: AQHO8a2PE5HQHW0giUOjF4n3P+kuVZpFaRYAgAABsACAACGfIP//8fiAgAAKm4CAABHWEA== Date: Thu, 5 Dec 2013 13:42:51 +0000 Message-ID: <9AAE0902D5BC7E449B7C8E4E778ABCD01A465F@AMSPEX01CL01.citrite.net> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <9CED6D8A-E29B-46BF-8BA5-1E0A868B936D@nottingham.ac.uk> <9AAE0902D5BC7E449B7C8E4E778ABCD01A44B7@AMSPEX01CL01.citrite.net> <74A8AF4B-21DE-4E43-A5F9-51A30E08FE9F@nottingham.ac.uk> In-Reply-To: Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.80.2.29] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-DLP: MIA1 Cc: "xen-devel@lists.xenproject.org" , Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 13:42:54 -0000 Content-Length: 1992 Lines: 44 De-html... ------ From: balraj885@gmail.com [mailto:balraj885@gmail.com] On Behalf Of Balraj = Singh Sent: 05 December 2013 13:33 To: Richard Mortier Cc: Paul Durrant; Ian Campbell; xen-devel@lists.xenproject.org; Mirage List= ; Anil Madhavapeddy Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen Thanks for clarifying Mort. =A0I did this test: I set up a long lived TCP c= onnection from a linux guest to a mirage guest each thru a VIF to the s/w b= ridge. =A0The various offload settings including checksum offload were the = default which is ON. =A0All packets received by Mirage had bad checksums. = =A0Now from dom0 I changed the offload settings on the VIFs using ethtool, = so the checksum offload was OFF. =A0Now all packets had good checksums. So to have no packets in the jeopardy of being accepted without their check= sum verified, I would like to know on each received pkt if the checksum was= already verified. =A0Detecting immediately that the setting on the VIF has= changed could also work, but it would involve throwing away some packets. Then again, I may have misunderstood something about how the stack should i= nteract with the backend. =A0We do declare (maybe just by staying mute, I t= hink) that we can handle packets with no checksums. =A0But does that mean t= hat we never need to do a checksum verification on RX packets? =A0If so tha= t's the best. =A0Though then I will need to think about what was going on i= n my test. ----- And can we avoid top-posting in future, please. It makes it very hard to fo= llow threads. Possibly you ran into the issue because (for some reason) the default is to= expect a frontend to handle IPv4 TCP/UDP checksum offload. The frontend ne= eds to set feature-no-csum-offload to avoid this expectation. I imagine tha= t's what you want to do. Also, the state of the checksum field when being passed a packet for offloa= ding will not be zero. It should contain a valid pseudo-header checksum. Paul From balraj885@gmail.com Thu Dec 05 13:43:08 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VoZCu-0004xi-P2 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:43:08 +0000 X-Cam-SpamDetails: score -0.3 from SpamAssassin-3.3.2-1547729 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.212.178 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (balraj885[at]gmail.com) * 0.2 FREEMAIL_ENVFROM_END_DIGIT Envelope-from freemail username ends in * digit (balraj885[at]gmail.com) * 0.0 HTML_MESSAGE BODY: HTML included in message * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wi0-f178.google.com ([209.85.212.178]:43080) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VoZCt-0004N4-j1 (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 13:43:08 +0000 Received: by mail-wi0-f178.google.com with SMTP id ca18so9807049wib.17 for ; Thu, 05 Dec 2013 05:43:07 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.180.189.68 with SMTP id gg4mr12203852wic.46.1386250987128; Thu, 05 Dec 2013 05:43:07 -0800 (PST) Sender: balraj885@gmail.com Received: by 10.216.91.6 with HTTP; Thu, 5 Dec 2013 05:43:07 -0800 (PST) In-Reply-To: References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <52A073A1.4000102@oracle.com> Date: Thu, 5 Dec 2013 13:43:07 +0000 X-Google-Sender-Auth: yzFZI0eIB5T-vxv6TCHHj-kLBy8 Message-ID: Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen From: Balraj Singh To: Jon Crowcroft Content-Type: multipart/alternative; boundary=001a11c35300a84df404ecc9b585 Cc: John Haxby , "xen-devel@lists.xenproject.org" , Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 13:43:08 -0000 Content-Length: 10201 Lines: 235 --001a11c35300a84df404ecc9b585 Content-Type: text/plain; charset=ISO-8859-1 That could work too to signal in the packet itself that the checksum is ok. But I don't think the received packets had 0 in the chksum field. It was just some random value, though I can check again. Thanks, Balraj On Thu, Dec 5, 2013 at 1:15 PM, Jon Crowcroft wrote: > i thought a value of 0 in the tcp chcksum field indicated "no checksum" > and could be used in the cases you identify and ought not to trigger > problems in correct code? > > > On Thu, Dec 5, 2013 at 12:37 PM, John Haxby wrote: > >> On 05/12/13 11:39, Ian Campbell wrote: >> > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: >> >> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: >> >>> > > Hi, >> >>> > > >> >>> > > I'm working on verifying TCP checksums on incoming packets in >> Mirage, but >> >>> > > I've run into a bit of a problem. >> >>> > > >> >>> > > If TCP checksum offload is turned on on a virtual interface (this >> is the >> >>> > > default), and if the TCP connection is local to the machine, it >> looks like >> >>> > > Xen does not calculate the checksum at all. This may be valid >> because Xen >> >>> > > may be providing a stronger guarantee, but it means that incoming >> packets >> >>> > > don't have a valid checksum in the header. This then means that >> in Mirage >> >>> > > we can't just have checksum verification turned on all the time. >> This >> >>> > > would have been the safe fall back option and detecting that >> checksum >> >>> > > offload is on, and then not duplicating the verification in >> Mirage would >> >>> > > have been an optimisation. But it looks like this is not an >> option. Now I >> >>> > > need to know for every incoming packet whether checksum >> verification should >> >>> > > be done or not. It should ideally be for every packet since >> chksum offload >> >>> > > can be turned off and on on the VIF and existing tcp connections >> should >> >>> > > continue. If not every packet, I need to get a notification or >> efficiently >> >>> > > detect right away that the setting is changed on the VIF. >> >> > >> >> > This is a question that seems to keep coming up even for Linux and >> >> > Windows, as the combination of local<->local VMs vs local<->off-host >> and >> >> > the checksum offload is quite confusing. >> >> > >> >> > CCing xen-devel: is the appropriate behaviour for a guest VM that >> wants to >> >> > use checksum offloading in all situations documented anywhere? >> > I don't understand the question/concern. If you have enabled checksum >> > offload then of course you don't recalculate the checksum, that's the >> > whole point of offloading it. >> >> I get this a lot. >> >> There are a few different cases: >> >> * domain to domain traffic >> * domain to external traffic with egress from a NIC that does offload >> * domain to external through a non-offloading NIC >> >> With xen checksum offloading, domain to domain traffic appears to be >> received with a bad checksum. This is OK, there is no point in >> calculating a checksum if the packets are only going through memory. If >> your memory is going to randomly corrupt packets you have more bigger >> problems to worry about. However, this does upset at least Solaris: if >> you're using a Solaris guest for NAT then the NAT module on Solaris gets >> all upset if the checksum is wrong and drops the packets. (This is >> Solaris's NAT module being overly picky, it may need to recalculate or >> at least invalidate the existing checksum, but it doesn't need to check >> it as well.) >> >> The second two cases are of interest from the domain perspective. A >> domain has no way of knowing how any given packet is going to leave the >> host (or even if it is) so it can't know ahead of time whether to >> calculate any checksums: the skb's are just marked with "checksum >> needed" as usual and either the egress NIC will do the job or dom0 will >> do it. >> >> There is absolutely nothing wrong in any of this (Solaris >> notwithstanding). The difficulty is getting people to realise that >> checksums are only calculated when a packet hits the cat-5. It doesn't >> need documenting, it just needs a little thought. I got tired of >> hammering the point home :) >> >> jch >> >> > --001a11c35300a84df404ecc9b585 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
That could work too to signal in the packet itself that th= e checksum is ok. =A0But I don't think the received packets had 0 in th= e chksum field. =A0It was just some random value, though I can check again.=

Thanks,

Balraj


On Thu, Dec 5, 20= 13 at 1:15 PM, Jon Crowcroft <jon.crowcroft@cl.cam.ac.uk><= /span> wrote:
i thought a value of 0 in t= he tcp chcksum field indicated "no checksum" and could be used in= the cases you identify and ought not to trigger problems in correct code?<= /div>


On Thu, Dec 5, 2013 at= 12:37 PM, John Haxby <john.haxby@oracle.com> wrote:
=
On 05/12/13 11:39, Ian Campbell wrote:
> On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote:
>> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote:=
>>> > > Hi,
>>> > >
>>> > > I'm working on verifying TCP checksums on incomi= ng packets in Mirage, but
>>> > > I've run into a bit of a problem.
>>> > >
>>> > > If TCP checksum offload is turned on on a virtual in= terface (this is the
>>> > > default), and if the TCP connection is local to the = machine, it looks like
>>> > > Xen does not calculate the checksum at all. =A0This = may be valid because Xen
>>> > > may be providing a stronger guarantee, but it means = that incoming packets
>>> > > don't have a valid checksum in the header. =A0Th= is then means that in Mirage
>>> > > we can't just have checksum verification turned = on all the time. =A0This
>>> > > would have been the safe fall back option and detect= ing that checksum
>>> > > offload is on, and then not duplicating the verifica= tion in Mirage would
>>> > > have been an optimisation. =A0But it looks like this= is not an option. =A0Now I
>>> > > need to know for every incoming packet whether check= sum verification should
>>> > > be done or not. =A0It should ideally be for every pa= cket since chksum offload
>>> > > can be turned off and on on the VIF and existing tcp= connections should
>>> > > continue. =A0If not every packet, I need to get a no= tification or efficiently
>>> > > detect right away that the setting is changed on the= VIF.
>> >
>> > This is a question that seems to keep coming up even for Linu= x and
>> > Windows, as the combination of local<->local VMs vs loc= al<->off-host and
>> > the checksum offload is quite confusing.
>> >
>> > CCing xen-devel: is the appropriate behaviour for a guest VM = that wants to
>> > use checksum offloading in all situations documented anywhere= ?
> I don't understand the question/concern. If you have enabled check= sum
> offload then of course you don't recalculate the checksum, that= 9;s the
> whole point of offloading it.

I get this a lot.

There are a few different cases:

=A0 * domain to domain traffic
=A0 * domain to external traffic with egress from a NIC that does offload =A0 * domain to external through a non-offloading NIC

With xen checksum offloading, domain to domain traffic appears to be
received with a bad checksum. =A0This is OK, there is no point in
calculating a checksum if the packets are only going through memory. =A0If<= br> your memory is going to randomly corrupt packets you have more bigger
problems to worry about. =A0 However, this does upset at least Solaris: if<= br> you're using a Solaris guest for NAT then the NAT module on Solaris get= s
all upset if the checksum is wrong and drops the packets. =A0(This is
Solaris's NAT module being overly picky, it may need to recalculate or<= br> at least invalidate the existing checksum, but it doesn't need to check=
it as well.)

The second two cases are of interest from the domain perspective. =A0A
domain has no way of knowing how any given packet is going to leave the
host (or even if it is) so it can't know ahead of time whether to
calculate any checksums: the skb's are just marked with "checksum<= br> needed" as usual and either the egress NIC will do the job or dom0 wil= l
do it.

There is absolutely nothing wrong in any of this (Solaris
notwithstanding). =A0 The difficulty is getting people to realise that
checksums are only calculated when a packet hits the cat-5. =A0It doesn'= ;t
need documenting, it just needs a little thought. =A0 I got tired of
hammering the point home :)

jch



--001a11c35300a84df404ecc9b585-- From john.haxby@oracle.com Thu Dec 05 15:20:10 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1Voaio-0001zI-Rv (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 15:20:10 +0000 X-Cam-SpamDetails: score -2.3 from SpamAssassin-3.3.2-1547729 * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/, * medium trust * [156.151.31.81 listed in list.dnswl.dnsbl.ja.net] * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain * 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay * lines X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from userp1040.oracle.com ([156.151.31.81]:38696) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:DHE-RSA-AES256-SHA:256) id 1Voain-00005h-hG (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 15:20:10 +0000 Received: from ucsinet21.oracle.com (ucsinet21.oracle.com [156.151.31.93]) by userp1040.oracle.com (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id rB5FK2Br027783 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Thu, 5 Dec 2013 15:20:03 GMT Received: from userz7021.oracle.com (userz7021.oracle.com [156.151.31.85]) by ucsinet21.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id rB5FK1s3018559 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 5 Dec 2013 15:20:01 GMT Received: from abhmp0005.oracle.com (abhmp0005.oracle.com [141.146.116.11]) by userz7021.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id rB5FK1W7018448; Thu, 5 Dec 2013 15:20:01 GMT Received: from sheep.uk.oracle.com (/10.167.241.51) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Thu, 05 Dec 2013 07:20:00 -0800 Message-ID: <52A0999E.3060100@oracle.com> Date: Thu, 05 Dec 2013 15:19:58 +0000 From: John Haxby User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0 MIME-Version: 1.0 To: Balraj Singh Subject: Re: [Xen-devel] Question about TCP checksum offload in Xen References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <52A073A1.4000102@oracle.com> In-Reply-To: X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Source-IP: ucsinet21.oracle.com [156.151.31.93] Cc: xen-devel@lists.xenproject.org, Ian Campbell , Mirage List , Anil Madhavapeddy X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 15:20:10 -0000 Content-Length: 5193 Lines: 118 On 05/12/13 12:56, Balraj Singh wrote: > Thanks very much. This is fine and exactly what is observed (that the > checksum is only calculated going to/from a real wire). The engineering > choice makes sense. But this does mean that I need to know when the > stack receives a pkt if the checksum should be verified for that packet. > I can't do a redundant verification because a bad chksum may be because > the field was clobbered (not set) during earlier verification. So, what > I wanted to know was where to look for this flag - a snippet of code or > a ptr to a file :). > Look at the skb in the netfront: there's a flag in there to say whether the checksum is valid. Interestingly, if the checksum is valid then you know that the data has come from outside the host (otherwise it would have been dropped). Why do you even care about the checksum? Packets with bad checksums are dropped by the NIC (with checksum offload) or by the NIC's driver (without) -- the only packets you'll see with a bad checksum are those that have come from another domain on the same host. jch > Thanks, > > Balraj > > > > On Thu, Dec 5, 2013 at 12:37 PM, John Haxby > wrote: > > On 05/12/13 11:39, Ian Campbell wrote: > > On Thu, 2013-12-05 at 11:29 +0000, Anil Madhavapeddy wrote: > >> > On Tue, Dec 03, 2013 at 01:00:23PM +0000, Balraj Singh wrote: > >>> > > Hi, > >>> > > > >>> > > I'm working on verifying TCP checksums on incoming packets > in Mirage, but > >>> > > I've run into a bit of a problem. > >>> > > > >>> > > If TCP checksum offload is turned on on a virtual interface > (this is the > >>> > > default), and if the TCP connection is local to the machine, > it looks like > >>> > > Xen does not calculate the checksum at all. This may be > valid because Xen > >>> > > may be providing a stronger guarantee, but it means that > incoming packets > >>> > > don't have a valid checksum in the header. This then means > that in Mirage > >>> > > we can't just have checksum verification turned on all the > time. This > >>> > > would have been the safe fall back option and detecting that > checksum > >>> > > offload is on, and then not duplicating the verification in > Mirage would > >>> > > have been an optimisation. But it looks like this is not an > option. Now I > >>> > > need to know for every incoming packet whether checksum > verification should > >>> > > be done or not. It should ideally be for every packet since > chksum offload > >>> > > can be turned off and on on the VIF and existing tcp > connections should > >>> > > continue. If not every packet, I need to get a notification > or efficiently > >>> > > detect right away that the setting is changed on the VIF. > >> > > >> > This is a question that seems to keep coming up even for Linux and > >> > Windows, as the combination of local<->local VMs vs > local<->off-host and > >> > the checksum offload is quite confusing. > >> > > >> > CCing xen-devel: is the appropriate behaviour for a guest VM > that wants to > >> > use checksum offloading in all situations documented anywhere? > > I don't understand the question/concern. If you have enabled checksum > > offload then of course you don't recalculate the checksum, that's the > > whole point of offloading it. > > I get this a lot. > > There are a few different cases: > > * domain to domain traffic > * domain to external traffic with egress from a NIC that does offload > * domain to external through a non-offloading NIC > > With xen checksum offloading, domain to domain traffic appears to be > received with a bad checksum. This is OK, there is no point in > calculating a checksum if the packets are only going through memory. If > your memory is going to randomly corrupt packets you have more bigger > problems to worry about. However, this does upset at least Solaris: if > you're using a Solaris guest for NAT then the NAT module on Solaris gets > all upset if the checksum is wrong and drops the packets. (This is > Solaris's NAT module being overly picky, it may need to recalculate or > at least invalidate the existing checksum, but it doesn't need to check > it as well.) > > The second two cases are of interest from the domain perspective. A > domain has no way of knowing how any given packet is going to leave the > host (or even if it is) so it can't know ahead of time whether to > calculate any checksums: the skb's are just marked with "checksum > needed" as usual and either the egress NIC will do the job or dom0 will > do it. > > There is absolutely nothing wrong in any of this (Solaris > notwithstanding). The difficulty is getting people to realise that > checksums are only calculated when a packet hits the cat-5. It doesn't > need documenting, it just needs a little thought. I got tired of > hammering the point home :) > > jch > > From james.harper@bendigoit.com.au Thu Dec 05 21:09:09 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VogAX-0003FK-EG (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 21:09:09 +0000 X-Cam-SpamDetails: score -0.0 from SpamAssassin-3.3.2-1547729 * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp2.bendigoit.com.au ([203.16.207.99]:57149) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1VogAW-0006kA-hD (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Thu, 05 Dec 2013 21:09:09 +0000 Received: from bitcom1.int.sbss.com.au ([192.168.200.237]) by smtp2.bendigoit.com.au with esmtp (Exim 4.80) (envelope-from ) id 1VogA0-0002bh-4Y; Fri, 06 Dec 2013 08:08:36 +1100 Received: from BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d]) by BITCOM1.int.sbss.com.au ([fe80::a5ca:4fd3:14f:ad5d%12]) with mapi id 14.01.0438.000; Fri, 6 Dec 2013 08:08:34 +1100 From: James Harper To: John Haxby , Ian Campbell , Anil Madhavapeddy Subject: RE: [Xen-devel] Question about TCP checksum offload in Xen Thread-Topic: [Xen-devel] Question about TCP checksum offload in Xen Thread-Index: AQHO8a3UuaVzdsuacUuZwoRELSOEpppEwXIAgAAQbYCAAUXqoA== Date: Thu, 5 Dec 2013 21:08:32 +0000 Message-ID: <6035A0D088A63A46850C3988ED045A4B66BF4F56@BITCOM1.int.sbss.com.au> References: <20131205112952.GF14792@dark.recoil.org> <1386243546.20047.26.camel@kazak.uk.xensource.com> <52A073A1.4000102@oracle.com> In-Reply-To: <52A073A1.4000102@oracle.com> Accept-Language: en-AU, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [172.16.3.239] x-tm-as-product-ver: SMEX-10.2.0.3176-7.000.1014-20340.002 x-tm-as-result: No--43.346600-0.000000-31 x-tm-as-user-approved-sender: Yes x-tm-as-user-blocked-sender: No Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Really-From-Bendigo-IT: magichashvalue Cc: "xen-devel@lists.xenproject.org" , Balraj, Singh , Mirage List X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 05 Dec 2013 21:09:09 -0000 Content-Length: 1310 Lines: 25 > With xen checksum offloading, domain to domain traffic appears to be > received with a bad checksum. This is OK, there is no point in > calculating a checksum if the packets are only going through memory. If > your memory is going to randomly corrupt packets you have more bigger > problems to worry about. However, this does upset at least Solaris: if > you're using a Solaris guest for NAT then the NAT module on Solaris gets > all upset if the checksum is wrong and drops the packets. (This is > Solaris's NAT module being overly picky, it may need to recalculate or > at least invalidate the existing checksum, but it doesn't need to check > it as well.) Windows 2003 can't handle receiving packets that have a bad checksum either= . Despite the fact that the 'checksum good' flag is set, Windows seems to g= o ahead and check it anyway. I wonder if it's the firewall doing that in Wi= ndows too... I always just assumed it was NDIS itself. Windows also seems to differ from Linux in its opinion on whether the total= packet length in a gso packet is included in the psuedoheader checksum. Th= at took a bit of mucking around to find as some hardware seems to ignore th= e psuedoheader checksum and calculate the whole checksum again anyway, so y= ou only see the problem on some cards. James From Richard.Mortier@nottingham.ac.uk Sun Dec 08 13:31:54 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VpeSg-00007j-M2 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Sun, 08 Dec 2013 13:31:54 +0000 X-Cam-SpamDetails: score 0.0 from SpamAssassin-3.3.2-1548817 * 0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from engine03-20433-8.icritical.com ([93.159.202.52]:55275) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with smtp id 1VpeSg-0006GH-7S (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Sun, 08 Dec 2013 13:31:54 +0000 Received: (qmail 17150 invoked from network); 8 Dec 2013 13:31:51 -0000 Received: from localhost (127.0.0.1) by engine03-20433-8.icritical.com with SMTP; 8 Dec 2013 13:31:51 -0000 Received: from engine03-20433-8.icritical.com ([127.0.0.1]) by localhost (engine03-20433-8.icritical.com [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 16999-04 for ; Sun, 8 Dec 2013 13:31:49 +0000 (GMT) Received: (qmail 17139 invoked by uid 599); 8 Dec 2013 13:31:49 -0000 Received: from unknown (HELO smtp3.nottingham.ac.uk) (128.243.44.55) by engine03-20433-8.icritical.com (qpsmtpd/0.28) with ESMTP; Sun, 08 Dec 2013 13:31:49 +0000 Received: from uiwexhub02.ad.nottingham.ac.uk ([128.243.15.132]) by smtp3.nottingham.ac.uk with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77) (envelope-from ) id 1VpeSd-0000lK-Co for cl-mirage@lists.cam.ac.uk; Sun, 08 Dec 2013 13:31:51 +0000 From: Richard Mortier To: "mirageos-devel@lists.xenproject.org" , Mirage List Date: Sun, 8 Dec 2013 13:31:50 +0000 Subject: opam repository problems Thread-Topic: opam repository problems Thread-Index: Ac70Gdnju7cCRJnlRv+A1/IBfu/v2w== Message-ID: <81A1D320-E98A-4678-AE44-D88338FA45BE@nottingham.ac.uk> Accept-Language: en-US, en-GB Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, en-GB Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Scanned: by iCritical at engine03-20433-8.icritical.com X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 08 Dec 2013 13:31:54 -0000 Content-Length: 1234 Lines: 30 is anyone else noticing anything? from what i can currently observe,=20 + opam.ocamlpro.org is quite out of date (seems to still give me omd.0.6.0 = rather than omd.0.8.2 for example) + opam.ocaml.org is fine for opam.1.1.0 but has a broken repository for opa= m.1.0.0 are these know problems, or should i file issues somewhere? (the combination is holding up some PRs for dependencies for the mirage blo= gging libraries because they can't pass travis...) --=20 Cheers, R. This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it. Please do not use, copy or disclose the information contained in this message or in any attachment. Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham. This message has been checked for viruses but the contents of an attachment may still contain software viruses which could damage your computer system, you are advised to perform your own checks. Email communications with the University of Nottingham may be monitored as permitted by UK legislation. From Ian.Campbell@citrix.com Mon Dec 09 13:20:32 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1Vq0lE-0003Qx-76 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 09 Dec 2013 13:20:32 +0000 X-Cam-SpamDetails: score -0.7 from SpamAssassin-3.3.2-1549009 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [66.165.176.63 listed in list.dnswl.dnsbl.ja.net] * -0.0 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp02.citrix.com ([66.165.176.63]:50208) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1Vq0lC-0000Au-2H (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 09 Dec 2013 13:20:32 +0000 X-IronPort-AV: E=Sophos;i="4.93,857,1378857600"; d="scan'208";a="79993409" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 09 Dec 2013 13:20:28 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL01.citrite.net (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Mon, 9 Dec 2013 08:20:27 -0500 Message-ID: <1386595227.30459.21.camel@kazak.uk.xensource.com> Subject: Re: [Xen-devel] Testing for the Xen Project From: Ian Campbell To: Date: Mon, 9 Dec 2013 13:20:27 +0000 In-Reply-To: <5294A073.9000209@xen.org> References: <5294A073.9000209@xen.org> Organization: Citrix Systems, Inc. Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Dec 2013 13:20:32 -0000 Content-Length: 12229 Lines: 275 On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote: > Hi all, > > you probably have all heard by now that the Xen Project Advisory Board > (a group of vendors who provide funds to the Xen Project that are > intended to be used for the good of the community) recently created the > Test Framework Working > Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains more > information about the group. The working group had its first meeting a > few weeks ago and one of the actions I had was to kick off a thread on > development lists to figure out what would help the developer community. > > I was planning to kick off this thread with some questions and options, > which reflect some discussions I had with individuals in the community, > various meetings (WG and AB meetings), etc. which I condensed into a > picture. > > This reflects my personal opinion (not a Citrix opinion) and is merely > intended to get a discussion going. Feel free to pick it apart: I won’t > be upset. > > First, I wanted to clear up a few misconceptions that I have heard from > a few people: > > * The Advisory Board has funds that can be used to create an > independently hosted test infrastructure to help the developer > community. However, funds are limited. Thus, it is important that we do > what is right for the Xen community in the short term and the longer > term. Otherwise, we will burn funds that could be used to help the Xen > community in other ways. > * The Test Framework Working Group is made up of people employed by > vendors who have some experience in testing. > * There is no intention to prescribe a test environment that you then > have to use. Advisory Board members made clear to me that they want to > make sure that what we end up with a solution that works for you. > * At the Xen Developer Summit two different solutions for system testing > were presented. The intention was to explain what is there and what we > can use going forward. A presentation on OSSTest which runs regularly > today was given. And one for XenRT, for which there is a plan to get a > small 3 box system up and running that can be used for you to look at. > Citrix volunteered to set this up at its own cost. > * Just to be clear: what works for you may be one of these, none of > these, both of them, … > * There may also be different answers in the short and the long run. > * At the end of the day, different community members will have different > views. Also the Advisory Board members who provide the funds, will also > have specific interests that they will push for. Thus, in all > likelihood, we will have to find a good enough compromise. > * The vast majority of Advisory Board members care about the Hypervisor > (and not so much about XAPI and Mirage OS). Thus, it is likely that the > focus of the test system would be the Hypervisor. > > So let me try and condense some of the arguments and opinions I heard > and information that is around. This list may be incomplete. > > == Work Flow == > > I added this section, because some members of the community and the > working group had prior experience with attempts to introduce a test > infrastructure for an open source community in the past, and these may > not have worked as well as hoped. I made up some of the terminology. > > *Local testing*: the basic idea here is for a developer to write their [...] We have a small amount of local test suites in the tree (e.g. vif and disk config parsing have little test suites) but it could do with tying together with some infrastructure into something which is simple to run (currently it requires an installed Xen system and there is no one single way to run something). As you correctly suggest there is a limit to how much local testing can cover in terms of elapsed time, available resources, the configurations which can be reasonably set up, running on real hardware etc. IMHO This could benefit from an enthusiastic (or press-ganged by their manager ;-)) community member putting some time into tying it all together into something which we can ask people to run before submitting with a straight face. > *System testing*: both OSSTest and XenRT are essentially system test [...] I think most people use "system testing" to mean testing of the integrated whole, as opposed to e.g. unit testing. The current "automated test" which we have covers some aspects of both whole system and unit testing. Anyway, terminology aside, the existing osstest stuff is *extremely* valuable IMHO, and the system testing has been very useful over the majority of the lifetime of the xen project, at least as long as I've been involved. The main limitation is the amount of resources dedicated to it, in terms of hardware (and its location within citrix infrastructure doesn't help here) and test coverage. Even with its current set of tests and limited hardware it already tests far more than we could ever realistically ask people to do locally before submitting and it catches real issues on real hardware. Any local test stuff should obviously be integrated into the system tests as a step as well. I notice that your description of system test omits the targeted local testing which we expect contributors to do before submitting a patch -- by targeted I mean you are changing $FOO therefore you should be trying $FOO! And if you think you might have an impact on $BAR you should be testing that too. I just mention it because your description seemed to imply (inadvertently I expect) that there was no testing at all between writing the code and the system tests running, which is not quite accurate. IMHO both local and system test are valuable. I think the local testing situation can be improved by people working within the community to do the work (in particular building out the infrastructure), whereas the system testing side of things would benefit greatly from any resourcing which the AB can provide in terms of hardware, hosting and sysadmin time etc. There is no doubt in my mind that this would be beneficial to the community in both the short and long term. It might also be worth considering spending some money kickstarting the actual tests (i.e. fleshing out the suites) in both cases, but I think ultimately I think this needs to be driven by community member (AB or otherwise) who care about particular functionality making sure the tests exist, probably by writing them. So in terms of budget I think that would be secondary to sorting out the hosting etc > *Test on demand:* this would be a mixture between local testing and [...] I think it would be nice long term goal to aim for this but short term the other two types of testing are more important. > IMHO, this would be a nice mid to long-term goal, > assuming it could be made to work with the funds we have. Heh, I should read right to the end ;-) > == OSSTest == > > What runs now and thus easiest to get started on > > More Info > *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-osstest/ > *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-step-by-step/ > *http://www.youtube.com/watch?v=JxTFZIwZzJ8 > > Problems: > * Runs on Citrix premises (thus general access is an issue) > * Ian Jackson is acting as sys-admin in his spare time. But, the > Advisory Board could provide resource to fix this > * Basic test coverage > * Not a lot of documentation right now (which is a bit of a barrier to > adoption) > > Risks > * Not well understood (maybe you guys can fill the gaps) This is slowly changing, Wei, Roger and myself have all done development with osstest and contributed (or are in the process of doing so) new bits of testing. I think Dario and Anthony have played with it too. There is certainly more which could be done here in terms of documentation. I at least was planning to make this part of my focus on future documentation and/or test days. I think all of the above applies equally to XenRT, either system is going to have a learning curve and is going to need documentation for the community etc. > == XenRT == > > Used by Citrix for XenServer testing. Tarballs have been made available > by Citrix under a BSD license. But the code has not been put into live > repos: my understanding is that Citrix would do this, if the Xen > community believes this is valuable. > > More Info > *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT > *http://www.youtube.com/watch?v=s11_Iw7AI_U > > Problems: > * No publicly accessible demo instance (this is being worked on – to be > hosted on a small test bed at http://osuosl.org/ – work sponsored by Citrix) > * Currently does not yet support “xl” (a “xl” connector is being worked > on – sponsored by Citrix) > * Code not in yet public repo > > Potentially Interesting Properties: > * Very large test coverage (including performance, security and other > tests). Most of them should work once an “xl” connector is in place I think that's rather optimistic. I would expect that a reasonable proportion of the interesting tests will require features of xapi to work, e.g. pools of hosts, storage management, networking etc and/or require some amount of reworking to function with xl. > * Been in production at scale for a long time: thus well understood > * XenRT has a lot of provisioning functionality and supports a > distributed architecture: aka the ability to manage machines in > different locations (data centres). The detail is abstracted away from > users. This creates some interesting possibilities. For example: > ** Hardware Vendors on the Advisory Board could provide hardware to the > community on their site (assuming that these can be hosted outside a > firewall). Some HW vendors on the AB indicated that this would indeed be > doable. > ** This would open up the opportunity to make available cutting edge or > “unusual” HW for testing to the community. > ** It would also mean that machines that would be expensive to ship and > host by the project, could be hosted on premise by AB vendors > * XenRT has the capability to “inject” some test code on the fly (i.e. > the test code is attached to a job that is submitted). > * I checked this with the XenRT devs and the *Test on demand* approach > should be relatively easy to implement, but does not exist. > > I do not know what of the above would apply to OSSTest. I think it is all equally doable for either. > Risks > * Complexity > * The cost of supporting such a system may be too high > * Not in use by the community today > * Not clear whether a *local test* version of XenRT is feasible > > == Support and Ownership == > > Whatever solution we go for, needs to be properly funded and looked > after. >From the remainder of the paragraph I think you are talking specifically about hiring a test person here I think? I think this is essential, the current testing is done on a shoe string and that is one of its main limiting factors. > This is understood and the intention would be for the Xen Project > (aka Advisory Board) to fund a Linux Foundation employee to do this on > behalf of the Xen Project: this is a bit like Greg KH and others being > LF employees working on the kernel. Some vendors on the Advisory Board > indicated that providing Colo/hosting space and HW would be possible in > principle, which could help keeping the cost manageable. We should certainly be taking them up on those offers IMHO. > == Access == > > Any central system, has of course the issue of access control and > managing users. This is obviously a barrier to entry (if we do not have > also a local test mechanism). Am wondering how other FOSS communities > handle this. This should certainly be the job of the Test Framework > owner (see above). At a minimum it ought to be possible to allow access to any employee of a project member, since we have the opportunity through the membership process to put whatever paperwork and agreements (acceptable use etc) in place. Unfettered access for anyone who rocks up and asks is a bit trickier. I'm quite happy to let that be the framework owner's problem ;-) Ian. From lars.kurth.xen@gmail.com Tue Dec 10 18:15:53 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VqRqb-000338-FY (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:15:53 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1549514 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [209.85.212.170 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (lars.kurth.xen[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wi0-f170.google.com ([209.85.212.170]:54662) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VqRqa-0005ee-2h (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:15:53 +0000 Received: by mail-wi0-f170.google.com with SMTP id hq4so5753479wib.1 for ; Tue, 10 Dec 2013 10:15:52 -0800 (PST) X-Received: by 10.180.109.201 with SMTP id hu9mr20343881wib.59.1386699352447; Tue, 10 Dec 2013 10:15:52 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id fu1sm7248724wib.8.2013.12.10.10.15.50 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Dec 2013 10:15:51 -0800 (PST) Sender: Lars Kurth Message-ID: <52A75A56.90001@xen.org> Date: Tue, 10 Dec 2013 18:15:50 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: George Dunlap Subject: Re: [Xen-devel] Testing for the Xen Project References: <5294A073.9000209@xen.org> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 8bit Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list Reply-To: lars.kurth@xen.org List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 18:15:53 -0000 Content-Length: 1981 Lines: 43 On 02/12/2013 15:55, George Dunlap wrote: > On Tue, Nov 26, 2013 at 1:21 PM, Lars Kurth wrote: >> Hi all, >> >> you probably have all heard by now that the Xen Project Advisory Board (a >> group of vendors who provide funds to the Xen Project that are intended to >> be used for the good of the community) recently created the Test Framework >> Working Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains >> more information about the group. The working group had its first meeting a >> few weeks ago and one of the actions I had was to kick off a thread on >> development lists to figure out what would help the developer community. >> >> I was planning to kick off this thread with some questions and options, >> which reflect some discussions I had with individuals in the community, >> various meetings (WG and AB meetings), etc. which I condensed into a >> picture. >> >> This reflects my personal opinion (not a Citrix opinion) and is merely >> intended to get a discussion going. Feel free to pick it apart: I won’t be >> upset. > While I have a few quibbles, what you wrote seems to be a fair > reflection of the situation as a whole. But I don't really see any > action items, or questions. So other than quibble with little > details, I don't see a way to engage with this and actually have a > discussion. :-) > > What do you need from us right now? Sorry, I missed this reply. Maybe this was all a bit too abstract What I am looking for is: * Are there any specific needs that you have that should be considered in this discussion * Is there anything in the way we do tests now that really sucks and thus should be fixed * Are there any red lines - aka any solutions, approaches, etc. - that in your opinion would prevent yourself and the community from using a common test framework * I am also looking for one (or maybe two) volunteers who can represent the developer communities view within the test framework WG Lars From lars.kurth.xen@gmail.com Tue Dec 10 18:30:02 2013 Received: from ppsw-52.csi.cam.ac.uk ([131.111.8.152]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VqS4I-0003Dd-8v (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:30:02 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1549514 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.49 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (lars.kurth.xen[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wg0-f49.google.com ([74.125.82.49]:59653) by ppsw-52.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.148]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VqS4G-0007YR-Fo (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:30:02 +0000 Received: by mail-wg0-f49.google.com with SMTP id x12so5242116wgg.28 for ; Tue, 10 Dec 2013 10:30:00 -0800 (PST) X-Received: by 10.180.75.202 with SMTP id e10mr20417910wiw.8.1386700200543; Tue, 10 Dec 2013 10:30:00 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id n6sm7377832wix.3.2013.12.10.10.29.59 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Dec 2013 10:29:59 -0800 (PST) Sender: Lars Kurth Message-ID: <52A75DA6.4020201@xen.org> Date: Tue, 10 Dec 2013 18:29:58 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Ian Campbell Subject: Re: [Xen-devel] Testing for the Xen Project References: <5294A073.9000209@xen.org> <1386595227.30459.21.camel@kazak.uk.xensource.com> In-Reply-To: <1386595227.30459.21.camel@kazak.uk.xensource.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list Reply-To: lars.kurth@xen.org List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 18:30:02 -0000 Content-Length: 13742 Lines: 296 Ian, I think that is a good assessment and thanks for pointing out some gaps in my understanding. So to summarize: * We have some local test suites which could be run, but are probably not as they are poorly documented * We expect people to do some targetted local testing (presumably performed in a manual manner) of the features they developed and of those which may be impacted. Bt we don't actually always know whether they do. * osstest (or system testing in general) is *extremely* valuable * building out the infrastructure for system testing (aka number and diversity of boxes) would be extremely valuable - this really means funding hardware, hosting and sysadmin time * It might also be worth considering spending some money kickstarting the actual tests (i.e. fleshing out the suites) * *Test on demand* would be a nice long term goal * Some members of the community are intending to make OSSTest more accessible by improving docs and sharing their experience * At a minimum it ought to be possible to allow access to any employee of, a project member, since we have the opportunity through the membership, process to put whatever paperwork and agreements (acceptable use etc) in place. Lars On 09/12/2013 13:20, Ian Campbell wrote: > On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote: >> Hi all, >> >> you probably have all heard by now that the Xen Project Advisory Board >> (a group of vendors who provide funds to the Xen Project that are >> intended to be used for the good of the community) recently created the >> Test Framework Working >> Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains more >> information about the group. The working group had its first meeting a >> few weeks ago and one of the actions I had was to kick off a thread on >> development lists to figure out what would help the developer community. >> >> I was planning to kick off this thread with some questions and options, >> which reflect some discussions I had with individuals in the community, >> various meetings (WG and AB meetings), etc. which I condensed into a >> picture. >> >> This reflects my personal opinion (not a Citrix opinion) and is merely >> intended to get a discussion going. Feel free to pick it apart: I won’t >> be upset. >> >> First, I wanted to clear up a few misconceptions that I have heard from >> a few people: >> >> * The Advisory Board has funds that can be used to create an >> independently hosted test infrastructure to help the developer >> community. However, funds are limited. Thus, it is important that we do >> what is right for the Xen community in the short term and the longer >> term. Otherwise, we will burn funds that could be used to help the Xen >> community in other ways. >> * The Test Framework Working Group is made up of people employed by >> vendors who have some experience in testing. >> * There is no intention to prescribe a test environment that you then >> have to use. Advisory Board members made clear to me that they want to >> make sure that what we end up with a solution that works for you. >> * At the Xen Developer Summit two different solutions for system testing >> were presented. The intention was to explain what is there and what we >> can use going forward. A presentation on OSSTest which runs regularly >> today was given. And one for XenRT, for which there is a plan to get a >> small 3 box system up and running that can be used for you to look at. >> Citrix volunteered to set this up at its own cost. >> * Just to be clear: what works for you may be one of these, none of >> these, both of them, … >> * There may also be different answers in the short and the long run. >> * At the end of the day, different community members will have different >> views. Also the Advisory Board members who provide the funds, will also >> have specific interests that they will push for. Thus, in all >> likelihood, we will have to find a good enough compromise. >> * The vast majority of Advisory Board members care about the Hypervisor >> (and not so much about XAPI and Mirage OS). Thus, it is likely that the >> focus of the test system would be the Hypervisor. >> >> So let me try and condense some of the arguments and opinions I heard >> and information that is around. This list may be incomplete. >> >> == Work Flow == >> >> I added this section, because some members of the community and the >> working group had prior experience with attempts to introduce a test >> infrastructure for an open source community in the past, and these may >> not have worked as well as hoped. I made up some of the terminology. >> >> *Local testing*: the basic idea here is for a developer to write their > [...] > > We have a small amount of local test suites in the tree (e.g. vif and > disk config parsing have little test suites) but it could do with tying > together with some infrastructure into something which is simple to run > (currently it requires an installed Xen system and there is no one > single way to run something). > > As you correctly suggest there is a limit to how much local testing can > cover in terms of elapsed time, available resources, the configurations > which can be reasonably set up, running on real hardware etc. IMHO This > could benefit from an enthusiastic (or press-ganged by their > manager ;-)) community member putting some time into tying it all > together into something which we can ask people to run before submitting > with a straight face. > > >> *System testing*: both OSSTest and XenRT are essentially system test > [...] > > I think most people use "system testing" to mean testing of the > integrated whole, as opposed to e.g. unit testing. The current > "automated test" which we have covers some aspects of both whole system > and unit testing. > > Anyway, terminology aside, the existing osstest stuff is *extremely* > valuable IMHO, and the system testing has been very useful over the > majority of the lifetime of the xen project, at least as long as I've > been involved. The main limitation is the amount of resources dedicated > to it, in terms of hardware (and its location within citrix > infrastructure doesn't help here) and test coverage. > > Even with its current set of tests and limited hardware it already tests > far more than we could ever realistically ask people to do locally > before submitting and it catches real issues on real hardware. > > Any local test stuff should obviously be integrated into the system > tests as a step as well. > > I notice that your description of system test omits the targeted local > testing which we expect contributors to do before submitting a patch -- > by targeted I mean you are changing $FOO therefore you should be trying > $FOO! And if you think you might have an impact on $BAR you should be > testing that too. I just mention it because your description seemed to > imply (inadvertently I expect) that there was no testing at all between > writing the code and the system tests running, which is not quite > accurate. > > IMHO both local and system test are valuable. I think the local testing > situation can be improved by people working within the community to do > the work (in particular building out the infrastructure), whereas the > system testing side of things would benefit greatly from any resourcing > which the AB can provide in terms of hardware, hosting and sysadmin time > etc. There is no doubt in my mind that this would be beneficial to the > community in both the short and long term. > > It might also be worth considering spending some money kickstarting the > actual tests (i.e. fleshing out the suites) in both cases, but I think > ultimately I think this needs to be driven by community member (AB or > otherwise) who care about particular functionality making sure the tests > exist, probably by writing them. So in terms of budget I think that > would be secondary to sorting out the hosting etc > >> *Test on demand:* this would be a mixture between local testing and > [...] > > I think it would be nice long term goal to aim for this but short term > the other two types of testing are more important. > >> IMHO, this would be a nice mid to long-term goal, >> assuming it could be made to work with the funds we have. > Heh, I should read right to the end ;-) > >> == OSSTest == >> >> What runs now and thus easiest to get started on >> >> More Info >> *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-osstest/ >> *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-step-by-step/ >> *http://www.youtube.com/watch?v=JxTFZIwZzJ8 >> >> Problems: >> * Runs on Citrix premises (thus general access is an issue) >> * Ian Jackson is acting as sys-admin in his spare time. But, the >> Advisory Board could provide resource to fix this >> * Basic test coverage >> * Not a lot of documentation right now (which is a bit of a barrier to >> adoption) >> >> Risks >> * Not well understood (maybe you guys can fill the gaps) > This is slowly changing, Wei, Roger and myself have all done development > with osstest and contributed (or are in the process of doing so) new > bits of testing. I think Dario and Anthony have played with it too. > There is certainly more which could be done here in terms of > documentation. I at least was planning to make this part of my focus on > future documentation and/or test days. > > I think all of the above applies equally to XenRT, either system is > going to have a learning curve and is going to need documentation for > the community etc. > >> == XenRT == >> >> Used by Citrix for XenServer testing. Tarballs have been made available >> by Citrix under a BSD license. But the code has not been put into live >> repos: my understanding is that Citrix would do this, if the Xen >> community believes this is valuable. >> >> More Info >> *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT >> *http://www.youtube.com/watch?v=s11_Iw7AI_U >> >> Problems: >> * No publicly accessible demo instance (this is being worked on – to be >> hosted on a small test bed at http://osuosl.org/ – work sponsored by Citrix) >> * Currently does not yet support “xl” (a “xl” connector is being worked >> on – sponsored by Citrix) >> * Code not in yet public repo >> >> Potentially Interesting Properties: >> * Very large test coverage (including performance, security and other >> tests). Most of them should work once an “xl” connector is in place > I think that's rather optimistic. I would expect that a reasonable > proportion of the interesting tests will require features of xapi to > work, e.g. pools of hosts, storage management, networking etc and/or > require some amount of reworking to function with xl. > >> * Been in production at scale for a long time: thus well understood >> * XenRT has a lot of provisioning functionality and supports a >> distributed architecture: aka the ability to manage machines in >> different locations (data centres). The detail is abstracted away from >> users. This creates some interesting possibilities. For example: >> ** Hardware Vendors on the Advisory Board could provide hardware to the >> community on their site (assuming that these can be hosted outside a >> firewall). Some HW vendors on the AB indicated that this would indeed be >> doable. >> ** This would open up the opportunity to make available cutting edge or >> “unusual” HW for testing to the community. >> ** It would also mean that machines that would be expensive to ship and >> host by the project, could be hosted on premise by AB vendors >> * XenRT has the capability to “inject” some test code on the fly (i.e. >> the test code is attached to a job that is submitted). >> * I checked this with the XenRT devs and the *Test on demand* approach >> should be relatively easy to implement, but does not exist. >> >> I do not know what of the above would apply to OSSTest. > I think it is all equally doable for either. > >> Risks >> * Complexity >> * The cost of supporting such a system may be too high >> * Not in use by the community today >> * Not clear whether a *local test* version of XenRT is feasible >> >> == Support and Ownership == >> >> Whatever solution we go for, needs to be properly funded and looked >> after. > From the remainder of the paragraph I think you are talking specifically > about hiring a test person here I think? > > I think this is essential, the current testing is done on a shoe string > and that is one of its main limiting factors. > >> This is understood and the intention would be for the Xen Project >> (aka Advisory Board) to fund a Linux Foundation employee to do this on >> behalf of the Xen Project: this is a bit like Greg KH and others being >> LF employees working on the kernel. Some vendors on the Advisory Board >> indicated that providing Colo/hosting space and HW would be possible in >> principle, which could help keeping the cost manageable. > We should certainly be taking them up on those offers IMHO. > >> == Access == >> >> Any central system, has of course the issue of access control and >> managing users. This is obviously a barrier to entry (if we do not have >> also a local test mechanism). Am wondering how other FOSS communities >> handle this. This should certainly be the job of the Test Framework >> owner (see above). > At a minimum it ought to be possible to allow access to any employee of > a project member, since we have the opportunity through the membership > process to put whatever paperwork and agreements (acceptable use etc) in > place. > > Unfettered access for anyone who rocks up and asks is a bit trickier. > I'm quite happy to let that be the framework owner's problem ;-) > > Ian. > > > > > > > > > > > > > > From lars.kurth.xen@gmail.com Tue Dec 10 18:35:33 2013 Received: from ppsw-32.csi.cam.ac.uk ([131.111.8.132]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VqS9d-0003Nj-MF (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:35:33 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1549514 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.173 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (lars.kurth.xen[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-we0-f173.google.com ([74.125.82.173]:47546) by ppsw-32.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.146]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VqS9d-0003oP-0a (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:35:33 +0000 Received: by mail-we0-f173.google.com with SMTP id u57so5380581wes.18 for ; Tue, 10 Dec 2013 10:35:32 -0800 (PST) X-Received: by 10.180.7.136 with SMTP id j8mr20882122wia.17.1386700532876; Tue, 10 Dec 2013 10:35:32 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id mt2sm7397134wic.7.2013.12.10.10.35.31 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Dec 2013 10:35:32 -0800 (PST) Sender: Lars Kurth Message-ID: <52A75EF1.6040501@xen.org> Date: Tue, 10 Dec 2013 18:35:29 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Dario Faggioli Subject: Re: [Xen-devel] Developer Dashboards for Xen Project sub-projects (need input) References: <52790B64.2060101@xen.org> <1385517429.15201.106.camel@Solace> In-Reply-To: <1385517429.15201.106.camel@Solace> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list Reply-To: lars.kurth@xen.org List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 18:35:33 -0000 Content-Length: 752 Lines: 20 On 27/11/2013 01:57, Dario Faggioli wrote: > >> We can do similar things for XAPI and Mirage. >> >> >> So what I am looking for is >> a) a discussion on the list on what might be useful, and >> b) a number of volunteers (ideally one per project) who will work with >> me and the vendor getting this off the ground >> > Can we have some more info (if you have them yourself) on what it is > that the volunteers would need to do? I did some more work with the vendor and I think at this stage we should just go for the standard package per sub-project. What I was originally looking for was to really figure out whether for example the review process is well defined enough to maybe do some automated analysis. But we can always do this later. Lars From lars.kurth.xen@gmail.com Tue Dec 10 18:42:54 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VqSGk-0003V5-Nq (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:42:54 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1549514 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.46 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (lars.kurth.xen[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-wg0-f46.google.com ([74.125.82.46]:52963) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VqSGk-0000v1-gp (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:42:54 +0000 Received: by mail-wg0-f46.google.com with SMTP id m15so5278780wgh.13 for ; Tue, 10 Dec 2013 10:42:54 -0800 (PST) X-Received: by 10.194.59.240 with SMTP id c16mr22678205wjr.13.1386700973917; Tue, 10 Dec 2013 10:42:53 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id q19sm7466116wiw.4.2013.12.10.10.42.51 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Dec 2013 10:42:52 -0800 (PST) Sender: Lars Kurth Message-ID: <52A760AA.3020405@xen.org> Date: Tue, 10 Dec 2013 18:42:50 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] Developer Dashboards for Xen Project sub-projects (need input) References: <52790B64.2060101@xen.org> <20131125143555.GA6095@phenom.dumpdata.com> In-Reply-To: <20131125143555.GA6095@phenom.dumpdata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list Reply-To: lars.kurth@xen.org List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 18:42:54 -0000 Content-Length: 3576 Lines: 75 On 25/11/2013 14:35, Konrad Rzeszutek Wilk wrote: > . snip.. >> I wanted to start a discussion about this and what would be useful. >> For the Hypervisor for example, we could track activity on xen.git >> and osstest.git on master as well as stable branches (not sure >> whether there is any point in tracking activity on staging >> branches). There is also stuff they can do such as map >> activity/authors/ to code, etc. >> See the example below which maps authors to kernel components. >> >> The mailing lists plugins are quite sophisticated apparently (they >> have support for the Linux kernel and its workflow) and have a lot >> of filtering and tagging capabilities. For example it should be >> possible to >> * Model our code review process and link it to commits (assuming >> that in the majority of cases there is a mapping between patch >> series and commit, e.g. via commit message or similar). I believe in >> our case we do have a mapping which would enable this. >> * It can in theory handle osstest mails and xenbugs, etc. - although >> this will probably require customization which will add extra set-up >> cost >> * We can track specific keywords in list conversations (e.g. arm, >> etc. as useful) and create custom views if we want to >> >> There is probably a lot more which can be done, but I believe that >> git activity, code review and list activity are most valuable for >> now. We may be able to use this for PVOPS and other upstreams too, >> but usefulness is an open question. > pvops is mostly Linus upstream. We have some patches - but every > merge window we flush them out to Linus. I checked with the vendor and they could run stats on part of a git tree (using a git log command to just process what we care about) >> We can do similar things for XAPI and Mirage. >> >> So what I am looking for is >> a) a discussion on the list on what might be useful, and >> b) a number of volunteers (ideally one per project) who will work >> with me and the vendor getting this off the ground > I like the idea of getting an idea of 'we are getting less and less > commits in this area' as a way to figure out what needs attention > (or perhaps no need). > > But not every week, not every month either - quaterly is nice enough. > Or maybe once a year (say at Xen Summit?). But that should be possible > already right? Or is it a major pain to create those nice graphs? It is a major pain. > What is the overall goal? > > From my PoV my feeling is that: > a). I need to hire more folks > b). I have more things we want to do than there are > developers. I probably have different goals than you would have. For example: * Creater reports that I can use to demonstrate things are going well for the community * Identifying potential problems in the community etc. > And I think the same is true for everybody else. But I don't know > if this dashboard will help in this regards? > > Or is it a way to use that information to figure out overall > trends of changes + test coverage -> good/bad patch ratio? > Good question: I don't think this is possible with what they have now. If it was possible to model the review process it is conceivable to identify components where the reviews take longer than expected (but we probably already know this). On the other hand, the xen-devel mailing list traffic is increasing (in Nov we had more than 4500 posts, whereas most of this year we had 3500). In other words it may be getting increasingly hard to keep on top of what is actually going on. Lars From lars.kurth.xen@gmail.com Tue Dec 10 18:47:28 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VqSLA-0003Yo-Nu (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:47:28 +0000 X-Cam-SpamDetails: score -0.6 from SpamAssassin-3.3.2-1549514 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [74.125.82.173 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (lars.kurth.xen[at]gmail.com) * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-we0-f173.google.com ([74.125.82.173]:65092) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VqSLA-0003GL-6p (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Tue, 10 Dec 2013 18:47:28 +0000 Received: by mail-we0-f173.google.com with SMTP id u57so5510312wes.32 for ; Tue, 10 Dec 2013 10:47:27 -0800 (PST) X-Received: by 10.194.175.202 with SMTP id cc10mr22480703wjc.48.1386701247821; Tue, 10 Dec 2013 10:47:27 -0800 (PST) Received: from [172.16.25.10] ([2.122.219.75]) by mx.google.com with ESMTPSA id mz10sm7518955wic.2.2013.12.10.10.47.25 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 10 Dec 2013 10:47:26 -0800 (PST) Sender: Lars Kurth Message-ID: <52A761BC.8010001@xen.org> Date: Tue, 10 Dec 2013 18:47:24 +0000 From: Lars Kurth User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: Dario Faggioli , Konrad Rzeszutek Wilk Subject: Re: [Xen-devel] Developer Dashboards for Xen Project sub-projects (need input) References: <52790B64.2060101@xen.org> <20131125143555.GA6095@phenom.dumpdata.com> <1385518798.15201.122.camel@Solace> In-Reply-To: <1385518798.15201.122.camel@Solace> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: "xen-devel@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-api@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list Reply-To: lars.kurth@xen.org List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Dec 2013 18:47:28 -0000 Content-Length: 1735 Lines: 44 On 27/11/2013 02:19, Dario Faggioli wrote: > >> But not every week, not every month either - quaterly is nice enough. >> Or maybe once a year (say at Xen Summit?). But that should be possible >> already right? Or is it a major pain to create those nice graphs? >> > Yes, I also agree that we should pick-up a proper periodicity with which > we look at this, or we risk going mad! :-) The way how the tool works is to just automatically produce stuff from source. >> What is the overall goal? >> >> From my PoV my feeling is that: >> a). I need to hire more folks >> b). I have more things we want to do than there are >> developers. >> >> And I think the same is true for everybody else. But I don't know >> if this dashboard will help in this regards? >> > Well, I think it goes way beyond that. > > Lars is collecting numbers and plotting graphs similar to the ones this > thing is able to produce from some time now, and, honestly, I think they > provide really useful information. They tell much more than just 'there > is more effort needed in this area', they, if done well, provide > insights about the health of a community that, in my opinion, every Open > Source project should be considering very seriously. > > As an example, have a look at his 'community roundup' from XS in > Edinburgh: > http://www.xenproject.org/component/allvideoshare/video/latest/xpds13-welcome.html > > So, if this allows for getting even more info with even less (or equal) > effort, I think it's 100% worth it. It took me 3 hours to get that NEWCOMERS vs DROPOUT graph together (should have thought this through before I started and written a script). Doing graphs today is generally a pain (even with scripts and tools). Lars From Ian.Campbell@citrix.com Wed Dec 11 10:12:16 2013 Received: from ppsw-52.csi.cam.ac.uk ([131.111.8.152]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1Vqgm8-0004MR-N0 (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 11 Dec 2013 10:12:16 +0000 X-Cam-SpamDetails: score -0.9 from SpamAssassin-3.3.2-1549785 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [66.165.176.63 listed in list.dnswl.dnsbl.ja.net] * -0.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp02.citrix.com ([66.165.176.63]:22806) by ppsw-52.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.148]:25) with esmtps (TLSv1:RC4-SHA:128) id 1Vqgm7-0007e5-D7 (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 11 Dec 2013 10:12:16 +0000 X-IronPort-AV: E=Sophos;i="4.93,870,1378857600"; d="scan'208";a="80817354" Received: from accessns.citrite.net (HELO FTLPEX01CL02.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 11 Dec 2013 10:12:13 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL02.citrite.net (10.13.107.79) with Microsoft SMTP Server id 14.2.342.4; Wed, 11 Dec 2013 05:12:12 -0500 Message-ID: <1386756731.30271.22.camel@kazak.uk.xensource.com> Subject: Re: [Xen-devel] Testing for the Xen Project From: Ian Campbell To: Date: Wed, 11 Dec 2013 10:12:11 +0000 In-Reply-To: <52A75DA6.4020201@xen.org> References: <5294A073.9000209@xen.org> <1386595227.30459.21.camel@kazak.uk.xensource.com> <52A75DA6.4020201@xen.org> Organization: Citrix Systems, Inc. Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: "xen-api@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , "xen-devel@lists.xen.org" X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2013 10:12:16 -0000 Content-Length: 15253 Lines: 327 On Tue, 2013-12-10 at 18:29 +0000, Lars Kurth wrote: > Ian, > > I think that is a good assessment and thanks for pointing out some gaps > in my understanding. No problem. > So to summarize: > * We have some local test suites which could be run, but are probably > not as they are poorly documented More documentation is always good. adding a top level script or make target to actually run them in a trivial way would IMHO be even more valuable in the short term. Having that target/script be easily extensible to other suites would be a must as well since we have some but not many of these sorts of tests. > * We expect people to do some targetted local testing (presumably > performed in a manual manner) of the features they developed and of > those which may be impacted. Bt we don't actually always know whether > they do. It's occasionally obvious that someone hasn't tested (or sometimes even compiled) their patches, but for the most part it does appear that people are actually doing this bit and I think it is well understood as an expectation in all development environments (i.e. OSS communities but also commercial settings etc), not just ours. (as well as a common understanding that it's expected there's probably some element of not wanting to look stupid by posting patches which don't compile, or haven't been tested) > * osstest (or system testing in general) is *extremely* valuable > * building out the infrastructure for system testing (aka number and > diversity of boxes) would be extremely valuable - this really means > funding hardware, hosting and sysadmin time > * It might also be worth considering spending some money kickstarting > the actual tests (i.e. fleshing out the suites) > * *Test on demand* would be a nice long term goal > * Some members of the community are intending to make OSSTest more > accessible by improving docs and sharing their experience > * At a minimum it ought to be possible to allow access to any employee > of, a project member, since we have the opportunity through the > membership, process to put whatever paperwork and agreements (acceptable > use etc) in place. Ack to all that. Ian. > > Lars > > On 09/12/2013 13:20, Ian Campbell wrote: > > On Tue, 2013-11-26 at 13:21 +0000, Lars Kurth wrote: > >> Hi all, > >> > >> you probably have all heard by now that the Xen Project Advisory Board > >> (a group of vendors who provide funds to the Xen Project that are > >> intended to be used for the good of the community) recently created the > >> Test Framework Working > >> Group.http://wiki.xenproject.org/wiki/AB_WG/Test_Frameworkcontains more > >> information about the group. The working group had its first meeting a > >> few weeks ago and one of the actions I had was to kick off a thread on > >> development lists to figure out what would help the developer community. > >> > >> I was planning to kick off this thread with some questions and options, > >> which reflect some discussions I had with individuals in the community, > >> various meetings (WG and AB meetings), etc. which I condensed into a > >> picture. > >> > >> This reflects my personal opinion (not a Citrix opinion) and is merely > >> intended to get a discussion going. Feel free to pick it apart: I won’t > >> be upset. > >> > >> First, I wanted to clear up a few misconceptions that I have heard from > >> a few people: > >> > >> * The Advisory Board has funds that can be used to create an > >> independently hosted test infrastructure to help the developer > >> community. However, funds are limited. Thus, it is important that we do > >> what is right for the Xen community in the short term and the longer > >> term. Otherwise, we will burn funds that could be used to help the Xen > >> community in other ways. > >> * The Test Framework Working Group is made up of people employed by > >> vendors who have some experience in testing. > >> * There is no intention to prescribe a test environment that you then > >> have to use. Advisory Board members made clear to me that they want to > >> make sure that what we end up with a solution that works for you. > >> * At the Xen Developer Summit two different solutions for system testing > >> were presented. The intention was to explain what is there and what we > >> can use going forward. A presentation on OSSTest which runs regularly > >> today was given. And one for XenRT, for which there is a plan to get a > >> small 3 box system up and running that can be used for you to look at. > >> Citrix volunteered to set this up at its own cost. > >> * Just to be clear: what works for you may be one of these, none of > >> these, both of them, … > >> * There may also be different answers in the short and the long run. > >> * At the end of the day, different community members will have different > >> views. Also the Advisory Board members who provide the funds, will also > >> have specific interests that they will push for. Thus, in all > >> likelihood, we will have to find a good enough compromise. > >> * The vast majority of Advisory Board members care about the Hypervisor > >> (and not so much about XAPI and Mirage OS). Thus, it is likely that the > >> focus of the test system would be the Hypervisor. > >> > >> So let me try and condense some of the arguments and opinions I heard > >> and information that is around. This list may be incomplete. > >> > >> == Work Flow == > >> > >> I added this section, because some members of the community and the > >> working group had prior experience with attempts to introduce a test > >> infrastructure for an open source community in the past, and these may > >> not have worked as well as hoped. I made up some of the terminology. > >> > >> *Local testing*: the basic idea here is for a developer to write their > > [...] > > > > We have a small amount of local test suites in the tree (e.g. vif and > > disk config parsing have little test suites) but it could do with tying > > together with some infrastructure into something which is simple to run > > (currently it requires an installed Xen system and there is no one > > single way to run something). > > > > As you correctly suggest there is a limit to how much local testing can > > cover in terms of elapsed time, available resources, the configurations > > which can be reasonably set up, running on real hardware etc. IMHO This > > could benefit from an enthusiastic (or press-ganged by their > > manager ;-)) community member putting some time into tying it all > > together into something which we can ask people to run before submitting > > with a straight face. > > > > > >> *System testing*: both OSSTest and XenRT are essentially system test > > [...] > > > > I think most people use "system testing" to mean testing of the > > integrated whole, as opposed to e.g. unit testing. The current > > "automated test" which we have covers some aspects of both whole system > > and unit testing. > > > > Anyway, terminology aside, the existing osstest stuff is *extremely* > > valuable IMHO, and the system testing has been very useful over the > > majority of the lifetime of the xen project, at least as long as I've > > been involved. The main limitation is the amount of resources dedicated > > to it, in terms of hardware (and its location within citrix > > infrastructure doesn't help here) and test coverage. > > > > Even with its current set of tests and limited hardware it already tests > > far more than we could ever realistically ask people to do locally > > before submitting and it catches real issues on real hardware. > > > > Any local test stuff should obviously be integrated into the system > > tests as a step as well. > > > > I notice that your description of system test omits the targeted local > > testing which we expect contributors to do before submitting a patch -- > > by targeted I mean you are changing $FOO therefore you should be trying > > $FOO! And if you think you might have an impact on $BAR you should be > > testing that too. I just mention it because your description seemed to > > imply (inadvertently I expect) that there was no testing at all between > > writing the code and the system tests running, which is not quite > > accurate. > > > > IMHO both local and system test are valuable. I think the local testing > > situation can be improved by people working within the community to do > > the work (in particular building out the infrastructure), whereas the > > system testing side of things would benefit greatly from any resourcing > > which the AB can provide in terms of hardware, hosting and sysadmin time > > etc. There is no doubt in my mind that this would be beneficial to the > > community in both the short and long term. > > > > It might also be worth considering spending some money kickstarting the > > actual tests (i.e. fleshing out the suites) in both cases, but I think > > ultimately I think this needs to be driven by community member (AB or > > otherwise) who care about particular functionality making sure the tests > > exist, probably by writing them. So in terms of budget I think that > > would be secondary to sorting out the hosting etc > > > >> *Test on demand:* this would be a mixture between local testing and > > [...] > > > > I think it would be nice long term goal to aim for this but short term > > the other two types of testing are more important. > > > >> IMHO, this would be a nice mid to long-term goal, > >> assuming it could be made to work with the funds we have. > > Heh, I should read right to the end ;-) > > > >> == OSSTest == > >> > >> What runs now and thus easiest to get started on > >> > >> More Info > >> *http://blog.xen.org/index.php/2013/02/02/xen-automatic-test-system-osstest/ > >> *http://blog.xen.org/index.php/2013/09/30/osstest-standalone-mode-step-by-step/ > >> *http://www.youtube.com/watch?v=JxTFZIwZzJ8 > >> > >> Problems: > >> * Runs on Citrix premises (thus general access is an issue) > >> * Ian Jackson is acting as sys-admin in his spare time. But, the > >> Advisory Board could provide resource to fix this > >> * Basic test coverage > >> * Not a lot of documentation right now (which is a bit of a barrier to > >> adoption) > >> > >> Risks > >> * Not well understood (maybe you guys can fill the gaps) > > This is slowly changing, Wei, Roger and myself have all done development > > with osstest and contributed (or are in the process of doing so) new > > bits of testing. I think Dario and Anthony have played with it too. > > There is certainly more which could be done here in terms of > > documentation. I at least was planning to make this part of my focus on > > future documentation and/or test days. > > > > I think all of the above applies equally to XenRT, either system is > > going to have a learning curve and is going to need documentation for > > the community etc. > > > >> == XenRT == > >> > >> Used by Citrix for XenServer testing. Tarballs have been made available > >> by Citrix under a BSD license. But the code has not been put into live > >> repos: my understanding is that Citrix would do this, if the Xen > >> community believes this is valuable. > >> > >> More Info > >> *http://wiki.xenproject.org/wiki/Getting_Started_with_XenRT > >> *http://www.youtube.com/watch?v=s11_Iw7AI_U > >> > >> Problems: > >> * No publicly accessible demo instance (this is being worked on – to be > >> hosted on a small test bed at http://osuosl.org/ – work sponsored by Citrix) > >> * Currently does not yet support “xl” (a “xl” connector is being worked > >> on – sponsored by Citrix) > >> * Code not in yet public repo > >> > >> Potentially Interesting Properties: > >> * Very large test coverage (including performance, security and other > >> tests). Most of them should work once an “xl” connector is in place > > I think that's rather optimistic. I would expect that a reasonable > > proportion of the interesting tests will require features of xapi to > > work, e.g. pools of hosts, storage management, networking etc and/or > > require some amount of reworking to function with xl. > > > >> * Been in production at scale for a long time: thus well understood > >> * XenRT has a lot of provisioning functionality and supports a > >> distributed architecture: aka the ability to manage machines in > >> different locations (data centres). The detail is abstracted away from > >> users. This creates some interesting possibilities. For example: > >> ** Hardware Vendors on the Advisory Board could provide hardware to the > >> community on their site (assuming that these can be hosted outside a > >> firewall). Some HW vendors on the AB indicated that this would indeed be > >> doable. > >> ** This would open up the opportunity to make available cutting edge or > >> “unusual” HW for testing to the community. > >> ** It would also mean that machines that would be expensive to ship and > >> host by the project, could be hosted on premise by AB vendors > >> * XenRT has the capability to “inject” some test code on the fly (i.e. > >> the test code is attached to a job that is submitted). > >> * I checked this with the XenRT devs and the *Test on demand* approach > >> should be relatively easy to implement, but does not exist. > >> > >> I do not know what of the above would apply to OSSTest. > > I think it is all equally doable for either. > > > >> Risks > >> * Complexity > >> * The cost of supporting such a system may be too high > >> * Not in use by the community today > >> * Not clear whether a *local test* version of XenRT is feasible > >> > >> == Support and Ownership == > >> > >> Whatever solution we go for, needs to be properly funded and looked > >> after. > > From the remainder of the paragraph I think you are talking specifically > > about hiring a test person here I think? > > > > I think this is essential, the current testing is done on a shoe string > > and that is one of its main limiting factors. > > > >> This is understood and the intention would be for the Xen Project > >> (aka Advisory Board) to fund a Linux Foundation employee to do this on > >> behalf of the Xen Project: this is a bit like Greg KH and others being > >> LF employees working on the kernel. Some vendors on the Advisory Board > >> indicated that providing Colo/hosting space and HW would be possible in > >> principle, which could help keeping the cost manageable. > > We should certainly be taking them up on those offers IMHO. > > > >> == Access == > >> > >> Any central system, has of course the issue of access control and > >> managing users. This is obviously a barrier to entry (if we do not have > >> also a local test mechanism). Am wondering how other FOSS communities > >> handle this. This should certainly be the job of the Test Framework > >> owner (see above). > > At a minimum it ought to be possible to allow access to any employee of > > a project member, since we have the opportunity through the membership > > process to put whatever paperwork and agreements (acceptable use etc) in > > place. > > > > Unfettered access for anyone who rocks up and asks is a bit trickier. > > I'm quite happy to let that be the framework owner's problem ;-) > > > > Ian. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > From Ian.Campbell@citrix.com Wed Dec 11 10:18:13 2013 Received: from ppsw-42.csi.cam.ac.uk ([131.111.8.142]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1Vqgrt-0004hd-KA (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 11 Dec 2013 10:18:13 +0000 X-Cam-SpamDetails: score -0.9 from SpamAssassin-3.3.2-1549785 * -0.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [66.165.176.63 listed in list.dnswl.dnsbl.ja.net] X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp02.citrix.com ([66.165.176.63]:26685) by ppsw-42.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.149]:25) with esmtps (TLSv1:RC4-SHA:128) id 1Vqgrs-0005Me-9M (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 11 Dec 2013 10:18:13 +0000 X-IronPort-AV: E=Sophos;i="4.93,870,1378857600"; d="scan'208";a="80819048" Received: from accessns.citrite.net (HELO FTLPEX01CL03.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 11 Dec 2013 10:18:11 +0000 Received: from [10.80.2.80] (10.80.2.80) by FTLPEX01CL03.citrite.net (10.13.107.80) with Microsoft SMTP Server id 14.2.342.4; Wed, 11 Dec 2013 05:18:10 -0500 Message-ID: <1386757089.30271.28.camel@kazak.uk.xensource.com> Subject: Re: [Xen-devel] Developer Dashboards for Xen Project sub-projects (need input) From: Ian Campbell To: Date: Wed, 11 Dec 2013 10:18:09 +0000 In-Reply-To: <52A761BC.8010001@xen.org> References: <52790B64.2060101@xen.org> <20131125143555.GA6095@phenom.dumpdata.com> <1385518798.15201.122.camel@Solace> <52A761BC.8010001@xen.org> Organization: Citrix Systems, Inc. Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.4.4-3 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.80.2.80] X-DLP: MIA2 Cc: "xen-api@lists.xen.org" , Dario Faggioli , "xen-devel@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , Konrad Rzeszutek Wilk X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2013 10:18:13 -0000 Content-Length: 774 Lines: 21 On Tue, 2013-12-10 at 18:47 +0000, Lars Kurth wrote: I think I said this to you IRL (or if I said it on list I can't see it in my archives), so I suppose I should put it in the thread also: > It took me 3 hours to get that NEWCOMERS vs DROPOUT graph together > (should have thought this through before I started and written a > script). Doing graphs today is generally a pain (even with scripts and > tools). I think if this tool is useful and worth it to you as community manager[0] then you should go ahead and do it, any additional benefits to the rest of us are secondary/gravy/nice-to-have IMHO. Ian. [0] and saving you 3 hours each time you want some stats + giving you better data, with better trend analysis over time etc certainly seems worthwhile to me. From dario.faggioli@citrix.com Wed Dec 11 17:09:31 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VqnHv-0003l8-4f (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 11 Dec 2013 17:09:31 +0000 X-Cam-SpamDetails: score -0.9 from SpamAssassin-3.3.2-1549785 * -0.7 RCVD_IN_DNSWL_LOW RBL: Sender listed at http://www.dnswl.org/, low * trust * [66.165.176.63 listed in list.dnswl.dnsbl.ja.net] * -0.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay * domain X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from smtp02.citrix.com ([66.165.176.63]:30191) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VqnHu-0003iB-h1 (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Wed, 11 Dec 2013 17:09:31 +0000 X-IronPort-AV: E=Sophos;i="4.93,872,1378857600"; d="asc'?scan'208";a="80980903" Received: from accessns.citrite.net (HELO FTLPEX01CL01.citrite.net) ([10.9.154.239]) by FTLPIPO02.CITRIX.COM with ESMTP; 11 Dec 2013 17:09:28 +0000 Received: from [127.0.0.1] (10.80.16.47) by smtprelay.citrix.com (10.13.107.78) with Microsoft SMTP Server id 14.2.342.4; Wed, 11 Dec 2013 12:09:27 -0500 Message-ID: <1386781764.5488.35.camel@Solace> Subject: Re: [Xen-devel] Developer Dashboards for Xen Project sub-projects (need input) From: Dario Faggioli To: Date: Wed, 11 Dec 2013 18:09:24 +0100 In-Reply-To: <52A761BC.8010001@xen.org> References: <52790B64.2060101@xen.org> <20131125143555.GA6095@phenom.dumpdata.com> <1385518798.15201.122.camel@Solace> <52A761BC.8010001@xen.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-Br0hc70aoqJYezaj9Anj" X-Mailer: Evolution 3.8.5 (3.8.5-2.fc19) MIME-Version: 1.0 X-DLP: MIA2 Cc: "xen-api@lists.xen.org" , "xen-devel@lists.xen.org" , "cl-mirage@lists.cam.ac.uk List" , Konrad Rzeszutek Wilk X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 Dec 2013 17:09:31 -0000 Content-Length: 1611 Lines: 48 --=-Br0hc70aoqJYezaj9Anj Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On mar, 2013-12-10 at 18:47 +0000, Lars Kurth wrote: > On 27/11/2013 02:19, Dario Faggioli wrote: > > As an example, have a look at his 'community roundup' from XS in > > Edinburgh: > > http://www.xenproject.org/component/allvideoshare/video/latest/xpds13-w= elcome.html > > > > So, if this allows for getting even more info with even less (or equal) > > effort, I think it's 100% worth it. > It took me 3 hours to get that NEWCOMERS vs DROPOUT graph together=20 > (should have thought this through before I started and written a=20 > script). Doing graphs today is generally a pain (even with scripts and= =20 > tools). >=20 Right. On that ground, pending a bit more of clarification of what is it that you'd need from one of us (and whether or not you think you still need it), I confirm my availability to help. Regards, Dario --=20 <> (Raistlin Majere) ----------------------------------------------------------------- Dario Faggioli, Ph.D, http://about.me/dario.faggioli Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK) --=-Br0hc70aoqJYezaj9Anj Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.15 (GNU/Linux) iEYEABECAAYFAlKonEQACgkQk4XaBE3IOsQONgCeMyy7pCT81l5MOVGPqORh5vQ5 RjcAoJfuIB+OycsWUqeGZKFX3CSxfzRV =rYo0 -----END PGP SIGNATURE----- --=-Br0hc70aoqJYezaj9Anj-- From russell.pavlicek.xen@gmail.com Mon Dec 16 21:45:17 2013 Received: from ppsw-33.csi.cam.ac.uk ([131.111.8.133]) by lists-1.csi.cam.ac.uk (lists.cam.ac.uk [131.111.8.15]:25) with esmtp id 1VsfyX-0000x3-Bd (Exim 4.70) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 16 Dec 2013 21:45:17 +0000 X-Cam-SpamScore: ss X-Cam-SpamDetails: score 2.6 from SpamAssassin-3.3.2-1551006 * -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no * trust * [209.85.192.175 listed in list.dnswl.dnsbl.ja.net] * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider * (russell.pavlicek.xen[at]gmail.com) * 2.5 SUSPICIOUS_RECIPS Similar addresses in recipient list * 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily * valid * 0.0 T_DKIM_INVALID DKIM-Signature header exists but is not valid X-Cam-ScannerInfo: http://www.ucs.cam.ac.uk/email/scanner/ Received: from mail-pd0-f175.google.com ([209.85.192.175]:34962) by ppsw-33.csi.cam.ac.uk (mx.cam.ac.uk [131.111.8.147]:25) with esmtps (TLSv1:RC4-SHA:128) id 1VsfyW-0002ZU-hY (Exim 4.82_3-c0e5623) for cl-mirage@lists.cam.ac.uk (return-path ); Mon, 16 Dec 2013 21:45:17 +0000 Received: by mail-pd0-f175.google.com with SMTP id w10so5855491pde.34 for ; Mon, 16 Dec 2013 13:45:14 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.68.252.161 with SMTP id zt1mr23009874pbc.130.1387230314798; Mon, 16 Dec 2013 13:45:14 -0800 (PST) Sender: russell.pavlicek.xen@gmail.com Received: by 10.68.78.137 with HTTP; Mon, 16 Dec 2013 13:45:14 -0800 (PST) Date: Mon, 16 Dec 2013 16:45:14 -0500 X-Google-Sender-Auth: EwEFb0s6T0ejSdkQHmy73X-ANP8 Message-ID: Subject: Xen Project User Summit 2014 Location Survey From: Russ Pavlicek To: "xen-users@lists.xen.org" , xen-devel@lists.xen.org, xen-api@lists.xen.org, cl-mirage@lists.cam.ac.uk, xs-devel@lists.xenserver.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: cl-mirage@lists.cam.ac.uk X-Mailman-Version: 2.1.8 Precedence: list List-Id: MirageOS development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 16 Dec 2013 21:45:17 -0000 Content-Length: 451 Lines: 16 We are beginning the plans for the 2014 Xen Project User Summit, but we have a problem: We are not sure where it should be held! Help us out by taking a 2 minute survey about location of the User Summit. Also, let us know if it should be colocated with some other conference like we did last year. Just go to the survey link and let us know what you think: https://www.surveymonkey.com/s/YJQCHJ6 Thanks! Russ Pavlicek Coordinator for XPUS 2014